Setting an Uplink Port as a Virtual Chassis Port (CLI Procedure)
You can interconnect EX 4200 switches that are beyond the reach of the virtual chassis cables as members of a virtual chassis configuration by installing the optional uplink module (EX-UM-2XFP) and connecting the 10-Gbps fiber uplink ports. To use the uplink ports for interconnecting member switches, you must explicitly set the uplink ports VCPs.
![]() |
Note: To use an uplink as a VCP, it must be one of the 10-Gigabit uplinks (EX-UM-2XFP uplink module). When a link is set as a VCP, it cannot be used for any other purpose. The EX-UM-2XP uplink module has two ports. You can set one port as a VCP and use the other port as a regular uplink. |
Before you set an uplink as a VCP:
- Install the uplink module (EX-UM-2XFP) in the member switches that you want to interconnect.
- Power on and connect to the switch that you plan
to designate as the master of the virtual chassis.

Note: Do not power on the other switches at this point.
- Run EZ Setup on the switch that you are configuring to be the master. Follow the prompts to specify the host name and other identification, time zone, and network properties. See Configuring Basic Settings for an EX-series Switch for details. The properties that you specify for the master apply to the entire virtual chassis, including all the member switches that you later interconnect with the master.
- If you want to configure and manage the virtual chassis remotely, specify the VME global management interface. You can configure the VME global management interface when you are setting up the master or you can do it after completing the other configuration steps for the virtual chassis. See Configuring the Virtual Management Ethernet Interface for Global Management of a Virtual Chassis (CLI Procedure).
- Configure mastership of the virtual chassis using either the nonprovisioned or preprovisioned configuration. See Configuring Mastership of the Virtual Chassis (CLI Procedure) for details.
![]() |
Note: A multimember virtual chassis 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. |
To interconnect a virtual chassis across longer distances, such as wiring closets, you need to:
- Prepare the existing virtual chassis for interconnecting with a potential member switch that is beyond the reach of a virtual chassis cable by setting at least one uplink VCP on an existing member of virtual chassis.
- Prepare the potential member switch for interconnecting with the existing virtual chassis by setting at least one uplink VCP on the standalone switch.
![]() |
Note: We recommend that you set two uplink VCPs within each wiring closet for redundancy. |
- Setting an Uplink VCP on the Master or on an Existing Member
- Setting an Uplink VCP on a Standalone Switch
Setting an Uplink VCP on the Master or on an Existing Member
Set an uplink port of a virtual chassis member as a VCP by executing the operational command request virtual-chassis vc-port on the master of the virtual chassis.
To set the uplink ports for the master (for example, member 0) and for an existing member (for example, member 1) to function as VCPs:
- Set one uplink port of member 0 (the master) as
a VCP interface. You do not need to specify the member member-id option, because the command applies by
default on the member where it is executed.
user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 - Set one uplink port of member 1 as VCP interface.
user@SWA-0>request virtual-chassis vc-port set pic-slot 1 port 0 member 1This example includes the member member-id option, because it is executed on the master (the master is member 0).
Setting an Uplink VCP on a Standalone Switch
To set an uplink VCP on a switch that is not interconnected with the master through the dedicated VCPs on the rear panel, first power on the switch as a standalone switch. You must set an uplink port on the standalone switch as a VCP prior to physically interconnecting the switch with the existing virtual chassis. Otherwise, the master cannot detect that the switch is a member of the virtual chassis.
To set one uplink VCP on the potential member (SWA-2), which is currently operating as a standalone switch:
- Power on the standalone switch.
- Set one uplink port as a VCP interface. You do
not need to specify the member member-id option, because the command applies by default on the member where
it is executed.
user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0
Note: If you do specify the member member-id option, use member ID 0. Because the switch is not yet interconnected with the other members of the virtual chassis, its current member ID is 0. Its member ID will change when it is interconnected with the virtual chassis. It does not impact the functioning of the uplink VCP that its VCP interface is set with 0 as the member ID. The VCP interface has significance only on the local switch.
- After you have set the uplink VCP on the standalone switch, physically interconnect its uplink port with the VCP uplink ports of the members in the existing virtual chassis.
- The new member switch reboots and joins the now
expanded virtual chassis with a different member ID.

Note: Its setting for the uplink VCP remains intact and is not affected by the change of member ID.
- If you have additional members in the second wiring closet, set a redundant VCP uplink on another member switch by issuing the command through the master of the virtual chassis.




