Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring an EX2200 Virtual Chassis (CLI Procedure)

You configure an EX2200 Virtual Chassis by configuring interfaces connecting EX2200 switches into Virtual Chassis ports (VCPs). Optical interfaces on EX2200 and EX2200-C switches can be configured into VCPs and can be used to connect EX2200 switches into a Virtual Chassis over short and long distances (up to 49.7 miles). All RJ-45 interfaces, including built-in network ports with 10/100/1000BASE-T Gigabit Ethernet connectors and 1000BASE-T RJ-45 transceivers, on EX2200 and EX2200-C switches can also be configured into VCPs.

An EX2200 Virtual Chassis can be configured with either:

• A preprovisioned configuration—You can deterministically control the member ID and role assigned to a member switch by tying it to its serial number.
• A nonprovisioned configuration—The master sequentially assigns a member ID to other member switches. The role is determined by the mastership priority value and other factors in the master election algorithm.

Note: A Virtual Chassis configuration has two Routing Engines—the master switch and the backup switch. 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.

Note: You do not have to purchase a license to configure an EX2200 Virtual Chassis starting in Junos OS release 12.3R2. Prior to Junos OS release 12.3R2, two enhanced feature licenses (EFLs)—one for the switch in the master role and another for the switch in the backup role—must be purchased to create an EX2200 Virtual Chassis. See Understanding Software Licenses for EX Series Switches.

This topic includes:

• Configuring an EX2200 Virtual Chassis with a Preprovisioned Configuration File
• Configuring an EX2200 Virtual Chassis with a Nonprovisioned Configuration File

Configuring an EX2200 Virtual Chassis with a Preprovisioned Configuration File

Preprovisioning a Virtual Chassis configuration allows you to assign the member ID and role for each switch in the Virtual Chassis.

To configure a Virtual Chassis using a preprovisioned configuration:

Note: We recommend that you physically cable the ports as the final step of this procedure. You can, however, configure an EX2200 Virtual Chassis while the cables are physically connected.

1. Make a list of the serial numbers of all the switches to be connected in a Virtual Chassis configuration.
2. Note the desired role (routing-engine or line-card) of each switch. If you configure the member with a routing-engine role, it is eligible to function in the master or backup role. If you configure the member with a line-card role, it is not eligible to function in the master or backup role.
3. Power on only the switch that you plan to use as the master switch.
4. Run the EZSetup program on the master switch, specifying the identification parameters. See Connecting and Configuring an EX Series Switch (CLI Procedure) for details.

   Note: The properties that you specify for the master switch apply to the entire Virtual Chassis configuration.

5. (Optional) Configure the master switch with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis:
   [edit]
user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/
6. Specify the preprovisioned configuration mode:
   [edit virtual-chassis]
user@switch# set preprovisioned

7. Specify all the members that you want included in the Virtual Chassis, listing each switch’s serial number with the desired member ID and role:
   [edit virtual-chassis]
user@switch# set member 0 serial-number abc123 role routing-engine
user@switch# set member 1 serial-number def456 role routing-engine
user@switch# set member 2 serial-number ghi789 role line-card
user@switch# set member 3 serial-number jkl012 role line-card


8. (Optional. Recommended for a two-member Virtual Chassis) Disable the split and merge feature:
   [edit virtual-chassis]
user@switch# set no-split-detection


9. Power on the other member switches. The member IDs and roles have been determined by the configuration, so you can power on the member switches in any order.
10. On each individual member switch, configure the ports that will be used to interconnect the EX2200 member switches into VCPs.

    You can configure a port on an EX2200 switch as a VCP using the following command:

    
user@switch> request virtual-chassis vc-port set pic-slot pic-slot-number port port-number

    where pic-slot-number is the PIC slot number. The PIC slot number is 0 when you are configuring a built-in port as a VCP and 1 when you are configuring an uplink port as a VCP.

    For instance, if you wanted to set built-in port 20 as a VCP:

    
user@switch> request virtual-chassis vc-port set pic-slot 0 port 20

    If you wanted to set uplink port 2 as a VCP:

    
user@switch> request virtual-chassis vc-port set pic-slot 1 port 2

    The VCPs automatically bundle into a Link Aggregation Group when two or more interfaces are configured into VCPs between the same two member switches. See Understanding EX Series Virtual Chassis Port Link Aggregation.

Note: You cannot modify the mastership priority when you are using a preprovisioned configuration. The mastership priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file. The two Routing Engines are assigned the same mastership priority value. However, the member that was powered on first has higher prioritization according to the master election algorithm. See Understanding How the Master in a Virtual Chassis Is Elected.

Configuring an EX2200 Virtual Chassis with a Nonprovisioned Configuration File

You can use nonprovisioned configuration to configure an EX2200 Virtual Chassis.

To configure the Virtual Chassis using a nonprovisioned configuration:

Note: We recommend that you physically cable the ports as the final step of this procedure. You can, however, configure an EX2200 Virtual Chassis while the cables are physically connected.

1. Power on only the switch that you plan to use as the master switch.
2. Run the EZSetup program on the master switch, specifying the identification parameters. See Connecting and Configuring an EX Series Switch (CLI Procedure) for details.

   Note: The properties that you specify for the master switch apply to the entire Virtual Chassis configuration.

3. (Optional) Configure the master switch with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis:
   [edit]
user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/
4. (Optional) Configure mastership priority for the other member switches:
   [edit virtual-chassis]
user@switch# set member 0 mastership-priority 255
user@switch# set member 1 mastership-priority 255

5. (Optional. Recommended for a two-member Virtual Chassis) On the master switch, disable the split and merge feature:
   [edit virtual-chassis]
user@switch# set no-split-detection

6. Power on the other member switches.
7. On each individual member switch, configure the ports that will be used to interconnect the EX2200 member switches into VCPs.

   You can configure a port on an EX2200 switch as a VCP using the following command:

   
user@switch> request virtual-chassis vc-port set pic-slot pic-slot-number port port-number

   where pic-slot-number is the PIC slot number. The PIC slot number is 0 when you are configuring a built-in port as a VCP and 1 when you are configuring an uplink port as a VCP.

   For instance, if you wanted to set built-in port 20 as a VCP:

   
user@switch> request virtual-chassis vc-port set pic-slot 0 port 20

   If you wanted to set uplink port 2 as a VCP:

   
user@switch> request virtual-chassis vc-port set pic-slot 1 port 2

   The VCPs automatically bundle into a Link Aggregation Group when two or more interfaces are configured into VCPs between the same two member switches. See Understanding EX Series Virtual Chassis Port Link Aggregation.

Note: If you do not edit the Virtual Chassis configuration file, a nonprovisioned configuration is generated by default. The mastership priority value for each member switch is 128. The master role is selected by default. You can change the role that is performed by the members by modifying the mastership priority. See Configuring Mastership of a Virtual Chassis (CLI Procedure). We recommend that you specify the same mastership priority value for the desired master and backup members. In this example, the highest possible mastership priority has been assigned to two members. However, the member that was powered on first has higher prioritization according to the master election algorithm. See Understanding How the Master in a Virtual Chassis Is Elected. The other members use the default mastership priority in this example, which configures them to function in the role of linecard.

Note: If you want to change the member ID that the master has assigned to a member switch, use the request virtual-chassis renumber command.