Network Policy Mode with Avi Load Balancer on Write Access VMware Cloud

In this mode, Avi Load Balancer is integrated with VMware and the VMware infrastructure is used to configure the interfaces and port groups.

For deploying Avi Load Balancer in Network Policy Mode the following minimum ACI configurations are required:

• A bridge domain defined containing subnets to be used for Virtual Service IPs and SE interfaces.

• An EPG created referencing the previous bridge domain

As seen above, the integration is with vCenter in write access mode.

The configuration workflow for this mode is given below:

To deploy Avi Load Balancer in vCenter with write access mode, see Installing Avi Load Balancer in VMware vSphere Environments.

This is a traditional deployment where ACI provides access (contracts) between the clients and virtual service and the Service Engine and servers.

Configuring APIC contracts for Avi Load Balancer

After deploying Avi Load Balancer in vCenter write access mode, you need to create contracts to allow communication between the clients and virtual service networks, and Service Engines and servers.

The contracts can be configured in ACI for the following deployment modes:

Avi Load Balancer Deployed in Two-Arm Mode

In this mode, SE connectivity to the clients and servers will use different networks. You need to create a contract to allow communication between the client EPG and virtual servers EPG and between Avi Load Balancer and the server EPG.

Avi Load Balancer Deployed in One Arm Mode

In this mode, connectivity from the SE to the clients and servers will use the same interface. You need to create a contract to allow communication between the client EPG and virtual servers EPG and between Avi Load Balancer and the server EPG.