Posts

Showing posts from 2026

vRA and vRO Connection Issue After vCenter Certificate Replacement

Image
 Hi Team, In this blog, I would like to share my real-time experience and troubleshooting steps after replacing certificates in vCenter Server, which caused connectivity issues with both VMware Aria Automation (vRA) and vRealize Orchestrator (vRO). Environment Issue After updating the vCenter Server certificate in our infrastructure, the integrations with: VMware Aria Automation (vRA) VMware vRealize Orchestrator (vRO) stopped working properly due to certificate trust issues. Issue 1 – vRA Cloud Account Connection Failure After the vCenter certificate replacement, the connection between vRA and vCenter was broken. Validation Steps in Aria Automation To validate the issue: Logged in to Aria Automation Navigated to: Infrastructure → Connections → Cloud Accounts Selected the affected vCenter Cloud Account Re-entered the required credentials/details Accepted the newly updated vCenter certificate After accepting the updated certificate, the connection bet...

Certificate Replacement in vIDM & Aria Automation – Real-Time Experience and Troubleshooting

Image
In this blog, I would like to share my real-time experience and troubleshooting steps while replacing certificates for: VMware Identity Manager (vIDM): 3.3.7 VMware Aria Suite Lifecycle (vRLCM): 8.18.0 Patch 7 VMware Aria Automation: 8.18.1.36791   Pre-Activity Preparation Before starting the certificate replacement activity, the following steps were completed: Imported the custom certificate into Locker in vRLCM and verified it Took snapshots of vIDM and Aria Automation nodes Performed Inventory Sync from vRLCM successfully   Aria Automation Certificate Replacement The certificate replacement for Aria Automation was completed successfully without any major issues. The new certificate was applied and validated.   Issue During vIDM Certificate Replacement While updating the certificate for vIDM , we encountered the following error: Error Code: LCMVRAVACONFIG590008 Reference KB We followed the of...

CSP-102547 Patch Upgrade Experience VMware Identity Manager 3.3.7 & Aria Suite Lifecycle 8.18.0 (Patch 5 → 7)

Image
In this blog, I would like to share my real-time experience and troubleshooting steps while applying the CSP-102547 patch for: VMware Identity Manager (vIDM): 3.3.7 VMware Aria Suite Lifecycle (vRLCM): 8.18.0 (Patch 5 to Patch 7) This includes the issues encountered during PostgreSQL cluster patching and how they were resolved.   Pre-Upgrade Validation Before starting the upgrade, I performed the necessary pre-check validations : Verified vIDM cluster node health Checked vRLCM status and services Confirmed connectivity and credentials We followed the official Broadcom KB article:    https://knowledge.broadcom.com/external/article/426230   Patch Upgrade Status VMware Identity Manager CSP-102547 patch was applied successfully All vIDM cluster nodes were upgraded without issues Aria Suite Lifecycle Upgrade from Patch 5 to Patch 7 completed successfully   Issue During Postgr...

Intermittent Aria Automation Login Issue Resolved by Infrastructure Health Validation

Environment Details We recently faced an intermittent login issue in our Production environment involving the following VMware components: VMware Identity Manager (vIDM): 3.3.7 VMware Aria Automation: 8.18.1 Issue Description After users successfully authenticated via tenant login , the Aria Automation home page intermittently failed to load and displayed the error: “Page can’t be reached” This issue did not occur consistently, making it difficult to immediately isolate the root cause. Initial Validation Checks During the issue window, we validated the following: ✅ Network connectivity between components was healthy ✅ DNS entries were resolving correctly ✅ No authentication failures were observed in vIDM Reference screenshots were captured for further analysis. Troubleshooting Approach 1. Validate Aria Automation & vIDM Services We first verified that all Aria Automation and vIDM services were up and running across the infrastructure. No immediate service-level failures were ...