Implementing BGP EVPN on IOS-XR

by Abhijit Tamuli
 Table of Contents
1. IMPLEMENTING BGP EVPN ON IOS-XR ................................................................................................ 3
ABOUT THIS DEMONSTRATION ............................................................................................................................. 3
EVPN Overview ........................................................................................................................................... 3
Route Type 1: Ethernet Auto-Discovery (AD) Route.................................................................................... 4
Route Type 2: MAC/IP Advertisement Route .............................................................................................. 4
Route Type 3: Inclusive Multicast Ethernet Tag Route ............................................................................... 4
Route Type 4: Ethernet Segment Route ...................................................................................................... 4
2. EVPN TESTBED: ................................................................................................................................... 4
3. LAB 0: TRANSPORT VERIFICATION....................................................................................................... 5
4. LAB 1: EVPN L2 ALL-ACTIVE MH SERVICE WITH INTRA-SUBNET IRB AND ANYCAST GATEWAY. ............ 6
5. LAB 2: VALIDATION AND VERIFICATION: ............................................................................................. 8
6. ROUTE-TYPE 4................................................................................................................................... 12
7. ROUTE-TYPE 1 (PER-ESI) .................................................................................................................... 13
8. ROUTE-TYPE 3 (INCLUSIVE-MULTICAST) ............................................................................................ 14
9. ROUTE-TYPE 2 (MAC-IP) .................................................................................................................... 15
10. ROUTE-TYPE 1 (PER-EVI) ................................................................................................................ 16
1. Implementing BGP EVPN on IOS-XR:

About This Demonstration:

This lab introduces users to the industry standard BGP EVPN and Cisco implementation of BGP on IOS-XR.
Users need to use real IOS-XR boxes to implement BGP EVPN control and data plane. Upon completion of
this lab, users will able to

• Manually configure BGP EVPN on IOS-XR.

• Use command line to verify BGP EVPN route-types.

EVPN Overview:

Ethernet VPN (EVPN) is a next generation solution that provide Ethernet multipoint services over MPLS
networks. EVPN operates in contrast to the existing Virtual Private LAN Service (VPLS) by enabling control-
plane based MAC learning in the core. In EVPN, PE's participating in the EVPN instances learn customer MAC
routes in Control-Plane using MP-BGP protocol. Control-plane MAC learning brings a number of benefits that
allow EVPN to address the VPLS shortcomings, including support for multi-homing with per-flow load
balancing.

The EVPN control-plane MAC learning has the following benefits:

• Eliminate flood and learn mechanism
• Fast-reroute, resiliency, and faster reconvergence when link to dual-homed server fails
• Enables load balancing of traffic to and from CEs that are multihomed to multiple Pes

The following EVPN modes are supported:

• Single homing - This enables you connect a customer edge (CE) device to one provider edge (PE) device.

• 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:

• Single-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.

• Active-Active - In active-active mode, all the PEs attached to the particular Ethernet-Segment is allowed
to forward traffic to and from that Ethernet Segment.
EVPN Route Types:

Route Type 1: Ethernet Auto-Discovery (AD) Route

The Ethernet (AD) routes are advertised on per EVI and per ESI basis. These routes are sent per ES. They
carry the list of EVIs that belong to the ES. The ESI field is set to zero when a CE is single-homed.
Route Type 2: MAC/IP Advertisement Route
The host's IP and MAC addresses are advertised to the peers within NLRI. The control plane learning of
MAC addresses reduces unknown unicast flooding.
Route Type 3: Inclusive Multicast Ethernet Tag Route
This route establishes the connection for broadcast, unknown unicast, and multicast (BUM) traffic from a
source PE to a remote PE. This route is advertised on per VLAN and per ESI basis.
Route Type 4: Ethernet Segment Route
Ethernet segment routes enable to connect a CE device to two or PE devices. ES route enables the
discovery of connected PE devices that are connected to the same Ethernet segment.

2. EVPN TESTBED:

Note:
Þ R36, R37,R38 are PE routers.
Þ RR103 and RR104 are Route-Reflectors.
Þ ASR-9001-1 and N9K-C9372PX-1 are CE devices.

Lab Tasks:

Lab 0: Transport Verification

Lab 1: EVPN L2 All-Active Multihomed Service with Intra-Subnet IRB and anycast gateway.
Lab 2: Validation and Verification
3. Lab 0: Transport Verification

