HP StorageWorks Fabric OS 5.3.2c release notes (5697-0150, October 2009)

Fixed in Fabric OS 5.3.1.
Backbone to edge traffic across FCIP links and ISLs may not be evenly dis-
tributed across all possible routes (edge to backbone and backbone to
edge).
Fixed in Fabric OS 5.3.1.
When disabling an NPIV switch which has an Access Gateway connected
to it, the F_Ports that failover to the other NPIV switch show as No device
found when running nszonemember for these F_Ports.
Fixed in Fabric OS 5.3.1.
When perfMonitorShow –class ISL 0 command is run, some
switches give incorrect output as follows: The number of destination
domains monitored is set to zero.
Fixed in Fabric OS 5.3.1.
Unexpected switch reboot may occur during hafailover. During an up-
grade, rcsd may get into an infinite loop and block RCS from completing
a sync dump, leaving RCS transaction hanging. Switch panic may occur
and traffic may be interrupted.
Fixed in Fabric OS 5.3.1.
Flooding of an unknown interswitch FDMI command from non-Brocade
switch causes daemon to be killed due to out of memory condition, causing
the switch to crash.
Fixed in Fabric OS 5.3.1.
Linux kernel issue may occur on 2Gb switches running Fabric OS 5.3.0x
caused by service daemon thread (fwd, nsd, fabricd) becoming un-
responsive due to deadlock condition. This can trigger a panic, or snmpd
hang.
Fixed in Fabric OS 5.3.1.
Fabric OS crash occasionally seen when Access Gateway enabled switch
is rebooted with large number of Access Gateway devices in the fabric.
Fixed in Fabric OS 5.3.1.
During fastwrite, specific third party device drops a frame that is not 8
byte aligned.
Fixed in Fabric OS 5.3.1.
With 2–GB switches, hafailover under heavy load across ISLs, followed
by portdisable/portenable of E-ports causes port blade fault with tx
parity error (error 21).
Fixed in Fabric OS 5.3.1.
When PID-2 change occurs, WebTools incorrectly translates the PID format
in the NameServer and displays an incorrect account of the area/ports
contained in a zone or alias member list. This can also happen when at-
tempting to add to a zone or alias list, causing an incorrect physical port
to be added.
Fixed in Fabric OS 5.3.1.
During stress test with 2Gb switch, when receive buffer overflow occurs,
third party device port is stuck in offline state for more than 30 seconds.
Portdisable/portenable will recover the port.
Fixed in Fabric OS 5.3.1.
Intermittent supportsave failure messages seen during sup-portsave
loop.
Fixed in Fabric OS 5.3.1.
Traffic stops during FCIP testing with Tape Pipelining enabled, when host
floods the switch with Name Server query. This occurs because the query
response is not passed back to the host on the backbone switch through
the FCR router.
Fixed in Fabric OS 5.3.1.
When executing fastwrite with Tape Pipelining with a slow responding
tape device, the switch sent improper frame causing tape job to fail. Ulti-
mately, this caused the initiator to lose access to the tape drive.
14