Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

request chassis routing-engine master

Syntax

request chassis routing-engine master (acquire | release | switch) <force><no-confirm>

Syntax (TX Matrix Routers)

request chassis routing-engine master (acquire | release | switch) (lcc number  |
scc | all-chassis) <force><no-confirm>

Syntax (TX Matrix Plus Routers)

request chassis routing-engine master (acquire | release | switch) (lcc number  |
sfc | all-chassis | all-lcc) <force><no-confirm>

Syntax (MX Series Routers)

request chassis routing-engine master (acquire | release | switch) <all-members><force><local><member member-id><no-confirm>

Syntax (MX2010 3D Universal Edge Routers)

request chassis routing-engine master (acquire | release | switch <check>) <no-confirm>

Syntax (MX2020 3D Universal Edge Routers)

request chassis routing-engine master (acquire | release | switch <check>) <no-confirm>

Syntax (QFabric Systems

request chassis routing-engine master (release | switch) <check><interconnect-device name><node-group name><no-confirm>

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 QFX Series.

Command introduced in Junos OS Release 12.3 for MX2020 3D Universal Edge Routers.

Command introduced in Junos OS Release 12.3 for MX2010 3D Universal Edge Routers.

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 routers (in a routing matrix based on the TX Matrix router or 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  or the Junos OS High Availability Configuration 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.

You will receive an error message stating “Command aborted. Not ready for mastership switch, try after n seconds” when this command is re-entered before 240 seconds have elapsed on EX Series switches.

Note: On a QFabric system, to avoid traffic loss on the network Node group, switch mastership of the routing engine to the backup routing engine, and then reboot.

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 or T4000 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.

check
—

(QFabric systems, MX240, MX480, MX960, MX2010, and MX2020 Routers only) (Optional) Available only with the switch option. Check graceful switchover status of the standby Routing Engine before toggling mastership between Routing Engines.

interconnect-device name
—

(QFabric systems only) (Optional) Control Routing Engine mastership on the Routing Engines on an Interconnect device.

lcc number
—

(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card chassis number.

Replace number with the following values depending on the LCC configuration:

  • 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix.
  • 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix.
  • 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.
  • 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.
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 systems only) (Optional) Control Routing Engine mastership on the Routing Engines on a Node group.

scc
—

(TX Matrix routers only) TX Matrix (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

 

List of Sample Output

request chassis routing-engine master acquire
request 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 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 mastership 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.

Published: 2013-08-15

Previous Page Next Page