route leak to VRF L3VPN #12475

AndreyBaycharov · 2022-12-09T06:50:50Z

AndreyBaycharov
Dec 9, 2022

Hi all!
When setting up an l3vpn between FRR and Cisco, I see a problem with a route leak to VRF.

I have same IP on interface loopback global vrf and clients vrf "test"
On the cisco in the route table vrf test i see route to 1.1.1.1/32

There is no route in 3.3.3.3/32 in the VRF table on FRRrouting

At the same time, other routes from cisco are included in the table
2022/12/09 09:39:08 BGP: [WNKP5-SN018] Found existing bnc 3.3.3.3/32(0)(VRF default) flags 0x4b ifindex 0 #paths 0 peer 0x74dab008
2022/12/09 09:39:08 BGP: [T6H55-B8TR5][EC 33554502] 3.3.3.3 Vendor specific capability 131
2022/12/09 09:39:08 BGP: [T5AAP-5GA85] 3.3.3.3(Unknown) rcvd UPDATE w/ attr: , origin ?, localpref 100, metric 0, extcommunity RT:64500:100, path
2022/12/09 09:39:08 BGP: [PCFFM-WMARW] 3.3.3.3(Unknown) rcvd UPDATE wlen 0 attrlen 115 alen 0
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd RD 64500:100 11.11.11.11/32 label 21 IPv4 vpn
2022/12/09 09:39:08 BGP: [WNKP5-SN018] Found existing bnc 3.3.3.3/32(0)(VRF default) flags 0x4b ifindex 0 #paths 0 peer 0x74dab008
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd RD 64500:100 192.168.20.0/24 label 20 IPv4 vpn
2022/12/09 09:39:08 BGP: [WNKP5-SN018] Found existing bnc 3.3.3.3/32(0)(VRF default) flags 0x4b ifindex 0 #paths 1 peer 0x74dab008
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd RD 64500:100 3.3.3.3/32 label 17 IPv4 vpn
2022/12/09 09:39:08 BGP: [N1KDM-HR02D] bgp_find_or_add_nexthop(3.3.3.3/32): prefix loops through itself
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd RD 64500:100 3.3.3.4/32 label 22 IPv4 vpn
2022/12/09 09:39:08 BGP: [WNKP5-SN018] Found existing bnc 3.3.3.3/32(0)(VRF default) flags 0x4b ifindex 0 #paths 2 peer 0x74dab008
2022/12/09 09:39:08 BGP: [T5AAP-5GA85] 3.3.3.3(Unknown) rcvd UPDATE w/ attr: , origin ?, localpref 100, metric 0, extcommunity RT:64500:200, path
2022/12/09 09:39:08 BGP: [PCFFM-WMARW] 3.3.3.3(Unknown) rcvd UPDATE wlen 0 attrlen 68 alen 0
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd RD 64500:200 99.99.99.99/32 label 23 IPv4 vpn
2022/12/09 09:39:08 BGP: [PCFFM-WMARW] 3.3.3.3(Unknown) rcvd UPDATE wlen 0 attrlen 6 alen 0
2022/12/09 09:39:08 BGP: [G3V0W-FSWRC] bgp_best_path_select_defer: processing route for IPv4 VPN : cnt 0
2022/12/09 09:39:08 BGP: [M59KS-A3ZXZ] bgp_update_receive: rcvd End-of-RIB for IPv4 VPN from 3.3.3.3 in vrf default
2022/12/09 09:39:08 BGP: [T5AAP-5GA85] 3.3.3.3(Unknown) rcvd UPDATE w/ attr: nexthop 3.3.3.3, localpref 100, metric 0, path
2022/12/09 09:39:08 BGP: [PCFFM-WMARW] 3.3.3.3(Unknown) rcvd UPDATE wlen 0 attrlen 41 alen 0
2022/12/09 09:39:08 BGP: [YCKEM-GB33T] 3.3.3.3(Unknown) rcvd 3.3.3.3/32 IPv4 unicast
2022/12/09 09:39:08 BGP: [N1KDM-HR02D] bgp_find_or_add_nexthop(3.3.3.3/32): prefix loops through itself
2022/12/09 09:39:08 BGP: [YT4EY-7V2YV] bgp_update(3.3.3.3): NH unresolved
2022/12/09 09:39:08 BGP: [PCFFM-WMARW] 3.3.3.3(Unknown) rcvd UPDATE wlen 0 attrlen 0 alen 0
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=vpn, p=11.11.11.11/32
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=vpn, p=192.168.20.0/24
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=vpn, p=3.3.3.3/32
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=vpn, p=3.3.3.4/32
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=vpn, p=99.99.99.99/32
2022/12/09 09:39:08 BGP: [K423X-ETGCQ] group_announce_route_walkcb: afi=IPv4, safi=labeled-unicast, p=3.3.3.3/32
2022/12/09 09:39:09 BGP: [K9G3A-CJ5QQ] u27:s27 announcing routes upon coalesce timer expiry(1050 ms)
2022/12/09 09:39:09 BGP: [JQB4F-DXP0F] subgroup_announce_check: BGP_PATH_ANNC_NH_SELF, family=IPv4
2022/12/09 09:39:09 BGP: [K9G3A-CJ5QQ] u28:s28 announcing routes upon coalesce timer expiry(1050 ms)
2022/12/09 09:39:09 BGP: [TN0HX-6G1RR] u27:s27 send UPDATE w/ attr: nexthop 0.0.0.0, localpref 100, metric 0, extcommunity RT:64500:100, originator 1.1.1.1, path
2022/12/09 09:39:09 BGP: [H06SA-0JAPR] u27:s27 send MP_REACH for afi/safi IPv4/vpn
2022/12/09 09:39:09 BGP: [HVRWP-5R9NQ] u27:s27 send UPDATE RD 64500:100 1.1.1.1/32 label 144 IPv4 vpn
2022/12/09 09:39:09 BGP: [WEV7K-2GAQ5] u27:s27 send UPDATE len 93 (max message len: 4096) numpfx 1
2022/12/09 09:39:09 BGP: [MBFVT-8GSC6] u27:s27 3.3.3.3 send UPDATE w/ nexthop 1.1.1.1 and RD
The route arrives at the same time, but is not added to the VRF table

