Chapter 4 Troubleshooting Line Cards
General Information for Troubleshooting Line Card Crashes
General Information for Troubleshooting Line Card Crashes
Line card crashes occur when the hardware or software encounter unexpected situations that are not expected in the current design. As a general rule, they usually indicate a configuration error, a software error, or a hardware problem.
Table
Table
Command | Description |
|
|
show version | Provides general information about the system's hardware and software |
| configurations |
|
|
show logging | Displays the general logs of the router |
|
|
show diag [slot/subslot] | Provides specific information about a particular slot: type of engine, |
| hardware revision, firmware revision, memory configuration, and so on. |
|
|
show context [summary | Provides context information about the most recent crashes. This is |
slot [slot/subslot] ] | often the most useful command for troubleshooting line card crashes. |
|
|
Use the following procedure if you suspect that a line card has crashed.
Step 1 If you can identify the particular card that has crashed or is experiencing problems, first use the other sections in this chapter to perform basic troubleshooting. In particular, ensure that the line card is fully inserted into the proper slot, and that all cables are properly connected.
Step 2 If any system messages were displayed on the console or in the SYSLOG logs at the time of the crash, consult the Cisco CMTS System Messages guide and the Cisco IOS System Messages Guide for possible suggestions on the source of the problem.
Step 3 Line cards can crash or appear to crash when an excessive number of debug messages are being generated. In particular, this can happen when using the verbose or detail mode of a debug command, or if the debug command is dumping the contents of packets or packet buffers. If the console contains a large volume of debug output, turn off all debugging with the no debug all command.
Step 4 If the system message log contains messages that indicate the line card is not responding (for example,
Step 5 Use the show context summary command to identify all of the line cards that have experienced a crash:
Router# show context summary
|
|
| CRASH | INFO SUMMARY | ||
|
|
| Slot | 1/0: 0 crashes | ||
|
|
| Slot | 1/1: 0 crashes | ||
|
|
| Slot | 2/0: 0 crashes | ||
|
|
| Slot | 2/1: 0 crashes | ||
|
|
| Slot | 3/0: 0 crashes | ||
|
|
| Slot | 3/1: 0 crashes | ||
|
|
| Slot | 4/0: 1 | crashes | |
1 - | crash at 04:28:56 EDT Tue Apr 20 1999 | |||||
|
|
| Slot | 4/1: 0 | crashes | |
|
|
| Slot | 5/0: 0 | crashes | |
|
|
| Cisco uBR10012 Universal Broadband Router Troubleshooting Guide | |||
|
|
| ||||
|
|
|
|
|
| |
|
|
|
|
| ||
