Display SIB Error Messages in the Chassis Daemon Log File
Purpose
To determine the details of the SIB error messages in the chassis daemon log file. The chassis daemon (chassisd) log file keeps track of the state of each chassis component.
Action
To display the SIB error messages logged in the chassis daemon log file, use the following command:
Sample Output
user@host> show log chassisd | match sib cli command Jan 29 18:37:07 CHASSISD_SNMP_TRAP10: SNMP trap: FRU power off: jnxFruContentsIn dex 15, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName SIB 2, jnx FruType 9, jnxFruSlot 3, jnxFruOfflineReason 7, jnxFruLastPowerOff 1701082, jnxF ruLastPowerOn 3250 Jan 29 18:37:09 send: yellow alarm set, device SIB 2, reason SIB 2 Not Online Jan 29 18:37:09 fm_recv_hsl_start_sib_ack plane case. Checking plane control to all line cards? Jan 29 18:37:09 fm_recv_hsl_start_sib_ack: Awaiting spmb ack for LC#0! Jan 29 18:37:09 fm_recv_hsl_start_sib_ack plane case. Checking plane control to all line cards? Jan 29 18:37:09 fm_recv_hsl_start_sib_ack: Awaiting spmb ack for LC#0! Jan 29 18:37:09 fm_recv_hsl_start_sib_ack plane case. Checking plane control to all line cards? Jan 29 18:37:09 fm_recv_hsl_start_sib_ack plane case. Sending plane control to a ll line cards!
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. You can search for multiple items in the chassisd log file by using the | match sib command to see error messages that are generated when a SIB fails or is offline. Use this information to diagnose a SIB problem and to let 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.
