We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Security Gateway

Centralized Linked Management of the Barracuda Web Security Gateway

  • Last updated on

This is an advanced configuration of the Linked Management feature. Barracuda recommends updating the firmware on all systems to the same version and using the same models across the cluster. If you want to use different models, or have questions about this configuration, contact Barracuda Technical Support.

Using the Linked Management feature you can cluster, or link two or more Barracuda Web Security Gateways together to provide synchronized configuration and policy settings across all systems. This article addresses the use case of choosing to designate one system in the cluster as the 'controller' if you only want to make configuration / policy changes to one system. These changes then automatically propagate to the others in the cluster.

For example, you have three Barracuda Web Security Gateways and you want to synchronize configuration and policies across all three systems. In this example, system B2 is the ‘controller’ and systems B1 and  B3 take their configuration and policies from B2. This configuration is illustrated in Figure 1. Steps to configure follow.

Figure 1. System B2 is the 'controller', and systems B1 and B3 pull their configuration from system B2

WSGClusterMS_2019.png

Step 1. Prepare each system for linking.

On each Barracuda Web Security Gateway, go to the ADVANCED > Linked Management page and create a Cluster Shared Secret. This is a password that is shared by all Barracuda Web Security Gateways in the cluster. Enter the same password on each system in the Cluster Shared Secret field in the Cluster Settings section of the page.

Step 2. Configure Centralized Management With Linked Systems
  1. On system B2, go to the ADVANCED > Linked Management page. Set the MODE to Active.
  2. On system B1, go to the ADVANCED > Linked Management page.
    1. In the table, set mode for THIS machine, B1, to Standby.
    2. In the Add System field, enter the IP address (or resolvable machine name) of B2.
    3. Click Join Cluster. The configuration of system B2 will overwrite the configuration on this system (B1).
  3. On system B3, go to the ADVANCED > Linked Management page.
    1. In the table, set mode for THIS machine, B3, to Standby.
    2. In the Add System field, enter the IP address (or resolvable machine name) of B2.
    3. Click Join Cluster. The configuration on system B2 will overwrite the configuration on this system (B3).
  4. On system B2, go to the ADVANCED > Linked Management page.
    1. Make sure the MODE for B1 and B3 are both set to Standby. This tells system B2 that systems B1 and B3 will each pull their configuration from THIS system (B2).
    2. On each of systems B1 and B3, go back to the ADVANCED > Linked Management page, and set the MODE for those systems to Standby.

Figure 2. Clustered Systems table on ADVANCED > Linked Management page on system B2.

Cluster_B1_B3_System_status.png

Important Notes About Centralized Management

  • Any change you make on B2 will propagate to systems B1 and B3.
  • Any change you make on any other system in the cluster (B1 and B3) will be unique to that system and will NOT propagate to the other systems.
  • The Mode on each system does not matter to that system; it only matters to other systems in the cluster.
  • Systems on Standby PULL their configuration from units set to Active.

  • You can cluster mixed models, but keep in mind that some versions of lower models (410, for example) do not include the additional features available on higher models.
Last updated on