Aria Automation requires updating IP addresses when network infrastructure changes or during VCF upgrade prerequisites. Renaming server hostnames or directly migrating the database remains unsupported. This article details the supported method for changing node or cluster IP addresses.
VMware Aria Automation 8.x
Network architecture changes or VCF upgrade alignment necessitates a formal re-IP procedure.
To safely update Aria Automation IP addresses, adhering to Broadcom's documentation (Change IP Addresses of vRA Node or Cluster), follow these steps:
Pre-Change Preparation:
Backup: Perform a full backup of your Aria Automation deployment.
Snapshot: Perform a full offline snapshot of the Aria Automation cluster nodes.
DNS Updates: Update DNS records to reflect the new IP addresses after the IP address is updated in the appliance, after performing step 5 from the tech document below.
Verify Infrastructure: Ensure all required network infrastructure is properly configured for the new IP addresses.
Changing the IP Address:
Follow Broadcom's Procedure: Use the provided procedure within the documentation to change the IP addresses of the Aria Automation nodes. This involves modifying network settings within the appliance.
Change IP addresses of VMware Aria Automation node or cluster
Update Integrations: Update integrations (vSphere, NSX, vRO, etc.) with the new IP addresses. Verify certificates and credentials after updating.
Post-Change Verification:
LB IP Address: If clustered deployment, update LB IP.
Accessibility: Verify access to the Aria Automation UI, API, and CLI using the new IP addresses.
Workload Functionality: Test workload deployment, management, and resource actions to ensure proper operation.
Integration Connectivity: Verify connectivity between Aria Automation and all integrated systems.
DNS Verification: Confirm that DNS resolution is working as expected.
Important Note:
Hostname changes are not supported. Database export/restore migrations are not supported due to Kubernetes dependencies.