EVPN-VXLAN and EVPN-MPLS Interworking

VXLAN and SR-MPLS are two of the most popular transport technologies used in Data Center (DC) and Wide-Area Network (WAN) environments. As a result, gateway interworking scenarios are relevant for Data Center Interconnect (DCI), Hybrid Cloud Integration (HCI), and service provider networks. The aim is to provide a unified solution for extending Ethernet services across different transport networks, such as VXLAN in data center environments and SR-MPLS in wide-area or carrier networks. Interworking these transport technologies enables seamless connectivity, scalability, and flexibility in modern networks, ensuring optimal service delivery across diverse infrastructures.
In our first run, we used a multihomed EVPN-SR-MPLS and EVPN-VXLAN gateway, during which we configured the Interconnect Ethernet Segment (I-ES) and the Interconnect Ethernet Segment Identifier (I-ESI) on the DUT. In this run, we did not utilize the domain path (D-path) attribute. We sent bi-directional unicast traffic from the left VXLAN domain to the right VXLAN domain through the SR-MPLS domain in the middle, focusing solely on Layer 2 bridging traffic. Ultimately, we observed no packet loss or duplication during this process.

In the second run, we simplified the topology from the first run and enabled D-path. The BGP Domain PATH (D-PATH) attribute is defined for Inter-Subnet Forwarding (ISF) BGP Sub-Address Families that advertise IP prefixes. When used along with EVPN IP Prefix routes or IP-VPN routes, it identifies the domain(s) through which the routes have passed, and that information can be used by the receiver BGP speakers to detect routing loops or influence the BGP best path selection. We sent bi-directional unicast traffic from the left VXLAN domain to the right SR-MPLS domain, focusing exclusively on Layer 3 routing traffic. Again, we observed no packet loss or duplication.
Spirent TestCenter was used as the traffic generator for this test.