Unable to integrate vCenter in VMware Aria Operations for Logs (vRLI) due to DNS Multi-IP Misconfiguration

Products

• VCF Operations

Issue/Introduction

 

• Unable to integrate a vCenter Server into VMware Aria Operations for Logs (formerly vRealize Log Insight).

• The Test Connection fails or times out during the integration process.

• Even if the test connection succeeds intermittently, saving the integration configuration takes an unusually long time, or the collection status for the hosts eventually turns to an "Error" state.

• Logs (vsphere-lib logs) on the Aria Operations for Logs nodes may show HTTP transport timeout errors, such as: java.net.ConnectException: Connection timed out.

["DaemonCommands-thread-262"/##.##.##.## ERROR] [com.vmware.loginsight.vsphere.client.VimClient] [Exception while consuming connection for vCenter '<vCenter_FQDN>': HTTP transport error: java.net.ConnectException: Connection timed out (Connection timed out)]
com.sun.xml.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection timed out (Connection timed out)

 

Environment

Aria Operations for Logs (vRLI) 8.18.x

vCenter Server 8.x

Cause

This issue occurs due to a DNS misconfiguration where the vCenter Server FQDN is associated with multiple IP addresses.

When executing an nslookup or curl against the vCenter FQDN from the Aria Operations for Logs nodes, it returns multiple IP addresses (e.g., 3 separate IPs), but only one of those IPs correctly resolves and routes to the vCenter Server. The other obsolete or incorrect IP addresses cause outbound requests from Aria Operations for Logs to periodically target unreachable endpoints, resulting in severe delays and connection timeouts.

Resolution

To resolve this issue, correction of the DNS records for the vCenter Server is needed to ensure traffic routes to the correct endpoint.

1. Review DNS and IP Configuration: Engage network or DNS administrator to review the DNS records (A and PTR records) for the affected vCenter Server FQDN.

2. Verify Resolution: Perform an nslookup for the vCenter FQDN from the Aria Operations for Logs node to identify all IP addresses being returned.

3. Remove Invalid IPs: Remove the non-working, duplicate, or obsolete IP addresses from your DNS server. The vCenter FQDN should resolve strictly to the single, correct IP address assigned to the vCenter Server Appliance.

4. Flush DNS (if applicable): Ensure that the updated DNS records have propagated and clear any local DNS caches if necessary.

5. Retry Integration: Once nslookup consistently returns only the single correct IP address, return to the Aria Operations for Logs UI and retry the vCenter integration and Test Connection.