Supported Platforms
Switching the Global Master and Backup Roles in a Virtual Chassis Configuration
You can 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. When you change the mastership by issuing the request virtual-chassis routing-engine master switch administrative command, the current master router in the Virtual Chassis (also known as the Virtual Chassis protocol master) becomes the backup router, and the current backup router (also known as the Virtual Chassis protocol backup) becomes the master router.
Before you begin:
- Make sure the system configuration is synchronized between
the master router and the backup router.
If the configuration between the member routers is not synchronized when you issue the request virtual-chassis routing-engine master switch command, the router displays the following error message and rejects the command.
Error: mastership switch request NOT honored, backup not ready
- Make sure the Virtual Chassis is not in a transition state
(for example, the backup router is in the process of disconnecting
from the Virtual Chassis) when you issue the request virtual-chassis routing-engine master switch command.
If you attempt to issue the request virtual-chassis routing-engine master switch command during a transition state, the router does not process the command.
To switch the global master and backup roles in an MX Series Virtual Chassis:
- Issue the request virtual-chassis routing-engine master switch command from the Virtual Chassis master router:
{master:member0-re0}Do you want to continue ? [yes,no] (no) yes
If you attempt to issue the request virtual-chassis routing-engine master switch command from the backup router, the router displays the following error message and rejects the command.
error: Virtual Chassis member is not the protocol master
Issuing the request virtual-chassis routing-engine master switch command from the Virtual Chassis master router causes the global role transitions listed in Table 1.
Table 1: Virtual Chassis Global Role Transitions Before and After Mastership Switchover
Virtual Chassis Role Before Switching Mastership
Virtual Chassis Role After Switching Mastership
Master Routing Engine in Virtual Chassis master router (VC-Mm)
Master Routing Engine in Virtual Chassis backup router (VC-Bm)
Standby Routing Engine in Virtual Chassis master router (VC-Ms)
Standby Routing Engine in Virtual Chassis backup router (VC-Bs)
Master Routing Engine in Virtual Chassis backup router (VC-Bm)
Master Routing Engine in Virtual Chassis master router (VC-Mm)
Standby Routing Engine in Virtual Chassis backup router (VC-Bs)
Standby Routing Engine in Virtual Chassis master router (VC-Ms)
The local roles (master and standby, or m and s) of the Routing Engines do not change after you issue the request virtual-chassis routing-engine master switch command. For example, as shown in Table 1, the master Routing Engine in the Virtual Chassis master router (VC-Mm) remains the master Routing Engine in the Virtual Chassis backup router (VC-Bm) after the switchover.
