After a failed converge, vCenter Server shows as embedded
search cancel

After a failed converge, vCenter Server shows as embedded

book

Article ID: 324319

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

The purpose of the KB is to guide you through reverting any configuration changes that have been made by the converge process.

Symptoms:
  • The converge process failed.
  • A further converge attempt is not possible.
  • The vCenter Server Appliance shows the following output when connecting via SSH:
Type: vCenter Server with an embedded Platform Services Controller


Environment

VMware vCenter Server Appliance 6.5.x
VMware vCenter Server Appliance 6.7.x

Cause

The converge can fail for a number of reasons and as a result can leave the environment in an incomplete state. This can prevent another converge from bring started.

Note: These steps were first used when a converge failed with the known issue outlined in KB "install.vmafd.vmdir_vdcpromo_error_21" error during VC convergence, cross domain repoint and fresh deployment.

Resolution

As the full extent of changes made in the environment during a failed converge can vary it is recommended to restore both the PSC and vCenter Server from a backup that was taken while both nodes were offline.

Once restored, the converge can be re-attempted.

Workaround:
To work around this issue, you can attempt to restore some of the changes made during the converge process by following the steps below:
  1. Run the following commands to revert the changes made during the converge:
echo "management" > /etc/vmware/install-defaults/deployment.node.type;
sed -i 's/embedded/external/g' /etc/issue;
echo "management" > /etc/vmware/deployment.node.type;
sed -i 's/embedded/external/g' /etc/applmgmt/appliance/appliance.conf;

 
  1. Reconnect to the vCenter Server via SSH and confirm that the output now shows:
Type: vCenter Server with an external Platform Services Controller
 
  1. Reattempt the converge of the PSC.