This guide explains how to integrate Avi Networks Load Balancer Controller into a VMware vCenter cloud. A single Avi Controller cluster supports multiple concurrent vCenter clouds.
AVI Networks Load Balancing are unique option for use High Level Load Balancing Solution and now when AVI Networks was added to NSX-T 3.X i decided to dive in to the technical side of the solution.
i am planning to write a series of Blogs covering the Configuration of AVI Load Balancing, including Configure vRealize Suite LB with AVI Load Balance with SSL termination Certificate Management.
Integrating Avi Vantage with vCenter 6.7
Avi Vantage runs on virtual machines (VMs) managed by VMware vCenter. When deployed into a vCenter The Avi Network Appliance performs as a fully distributed, virtualized system consisting of the Avi Controller and Avi Service Engines each running as a VM.
Virtual Machine Requirements
Refer to the Hardware Requirements document for the minimum hardware requirements required to install Avi Controller and Service Engines.
Avi Controller can also be deployed as a three-node cluster for redundancy. A separate VM is required for each of the three Avi Controller nodes. However, the requirements for each VM would remain the same.
Refer to Overview of Avi Vantage High Availability for more information on High Availability. Ensure that the ESX host has the required physical resources. Service Engine creation will fail in the absence of these resources.
VMware Virtual Hardware Version 10
IP Address Requirements
The Avi 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 Service Engines. This IP address for all Controllers within a cluster should belong to the same subnet. For more information, refer to the Controller Cluster IP document.
Each Avi Service Engine require 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 static assignment for Avi SE management and the pool network IP address allocation.
I will Configure the virtual service IP address 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, refer to IPAM and DNS Support.
Avi Vantage load balances the traffic with VIP address:port as its destination across the members (servers) within the pool.
Deploying Avi Vantage in Write Access Mode
Deploying Avi Controller OVA
Choose the Vcenter Cluster you wish to deploy the AVI Appliance, Right Click and choose to deploy OVF Template.
Choose browse to choose the AVI ova file.
provide a name for the AVI Virtual machine.
you will need to choose the Compute for the AVI Appliances.
Choose Thick Provision Lazy Zeroed for disk format.
Choose a port group for Destination Networks in Network Mapping. This port group will be used by the Avi Controller to communicate with vCenter.
Specify the management IP address and default gateway
Press Next and review the Template Deploy.
Power on your AVI VM’s
if you see this error when you try yo start your AVI VM’s it means just you dont have resources to run the workload and you will need to find more empty Host to run this 24 G.B Memory VM.
Performing the Avi Controller Initial setup
Configure the basic system settings:
- Administrator account
- DNS and NTP server information
- Email or SMTP information
Provide the DNS Resolver and dont forget to add Google 126.96.36.199 to the list.
the DNS Search Domain need to be add.
Set the infrastructure type to VMware
Enter the vCenter settings.
- vCenter credentials – To create Service Engines, the vCenter account must have privileges to create new folders in vCenter.
- vCenter IP address
- Permissions – Select Write.
- Integration with Cisco APIC – Leave unselected or disabled.
- Data center – Where Avi Networks LB will be deployed here.
- IP allocation method for the networks where the pools and virtual services will be located – DHCP or Static. (Wizard screen example below shows DHCP.)
it will be critical to define Static IP Address to the AVI Network Controller, i will also advice to use Disturb Switch Configuration for the Management network
you are able to use Tenants to have separate LB Controller, lets choose No for simple Deployment.
and here you go , you are able to login to the AVI Network LB Dashboard and start configure your first Virtual Services.
i will cover with follow-up Blogs on how to do more Configuration with AVI and how to Configure the AVI Networks LB to work with VRA 8.1 , VIDM 3.3.2 and VROPS 8.1