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-19
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Supervisor Issues
dpvm 0 N/A
dstats 1 0
epld_upgrade 0 N/A
epp 1 1
Step 5
Use the s
how system internal sysmgr service all
command on the standby supervisor to determine
whether or not any process is experiencing excessive restarts. (See
Example 4-12
.)
Note
This command may not be available if the standby supervisor is at the
loader>
prompt.
Example 4-12 Finding Excessive Restarts
switch(standby)#
show system internal sysmgr service al
l
Name UUID PID SAP state Start count
------------ -------- ------ ----- ----- -----------
aaa 0x000000B5 1458 111 s0009 1
ExceptionLog 0x00000050 [NA] [NA] s0002 None
platform 0x00000018 1064 39 s0009 1
radius 0x000000B7 1457 113 s0009 1
securityd 0x0000002A 1456 55 s0009 1
vsan 0x00000029 1436 15 s0009 1
vshd 0x00000028 1408 37 s0009 1
wwn 0x00000030 1435 114 s0009 1
xbar 0x00000017 [NA] [NA] s0017 23
xbar_client 0x00000049 1434 917 s0009 1
Looking at the standby supervisor in
Example 4-12
shows that the crossbar (xbar) software component
has been restarted 23 times. This has probably prevented the standby from initializing properly.
Step 6
Use the
reload module
command to restart the standby supervisor. If the restart fails, use the
reload
module 6 force-dlnd
command from the active supervisor to force the standby supervisor to netboot off
of the active supervisor.
Standby Supervisor Stays in Powered-Up State
Symptom
Standby supervisor stays in powered-up state.
Table 4-9
Symptom
Possible Cause
Solution
Standby supervisor
stays in powered-up
state.
Standby supervisor did not synchronize
properly with active supervisor.
See the
“Verifying That a Standby Supervisor Is in the
Powered-Up State Using Device Manager” section on
page 4-20
or the
“Verifying That a Standby Supervisor Is
in Powered-Up State Using the CLI” section on
page 4-20
.
