chore(agent): adv. all VTEPs on leaves #1238
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
regardless of fabric or mesh links. this allows us to e.g. connect gateways to leaves in spine-leaf topologies, whereas right now the VTEP of the gateway would not be advertised by the leaf attached to it. The only downside of this is that we are advertising some routes which will be rejected by our peers, but the configuration is simpler, and the alternative (adding the gateway VTEP to the prefix list of advertised routes) is quite convoluted, since that VTEP is only present on the gateway object, not on the connection. Signed-off-by: Emanuele Di Pascale <[email protected]>
|
🚀 Temp artifacts published: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
regardless of fabric or mesh links. this allows us to e.g. connect gateways to leaves in spine-leaf topologies, whereas right now the VTEP of the gateway would not be advertised by the leaf attached to it. The only
downside of this is that we are advertising some routes which will be rejected by our peers, but the configuration is simpler, and the alternative (adding the gateway VTEP to the prefix list of advertised routes) is quite convoluted, since that VTEP is only present on the gateway object, not on the connection.
Fix #1237