This article provides steps to troubleshoot when an ESXi is in disconnected or a not responding state in vCenter Server. In addition, it provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking and management server agents is correct and confirm the availability of resources on your ESXi host.
Symptoms:
- An ESXi host shows as "not responding" in vCenter Server.
- An ESXi host shows as disconnected in vCenter Server.
- Cannot connect an ESXi host to vCenter Server.
- Virtual machines on an ESXi host show as greyed out in vCenter Server.
- When attempting to add an ESXi to vCenter Server, you see an error similar to:
Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problem
- In the vpxd.log file, you see entries similar to:
- <YYYY-MM-DD>T<time>.696-05:00 [08128 info 'vpxdvpxdMoHost' opID=37D08048-00006071-85] [HostMo] host connection state changed to [DISCONNECTED] for host-26725
</time> - <YYYY-MM-DD>T<time>.508-04:00 [04944 error 'vpxdvpxdInvtHostCnx' opID=HB-host-385@3560-79f8b53e] [VpxdInvtHostSyncHostLRO] FixNotRespondingHost failed for host host-385, marking host as notResponding
<YYYY-MM-DD>T<time>.633-04:00 [00812 error 'vpxdvpxdInvtHostCnx' opID=HB-host-385@3565-12c9cfec] [VpxdInvtHostSyncHostLRO] FixNotRespondingHost failed for host host-385, marking host as notResponding
</time></time>
For more information, see Location of vCenter Server log files (1021804)
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.