Unable to connect to vCenter server '##############################'.
ERROR - [UI-] [####################] c.v.h.c.c.error.ExceptionAdvisorBase : A GET request from root to /vm-replications?sourceSite=#&site=#&limit=1&includeTemplates=true failed.com.vmware.exception.CertificateMismatchException: Certificate seen on the network differs from the certificate we expectedat com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:67)
ERROR - [UI-] [###############] c.v.h.c.c.error.ExceptionAdvisorBase : A POST request from __system failed.com.vmware.vlsi.client.exception.VlsiClientException: VC not found: '################################'.at com.vmware.vlsi.client.sso.Ls2Gateway.findVc(Ls2Gateway.java:58)at com.vmware.h4.replicator.vc.VcConnector.vcServiceEndpoint(VcConnector.java:351)at com.vmware.h4.replicator.vc.VcConnector.vcSettings(VcConnector.java:396)
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware Cloud Director Availability 4.7.1
This issue occurs when the lookup service address of the vCenter server is not configured on the replicator instance. Additionally, if there is a certificate change on the vCenter server and the change is not updated on the VMware Cloud Director Availability appliance reverse replications will result in error e.g: "Unexpected error occurred".
To resolve the vSphere connectivity issue on the local replicator, re-configure the vCenter server lookup address on the replicator appliance.
To resolve 'Certificate seen on the network differs from the certificate we expected', re-establish the trust between the two sites.
To complete the Re-Trust establishment between the two sites, re-pair the two sites.
For more information, please see the VMware Cloud Director Availability document for replacing certificates: VMware Cloud Director Availability Documentation