Displaying Fpc Error Messages In The System Log File - Juniper M Series Monitoring And Troubleshooting Manual

Meaning

Displaying FPC Error Messages in the System Log File

Purpose
Action
Sample Output
Copyright © 2012, Juniper Networks, Inc.
The command output displays the current FPC alarms, including the time the alarm
occurred, the severity level, and the alarm description. At the command line, you see the
following FPC error messages:
Too many unrecoverable errors
Too many recoverable errors
From the router craft interface LCD screen, you see the following:
Slot x: errors
Check for FPC alarms on the router craft interface. You can physically look at the craft
interface or use the
show chassis craft-interface
occurs, the craft interface goes into alarm mode. Alarm mode preempts idle mode,
displaying a message to alert you of serious alarm conditions. In alarm mode, the screen
displays the following information:
+--------------------+
|myrouter |
|1 Alarm active |
|R: Slot 2:errors |
| |
+--------------------+
The craft interface output provides the following information:
First line—Name of the router.
Second line—Number of alarms active on the router.
Third and fourth lines—Individual alarms, with the most severe condition shown first.
Each line indicates whether the alarm is a red (R) or yellow (Y) alarm.
Gather FPC error messages from the system log file.
To determine the details of the FPC error messages in the system log file.
To check for FPC error messages in the system log
command:
user@host> show log messages | match fpc
Check for error messages at least 5 minutes before and after an FPC alarm occurs.
The following output displays when you browse through the
time and date stamp to look for error messages that occur 5 minutes before and after
the FPC event:
user@host> show log messages
Mar 10 09:20:31 cls-edge-02 ssb RDP: Keepalive timeout for
rdp.(scb:chassis).(fpc1:36865) (elapsed 5595)
Mar 10 09:20:33 cls-edge-02 ssb SSB(0): Slot 0, serial number S/N BD9709.
Mar 10 09:20:37 cls-edge-02 ssb BCHIP 1: SRAM test failed.
Mar 10 09:20:37 cls-edge-02 ssb CM(0): Slot 1: B-chip diagnostics failed
Chapter 7: Monitoring FPCs
command. When a red or yellow alarm
file, use the following
messages
log file using the
messages
221