This is a known issue affecting vCenter Server 6.0.x.
To resolve this issue, perform one of these options.
Replace the failed PSC
- Power off the corrupted PSC.
- Repoint vCenter Server associated with failed PSC to another PSC in the same region using this command:
cmsso-util repoint --repoint-psc OTHER_PSC_FQDN
Where OTHER_PSC_FQDN is the correct PSC.
- Log in to vCenter Server.
To Repoint vCenter Server associated with the failed PSC to another PSC in the same region:
Note: Deploying a new PSC in the existing SSO site may fail if there is an existing entry for the PSC host name. Therefore, perform these steps before deploying a new PSC:
- Clean the SSO database.
- Connect to the working PSC using SSH.
- Run this command to list all PSC servers in the vsphere.local domain:
/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showservers -h localhost -u administrator -w PASSWORD
- Run this command to unregister failed PSCs from the SSO database:
/usr/lib/vmware-vmdir/bin/vdcleavefed -h hostname -u administrator -w PASSWORD
Where hostname is the hostname of the PSC that must be removed.
Deploy new PSC appliance by selecting existing SSO site and repoint to vCenter Server to the newly deployed PSC
- Join the Platform Services Controller for the Management vCenter Server to the Active Directory.
Note: Before deploying a new PSC instance, ensure that the default identity source is set.
- Navigate to Administration > Single Sign-On > Configuration > Identity Sources.
- Repoint vCenter Server to the newly deployed PSC.
- Run this command in the vCenter Server:
cmsso-util repoint --repoint-psc NEW_PSC_FQDN
Where NEW_PSC_FQDN is the new PSC FQDN.
- Run this command to verify that vCenter Server is pointing to newly deployed PSC:
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost
- Log in to vCenter Server usingthe vSphere Web Client.