After you replace the certificates of all Platform Services Controller instances and all vCenter Server instances, replace the certificates for the NSX Manager instances.

About this task

You replace certificates twice, once for each NSX Manager. You start by replacing certificates on NSX Manager for the mgmt01nsxm51.lax01.rainpole.local management cluster. 

Table 1. Certificate-Related Files on the NSX Manager Instances in Region B

NSX Manager FQDN

Certificate File Name

Replacement Time

mgmt01nsxm51.lax01.rainpole.local

  • mgmt01nsxm51.lax01.chain.cer from manual generation

  • mgmt01nsxm51.lax01.4.p12 from the CertGenVVD tool

After you replace the certificate on the Management vCenter Server

comp01nsxm51.lax01.rainpole.local

  • comp01nsxm51.lax01.cer.chain.cer from manual generation

  • comp01nsxm51.lax01.4.p12 from the CertGenVVD tool

After you replace the certificate on the Compute vCenter Server

Procedure

  1. On the Windows host that has access to the data center, log in to the NSX Manager Web interface.
    1. Open a Web browser and go to following URL. 

      NSX Manager

      URL

      NSX Manager for the management cluster

      https://mgmt01nsxm51.lax01.rainpole.local

      NSX Manager for the shared compute and edge cluster

      https://comp01nsxm51.lax01.rainpole.local

    2. Log in using the following credentials.

      Setting

      Value

      User name

       admin

      Password

       nsx_manager_admin_password

  2. On the Manage tab, click SSL Certificates, click Import and provide the certificate chain file.
  3. Restart the NSX Manager to propagate the CA-signed certificate.
    1. In the right corner of the NSX Manager page, click the Settings icon. 
    2. From the drop-down menu, select Reboot Appliance.
  4. Re-register the NSX Manager to the Management vCenter Server.
    1. Open a Web browser and go to the NSX Manager Web interface.

      NSX Manager

      URL

      NSX Manager for the management cluster

      https://mgmt01nsxm51.lax01.rainpole.local

      NSX Manager for the shared compute and edge cluster

      https://comp01nsxm51.lax01.rainpole.local

    2. Log in using the following credentials.

      Setting

      Value

      User name

      admin

      Password

      nsx_mngr_admin_password

    3. Click Manage vCenter Registration.
    4. Under Lookup Service, click the Edit button.
    5. In the Lookup Service dialog box, enter the following settings, and click OK.

      Setting

      Value

      Lookup Service IP

      lax01psc51.lax01.rainpole.local

      Lookup Service Port

      443

      SSO Administrator User Name

      administrator@vsphere.local

      Password

      vsphere_admin_password

    6. In the Trust Certificate? dialog box, click Yes.
    7. Under vCenter Server, click the Edit button.
    8. In the vCenter Server dialog box, enter the following settings, and click OK.

      Setting

      Value for the NSX Manager for the Management Cluster

      Value for the NSX Manager for the Shared Edge and Compute Cluster

      vCenter Server

      mgmt01vc51.lax01.rainpole.local

      comp01vc51.lax01.rainpole.local

      vCenter User Name

      svc-nsxmanager@rainpole.local

      Password

      svc-nsxmanager_password

    9. In the Trust Certificate? dialog box, click Yes.
    10. Wait until the Status indicators for the Lookup Service and vCenter Server change to Connected.
  5. Repeat the steps for the NSX Manager for the shared compute and edge cluster.
  6. Reconnect to the NSX Manager instances in Region A.
    1. Open a Web browser and go to https://mgmt01vc51.lax01.rainpole.local
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

    3. From the vSphere Web Client Home menu, select Networking & Security.
    4. Click Installation in the Navigator.
    5. On the Management tab , select the 172.17.11.65 instance from the NSX Manager menu.
    6. If primary and secondary nodes are not syncing correctly
    7. Select Actions > Disconnect from Primary NSX Manager.
    8. On the Management tab , select the 172.16.11.65 instance from the NSX Manager drop-down menu.
    9. Select Actions > Add Secondary NSX Manager
    10. In the Add Secondary NSX Manager dialog box, enter the following settings and click OK.

      Setting

      Value

      NSX Manager

      172.17.11.65

      Username

      admin

      Password

      mgmtnsx_admin_password

      Confirm Password

      mgmtnsx_admin_password

    11. In the Trust Certificate confirmation dialog box, click Yes.
    12. Repeat Step e to Step k for the NSX Manager instances for the shared edge and compute cluster.

      Reconnect the 172.17.11.66 secondary NSX Manager for the shared edge and compute cluster in Region B to the primary NSX Manager 172.16.11.66 for the shared edge and compute cluster in Region A.

  7. Reconnect the NSX Manager instances to vRealize Operations Manager.
    1. Open a Web browser and go to https://vrops-cluster-01.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      admin

      Password

      vrops_admin_password

    3. In the left pane of vRealize Operations Manager, click Administration and click Certificates.
    4. Select the row that contains CN=mgmt01nsxm51.lax01.rainpole.local and click the Delete icon.
    5. Select the row that contains CN=comp01nsxm51.lax01.rainpole.local and click the Delete icon.
    6. In the left pane of vRealize Operations Manager, click Administration and click Solutions.
    7. From the solution table on the Solutions page, select the Management Pack for NSX-vSphere solution, and click the Configure icon at the top.
    8. In the Manage Solutions dialog box, from the Adapter Type table at the top, select NSX-vSphere Adapter.
    9. Click the mgmt01nsxm51-lax01 adapter instance, click Test Connection, accept the new certificate and click Save settings.
    10. Click comp01nsxm51-lax01 adapter instance, click Test Connection, accept the new certificate and click Save settings.