Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring the Virtual Chassis for a Copper-Based QFX3000-G QFabric System Control Plane

 

This example shows you how to connect QFabric system components and configure the Virtual Chassis used by a copper-based QFX3000-G QFabric system control plane network. Proper wiring of Director devices, Interconnect devices, and Node devices to the Virtual Chassis, 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

  • Eight EX4200-48T switches, used to make two redundant Virtual Chassis with four members apiece

    Note

    You can use eight EX4300-48T switches in place of eight EX4200-48T switches.

  • Junos OS Release 12.3R6.6 for the EX Series switches used in the Virtual Chassis

  • Junos OS Release 13.2X52-D10 for the QFX Series

Before you begin:

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 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 31 to Node devices, ports 38 and 39 to Interconnect devices, and ports 40 and 41 to Director devices. Table 1 shows the details of the QFabric system device-to-Virtual Chassis port mappings.

Figure 1: QFX3000-G QFabric System Control Plane—Virtual Chassis Port Ranges
QFX3000-G QFabric System Control Plane—Virtual
Chassis Port Ranges
Caution
  • The control plane network within a QFabric system should be considered a critical component of the system that should not be shared with other network traffic. In order to scale efficiently, the control plane network must be reserved for the QFabric system and its components. As a result, the ports of the QFabric system control plane must never be used for any purpose other than to transport QFabric system control plane traffic, and we neither recommend nor support the connection of other devices to the QFabric system control plane network.

  • Do not install Junos Space and AI-Scripts (AIS) on the control plane network Virtual Chassis in a QFX3000-G QFabric system.

Note

Not all port numbers are represented in Table 1, and ports 32 through 37 and ports 42 through 47 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 Control Plane Port Assignments

Member 0

Member 1

Member 2

Member 3

Member Port Number

QFabric System Component

Node0

ge-0/0/0

Node32

ge-1/0/0

Node64

ge-2/0/0

Node96

ge-3/0/0

ge-X/0/0

Node devices

Node1

ge-0/0/1

Node33

ge-1/0/1

Node65

ge-2/0/1

Node97

ge-3/0/1

ge-X/0/1

Node devices

Node2

ge-0/0/2

Node34

ge-1/0/2

Node66

ge-2/0/2

Node98

ge-3/0/2

ge-X/0/2

Node devices

Node3

ge-0/0/3

Node35

ge-1/0/3

Node67

ge-2/0/3

Node99

ge-3/0/3

ge-X/0/3

Node devices

Node4

ge-0/0/4

Node36

ge-1/0/4

Node68

ge-2/0/4

Node100

ge-3/0/4

ge-X/0/4

Node devices

Node5

ge-0/0/5

Node37

ge-1/0/5

Node69

ge-2/0/5

Node101

ge-3/0/5

ge-X/0/5

Node devices

Node6

ge-0/0/6

Node38

ge-1/0/6

Node70

ge-2/0/6

Node102

ge-3/0/6

ge-X/0/6

Node devices

Node7

ge-0/0/7

Node39

ge-1/0/7

Node71

ge-2/0/7

Node103

ge-3/0/7

ge-X/0/7

Node devices

Node8

ge-0/0/8

Node40

ge-1/0/8

Node72

ge-2/0/8

Node104

ge-3/0/8

ge-X/0/8

Node devices

Node9

ge-0/0/9

Node41

ge-1/0/9

Node73

ge-2/0/9

Node105

ge-3/0/9

ge-X/0/9

Node devices

Node10

ge-0/0/10

Node42

ge-1/0/10

Node74

ge-2/0/10

Node106

ge-3/0/10

ge-X/0/10

Node devices

Node11

ge-0/0/11

Node43

ge-1/0/11

Node75

ge-2/0/11

Node107

ge-3/0/11

ge-X/0/11

Node devices

Node12

ge-0/0/12

Node44

ge-1/0/12

Node76

ge-2/0/12

Node108

ge-3/0/12

ge-X/0/12

Node devices

Node13

ge-0/0/13

Node45

ge-1/0/13

Node77

ge-2/0/13

Node109

ge-3/0/13

ge-X/0/13

Node devices

Node14

ge-0/0/14

Node46

ge-1/0/14

Node78

ge-2/0/14

Node110

ge-3/0/14

ge-X/0/14

Node devices

Node15

ge-0/0/15

Node47

ge-1/0/15

Node79

ge-2/0/15

Node111

ge-3/0/15

ge-X/0/15

Node devices

Node16

ge-0/0/16

Node48

ge-1/0/16

Node80

ge-2/0/16

Node112

ge-3/0/16

ge-X/0/16

Node devices

Node17

ge-0/0/17

Node49

ge-1/0/17

Node81

ge-2/0/17

Node113

ge-3/0/17

ge-X/0/17

Node devices

Node18

ge-0/0/18

Node50

ge-1/0/18

Node82

ge-2/0/18

Node114

ge-3/0/18

ge-X/0/18

Node devices

Node19

ge-0/0/19

