request chassis routing-engine master
Syntax
request chassis routing-engine master (acquire | release | switch) <no-confirm>
Syntax (M Series, MX Series, ACX7509, ACX1000 Devices)
request chassis routing-engine master (acquire | release | switch) <no-confirm> <check>
Syntax (MX Series Virtual Chassis)
request chassis routing-engine master (acquire | release | switch) <all-members> <check> <local> <member member-id> <no-confirm>
Syntax (QFX Series)
request chassis routing-engine master (release | switch) <check> <interconnect-device name> <node-group name> <no-confirm>
Description
For routers or switches with multiple Routing Engines, control which Routing Engine is the primary.
Successive graceful Routing Engine switchover events must be a minimum of 240 seconds (4 minutes) apart after both Routing Engines have come up.
If the router or switch displays a warning message similar to “Standby Routing Engine is not ready for graceful switchover. Packet Forwarding Engines that are not ready for graceful switchover might be reset,” do not attempt switchover. If you choose to proceed with switchover, only the Packet Forwarding Engines that were not ready for graceful switchover are reset. None of the Flexible PIC concentrators (FPCs) should spontaneously restart. We recommend that you wait until the warning no longer appears and then proceed with the switchover.
You will receive an error message stating “Command terminated. Not ready for primary role switch, try after n seconds” when this command is re-entered before 240 seconds have elapsed on EX Series switches.
On a QFabric system, to avoid traffic loss on the network Node group, switch primary role of the routing engine to the backup routing engine, and then reboot.
Options
| acquire |
(Not available for Junos OS Evolved) Attempt to become the primary Routing Engine. |
| release |
(Not available for Junos OS Evolved) Request that the other Routing Engine become the primary. |
| switch |
Toggle primary role between Routing Engines. |
The acquire option should be used with caution because acquiring
a Routing Engine may result in a corrupted database. If possible, use the
switch option instead.
The acquire, release, and switch
options have the following suboptions:
| all-members |
(MX Series routers only) (Optional) Control Routing Engine primary role on the Routing Engines in all member routers of the Virtual Chassis configuration. |
| check |
(ACX7509, MX104, MX480, MX960, MX2010, MX2020, and MX2008 routers,
QFabric systems, and PTX5000 routers
only)
(Optional) Available with the |
| interconnect-device name |
(QFabric systems only) (Optional) Control Routing Engine primary role on the Routing Engines on an Interconnect device. |
| local |
(MX Series routers only) (Optional) Control Routing Engine primary role on the Routing Engines in the local Virtual Chassis member. |
| member member-id |
(MX Series routers only) (Optional) Control Routing Engine primary role
on the Routing Engines of the specified member in the Virtual Chassis
configuration. Replace |
| no-confirm |
(Optional) Do not request confirmation for the switch. |
| node-group name |
(QFabric systems only) (Optional) Control Routing Engine primary role on the Routing Engines on a Node group. |
Additional Information
Always use the show system switchover command on the backup Routing
Engine to determine if the backup is ready to take over as the primary Routing
Engine.
By default, the Routing Engine in slot 0 (RE0) is the primary and
the Routing Engine in slot 1 (RE1) is the backup. To change the
default primary Routing Engine, include the routing-engine
statement at the [edit chassis redundancy] hierarchy level in the
configuration.
To have the backup Routing Engine become the primary Routing Engine, use the
request chassis routing-engine master switch command. If you
use this command to change the primary and then restart the chassis software for any
reason, the primary reverts to the default setting.
Although the configurations on the two Routing Engines do not have to be the same and are not automatically synchronized, we recommend making both configurations the same.
Required Privilege Level
maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
- request chassis routing-engine primary acquire
- request chassis routing-engine primary switch
- request chassis routing-engine master switch (Junos OS Evolved)
- request chassis routing-engine master switch (ACX7348)
- request chassis routing-engine primary switch check (ACX7509, M Series, and MX Series Devices)
- request chassis routing-engine master switch check (DRAM Size Mismatch Between Primary and Standby)
- request chassis routing-engine master switch check (Disabled Backup Routing Engine)
- request chassis routing-engine master switch no-confirm (Disabled Backup Routing Engine)
request chassis routing-engine primary acquire
user@host> request chassis routing-engine master acquire warning: Traffic will be interrupted while the PFE is re-initialized warning: The other routing engine's file system could be corrupted Reset other routing engine and become master ? [yes,no] (no)
request chassis routing-engine primary switch
user@host> request chassis routing-engine master switch warning: Traffic will be interrupted while the PFE is re-initialized Toggle mastership between Routing Engines ? [yes,no] (no) yes Resolving mastership... Complete. The other Routing Engine becomes the master.
Switch primary role back to the local Routing Engine:
user@host> request chassis routing-engine master switch warning: Traffic will be interrupted while the PFE is re-initialized Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The local routing engine becomes the master.
request chassis routing-engine master switch (Junos OS Evolved)
user@host> request chassis routing-engine master switch Resolving mastership... Complete. The other Routing Engine becomes the master.
Switching back to primary router:
user@host> request chassis routing-engine master switch Resolving mastership... Complete. The local Routing Engine becomes the master.
If you did not switch back and tried to enter configuration mode, you would get the following error message:
user@host> configure error: unknown command: configure Configuration is allowed only from the master Routing Engine.
request chassis routing-engine master switch (ACX7348)
user@host> request chassis routing-engine master switch Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Mastership will switchover within 45 secs Please check mastership status using 'show chassis routing-engine'
request chassis routing-engine primary switch check (ACX7509, M Series, and MX Series Devices)
warning: Standby Routing Engine is not ready for graceful switchover.
{master}[edit]
user@host> request chassis routing-engine master switch check
Platform specific components not ready for switchover
Output when system is ready for graceful switchover.
user@host> request chassis routing-engine master switch check Switchover Ready
You can similarly check the backup Routing Engine for the switchover readiness.
request chassis routing-engine master switch check (DRAM Size Mismatch Between Primary and Standby)
user@host> request chassis routing-engine master switch check
error: Standby mirror connection is not up:RE DRAM Size Mismatch
{master}To check switchover readiness, use the show system switchover
command before changing the mastership. Please note that the switchover is
denied until 360 seconds have passed from the previous switchover.
request chassis routing-engine master switch check (Disabled Backup Routing Engine)
user@host> request chassis routing-engine master switch check Backup RE disabled
request chassis routing-engine master switch no-confirm (Disabled Backup Routing Engine)
user@host> request chassis routing-engine master switch no-confirm Backup RE disabled
Release Information
Command introduced before Junos OS Release 7.4.
all-chassis option added in Junos OS Release 8.0.
Command support added to ACX7509 platform in Junos OS Evo Release 22.1.