Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual page 112

Troubleshooting Supervisor Issues
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
Example 4-8
diagnostic failure.
Example 4-8
switch# show module internal exceptionlog module 6
********* Exception info for module 6 ********
exception information --- exception instance 1 ----
device id:
device errorcode:
system time:
error type:
Number Ports went bad:
1,2,3,4,5,6
exception information --- exception instance 2 ----
device id:
device errorcode:
system time:
error type:
Number Ports went bad:
1,2,3,4,5,6
Example 4-9
reboots after a runtime diagnostic failure.
Example 4-9
Switch# show logging
2005 Sep 28 14:17:47 172.20.150.204 %XBAR-5-XBAR_STATUS_REPORT: Module 6 reported status
for component
2005 Sep 28 14:17:59 172.20.150.204 %PORT-5-IF_UP: Interface mgmt0 on slot 5 is up
2005 Sep 28 14:18:00 172.20.150.204 %CALLHOME-2-EVENT: SUP_FAILURE
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
4-16
displays the exception log that appears when a supervisor module reboots after a runtime
Exception Log for Supervisor Reboot Caused by Runtime Diagnostic Failure
12
0x80000020
(1127917068 ticks) Wed Sep 28 14:17:48 2005
FATAL error <--------------------- exception that caused the reboot
12
0x00060a02
(1127917067 ticks) Wed Sep 28 14:17:47 2005
Warning
displays the system messages on the standby supervisor module when a supervisor module
System Messages for Supervisor Reboot Caused by Runtime Diagnostic Failure
12 code 0x60a02.
Chapter 4 Troubleshooting Hardware
OL-9285-05