vCenter Collection status as unknown.

Products

• VMware Aria Suite

Issue/Introduction

The Aria Operations for Logs 8.18.x can collect the logs from vCenter however the VC Collection Status shows unknown.

• The vCenter integration "Test Connection" returned with "Tested Successfully".
• Getting an alert for vCenter on Aria Logs: vCenter auto-configuration failed.
• However, the VC Collection Status still shows "Unknown" under the vSphere page in Aria Operations for Logs.

 

NOTE: If the issue you are facing does not have the same symptoms as this one, please check the KB below.

vCenter Collection Status = Unknown and not seeing vCenter logs

Environment

Aria Operations for Logs 8.18.x

Resolution

First, attempt to reboot the Aria Operations for Logs nodes. If the issue persists, please continue with the steps below.

NOTE: Please make sure to create snapshots of the cluster before proceeding.

Remove and re-add the vSphere integration:

1. Delete the vSphere integration from Integrations > vSphere page.
2. Restart the Log Insight service on all nodes by executing the following command from an SSH session:
   • service loginsight restart
3. Re-add the vCenter Server under Integrations > vSphere page.

 

If the above steps did not resolve the issue, or you do not wish to remove the existing vSphere integration, please follow the procedure below:

1. Log into the primary node via SSH as root
2. Determine if the assignee-cluster-node value is set to null
   • grep '<assignee-cluster-node value="null"' $(ls /storage/core/loginsight/config/loginsight-config.xml#* | tail -n1)
3. If there is a result, then identify the valid "token" values:
   • grep -m1 "token=" $(ls -d /storage/core/loginsight/config/* | grep loginsight-config | tail -n1)
4. Open the Server Settings Configuration page by adding /internal/config at the end of the Aria Operations for Logs FQDN in the browser's address bar.
   • Example: https://AO4L_FQDN/internal/config
5. Search for "host value"
6. Replace "null" with the token value from step 3 and click Save at the bottom of the page
   • Example:  <assignee-cluster-node value="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" />
7. Confirm that the unknown status in the vCenter Collection status changes to Collecting.

 

Additional Information