White Papers

DR Series Best Practice Guide
30
In order for the two DRs to replicate over the dedicated links, static routes should be provisioned
in such a way that the replication flows over those paths. This is done in the steps below.
1. Use the following command to assign a static IP to eth2 on DR1:
network --create_eth --nwif <eth0,eth2,ethN> --static --ip <ip_address> --netmask <netmask>
2. Use the following command to assign a static IP to eth3 on DR1:
network --create_eth --nwif <eth0,eth2,ethN> --static --ip <ip_address> --netmask <netmask>
3. Ensure connectivity of DR1 eth2 and eth3 by pinging the gateway using the following command:
network --ping --destination <destination_ip_address> --interface <ethN>
4. On DR2 use the following commands to release 1GB interfaces eth and eth3 from bond0:
network --delete --member <eth0,eth1,ethN>
network --restart
network --show
5. Use the following commands to assign IP address to eth2 and eth3 on DR2:
Note: The above is an example of a default route. The command above is not accessible to
customers.
Example
administrator@DR1 > network --create_eth --nwif eth2 --static --ip 172.20.20.2 --netmask
255.255.255.0
Example
administrator@DR1 > network --create_eth --nwif eth3 --static --ip 172.20.22.2 --netmask
255.255.255.0
Example
administrator@DR1 > network --ping --destination 172.20.20.1 --interface eth2
administrator@DR1 > network --ping --destination 172.20.22.1 --interface eth3
Example
administrator@DR2> network --delete --member eth2,eth3
administrator@DR2 > network --restart
administrator@DR2 > network --show