This section covers the following configuration options: Configuring VRF Configuring Avi Load Balancer IPAM and DNS What to read next Changing vCenter IP in existing vCenter CloudYou can change the vCenter IP by setting the Cloud to No Access. VRFVirtual Routing Framework (VRF) is a method of isolating traffic within a system. This is also referred to as a routing domain within the load balancer community. Avi Load Balancer High Availability in VMware vCenter EnvironmentThe Avi Load Balancer Controller and Service Engines can be deployed in an environment with VMware vSphere high availability (HA) and Distributed Resource Scheduler (DRS) features enabled. This topic provides details on high availability considerations when HA-DRS or a live vMotion is performed. Avi Load Balancer Interaction with vCenterThe Avi Load Balancer can be deployed with a VMware cloud in either no access or write access mode. Each mode results in escalating functionality and automation and requires higher levels of privilege for the Controller within VMware vCenter. Enabling VLAN trunking on Avi Load Balancer Service EngineThis section discusses configuration changes required to enable VLAN trunking on Avi Load Balancer SEs running on ESX in no-access mode. Pool-Server Autoscaling in VMware CloudsThe pyVmomi VMware automation library is available on the Avi Load Balancer Controller for use by ControlScripts. pyVmomi is the Python SDK for the VMware vSphere API that supports management of ESX, ESXi, and vCenter. One common use of such automation is for back-end, pool-server autoscaling. The steps outlined in this topic enable automatic scale in and scale out of pool servers, based on an autoscaling policy. DRS and Anti-affinity RulesThis section explains the DRS Configuration and anti-affinity rules within VMware vSphere environments. DRS VM overrides are used to disable vMotion for controllers, and anti-affinity rules are used to prevent the placement of the controllers or SEs on the same hypervisor. Performing Manual Discovery of New Networks in VMware CloudThis topic details the process to perform a manual discovery for the newly added networks in a VMware cloud. When new networks or a port groups are added in the vCenter, but are not available under the Networks tab of the user interface, a manual rediscovery is required for the VMware cloud. Manually Deploy Service Engines in Non-Default Tenant/CloudService Engines deployed manually by the Avi Load Balancer administrator in No Orchestrator clouds requires the user to download a unique copy of the Service Engine image for each cloud configured in the system. Troubleshooting Avi Load Balancer Deployment into VMwareThis section provides troubleshooting tips for Avi Load Balancer deployment into a VMware vCenter-managed cloud. Parent topic: Installing Avi Load Balancer in VMware vSphere Environments