vSphere replication shows not accessible on the Site recovery page.

Products

• VMware Live Recovery

Issue/Introduction

The customer is not able to access the vSphere replication and on the Site Recovery page below error is displayed.

 

Below is the error showed in the hms.logs 

xxxx-xx-xx 09:07:39.811 ERROR com.vmware.hms.remote.HmsServer.HMSSRV-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx [tcweb-11] (..hms.remote.HmsServerImpl) [operationID=f204519a-1898-462f-ac2c-fd6dd988271e-HMS-97763,sessionID=11B7467B] | Failed to compute capabilities of pairing with UUID 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx'.
com.vmware.jvsl.sessions.net.ContextUnavailableException: https://VC FQDN:443/lookupservice/sdk invocation failed with "org.apache.http.conn.ConnectTimeoutException: Connect to VC FQDN:443 [VC FQDN/VC IP] failed: Connect timed out"

Dr.log

2025-08-20 08:53:01,806 [srm-reactive-thread-517] WARN  com.vmware.srm.client.topology.impl.lspp.LsppNegotiator -1212916191214228897 7bc6ff83-9d74-41e2-aa5b-01d32ae69483  - Version negotiation for 'https://VC FQDN:443/lookupservice/sdk' failed.
com.vmware.vim.vmomi.client.exception.ConnectionException: Unable to connect to Lookup Service at https://VC FQDN:443/lookupservice/sdk. Reason: https://VC FQDN:443/lookupservice/sdk invocation failed with "java.net.ConnectException: Timeout connecting to [VC FQDN/VC IP:443]"
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:265)

Environment

VLSR 9.x

Cause

There is a connection issue from the vSphere replication to the vCenter on port 443.

root@VLSR [ ~ ]# nc -vvz VC IP/FQDN 443
VC FQDN [VC IP] 443 (https): Connection timed out
Total received bytes: 0
Total sent bytes: 0

Resolution

In the current scenario the customer was using VCHA prior to the upgrade to 8.0.3.

Though the VCHA was destroyed prior to the upgrade the eth1 network card was still active and the traffic between vCenter and vSphere replication was flowing through eth1 blocking the lookupservice connectivity.

Once eth1 was disabled on the vCenter,VLSR was able to communicate with lookup service fixing the issue.