To take a host subsystem offline:
1. Determine whether the host subsystem is functioning as the master or as the backup,
using one of the two following methods:
•
Check the Routing Engine LEDs on the craft interface. If the green MASTER LED is
lit, the corresponding host subsystem is functioning as the master.
•
Issue the following CLI command. The master Routing Engine is designated Master
in the Current state field:
user@host> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 34 degrees C / 93 degrees F
DRAM 2048 Mbytes
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 99 percent
Start time 2002-01-22 05:21:31 UTC
Uptime 10 days, 16 hours, 4 minutes, 52 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
Routing Engine status:
Slot 1:
Current state Empty
2. If the host subsystem is functioning as the master, switch it to backup using the CLI
command:
user@host> request chassis routing-engine master switch
3. To halt the router:
user@host> request system halt
Wait until a message appears on the console confirming that the operating system
has halted.
The command shuts down the Routing Engine cleanly, so its state information is
preserved. For more information about the command, see request system halt.
NOTE: The SIBs might continue forwarding traffic for approximately 5
minutes after the request system halt command has been issued.
4. On the console or other management device connected to the other Routing Engine,
enter CLI operational mode and issue the following command.
user@host> request chassis cb offline slot n
309Copyright © 2017, Juniper Networks, Inc.
Chapter 27: Replacing Host Subsystem Components