Upgrading Load Balanced PSCs 6.x to vCenter Server 7.0
search cancel

Upgrading Load Balanced PSCs 6.x to vCenter Server 7.0

book

Article ID: 318205

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This article details the steps that need to be taken when upgrading a vSphere 6.5 or 6.7 environment that has external, load-balanced Platform Services Controllers to vCenter Server 7.0.

Note: With vSphere 7 there is no longer a Windows installed vCenter Server and all references to vCenter Server are for the Appliance.

Environment

VMware vCenter Server 7.0.x

Resolution

Single vCenter Server Environments

  1. Create powered-off snapshots or backups the vCenter Server and Platform Service Controllers.
  2. Upgrade or migrate the vCenter Server to 7.0.
  3. Re-point any external solutions that originally used the Platform Services Controller VIP address as a direct endpoint. (i.e. vSphere NSX) 
  4. Power off the 6.7 Platform Services Controllers.
  5. Decommission the 6.7 Platform Services Controllers from the vCenter Server using the CLI.
  • Log in as root to the appliance shell of vCenter Server Appliance.
  • Run the shell command to start the Bash shell and log in.
  • Run the cmsso-util unregister command to unregister the stopped Platform Services Controller:
cmsso-util unregister --node-pnid PSC_NAME --username administrator@your_domain_name --passwd 'vCenter_Single_Sign_On_password'
  • Where, PSC_NAME is the FQDN or IP address of the Platform Services Controller that you want to decommission. Please enter vCenter_Single_Sign_On_password in quotes.
  • Note: There is downtime involved in executing cmsso-util unregister command, it will restart the services on the vCenter Server / PSC where you are executing the command.
  • Repeat this process for any remaining Platform Services Controllers in the environment
  1. Decommission the Platform Services Controller VIP from the vCenter Server using the same command used to decommission the Platform Services Controllers.
cmsso-util unregister --node-pnid PSC_VIP_NAME --username administrator@your_domain_name --passwd 'vCenter_Single_Sign_On_password'
  1. Where, PSC_VIP_NAME is the FQDN or IP address of the Load Balancer that you want to decommission. Please enter vCenter_Single_Sign_On_password in quotes.
  2. Note: Decomissioning the PSC VIP will end with an expected error as the VIP does not contain any PSC services itself: 
 "Stdout = vdcleavefd offline for server"
 
  1. Delete the Platform Services Controller virtual machines that you no longer need from the vSphere inventory.
 

Multiple vCenter Server Environments 

  1. Create powered-off snapshots or backups the vCenter Servers and Platform Service Controllers.
  2. Upgrade or migrate every vCenter Server in the SSO domain to 7.0. When asked to supply the replication partner during each upgrade, ensure to choose consecutively to begin the formation of a ring topology between the 7.0 vCenter Servers.
  3. Re-point any external solutions that originally used the Platform Services Controllers or the VIP addresses as a direct endpoint. (i.e. vSphere NSX) 
  4. Power off the 6.7 Platform Services Controllers.
  5. Decommission all of the 6.7 Platform Services Controllers from the vCenter Server using the CLI.
  • Log in as root to the appliance shell of a vCenter Server Appliance.
  • Run the shell command to start the Bash shell and log in.
  • Run the cmsso-util unregister command to unregister the stopped Platform Services Controller:
cmsso-util unregister --node-pnid PSC_NAME --username administrator@your_domain_name --passwd 'vCenter_Single_Sign_On_password'
  • Where, PSC_NAME is the FQDN or IP address of the Platform Services Controller that you want to decommission. Please enter vCenter_Single_Sign_On_password in quotes.
  • Note: There is downtime involved in executing cmsso-util unregister command, it will restart the services on the vCenter Server / PSC where you are executing the command.
  • Repeat this process for any remaining Platform Services Controllers in the environment
  1. Decommission any Platform Services Controller VIPs from the vCenters using the same command used to decommission the Platform Services Controllers.
cmsso-util unregister --node-pnid PSC_VIP_NAME --username administrator@your_domain_name --passwd 'vCenter_Single_Sign_On_password'
  1. Where, PSC_VIP_NAME is the FQDN or IP address of the Load Balancer that you want to decommission. Please enter vCenter_Single_Sign_On_password in quotes.
  2. Note: Decomissioning the PSC VIP will end with an expected error as the VIP does not contain any PSC services itself: 
"Stdout = vdcleavefd offline for server"
 
  1. Delete the Platform Services Controller virtual machines that you no longer need from the vSphere inventory.
  2. As a final step, complete the ring topology by manually creating a replication agreement between the first and last vCenter that was upgraded.
  • Log in to an SSH session of the first vCenter Server you upgraded as root 
  • Run the shell command to start the Bash shell and log in
  • Run the vdcrepadmin createagreement command to create a new replication agreement.
/usr/lib/vmware-vmdir/bin/vdcrepadmin -f createagreement -2 -h <FIRST_UPGRADED_VC> -H <LAST_UPGRADED_VC> -u administrator
 

Powered by Wolken Software