VCF Installer: Add Host to DVS Failed Due to VLAN Configuration Mismatch in VCF

Products

• VMware NSX

Issue/Introduction

The VCF Installer deployment fails during the "Configure the vSphere cluster" phase at the "Add ESXi Hosts to vSphere Distributed Switch" task. This typically occurs during the vmkNIC migration from a standard vSwitch to a Distributed Switch (vDS), leading to the error: 
VSPHERE_ADD_HOST_TO_DVS_FAILED 
java.util.NoSuchElementException: No available vmnic found on the host.

Environment

VMware Cloud Foundation 9.x

Cause

A VLAN configuration mismatch often exists between the physical interfaces (vmnics) on the ESXi hosts and the target vDS port group in vCenter. This mismatch causes network isolation during the automated vmkNIC migration process, leading the installer to report that no vmnics are available.

Resolution

1. Identify the Management VLAN tagged on the ESXi host physical network interfaces.
2. Log in to the newly deployed vCenter Server.
3. Navigate to the Networking inventory.
4. Locate the target Distributed Port Group (e.g., VCF-ESX-MGMT-pg-esx-mgmt) used for the management vmkNIC migration.
5. Edit the settings of the Port Group and manually configure the VLAN ID to match the VLAN tagged on the ESXi host management interface.
6. Ensure the physical switch ports are configured to allow the necessary VLANs.
7. Retry the task from the VCF Installer UI.

• If the issue persists, verify that the deployment JSON/specification file includes at least two physical network adapters (vmnics) assigned to each vDS switch, as single-pNIC configurations for management traffic are not supported for these workflows.