HP 4400 HP StorageWorks Fabric OS 6.2.2e Release Notes (5697-0809, February 20 - Page 41

Table 11 Fabric OS 6.2.2 closed defects (continued) Closed defect summary Solution When running the Zone admin, with 48 port blade where there is port Fixed in Fabric OS 6.2.2 address sharing, devices show up on the wrong port. When port index and port address of the given port is different, end device will be seen connected to a different port (U port) than the original one (F_Port). HP StorageWorks DC Switch Encryption blade comes up faulty after firmwaredownload -sf and reboot of both CPs at the same time. Fixed in Fabric OS 6.2.2 Workaround prior to update: Reseat the blade. After upgrade to Fabric OS 6.x, rsh using user credential gets ifmodeshow eth0: ioctl (ETHTOOL_GSET) failed error in response to ifmodeshow command. Telnet and rsh with root credential work fine. Fixed in Fabric OS 6.2.2 Workaround prior to update: Set suid permissions for ethmode: chmod +s /fabos/libexec/ethmode Backup job stopped for an extended period of time when running through Fixed in Fabric OS 6.2.2 HP StorageWorks Encryption switch or encryption blade after bouncing 1 of the 2 connected ISLs. The 4Gb SAN Switch for HP c-Class BladeSystem AG may login to DC SAN Director with wrong PWWN. Fixed in Fabric OS 6.2.2 Workaround prior to update: Reboot AG. During director switch initialization from power on, reboot, or hafailover, Fixed in Fabric OS 6.2.2 daemons fail to load causing switch to auto reboot and ffdc HAM-1008 and HAM-1007 errors are observed. When running a third-party host scan, the http daemon (weblinker.fcg) Fixed in Fabric OS 6.2.2 terminates and restarts several times, causing a temporary management service interruption. In Fabric OS 6.2, OID for connUnitType no longer returns the correct Fixed in Fabric OS 6.2.2 access gateway mode status after upgrade from Fabric OS 6.1.1d to 6.2.0f. Fabric binding does not work in 239 domain mode in Interopmode 3 with Fixed in Fabric OS 6.2.2 FCR on 8Gb switches. EX port rejects it. Fabric Watch sometimes logs messages with values above 100%. Most Fixed in Fabric OS 6.2.2 likely occurs during first Fabric Watch polling cycle after slotstatsclear command is issued. The following message may display on the console while firmware commit Fixed in Fabric OS 6.2.2 is in progress: ssnGet: Unable to get WWN info.sw=0 rc=-5. While doing a disruptive CP reboot on a director class switch (reboot active Fixed in Fabric OS 6.2.2 CP when no standby CP is present), if simultaneous fabric update causes 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. Fabric OS 6.2.2 fixes 41