Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Segment Routing v6 Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

EVPNv6 ELAN Layer 2 gateway with automated steering

Want to summarize with AI?

Log in

Explains how EVPN E-LAN services use Flex-Algo or SRv6-TE to automate traffic steering and provides deployment, resiliency, configuration, and verification guidance.


EVPNv6 ELAN Layer 2 gateway with automated steering is a capability that

  • enables multipoint Layer 2 ELAN services over an SRv6-based network using EVPN BGP signaling,

  • automatically steers EVPN ELAN traffic into paths associated with best-effort or Flex-Algorithm locators, and

  • combines the advantages of EVPN ELAN services with SRv6 Micro-SIDs for efficient traffic forwarding.

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

EVPNv6 ELAN multihoming

Release 26.1.1

Introduced in this release on: Fixed Systems (8200 [ASIC: Q200]); Centralized Systems (8600 [ASIC:Q200]); Modular Systems (8800 [LC ASIC: Q200])

The feature introduces support for an ELAN (P2P) service with multihoming capability over an SRv6 network. The feature supports only the Port-Active multihoming mode.

EVPNv6 ELAN single-homing

Release 26.1.1

Introduced in this release on: Fixed Systems (8200 [ASIC: Q200]); Centralized Systems (8600 [ASIC:Q200]); Modular Systems (8800 [LC ASIC: Q200])

EVPNv6 ELAN single-homing provides seamless multipoint-to-multipoint Layer 2 connectivity, enabling efficient communication between multiple customer sites or data centers.

EVPNv6 ELAN multihoming

Release 25.4.1

Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100], 8010 [ASIC: A100]); Modular Systems (8800 [LC ASIC: P100])

The feature introduces support for an ELAN (P2P) service with multihoming capability over an SRv6 network.

Supported multihoming modes:

  • All-Active

  • Single-Active

  • Port-Active

EVPNv6 ELAN single-homing

Release 25.4.1

Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100], 8010 [ASIC: A100]); Modular Systems (8800 [LC ASIC: P100])

EVPNv6 ELAN single-homing provides seamless multipoint-to-multipoint Layer 2 connectivity, enabling efficient communication between multiple customer sites or data centers. This solution delivers a cost-effective and simplified approach for connecting sites within the same service provider network using EVPN single-homing mode.

EVPNv6 ELAN Layer 2 gateway with automated steering to Flex Algo

Release 25.4.1

Introduced in this release on: Fixed Systems (8200 [ASIC: P100], 8700 [ASIC: P100, K100], 8010 [ASIC: A100]); Modular Systems (8800 [LC ASIC: P100])

The feature builds upon EVPN BGP signaling to provide Emulated Local Area Network (ELAN) multipoint-to-multipoint Ethernet services over an SRv6-based network.

Automated steering of EVPN ELAN traffic can be enabled for paths associated with a best-effort or Flex-Algorithm locator. This feature combines the benefits of EVPN ELAN service and SRv6 Micro-SIDs.

The feature introduces these changes:

The segment-routing srv6 option was added to the evi (bridge-domain) command.

SRv6 behavior for EVPN Layer 2 traffic

You can transport EVPN ELAN bridged unicast and broadcast, unknown unicast, and multicast (BUM) traffic over an SRv6 network in the Micro-SID format.

Relevant SRv6 headend and endpoint definitions include:

  • H.Encaps.L2.Red . This headend router operation uses reduced encapsulation of Layer 2 or Ether frames through an SRv6 Policy.

  • uDT2U . This endpoint router operation involves traffic decapsulation and unicast MAC Layer 2 table lookup. This is used for the EVPN bridging unicast traffic use case.

  • uDT2M . This endpoint router operation involves traffic decapsulation and Layer 2 table flooding. This is used for the EVPN bridging BUM traffic with ESI filtering use case.

  • Multihoming . This enables you to connect a customer edge (CE) device to two or more provider edge (PE) devices to provide redundant connectivity. The redundant PE device ensures that there is no traffic disruption when there is a network failure. Following are the types of multihoming:

Note

For more information on SRv6 headend and endpoint behaviors, see the Segment Routing over IPv6 Overview chapter.

