0.- not clear on if after adding ESXi host to the custer the error happens or after prepare to VXLAN
1.- verify please check host.event log file and paste what is in the logs here
2.- check vmkernel log as well
3.- check if VTEP ip pool has enough ip addresses
Firstly do check NTP/DNS of the new host which is added to the cluster.
I have confiemed the there is more than enough vxlan IP addresses however I did need to free some using the API as there were not being release when removing other hosts.
I have posted the esxcli.log and notice an error. I cannot see to find the host event error log that you ask
I have also looked at the vmkernel.log and cannot see anything that stands out.
All DNS and NTP info are correct and is exactly the same as every other host that gets added to the cluster.
I believe that the vibs have been installed as the hosts works perfectly fine and as the error is cluster based the error is not particular to any given host.
I can ping the vcenter from the host and reverse DNS is working too.
Looks like VIbs are loaded to the host . If feasible try rebooting the host once and confirm the status.
can you please be so kind to post this logs as well?
VTEP Pool shows not assigned any IP's
ESXi servers are rebooted but still having same issue
Did you have any luck solving this? we had to change the VXLAN VLANID on a fully configured and are now stuck for one host in one cluster...... It seems a bit overkilling to destroy and rebuild from scratch....