host1#esxcfg-vmk -l | grep vmk0
vmk0 29 IPv4 169.254.0.2 255.255.255.0 169.254.0.255 ##:##:##:##:##:8d 1500 65535 true STATIC defaultTcpipStackvmk0 29 IPv6 ####::###:####:####:1234 64 ##:##:##:##:##:8d 1500 65535 true STATIC, PREFERRED defaultTcpipStack
host2#esxcfg-vmk -l | grep vmk0
vmk0 83 IPv4 169.254.0.2 255.255.255.0 169.254.0.255 ##:##:##:##:##:91 1500 65535 true STATIC defaultTcpipStackvmk0 83 IPv6 ####::###:####:####:1235 64 ##:##:##:##:##:91 1500 65535 true STATIC, PREFERRED defaultTcpipStack
Error: Node host1.example.com with same ip <IP address of host host1.example.com> already exists. Check the state of existing transport node. If it is a failure in deletion then use force option to delete previous transport node and retry the operation. If the host is part of a cluster having transport node profile applied then then move the host into datacenter before deletion. Refer KB article number 319975 for more details. (Error code: 26210)The IPv4 APIPA (169.254.0.2) address was manually configured on the ESXi host.
If vmk0 is using IPv6, as seen above, managed by VxRail, clear the manually configured IPv4 address:
#esxcli network ip interface ipv4 set -t none
If there is no duplicate IP address found, please review this KB mentioned in the error, which deals with stale host which can also lead to the same error message:
Installing or Upgrading NSX on an ESXi host fails reporting the node already exists
If in doubt, please consult VxRail support to confirm correct vmk0 IP assignment.