Troubleshoot ESXi hosts that appear disconnected in vCenter by checking management networking, DNS, hostd, vpxa, certificates and time.
Start with Check management connectivity and work through the six diagnostic checks in order.
Record results before changing configuration and validate the original symptom after each controlled change.
Quick checks
Start with the basic checks in this runbook before moving to deeper troubleshooting.
- Confirm the affected service or component is available.
- Check recent configuration or connectivity changes.
- Run the relevant commands and compare the result with the expected state.
Check management connectivity
Verify the ESXi management VMkernel address, VLAN, gateway and reachability to vCenter.
Check DNS
Confirm forward and reverse DNS resolution for the ESXi host and vCenter names.
Check management services
Review hostd and vpxa service health before restarting services.
Check required ports
Confirm required management traffic is permitted between ESXi and vCenter.
Check certificates and time
Check certificate validity and time synchronization when trust or authentication errors are reported.
Reconnect and verify
Reconnect the host after correcting the underlying dependency and verify inventory and alarms.
Useful commands
Run these checks from an appropriate administrative session and replace example values with your environment.
Management interfaces
esxcli network ip interface listServices
/etc/init.d/hostd status && /etc/init.d/vpxa statusQuick troubleshooting path
Use this sequence to isolate the failing dependency before changing production configuration.
- Check management connectivity → Verify the ESXi management VMkernel address, VLAN, gateway and reachability to vCenter.
- Check DNS → Confirm forward and reverse DNS resolution for the ESXi host and vCenter names.
- Check management services → Review hostd and vpxa service health before restarting services.
- Check required ports → Confirm required management traffic is permitted between ESXi and vCenter.
- Check certificates and time → Check certificate validity and time synchronization when trust or authentication errors are reported.
- Reconnect and verify → Reconnect the host after correcting the underlying dependency and verify inventory and alarms.
What good troubleshooting looks like
Good infrastructure troubleshooting is evidence-driven. Capture the original state, test the dependency that can prove or disprove your hypothesis, make the smallest safe change and repeat the original test.
Symptom → hypothesis → direct test → result → controlled change → validation → documentation