michael.leblanc Wed, 05/28/2008 - 10:59
User Badges:
  • Silver, 250 points or more

Connect to the console port (with a terminal emulator) and log the system messages that scroll by.

Then post the output here.

jim_berlow Wed, 05/28/2008 - 13:53
User Badges:
  • Bronze, 100 points or more

One other thing, if the router is rebooting randomly and you want to capture the log through a reboot issue the following command:

# logging buffered

This will put the log into NVRAM so that you don't lose the log each time it reboots. Good for seeing log messages just prior to a reboot or crash.

Hope that helps!

Richard Burts Wed, 05/28/2008 - 18:54
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN


There is a major flaw in your suggestion about using logging buffered to see what causes a reload. The logging buffer is erased and re-initialized when the router boots. So after the boot the logging buffer is no help in understanding what happened before the boot.

A similar kind of suggestion might be to have some PC telnet or SSH to the router and do term mon and just leave it running. The log messages will display on the PC (through terminal monitor) up to the point of the boot and then the connection will break. So the screen of the PC should have the messages that were generated just before the boot.

And I believe that the best suggestion is the suggestion that Michael made which is to connect to the console port. That way you will get the messages before the boot, and also get the messages during the boot.




This Discussion