It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

How to Configure the Barracuda Load Balancers for High Availability

  • Last updated on

For an overview of High Availability (HA), and a list of requirements, see the article Understanding Barracuda Load Balancer High Availability.


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.

The active system should be fully configured; see Services and Step 5: How to Configure the Barracuda Load Balancer Networkfor a complete list of service and network configuration tasks.

When clustering two Barracuda Load Balancers for HA, Barracuda Networks recommends enabling PortFast on the switch ports to which the Barracuda Load Balancer’s interfaces are to be connected.

Configure the Active (Primary) System

On the Primary system, complete the following steps:

  1. Log into the Primary system as the administrator, go to the ADVANCED > BACKUP page, and back up the configuration.
  2. Go to the ADVANCED > High Availability page, and complete the following:
    • Set Enable High Availability to Yes.

    • In the Cluster Shared Secret field, enter an alphanumeric shared secret passcode; you must enter the same code on the Active and Passive systems in an HA configuration so that the systems ‘trust’ one another. Do not use special characters.

    • In the Cluster group ID field, enter a numeric shared group value. You must enter the same value on the Primary and Secondary systems in an HA configuration. The Maximum value is 255.

    • Specify how you wish a failed system to behave when recovering from a failed state:
      • Select Automatic if you wish the failed system to resume the active role upon recovery.
      • Select Manual to ensure that the currently active system does not failback to the peer automatically but continues to remain active until the administrator can determine the cause of failure of the now recovered peer.
  3. Click Save Changes.
  4. Go to the BASIC > IP Configuration page, and note the WAN IP Address; you will enter this value on the Secondary system in the ADVANCED > High Availability page in the section that follows.

Configure the Passive (Secondary) System

On the Secondary system, complete the following steps:

  1. Log into the Secondary system as the administrator, go to the ADVANCED > High Availability page, and complete the following:
    • Set Enable High Availability to Yes.
    • Enter the same shared secret you entered on the Primary system in the Cluster Shared Secret field.
    • In the Cluster group ID field, enter the same value you entered on the Primary system.
  2. Click Save Changes.
  3. Go to the BASIC > IP Configuration page, and verify the LAN IP Address and LAN Netmask fields are blank.
  4. Go to the ADVANCED > High Availability page, and enter the WAN IP address of the Primary system in the Clustered Systems field, and click Join Cluster.
  5. Allow a few minutes for the clustering process to complete.

Verify the Configuration is in Sync

Once joined in a cluster, on each system, verify the associated system displays its peer in the Clustered Systems table on the ADVANCED > High Availability page.

After verifying that the configuration is in sync, please perform some configuration changes on the active unit and check whether those changes appear on the Passive unit.

The clustering process may take up to 5 minutes to complete and no configuration changes are permitted during this period. Configuration changes may take up to a minute to sync to the peer, on clustered systems.



Related Articles

Last updated on