Skip to main content

 Changing IP Addresses in Aria Automation

https://knowledge.broadcom.com/external/article?articleNumber=390017

Issue/Introduction

Network changes may require updating Aria Automation's IP addresses. However, renaming server hostnames or directly migrating the database is unsupported. This guide details the only supported method for changing IP addresses without disrupting services.

Environment

VMware Aria Automation 8.x

Resolution

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.
DNS Updates: Update DNS records to reflect the new IP addresses.
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:

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.

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more