Configuring Seamless Type-5 to Type-5 Stitching for EVPN-VXLAN
Seamless stitching of EVPN Type 5 routes is beneficial in multi-POD data center architectures, or Data Center Interconnect (DCI) using pure Type 5 routing. It reduces the number of Type 5 tunnels between border-leaf or border-spine devices.
This article contains the configuration necessary for implementing seamless stitching of Type 5 routes between data center PODs. We support a 1:1 VRF instance mapping, meaning that a single VRF instance on the local data center gateway maps to another VRF instance on the remote gateway.
Topology
The following diagram shows two data center PODs connected over a WAN. The two data centers are configured using edge-routed bridging (ERB).
Configuration Overview
The following steps show the relevant configuration to implement pure EVPN Type 5 routing between stitched data centers. Each data center POD will have a local EVPN-VXLAN overlay fabric, and utilize EVPN DCI across the WAN to the remote data center POD.
Devices within the same POD will use MAC-VRF instances for the EVPN-VXLAN overlay fabric. Gateway devices will additionally use a Layer 3 VRF instance for the Type 5 DCI across the WAN. Our example focuses on the gateway device overlay configuration. The underlay can use multiple options. See Understanding EVPN with VXLAN Data Plane Encapsulation for details.
Configure a MAC-VRF Instance
Configure the MAC-VRF for GW11. Here we're using the
vlan-awareservice. You might alternately configurevlan-basedservice orvlan-bundleservice. See Overview of VLAN Services for EVPN for additional information about these service types.user@GW11#set routing-instances <instance-name> instance-type mac-vrf
Configure the EVPN protocol with VXLAN encapsulation.
user@GW11#set routing-instances <instance-name> protocols evpn encapsulation vxlan set routing-instances <instance-name> protocols evpn default-gateway do-not-advertise
Configure a VXLAN tunnel endpoint (VTEP) interface (such as the lo0 interface), the aforementioned service type, one or more VLAN-tagged interfaces, and a router distinguisher and VRF target unique to this MAC-VRF instance.
user@GW11#set routing-instances <instance-name> vtep-source-interface interface set routing-instances <instance-name> service-type vlan-aware set routing-instances <instance-name> interface <interface> set routing-instances <instance-name> route-distinguisher <value> set routing-instances <instance-name> vrf-target target:<value>
Configure the bridge domain used for the EVPN interconnection. See Configuring a Bridge Domain for more details. That reference page also includes important information regarding the use of the
routing-instances <instance-name> bridge-domainshierarchy, or therouting-instances <instance-name> vlanshierarchy.user@GW11#set routing-instances <instance-name> bridge-domains <name> vlan-id <vlan-id> set routing-instances <instance-name> bridge-domains <name> interface <interface> set routing-instances <instance-name> bridge-domains <name> routing-interface <irb interface> set routing-instances <instance-name> bridge-domains <name> vxlan vni <value>
Configure a Layer 3 VRF Instance
Configure the Layer 3 VRF instance for GW11, including a route distinguisher and VRF target unique to this VRF instance.
user@GW11#set routing-instances <instance-name> instance-type vrf set routing-instances <instance-name> routing-options multipath set routing-instances <instance-name> interface interface set routing-instances <instance-name> route-distinguisher <value> set routing-instances <instance-name> vrf-target target:<value> set routing-instances <instance-name> vrf-table-label
Configure the EVPN interconnect, including a route distinguisher and VRF target unique to the interconnect configuration.
user@GW11#set routing-instances <instance-name> protocols evpn interconnect vrf-target target:<value> set routing-instances <instance-name> protocols evpn interconnect route-distinguisher <value>
Configure Type 5 advertisements using the
ip-prefix-routesstatement.Thevnistatement maps VLAN's across the interconnect. The VNI here must be unique to theip-prefix-routesconfiguration.user@GW11#set routing-instances <instance-name> protocols evpn ip-prefix-routes advertise direct-nexthop set routing-instances <instance-name> protocols evpn ip-prefix-routes encapsulation vxlan set routing-instances <instance-name> protocols evpn ip-prefix-routes vni <vni>
Domain Path ID
You can optionally configure the domain-path-id statement as part of your
DCI Type 5 stitching implementation. This configuration helps to prevent Type 5 routing
loops. The domain-path-id statement is configured in the protocols
evpn interconnect stanza. See domain-path-id for more details.
set protocols evpn interconnect domain-path-id <domain-id-string>
Release Information
Support for Advanced Forwarding Toolkit (AFT)-based linecards on supported MX Series routers introduced in Junos OS Release 25.2R1.