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
Hello,
When a global vtep entry already exist on the switch and that I launch this role with a specific vtep entry to add, the task simply says it's OK and not changed.
Here is a debug output of the configuration passed to the arista.eos-vxlan role:
You can see that on the DEV-ARISTA-LMAL-MAC-SW-WAN-01 nothing is changed => because it is the only switch with an already configured default vtep entry, here is the vxlan running-configuration before the playbook execution on this switch:
Hello,
When a global vtep entry already exist on the switch and that I launch this role with a specific vtep entry to add, the task simply says it's OK and not changed.
Here is a debug output of the configuration passed to the arista.eos-vxlan role:
and the output of the vtep implementation of the arista.eos-vxlan role:
You can see that on the
DEV-ARISTA-LMAL-MAC-SW-WAN-01
nothing is changed => because it is the only switch with an already configured default vtep entry, here is the vxlan running-configuration before the playbook execution on this switch:And after the playbook execution on this switch:
=> the vni implementation is OK but not the vtep specific one. I also have this parameter set :
I've tested it on version
2.1.8
of this role, and here is the ansible version:The text was updated successfully, but these errors were encountered: