ESXi host fails to add to a new vCenter Server with the error: "The host proxy switch associated with [host] no longer exists in vCenter Server"

Products

• VMware vCenter Server

Issue/Introduction

When attempting to migrate or add an ESXi host from a legacy vCenter Server to a newly deployed destination vCenter Server, the operation fails, and the following error banner notification appears in the vSphere Client UI:

The host proxy switch associated with <ESXi_Host_FQDN> no longer exists in vCenter Server.

Environment

VMware ESX

Cause

This issue occurs because orphaned host proxy switch from the legacy vCenter Server configuration remain tied to the networking stack of the ESXi host.

Because these legacy distributed switch database objects are still bound to local virtual machines or VMkernel network adapters, the destination vCenter Server cannot automatically overwrite, flush, or remove them, safely blocking the registration workflow.

 

Resolution

Depending on the environment type and whether production workloads are running on the affected host, select one of the following remediation workflows:

Method 1: Clean Reconstruction via Re-imaging (Recommended for Greenfield / Non-Production Environments)

If the destination vCenter is a fresh greenfield environment and the targeted ESXi hosts do not contain any active production workloads, troubleshooting legacy database objects can be bypassed completely by re-imaging the hosts to establish an optimal, clean baseline.

Follow this deployment and network migration sequence:

1. Clean Host Imaging: Evacuate any non-production data and completely re-image the target ESXi hosts (esx01 and esx02) with the desired ESXi release version.

2. Deploy Destination vCenter: Install the new vCenter Server Appliance (VCSA) directly onto the local datastore of one of your freshly imaged hosts (e.g., esx02).

3. Onboard First Host & Configure VDS:

   • Log into the new vCenter Server and add the first clean host (e.g., esx01) to the inventory.

   • Create a new vSphere Distributed Switch (VDS) and map the host uplinks to it.

4. Migrate vCenter & Resolve Upstream LACP Mismatch:

   • Migrate the vCenter Server VM network connection over to the new VDS portgroup.

   • Note on Network Challenges: If the upstream physical switches have Link Aggregation Control Protocol (LACP) active, but the new VDS Link Aggregation Group (LAG) has not yet been formed in vSphere, a transient disconnect may occur.

   • Workaround: Temporarily disable the LACP configuration on the physical network switch ports to restore immediate host management connectivity. To ensure reliable packet delivery without active host-side LACP configured, change the VDS portgroup teaming policy to "Route based on IP hash."

5. Onboard Secondary Hosts: Connect the remaining clean hosts (e.g., esx02) to the vCenter inventory and seamlessly migrate their VMkernel network management adapters from vSphere Standard Switches (VSS) over to the functional VDS topology.

Method 2: Manual Removal of Stale Components (Required for Active Production Environments)

If the host contains live production workloads and cannot be re-imaged, you must manually clear the bindings holding the legacy proxy switch in place by referencing KB 431992:

1. Identify all virtual machine network adapters and VMkernel interfaces currently associated with the legacy distributed switch.

2. Temporarily migrate those workloads and VMkernel ports over to a temporary vSphere Standard Switch (VSS).

3. Once the proxy switch is completely vacant of active connections, delete the stale switch instance via the ESXi CLI or vCenter UI to unblock the new registration workflow.