4 server redundant solution

From Kolmisoft Wiki
Revision as of 13:31, 19 January 2009 by Mindaugas (talk | contribs) (New page: Image:4serverredundant_withlinuxha.png * Servers 1 and 2 (S1 and S2) are identical. They server as gateways with Asterisk + MOR installed. * Both of them have two network interfaces ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

4serverredundant withlinuxha.png


  • Servers 1 and 2 (S1 and S2) are identical. They server as gateways with Asterisk + MOR installed.
  • Both of them have two network interfaces - one for Main IP which is visible from outside, and one for local IP for interconnection (heartbeat monitoring)
  • LinuxHA heartbeat monitors servers, e.g.
    • When S1 fails - S2 sees that and after 10s (default) will take main IP, e.g. will start to serve calls, it is done automatically
    • When S1 is back up - S2 returns main IP to S1 and system starts to function in normal work flow (done automatically).
  • Servers 3 and 4 (S3 and S4) are identical. They server as MySQL DB.
  • Both of them have two network interfaces - one for Main DB IP which is visible for Asterisk servers S1 and S2, and one for local IP for interconnection (heartbeat monitoring)
  • LinuxHA heartbeat monitors servers, e.g.
    • When S3 fails - S4 sees that and after 10s (default) will take main IP, it is done automatically
    • When S3 is back up - S4 returns main IP to S3 and system starts to function in normal work flow (done automatically).
  • DBs on S3 and S4 are synchronized over MySQL Replication


Linux Heartbeat