01-14-2003 11:45 AM - edited 03-02-2019 04:10 AM
I have been advised to:
Post sh stack after router reboots on its own and come back up next time.
However, that's always been my big problem -- it will not reboot on it's own -- It crashes, freezes and will never reboot. I have seen it go over two hours without rebooting itself.
01-14-2003 01:13 PM
You can have PC plugged in to the console port of a 5300 showing the issue. It will dump some cpu hog messages or some indication of why it loks up or crashes etc..
You can also configure the 5300 to dump a crash informatioin (core dump) and store in the flash disk. Pl. visit following url for ways to collect that coredump.
http://www.cisco.com/univercd/cc/td/doc/cisintwk/itg_v1/tr19aa.htm
01-14-2003 01:45 PM
I have a laptop plugged in and have seen cpuhog messages. Sometimes they result in the machine crashing and sometimes they don't. Lately, they don't.
This problem started late last November. It was crashing about once a week. Then it stopped crashing and just started marking the modems as bad. You ask me to post the results of several show commands, which I did and put them on a web page at: http://www.riverview.net/show_proc.htm
Is that still useful? Should I try to collect the core dumps? It looks like the ftp method would be the easiest for me to do.
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