This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
userdoc:tt_high_availability [2018/07/29 20:14] abelbeck [Example Basic Configuration] |
userdoc:tt_high_availability [2018/07/29 20:16] abelbeck [Example Basic Configuration] |
and the backup box should not display ''10.10.50.244'' . Note that if something blocked VRRP packets between the boxes then both boxes would think they are the master and both would have ''10.10.50.244'' assigned, which is not good. Only one occurrence of ''10.10.50.244'' should exist at a time. | and the backup box should not display ''10.10.50.244'' . Note that if something blocked VRRP packets between the boxes then both boxes would think they are the master and both would have ''10.10.50.244'' assigned, which is not good. Only one occurrence of ''10.10.50.244'' should exist at a time. |
| |
Now test, disconnect the ''eth0'' cable from the master box ... watch the backup box acquire the ''10.10.50.244'' address, then reattach the network cable and watch ''10.10.50.244'' move back to the master. For added fun, perform a ''ping 10.10.50.244'' from a local device and watch it (almost) not miss a beat. | Now test, disconnect the ''eth0'' cable from the master box ... watch the backup box acquire the ''10.10.50.244'' address, then reattach the network cable and watch ''10.10.50.244'' move back to the master. For added fun, perform a ''ping 10.10.50.244'' from a local device and watch it (almost) not miss a beat during this test. |
| |
More testing, edit the ''/mnt/kd/keepalived/keepalived.conf'' file on the backup and change ''priority 99'' to ''priority 101'', restart ''keepalived'' by: | More testing, edit the ''/mnt/kd/keepalived/keepalived.conf'' file on the backup and change ''priority 99'' to ''priority 101'', restart ''keepalived'' by: |