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

Chapter 4 Troubleshooting Hardware
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-12 Module is Automatically Reloaded
Symptom Possible Cause
Module is Module experienced
automatically heartbeat failures.
reloaded.
The module experienced
runtime diagnostic failures.
Module lost synchronize
with the fabric.

Diagnosing a Reloaded Module

To diagnose the reason for a reloaded module, follow these steps:
Right-click the module and select Module on Device Manager or use the show module CLI command
Step 1
to verify the status of the module.
Choose Logs > Switch Resident > Syslog > Sever Events on Device Manager or use the show logging
Step 2
CLI command to search for common reload problems.
Use the show module internal exception module CLI command to view the exception log.
Step 3
switch#
********* Exception info for module 8 ********
exception information --- exception instance 3 ----
device id:
device errorcode:
system time:
error type:
Number Ports went bad:
1,2,3,4,5,6,7,8
exception information --- exception instance 4 ----
device id:
OL-9285-05
Solution
Choose Logs > Switch Resident > Syslog > Sever Events on Device
Manager or use the show logging CLI command to verify bootup
problems.
Use the show module internal event-history module CLI command and
look for
to verify that the module did not respond to heartbeat requests. Right-click
the module in Device Manager and select Reset or use the reload module
CLI command to restart the module. See the
Module Using Fabric Manager" section on page 4-36
"Reinitializing a Failed Module Using the CLI" section on page
Verify the cause of the failure. See the
section on page
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
on page 4-37.
Use the show system internal xbar internal event-history errors and look
for something similar to:
fabric 0 link 0
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
on page 4-37.
show module internal exceptionlog module 8
0
0x40730017
(1127843486 ticks) Tue Sep 27 17:51:26 2005
FATAL error
5
Troubleshooting Switching and Services Modules
Triggered event: [LCM_EV_LCP_ALIVE_TIMEOUT]
4-33. Right-click the module in Device Manager and
or the "Reinitializing a Failed Module Using the CLI" section
Rx MTS_OPC_SSA_LOST_SYNC_SERIAL slot 8
to verify that the module lost sync with the fabric.
or the "Reinitializing a Failed Module Using the CLI" section
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
"Reinitializing a Failed
or the
4-37.
"Diagnosing a Reloaded Module"
4-33