HP B-series Fabric OS 6.3.2e Release Notes (5697-1816, March 2012) - includes all 6.3.2x versions

Table 6 Fabric OS 6.3.2 closed defects (continued)
Workaround prior to upgrade: Use the
CLI.
Access Control Lists are not getting populated, even though the ACL Policies
are set on the switch. As a result, ACL related configuration is not possible
Fixed in Fabric OS 6.3.2.
through DCFM or other common access layer (CAL) interfaces, even though
it can be done through the CLI. This issue affects only the HP 2408 FCoE
switch and 10/24 FCoE blade.
Fixed in Fabric OS 6.3.2.CNA cannot login during shut/no shut of port that occurs in the middle of
FCoE login attempt. Doing fcoe -enable/disable does not recover it.
This issue affects only the HP 2408 FCoE switch and 10/24 FCoE blade.
Fixed in Fabric OS 6.3.2.After a firmwaredownload hafailover/hareboot, switch is missing
domain route, indicated by RTWR-1003 retry messages. Only pertinent to
fabric with VE link to 1606 Extension SAN switch or Multiprotocol Extension
blade in IM2 mode.
Fixed in Fabric OS 6.3.2.A device with a node WWN of zero connected to an NPIV port that is
queried by CALD, causes the switch to panic and reboot about every 20 to
30 minutes.
Fixed in Fabric OS 6.3.2.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.
Workaround prior to upgrade: Keep
trunk groups with equal bandwidth.
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.
Fixed in Fabric OS 6.3.2.
Fixed in Fabric OS 6.3.2.Detected termination of zoning daemon process during firmwaredownload.
Race condition triggered the zoning daemon to access unintialized global
memory and then crash.
Workaround prior to upgrade: May need
to block and unblock all ports in the trunk
to recover from the rare condition.
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.
Fixed in Fabric OS 6.3.2.
Workaround prior to upgrade: Disable
FCR matrix by issuing the following
commands:
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
1. fcrlsanmatrix -remove -fcr
wwn wwn
out of sync among all FCRs in the fabric; all imported disks went to
configured.
2. fcrlsanmatrix -apply -fcr
Fixed in Fabric OS 6.3.2.
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).
Workaround prior to upgrade: Remove
the condition/cause of the excessive
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
CRC errors (that is, replace cable or
SFP).
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.
Fixed in Fabric OS 6.3.2.
42