request chassis routing-engine master

Syntax

Syntax (Routing Matrix)

Release Information

Description

For routers with multiple Routing Engines, control which Routing Engine is the master.

Caution: (Routing matrix only) Within the routing matrix, we recommend that all Routing Engines run the same JUNOS software release. If you run different JUNOS releases on the Routing Engines and a change in mastership occurs on any backup Routing Engine in the routing matrix, one or all T640 routing nodes might become logically disconnected from the TX Matrix platform and cause data loss. For more information, see the TX Matrix Platform Hardware Guide or the JUNOS System Basics Configuration Guide.

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.

lcc number — (Routing matrix only) T640 routing node (or line-card chassis) that is connected to a TX Matrix platform. Replace number with a value from 0 through 3.

scc — (Routing matrix only) TX Matrix platform (or switch-card chassis).

all-chassis — (Routing matrix only) Available only with the switch option. Switch mastership on all Routing Engines in a TX Matrix platform.

force — (Optional) Available only with the acquire option. Force the change to a new master Routing Engine.

no-confirm — (Optional) Do not request confirmation for the switch.

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 Physical Interface Cards (PICs). Interior Gateway Protocol (IGP) and Border Gateway Protocol (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 System Basics Configuration Guide

To have the backup Routing Engine become he 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.

If you configure both Routing Engines as masters, when the chassis software restarts for any reason, the Routing Engine in slot 0 becomes the master and the one in slot 1 becomes the backup.

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.

When both Routing Engines are configured as master or when both are configured as backup, and both Routing Engines become operational at the same time, the Routing Engine in slot 0 becomes the master.

Required Privilege Level

maintenance

See Also

List of Sample Output

Output Fields

When you enter this command, you are provided feedback on the status of your request.

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) 

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.

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.