Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Checking for FPC Alarms

    To check for FPC alarms:

    1. Replacing an FPC
    2. Displaying FPC Error Messages in the System Log File
    3. Displaying FPC Error Messages in the Chassis Daemon Log File

    Replacing an FPC

    Purpose

    Display the current FPC alarms.

    To determine the details of the FPC alarms using the command line, or checking the alarms on the craft interface physically.

    Action

    You can display current FPC alarms at the command line or use the following command:

    user@host> show chassis alarms

    Meaning

    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 command. When a red or yellow alarm 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.

    Displaying FPC Error Messages in the System Log File

    Purpose

    Gather FPC error messages from the system log file.

    To determine the details of the FPC error messages in the system log file.

    Action

    To check for FPC error messages in the system log messages file, use the following 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!
    

    Meaning

    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 OS System Log Messages Reference .

    Displaying FPC Error Messages in the Chassis Daemon Log File

    Purpose

    To determine the details of the FPC error messages in the Chassis Daemon log file.

    Action

    To display FPC error messages in the chassisd log file, use the following command:

    user@host> show log chassisd | match “fpc | kernel | tnp”

    Sample Output

    user@host> show log chassisd | match “fpc | kernel | tnp”
    Nov 11 15:58:31 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=0, tnpaddr=2
    Nov 11 15:58:42 m40-2 tnp.bootpd[2497]: BOOTPD_BOOTSTRING: Boot string: boot 1 fpc.jbf
    Nov 11 15:58:42 m40-2 tnp.tftpd[2647]: TFTPD_CONNECT_INFO: tftp read from addr 16 port 1024 file fpc.jbf
    Nov 11 15:58:42 m40-2 tnp.bootpd[2497]: BOOTPD_BOOTSTRING: Boot string: boot 1 fpc.jbf
    Nov 11 15:58:43 m40-2 tnp.tftpd[2649]: TFTPD_CONNECT_INFO: tftp read from addr 17 port 1024 file fpc.jbf
    Nov 11 15:58:44 m40-2 tnp.tftpd[2651]: TFTPD_CONNECT_INFO: tftp read from addr 18 port 1024 file fpc.jbf
    Nov 11 15:58:45 m40-2 tnp.tftpd[2653]: TFTPD_CONNECT_INFO: tftp read from addr 19 port 1024 file fpc.jbf
    Nov 11 15:58:46 m40-2 tnp.tftpd[2655]: TFTPD_CONNECT_INFO: tftp read from addr 20 port 1024 file fpc.jbf
    Nov 11 15:58:47 m40-2 tnp.tftpd[2657]: TFTPD_CONNECT_INFO: tftp read from addr 21 port 1024 file fpc.jbf
    Nov 11 15:58:47 m40-2 fpc6 TFTP Error - Timeout
    Nov 11 15:58:47 m40-2 fpc7 TFTP Error - Timeout
    Nov 11 15:58:48 m40-2 tnp.tftpd[2659]: TFTPD_CONNECT_INFO: tftp read from addr 22 port 1024 file fpc.jbf
    Nov 11 15:58:49 m40-2 tnp.tftpd[2661]: TFTPD_CONNECT_INFO: tftp read from addr 23 port 1024 file fpc.jbf
    Nov 11 15:58:50 m40-2 tnp.tftpd[2663]: TFTPD_CONNECT_INFO: tftp read from addr 22 port 1024 file fpc.jbf
    Nov 11 15:58:50 m40-2 fpc6 TFTP read - saw block 1, expected 572
    Nov 11 15:58:51 m40-2 tnp.tftpd[2665]: TFTPD_CONNECT_INFO: tftp read from addr 23 port 1024 file fpc.jbf
    Nov 11 15:58:51 m40-2 fpc6 TFTP read - saw block 1, expected 731
    Nov 11 15:58:51 m40-2 fpc7 TFTP read - saw block 1, expected 200
    Nov 11 15:58:52 m40-2 fpc6 TFTP read - saw block 1, expected 775
    Nov 11 15:58:52 m40-2 fpc7 TFTP read - saw block 1, expected 265
    Nov 11 15:58:52 m40-2 tnp.tftpd[2647]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:58:53 m40-2 fpc6 TFTP read - saw block 1, expected 782
    Nov 11 15:58:53 m40-2 fpc7 TFTP read - saw block 1, expected 340
    Nov 11 15:58:54 m40-2 fpc7 TFTP read - saw block 1, expected 428
    Nov 11 15:58:54 m40-2 fpc6 TFTP read - saw block 1, expected 1016
    Nov 11 15:58:55 m40-2 fpc7 TFTP read - saw block 1, expected 531
    Nov 11 15:58:57 m40-2 tnp.tftpd[2649]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:58:57 m40-2 tnp.tftpd[2651]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:58:58 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=1, tnpaddr=16
    Nov 11 15:58:58 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 0 restart
    Nov 11 15:59:00 m40-2 tnp.tftpd[2653]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:59:00 m40-2 tnp.tftpd[2659]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:59:01 m40-2 tnp.tftpd[2655]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:59:02 m40-2 tnp.tftpd[2661]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:59:02 m40-2 tnp.tftpd[2657]: TFTPD_SENDCOMPLETE_INFO: Sent 2335 blocks of 1024 and 1 block of 960 for file '/usr/share/pfe/fpc.jbf'
    Nov 11 15:59:03 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=2, tnpaddr=17
    Nov 11 15:59:03 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 1 restart
    Nov 11 15:59:03 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=3, tnpaddr=18
    Nov 11 15:59:03 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 2 restart
    Nov 11 15:59:06 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=4, tnpaddr=19
    Nov 11 15:59:06 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 3 restart
    Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=5, tnpaddr=22
    Nov 11 15:59:07 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 6 restart
    Nov 11 15:59:07 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=6, tnpaddr=20
    Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 4 restart
    Nov 11 15:59:08 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=7, tnpaddr=23
    Nov 11 15:59:08 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 7 restart
    Nov 11 15:59:09 m40-2 /kernel: pfe_listener_connect: conn established: listener idx=8, tnpaddr=21
    Nov 11 15:59:09 m40-2 chassisd[2476]: CHASSISD_EVENT: fpc slot 5 restart
    

    Meaning

    The chassisd log file is a database that provides the date, time, and a component status message. The chassisd database is dynamic. It is initialized at router startup and is updated when components are added or removed. The sample command output shows the results of a multiple item search in the log file (“fpc | kernel | tnp”): error messages for the FPC, kernel, and Trivial Networking Protocol (TNP) that indicate communication issues between the Routing Engine and the Packet Forwarding Engine components.

    Published: 2012-08-20