It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Campus Barracuda Campus
Barracuda WAF Control Center
Overview Documentation Training Materials

How to Replace a Barracuda WAF Control Center in a High Availability Environment

  • Last updated on
Warning

High availability (HA) is an advanced feature. Contact Barracuda Networks Technical Support  before replacing a Barracuda WAF Control Center in a cluster.

Note that both Barracuda WAF Control Centers in HA must be the same model and on the same firmware.

Scenario 1. Replace the Secondary Instance in a High Availability Environment

  1. Remove the secondary instance from the AWS Classic Load Balancer.

  2. Disjoin the secondary instance from the cluster. Perform the following steps to disjoin:
    1. On the  Secondary instance, go to the  ADVANCED > High Availability  page.
    2. Click the Delete icon available on the Clustered Systems table.

  3. Once the new instance is installed, perform the following steps:

    1. Go to the  ADVANCED > High Availability  page and configure all attributes in the exact same manner as those on the primary instance. The Cluster Shared Secret must match.

    2. In the Clustered Systems section, enter the system IP address of the primary instance and click Join Cluster.
  4. Add the new instance to the AWS Classic Load Balancer.

Scenario 2. Replace the Primary instance in a High Availability Environment

Removing the primary instance from the cluster will move all the WAFs connected to it to the secondary instance.

  1. Remove the primary instance from the AWS Classic Load Balancer.

  2. Disjoin the primary instance from the cluster. Perform the following steps to disjoin:
    1. On the primary instance, go to the ADVANCED > High Availability page.
    2. Click the Delete icon available on the Clustered Systems table.

  3. Once the new instance is installed, perform the following steps:

    1. Go to the ADVANCED > High Availability page and configure all attributes in the exact same manner as those on the peer instance. The Cluster Shared Secret must match.

    2. In the Clustered Systems section, enter the system IP address of the peer instance and click Join Cluster.
  4. Add the new instance to the AWS Classic Load Balancer.

When replacing a system in a cluster, both systems must be on the same firmware version.