Fix(eos_designs): Remove EVPN related config if VRF 'default' is not EVPN enabled #2888
Conversation
This file contains 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
github-actions
bot
added
role: eos_designs
ClausHolbechArista
added
the
cherry-pick-for-3.8.x
ClausHolbechArista
force-pushed
the
fix/eos_designs/default-vrf-without-evpn
branch
from
32dff48
to
6220c73
Compare
.../molecule/eos_designs_unit_tests/inventory/host_vars/evpn-vtep-with-default-vrf-not-evpn.yml
Outdated
Show resolved
Hide resolved
…/inventory/host_vars/evpn-vtep-with-default-vrf-not-evpn.yml Co-authored-by: Carl Buchmann <carl.buchmann@arista.com>
Shivani-chourasiya
pushed a commit
to Shivani-chourasiya/ansible-avd
that referenced
this pull request
Jul 14, 2023
Merged
4 tasks
carlbuchmann
removed
the
cherry-pick-for-3.8.x
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.
Change Summary
Remove EVPN related config if VRF 'default' is not EVPN enabled
Related Issue(s)
For EVPN networks carrying VRF 'default' the best practice is to use the overlay (EVPN l3vni) for services, but keep loopbacks in the underlay. To avoid the services from being routed in the underlay, AVD implements route-maps and prefix-lists when VRF 'default' is defined on an EVPN VTEP.
It is possible to disable EVPN under the VRF configuration by setting
address_families:[]in which case the VRF should not be added to EVPN configuration, and the route-maps and prefix-lists should not be created at all.Before this fix, the route-maps and prefix-lists were still configured even if the VRF was not configured for EVPN. The VRF was also configured with a VNI under the VXLAN interface.
Component(s) name
arista.avd.eos_designsProposed changes
evpnaddress-family enabled (true by default)How to test
Added a molecule test case for this corner case.
No other changes to molecule outputs.
Checklist
User Checklist
Repository Checklist