When Region B is back online after a failback for disaster recovery to Region A, to avoid conflicts in the management and control planes of NSX, modify the roles of the NSX Managers and delete certain NSX components in Region B.

When the NSX instance for the management cluster in Region B is back online, the NSX Manager instance in Region B still has the primary role. The legacy universal NSX Controller cluster and UDLR control VM in Region B are duplicating the functions of the NSX components that you deployed in Region A during the failback for disaster recovery.

Procedure

  1. In a Web browser, log in to vCenter Server by using the vSphere Client.
    Settings Value
    URL https://lax01m01vc01.lax01.rainpole.local/ui
    User name administrator@vsphere.local
    Password vsphere_admin_password
  2. In the Networking and security inventory, click Installation and upgrade.
  3. On the Management tab, click the NSX Managers tab.

    Both NSX Manager instances 172.16.11.65 and 172.17.11.65 are assigned the primary role.

  4. Remove the NSX Manager instance in Region A as secondary to the NSX Manager instance in Region B.
    1. Select the 172.17.11.65 instance, and from the Actions drop-down menu, select Remove secondary Manager.
    2. Select the Perform operation even if NSX manager is inaccessible check box and click Remove.
  5. Demote the NSX Manager instance in Region B to the transit role.
    1. Select the 172.17.11.65 instance, from the Actions drop-down menu, select Remove primary role.
    2. In the confirmation dialog box, click Yes.
  6. Delete the NSX Controller nodes in Region B.
    1. On the Management tab, click the NSX Controller nodes tab.
    2. From the NSX Manager drop-down menu, select 172.17.11.65.
    3. Select the lax01m01nsxc01 node and click Delete.
    4. On the confirmation dialog box, click Delete.
    5. Delete the remaining lax01m01nsxc02 and lax01m01nsxc03 NSX Controller nodes.
    6. When you delete the last controller, select the Proceed to force delete option .
  7. Delete the UDLR node in Region B.
    1. In the Networking and security inventory, click NSX Edges.
    2. From the NSX Manager drop-down menu, select 172.17.11.65
    3. Select sfo01m01udlr01 and click Delete.
    4. In the Delete NSX Edge confirmation dialog box, click Delete.
  8. Assign the NSX Manager instance for the management cluster in Region B as secondary to the NSX Manager instance in Region A.
    1. In the Networking and security inventory, click Installation and upgrade.
    2. On the Management tab, click the NSX Managers tab.
    3. Select the primary 172.16.11.65 instance, and from the Actions drop-down menu, select Add secondary Manager.
    4. In the New secondary Manager dialog box, configure the settings and click Add.
      Setting Value
      NSX Manager 172.17.11.65
      User Name admin
      Password mgmtnsx_admin_password
      Confirm Password mgmtnsx_admin_password
    5. In the Thumbprint confirmation dialog box, click Accept.