Troubleshooting Aria Operations Cloud Proxy Scale-Out Deployment Failure LCMVROPSSYSTEM29002

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Aria Operations Cloud Proxy scale-out via VMware Aria Suite Lifecycle Manager (vRSLCM) fails with error LCMVROPSSYSTEM29002

• OVA successfully deploys and Cloud Proxy successfully powers on.

• Cloud Proxy appliance is unable to establish a initial handshake with the with the Aria Operations cluster. The registration sequence times out with the error Creation Status: Exceeded max retry count and  Failed to connect to VMware Aria Operations after 30 tries.

• A network health check via cprc-cli -v -d network indicates that the cloud proxy appliance has lost network connectivity. Specifically, the DNS server is unresponsive to pings, the VMware Aria Operations host name cannot be resolved, and the default gateway is currently reported as unknown

Environment

Aria Operations 8.18.x

Cause

The vRSLCM Network Profile may fail to correctly inject the Default Gateway and Netmask into the vApp properties during the OVF deployment process. This results in the Cloud Proxy being isolated from the network, preventing communication with the Aria Operations cluster.

Resolution

1. Initiate a new scale-out task in vRSLCM.
2. Before powering on the appliance, ensure the VM is powered off in vCenter.
3. Right-click the Cloud Proxy VM and navigate to Edit Settings > vApp Options.
4. Manually correct the Gateway and Netmask values to match the intended network profile configuration. Ensure the IP address ####.####.####.#### is applied correctly.
5. Configure the Cloud Proxy default password as a complex password to satisfy security requirements and prevent LCMVACONFIG80003 deployment errors.
6. Ensure both the current and new passwords are added to the vRSLCM locker before proceeding with the deployment.
7. Start the VM and verify connectivity. The Cloud Proxy should now establish a connection with the Aria Operations cluster.