HP Fabric OS 6.2.2f Release Notes (5697-1756, February 2012)
Table 11 Fabric OS 6.2.2 closed defects (continued)
SolutionClosed defect summary
a large volume of F-Class traffic, a potential exists for an edge switch to be
faulted due to lack of response from the core director.
Fixed in Fabric OS 6.2.2In a rare circumstance with a switch running Fabric Watch, a panic can
occur after fwd terminated with exit code:134, exit sig:17, and parent
sig:0 when IPC buffer is overrun on a busy system.
Fixed in Fabric OS 6.2.2Telnet banner and switchname are not consistent after a new switchname
is defined without doing multiple hafailover commands. Can also occur
Workaround prior to update: Use the
hostname xyz command when a
after a standby CP is replaced where the new CP hosts file does not get
synchronized with active CP without two hafailover commands.
switchname xyz is used. The problem
does not occur with SSH; it does not use
the banner.
Fixed in Fabric OS 6.2.2The SNMP manager gets incorrect MIB information from a switch running
Fabric OS 6.1.x, due to a change in SwFwEPortUtil and SwFwEPort-
Pktl between SW_v5_7 to SW_v5_8 MIB.
Fixed in Fabric OS 6.2.2When port 254 is used in directors in non-FICON setup, after multiple
hafailovers, port 254 may lose its name server entry, and/or CP reports
a synchronization error while overall system HA maintains sync.
Workaround prior to update: Reboot
standby CP to force a re-synchronization.
Fixed in Fabric OS 6.2.2During firmwaredownload, standby CP reboots due to assert and recovers
with no functional impact observed.
Fixed in Fabric OS 6.2.2With HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb
BladeSystem switches for p-Class and c-Class BladeSystem, speed
negotiation fails when the port is locked as G-port, and port cannot come
online.
Fixed in Fabric OS 6.2.2On a switch running Fabric OS 6.2.x, when a firmwaredownload -sn
and reboot is executed with Fabric OS 6.3.0x such that the new firmware
Workaround prior to update: Invoke a
manual reboot.
image is active but the secondary image has the old image, if a
firmwarerestore is run to revert back to the original image, it will fail.
Fixed in Fabric OS 6.2.2CALD panic occurred on a director and CPs got out of sync, but no failover
happened as CALD was in defunct state due to race condition.
Workaround prior to update: Manually
reboot the switch.
Fixed in Fabric OS 6.2.2Supportsave does not clear the FFDC files, leading to continued FFDC
file warnings being issued until a second supportsave is issued.
Fixed in Fabric OS 6.2.2Peak data rate is reported as 4096 MB/s for 2Gb/s port.
Fixed in Fabric OS 6.2.2NPIV tape devices may not be seen by hosts due to name server not sending
subsequent PLOGI ACC following a sequence where NPIV device sends
LOGO before link down.
Fixed in Fabric OS 6.2.2HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb BladeSystem
switch for c-Class BladeSystem has incomplete supportsave .
Workaround prior to update: Run
individual command such as
portstatsshow on the switch.
Fixed in Fabric OS 6.2.2On HP StorageWorks DC SAN or DC04 director, SwFCPortTxType MIB
does not report the type of CoreBlade's ICL port correctly. Reports as
swFCPortTxType.385 unknown(1)
Fixed in Fabric OS 6.2.2Configdownload removes license keys from a new replacement switch.
This applies only to Fabric OS 6.2.x code.
Fabric OS 6.2.2a fixes
Table 12 (page 45) lists defects closed in the Fabric OS 6.2.2a firmware release.
44