The Avi Load Balancer Controller requires only one management IP address. Administrative commands are configured on the Controller by accessing it using this IP address.

The management IP address is also used by the Controller to communicate with other SEs. This IP address for all Controllers within a cluster should belong to the same subnet. For more information, see the Controller Cluster IP topic in the VMware NSX Advanced Load Balancer Administration Guide.

Each Avi Load Balancer Service Engine requires one management IP address, a virtual service IP address, and an IP address that faces the pool network.

For quick deployments, DHCP is recommended over the static assignment for Avi Load Balancer SE management. For data vNICs, one arm and two arm topologies should use IP pool address allocation.

Note:

Use a static IP for the Avi Load Balancer Controller management address, unless your DHCP server can preserve the assigned IP address permanently.

The virtual service IP address is manually specified while creating the load balancing application. You can automate the virtual service IP address allocation by integrating it with an IPAM service. For more information, see NSX Advanced Load Balancer IPAM and DNS in this guide.

Avi Load Balancer load balances the traffic with VIP address: port as its destination across the members (servers) within the pool.