Configuring Mastership Using A Preprovisioned Configuration File - Dell PowerConnect J-EX4200-24T Software Manual

Configuring Mastership Using a Preprovisioned Configuration File

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
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 on page 791
Configuring Mastership Using a Configuration File That Is Not Preprovisioned on page 792
To configure mastership using a preprovisioned configuration:
Note the serial numbers of the switches that you want to function in the master role
1.
and backup role.
Power on only the switch (SWA-0) that you want to function in the master role.
2.
Edit the configuration to specify the preprovisioned configuration mode:
3.
[edit virtual-chassis]
user@SWA-0# set preprovisioned
List the serial numbers of the member switches that you want to function as master
4.
and backup, specifying their role as
[edit]
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
( ). However, the member that was powered on first has higher
128
prioritization according to the master election algorithm. See
"Understanding How the Master in a Virtual Chassis Configuration Is
Elected" on page 698. Only two members can be specified with the
routing-engine
List the serial numbers of any other member switches that you want to include in the
5.
Virtual Chassis configuration. You may also specify their role as
commit synchronize rather than simply
:
routing-engine
role.
Chapter 45: Configuring Virtual Chassis
commit to save
, if desired.
linecard
791