When attempting to add an ESXi host to the vCenter Server inventory, the host may appear in a "Disconnected" state. This issue occurs when the primary management VMkernel adapter (vmk0) lacks a valid static IP address, subnet mask, or a correctly configured Fully Qualified Domain Name (FQDN). Without these core network identity parameters, the host cannot establish the necessary management handshake with vCenter Server, and external management machines will be unable to reach the host via ICMP ping. This article provides the diagnostic steps and esxcli commands required to manually restore the management network identity directly from the host console to facilitate successful vCenter integration.
Symptoms:
vmk0 is missing an IP address or FQDN.The root cause is an incomplete or incorrect network configuration on the ESXi host, specifically involving the management IP assignment and the hostname/FQDN settings on the primary management interface (vmk0).
To resolve this issue manually, configure the management network settings directly via the ESXi command line:
vmk0 interface: esxcli network ip interface ipv4 set -i vmk0 -I <new-ip-address> -N <subnet-mask> -t staticesxcli system hostname set --fqdn=<my-hostname.domain.com>esxcli network ip dns server list