Related Documentation
- EX Series
- Installing and Connecting an EX4200 Switch
- Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
- QFabric System
- QFX3000-G QFabric System Installation Overview
- Installing and Connecting a QFX3100 Director Device
- Installing and Connecting a QFX3008-I Interconnect Device
- Installing and Connecting a QFX3500 Device
- Installing and Connecting a QFX3600 or QFX3600-I Device
- Understanding the QFabric System Control Plane
- QFX Series standalone switches
- Installing and Connecting a QFX3500 Device
- Installing and Connecting a QFX3600 or QFX3600-I Device
Example: Configuring a Fiber-Based Control Plane for the QFX3000-G QFabric System
This example shows you how to connect components and configure switches used by a fiber-based QFX3000-G QFabric system control plane network. Proper wiring of Director devices, Interconnect devices, and Node devices to the control plane switches, combined with a standard configuration, enables you to bring up the internal QFabric system management network and prepare your QFabric system for full operation.
Requirements
This example uses the following hardware and software components:
- One QFX3000-G QFabric system containing:
- Two QFX3100 Director devices
- Two QFX3008-I Interconnect devices
- Eight QFX3500 Node devices
- Sixteen EX4200-24F switches, used to make two redundant Virtual Chassis with eight members apiece
- Junos OS Release 12.3R6.6 for the EX Series switches used in the Virtual Chassis
- Junos OS Release 13.2X52-D10 for the QFabric system devices
Before you begin:
- Rack, mount, and install your QFabric system hardware (Director group, Interconnect devices, and Node devices). For more information, see Installing and Connecting a QFX3100 Director Device, Installing and Connecting a QFX3008-I Interconnect Device, Installing and Connecting a QFX3500 Device, and Installing and Connecting a QFX3600 or QFX3600-I Device.
- Rack, mount, and install your Virtual Chassis hardware (EX4200 switches). For more information, see Installing and Connecting an EX4200 Switch.
- Create two Virtual Chassis of eight members each. For more information, see Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure).
Overview
The QFX3000-G QFabric system control plane network connects the Director group, Interconnect devices, and Node devices in a QFabric system across a pair of redundant Virtual Chassis. By separating the management control plane from the data plane, the QFabric system can scale efficiently. The control plane network uses Gigabit Ethernet cabling and connections between components, and a 10-Gigabit Ethernet backbone between the redundant Virtual Chassis.
Specific ports have been reserved on the Virtual Chassis to connect to each of the QFabric system device types. Such design simplifies installation and facilitates timely deployment of a QFabric system. It also permits the use of a standard Virtual Chassis configuration included as part of this example. The standard configuration can scale from the minimum topology of eight Node devices shown in this example to the maximum topology of 128 Node devices for a fully implemented QFX3000-G QFabric system.
Topology
Figure 1 shows the general port ranges where QFabric system devices must be connected to the Virtual Chassis. For each Virtual Chassis member, connect ports 0 through 15 to Node devices, ports 18 through 21 to Interconnect devices, and ports 22 and 23 to Director devices. Table 1 shows the details of the QFabric system device-to-Virtual Chassis port mappings for a fiber-based control plane network.
Figure 1: QFX3000-G QFabric System Fiber-Based Control Plane—Virtual Chassis Port Ranges

