36DR4100 Best Practice Guide | April 20146.Establish replication from Seattle1 to Lansing1 using the following command:replication--add--name < container-name>--role<source| target>--peer address>--replication_traffic --encryption 7.On Lansing2add replication to the 10GB bond using the following command:system–replication_traffic--add--interface -N) | eth(0-N) | lo#>8.Create a route from Lansing2 to Lansing1 using the following command:network--route--add--network <destination_network>--gateway --interface-N) | eth(0-N) | lo#>9.Create aroute from Lansing1 to Lansing2 using the following commands:network--route--add--network --gateway --interface-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 address>--replication_traffic --encryption Exampleadministrator@Seattle1 >replication--add--name backup--role source--peer 1GBond of Lansing1>--replication_traffic replication| hostname>--encryption aes256Exampleadministrator@Lansing2>system--replication_traffic--add--interface bond0Exampleadministrator@Lansing2>network–route--add--network --gateway --interface bond0Exampleadministrator@Lansing1>network--route--add--network --gateway --Exampleadministrator@Lansing1 >replication--update--name