frr
frr copied to clipboard
BGP route distinguisher not working
Description
I have two VRFs vrf1 and dummy_vrf1, and i want to import routes learned in each vrf to the other one. But when I try the below config, I see the learned routes in their respective VRFs but not imported to other one. Also, I don't see rd and rt config being applied anywhere in the vtysh cli.
Version
FRRouting 8.0.1
How to reproduce
I have below config for the same:-
router bgp 65001 vrf dummy_vrf_1
bgp router-id 192.168.251.124
no bgp network import-check
neighbor 24.2.1.102 remote-as 65001
neighbor 2001:24:2:1::102 remote-as 65001
!
address-family ipv4 unicast
neighbor 24.2.1.102 soft-reconfiguration inbound
rd vpn export 65001:100
rt vpn import 65001:100 65001:200
rt vpn export 65001:100
export vpn
import vpn
exit-address-family
!
address-family ipv6 unicast
neighbor 2001:24:2:1::102 activate
neighbor 2001:24:2:1::102 soft-reconfiguration inbound
exit-address-family
!
router bgp 65001 vrf vrf_1
bgp router-id 192.168.251.124
no bgp network import-check
neighbor 37.2.1.102 remote-as 65001
neighbor 2001:37:2:1::102 remote-as 65001
!
address-family ipv4 unicast
network 24.1.1.0/24
network 48.1.1.0/24
redistribute kernel
neighbor 37.2.1.102 soft-reconfiguration inbound
rd vpn export 65001:200
rt vpn import 65001:200 65001:100
rt vpn export 65001:200
export vpn
import vpn
exit-address-family
!
address-family ipv6 unicast
network 2001:24:1:1::/64
network 2001:48:1:1::/64
neighbor 2001:37:2:1::102 activate
neighbor 2001:37:2:1::102 soft-reconfiguration inbound
exit-address-family
!
Expected behavior
vtysh cli does not show any route distinguisher config:-
j3chysr01stg06# show bgp vrf er_vrf_1 ipv4 vpn
No BGP prefixes displayed, 0 exist
j3chysr01stg06#
Actual behavior
Ideally I should be seeing routes learned in vrf1 being imported to dummy_vrf1 and vice versa.
Additional context
No response
Checklist
- [X] I have searched the open issues for this bug.
- [X] I have not included sensitive information in this report.
Before spending the time digging if this is a real issue or not, could you verify if it's still the problem on the latest versions (9.1, 10.0, or even master)?
I'm using the topology mentioned above to attempt and reproduce this bug
Have you tried the latest versions of FRR?
So, closing this issue?
where to see the code changes for this bug