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
Next revision Both sides next revision
litespeed_wiki:lslb:ha [2018/08/03 20:05]
Lisa Clarke Proofreading
litespeed_wiki:lslb:ha [2019/03/18 12:21]
Kevin Fwu
Line 2: Line 2:
 LiteSpeed Web ADC's High Availability (HA) configuration provides a failover setup for two ADC Nodes. When one node is temporarily unavailable,​ the other one will automatically detect and take over the traffic. ​ LiteSpeed Web ADC's High Availability (HA) configuration provides a failover setup for two ADC Nodes. When one node is temporarily unavailable,​ the other one will automatically detect and take over the traffic. ​
  
-LiteSpeed Web ADC HA will use Keepalived to detect the failover.+Two ADC nodes will need to be set up individually.  
 + 
 +Once they are set up, LiteSpeed Web ADC HA will use Keepalived to detect the failover.
  
 ===== Two Example Nodes ===== ===== Two Example Nodes =====
Line 232: Line 234:
 When making changes to the configuration,​ such as changing the listener from ''<​IP>:​443''​ to ''​*:​443'',​ a full stop/start is required. When making changes to the configuration,​ such as changing the listener from ''<​IP>:​443''​ to ''​*:​443'',​ a full stop/start is required.
  
-==== Inconsistent HA Configuraton Between Boxes  ====+==== Inconsistent HA Configuraton Between Boxes ====
 When you see an error similar to the following: When you see an error similar to the following:
   2018-08-03 16:​24:​20.099467 [WARN] [REPL] HA configures are inconsistent between boxes, full replicaton can't proceed   2018-08-03 16:​24:​20.099467 [WARN] [REPL] HA configures are inconsistent between boxes, full replicaton can't proceed
Line 238: Line 240:
  
 It is because the configuration is out of sync between two LS ADC instances. Replication only works if the two ADCs are serving the exact same sites. ​ You need to keep ADC configuration in sync. If it is out of sync temporarily,​ it will break the synchronization. Once the configurations are synced, ADC will restore replication synchronization. ​ It is because the configuration is out of sync between two LS ADC instances. Replication only works if the two ADCs are serving the exact same sites. ​ You need to keep ADC configuration in sync. If it is out of sync temporarily,​ it will break the synchronization. Once the configurations are synced, ADC will restore replication synchronization. ​
 +
 +==== Keepalived Indicates Multiple Masters ====
 +When the configured VIP is shown on multiple nodes, it usually indicates a Split-Brain issue with keepalived.
 +
 +Keepalived defaults to using multicast packets. Please verify that multicast packets are not filtered/​blocked by your firewall.
  
 ===== Alternative ===== ===== Alternative =====
  • Admin
  • Last modified: 2019/04/12 18:08
  • by Michael Alegre