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
4-34
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Switching and Services Modules
device errorcode: 0x40730019
system time: (1127843486 ticks) Tue Sep 27 17:51:26 2005
error type: Minor error
Number Ports went bad:
8
Step 4
Use the
show module internal event-history module
CLI command to gather more information.
Switch# show module internal event-history module 8
84) FSM:<ID(3): Slot 8, node 0x0802> Transition at 755101 usecs after Tue Sep 27
17:51:26 2005
Previous state: [LCM_ST_LC_ONLINE]
Triggered event: [
LCM_EV_LCP_RUNTIME_DIAG_FAILURE]
Next state: [LCM_ST_CHECK_REMOVAL_SEQUENCE]
85) Event:ESQ_START length:32, at 755279 usecs after Tue Sep 27 17:51:26 2005
Instance:3, Seq Id:0x2710, Ret:success
Seq Type:SERIAL
Troubleshooting Modules in an Unknown State
Symptom
Module is in the unknown state.
Diagnosing a Module in the Unknown State
To diagnose a module in the unknown state, follow these steps:
Step 1
Right-click the module and select
Module
on Device Manager or use the
show module
CLI command
to verify the status of the module.
Step 2
Choose
Logs > Switch Resident > Syslog > Sever Events
on Device Manager or use the
show logging
CLI command to search for common problems.
Step 3
Use the
show platform internal event-history
errors CLI command
to view possible causes for the
unknown state.
switch#
show platform internal event-history
errors
1) Event:E_DEBUG, length:37, at 370073 usecs after Thu Sep 29 17:22:48 2005
[103]
unable to init lc sprom 0 mod 8
switch#
show platform internal event-history module 8
Inside pfm_show_eventlog
Table 4-13
Module Is in an Unknown State
Symptom
Possible Cause
Solution
Module is in an
unknown state.
Module experienced SPROM
failures.
Verify the cause of the failure. See the
“Diagnosing a Module in the
Unknown State” section on page 4-34
. Right-click on 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
.
