Step 4: Display CFEB Error Messages in the Chassis Daemon Log File

Action

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

user@host> show log chassisd | match cfeb

Sample Output

user@host> show log chassisd | match cfeb

Apr 28 03:25:13 Resetting CFEB 0

Apr 28 03:25:26 send: red alarm set, device CFEB 0, reason CFEB Not Online

Apr 28 03:25:26 Resetting CFEB 0

Apr 28 03:25:27 CFEB 0 added

Apr 28 03:25:27 CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruC

ontentsIndex 6, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName 

CFEB, jnxFruType 4, jnxFruSlot 1)

Apr 28 03:25:46 Resetting CFEB 0

Apr 28 03:28:42 send: red alarm set, device CFEB 0, reason CFEB Not Online

Apr 28 03:28:42 Resetting CFEB 0

Apr 28 03:28:43 CFEB 0 added

Apr 28 03:28:43 CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruC

ontentsIndex 6, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName 

CFEB, jnxFruType 4, jnxFruSlot 1)

Apr 28 03:29:17 rcv reply: CFEB Restart

Apr 28 03:29:17 CHASSISD_SNMP_TRAP9: SNMP trap generated: FRU power on (jnxFruCo

ntentsIndex 6, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName 

CFEB, jnxFruType 4, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 
5526, jnxFruLastPowerOn 5526)

Apr 28 03:29:17 sending 1 queued messages to CFEB 0

Apr 28 03:29:17 missing ctm for CFEB 0 -- timerid 0x0, timerset 0

Apr 28 03:29:17 send: CFEB config cmd

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting debugmode off

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting coredump on 

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting source-route on

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting mtu-check off

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting soft-restart on

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting pfeman-reconnect off

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting l2cache on

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting no-load-balancing-clone off

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting equal-weighted-mode off

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting ipv4-key-hash-L3 on

Apr 28 03:29:17 send: set_boolean_cmd CFEB 0 setting mpls-key-hash-2label off

Apr 28 03:29:27 send: red alarm clear, device CFEB 0, reason CFEB Not Online

What It Means

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 show log chassisd | match cfeb command to see error messages that are generated when a Control Board fails or is offline. Use this information to diagnose a Control Board 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 System Log Messages Reference.