Supported Platforms
request virtual-chassis routing-engine master switch (MX Series Virtual Chassis)
Syntax
Release Information
Command introduced in Junos OS Release 11.2.
Option check introduced in Junos OS Release 12.2.
Description
Change the mastership in an MX Series Virtual Chassis by switching the global roles of the master router and backup router in the Virtual Chassis configuration. The request virtual-chassis routing-engine master switch command must be issued from the master router (VC-Mm).
For MX Series routers with dual Routing Engines in a Virtual Chassis, the local roles (master and standby) of the Routing Engines in each member router do not change after you issue the request virtual-chassis routing-engine master switch command.
![]() | Note: Before you issue the request virtual-chassis routing-engine master switch command from the master router in the Virtual Chassis, make sure that the system configuration is synchronized between the master router and backup router. If the configuration on the master router and backup router is not synchronized, or if you attempt to issue the request virtual-chassis routing-engine master switch command from the backup router instead of from the master router, the router displays an error message and rejects the command. If you issue the request virtual-chassis routing-engine master switch command when the Virtual Chassis is in a transition state (for example, the backup router is disconnecting from the Virtual Chassis), the router does not process the command. |
Options
check | — | (Optional) Perform a check from the master router in an MX Series Virtual Chassis to determine whether the member routers are ready for GRES from a database synchronization perspective, without initiating the GRES operation itself. |
Required Privilege Level
system-control
List of Sample Output
request virtual-chassis routing-engine master switch (From Master Router)request virtual-chassis routing-engine master switch (Error When Configuration Not Synchronized)
request virtual-chassis routing-engine master switch (Error When Run from Backup Router)
request virtual-chassis routing-engine master switch check (Ready for GRES)
request virtual-chassis routing-engine master switch check (Not Ready for GRES)
Sample Output
request virtual-chassis routing-engine master switch (From Master Router)
{master:member0-re0}
user@host> request virtual-chassis routing-engine
master switch
Do you want to continue ? [yes,no] (no)
request virtual-chassis routing-engine master switch (Error When Configuration Not Synchronized)
{master:member0-re0}
user@host> request virtual-chassis routing-engine
master switch
Error: mastership switch request NOT honored, backup not ready
request virtual-chassis routing-engine master switch (Error When Run from Backup Router)
{backup:member1-re0}
user@host1> request virtual-chassis routing-engine
master switch
error: Virtual Chassis member is not the protocol master
request virtual-chassis routing-engine master switch check (Ready for GRES)
{master:member0-re0}
user@host> request virtual-chassis routing-engine
master switch check
{master:member0-re0}
request virtual-chassis routing-engine master switch check (Not Ready for GRES)
{master:member0-re0}
user@host> request virtual-chassis routing-engine
master switch check
error: chassisd Not ready for mastership switch, try after 217 secs. mastership switch request NOT honored, backup not ready