HP Brocade 8/12c HP Fabric OS 6.2.2f Release Notes (5697-1756, February 2012) - Page 44

Table 11 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution 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. In 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.2 Telnet banner and switchname are not consistent after a new switchname Fixed in Fabric OS 6.2.2 is defined without doing multiple hafailover commands. Can also occur Workaround prior to update: Use the after a standby CP is replaced where the new CP hosts file does not get hostname xyz command when a 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. The SNMP manager gets incorrect MIB information from a switch running Fixed in Fabric OS 6.2.2 Fabric OS 6.1.x, due to a change in SwFwEPortUtil and SwFwEPortPktl between SW_v5_7 to SW_v5_8 MIB. When port 254 is used in directors in non-FICON setup, after multiple Fixed in Fabric OS 6.2.2 hafailovers, port 254 may lose its name server entry, and/or CP reports Workaround prior to update: Reboot a synchronization error while overall system HA maintains sync. standby CP to force a re-synchronization. During firmwaredownload, standby CP reboots due to assert and recovers Fixed in Fabric OS 6.2.2 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. Fixed in Fabric OS 6.2.2 On a switch running Fabric OS 6.2.x, when a firmwaredownload -sn Fixed in Fabric OS 6.2.2 and reboot is executed with Fabric OS 6.3.0x such that the new firmware Workaround prior to update: Invoke a image is active but the secondary image has the old image, if a manual reboot. 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 Fixed in Fabric OS 6.2.2 happened as CALD was in defunct state due to race condition. Workaround prior to update: Manually reboot the switch. Supportsave does not clear the FFDC files, leading to continued FFDC Fixed in Fabric OS 6.2.2 file warnings being issued until a second supportsave is issued. Peak data rate is reported as 4096 MB/s for 2Gb/s port. Fixed in Fabric OS 6.2.2 NPIV tape devices may not be seen by hosts due to name server not sending Fixed in Fabric OS 6.2.2 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 . Fixed in Fabric OS 6.2.2 Workaround prior to update: Run individual command such as portstatsshow on the switch. On HP StorageWorks DC SAN or DC04 director, SwFCPortTxType MIB Fixed in Fabric OS 6.2.2 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. Fixed in Fabric OS 6.2.2 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