HP Cisco Nexus 5000 Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS R - Page 32

no shut, Workaround, Symptom, show module internal

Page 32 highlights

Caveats Send documentation comments to [email protected] Frame was lost in device 55 (error 0xc3700120) 2009 Jun 15 19:55:48 mds01 %CALLHOME-2-EVENT: PORT_FAILURE 2009 Jun 15 19:55:54 mds01 %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 2167%$ Interface fc1/5 is down (Hardware Failure) Simultaneously, the affected module might display "0x40730024 Analysis Frame was lost" in the exception log, while the current active supervisor might display "0x4042003a BC Inband experienced an error". A shut command followed by a no shut command on the affected port will fail to bring it up. Workaround: This issue is resolved. • CSCsu84919 Symptom: In certain situations, the SSM might fail becuase of a memory leak in an iSAPI process. Workaround: This issue is resolved. • CSCsv43888 Symptom: A port went into a hardware failure state and displayed the following message: %MODULE-2-MOD_DIAG_FAIL: Module 4 (serial: JAExxxxxxxx) reported failure on ports 4/9-4/9 (Fibre Channel) due to Stratosphere common module experienced an error in device 63 (device error 0xc3f00278) The show module internal command displays the following information in the exception log: exception information --- exception instance Module Slot Number: 4 Device Id : 63 Device Name : Stratosphere Device Error Code : c3f00278(H) Device Error Type : ERR_TYPE_HW Device Error Name : BMx PortQx Qx Overflow Device Instance : 0 Sys Error : Stratosphere common module experienced an error Errtype : NON-CATASTROPHIC PhyPortLayer : Fibre Channel Port(s) Affected : 9 Error Description : BM1 dev_if 7 Q0 Overflow (or BM1 dev_if 7 Q-NC Overflow) DSAP : 0 UUID : 253 Workaround: This issue is resolved. • CSCsw19820 Symptom: Switch1 has IVR enabled and has a virtual domain route injection (VDRI) finite state machine (FSM) running on it. The VDRI FSM includes switch2, which previously had IVR enabled on it in its switch1 context. Whenever a host is flapped, the VDRI FSM on switch1 tries to sync with the domain of switch2. Because switch2 no longer has IVR enabled, switch1 receives a reject retry message and eventually gives up. As a result, the host cannot see the disk. Workaround: This issue is resolved. • CSCsy74340 Symptom: The SCSI Flow Manager (SFM) failed as a result of a link flap of a SCSI-FLOW target configured for IVR. Workaround: This issue is resolved. • CSCsz37102 Symptom: Severe flow control for iSCSI sessions on an MSM-18/4 module that is installed in an MDS 9500 Series switch might cause the module to fail. Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4) 32 OL-14116-12

  • 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

Send documentation comments to [email protected]
32
Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 3.3(4)
OL-14116-12
Caveats
Frame was lost in device 55 (error 0xc3700120)
2009 Jun 15 19:55:48 mds01 %CALLHOME-2-EVENT: PORT_FAILURE
2009 Jun 15 19:55:54 mds01 %PORT-5-IF_DOWN_HW_FAILURE: %$VSAN 2167%$ Interface
fc1/5 is down (Hardware Failure)
Simultaneously, the affected module might display “0x40730024 Analysis Frame was lost” in the
exception log, while the current active supervisor might display “0x4042003a BC Inband
experienced an error”.
A
shut
command followed by a
no shut
command on the affected port will fail to bring it up.
Workaround
: This issue is resolved.
CSCsu84919
Symptom
: In certain situations, the SSM might fail becuase of a memory leak in an iSAPI process.
Workaround
: This issue is resolved.
CSCsv43888
Symptom
: A port went into a hardware failure state and displayed the following message:
%MODULE-2-MOD_DIAG_FAIL: Module 4 (serial: JAExxxxxxxx) reported failure on ports
4/9-4/9 (Fibre Channel) due to Stratosphere common module experienced an error in
device 63 (device error 0xc3f00278)
The
show module internal
command displays the following information in the exception log:
exception information --- exception instance
Module Slot Number: 4
Device Id
: 63
Device Name
: Stratosphere
Device Error Code : c3f00278(H)
Device Error Type : ERR_TYPE_HW
Device Error Name : BMx PortQx Qx Overflow
Device Instance
: 0
Sys Error
: Stratosphere common module experienced an error
Errtype
: NON-CATASTROPHIC
PhyPortLayer
: Fibre Channel
Port(s) Affected
: 9
Error Description : BM1 dev_if 7 Q0 Overflow
(or BM1 dev_if 7 Q-NC Overflow)
DSAP
: 0
UUID
: 253
Workaround
: This issue is resolved.
CSCsw19820
Symptom
: Switch1 has IVR enabled and has a virtual domain route injection (VDRI) finite state
machine (FSM) running on it. The VDRI FSM includes switch2, which previously had IVR enabled
on it in its switch1 context. Whenever a host is flapped, the VDRI FSM on switch1 tries to sync with
the domain of switch2. Because switch2 no longer has IVR enabled, switch1 receives a reject retry
message and eventually gives up. As a result, the host cannot see the disk.
Workaround
: This issue is resolved.
CSCsy74340
Symptom
: The SCSI Flow Manager (SFM) failed as a result of a link flap of a SCSI-FLOW target
configured for IVR.
Workaround
: This issue is resolved.
CSCsz37102
Symptom
: Severe flow control for iSCSI sessions on an MSM-18/4 module that is installed in an
MDS 9500 Series switch might cause the module to fail.