I found a similar problem #11837, but the FRR update didn't help.

AndreyBaycharov · 2022-12-09T07:06:03Z

AndreyBaycharov
Dec 9, 2022
Author

Config file from FRR
frr version 8.4.1
frr defaults traditional
hostname topaz-2530002866
log file /tmp/frr.log
no ip forwarding
service integrated-vtysh-config
!
debug bgp nht
debug bgp updates in
debug bgp updates out
!
interface e1p1
description R1-R2
ip address 10.10.10.1/30
mpls
mpls bgp forwarding
exit
!
interface loopback0
description vrf global
ip address 1.1.1.1/32
mpls
mpls bgp forwarding
exit
!
interface test
ip address 1.1.1.1/32
exit
!
router bgp 64500
bgp router-id 1.1.1.1
neighbor 3.3.3.3 remote-as 64500
neighbor 3.3.3.3 update-source loopback0
!
address-family ipv4 unicast
no neighbor 3.3.3.3 activate
exit-address-family
!
address-family ipv4 labeled-unicast
network 1.1.1.1/32
neighbor 3.3.3.3 activate
exit-address-family
!
address-family ipv4 vpn
neighbor 3.3.3.3 activate
exit-address-family
exit
!
router bgp 64500 vrf test
!
address-family ipv4 unicast
redistribute connected
label vpn export auto
rd vpn export 64500:100
rt vpn both 64500:100
export vpn
import vpn
exit-address-family
exit
!
router ospf
ospf router-id 1.1.1.1
network 1.1.1.1/32 area 0
network 10.10.10.0/30 area 0
exit
!
mpls ldp
router-id 1.1.1.1
!
address-family ipv4
discovery transport-address 1.1.1.1
!
interface e1p1
exit
!
interface e1p2
exit
!
interface loopback0
exit
!
exit-address-family
!
exit
!
end
Config file from cisco
R03#sh run

hostname R03
!
boot-start-marker
boot-end-marker
!
vrf definition test
rd 64500:100
route-target export 64500:100
route-target import 64500:100
!
address-family ipv4
exit-address-family