Multihoming concepts and modes

Multihoming allows a CE device to connect to two or more PE devices, providing redundant connectivity. This redundant configuration ensures continuous traffic flow even if a network failure occurs.

The multihoming modes are:

  • All-Active . In active-active mode, all PEs attached to the Ethernet Segment are allowed to forward traffic to and from that segment.

  • Single-Active . In single-active mode, only one PE among a group attached to the Ethernet Segment is allowed to forward traffic to and from that segment, while backup ports are out of service.

  • Port-Active . In single-active mode, only a single PE among a group of PEs attached to the particular Ethernet-Segment is allowed to forward traffic to and from that Ethernet Segment; backup ports are Out-of-Service.

For more information about EVPN single-homing, multihoming, and topology concepts, see L2VPN and Ethernet Services Configuration Guide for Cisco 8000 Series Routers.


Usage guidelines and restrictions for EVPNv6 ELAN Layer 2 gateway

Usage guideline

To transport broadcast, unknown unicast, and multicast (BUM) traffic, the Border Gateway Protocol (BGP) Route Reflector device must have an IOS XR release version 7.5.2 or later.

Restriction

uDT2U and uDT2M do not support disposition when the packet contains a Segment Routing Header (SRH) with Segment Left (SL) set to 0.


Configure SRv6 EVPN bridging

Enable these configurations on PE routers R1, R3, and R8, which participate in the EVPN EVI.

Before you begin

Complete the steps in the Segment Routing over IPv6 Overview chapter before you perform these steps.

