MX EVPN-MPLS basic config
Short notes about MX EVPN-MPLS configuration.
Vlan-based configuration:
routing-instances {
EVPN-1 {
instance-type evpn;
vlan-id 100;
interface ae0.100;
routing-interface irb.100;
route-distinguisher 11.11.11.11:1;
vrf-target target:65000:1;
protocols {
evpn {
default-gateway do-not-advertise;
}
}
}
}
interfaces {
irb {
unit 100 {
family inet {
address 100.1.1.1/24;
}
mac 00:00:00:01:01:01;
}
}
}
EVPN-1 {
instance-type evpn;
vlan-id 100;
interface ae0.100;
routing-interface irb.100;
route-distinguisher 11.11.11.11:1;
vrf-target target:65000:1;
protocols {
evpn {
default-gateway do-not-advertise;
}
}
}
}
interfaces {
irb {
unit 100 {
family inet {
address 100.1.1.1/24;
}
mac 00:00:00:01:01:01;
}
}
}
Vlan-aware configuration:
routing-instances {
EVPN-2 {
instance-type virtual-switch;
interface ae0.200;
route-distinguisher 11.11.11.11:2;
vrf-target target:65000:2;
protocols {
evpn {
extended-vlan-list 200-202;
default-gateway advertise;
}
}
bridge-domains {
V200 {
vlan-id 200;
routing-interface irb.200;
}
V201 {
vlan-id 201;
routing-interface irb.201;
}
V202 {
vlan-id 202;
routing-interface irb.202;
}
}
}
}
EVPN-2 {
instance-type virtual-switch;
interface ae0.200;
route-distinguisher 11.11.11.11:2;
vrf-target target:65000:2;
protocols {
evpn {
extended-vlan-list 200-202;
default-gateway advertise;
}
}
bridge-domains {
V200 {
vlan-id 200;
routing-interface irb.200;
}
V201 {
vlan-id 201;
routing-interface irb.201;
}
V202 {
vlan-id 202;
routing-interface irb.202;
}
}
}
}
I think that Vlan-based configuration should never be used – just always configure Vlan-aware style, even for one VLAN.
Note extended-vlan-list for EVPN-MPLS (instead of extended-vni-list for EVPN-VXLAN).
Configuration of IRB intefaces and default-gateway community is pretty complex topic, I plan to write separate post about it.