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

Configuring Platform Service Controller HA in vSphere 6.7 (53661)

Last Updated: 7/26/2019Categories: How toTotal Views: 24490Language:
Chinese (Simplified)JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Purpose

This article provides information on configuring Platform Service Controller High Availability in a vSphere 6.7 (PSC HA 6.7) environment that has been installed or upgraded from vSphere 6.0 or 6.5.

Resolution

Notes:

Before performing these steps confirm that you have taken a backup of the environment.

Ensure that replication between the PSCs is working properly prior to upgrading.

Review the article Important information before upgrading to vSphere 6.7.

Available supported Installation, Upgrade and, Migration paths:

New vSphere 6.7 installation with SSL pass through

Upgrading from vSphere 6.0 to 6.7 with SSL pass through

Upgrading from vSphere 6.0 to 6.7 with SSL termination

Upgrading from vSphere 6.5 to 6.7 with SSL pass through

Upgrading from vSphere 6.5 to 6.7 with SSL termination

Migrating a 6.0 vCenter Server to vCenter Server Appliance 6.7 with SSL Pass through

Migrating a 6.0 vCenter Server to vCenter Server Appliance 6.7 with SSL termination

Migrating a 6.5 vCenter Server to vCenter Server Appliance 6.7 with SSL Pass through

Migrating a 6.5 vCenter Server to vCenter Server Appliance 6.7 with SSL termination

New environment installation

Configuring vSphere 6.7 Platform Service Controllers for High availability for a new vSphere 6.5 installation with SSL pass through

Install the primary external Platform Services Controller node.

Deploy the secondary SSO node as a replication partner to the primary Platform Service Controller node.

Create a new machine SSL certificate. For more information, see:

Configuring certificates for PSC for High Availability in vSphere 6.5 and 6.7

Configuring certificates for Windows Platform Services Controller for High Availability in vSphere 6.5 and 6.7

Configure the load balancer. For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Run the configuration scripts on the Platform Service Controllers. For more information, see

Configuring Windows PSC for High Availability in vSphere 6.5/6.7

Configuring PSC Appliance for High Availability in vSphere 6.5/6.7

Verify the machine Certificate:

Windows vCenter Server - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

vCenter Server Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate.

Platform Services Controller - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

Platform Services Controller Appliance - openssl s_client -connect SSOLB.vmware.local:443

Install the vCenter Server using the Load Balancer virtual IP for the Platform Service Controller when prompted.

Upgraded environment

Configuring Platform Services Controller High Availability upgrading from vSphere 6.0 to 6.7 with SSL pass through

Except the node that is to be upgraded, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control –-stop --all

Upgrade the Platform Services Controller 6.0 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been upgraded and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Create a new machine SSL certificate. For more information, see:

Configuring certificates for PSC for High Availability in vSphere 6.5 and 6.7

Configuring certificates for Windows Platform Services Controller for High Availability in vSphere 6.5 and 6.7

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability in vSphere 6.5/6.7

Configuring PSC Appliance for High Availability in vSphere 6.5/6.7

Verify the Load Balancer configuration/ For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify vCenter functionality is still available.

Upgrade all vCenter Server nodes.

Verify the machine Certificate:

Platform Services Controller - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

Platform Services Controller Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Windows vCenter Server - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

vCenter Server Appliance - openssl s_client -connect SSOLB.vmware.local:443

Configuring Platform Services Controller High Availability upgrading from vSphere 6.0 to 6.7 with SSL termination

Except the node that is to be upgraded, stop the services on all other PSC nodes. Use this command to stop the services.

Widows server "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

Linux appliance service-control --stop --all

Upgrade the Platform Services Controller 6.0 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been upgraded and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability SSL termination in vSphere 6.7

Configuring PSC Appliance for High Availability SSL termination in vSphere 6.7

Verify the Load Balancer configuration/ For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify vCenter functionality is still available.

Upgrade vCenter Server nodes.

Configuring Platform Services Controller High Availability upgrading from vSphere 6.5 to 6.7 with SSL pass through

Except the node that is to be upgraded, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Upgrade the Platform Services Controller 6.5 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been upgraded and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability in vSphere 6.5/6.7

Configuring PSC Appliance for High Availability in vSphere 6.5/6.7

Verify the Load Balancer configuration/ For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify vCenter functionality is still available.

Upgrade vCenter Server nodes.

Verify the machine Certificate:

Platform Services Controller - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

Platform Services Controller Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Windows vCenter Server - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

vCenter Server Appliance - openssl s_client -connect SSOLB.vmware.local:443

Configuring Platform Services Controller High Availability upgrading from vSphere 6.5 to 6.7 with SSL termination

Except the node that is to be upgraded, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Upgrade the Platform Services Controller 6.5 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been upgraded and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability SSL termination in vSphere 6.7

Configuring PSC Appliance for High Availability SSL termination in vSphere 6.7

Verify the Load Balancer configuration/ For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify vCenter functionality is still available.

Upgrade all vCenter Server nodes.

Migrated Environment

Configuring Platform Services Controller High Availability migrating a 6.0 vCenter Server to vCenter Server Appliance 6.7 with SSL Pass through

Except the node that is to be migrated, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Migrate the Platform Services Controller 6.0 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been migrated and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Create a new machine SSL certificate. For more information, see:

Configuring certificates for PSC for High Availability in vSphere 6.5 and 6.7

Configuring certificates for Windows Platform Services Controller for High Availability in vSphere 6.5 and 6.7

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability in vSphere 6.5/6.7

Configuring PSC Appliance for High Availability in vSphere 6.5/6.7

Verify the Load Balancer configuration. For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify if vCenter functionality is still available.

Migrate all vCenter Server nodes.

Verify the machine Certificate:

Windows vCenter Server - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

vCenter Server Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Platform Services Controller - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

Platform Services Controller Appliance - openssl s_client -connect SSOLB.vmware.local:443

Verify the machine Certificate:

Platform Services Controller - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

Platform Services Controller Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Windows vCenter Server - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

vCenter Server Appliance - openssl s_client -connect SSOLB.vmware.local:443

Configuring Platform Services Controller High Availability migrating a 6.0 vCenter Server to vCenter Server Appliance 6.7 with SSL termination

Except the node that is to be migraed, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Migrate the Platform Services Controller 6.0 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been migrated and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability SSL termination in vSphere 6.7

Configuring PSC Appliance for High Availability SSL termination in vSphere 6.7

Verify the Load Balancer configuration. For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify if vCenter functionality is still available.

Migrate all vCenter Server nodes.

Configuring Platform Services Controller High Availability migrating a 6.5 vCenter Server to vCenter Server Appliance 6.7 with SSL Pass through

Except the node that is to be migrated, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Migrate the Platform Services Controller 6.5 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been migrated and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability in vSphere 6.5/6.7

Configuring PSC Appliance for High Availability in vSphere 6.5/6.7

Verify the Load Balancer configuration. For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify if vCenter functionality is still available.

Migrate all vCenter Server nodes.

Verify the machine Certificate:

Windows vCenter Server - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

vCenter Server Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Platform Services Controller - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

Platform Services Controller Appliance - openssl s_client -connect SSOLB.vmware.local:443

Verify the machine Certificate:

Platform Services Controller - "%VMWARE_CIS_HOME%"/vmafdd/vecs-cli.exe entry list --store MACHINE_SSL_CERT --text

Platform Services Controller Appliance - /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text

Verify the Load Balancer is presenting the same certificate:

Windows vCenter Server - "%VMWARE_OPENSSL_BIN%"openssl s_client -connect SSOLB.vmware.local:443

vCenter Server Appliance - openssl s_client -connect SSOLB.vmware.local:443

Configuring Platform Services Controller High Availability migrating a 6.5 vCenter Server to vCenter Server Appliance 6.7 with SSL termination

Except the node that is to be migrated, stop the services on all other PSC nodes. Use this command to stop the services.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --stop –all

vCenter Server Appliance - service-control --stop --all

Migrate the Platform Services Controller 6.5 node to 6.7.

Start the services on all other PSC nodes in the environment and allow them to replicate.
Note: It is very important to allow the PSCs to replicate with the upgraded node before proceeding. The steps to check replication status can be found in Determining replication agreements and status with the Platform Services Controller 6.x

Choose the next node to be upgraded and stop the services of all the other nodes, including the node that has been upgraded previously.

Repeat this process until all the PSC nodes have been migrated and start the services on all the PSC nodes.

Windows vCenter Server - "%VMWARE_CIS_HOME%"\bin\service-control --start –all

vCenter Server Appliance - service-control –start --all

Run the configuration scripts on the Platform Service Controllers. For more information, see:

Configuring Windows PSC for High Availability SSL termination in vSphere 6.7

Configuring PSC Appliance for High Availability SSL termination in vSphere 6.7

Verify the Load Balancer configuration. For more information, see:

Configuring Netscaler Load Balancer to provide the PSC 6.5/6.7 High Availability

Configuring F5 BIG-IP Load Balancer for use with vSphere Platform Services Controller (PSC) 6.5/6.7

Verify if vCenter functionality is still available.

Migrate all vCenter Server nodes.

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)

KB
•
vCenter Server 6.0 から 6.5 への移行時に「vSphere ESX Agent Manager のエクスポート中に内部エラーが発生しました (Internal error occurs during Export of vSphere ESX Agent Manager)」エラーが発生する (2147898)

Results 1-2 of 2

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 6.7.x

Take Our Survey

Support Assistant