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
SolutionClosed defect summary
Fixed in Fabric OS 6.3.2.A switch panic occurs during firmwaredownload with termination of msd
(management server daemon). If a request was cancelled in the midst of
processing, a race condition between two threads can occur, triggering an
msd panic and hareboot/hafailover of switches. Observed in fabric
with EOSc switch that ignores GMAL request.
Workaround prior to upgrade: Manually
reboot the switch after
firmwarerestore.
The firmwarerestore command does not restore the firmware to the
original version after a firmwaredownload to downgrade from Fabric OS
6.4.x to 6.3.x, or from Fabric OS 6.3.x to 6.2.x with the -sfbn option
Fixed in Fabric OS 6.3.2.
Workaround prior to upgrade: Use
slotpoweroff/on the 10/24 FCoE
blade to clear the faulty state.
As a result of firmwaredownload, systemverifcation test, or blade
insertion, occasionally 10/24 FCoE blade may turn faulty 21.
Fixed in Fabric OS 6.3.2.
Fixed in Fabric OS 6.3.2.Intermittent network connection problem led to failure of the management
interface port on the encryption SAN switch, causing multiple switches within
the encryption group to go out of sync. The encryption Group Leader detected
the departure of a member, but the member did not detect the departure of
the Group Leader, and the group got out of sync.
Fixed in Fabric OS 6.3.2.After moving a 10/24 FCoE director blade from slot 1 to slot 2 in a DC SAN
Backbone director, and a CP failover, CNAs are not able to login.
Workaround prior to upgrade: Avoid
configuring an EX_Port or a VE_Port near
Directors with 8Gb blade in slot 1 or 8Gb switches see frame drop in the
fabric when there are Ex/VEx ports configured in the same ASIC chip as an
an F/E_Port with an EGID of 0. ToF/E port with EGID 0. Fabric with this problem can be identified by running
identify a port with an EGID of 0, loginsloterrshow 1 on directors or sloterrshow on a switch, and
as root and run bladeportmap [1].
type6_miss counter should be seen continuously incrementing during traffic
load on backend port/E_Port.
The first port where Upt is not -1 uses
EGID 0. Once the problem occurs, the
user must make the F/E port into an
EX_Port and then configure it back to an
F/E_Port to fix the problem port. Execute
the following instructions:
1. Disable the F/E_Port.
2. Configure the F/E_Port as an EC_Port
for a valid FID.
3. Connect a link between the FID and
the EX port (IFL).
4. Enable the port.
5. Verify that the link is online, then
disable the port.
6. Disable the EX_Port configuration.
7. Connect the host/ISL back to the
F/E_Port.
8. Enable the port.
Fixed in Fabric OS 6.3.2.
Fixed in Fabric OS 6.3.2.Switch reboot after Access Gateway daemon panic following hot code load
(HCL). This failure is usually observed with [PORT-1003] in raslog, and only
with Access Gateway enabled switches.
Workaround prior to upgrade: Stop
using the SMI-based application until the
Very intermittent issue where rpcd crash can occur due to uninitialized pointer,
if user changes security configuration (certificates or rpc secret) through Web
firmware is upgraded to Fabric OS
6.3.2.
Tools while there is an active rpc connection from SMI-A. Due to this rpcd
panic followed by weblinker.fcg restart to make the configuration
effective, a cold recovery of the CPs is triggered.
Fixed in Fabric OS 6.3.2.
Fabric OS 6.3.2 fixes 41