EVPN-VXLAN to EVPN-MPLS stitching
For full configuration eample of EVPN-VXLAN to EVPN-MPLS stitching refer to MX Layer 2 VPNs Feature Guide, Chapter 28.
First of all, you need to configure Logical Tunnel (lt-) interface for traffic between EVPN-VXLAN and EVPN-MPLS instances:
esi {
36:36:36:36:36:36:36:36:36:36;
all-active;
}
unit 3 {
encapsulation ethernet-bridge;
peer-unit 4;
family bridge {
interface-mode trunk;
vlan-id-list [ 51 52 ];
}
}
unit 4 {
encapsulation ethernet-bridge;
peer-unit 3;
family bridge {
interface-mode trunk;
vlan-id-list [ 51 52 ];
}
}
}
You need to configure ES ID and type only in case of redundant stitching points – if you stitch two EVPN domains on two MX boxes, then you need to configure same ESI on every participating lt- interface (from each EVPN domain point of view – lt- interface is just another CE-facing interface, nothing special; if you fave more than one CE facing interface you need to apply standart procedures to configure All-Active Ethernet Segment).
After this, there is nothing special left to do – just standart EVPN-VXLAN configuration:
vtep-source-interface lo0.0;
instance-type virtual-switch;
interface lt-1/0/10.4
route-distinguisher 101:1;
vrf-target target:1:1;
protocols {
evpn {
encapsulation vxlan;
extended-vni-list all;
}
}
bridge-domains {
bd1 {
domain-type bridge;
vlan-id 51;
routing-interface irb.0;
vxlan {
vni 51;
encapsulate-inner-vlan;
decapsulate-accept-inner-vlan;
ingress-node-replication;
}
}
bd2 {
domain-type bridge;
vlan-id 52;
routing-interface irb.1;
vxlan {
vni 52;
encapsulate-inner-vlan;
decapsulate-accept-inner-vlan;
ingress-node-replication;
}
}
}
}
and EVPN-MPLS configuration:
instance-type virtual-switch;
interface lt-1/0/10.3;
route-distinguisher 101:2;
vrf-target target:2:2;
protocols {
evpn {
extended-vlan-list 51-52;
}
}
bridge-domains {
bd1 {
domain-type bridge;
vlan-id 51;
}
bd2 {
domain-type bridge;
vlan-id 52;
}
}
}
Note lt- interface assignment and extended-vlan/vni configuration.