HP 8/20q HP StorageWorks Simple SAN Connection Manager 3.20 Release Notes (569 - Page 8

would have been registered by FDMI will not be available for the HBA ports that have been

Page 8 highlights

Workaround: For those HBAs affected, you must manually enter information (Host Name and OS type) for each Emulex HBA port in the server as prompted by SSCM. If you supply the Host Name and OS type for all HBA ports affected, there is no impact for LUN assignments. If you do not supply the Host Name and OS type, LUNs cannot be assigned to the individual server. All HBAs without a Host Name and OS type are grouped together. The information that would have been registered by FDMI will not be available for the HBA ports that have been manually added. This issue is expected to be fixed in the next release of the HBA driver. 8

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8

Workaround:
For those HBAs affected, you must manually enter information (Host Name and OS
type) for each Emulex HBA port in the server as prompted by SSCM. If you supply the Host Name
and OS type for all HBA ports affected, there is no impact for LUN assignments.
If you do not supply the Host Name and OS type, LUNs cannot be assigned to the individual
server. All HBAs without a Host Name and OS type are grouped together. The information that
would have been registered by FDMI will not be available for the HBA ports that have been
manually added.
This issue is expected to be fixed in the next release of the HBA driver.
8