The SP core is emulated via PE’s R36, R37 and R38. RR103 and RR104 are route-reflector’s. ISIS is used as the
underlay. All connected interfaces and associated loopback’s are advertised in Level-2.

After the ISIS Level-2 adjacency has been setup successfully, we should be able to see the loopback’s of
R37,R38,RR103 and RR104 on R36.

RP/0/RSP0/CPU0:R36#sh run router isis

router isis 1
is-type level-2-only
net 00.0000.0000.0004.00
address-family ipv4 unicast
!
interface Loopback0
address-family ipv4 unicast
!
!
interface TenGigE0/0/2/0
address-family ipv4 unicast
!
!
!

RP/0/RSP0/CPU0:R36#sh route ipv4 unicast

L 3.3.3.36/32 is directly connected, 00:41:54, Loopback0

i L2 3.3.3.37/32 [115/40] via 10.0.24.2, 00:41:38, TenGigE0/0/2/0
i L2 3.3.3.38/32 [115/30] via 10.0.24.2, 00:41:38, TenGigE0/0/2/0
i L2 3.3.3.103/32 [115/20] via 10.0.24.2, 00:41:43, TenGigE0/0/2/0
i L2 3.3.3.104/32 [115/30] via 10.0.24.2, 00:41:38, TenGigE0/0/2/0
i L2 10.0.23.0/24 [115/20] via 10.0.24.2, 00:41:43, TenGigE0/0/2/0
C 10.0.24.0/24 is directly connected, 00:41:54, TenGigE0/0/2/0
L 10.0.24.4/32 is directly connected, 00:41:54, TenGigE0/0/2/0
i L2 10.0.26.0/24 [115/20] via 10.0.24.2, 00:41:43, TenGigE0/0/2/0
i L2 10.0.35.0/24 [115/30] via 10.0.24.2, 00:41:38, TenGigE0/0/2/0
i L2 10.0.36.0/24 [115/30] via 10.0.24.2, 00:41:38, TenGigE0/0/2/0
4. Lab 1: EVPN L2 All-Active MH Service with Intra-Subnet IRB and anycast gateway.

Interface Config on R36/37/38:

R38 R37 R36

interface TenGigE0/0/0/0 interface TenGigE0/0/2/3 interface TenGigE0/0/2/2

bundle id 100 mode active bundle id 100 mode active bundle id 100 mode active
cdp cdp cdp
! ! !
interface Bundle-Ether100 interface Bundle-Ether100 interface Bundle-Ether100
! ! !
interface Bundle-Ether100.12 l2transport interface Bundle-Ether100.12 l2transport interface Bundle-Ether100.12 l2transport
encapsulation dot1q 12 encapsulation dot1q 12 encapsulation dot1q 12
rewrite ingress tag pop 1 symmetric rewrite ingress tag pop 1 symmetric rewrite ingress tag pop 1 symmetric
! ! !

EVPN Config on R36/37/38:

R36/37 R38

evpn evpn
evi 100 evi 100
! !
interface Bundle-Ether100 interface Bundle-Ether100
ethernet-segment ethernet-segment
identifier type 0 36.37.00.00.00.00.00.11.00 identifier type 0 36.37.00.00.00.00.00.11.00
! !
! !
! !

EVPN IRB Config on R36/37/38:

interface BVI100
host-routing
vrf a
ipv4 address 192.168.1.1 255.255.255.0
mac-address 3637.3637.3637
!
l2vpn
bridge group 100
bridge-domain 100
interface Bundle-Ether100.12
!
routed interface BVI100
!
evi 100
!
!
!
!
cef adjacency route override rib
!
vrf a
address-family ipv4 unicast
import route-target
100:100
!
export route-target
100:100
!
!
!
router bgp 1
address-family vpnv4 unicast
!
!
Config: BGP for EVPN on L1/L2/L3:

R36 R37 R38

router bgp 1 router bgp 1 router bgp 1

