Posted on November 10, 2021 4:07 pm
 |  Asked by Radim Roska
 |  64 views
RESOLVED
0
0
Print Friendly, PDF & Email

Hello,

I’m trying to configure EVPN multidomain in the vEOS based lab (version 2.6.23M). I have DC1 – GW1 – GW2 – DC2.

I started with Layer 2 service. Is that supported on vEOS?  I can configure everything as in the eos article:

Multi-Domain EVPN VXLAN

Just instead of asymmetric IRB, I use symmetric.

The problem appears that the MAC-IP route is correctly advertised from LEAF1 => GW1, then GW1 => GW2 advertise it, but does not change the next hop…and as I understand, it should :)

So maybe its because of vEOS? :)

Follows MAC-IP route on GW1
dc1-bleaf1(config-macvrf-102)#sh bgp evpn route-type mac-ip domain remote detail
BGP routing table information for VRF default
Router identifier 10.0.0.4, local AS number 65001
BGP routing table entry for mac-ip 5000.002f.d8fe remote, Route Distinguisher: 100.0.0.1:102
Paths: 1 available
Local
- from - (0.0.0.0)
Origin IGP, metric -, localpref -, weight 0, valid, local, best
Extended Community: Route-Target-AS:65002:102 TunnelEncap:tunnelTypeVxlan
VNI: 10102 ESI: 0000:0000:0000:0000:0000

Follows MAC-IP in GW2, where its obvious that its invalid

dc2-bleaf1(config)#sh bgp evpn route-type mac-ip detail
BGP routing table information for VRF default
Router identifier 20.0.0.1, local AS number 65002
BGP routing table entry for mac-ip 5000.002f.d8fe remote, Route Distinguisher: 100.0.0.1:102
Paths: 1 available
65001
10.0.1.4 from 100.0.0.1 (10.0.0.4)
Origin IGP, metric -, localpref 100, weight 0, invalid, external
Extended Community: Route-Target-AS:65002:102 TunnelEncap:tunnelTypeVxlan
VNI: 10102 ESI: 0000:0000:0000:0000:0000

configuraiton on GW1 of the bridgedomain..

dc1-bleaf1(config-macvrf-102)#sh a
router bgp 65001
vlan 102
rd 10.0.0.4:102
rd evpn domain remote 100.0.0.1:102
route-target both 65001:10102
route-target import export evpn domain remote 65002:102
redistribute learned
dc1-bleaf1(config-macvrf-102)#sh run int vx1
interface Vxlan1
vxlan source-interface Loopback1
vxlan udp-port 4789
vxlan vlan 102 vni 10102
vxlan vlan 103 vni 10103

Thanks for hints ;)
Radim

0
Posted by Radim Roska
Answered on November 11, 2021 10:32 am

well...i found the issue :), it was just my mistake, I somehow did not realize that GW is readvertising the crossdomain BGP EVPN route using its VTEP IP. Solution therefore is to make VTEP IP reachable over the DCI network...

It works on vEOS.

it was not obvious from that article i refered to ...

0
Posted by Jeffrey Nelson
Answered on November 11, 2021 6:47 pm

Hi Radim, glad you found the issue, and yes, this feature works on vEOS-lab on 4.26.1F and above. I will update that article you linked to include vEOS-lab, cheers

Post your Answer

You must be logged in to post an answer.