Error: Connection refused during SRM Re-protect or reverse replication workflow in vSphere Replication

Products

• VMware Site Recovery Manager

Issue/Introduction

• SRM Re-protect or reverse replication tasks fail to synchronize after a planned migration.
• This article provides steps to resolve connectivity failures between vSphere Replication Management Servers (VRMS) and ESXi hosts when the hms.log reports "Connection refused" or an "endless loop of dynamic operation IDs."
  
  

Environment

• VMware Site Recovery Manager (SRM) 8.x, 9.x
• vSphere Replication 8.x, 9.x
• ESXi 7.x, 8.x

Cause

• The error occurs when the vSphere Replication service state becomes inconsistent following a site failover, causing the target VR server to refuse connections from source ESXi hosts.
• This is often due to service stalls or missing routing persistence on the VRMS appliance.

Resolution

Follow these steps to restore connectivity:

1. Log into the vSphere Replication Appliance (VRMS) at the recovery site via SSH.
2. Restart the management and replication services:
   bash

    

   systemctl restart hms hbrsrv

3. Migrate the vSphere Replication appliance to a different ESXi host in the cluster to refresh the virtual switch port state.
4. Verify that ports 31031 and 44046 are open between the source ESXi hosts and the VR server.
5. If running vSphere Replication 9.x, upgrade to a version containing the permanent fix.

Fixed in release vSphere Replication 9.0.2.1 and higher. See Download Broadcom products and software for steps to download this release.

Additional Information

For further assistance, see Contact Broadcom Support. To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.