HP 4400 Release Note page 42

Table 1 1 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary
When 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.
During firmwaredownload, standby CP reboots due to assert and recovers
with no functional impact observed.
With 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.
On 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
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.
CALD 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.
Supportsave does not clear the FFDC files, leading to continued FFDC
file warnings being issued until a second supportsave is issued.
Peak data rate is reported as 4096 MB/s for 2Gb/s port.
NPIV 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.
HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb BladeSystem
switch for c-Class BladeSystem has incomplete supportsave .
On 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)
Configdownload 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 42)
Table 12 Fabric OS 6.2.2a closed defects
Closed defect summary
After a target port bounce, the FC FastWrite host cannot recognize the
target due to a cam setup problem on the backend port used by FC
FastWrite.
After upgrading to Fabric OS 6.2.x, the 400 MP Router or Multiprotocol
Router blade detects a credit problem on virtual channel 0, causing a frame
drop on FCIP and FC FastWrite, and the host is unable to recognize the
target.
42
lists defects closed in the Fabric OS 6.2.2a firmware release.
Solution
Fixed in Fabric OS 6.2.2
Workaround prior to update: Reboot
standby CP to force a re-synchronization.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Invoke a
manual reboot.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Manually
reboot the switch.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Run
individual command such as
portstatsshow on the switch.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Solution
Fixed in Fabric OS 6.2.2a
Fixed in Fabric OS 6.2.2a