Supervisor deployment fails with VM_NOT_DEPLOYED error due to network misconfiguration

Products

• VMware vSphere Kubernetes Service
• VMware NSX

Issue/Introduction

You encounter a failure when deploying a Supervisor Cluster in VMware Cloud Foundation. The deployment remains in a stuck state, and the Supervisor Control Plane VMs fail to deploy.

You observe the following errors in the system logs:

wcpsvc.log:
#### DEBUG wcp #### [vc@####] ... status:ISSUE issue:[]vms.IssueInfo{vms.IssueInfo{Type:"VM_NOT_DEPLOYED", Notifications:rest.Notifications{Errors:[]rest.Notification{rest.Notification{Message:rest.LocalizableMessage{DefaultMessage:"The System VM for solution #### on cluster #### has not been deployed because of unexpected error."}}}}}}

eam.log:
WARNING EAM #### [vc@#### threadName="####" source="Retry.java:####"] Failed to Deploying VM for LCCMAgent #### Reason: com.vmware.eam.EamRemoteSystemException: Failed to get placement recommendation virtual machine in the cluster

vpxd.log:
error = (vmodl.MethodFault) [ (vim.fault.CannotAccessNetwork) { device = "Network 1", backing = "DVSwitch[####] NSX port group [####](### down)", connected = false, msg = "The NSX-T components are down: DVSwitch[####], NSX DVPG/SUBNET [####] (Status: ### down)." } ]

Environment

VCF 9.1

Cause

The issue can occur because the Host TEP VLAN is configured on the incorrect physical ports within the top-of-rack switches. This network misconfiguration causes the NSX-T components to go down, which prevents the VPXD from finding a compatible host with the required network access to place the Supervisor VMs.

Resolution

To resolve this issue, you must correct the environmental network configuration:

1. Verify the physical cabling and port assignments for your ESXi hosts.
2. Correct the VLAN configuration on the physical top-of-rack switches to ensure the Host TEP VLAN is assigned to the proper ports.
3. Confirm that all TEP tunnels return to an "Up" status within the NSX Manager.
4. Once network restoration is complete, DRS is able to find compatible hosts, and the Supervisor VMs successfully deploy.