interface Loopback1
description global
ip address 3.3.3.3 255.255.255.255
mpls bgp forwarding
!
!
interface Loopback2
vrf forwarding test
ip address 3.3.3.3 255.255.255.255
!
!
interface Loopback3
vrf forwarding test
ip address 11.11.11.11 255.255.255.255
!
!
interface Loopback4
vrf forwarding test
ip address 3.3.3.4 255.255.255.255
!
interface GigabitEthernet0/0.20
vrf forwarding test
encapsulation dot1Q 20
ip address 192.168.20.1 255.255.255.0
!

interface GigabitEthernet0/1
ip address 30.30.30.1 255.255.255.252
duplex auto
speed auto
mpls bgp forwarding
mpls ip
!
!
interface GigabitEthernet0/2
ip address 20.20.20.1 255.255.255.252
duplex auto
speed auto
mpls bgp forwarding
mpls ip
!
!
!
router ospf 1
router-id 3.3.3.3
log-adjacency-changes
network 3.3.3.3 0.0.0.0 area 0
network 20.20.20.0 0.0.0.3 area 0
!
router bgp 64500
bgp router-id 3.3.3.3
bgp log-neighbor-changes
neighbor 1.1.1.1 remote-as 64500
neighbor 1.1.1.1 update-source Loopback1
!
address-family ipv4
no synchronization
network 3.3.3.3 mask 255.255.255.255
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-label
no auto-summary
exit-address-family
!
address-family vpnv4
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 send-community both
exit-address-family
!
address-family ipv4 vrf test
no synchronization
redistribute connected
exit-address-family

0 replies

AndreyBaycharov · 2022-12-09T08:27:30Z

AndreyBaycharov
Dec 9, 2022
Author

topaz-2530002866# sh ip bgp vrf test 3.3.3.3/32
BGP routing table entry for 3.3.3.3/32, version 0
Paths: (1 available, no best path)
Not advertised to any peer
Imported from 64500:100:3.3.3.3/32
Local
3.3.3.3 (inaccessible) from 0.0.0.0 (0.0.0.0) vrf default(0) announce-nh-self
Origin incomplete, metric 0, localpref 100, invalid, sourced, local
Extended Community: RT:64500:100
Remote label: 17
Last update: Fri Dec 9 11:17:37 2022
topaz-2530002866# sh ip bgp vrf test 3.3.3.4/32
BGP routing table entry for 3.3.3.4/32, version 11
Paths: (1 available, best #1, vrf test)
Not advertised to any peer
Imported from 64500:100:3.3.3.4/32
Local
3.3.3.3 (metric 2001) from 0.0.0.0 (0.0.0.0) vrf default(0) announce-nh-self
Origin incomplete, metric 0, localpref 100, valid, sourced, local, best (First path received)
Extended Community: RT:64500:100
Remote label: 22
Last update: Fri Dec 9 11:17:37 2022

0 replies

AndreyBaycharov · 2022-12-20T16:48:01Z

AndreyBaycharov
Dec 20, 2022
Author

I checked on 8.4.1, it doesn't work

0 replies

AndreyBaycharov · 2022-12-20T21:37:33Z

AndreyBaycharov
Dec 20, 2022
Author

Checked on 7.5.1, routes are being added. But icmp is still a problem...

0 replies

AndreyBaycharov · 2022-12-22T11:27:15Z

AndreyBaycharov
Dec 22, 2022
Author

On FRRouting 7.5.1 it work

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

route leak to VRF L3VPN #12475

{{title}}

Replies: 5 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

route leak to VRF L3VPN #12475

AndreyBaycharov Dec 9, 2022

Replies: 5 comments

AndreyBaycharov Dec 9, 2022 Author

AndreyBaycharov Dec 9, 2022 Author

AndreyBaycharov Dec 20, 2022 Author

AndreyBaycharov Dec 20, 2022 Author

AndreyBaycharov Dec 22, 2022 Author

AndreyBaycharov
Dec 9, 2022

AndreyBaycharov
Dec 9, 2022
Author

AndreyBaycharov
Dec 9, 2022
Author

AndreyBaycharov
Dec 20, 2022
Author

AndreyBaycharov
Dec 20, 2022
Author

AndreyBaycharov
Dec 22, 2022
Author