VMware Cloud Foundation 9 validation fails for vMotion and vSAN VMkernel port groups due to naming conflict

Products

• VMware Cloud Foundation

Issue/Introduction

• During the VMware Cloud Foundation (VCF) 9 deployment or expansion process, the validation phase fails when attempting to audit or create vMotion and vSAN network connectivity.
• The following error is observed in the UI or Domain Manager logs: Failed to validate connectivity of VSAN network

/var/log/vmware/vcf/domainmanager/domainmanager.log
ERROR [c.v.e.s.c.h.n.EsxiHostNetworkingUtil]  Unable to create Port group VSAN with VLAN ID #### and attached it to vSwitch <vds_switch_Name> on host <ESX_Host_Name>. The specified key, name, or identifier '<Port_Group_Name>' already exists.
ERROR [c.v.e.s.v.a.AuditSinglePortgroupAction]  Failed to validate single portgroup for network VSAN com.vmware.vim.binding.vim.fault.AlreadyExists: The specified key, name, or identifier '<Port_Group_Name>' already exists.

Environment

VCF 9.x

Cause

If a port group name vSAN or vMotion already exists on an ESX host, the validation can fail with an AlreadyExists fault because the deployment workflow attempts to create port groups using the same names/identifiers.

This typically happens on hosts where these port groups were previously created, either left over from a failed deployment attempt or created manually, resulting in a naming conflict during validation.

Resolution

To resolve this issue, manually remove the conflicting network configuration from the affected ESX hosts:

1. Log in to the ESX Host Client for the host(s) identified in the logs.

2. Navigate to Networking > Port groups.

3. Identify and remove any existing port groups named VSAN or vMotion.
   
   Note: Ensure no VMkernel adapters are attached to these port groups and that the VLANs are not in use.

4. Restart ESX management agents to clear cached state: Restarting Management Agents in ESXi

   • DCUI: Troubleshooting Options > Restart Management Agents
   • SSH: run services.sh restart

5. Repeat these steps for all hosts intended for the VCF deployment.

6. Rerun the VCF Validation process from the SDDC Manager/Deployment parameter tool.