Verifying Routing Engine Failure ! 149
Chapter 14: Monitoring the Routing Engine
Verifying Routing Engine Failure
The following sections describe how to check for the following failure conditions:
Steps To Follow 1. Check Core Files If the Routing Engine Reboots on page 149
2. Example of Boot Messages If Routing Engine Fails to Boot on page 150
3. Check for Compact Flash Media and Hard Disk Failure on page 150
Step 1: Check Core Files If the Routing Engine Reboots
List the Core Files Generated After A Crash Occurs
A vmcore file is only generated if the Routing Engine has a kernel crash. Kernel
crashes can be generated by such things as a bug in the kernel software or bad
memory. If the router has a kernel crash, the
vmcore.<n> file is generated while the
Routing Engine comes back up.
Action A vmcore file is always saved in /var/crash/. To view the core file that is generated
when a crash occurs, use the following CLI command:
user@host> file list /var/crash/ detail
Sample Output
user@host>
file list /var/crash/ detail
/var/crash/:
total 892856
-rw-r--r-- 1 root wheel 2 May 14 2004 bounds
-rw-r--r-- 1 root wheel 11959693 Oct 13 2003 kernel.0
-rw-r--r-- 1 root wheel 10114127 May 14 2004 kernel.1
-rw-r--r-- 1 root wheel 5 Feb 26 1997 minfree
-rw------- 1 root wheel 805240832 Oct 13 2003 vmcore.0
-rw------- 1 root wheel 805240832 May 14 2004 vmcore.1
What It Means The command output lists the vmcore.<n> files that have been generated.
NOTE: Routing Engine failures can include compact flash failure and hard disk
failure. If the Routing Engine has a compact flash failure and hard disk failure at
the same time, you will not be able to boot up the Routing Engine.
NOTE: The M7i and M10i routers by default come with no compact flash.