Posted on July 19, 2021 2:58 am
 |  Asked by Michael Witte
 |  24 views
0
0
Print Friendly, PDF & Email

I am using vEOS to build out a spine-leaf EVPN fabric, and using CVP, IPAM and cloud builder to push out appropriate configs. Each P-P link is a vswitch then i map the appropriate port groups which then map to the correct eth ports in the vEOS switch. CVP and cloud builder all seems to work fine building the config but I was having weird connectivity issues. After a great deal of digging it appears that the mapping of the vSphere VMs port groups and hence vswitch and P-P links  to vEOS Switches are bound correctly but upon reboot remap randomly. For instance VM portgroup nics 0-4 would be nic0= mgmt ,then portgroup nic 1-4 would be eth1,eth2,eth3,eth4. so then when applying configs via cloudbuilder it would create the configs for the appropriate NIC connectivity

What i found after digging into LLDP neighbors and matching mac addreses of the VM port group NIC 1, to the say eth1  after a reboot it could become eth4 which is verified by LLDP neighbors and mac addresses of the th port.

So on my spine;

NIC 1 MAC=Eth1 MAC

NIC 2 MAC =Eth2 MAC

NIC 3 MAC =Eth3 MAC

NIC 4 MAC =Eth4 MAC

After the reboot

NIC 1 MAC =Eth4 MAC

NIC 2 MAC =Eth1 MAC

NIC 3 MAC =Eth3 MAC

NIC 4 MAC =Eth2 MAC

This is repeatable and appears to have something with the way the interfaces come up and grabs the next port group really have no explanation. I dont know how to reserve the VM port group to vEOS eth mapping so its consistent and its impossible to reliably build a lab with this issue.

0
Posted by Tamas Plugor
Answered on July 19, 2021 1:29 pm

Seems like you're hitting the same issue describe by Colin here: https://eos.arista.com/forum/veos-cloudeos-and-interface-ordering/

Post your Answer

You must be logged in to post an answer.