EVPN E-LAN (Ethernet LAN) is the EVPN model for multipoint Layer 2 connectivity — allowing multiple customer sites to share a common Ethernet broadcast domain over an MPLS/SR backbone. It is the modern replacement for VPLS, delivering the same multipoint service with dramatically better scalability, faster convergence, and native multi-homing support through the BGP control plane.
EVPN-ELAN vs. VPLS
| Feature | VPLS | EVPN E-LAN |
|---|---|---|
| MAC learning | Data plane (flooding) | BGP control plane |
| BUM traffic | Flood to all PEs | Ingress replication or multicast |
| Multi-homing | H-VPLS (complex) | Native ESI-based |
| Fast convergence | Slow (MAC aging) | Mass withdrawal (sub-second) |
| Split-horizon | Manual configuration | Automatic via ESI |
| L3 integration | Separate L3VPN required | EVPN IRB (native) |
EVPN-ELAN Topology
Single-Homed EVPN-ELAN Configuration
! OcNOS -- PE1: EVPN E-LAN single-homed (EVI 200)
!
! Step 1: ISIS-SR underlay with TI-LFA
router isis CORE
net 49.0001.0000.0000.0001.00
is-type level-2-only
segment-routing mpls
fast-reroute per-prefix level-2 ti-lfa
address-family ipv4 unicast
segment-routing mpls
exit-address-family
!
! Step 2: BGP EVPN full-mesh (or via Route Reflector)
router bgp 65001
bgp router-id 10.0.0.1
neighbor 10.0.0.2 remote-as 65001
neighbor 10.0.0.2 update-source lo
neighbor 10.0.0.3 remote-as 65001
neighbor 10.0.0.3 update-source lo
!
address-family l2vpn evpn
neighbor 10.0.0.2 activate
neighbor 10.0.0.3 activate
exit-address-family
!
! Step 3: EVPN E-LAN instance
l2vpn evpn
instance 200 vlan-based
rd 65001:200
route-target import 65001:200
route-target export 65001:200
!
evi 200
encapsulation mpls
!
! Step 4: Attach CE-facing interfaces
interface eth-0-1
l2vpn evpn evi 200
encapsulation dot1q 200
!
interface eth-0-2
l2vpn evpn evi 200
encapsulation dot1q 200Multi-Homed EVPN-ELAN Configuration (PE2 + PE3)
! OcNOS -- PE2 and PE3: Multi-homed E-LAN for CE-C
! Both PEs share the same ESI for the CE-C segment
!
! Step 1: Define shared Ethernet Segment
evpn
ethernet-segment 1
identifier 0100:0000:0000:0001:0000 ! ESI shared between PE2 and PE3
multihoming-mode all-active ! Both PEs forward (active/active)
df-election algorithm preference ! PE2 is preferred DF (lower pref wins)
df-election preference 100 ! PE2: pref 100; PE3: pref 200
!
!
! Step 2: Attach ESI to LAG interface (CE-C link)
interface bond0 ! LAG interface toward CE-C
evpn ethernet-segment 1
l2vpn evpn evi 200
encapsulation dot1q 200
!
! Verify Designated Forwarder election:
show evpn ethernet-segment detail
! DF should be PE2 (lower preference wins)
!
! Verify MAC sync between PE2 and PE3 via BGP:
show bgp l2vpn evpn route type mac-ip
show bgp l2vpn evpn route type ead ! Auto-discovery routes for ESIBUM Traffic Handling in EVPN-ELAN
! OcNOS -- Configure ingress replication for BUM traffic
! (Broadcast, Unknown unicast, Multicast)
!
l2vpn evpn
instance 200 vlan-based
replication-mode ingress ! Head-end replication (default)
! Alternative: replication-mode static multicast 239.1.1.1
!
!
! Verify BUM replication list (should show all remote VTEPs):
show evpn evi detail
show evpn mac detail- EVPN-ELINE: Point-to-Point L2 Service
- EVPN-ETREE: Rooted Multipoint
- EVPN-L3VPN over ISIS-SR
- OcNOS-SP Product Page
- Contact IP Infusion
IP Infusion Engineering Team