Unfortunately that's all the information I've got. No crashinfo has been generated and while being live inside the console, it did nothing but reload and the output was:
Are you sure about that?
%Error opening bootflash:crashinfo (File not found)
Huh. The crashinfo files are not normally called that. Try: dir sup-bootflash: dir bootflash: dir slavesup-bootflash: dir slave-bootflash: ...you're looking for a file called: crashinfo_20090112-083919 ...or similar, timestamped for the crash. Are the bootflash full?
Weeks ago, when the same crash happened, I caught this error message from the console: *** System received a Software forced crash *** signal= 0x17, code= 0x24, context= 0x42352a54 PC = 0x402d1e6c, Cause = 0x3020, Status Reg = 0x34008002 System Bootstrap, Version 8.5(2) Copyright (c) 1994-2007 by cisco Systems, Inc. Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
...I'd be surprised and a little bit concerned if such a crash generated no crashinfo. Literally every time I've seen a 6500 crash, under multiple boxes and multiple IOS versions, a crashinfo has been generated.
Without a crashinfo, you're not going to be able to proceed.
I should mention that this router worked fine for more than 15 months. We are constantly adding new peers and customers to it, so the workload is growing. But as I said, this is not the busiest router in my network.
Well, when you get IOS crashes, an IOS upgrade is usually the outcome. I have seen routers which were fine below a certain workload, then went bad - in several cases, related to memory corruption under increasing memory use.
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
