Error: vsr-sdr : vSphere Replication Management Server could not establish connection to vSphere Replication Server at '127.0.0.1:8123'Reconnect vSphere Replication Server | #### | The object 'vim.VirtualMachine:vm-####' has already been deleted or has not been completely created.hbrsrv.log indicates that an SSL thumbprint mismatch or initialization error is causing HMS login to fail: warning hbrsrv[####] [Originator@6876 sub=Main opID=####-HMS-PING] [0] Invalid login warning hbrsrv[####] [Originator@6876 sub=Main opID=####-HMS-PING] [1] Unknown client SSL thumbprint ####Reconnect vSphere Replication Server | vCenter_FQDN_Name | The object'vim. VirtualMachine:vm-####' has already been deleted or has not been completely created.
hbrsrv.log indicates that the SSL thumbprint mismatch is causing HMS login to fail.YYYY-MM-DDThh:mm:ss.ms.094+07:00 warning hbrsrv[01004] [Originator@6876 sub=Main opID=####-####-####-####-####-HMS-PING---Ping Thread for session key: N/A and vmomi session: null and server: 127.0.0.1:8123] HbrError stack:YYYY-MM-DDThh:mm:ss.ms.094+07:00 warning hbrsrv[01004] [Originator@6876 sub=Main opID=####-####-####-####-####-HMS-PING---Ping Thread for session key: N/A and vmomi session: null and server: 127.0.0.1:8123] [0] Invalid loginYYYY-MM-DDThh:mm:ss.ms.094+07:00 warning hbrsrv[01004] [Originator@6876 sub=Main opID=########-####-####-####-####-HMS-PING---Ping Thread for session key: N/A and vmomi session: null and server: 127.0.0.1:8123] [1] Unknown client SSL thumbprint 06:FE:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:E1YYYY-MM-DDThh:mm:ss.ms.094+07:00 warning hbrsrv[01004] [Originator@6876 sub=Main opID=e4601195-0405-431d-85aa-5aebd7671725-HMS-PING---Ping Thread for session key: N/A and vmomi session: null and server: 127.0.0.1:8123] [2] Error converted to Vmomi fault hbr.replica.fault.InvalidLogin
The SSL thumbprint used by hbrsrv does not match the one configured for hms.
Run the following command to compare the thumbprint between hbrsrv and HMS.
root [ /opt/vmware/support/logs ]# /usr/bin/hbrsrv-guestinfo.sh get guestinfo.hbr.hbrsrv-thumbprint
06:FE:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:E1
root [ /opt/vmware/support/logs ]# /usr/bin/hbrsrv-guestinfo.sh get guestinfo.hbr.hms-thumbprint
6F:4F:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:####:E1
VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x
This issue can occur due to one of the following reasons:
hbrsrv (Replication Service) trust settings are not fully initialized in memory, even if SSL thumbprints match at the OS level.hms and hbrsrv services.HostInfo database table are preventing the service from starting correctly.Follow these steps to resolve the connection issue:
hbrsrv service to force the process to load verified thumbprint configurations into memory: systemctl restart hbrsrv/usr/bin/hbrsrv-guestinfo.sh get guestinfo.hbr.hbrsrv-thumbprint/usr/bin/hbrsrv-guestinfo.sh get guestinfo.hbr.hms-thumbprint/usr/bin/hbrsrv-guestinfo.sh set guestinfo.hbr.hms-thumbprint [CORRECT_THUMBPRINT]systemctl restart hbrsrvIf you require a software update or patch to resolve persistent connectivity issues, please see .
To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.