Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    EX Series Virtual Chassis Overview

    Many Juniper Networks EX Series switches support the Virtual Chassis flexible, scaling switch solution. You can connect individual switches together to form one unit and manage the unit as a single chassis.

    The following feature guides describe Virtual Chassis on different switches:

    This topic applies to all EX Series Virtual Chassis except EX8200 and EX9200 Virtual Chassis.

    The following Virtual Chassis are supported on EX Series switches:

    • An EX2200 Virtual Chassis, composed of up to four EX2200 switches
    • An EX2300 Virtual Chassis, composed of up to four EX2300 switches
    • An EX3300 Virtual Chassis, composed of up to ten EX3300 switches
    • An EX3400 Virtual Chassis, composed of up to ten EX3400 switches
    • An EX4200 Virtual Chassis, composed of up to ten EX4200 switches
    • An EX4300 Virtual Chassis, composed of up to ten EX4300 switches
    • An EX4500 Virtual Chassis, composed of up to ten EX4500 switches
    • An EX4550 Virtual Chassis, composed of up to ten EX4550 switches
    • An EX4600 Virtual Chassis, composed of up to ten EX4600 switches.
    • A mixed EX4200 and EX4500 Virtual Chassis, a Virtual Chassis composed of up to ten total EX4200 and EX4500 switches
    • A mixed EX4200 and EX4550 Virtual Chassis, a Virtual Chassis composed of up to ten total EX4200 and EX4550 switches
    • A mixed EX4200, EX4500, and EX4550 Virtual Chassis, a Virtual Chassis composed of up to ten total EX4200, EX4500, and EX4550 switches
    • A mixed EX4300 and EX4600 Virtual Chassis, a Virtual Chassis composed of up to ten total EX4300 and EX4600 switches.
    • A mixed EX4500 and EX4550 Virtual Chassis, a Virtual Chassis composed of up to ten total EX4500 and EX4550 switches

    Table 1 lists the initial Junos OS release that supports each Virtual Chassis combination. “N/A” indicates the combination is not supported.

    Table 1: Minimum Junos OS Release by Virtual Chassis Connection Type

    Switch

    EX2200 Switch

    EX2300 Switch

    EX3300 Switch

    EX3400 Switch

    EX4200 Switch

    EX4300 Switch

    EX4500 Switch

    EX4550 Switch

    EX4600 Switch

    EX2200 Switch

    12.2R1

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    EX2300 Switch

    N/A

    15.1X53-
    D50

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    EX3300 Switch

    N/A

    N/A

    11.3R1

    N/A

    N/A

    N/A

    N/A

    N/A

    N/A

    EX3400 Switch

    N/A

    N/A

    N/A

    15.1X53-
    D50

    N/A

    N/A

    N/A

    N/A

    N/A

    EX4200 Switch

    N/A

    N/A

    N/A

    N/A

    9.0R1

    N/A

    11.1R1

    12.2R1

    N/A

    EX4300 Switch

    N/A

    N/A

    N/A

    N/A

    N/A

    13.2X50-
    D10

    N/A

    N/A

    13.2X51-
    D25

    EX4500 Switch

    N/A

    N/A

    N/A

    N/A

    11.1R1

    N/A

    11.1R1

    12.2R1

    N/A

    EX4550 Switch

    N/A

    N/A

    N/A

    N/A

    12.2R1

    N/A

    12.2R1

    12.2R1

    N/A

    EX4600 switch

    N/A

    N/A

    N/A

    N/A

    N/A

    13.2X51-
    D25

    N/A

    N/A

    13.2X51-
    D25

    This topic describes:

    Basic Configuration of a Virtual Chassis

    You need to interconnect at least two switches to form a Virtual Chassis.

    You can interconnect EX2200 switches into an EX2200 Virtual Chassis by configuring uplink ports as Virtual Chassis Ports (VCPs). You can configure any EX2200 uplink ports that support 1-Gbps speeds as VCPs.

    You can interconnect EX2300 switches into an EX2300 Virtual Chassis by configuring uplink ports as VCPs and using SFP+ transceivers.

    Note: You cannot use SFP tranceivers on uplink ports to interconnect EX2300 switches into a Virtual Chassis.

    You can interconnect EX3300 switches into a Virtual Chassis by interconnecting uplink port connections configured as VCPs between two or more switches. By default, uplink ports 2 and 3 on EX3300 switches are configured as VCPs. EX3300 switches do not have dedicated VCPs. See Configuring an EX3300 Virtual Chassis (CLI Procedure).

    You can interconnect EX3400 switches into a Virtual Chassis using uplink port connections configured as VCPs between two or more switches. EX3400 switches do not have dedicated VCPs, but the QSFP+ uplink ports on EX3400 switches are configured as VCPs by default, or you can configure uplink ports with SFP+ tranceivers as VCPs.

    You can interconnect EX4200, EX4500, and EX4550 switches in a Virtual Chassis by either interconnecting the switches through the dedicated VCPs or by configuring the optical port connections as VCPs. All EX4200 switches are shipped with two built-in dedicated VCPs. The dedicated VCPs are on the Virtual Chassis module in an EX4500 or EX4550 switch. All supported SFP, SFP+, and XFP uplink connections between EX4200, EX4500, and EX4550 switches can be configured as VCPs.

    You interconnect EX4300 switches and EX4600 switches into a Virtual Chassis using the uplink ports. All uplink ports on EX4300 and EX4600 switches are not configured into VCPs by default, with the exception that all 40-Gbps QSFP+ ports on an EX4300 switch are configured as VCPs by default.

    See the following for more information on configuring EX Series Virtual Chassis:

    Expanding Configurations—Within a Single Wiring Closet and Across Wiring Closets

    Within a single wiring closet, you can simply add a new member switch to a Virtual Chassis by cabling the member switch into the Virtual Chassis using the dedicated VCPs (for EX4200, EX4500, and EX4550 switches) or default-configured VCPs (for switches such as EX3300, EX3400 or EX4300 switches).

    You can easily expand a Virtual Chassis configuration beyond a single wiring closet or over a longer distance by connecting member switches together using SFP, SFP+, or XFP uplink connections and configuring those connections as VCPs. All supported SFP, SFP+, and XFP uplink connections between EX4200, EX4500, and EX4550 switches can be configured as VCPs. All supported SFP+ and QSFP+ uplink connections between EX4300 and EX4600 switches can also be configured into VCPs.

    EX2200, EX2300, EX3300, and EX3400 switches do not have dedicated VCPs. You must always use the uplink ports on an EX2200, EX2300, EX3300, or EX3400 switch to connect the Virtual Chassis both within a wiring closet and across wiring closets. Uplink ports 2 and 3 are automatically configured as VCPs on EX3300 switches. All QFSP+ ports on EX3400 switches are configured as VCPs by default. No uplink ports on EX2200 or EX2300 switches are automatically configured as VCPs. You can configure SFP ports on EX2200 switches and SFP+ ports on EX2300s as VCPs.

    When you are creating a Virtual Chassis, you might want to deterministically control the role and member ID assigned to each member switch. You can do this by creating a preprovisioned configuration. You can add switches to a preprovisioned configuration by using the autoprovisioning feature to automatically configure the uplink ports as VCPs on the switches being added.

    For procedures on adding a new switch to a wiring closet, see:

    To manually configure a VCP, see:

    Global Management of Member Switches in a Virtual Chassis

    The interconnected member switches in a Virtual Chassis operate as a single network entity. You run EZSetup only once to specify the identification parameters for the master, and these parameters implicitly apply to all members of the Virtual Chassis. You can view the Virtual Chassis as a single device in the J-Web user interface (on platforms and software that support J-Web) and apply various device management functions to all members of the Virtual Chassis.

    The serial console port and dedicated out-of-band management port that are on the rear panel of the individual switches have global virtual counterparts when the switches are interconnected in a Virtual Chassis configuration. A PC or laptop allows you to connect to the master switch by connecting a terminal directly to the console port of any member switch. A virtual management Ethernet (VME) interface allows you to remotely manage the Virtual Chassis configuration by connecting to the out-of-band management port of any member switch through a single IP address. See Understanding Global Management of a Virtual Chassis.

    High Availability Through Redundant Routing Engines

    You increase your network’s high availability when you interconnect an EX Series switch into a Virtual Chassis. A Virtual Chassis is more fault tolerant then a standalone EX series switch because it remains up when a single member switch fails, and provides sub-second convergence in the case of a device or link failure.

    A Virtual Chassis has dual Routing Engines, with one switch in the master role and one switch in the backup role, and therefore supports many high availability features not supported on standalone EX Series switches, such as Graceful Routing Engine Switchover (GRES) for hitless failover. See Understanding High Availability on an EX Series Virtual Chassis for more information on high availability features in a Virtual Chassis.

    You can further improve the high availability of your network by configuring the high availability features available for your EX Series Virtual Chassis. You can, for instance, configure Link Aggregation Groups (LAG) bundles to include member links on multiple member switches in the same Virtual Chassis. This configuration increases fault tolerance because traffic traversing the LAG can be redirected to an active member switch when a single member switch fails.

    Adaptability as an Access Switch or Distribution Switch

    A Virtual Chassis configuration supports a variety of user environments, because it can be composed of different models of switches. You can select different switch models to support various functions. For example, you might set up one Virtual Chassis access switch configuration composed of the full Power over Ethernet (PoE) models to support users sitting in cubicles equipped with PCs and Voice over IP (VoIP) phones. You could set up another Virtual Chassis configuration with partial PoE models to support the company's internal servers and configure one more Virtual Chassis configuration with partial PoE models to support the company's external servers. Alternatively, you can use the Virtual Chassis as a distribution switch.

    Modified: 2018-03-13