HP 1606 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 42

Fixed in Fabric OS 6.3.2., Workaround prior to upgrade

Page 42 highlights

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 through DCFM or other common access layer (CAL) interfaces, even though it can be done through the CLI. This issue affects only the HP StorageWorks 2408 FCoE switch and 10/24 FCoE blade. Workaround prior to upgrade: Use the CLI. 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 StorageWorks 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 Fixed in Fabric OS 6.3.2. 20 to 30 minutes. 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. Fixed in Fabric OS 6.3.2. 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. Workaround prior to upgrade: Keep trunk groups with equal bandwidth. Fixed in Fabric OS 6.3.2. Detected termination of zoning daemon process during firmwaredownload. Race condition triggered the zoning daemon to access unintial- Fixed in Fabric OS 6.3.2. ized global memory and then crash. 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. Workaround prior to upgrade: May need to block and unblock all ports in the trunk to recover from the rare condition. Fixed in Fabric OS 6.3.2. 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 out of sync among all FCRs in the fabric; all imported disks went to configured. Workaround prior to upgrade: Disable FCR matrix by issuing the following commands: 1. fcrlsanmatrix -remove -fcr wwn wwn 2. fcrlsanmatrix -apply fcr Fixed in Fabric OS 6.3.2. 42

  • 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
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52

Workaround prior to upgrade:
Use
the CLI.
Fixed in Fabric OS 6.3.2.
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 through DCFM or other common access layer (CAL) inter-
faces, even though it can be done through the CLI. This issue affects
only the HP StorageWorks 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 StorageWorks 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 Multi-
protocol 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.
Fixed in Fabric OS 6.3.2.
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.
Detected termination of zoning daemon process during
firmwaredown-
load
. Race condition triggered the zoning daemon to access unintial-
ized 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.
Fixed in Fabric OS 6.3.2.
May see frame drops on some device ports and E_Ports after
hafail-
over
. 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.
Workaround prior to upgrade:
Disable FCR matrix by issuing the
following commands:
1.
fcrlsanmatrix -remove
-fcr wwn wwn
2.
fcrlsanmatrix -apply -
fcr
Fixed in Fabric OS 6.3.2.
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 out of sync among all FCRs in the fabric;
all imported disks went to configured.
42