Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure a Virtual Chassis Using EX2300, EX4650, or QFX5120 Switches

Follow these steps to configure Virtual Chassis on Juniper switches that don't have a dedicated VC port. Note that the screenshots used in this procedure are for reference only.

The Juniper Networks EX2300, EX4650, and QFX5120 switches do not form a Virtual Chassis by default, as these switches don’t have dedicated Virtual Chassis ports (VCPs). Therefore, to create a Virtual Chassis with these switches, you need to use the Form Virtual Chassis option on the Juniper Mist™ portal. The Form Virtual Chassis option applies only to the EX2300, EX4650, and QFX5120 switches. This workflow creates a preprovisioned Virtual Chassis configuration. Mist supports only the preprovisioned Virtual Chassis configuration.

The procedure to configure a Virtual Chassis using the EX3400, EX4100, EX4100-F, EX4300, or EX4400 switches is different, as those switches have dedicated Virtual Chassis ports (VCPs). For more information, see Configure a Virtual Chassis Using EX3400, EX4100, EX4100-F, EX4100-H, EX4300, EX4000, or EX4400.

Note:

Ensure that you use the Mist portal interfaces to manage all Virtual Chassis configurations. Avoid using CLIs or Additional CLIs for managing Virtual Chassis settings.

To configure a Virtual Chassis using EX2300, EX4650, or QFX5120 switches:

  1. Connect the switches to the Mist cloud. Ensure that you have an uplink connection directly to the switch.
  2. Ensure that all the switches that you want to include in the Virtual Chassis are onboarded to the Juniper Mist™ cloud and assigned to the same site. Also, ensure that configuration management is enabled on the switches.
    To onboard a new switch (greenfield deployment), see Onboard Switches to Mist Cloud. To onboard an existing switch (brownfield deployment) to Juniper Mist, see Onboard a Brownfield Switch (EX and QFX Series).
  3. Click the Switches tab on the left to navigate to the Switches page.
  4. Select the switches that you want to include in the Virtual Chassis.
    An EX2300 switch variant can form a Virtual Chassis with any EX2300 switch variants. An EX4650 variant switch can form a Virtual Chassis with any EX4650 switch variants. A QFX5120 switch variant can form a Virtual Chassis only with the same QFX5120 switch variant. Therefore, the Form Virtual Chassis option is available only if you select the right switch models for a Virtual Chassis.
  5. Click More > Form Virtual Chassis.
    Network management interface displaying Mist-Office-54 site with 4 switches connected, 1 Mist AP, 2 wired clients, 0 wireless clients, total AP power 18W. Switch metrics like affinity, PoE compliance, VLANs, version compliance, and uptime are at 100 percent. Dropdown menu includes switch role assignment, disabling configuration, and virtual chassis options. Buttons for inventory, upgrade, and claim switches are visible.
    Note:

    You can see the Form Virtual Chassis option only if:

    • The selected switches are running the same Junos version and have the configuration management option enabled.

    • All the selected switch models are supported by the Virtual Chassis.

    You can also create Virtual Chassis from the switch details page by using the Utilities > Form Virtual Chassis option.

    The Form Virtual Chassis window appears, as shown in the following example.

    Configuration interface for forming a virtual chassis with Mist EX2300-C-12P switches. Includes options to connect uplink ports, select virtual chassis ports, designate primary and backup switches, and set routing engines. Features dropdown for adding switches, diagram for connection example, and buttons to apply or cancel configuration.
    Note:

    This example shows two switches included in the Virtual Chassis. A Virtual Chassis device created using EX2300 or EX4650 switches supports up to 4 switches. All switches, except those assigned Routing Engine roles, function as linecard members.

  6. On the Form Virtual Chassis window, specify the following:
    1. Port IDs for the switches. These are IDs for the Virtual Chassis ports (VCPs). This window displays all the switches you selected from the Switches page.
    2. The Routing Engine 1 switch. The switch that you selected first is shown as the Routing Engine 1 switch by default. You can modify that.
    3. The Routing Engine 2 switch. This configuration is optional. If you don't select a switch to function in the Routing Engine 2 role, Mist assigns the linecard role to that switch.
    Note:

    • Juniper Mist automatically upgrades a Virtual Chassis linecard member if it is running a Junos version that is different from that of the primary member. The linecard member will be upgraded to the same version as the primary member if the following conditions are met:

      • The switch must form a Virtual Chassis with three or more members—that is, a primary, a backup, and a linecard member.

      • The Junos version on the linecard member is different from that on the primary member.

      • The linecard member must be in Inactive state.

        Note that a linecard member will be upgraded only if it is inactive and running a clearly different Junos version. Minor differences, such as different spin numbers, will not trigger an upgrade.

      • Only the Junos versions listed on the Mist portal are available for upgrade.

    • Ensure that port configurations are tailored to the number of members in the Virtual Chassis. For example, the following configuration should be applied only to a 5-member Virtual Chassis:

      Avoid applying the same port settings across Virtual Chassis devices of different sizes.
    This operation converts the ports to Virtual Chassis ports (VCPs) and also pre-provisions the Virtual Chassis.
  7. Click Form Virtual Chassis and wait for the Virtual Chassis to be created.
    The switches page shows a message indicating that you must connect the switches to each other using the VCPs.
    Network management interface for Mist switches showing metrics: 4 switches, 1 Mist AP, 2 wired clients, 0 wireless clients, 18W AP power. All switches connected with 100 percent uptime and compliance. Navigation menu on the left includes options for monitoring, analytics, and organization.
  8. Connect the switches to each other using the VCPs mentioned earlier.

    When the Virtual Chassis formation is in progress, the Switches page shows the switch status as VC forming.

    Network management dashboard showing Mist-Office-54 site with 4 switches, 1 Mist AP, 2 wired clients, 0 wireless clients, and 18W AP power. Compliance metrics are at 100 percent. Two switches are VC forming, two are connected.

    After the Virtual Chassis formation is successful, the Switches page displays only one entry for the Virtual Chassis with the name of the primary switch. However, the MIST APs column displays one AP for each Virtual Chassis member in a comma-separated format.

    Network management interface displaying site MIST-OFFICE-54 with 3 switches, 1 Mist access point, 3 wired clients, 0 wireless clients, and 18W allocated AP power. Compliance metrics show 100 percent status for Switch-AP Affinity, PoE Compliance, VLANs, Version Compliance, and Switch Uptime. Table lists switch details including status, name, IP address, associated Mist access points, wired clients, wireless clients, and model. Action buttons for inventory, upgrade switches, and claim switches are available.

    The switch details page displays the front panel of all the Virtual Chassis members.

    Network switch management interface showing Mist-ex2300-01 overview with metrics, properties, configuration options, port statuses, and RADIUS settings for monitoring and managing network performance.
Note:

Once the Virtual Chassis is formed, if you need only one uplink to the Virtual Chassis, maintain the uplink to primary switch and remove uplinks from other switches.

You can use the Modify Virtual Chassis option on the switch details page to renumber and replace Virtual Chassis members and add members to a Virtual Chassis connected to the Mist cloud. For more information, see Manage a Virtual Chassis Using Mist.