Or Removal - Juniper M120 Hardware Manual

Related
Documentation
Troubleshooting an M120 FEB When a Chassis Alarm Is Lit Upon Initial Startup or
Removal
Problem
Solution
Copyright © 2018, Juniper Networks, Inc.
3.3 V
5.0 V
1.2 V Rocket IO
1.5 V Rocket IO
1.8 V RLDRAM
I2C Slave Revision
M120 Forwarding Engine Boards (FEBs) Description on page 75
Maintaining the M120 FEBs on page 278
Replacing an M120 FEB on page 255
Description: An FPC is mapped to an empty FEB slot, the red alarm LED on the chassis
is lit:
The FPC mapped to an empty FEB slot (or to a FEB that is offline) comes online, but its
Physical Interface Cards (PICs) do not, and the physical interfaces on those PICs are not
created.
On startup, the red alarm LED is lit if an FPC slot is filled, but the corresponding FEB
slot is empty.
The red alarm LED is lit if a FEB is removed before its connected FPCs are remapped
to either another FEB or to
To eliminate the red alarm LED:
Check the status of FEBs and determine whether each FPC is connected to an active
1.
FEB by entering the show chassis fpc-feb-connectivity
FPC is associated with the FEB of the same identifying number; for example, FPC 1 to
FEB 1.
If necessary, change the default FPC-FEB connection by using the
2.
statement at the
[edit chassis]
specify that the FPC is not mapped to any FEB. (When an FPC is configured not to
connect to any FEB, interfaces on that FPC are not created; however, no alarm is
triggered.)
Verify that the associated physical interfaces are created by entering the
3.
command.
interfaces terse
For more information about configuring FPC-FEB connectivity, see the Junos OS
Administration Library.
Chapter 32: Troubleshooting Components
3138 mV
4763 mV
1160 mV
1408 mV
1717 mV
15
.
none
hierarchy level. You can also map an FPC to
command. By default, each
fpc-feb-connectivity
none
show
to
291