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

VE_Port near an F/E_Port with an, Con the F/E_Port as an

Get HP 1606 PDF manuals and user guides View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 41 highlights

As a result of firmwaredownload, systemverifcation test, or blade insertion, occasionally 10/24 FCoE blade may turn faulty 21. Workaround prior to upgrade: Use slotpoweroff/on the 10/24 FCoE blade to clear the faulty state. 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. Fixed in Fabric OS 6.3.2. 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 F/E port with EGID 0. Fabric with this problem can be identified by running sloterrshow 1 on directors or sloterrshow on a switch, and type6_miss counter should be seen continuously incrementing during traffic load on backend port/E_Port. Workaround prior to upgrade: Avoid configuring an EX_Port or a VE_Port near an F/E_Port with an EGID of 0. To identify a port with an EGID of 0, login as root and run bladeportmap [1]. 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. Switch reboot after Access Gateway daemon panic following hot code load (HCL). This failure is usually observed with [PORT-1003] in raslog, Fixed in Fabric OS 6.3.2. and only with Access Gateway enabled switches. Very intermittent issue where rpcd crash can occur due to uninitialized pointer, if user changes security configuration (certificates or rpc secret) through Web 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. Workaround prior to upgrade: Stop using the SMI-based application until the firmware is upgraded to Fabric OS 6.3.2. Fixed in Fabric OS 6.3.2. HP StorageWorks Fabric OS 6.3.2b Release Notes 41

  • 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
slotpoweroff/on
the 10/24
FCoE blade to clear the faulty state.
Fixed in Fabric OS 6.3.2.
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.
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 an F/E_Port with an
EGID of 0. To identify a port with an
EGID of 0, login as root and run
bladeportmap [1]
. 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 configura-
tion.
7.
Connect the host/ISL back to the
F/E_Port.
8.
Enable the port.
Fixed in Fabric OS 6.3.2.
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 F/E port with EGID 0. Fabric with this problem can be
identified by running
sloterrshow 1
on directors or
sloterrshow
on a switch, and
type6_miss
counter should be seen continuously
incrementing during traffic load on backend port/E_Port.
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 firmware is upgraded to Fabric
OS 6.3.2.
Fixed in Fabric OS 6.3.2.
Very intermittent issue where rpcd crash can occur due to uninitialized
pointer, if user changes security configuration (certificates or rpc secret)
through Web 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.
HP StorageWorks Fabric OS 6.3.2b Release Notes
41