VCDA - Unable to connect to vCenter

VCDA – Unable to connect to vCenter

VCDA

1 year ago

TL/DR – This post lists the investigation and troubleshooting steps taken, but no fix. No tech support since this is a lab.
VCDA 4.7.0.8400987-96215f032c in a VC to VC setup (no VCD) using vCenter 7.0.3 and ESXi 7.0.3, 20328353. VCDA was born on version 4.4
Site A has an outgoing V2V Protection to Site B.
Both sites VCDA’s report an banner error message for VM in scope – Unable to connect to vCenter ‘d5dd61d8-462d-44c1-9cd2-3e7b5b4f0362’.
New Outgoing Protection show the same error.

The vCenter cert did not expire (on both sites)
The guest VM in scope of replication is online.
VCSA on both site Setting and Peer Site do not report any issues. System health all green.

VCDA where the VM is resides, Settings / Service endpoints / Lookup Service address / Edit
Re-entered the VCDA service account used for the VC.
Did not resolve.
Reboot the VCDA VM. Did not resolve.
Repeated the same 2 step on the destination site VCDA. Did not resolve.

Replicator Services administration
Repaired the same VCDA.

Reading https://knowledge.broadcom.com/external/article/315168/unable-to-connect-to-vcenter-error-when.html
“This issue occurs on the destination site when the instance UUID of a resource vCenter Server in Cloud Director has changed, but Cloud Director is not aware of the vCenter UUID change or Cloud Director has an incorrect value saved for the vCenter UUID.”
Does not apply since there were not VC change to trigger a new UUID.
/opt/vmware/h4/cloud/log does not have any log files.
```
grep instanceUuid /etc/vmware-vpx/instance.cfg
```
shows Sita A’s vCenter matches the VCDA error ID>
instanceUuid=2d2a8e88-c3ba-4ea2-a2a3-4b5505d4d6ca
instanceUuid=d5dd61d8-462d-44c1-9cd2-3e7b5b4f0362

https://knowledge.broadcom.com/external/article?legacyId=78337
The vCenter SSO account used is not expired and does not have an expiration date.

https://knowledge.broadcom.com/external/article/315112/unable-to-connect-to-vcenter-error-when.html

/usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert --ep-type com.vmware.cis.cs.identity.sso 2>/dev/null

showed one STS.

Both vCenters 7.0.3 21290409 /ui/app/admin/certificates STS Signing Certificate are Valid until Feb 18, 2033

Rebooted Site A’s vCenter eventhough all services were running and was healthy.
Upgrade ISO via CLI
https://docs.vmware.com/en/VMware-Cloud-Director-Availability/4.7/VMware-Cloud-Director-Availability-Install-Config-Upgrade-On-Prem/GUID-C8F98C0C-B373-4129-A3AE-DC29E40AB85C.html
VMware-Cloud-Director-Availability-4.7.2.10056114-4ada44c9c3.iso
Upgrading the other VCDA did not resolve.