vSphere Replication fails with the error "No connection to VR server: Unknown" shown on the replication VMs.
search cancel

vSphere Replication fails with the error "No connection to VR server: Unknown" shown on the replication VMs.

book

Article ID: 424288

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • Legacy replication for VM goes to Not Active state with the error message displayed below:

    A replication error occurred at the vSphere Replication Server for replication '####-#####'. Details: 'No connection to VR Server for virtual machine #####-#### on host ####.###.###.## in cluster ####.####.####.## in #####-######: Not responding'

  • The virtual machine summary page displays the error "No connection to VR server: Unknown".



  • The /varrun/log/vmkernel.log file of the ESXi Host hosting the replication VMs report below mentioned errors:

    YYYY-MM-DDTHH:MM.SSSZ cpu74:6226347)WARNING: Hbr: 5093: Failed to establish connection to [##.##.##.##]:31031 (groupID=GID-########-####-####-####-########): Failure
    YYYY-MM-DDTHH:MM.SSSZ cpu62:6226347)Hbr: 3410: Command: INIT_SESSION: error result=Failed gen=-1: Group GID-GID-########-####-####-####-########not registered
    YYYY-MM-DDTHH:MM.SSSZ cpu62:6226347)WARNING: Hbr: 3438: Command INIT_SESSION failed (result=Failed) (isFatal=FALSE) (Id=0) (GroupID=GID-########-####-####-####-########)
    YYYY-MM-DDTHH:MM.SSSZ cpu62:6226347)WARNING: Hbr: 5093: Failed to establish connection to [##.##.##.##]:31031 (groupID=GID-GID-########-####-####-####-########): Failure
    YYYY-MM-DDTHH:MM.SSSZ cpu52:6226347)Hbr: 3410: Command: INIT_SESSION: error result=Failed gen=-1: Group GID-GID-########-####-####-####-######## not registered
    YYYY-MM-DDTHH:MM.SSSZ cpu52:6226347)WARNING: Hbr: 3438: Command INIT_SESSION failed (result=Failed) (isFatal=FALSE) (Id=0) (GroupID=GID-GID-########-####-####-####-########)

 

 

Environment

  • VMware ESXi 8.x
  • VMware ESXi 9.x
  • VMware Live Site Recovery 9.0.x

Cause

  • Port 31031 is not open between the ESXi host at the protected site and the vSphere Replication appliance.
  • Netcat test from the source ESXi host to vSphere Replication report "Connection timed out":

    nc -zv ##.##.###.## 31031
    nc: connect to ##.##.###.## port 31031 (tcp) failed: Connection timed out

Resolution