![]() | Caution:
|
![]() | Note: Not all port numbers are represented in Table 1, and ports 16 and 17 are reserved for future uses. |
Table 1 shows the specific mappings of QFabric system control plane network ports from the Virtual Chassis to the QFabric system components.
Table 1: QFX3000-G QFabric System Virtual Chassis Fiber-Based Control Plane Port Assignments
Member 0 | Member 1 | Member 2 | Member 3 | Member 4 | Member 5 | Member 6 | Member 7 | Member Port Number | QFabric System Component |
|---|---|---|---|---|---|---|---|---|---|
Node0 ge-0/0/0 | Node16 ge-1/0/0 | Node32 ge-2/0/0 | Node48 ge-3/0/0 | Node64 ge-4/0/0 | Node80 ge-5/0/0 | Node96 ge-6/0/0 | Node112 ge-7/0/0 | ge-X/0/0 | Node devices |
Node1 ge-0/0/1 | Node17 ge-1/0/1 | Node33 ge-2/0/1 | Node49 ge-3/0/1 | Node65 ge-4/0/1 | Node81 ge-5/0/1 | Node97 ge-6/0/1 | Node113 ge-7/0/1 | ge-X/0/1 | Node devices |
Node2 ge-0/0/2 | Node18 ge-1/0/2 | Node34 ge-2/0/2 | Node50 ge-3/0/2 | Node66 ge-4/0/2 | Node82 ge-5/0/2 | Node98 ge-6/0/2 | Node114 ge-7/0/2 | ge-X/0/2 | Node devices |
Node3 ge-0/0/3 | Node19 ge-1/0/3 | Node35 ge-2/0/3 | Node51 ge-3/0/3 | Node67 ge-4/0/3 | Node83 ge-5/0/3 | Node99 ge-6/0/3 | Node115 ge-7/0/3 | ge-X/0/3 | Node devices |
Node4 ge-0/0/4 | Node20 ge-1/0/4 | Node36 ge-2/0/4 | Node52 ge-3/0/4 | Node68 ge-4/0/4 | Node84 ge-5/0/4 | Node100 ge-6/0/4 | Node116 ge-7/0/4 | ge-X/0/4 | Node devices |
Node5 ge-0/0/5 | Node21 ge-1/0/5 | Node37 ge-2/0/5 | Node53 ge-3/0/5 | Node69 ge-4/0/5 | Node85 ge-5/0/5 | Node101 ge-6/0/5 | Node117 ge-7/0/5 | ge-X/0/5 | Node devices |
Node6 ge-0/0/6 | Node22 ge-1/0/6 | Node38 ge-2/0/6 | Node54 ge-3/0/6 | Node70 ge-4/0/6 | Node86 ge-5/0/6 | Node102 ge-6/0/6 | Node118 ge-7/0/6 | ge-X/0/6 | Node devices |
Node7 ge-0/0/7 | Node23 ge-1/0/7 | Node39 ge-2/0/7 | Node55 ge-3/0/7 | Node71 ge-4/0/7 | Node87 ge-5/0/7 | Node103 ge-6/0/7 | Node119 ge-7/0/7 | ge-X/0/7 | Node devices |
Node8 ge-0/0/8 | Node24 ge-1/0/8 | Node40 ge-2/0/8 | Node56 ge-3/0/8 | Node72 ge-4/0/8 | Node88 ge-5/0/8 | Node104 ge-6/0/8 | Node120 ge-7/0/8 | ge-X/0/8 | Node devices |
Node9 ge-0/0/9 | Node25 ge-1/0/9 | Node41 ge-2/0/9 | Node57 ge-3/0/9 | Node73 ge-4/0/9 | Node89 ge-5/0/9 | Node105 ge-6/0/9 | Node121 ge-7/0/9 | ge-X/0/9 | Node devices |
Node10 ge-0/0/10 | Node26 ge-1/0/10 | Node42 ge-2/0/10 | Node58 ge-3/0/10 | Node74 ge-4/0/10 | Node90 ge-5/0/10 | Node106 ge-6/0/10 | Node122 ge-7/0/10 | ge-X/0/10 | Node devices |
Node11 ge-0/0/11 | Node27 ge-1/0/11 | Node43 ge-2/0/11 | Node59 ge-3/0/11 | Node75 ge-4/0/11 | Node91 ge-5/0/11 | Node107 ge-6/0/11 | Node123 ge-7/0/11 | ge-X/0/11 | Node devices |
Node12 ge-0/0/12 | Node28 ge-1/0/12 | Node44 ge-2/0/12 | Node60 ge-3/0/12 | Node76 ge-4/0/12 | Node92 ge-5/0/12 | Node108 ge-6/0/12 | Node124 ge-7/0/12 | ge-X/0/12 | Node devices |
Node13 ge-0/0/13 | Node29 ge-1/0/13 | Node45 ge-2/0/13 | Node61 ge-3/0/13 | Node77 ge-4/0/13 | Node93 ge-5/0/13 | Node109 ge-6/0/13 | Node125 ge-7/0/13 | ge-X/0/13 | Node devices |
Node14 ge-0/0/14 | Node30 ge-1/0/14 | Node46 ge-2/0/14 | Node62 ge-3/0/14 | Node78 ge-4/0/14 | Node94 ge-5/0/14 | Node110 ge-6/0/14 | Node126 ge-7/0/14 | ge-X/0/14 | Node devices |
Node15 ge-0/0/15 | Node31 ge-1/0/15 | Node47 ge-2/0/15 | Node63 ge-3/0/15 | Node79 ge-4/0/15 | Node95 ge-5/0/15 | Node111 ge-6/0/15 | Node127 ge-7/0/15 | ge-X/0/15 | Node devices |
Reserved ge-0/0/16 | Reserved ge-1/0/16 | Reserved ge-2/0/16 | Reserved ge-3/0/16 | Reserved ge-4/0/16 | Reserved ge-5/0/16 | Reserved ge-6/0/16 | Reserved ge-7/0/16 | ge-X/0/16 | Future use |
Reserved ge-0/0/17 | Reserved ge-1/0/17 | Reserved ge-2/0/17 | Reserved ge-3/0/17 | Reserved ge-4/0/17 | Reserved ge-5/0/17 | Reserved ge-6/0/17 | Reserved ge-7/0/17 | ge-X/0/17 | Future use |
IC2 CB0 ge-0/0/18 | IC2 CB1 ge-1/0/18 | IC3 CB0 ge-2/0/18 | IC3 CB1 ge-3/0/18 | Reserved ge-4/0/18 | Reserved ge-5/0/18 | Reserved ge-6/0/18 | Reserved ge-7/0/18 | ge-X/0/18 | Interconnect devices Note: On both Control Boards, use port 0 to connect to VC0, and port 1 to connect to VC1. |
IC0 CB0 ge-0/0/19 | IC0 CB1 ge-1/0/19 | IC1 CB0 ge-2/0/19 | IC1 CB1 ge-3/0/19 | Reserved ge-4/0/19 | Reserved ge-5/0/19 | Reserved ge-6/0/19 | Reserved ge-7/0/19 | ge-X/0/19 | Interconnect devices Note: On both Control Boards, use port 0 to connect to VC0, and port 1 to connect to VC1. |
Reserved ge-0/0/20 | Reserved ge-1/0/20 | Reserved ge-2/0/20 | Reserved ge-3/0/20 | Reserved ge-4/0/20 | Reserved ge-5/0/20 | Reserved ge-6/0/20 | Reserved ge-7/0/20 | ge-X/0/20 | Interconnect devices |
Reserved ge-0/0/21 | Reserved ge-1/0/21 | Reserved ge-2/0/21 | Reserved ge-3/0/21 | Reserved ge-4/0/21 | Reserved ge-5/0/21 | Reserved ge-6/0/21 | Reserved ge-7/0/21 | ge-X/0/21 | Interconnect devices |
DG0 port 0 ge-0/0/22 | DG0 port 1 ge-1/0/22 | DG0 port 2 ge-2/0/22 | Reserved ge-3/0/22 | Reserved ge-4/0/22 | Reserved ge-5/0/22 | Reserved ge-6/0/22 | Reserved ge-7/0/22 | ge-X/0/22 | Director device 0 |
DG1 port 0 ge-0/0/23 | DG1 port 1 ge-1/0/23 | DG1 port 2 ge-2/0/23 | Reserved ge-3/0/23 | Reserved ge-4/0/23 | Reserved ge-5/0/23 | Reserved ge-6/0/23 | Reserved ge-7/0/23 | ge-X/0/23 | Director device 1 |
Inter-VC xe-0/1/0 | Inter-VC xe-1/1/0 | Inter-VC xe-2/1/0 | Inter-VC xe-3/1/0 | Inter-VC xe-4/1/0 | Inter-VC xe-5/1/0 | Inter-VC xe-6/1/0 | Inter-VC xe-7/1/0 | Inter-VC xe-X/1/0 | Inter-Virtual Chassis LAG |
Inter-VC xe-0/1/2 | Inter-VC xe-1/1/2 | Inter-VC xe-2/1/2 | Inter-VC xe-3/1/2 | Inter-VC xe-4/1/2 | Inter-VC xe-5/1/2 | Inter-VC xe-6/1/2 | Inter-VC xe-7/1/2 | Inter-VC xe-X/1/2 | Inter-Virtual Chassis LAG |
Next, connect the Director devices to the Virtual Chassis. In general, you want to accomplish the following:
- Connect three ports from one network module in a Director device to the first Virtual Chassis, and three ports from the second network module to the second Virtual Chassis. You need to repeat these connections from the second Director device to both Virtual Chassis to provide resiliency for the system.
- Connect the Director devices to each other and create a Director group. Connect one port from each network module on the first Director device to one port in each network module on the second Director device.
Figure 2 shows the specific ports on the Director group that you must connect to the Virtual Chassis and interconnect between the Director devices.
Figure 2: QFX3000-G QFabric System Fiber-Based Control Plane—Director Group to Virtual Chassis Connections

