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
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 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 OS System Log Messages Reference.
Related
Documentation
Checklist for Monitoring the CFEB on page 517•
Verify CFEB Failure
To verify CFEB failure:
1.
Check the CFEB Uptime on page 526
2.
Check the System Uptime on page 527
3.
Check the CFEB Connection on page 527
4.
Perform a Swap Test on the CFEB on page 527
Check the CFEB Uptime
Purpose To check the CFEB uptime. A short uptime can indicate a CFEB failure.
Action To check the CFEB uptime, use the following command:
user@host> show chassis cfeb
Sample Output
user@host> show chassis cfeb
CFEB status:
Slot 0 information:
State Master
Intake temperature 29 degrees C / 84 degrees F
Exhaust temperature 38 degrees C / 100 degrees F
CPU utilization 3 percent
Interrupt utilization 0 percent
Heap utilization 10 percent
Buffer utilization 22 percent
Total CPU DRAM 128 MB
Internet Processor II Version 1, Foundry IBM, Part number 164
Start time: 2004-09-28 03:07:54 PDT
Uptime: 9 days, 18 hours, 41 minutes, 32 seconds
Copyright © 2012, Juniper Networks, Inc.526
M Series and T Series Routers Monitoring and Troubleshooting Guide