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

Table 7 Fabric OS 6.3.2a closed defects
SolutionClosed defect summary
Fixed in Fabric OS 6.3.2a.In a fabric containing the encryption switch and/or encryption blade,
numerous weblinker termination and restart messages can be seen due to
timeouts in handling multiple stats calls in parallel.
Fixed in Fabric OS 6.3.2a.After doing a firmware upgrade or an hafailover on a 4/256 director with
4Gb 48 port blade installed, the CP blade faults and traffic is disrupted.
External RASLOG EM-1051 messages are seen, reporting a slot inconsistency
detected. This can occur if a PLOGI is received right before the hafailover
or hot code load and it has zone misses for devices communicating through
the primary shared area port.
Fixed in Fabric OS 6.3.2a.Port zoning enforcement cycles between session based zoning and hard
zoning. This can happen when name server queries occur at the same time
as a zone configuration change is initiated. ZONE-1004 messages are seen
in RASLOGs but no traffic interruption is observed. Applies to all platforms.
Fixed in Fabric OS 6.3.2a.When standby CP is not responsive (stuck in reboot loop) on any director
class switch, Weblinker causes the active CP to reboot, leading to a cold
recovery.
Fixed in Fabric OS 6.3.2a.FICUD ASSERT/auto-reboot occurs when changing logical switch
configuration due to random timing condition in accessing switch
configuration data. Observed when running lscfg commands to configure
FICUD ports. Both CPs reboot with disruptive recovery.
Workaround prior to upgrade: Perform
hafailover/hareboot to clean up any
Race condition in FCP daemon logging mechanism causes memory corruption
and panic. This leads to cold recovery during firmware download or when
existing corruption before code upgrade,management applications using the SMI client continuously query the switch.
then disable FCP logging usingOccurs in VF configurations with multiple logical switches configured running
Fabric OS 6.2.x and 6.3.x previous to 6.3.2a only. fcplogdisable to avoid any further
corruption until upgrading to a version
of Fabric OS with the fix.
Fixed in Fabric OS 6.3.2a.
Fixed in Fabric OS 6.3.2a.During host reboot, F_Port may come up as G_Port on 4/8, 4/16, 4Gb
switch for HP p-Class BladeSystem or 4Gb switch for HP c-Class BladeSystem.
Fixed in Fabric OS 6.3.2a.Compact Flash (CF) can sometimes fail silently. In such cases, the user sees
only critical daemon failures triggering a failover. Sometimes no failure is
seen, and the switch continues running but does not produce any logs. Fabric
OS 6.3.2a provides an enhancement to CF failure handling to detect and
proactively trigger an hafailover when a bad part is detected.
Workaround prior to upgrade: Use
OOS mode.
On 8Gb switches, constant link resets occur when a long distance E_Port
port is configured that requires 128 to 511 credits. These link resets occur
Fixed in Fabric OS 6.3.2a.
continuously with no traffic, and a constant stream of C2-5021 indications
are seen.
Fixed in Fabric OS 6.3.2a.Host ports can experience slow performance after enabling and then disabling
Top Talker. Class 3 frame rejects can also be seen in the portlogdump. This
is due to a residual setting in the firmware that causes class 3 frame rejects
to be continuously forwarded to the CPU causing the slow performance.
Fixed in Fabric OS 6.3.2a.Switch panics, blade faults, or switches getting disabled when credit loss is
detected on internal backend port. RASLOG C-5021 or C2-5021 indications
are reported.
Fixed in Fabric OS 6.3.2a.Fabric Watch FW-1186 and FW-1190 messages are logged with values
above 100%. Likely to occur during first Fabric Watch polling cycle after
slotstatsclear command has been issued.
Workaround prior to upgrade: Bounce
affected primary port or move device off
the secondary shared area port.
Traffic routed through an 8Gb 48 port blade in a DC SAN Backbone director
running Fabric OS 6.3.0 through 6.3.2 will be misrouted following an HA
failover. HA failover can be triggered in numerous ways including a firmware
Fixed in Fabric OS 6.3.2a.
upgrade. When this occurs in this configuration, the DCX misroutes traffic
46