"Timeout while waiting for the vSphere replication manager server to become connected" while Connecting/Pairing vSphere Replication or VMware Live Site Recovery

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• Connecting the target site reports an error on web client:
  
  "timeout while waiting for the vSphere replication manager server to become connected".
• Pairing of vSphere replication fails with below error,

         

• Site Recovery Manager Plugin show similar error for vSphere Replication as below,

         

Issue Validation:

• In the HMS.log file, you see error similar to:
  
  "2017-04-03 19:35:39.083 TRACE hms.updates.changeManager [tcweb-5] (..vmware.hms.ChangeManagerImpl) operationID=1b51e42c-####-####-####-dd9d91a83c63-HMS-15647017 | Got 0 object changes.
  2017-04-03 19:35:39.083 TRACE hms.updates.changeManager [tcweb-5] (..vmware.hms.ChangeManagerImpl) operationID=1b51e42c-####-####-####-dd9d91a83c63-HMS-15647017 | Got 0 collection changes.
  2017-04-03 19:35:39.386 ERROR jvsl.sessions [Ping Thread for server 172.xx.xx.xxx:8043] (..net.impl.VmomiPingConnectionHandler) | Ping session on server 172.xx.xx.xxx:8043 failed: (vim.fault.NotAuthenticated) {
  faultCause = null,
  faultMessage = null,
  object = ManagedObjectReference: type = HmsSessionManager, value = session-manager, serverGuid = 25f22817-####-####-####-6e5f5e45ce5e,
  privilegeId = System.View
  }
  (vim.fault.NotAuthenticated) {
  faultCause = null,
  faultMessage = null,
  object = ManagedObjectReference: type = HmsSessionManager, value = session-manager, serverGuid = 25f22817-####-####-####-6e5f5e45ce5e,
  privilegeId = System.View
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
  
  
• In the Virgo.log file, you see error similar to:
  
  Caused by: com.vmware.vim.binding.hms.fault.CannotVerifyCredentialsFault: Cannot verify login credentials. The authentication service infrastructure is not responding.
  at sun.reflect.GeneratedConstructorAccessor1097.newInstance(Unknown Source)
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
  at java.lang.Class.newInstance(Class.java:383)

Environment

VMware vSphere Replication

VMware Site Recovery Manager 8.x

VMware Live Site Recovery

Cause

The issue occurs because of the time taken to get the name resolution from the domain controllers or DNS servers

Resolution

The issue should be resolved by the administrators in charge of DNS servers or Domain Controllers

 

Workaround

 

• To workaround this issue, add the vCenter, SRM and VRMS  IP and FQDN for both paired sites in the /etc/hosts file on both VRMS, vCenter and SRM appliances.
• To add the vCenter IP and FQDN:

 

1. Log in to vSphere Replication Appliance.
2. Run these commands:
   
   cd /etc
   cp hosts hosts.bak (to create back for host file )
   vi hosts
   
   
3. Enter I key to enable insert mode.
4. Move the cursor, create an entry for vCenter, SRM and VRMS IP and FQDN for both sites below the local host entry.
   
   Example of hosts file:
   
   # VAMI_EDIT_BEGIN
   127.x.x.x localhost
   192.xxx.x.xx srmr-a.example.local srmr-a
   # VAMI_EDIT_END
   
5. Add the vCenter IP and FQDN after vSphere Replication Appliance IP and FQDN.
   
   Example of hosts file after the change:
   
   # VAMI_EDIT_BEGIN
   127.x.x.x localhost
   192.168.x.xx srmr-a.example.local srmr-a
   192.167.x.xx vcprod.example.local vcprod
   192.166.x.xx vr.example.local vr
   # VAMI_EDIT_END
   
   
6. Connect the target site.
   
   Note: If the connection fails, restart web client services of vCenter on both sites and try to connect.

Additional Information

Check if the ports are open between both the sites. For more information, see Port numbers that must be open for vSphere Replication 8.x.