After upgrading to Aria Operations 8.18.5, vCenter adapters stop collecting metrics and enter a "Warning" state. The following status messages are displayed in the user interface:
Unable to connect to VCObject downThe "Validate Connection" action fails intermittently with "Connection refused" or "Error trying to establish connection."
Logs on the collector node (/storage/log/vcops/log/adapters/VMwareAdapter/VMwareAdapter_ID.log) contain the following error:
java.net.NoRouteToHostException: No route to host ( Host unreachable )
Aria Operations 8.18.5
This issue is caused by a network configuration error on the underlying network infrastructure (such as core switches). Specifically, missing syntax in static route configurations (e.g., a missing "tag" parameter) can cause traffic to be dropped or misrouted when Aria Operations attempts to resolve and connect to the vCenter via FQDN, even if IP-based connectivity appears functional.
To resolve this issue, you must verify the network path and correct the switch configuration.
Log in to the Aria Operations node (or Cloud Proxy) via SSH and run the following commands to test connectivity to the vCenter.
Test connection using the IP address:
curl -k telnet://<VC_IP_Address>:443
Test connection using the FQDN:
curl -k telnet://<VC_FQDN>:443
Engage your network team to review the configuration of core switches and firewalls between the Aria Operations nodes and the vCenter.
Once the network changes are applied, return to the Aria Operations UI: