Verifying FEB Failure ! 457
Chapter 35: Monitoring the FEB
Step 1: Check the FEB Uptime
Action To check the FEB uptime, use the following CLI command:
user@host> show chassis feb
Sample Output
user@host>
show chassis feb
FEB status:
Temperature 24 degrees C / 75 degrees F
CPU utilization 1 percent
Interrupt utilization 0 percent
Heap utilization 17 percent
Buffer utilization 44 percent
Total CPU DRAM 64 MB
Internet Processor II Version 1, Foundry IBM, Part number 9
Start time: 2002-07-12 17:30:43 PDT
Uptime: 0 days, 0 hours, 1 minutes, 0 seconds
What It Means The command output displays how long the FEB has been operating. A short
uptime can indicate an FEB failure. Look for error messages that were generated at
least 5 minutes prior to the failure event by using the following CLI command:
user@host> show log messages
Step 2: Check the System Uptime
Action To check the system uptime, use the following CLI 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
What It Means 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 an FEB
failure. Look for error messages that were generated at least 5 minutes prior to the
failure event by using the following CLI command:
user@host> show log messages
Step 3: Check the FEB Connection
Action Make sure the FEB is properly seated in the midplane. Use a Phillips screwdriver to
ensure that the screws at the top of the FEB are securely tightened.
To Next Page
Loading...
Need help?
General
