Getting LCMVRNICONFIG90108 during deployment of collector node via Aria Suite Lifecycle 8.x, or VCF Operations Lifecycle tab in 9.x

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When deploying a VMware Aria Operations for Networks collector node via VMware Aria Suite Lifecycle (formerly vRSLCM), or VCF Operations 9.0 Fleet Management > Lifecycle tab, the deployment may fail during the post-check stage. It may appear the Platform node deploys successfully, but the Collector node fails verification.

This issue is often observed when the appliance is deployed onto an incorrect network segment in vCenter, causing it to fail IP verification checks.

The user experiences the following error in the UI:

Error Code: LCMVRNICONFIG90108
Status Check of node timeout. Please check the connection and retry.
VMware Aria Operations for Networks proxy status check timed out. Please check the connection. Node is not responding with IP ###.###.###.###

Environment

VCF Operations 8.18.0
VCF Operations for Networks 9.0.0
VCF Operations 9.0.0
VMware Cloud Foundation 9.0.0

Cause

The network was misconfigured during the initial setup wizard. Specifically, the Collector node was assigned to an incorrect Port Group or Network Segment in vCenter, preventing the appliance from communicating with the Aria Suite Lifecycle manager to verify its own IP address.  This may also be caused by a network configuration issue in the environment.

 

Resolution

Table of Contents

• Aria Suite Lifecycle Manager 8.18.x
• VCF Operations 9.0.0

Aria Suite Lifecycle Manager 8.18.x

To resolve this issue, the failed deployment artifacts must be cleaned up manually from the vCenter inventory before retrying the deployment with the correct network configuration.

Follow the steps below to clean up the failed node:

1. Log in to the vCenter Server where the deployment was attempted.
2. Locate the failed Aria Operations for Networks Collector VM in the inventory.
3. Right-click the VM, select Power, and choose Power Off.
4. Once powered off, right-click the VM again and select Delete from Disk.
   Note: it is assumed that there will be no data loss since this is a fresh deployment.  You can simply remove the VM from inventory and delete later after verification if you are concerned about data loss or having a recovery point.

Once the orphaned VM is removed, proceed to Aria Suite Lifecycle:

1. Log in to VMware Aria Suite Lifecycle.
2. Navigate to Requests and locate the failed deployment request.
3. If the option is available, click Retry. Ensure you update the network configuration to the correct segment during the retry wizard.
   Note:If a Retry is not possible or the transaction is stuck, you may need to re-initiate the Add Collector workflow from the environment page, ensuring the correct Network Segment is selected in the infrastructure settings.

VCF Operations 9.0.0

To resolve this issue, the failed deployment artifacts must be cleaned up manually from the vCenter inventory before retrying the deployment with the correct network configuration.

Follow the steps below to clean up the failed node:

1. Log in to the vCenter Server where the deployment was attempted.
2. Locate the failed VCF Operations for Network Collector VM in the inventory.
3. Right-click the VM, select Power, and choose Power Off.
4. Once powered off, right-click the VM again and select Delete from Disk.
   Note: it is assumed that there will be no data loss since this is a fresh deployment.  You can simply remove the VM from inventory and delete later after verification if you are concerned about data loss or having a recovery point.

Once the orphaned VM is removed, proceed to VCF Operations:

1. Log in to VCF Operations.
2. Navigate to Fleet Management > Lifecycle and then navigate to the Tasks tab and locate the failed deployment request.
3. If the option is available, click Retry. Ensure you update the network configuration to the correct segment during the retry wizard.
   Note: If a Retry is not possible or the transaction is stuck, you may need to re-initiate the Deployment workflow from the Overview tab, ensuring the correct Network Segment is selected in the infrastructure settings.

If there is still no route to host and the correct networking has certainly been selected, please determine why the network is unable to communicate between the VCF Operations deployment and the desired network/subnet as the deployment expects a functioning network path to the desired subnet to complete.