Slot 1 information:
State Backup
Meaning The command output displays how long the CFEB has been operating. A short uptime
can indicate a CFEB failure. Look for error messages that were generated at least 5
minutes prior to the failure event by using the following command:
user@host> show log messages | match cfeb
Check the System Uptime
Purpose To verify CFEB failure by checking the system uptime.
Action To check the system uptime, use the following command:
user@host> show system uptime
Sample Output
user@host> show system uptime
Current time: 2002-07-17 16:43:45 PDT
System booted: 2002-07-12 17:29:12 PDT (4d 23:14 ago)
Protocols started: 2002-07-12 17:29:56 PDT (4d 23:13 ago)
Last configured: 2002-07-10 23:10:27 PDT (6d 17:33 ago) by regress
4:43PM up 4 days, 23:15, 2 users, load averages: 0.07, 0.02, 0.00
Meaning The command output displays the time when the system was last booted, in days and
hours. If the boot time is short, it can indicate a Routing Engine or a CFEB failure. Look
for error messages that were generated at least 5 minutes prior to the failure event by
using the following command:
user@host> show log messages | match cfeb
Check the CFEB Connection
Purpose Verify CFEB failure by checking the CFEB connection.
Action Make sure the CFEB is properly seated in the midplane. Check that the thumbscrews on
each CFEB ejector lever are securely tightened. Use a Phillips screwdriver to ensure that
the screws are securely tightened.
Perform a Swap Test on the CFEB
Purpose To verify CFEB failure by performing a swap test on the CFEB.
CAUTION: Before performing a swap test, always check for bent pins in the
midplane and check the CFEB for stuck pins in the connector. Pins stuck in
the component connector can damage other good slots during a swap test.
527Copyright © 2012, Juniper Networks, Inc.
Chapter 24: Monitoring the CFEB
To Next Page
Loading...
Need help?
General