Node51

ge-1/0/19

Node83

ge-2/0/19

Node115

ge-3/0/19

ge-X/0/19

Node devices

Node20

ge-0/0/20

Node52

ge-1/0/20

Node84

ge-2/0/20

Node116

ge-3/0/20

ge-X/0/20

Node devices

Node21

ge-0/0/21

Node53

ge-1/0/21

Node85

ge-2/0/21

Node117

ge-3/0/21

ge-X/0/21

Node devices

Node22

ge-0/0/22

Node54

ge-1/0/22

Node86

ge-2/0/22

Node118

ge-3/0/22

ge-X/0/22

Node devices

Node23

ge-0/0/23

Node55

ge-1/0/23

Node87

ge-2/0/23

Node119

ge-3/0/23

ge-X/0/23

Node devices

Node24

ge-0/0/24

Node56

ge-1/0/24

Node88

ge-2/0/24

Node120

ge-3/0/24

ge-X/0/24

Node devices

Node25

ge-0/0/25

Node57

ge-1/0/25

Node89

ge-2/0/25

Node121

ge-3/0/25

ge-X/0/25

Node devices

Node26

ge-0/0/26

Node58

ge-1/0/26

Node90

ge-2/0/26

Node122

ge-3/0/26

ge-X/0/26

Node devices

Node27

ge-0/0/27

Node59

ge-1/0/27

Node91

ge-2/0/27

Node123

ge-3/0/27

ge-X/0/27

Node devices

Node28

ge-0/0/28

Node60

ge-1/0/28

Node92

ge-2/0/28

Node124

ge-3/0/28

ge-X/0/28

Node devices

Node29

ge-0/0/29

Node61

ge-1/0/29

Node93

ge-2/0/29

Node125

ge-3/0/29

ge-X/0/29

Node devices

Node30

ge-0/0/30

Node62

ge-1/0/30

Node94

ge-2/0/30

Node126

ge-3/0/30

ge-X/0/30

Node devices

Node31

ge-0/0/31

Node63

ge-1/0/31

Node95

ge-2/0/31

Node127

ge-3/0/31

ge-X/0/31

Node devices

Reserved

ge-0/0/32

Reserved

ge-1/0/32

Reserved

ge-2/0/32

Reserved

ge-3/0/32

ge-X/0/32

Future use

...

...

...

...

...

...

Reserved

ge-0/0/37

Reserved

ge-1/0/37

Reserved

ge-2/0/37

Reserved

ge-3/0/37

ge-X/0/37

Future use

IC2 CB0

ge-0/0/38

IC2 CB1

ge-1/0/38

IC3 CB0

ge-2/0/38

IC3 CB1

ge-3/0/38

ge-X/0/38

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/39

IC0 CB1

ge-1/0/39

IC1 CB0

ge-2/0/39

IC1 CB1

ge-3/0/39

ge-X/0/39

Interconnect devices

Note: On both Control Boards, use port 0 to connect to VC0, and port 1 to connect to VC1.

DG0 port 0

ge-0/0/40

DG0 port 1

ge-1/0/40

DG0 port 2

ge-2/0/40

Reserved

ge-3/0/40

ge-X/0/40

Director device 0

DG1 port 0

ge-0/0/41

DG1 port 1

ge-1/0/41

DG1 port 2

ge-2/0/41

Reserved

ge-3/0/41

ge-X/0/41

Director device 1

Reserved

ge-0/0/42

Reserved

ge-1/0/42

Reserved

ge-2/0/42

Reserved

ge-3/0/42

ge-X/0/42

Future use

...

...

...

...

...

...

Reserved

ge-0/0/47

Reserved

ge-1/0/47

Reserved

ge-2/0/47

Reserved

ge-3/0/47

ge-X/0/47

Future use

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-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-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. You can use either straight-through RJ-45 patch cables or crossover cables, because the Director devices contain autosensing modules. 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 Control Plane—Director Group to Virtual Chassis Connections
QFX3000-G QFabric System 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 40 on Virtual Chassis VC0 (ge-0/0/40, ge-1/0/40, and ge-2/0/40), and connect ports 0, 1, and 2 from module 1 to port 40 on Virtual Chassis VC1 (ge-0/0/40, ge-1/0/40, and ge-2/0/40).

For Director device DG1, connect ports 0, 1, and 2 from module 0 to port 41 on Virtual Chassis VC0 (ge-0/0/41, ge-1/0/41, and ge-2/0/41), and connect ports 0, 1, and 2 from module 1 to port 41 on Virtual Chassis VC1 (ge-0/0/41, ge-1/0/41, and ge-2/0/41).

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

  • Module 0, port 0 to ge-0/0/40 on VC0

  • Module 0, port 1 to ge-1/0/40 on VC0

  • Module 0, port 2 to ge-2/0/40 on VC0

  • Module 0, port 3 to module 0, port 3 on DG1

  • Module 1, port 0 to ge-0/0/40 on VC1

  • Module 1, port 1 to ge-1/0/40 on VC1

  • Module 1, port 2 to ge-2/0/40 on VC1

  • Module 1, port 3 to module 1, port 3 on DG1