In this specific example, connect ports 0, 1, and 2 from module 0 on Director device DG0 to port 22 on Virtual Chassis VC0 (ge-0/0/22, ge-1/0/22, and ge-2/0/22), and connect ports 0, 1, and 2 from module 1 to port 22 on Virtual Chassis VC1 (ge-0/0/22, ge-1/0/22, and ge-2/0/22).
For Director device DG1, connect ports 0, 1, and 2 from module 0 to port 23 on Virtual Chassis VC0 (ge-0/0/23, ge-1/0/23, and ge-2/0/23), and connect ports 0, 1, and 2 from module 1 to port 23 on Virtual Chassis VC1 (ge-0/0/23, ge-1/0/23, and ge-2/0/23).
To form the Director group, connect module 0, port 3 on Director device DG0 to module 0, port 3 on Director device DG1. Similarly, connect module 1, port 3 on Director device DG0 to module 1, port 3 on Director device DG1. Table 2 shows the port mappings for the Director group in this example.
Table 2: Director Group Port Mappings
Director Device | Virtual Chassis VC0 | Virtual Chassis VC1 |
|---|---|---|
DG0 |
|
|
DG1 |
|
|
In the software, the ports of each network module are reversed, numbered from right to left, and incremented sequentially across modules. If you issue interface operational commands directly on the Director device, please note the following port mappings as shown in Table 3:
Table 3: Hardware to Software Port Mappings for Director Device Network Modules
Network Module | Port 0 | Port 1 | Port 2 | Port 3 |
|---|---|---|---|---|
Module 0 | eth5 | eth4 | eth3 | eth2 |
Module 1 | eth9 | eth8 | eth7 | eth6 |
Figure 3 shows the specific ports on the Interconnect devices that you must connect to the Virtual Chassis. In general, connect one port from each Control Board module in an Interconnect device to the first Virtual Chassis, and a second port from each Control Board module to the second Virtual Chassis.
Figure 3: QFX3000-G QFabric System Fiber-Based Control Plane—Interconnect Device to Virtual Chassis Connections

In this specific example, for both Interconnect devices IC0 and IC1, connect port 0 from CB0 and CB1 to Virtual Chassis VC0 and port 1 from CB0 and CB1 to Virtual Chassis VC1. Connect the port 0 cables to port 19 on Virtual Chassis VC0 (ge-0/0/19, ge-1/0/19, ge-2/0/19, and ge-3/0/19), and connect the port 1 cables to port 19 on Virtual Chassis VC1 (ge-0/0/19, ge-1/0/19, ge-2/0/19, and ge-3/0/19). Table 4 shows the port mappings for the Interconnect devices in this example.
Table 4: Interconnect Device Port Mappings
Interconnect Device | Virtual Chassis VC0 | Virtual Chassis VC1 |
|---|---|---|
IC0 |
|
|
IC1 |
|
|
As required, you can extend the number of Interconnect devices from two to four. For additional Interconnect devices IC2 and IC3, connect port 0 from CB0 and CB1 to Virtual Chassis VC0 and port 1 from CB0 and CB1 to Virtual Chassis VC1. Connect the port 0 cables to port 18 on Virtual Chassis VC0 (ge-0/0/18, ge-1/0/18, ge-2/0/18, and ge-3/0/18), and connect the port 1 cables to port 18 on Virtual Chassis VC1 (ge-0/0/18, ge-1/0/18, ge-2/0/18, and ge-3/0/18). Table 5 shows the port mappings needed to extend the number of Interconnect devices in this example to four devices.
Table 5: Interconnect Device Port Mappings for Two Additional Devices
Interconnect Device | Virtual Chassis VC0 | Virtual Chassis VC1 |
|---|---|---|
IC2 |
|
|
IC3 |
|
|
Figure 4, Figure 5, and Figure 6 show the specific ports on the Node devices that you must connect to the Virtual Chassis. In general, connect the first management port from a Node device to the first Virtual Chassis, and the second management port to the second Virtual Chassis.
Figure 4: QFX3000-G QFabric System Fiber-Based Control Plane—QFX3500 Node Device to Virtual Chassis Connections

