Chapter 25
Troubleshooting Call Home
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 25-1
Call Home Level
Catastrophic (9)
Disaster (8)
Fatal (7)
Critical (6)
Major (5)
Minor (4)
Warning (3)
Notify (2)
Normal (1)
Debug (0)
Initial Troubleshooting Checklist
Begin troubleshooting Call Home issues by checking the following issues first:
Checklist
Verify that you have configured the contact name, phone, and street address on the switch.
Verify that the switch has IP connectivity to your e-mail server.
If Cisco AutoNotify is used, verify that you have an active service contract that covers the
device being configured.
Verify that you have configured at least one destination profile on the switch.
Common Troubleshooting Tools in Fabric Manager
Choose Switches > Events > Call Home to verify the Call Home configuration.
Common Troubleshooting Tools in Device Manager
You can test the Call Home alert messages. Choose Admin > Events > Call Home > Alerts > Test.
Common Troubleshooting Commands in the CLI
The following commands may be useful in troubleshooting Call Home issues:
•
•
•
OL-9285-05
Severity and Syslog Level Mapping
Keyword Used Syslog Level
Catastrophic
Disaster
Fatal
Critical
Major
Minor
Warning
Notification
Normal
Debugging
show callhome
show callhome user-def-cmds
callhome test
Description
N/A
Network wide catastrophic failure.
N/A
Significant network impact.
Emergency (0)
System is unusable.
Alert (1)
Critical conditions, immediate attention needed.
Critical (2)
Major conditions.
Error (3)
Minor conditions.
Warning (4)
Warning conditions.
Notice (5)
Basic notification and informational messages.
Possibly independently insignificant.
Information (6) Normal event signifying return to normal state.
Debug (7)
Debugging messages.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
Initial Troubleshooting Checklist
Check off
25-3