VLCR Connector in Protected Site is unable to reach vCenter due to Login Credentials

Products

• VMware Live Recovery

Issue/Introduction

The following error can be seen in the VLCR UI:
"Connector <connector name> in protected site <site name> is unabe to reach vCenter <IP address>. Cannot complete login due to an incorrect username or password on port 443."

The following message is seen when running the cli command 'drc network test --scope all'  on the VLCR connector. Typically you would expect to see the local, on-premise, ESXi hosts listed in this output as well.



The expected output of the cli command 'drc network test --scope local' on the VLCR connector should also include both the vCenter information and on-premise ESXi host information. When running the 'drc network test --scope local' cli command only the on-premise vCenter information was shown along with the login error message.

Environment

VMware Live Cyber Recovery

Cause

The vCenter had been reprovisioned with the same IP address, but the on-premise vCenter NTP settings no longer matched the NTP settings of the on-premise ESXi host that contained the VLCR connectors. The reprovision of the vCenter also means that there was a change in the UUID (unique identifier) tied to the on-premise vCenter. This change in the UUID is not automatically recognized by VLCR.

Resolution

Check the on-premise vCenter NTP settings and on-premise EXSi host NTP settings to verify that the settings match. There are several ways to view and configure this information. Helpful articles are posted below:

• Configuring Network Time Protocol (NTP) on an ESXi host using the vSphere Client
• Configure the System Time Zone and Time Synchronization Settings with the vCenter Server Management Interface

After verifying or correcting the NTP settings, the next step is to re-register the vCenter. There are two ways to re-register the vCenter:

• The reregister button in the VLCR UI.

            

OR

• Use the cli command 'drc register-vcenter --reregister --vcenter <x.x.x.x.> --username <vsphere-user> --password <vsphere-password>' in the connector ssh session.
  1. Replace the <x.x.x.x> with the appropriate vCenter IP address.
  2. Replace the <vpshere-user> with the appropriate username. 
  3. Replace <vsphere-password> with the correct password.

Additional Information