You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a setup where l3leaf switches are providing uplinks to hosts and l2leaf switches via EVPN multihoming. The l2leaf switches are using LACP portchannel to connect to the l3leaf switches.
The creation of portchannels on l2leaf works flawlessly. But on the l3leaf the same port-channel are created on the two l3leaf switches with different ethernet segment identifiers and lacp system ids.
While testing we found out, that the issue is using short_esi: auto. When using seting short_esi manually it works out.
Please fix the creation of uplink port-channels for l2leaf switches to l3leaf switches by using short_esi:auto.
Following code snippets were used to create the issue:
Issue Summary
We have a setup where l3leaf switches are providing uplinks to hosts and l2leaf switches via EVPN multihoming. The l2leaf switches are using LACP portchannel to connect to the l3leaf switches.
The creation of portchannels on l2leaf works flawlessly. But on the l3leaf the same port-channel are created on the two l3leaf switches with different ethernet segment identifiers and lacp system ids.
While testing we found out, that the issue is using
short_esi: auto
. When using setingshort_esi
manually it works out.Please fix the creation of uplink port-channels for l2leaf switches to l3leaf switches by using
short_esi:auto
.Following code snippets were used to create the issue:
This creates port-channels as below:
l3leaf-1
l3leaf-2
Which component(s) of AVD impacted
eos_designs
How do you run AVD ?
Ansible CLI with AVD Runner
Steps to reproduce
Relevant log output
No response
Contributing Guide
The text was updated successfully, but these errors were encountered: