Server with UUID not found error in VMware Live Site Recovery 9.x

Products

• VMware Site Recovery Manager

Issue/Introduction

When attempting to access or pair sites in VMware Live Site Recovery (formerly Site Recovery Manager), the UI displays the following errors:

• Server with UUID '########-####-####-####-############' not found.
• Server for guid '########-####-####-####-############' not found, but pair server(s) exist.
• Site pairing status shows as "not accessible" or "disconnected."

Environment

• VMware Live Site Recovery (VLSR) 9.0.x
• VMware vCenter Server 8.0.x
• Enhanced Linked Mode (ELM)

Cause

This issue occurs due to a synchronization failure in the VMware Directory Service (VMDir).

1. Broken VMDir Replication: Bidirectional replication agreements between vCenter SSO nodes are missing or broken, preventing solution user GUIDs from synchronizing.
2. Hostname/PNID Mismatch: Inconsistencies between the vCenter hostname and its Primary Network ID (PNID) disrupt Lookup Service registrations.
3. Stale Extensions: A previous appliance was redeployed without first breaking the site pair.

Resolution

Follow these steps to restore directory synchronization and site pairing:

I. Verify vCenter Hostname and PNID

1. Log into the vCenter Server Appliance via SSH.
2. Run the following commands to check for inconsistencies:

   hostname -f/usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost

3. If there is a mismatch (e.g., casing differences), update the PNID to match the FQDN exactly.

II. Recreate VMDir Replication Agreements

1. Check the current replication status on both vCenter nodes:

   /usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator -w ####

2. If no partners are listed or the status is not "available," manually recreate the bidirectional partnership:

   /usr/lib/vmware-vmdir/bin/vdcrepadmin -f createpartnership -h <Local_VC_FQDN> -H <Remote_VC_FQDN> -u administrator -w ####

3. Verify that "Partner is 0 changes behind" is reported for both nodes.

III. Reconfigure the Appliances

1. Log into the VAMI (https://<Appliance_IP>:5480) for the VLSR/SRM appliances at both sites.
2. Navigate to Summary > Configure Appliance.
3. Select Unregister to remove the stale extension from vCenter.
4. Perform the Register process again for both sites to refresh the Lookup Service entries.
5. Restart the vsphere-ui service on the vCenter Servers:

   service-control --restart vsphere-ui

6. Re-attempt the site pairing from the Site Recovery UI.

Note: For defects related to directory synchronization, recommend the user subscribe to this article (reference: https://knowledge.broadcom.com/external/article/275360) to be updated on fix status.