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

Example: Configuring a Preprovisioned Mixed EX4200 and EX4500 Virtual Chassis

You can deterministically control both the role and the member ID assigned to each member switch in a mixed EX4200 and EX4500 Virtual Chassis configuration by creating a preprovisioned configuration.

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 mixed EX4200 and EX4500 Virtual Chassis using a preprovisioned configuration file:

Requirements

• Junos OS Release 11.1 or later for EX Series switches

  Note: You must use Junos OS Release 11.4 or later if you are including three or more EX4500 switches in an EX4500 Virtual Chassis or a mixed EX4200 and EX4500 Virtual Chassis.

• Two EX4500 switches, each with a Virtual Chassis module
• Two EX4200 switches

Overview and Topology

A preprovisioned configuration file links the serial number of each switch in the Virtual Chassis configuration to a specified member ID and role. The serial number must be specified in the configuration file for the member to be recognized as part of the Virtual Chassis configuration.

You designate additional members, which are not eligible for election as master, as having the line-card role in the preprovisioned configuration file.

In this example, two EX4500 switches (SWA-0 and SWA-1) are in the routing-engine role and interconnected to two EX4200 switches (SWA-2 and SWA-3) in the linecard role using dedicated Virtual Chassis ports (VCPs).

SWA-0 will 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 all member switches.

SWA-1 will be the backup of the Virtual Chassis configuration. Both SWA-0 and SWA-1 are specified in the preprovisioned configuration file with the role of routing-engine. All other members are specified with the role of line-card.

After all member switches are interconnected with their dedicated VCPs, you can simply power on the switches after saving and committing the preprovisioned configuration file. The master detects the connection of the members through the dedicated VCPs and applies the parameters specified in the preprovisioned configuration file.

Note: You can use interfaces on SFP, SFP+, and XFP uplink modules as VCPs. When an uplink module port or SFP network port is set as a VCP, it cannot be used for any other purpose.

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.

The topology for this example consists of:

• Two EX4500 switches (SWA-0 and SWA-1)
• Two EX4200 switches (SWA-2 and SWA-3)

Table 1 shows the Virtual Chassis configuration settings for a preprovisioned Virtual Chassis.

Configuration

To configure the Virtual Chassis across multiple wiring closets using a preprovisioned configuration, perform this task:

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

Step-by-Step Procedure

1. Power on the EX4500 switch (SWA-0)in the master role..
2. Set the PIC mode to Virtual Chassis mode on SWA-0:
   user@switch> request chassis pic-mode virtual-chassis
3. Set the Virtual Chassis mode to mixed:
   user@switch> request virtual-chassis mode mixed
4. Reboot the switch.
5. After the switch reboots, specify the preprovisioned configuration mode:
   [edit virtual-chassis]
user@SWA–0# set preprovisioned

6. Specify all members to 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@SWA–0# set member 0 serial-number abc123 role routing-engine
user@SWA–0# set member 1 serial-number def456 role line-card
user@SWA–0# set member 2 serial-number ghi789 role line-card
user@SWA–0# set member 3 serial-number jkl012 role line-card

7. Power on the remaining switches.
8. Set the Virtual Chassis mode to mixed on the remaining switches:
   user@switch> request virtual-chassis mode mixed
9. Reboot the switches.
10. When the reboot completes, physically cable the switches together using the dedicated VCPs.

Results

Display the results of the configuration on SWA-0:

Verification

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

• Verifying the Member IDs and Roles of the Member Switches

Verifying the Member IDs and Roles of the Member Switches

Purpose

Verify that the member IDs and roles are all set as expected.

Action

Display the members of the Virtual Chassis configuration:

Preprovisioned Virtual Chassis
Virtual Chassis ID: 0000.e255.0000

                                            Mastership          Neighbor List
Member ID  Status   Serial No    Model      Priority  Role      ID  Interface

0 (FPC 0)  Prsnt    abc123       ex4500-40f      129  Master*    1 vcp-1
                                                                 3 vcp-0
                                                                 
1 (FPC 1)  Prsnt    def456       ex4500-40f        0  Backup     0 vcp-0
                                                                 2 vcp-1

2 (FPC 2)  Prsnt    ghi789       ex4200-48p        0  Linecard   1 vcp-0
                                                                 3 vcp-1
                                                                

3 (FPC 3)  Prsnt    jkl012       ex4200-24t        0  Linecard   2 vcp-0
                                                                 0 vcp-1

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. The other switch configured with the routing-engine role (SWA-1) is functioning as the backup. The Neighbor List displays the interconnections of the member VCPs.

Troubleshooting

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

• Troubleshooting Nonoperational VCPs

Troubleshooting Nonoperational VCPs

Problem

A VCP shows a status of down.

Solution

Check the cable to make sure that it is properly and securely connected to the ports.