Configuring Mastership of the Virtual Chassis (CLI Procedure)
You can designate the role (master, backup, or linecard) that a member switch performs within a Virtual Chassis configuration whether or not you are using a preprovisioned configuration.
Note: A multimember Virtual Chassis configuration has two Routing Engines, one in the master and the other in the backup. Therefore, we recommend that you always use commit synchronize rather than simply commit to save configuration changes made for a Virtual Chassis. This ensures that the configuration changes are saved in both Routing Engines.
This topic describes:
- Configuring Mastership Using a Preprovisioned Configuration File
- Configuring Mastership Using a Configuration File That Is Not Preprovisioned
Configuring Mastership Using a Preprovisioned Configuration File
To configure mastership using a preprovisioned configuration:
- Note the serial numbers of the switches that you want to function in the master role and backup role.
- Power on only the switch (SWA-0) that you want to function in the master role.
- Edit the configuration to specify the preprovisioned
user@SWA-0# set preprovisioned
- List the serial numbers of the member switches
that you want to function as master and backup, specifying their role
user@SWA-0# set virtual-chassis member 0 serial-number abc123 role routing-engine
user@SWA-0# set virtual-chassis member 2 serial-number def456 role routing-engine
Note: You cannot directly modify the mastership priority value when you are using a preprovisioned configuration. The mastership priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file. The two members assigned the routing-engine role are assigned the same mastership priority value (128). However, the member that was powered on first has higher prioritization according to the master election algorithm. See Understanding How the Master in a Virtual Chassis Configuration Is Elected. Only two members can be specified with the routing-engine role.
- List the serial numbers of any other member switches that you want to include in the Virtual Chassis configuration. You may also specify their role as linecard, if desired.
Configuring Mastership Using a Configuration File That Is Not Preprovisioned
To configure mastership of the Virtual Chassis through a configuration that is not preprovisioned:
- Power on only the switch that you want to function in the master role (SWA-0).
- Configure the highest possible mastership priority
value (255) for the member that you want to function in the
user@SWA-0# set member 0 mastership-priority 255
- Configure the same mastership priority value (continue
to edit the Virtual Chassis configuration on the master) for the member
that you want to be the backup (SWA-1):
user@SWA-0# set member 1 mastership-priority 255
Note: We recommend that the master and backup have the same mastership priority value to prevent the master and backup status from switching back and forth between master and backup members in failover conditions.
- Use the default mastership priority value (128) for the remaining member switches or configure the mastership priority to a value that is lower than the value specified for members functioning in the master and backup roles.