bgp router-id 3.3.3.36 bgp router-id 3.3.3.37 bgp router-id 3.3.3.38
address-family ipv4 unicast address-family ipv4 unicast address-family ipv4 unicast
! ! !
address-family vpnv4 address-family vpnv4 address-family vpnv4
unicast unicast unicast
! ! !
address-family l2vpn evpn address-family l2vpn evpn address-family l2vpn evpn
! ! !
neighbor-group rr neighbor-group rr neighbor-group rr
remote-as 1 remote-as 1 remote-as 1
update-source Loopback0 update-source Loopback0 update-source Loopback0
address-family l2vpn evpn address-family l2vpn evpn address-family l2vpn evpn
! ! !
! ! !
neighbor 3.3.3.103 neighbor 3.3.3.103 neighbor 3.3.3.103
use neighbor-group rr use neighbor-group rr use neighbor-group rr
! ! !
neighbor 3.3.3.104 neighbor 3.3.3.104 neighbor 3.3.3.104
use neighbor-group rr use neighbor-group rr use neighbor-group rr
! ! !
vrf a vrf a vrf a
rd auto rd auto rd auto
address-family ipv4 unicast address-family ipv4 unicast address-family ipv4 unicast
additional-paths receive additional-paths receive additional-paths receive
maximum-paths ibgp 2 maximum-paths ibgp 2 maximum-paths ibgp 2
redistribute connected redistribute connected redistribute connected
! ! !
! ! !
! ! !

Config: BGP for EVPN on RR103 / RR104:

RR103 RR104

router bgp 1 router bgp 1

bgp router-id 3.3.3.103 bgp router-id 3.3.3.104
address-family l2vpn evpn address-family l2vpn evpn
! !
neighbor-group rr neighbor-group rr
remote-as 1 remote-as 1
update-source Loopback0 update-source Loopback0
address-family l2vpn evpn address-family l2vpn evpn
route-reflector-client route-reflector-client
! !
! !
neighbor 3.3.3.36 neighbor 3.3.3.36
use neighbor-group rr use neighbor-group rr
! !
neighbor 3.3.3.37 neighbor 3.3.3.37
use neighbor-group rr use neighbor-group rr
! !
neighbor 3.3.3.38 neighbor 3.3.3.38
use neighbor-group rr use neighbor-group rr
! !
! !
5. Lab 2: Validation and Verification:

Þ show evpn evi vpn-id detail

RP/0/RSP0/CPU0:R36#show evpn evi vpn-id 100 detail RP/0/RSP0/CPU0:R37#show evpn evi vpn-id 100 detail

EVI Bridge Domain Type VPN-ID Encap Bridge Domain Type

---------- ---------------------------- ------------------- ---------- ------ ---------------------------- -------------------
100 100 EVPN 100 MPLS 100 EVPN
Instance Attributes: MPLS, Regular Stitching: Regular
Unicast Label : 36000 Unicast Label : 37000
Multicast Label: 36001 Multicast Label: 37001
Flow Label: N Flow Label: N
Control-Word: Enabled Control-Word: Enabled
Forward-class: 0 Forward-class: 0
Advertise MACs: No Advertise MACs: No
Advertise BVI MACs: No Advertise BVI MACs: No
Aliasing: Enabled Aliasing: Enabled
UUF: Enabled UUF: Enabled
Re-origination: Enabled Re-origination: Enabled
RD Config: none Multicast source connected: No
RD Auto : (auto) 3.3.3.36:100 BGP Implicit Import: Enabled
RT Auto : 1:100 VRF Name: a
Route Targets in Use Type RD Config: none
------------------------------ --------------------- RD Auto : (auto) 3.3.3.37:100
1:100 Import RT Auto : 1:100
1:100 Export Route Targets in Use Type
------------------------------ ---------------------
1:100 Import
1:100 Export

RP/0/RSP0/CPU0:R38#show evpn evi vpn-id 100 detail

EVI Bridge Domain Type

---------- ---------------------------- -------------------
100 100 EVPN
Instance Attributes: MPLS, Regular
Unicast Label : 38000
Multicast Label: 38001
Flow Label: N
Control-Word: Enabled
Forward-class: 0
Advertise MACs: Yes
Advertise BVI MACs: No
Aliasing: Enabled
UUF: Enabled
Re-origination: Enabled
RD Config: none
RD Auto : (auto) 3.3.3.38:100
RT Auto : 1:100
Route Targets in Use Type
------------------------------ ---------------------
1:100 Import
1:100 Export
Þ show bgp l2vpn evpn summary

Verify bgp l2vpn evpn peering towards the RR’s 3.3.3.103 and 3.3.3.104.

