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 a QFX Series Virtual Chassis (CLI Procedure)

This topic discusses configuring a QFX Series Virtual Chassis only. It does not apply to configuring a Virtual Chassis Fabric (VCF). For information on configuring a VCF, see Understanding Virtual Chassis Fabric Configuration.

You configure a QFX Series Virtual Chassis—a Virtual Chassis composed of QFX3500 standalone switches, QFX3600 standalone switches, QFX5100 standalone switches, or a combination of the three—by configuring 10-Gbps SFP+ or 40-Gbps QSFP+ interfaces connecting the member switches into Virtual Chassis ports (VCPs). EX4300 switches can also be included in a Virtual Chassis with QFX3500, QFX3600, and QFX5100 switches. All non-channelized QSFP+ uplink interfaces on standalone QFX series switches can be configured into VCPs. All fixed SFP+ and QSFP+ interfaces on can also be configured into VCPs.

A Virtual Chassis can only be configured on a QFX series device configured in standalone mode. The Junos OS image that supports Virtual Chassis—the Junos OS images that support Virtual Chassis include the “jinstall-qfx-3-” text in the filename when the Junos OS image is downloaded from the Software Center—for standalone switches must be downloaded on QFX3500 or QFX3600 switches in order for the member switches to be part of a Virtual Chassis. For QFX5100 switches, you must download the software image for the standalone switch.

A QFX Series 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 to both switches acting as Routing Engines.

Note: In Junos OS release 13.2X51-D20, you can interconnect up to ten QFX5100 switches into a Virtual Chassis with the exception of the QFX5100-96S switch, which you could configure into a non-mixed Virtual Chassis that included up to four QFX5100-96S switches only. You can configure up to ten QFX5100-96S switches into a mixed or non-mixed Virtual Chassis starting in Junos OS release 13.2X51-D25.

Be sure that all switches that are interconnected into a Virtual Chassis are running the same version of Junos OS. See Upgrading Software.

This topic includes:

• Configuring a QFX Series Virtual Chassis with a Preprovisioned Configuration File
• Configuring a QFX Series Virtual Chassis with a Nonprovisioned Configuration File

Configuring a QFX Series 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: You can configure a QFX Series Virtual Chassis while the cables are or are not 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. Specify the identification parameters for the switch by completing the initial configuration. See Configuring a QFX3500 Device as a Standalone Switch or Configuring a QFX3600 Device as a Standalone Switch, or Configuring a QFX5100 Device.

   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:
   user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/
6. (Required for a mixed Virtual Chassis only) Set the master switch into mixed mode, and reboot the switch to complete the configuration:

   Note: You do not have to complete this step if you are configuring a Virtual Chassis that includes QFX3500 and QFX3600 switches only. You must complete this step if your Virtual Chassis includes a mix of QFX5100, EX4300, and QFX3500 or QFX3600 switches.

   user@device> request virtual-chassis mode mixed reboot

7. After the reboot is complete, specify the preprovisioned configuration mode:
   [edit virtual-chassis]
user@switch# set preprovisioned

8. 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


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


10. 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.
11. (Required if you are configuring a mixed Virtual Chassis) Set each individual switch into mixed mode, and reboot the switch to complete the configuration:

    Note: You do not have to complete this step if you are configuring a Virtual Chassis that includes QFX3500 and QFX3600 switches only. You must complete this step if your Virtual Chassis includes a mix of QFX5100, EX4300, and QFX3500 or QFX3600 switches.

    user@device> request virtual-chassis mode mixed reboot


12. (Optional) On each individual member switch, configure the ports that will be used to interconnect the member switches into VCPs using the following command:

    Note: SFP+, QSFP+, and 10Gbps copper links are automatically turned into VCPs when the preprovisioned configuration is set. This step is, therefore, optional and should only be used when a VCP is not automatically created.

    
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.

    For instance, if you wanted to set port 0 on the QSFP+ interface on PIC slot 2 as a VCP:

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

    The VCPs automatically bundle into a Link Aggregation Group when two or more interfaces of the same speed 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 a QFX Series Virtual Chassis with a Nonprovisioned Configuration File

You can use nonprovisioned configuration to configure a QFX Series Virtual Chassis.

To configure the Virtual Chassis using a nonprovisioned configuration:

Note: You can configure a QFX Series Virtual Chassis while the cables are or are not physically connected.

1. Power on only the switch that you plan to use as the master switch.
2. (Required for a mixed Virtual Chassis only) Set the master switch into mixed mode, and reboot the switch to complete the configuration:

   Note: You do not have to complete this step if you are configuring a Virtual Chassis that includes QFX3500 and QFX3600 switches only. You must complete this step if your Virtual Chassis includes a mix of QFX5100, EX4300, and QFX3500 or QFX3600 switches.

   user@device> request virtual-chassis mode mixed reboot

3. After the master switch reboots, specify the identification parameters for the switch by completing the initial configuration. See Configuring a QFX3500 Device as a Standalone Switch or Configuring a QFX3600 Device as a Standalone Switch for details.

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

4. (Optional) Configure the master switch with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis:
   user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/
5. (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

6. (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

7. Power on the other member switches.
8. (Required for a mixed Virtual Chassis only) Set each individual switch into mixed mode, and reboot the switch to complete the configuration:

   Note: You do not have to complete this step if you are configuring a Virtual Chassis that includes QFX3500 and QFX3600 switches only. You must complete this step if your Virtual Chassis includes a mix of QFX5100, EX4300, and QFX3500 or QFX3600 switches.

   user@device> request virtual-chassis mode mixed reboot


9. On each individual member switch, configure the ports that will be used to interconnect the member switches into VCPs 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.

   For instance, if you wanted to set port 0 on the QSFP+ interface on PIC slot 2 as a VCP:

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

   The VCPs automatically bundle into a Link Aggregation Group when two or more interfaces of the same speed 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.