Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configure EVPN-VXLAN Data Center Stitching Through Interconnected EVPN-MPLS WAN Gateways

You can seamlessly stitch Ethernet VPN Virtual Extensible LAN (EVPN-VXLAN) data centers through WAN gateway devices running EVPN-MPLS.

This article outlines the configuration necessary to stitch an EVPN-VXLAN data center to another EVPN-VXLAN data center, while traversing an EVPN-MPLS WAN fabric. Your WAN could be geographically dispersed or local to the same data center where the EVPN-VXLAN points of delivery (PODS) reside. See RFC 9014.

Topology

The following diagram shows two EVPN-VXLAN data centers connected through an EVPN-MPLS WAN, using the gateway model. Each gateway is configured with an EVPN MAC-VRF routing instance. Each MAC-VRF instance uses VXLAN encapsulation, and the interconnect within each MAC-VRF instance uses MPLS encapsulation.

EVPN-VLXAN through EVPN-MPLS WANTopology

Configuration

Follow the steps below to configure a pair of gateways. We'll show the relevant configuration for DC1 Spine1 and DC2 Spine1. Full device configurations are beyond the scope of this document.

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

  1. Configure a MAC VRF routing instance.
  2. Configure the EVPN protocol.
  3. Configure VXLAN encapsulation and supporting elements.
  4. Configure the interconnect statement and supporting elements.
  5. Based on the platform you're configuring, set these platform-specific options as required:

    • (QFX5120 switches) You are required to configure the following to enable Layer 2 stitching:

      The packet forwarding engine (PFE) restarts when you apply this configuration, and the associated FPC and interfaces restart. See the evpn-vxlan statement page for more information on the vxlan-trans-vni-enable option.

    • (ACX Series routers) You are required to configure the following on ACX Series routers to support an IPv6 underlay:

      Refer to vxlan-extended for additional information.

    • (ACX Series routers) You are required to configure the following to enable Layer 2 stitching. The PFE restarts when you apply this configuration.

      Refer to vxlan-stitching for additional details related to control-word support in EVPN-VXLAN and EVPN-MPLS environments, and further ACX requirements.

    • (ACX Series routers) You can configure the following parameters to enable load balancing based on traffic payload:

      Refer to hash-key (Forwarding Options) for additional information and requirements related to ACX Series and PTX Series devices.

    • (ACX Series routers) For features such as EVPN-VXLAN, if you have a requirement for a higher Layer 2 MAC scale, then we recommend that you migrate to the “cloud-metro” profile. You set this profile at the [edit system packet-forwarding-options hw-db-profile] hierarchy level. ACX7024 devices support only the lean-edge and cloud-metro profile options. Refer to hw-db-profile for more information and ACX Series router requirements for these profile options.

  6. Configure the interconnect Ethernet segment identifier (ESI) and supporting elements.
  7. Configure additional elements of the MAC-VRF instance.
  8. Configure VLANs.
See the following example configuration for DC1 Spine1. Change any values to match your existing network.See the following example configuration for DC2 Spine1. Change any values to match your existing network.
Note:

For multihomed gateway devices, you must include the following statement at the global level:

set protocols evpn interconnect-multihoming-peer-gateways VTEP-IP-of-each-DCI-GW-peer-in-local-DC

You can't configure the above statement within a routing instance.

Also, the statement interconnect-multihoming-peer-gateways is renamed in Junos OS Release 24.2R1 to multihoming-peer-gateways to support identifying multihoming peer devices in multiple use cases. Starting in Junos OS and Junos OS Evolved Release 24.4R1, we restored the interconnect-multihoming-peer-gateways statement name specifically for the interconnect use case. We've implemented other statements for other feature use cases too, and you won't see the multihoming-peer-gateways statement in the Junos OS CLI anymore.

A full discussion of multihoming is beyond the scope of this document. For more about multihoming, see EVPN Multihoming Overview.

Verification

Confirm that routes are showing in mpls.0.

Confirm that VXLAN VNI's are populating in the EVPN database.

Confirm MAC table entries for an IRB.