bgpd: Ignore auto created VRF BGP instances #16159
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Configuration:
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 createrouter 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:
Fixes: #16152
Fixes: #9537