Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Upgrading Load Balanced PSCs 6.x to vCenter Server 7.0 (78446)

Last Updated: 2/27/2024Categories: How toTotal Views: 8139Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

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.

Solution

Single vCenter Server Environments

Create powered-off snapshots or backups the vCenter Server and Platform Service Controllers.

Upgrade or migrate the vCenter Server to 7.0.

Re-point any external solutions that originally used the Platform Services Controller VIP address as a direct endpoint. (i.e. vSphere NSX)

Power off the 6.7 Platform Services Controllers.

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

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'

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.

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"

Delete the Platform Services Controller virtual machines that you no longer need from the vSphere inventory.

Multiple vCenter Server Environments

Create powered-off snapshots or backups the vCenter Servers and Platform Service Controllers.

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.

Re-point any external solutions that originally used the Platform Services Controllers or the VIP addresses as a direct endpoint. (i.e. vSphere NSX)

Power off the 6.7 Platform Services Controllers.

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

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'

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.

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"

Delete the Platform Services Controller virtual machines that you no longer need from the vSphere inventory.

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant