Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
This topic does not apply to a mixed Virtual Chassis configuration. For information on configuring a mixed Virtual Chassis, see Configuring a Mixed Virtual Chassis with EX4200, EX4500, and EX4550 Member Switches (CLI Procedure).
You can interconnect EX4200, EX4500, and EX4550 switches using the dedicated Virtual Chassis ports (VCPs) on the rear panel of EX4200 switches and on the Virtual Chassis module in EX4500 and EX4550 switches. You do not have to configure the interfaces for the dedicated VCPs.
If you want to interconnect member switches that are located in different racks or wiring closets, you interconnect them using optical ports configured as VCPs. See Setting an Uplink Port on an EX Series or QFX Series Switch as a Virtual Chassis Port or Setting an Uplink Port as a Virtual Chassis Port on an EX4500 or EX4550 Switch (CLI Procedure).
A Virtual Chassis configuration has two Routing Engines, one in the primary 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.
An EX4200, EX4500, or EX4550 Virtual Chassis can be configured with either:
A preprovisioned configuration—Allows you to deterministically control the member ID and role assigned to a member switch by tying it to its serial number.
A nonprovisioned configuration—The primary sequentially assigns a member ID to other member switches. The role is determined by the primary-role priority value and other factors in the primary-role election algorithm.
This topic includes:
Configuring an EX4200, EX4500, or EX4550 Virtual Chassis with a Preprovisioned Configuration File
Preprovisioning a Virtual Chassis configuration allows you to assign the member ID and role for each switch in the Virtual Chassis.
To configure a Virtual Chassis using a preprovisioned configuration:
You cannot modify the primary-role priority when you are using a preprovisioned configuration. The primary-role priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file. The two Routing Engines are assigned the same primary-role priority value. However, the member that was powered on first has higher prioritization according to the primary-role election algorithm. See Understanding How the Primary in a Virtual Chassis Is Elected.
Configuring an EX4200, an EX4500, or EX4550 Virtual Chassis with a Nonprovisioned Configuration File
To configure the Virtual Chassis using a nonprovisioned configuration:
If you do not edit the Virtual Chassis configuration file, a nonprovisioned configuration is generated by default. The primary-role priority value for each member switch is 128. The primary role is selected by default. You can change the role that is performed by the members by modifying the primary-role priority. See Configuring Primary Role of a Virtual Chassis. We recommend that you specify the same primary-role priority value for the desired primary and backup members. In this example, the highest possible primary-role priority has been assigned to two members. However, the member that was powered on first has higher prioritization according to the primary-role election algorithm. See Understanding How the Primary in a Virtual Chassis Is Elected. The other members use the default primary-role priority in this example, which configures them to function in the role of linecard.
If you want to change the member ID that the primary has
assigned to a member switch, use the request virtual-chassis renumber command.