# vmware\_guest multiple adapter

**URL:** <https://forum.ansible.com/t/vmware-guest-multiple-adapter/33492>\
**Category:** Ansible Project\
**Tags:** vmware\
**Created:** [July 25, 2020, 4:53am UTC](https://forum.ansible.com/t/vmware-guest-multiple-adapter/33492 "2020-07-25T04:53:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mpunix](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@mpunix](https://forum.ansible.com/u/mpunix)\
**Post date:** [July 25, 2020, 4:53am UTC](https://forum.ansible.com/t/vmware-guest-multiple-adapter/33492/1 "2020-07-25T04:53:13Z")

</div>

Hi,

I am trying to setup a RHEL7 VMware Linx VM on Vcenter 6.5 with ansible 2.9 with multiple adapters, it looks I am getting inconsistent results with the VMware adapter mac address and OS level ethx mapping. First I created with one interface (eth0), it works perfectly and matches with VM adapter mac address and OS interface output. When I add two or three adapters with vmware\_guest or vmware\_guest\_network module, the order of the creation works fine but on the os level mac address does not matches to the order of the VM adapter VLAN.

Example:

vars:  
network\_interfaces:

- name: VLAN1  
type:static  
ip: 1.1.1.1  
netmask: 255.255.255.0
- name: VLAN2
- name: VLAN3

I just want to create eth0 ip/netmask during the initial VM creation and configure the eth1, eth2 with Ansible at the later stage.

On the playbook, I call the network\_interfaces variable

networks: “{{ network\_interfaces }}”  
wait\_for\_ip\_address: yes

Does anyone come across the issue? Just wondering am I missing on the network\_interfaces variable definition.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![mpunix](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@mpunix](https://forum.ansible.com/u/mpunix)\
**Post date:** [July 25, 2020, 3:19pm UTC](https://forum.ansible.com/t/vmware-guest-multiple-adapter/33492/2 "2020-07-25T15:19:10Z")

</div>

Hi - Just to update, it seems the issue relate to the VMXnet3 driver where VM configured with 4 or more adapters cause this ordering issue and not related to ansible module.

[https://support.kemptechnologies.com/hc/en-us/articles/201978745-When-adding-4-or-more-VMXNET3-NICs-to-a-VLM-in-VMware-the-order-is-wrong](https://support.kemptechnologies.com/hc/en-us/articles/201978745-When-adding-4-or-more-VMXNET3-NICs-to-a-VLM-in-VMware-the-order-is-wrong)