Cisco 9134 - MDS Multilayer Fabric Switch - Diagnosing a Powered-Down Module

Send documentation comments to mdsfeedback-doc@cisco.com
4-28
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Switching and Services Modules
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 Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standby
6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active *
8 8 IP Storage Services Module powered-dn
Mod Sw Hw World-Wide-Name(s) (WWN)
--- ----------- ------ ------------------------------------
5 2.1(2) 1.1 --
6 2.1(2) 0.602 --
Table 4-11 Module is in the Powered-Down State
Symptom Possible Cause Solution
Module is in
powered-down
state.
Module experienced
boot-up failures.
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 “Reinitializing a Failed Module Using
Fabric Manager” section on page 4-36 or the “Reinitializing a Failed Module
Using the CLI” section on page 4-37.
Module failed to
register with the
supervisor.
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 “Reinitializing a Failed Module Using Fabric Manager”
section on page 4-36 or the “Reinitializing a Failed Module Using the CLI”
section on page 4-37.
Module failed to
connect to fabric.
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 “Reinitializing a Failed Module Using
Fabric Manager” section on page 4-36 or the “Reinitializing a Failed Module
Using the CLI” section on page 4-37.
Supervisor failed to
configure the module.
Verify the cause of the failure. See the “Diagnosing a Powered-Down Module”
section on page 4-28. Right-click the module in Device Manager and select
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 4-37.