HP StorageWorks FabricManager 5.4.0a release notes (AA-RWFHA-TE, March 2008)

Topology legend doe
snothaveareferencefor8Gblinks
The Topology legen
d d oes not have a graphic for 8Gb link. To display the link speed or
select the link in the Topology view position the mouse over the link.
Secure Sockets Layer (SSL) and the Management Console
When SSL is enabled for a fabric, the Fabric Manager Server Management Console
(SMC) does not verify the host name when authentication is set to switch-based. If the
CN of the switch cer t is not a switch IP address the Fabric M anager client startup fails.
Device Diagnostic wizard
The Device Diagnostic wizard might hang when you start to run an analysis. If this
happens, restart the Fabric Manager server. You can do this from the Services tab in
the server Man
agement Console.
End-to-End performance monitoring for Fabric OS 4.1.2 to 4.2.2b
In very rare circumstances, for switches running Fabric OS 4.1.2 to 4.2.2b, the PSD
might crash after enabling end-to-end performance monitoring from Fabric Manager 4.4
and later. This could lead to a switch reboot or failover.
Workaround: Upgrade to Fabric OS versions later than 4.2.2b, 4.4.0d, or 5.0.1; or
disable end-to-end performance monitoring from Fabric Manager.
Fabric discovery
If you use F
abric OS 4.4.0c or earlier 4.x releases as the launch switch, you will not see
any devices in Fabric Manager for the fabric if the Fabric Device Management Interface
(FDMI) capable devices are configured with port attributes.
Workaround: Upgrade to Fabric OS versions later than 4.4.0d or 4.4.2 .
Host Bus Adapter (HBA) firmware download
• When using Fabric Manager to download firm w ar e to the HBA, invalid firmware
files are downloaded. This causes the operation to report that it has finished
successfully; however, the firmware is corrupted when rebooted.
This is not a switch issue. The HBA loads any files, even if they are not meant
to be loaded.
• Firmware download does not work for certain earlier and unsupported versions
of HBA firmware,driver,andHBAnywareversions.
Workaround: Use the latest versions of HBA firmware,driver,andHBAnyware.
12