Juniper Core Router T Series Hardware Manual page 235

Copyright © 2018, Juniper Networks, Inc.
NOTE: The first supported release for graceful Routing Engine switchover
and nonstop active routing on the T320 router is Junos OS Release 7.0 and
Junos OS Release 8.4, respectively. Graceful restart software requirements
are dependent on the routing protocols configured on the router. For the
minimum software requirements for graceful restart, see the Junos OS High
Availability Library for Routing Devices.
To take a host subsystem offline:
Determine whether the host subsystem is functioning as the master or as the backup,
1.
using one of the two following methods:
Check the Routing Engine LEDs on the craft interface. If the green
lit, the corresponding host subsystem is functioning as the master.
Issue the following CLI command. The master Routing Engine is designated
in the Current state field:
user@host> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state
...
If the host subsystem is functioning as the master, switch it to backup using the CLI
2.
command:
user@host> request chassis routing-engine master switch
To halt the Routing Engine:
3.
user@host> request system halt
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 five
minutes after the
On the console or other management device connected to the other Routing Engine,
4.
enter CLI operational mode and issue the following command.
user@host> request chassis cb offline slot n
n is 0 or 1 for the slot number of the host subsystem being taken offline.
Verify that the control board is offline:
5.
Chapter 26: Replacing Host Subsystem Components
Master
request system halt command has been issued.
LED is
MASTER
Master
207