Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring an EX9200 Virtual Chassis

 
Caution

We do not recommend using EX9200 switches in a Virtual Chassis, and support for that architecture was phased out as of Junos OS Release 17.1R1. For deployments with EX9200 switches, we recommend planning or moving to MC-LAG or Junos Fusion Enterprise architectures instead of using a Virtual Chassis.

You configure an EX9200 Virtual Chassis by configuring optical interfaces into Virtual Chassis ports (VCPs). VCPs connect switches together to form a Virtual Chassis, and are responsible for passing all data and control traffic between member switches in the Virtual Chassis.

Note

Starting with Junos OS Release 17.1R1, EX9200 switches support the EX9200-RE2 module. You cannot form a Virtual Chassis using an EX9200 switch with an EX9200-RE2 module installed in it. If inadvertently configured as a Virtual Chassis, the device will not start up properly; use the request virtual-chassis member-id delete <force> command to remove the Virtual Chassis setting.

This topic includes:

Creating Configuration Groups for an EX9200 Virtual Chassis

A standalone EX9200 switch uses the re0 and re1 configuration groups to apply groups on both Routing Engines. Because a Virtual Chassis with two member switches has four Routing Engines that often have a need to share configuration amongst one another, you should create four groups—one group for each Routing Engine in the Virtual Chassis—instead of using the standard re0 and re1 configuration groups.

For a Virtual Chassis configuration consisting of two EX9200 switches, we strongly recommend that you create and apply on the switch in the master role of the Virtual Chassis the following configuration groups, instead of using the standard re0 and re1 configuration groups:

  • member0-re0

  • member0-re1

  • member1-re0

  • member1-re1

We recommend that you configure these groups before you configure your Virtual Chassis, to ensure that your configuration is always identical on all Routing Engines in the Virtual Chassis.

For information on creating and applying configuration groups for your EX9200 Virtual Chassis, see Creating and Applying Configuration Groups for a Virtual Chassis.

Configuring the EX9200 Virtual Chassis

To configure an EX9200 Virtual Chassis:

Before you perform this procedure:

  1. Log onto the switch that you want to assign as member 0 in your Virtual Chassis.
  2. Specify the preprovisioned configuration mode:
    [edit virtual-chassis]

    user@switch-0# set preprovisioned

    You must use preprovisioned configuration mode to configure an EX9200 Virtual Chassis.

  3. Configure the Virtual Chassis by including both member switches in the Virtual Chassis configuration:
    [edit virtual-chassis]

    user@switch-0# set member 0 serial-number serial-number role routing-engine

    user@switch-0# set member 1 serial-number serial-number role routing-engine

    where serial-number is the chassis serial number of the member switch. You can retrieve the chassis serial number in the show chassis hardware command output or by physically viewing the serial number label on the switch. See Locating the Serial Number on an EX9204 Switch or Component, Locating the Serial Number on an EX9208 Switch or Component, or Locating the Serial Number on an EX9214 Switch or Component for additional information

    An EX9200 Virtual Chassis supports two member switches. Both switches should be assigned the routing-engine role.

    For instance, if you wanted to configure the switch with chassis serial number JN1234567ABC as member 0 and the switch with chassis serial number JN9876543ZYX as member 1 in your EX9200 Virtual Chassis:

    [edit virtual-chassis]

    user@switch-0# set member 0 serial-number JN1234567ABC role routing-engine

    user@switch-0# set member 1 serial-number JN9876543ZYX role routing-engine

  4. Disable the split and merge feature:
    [edit virtual-chassis]

    user@switch-0# set no-split-detection

    Disabling split and merge ensures that all interfaces on the member switch in the master Routing Engine role remain up if the member switch in the backup Routing Engine role fails.

    Split and merge is enabled by default. If the member switch in the backup Routing Engine role fails when split and merge is enabled, all interfaces on all line cards that do not contain at least one Virtual Chassis port (VCP) on the member switch in the master Routing Engine role also fail.

  5. Commit the configuration:
    [edit]

    user@switch-0# commit
  6. Enable Virtual Chassis mode and set the member ID of the switch:
    user@switch-0>request virtual-chassis member-id set member 0

    You must reboot both Routing Engines on the switch to complete this step. We recommend rebooting the switch by answering yes to the prompt that appears on the screen after entering the request virtual-chassis member-id set member command, but you can also enter the request system reboot command to reboot one Routing Engine on the switch or the request system reboot both-routing-engines command to reboot both Routing Engines simultaneously.

  7. Log onto the switch that you want to assign as member 1 in your Virtual Chassis.
  8. Enable Virtual Chassis mode and set the member ID of the switch:
    user@switch-1>request virtual-chassis member-id set member 1

    You must reboot both Routing Engines on the switch to complete this step. We recommend rebooting the switch by answering yes to the prompt that appears on the screen after entering the request virtual-chassis member-id set member command, but you can also enter the request system reboot command to reboot one Routing Engine on the switch or the request system reboot both-routing-engines command to reboot both Routing Engines simultaneously.

  9. Log back onto member 0 after the reboot is complete. Configure the interfaces that you want to configure as VCPs as VCPs:
    user@switch-0>request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number
    Note

    A VCP is not created until the request virtual-chassis vc-port set command is enabled on the interfaces on the member switches at both ends of the link.

    The request virtual-chassis vc-port set is enabled on the interface on the other end of the link in step 10 to complete the VCP configuration process.

    For instance, you can configure port 0 on PIC slot 1 in FPC slot 1 as a VCP using the following command:

    user@switch-0> request virtual-chassis vc-port set fpc-slot 1 pic-slot 1 port 0
  10. Log back onto member 1 after the reboot is complete. Configure the interfaces that you want to configure as VCPs:
    user@switch-0>request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number
    Note

    You can configure multiple links into VCPs. If you configure interfaces of the same speed between the member switches into the VCPs, the VCPs automatically form a Link Aggregation group (LAG) bundle.

    You can use the show virtual-chassis vc-port command to verify that a VCP is created.

    You can use the show virtual-chassis command to verify Virtual Chassis status.

Release History Table
Release
Description
We do not recommend using EX9200 switches in a Virtual Chassis, and support for that architecture was phased out as of Junos OS Release 17.1R1.