vSphere Replication Cycles Fail with Socket Timeout Errors

Products

• VMware Live Recovery

Issue/Introduction

 Virtual machines configured for replication via a primary vSphere Replication Server fail to synchronize. Other virtual machines on the same source ESXi host replicate successfully to alternative targets.

• hms.log: A replication error occurred at the vSphere Replication Server for replication '####'. Details: 'No connection to VR Server for virtual machine #### on host #### in cluster ####: Not responding'.
• vmkwarning.log: WARNING: Hbr: 5362: Failed to establish connection to [####]:31031: Timeout

Environment

• VMware vSphere Replication 9.x
• VMware vCenter Server 8.x
• VMware ESXi 8.x

Cause

An intermediate firewall or network security policy blocks outbound TCP port 31031 traffic from the source ESXi host to the target vSphere Replication Server.

Resolution

1. Coordinate with Network Security to audit the path between the source ESXi replication interface (####) and the target vSphere Replication Server (####).
2. Permit outbound TCP Port 31031.
3. Permit outbound TCP Port 32032 if "Network encryption" is enabled on the replication group.
4. Verify connectivity from the ESXi shell: nc -zv #### 31031
5. Force a replication sync in the vSphere Client once the handshake succeeds.

• Port numbers that must be open for vSphere Replication
• Contact Broadcom Support

Additional Information

Port numbers that must be open for vSphere Replication - https://knowledge.broadcom.com/external/article/312798