Example: Adding an EX4500 Switch to a Nonprovisioned Virtual Chassis
A Virtual Chassis is multiple switches operating as a single network entity. You might want to expand an existing Virtual Chassis by adding EX4500 switches to it. You can include up to ten EX4500 switches in an EX4500 Virtual Chassis or a mixed EX4200 and EX4500 Virtual Chassis.
This example describes how to add two EX4500 switches to an existing EX4200 Virtual Chassis that was nonprovisioned. A nonprovisioned configuration is a Virtual Chassis whose roles were assigned automatically rather than configured statically (preprovisioned).
Requirements
This example uses the following hardware and software components:
Junos OS Release 11.1 or later for EX Series switches
Two EX4200 switches interconnected into a nonprovisioned Virtual Chassis
Two standalone EX4500 switches with Virtual Chassis modules
Before you begin, be sure you have:
An operational EX4200 Virtual Chassis with two member EX4200 switches that was configured using a nonprovisioned configuration.
Installed the same version of Junos OS Release 11.1 or later for all members of the Virtual Chassis and on the EX4500 switches.
You must use Junos OS Release 11.4 or later if you are including three or more EX4500 switches in an EX4500 Virtual Chassis or a mixed EX4200 and EX4500 Virtual Chassis.
Overview and Topology
You can create an EX4200 Virtual Chassis by cabling two operational EX4200 switches together using the dedicated Virtual Chassis ports (VCPs) on each EX4200 switch. When you cable a Virtual Chassis using the dedicated VCPs, the switches run a primary-role election algorithm that determines the Virtual Chassis roles for each member switch. The primary-role election algorithm first checks the primary-role priority ID. The primary-role priority ID is any number between 0 and 255. The switch with the higher primary-role priority ID is elected into the primary role and the other switch, unless it has been configured with a primary-role priority value of 0, is elected into the backup role.
The default primary-role priority ID for an EX4200 or EX4500 switch is 128. Both EX4200 switches are using this default primary-role priority ID in the operational EX4200 Virtual Chassis in this example.
We recommend that you use the commit synchronize
command to save any configuration changes that you make to a Virtual
Chassis.
Topology
Table 1 shows the default configuration settings for the two-member Virtual Chassis before the EX4500 member switches are added to the Virtual Chassis.
Member Switch | Hardware | Member ID | Role and Priority |
---|---|---|---|
SWA-0 |
EX4200 switch |
0 |
Primary: primary-role priority 128 |
SWA-1 |
EX4200 switch |
1 |
Backup: primary-role priority 128 |
Table 2 shows the configuration of the mixed EX4200 and EX4500 Virtual Chassis after the EX4500 member switches are added to the Virtual Chassis and the EX4500 switches have been configured in the primary and backup roles.
Member Switch | Hardware | Member ID | Role and Priority |
---|---|---|---|
SWA-0 |
EX4200 switch |
0 |
Linecard: primary-role priority 0 |
SWA-1 |
EX4200 switch |
1 |
Linecard: primary-role priority 0 |
SWA-2 |
EX4500 switch |
2 |
Primary: primary-role priority 255 |
SWA-3 |
EX4500 switch |
3 |
Backup: primary-role priority 255 |
Figure 1 shows the hardware topology of the mixed EX4200 and EX4500 Virtual Chassis.

Configuration
Procedure
Step-by-Step Procedure
To add two EX4500 switches to an existing EX4200 Virtual Chassis:
Log in to the EX4200 Virtual Chassis.
Set all member switches into mixed mode:
user@switch> request virtual-chassis mode mixed all-members
Reboot all member switches in the Virtual Chassis:
user@switch> request system reboot
Power on SWA-2, the EX4500 switch that you want to function in the primary role.
Power on SWA-3, the EX4500 switch that you want to function in the backup role.
Set the PIC mode to the Virtual Chassis mode on both SWA-2 and SWA-3:
user@switch> request chassis pic-mode virtual-chassis
Configure SWA-2 and SWA-3 as a member of the mixed EX4200 and EX4500 Virtual Chassis:
user@switch> request virtual-chassis mode mixed
Reboot the EX4500 switches.
Cable SWA-2 into the Virtual Chassis using the dedicated VCP on the back of the EX4200 member switch and the dedicated VCP on the Virtual Chassis module in the EX4500 switch.
Note:We recommend cabling one VCP into the Virtual Chassis, waiting for the new switch to be recognized by the Virtual Chassis, then cabling the other VCP on the new switch into the Virtual Chassis.
If you immediately cable both VCPs into the existing Virtual Chassis, one of the Virtual Chassis member switches might become nonoperational for several seconds. Network traffic to that member switch is dropped during the downtime.
The switch will return to the normal operational state with no user intervention, and normal operation of the Virtual Chassis will resume after this downtime.
Cable SWA-3 into the Virtual Chassis using the dedicated VCP on the back of the EX4200 member switch and the dedicated VCP on the Virtual Chassis module in the EX4500 switch.
Note:We recommend cabling one VCP into the Virtual Chassis, waiting for the new switch to be recognized by the Virtual Chassis, then cabling the other VCP on the new switch into the Virtual Chassis.
If you immediately cable both VCPs into the existing Virtual Chassis, one of the Virtual Chassis member switches might become nonoperational for several seconds. Network traffic to that member switch is dropped during the downtime.
The switch will return to the normal operational state with no user intervention, and normal operation of the Virtual Chassis will resume after this downtime.
Log in to the Virtual Chassis and set the primary-role priority for the EX4200 switches to 0 and the EX4500 switches to 255:
[edit virtual-chassis] user@SWA–0# set member 0 mastership-priority 0 user@SWA–0# set member 1 mastership-priority 0 user@SWA–0# set member 2 mastership-priority 255 user@SWA–0# set member 3 mastership-priority 255
Note:A switch with a primary-role priority value of 0 never assumes the primary or backup role within a Virtual Chassis. This configuration ensures that the EX4200 member switches remain in the linecard roles even during Virtual Chassis topology changes.
If you want the EX4200 switches to assume the primary or backup roles, assign the switches a primary-role priority between 1 and 255.
Verification
To confirm that the Virtual Chassis configuration is operational, perform these tasks:
Verifying Virtual Chassis Availability and Roles
Purpose
Verify that the Virtual Chassis is up and that the member switches are in the correct roles.
Action
List the member switches and roles.
user@SWA-2> show virtual-chassis Virtual Chassis ID: 0019.e250.47a0 Mastership Neighbor List Member ID Status Serial No Model priority Role ID Interface 0 (FPC 0) Prsnt AK02073602764 ex4200-48p 0 Linecard 1 vcp-0 3 vcp-1 1 (FPC 1) Prsnt AK02073602814 ex4200-48p 0 Linecard 0 vcp-0 2 vcp-1 2 (FPC 2) Prsnt AK02073602844 ex4500-40f 255 Master* 1 vcp-0 3 vcp-1 3 (FPC 3) Prsnt AK02073602088 ex4500-40f 255 Backup 2 vcp-0 0 vcp-1 Member ID for next new member: 4 (FPC 4)
Meaning
The show virtual-chassis
command lists the member switches interconnected in a Virtual
Chassis configuration with the member IDs that have been assigned
by the primary, the primary-role priority values, and the roles. It
also displays the neighbor members with which each member is interconnected.
The output shows that the switches have the correct primary role priorities
and roles.