HP 4400 HP B-series Fabric OS 6.3.2d Release Notes (5697-1105, July 2011) - Page 52
Fabric OS 6.3.2c fixes, lists defects closed in the Fabric OS 6.2.3c firmware release.
View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 52 highlights
Tape performance is degraded after a tape drive has been idle for a few hours and then traffic is restarted on an HP 1606 SAN Extension Switch. Fixed in Fabric OS 6.3.2b. Users are unable to create a Certificate Signing Request (CSR) on a switch with only an IPv6 address configured. Fixed in Fabric OS 6.3.2b. The output of the switchstatusshow command reports an invalid switch status rather than the "marginal" status when application blades go down. This is caused by the Fabric Watch blade handler monitor mishandling the status of application blades. Fixed in Fabric OS 6.3.2b. Fabric Watch reports TX/RX performance over 100% after executing the statsclear command. Workaround prior to upgrade: Use the slotstatsclear command instead of the statsclear command. Fixed in Fabric OS 6.3.2b. The LED for online trunked F_Ports goes from a steady green to off after Fixed in Fabric OS 6.3.2b. a code upgrade or hareboot/hafailover. For both portstats and SNMP MIB output commands, counters quickly wrap on GE_Ports of an HP 1606 SAN Extension Switch or an HP DC Fixed in Fabric OS 6.3.2b. SAN Director Multiprotocol Extension Blade. Fabric OS 6.3.2c fixes Table 9 lists defects closed in the Fabric OS 6.2.3c firmware release. Table 9 Fabric OS 6.3.2c closed defects Closed defect summary Solution Frames received on shared area port trunks are improperly routed on an HP SAN Director 48-port 8Gb FC Blade in an HP DC SAN Backbone Director. This may occur after the remote trunk master goes offline and then comes back online. Fixed in Fabric OS 6.3.2c. A switch panic/director HA Failover may occur due to resource conten- Fixed in Fabric OS 6.3.2c. tion when TopTalker is monitoring traffic flows. Customers are unable to access a device after FCIP links bounce multiple times. Frames with same SID/DID were sent to the device after the proxy Fixed in Fabric OS 6.3.2c. translation failed in a backbone to edge FCR setup. After upgrading a fabric switch from Fabric OS from 6.2.x to 6.3.x, the N_Port was stuck in G_Port when the fabric switch is attached to an Access Gateway switch with QoS enabled. FAN frames are not being sent by the switch to loop devices after LIP when fcAL.fanFrameDisable is set to 0. Fixed in Fabric OS 6.3.2c. Fixed in Fabric OS 6.3.2c. A reboot of a host on one port group may adversely affect another host Fixed in Fabric OS 6.3.2c. in a different port group causing loss of connectivity to their storage. 52