High Availability Operation
Use High Availability (HA) to cluster two Barracuda Load Balancers as an active-passive pair. Only one system actively processes traffic at any one time, but the two systems continuously share almost all configuration and monitor each other's health.
The active system in a clustered pair handles all of the traffic until one of the following conditions is encountered:
- Passive system detects that the active system is no longer responsive on the WAN;
- Active system detects that its LAN connection has been lost;
- Administrator manually forces failover using the web interface;
- Active system encounters a hardware failure (including a power failure) or a failure in one of its critical software modules.
If any of these conditions is encountered, the passive Barracuda Load Balancer then:
- becomes active;
- assumes all of the Virtual IP addresses of the services and the LAN IP address of the other Barracuda Load Balancer;
- performs the load balancing.
Clustered Barracuda Load Balancers negotiate which is the active one according to the Virtual Router Redundancy Protocol (VRRP) specification. The two systems must be configured with the same cluster shared secret and group ID. If other systems on the same subnet are also using VRRP, the cluster group ID must be unique.
The passive Barracuda Load Balancer does not do any load-balancing or monitoring of Services or Real Servers. For example, in the web interface of the passive system, all of the Services and Real Servers on the BASIC > Services have red health indicators.
Before joining two systems, each Barracuda Load Balancer must meet the following requirements:
- Barracuda Load Balancer 340 or higher; note that both Barracuda Load Balancers must be the same model;
- Activated and on the same version of firmware;
- Able to access all Real Servers;
- On the same physical network segment;
- Able to reach the other Barracuda Load Balancer on the WAN interface.
In addition, the active system should be fully configured; see Services and Configuring the Load Balancer Network for a complete list of service and network configuration tasks. For the passive system, follow the instructions in the Configuring the Passive System section. Once the systems are clustered, you must manually reboot the passive system.
To speed up recognition of a newly active Barracuda Load Balancer, disable spanning tree protocol on the ports of the switch where the WAN ports of the two Barracuda Load Balancers are connected. If it is a Cisco switch, enable Spanning Tree PortFast on the ports connected to the WAN ports of the Barracuda Load Balancers.
When the Barracuda Load Balancer becomes active it sends out a gratuitous address resolution protocol (ARP). It continues to send a gratuitous ARP every minute; the passive system does not issue any ARPs.
- How to Configure the Barracuda Load Balancers for High Availability
- How to Manage of a High Availability Environment with Two Barracuda Load Balancers
- How to Remove a Barracuda Load Balancer from a High Availability Environment