vSphere Replication Appliance trying to register system under 'Replication Servers' that is not an appliance/ESXi host.
search cancel

vSphere Replication Appliance trying to register system under 'Replication Servers' that is not an appliance/ESXi host.

book

Article ID: 393258

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

After upgrading to vSphere Replication 9.x and ESXi 8.0u3, ESXi host fails to register as a replication server through HBRSRV.

The ESXi host has two management vmks:


Environment

vSphere Replication 9.x

ESXi 8.0u3

Nutanix Array

Cause

vSphere Replication Appliance tries to register system under 'Replication Servers' that is not a vSphere Replication appliance or ESXi host.

  • vSphere Replication is trying to register an IP address that does not correspond to an ESXi host management IP. (Such as Nutanix management interface)
  • In certain Nutanix environments, management is tagged on two VMK interfaces, with Nutanix using vmk0, while ESXi management is using a different vmk such as vmk1 or vmk2. This can cause conflict issues with Enhanced Replication.
  • This issue may arise after upgrading to vSphere Replication 9.0 and ESXi 8.0u3. In these versions, the hbrsrv service begins registering ESXi hosts as replication servers. Traditional vSphere Replication routes traffic to the replication appliance at the target site. With Enhanced vSphere Replication, replication traffic goes directly to the host at the target site.

See Enhanced vSphere Replication

Resolution

1. SSH to ESXi

2. Show ESXi management VMK
esxcfg-advcfg -g /Net/ManagementIface

3. Set ESXi management VMK to where it needs to be (example vmk2)
esxcfg-advcfg -s vmk2 /Net/ManagementIface

4. On the Replication appliance, clear the HostInfo table:

  •  ssh into Replication server that is showing disconnected.
  • cd /etc/vmware/ and make a backup of the latest hbrsrv.*.db file: ie 'cp hbrsrv.85.db'
  • Perform the command to stop service: service hbrsrv stop
  • Perform the command to remove "hostinfo" table which can cause the disconnection: sqlite3 /etc/vmware/hbrsrv.85.db "DELETE FROM HostInfo;"
  • Make sure hbrsrv db file has the appropriate number
  • Make sure table information was remove with sqlite3 /etc/vmware/hbrsrv.85.db "select * from HostInfo;"
  • Start HBRSRV service: service hbrsrv start
  • SSH to replication appliance and perform: service hms restart
  • From SRM gui perform a reconnect on disconnected replication server if needed (Often times automatically reconnects)

5 . Lastly, reboot the hosts that had the vmk misconfiguration

Additional Information

Powered by Wolken Software