VPC Connectivity Profile dropdown is empty when Activating a Supervisor cluster

Products

• VMware NSX

Issue/Introduction

• On the vSphere client, Activate a Supervisor -> Workload Network, the dropdown for VPC Connectivity Profile is not populated (has no entries)
• It is not possible to proceed as VPC Connectivity Profile is a required field, the error shows "This field is required"

• On the NSX UI, at least one VPC Connectivity Profile exists under VPCs -> Profiles -> VPC Connectivity Profile and the status is "Success".

Environment

VMware NSX 9.x

Cause

The field "default outbound NAT" must be enabled on the VPC Connectivity Profile for it to be available to select during Supervisor cluster creation.
Note, it is only possible to enable "default outbound NAT" when the T0 Gateway is configured with HA Mode Active Standby.

Resolution

If the T0 is Active Standby, enable "default outbound NAT" on the VPC Connectivity Profile and return to the Supervisor configuration page.
If the T0 is Active Active, the T0 must be reconfigured to Active Standby HA mode. Afterwards enable "default outbound NAT" on the VPC Connectivity Profile and return to the Supervisor configuration page.

Additional Information

If the T0 has external connections and BGP neighbors configured, changing to Active-Standby will not be allowed. These configurations must be remove prior to making the change. Additionally, if an external connection is using the T0, it will need to be removed.

• Remove the external connection from the transit gateway.
• Delete the external connection.
• Delete the BGP neighbors in the T0.
• Delete the external interfaces in the T0.
• Set the T0 to active-standby.
• Recreate the external interfaces in the T0.
• Recreate the BGP neighbors in the T0.
• Recreate the external connection, configure it to use the T0.
• Add the external connection to the transit gateway.