Example: Configuring a Virtual Chassis with a Preprovisioned Configuration File

You can deterministically control both the role and the member ID assigned to each member switch in a Virtual Chassis configuration by creating a preprovisioned configuration file. A preprovisioned configuration file links the serial number of each EX 4200 switch to a specified member ID and role. The serial number must be specified in the configuration file in order for the member to be recognized as part of the Virtual Chassis configuration. You must select two members that you want to make eligible for election as master of the Virtual Chassis configuration. When you list these two members in the preprovisioned configuration file, you designate the members role as routing-engine. One will function as the master of the Virtual Chassis configuration and the other will function as the backup. Additional members, not eligible for election as master, can be specified as linecard in the preprovisioned configuration file.

NOTE: When you use a preprovisioned configuration, you cannot modify the mastership priority or member ID of member switches through the user interfaces. This example describes how to configure a Virtual Chassis across multiple wiring closets using a preprovisioned configuration file:

Requirements on page 1 Overview and Topology on page 2 Configuration on page 6 Verification on page 8 Troubleshooting on page 11

Requirements
This example uses the following hardware and software components:

JUNOS Release 9.0 or later for EX-series switches Five EX 4200-48P switches Five EX 4200-24T switches Four EX-UM-2XFP uplink modules

Example: Configuring a Virtual Chassis with a Preprovisioned Configuration File

Before you create the preprovisioned configuration of the Virtual Chassis and interconnect the members across the wiring closets, be sure you have:
1. 2.

Made a list of the serial numbers of all the switches to be connected as a Virtual Chassis configuration. Noted the desired role (routing-engine or linecard) of each switch. If you configure the member with a routing-engine role, it is eligible to function as a master or backup. If you configure the member with a linecard role , it is not eligible to become a master or backup. Installed an EX-UM-2XFP uplink module in the member switches that will be interconnected across wiring closets. See Installing an Uplink Module in an EX-series Switch. Interconnected the member switches within each wiring closet using the dedicated VCPs on the rear panel of switches. See Connecting a Virtual Chassis Cable to an EX 4200 Switch. Powered on the switch that you plan to use as the master switch (SWA-0). Run the EZ Setup program on SWA-0, specifying the identification parameters. See Connecting and Configuring an EX-series Switch (CLI Procedure) for details. SWA-0 is going to be configured in the example to function as the master of the Virtual Chassis configuration. Thus, the properties that you specified for SWA-0 apply to the entire Virtual Chassis configuration, including all the member switches that you specify in the preprovisioned configuration file.

3.

4.

5. 6.

7.

Configure SWA-0 with the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis configuration, if desired.
[edit] user@SWA-0# set interfaces vme unit 0 family inet /ip-address/mask/

Overview and Topology

In this example, five EX 4200 switches (SWA-0 through SWA-4) are interconnected with their dedicated VCPs in wiring closet A and five EX 4200 switches (SWA-5 through SWA-9) are interconnected with their dedicated VCPs in wiring closet B. SWA-0 (in wiring closet A) is going to be the master of the Virtual Chassis configuration. This example shows how to create a preprovisioned configuration file on SWA-0 for all member switches that will be interconnected in the Virtual Chassis configuration. The preprovisioned configuration file includes member IDs for the members in wiring closet A and for the members in wiring closet B. SWA-5 (in wiring closet B) is going to be the backup of the Virtual Chassis configuration. Both SWA-0 and SWA-5 are specified in the preprovisioned configuration file with the role of routing-engine. All other members are specified with the role of linecard. If all member switches could be interconnected with their dedicated VCPs, you could simply power on the switches after saving and committing the preprovisioned configuration file. The master detects the connection of the members through the

Overview and Topology

dedicated VCPs and applies the parameters specified in the preprovisioned configuration file. However, the Virtual Chassis cables that interconnect the VCPs of member switches within a single wiring closet are not long enough to connect member switches across wiring closets. Instead, you can use the fiber cable connections in the EX-UM-2XFP or EX-UM-4SFP uplink modules to interconnect the member switches in wiring closet A to the member switch in wiring closet B. For redundancy, this example connects uplink ports from two member switches in wiring closet A (SWA0 and SWA2) to two member switches (SWA-5 and SWA-7) in wiring closet B.

