JUNOS Internet Software Network Operations Guide: Hardware
What It Means The command output displays the temperature and status of the FEB, which can be
OK , Failed , or Absent .
Step 2: Display the FEB Detailed Status
Action To display more detailed FEB status, use the following CLI command: user@host> show chassis feb
Sample Output user@host> show chassis feb
FEB status:
Temperature 37 Centigrade
CPU utilization 0 percent
Interrupt utilization 0 percent
Heap utilization 16 percent
Buffer utilization 43 percent
DRAM 64 Mbytes
Internet Processor II Version 1, Foundry IBM, Part number 9
Start time 1999-01-24 16:24:42 UTC
Uptime 2 hours, 21 minutes, 28 seconds
What It Means The command output displays the temperature of the air passing by the FEB, in degrees Centigrade. It displays the total percentage of CPU, interrupt, heap space, and buffer space being used by the FEB processor, including the total DRAM available to the FEB processor. The command output displays the time when the
FEB started running and how long the FEB has been running. A short uptime can indicate that there is an FEB problem.
Verifying FEB Failure
The FEB will either restart, keep crashing, or fail completely. If the FEB fails, you will loose the router interface connections.
Steps To Take To verify FEB failure, follow these steps:
1.
Check the FEB Uptime on page 457
2.
Check the System Uptime on page 457
3.
Check the FEB Connection on page 457
4.
Perform a Swap Test on the FEB on page 458
456 !
Verifying FEB Failure
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.
Verifying FEB Failure !
457
JUNOS Internet Software Network Operations Guide: Hardware
Step 4: Perform a Swap Test on the FEB
CAUTION: Before performing a swap test, always check for bent pins in the midplane and check the FEB for stuck pins in the connector. Pins stuck in the component connector can damage other good slots during a swap test.
You must power down the router to remove and replace the FEB.
Action To perform a swap test on an FEB, follow these steps:
1.
Attach an electrostatic discharge (ESD) wrist strap to your bare wrist, and connect the wrist strap to one of the two ESD points on the chassis.
2.
Turn off power to the router. For information on powering down the router, see the M5 and M10 Internet Router Hardware Guide .
3.
Unscrew the five screws holding the rear chassis component cover in place, and remove the cover. Be sure to save the screws for when you reinstall the cover.
4.
Flip the ends of the two ejector levers towards the outside edges of the router.
5.
Grasp both sides of the FEB and slide it about three-quarters of the way out of the router.
6.
Move one hand underneath the FEB to support it and slide it completely out of the chassis.
7.
Remove the Routing Engine from the FEB.
Unscrew the screws on the outside edges of the extractor clips to unseat the
Routing Engine from the FEB. Press in on the red tabs on the extractor clips, then flip the ends of the extractor clips toward the outside edges of the router to release the Routing Engine. Grasp both sides of the Routing Engine and slide it evenly out of the FEB.
8.
Replace the Routing Engine in the FEB.
Align the rear of the unit with the guides inside the chassis. Slide the Routing
Engine all the way in until it contacts the connectors on the FEB. Flip the ends of the extractor clips toward the center of the router to seat the Routing Engine onto the FEB. Using a screwdriver, tighten the screws on the outside edges of the extractor clips. Slide the Routing Engine into the slot evenly.
9.
Use both hands to grasp the front of the replacement FEB that works and align the rear of the FEB with the guides on the chassis.
10. To ensure proper seating of the ejector levers, move them to an outward position slightly less than perpendicular to the faceplate before seating the FEB in the slot.
11. Slide the FEB all the way into the chassis until it contacts the midplane.
12. Grasp the ejector levers and carefully push the FEB to seat it onto the midplane.
13. Flip the ejector levers toward each other to lodge the FEB in place.
458 !
Verifying FEB Failure
Chapter 35: Monitoring the FEB
Getting FEB Hardware Information
Steps To Take To obtain FEB hardware information, follow these steps:
1.
Display the FEB Hardware Information on page 459
2.
Display the FEB Firmware Information on page 459
3.
Locate the FEB Serial Number ID Label on page 460
Step 1: Display the FEB Hardware Information
Action To display the FEB hardware information, use the following CLI command: user@host> show chassis hardware
Sample Output user@host> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis 50974 M10
Midplane REV 03 710-001950 HA9949
Power Supply A Rev 03 740-002498 LK33316 DC
Display REV 04 710-001995 HB2079
Routing Engine a000000792cd0a01 RE-2.0
FEB REV 11 710-001948 HE6497 Internet Processor II
[...Output truncated...]
What It Means The command output displays the FEB version level, part number, serial number, and description.
Step 2: Display the FEB Firmware Information
Action To display the firmware running on the FEB, use the following CLI command: user@host> show chassis firmware
Sample Output user@host> show chassis firmware
Part Type Version
Forwarding engine board ROM Juniper ROM Monitor Version 4.1b2
O/S Version 4.1I1 by tlim on 2000-04-24 11:27
What It Means The command output displays the type and version level of the firmware running on the FEB.
Getting FEB Hardware Information !
459
JUNOS Internet Software Network Operations Guide: Hardware
Step 3: Locate the FEB Serial Number ID Label
Action To locate the FEB serial number ID label, look near the back on the right side of the
FEB (see Figure 182).
Figure 182: FEB Serial Number ID Label
Serial number ID label
AA1234
Returning the FEB
Action To replace the FEB, see “Return the Failed Component” on page 86 or the M5 and
M10 Internet Router Hardware Guide .
460 !
Returning the FEB
Part 10
Monitoring Redundant Router
Components
!
Host Redundancy Overview on page 463
!
Monitoring Redundant Routing Engines on page 491
!
Monitoring Redundant Power Supplies on page 507
!
Monitoring Redundant Cooling System Components on page 523
!
Monitoring Redundant SIBs on page 543
!
Monitoring Redundant SCGs on page 551
!
Monitoring Redundant Control Boards on page 559
!
(For M40e and M160 routers) Monitoring Redundant MCSs on page 567
!
(For M40e and M160 routers) Monitoring Redundant SFMs on page 577
!
(For M40e and M160 routers) Monitoring Redundant PCGs on page 595
!
(For the M20 router) Monitoring Redundant SSBs on page 605
!
(For the M10i router) Monitoring Redundant CFEBs on page 617
!
(For the M10i router) Monitoring Redundant HCMs on page 623
Monitoring Redundant Router Components !
461
JUNOS Internet Software Network Operations Guide: Hardware
462 !
Monitoring Redundant Router Components
