HP StorageWorks Fabric OS 5.3.1a release notes (AA-RWEYJ-TE, May 2008)

Fabric OS 5.3.0d
fixes
Table 7 lists defects closed in the Fabric OS 5.3.0d firmware release.
Table 7 Fabric OS 5.3.0d closed defects
Closed defect summary
Solution
During POST & system verification tests, customer may see false
failures from stres s tests only intended for engineering design
verification.
Removed "minicycle" for all
platformsaswellascertaintestsfor
multi-protocol router blade, & iSCSI
blade, with 5.3.0d.
When port type can’t be determined on 4/256 director during
filter install for any ports greater than 256 (for example, installing
Performance Monitor on an offline port), filter could be programmed
incorrectly. If FC4-48 blade port greater than 256 is then enabled
as ISL, all frames will be dropped. Can also happen at corner event
timing sequence during port initialization, resulting in host not seeing
the target.
Fixed in Fabric OS 5.3.0d.
Switch panic can occur due to HBA not shutting off light and sending
invalid primitives during boot, causing port "LOSS of SYNC" a nd
generating too many interrupts.
Firmware changed to fault the port to
avoid too many interrupts generated
to CPU in a short period of time with
5.3.0d.
Certain Web Tools issues exist (i.e. does not display fabric event
information with "https" access, & is unable to open Web Tools
GUI from laptop).
Fixed in Fabric OS 5.3.0d.
Cold boot of a heavily loaded chassis on the Brocade 4Gb
SAN Switch for HP c-Class BladeSystem during POST causes an
unexpected interrupt whereby POST fails and the switch faults.
Fabric OS 5.3.0d changed to delay
processing interrupts during POST.
Fabric OS 5.3.1 fixes
Table 8 lists defects closed in the Fabric OS 5.3.1 firmware release.
Table 8 Fabric OS 5.3.1c losed defects
Closed defect summary
Solution
Management Server Daemon (MSD) panic occurs on switch during
fabric initialization. When fabric hasn’t initialized its database during
fabric initialization, MSD gets ipaddress of switches in fabric which
couldleadtomemorycorruptionandcauseMSDtopanic.
Fixed in Fabric OS 5.3.1
Backbone to edge traffic across FCIP links and ISLs may not b e
evenly distributed across all possible routes (edge to backbone and
backbone to edge).
Fixed in Fabric OS 5.3.1
WhendisablinganNPIVswitchwhichhasanAccessGateway
connected to it, the F-ports that failover to the other NPIV switch s how
as “no d evice 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 upgrade, rcsd may get into an infinite lo
op and block RCS from
completing a sync dump, leaving RCS trans
action hanging. Switch
panic may occur and traffic may be interrupted.
Fixed in Fabric OS 5.3.1
Flooding of an u nknown inter-switch FDMI command from
non-Brocade swi tch causes daemon to be killed due to out of memory
condition, causing the switch to crash.
Fixed in Fabric OS 5.3.1
HP StorageWorks Fabric OS 5.3.1a release notes
27