After you complete the upgrade of the management virtual infrastructure in Region A, you upgrade the Platform Services Controller instances in Region B. To keep the services provided by the Platform Services Controller instances running, you direct all network traffic to one instance while the other instance of the highly available pair is being upgraded.

Role Virtual Machine Name Fully Qualified Domain Name
Platform Services Controller for the management cluster lax01m01psc01 lax01m01psc01.lax01.rainpole.local
Platform Services Controller for the shared edge and compute cluster lax01w01psc01 lax01w01psc01.lax01.rainpole.local

Procedure

  1. Log in to the Management vCenter Server by using the vSphere Client.
    1. Open a Web browser and go to https://lax01m01vc01.lax01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.
      Setting Value
      User name administrator@vsphere.local
      Password vsphere_admin_password
  2. To direct all traffic to the Platform Services Controller for the Management cluster, disable the membership of the Platform Services Controller for the Shared Edge and Compute cluster in the load balancer pools.
    1. From the Home menu of the vSphere Web Client, select Networking & Security.
    2. In the Navigator, select NSX Edges.
    3. From the NSX Manager drop-down menu, select the 172.17.11.65 NSX Manager, and double-click the lax01psc01 NSX Edge device.
    4. On the Manage tab, click Load Balancer > Pools.
    5. Select the psc-https-443 load balancer pool and click the Edit button.
    6. In the Edit Pool dialog box, from the Members pane, select lax01m01psc01, and click the Edit button.
    7. In the Edit Member dialog box, from the State drop-down menu, select Disable, and click OK.
    8. In the Edit Pool dialog box, click OK.
    9. Repeat Step e to Step h for the psc-tcp-389 load balancer pool.
    10. On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-389 report status DOWN for lax01m01psc01.
  3. Rename the lax01m01psc01 virtual machine.
    1. From the Home menu of the vSphere Web Client, select Hosts and Clusters.
    2. Expand the lax01m01vc01.lax01.rainpole.local tree, double-click the lax01-m01dc data center, and expand the lax01-m01fd-mgmt folder.
    3. Right-click lax01m01psc01 and select Rename.
    4. Enter lax01m01psc01_old as the new virtual machine, and click OK.
  4. On the Windows host that has access to your data center, mount the vCenter Server Appliance installer VMware-VCSA-all-6.7.x-build_number.iso.
  5. Navigate to the \vcsa-ui-installer\win32 directory and start the installer.exe executable file.
    The vCenter Server Appliance Installer starts.
  6. On the Home page, click Upgrade.
  7. Follow the prompts and configure the following settings for the first stage of the vCenter Server Appliance Installer.
    Table 1. Upgrade - Stage 1: Deploy Platform Services Controller
    Upgrade Wizard Page Setting Value
    Introduction - -
    End user license agreement Read and accept the EULA, and click Next.
    Connect to source appliance Appliance FQDN or IP address lax01m01psc01.lax01.rainpole.local
    Appliance HTTPS port 443
    Configure the settings and click Connect to source.
    Appliance OS root password lax01m01psc01_root_password
    ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local
    HTTPS port 443
    User name administrator@vsphere.local
    Password vsphere_admin_password
    1. Configure the settings and click Next.
    2. On the Certificate Warning dialog box, click Yes.
    Appliance deployment target ESXi host or vCenter Server name lax01m01vc01.lax01.rainpole.local
    HTTPS port 443
    User name administrator@vsphere.local
    Password vsphere_admin_password
    1. Configure the settings and click Next.
    2. On the Certificate Warning dialog box, click Yes.
    Select folder Folder lax01-m01fd-mgmt
    Select compute resource Compute resource lax01-m01fd-mgmt
    Set up target appliance VM VM name lax01m01psc01
    Set root password lax01m01psc01_root_password
    Confirm root password lax01m01psc01_root_password
    Select datastore Datastore lax01-m01-vsan01
    Enable thin disk mode Selected
    Configure network settings Network lax01-m01-vds01-management
    IP version IPv4
    IP assignment Static
    Temporary IP address 172.17.11.70
    Subnet mask or prefix length 24
    Default gateway 172.17.11.1
    DNS servers 172.17.11.5,172.17.11.4
    Configure the settings and click Connect to source.
    Ready to complete stage 1 Verify the configuration and click Finish.
    Wait until the first stage of the vCenter Server Appliance Installer completes. The deployment process might take several minutes.
  8. On the Upgrade - Stage 1: Deploy Platform Services Controller page, click Continue.
  9. Follow the prompts and configure the following settings for the second stage of the vCenter Server Appliance Installer.
    Table 2. Upgrade - Stage 2: Platform Services Controller Appliance
    Upgrade Wizard Page Setting Value
    Introduction - -
    Connect to source PSC Single Sign-On user name administrator@vpshere.local
    Single Sign-On password vsphere_admin_password
    Source PSC appliance (OS) root password lax01m01psc01_root_password
    ESXi host or vCenter Server user name administrator@vpshere.local
    Password vsphere_admin_password
    Configure CEIP Join the VMware's Customer Experience Improvement Program (CEIP) Selected
    Ready to complete I have backed up the source Platform Services Controller and all the required data from the database. Selected
    1. Review the new appliance configuration and click Finish.
    2. On the Shutdown Warning dialog box, click Ok.
    Wait until the second stage of the vCenter Server Appliance Installer completes. The process might take several minutes.
  10. To restore traffic to the Platform Services Controller for the Management cluster, enable membership of the Platform Services Controller instance in the load balancer pools.
    1. From the Home menu of the vSphere Web Client, select Networking & Security.
    2. In the Navigator, select NSX Edges.
    3. From the NSX Manager drop-down menu, select the 172.17.11.65 NSX Manager, and double-click the lax01psc01 NSX Edge device.
    4. On the Manage tab, click Load Balancer > Pools.
    5. Select the psc-https-443 load balancer pool and click the Edit button.
    6. In the Edit Pool dialog box, from the Members pane, select lax01m01psc01, and click the Edit button.
    7. In the Edit Member dialog box, from the State drop-down menu, select Enable, and click OK.
    8. In the Edit Pool dialog box, click OK.
    9. Repeat Step e to Step h for the psc-tcp-389 load balancer pool.
    10. On the Pools page, click Show Pools Statistics and verify that both psc-https-443 and psc-tcp-389 report status UP for lax01m01psc01.
  11. Repeat this procedure for the lax01w01psc01.lax01.rainpole.local Platform Services Controller instance in Region B.