When Region B is back online after a disaster recovery to Region A, you must update the routing configuration to implement the original routing setup between Region B and Region A.

When Region B is back online, on the universal distributed logical router in Region A, you must add a route to the ECMP-enabled NSX Edge nodes in Region B to provide connection to the secondary management components in Region B. Also update the routing configuration in the SDDC to direct traffic to the NSX components in Region A with priority.

Procedure

  1. In a Web browser, log in to vCenter Server by using the vSphere Client.
    Setting Value
    URL https://sfo01m01vc01.sfo01.rainpole.local/ui
    User name [email protected]
    Password vsphere_admin_password
  2. In the Networking and security inventory, click NSX Edges.
  3. Configure BGP on the universal distributed logical router in Region B.
    1. From the NSX Manager drop-down menu, select 172.16.11.65 .
    2. Click the edge link of the sfo01m01udlr01 device.
    3. Click the  Routing tab and, in the left pane, click BGP.
    4. Select the neighbor NSX Edge devices, click Edit, configure the settings, and clickSave.
      Setting lax01m01esg01 Value lax01m01esg02  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
    5. Click Publish.
    6. In the left pane, click Static routes.
    7. Select the existing static route (Network: 172.16.11.0/24) and click Edit.
    8. In the Edit static route dialog box, configure the settings and click Save.
      Setting Value
      Network 172.17.11.0/24
      Next Hop 192.168.10.50,192.168.10.51
      Admin Distance 1
    9. Click Publish.
  4. Reduce the BGP weight of the lax01m01esg01 and lax01m01esg02 NSX Edge nodes.
    1. On the NSX Edges page,  from the NSX Manager drop-down menu, select 172.17.11.65.
    2. Click the edge link of the lax01m01esg01 device.
    3. Click the Routing tab.
    4. In the left pane, click BGP, select the 192.168.10.4 neighbor, and click Edit.
    5. In the Edit BGP neighbor dialog box, change the Weight value to 10 and click Save.
    6. Click Publish.
    7. Repeat the step for the lax01m01esg02 edge.
  5. Verify that the NSX Edge nodes are successfully peering and that BGP routing has been established.
    1. Log in to the first NSX Edge device by using a Secure Shell (SSH) client.
      Setting Value
      Hostname lax01m01esg01
      User name admin
      Password edge_admin_password
    2. To display information about the BGP connections to neighbors, run the show ip bgp neighbors command.
      The BGP State displays  Established UP if you have successfully peered with UDLR.
    3. To verify that you are receiving routes using BGP, run the show ip route command.
    4. Repeat the step for the lax01m01esg02 NSX Edge node.