Table of Contents
Advertisement
6.
Establish replication from Seattle1 to Lansing1 using the following command:
replication --add --name < container-name> --role <source | target> --peer <IP address> --
replication_traffic <ip address | hostname> --encryption <none | aes128 | aes256>
7.
On Lansing2 add replication to the 10GB bond using the following command:
system –replication_traffic --add --interface <bond(0-N) | eth(0-N) | lo#>
8.
Create a route from Lansing2 to Lansing1 using the following command:
network --route --add --network <destination_network> --gateway <gateway addresses> --interface
<bond(0-N) | eth(0-N) | lo#>
9.
Create a route from Lansing1 to Lansing2 using the following commands:
network --route --add --network <destination_network> --gateway <gateway addresses> --interface
<bond(0-N) | eth(0-N) | lo#>
10. Establish replication from Lansing1 to Lansing2 using the following command:
replication --add --name < container-name> --role <source | target> --peer <IP address> --
replication_traffic <ip address | hostname> --encryption <none | aes128 | aes256>
36
DR4100 Best Practice Guide | April 2014
administrator@Seattle1 > replication --add --name backup --role source --peer <IP of 1G
Bond of Lansing1> --replication_traffic <ip address of local 1G interface to be used for
replication| hostname> --encryption aes256
administrator@Lansing2 > system --replication_traffic --add --interface bond0
administrator@Lansing2 > network –route --add --network <Lansing1's 10G network> --
gateway <gateway addresses> --interface bond0
administrator@Lansing1 > network --route --add --network <Lansing2's 10G network> --
gateway <gateway addresses> --<IP of 10Gbond of Lansing1>
administrator@Lansing1 > replication --update --name <source-container-name> --role
source --peer <IP of 10G Bond of Lansing2> --replication_traffic <IP of 10G bond of
Lansing1>
Example
Example
Example
Example
Example
Advertisement
Table of Contents
