Unable to force unregister vCenter Server from VMware Live Cyber Recovery (VLCR)

Products

• VMware Live Recovery

Issue/Introduction

 

• Administrators are unable to unregister a vCenter Server from the VMware Live Cyber Recovery (VLCR) inventory.

• The Force Unregister action in the VLCR UI fails or errors out.
  
  

• The vCenter Server is standalone (not in Linked Mode).

 

Environment

 

VMware Live Cyber Recovery (VLCR)
VLCR Cloud Connector (Release 10.7.x or later)

 

Cause

The vCenter Server registration has become stale or desynchronized within the Cloud Connector's local configuration database. While the SaaS management plane attempts to trigger removal, the local connector retains the entry, causing the workflow to fail.

Resolution

To resolve this issue, you must manually remove the vCenter reference from the Cloud Connector using the Command Line Interface (CLI).

1. SSH into the VLCR Cloud Connector appliance using the root credentials.

2. Identify the site-id and the vcenter-ip of the vCenter you wish to remove.

3. Verify the vCenter exists in the connector's database by running the following command:

   vcenter show --site-id <SITE_ID> --vcenter <VCENTER_IP>

4. Execute the force removal command:

   vcenter remove --site-id <SITE_ID> --vcenter <VCENTER_IP>

5.  Verify the removal by running the show command again. The output should be empty or indicate the record is not found.

   vcenter show --site-id <SITE_ID> --vcenter <VCENTER_IP>
   

6. Return to the VLCR SaaS Console and refresh the page to confirm the vCenter is no longer listed.

    

Additional Information

 

• Warning: Ensure you are removing the correct vCenter IP. This command modifies the connector's local configuration immediately.

• If the vCenter remains visible in the UI after these steps, contact Broadcom Support to clear the stale entry from the SaaS backend.