After Region B comes back online, you must perform additional configuration of the networking layer to avoid conflicts. 

About this task

You demote the NSX Manager to the secondary role, delete the universal controller cluster, disable the load balancer, and perform additional configuration on the NSX Edges.

Procedure

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

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. From the Home menu from the vSphere Web Client, click Networking & Security.
  3. In the Navigator, click Installation and click the Management tab.

    You see that both NSX Managers 172.17.11.65 and 172.16.11.65 are assigned the primary role.

  4. Force the removal of the registered secondary NSX Manager before removing the primary role.
    1. Select the 172.17.11.65 instance, and select Actions > Remove Secondary NSX Manager .
    2. Select the Perform operation even if the NSX manage is inaccessible check box and click OK.
  5. Demote the original primary site NSX Manager to the transit role.
    1. Select the 172.17.11.65 instance, click Actions > Remove Primary Role.
    2. Click Yes in the confirmation dialog box.
  6. Delete the NSX controllers in the primary site.
    1. Select the nsx-controller-mgmt-51 node and click Delete.
    2. In the Delete Controller confirmation dialog box, click Yes.
    3. Repeat step to delete the remaining two NSX Controller nodes.
    4. Select Forcefully remove the controller when you delete the last controller.
  7. Delete the UDLR01 edge in the protected site.
    1. In the Navigator, click NSX Edges.
    2. Select 172.17.11.65 from the NSX Manager drop-down menu.
    3. Select the UDLR01 and click Delete.
    4. In the Delete NSX Edge confirmation dialog box, click Yes.
  8. Assign the Region B management cluster NSX Manager the secondary role to the already promoted primary NSX Manager in Region A.
    1. In the Navigator, click Installation.
    2. On the Management tab select the primary 172.16.11.65 instance.
    3. Select Actions > Add Secondary NSX Manager.
    4. In the Add secondary NSX Manager dialog box, enter the following settings and click OK.

      Setting

      Value

      NSX Manager

      172.17.11.65

      User Name

      admin

      Password

      mgmtnsx_admin_password

      Confirm Password

      mgmtnsx_admin_password

    5. In the Trust Certificate confirmation dialog box, click Yes.
  9. Disable network connectivity for the NSX load balancer in Region B.
    1. In the Navigator, click NSX Edges.
    2. Select 172.17.11.65 from the NSX Manager drop-down menu.
    3. Double-click the LAXMGMT-LB01 device.
    4. Click the Manage tab and click the Settings tab.
    5. Click Interfaces, select the OneArmLB vnic, and click Edit.
    6. In the Edit NSX Edge Interface dialog box, select Disconnected as Connectivity Status and click OK.
  10. Configure the routing for the universal distributed logical router in Region A.
    1. In the Navigator, click NSX Edges.
    2. Select 172.16.11.65 from the NSX Manager drop-down menu.
    3. Double-click UDLR01.
    4. Click the Manage tab and click Routing.
    5. On the left, select BGP.
    6. Select the following NSX Edge devices, click Edit, configure the following settings and click OK.

      Setting

      LAXMGMT-ESG01 Value

      LAXMGMT-ESG02  Value

      IP Address

      192.168.10.50

      192.168.10.51

      Forwarding Address

      192.168.10.3

      192.168.10.3

      Protocol Address

      192.168.10.4

      192.168.10.4

      Remote AS

      65003

      65003

      Weight

      10

      10

      Keep Alive Time

      1

      1

      Hold Down Time

      3

      3

      Password

      BGP_password

      BGP_password

    7. Click Publish Changes.
    8. On the left, select Static Routes.
    9. On the Static Routes page, click the existing static route (Network: 172.16.11.0/24) and click Edit button.
    10. In the Edit Static Route dialog box, update the following values and click OK.

      Setting

      Value

      Network

      172.17.11.0/24

      Next Hop

      192.168.10.50,192.168.10.51

      MTU

      9000

      Admin Distance

      1

    11. Click Publish Changes.
  11. Reconfigure the weight value of LAXMGMT-ESG01 and LAXMGMT-ESG02 edges.
    1. In the Navigator, click NSX Edges.
    2. Select 172.17.11.65 from the NSX Manager drop-down menu.
    3. Double-click LAXMGMT-ESG01.
    4. Click the Manage tab and click Routing.
    5. On the left, select BGP, select the 192.168.10.4 neighbour and click Edit.
    6. In the Edit Neighbour dialog box, change the Weight value to 10 and click OK.
    7. Click Publish Changes.
    8. Repeat the step for the LAXMGMT-ESG02 edge.
  12. Verify that the NSX Edge devices are successfully peering, and that BGP routing has been established.
    1. Log in to the LAXMGMT-ESG01 NSX Edge device using a Secure Shell (SSH) client with the following credentials.

      Setting

      Value

      User name

      admin

      Password

      edge_admin_password

    2. Run the show ip bgp neighbors command to display information about the BGP connections to neighbors. 

      The BGP State will display Established, UP if you have successfully peered with UDLR01.

    3. Run the show ip route command to verify that you are receiving routes using BGP.
    4. Repeat the step for the LAXMGMT-ESG02 NSX Edge device.