Posted on March 29, 2020 3:32 pm
 |  Asked by Roman Roman
 |  129 views
RESOLVED
0
0
Print Friendly, PDF & Email

Hi,

Is it normal that in BGP EVPN the local connected routes are not imported locally in another VRF ?

On a leaf I have:

router bgp 55000

….

vrf VRFA
rd 55001:55001
route-target import evpn 55001:55001
route-target import evpn 55002:55002
route-target export evpn 55001:55001
redistribute connected
!
vrf VRFB
rd 55002:55002
route-target import evpn 55001:55001
route-target import evpn 55002:55002
route-target export evpn 55002:55002
redistribute connected
!

The other part of the conf

vrf definition VRFA
vrf definition VRFB

ip routing vrf VRFA
ip routing vrf VRFB

int vxlan1
vxlan vrf VRFA vni 55001
vxlan vrf VRFB vni 55002

int lo151
vrf forwarding VRFA
ip address 55.151.0.2/32

int lo152
vrf forwarding VRFB
ip address 55.152.0.2/32

 

The underlay BGP and overlay BGP EVPN  is up with the SPINES (even if it does not matter I think)

Arista-imp-exp#sh ip route vrf VRFA

C 55.151.0.2/32 is directly connected, Loopback151

 

Arista-imp-exp#sh ip route vrf VRFB

C 55.152.0.2/32 is directly connected, Loopback152

 

I was expected to see both routes in both routing table or at least as the evpn routes

Is this the normal behavior or I missiong something ?

 

0
Posted by Aniket Bhowmick
Answered on March 29, 2020 6:05 pm

Hi Roman,

The current configuration you applied is used only to import/export route in EVPN table. It cannot be used to leak directly connected routes in different VRF.

If you want to leak locally connected routes in other VRF's, please read the below article:

https://eos.arista.com/eos-4-21-3f/inter-vrf-local-route-leaking/

After reading the article if you have any concern, please let us know.

Thanks & Regards,

Aniket

0
Posted by Roman Roman
Answered on April 4, 2020 9:17 am

Hi Aniket,

Thank you for your reply. I  had previously read this article: https://www.arista.com/en/um-eos/eos-section-23-6-inter-vrf-local-route-leaking and I tried also  route-target import/export vpnv4-ipv4  and it did'nt work.  I think I forgot to activate mpls ip, I did it and it started to work as expected.  But, my tests were done in the veos version 4.21.1.1F.

I tried a new veos version 4.23.2.1F and  I didn't need anymore theses commands

  • mpls ip
  • service routing protocols model multi-agent
  • route-target import/export vpnv4-ipv4 in bgp

It works only with the commands in my first post. It is magic or Arista updated the functionalities of local vrf leaking.

 

Thank you

Roman

0
Posted by Roman Roman
Answered on April 4, 2020 9:23 am

p.s Thank you for the article. I think it needs maybe some updates. These commands bellow, from the article cannot be configured at the same time

1. Under router bgp vrf config mode:

switch(config-router-bgp-vrf-services-vrf)# route-target {import|export} [evpn|vpn-ipv4|vpn-ipv6] route-map <RM>

switch(config-router-bgp-vrf-services-vrf)# {no|default} route-target {import|export} [evpn|vpn-ipv4|vpn-ipv6] route-map [<RM>]

2. Under router bgp vrf address-family ipv4 config mode:

switch(config-router-bgp-vrf-services-vrf-af)# route-target {import|export} [evpn|vpn-ipv4] route-map <RM>

switch(config-router-bgp-vrf-services-vrf-af)# {no|default} route-target {import|export} [evpn|vpn-ipv4] route-map [<RM>]

 

 

0
Posted by Aniket Bhowmick
Answered on April 15, 2020 3:00 am

Hi Roman,

Whatever you configure in "router bgp vrf config mode"  is by default part of "vrf address-family ipv4". So there is no need for configuring the same thing in both "router bgp vrf config mode" and  "address-family ipv4" as both are same.

The "address-family ipv4" is additionally used to deactivate IPv4 BGP neighbourship for those IP's which is being used to form EVPN/VPN-v4 neighbourship. Otherwise, with same IP, both EVPN/VPN-v4 and IPv4 BGP neighbourship will be established.

Regarding the part where you mentioned- "I tried a new veos version 4.23.2.1F and I didn't need anymore theses commands ..", can you please specify the source of this information ? 

AFAIK, the configuration in your first post cannot be used to leak directly connected routes in different VRFs in same switch. Those configurations is specific to EVPN which will do the following- it will create ip-prefix (Type-5) for all your directly connected subnet in VRFA and VRFB and will be advertised to all the EVPN peers. Also, it can install any route which comes with route-targets as specified as "export" in the respective VRFs.

It will be good if you can share the documentation from where you referred this configuration to leak directly connected routes in different VRF on same device.

Thanks,

Aniket

 

Post your Answer

You must be logged in to post an answer.