Display Cfeb Error Messages In The Chassis Daemon Log File - Juniper M Series Monitoring And Troubleshooting Manual

Meaning

Display CFEB Error Messages in the Chassis Daemon Log File

Purpose
Action
Sample Output
Copyright © 2012, Juniper Networks, Inc.
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]:
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
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
command to see error messages that are generated when a Control Board fails or
cfeb
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 OS System Log Messages Reference.
To determine the details of the CFEB error messages in the chassis daemon log file.
To display CFEB error messages in the
user@host> show log chassisd | match cfeb
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
Chapter 24: Monitoring the CFEB
Major alarm set, CFEB not online, the
show log messages | match
log file, use the following command:
chassisd
525