Duplicate vCenter Instances registered with your Platform Services Controller can occur when you re-deploy a vCenter with the same name or in the same database. Duplicate vCenter instances can exist after a faulty certificate replacement as well.
Apart from the annoying ‘Can’t connect to vcenter.fqdn/sdk‘ message, some features are relying on properly configured vCenters within your SSO domain. You can get issues with your License Manager or with tools like vSphere Replication.
To recover from such a situation please follow these steps:
* The following steps are for the Appliance-Based vCenter and Platform Services Controllers. And tested on 6.5 U1
- Connect to the Platform Services Controller using SSH.
- Enable the shell by typing the ‘shell’ command.
- Create a text file with a list of the services registered within the Platform Services Controller, by running this command:
/usr/lib/vmidentity/tools/scripts/lstool.py list –url http://localhost:7080/lookupservice/sdk –type vcenterserver > /tmp/psc_vcenter_instances.txt
- Open the generated text file to find a list of services registered to the Platform Services Controller, by running this command: ‘cat /tmp/psc_vcenter_instances.txt’In the text file, you see output similar to:Name: AboutInfo.vpx.name
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: 1dbc3e9f-626d-4314-8731-ca744a0d9f4b
Site ID: home
Node ID: d3eba55a-d4df-11e4-b3f7-000c2987c143
Owner ID: firstname.lastname@example.org
Your duplicate vCenter should be in here.
- To unregister the duplicate instance, run this command:/usr/lib/vmidentity/tools/scripts/lstool.py unregister –url http://localhost:7080/lookupservice/sdk –id ‘Refer to the RED output from the previous step’ –user ‘email@example.com‘ –password ‘administrator_password‘ –no-check-cert