JUNOS Internet Software Network Operations Guide: Hardware
150 ! Verifying Routing Engine Failure
Display the Messages Log File After A Crash Occurs
Action You might see the following in the /var/log/messages file after the router comes
back up after a kernel crash occurred. To view the
messages log file, use the
following CLI command:
user@host> show log messages
Sample Output
user@host>
show log messages
Mar 9 12:22:02 host savecore: Router crashed.....
Mar 9 12:22:02 host savecore: reboot after panic: Loss of soft watchdog Mar 9
12:22:02 host savecore: system went down at Sun Mar 9 12:22:02 2003 Mar 9
12:22:02 host savecore: Selective dump will be saved now
What It Means A kernel crash occurred and a core file has been generated.
Example of When No Core File Is Generated
When a power outage occurs, no kernel crash core file is generated. To view the
messages log file, use the following CLI command:
user@host> show log messages
Sample Output
user@host>
show log messages
Aug 15 15:35:58 host /kernel: checking for core dump...
Aug 15 15:35:59 host /kernel: savecore: Router rebooted. Cause unknown....
Aug 15 15:35:59 host savecore: Router rebooted. Cause unknown....
What It Means The kernel checks for a core dump file when the router reboots.
Example of Boot Messages If Routing Engine Fails to Boot
The following example shows boot messages that occur when a Routing Engine
remains in a constant boot loop. In this condition, contact JTAC for further analysis
and assistance.
Trying to boot from PCMCIA Flash Card ...
Trying to boot from Compact Flash ...
Trying to boot from Ethernet ...
Step 2: Check for Compact Flash Media and Hard Disk Failure
If the Routing Engine has a compact flash failure, the router boots from the hard
disk. When you log in to the router, the JUNOS software CLI will indicate that the
router has booted from alternate media.
If the Routing Engine has a hard drive failure, the router boots from the compact
flash as usual. However, the router cannot write to the hard drive.