Symptoms
After reinstalling ESXi on a host or replacing a failed server with a new installation using the same IP address/hostname, you experience the following symptoms:
Context
This issue typically occurs if the original ESXi host experienced a corruption or hardware failure and was deleted or reinstalled without first being gracefully removed from the VDS.
When an ESXi host is reinstalled or replaced, its local VDS runtime configuration is lost. However, if the host was not gracefully removed from the VDS inventory within vCenter Server prior to the reinstallation, vCenter Server still considers the host a member of the switch.
Upon reconnection, vCenter Server attempts to automatically push the existing VDS configuration back to the host. This process fails if there is a resource conflict—most commonly when the physical network adapters (vmnic0, vmnic1, etc.) required by the VDS configuration are currently allocated to the default Standard Switch (vSwitch0) created during the fresh ESXi installation. Because the host lacks the VDS configuration, subsequent network migration tasks fail.
To resolve this issue, the host's stale registration must be cleared from the Distributed Switch configuration in vCenter Server, and the host must be cleanly re-added.
Step 1: Remove the Host from the VDS
Step 2: Re-add the Host to the VDS
Once the host is cleanly re-added, retry your original network migration or configuration operations.