Replies: 1 comment
-
|
Take a look at this section https://avd.arista.com/5.7/ansible_collections/arista/avd/roles/eos_designs/docs/input-variables.html#connected-endpoints-settings under the example dropdown "Example with EVPN A/A ESI dual-attached endpoint". I think that should do what you need. We have a default key for connected endpoints called "switches" which seems fitting for this, so replace the top level |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are building an MPLS + iBGP backbone with IS-IS underlay. For connections towards a legacy layer-2 core, we want to use EVPN multihoming to create an L2 port channel terminating on two different Arista backbone switches.
I tried adding this structured config piece:
The generated structured config however includes peer_groups two times, one is from the general config and one from the snippet.
It generally feels like a workaround. Is there any good example (or can somebody provide one here) that we can follow?
Beta Was this translation helpful? Give feedback.
All reactions