vCenter Server design of the Advanced Load Balancing for VMware Cloud Foundation.

Table 1. Design Decisions for the Virtual Infrastructure to support the VMware NSX Advanced Load Balancer

Decision ID

Decision ID

Design Justification

Design Implication

AVI-VI- VC-004

Create anti-affinity 'VM/ Host' rule that prevents collocation of Avi Controller VMs.

vSphere will take care of placing the Avi Controller VMs in a way that always ensures maximum HA for the Avi Controller cluster.



Create a virtual machine group for the Avi Controller VMs.

Ensures that the Avi Controller VMs can be managed as a group.

You must add virtual machines to the allocated groups manually.


In vSphere HA, for each Avi Controller and Avi SE VMs, set the restart priority policy to high and host isolation response to disabled.

This ensures fast recovery for the VMware NSX Advanced Load Balancer.



Create one Content Library on the management domain to store Avi Controller OVA.

Deploying OVA from the Content Library will be operationally easy to do.

Might not be necessary if deploying Avi Controller VMs using automation tools such as vRO, Ansible, etc.


Create one Content Library on each of the VI workload domain to store Avi SE OVA.

Avi Controller's NSX-T Cloud Connector would require a Content Library configured to create Avi SEs.


Users and Roles required by the Advanced Load Balancing for VMware Cloud Foundation

Avi Controller(s) interacts with vCenter Server and NSX-T Managers clusters to provide full lifecycle management of the Avi SEs. This requires users in vCenter Server and NSX-T Manager cluster with specific roles and permissions to exist or be created.