No connection to VR Server for virtual machine due to time sync failure
search cancel

No connection to VR Server for virtual machine due to time sync failure

book

Article ID: 450999

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • All the connectivity between vCenter, SRM and vSphere replication servers look healthy and connected.

  • Virtual machine with replication configured shows the below alert in vCenter server:



  • When trying to configure replication for a VM using vSphere replication following error is reported in the hbr-agent.log

    error: [Proxy [Group: GID-####-####-####-####] -> [<ip-addr>:32032]] Failed to login to brokered server: (18) Login denied.
    error: [Proxy [Group: GID-####-####-####-####] -> [<ip-addr>:32032]] Failed to login to brokered server additional error info: Broker or host clocks may be out of sync.
    error: [Proxy [Group: GID-####-####-####-####] -> [<ip-addr>:32032]] Exhausted all server endpoints reported by broker.
     

Environment

VMware vSphere Replication 8.x

VMware vSphere Replication 9.x

Resolution

  1. Verify NTP settings on all ESXi hosts, vCenter Server, and the vSphere Replication appliance to ensure they are synchronized with the same authoritative time source.
  2. If time drift is detected, correct the time configuration on the affected systems.
  3. Restart the hms and hbrsrv services on the vSphere Replication appliance: service hms restart service hbrsrv restart
  4. Restart the hbrsrv service on the ESXi host: /etc/init.d/hbrsrv restart
  5. Verify the connection to port 32032 from the ESXi host to the VR appliance: nc -zv <VR_Appliance_IP> 32032

If these steps do not resolve issue please contact Broadcom Support for assistance.