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

Adding a Device to a Virtual Chassis Fabric

Adding a Leaf Device to an Autoprovisioned Virtual Chassis Fabric

Update your device to the same version of Junos OS running on the devices in the VCF. See Upgrading Software or Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

1. Log onto the device that you are adding to the VCF.
2. (Optional) Perform this step if you want to avoid the downtime associated with an extra reboot when your device is interconnected into your VCF. If you do not perform this step, the VCF auto-detects the fabric and mixed mode settings and, if needed, reboots the device as part of the process of changing these settings.

   Configure the leaf device into fabric mode. Configure your device into mixed mode if your VCF includes QFX3600, QFX3500, or EX4300 devices as leaf devices..

   If you are configuring a VCF composed entirely of QFX5100 devices:

   user@device> request virtual-chassis mode fabric local


   If you are configuring a VCF composed of two or more types of devices:

   user@device> request virtual-chassis mode fabric mixed local

3. If the leaf device that you are adding to the VCF has not previously been configured, proceed to the next step.

   If your device has been configured, zeroize your device and reboot:

   user@device> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files? [yes,no] (yes) yes

   Note: You must zeroize your device if you have previously entered one or more configuration commands, including basic configuration commands. Your device will not join the VCF if it contains any configuration until it has been zeroized.

   Note: The request virtual-chassis mode fabric local and request virtual-chassis mode fabric mixed local commands are entered in operational mode, so those settings are maintained when the device is zeroized.

   You cannot use other methods to set a device into factory default mode before inserting it into a VCF if it was previously configured in another Virtual Chassis or VCF. You must use request system zeroize.

   For additional information on this procedure, see Reverting to the Default Factory Configuration for the EX Series Switch or Reverting to the Default Factory Configuration.

4. (Required only if you are adding a device that turns a non-mixed VCF into a mixed VCF) Log in to the VCF and set all devices in the VCF to mixed mode, Configure all devices to reboot to complete this procedure.
   user@device> request virtual-chassis mode mixed all-members reboot


   The VCF experiences downtime as part of the reboot procedure.

5. Interconnect your leaf device into the existing spine devices, using at least one 10-Gbps SFP+ interface or 40-Gbps QSFP+ interface to connect to each spine device in the VCF.

   An autoprovisioned VCF automatically adds a supported device in factory-default mode to the VCF when it is connected to a spine devices using a supported SFP+ or QSFP+ link. The SFP+ or QSFP+ link is automatically converted into a Virtual Chassis port (VCP) as part of this process.

   No further configuration is required.

Adding a Spine Device to an Autoprovisioned Virtual Chassis Fabric

Update your device to the same version of Junos OS running on the devices in the VCF before interconnecting it into the VCF. See Upgrading Software or Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

1. Log in to your VCF.
2. If you are replacing a spine device that is already part of the VCF, power off the spine device in the VCF.

   Follow the steps in Removing a Device From a Virtual Chassis Fabric to remove the device from the VCF.

3. Modify the configuration.

   If your new spine device is replacing an existing spine, modify the configuration to remove the old spine.

   You can skip this step if you are not replacing an existing spine device.

   [edit virtual-chassis]
user@device# delete member member-id


   where member-id is the member ID of the spine that is removed from this procedure.

   Add the spine device to the configuration:

   [edit virtual-chassis]
user@device# set member member-id serial-number serial-number role [line-card | routing-engine]

   For instance, to configure a spine device acting in the linecard role with the serial number OU81234567890 as member 3:

   [edit virtual-chassis]
user@device# set member 3 serial-number OU81234567890 role line-card


4. Commit the configuration.
   [edit]
user@device# commit
5. Log in to the device that is going to be added to the VCF.
6. Configure the device into fabric mode. If needed, also configure the device into mixed mode.

   Reboot the device to complete this configuration step.

   If you are configuring a VCF composed entirely of QFX5100 devices:

   user@device> request virtual-chassis mode fabric local reboot


   If you are configuring a VCF composed of QFX5100 devices and at least one other type of device:

   user@device> request virtual-chassis mode fabric mixed local reboot


   Note: We recommend setting the fabric and mixed mode settings before interconnecting your devices into a VCF to avoid the following issues: Incurring downtime as the devices reboot to commit the mixed mode or fabric settings. Manually correcting potential issues related to VCF formation because the device did not immediately join the VCF. You can, however, use the request virtual-chassis mode fabric local or request virtual-chassis mode mixed local commands to set a device into fabric or mixed mode after interconnecting your VCF.

7. (Required only if you are adding a device that turns a non-mixed VCF into a mixed VCF) Log in to the VCF and set all devices in the VCF to mixed mode, Configure all devices to reboot to complete this procedure.
   user@device> request virtual-chassis mode mixed all-members reboot


   The VCF experiences downtime as part of the reboot procedure.

8. After the device reboots, interconnect the new device into the VCF by cabling the device to the leaf devices in the VCF using supported SFP+ or QSFP+ interfaces.

   The SFP+ or QSFP+ links are converted into VCPs automatically.

   The new spine device should be operational once the cabling is complete.

Adding a Spine or Leaf Device to a Preprovisioned Virtual Chassis Fabric

Update your device to the same version of Junos OS running on the devices in the VCF before interconnecting it into the VCF. See Upgrading Software or Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

1. Log in to your VCF.
2. If you are replacing a device that is already part of the VCF, power off the device in the VCF.

   Follow the steps in Removing a Device From a Virtual Chassis Fabric to remove the device from the VCF.

