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

    Check for SSB Alarms

    To check for SSB alarms:

    1. Display the Current SSB Alarms
    2. Display SSB Error Messages in the System Log File
    3. Display SSB Error Messages in the Chassis Daemon Log File

    Display the Current SSB Alarms

    Purpose

    To determine the details of the current SSB alarms.

    Action

    To display the current SSB alarms, use the following command:

    user@host> show chassis alarms

    Sample Output

    user@host> show chassis alarms
    2 alarms currently active
    Alarm time               Class  Description
    2002-06-05 19:55:57 UTC  Major  fxp0: ethernet link down
    

    Meaning

    The command output displays the alarm date, time, severity level, and description. An SSB failure or removal generates an fxp0 link alarm. The fxp0 link is the dedicated 100-Mbps Fast Ethernet link between the SSB and the Routing Engine. This link transfers routing table data from the Routing Engine to the forwarding table in the Internet Processor ASIC. The link also transfers, from the SSB to the Routing Engine, routing link-state updates and other packets destined for the router that have been received through the router interfaces.

    Display SSB Error Messages in the System Log File

    Purpose

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

    Action

    Periodically check the system log messages on the management console for messages sent by the SSB. During normal operation, the SSB notifies the Routing Engine of any errors it detects.

    To display the SSB error messages in the system log file, use the following CLI command:

    user@host> show log messages

    Sample Output

    user@host> show log messages
    Jul 10 13:28:45 myrouter /kernel: fxp1: media DOWN 100Mb / full-duplex
    Jul 10 13:28:45 myrouter /kernel: fxp1: media DOWN 10Mb / half-duplex
    Jul 10 13:28:45 myrouter /kernel: fxp1: media DOWN 100Mb / full-duplex
    Jul 10 13:28:45 myrouter /kernel: fxp1: link UP 100Mb / full-duplex
    Jul 10 13:28:45 myrouter rpd[564]: EVENT <UpDown> fxp1.0 index 1 <Up Broadcast Multicast> address #0 0.a0.a5.12.1d.6d
    Jul 10 13:28:45 myrouter mib2d[563]: SNMP_TRAP_LINK_UP: ifIndex 2, ifAdminStatus up(1), ifOperStatus up(1), ifName fxp1
    [...Output truncated...]
    

    Meaning

    The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. You can also use the show log messages | match ssb command to see error messages that are generated when an SSB fails or is offline. Use this information to diagnose a problem and to let the Juniper Networks Technical Assistance Center (JTAC) know what error messages were generated and the router events that occurred before and after the problem. For more information about system log messages, see the Junos OS System Log Messages Reference.

    Display SSB Error Messages in the Chassis Daemon Log File

    Purpose

    To determine the details of the SSB error messages in the chassis daemon log file.

    Action

    To display the SSB error messages in the chassis daemon (chassisd) log file, use the following command:

    user@host> show log chassisd

    Sample Output

    user@host> show log chassisd
    Jul 10 13:27:28 SSB0 is now not present
    Jul 10 13:27:28 Assert reset on SSB0
    Jul 10 13:27:28 Turn on ethernet loop
    [...Output truncated...]
    

    Meaning

    The command output displays the SSB hardware version level, part number, and serial number.

    Published: 2012-08-20