01-15-2017 03:40 AM - edited 03-08-2019 08:55 AM
Hey guys,
I have just bought a new Cisco 2600 router, and I have connected to it via the console. However, the router seems to be stuck in a continuous boot loop. I have done a bit of searching and have tried a few different possible solutions but so far, no luck.
I will post the console output
Unexpected exception to CPUvector 200, PC = 80433764
-Traceback= 80433764 80432B68 80432308 801E1300 801DAD04 80430548 80430640 803E76DC 80320340 80320548 803F257CWriting crashinfo to flash:crashinfo_19930301-000009write1 531 bytes to flash:crashinfo_19930301-000009 gets 120
Queued messages:
*** System received a Bus Error exception ***
signal= 0xa, code= 0x200, context= 0x81c6284c
PC = 0x80433764, Vector = 0x200, SP = 0x81e92e00
Solved! Go to Solution.
01-15-2017 01:46 PM
Hello,
the document I linked above has a hardware troubleshooting procedure, which pretty much involves inserting whatever network modules you have into different slots on the chassis, in order to find out if the problem is with a slot.
In the end, your chassis might be the culprit, and you might have to replace it...
01-15-2017 08:38 AM
Hello,
try the below (excerpt from the full document linked below):
Software Failure
On 2600 and 3600 routers, the router's I/O memory is configurable as a percentage of the main memory. If the I/O memory settings are inappropriate for the installed network modules or WAN interface cards (WICs), the 2600/3600 platform may have trouble booting and may crash with bus errors.
If a software configuration change has recently been made, and the router is in a booting loop, a software bug may be causing this issue.
If the router is not able to boot up, you can bypass the configuration to identify whether that is causing the issue. Follow these steps:
1. Break into ROMMON by sending the break sequence (press the BREAK key on your keyboard when the router starts up) to the router during the first 60 seconds of boot up.
2. From ROM Monitor, use the confreg command to change the configuration register to a setting, such as 0x2142, to ignore the router's configuration:
rommon 1 > confreg 0x2142
3. You must reset or power cycle for new config to take effect
rommon 2 > reset
http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/7949-crashes-buserror-troubleshooting.html
01-15-2017 01:31 PM
Thank you for the reply. I broke into
Could this be a hardware related issue? I've already reseated all my memory cards and the only network cards I have are needed for me to plug into the console.
01-15-2017 01:46 PM
Hello,
the document I linked above has a hardware troubleshooting procedure, which pretty much involves inserting whatever network modules you have into different slots on the chassis, in order to find out if the problem is with a slot.
In the end, your chassis might be the culprit, and you might have to replace it...
01-15-2017 01:56 PM
Okay I will work through it, thank you so much for your help! :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide