IPAM and DNS (16.2.x)

The Avi Controller can be configured to provide automatic IP address allocation for virtual services and to provide authoritative DNS resolution for their virtual IP addresses.

Note: Users of Avi Vantage 16.3+ should instead refer to Service Discovery Using IPAM and DNS (16.3+).

To enable auto-allocation of VIPs, configure an IP address management (IPAM) profile and add it to the configuration of the cloud on the Avi Controller. IPAM profiles can be configured to use the following IP providers:

  • Avi Vantage
  • Infoblox
  • Amazon Web Services (AWS)
  • OpenStack

To enable authoritative DNS resolution of queries for the VIP addresses, configure a DNS profile and add it to the configuration of the cloud on the Avi Controller.

Notes

These procedures assume the cloud configuration has already been created on the Avi Controller.

Providers of IPAM and DNS Support

Here is the list of providers and supported functionalities for IPAM and DNS:

Support / Provider Profile Infoblox Internal  AWS/OpenStack
IPAM only No (not currently supported) Yes Yes
DNS only No (not currently supported) Yes No
IPAM + DNS Yes Yes No

For example, if Infoblox is the chosen provider, both IPAM and DNS profiles should be pointing to Infoblox. If Avi Vantage is the chosen provider, the Avi Vantage user has an option to use IPAM, DNS, or both.

IPAM / DNS Support for Cloud Infrastructure

This table lists the IPAM and DNS provider support available for each type of cloud (infrastructure) configured in Avi Vantage. For example, when creating VirtualServices in OpenStack or AWS cloud, a separate configuration for IPAM is not needed/allowed as the cloud configuration has support for IPAM natively in Avi. However, Avi Vantage DNS service can be still be used with these Clouds.

 

Cloud / Provider Profile Infoblox Internal AWS/OpenStack
IPAM+DNS IPAM DNS IPAM DNS
VMware (Read Access) Yes Yes Yes N/A N/A
VMware (Write Access) No No No N/A N/A
OpenStack No No Yes N/A (default, native) N/A (default, not used)
AWS No No Yes N/A (default, native) N/A (default, native)
Containers (Mesos/Rancher/Docker UCP) Yes Yes Yes Yes No
Linux Server Yes Yes Yes Yes No
No access Yes Yes Yes Yes No

 

Cloud Configuration Workflow

This section lists the steps for configuring IPAM and DNS support. The configuration fields differ among the infrastructure types and the provider (Vantage, Infoblox, AWS, and OpenStack). See the sections following this one for detailed steps.

  1. Navigate to Templates > Profiles.
  2. Click IPAM/DNS Profile.
  3. Click Create and select the provider:
    • Internal
    • Infoblox
    • AWS
    • OpenStack
  4. Fill in the displayed fields. (Detailed steps are provided in the sections below.)
  5. Click Save. The profile appears in the list.
  6. Navigate to Infrastructure > Clouds, and edit the cloud setting.
  7. Select the IPAM and DNS providers from the pull-down list. Either one or both need to be selected, based on the provider selected.
    For example: if Infoblox is the IPAM provider, it must be the DNS provider as well.
  8. (Optional) For east-west virtual services in this cloud, you need to additionally select east-west IPAM and DNS providers from the pull-down list. Either one or both can be selected.
  9. Click Save.

Sample Cloud Configuration with IPAM & DNS from steps 1 through 9:

cloud-ipam-dns

Following sections provide information for each of the IPAM / DNS providers supported by Avi Vantage.

Avi Vantage -> https://kb.avinetworks.com/ipam-and-dns-provider-avi-vantage/

Infoblox -> https://kb.avinetworks.com/ipam-and-dns-provider-infoblox/

AWS IPAM -> https://kb.avinetworks.com/ipam-and-dns-provider-aws/

Openstack IPAM -> https://kb.avinetworks.com/ipam-and-dns-provider-openstack/

Virtual Service Configuration Workflow

Select Auto Allocate IP and a network from a list of networks & subnets in the VS create window as shown below:

vs-create-dns

Select FQDN for the virtual service from a list of configured domain names:

vs-create-ipam

 

Note:

  1. If a DNS profile is configured under a Cloud where the virtual service is being created, then the virtual service's IP cannot be determined from a fully qualified domain name; the user is expected to enter an IP address or select the auto-allocate IP checkbox.
  2. In case of Infoblox, if there is a list of usable_subnets/usable_domains configured (refer to section for Infoblox above in this article), then the dropdown will consist only of those entries. If no such configuration is found, Avi will display the entire list of available subnets/domains from Infoblox.