RP/0/RSP0/CPU0:R36#show bgp l2vpn evpn summary

BGP router identifier 3.3.3.36, local AS number 1
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 0
BGP main routing table version 74
BGP NSR Initial initsync version 10 (Reached)
BGP NSR/ISSU Sync-Group versions 0/0
BGP scan interval 60 secs

BGP is operating in STANDALONE mode.

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 74 74 74 74 74 0

Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd

3.3.3.103 0 1 183 168 74 0 0 02:37:02 10
3.3.3.104 0 1 183 168 74 0 0 02:37:04 10

RP/0/RSP0/CPU0:R37#show bgp l2vpn evpn summary

BGP router identifier 3.3.3.37, local AS number 1
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 0
BGP main routing table version 53
BGP NSR Initial initsync version 5 (Reached)
BGP NSR/ISSU Sync-Group versions 0/0
BGP scan interval 60 secs

BGP is operating in STANDALONE mode.

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 53 53 53 53 53 0

Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd

3.3.3.103 0 1 183 173 53 0 0 02:37:06 10
3.3.3.104 0 1 183 172 53 0 0 02:37:18 10

RP/0/RSP0/CPU0:R38#show bgp l2vpn evpn summary

BGP router identifier 3.3.3.38, local AS number 1
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 0
BGP main routing table version 54
BGP NSR Initial initsync version 5 (Reached)
BGP NSR/ISSU Sync-Group versions 0/0
BGP scan interval 60 secs

BGP is operating in STANDALONE mode.

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 54 54 54 54 54 0

Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd

3.3.3.103 0 1 183 166 54 0 0 02:37:16 8
3.3.3.104 0 1 183 166 54 0 0 02:37:16 8
Þ show evpn ethernet-segment

Verify evpn ethernet-segment. R36 and R37 should display 2 NH’s.

RP/0/RSP0/CPU0:R36#show evpn ethernet-segment

Ethernet Segment Id Interface Nexthops

------------------------ ---------------------------------- --------------------
0036.3700.0000.0000.1100 BE100 3.3.3.36
3.3.3.37

RP/0/RSP0/CPU0:R37#show evpn ethernet-segment

Ethernet Segment Id Interface Nexthops

------------------------ ---------------------------------- --------------------
0036.3700.0000.0000.1100 BE100 3.3.3.36
3.3.3.37

RP/0/RSP0/CPU0:R38#show evpn ethernet-segment

Ethernet Segment Id Interface Nexthops

------------------------ ---------------------------------- --------------------
0038.3900.0000.0000.2200 BE100 3.3.3.38

Þ show evpn ethernet-segment esi carving detail

This command verifies the DF election for the EVI 100. R36 is the DF for EVI 100 ( 100 modulo 2 = 0 ).

R37 is not the DF for EVI 100.

RP/0/RSP0/CPU0:R36#show evpn ethernet-segment esi 0036.3700.0000.0000.1100 carving detail

Ethernet Segment Id Interface Nexthops

------------------------ ---------------------------------- --------------------
0036.3700.0000.0000.1100 BE100 3.3.3.36
3.3.3.37
ES to BGP Gates : Ready
ES to L2FIB Gates : Ready
Main port :
Interface name : Bundle-Ether100
Interface MAC : b026.803d.0f9c
IfHandle : 0x000005e0
State : Up
Redundancy : Not Defined
ESI type :0
Value : 36.3700.0000.0000.1100
ES Import RT : 3637.0000.0000 (from ESI)
Source MAC : 0000.0000.0000 (N/A)
Topology :
Operational : MH, All-active
Configured : All-active (AApF) (default)
Primary Services : Auto-selection
Secondary Services: Auto-selection
Service Carving Results:
Forwarders : 1
Permanent : 0
Elected :1
EVI E : 100
Not Elected : 0
MAC Flushing mode : STP-TCN
Peering timer : 3 sec [not running]
Recovery timer : 30 sec [not running]
Carving timer : 0 sec [not running]
Local SHG label : 36002
Remote SHG labels : 1
592032 : nexthop 3.3.3.37
RP/0/RSP0/CPU0:R37#show evpn ethernet-segment esi 0036.3700.0000.0000.1100 carving detail
Ethernet Segment Id Interface Nexthops
------------------------ ---------------------------------- --------------------
0036.3700.0000.0000.1100 BE100 3.3.3.36
3.3.3.37
ES to BGP Gates : Ready
ES to L2FIB Gates : Ready
Main port :
Interface name : Bundle-Ether100
Interface MAC : b026.803d.5104
IfHandle : 0x00000220
State : Up
Redundancy : Not Defined
ESI type :0
Value : 36.3700.0000.0000.1100
ES Import RT : 3637.0000.0000 (from ESI)
Source MAC : 0000.0000.0000 (N/A)
Topology :
Operational : MH, All-active
Configured : All-active (AApF) (default)
Service Carving : Auto-selection
Peering Details : 3.3.3.36[MOD:P:00] 3.3.3.37[MOD:P:00]
Service Carving Results:
Forwarders : 1
Permanent : 0
Elected :0
Not Elected : 1
EVI NE : 100
MAC Flushing mode : STP-TCN
Peering timer : 3 sec [not running]
Recovery timer : 30 sec [not running]
Carving timer : 0 sec [not running]
Local SHG label : 37002
Remote SHG labels : 1
2250 : nexthop 3.3.3.36
6. Route-Type 4