NOTE: You can use either a 10-Gbps Ethernet uplink port (EX-UM-2XFP) or a 1-Gbps Ethernet uplink port (EX_UM-4SFP) as a VCP interface. When an uplink port is set as a VCP interface, it cannot be used for any other purpose. The EX-UM-2XP uplink module has two 10-Gbps ports; the EX-UM-4SFP has four 1-Gbps ports. You can set one port as a VCP interface and configure the other port in trunk mode as an uplink to a distribution switch. Because this particular preprovisioned configuration is for a Virtual Chassis that is interconnected across wiring closets, we will bring up the Virtual Chassis configuration in stages. First, we power on SWA-0 (without powering on any other switches) and create the preprovisioned configuration file. Then we power on the remaining switches in wiring closet A. If we check the status of the Virtual Chassis configuration at this point by using the show virtual-chassis status command, it will display only member 0 through member 4. The members that have not yet been interconnected will not be listed. Next power on SWA-5 without powering on the remaining switches (SWA-6 through SWA-9) in wiring closet B. Bring up SWA-5 as a standalone switch and set one of its uplinks as a VCP interface prior to interconnecting it with the Virtual Chassis configuration in wiring closet A. Without this setting, SWA-5 cannot be detected as a member switch by the master of the Virtual Chassis configuration. You can set the uplink VCP of SWA5 without running the EZ Setup program by directly connecting to the console port. If you wish, you can run EZ Setup program and specify identification parameters. When you interconnect SWA-5 with the master of the Virtual Chassis configuration, the master overwrites any conflicting parameters. After setting the VCP uplink in SWA-5, connect this VCP uplink with the VCP uplink of SWA-0 in wiring closet A. SWA-5 (serial number pqr678) is specified as a routing-engine in the preprovisioned configuration file. This example uses SWA-5 as the backup of the Virtual Chassis configuration. If a problem occurs in wiring closet A, SWA-5 would take control of the Virtual Chassis configuration and maintain the network connections. Specify both SWA-0 and SWA-5 as routing-engine. Because SWA-0 is powered on prior to SWA-5, it has additional prioritization properties that cause it to be elected as master of the Virtual Chassis configuration. After being physically interconnected with SWA-0, SWA-5 reboots and comes up as member 5 and as the backup of the Virtual Chassis configuration.

Overview and Topology

Power on the remaining switches (SWA-6 through SWA-9) in wiring closet B. The master can now detect that all members are present. Finally, for redundancy, configure an additional VCP uplink on SWA-7 through the master. The topology for this example consists of:

Three EX 4200-48P switches (SWA-0 , SWA-2, and SWA-4) in wiring closet A. Two EX 4200-48P switches (SWA-5 and SWA-9) in wiring closet B. Two EX 4200-24T switches (SWA-1 and SWA-3) in wiring closet A. Three EX 4200-24T switches (SWA-6, SWA-7, and SWA-8) in wiring closet B. Four EX-UM-2XFP uplink modules. Two are installed in wiring closet A and two are installed in wiring closet B.

Table 1 on page 4 shows the Virtual Chassis configuration settings for a preprovisioned Virtual Chassis composed of member switches in different wiring closets.
Table 1: Components of a Preprovisioned Virtual Chassis Interconnected Across Multiple Wiring Closets
Switch Serial number Member ID Role Uplink Ports xe-0/1/0 Hardware Location

SWA-0

abc123

routing-engine

EX 4200-48P and EX-UM-2XFP uplink module EX 4200-24T

Wiring closet A

SWA-1 SWA-2 SWA-3 SWA-4 SWA-5

def456 ghi789 jkl012 mno345 pqr678

1 2 3 4 5

linecard linecard linecard linecard routing-engine

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

Wiring closet A Wiring closet A Wiring closet A Wiring closet A Wiring closet B

EX 4200-48P EX 4200-24T EX 4200-48P EX 4200-48P and EX-UM-2XFP uplink module

NOTE: The member ID of SWA-5 is 0 at the time that its uplink port is configured as a VCP. SWA-6 SWA-7 SWA-8 SWA-9 stu901 vwx234 yza567 bcd890 6 7 8 9 linecard linecard linecard linecard
xe-7/1/0

EX 4200-24T EX 4200-24T EX 4200-24T EX 4200-48P

Wiring closet B Wiring closet B Wiring closet B Wiring closet B

Overview and Topology

Figure 1 on page 5 shows the different types of interconnections used for this Virtual Chassis configuration. The rear view shows that the member switches within each wiring closet are interconnected to each other using the dedicated VCPs. The front view shows that the uplink ports that have been set as VCPs and interconnected across the wiring closets. The uplink ports that are not set as VCPs can be configured as trunk ports to connect to a distribution switch.