Figure 5: QFX3000-G QFabric System Fiber-Based Control Plane—QFX3600 Node Device to Virtual Chassis Connections

Figure 6: QFX3000-G QFabric System Fiber-Based Control Plane—QFX5100 Node Device to Virtual Chassis Connections

In this specific example, for Node device Node0, connect port C0 (also known as me0) to Virtual Chassis 0 port ge-0/0/0, and connect port C1 (also known as me1) to Virtual Chassis 1 port ge-0/0/0.
For the remaining seven Node devices, connect port C0 to the ge-0/0/X port on Virtual Chassis 0 that matches the Node device number. Similarly, connect port C1 to the port on Virtual Chassis 1 that matches the Node device number. For example, you would connect Node device Node5 to port ge-0/0/5. Table 6 shows the full set of port mappings for the Node devices in this example.
Table 6: Node Device Port Mappings
Node Device | Virtual Chassis 0 | Virtual Chassis 1 |
|---|---|---|
Node0 | C0 to ge-0/0/0 | C1 to ge-0/0/0 |
Node1 | C0 to ge-0/0/1 | C1 to ge-0/0/1 |
Node2 | C0 to ge-0/0/2 | C1 to ge-0/0/2 |
Node3 | C0 to ge-0/0/3 | C1 to ge-0/0/3 |
Node4 | C0 to ge-0/0/4 | C1 to ge-0/0/4 |
Node5 | C0 to ge-0/0/5 | C1 to ge-0/0/5 |
Node6 | C0 to ge-0/0/6 | C1 to ge-0/0/6 |
Node7 | C0 to ge-0/0/7 | C1 to ge-0/0/7 |
Figure 7 shows the specific ports on the members of the first Virtual Chassis that you must connect to the members of the second Virtual Chassis. These connections create a link aggregation bundle (LAG) that provides redundancy and resiliency for the Virtual Chassis portion of the control plane. In general, connect each 10-Gigabit Ethernet uplink port from the first Virtual Chassis to the corresponding 10-Gigabit Ethernet uplink port on the second Virtual Chassis.
Figure 7: QFX3000-G QFabric System Fiber-Based Control Plane—Inter-Virtual Chassis LAG Connections

