Error : A replication error occurred at the vSphere Replication Server for replication "VM name: test". Details: 'No connection to VR Server for virtual machine "VM name: test" on host "ESXi host : host#" in cluster "Cluster name : cluster#" in "Cluster name : cluster#" : Unknown'.
Virtual Machines appears as "Not Active (RPO Violation)" on some vCenter Server UI/ESXI hosts but will be working when vMotioned to other ESXI hosts.
Below events from the logs of Source ESXi host /var/log/run/vmkernel, indicates connection failure on port 31031 used for replication at destination VR
WARNING: Hbr: 5362: Failed to establish connection to [Appliance_IP]:31031 ... Timeout/opt/vmware/support/logs/dr-client/dr.log.2026-08-28 01:53:24,322 [srm-reactive-thread-5768] WARN com.vmware.vr.client.replications.VrIssuesDataHandlerBase -############# #########-####-####-####-############ getPairSrmSummaryIssues - Cannot access remote vSphere Replication server.com.vmware.srm.client.topology.client.view.availability.PairSetup$PairSetupException: Unable to connect to Lookup Service at https://#####:443/lookupservice/sdk. Reason: https://#######:443/lookupservice/sdk invocation failed with "java.net.UnknownHostException: ########: Temporary failure in name resolution".
vSphere Replication 8.x / 9.x
VMware Live Recovery (VLR) 9.x
This issue occurs when the target vSphere Replication appliance is unable to communicate with the source ESXi host's VMkernel interface, with replication traffic tagged, due to a missing static route, especially when the source is on a different subnet.
If the appliance can't reach the source OR destination network (it depends where the appliance is placed), add a static route. To add a static route to the vSphere Replication, you need to SSH the appliance. By default SSH service is disabled using vSphere Replication VAMI enable the SSH feature.
root@V####R [ ~ ]# /usr/bin/enable-sshd.sh
root@V####R[ ~ ]# service sshd start
In the above screenshot:
10-eth0.network -> Management
10-eth1.network -> VR Traffic
10-eth2.network -> VR NFC Traffic
NOTE: Edit the NIC configured for VR traffic, this could depend on your NIC configuration in the appliance. Below is an example from the KB: Isolating the Network Traffic of vSphere Replication
VRMSPR is the prod site vSphere replication appliance
VRMSDR is the Recovery site vSphere replication appliance
In the above screenshot, a static route entry for the source ESXi host network (###.###.##.#.#/##) has been added to the 10-eth1.network file on the DR site replication appliance, which is used by a VMkernel interface to handle replication traffic.
In the above screenshot, a static route entry for the source ESXi host network (###.###.##.#.#/##) has been added to the 10-eth1.network file on the PROD site replication appliance, which is used by a VMkernel interface to handle replication traffic.
Running tests to check if static route is working:
# netstat –r
vmkping commandvmkping -I <VMK# of VR network> <IP address of VR appliance>
You can also PING the hosts from the VR appliance to test connectivity.
Static routes are specifically required when the host must transport traffic to a destination network outside of it's own datacenter that has a different IP range.
For detailed information on how traffic is isolated in vSphere replication refer to this document: Isolating the Network Traffic of vSphere Replication