SRM Collection Fails with “Incomplete Collection” Error After Configuring vCenter
book
Article ID: 407466
calendar_today
Updated On:
Products
VMware Usage Meter
Issue/Introduction
After configuring a vCenter Server in the Usage Meter, the SRM (Site Recovery Manager) endpoint shows the status as “Incomplete Collection”. Additionally, the Notifications tab displays the following error:
The following error is also seen in the collection-vcenter-error.log:
ERROR --- [#########-####-######] com.vmware.um.vccollector.VCCollector: SRM stage raised exception com.vmware.um.collector.CollectionError: SRM collection failed on server Y failed due to Collection error: Unknown Failure HTTP transport error: java.net.SocketTimeoutException: Connect timed out :: https://#.#.#.#:443/drserver/vcdr/extapi/sdk
Environment
VCF Usage Meter 9.x
Cause
The issue is caused by a network connectivity failure between the Usage Meter and the SRM endpoint. Specifically, the connection to the SRM service over port 443 is timing out, which leads to the SRM stage in the vCenter collection process failing. This was confirmed by attempting a connectivity test from Usage Meter appliance using the following command:
curl -v telnet://<SRM_IP>:443
The connection attempt failed, indicating that communication over port 443 is blocked or unreachable from the SRM.
Resolution
To resolve this issue, ensure that there is proper network connectivity between the Usage Meter and the SRM server over port 443.
Recommended Actions:
Engage your organization's networking team to verify and establish required communication paths.
Ensure there are no firewalls, ACLs, or security groups blocking outbound traffic to port 443 of the SRM server.
Once network communication is established, Edit and Save the vCenter Server endpoint in the Usage Meter.
After connectivity is confirmed and restored, the SRM collection should proceed successfully and the “Incomplete Collection” status should clear.