HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.2 release notes (5697-0349, - Page 28

Fixed in Fabric OS 6.1.2, Always Receive

Page 28 highlights

Cald panic occurs due to race condition when multiple requests are being issued throughout the fabric. Restarts with no impact to host/target traffic. Fixed in Fabric OS 6.1.2 Enhancements needed to supportsave to provide additional troubleshooting information. Fixed in Fabric OS 6.1.2 Zoning operations will not propagate to backbone router from edge fabric when performed while the fabric is building. Fixed in Fabric OS 6.1.2 Buffer-limited ports were not persistent across reboots, such that they do not stay buffer limited and other ports become buffer limited. Fixed in Fabric OS 6.1.2 Credit recovery does not reallocate credits properly when QoS is ON, and QoS E_Port does not recover credit via link reset, so traffic may Fixed in Fabric OS 6.1.2 not run properly through the fabric. Misbehaving third-party devices can cause soft fault entries per SN failures. Need to minimize these entries. Fixed in Fabric OS 6.1.2 Some NPIV-capable HBAs have problems talking to the switch due to FDISC occurring after a successful ACC of NPIV establishment was not supported. Leads to ABTS being sent to the wrong N_Port ID. Fixed in Fabric OS 6.1.2 After removing a Long Distance EX_Port configuration and doing portenable to Long Distance (non-EX_port), the FCR-1063 message Fixed in Fabric OS 6.1.2 is displayed followed by VERIFY being displayed on the console. Channel receives bad LS_RJT reason code of 0x0B00 rather than expected 0x092c on attempt to register LIRR with Registration Function Always Receive. Fixed in Fabric OS 6.1.2 Kernel access of bad area panic from NSD task due to device going away in a small timing window when switch is in process of doing PLOGI. Both CPs could hit the same panic during this small window. Fixed in Fabric OS 6.1.2 Switch panic due to detected termination of ficud, due to access of uninitialized data. Fixed in Fabric OS 6.1.2 Switch panic due to management server daemon (MSD) data structure corruption during hafailover/hareboot. Fixed in Fabric OS 6.1.2 After a specific hafailover sequence (disable FCR before hafailover, then do hafailover, then another hafailover, then enable FCR again), the switch encounters a frame drop on EX_Port. Fixed in Fabric OS 6.1.2 The command firmwareupgrade fails (does not commit) during a very small window of time, when active CP did not wait for standby CP to timeout before recovering it. Fixed in Fabric OS 6.1.2 Performance monitor filter block is processed in the wrong block size, leading to memory corruption, because the trace buffer filled up. Could Fixed in Fabric OS 6.1.2 result in switch panic. Port state mismatch seen on embedded switches between switchshow and portcfgshow regarding PersistenDisable flag. Portcfg- Fixed in Fabric OS 6.1.2 show shows persistent disable state while port is actually enabled. 28

  • 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
  • 29
  • 30

Fixed in Fabric OS 6.1.2
Cald panic occurs due to race condition when multiple requests are
being issued throughout the fabric. Restarts with no impact to
host/target traffic.
Fixed in Fabric OS 6.1.2
Enhancements needed to
supportsave
to provide additional
troubleshooting information.
Fixed in Fabric OS 6.1.2
Zoning operations will not propagate to backbone router from edge
fabric when performed while the fabric is building.
Fixed in Fabric OS 6.1.2
Buffer-limited ports were not persistent across reboots, such that they
do not stay buffer limited and other ports become buffer limited.
Fixed in Fabric OS 6.1.2
Credit recovery does not reallocate credits properly when QoS is ON,
and QoS E_Port does not recover credit via link reset, so traffic may
not run properly through the fabric.
Fixed in Fabric OS 6.1.2
Misbehaving third-party devices can cause soft fault entries per SN
failures. Need to minimize these entries.
Fixed in Fabric OS 6.1.2
Some NPIV-capable HBAs have problems talking to the switch due to
FDISC occurring after a successful ACC of NPIV establishment was
not supported. Leads to ABTS being sent to the wrong N_Port ID.
Fixed in Fabric OS 6.1.2
After removing a Long Distance EX_Port configuration and doing
portenable
to Long Distance (non-EX_port), the
FCR-1063
message
is displayed followed by
VERIFY
being displayed on the console.
Fixed in Fabric OS 6.1.2
Channel receives bad LS_RJT reason code of
0x0B00
rather than ex-
pected
0x092c
on attempt to register LIRR with Registration Function
Always Receive
.
Fixed in Fabric OS 6.1.2
Kernel access of bad area panic from NSD task due to device going
away in a small timing window when switch is in process of doing
PLOGI. Both CPs could hit the same panic during this small window.
Fixed in Fabric OS 6.1.2
Switch panic due to detected termination of
ficud
, due to access of
uninitialized data.
Fixed in Fabric OS 6.1.2
Switch panic due to management server daemon (MSD) data structure
corruption during
hafailover/hareboot
.
Fixed in Fabric OS 6.1.2
After a specific
hafailover
sequence (disable FCR before
hafailover
, then do
hafailover
, then another
hafailover
,
then enable FCR again), the switch encounters a frame drop on
EX_Port.
Fixed in Fabric OS 6.1.2
The command
firmwareupgrade
fails (does not commit) during a
very small window of time, when active CP did not wait for standby
CP to timeout before recovering it.
Fixed in Fabric OS 6.1.2
Performance monitor filter block is processed in the wrong block size,
leading to memory corruption, because the trace buffer filled up. Could
result in switch panic.
Fixed in Fabric OS 6.1.2
Port state mismatch seen on embedded switches between
switchshow
and
portcfgshow
regarding
PersistenDisable
flag.
Portcfg-
show
shows persistent disable state while port is actually enabled.
28