EVPN – Single-active redundancy
In the previous 2 posts I looked at the basics of EVPN including the new BGP based control-plane, later I looked at the integration between the layer-2 and layer-3 worlds within EVPN. However – all the previous examples were shown with basic single site networks with no link or device redundancy, this this post I’m going to look at the first and simplest EVPN redundancy mode.
First – consider the new lab topology:

The topology and configuration remains pretty much the same, except that MX-1 and MX-2 each connect back to EX4200-1, for VLAN 100 and VLAN 101, with the same IRB interfaces present on each MX router, essentially a very basic site with 2 PEs for redundancy.
Let’s recap the EVPN configuration on each MX1, I’ve got the exact same configuration loaded on MX-2 and MX-3, the only differences being the interface numbers and a unique RD for each site.
MX-1:
-
tim@MX5-1> show configuration routing-instances
-
EVPN-100 {
-
instance-type virtual-switch;
-
route-distinguisher 1.1.1.1:100;
-
vrf-target target:100:100;
-
protocols {
-
evpn {
-
extended-vlan-list 100-101;
-
default-gateway do-not-advertise;
That includes Windows containers, as ContainerX likes to tell enterprises.
The cybersecurity and security solutions landscape is in constant flux.
$45 million in synergies is expected from the deal.