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

Configuring a Mixed Virtual Chassis with EX4200, EX4500, and EX4550 Member Switches (CLI Procedure)

Ensure that all switches are running the same version of Junos OS. See Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

To configure a mixed Virtual Chassis:

1. Make a list of the serial numbers of all the switches to be connected in the Virtual Chassis. You can get the serial numbers in the show chassis hardware output or by following the instructions in Locating the Serial Number on an EX4200 Switch or Component, Locating the Serial Number on an EX4500 Switch or Component, or Locating the Serial Number on an EX4550 Switch or Component.
2. Decide which switches you want to act in the master and backup roles. See Understanding EX Series Virtual Chassis Components.
3. Power and log in to the switch that you want to function in the master role. If the switch has not previously been configured, configure it. See Connecting and Configuring an EX Series Switch (CLI Procedure).
4. Power and log in to the switch that you want to function in the backup role. If the switch has not previously been configured, configure it. See Connecting and Configuring an EX Series Switch (CLI Procedure).
5. Power on all other member switches.
6. (EX4500 switches only) Verify the PIC mode setting:
   user@switch> show chassis pic-mode
7. (EX4500 switches only) If the PIC mode was not set to Virtual Chassis mode, set the PIC mode to Virtual Chassis mode:
   user@switch> request chassis pic-mode virtual-chassis

   Note: This step is required if you are using the dedicated VCPs on the Virtual Chassis module to connect the Virtual Chassis. The PIC mode setting has no impact on optical ports that are configured as VCPs.

8. (Mixed Virtual Chassis with EX4200 switches only) Set the Virtual Chassis mode to mixed on all member switches if your mixed Virtual Chassis includes EX4200 switches:
   user@switch> request virtual-chassis mode mixed
9. If the PIC mode or the mixed mode was changed in step 7 or step 8, reboot each member switch:
   user@switch> request system reboot

   You can skip this step and proceed to step 11 if you did not change the PIC mode or the mixed mode.

10. After you have rebooted the switches, log into the switch that you powered on first. This switch is the master switch.
11. Run the EZSetup program on the master switch, specifying the identification parameters. See Connecting and Configuring an EX Series Switch (CLI Procedure).

    Note: The properties that you specify for the master switch apply to the entire Virtual Chassis.

12. (Optional) On the master switch, configure the virtual management Ethernet (VME) interface for out-of-band management of the Virtual Chassis, if desired:
    [edit]
user@switch# set interfaces vme unit 0 family inet address /ip-address/mask/
13. On the master switch, specify the preprovisioned configuration mode:
    [edit virtual-chassis]
user@switch# set preprovisioned

14. On the master switch, specify all members for the Virtual Chassis configuration, listing each switch’s serial number with the desired member ID and the desired role.

    Note: The routing-engine role can be assigned to any member switch, unless otherwise noted. The routing-engine role can be assigned to any member switch in a mixed Virtual Chassis starting in Junos OS Release 11.4. Ensure that you assign the routing-engine role to two members that are the same type of switch if you are running Junos OS Release 11.2 or 11.3.. Ensure that you assign only the routing-engine role to EX4500 member switches if you are running Junos OS Release 11.1.

    [edit virtual-chassis]
user@switch# set member 0 serial-number serial-number role routing-engine
user@switch# set member 1 serial-number serial-number role routing-engine
user@switch# set member 2 serial-number serial-number role line-card
user@switch# set member 3 serial-number serial-number role line-card
user@switch# set member 4 serial-number serial-number role line-card
user@switch# set member 5 serial-number serial-number role line-card
user@switch# set member 6 serial-number serial-number role line-card
user@switch# set member 7 serial-number serial-number role line-card
user@switch# set member 8 serial-number serial-number role line-card
user@switch# set member 9 serial-number serial-number role line-card
15. Interconnect the member switches by using either the dedicated VCPs on the member switches (see Connecting a Virtual Chassis Cable to an EX4200 Switch or Connecting a Virtual Chassis Cable to an EX4500 Switch) or by connecting them through the optical ports that you have configured as VCPs (see Setting an Uplink Port on an EX2200, EX3300, or EX4200 Switch as a Virtual Chassis Port (CLI Procedure) or Setting an Uplink Port as a Virtual Chassis Port on an EX4500 or EX4550 Switch (CLI Procedure)).

Note: You cannot modify the mastership priority when you are using a preprovisioned configuration. The mastership priority values are generated automatically and controlled by the role that is assigned to the member switch in the configuration file.

For information on adding a switch to an existing Virtual Chassis or configuring a Virtual Chassis port (VCP) to connect member switches over long distances, see Related Documentation.