In the event of a site failure, when Region B becomes unavailable, prepare the network layer in Region A for failback of management applications. Change the role of the NSX Manager in Region A to primary, redeploy the universal controller cluster, and synchronize the universal controller cluster configuration.

Procedure

  1. Log in to the Management vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Promote the NSX Manager for the management cluster in Region A to the primary role.

    You must first disconnect the NSX Manager for the management cluster in Region A from the Primary NSX Manager in Region B.

    1. From the Home menu of the vSphere Web Client, click Networking & Security.
    2. In the Navigator, click Installation and Upgrade.
    3. On the Management tab, select the 172.16.11.65 instance.
    4. Click the Actions menu and click Disconnect from Primary NSX Manager.
    5. In the Disconnect from Primary NSX Manager confirmation dialog box, click Yes.

      The NSX Manager gets the Transit role.

    6. On the Management tab, select the 172.16.11.65 instance again.
    7. Click Actions and select Assign Primary Role.
    8. In the Assign Primary Role confirmation dialog box, click Yes.
  3. Deploy the universal controller cluster in Region A.
    1. In the Navigator, click Networking & Security and click Installation.
    2. Under NSX Controller nodes, click the Add icon to deploy three NSX Controller nodes with the same configuration.
    3. In the Add Controller dialog box, enter the following settings and click OK.

      You configure a password only during the deployment of the first controller. The other controllers use the same password.

      Setting

      Value

      Name

      • sfo01m01nsxc01 for controller 1

      • sfo01m01nsxc02 for controller 2

      • sfo01m01nsxc03 for controller 3

      NSX Manager

      172.16.11.65

      Datacenter

      sfo01-m01dc

      Cluster/Resource Pool

      sfo01-m01-mgmt01

      Datastore

      sfo01-m01-vsan01

      Connected To

      sfo01-m01-vds01-management

      IP Pool

      sfo01-mgmt01-nsxc01

      Password

      mgmtnsx_controllers_password

      Confirm Password

      mgmtnsx_controllers_password

    4. After the Status of the controller node changes to Connected, deploy the remaining two NSX Controller nodes sfo01m01nsxc02 and sfo01m01nsxc03.

      Wait until the current deployment is finished, before you start the next one.

  4. Configure DRS affinity rules for the deployed NSX Controller nodes.
    1. From the Home menu of the vSphere Web Client, select Hosts and Clusters.
    2. Expand the sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc tree and click the sfo01-m01-mgmt01 cluster.
    3. Click the Configure tab, under Configuration, click VM/Host Rules, and click Add.
    4. In the sfo01-m01-mgmt01 - Create VM/Host Rule dialog box, enter the following settings and click OK.

      Setting

      Value

      Name

      anti-affinity-rule-nsxc

      Enable rule

      Selected

      Type

      Separate Virtual Machines

      Members

      • sfo01m01nsxc01

      • sfo01m01nsxc02

      • sfo01m01nsxc03

  5. Use the Update Controller State mechanism on the NSX Manager to synchronize the state of the newly deployed controllers.

    Update Controller State pushes the current VXLAN and universal distributed logical router configuration from NSX Manager to the controller cluster.

    1. From the Home menu, select Networking & Security.
    2. In the Navigator, click Installation.
    3. On the Management tab, select the 172.16.11.65 instance.
    4. Click the Actions menu and select Update Controller State.
    5. In the Update Controller State confirmation dialog box, click Yes.