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
     

    Related Documentation

     

    Display PCG Alarms

    To display PCG alarms and error messages:

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

    Display Current PCG Alarms

    Purpose

    To determine the details of the current PCG alarms.

    Action

    To display the current PCG 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-11 20:30:29 PDT  Minor PCG 0 Not Online
    2002-06-11 20:30:32 PDT  Minor No PCGs Online
    

    Meaning

    The command output displays the alarm date, time, severity level, and description.

    Display PCG Error Messages in the System Log File

    Purpose

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

    Action

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

    user@host> show log messages

    Sample Output

    user@host> show log messages
    Jun 11 20:31:31 myrouter chassisd[553]: CHASSISD_NO_GOOD_PCGS: 
    

    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 pcgs command to see error messages that are generated when a PCG 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 PCG Error Messages in the Chassis Daemon Log File

    Purpose

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

    Action

    To display the PCG 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
    Jun 11 20:31:17 FPC 7 - Disable Power [addr 0x17 cmd 0x10]
    Jun 11 20:31:17 CMB readback FPC 7 [0xf7, 0xf2] -> 0x26
    Jun 11 20:31:17 power disable verified, FPC 7
    Jun 11 20:31:17 CHASSISD_IFDEV_DETACH: ifdev_detach(7)
    Jun 11 20:31:17 ifd so-7/0/0 marked as gone
    Jun 11 20:31:19 PCG 0 set alarm 0x3
    Jun 11 20:31:19 alarm op fru 1 op 1 reason 3
    Jun 11 20:31:19 send: yellow alarm set, class 100 obj 110 reason 3
    Jun 11 20:31:19 CMB cmd to PCG 0 [0xe2], Disable Power [0x10]
    Jun 11 20:31:19 PCG 0 - Disable Power [addr 0x2 cmd 0x10]
    Jun 11 20:31:19 CMB readback PCG 0 [0xe2, 0xf2] -> 0x6
    Jun 11 20:31:19 power disable verified, PCG 0
    Jun 11 20:31:19 CMB cmd to PCG 0 [0xe2], Blue LED Off [0x16]
    Jun 11 20:31:19 PCG 0 - Blue LED Off
    Jun 11 20:31:19 CMB cmd to PCG 0 [0xe2], Green LED Off [0x1a]
    Jun 11 20:31:19 PCG 0 - Green LED Off
    Jun 11 20:31:19 CMB cmd to PCG 0 [0xe2], Amber LED Off [0x18]
    Jun 11 20:31:19 PCG 0 - Amber LED Off
    Jun 11 20:31:19 mcs_intr_handler fpm_mcsfd 10
    Jun 11 20:31:19 mcs_intr mcs_ints_pending 0x7cbf20 button_status 0x0
    Jun 11 20:31:19 bp_handle_button_intr button status 0x0
    Jun 11 20:31:21 reading FPC 0 initial state
    Jun 11 20:31:21 CMB readback FPC 0 [0xf0, 0xff] -> 0xc
    Jun 11 20:31:21 reading FPC 0 ideeprom
    Jun 11 20:31:21 reading FPC 1 initial state
    Jun 11 20:31:21 CMB readback FPC 1 [0xf1, 0xff] -> 0xc
    Jun 11 20:31:21 reading FPC 1 ideeprom
    Jun 11 20:31:21 reading FPC 2 initial state
    Jun 11 20:31:21 CMB readback FPC 2 [0xf2, 0xff] -> 0xc
    Jun 11 20:31:21 reading FPC 2 ideeprom
    Jun 11 20:31:21 reading FPC 6 initial state
    Jun 11 20:31:21 CMB readback FPC 6 [0xf6, 0xff] -> 0xc
    Jun 11 20:31:21 reading FPC 6 ideeprom
    Jun 11 20:31:21 reading FPC 7 initial state
    Jun 11 20:31:21 CMB readback FPC 7 [0xf7, 0xff] -> 0xc
    Jun 11 20:31:21 reading FPC 7 ideeprom
    Jun 11 20:31:21 gen_sfm_wait_mask 0x0
    Jun 11 20:31:21 ...power sequencer started...
    

    Meaning

    The chassisd database 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.

     

    Related Documentation

     

    Published: 2012-08-20