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
litespeed_wiki:lslb:ha [2019/02/11 20:50]
Jackson Zhang [How to Enable High Availability for Web ADC]
litespeed_wiki:lslb:ha [2019/04/12 18:08] (current)
Michael Alegre [Fixing Out of Sync Replication] Adjusted image properties.
Line 47: Line 47:
   File Cache Server Address ​ 10.10.30.96:​1447   File Cache Server Address ​ 10.10.30.96:​1447
   ​   ​
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1.png?​nolink ​|}}
  
 Click **Add** in **HA Interfaces** to add a Virtual IP: Click **Add** in **HA Interfaces** to add a Virtual IP:
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1-add-internface.png?​800 |}}  ​+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1-add-internface.png?​nolink ​|}}  ​
  
 After a VIP has been added through the GUI, the configuration will be added to the Keepalived configuration and it will look like this: After a VIP has been added through the GUI, the configuration will be added to the Keepalived configuration and it will look like this:
Line 88: Line 88:
   File Cache Server Address ​ 10.10.30.97:​1447   File Cache Server Address ​ 10.10.30.97:​1447
   ​   ​
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1.png?​800 |}}  ​+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1.png?​nolink ​|}}  ​
  
 Click **Add** in **HA Interfaces** to add a Virtual IP: Click **Add** in **HA Interfaces** to add a Virtual IP:
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha2-add-internface.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha2-add-internface.png?​nolink ​|}}
  
 After a VIP has been added through the GUI, the configuration will be added to the Keepalived configuration,​ and it will look like this: After a VIP has been added through the GUI, the configuration will be added to the Keepalived configuration,​ and it will look like this:
Line 187: Line 187:
  
 On Node 1: On Node 1:
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1-status.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha1-status.png?​nolink ​|}}
  
 On Node 2: On Node 2:
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha2-status.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-ha2-status.png?​nolink ​|}}
  
 ===== Fixing Out of Sync Replication ===== ===== Fixing Out of Sync Replication =====
Line 196: Line 196:
 Sometimes you may see replication is out of sync: Sometimes you may see replication is out of sync:
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-status-out-sync.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-status-out-sync.png?​nolink ​|}}
  
 Check the following: Check the following:
Line 209: Line 209:
 With IP failover, we recommend listening on ''​*:<​port>'',​ instead of individual ''<​IP>:<​port>''​. With IP failover, we recommend listening on ''​*:<​port>'',​ instead of individual ''<​IP>:<​port>''​.
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-listener.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-listener.png?​nolink ​|}}
  
 Virtual Host: Virtual Host:
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-vhost.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-vhost.png?​nolink ​|}}
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-vhost2.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-vhost2.png?​nolink ​|}}
  
  
 ClusterHTTP setup: ClusterHTTP setup:
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp.png?​nolink ​|}}
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-2.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-2.png?​nolink ​|}}
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-3.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-3.png?​nolink ​|}}
  
-{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-4.png?​800 |}}+{{ :​litespeed_wiki:​lslb:​adc-ha-configuration-clusterhttp-4.png?​nolink ​|}}
  
 ===== Testing VIP ===== ===== Testing VIP =====
Line 234: 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 240: 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/02/11 20:50
  • by Jackson Zhang