curl -v telnet://<Affected_ESXI_Mgmt_IP>:<port#>nc -z <vcenter_ip> <port#>
nc -zu <vcenter_ip> <902>nslookup, forward and reverse name resolutions work on both the vCenter Server and the affected host and they are able to resolve each other's FQDNs and IP addresses:nslookup <IP/FQDN>Disconnected from host. Reason: Cannot verify the SSL trust
/var/run/log/vobd.log file of the affected ESXi hosts and other hosts in the cluster, entries similar to the following indicate an IP conflict with the affected ESXi host's management IP address:YYYY-MM-DDThh:mm:ss In(##) vobd[#######]: [netCorrelator] ########us: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for <Affected_ESXI_Mgmt_IP> on interface vmk0. The current owner is <Duplicate_IP_owner_MAC>.YYYY-MM-DDThh:mm:ss In(##) vobd[#######]: [netCorrelator] ########us: [esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for <Affected_ESXI_Mgmt_IP> on interface vmk0, current owner being <Duplicate_IP_owner_MAC>.YYYY-MM-DDThh:mm:ss In(##) vobd[#######]: The event ([esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for <Affected_ESXI_Mgmt_IP> on interface vmk0, current owner being <Duplicate_IP_owner_MAC>) was sent immediately to hostd;
To resolve the IP conflict, follow the below steps
Identify the node or device that currently owns the duplicate IP address on the management network. Work with your network team and use the MAC address obtained from the vobd.log file to locate the conflicting node.
Remove or reconfigure the conflicting node with a different, available IP address.
If reconfiguring the conflicting node is not feasible, perform the following steps to change the affected ESXi host IP:
Remove the affected ESXi host from the vCenter Server inventory.
Connect directly to the affected ESXi host via the Direct Console User Interface (DCUI).
Change the management IP address to a new, unused static IP address, or configure it to use DHCP.
Add the ESXi host back to the vCenter Server inventory.