vSphere Supervisor Cluster enablement is stuck at "Configuring" when using NSX and Avi Load Balancer

Products

• VMware NSX

Issue/Introduction

• When enabling vSphere with Tanzu (TKGs) on a cluster using NSX and Avi Load Balancer (NSX Advanced Load Balancer), the deployment stalls at the "Configuring" or "Configuring Load Balancer" stage.
• In the Avi Controller UI, no Virtual Services (VS) are created for the Supervisor Cluster Control Plane, or they remain in a pending state.
• The Supervisor Cluster status remains stuck while waiting for Load Balancer service updates. 

Environment

VMware NSX

VMware Cloud Foundation (VCF)

VMware Avi Load Balancer (NSX Advanced Load Balancer)

Cause

This issue occurs because the NSX Cloud configuration within the Avi Controller is incomplete or not fully synchronized. 

As NSX Manager is registered with Avi, it delegates load balancing logic to Avi.

The deployment will fail if:

• The NSX Cloud connector status in Avi is not "Green" or "Healthy."
• The Network/Subnet configurations within the Avi Cloud are not finalized, preventing the Avi-AKO (Avi Kubernetes Operator) from provisioning Virtual IPs (VIPs).

Resolution

To resolve this issue, ensure the integration between Avi and NSX is fully operational:

1. Verify Cloud Connector Status:

   • Log in to the Avi (NSX Advanced Load Balancer) Controller UI.
   • Navigate to Infrastructure > Clouds.
   • Locate the NSX Cloud being used for the Supervisor Cluster and ensure the status is Green (Healthy).

2. Assign/Verify IPAM Profile:

   • Edit the NSX Cloud configuration.
   • Under the IPAM/DNS tab, verify that a valid IPAM Profile is selected. This profile is responsible for allocating external VIPs. 

3. Validate Network Configuration:

   • Ensure the correct Transport Zone and Tier-1 Router are selected within the Avi Cloud settings.
   • Verify that the subnets used for VIP allocation have available free IP addresses. 
   • Confirm Cloud is selected under Infrastructure/Networks

4. Monitor Deployment:

   • Once the Avi configuration is finalized and synchronized, the Avi-AKO pod in the Supervisor Cluster will automatically reconcile.
   • The Virtual Services should appear in the Avi UI, and the Supervisor Cluster status will transition to "Running."

Additional Information

Related Articles:

https://knowledge.broadcom.com/external/article/425179

https://knowledge.broadcom.com/external/article/425348