An administrator is attempting to activate a new vSphere Supervisor for use with VMware Cloud Foundation (VCF) Automation on a newly deployed cluster. In the VMware vSphere client, when going through the vSphere Supervisor activation having selected VCF Networking with VPC, the Virtual Private Cloud (VPC) Connectivity Profile dropdown is empty on the workload network page. The administrator verified that a Virtual Private Cloud (VPC) Connectivity Profile exists in NSX.
What is the cause of the issue?
When activating a vSphere Supervisor using VCF Networking with VPC, the Supervisor Workload Network must use a VPC Connectivity Profile. These profiles are scoped to an NSX Project, and cannot be consumed from the Default Project.
VCF Automation requires that:
A custom NSX Project be used for VPC networking integrations.
The Default Project cannot host Connectivity Profiles or VPC constructs intended for Supervisor activation.
Even though the administrator verified that a VPC Connectivity Profile exists in NSX, the Supervisor wizard will not display it if:
The VPC Connectivity Profile belongs to a different project, or
The current selection is the Default Project, which blocks visibility.
This exact behavior---empty VPC Connectivity Profile dropdown---is documented when attempting Supervisor activation under the Default NSX Project.
Option A (T0 active/active) affects North-South routing but does not hide VPC profiles. Option B (Supervisor HA mode) does not impact network profile selection. Option D (missing default VPC) is incorrect because the wizard is complaining about availability of Connectivity Profiles, not VPC instances.
Nikita
3 days agoLeah
8 days agoStacey
13 days agoVon
19 days agoMarkus
24 days agoCrista
29 days agoTambra
1 month agoChauncey
1 month agoNatalie
1 month agoJulie
2 months agoTegan
2 months agoLang
2 months ago