Usage:
• Auto-discovery of multi-homed Ethernet Segments
• Designated Forwarder election

Tagged with ES-Import Extended Community:

PEs apply route filtering based on ES-Import community. Thus, Ethernet Segment route is imported only by
the PEs that are multi-homed to the same Ethernet segment

ES-Import extended community is not the same as the Route Target (RT) extended community

ES-Import Extended Community Usage:

Used to tag the Ethernet Segment route

Limits the scope of Ethernet Segment routes distribution to PEs connected to the same multi-homed
Segment

RP/0/RSP0/CPU0:R36#show bgp l2vpn evpn rd 3.3.3.36:0 [4][0036.3700.0000.0000.1100][32][3.3.3.36]/128

BGP routing table entry for [4][0036.3700.0000.0000.1100][32][3.3.3.36]/128, Route Distinguisher: 3.3.3.36:0
Versions:
Process bRIB/RIB SendTblVer
Speaker 44 44
Last Modified: Jan 28 04:11:13.051 for 05:08:35
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (3.3.3.36)
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate, rib-install
Received Path ID 0, Local Path ID 1, version 44
Extended community: EVPN ES Import:3637.0000.0000
7. Route-Type 1 (Per-ESI)

Per-ESI Ethernet A-D route

• Advertise Split Horizon Label associated with an Ethernet Segment

• Used for MAC Mass Withdraw
• Tagged with ESI MPLS Label Extended Community

ESI Label Extended Community Usage:

• Used to tag the Ethernet AD Route per ESI

• Advertises the Split Horizon Label for the Ethernet Segment
• Indicates the Redundancy Mode: Single Active vs. All Active

RP/0/RSP0/CPU0:R36#show bgp l2vpn evpn rd 3.3.3.36:0 [1][3.3.3.36:1][0036.3700.0000.0000.1100][4294967295]/184

BGP routing table entry for [1][3.3.3.36:1][0036.3700.0000.0000.1100][4294967295]/184, Route Distinguisher: 3.3.3.36:0
Versions:
Process bRIB/RIB SendTblVer
Speaker 45 45
Local Label: 0
Last Modified: Jan 28 04:11:13.051 for 05:07:03
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (3.3.3.36)
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate, rib-install
Received Path ID 0, Local Path ID 1, version 45
Extended community: EVPN ESI Label:0x00:36002 RT:1:100
8. Route-Type 3 (Inclusive-Multicast)

Inclusive Multicast Route 0x3 Usage:

• Multicast tunnels used to transport Broadcast, Multicast and Unknown Unicast frames (BUM)

RP/0/RSP0/CPU0:R36#show bgp l2vpn evpn rd 3.3.3.36:100 [3][0][32][3.3.3.36]/80

BGP routing table entry for [3][0][32][3.3.3.36]/80, Route Distinguisher: 3.3.3.36:100
Versions:
Process bRIB/RIB SendTblVer
Speaker 3 3
Last Modified: Jan 28 03:44:21.051 for 05:38:53
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (3.3.3.36)
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate
Received Path ID 0, Local Path ID 1, version 3
Extended community: RT:1:100
PMSI: flags 0x00, type 6, label 36001, ID 0x03030324

