Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Adding a New EX4200 Switch to an Existing EX4200 Virtual Chassis (CLI Procedure)

 

This topic explains how to add an EX4200 switch to an existing EX4200 Virtual Chassis. For information about adding an EX4200 switch to an EX4500 Virtual Chassis or a mixed Virtual Chassis, see Adding an EX4200 Switch to a Preprovisioned EX4500 Virtual Chassis or a Preprovisioned Mixed EX4200 and EX4500 Virtual Chassis (CLI Procedure).

To add an EX4200 switch to an existing EX4200 Virtual Chassis, use the procedure that matches what you need to accomplish:

Adding a New Switch to an Existing Virtual Chassis Within the Same Wiring Closet

This procedure can be used to add an EX4200 switch to an EX4200 Virtual Chassis.

Before you begin, be sure you have:

  • Mounted the new switch in a rack.

  • Confirmed that the new switch is powered off.

  • If you are expanding a preprovisioned configuration, made a note of the serial number (the number is on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch.

  • If you are expanding a preprovisioned configuration, edited the existing Virtual Chassis configuration to include the serial number of the new member switch. The parameters specified in the master Virtual Chassis configuration file are applied to the new switch after it has been interconnected to an existing member switch.

    Note

    After you have created a preprovisioned Virtual Chassis configuration, you can use the autoprovisioning feature to add member switches to that configuration.

  • (Optional) Configured Ethernet interfaces on different member switches into the same LAG.. See Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch

    An active member switch might temporarily go down before coming back up as part of this procedure. Having traffic load-balanced across member switches using a LAG helps alleviate traffic loss during this procedure.

To add a new member switch to an existing Virtual Chassis configuration within the same wiring closet:

  1. If the new member switch has been previously configured, revert that switch’s configuration to the factory defaults. See Reverting to the Default Factory Configuration for the EX Series Switch.
  2. Interconnect the unpowered new switch to one member of the existing Virtual Chassis configuration using the dedicated Virtual Chassis ports (VCPs). Connect only one VCP on the unpowered new switch to a VCP on a member switch in the existing Virtual Chassis at this point of the procedure.
  3. Power on the new switch.
  4. Confirm that the new member switch is now included within the Virtual Chassis configuration by checking the front-panel LCD for the member ID. It should display a member ID that is greater than 0 (1 through 9), because there is already at least one member of the Virtual Chassis configuration.Note

    If you are using a preprovisioned configuration, the member ID is automatically assigned to the member’s serial number in the configuration file.

  5. Cable the other dedicated VCP on the new member switch to the Virtual Chassis.Caution

    If you immediately cable both VCPs on the new switch into the existing Virtual Chassis at the same time, a member switch that was already part of the Virtual Chassis might become nonoperational for several seconds. Network traffic to this switch is dropped during the downtime.

    The member switch will return to the normal operational state with no user intervention, and normal operation of the Virtual Chassis will resume after this downtime.

Adding a New Switch from a Different Wiring Closet to an Existing Virtual Chassis

This procedure can be used to add an EX4200 switch to an EX4200 Virtual Chassis from a different wiring closet to an existing Virtual Chassis.

To add a new switch from a different wiring closet to an existing Virtual Chassis configuration, you must use a long cable to connect the members switches across wiring closets. You can use any SFP, SFP+, or XFP port and a fiber-optic cable for this purpose.

Before you begin, be sure you have:

  • Installed the uplink modules needed for the Virtual Chassis configuration. See Installing an Uplink Module in an EX4200 Switch.

  • Mounted the new switch in a rack.

  • If the new member switch has been previously configured, reverted its configuration to the factory defaults. See Reverting to the Default Factory Configuration for the EX Series Switch.

  • If you are expanding a preprovisioned configuration, made a note of the serial number (the number is on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch.

  • If you are expanding a preprovisioned configuration, edited the existing Virtual Chassis configuration to include the serial number of the new member switch. You can specify the role of the new member switch when you add its serial number in the Virtual Chassis configuration file. The parameters specified in the master Virtual Chassis configuration file are applied to the new switch after it has been interconnected with its uplink VCP to an existing member switch.

    Note

    After you have created a preprovisioned Virtual Chassis configuration, you can use the autoprovisioning feature to add member switches to that configuration.

To add a new member switch that is going to be interconnected with the existing Virtual Chassis configuration across wiring closets:

  1. Power on the new switch.
  2. Connect a laptop or terminal to the console port of the switch, or use EZSetup on the LCD Panel of the standalone switch to specify temporary identification parameters. (When you interconnect the new member switch with the existing Virtual Chassis configuration, the master will overwrite and disable any specified parameters that conflict with the Virtual Chassis parameters or assigned member configuration.)
  3. Use the CLI or the J-Web interface to set one uplink module port as a VCP:
    user@switch> request virtual-chassis vc-port set pic-slot 1 port 0
    Note

    If you are using a nonprovisioned configuration, you might configure the new member switch with a mastership priority value that is less than that of the existing member switches. Doing so ensures that the new member switch will function in a linecard role when it is included within the Virtual Chassis configuration.

  4. Power off the new switch.
  5. Interconnect the new member switch to one existing member switch in the Virtual Chassis configuration using one of the uplink module ports that you has configured as a VCP. Connect only one VCP on the unpowered new switch to a VCP on a member switch in the existing Virtual Chassis at this point of the procedure.
  6. Power on the new member switch.
  7. Confirm that the new member switch is now included within the Virtual Chassis configuration by checking the front-panel LCD for the member ID. It should display a member ID that is greater than 0 (1 through 9), because there is already at least one member of the Virtual Chassis configuration.Note

    If you are using a preprovisioned configuration, the member ID is automatically assigned to the member's serial number in the configuration file.

  8. Cable another user-configured VCP on the new member switch to the Virtual Chassis, if desired.Caution

    If you immediately cable both VCPs on the new switch into the existing Virtual Chassis at the same time, a member switch that was already part of the Virtual Chassis might become nonoperational for several seconds. Network traffic to this switch is dropped during the downtime.

    The member switch will return to the normal operational state with no user intervention, and normal operation of the Virtual Chassis will resume after this downtime.

Adding a New Switch to an Existing Preprovisioned Virtual Chassis Using Autoprovisioning and Automatic VCP Conversion

This procedure can be used to add an EX4200 switch to an existing EX4200 Virtual Chassis using autoprovisioning, where after the new switch is provisioned and cabled into the Virtual Chassis, the interconnecting links automatically convert into VCP links.

Before you begin, be sure you have:

  • Installed the uplink modules needed for the Virtual Chassis configuration.

  • Mounted the new switch in a rack.

  • Ensured that the preprovisioned Virtual Chassis configuration has an active master. For more information, see Example: Configuring an EX4200 Virtual Chassis Using a Preprovisioned Configuration File.

  • On the master, configured the Link Level Discovery Protocol (LLDP) on the uplink module ports that will be used as VCPs. LLDP is configured by default but might have been disabled. Both sides of the new links exchange LLDP messages to accomplish automatic VCP conversion. To configure LLDP, see Configuring LLDP (CLI Procedure).

  • Ensured that the new member switch has the factory-default configuration. If the new member switch has been previously configured, revert its configuration to the factory defaults. See Reverting to the Default Factory Configuration for the EX Series Switch.

  • Made a note of the serial number (the number is on the back of the switch). You will need to edit the Virtual Chassis configuration to include the serial number of the new member switch.

  • Edited the existing Virtual Chassis preprovisioned configuration to include the serial number of the new member switch. The parameters specified in the master Virtual Chassis configuration file are applied to the new member switch after it has been interconnected through its uplink VCP to an existing member switch.

  • Prepared an existing member switch to interconnect with the new switch through an uplink module port by ensuring that port is not set as a VCP. One of the conditions for automatic VCP conversion to be invoked is that the ports on both sides of the new link must not already be configured as VCPs.

    Caution

    When automatic VCP conversion is enabled in a Virtual Chassis with switches that have dedicated VCPs (EX4200, EX4500, or EX4550 Virtual Chassis), if network or uplink ports are automatically converted into VCPs to create a redundant link with a dedicated VCP connection between the same two Virtual Chassis members, you must reboot the Virtual Chassis to avoid creating a traffic loop within the Virtual Chassis. (The same issue can occur even if the ports are manually converted into VCPs to create the redundant VCP link with a dedicated VCP link, so the reboot is required to avoid traffic looping in that case as well.)

  • Ensured that the operational modes of the uplink modules on the existing member switch and the new member switch match.

  • Confirmed that the new member switch is powered off.

If the preceding conditions are not met, autoprovisioning will not work and you will need to manually configure uplink module ports on the switch to be added to the configuration to be VCPs. For more information, see Setting an Uplink Port on an EX Series or QFX Series Switch as a Virtual Chassis Port.

To add a switch to an existing preprovisioned Virtual Chassis configuration using the autoprovisioning feature:

  1. Interconnect the unpowered new switch to one member of the existing Virtual Chassis configuration. Only connect one VCP on the unpowered new switch to a VCP on a member switch in the existing Virtual Chassis at this point of the procedure.
  2. Power on the new member switch.
  3. Confirm that the new member switch is now included in the Virtual Chassis configuration by checking the front-panel LCD for the member ID. It should display a member ID in the range from 0 through 9. The member ID is automatically assigned to the new member switch's serial number in the configuration file.
  4. Cable the other VCP on the new member switch to the Virtual Chassis.Caution

    If you immediately cable both VCPs on the new switch into the existing Virtual Chassis at the same time, a member switch that was already part of the Virtual Chassis might become nonoperational for several seconds. Network traffic to this switch is dropped during the downtime.

    The member switch will return to the normal operational state with no user intervention, and normal operation of the Virtual Chassis will resume after this downtime.