HP StorageWorks Fabric OS 5.2.3 Release Notes (AA-RWEYD-TE, November 2007)

Fabric OS 5.2.1a
fix
When run as a separate command from the CLI, diagclearerror may hang the console or cause the
system to crash. Affects only the Brocade 4Gb SAN Switch for HP c -Class BladeSystem platform.
Fixed per Fabric OS 5.2 .1a.
Fabric OS 5.2.1b fixes
Table 4 lists defects closed in the Fabric 5.2.1b firmware release.
Table 4 Fabric OS 5.2.1b fi xes
Closed defect summary
Solution
Traffic path between host an d target not established on HP 4Gb
VC-FC Module for c-Class B ladeSystem due to PLOGI ACC frame not
being routed to the destination virtual port when host and target are
onthesameNPIVport.
Fixed per Fabric OS 5.21b.
400 MP router does not pass initial N-port login (PLOGI) frames with
host in edge fabric and target in backbone fabric. Subsequent attempt
sever al seconds later is ok.
Fixed per Fabric OS 5.21b.
Using API to access default zoning information may cause the switch
to panic.
Fixed per Fabric OS 5.21b.
On switches running Fabric OS 5.2.0x, if device sends PLOGI very
fast, during a small window prior to name server information being
fully propagated, it may be dropped by a switch using domain/por t
zoning. No impact to WWN zoning.
Fixed per Fabric OS 5.21b.
After upgrading 400 MP router firmware to Fabric OS 5.2.1 on fabric
designated with Fabric ID 128, the host loses paths to devices.
Fixed per Fabric OS 5.21b.
When upgrading firmware to Fabr ic OS 5.2.1 or 5.2.1a, the internal
routingtablewillbeoverwritten. On400MProuter,or4/256
director with FR4-18i blade, EX_port routes can be lost causing lost
paths. Other 4Gb switches (including embedded) will experience
imbalanced routes, resulting in performance problems.
Fixed per Fabric OS 5.21b.
Host loses target for 15 seconds after a non-disruptive failover on an
Access Gateway-enabled switch. This impacts the Brocade 4Gb SAN
Switch for HP c -Class BladeSystem and Brocade 4Gb SAN Switch for
HP p-Class BladeSystem.
Fixed per Fabric OS 5.21b.
Fabric OS 5.2 .2 fixes
Table 5 lists defects closed in the Fabric 5.2.2 firmware release.
Table 5 Fabric OS 5.2.2 fixes
Closed defect summary
Solution
In a dual ba ckbone fabric with EX_port trunking links to edge fabrics,
host may not be able to see targets after a port disable/enable of one
the EX trunk ports.
Fixed per Fabric OS 5.2.2.
On 2 Gbit/sec platforms, a switch panic reboot condition can occur if
an unstable or faulty port generates more interrupts than the switch
could process.
Fixed per Fabric OS 5.2.2.
Third party application crashes during an activation of a large zoneset
with over 1200 zones due to API library crash as the zone library does
a memcpy that does not include the terminating zero to the buffer.
Fixed per Fabric OS 5.2.2.
20