userdoc:tt_high_availability

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
userdoc:tt_high_availability [2018/07/29 20:14]
abelbeck [Example Basic Configuration]
userdoc:tt_high_availability [2018/08/02 10:51] (current)
abelbeck
Line 1: Line 1:
-====== High Availability (keepalived) ======+====== VRRP High Availability Daemon (keepalived) ======
  
 AstLinux now supports the [[http://www.keepalived.org/|keepalived]] package, High Availability (HA) is achieved via the VRRP protocol. VRRP is a fundamental brick for implementing router failover. AstLinux now supports the [[http://www.keepalived.org/|keepalived]] package, High Availability (HA) is achieved via the VRRP protocol. VRRP is a fundamental brick for implementing router failover.
Line 22: Line 22:
  
 \\ \\
- 
 ===== Example Basic Configuration ===== ===== Example Basic Configuration =====
  
Line 117: Line 116:
 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:
Line 123: Line 122:
   service keepalived restart   service keepalived restart
  
-now the backup box should be the master since it has a higher priority.  Undo the priority changes and watch it return to normal.+now the backup box should be the master since it has a higher priority.  Undo the priority change and watch it return to normal.
  
-Now you get the idea, to make this a production solution a few more details will probably need to be addressed, research the topic and build upon this basic example.+Now you get the idea, to make this a production solution a few more details will need to be addressed, research the topic and build upon this basic example.
  
 \\ \\
  • userdoc/tt_high_availability.1532913276.txt.gz
  • Last modified: 2018/07/29 20:14
  • (external edit)