Diagnosing A Powered-Down Module - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Troubleshooting Switching and Services Modules
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Table 4-11 Module is in the Powered-Down State
Symptom Possible Cause
Module is in Module experienced
powered-down boot-up failures.
state.
Module failed to
register with the
supervisor.
Module failed to
connect to fabric.
Supervisor failed to
configure the module.

Diagnosing a Powered-Down Module

To diagnose the reason for a powered-down module using the CLI, follow these steps:
Step 1 Use the show system reset-reason module to show the reason for the last reload of the module.
Step 2 Use the show module command to verify the status of the module.
switch# show module
Mod
---
5
6
8
Mod
---
5
6
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
4-28
Solution
Choose Logs > Switch Resident > Syslog > Sever Events on Device Manager
or use the show logging CLI command to verify bootup problems. Right-click
the module in Device Manager and select Reset or use the reload module CLI
command to restart the module. See the
Fabric Manager" section on page 4-36
Using the CLI" section on page
Use the show module internal event-history module CLI command and look
for:
Triggered event: [LCM_EV_LCP_REGISTRATION_TIMEOUT]
to verify that the module did not register. Right-click the module in Device
Manager and select Reset or use the reload module CLI command to restart
the module. See the
section on page 4-36
section on page
Use the show system internal xbar internal event-history module CLI
command and look for
Triggered event: [XBM_MOD_EV_SYNC_FAILED]
to verify that the module could not connect to the fabric. Right-click the
module in Device Manager and select Reset or use the reload module CLI
command to restart the module. See the
Fabric Manager" section on page 4-36
Using the CLI" section on page
Verify the cause of the failure. See the
section on page
Reset or use the reload module CLI command to restart the module. See the
"Reinitializing a Failed Module Using Fabric Manager" section on page 4-36
or the "Reinitializing a Failed Module Using the CLI" section on page
Ports Module-Type
----- -------------------------------- ------------------ ------------
0 Supervisor/Fabric-1
0 Supervisor/Fabric-1
8 IP Storage Services Module
Sw Hw World-Wide-Name(s) (WWN)
----------- ------ ------------------------------------
2.1(2) 1.1 --
2.1(2) 0.602 --
"Reinitializing a Failed Module Using
or the
4-37.
"Reinitializing a Failed Module Using Fabric Manager"
or the "Reinitializing a Failed Module Using the CLI"
4-37.
:
"Reinitializing a Failed Module Using
or the
4-37.
"Diagnosing a Powered-Down Module"
4-28. Right-click the module in Device Manager and select
Model
DS-X9530-SF1-K9
DS-X9530-SF1-K9
Chapter 4 Troubleshooting Hardware
"Reinitializing a Failed Module
"Reinitializing a Failed Module
4-37.
Status
ha-standby
active *
powered-dn
OL-9285-05