HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.1b release notes (5697-764 - Page 25

Fabric OS 5.3.1

Page 25 highlights

Fabric OS 5.3.1 fixes Table 8 lists defects closed in the Fabric OS 5.3.1 firmware release. Table 8 Fabric OS 5.3.1 closed defects Closed defect summary Solution Management Server Daemon (MSD) panic occurs on switch during fabric initialization. When fabric hasn't initialized its database during fabric initialization, MSD gets ipaddress of switches in fabric which could lead to memory corruption and cause MSD to panic. Fixed in Fabric OS 5.3.1 Backbone to edge traffic across FCIP links and ISLs may not be evenly distributed across all possible routes (edge to backbone and backbone to edge). Fixed in Fabric OS 5.3.1 When disabling an NPIV switch which has an Access Gateway connected to it, the F_Ports that failover to the other NPIV switch show as "No device found" when running nszonemember for these F_Ports. Fixed in Fabric OS 5.3.1 When perfMonitorShow -class ISL 0 command is run, some switches give incorrect output as follows: The number of destination domains monitored is set to zero. Fixed in Fabric OS 5.3.1 Unexpected switch reboot may occur during hafailover. During an upgrade, rcsd may get into an infinite loop and block RCS from completing a sync dump, leaving RCS transaction hanging. Switch panic may occur and traffic may be interrupted. Fixed in Fabric OS 5.3.1 Flooding of an unknown inter-switch FDMI command from non-Brocade switch causes daemon to be killed due to out of memory Fixed in Fabric OS 5.3.1 condition, causing the switch to crash. Linux kernel issue may occur on 2Gb switches running Fabric OS 5.3.0x caused by service daemon thread (fwd, nsd, fabricd) becoming unresponsive due to deadlock condition. This can trigger a panic, or snmpd hang. Fixed in Fabric OS 5.3.1 Fabric OS crash occasionally seen when Access Gateway enabled switch is rebooted with large number of Access Gateway devices in the fabric. Fixed in Fabric OS 5.3.1 During fastwrite, specific third party device drops a frame that is not 8 byte aligned. Fixed in Fabric OS 5.3.1 With 2Gb switches, hafailover under heavy load across ISLs, followed by portdisable/portenable of E-ports causes port blade fault with tx parity error (error 21). Fixed in Fabric OS 5.3.1 When PID-2 change occurs, Web Tools incorrectly translates the PID format in the NameServer and displays an incorrect account of the area/ports contained in a zone or alias member list. This can also happen when attempting to add to a zone or alias list, causing an incorrect physical port to be added. Fixed in Fabric OS 5.3.1 During stress test with 2Gb switch, when receive buffer overflow occurs, third party device port is stuck in offline state for more than 30 seconds. Portdisable/portenable will recover the port. Fixed in Fabric OS 5.3.1 Intermittent supportsave failure messages seen during supportsave loop. Fixed in Fabric OS 5.3.1 Traffic stops during FCIP testing with tape pipelining enabled, when host floods the switch with Name Server query. This occurs because the query response is not passed back to the host on the backbone switch through the FCR router. Fixed in Fabric OS 5.3.1 HP StorageWorks Fabric OS 5.3.1b release notes 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28

Fabric OS 5.3.1
xes
Table 8
lists defects closed in the Fabric OS 5.3.1
rmware release.
Table 8 Fabric OS 5.3.1 closed defects
Closed defect summary
Solution
Management Server Daemon (MSD) panic occurs on switch during
fabric initialization. When fabric hasn’t initialized its database during
fabric initialization, MSD gets ipaddress of switches in fabric which
could lead to memory corruption and cause MSD to panic.
Fixed in Fabric OS 5.3.1
Backbone to edge traf
c across FCIP links and ISLs may not be
evenly distributed across all possible routes (edge to backbone and
backbone to edge).
Fixed in Fabric OS 5.3.1
When disabling an NPIV switch which has an Access Gateway
connected to it, the F_Ports that failover to the other NPIV switch show
as “
No device found
” when running
nszonemember
for these
F_Ports.
Fixed in Fabric OS 5.3.1
When
perfMonitorShow –class ISL 0
command is run,
some switches give incorrect output as follows:
The number of
destination domains monitored is set to zero.
Fixed in Fabric OS 5.3.1
Unexpected switch reboot may occur during
hafailover
. During
an upgrade, rcsd may get into an in
nite loop and block RCS from
completing a sync dump, leaving RCS transaction hanging. Switch
panic may occur and traf
c may be interrupted.
Fixed in Fabric OS 5.3.1
Flooding of an unknown inter-switch FDMI command from
non-Brocade switch causes daemon to be killed due to out of memory
condition, causing the switch to crash.
Fixed in Fabric OS 5.3.1
Linux kernel issue may occur on 2Gb switches running Fabric OS
5.3.0x caused by service daemon thread (
fwd, nsd, fabricd
)
becoming unresponsive due to deadlock condition. This can trigger
a panic, or
snmpd
hang.
Fixed in Fabric OS 5.3.1
Fabric OS crash occasionally seen when Access Gateway enabled
switch is rebooted with large number of Access Gateway devices in
the fabric.
Fixed in Fabric OS 5.3.1
During
fastwrite
, speci
c third party device drops a frame that is
not 8 byte aligned.
Fixed in Fabric OS 5.3.1
With 2Gb switches,
hafailover
under heavy load across ISLs,
followed by
portdisable
/
portenable
of E-ports causes port
blade fault with tx parity error (error 21).
Fixed in Fabric OS 5.3.1
When PID-2 change occurs, Web Tools incorrectly translates the PID
format in the NameServer and displays an incorrect account of the
area/ports contained in a zone or alias member list. This can also
happen when attempting to add to a zone or alias list, causing an
incorrect physical port to be added.
Fixed in Fabric OS 5.3.1
During stress test with 2Gb switch, when receive buffer over
ow
occurs, third party device port is stuck in of
ine state for more than
30 seconds.
Portdisable
/
portenable
will recover the port.
Fixed in Fabric OS 5.3.1
Intermittent
supportsave
failure messages seen during
supportsave
loop.
Fixed in Fabric OS 5.3.1
Traf
c stops during FCIP testing with tape pipelining enabled, when
host
oods the switch with Name Server query. This occurs because
the query response is not passed back to the host on the backbone
switch through the FCR router.
Fixed in Fabric OS 5.3.1
HP StorageWorks Fabric OS 5.3.1b release notes
25