Member-only story
BGP EVPN and All-Active Multi-Homing Ethernet Segment on GNS3
Introduction
BGP MPLS-Based Ethernet VPN or BGP EVPN (RFC 7432) offers more scalable, flexible (e.g., per flow and service load balance) and resilience (e.g., Multi-Home) Overlay layer 2 (L2) and layer 3 (L3) network services than the older TLDP and MP-BGP VPN based L2 and L3 MPLS network services designed in 2000s. BGP EVPN supports the following Underlay network transports:
- EVPN-MPLS (RFC 7432) — BGP EVPN L2 and L3 services over MPLS WAN
- EVPN-PBB (RFC 7623) — BGP EVPN L2 and L3 services over Ethernet Provider Backbone
- EVPN-NVO (RFC8365) — BGP EVPN L2 and L3 network services for Data Center (DC) with Network Virtualization Overlay (NVO)
In my previous article, BGP EVPN NVO and Data Center Gateway with Nokia 7750 and Juniper MX — Part 1, I talked about how to deploy VPLS service using BGP EVPN-NVO to interconnect a tenant’s VMs inside and across Data Centers (DCs). In this article, I will talk about a typical Customer Edge (CE) and Provider Edge (PE) access/core MPLS network deployment using RFC 7432 BGP EVPN-MPLS . Ethernet Segments (ES) are used in the example to provide All-Active Multi-Home (MH) connections for the branch routers (CE) for link and PE failure redundancy protection and improve CEs’ uplink utilization.
