vCenter Server Converge Tool - How do I Converge an Environment Using the UI
vSphere 6.7 Update 2 is now available! Inside this update include enhancements to the vCenter Server Converge Tool. Let’s dive in and take a look at whats new and see how to converge a deployment using the new UI.
Included in vSphere 6.7 Update 2 is an overhauled system configuration section. Within system configuration you have a table view showing you the Platform Services Controllers and vCenter Servers in your Environment.
vCenter Server Topology View
Alongside the new system configuration table view there is a new topology view. This view allows you to have a graphical representation of the nodes in your SSO domain. This is useful when someone might’ve configured additional replication agreements between External Platform Services Controllers. Previously the only method to view replication agreements was using vdcrepadmin against each PSC in your environment to manually build out the topology diagram.
When I am in the field we tend to inform users about how to properly setup additional replication agreements in an SSO domain when using 3 or more External PSCs or Embedded vCenter Servers. My recommendation is to create one additional replication agreement to be used as a ring topology. At some point I have heard of customers using a mesh topology, without mapping out all the replication agreements they may have never known they were in a non-recommended topology. Using the new topology view you can easily see if someone incorrectly setup additional replication agreements and then go back in and clean them up using vdcrepadmin.
vCenter Server Converge Tool UI
When reviewing the new table view you might have noticed two new buttons. You now have the ability ability to Converge and Decommission nodes through the vSphere Client. No longer are you required to utilize the CLI and JSON templates to run the converge tool! This is great for customers or partners who wish for a simplistic and foolproof method to migrate their vSphere Environment to an Embedded vCenter Server Deployment.
I will run through a convergence example of a vSphere Environment that has two External PSCs and two External vCenter Servers. I will be migrating these nodes to vCenter Servers with an Embedded PSC.
Once I have selected our vCenter Server Appliance that we wish to converge to embedded I will first be notified that the vCenter Services will be restarted and then the next step will proceed to the information gathering screen. If you have previously used the CLI based Converge Tool you might of remember being prompted for the managing vCenter Server credentials. This is no longer needed as the vCenter Server Converge Tool is already aware of this information.
On this screen I’ll will be prompted certain pieces of information:
- External PSC SSO Username and Password
- Needed to be able to install the required components to the vCenter Server and allow replication between the new embedded vCenter Server and the existing External PSC.
- New Replication Partner
- As seen below you can see that no embedded node is available. This is because this is the first node I have ran the converge utility against and it will reuse the existing replication agreement. When I proceed to converge any additional vCenter Servers I will see the already existing vCenter Servers with an Embedded PSC and will have the ability to choose a replication partner.
- Skip AD Join or Join AD
- If you wish to join your vCenter Server Appliance to Active Directory then select this option and you will prompted to enter in additional information.
- Acknowledge that you have made a backup of your vCenter Server Appliance before initiating convergence.
- This is extremely important as you are making major changes to your vSphere Environment. Before proceeding with convergence not only should you back up the node you are currently converging, but you should be backing up ALL External PSC and vCenter Servers within your SSO domain. To perform a backup you should be using the built in file-based backup in the VAMI and NOT relying on snapshots.
Once I have successfully converged both our vCenter Servers I can now proceed to decommission the two External PSC’s. As we are already aware of the managing vCenter Server all we need to do is enter in the vCenter Server SSO credentials so that the external PSC can be shutdown and unregistered from the SSO domain.
Now that the converge and decommission process is completed, I will go back and review the toplogy view to see that we now have migrated to our simplified deployment topology using Embedded PSCs.
- Blog: Understanding the vCenter Server Converge Tool
- Blog: vCenter Server Converge Tool Enhancements in vSphere 6.7 Update 2
- Product Walkthrough: Converging a Load Balanced External vCenter Deployment using the vSphere Client
- Product Walkthrough: Converging an External vCenter Deployment using the vSphere Client
- Documentation: vCenter Server Converge Tool
Share this postcomments powered by Disqus
- Patching the vCenter Server Appliance (VCSA) using the REST API - Part 2 (PowerCLI Module)
- Patching the vCenter Server Appliance (VCSA) using the REST API - Part 1 (Postman Collection)
- Upgrading Platform Services Controller and vCenter Server via the CLI Installer
- Patching your vCenter Server Appliance from 6.7 to 6.7a
- Upgrading to VMware vSphere 6.7