EVPN Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

EVPN Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

EVPN E-Line single-active multihoming mode

Updated: June 10, 2026

Want to summarize with AI?

Log in

Explains the EVPN E-Line single-active multihoming modes and their role in providing network redundancy and efficient resource use.

EVPN E-Line single-active multihoming mode is a network redundancy model that

  • enables PE nodes locally connected to an Ethernet segment to load balance traffic to and from the segment based on an EVI

  • ensures that within an EVI, only one PE forwards traffic to and from the Ethernet segment, and

  • supports efficient use of network resources by managing active forwarding paths.

The EVPN E-Line single-active multihoming mode uses the same conceptual framework as the EVPN E-LAN single-active multihoming mode. For more details, refer to the EVPN E-LAN single-active multihoming mode section.

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

EVPN E-Line single-active multihoming mode

 Release 26.2.1

Introduced in this release on: Modular Systems (8800 [LC ASIC: K100])(select variants only*);

*This feature is supported on Cisco 88-LC1-48Y8H-EM line cards.

EVPN E-Line single-active multihoming mode

 Release 26.1.1

Introduced in this release on: Centralized Systems (8400 [ASIC: K100])(select variants only*)

*This feature is now supported on Cisco 8404-SYS-D routers.

EVPN E-Line single-active multihoming mode

Release 25.4.1

Introduced in this release on: Fixed Systems (8010 [ASIC: A100]) (select variants only*)

*This feature is supported on:

  • 8011-32Y8L2H2FH

  • 8011-12G12X4Y-A

  • 8011-12G12X4Y-D

EVPN E-Line single-active multihoming mode

Release 25.1.1

Introduced in this release on: Fixed Systems (8010 [ASIC: A100]) (select variants only*)

*This feature is now supported on the Cisco 8011-4G24Y4H-I routers.

EVPN E-Line single-active multihoming mode

Release 24.4.1

Introduced in this release on: Fixed Systems (8200, 8700); Centralized Systems (8600); Modular Systems (8800 [LC ASIC: Q200]) (select variants only*)

*The EVPN E-Line single-active multihoming mode is now extended to:

  • 8712-MOD-M

  • 8201-32FH

  • 8201-24H8FH

  • 8202-32FH-M

  • 8608

  • 88-LC0-34H14FH

  • 88-LC0-36FH

  • 88-LC0-36FH-M

EVPN E-Line single-active multihoming mode

Release 24.3.1

Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100])(select variants only*); Modular Systems (8800 [LC ASIC: P100]) (select variants only*)

*The EVPN E-Line single-active multihoming mode is now extended to:

  • 8212-48FH-M

  • 8711-32FH-M

  • 88-LC1-52Y8H-EM

  • 88-LC1-12TH24FH-E

EVPN E-Line single-active multihoming mode

Release 24.2.11

Introduced in this release on: Modular Systems (8800 [LC ASIC: P100]) (select variants only*)

The single-active multihoming mode offers redundant connectivity on a single link at a time with failover to the second link in case the active link fails. In this mode, only a single PE among a group of PEs attached to an Ethernet segment forwards traffic to and from that Ethernet Segment.

*This feature is supported only on routers with the 88-LC1-36EH line cards.

Configure EVPN E-Line single-active multihoming mode

Configure an EVPN E-Line service in single-active multihoming mode to provide redundancy while allowing only one active link per Ethernet segment.

In single-active multihoming mode, only one PE device in a redundant pair actively forwards traffic for a given Ethernet segment, ensuring loop-free forwarding and simplified failover. This configuration is typically used in point-to-point (p2p) services where load sharing is not required.

Procedure

1.

Create a cross-connect group on all the PE devices.

Example:


Router# configure 
Router(config)# l2vpn 
Router(config-l2vpn)# xconnect group xg1
2.

Configure point-to-point (p2p) cross-connect and assign an interface to the cross-connect on all the PE devices.

  1. Point-to-point (p2p) cross-connect and assign an interface to the cross-connect on PE1.

    Example:

    
Router(config-l2vpn-xc)# p2p e1_5-6
Router(config-l2vpn-xc-p2p)# interface Bundle-Ether10.2

  2. Point-to-point (p2p) cross-connect and assign an interface to the cross-connect on PE2.

    Example:

    
Router(config-l2vpn-xc)# p2p e1_5-6
Router(config-l2vpn-xc-p2p)# interface Bundle-Ether10.2

  3. Point-to-point (p2p) cross-connect and assign an interface to the cross-connect on PE3.

    Example:

    
