request virtual-chassis routing-engine master switch
Syntax
request virtual-chassis routing-engine master switch <check>
Description
Change the primary role in an MX Series Virtual
Chassis or EX9200 Virtual Chassis by switching the global roles of
the primary router or switch and backup router or switch in the Virtual
Chassis configuration. The request virtual-chassis routing-engine
master switch command must be issued from the primary router
or switch (VC-Pp).
(MX Series
routers only) The local roles (master and standby, or m and s) of the Routing Engines in the
Virtual Chassis primary router change after a global switchover, but
the local roles of the Routing Engines in the Virtual Chassis backup
router do not change. For example, the primary Routing Engine in the
Virtual Chassis primary router (VC-Pp) becomes the standby Routing
Engine in the Virtual Chassis backup router (VC-Bs) after the global
switchover. By contrast, the primary Routing Engine in the Virtual
Chassis backup router (VC-Bp) remains the primary Routing Engine in
the Virtual Chassis primary router (VC-Pp) after the global switchover.
Before you issue the request virtual-chassis routing-engine
master switch command from the primary router or switch in the
Virtual Chassis, make sure that the system configuration is synchronized
between the primary and backup router or switch. If the configuration
is not synchronized, or if you attempt to issue the request virtual-chassis
routing-engine master switch command from the backup router
or switch instead of from the primary router or switch, the device
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 or switch is disconnecting from
the Virtual Chassis), the device does not process the command.
Options
| check | (Optional) Perform a check from the primary router or switch to determine whether the member routers or switches are ready for GRES from a database synchronization perspective, without initiating the GRES operation itself. |
Required Privilege Level
system-control
Sample Output
- request virtual-chassis routing-engine master switch (From Primary 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)
request virtual-chassis routing-engine master switch (From Primary 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 readyrequest virtual-chassis routing-engine master switch (Error When Run from Backup Router)
{backup:member1-re0}
user@host> request virtual-chassis routing-engine master switch
error: Virtual Chassis member is not the protocol masterrequest virtual-chassis routing-engine master switch check (Ready for GRES)
{master:member0-re0}
user@host> request virtual-chassis routing-engine master switch check
Switchover Readyrequest 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 readyRelease Information
Command introduced in Junos OS Release 11.2.
Option check introduced in Junos OS Release 12.2.