-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frr won't load different bgp config with different asn in different vrf #9537
Comments
I can't reproduce it on both 7.5.1 and master. |
Here is my full config, which may help, or if I can provide something else? And as I install frr by the using the And then I have noticed there are some patches like this: Should I do something else that may help? |
The problem is reproducible with the full config. |
This issue is stale because it has been open 180 days with no activity. Comment or remove the |
This issue will be automatically closed in the specified period unless there is further activity. |
I don't think it's good to just close a reproducible bug just for inactivity. |
This issue will no longer be automatically closed. |
This issue is stale because it has been open 180 days with no activity. Comment or remove the |
This issue will be automatically closed in the specified period unless there is further activity. |
Again, I don't think it's reasonable to just close a reproducible bug just for inactivity. |
This issue will no longer be automatically closed. |
Configuration: ``` vtysh <<EOF configure vrf vrf100 vni 10100 exit-vrf router bgp 50 address-family l2vpn evpn advertise-all-vni exit-address-family exit router bgp 100 vrf vrf100 exit EOF ``` TL;DR; When we configure `advertise-all-vni` (in this case), a new BGP instance is created with the name vrf100, and ASN 50. Next, when we create `router bgp 100 vrf vrf100`, we look for the BGP instance with the same name and we found it, but ASNs are different 50 vs. 100. Every such a new auto created instance is flagged with BGP_VRF_AUTO. After the fix: ``` router bgp 50 ! address-family l2vpn evpn advertise-all-vni exit-address-family exit ! router bgp 100 vrf vrf100 exit ! end donatas.net(config)# router bgp 51 BGP is already running; AS is 50 donatas.net(config)# router bgp 50 donatas.net(config-router)# router bgp 101 vrf vrf100 BGP is already running; AS is 100 donatas.net(config)# router bgp 100 vrf vrf100 donatas.net(config-router)# ``` Fixes: FRRouting#16152 Fixes: FRRouting#9537 Signed-off-by: Donatas Abraitis <[email protected]>
Describe the bug
While using different asn in BGP in different vrf, the configuration will not load correctly as the BGP after the first in the config file will be ignored and still use the first asn and drop all the configuration.
[X] Did you check if this is a duplicate issue?
[ ] Did you test it on the latest FRRouting/frr master branch?
To Reproduce
Config like
write memory
exit vtysh
service frr restart
vtysh
show run
and then check the output
Expected behavior
The config is loaded correctly and service running correctly.
Screenshots
Versions
Additional context
I can actually run
service frr reload
to workaround this thing but if bgpd is being restarted, it will not load config correctly.The text was updated successfully, but these errors were encountered: