HP StorageWorks Fabric OS 5.0.5f Release Notes (AA-RW1WH-TE, December 2007)

Closed Defects
During stress testing, after fastboot on a fully-loaded 4/256 SAN Director a few E_ports and F_ports may stay
in "Mod_Val" mo
de. If not upgrading to this Fabric OS 5.0.5b release the workaround is to disable and
enable the port
that is stuck in the Mod-Val state.
During 3rd party SFP qualification testing with certain types of SFP, a high number of cyclic redundancy check
(CRC) and low level interrupt (LLI) errors were reported by porterrshow.
On the Core switch 2/64, logging into both logical IP addresses puts the user on the same lo gical switch. If
not upgrading to this Fabric OS 5.0.5b release the workaround is to use ssh (secure shell) or after logging in
as root, change the logical switch instance: Enter the setswitch <instance> command where <instance> is
either 0 or 1. Change 0 to 1 if needed. The PS1 line needs to be entered only once per login.
Port blade on
a SAN Director 2/128 faulted due to Failure Detection when there is a 1Gb F_port on an
even-number
ed user port. If not upgrading to this Fabric OS 5.0.5b release the workaround is to connect 1Gb
F_ports to o
dd-numbered user ports only.
Fabric OS 5.0.5c fixes
Table 4 listsimprovementsincludedinFabricOS5.0.5c.
Table 4 Fabric OS 5.0.5c closed defects
Closed Defects
Switch panic or CP failover when a kernel process is spawned by a non-root user.
Switch panics due to a bad ipaddress in the syslog.conf file. This affects all platforms.
After an upgrade to Fabric OS 5.0.5x. dual CP switches show excessive TRCK-1004 logs though there is no
change to the configuration.
Fabric OS 5.0.5d fixes
Table 5 listsimprovementsincludedinFabricOS5.0.5d.
Table 5 Fabric OS 5.0.5d closed defects
Closed Defects
Switch panic can occur i f an unstable or faulty port generates an excessive number of interrupts.
Switch panic occurs when the Remote Procedure Call Daemon (RPCD) attempts to retrieve a non-initialized
variable.
When an FCP probe failure occurs, the failing port results in an "In_Sync" state. As a result the device does
not appear in Name server because of the traffic interruption through this port.
APIlibrarycancrashduringtheactivationofalargezoneset.
Due to Performance Ser ver Daemon (PSD) panic assertions, the standby CP on all Directors can result in a
reboot loop.
Zone changes cause the CALD (Common Access Layer Daemon) to return a SCN-1001 code from the
standby CP.
The zoneObjectRename command allows the creation of duplicate aliases causing zone database corruption.
8