NOTE: The interconnections shown in this figure are the same as they would be for a configuration that was not preprovisioned across wiring closets.

Figure 1: Maximum Size Virtual Chassis Interconnected Across Wiring Closets

Overview and Topology

Configuration
To configure the Virtual Chassis across multiple wiring closets using a preprovisioned configuration, perform these tasks:

NOTE: We recommend that you use the commit synchronize command to save any configuration changes that you make to a multimember Virtual Chassis configuration.
CLI Quick Configuration

To quickly configure SWA-0 with a preprovisioned configuration, copy the following commands and paste them into the switch terminal window:
[edit] set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis set virtual-chassis

preprovisioned member 0 serial-number member 1 serial-number member 2 serial-number member 3 serial-number member 4 serial-number member 5 serial-number member 6 serial-number member 7 serial-number member 8 serial-number member 9 serial-number

abc123 def456 ghi789 jkl012 mno345 pqr678 stu901 vwx234 yza567 bcd890

role role role role role role role role role role

routing-engine linecard linecard linecard linecard routing-engine linecard linecard linecard linecard

Step-by-Step Procedure

To create a preprovisioned configuration for the Virtual Chassis:

1.

Specify the preprovisioned configuration mode:

[edit virtual-chassis] user@SWA0# set preprovisioned

2.

Specify all the members that will be included in the Virtual Chassis configuration, listing each switch's serial number with the desired member ID and the desired role:
[edit virtual-chassis] user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA0# set member user@SWA-0# set member user@SWA0# set member

0 1 2 3 4 5 6 7 8 9

serial-number serial-number serial-number serial-number serial-number serial-number serial-number serial-number serial-number serial-number

abc123 def456 ghi789 jkl012 mno345 pqr678 stu901 vwx234 yza567 bcd890

role role role role role role role role role role

routing-engine linecard linecard linecard linecard routing-engine linecard linecard linecard linecard

3. 4.

Power on the member switches in wiring closet A. Prepare the members in wiring closet A for interconnecting with the member switches in wiring closet B by setting uplink VCPs for member 0 and member 2:
user@SWA-0>

request virtual-chassis vc-port

set pic-slot 1 port 0

Configuration

user@SWA-2> request virtual-chassis vc-port set pic-slot 1 port 0 member 2

NOTE: For redundancy, this example sets an uplink VCP interface in both SWA-0 and SWA-2.

This example omits the specification of the member0 in setting the uplink for SWA-0. The command applies by default to the switch where it is executed.

5.

Power on and connect to SWA-5. This switch comes up as member ID 0 and functions as master of itself. Although SWA-5 is listed in the preprovisioned configuration file, it is not a present member of the Virtual Chassis configuration that has been powered on thus far. In order for the master to detect SWA-5 as a connected member, you must first set an uplink VCP on SWA-5 and interconnect that VCP uplink with the VCP uplink of SWA-0. Set the first uplink of SWA-5 to function as a VCP interface. Because SWA-5 has been powered on as a separate switch and is still operating independently at this point, its member ID is 0.
user@SWA-5>request virtual-chassis vc-port set pic-slot 1 port 0

6.

NOTE: This example omits the specification of the member0 in configuring the uplink for SWA-5 (at this point the member ID of SWA-5 is still 0). The command applies by default to the switch where it is executed. Power off SWA-5 and connect the fiber cable from SWA-5 uplink port xe-0/1/0 to the uplink port xe-0/1/0 on SWA-0. Power on SWA-5. Now that SWA-5 has been brought up as member 5 of the Virtual Chassis configuration, power on the remaining switches (SWA-6 through SWA-9) in wiring closet B. They are interconnected with SWA-5 using the dedicated VCPs on the rear panel and are therefore detected by the master as interconnected members. If you check the status of the Virtual Chassis configuration at this point, all the members that were specified in the preprovisioned configuration file should be displayed as present. Additional configuration for member switches can now be done through the master switch. Set one uplink port of SWA-7 to function as a VCP:
user@SWA-0> request virtual-chassis vc-port set pic-slot 1 port 0 member 7

7. 8. 9.

10.

Configuration

Results

Display the results of the configuration on SWA-0:

[edit] user@SWA-0# show virtual-chassis { member 0 { role routing-engine; serial-number abc123; } member 1 { role linecard; serial-number def456; } member 2 { role linecard; serial-number ghi789; } member 3 { role linecard; serial-number jkl012; } member 4 { role linecard; serial-number mno345; } member 5 { role routing-engine; serial-number pqr678; } member 6 { role linecard; serial-number stu901; } member 7 { role linecard; serial-number vwx234; } member 8 { role linecard; serial-number yza567; } member 9 { role linecard; serial-number bcd890; } preprovisioned; }

Verification
To confirm that the configuration is working properly, perform these tasks:

Verifying the Member IDs and Roles of the Member Switches on page 9 Verifying That the Dedicated VCPs and Uplink VCPs Are Operational on page 10

Verification

Verifying the Member IDs and Roles of the Member Switches

Purpose Action

Verify that the member IDs and roles are all set as expected. Display the members of the Virtual Chassis configuration:
user@SWA-0> show virtual-chassis status Preprovisioned Virtual Chassis Virtual Chassis ID: 0000.e255.0000 Member ID 0 (FPC 0) Status Prsnt Serial No abc123 Model ex4200-48p Mastership Priority Role 129 Master* Neighbor List ID Interface 1 4 5 2 0 vcp-0 vcp-1 1/0 vcp-0 vcp1

1 (FPC 1)

Prsnt

def456

ex4200-24t

Linecard

2 (FPC 2)

Prsnt

ghi789

ex4200-48p

Linecard

3 1 7 4 2 0 3 6 9 0 7 5

vcp-0 vcp-1 1/0 vcp-0 vcp-1 vcp-0 vcp-1 vcp-0 vcp-1 1/0 vcp-0 vcp-1

3 (FPC 3)

Prsnt

jkl012

ex4200-24t

Linecard

4 (FPC 4)

Prsnt

mno345

ex4200-48p

Linecard

FPC 5)

Prsnt

pqr678

ex4200-48p

129

Backup

6 (FPC 6)

Prsnt

stu901

ex4200-24t

Linecard

7 (FPC 7)

Prsnt

vwx234

ex4200-24t

Linecard

8 6 2 9 7 5 8

vcp-0 vcp-1 1/0 vcp-0 vcp-1 vcp-0 vcp-1

8 (FPC 8)

Prsnt

yza567

ex4200-24t

Linecard

9 (FPC 9)

Prsnt

bc7890

ex4200-48p

Linecard

Meaning

The output shows that all members listed in the preprovisioned configuration file are connected to the Virtual Chassis configuration. It confirms that SWA-0 (member 0) is functioning as the master of the Virtual Chassis configuration, which was the intention of the configuration procedure. The other configured routing-engine (SWA-5) is functioning as the backup. The Neighbor List displays the interconnections of the member VCPs.

Verifying the Member IDs and Roles of the Member Switches

Verifying That the Dedicated VCPs and Uplink VCPs Are Operational
Purpose

Verify that the dedicated VCPs interconnecting the member switches within each wiring closet and the uplink VCPs interconnecting the member switches across wiring closets are operational. Display the Virtual Chassis interfaces:
user@SWA-0> show virtual-chassis vc-port all-members fpc0: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc1: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc2: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc3: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc4: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc5: Interface or PIC / Port vcp-0 vcp-1 1/0 Type Status

Action

Dedicated Dedicated Configured

Up Up Up

10

Verifying That the Dedicated VCPs and Uplink VCPs Are Operational

fpc6: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc7: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up 1/0 Configured Up fpc8: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up fpc9: -------------------------------------------------------------------------Interface Type Status or PIC / Port vcp-0 Dedicated Up vcp-1 Dedicated Up

Meaning

The dedicated VCPs interconnecting the member switches within wiring closets are displayed as vcp-0 and vcp-1. The uplink VCP ports interconnecting member switches (members 0, 2, 5 and 7) across wiring closets are displayed as 1/0 and 1/1 and identified as Configured.

Troubleshooting
To troubleshoot a preprovisioned Virtual Chassis configuration that is interconnected across wiring closets, perform these tasks:

Troubleshooting Nonoperational VCPs

Problem Solution Related Topics

A VCP interface shows a status of down. Check the cable to make sure that it is properly and securely connected to the ports.

Example: Configuring a Virtual Chassis with a Master and Backup in a Single Wiring Closet Example: Configuring a Virtual Chassis Interconnected Across Multiple Wiring Closets

Troubleshooting

11

Configuring a Virtual Chassis (CLI Procedure) Configuring a Virtual Chassis (J-Web Procedure)

12

Troubleshooting Nonoperational VCPs