3. Modify the configuration.

   If your new device is replacing an existing device, modify the configuration to remove the old device.

   You can skip this portion of the procedure if you are not replacing an existing device.

   [edit virtual-chassis]
user@device# delete member member-id


   where member-id is the member ID of the spine that is removed from this procedure.

   Add the new device to the configuration:

   [edit virtual-chassis]
user@device# set member member-id serial-number serial-number role [line-card | routing-engine]

   For instance, to configure a device with the serial number OU81234567890 into the Routine Engine role as member 3:

   [edit virtual-chassis]
user@device# set member 3 serial-number OU81234567890 role routing-engine


4. Commit the configuration.
   [edit]
user@device# commit
5. Log in to the device that is going to be added to the VCF.
6. Configure the device into fabric mode. If needed, also configure the device into mixed mode.

   Reboot the device to complete this configuration step.

   If you are configuring a VCF composed entirely of QFX5100 devices:

   user@device> request virtual-chassis mode fabric local reboot


   If you are configuring a VCF composed of two or more types of devices:

   user@device> request virtual-chassis mode fabric mixed local reboot


   Note: If you are adding a QFX3600, QFX3500, or EX4300 device to a VCF that is composed entirely of QFX5100 devices, you must also log in to the VCF and set all of the devices in the VCF into mixed mode. Log in to the VCF and enter the request virtual-chassis mode mixed all-members reboot command to perform this task. The VCF reboots and incurs downtime to complete this procedure.

   Note: We recommend that you set the fabric and mixed mode settings before you interconnect your devices into a VCF to avoid the following issues: Incurring downtime as the devices reboot to commit the mixed mode or fabric settings. Manually correcting potential issues related to VCF formation because the device did not immediately join the VCF. You can, however, use the request virtual-chassis mode fabric local or request virtual-chassis mode mixed local commands to recover a device that was not set into fabric or mixed mode before you interconnect it into your VCF.

7. (Required only if you are adding a device that turns a non-mixed VCF into a mixed VCF) Log in to the VCF and set all devices in the VCF to mixed mode, Configure all devices to reboot to complete this procedure.
   user@device> request virtual-chassis mode mixed all-members reboot


   The VCF experiences downtime as part of the reboot procedure.

8. After the device reboots, interconnect the new device into the VCF using supported SFP+ or QSFP+ interfaces.

   The SFP+ or QSFP+ links are converted into VCPs automatically.

   The new device should be operational shortly after the cabling is complete.

Adding a Spine or Leaf Device to a Nonprovisioned Virtual Chassis Fabric

Caution: Configure your VCF using autoprovisioning or preprovisioning unless you have a compelling reason to use nonprovisioned configuration. You can configure all aspects of a VCF using autoprovisioned or preprovisioned configuration. Nonprovisioned VCF configuration is highly discouraged. Nonprovisioned VCF configuration should only be used by VCF experts in specialized scenarios.

Update your device to the same version of Junos OS running on the devices in the VCF before interconnecting it into the VCF. See Upgrading Software or Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

1. Log in to your VCF.
2. If you are replacing a device that is already part of the VCF, power off the device in the VCF. Uncable the device once the power off is complete.

   You can skip this step if you are adding a new device without replacing an existing device. You must skip this step if there is no configuration for the device that you are removing from the VCF.

   If the device is configured, delete the device from the VCF configuration:

   [edit virtual-chassis]
user@device# delete member member-id


   where member-id is the member ID of the device that you are removing.

3. Log in to the device that you are going to add to the VCF.
4. Configure the device into fabric mode. If needed, also configure the device into mixed mode.

   Reboot the device to complete this configuration step.

   If you are configuring a VCF composed entirely of QFX5100 devices:

   user@device> request virtual-chassis mode fabric local reboot


   If you are configuring a VCF that includes at least one QFX3600, QFX3500, or EX4300 devices as a leaf device:

   user@device> request virtual-chassis mode fabric mixed local reboot


   Note: If you are adding a QFX3600, QFX3500, or EX4300 device to a VCF that is composed entirely of QFX5100 devices, you must also log in to the VCF and set all of the devices in the VCF into mixed mode. Log in to the VCF and enter the request virtual-chassis mode mixed all-members reboot command to perform this task. The VCF reboots and incurs downtime to complete this procedure.

   Note: We recommend that you set the fabric and mixed mode settings before you interconnect your devices into a VCF to avoid the following issues: Incurring downtime as the devices reboot to commit the mixed mode or fabric settings. Manually correcting potential issues related to VCF formation because the device did not immediately join the VCF. You can, however, use the request virtual-chassis mode fabric local or request virtual-chassis mode mixed local commands to set a device into fabric or mixed mode after interconnecting your VCF.

5. (Required only if you are adding a device that turns a non-mixed VCF into a mixed VCF) Log in to the VCF and set all devices in the VCF to mixed mode, Configure all devices to reboot to complete this procedure.
   user@device> request virtual-chassis mode mixed all-members reboot


   The VCF experiences downtime as part of the reboot procedure.

6. After the device reboots, interconnect it into the VCF using supported SFP+ or QSFP+ interfaces.
7. Configure the SFP+ or QSFP+ interfaces into Virtual Chassis ports (VCPs):
   user@device> request virtual-chassis vc-port set pic-slot pic-slot-number port port-number

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

   The request virtual-chassis vc-port must be configured on the ports at both ends of the link in order for that link to be configured into a VCP.

8. (Optional) Log in to the VCF and set the mastership priority of the new device:
   [edit virtual-chassis]
user@device# set member member-id mastership-priority number

   If needed, enter the show virtual-chassis command to learn the member ID of the new member device in the VCF.