After you replace the certificates on the Platform Services Controller instances in Region B, update the certificates on the vCenter Server instances, reconnect NSX Manager to the Platform Services Controller VIP address, and restore load balancing.

Procedure

  1. Restart the services on the Management vCenter Server.
    1. Open an SSH connection to lax01m01vc01.lax01.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Values

      Username

      root

      Password

      lax01m01vc01_root_password

    3. Switch from the vCenter Server Appliance command shell to the Bash shell.
      shell
    4. Restart vCenter Server services by using the following command.
      service-control --stop --all
      service-control --start --all
    5. Repeat the steps to restart the lax01w01vc01.lax01.rainpole.local vCenter Server.
  2. Reconnect the NSX Managers to the Platform Services Controller load balancer and to vCenter Server after you install the custom certificates on the nodes. See Connect NSX Manager to the Management vCenter Server After Certificate Replacement in Region B.
  3. Restore load balancer configuration.
    1. Open a Web Browser and go to https://lax01m01vc01.lax01.rainpole.local/vsphere-client.
    2. Log in using the following credentials

      Setting

      Values

      Username

      administrator@vsphere.local

      Password

      vsphere_admin_password

    3. From the vSphere Web Client Home menu, select Network & Security.
    4. In the Navigator, select NSX Edges.
    5. Select 172.17.11.65 from the NSX Manager drop-down menu.
    6. Double-click the lax01psc01 edge device to open its network settings.
    7. On the Manage tab, click the Load Balancer tab and click Pools.
    8. Select pool-1 and click Edit.
    9. Select the lax01w01psc01 member, click Edit, select Enabled from the State drop-down menu, and click OK.
    10. Repeat the steps to enable lax01w01psc01 in pool-2.