Procedure

  1. Associate SRv6 with EVPN.

    1. Run the segment-routing srv6 and locator sample commands to enable SRv6 under the EVPN mode and associate a global locator with EVPN.

      Example:

      In the example configuration, the global locator sample is associated with EVPN.

      Router# configure terminal 
      Router(config)# evpn
      Router(config-evpn)# segment-routing srv6 
      Router(config-evpn-srv6)# locator sample 
      Router(config-evpn-srv6)# exit 
      
    2. Run the evi command to associate an EVI-specific locator.

      Example:

      Router(config-evpn)# evi 1 segment-routing srv6 
      Router(config-evpn-instance)# locator sample_evi_loc  
      Router(config-evpn-instance)# commit 
  2. Associate SRv6 with L2VPN.

    1. Run the bridge group command to associate a sub-interface to the bridge domain.

      Example:

      Router(config)# l2vpn 
      Router(config-l2vpn)# bridge group bg1 
      Router(config-l2vpn-bg)# bridge-domain bd1 
      Router(config-l2vpn-bg-bd)# interface Hu0/0/0/0.1 
      Router(config-l2vpn-bg-bd-ac)# exit 
      
    2. Run the evi command to enable a specific EVPN instance ID to utilize SRv6 as its underlying transport for Layer 2 services.

      Example:

      Router(config-l2vpn-bg-bd)# evi 1 segment-routing srv6 
      Router(config-l2vpn-bg-bd-evi-srv6)# commit 
      
  3. Run the show commands to verify the SRv6 EVPN bridging configuration.

    This sample output displays the SRv6 EVPN ELAN traffic unicast and multicast SID information.

    Router# show evpn evi vpn-id 1 detail  
    
    VPN-ID     Encap      Bridge Domain                Type
    ---------- ---------- ---------------------------- -----------------
    1          SRv6       bd1                          EVPN
    
    ..
       Stitching: Regular
       Unicast SID:  fccc:ccc1:a1:e000:: 
       Multicast SID: fccc:ccc1:a1:e001:: 
    ..
    

    This sample output displays EVI 1 details, including the corresponding SID and EVPN MAC address.

    Router# show evpn evi vpn-id 1 mac 
    
    VPN-ID    Encap   MAC            IP        Nexthop      Label    SID 
                      address        address
    -----     ------ --------       --------   -------      -----         ---
    
    1         SRv6    0010.3000.01d0  ::       Hu0/0/0/0.1    0     fccc:ccc1:a1:e000:: 
     

    This sample output displays SRv6 EVPN ELAN traffic details for the specified EVI and EVPN MAC address.

    Router# show evpn evi vpn-id 1 mac 0010.3000.01d0 detail 
    
    VPN-ID Encap       MAC            IP       Nexthop      Label         SID 
                       address        address 
    ------ -----       ------         ------  -------       -----         --- 
    1     SRv6   ee03.0500.0130  ::     192.168.0.3  IMP-NULL fccc:ccc1:a3:e000:: 
     
       Ethernet Tag                            : 0
       Multi-paths Resolved                    : True
       Multi-paths Internal label              : None
       Local Static                            : No
       Remote Static                           : Yes
       Local Ethernet Segment                  : N/A
       Remote Ethernet Segment                 : 0100.0205.acce.5500.0500
       Local Sequence Number                   : N/A
       Remote Sequence Number                  : 0
       Local Encapsulation                     : N/A
       Remote Encapsulation                    : SRv6 
       Local E-Tree                            : Root
       Remote E-Tree                           : Root
       Remote matching E-Tree RT               : No
       Local AC-ID                             : 0x0
       Remote AC-ID                            : 0x13
    

    This sample output displays multicast SID details for the specified EVI.

    Router# show evpn evi vpn-id 1 inclusive-multicast detail 
    
    VPN-ID        Encap           EtherTag             Originating IP 
    ---           ----            -------              ------------- 
    1            SRv6       0                    192.168.0.1 
    ..
              TEPid: 0xffffffff
    		PMSI Type: 6
    		Nexthop: ::
    		SR-TE Info: N/A
    	    SID: fccc:ccc1:a1:e001:: 
    		Source: Local
    		E-Tree: Root
    ..
    

    This sample output displays bridge domain information for the specified MAC address.

    Router# show l2route evpn mac all | i ee03.0500.0130 
    
    Topo ID   Mac Address             Producer     Next Hop(s)
    ------    -----------             -------      ------------- 
    1         ee03.0500.0130    L2VPN        ::ffff:10.0.0.10/IID/V6, N/A 
    

    This sample output displays SRv6 network locator and the corresponding SID information.

    uDT2U and uDT2M refer to SRv6 network endpoint operations. uDT2U indicates SRv6 traffic decapsulation, wherein EVPN bridged unicast traffic is forwarded out of the SR network. uDT2M indicates SRv6 traffic decapsulation, wherein EVPN bridged multicast traffic is forwarded out of the SR network.

    Router# show segment-routing srv6 sid 
    
    *** Locator: 'sample_evi_loc' ***
    
    SID                     Behavior      Context        Owner        State   RW
    ---                     --------      -------        -----        -----   --
    fccc:ccc1:a1::          uN(PSP/USD)  'default':161   sidmgr        InUse   Y
    fccc:ccc1:a1:e000::     uDT2U   7:0            l2vpn_srv6    InUse   Y
    fccc:ccc1:a1:e001::     uDT2M   7:0            l2vpn_srv6    InUse   Y
    

    This sample output displays CEF information, including SRv6 network endpoint details. uDT2U is an SRv6 network endpoint operation wherein SRv6 traffic is decapsulated and EVPN bridged unicast traffic is forwarded out of the SR network.

    Router# show cef ipv6 fccc:ccc1:a1:e000:: detail 
    
    fccc:ccc1:a1:e000::, version 14, SRv6 Endpoint uDT2U, internal 0x1000001 
    0x0 (ptr 0x8ba26050) [1], 0x400 (0x8bbf7b58), 0x0 (0x92396138)
    
     Prefix Len 64, traffic index 0, precedence n/a, priority 0
      gateway array (0x8ba33e90) reference count 4, flags 0x0, source rib (7), 0 backups
                    [5 type 3 flags 0x8401 (0x8baf8ca8) ext 0x0 (0x0)]
    
      LW-LDI[type=3, refc=1, ptr=0x8bbf7b58, sh-ldi=0x8baf8ca8]
      gateway array update type-time 1 Sep  8 11:46:51.242
    
     LDI Update time Sep  8 11:46:51.303
     LW-LDI-TS Sep  8 11:46:51.380
       via ::/128, 0 dependencies, weight 0, class 0 [flags 0x0]
        path-idx 0 NHID 0x0 [0x8afdf120 0x0]
        next hop ::/128
        XConnect ID: 0x80000003
        Bridge ID: 0x1
        Shg ID: 0x1
    
        Load distribution: 0 (refcount 5)
    
        Hash  OK  Interface                 Address
        0     Y   recursive                 Lookup in table
    

    In the following examples, SRv6 EVPN ELAN traffic-related IID information is displayed.

    Router# show evpn internal-id vpn-id 3001 detail 
    
    VPN-ID  Encap  Ethernet Segment Id         EtherTag     Internal ID
    -----   ------ --------------------------- ----------   -----------
    1       SRv6   0001.0001.0001.1501.0015    0         ::ffff:10.0.0.4 
    
       Summary pathlist:
    
     0x05000002 (P) 192.168.0.3 fccc:ccc1:a3:e000::
     0x05000002 (P) 192.168.0.3 fccc:ccc1:a4:e000::
    
    Router# show cef vrf **iid ipv6 ::ffff:10.0.0.4 
    
    ::ffff:10.0.0.4/128, version 39, SRv6 Headend, IID (EVPN-MH), internal 0x1000001 0x0 (ptr 0x8ba21798) [3], 0x0 (0x0), 0x0 (0x923967b0)
     Updated Sep  8 18:01:06.495
     Prefix Len 128, traffic index 0, precedence n/a, priority 0
      gateway array (0x8ba36018) reference count 1, flags 0x2010, source rib (7), 0 backups
                    [1 type 3 flags 0x48441 (0x8baf9a28) ext 0x0 (0x0)]
      LW-LDI[type=0, refc=0, ptr=0x0, sh-ldi=0x0]
      gateway array update type-time 1 Sep  8 18:01:06.495
     LDI Update time Sep  8 18:01:06.495
    
      Level 1 - Load distribution: 0
      [0] via fccc:ccc1:a3::/128, recursive
    
       via fccc:ccc1:a3:e000::/128, 10 dependencies, recursive [flags 0x0]
        path-idx 0 NHID 0x0 [0x8ba24e78 0x0]
        next hop VRF - 'default', table - 0xe0800000
        next hop fccc:ccc1:a3::/128 via fccc:ccc1:a3::/48
        SRv6 H.Encaps.L2.Red SID-list { fccc:ccc1:a3:e000::}
    
        Load distribution: 0 (refcount 1)
    
        Hash  OK  Interface        Address
        0     Y   Hu0/0/0/0        remote
    
       via fccc:ccc1:a4::/128, 10 dependencies, recursive [flags 0x100]
        path-idx 0 NHID 0x0 [0x8ba24e78 0x0]
        next hop VRF - 'default', table - 0xe0800000
        next hop fccc:ccc1:a4::/128 via fccc:ccc1:a4::/48
        SRv6 H.Encaps.L2.Red SID-list {fccc:ccc1:a4:e000::}
    
    Router# show rib ipv6 iid 
    
    IID         Prefix                Context             Owner           State      RW 
    -------     ------                -------             -------         -----      -- 
    0xa000001 ::ffff:10.0.0.1 [EVPN-ELAN:evi=7:esi=8300.fccc.ccc1.00a4.0000:nh=fccc:ccc1:a4:::eth_tag=0:type=0:encap=255:opaque=0] 
                                                          l2vpn_iid        InUse      Y 
    
    0xa000002 ::ffff:10.0.0.2 [EVPN-ELAN:evi=8:esi=8300.fccc.ccc1.00a4.0000:nh=fccc:ccc1:a4:::eth_tag=0:type=0:encap=255:opaque=0] 
                                                          l2vpn_iid        InUse      Y 
    
    0xa000003 ::ffff:10.0.0.3  [EVPN-ELAN:evi=9:esi=8300.fccc.ccc1.00a4.0000:nh=fccc:ccc1:a4:::eth_tag=0:type=0:encap=255:opaque=0]
                                                          l2vpn_iid        InUse      Y