Step 3: Display CFEB Error Messages in the System Log File

Check for messages at least 5 minutes before and after a CFEB alarm occurs.

Action

To check for CFEB error messages in the system log messages file, use the following CLI command:

user@host> show log messages | match cfeb

Sample Output

user@host> show log messages | match cfeb

Sep 14 11:00:01  clinton cfeb CM: ALARM SET: (Major) Slot 0: CFEB not online, 

the box is not forwarding

Sep 14 11:00:11  clinton craftd[4896]: Major alarm cleared, CFEB not online, the 
box is not forwarding

Sep 14 11:00:11  clinton alarmd[4893]: Alarm cleared: CFEB color=RED, class=

CHASSIS, reason=CFEB not online, the box is not forwarding

Sep 14 11:00:12  clinton cfeb CM: ALARM CLEAR: Slot 0: CFEB not online, the box

is not forwarding

Oct  8 00:29:02  clinton craftd[4896]:  Major alarm set, CFEB not online, the 

box is not forwarding

Oct  8 00:29:02  clinton chassisd[4891]: CHASSISD_SHUTDOWN_NOTICE: Shutdown 
reason: CFEB connection lost

Oct  8 00:29:02  clinton alarmd[4893]: Alarm set: CFEB color=RED, class=CHASSIS, 
reason=CFEB not online, the box is not forwarding 

What It Means

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