Configure the replication traffic between the protected and the recovery region by adding static routes on both vSphere Replication appliances in each region.

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 administrator@vsphere.local
    Password vsphere_admin_password
  2. In the Hosts and clusters inventory, expand the sfo01m01vc01.sfo01.rainpole.local tree and expand the sfo01-m01dc data center.
  3. Expand the sfo01-m01-mgmt01 cluster.
  4. On the vSphere Replication appliances, add static network routes to the host in the other region.
    1. Right-click sfo01m01vrms01 and select Open Console.
    2. To switch to command prompt shell, press ALT+F2.
    3. Log in by using the following credentials.
      Setting Value
      User name root
      Password vr_root_password
    4. Edit the /etc/systemd/network/10-eth2.network file. 
      vi /etc/systemd/network/10-eth2.network
    5. To create a route to from the recovery to the protected region, add the following text at the end of the file.
      File Value for sfo01m01vrms01 Value for lax01m01vrms01
      /etc/systemd/network/10-eth2.network 
      [Route] 
Gateway=172.16.26.253
Destination=172.17.16.0/24
      		 
      [Route] 
Gateway=172.17.16.253
Destination=172.16.26.0/24
    6. To restart the network service, run the command. 
      systemctl restart systemd-networkd.service
    7. To verify the routing table, run the route -n command.
      Command Output for sfo01m01vrms01 Output for lax01m01vrms01
      route -n 
      default 172.16.11.253 -- 172.17.16.0/24 172.16.26.253 dev eth2
      		 
      default 172.17.11.253 -- 172.16.26.0/24 172.17.16.253 dev eth1
  5. Repeat this procedure for the lax01m01vrms01 vSphere Replication appliance in Region B.