White Papers

DR Series Best Practice Guide
32
9. From either DR1 or DR2 verify network connectivity using the following command:
network -- ping -- destination <ip_address> --interface<eth0,eth1,ethN>
10. Assuming that DR1 and DR2 already had replication established, stop replication and update it to
use the newly configured interfaces using the commands below.
replication --stop --name <replication_container> --role <source|target>
replication --update --name <replication_container> --peer <target_ip_address> --
replication_traffic <source_ip_address> --role source
Example
administrator@DR1 > network --route --add --network 172.20.21.2 --netmask 255.255.255.0
--gateway 172.20.21.1 --interface eth2
administrator@DR1 > network --route --add --network 172.20.23.2 --netmask 255.255.255.0
--gateway 172.20.23.1 --interface eth3
administrator@DR1 > network --show --routes
Destination Gateway Mask Interface
172.20.21.0 172.20.20.1 255.255.255.0 eth2
172.20.23.0 172.20.22.1 255.255.255.0 eth3
Example
administrator@DR1 > network --ping --destination 172.20.23.2 --interface eth3 --tries 1
Example
administrator@DR1 > replication --stop --name cv-replicated-maglib --role source
administrator@DR1 > replication --update --name cv-replicated-maglib --peer 172.20.21.2 --
replication_traffic 172.20.20.2 --role source
Note: If a replication pair does not already exist between DR1 and DR2, use the steps outlined in
scenario 1 for assigning replication to designated interfaces and to create a replication pair.