HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.2 release notes (5697-7964 - Page 17

Fabric OS 5.3.1 fixes Table 3 lists defects closed in the Fabric OS 5.3.1 firmware release. Table 3 Fabric OS 5.3.1 closed defects Closed defect summary Solution Management Server Daemon (MSD) panic occurs on switch during fabric initialization. When fabric has not initialized its database during fabric initialization, MSD gets ipaddress of switches in fabric which could lead to memory corruption and cause MSD to panic. Fixed in Fabric OS 5.3.1 Backbone to edge traffic across FCIP links and ISLs may not be evenly distributed across all possible routes (edge to backbone and backbone Fixed in Fabric OS 5.3.1 to edge). 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 Fixed in Fabric OS 5.3.1 "No device found" when running nszonemember for these F_Ports. When perfMonitorShow -class ISL 0 command is run, some switches give incorrect output as follows: The number of destin- Fixed in Fabric OS 5.3.1 ation domains monitored is set to zero. Unexpected switch reboot may occur during hafailover. During an upgrade, 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 inter-switch FDMI command from non-Brocade switch causes daemon to be killed due to out of memory condition, Fixed in Fabric OS 5.3.1 causing the switch to crash. Linux kernel issue may occur on 2Gb switches running Fabric OS 5.3.0x caused by service daemon thread (fwd, nsd, fabricd) becoming unresponsive 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 Fixed in Fabric OS 5.3.1 fault with tx parity error (error 21). When PID-2 change occurs, Web Tools 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 attempting 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. Fixed in Fabric OS 5.3.1 Portdisable/portenable will recover the port. HP StorageWorks Fabric OS 5.3.2 release notes 17