Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vteps specific entry not added when a global vtep entry exist #17

Open
lmaleasi opened this issue Jul 15, 2021 · 0 comments
Open

vteps specific entry not added when a global vtep entry exist #17

lmaleasi opened this issue Jul 15, 2021 · 0 comments

Comments

@lmaleasi
Copy link

lmaleasi commented Jul 15, 2021

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:

TASK [eos/eos.vxlan : debug] ***************************************************
ok: [DEV-ARISTA-LMAL-05] => {
    "msg": [
        "ARISTA.EOS-VXLAN config:",
        "vxlan: {'name': 'Vxlan1', 'source_interface': 'Loopback1'}",
        "vteps: [{'vtep': ['10.16.30.1', '10.16.30.2'], 'vlan': 2624}]",
        "vlans: [{'vlanid': 2624, 'name': 'TEST_LIO', 'vni': '2624'}]"
    ]
}
ok: [DEV-ARISTA-LMAL-MAC-SW-WAN-01] => {
    "msg": [
        "ARISTA.EOS-VXLAN config:",
        "vxlan: {'name': 'Vxlan1', 'source_interface': 'Loopback1'}",
        "vteps: [{'vtep': ['10.16.30.2', '10.16.30.3'], 'vlan': 2624}]",
        "vlans: [{'vlanid': 2624, 'name': 'TEST_LIO', 'vni': '2624'}]"
    ]
}
ok: [DEV-ARISTA-LMAL-GEM-SW-WAN-01] => {
    "msg": [
        "ARISTA.EOS-VXLAN config:",
        "vxlan: {'name': 'Vxlan1', 'source_interface': 'Loopback1'}",
        "vteps: [{'vtep': ['10.16.30.1', '10.16.30.3'], 'vlan': 2624}]",
        "vlans: [{'vlanid': 2624, 'name': 'TEST_LIO', 'vni': '2624'}]"
    ]
}

and the output of the vtep implementation of the arista.eos-vxlan role:

TASK [arista.eos-vxlan : Arista EOS Vxlan vtep resources (Ansible >= 2.2)] *****
ok: [DEV-ARISTA-LMAL-MAC-SW-WAN-01] => (item={'vtep': ['10.16.30.2', '10.16.30.3'], 'vlan': 2624})
changed: [DEV-ARISTA-LMAL-05] => (item={'vtep': ['10.16.30.1', '10.16.30.2'], 'vlan': 2624})
changed: [DEV-ARISTA-LMAL-GEM-SW-WAN-01] => (item={'vtep': ['10.16.30.1', '10.16.30.3'], 'vlan': 2624})

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:

DEV-ARISTA-LMAL-01#show running-config interfaces vxlan 1
interface Vxlan1
   vxlan source-interface Loopback1
   vxlan udp-port 4789
   vxlan flood vtep 10.16.30.99

And after the playbook execution on this switch:

DEV-ARISTA-LMAL-01#show running-config interfaces vxlan 1
interface Vxlan1
   vxlan source-interface Loopback1
   vxlan udp-port 4789
   vxlan vlan 2624 vni 2624
   vxlan flood vtep 10.16.30.99

=> the vni implementation is OK but not the vtep specific one. I also have this parameter set :

eos_purge_vxlan: false

I've tested it on version 2.1.8 of this role, and here is the ansible version:

ansible 2.9.18
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/var/lib/awx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.6/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.6.8 (default, Aug 24 2020, 17:57:11) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant