When the OVA deployment finishes, you are redirected to stage 2 of the upgrade process to transfer the data from the old appliance and start the services of the newly deployed Platform Services Controller appliance 6.7.

Procedure

  1. Review the introduction to stage 2 of the upgrade process and click Next.
  2. Wait for the pre-upgrade check to finish and read the pre-upgrade check result if any.
    • If the pre-upgrade check result contains error messages, read the messages and click Logs to export and download a support bundle for troubleshooting.

      You cannot proceed with the upgrade until you have corrected the errors.

      Important: If you have provided incorrect vCenter Single Sign-On user name and password of the source appliance during stage 1, the pre-upgrade check fails with an authentication error.
    • If the pre-upgrade check result contains warning messages, read the messages and click Close.

      After you have verified that your system meets the requirements from the warning message, you can proceed with the upgrade.

  3. Review the VMware Customer Experience Improvement Program (CEIP) page and choose if you want to join the program.
    For information about the CEIP, see the Configuring Customer Experience Improvement Program section in vCenter Server and Host Management.
  4. On the Ready to complete page, review the upgrade settings, accept the backup acknowledgment, and click Finish.
  5. Read the shutdown warning message and click OK.
  6. Wait for the data transfer and setup process to finish and click OK to go to the Platform Services Controller Getting Started page.

Results

The Platform Services Controller appliance is upgraded. The old Platform Services Controller appliance is powered off and the new appliance starts.

What to do next

Repeat this procedure to upgrade the secondary Platform Services Controller HA node, and any other HA nodes in your environment.
  1. Re-enable traffic to the primary Platform Services Controller node.
  2. From the load balancer, disable monitoring and node membership on the secondary Platform Services Controller node, and redirect all connecting clients to the primary Platform Services Controller node.
  3. Upgrade the secondary Platform Services Controller node.
  4. After you finish the upgrade, re-enable traffic to the secondary Platform Services Controller node, and re-enable health monitoring on the load balancer.
  5. After you have upgraded all the Platform Services Controller HA nodes, start the services on all the nodes.
  6. To configure the Platform Services Controller nodes for load balancing, run the updateSSOConfig.py and updateLsEndpoint.py scripts. See Knowledge Base article KB 2147384.
  • If the old Platform Services Controller appliance uses a non-ephemeral distributed virtual port group, to preserve the port group setting, you can manually connect the new appliance to the original non-ephemeral distributed virtual port group. For information about configuring virtual machine networking on a vSphere distributed switch, see vSphere Networking.
  • If the Platform Services Controller appliance replicates the infrastructure data with other Platform Services Controller instances, you must upgrade all Platform Services Controller instances in the vCenter Single Sign-On domain to the same version.