DG1

  • Module 0, port 0 to ge-0/0/41 on VC0

  • Module 0, port 1 to ge-1/0/41 on VC0

  • Module 0, port 2 to ge-2/0/41 on VC0

  • Module 0, port 3 to module 0, port 3 on DG0

  • Module 1, port 0 to ge-0/0/41 on VC1

  • Module 1, port 1 to ge-1/0/41 on VC1

  • Module 1, port 2 to ge-2/0/41 on VC1

  • Module 1, port 3 to module 1, port 3 on DG0

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 Control Plane—Interconnect Device to Virtual Chassis Connections
QFX3000-G QFabric System 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 39 on Virtual Chassis VC0 (ge-0/0/39, ge-1/0/39, ge-2/0/39, and ge-3/0/39), and connect the port 1 cables to port 39 on Virtual Chassis VC1 (ge-0/0/39, ge-1/0/39, ge-2/0/39, and ge-3/0/39). 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

  • CB0, port 0 to ge-0/0/39

  • CB1, port 0 to ge-1/0/39

  • CB0, port 1 to ge-0/0/39

  • CB1, port 1 to ge-1/0/39

IC1

  • CB0, port 0 to ge-2/0/39

  • CB1, port 0 to ge-3/0/39

  • CB0, port 1 to ge-2/0/39

  • CB1, port 1 to ge-3/0/39

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 38 on Virtual Chassis VC0 (ge-0/0/38, ge-1/0/38, ge-2/0/38, and ge-3/0/38), and connect the port 1 cables to port 38 on Virtual Chassis VC1 (ge-0/0/38, ge-1/0/38, ge-2/0/38, and ge-3/0/38). 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

  • CB0, port 0 to ge-0/0/38

  • CB1, port 0 to ge-1/0/38

  • CB0, port 1 to ge-0/0/38

  • CB1, port 1 to ge-1/0/38

IC3

  • CB0, port 0 to ge-2/0/38

  • CB1, port 0 to ge-3/0/38

  • CB0, port 1 to ge-2/0/38

  • CB1, port 1 to ge-3/0/38

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 Control Plane—QFX3500 Node Device to Virtual Chassis Connections
QFX3000-G QFabric System Control Plane—QFX3500
Node Device to Virtual Chassis Connections
Figure 5: QFX3000-G QFabric System Control Plane—QFX3600 Node Device to Virtual Chassis Connections
QFX3000-G QFabric System Control Plane—QFX3600
Node Device to Virtual Chassis Connections
Figure 6: QFX3000-G QFabric System Control Plane—QFX5100 Node Device to Virtual Chassis Connections
QFX3000-G QFabric System 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 Control Plane—Inter-Virtual Chassis LAG Connections
QFX3000-G QFabric System 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-2/1/2 port on VC0 to port xe-2/1/2 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

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

Uplink port 2

xe-0/1/2 to xe-0/1/2

xe-1/1/2 to xe-1/1/2

xe-2/1/2 to xe-2/1/2

xe-3/1/2 to xe-3/1/2

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:

  1. 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, 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, define options for aggregated Ethernet interfaces, and enable the uplink module for 10-Gigabit Ethernet operation.

    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.

  2. Configure interfaces for the QFabric system control plane network. Set the interface ranges where Node devices (0 through 31), Interconnect devices (38 and 39), and Director devices (40 and 41) 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 remaining aggregated Ethernet interfaces (ae0 through ae7).
  3. Configure settings to enable the Virtual Chassis to interoperate with your management network. Set a hostname, system services (such as Telnet), system log thresholds, management interface parameters, default routes, Virtual Chassis preprovisioning, and any additional preferences you might have.

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

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
{master:0}
user@vc0> show interfaces terse

Meaning

In the output of the show virtual-chassis status command, if all four 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/39, ge-1/0/39, ge-2/0/39, and ge-3/0/39 for the Interconnect devices; ge-0/0/40, ge-1/0/40, and ge-2/0/40 for the Director devices; ge-0/0/0 through ge-0/0/7 for the Node devices; and xe-0/1/0, xe-0/1/2, xe-1/1/0, xe-1/1/2, xe-2/1/0, xe-2/1/2, xe-3/1/0, and xe-3/1/2 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
{master:0}
user@vc1> show interfaces terse

Meaning

In the output of the show virtual-chassis status command, if all four 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/39, ge-1/0/39, ge-2/0/39, and ge-3/0/39 for the Interconnect devices; ge-0/0/40, ge-1/0/40, and ge-2/0/40 for the Director devices; ge-0/0/0 through ge-0/0/7 for the Node devices; and xe-0/1/0, xe-0/1/2, xe-1/1/0, xe-1/1/2, xe-2/1/0, xe-2/1/2, xe-3/1/0, and xe-3/1/2 for the inter-Virtual Chassis connections), the control plane is properly connected.