Migration of ESXi host management network (vmk0) to a LAG-backed Distributed Switch fails after host rename

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms

1. Legacy Configuration: The management network is currently hosted on an old vSphere Distributed Switch (vDS) utilizing a Link Aggregation Group (LAG/LACP).
2. Host Identity Change: The ESXi host has been renamed.
3. Network Reset: The management network was reset via the Direct Console User Interface (DCUI) and assigned to a single physical uplink (vmnic) that is still logically associated with the LAG, currently residing on a Standard Switch (vSS).
4. Migration Failure: After re-adding the host to vCenter, attempts to migrate the management network to a new vDS fail. The host successfully joins the new vDS, but with the following misconfigurations:
   • The new vDS has no active uplinks.
   • The physical vmnic on the Standard Switch remains in an "Unused" status, preventing it from being claimed by the new Distributed Switch.

 

Environment

ESXi 8.0U3

Cause

The used vmnic could not be migrated to the new vDS in this flow.

Resolution

To successfully migrate the host to a new LAG-backed vDS following a migration failure, follow this specific sequence:

1. Initialize Uplink Redundancy: Add the remaining physical uplinks (those assigned to the LAG but not currently in use by the Standard Switch) to the new vDS to establish initial connectivity paths.
2. Migrate Management Interface: Execute the "Manage Host Networking" wizard to migrate the management VMkernel (vmk0) from the Standard Switch to the designated port group on the new vDS.
3. Reclaim and Consolidate Uplinks:
   • Navigate to the Standard Switch and move the remaining vmnic to an "Unclaimed" state.
   • Add this reclaimed vmnic to the new vDS and assign it to the appropriate LAG member port to complete the aggregation.