01-28-2025 11:46 PM
Virtual image = 9000v
NXOS image file is: bootflash:///nxos.9.2.4.bin
User-1 generated G-ARP and directly installed it on LEAF 2. In the next phase LEAF 2 generated MAC-IP route (10.10.10.10 - IP
5000.0003.0007-MAC & ESI= Non zero). This route has been learned on LEAF 1.
LEAF - 1 re-originated the same route with site of origin field and advertised it.
is it expected behavior in the ES scenario ?
Outputs
------
LEAF-1# sh ip arp vrf test-10 | begin Address
Address Age MAC Address Interface Flags
10.10.10.10 00:02:29 5000.0003.0007 Vlan10 PS RO
LEAF-2# sh ip arp vrf test-10 | begin Address
Address Age MAC Address Interface Flags
10.10.10.10 00:03:42 5000.0003.0007 Vlan10
LEAF-3# show bgp l2vpn evpn 10.10.10.10
BGP routing table information for VRF default, address family L2VPN EVPN
Route Distinguisher: 1.1.1.1:32777
BGP routing table entry for [2]:[0]:[0]:[48]:[5000.0003.0007]:[32]:[10.10.10.10]
/248, version 717
Paths: (1 available, best #1)
Flags: (0x000202) (high32 00000000) on xmit-list, is not in l2rib/evpn, is not i
n HW
Advertised path-id 1
Path type: internal, path is valid, is best path, no labeled nexthop
Imported to 1 destination(s)
AS-Path: NONE, path sourced internal to AS
11.11.11.11 (metric 41) from 1.1.1.1 (1.1.1.1)
Origin IGP, MED not set, localpref 100, weight 0
Received label 10100
Extcommunity: RT:65501:10100 SOO:1.1.1.1:256 ENCAP:8
ESI: 0301.0203.0405.0600.0007
Path-id 1 not advertised to any peer
Route Distinguisher: 2.2.2.2:32777
BGP routing table entry for [2]:[0]:[0]:[48]:[5000.0003.0007]:[32]:[10.10.10.10]
/248, version 703
Paths: (1 available, best #1)
Flags: (0x000202) (high32 00000000) on xmit-list, is not in l2rib/evpn, is not i
n HW
Advertised path-id 1
Path type: internal, path is valid, is best path, no labeled nexthop
Imported to 1 destination(s)
AS-Path: NONE, path sourced internal to AS
22.22.22.22 (metric 41) from 2.2.2.2 (2.2.2.2)
Origin IGP, MED not set, localpref 100, weight 0
Received label 10100
Extcommunity: RT:65501:10100 ENCAP:8
ESI: 0301.0203.0405.0600.0007
Path-id 1 not advertised to any peer
Route Distinguisher: 3.3.3.3:32777 (L2VNI 10100)
BGP routing table entry for [2]:[0]:[0]:[48]:[5000.0003.0007]:[32]:[10.10.10.10]
/248, version 718
Paths: (2 available, best #1)
Flags: (0x000212) (high32 00000000) on xmit-list, is in l2rib/evpn, is not in HW
Advertised path-id 1
Path type: internal, path is valid, is best path, no labeled nexthop, in rib
Imported from 1.1.1.1:32777:[2]:[0]:[0]:[48]:[5000.0003.0007]:[32]:
[10.10.10.10]/248
AS-Path: NONE, path sourced internal to AS
11.11.11.11 (metric 41) from 1.1.1.1 (1.1.1.1)
Origin IGP, MED not set, localpref 100, weight 0
Received label 10100
Extcommunity: RT:65501:10100 SOO:1.1.1.1:256 ENCAP:8
ESI: 0301.0203.0405.0600.0007
Path type: internal, path is valid, not best reason: Router Id, no labeled nex
thop
Imported from 2.2.2.2:32777:[2]:[0]:[0]:[48]:[5000.0003.0007]:[32]:
[10.10.10.10]/248
AS-Path: NONE, path sourced internal to AS
22.22.22.22 (metric 41) from 2.2.2.2 (2.2.2.2)
Origin IGP, MED not set, localpref 100, weight 0
Received label 10100
Extcommunity: RT:65501:10100 ENCAP:8
ESI: 0301.0203.0405.0600.0007
Path-id 1 not advertised to any peer
01-30-2025 01:32 AM
Hey @Ratheesh mv
is it expected behavior in the ES scenario ?
The described behavior is expected in an Ethernet Segment (ES) scenario. The re-origination of the route with the SOO (Site of Origin) attribute, the BGP EVPN route selection process, and the ARP table consistency all align with the expected behavior in a multi-homed EVPN deployment.
Hope This Helps!!!
AshSe
Forum Tips:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide