VCDA replications in and out of one site failing after a vCenter upgrade

Products

• VMware Cloud Director
• VMware Cloud Director Availability - Disaster Recovery 4.x
• VMware Cloud Director Availability - Migration 4.x

Issue/Introduction

• In the site's Cloud Director Availability Portal, you see an increasing number of RPO violations for replications.
• Performing a pause and then resume of the replications doesn't start the synchronization for the impacted replications with RPO violations.
• vCenter Server was recently upgraded.
• There may not be any health issues showing on the Appliance Health Status pages.
• The replicator.log files may show errors similar to the following:
  
  

  WARN - [UI-<UUID>] [job-##] c.v.h.r.diagnostics.DiagnosticsService   : Unable to connect to vc <UUID> with manager <UUID>'s credentials
  
  com.vmware.vlsi.client.exception.InvalidVcLoginException: (vim.fault.InvalidLogin) {
     faultCause = null,
     faultMessage = null
  ...

Environment

VMware Cloud Director Availability 4.7.3.x

Cause

As part of the registration with the site, there are details stored between the sites to facilitate and maintain the health of the connection. The vCenter upgrade can invalidate this registration and prevent appropriate validation of a healthy configuration.

 

Resolution

Repair the VCDA Appliance registrations with the vCenter Server Lookup service of the upgraded vCenter. The procedure is outlined in the documentation:

Configure after changing the vCenter SSO credentials

Additional Information

Similar issues may happen if the vCenter SSO Credentials were recently updated.

KB 415446 : Failing to authenticate to vCenter server error after updating the SSO credentials for an on-premise VMware Cloud Director Availability appliance