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

Design Description

Design Justification

Design Implication


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

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



Create a virtual machine group for the Controller VMs.

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

You must add virtual machines to the allocated groups manually.


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

This ensures fast recovery for the NSX Advanced Load Balancer.



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

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

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


Create one Content Library on each of the VI workload domain to store Service Engine OVA.

The Controller's NSX-T Cloud Connector requires a Content Library configured to create the Service Engines.


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

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