Automating IPAM Endpoint Migration in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

An existing IPAM integration in Aria Automation is referencing an outdated IPAM endpoint that is no longer in use. A new IPAM instance has been configured, but Aria Automation continues to associate IP allocation and release operations with the previous configuration.

Due to this, IP addresses must currently be released and reserved manually, leading to inefficiencies and a risk of IP conflicts. The goal is to migrate IP tracking and operations from the deprecated IPAM instance to the new one in a streamlined, automated manner.

Environment

Aria Automation 8.x

Cause

Manual IP management is leading to confusion, delays, and potential errors. The customer is looking for an automated solution to transition IPAM tracking in vRA to the new IPAM target instance, eliminating the need for manual IP allocation and release.

Resolution

The Aria Automation engineering team developed a custom workflow specifically for this customer. This workflow enables:

• Automated release of IPs from the old IPAM
• Identification and migration of IPs to the IPAM target
• Reallocation or relinking of those IPs within Aria Automation

This solution simplifies the migration and reduces the risk of errors during VM provisioning or decommissioning.

The workflows and actions contained in the solution are intended to automate the migration of IP addresses across IPAM systems. Additionally it is performing a discovery and pre-check of all IP ranges that are properly configured to accept the migration of IP addresses.
The following migration scenarios are subject to this process:
External IPAM to internal IPAM
External IPAM to external IPAM
Internal IPAM to external IPAM

 

If you are experiencing a similar issue, please download the migration guide and workflow package.