In this specific example, for Virtual Chassis VC0, connect port xe-0/1/0 to Virtual Chassis VC1 port xe-0/1/0. For the remaining seven 10-Gigabit Ethernet uplink ports, connect each port from VC0 to the corresponding port on VC1. For example, you would connect the xe-1/1/0 port on VC0 to port xe-1/1/0 on VC1, and so on.
Table 7 shows the full set of port mappings for the Virtual Chassis LAG connections in this example.
Table 7: Virtual Chassis LAG Port Mappings
VC0 and VC1 | Member 0 | Member 1 | Member 2 | Member 3 | Member 4 | Member 5 | Member 6 | Member 7 |
|---|---|---|---|---|---|---|---|---|
Uplink port 0 | xe-0/1/0 to xe-0/1/0 | xe-1/1/0 to xe-1/1/0 | xe-2/1/0 to xe-2/1/0 | xe-3/1/0 to xe-3/1/0 | xe-4/1/0 to xe-4/1/0 | xe-5/1/0 to xe-5/1/0 | xe-6/1/0 to xe-6/1/0 | xe-7/1/0 to xe-7/1/0 |
Configuration
CLI Quick Configuration
To quickly configure the QFabric system control plane Virtual Chassis, copy the following commands, paste them in a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
![]() | Note:
The configuration files for a QFabric system control plane network are also available for download from the QFX Series section of the Junos OS software download page at https://www.juniper.net/support/downloads/junos.html. |
Step-by-Step Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.
To configure a Virtual Chassis for the QFabric system control plane network:
- Create a configuration group to define global QFabric
system control plane properties. Enable commit synchronization and
graceful switchover, set up the number of aggregated Ethernet devices,
enable 10-Gigabit Ethernet mode on the inter-VC links, configure alarm
and LCD management, activate loop prevention, nonstop bridging, and
storm control, configure Link Layer Discovery Protocol (LLDP), specify
a global VLAN (VLAN 100) and 802.1q tunneling, and define options
for aggregated Ethernet interfaces.
Enable class of service (CoS) for the QFabric system control plane network. Establish forwarding classes, priorities, scheduler maps, classifiers, and queues for three types of traffic: control traffic, interdevice traffic, and best-effort traffic. Apply the qfabric group settings to the configuration.
[edit]user@switch# set groups qfabric system commit synchronizeuser@switch# set groups qfabric chassis redundancy graceful-switchoveruser@switch# set groups qfabric chassis aggregated-devices ethernet device-count 10user@switch# set groups qfabric chassis alarm management-ethernet link-down ignoreuser@switch# set groups qfabric chassis fpc 0 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 1 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 2 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 3 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 4 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 5 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 6 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis fpc 7 pic 1 sfpplus pic-mode 10guser@switch# set groups qfabric chassis lcd-menu fpc 0 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 1 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 2 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 3 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 4 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 5 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 6 menu-item maintenance-menu disableuser@switch# set groups qfabric chassis lcd-menu fpc 7 menu-item maintenance-menu disableuser@switch# set groups qfabric protocols rstp interface ae8.0 mode point-to-pointuser@switch# set groups qfabric protocols rstp interface all edgeuser@switch# set groups qfabric protocols rstp interface all no-root-portuser@switch# set groups qfabric protocols rstp bpdu-block-on-edgeuser@switch# set groups qfabric protocols lldp interface alluser@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_3 loss-priority low code-points 110user@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_3 loss-priority low code-points 111user@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_2 loss-priority low code-points 100user@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_2 loss-priority high code-points 101user@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_0 loss-priority low code-points 010user@switch# set groups qfabric class-of-service classifiers ieee-802.1 onep_qfabric_classifier forwarding-class class_0 loss-priority high code-points 001user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_3 loss-priority low code-points 110user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_3 loss-priority low code-points 111user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_2 loss-priority low code-points 100user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_2 loss-priority high code-points 101user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_0 loss-priority low code-points 010user@switch# set groups qfabric class-of-service classifiers inet-precedence IP_qfabric_classifier forwarding-class class_0 loss-priority high code-points 001user@switch# set groups qfabric class-of-service forwarding-classes class class_3 queue-num 7user@switch# set groups qfabric class-of-service forwarding-classes class class_2 queue-num 2user@switch# set groups qfabric class-of-service forwarding-classes class class_0 queue-num 0user@switch# set groups qfabric class-of-service interfaces ge-*/0/* scheduler-map cpe_network_smapuser@switch# set groups qfabric class-of-service interfaces ge-*/0/* unit 0 classifiers ieee-802.1 onep_qfabric_classifieruser@switch# set groups qfabric class-of-service interfaces ge-*/0/* unit 0 classifiers inet-precedence IP_qfabric_classifieruser@switch# set groups qfabric class-of-service interfaces ae* scheduler-map cpe_network_smapuser@switch# set groups qfabric class-of-service interfaces ae* unit 0 classifiers ieee-802.1 onep_qfabric_classifieruser@switch# set groups qfabric class-of-service interfaces ae* unit 0 classifiers inet-precedence IP_qfabric_classifieruser@switch# set groups qfabric class-of-service scheduler-maps cpe_network_smap forwarding-class class_3 scheduler scheduler_3user@switch# set groups qfabric class-of-service scheduler-maps cpe_network_smap forwarding-class class_2 scheduler scheduler_2user@switch# set groups qfabric class-of-service scheduler-maps cpe_network_smap forwarding-class class_0 scheduler scheduler_0user@switch# set groups qfabric class-of-service schedulers scheduler_3 buffer-size percent 30user@switch# set groups qfabric class-of-service schedulers scheduler_3 priority strict-highuser@switch# set groups qfabric class-of-service schedulers scheduler_2 transmit-rate percent 75user@switch# set groups qfabric class-of-service schedulers scheduler_2 buffer-size percent 30user@switch# set groups qfabric class-of-service schedulers scheduler_2 priority lowuser@switch# set groups qfabric class-of-service schedulers scheduler_0 transmit-rate percent 25user@switch# set groups qfabric class-of-service schedulers scheduler_0 buffer-size percent 40user@switch# set groups qfabric class-of-service schedulers scheduler_0 priority lowuser@switch# set groups qfabric ethernet-switching-options nonstop-bridginguser@switch# set groups qfabric ethernet-switching-options storm-control interface all bandwidth 10000user@switch# set groups qfabric vlans qfabric vlan-id 100user@switch# set groups qfabric vlans qfabric dot1q-tunnelinguser@switch# set groups qfabric-int interfaces <*> mtu 9216user@switch# set groups qfabric-int interfaces <*> unit 0 family ethernet-switching port-mode accessuser@switch# set groups qfabric-int interfaces <*> unit 0 family ethernet-switching vlan members qfabricuser@switch# set groups qfabric-ae interfaces <*> aggregated-ether-options link-speed 1guser@switch# set groups qfabric-ae interfaces <*> aggregated-ether-options lacp activeuser@switch# set apply-groups qfabric - Configure interfaces for the QFabric system control plane
network. Set the interface ranges where Node devices (0 through 15),
Interconnect devices (18 and 19), and Director devices (22 and 23)
connect to the control plane network through the Virtual Chassis.
Configure the inter-Virtual Chassis LAG connections for the ae8 interface
and apply the ae-interfaces configuration group to the Director group
aggregated Ethernet interfaces (ae0 and ae1).[edit]user@switch# set interfaces interface-range Node_Device_Interfaces member "ge-[0-7]/0/[0-15]"user@switch# set interfaces interface-range Node_Device_Interfaces apply-groups qfabric-intuser@switch# set interfaces interface-range Node_Device_Interfaces description "QFabric Node Device"user@switch# set interfaces interface-range Interconnect_Device_Interfaces member "ge-[0-7]/0/[18-21]"user@switch# set interfaces interface-range Interconnect_Device_Interfaces apply-groups qfabric-intuser@switch# set interfaces interface-range Interconnect_Device_Interfaces description "QFabric Interconnect Device"user@switch# set interfaces interface-range Director_Device_DG0_LAG_Interfaces member "ge-[0-7]/0/22"user@switch# set interfaces interface-range Director_Device_DG0_LAG_Interfaces description "QFabric Director Device - DG0"user@switch# set interfaces interface-range Director_Device_DG0_LAG_Interfaces ether-options 802.3ad ae0user@switch# set interfaces interface-range Director_Device_DG1_LAG_Interfaces member "ge-[0-7]/0/23"user@switch# set interfaces interface-range Director_Device_DG1_LAG_Interfaces description "QFabric Director Device - DG1"user@switch# set interfaces interface-range Director_Device_DG1_LAG_Interfaces ether-options 802.3ad ae1user@switch# set interfaces interface-range Control_Plane_Inter_VC_LAG_Interfaces member "xe-[0-7]/1/0"user@switch# set interfaces interface-range Control_Plane_Inter_VC_LAG_Interfaces description "QFabric Control Plane (Inter-VC LAG)"user@switch# set interfaces interface-range Control_Plane_Inter_VC_LAG_Interfaces ether-options 802.3ad ae8user@switch# set interfaces ae0 apply-groups qfabric-intuser@switch# set interfaces ae0 apply-groups qfabric-aeuser@switch# set interfaces ae0 description "QFabric Director Device - DG0"user@switch# set interfaces ae1 apply-groups qfabric-intuser@switch# set interfaces ae1 apply-groups qfabric-aeuser@switch# set interfaces ae1 description "QFabric Director Device - DG1"user@switch# set interfaces ae8 description "QFabric Control Plane (Inter-VC LAG)"user@switch# set interfaces ae8 mtu 9216user@switch# set interfaces ae8 aggregated-ether-options link-speed 10guser@switch# set interfaces ae8 aggregated-ether-options lacp activeuser@switch# set interfaces ae8 unit 0 family ethernet-switching vlan members qfabric
- Configure settings to enable the Virtual Chassis to interoperate
with your management network. Set a hostname, system services (such
as Telnet and SSH), system log thresholds, management interface parameters,
default routes, Virtual Chassis preprovisioning, and any additional
preferences you might have.[edit]user@switch# set system host-name qfabric-control-planeuser@switch# set system services sshuser@switch# set system services telnetuser@switch# set system services web-management httpuser@switch# set system syslog user * any emergencyuser@switch# set system syslog file messages any noticeuser@switch# set system syslog file messages authorization infouser@switch# set system syslog file messages archive world-readableuser@switch# set system syslog file messages explicit-priorityuser@switch# set system syslog file interactive-commands interactive-commands anyuser@switch# set system syslog file secure authorization infouser@switch# set system syslog file default-log-messages any anyuser@switch# set system syslog file default-log-messages structured-datauser@switch# set system syslog file console any erroruser@switch# set system syslog time-format milliseconduser@switch# set interfaces vme unit 0 family inet address 192.168.157.26/24user@switch# set routing-options static route 0.0.0.0/0 next-hop 192.168.157.1user@switch# set virtual-chassis preprovisioneduser@switch# set virtual-chassis member 0 role routing-engineuser@switch# set virtual-chassis member 0 serial-number abc123user@switch# set virtual-chassis member 1 role routing-engineuser@switch# set virtual-chassis member 1 serial-number def456user@switch# set virtual-chassis member 2 role line-card user@switch# set virtual-chassis member 2 serial-number ghi789user@switch# set virtual-chassis member 3 role line-carduser@switch# set virtual-chassis member 3 serial-number jkl012user@switch# set virtual-chassis member 4 role line-carduser@switch# set virtual-chassis member 4 serial-number mno321user@switch# set virtual-chassis member 5 role line-carduser@switch# set virtual-chassis member 5 serial-number pqr654user@switch# set virtual-chassis member 6 role line-carduser@switch# set virtual-chassis member 6 serial-number stu987user@switch# set virtual-chassis member 7 role line-carduser@switch# set virtual-chassis member 7 serial-number vwx210
Results
To view the configuration, issue the show command in configuration mode or the show configuration command in operational mode. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
The following configuration is the standard configuration that applies universally to both Virtual Chassis in your QFabric system control plane network.
The following portion of the configuration applies to the specific requirements of your management network. Modify this section to meet the needs of your network.
To verify the syntax of your configuration before committing it, enter commit check from configuration mode. If you are done configuring the device, enter commit from configuration mode.
Verification
Confirm that the Virtual Chassis configuration is working properly.
- Verifying the QFabric System Control Plane—Virtual Chassis VC0
- Verifying the QFabric System Control Plane—Virtual Chassis VC1
Verifying the QFabric System Control Plane—Virtual Chassis VC0
Purpose
Verify that your first Virtual Chassis is operational.
Action
Connect to the Junos OS CLI of Virtual Chassis VC0, either from your management network or from the console port of the master Virtual Chassis member. In operational mode, enter the show virtual-chassis status and show interfaces terse commands.
Sample Output
{master:0} user@vc0> show virtual-chassis status
Preprovisioned Virtual Chassis
Virtual Chassis ID: c809.2c5d.9f7b
Virtual Chassis Mode: Enabled
Mstr Mixed Neighbor List
Member ID Status Serial No Model prio Role Mode ID Interface
0 (FPC 0) Prsnt BP0210471476 ex4200-24f 129 Master* N 7 vcp-0
1 vcp-1
1 (FPC 1) Prsnt BP0210460181 ex4200-24f 129 Backup N 2 vcp-0
0 vcp-1
2 (FPC 2) Prsnt BP0210458724 ex4200-24f 0 Linecard N 3 vcp-0
1 vcp-1
3 (FPC 3) Prsnt BP0210477189 ex4200-24f 0 Linecard N 4 vcp-0
2 vcp-1
4 (FPC 4) Prsnt BP0210471467 ex4200-24f 0 Linecard N 5 vcp-0
3 vcp-1
5 (FPC 5) Prsnt BP0210460118 ex4200-24f 0 Linecard N 6 vcp-0
4 vcp-1
6 (FPC 6) Prsnt BP0210458742 ex4200-24f 0 Linecard N 7 vcp-0
5 vcp-1
7 (FPC 7) Prsnt BP0210477198 ex4200-24f 0 Linecard N 0 vcp-0
6 vcp-1{master:0} user@vc0> show interfaces terse Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.0 up up eth-switch
ge-0/0/1 up up
ge-0/0/1.0 up up eth-switch
ge-0/0/2 up up
ge-0/0/2.0 up up eth-switch
ge-0/0/3 up up
ge-0/0/3.0 up up eth-switch
ge-0/0/4 up up
ge-0/0/4.0 up up eth-switch
ge-0/0/5 up up
ge-0/0/5.0 up up eth-switch
ge-0/0/6 up up
ge-0/0/6.0 up up eth-switch
ge-0/0/7 up up
ge-0/0/7.0 up up eth-switch
ge-0/0/19 up up
ge-0/0/19.0 up up eth-switch
ge-0/0/22 up up
ge-0/0/22.0 up up aenet --> ae0.0
ge-0/0/23 up up
ge-0/0/23.0 up up aenet --> ae1.0
xe-0/1/0 up up
xe-0/1/0.0 up up aenet --> ae8.0
xe-0/1/2 up up
ge-1/0/19 up up
ge-1/0/19.0 up up eth-switch
ge-1/0/22 up up
ge-1/0/22.0 up up aenet --> ae0.0
ge-1/0/23 up up
ge-1/0/23.0 up up aenet --> ae1.0
xe-1/1/0 up up
xe-1/1/0.0 up up aenet --> ae8.0
xe-1/1/2 up up
ge-2/0/19 up up
ge-2/0/19.0 up up eth-switch
ge-2/0/22 up up
ge-2/0/22.0 up up aenet --> ae0.0
ge-2/0/23 up up
ge-2/0/23.0 up up aenet --> ae1.0
xe-2/1/0 up up
xe-2/1/0.0 up up aenet --> ae8.0
xe-2/1/2 up up
ge-3/0/19 up up
ge-3/0/19.0 up up eth-switch
xe-3/1/0 up up
xe-3/1/0.0 up up aenet --> ae8.0
xe-3/1/2 up up
xe-4/1/0 up up
xe-4/1/0.0 up up aenet --> ae8.0
xe-4/1/2 up up
xe-5/1/0 up up
xe-5/1/0.0 up up aenet --> ae8.0
xe-5/1/2 up up
xe-6/1/0 up up
xe-6/1/0.0 up up aenet --> ae8.0
xe-6/1/2 up up
xe-7/1/0 up up
xe-7/1/0.0 up up aenet --> ae8.0
xe-7/1/2 up up
vcp-0 up up
vcp-0.32768 up up
vcp-1 up up
vcp-1.32768 up up
ae0 up up
ae0.0 up up eth-switch
ae1 up up
ae1.0 up up eth-switch
ae2 up down
ae3 up down
ae4 up down
ae5 up down
ae6 up down
ae7 up down
ae8 up up
ae8.0 up up eth-switch
ae9 up down
bme0 up up
bme0.32768 up up inet 128.0.0.1/2
128.0.0.16/2
128.0.0.32/2
tnp 0x10
bme0.32770 up up eth-switch
bme0.32771 down up eth-switch
bme0.32772 down up eth-switch
bme0.32773 down up eth-switch
bme0.32774 down up eth-switch
bme0.32775 down up eth-switch
bme0.32776 down up eth-switch
dsc up up
gre up up
ipip up up
lo0 up up
lo0.0 up up inet 10.255.195.96 --> 0/0
iso 47.0005.80ff.f800.0000.0108.0001.0102.5519.5096
inet6 abcd::10.255.195.96
fe80::21f:120f:fc39:6d80
lsi up up
me0 up up
mtun up up
pimd up up
pime up up
tap up up
vlan up up
vme up up
vme0.0 up up inet 192.168.157.26/24
Meaning
In the output of the show virtual-chassis status command, if all eight members appear, the Virtual Chassis is operational.
In the output of the show interfaces terse command, if all interfaces that connect to the QFabric system devices are listed as up (such as ge-0/0/0 through ge-0/0/7 for the Node devices; ge-0/0/19, ge-1/0/19, ge-2/0/19, and ge-3/0/19 for the Interconnect devices; ge-0/0/22, ge-0/0/23, ge-1/0/22, ge-1/0/23, ge-2/0/22, and ge-2/0/23 for the Director devices; and xe-0/1/0, xe-1/1/0, xe-2/1/0, xe-3/1/0, xe-4/1/0, xe-5/1/0, xe-6/1/0, and xe-7/1/0 for the inter-Virtual Chassis connections), the control plane is properly connected.
Verifying the QFabric System Control Plane—Virtual Chassis VC1
Purpose
Verify that your second Virtual Chassis is operational.
Action
Connect to the Junos OS CLI of Virtual Chassis VC1, either from your management network or from the console port of the master Virtual Chassis member. In operational mode, enter the show virtual-chassis status and show interfaces terse commands.
Sample Output
{master:0} user@vc1> show virtual-chassis status
Preprovisioned Virtual Chassis
Virtual Chassis ID: c809.2c5d.9f8a
Virtual Chassis Mode: Enabled
Mstr Mixed Neighbor List
Member ID Status Serial No Model prio Role Mode ID Interface
0 (FPC 0) Prsnt BP0210471477 ex4200-24f 129 Master* N 7 vcp-0
1 vcp-1
1 (FPC 1) Prsnt BP0210460182 ex4200-24f 129 Backup N 2 vcp-0
0 vcp-1
2 (FPC 2) Prsnt BP0210458725 ex4200-24f 0 Linecard N 3 vcp-0
1 vcp-1
3 (FPC 3) Prsnt BP0210477180 ex4200-24f 0 Linecard N 4 vcp-0
2 vcp-1
4 (FPC 4) Prsnt BP0210471478 ex4200-24f 0 Linecard N 5 vcp-0
3 vcp-1
5 (FPC 5) Prsnt BP0210460128 ex4200-24f 0 Linecard N 6 vcp-0
4 vcp-1
6 (FPC 6) Prsnt BP0210458752 ex4200-24f 0 Linecard N 7 vcp-0
5 vcp-1
7 (FPC 7) Prsnt BP0210477108 ex4200-24f 0 Linecard N 0 vcp-0
6 vcp-1
{master:0} user@vc1> show interfaces terse Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.0 up up eth-switch
ge-0/0/1 up up
ge-0/0/1.0 up up eth-switch
ge-0/0/2 up up
ge-0/0/2.0 up up eth-switch
ge-0/0/3 up up
ge-0/0/3.0 up up eth-switch
ge-0/0/4 up up
ge-0/0/4.0 up up eth-switch
ge-0/0/5 up up
ge-0/0/5.0 up up eth-switch
ge-0/0/6 up up
ge-0/0/6.0 up up eth-switch
ge-0/0/7 up up
ge-0/0/7.0 up up eth-switch
ge-0/0/19 up up
ge-0/0/19.0 up up eth-switch
ge-0/0/22 up up
ge-0/0/22.0 up up aenet --> ae0.0
ge-0/0/23 up up
ge-0/0/23.0 up up aenet --> ae1.0
xe-0/1/0 up up
xe-0/1/0.0 up up aenet --> ae8.0
xe-0/1/2 up up
ge-1/0/19 up up
ge-1/0/19.0 up up eth-switch
ge-1/0/22 up up
ge-1/0/22.0 up up aenet --> ae0.0
ge-1/0/23 up up
ge-1/0/23.0 up up aenet --> ae1.0
xe-1/1/0 up up
xe-1/1/0.0 up up aenet --> ae8.0
xe-1/1/2 up up
ge-2/0/19 up up
ge-2/0/19.0 up up eth-switch
ge-2/0/22 up up
ge-2/0/22.0 up up aenet --> ae0.0
ge-2/0/23 up up
ge-2/0/23.0 up up aenet --> ae1.0
xe-2/1/0 up up
xe-2/1/0.0 up up aenet --> ae8.0
xe-2/1/2 up up
ge-3/0/19 up up
ge-3/0/19.0 up up eth-switch
xe-3/1/0 up up
xe-3/1/0.0 up up aenet --> ae8.0
xe-3/1/2 up up
xe-4/1/0 up up
xe-4/1/0.0 up up aenet --> ae8.0
xe-4/1/2 up up
xe-5/1/0 up up
xe-5/1/0.0 up up aenet --> ae8.0
xe-5/1/2 up up
xe-6/1/0 up up
xe-6/1/0.0 up up aenet --> ae8.0
xe-6/1/2 up up
xe-7/1/0 up up
xe-7/1/0.0 up up aenet --> ae8.0
xe-7/1/2 up up
vcp-0 up up
vcp-0.32768 up up
vcp-1 up up
vcp-1.32768 up up
ae0 up down
ae0.0 up down eth-switch
ae1 up down
ae1.0 up down eth-switch
ae2 up down
ae3 up down
ae4 up down
ae5 up down
ae6 up down
ae7 up down
ae8 up up
ae8.0 up up eth-switch
ae9 up down
bme0 up up
bme0.32768 up up inet 128.0.0.1/2
128.0.0.16/2
128.0.0.32/2
tnp 0x10
bme0.32770 up up eth-switch
bme0.32771 down up eth-switch
bme0.32772 down up eth-switch
bme0.32773 down up eth-switch
bme0.32774 down up eth-switch
bme0.32775 down up eth-switch
bme0.32776 down up eth-switch
dsc up up
gre up up
ipip up up
lo0 up up
lo0.0 up up inet 10.255.195.97 --> 0/0
iso 47.0005.80ff.f800.0000.0108.0001.0102.5519.5097
inet6 abcd::10.255.195.97
fe80::21f:120f:fc39:6d81
lsi up up
me0 up up
mtun up up
pimd up up
pime up up
tap up up
vlan up up
vme up up
vme0.0 up up inet 192.168.157.27/24
Meaning
In the output of the show virtual-chassis status command, if all eight members appear, the Virtual Chassis is operational.
In the output of the show interfaces terse command, if all interfaces that connect to the QFabric system devices are listed as up (such as ge-0/0/0 through ge-0/0/7 for the Node devices; ge-0/0/19, ge-1/0/19, ge-2/0/19, and ge-3/0/19 for the Interconnect devices; ge-0/0/22, ge-0/0/23, ge-1/0/22, ge-1/0/23, ge-2/0/22, and ge-2/0/23 for the Director devices; and xe-0/1/0, xe-1/1/0, xe-2/1/0, xe-3/1/0, xe-4/1/0, xe-5/1/0, xe-6/1/0, and xe-7/1/0 for the inter-Virtual Chassis connections), the control plane is properly connected.
![]() | Note: The ae0 and ae1 LAG connections on Virtual Chassis VC1 appear as down in the output of the show interfaces terse command because they are the backup connections to the Director devices. The active, primary LAG connections are typically on Virtual Chassis VC0. |
Related Documentation
- EX Series
- Installing and Connecting an EX4200 Switch
- Configuring an EX4200, EX4500, or EX4550 Virtual Chassis (CLI Procedure)
- QFabric System
- QFX3000-G QFabric System Installation Overview
- Installing and Connecting a QFX3100 Director Device
- Installing and Connecting a QFX3008-I Interconnect Device
- Installing and Connecting a QFX3500 Device
- Installing and Connecting a QFX3600 or QFX3600-I Device
- Understanding the QFabric System Control Plane
- QFX Series standalone switches
- Installing and Connecting a QFX3500 Device
- Installing and Connecting a QFX3600 or QFX3600-I Device



