HP 4400 HP B-series Fabric OS 6.3.2d Release Notes (5697-1105, July 2011) - Page 43
Rolling asserts occur on 4/256 SAN Director with Multiprotocol Router, Fixed in Fabric OS 6.3.2.
View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 43 highlights
With a switch in Access Gateway mode, a few ports were observed as persistently disabled after enabling QoS on all trunked F_Ports, with the message: Area of those ports had been acquired by the ports that were not in the same trunk. Occurs when port SCNs come in an unexpected order. Fixed in Fabric OS 6.3.2. A switch panic occurs during reboot due to a race condition caused by a data structure not yet being allocated by a daemon and yet another daemon querying it. Applies only to the 2408 FCoE switch and 10/24 FCoE blade. Fixed in Fabric OS 6.3.2. Routes are not being properly rebalanced after a trunk group loses a member, which could lead to sluggish performance on 8Gb switches if there is a slow drain device using the lower bandwidth link to further congest the fabric. Workaround prior to upgrade: Keep trunk groups with equal bandwidth. Fixed in Fabric OS 6.3.2. Detected termination of zoning daemon process during firmwaredownload. Race condition triggered the zoning daemon to access unintial- Fixed in Fabric OS 6.3.2. ized global memory and then crash. May see frame drops on some device ports and E_Ports after hafailover. E_Port change SCN event or fabric unstable event results in fspf routing protocol incorrectly mapping slave to master port or incorrectly programming interface IDs on the trunks. Frames are routed to the wrong port and dropped. Workaround prior to upgrade: May need to block and unblock all ports in the trunk to recover from the rare condition. Fixed in Fabric OS 6.3.2. FCR matrix specifies which FCR pairs can talk to each other. All edge fabrics connected to the defined pair of FCRs are allowed to import devices to each other. However, after a fabric event, FCR did not handle domain unreachable SCN timing sequence correctly, leading to the FCR matrix information being out of sync among all FCRs in the fabric; all imported disks went to configured. Workaround prior to upgrade: Disable FCR matrix by issuing the following commands: 1. fcrlsanmatrix -remove -fcr wwn wwn 2. fcrlsanmatrix -apply fcr Fixed in Fabric OS 6.3.2. WWN PID static binding was setup on the switch using the wwnaddress -bind command and WWN_A is bound to PID A, and WWN_B is bound to PID B. Almost instantaneously, both ports go offline due to a device "rebalance" and, when the links come back up, WWN to PID binding is swapped. Ports become disabled with the reason Disabled (PPID set on device, other port online with area). Fixed in Fabric OS 6.3.2. As a result of an external FC port on the encryption SAN switch or blade experiencing an excessive number of encoding CRC errors, the internal ports are faulted incorrectly by switch firmware. This leads to a data encryption virtual initiator associated with the internal port failing to appear in the name server. Workaround prior to upgrade: Remove the condition/cause of the excessive CRC errors (that is, replace cable or SFP). Fixed in Fabric OS 6.3.2. Rolling asserts occur on 4/256 SAN Director with Multiprotocol Router blade, or on 400 Multiprotocol Router when attempting to connect to an encryption SAN switch via EX_Port. Workaround prior to upgrade: Disable the E_Port on the encryption switch to recover the switch. Fixed in Fabric OS 6.3.2. HP B-series Fabric OS 6.3.2d Release Notes 43