Explains this feature provides active-active connectivity to a CE device in a L3VPN deployment. The CE device can be Layer-2 or Layer-3 device connecting to the redundant PEs over a single LACP LAG port.
A L3VPN active-active redundancy is a network availability feature that
-
enables a Customer Edge (CE) device (Layer-2 or Layer-3) to connect to two or more Provider Edge (PE) routers over a single LACP LAG port,
-
synchronizes Layer-3 route learning between redundant PEs using EVPN route-types to minimize service disruption, and
-
eliminates the need for GARP or IPv6 NA replay for CEs connected over a single LAG port.
|
Feature Name |
Release Information |
Feature Description |
|---|---|---|
|
SRv6 L3VPN VPNv4 Active-Active Redundancy |
Release 25.4.1 |
Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only*) *This feature is supported on:
|
|
SRv6 L3VPN VPNv4 Active-Active Redundancy |
Release 25.1.1 |
Introduced in this release on: Fixed Systems ( 8010 [ASIC: A100]) This feature is now supported on Cisco 8011-4G24Y4H-I routers. |
|
SRv6 L3VPN VPNv4 Active-Active Redundancy |
Release 24.4.1 |
Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100])(select variants only*); Modular Systems (8800 [LC ASIC: P100])(select variants only*) You can now provide active-active connectivity to a CE device in an L3VPN deployment. The CE device connects to redundant PEs over a single LACP LAG port. Depending on the bundle hashing, ARP or IPv6 ND packets can be sent to any redundant router. Layer-3 local route learning is enhanced with remote route-synchronization to ensure minimal service interruption, using EVPN route-types 2, 7/8, and 5 for synchronization. *This feature is supported on:
|
This feature provides active-active connectivity to a CE device in a L3VPN deployment. The CE device can be Layer-2 or Layer-3 device connecting to the redundant PEs over a single LACP LAG port.
Depending on the bundle hashing, an ARP or IPv6 Network Discovery (ND) packet can be sent to any of the redundant routers. As a result, not all entries will exist on a given PE. In order to provide complete awareness, Layer-3 local route learning is augmented with remote route-synchronization programming.
Route synchronization between service PEs is required in order to provide minimum interruption to unicast and multicast services after failure on a redundant service PE. The following EVPN route-types are used for Layer-3 route synchronization:
-
EVPN route-type 2 for synchronizing ARP tables
-
EVPN route-type 7/8 for synchronizing IGMP JOINS/LEAVES
In a Layer-3 CE scenario, the router that connects to the redundant PEs may establish an IGP adjacency on the bundle port. In this case, the adjacency will be formed to one of the redundant PEs, and IGP customer routes will only be present on that PE. To synchronize Layer-3 customer subnet routes (IP Prefixes), the EVPN route-type 5 is used to carry the ESI and ETAG as well as the gateway address (prefix next-hop address).
Gratuitous ARP (GARP) or IPv6 Network Advertisement (NA) replay is not needed for CEs connected to the redundant PEs over a single LAG port.
The below configuration enables Layer-3 route synchronization for routes learned on the Ethernet-segment sub-interfaces.
evpn
route-sync vrf default
!
vrf RED
evi route-sync 10
!
vrf BLUE
evi route-sync 20
!
EVPN does not support untagged interfaces.