ESXi Host Fails to Add to vCenter with "Host is Already Connected" Message
Article ID: 404373
Updated On:
Products
Issue/Introduction
When attempting to add the ESXi host to vCenter, the following error was encountered:
The host <hostname with FQDN or IP> is already connected to this vCenter Server.
This usually indicates that vCenter is detecting an IP address conflict or a stale entry, which blocks the addition of the host.
Environment
VMware vCenter Server 8.x
VMware vSphere ESXI 8.x
VMware vCenter Server 7.x
VMware vSphere ESXI 7.x
Cause
The output indicates that an IP address remains associated within the configuration store, despite the ESXi host no longer being inventoried by vCenter. This confirms that the error is caused by a persistent/lingering configuration entry that retains the IP address, leading to the misidentification of the host as already connected.
# configstorecli config current get -c esx -g services -k vpxa_solution_user_config | grep -i server_ip
Note: Run the command on the affected ESXi host by connecting through a PuTTY session. Use the management IP address `<Example: 12.123.12.123>`—the one listed under <Select ESXi Host > Configure > Networking > VMkernel Adapters>. If the output doesn't return anything, rerun the same command using `<Example: 12.123.12.1>`. This will show the old IP entry, which is still present in the **vpxa solution user configuration**, instead of the current IP assigned to the host.
There’s an old entry in the vpxa solution user configuration where the same IP is still listed. This is likely from a previous host or device that had registered the same IP with vCenter.
Log File: /var/run/log/vobd.log
Description: Log entries suggesting some other endpoint responding to IP address assigned to VMkernel Interfaces
YYYY-MM-DDTHH:MM:SS: [netCorrelator]: [esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for ##.###.##.### on interface vmk0, current owner being ##.##.##.##.##.##.YYYY-MM-DDTHH:MM:SS: [netCorrelator]: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for ##.###.##.### on interface vmk0. The current owner is ##.##.##.##.##.##.YYYY-MM-DDTHH:MM:SS: [netCorrelator]: [esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for ##.###.##.### on interface vmk0, current owner being ##.##.##.##.##.##.YYYY-MM-DDTHH:MM:SS: [netCorrelator]: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for ##.###.##.### on interface vmk0. The current owner is ##.##.##.##.##.##.
Log File: /var/run/log/vpxa.log
Description: Log entries showing failure to start heartbeating
YYYY-MM-DDTHH:MM:SS warning vpxa[#######] [Originator@#### sub=Heartbeat opID=SWI-########] Failed to bind heartbeat socket; '##.###.##.###', e: 99(Cannot assign requested address)YYYY-MM-DDTHH:MM:SS warning vpxa[#######] [Originator@#### sub=Heartbeat opID=SWI-########] Failed to bind heartbeat socket; '##.###.##.###', e: 99(Cannot assign requested address)
Resolution
Steps:
Remove the stale IP from the config store by running:
# configstorecli config current delete -c esx -g services -k vpxa_solution_user_config
Restart the vpxa service using:
# /etc/init.d/vpxa stop && /etc/init.d/vpxa startFeedback
