Problem: Attempting to join an Appliance-based Platform Services Controller or vCenter Server to a vSphere domain fails with the error: ERROR_TOO_MANY_NAMES (68)
To resolve this issue, unregister the failed machine using the cmsso-util command.
To unregister the failed machine:
1. Log in as root to the appliance shell of one of the available Platform Services Controller appliances within the vSphere Domain.
2. To enable the Bash shell, run the shell.set --enabled true command.
3. Run the shell command to start the Bash shell and log in.
4. Run the cmsso-util unregister command to unregister the failed Platform Services Controller or vCenter Server:
cmsso-util unregister --node-pnid FQDN_of_failed_PSC_or_vCenter --username administrator@your_domain_name --passwd vCenter-Single-Sign-On-password
Where FQDN_of_failed_PSC_or_vCenteris the FQDN or IP address of the Platform Services Controller or vCenter Server that failed to install. Ensure that this is the correct FQDN or IP address before executing.
Note: After executing the command, the removal process is not recoverable. You must run this command only on one of the Platform Services Controller replication partners, as the synchronization removes the entries from all other Platform Services Controller replication partners.
After the preceding steps are executed, try installing the Platform Services Controller or vCenter Server again.
Run below command to show the list of the registered PSC/VCSA/Extensions.
/usr/lib/vmware-vmafd/bin/dir-cli service list
Example it will show the list like below
1. machine-50163016-ccba-42a0-9ab4-27a605873c2b
2. vsphere-webclient-50163016-ccba-42a0-9ab4-27a605873c2b
3. machine-a3881909-f496-4dc0-88d4-8d33700efbf5
4. vsphere-webclient-a3881909-f496-4dc0-88d4-8d33700efbf5
5. machine-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
6. vsphere-webclient-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
7. vpxd-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
8. vpxd-extension-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
9. SRM-remote-24f1330b-507d-4802-b896-9c73b352e4f6
10. SRM-remote-115c3d71-e85f-4fb5-af2d-8c21cd7be1b2
11. SRM-a52c6186-c829-452a-b97a-0fdf110e7336
12. SRM-remote-f196f1de-352b-496e-9495-1dd64f0f3fbe
13. com.vmware.vr-d673abc3-0fe6-446d-b18f-da5856d37292
14. com.vmware.vr-e9b25284-b7eb-431a-94f9-e73a66cd98cd
15. com.vmware.vr-de2f42b5-8114-468b-a889-62690f654793
After unregister the failed PSC/VCSA list should be like below.
1. machine-50163016-ccba-42a0-9ab4-27a605873c2b
2. vsphere-webclient-50163016-ccba-42a0-9ab4-27a605873c2b
3. machine-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
4. vsphere-webclient-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
5. vpxd-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
6. vpxd-extension-cdb8fbc0-bc40-11e6-a6c5-0050569d2101
7. SRM-remote-24f1330b-507d-4802-b896-9c73b352e4f6
8. SRM-remote-115c3d71-e85f-4fb5-af2d-8c21cd7be1b2
9. SRM-a52c6186-c829-452a-b97a-0fdf110e7336
10. SRM-remote-f196f1de-352b-496e-9495-1dd64f0f3fbe
11. com.vmware.vr-d673abc3-0fe6-446d-b18f-da5856d37292
12. com.vmware.vr-e9b25284-b7eb-431a-94f9-e73a66cd98cd
13. com.vmware.vr-de2f42b5-8114-468b-a889-62690f654793