Inventory Sync for Aria Operations for Networks Fails with LCMVRNICONFIG Credential Errors in Aria Suite Lifecycle Manager

Products

• VCF Operations for Networks

Issue/Introduction

When importing or synchronizing Aria Operations for Networks into Aria Suite Lifecycle Manager, the inventory sync may fail with one or more of the following errors:

• Error Code: LCMVRNICONFIG90045 — Failed to get CSRF token for VMware Aria Operations for Networks. Validate if the IP Address, credentials are correct and all services are running.
• Error Code: LCMVRNICONFIG90114 — General Error while connecting to SSH. Cause unknown. Potential causes include incorrect credentials or high latency in the network. Ensure that you check logs for more details and adhere to the system latency guidelines. Also verify the authorization fields, and then retry.
• Error Code: LCMVRNICONFIG90115 — Invalid credentials provided for Console user. Please retry with correct console password.
• Error Code: LCMVRNICONFIG90126 — Invalid credentials provided for Support user. Please retry with correct support password.

These errors occur when:

• Aria Operations for Networks was imported into Aria Suite Lifecycle with a user other than admin@local.
• The passwords stored in the Aria Suite Lifecycle Locker do not match the actual passwords on the Aria Operations for Networks appliances.
• The Locker contains mismatched or outdated credentials for one or more of the three user accounts: admin@local, consoleuser, and support.

Each error code corresponds to a specific credential validation failure: LCMVRNICONFIG90045 (CSRF token/admin@local), LCMVRNICONFIG90114 (SSH general), LCMVRNICONFIG90115 (consoleuser), and LCMVRNICONFIG90126 (support user).

Important: Aria Suite Lifecycle Manager validates credentials for all three user accounts (admin@local, consoleuser, and support) across every node (Platform and Collector nodes) during inventory sync. A mismatch on any account or node will cause the sync to fail. The stack trace for these errors typically references com.vmware.vrealize.lcm.plugin.core.vrni.common.exception.VerifySshConn, confirming these are SSH credential validation failures.

Environment

Aria Suite Lifecycle Manager 8.x

Cause

Aria Suite Lifecycle Manager uses the default administrator user admin@local for inventory sync with Aria Operations for Networks. During the sync process, Lifecycle Manager validates SSH connectivity and credentials for three separate user accounts on each node:

• admin@local — The default administrator account
• consoleuser — The console access account
• support — The support access account

If any of the following conditions are true, the inventory sync will fail:

• The product was imported using a user other than admin@local.
• The password stored in Locker does not match the actual password on one or more of the appliance nodes.
• Passwords were changed on the appliances outside of Aria Suite Lifecycle Manager.

Each node (Platform and Collector) is validated independently for each user account, meaning a single sync attempt may produce multiple credential errors across different nodes and users.

Resolution

Step 1: Ensure admin@local Is Used for the Import

When importing or integrating Aria Operations for Networks into Aria Suite Lifecycle, you must use admin@local as the Platform Username. This is a requirement for inventory sync to succeed.

Step 2: Verify and Update Locker Passwords

Before triggering inventory sync, verify that the passwords stored in the Aria Suite Lifecycle Locker are correct and match the actual credentials on the Aria Operations for Networks appliances.

1. Navigate to Locker > Passwords in Aria Suite Lifecycle Manager.
2. Locate the password alias being used for Aria Operations for Networks. The password alias names in Locker may still show legacy branding — this is cosmetic and does not affect functionality.
3. Click on the password alias to view its References tab. This shows all environment references including which nodes and user accounts (consoleuser, support, admin@local) are using this password.
4. Verify the password is correct by attempting to log in to the Aria Operations for Networks GUI with the stored credentials.
5. If passwords need to be updated, follow the procedure in the Broadcom KB article: Changing passwords on VMware Aria Operations using VMware Aria Suite Lifecycle. This article covers updating both admin and root passwords through the Locker and Lifecycle Operations workflow.

Note: On VCF mode Aria Suite Lifecycle, passwords are managed by the SDDC Manager rotation tool. If passwords managed by the SDDC password rotation tool were updated outside of SDDC Manager, you must remediate them through SDDC Manager before proceeding.

Step 3: Trigger Inventory Sync and Retry Failures

After verifying or updating the Locker passwords, trigger the inventory sync:

1. Navigate to Lifecycle Operations > Environments and click VIEW DETAILS on the environment where Aria Operations for Networks is deployed.
2. Click the Networks tab to view Aria Operations for Networks.
3. Click the three-dot menu (…) on the product and select Trigger Inventory Sync.
4. If the sync fails, navigate to the Request Details page to review the specific error(s).
5. Click the RETRY button. The Retry Request dialog will appear, showing the Operations for Networks Platform Username, Password, and Platform IP.
6. In the Retry Request dialog, verify the password field references the correct Locker password alias. Update the password alias if needed, then click SUBMIT.

Critical: The retry process must be repeated multiple times because Lifecycle Manager validates credentials for each user account (admin@local, consoleuser, support) on each node (Platform node and each Collector node) independently. Expect to click RETRY once per failed validation. For example, an environment with one Platform node and two Collector nodes may require up to 9 retries (3 users × 3 nodes) if all credentials were out of sync.

Step 4: Update Node and Product References After Resync

After the inventory sync completes successfully, you must verify and update the Locker references for all nodes and products. If you changed any passwords during this process, the updated Locker password must be applied to every node and product reference individually.

1. Navigate to Locker > Passwords.
2. Click on the password alias used for Aria Operations for Networks.
3. Click the References tab.
4. Verify that all references are present and correct. The References tab will show entries for each combination of node and user account. For example, you should see product-level references for admin@local, consoleuser, and support, as well as node-level references for each node (Platform and Collector) with each user account.
5. If any references are missing or pointing to an old password alias, update them one at a time through the environment's product settings.
6. Once all references are updated, trigger a final Inventory Sync to confirm the sync completes without errors. After any password change, always re-trigger Inventory Sync and verify all node/product references are updated to use the new Locker password configuration. References must be updated one at a time per node.