JUNOS Internet Software Network Operations Guide: Hardware
156 ! Verifying Routing Engine Failure
For hard drive errors:
user@host>
show log messages
Jun 3 12:00:28 router /kernel: ad1: WRITE command timeout - resetting
Jun 3 12:00:44 router /kernel: ata0: resetting devices ..
Jun 3 12:00:44 router /kernel: ata0: Succeeded in resetting devices.
Jun 3 12:00:28 router /kernel: ad1: WRITE command timeout - resetting
Jun 3 12:00:17 router /kernel: ata0: resetting devices ..
What It Means The messages system log file records the time the failure or event occurred, the
severity level, a code, and a message description. Use the
show log messages CLI
command to browse error messages that are generated at least 5 minutes before
and after an event. You can also use the
show log messages | match “device-name”
command to view error messages that are specific to a device name. Use this
information to diagnose a problem and to let JTAC know what error messages were
generated and the router events prior to the event. For more information about
system log messages, see the JUNOS Software System Log Messages Reference.
Step 7: Document the Events Prior to the Failure
Action To document events that occurred prior to a Routing Engine failure, follow these
steps:
1. Write down any events such as an abrupt router shutdown because of a power
outage, a software upgrade, a configuration commit, or a system snapshot
request.
2. Write down any recovery procedures attempted. If the Routing Engine
reported some errors on the hard drive but appeared to be working fine or a
backup Routing Engine is available, it may not be necessary to recover.
3. Turn on logging to your console to start capturing screen output. This is
especially useful if a terminal server is connected to the Routing Engine console
port.
4. While you have screen capturing enabled, boot the Routing Engine and look at
the router boot messages.
To Next Page
Loading...
Need help?
General
