Cisco MDS-9124 Troubleshooting Guide - Page 124
show module internal event-history module, show system internal xbar internal event-history module
View all Cisco MDS-9124 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 124 highlights
Troubleshooting Switching and Services Modules Chapter 4 Troubleshooting Hardware Send documentation comments to [email protected] Table 4-11 Module is in the Powered-Down State Symptom Module is in powered-down state. Possible Cause Module experienced boot-up failures. Module failed to register with the supervisor. Module failed to connect to fabric. Supervisor failed to configure the module. 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 "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. 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. 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. 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. Diagnosing a Powered-Down Module To diagnose the reason for a powered-down module using the CLI, follow these steps: Step 1 Step 2 Use the show system reset-reason module to show the reason for the last reload of the module. 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 -- 4-28 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05