IPAM Provider (Avi Vantage)
This article discusses Avi Vantage’s native IPAM configuration. This is supported on the following clouds:
- Containers (Mesos, OpenShift, Docker UCP, Rancher)
- Linux server cloud (bare metal)
- No access
Note: Starting with Avi Vantage release 18.1.2, this feature is supported for IPv6 for the clouds mentioned at Ecosystem Integration.
Avi Vantage allocates IP addresses from a pool of IP addresses within the subnet configured as listed below.
- Navigate to Infrastructure > Networks.
- For Select Cloud choose the cloud from the dropdown list and click on Create.
- Enter the name of the network.
- Under IP Address Management, click on the required option for DHCP Enabled and IPv6 Auto Configuration.
- Add IPv4 and/or IPv6 networks for IP address allocation.
- Click on Add Subnet.
- Specify the subnet address under IP Subnet.
- Enable Add Static IP Address Pool to specify the pool of IP addresses. Enter the range of the pool under IP Address Pool.
- Click on Save.
- Repeat steps from 1 to 4 for each network that is to be used for IP address allocation.
- Click on Save.
- Virtual service creation will fail if the static IP address pool is empty or exhausted.
- For east-west IPAM (applicable to container-based clouds, i.e., Mesos, OpenShift, Docker UCP, and Rancher) create another network with the appropriate link-local subnet and a separate IPAM/DNS profile.
Creating IPAM Networks using both IPv4 and IPv6 Subnets
The following is an instance of creating IPAM networks using both IPv4 and IPv6 subnets:
Navigate to Templates > IPAM/DNS Profiles and create a placeholder for IPAM. Create a separate placeholder for east-west wherever it is relevant.
You can assign one or more of the created networks to be the default usable network, if no specific network and/or subnet are provided in the virtual service configuration.
You can enable the Allocate IP in VRF checkbox for Avi Vantage to allocate IPs from networks in the virtual service’s VRF. This option is applicable to only Avi Vantage IPAM.
Selecting Network for IP Allocation
The selection of network for given allocated IP request is based on the following:
If a network and subnet is specified during virtual service creation, the system will attempt to allocate from that specific network/subnet. If that subnet does not have free static IPs, then the API request will fail.
If no network/subnet is specified (only possible via CLI or API) during virtual service creation, the system will consider all networks in the Usable Networks of the IPAM/DNS profile and randomly select the one which has free IPs available.
a) for v4 request, the system will check for free IPs in networks with v4 subnets before considering networks with v4 and v6 subnets.
b) for v6 request, the system will check for free IPs in networks with v6 subnets before considering networks with v4 and v6 subnets.
Note: Any change in the VIP’s IPv4 or IPv6 address will result in disruption of the virtual service. This can occur if the VS’s auto allocate type is changed. For instance, if a virtual service’s IPv4 address was allocated using a network with both v4 and v6 subnets, and its
auto_allocate_type is changed from v4 to
V4_V6 with a corresponding v6 subnet selected, the system will attempt to allocate an IPv6 address for that virtual service. If the allocation is successful, a virtual service disruption will occur.