Step 2: Display FPC Error Messages in the System Log File

Action

To check for FPC error messages in the system log messages file, use the following CLI command:

user@host> show log messages | match fpc

Check for error messages at least 5 minutes before and after an FPC alarm occurs.

Sample Output

The following output displays when you browse through the messages log file using 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 

Mar 10 09:20:37 cls-edge-02 ssb CM(0): Slot 1: Unrecoverable error; probe failed 

Mar 10 09:20:37 cls-edge-02 ssb CM(0): Slot 1: Too many unrecoverable errors, 
going off-line 

Mar 10 09:20:37 cls-edge-02 ssb CM(0): ALARM SET: (Major) Slot 1: Too many 
unrecoverable errors 

Mar 10 09:20:37 cls-edge-02 ssb CM(0): Slot 1: Off-line 

Mar 10 09:20:38 cls-edge-02 ssb PFEMAN: FPC socket closure indicated 

Mar 10 09:20:38 cls-edge-02 ssb PFEMAN: closing FPC 1 socket 

Mar 10 09:20:42 cls-edge-02 ssb PFEMAN: FPC socket closure indicated 

Mar 10 09:20:42 cls-edge-02 ssb PFEMAN: close on unlisted socket, 0xb0e200

The following output displays when you use the | match filter command to look for specific information in the messages log file:

user@host> show log messages | match fpc

Mar 31 05:07:58 bopper fpc6 D4-6/0 AMCC: Transmitter laser bias out of range.

Mar 31 05:08:37 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 2, power on 
timeout, retry 1, restarting

Mar 31 05:08:44 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 5, power on 
timeout, retry 1, restarting

Mar 31 05:10:19 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 2, power on 
timeout, retry 2, restarting

Mar 31 05:10:26 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 5, power on 
timeout, retry 2, restarting

Mar 31 05:12:00 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 2, power on 
timeout, retry 3, restarting

Mar 31 05:12:07 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: fpc 5, power on 
timeout, retry 3, restarting

Mar 31 05:13:41 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: FPC 2 
unresponsive, setting offline!

Mar 31 05:13:48 bopper chassisd[630]: CHASSISD_FRU_UNRESPONSIVE: FPC 5 
unresponsive, setting offline!

What It Means

When an FPC fails, the System and Switch Board (SSB), System Control Board (SCB), and Switching and Forwarding Modules (SFMs) generate error messages. 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 | match fpc command to view only FPC error messages. Use this information to diagnose an FPC problem and to let the Juniper Networks Technical Assistance Center (JTAC) know what error messages were generated and the router events prior to the FPC problem. For more information about system log messages, see the JUNOS System Log Messages Reference.