Cisco 1721 - VPN Security Router Bundle Hardware Troubleshooting page 5

Cisco - Hardware Troubleshooting for Cisco 1700 Series Routers
If you have the output of a show command from your Cisco device (including show technical-
support), you can use the
fixes. To use the Output Interpreter
enabled.
Troubleshooting ISDN Interfaces
Here is a list of references to use for troubleshooting ISDN interfaces:
Troubleshooting ISDN Layer 1
Troubleshooting ISDN Layer 2
Troubleshooting ISDN Layer 3
Troubleshooting Router Hangs
Refer to Troubleshooting Router Hangs
Troubleshooting Bus Error Crashes
The system encounters a bus error when the processor tries to access a memory location that either does
not exist (a software error) or does not respond properly (a hardware problem). A bus error can be
identified by looking at the output of the show version command provided by the router (if not power-
cycled or manually reloaded).
Here are two examples of bus error crashes:
Router uptime is 2 days, 21 hours, 30 minutes
System restarted by bus error at PC 0x30EE546, address 0xBB4C4
System image file is "flash:igs-j-l.111-24.bin", booted via flash
.........
At the console prompt, the following error message might also be seen during a bus error:
*** System received a Bus Error exception ***
signal= 0xa, code= 0x8, context= 0x608c3a50
PC = 0x60368518, Cause = 0x20, Status Reg = 0x34008002
For more information regarding this issue, refer to
Router Does Not Boot
Capturing information from the console of the router is essential for troubleshooting a router that does
not boot. The console output should be logged in a file for later analysis or for the Cisco Technical
Assistance Center (TAC) if a TAC case is opened.
The following table lists symptoms and recommended actions to take if you are encountering boot
problems:
http://kbase:8000/paws/servlet/ViewFile/17959/hwts_1700_17959.xml?convertPaths=1
Output Interpreter (
registered
(
registered customers only
for this issue.
) to display potential issues and
customers only
) , you must be logged in and have JavaScript
Troubleshooting Bus Error
Page 5 of 12
Crashes.
01/10/2004