HP 4400 Release Note page 38

Table 9 Fabric OS 6.2.1a closed defects (continued)
HP StorageWorks DC SAN Director panics due to termination of msd during
fabric reconfiguration while doing switchdisable, agshow,
switchenable loop, in a fabric with an Access Gateway device with
more than 56 switches.
A small memory leak occurs when multiple simultaneous MIB WALK queries
are performed.
96-bit licenses disappear from the HP StorageWorks 8/80 SAN Switch
due to a race condition, even when there are no fabric changes in the
environment.
Merging an M6140 M-EOS switch into a Fabric OS switch fabric causes
a Fabric OS switch to panic.
Fabric OS 6.2.1b fixes
Table 10 (page 38)
including all fixes from the 6.2.0x, 6.2.1, and 6.2.1a releases, it contains all fixes included in the
5.3.2c, 6.1.2b, and 6.2.0g releases.
Table 10 Fabric OS 6.2.1b closed defects
Closed defect summary
Switch panic occurs due to an out-of-memory condition when a management
application performs repeated FCR LUN emulation queries via SMI, or when
polling a switch whose password has changed multiple times.
HP StorageWorks DC SAN Director panicked and rebooted after fwshow
--disable --port command.
Segmentation fault causes a CALD panic in the fabric when the switch
running Fabric OS 5.2.x sends an internal query to directors that were not
properly set up to handle switches with more than 256 ports.
Switch panic is triggered by size-64 kernel message buffer being used up
in a virtual fabric with logical ISL configured.
Fabric OS 6.2.2 fixes
Table 1 1 (page 38)
including all fixes from previous 6.2.1x releases, 6.2.2 contains all fixes included in the 5.3.2c,
6.0.1a, 6.1.1d, 6.1.2b and 6.2.0g releases.
Table 1 1 Fabric OS 6.2.2 closed defects
Closed defect summary
HP StorageWorks 4/256 SAN Director with multiprotocol router blade
does not see new device across LSAN after upgrade from Fabric OS 5.x
non-disruptively to Fabric OS 6.2.x. Bounce of host port causes paths to be
lost between host and target.
8Gb blade in HP StorageWorks DC SAN Director configured for Integrated
Routing fails to route traffic on EX ports after firmware upgrade from 6.1
to 6.2. If there is an additional hafailover, a new device is added.
Bouncing the device ports could trigger a route problem leading to the host
not being able to see the device.
38
lists defects closed in the Fabric OS 6.2.1b firmware release. In addition to
lists defects closed in the Fabric OS 6.2.2 firmware release. In addition to
Fixed in Fabric OS 6.2.1a
Fixed in Fabric OS 6.2.1a
Fixed in Fabric OS 6.2.1a
Fixed in Fabric OS 6.2.1a
Solution
Fixed in Fabric OS 6.2.1b
Workaround prior to update: Disable SMI
agents.
Fixed in Fabric OS 6.2.1b
Fixed in Fabric OS 6.2.1b
Fixed in Fabric OS 6.2.1b
Workaround prior to update: Configure
only DISLs between switches.
Solution
Fixed in Fabric OS 6.2.2
Workaround prior to update: Do a
slotpoweroff/slotpoweron of the
router blade or reboot.
Fixed in Fabric OS 6.2.2
Workaround prior to update: If problem
has already occurred, bounce all EX ports
in the same chip together. After recovery,
fabric is no longer susceptible to the
problem.