Aria Automation Internal IPAM not syncing up with our external IPAM causing IP conflict

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

We’re experiencing IP address conflicts between Aria Automation’s internal IPAM and our external IPAM (Proteus). The internal IPAM is assigning IP addresses that are already in use according to Proteus, which is causing conflicts and resulting in automation failures or stalled provisioning. How can we ensure that pre-checks are performed with Proteus before Aria Automation assigns IP addresses?

Resolution

This behavior occurs because Aria Automation’s internal IPAM and external IPAM solutions, such as Proteus, operate independently and do not synchronize with each other by default. The internal IPAM in Aria Automation is designed to manage IP addresses within its own ecosystem and does not provide native integration or pre-check capabilities with external IPAM platforms. As a result, IP conflicts can occur when both systems allocate addresses without coordination.

To prevent such conflicts, it is recommended to use either the internal IPAM or the external IPAM exclusively. Simultaneous use of both is not supported.

For organizations that require integration between Aria Automation and external IPAM solutions, Aria Automation provides extensibility options through vRealize Orchestrator (vRO) or Action-Based Extensibility (ABX). These can be leveraged to build custom workflows that perform IP allocation checks or reservation updates in external systems like Proteus before provisioning occurs in Aria Automation.