You must configure the relevant static routes on each ESXi host at the source site to communicate with the target site. For replications to flow in the opposite direction, you must configure reverse routes on the ESXi hosts on the target site.

You add static routes on all hosts in the management domain in Region A and Region B.

Region

Hosts

Source Gateway

Target Network

Region A

sfo01m01esx01.sfo01.rainpole.local

172.16.16.253

172.17.16.0/24

sfo01m01esx02.sfo01.rainpole.local

sfo01m01esx03.sfo01.rainpole.local

sfo01m01esx04.sfo01.rainpole.local

Region B

lax01m01esx01.lax01.rainpole.local

172.17.16.253

172.16.16.0/24

lax01m01esx02.lax01.rainpole.local

lax01m01esx03.lax01.rainpole.local

lax01m01esx03.lax01.rainpole.local

Procedure

  1. Log in to the ESXi host by using a Secure Shell (SSH) client.

    Settings

    Value

    FQDN

    sfo01m01esx01.sfo01.rainpole.local

    User name

    root

    Password

    vcenter_server_root_password

  2. To create a route to the recovery region for the hosts in Region A or to the protected region for the hosts in Region B, run the following command.
    Region Command
    Region A
    esxcli network ip route ipv4 add --gateway 172.16.16.253 --network 172.17.16.0/24
    Region B
    esxcli network ip route ipv4 add --gateway 172.17.16.253 --network 172.16.16.0/24
  3. Verify the routing table by running the command.
    esxcli network ip route ipv4 list
  4. Repeat this procedure for all management hosts in Region A and Region B.
    Important: If you add new hosts to the management domain using SDDC Manager, you must follow this procedure to configure static routes on the hosts..