The Routing Engines are hot-pluggable, as described in M10i Field-Replaceable Units (FRUs). If two Routing Engines are installed, removal or failure of the backup Routing Engine does not affect router function. Removal or failure of the master Routing Engine affects forwarding and routing depending on your high availability configuration. For detailed information, see M10i Routing Engine Description. To replace a Routing Engine, perform the following procedures:
To remove a Routing Engine (see Figure 1):
user@host> show chassis routing-engineRouting Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 27 degrees C / 80 degrees F
CPU temperature 27 degrees C / 80 degrees F
DRAM 768 MB
Memory utilization 45 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 3 percent
Interrupt 0 percent
Idle 97 percent
Model RE-5.0
Serial ID 1000647001
Start time 2009-01-28 14:11:50 PST
Uptime 21 hours, 51 minutes, 16 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.02 0.00
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 26 degrees C / 78 degrees F
CPU temperature 27 degrees C / 80 degrees F
DRAM 1536 MB
Memory utilization 23 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 99 percent
Model RE-850
Serial ID 1000648260
Start time 2009-01-28 16:18:12 PST
Uptime 19 hours, 44 minutes, 51 secondsuser@host> request chassis routing-engine
master switch![]() | Note: Router performance might change if the backup Routing Engine's configuration differs from the former master's configuration. For the most predictable performance, configure the two Routing Engines identically, except for parameters unique to a Routing Engine, such as the hostname defined at the [edit system] hierarchy level and the management interface (fxp0 or equivalent) defined at the [edit interfaces] hierarchy level. To configure Routing Engine-specific parameters and still use the same configuration on both Routing Engines, include the appropriate configuration statements under the re0 and re1 statements at the [edit groups] hierarchy level and use the apply-groups statement. For instructions, see the Junos OS System Basics Configuration Guide. |
user@host> request system halt![]() | Note: Wait until a message appears on the console confirming that the operating system has halted. |
For more information about the command, see the Junos OS System Basics and Services Command Reference.
![]() | Note: The CFEB might continue forwarding traffic for approximately 5 minutes after the request system halt command has been issued. |
![]() | Caution: Slide the Routing Engine straight out of the chassis. Damage can result if the Routing Engine gets lodged because of uneven movement. |
Figure 1: Removing a Routing Engine

To install a Routing Engine (see Figure 2):
![]() | Caution: Align the Routing Engine carefully with the guide rails and push it in evenly. Damage can result if the Routing Engine gets lodged in the rails because of uneven movement. |
The Routing Engine might require several minutes to boot.
Figure 2: Installing a Routing Engine
