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 CloudGen Firewall

How to Set Up a High Availability Cluster

  • Last updated on

The functionality of stand-alone and managed high availability clusters are the same. However, the configuration differs. For a stand-alone HA cluster, the primary firewall downloads the licenses for both firewalls, and when the secondary firewall is joined to the HA cluster, the license for the secondary firewall is transferred over. The licenses are bound to the MAC addresses of the primary and secondary firewall. The primary firewall is also the configuration master for all configurations, except for the Network page. All configurations and session information are synced from the primary firewall to the secondary firewall. To protect against failure of network components, you can use a dedicated private link as a secondary HA connection.

Stand-Alone HA Cluster

ha_sync_02.png

Before You Begin
  • Connect the primary firewall and secondary firewall to a network switch.
Step 1. (Virtual only) Verify the Product Type

Set the product type matching your license if you are using a virtual Barracuda CloudGen Firewall. This is not necessary on hardware appliances.

  1. Go to CONFIGURATION > Configuration Tree > Box > Box Properties.
  2. Click Lock.
  3. Select the model from the Product Type list. E.g., CloudGen Firewall VF50
  4. Select the model from the Hardware Model list.
    HA_set_product_type.png
  5. Click Send Changes and Activate.
Step 2. Create the Secondary Firewall

On the primary firewall, create the configuration for the secondary HA firewall.

  1. Go to CONFIGURATION > Configuration Tree > Box.
  2. Right-click Box and select Create Secondary box.
    HA_create_secondary_box.png
  3. The Box Properties and Network nodes are replaced by new a node, each suitable for an HA configuration.
    HA_nodes_for_secondary_created.png
  4. Open the Network page.
  5. Enter the Management IP (MIP) for the secondary firewall. The MIPs of the HA pair must be in the same subnet.
    HA_enter_management_IP_for_secondary.png
  6. Click Send Changes and Activate.
Step 3. Create the PAR File for the Secondary Firewall

On the primary firewall, export the PAR file for the secondary firewall.

  1. On the primary firewall, create the PAR file:
  2. Go to CONFIGURATION > Configuration Tree > Box.
  3. From the Config Tree, right-click Box and select Create PAR file for Secondary box.
  4. Save the PAR file to your local hard disk drive.
Step 4. Import the PAR File on the Secondary Firewall

On the secondary firewall, import the boxha.par PAR file created on the primary firewall:

  1. Go to CONFIGURATION > Configuration Tree > Box.
  2. From the Config Tree, right-click Box and select Restore from PAR file.
  3. Click OK.
  4. Select the box_secondary.par file created in Step 3 and click OK.
  5. Click Activate .
Step 5. Activate the New Network Configuration for the Secondary Firewall

On the secondary firewall, activate the network configuration.

  1. Go to CONTROL > Box.
  2. In the left navigation pane, expand Network and click Activate new network configuration.
  3. Select Failsafe as the activation mode.
  4. In the left menu, expand Operating System and click Reboot Box.
Step 6. Activate the New Network Configuration for the Primary Firewall

On the primary firewall, activate the network configuration.

  1. Go to CONTROL > Box.
  2. In the left navigation pane, expand Network and click Activate new network configuration.
  3. Select Failsafe as the activation mode.
  4. In the left menu, expand Operating System and click Reboot Box.
Step 6. Install Licenses

You must install licenses on both firewalls. For instructions, see How to Activate and License a Standalone High Availability Cluster.

Next Steps

Configure a Private Uplink

To avoid the switch connecting the primary and secondary firewall from becoming the single point of failure for the HA cluster, configure a private uplink for HA sync. Connect both firewalls with a crossover cable. Each firewall receives an additional management IP address in the /30 subnet used for the private uplink. The HA sync can use the private uplink as an alternative to the normal connection between the management IPs, or it can use both links simultaneously.

For more information, see How to Configure a Private Uplink for a High Availability Cluster.

Check the Virtual Server HA Status

Check the server status on both HA firewalls to verify that the virtual servers have been correctly assigned.

  1. Go to CONTROL > Services.
    HA_in_default_state.png

When the primary firewall goes down, the secondary firewall changes its status to primary and replaces the primary firewall with all its functionalities. Immediately after the failover, the services on the primary are blocked:

HA_failover_to_secondary.png

When clicking Unlock Failover, the services on the primary will be put into standby mode:
HA_secondary_is_active.png

Last updated on