EVPN

EVPN-VXLAN to EVPN-VXLAN seamless stitching for EVPN Type 5 routes (ACX7100-32C, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.4R1, you can configure EVPN-VXLAN to EVPN-VXLAN seamless stitching with EVPN Type 5 (IP prefix) routes between two interconnected data centers or between two points of delivery (pods) in a data center.

In the EVPN-VXLAN fabric, border leaf or border spine devices act as interconnection gateways. You enable EVPN Type 5 routes in virtual routing and forwarding (VRF) instances on both sides of the interconnection. For each VRF instance, the server leaf devices in the first data center create VXLAN tunnels for Type 5 routes (with corresponding VXLAN network identifiers [VNIs]) toward their local gateway devices. The gateway devices map those VXLAN tunnels to an interconnection tunnel (with a new route distinguisher [RD], route target, and VNI) toward the second data center. The gateway devices in the second data center re-create the Type 5 VXLAN tunnels using their local RD.

We support one-to-one mapping of Type 5 VRF instances across the interconnection.

Overlay and CE-IP ping and traceroute support for EVPN-VXLAN (ACX7100-32C, ACX710048L, PTX10001-36MR, PTX10004, PTX10016, QFX5130-32CD, and QFX5700)—Starting in Junos OS Evolved Release 22.4R1, you can perform ping and traceroute operations within an EVPN-VXLAN overlay or to a specific customer edge [CE] device IP address (CE-IP) across an EVPN-VXLAN overlay. You can use ping and traceroute and CE-IP ping and traceroute utilities to detect and isolate faults in overlay networks.

[See Understanding Overlay ping and traceroute Packet Support.]

Loop detection for EVPN-VXLAN fabrics (ACX7100-32C, ACX7100-48L)—Support for configuration of loop detection on the server-facing Layer 2 interfaces of the leaf devices in an EVPN-VXLAN fabric. This feature can detect the following types of Ethernet loops:

• A loop between two interfaces with different Ethernet segment identifiers (ESIs). This loop is typically caused by miswiring fabric components.
• A loop between two interfaces with the same ESI. This loop is typically caused by miswiring a third-party switch to the fabric.

  [See EVPN User Guide, loop detect, and show loop-detect enhanced interface command.]