----------------------------------------
A QFX Series Virtual Chassis is a flexible, scaling switch solution for supported combinations of QFX3500, QFX3600, QFX5100, and QFX5110 switches. EX4300 switches can also be included in some configurations of a QFX Series Virtual Chassis..
In a QFX Series Virtual Chassis, you can interconnect up to ten standalone switches in the following
combinations into one logical device, and manage the logical device as a single chassis:
QFX5110 switches or a combination of QFX5110 and QFX5100 switches (a non-mixed Virtual Chassis)
QFX5100 switches (a non-mixed Virtual Chassis)
QFX5100 switches with any combination of QFX3500, QFX3600, or EX4300 switches (a mixed mode Virtual Chassis)
QFX3500 switches or QFX3600 switches, or a combination of QFX3500 and QFX3600 switches (a non-mixed Virtual Chassis)
QFX3500 or QFX3600 switches with EX4300 switches, or a combination of all three types of switches (a mixed mode Virtual Chassis)
The advantages of connecting multiple switches into a Virtual Chassis include better-managed bandwidth at a network layer, simplified configuration and maintenance because multiple devices can be managed as a single device, increased fault tolerance and high availability(HA) because a Virtual Chassis can remain active and network traffic can be redirected to other member switches when a single member switch fails, and a flatter, simplified Layer 2 network topology that minimizes or eliminates the need for loop prevention protocols such as Spanning Tree Protocol (STP).
You set up a Virtual Chassis by configuring Virtual Chassis ports (VCPs) on the member switches, and interconnecting the switches using the VCPs . VCPs are responsible for passing all data and control traffic between member switches in the Virtual Chassis. The following ports on QFX Series switches that support Virtual Chassis can be configured into VCPs to form a QFX Series Virtual Chassis:
Any 100-Gbps or 40-Gbps QSFP28 ports on QFX5110 switches
Any non-channelized 40-Gbps QSFP+ ports on QFX3500, QFX3600, QFX5100, or QFX5110 switches
Any fixed 10-Gbps SFP+ ports on QFX Series switches with these ports
You can increase VCP bandwidth between member switches by configuring multiple interfaces between the same two switches into VCPs. When multiple VCPs interconnect the same two member switches, a Link Aggregation Group (LAG) or bundle is automatically formed when the VCPs are on interfaces supporting identical speeds. For example, if you have two 40-Gbps QSFP+ interfaces configured as VCPs between member switches, a LAG with two member links with 80Gbps of total bandwidth is formed. However, 10-Gbps SFP+ and 40-Gbps QSFP+ interfaces configured as VCPs
will not become members of the same VCP LAG.
----------------------------------
Before configuration note
----------------------------------
1. IF the new member switch is running a version of Junos OS that is different than the version of
Junos OS running on the Virtual Chassis, then ensure that the correct version of Junos OS is or
will be installed on the new member switch by performing software update or automatic software update enable.
root> request system software add ftp://ip address/jinstall-qfx-5-14.1X53-D42.3-domestic-signed.tgz no-validate no-copy
user@device# set virtual-chassis auto-sw-update package-name ftp://hostname/pathname/package-name
--------------------------------------------------------------------------------------------------------------------------
Configuring a QFX5100 two-member Virtual Chassis with a Preprovisioned Configuration File:
--------------------------------------------------------------------------------------------------------------------------
1.Make a list of the serial numbers of all the switches to be connected in a
Virtual Chassis configuration.
S/N: TR02171XXXXX
S/N: TR021712XXXX
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 with S/N: TR02171XXXXX that you plan to use as the master switch.
-------------------------------------------------
For SW with S/N: TR02171XXXXX
-------------------------------------------------
4.After the reboot is complete, specify the preprovisioned configuration mode:
[edit virtual-chassis]
user@switch# set preprovisioned
5.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 TR02171XXXXX role routing-engine
user@switch# set member 1 serial-number TR021712XXXX role routing-engine
6.(Recommended for a two-member Virtual Chassis) Disable the split and merge
feature:
[edit virtual-chassis]
user@switch# set no-split-detection
-------------------------------------------------
For SW with S/N: TR021712XXXX
-------------------------------------------------
7. Power on only the switch with S/N: TR021712XXXX that you plan to use as the Backup switch.
After the boot 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 TR02171XXXXX role routing-engine
user@switch# set member 1 serial-number TR021712XXXX role routing-engine
9.(Recommended for a two-member Virtual Chassis) Disable the split and merge
feature:
[edit virtual-chassis]
user@switch# set no-split-detection
10.Finaly connect the qsfp+ cable to the et-0/0/53 for both switch according to the picture.
N.B. Now wait for 5 mintues. Changing any configuration from master sw do "commit synchronous" command.
-------------------
Verifying VC:
-------------------
##From SW with S/N: TR02171XXXXX
root> show virtual-chassis
Preprovisioned Virtual Chassis
Virtual Chassis ID: 9b18.70fb.c786
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Prsnt TR02171XXXXX qfx5100-48t-6q 129 Master* N VC 1 vcp-255/0/53
1 (FPC 1) Prsnt TR021712XXXX qfx5100-48t-6q 129 Backup N VC 0 vcp-255/0/53
##From SW with S/N: TR021712XXXX
root> show virtual-chassis
Preprovisioned Virtual Chassis
Virtual Chassis ID: 9b18.70fb.c786
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Prsnt TR02171XXXXX qfx5100-48t-6q 129 Master* N VC 1 vcp-255/0/53
1 (FPC 1) Prsnt TR021712XXXX qfx5100-48t-6q 129 Backup N VC 0 vcp-255/0/53
------------------------------------------------------------------
login to the member switch of the Virtual Chassis:
------------------------------------------------------------------
root>request session member <member-id>
>>>Here member ID '0' is for master and '1' for Backup<<<
------------------------------------------------------------
Mastership switching of the Virtual Chassis:
------------------------------------------------------------
{master:member0-re0}
root> request virtual-chassis routing-engine master switch
Do you want to continue ? [yes,no] (no)yes
{backup:member0-re0}
root>
NOTE:Before you issue the request virtual-chassis routing-engine master switch command from the master router or switch in the Virtual Chassis, make sure that the system configuration is synchronized between the master and backup router or switch. If the configuration is not synchronized, or if you attempt to issue the request virtual-chassis routing-engine master switch command from the backup router or switch instead of from the master router or switch, the device displays an error message and rejects the command.If you issue the request virtual-chassis routing-engine master switch command when the Virtual Chassis is in a transition state (for example, the backup router or switch is disconnecting from the Virtual Chassis),
the device does not process the command.
