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 Long-Distance Virtual Chassis Port Connection for an EX8200 Virtual Chassis

This procedure describes how to connect XRE200 External Routing Engine to EX8200 switch connections over long distances in an EX8200 Virtual Chassis only.

You can connect XRE200 External Routing Engines together over distances up to 43.5 miles (70 km) within an EX8200 Virtual Chassis using the 1000BASE-X SFP Virtual Chassis Control Interface (VCCI) module ports. No software configuration is needed to make these connections.

You can connect EX8200 switches together over longer distances within an EX8200 Virtual Chassis by configuring a 10-Gigabit Ethernet port as a Virtual Chassis port (VCP). See Setting a 10-Gigabit Ethernet Port as a Virtual Chassis Port in an EX8200 Virtual Chassis (CLI Procedure).

You can connect an XRE200 External Routing Engine to an EX8200 switch to form a Virtual Chassis over a longer distance by using an intermediary switch. The intermediary switch should be located within 328 feet (100 meters) of the EX8200 member switch to ensure a Gigabit Ethernet connection to the management port (labeled MGMT) can be made. The intermediary switch is required because an SFP connection from an external Routing Engine cannot directly connect to the management port of an EX8200 switch. Virtual Chassis Control Protocol (VCCP) traffic traversing the intermediary switches must be placed into VLANs to ensure it is directed to the correct destination.

This procedure shows how to connect two XRE200 External Routing Engines to two EX8200 member switches together over a long-distance connection.

Ensure that you have the following parts and tools available:

• Two XRE200 External Routing Engines, each with at least one installed 1000BASE-X SFP VCCI module
• Two EX8200 switches
• Two EX Series switches

  Note: Any EX Series switch can be used as an intermediary switch in an EX8200 Virtual Chassis. The most affordable EX Series switch is an EX2200 switch with 24 total ports and no Power over Ethernet (PoE) ports (model number EX2200-24T-4G). If you need to purchase a new switch to extend a VCP for an EX8200 Virtual Chassis, we recommend purchasing this switch with an SFP uplink module that supports the same SFPs as an XRE200 External Routing Engine and an SFP cable whose length is appropriate for your environment. The EX2200 switch supports uplink modules with SFP connections that span up to 43.5 miles (70 km). See Optical Interface Support in EX2200 Switches and Optical Interface Support in XRE200 External Routing Engines for information on supported optical uplinks.

The EX Series switches used as intermediary switches in this procedure must be dedicated to this task. These switches cannot receive or forward any other network traffic.

Figure 1 provides a diagram of the XRE200 External Routing Engine-to-EX8200 switch long-distance connections in the EX8200 Virtual Chassis. The diagram shows the physical and VLAN setup of the Virtual Chassis.

Figure 1: Long Distance EX8200 Virtual Chassis

1. Cable the devices. The following connections must be cabled:

   VLAN 1:

   • SFP VCP on the master XRE200 External Routing Engine connected to intermediary switch 0.
   • Gigabit Ethernet port on intermediary switch 0 to the management port (labeled MGMT) on the master Switch Fabric and Routing Engine (SRE) module or Routing Engine (RE) module on the EX8200 member switch ID 0.

   VLAN 2:

   • SFP VCP on the master XRE200 External Routing Engine connected to intermediary switch 1.
   • Gigabit Ethernet port on intermediary switch 1 to the management port (labeled MGMT) on the master SRE module or RE module on the EX8200 member switch ID 1.

   VLAN 3:

   • SFP VCP on the backup XRE200 External Routing Engine connected to intermediary switch 0.
   • Gigabit Ethernet port on intermediary switch 0 to the management port (labeled MGMT) on the backup SRE module or RE module on the EX8200 member switch ID 0.

   VLAN 4:

   • SFP VCP on the backup XRE200 External Routing Engine connected to intermediary switch 1.
   • Gigabit Ethernet port on intermediary switch 1 to the management port (labeled MGMT) on the backup SRE module or RE module on the EX8200 member switch ID 1.
2. Configure the VLANs on the intermediary switches. Each VLAN must contain the interface on the intermediary switch connecting to the XRE200 External Routing Engine and the interface connecting to the EX8200 member switch.

   Note: You only need to configure the VLANs on the intermediary switches. You do not need to place any interfaces on the XRE200 External Routing Engine or on the EX8200 member switches into the VLANs.

   VLAN 1:

   user@switch-0# set vlans vcp-vlan-1 interface ge-0/1/0

   user@switch-0# set vlans vcp-vlan-1 interface ge-0/0/0

   VLAN 2:

   user@switch-1# set vlans vcp-vlan-2 interface ge-0/1/0

   user@switch-1# set vlans vcp-vlan-2 interface ge-0/0/0

   VLAN 3:

   user@switch-0# set vlans vcp-vlan-3 interface ge-0/1/1

   user@switch-0# set vlans vcp-vlan-3 interface ge-0/0/1

   VLAN 4:

   user@switch-1# set vlans vcp-vlan-4 interface ge-0/1/1

   user@switch-1# set vlans vcp-vlan-4 interface ge-0/0/1
3. Set the maximum transmission units (MTU) value on all interfaces on both intermediary switches transmitting VCCP traffic to 3000 bytes or more.

   On switch 0:

   user@switch-0# set interfaces ge-0/0/0 mtu 3000

   user@switch-0# set interfaces ge-0/0/1 mtu 3000

   user@switch-0# set interfaces ge-0/1/0 mtu 3000

   user@switch-0# set interfaces ge-0/1/1 mtu 3000

On switch 1: