Technical Documentation
Related Documentation
- EX Series
- show chassis routing-engine
- J Series
- show chassis routing-engine
- M Series
- show chassis routing-engine
- MX Series
- show chassis routing-engine
- QFX Series
- show chassis routing-engine
- T Series
- show chassis routing-engine
request chassis routing-engine master
Syntax
Syntax (TX Matrix Router)
scc | all-chassis) <force><no-confirm>
Syntax (TX Matrix Plus Router)
sfc | all-chassis | all-lcc) <force><no-confirm>
Syntax (MX Series Router)
Syntax (QFX Series)
Release Information
Command introduced before Junos OS Release 7.4.
all-chassis option added in Junos OS Release 8.0.
Command introduced in Junos OS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Description
For routers or switches with multiple Routing Engines, control which Routing Engine is the master.
 | Caution:
(Routing matrix based on the TX Matrix or TX Matrix
Plus routers only) Within the routing matrix, we recommend that all
Routing Engines run the same Junos OS Release. If you run different
releases on the Routing Engines and a change in mastership occurs
on any backup Routing Engine in the routing matrix, one or all T640
routers (in a routing matrix based on the TX Matrix router) or T1600
routers (in a routing matrix based on a TX Matrix Plus router) might
become logically disconnected from the TX Matrix router and cause
data loss. For more information, see the TX Matrix Router Hardware Guide |
 | Note: 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. |
Options
acquire | — | Attempt to become the master Routing Engine. |
release | — | Request that the other Routing Engine become the master. |
switch | — | Toggle mastership between Routing Engines. |
The acquire, release, and switch options have the following suboptions:
all-chassis | — | (TX Matrix and TX Matrix Plus routers only) On a routing matrix composed of a TX Matrix router and the attached T640 routers, switch mastership on all the Routing Engines in the routing matrix. Likewise, on a routing matrix composed of a TX Matrix Plus router and the attached T1600 routers, switch mastership on all the Routing Engines in the routing matrix. |
all-lcc | — | (TX Matrix Plus routers only) Request to acquire mastership for all line-card chassis (LCC). |
all-members | — | (MX Series routers only) (Optional) Control Routing Engine mastership on the Routing Engines in all member routers of the Virtual Chassis configuration. |
interconnect-device name | — | (QFabric switches only) (Optional) Control Routing Engine mastership on the Routing Engines on an Interconnect device. |
lcc number | — | (TX Matrix and TX Matrix Plus routers only) On a TX Matrix router, the T640 router (or LCC) that is connected to the TX Matrix router (or switch-card chassis). On a TX Matrix Plus router, the T1600 router (or LCC) that is connected to the TX Matrix Plus router (or switch-fabric chassis). Replace number with a value from 0 through 3. |
local | — | (MX Series routers only) (Optional) Control Routing Engine mastership on the Routing Engines in the local Virtual Chassis member. |
member member-id | — | (MX Series routers only) (Optional) Control Routing Engine mastership on the Routing Engines of the specified member in the Virtual Chassis Configuration. Replace member-id with a value of 0 or 1. |
no-confirm | — | (Optional) Do not request confirmation for the switch. |
node-group name | — | (QFabric switches only) (Optional) Control Routing Engine mastership on the Routing Engines on a Node group. |
scc | — | (TX Matrix routers only) TX Matrix (or switch-card chassis). |
sfc | — | (TX Matrix Plus routers only) TX Matrix Plus router (or switch-fabric chassis). |
force | — | (Optional) Available only with the acquire option. Force the change to a new master Routing Engine. |
Additional Information
Because both Routing Engines are always running, the transition from one to the other as the master Routing Engine is immediate. However, the changeover interrupts communication to the System and Switch Board (SSB). The SSB takes several seconds to reinitialize the Flexible PIC Concentrators (FPCs) and restart the PICs. Interior gateway protocol (IGP) and BGP convergence times depend on the specific network environment.
By default, the Routing Engine in slot 0 (RE0) is the master
and the Routing Engine in slot 1 (RE1) is the backup. To change
the default master Routing Engine, include the routing-engine statement at the [edit chassis redundancy] hierarchy
level in the configuration. For more information, see the Junos OS System Basics Configuration Guide 
To have the backup Routing Engine become the master Routing Engine, use the request chassis routing-engine master switch command. If you use this command to change the master and then restart the chassis software for any reason, the master reverts to the default setting.
| Note: 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
Related Documentation
- EX Series
- show chassis routing-engine
- J Series
- show chassis routing-engine
- M Series
- show chassis routing-engine
- MX Series
- show chassis routing-engine
- QFX Series
- show chassis routing-engine
- T Series
- show chassis routing-engine
List of Sample Output
request chassis routing-engine master acquirerequest chassis routing-engine master switch
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
request chassis routing-engine master 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 master switch
user@host> request chassis routing-engine master
switchwarning: 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 mastership back to the local Routing Engine:
user@host> request chassis routing-engine master
switchwarning: 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.
