Setting maximum paths & ecmp for eBGP in eos_l3ls_evpn role #442
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.
Change Summary
In the current AVD model, the number of maximum paths and the number of ecmp paths can not be set. It is configured automatically using the number of spines in the fabric as a reference. In some design the desired maximum paths is the target number of spines from the beginning on even though spines will be added little by little. In this case, this value can be set manually in the fabric description.
Types of changes
Related Issue(s)
#384
Component(s) name
eos_l3ls_evpn role
Proposed changes
The new optional keys are added in the description of the fabric as follows:
How to test
Add for example the following values and keys in DC1_FABRIC.yml:
This will render the following structured config file (at the bottom of all the other declared bgp_defaults values):
If not defined, it will simply render the line above with the number of spines instead of 8.
Checklist:
pre-commit
,make linting
andmake sanity-lint
).