Router(config-l2vpn-xc)# p2p e1_5-6
Router(config-l2vpn-xc-p2p)# interface Bundle-Ether20.1

  4. Point-to-point (p2p) cross-connect and assign an interface to the cross-connect on PE4.

    Example:

    
Router(config-l2vpn-xc)# p2p e1_5-6
Router(config-l2vpn-xc-p2p)# interface Bundle-Ether20.1
3.

Enable EVPN E-Line endpoint on the p2p cross-connect and configure the ESI on all PE devices.

  1. Enable EVPN E-Line endpoint on the p2p cross-connect and configure the ESI on PE1.

    Example:

    Router(config-l2vpn-xc-p2p)# neighbor evpn evi 1 target 5 source 6
Router(config-l2vpn-xc-p2p)#  root
Router(config)# evpn
Router(config-evpn)# interface Bundle-Ether10
Router(config-evpn-ac)#  ethernet-segment
Router(config-evpn-ac-es)# identifier type 0 00.01.00.ac.ce.55.00.0a.00

  2. Enable EVPN E-Line endpoint on the p2p cross-connect and configure the ESI on PE2.

    Example:

    Router(config-l2vpn-xc-p2p)# neighbor evpn evi 1 target 5 source 6
Router(config-l2vpn-xc-p2p)#  root
Router(config)# evpn
Router(config-evpn)# interface Bundle-Ether10
Router(config-evpn-ac)#  ethernet-segment
Router(config-evpn-ac-es)# identifier type 0 00.01.00.ac.ce.55.00.0a.00

  3. Enable EVPN E-Line endpoint on the p2p cross-connect and configure the ESI on PE3.

    Example:

    Router(config-l2vpn-xc-p2p)# neighbor evpn evi 1 target 6 source 5
Router(config-l2vpn-xc-p2p)#  root
Router(config)# evpn
Router(config-evpn)# interface Bundle-Ether20
Router(config-evpn-ac)# ethernet-segment
Router(config-evpn-ac-es)# identifier type 0 00.01.00.ac.ce.55.00.14.00

  4. Enable EVPN E-Line endpoint on the p2p cross-connect and configure the ESI on PE4.

    Example:

    Router(config-l2vpn-xc-p2p)# neighbor evpn evi 1 target 6 source 5
Router(config-l2vpn-xc-p2p)#  root
Router(config)# evpn
Router(config-evpn)# interface Bundle-Ether20
Router(config-evpn-ac)# ethernet-segment
Router(config-evpn-ac-es)# identifier type 0 00.01.00.ac.ce.55.00.14.00
4.

Enable single-active load balancing mode on all the PE devices.

Example:

Router(config-evpn-ac-es)# load-balancing-mode single-active
Router(config-evpn-ac-es)# commit
5.

Running configuration of EVPN E-Line single-active multihoming mode.

Example:

/* On PE1 */
!
l2vpn xconnect group xg1
 p2p e1_5-6
  interface Bundle-Ether10.2
  neighbor evpn evi 1 target 5 source 6
!
evpn
interface Bundle-Ether10
  ethernet-segment
   identifier type 0 00.01.00.ac.ce.55.00.0a.00
   load-balancing-mode single-active
!


/* On PE2 */
!
l2vpn xconnect group xg1
 p2p e1_5-6
  interface Bundle-Ether10.2
  neighbor evpn evi 1 target 5 source 6
!
evpn
interface Bundle-Ether10
  ethernet-segment
   identifier type 0 00.01.00.ac.ce.55.00.0a.00
   load-balancing-mode single-active
!

/* On PE3 */
!
l2vpn xconnect group xg1
 p2p e1_5-6
  interface Bundle-Ether20.1
  neighbor evpn evi 1 target 6 source 5
!
evpn
interface Bundle-Ether20
  ethernet-segment
   identifier type 0 00.01.00.ac.ce.55.00.14.00
   load-balancing-mode single-active
!

/* On PE4 */
!
l2vpn xconnect group xg1
 p2p e1_5-6
  interface Bundle-Ether20.1
  neighbor evpn evi 1 target 6 source 5
!
evpn
interface Bundle-Ether20
  ethernet-segment
   identifier type 0 00.01.00.ac.ce.55.00.14.00
   load-balancing-mode single-active
!