Aria Automation: Infoblox IP allocation fails with "network interface IP assignment [STATIC] allocation failed: Network profile ... has no subnets with static IP ranges or ranges do not have available IP addresses.'

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Deploying with Infoblox external IPAM fails, saying there are no IP addresses available
• However this should not have been the case: checking in Infoblox shows there are IP addresses available ("Unused")
• No placement exists that satisfies all of the request requirements. See 'Provisioning Diagram' for more information. Original Task Error: 'Allocation filter error: Unable to find a common placement for compute 'Cloud_vSphere_Machine_1' and its associated network resources on region '(REGION)[/provisioning/resources/provisioning-regions/<UUID>]'. Reason: Network filters: network profile data [[Network profile name [NetName-123.45.67.89-example],document link [/provisioning/resources/network-profiles/<UUID>],subnets [NetName-123.45.67.89-example]]],network interface IP assignment [STATIC] allocation failed: Network profile [NetName-123.45.67.128-example] has no subnets with static IP ranges or ranges do not have available IP addresses.'

Environment

• VMware Aria Automation 8.x
• Infoblox IPAM plugin for Aria Automation

Cause

• The count of free IP addresses is thrown off by unallocated or duplicated IPs which are marked as allocated in the Automation DB
• These IP addresses may be associated with "Missing" resources or not linked to any resource in the Automation GUI > Networks > IP Addresses

Resolution

Quick resolution

If it is seen in the Automation GUI > Networks > IP Addresses that there are IP addresses may be associated with "Missing" resources or not linked to any resource (resource field blank),

 => Then you can RELEASE these IP addresses on this page.

This will provide addresses for allocation in new vRA deployments.

 

In-depth analysis

For a deeper examination of which addresses are causing the issue and manual fixing of the database, please contact VMware support, referencing this KB.

There is some further info in the Internal section.