RP/0/RSP0/CPU0:R36#sh l2vpn forwarding bridge-domain 100:100 evpn inclusive-multicast location 0/0/CPU0

Bridge-Domain Name BD-ID XCID Next Hop Label/VNI
-------------------------------- ------ ---------- --------------- ----------
100:100 1 0x80000003 3.3.3.37 37001
3.3.3.38 38001
9. Route-Type 2 (Mac-IP)

MAC-IP Advertisement.

RP/0/RSP0/CPU0:R36#show bgp l2vpn evpn rd 3.3.3.36:100 [2][0][48][188b.9dac.cab1][32][192.168.1.10]/136

BGP routing table entry for [2][0][48][188b.9dac.cab1][32][192.168.1.10]/136, Route Distinguisher: 3.3.3.36:100
Versions:
Process bRIB/RIB SendTblVer
Speaker 76 76
Local Label: 36000
Last Modified: Jan 28 08:07:25.051 for 01:18:02
Paths: (2 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (3.3.3.36)
Second Label 36013
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate, rib-install
Received Path ID 0, Local Path ID 1, version 76
Extended community: SoO:3.3.3.36:100 RT:1:100 RT:100:100
EVPN ESI: 0036.3700.0000.0000.1100
Path #2: Received by speaker 0
Not advertised to any peer
Local
3.3.3.37 (metric 40) from 3.3.3.103 (3.3.3.37)
Received Label 37000, Second Label 37012
Origin IGP, localpref 100, valid, internal, import-candidate, imported, rib-install
Received Path ID 0, Local Path ID 0, version 0
Extended community: SoO:3.3.3.36:100 RT:1:100 RT:100:100
Originator: 3.3.3.37, Cluster list: 3.3.3.103
EVPN ESI: 0036.3700.0000.0000.1100
Source AFI: L2VPN EVPN, Source VRF: default, Source Route Distinguisher: 3.3.3.37:100

RP/0/RSP0/CPU0:R36#sh evpn evi mac

EVI MAC address IP address Nexthop Label

---------- -------------- ---------------------------------------- --------------------------------------- --------
100 188b.9dac.cab1 192.168.1.10 Bundle-Ether100.12 36000
100 b026.803c.dd4b :: 3.3.3.38 38000
100 b026.803c.dd4b 192.168.1.20 3.3.3.38 38000
65535 b026.803d.0f98 :: Local 0
10. Route-Type 1 (Per-EVI)

Per EVI Ethernet A-D route Usage:

• Advertise VPN label used for Aliasing or Backup Path

RP/0/RSP0/CPU0:R36#sh bgp l2vpn evpn rd 3.3.3.36:100 [1][0036.3700.0000.0000.1100][0]/120

BGP routing table entry for [1][0036.3700.0000.0000.1100][0]/120, Route Distinguisher: 3.3.3.36:100
Versions:
Process bRIB/RIB SendTblVer
Speaker 27 27
Local Label: 36000
Last Modified: Jan 28 03:44:21.051 for 05:53:11
Paths: (2 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (3.3.3.36)
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate, rib-install
Received Path ID 0, Local Path ID 1, version 27
Path #2: Received by speaker 0
Not advertised to any peer
Local
3.3.3.37 (metric 40) from 3.3.3.103 (3.3.3.37)
Received Label 37000
Origin IGP, localpref 100, valid, internal, import-candidate, imported, rib-install
Received Path ID 0, Local Path ID 0, version 0
Extended community: RT:1:100
Originator: 3.3.3.37, Cluster list: 3.3.3.103
Source AFI: L2VPN EVPN, Source VRF: default, Source Route Distinguisher: 3.3.3.37:100

Þ cef adjacency route override rib

RP/0/RSP0/CPU0:R36#show cef vrf a 192.168.1.10/32 location 0/0/CPU0

192.168.1.10/32, version 0, internal 0x1120001 0x0 (ptr 0x82198f9c) [1], 0x0 (0x8200b758), 0x0 (0x0)
Updated Jan 28 08:07:25.439
local adjacency 192.168.1.10
Prefix Len 32, traffic index 0, Adjacency-prefix, precedence n/a, priority 15
via 192.168.1.10/32, BVI100, 2 dependencies, weight 0, class 0 [flags 0x0]
path-idx 0 NHID 0x0 [0x81de13d8 0x0]
next hop
local adjacency