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

8.3.2 Migration Notes

  • Last updated on

Important Note for Users Operating Firmware 7.2.5 or 7.2.6


IMPORTANT NOTE

Ensure that the partition layout of your firewall/Control Center applies to the values in the table of the paragraph "Disk Space Requirements" below.

  1. If you operate a firewall that was shipped from the factory with firmware 7.2.6, or if you have already repartitioned the hard disk and performed a fresh install of firmware 7.2.6, then the hard disk already has a partition layout that is suitable for firmware 8.x.
    In this case, you can upgrade directly to firmware 8.x without repartitioning the hard disk.
  2. If you operate a firewall with firmware version 7.2.5 or earlier, you must repartition the hard disk with the layout listed below and fresh install firmware 8.0.6. After that, you can update to 8.x without repartitioning.

Before You Begin

  • The information contained in this article applies insofar as it was not already taken into account in the previous migration note 8.3.1.

  • The following instructions apply both to firewalls and Control Centers.

Operators of Firewall Models F800 and F900
If you are going to update an F800 and an F900, disable IPMI before updating to firmware 8.3.2. After the update to 8.3.2, re-enable IPMI again.


Barracuda Firewall Admin

After updating a system, you must also download Firewall Admin with the same version. Firewall Admin is backward-compatible. That means you can manage 7.x and 8.x F-Series Firewalls and Control Centers with Firewall Admin 8.x.

Always use the latest version of Barracuda Firewall Admin.
New 2-Layer Service Architecture

With firmware release 8.0.2, Barracuda introduced a new 2-layer service architecture that makes the former server node in the configuration tree obsolete. As already announced in previous migration notes, converting the former 3-layer server-service architecture to the new 2-layer service architecture was optional within the period of firmware version 8.0.2 to 8.0.6

If you have not yet done so, you must now transform the former 3-layer architecture to the new 2-layer service architecture on the box level before upgrading to firmware version 8.3.2.

This applies both to firewalls and Control Centers.


Supported Models for Firmware Version 8.3.2

The following models are capable of running firmware version 8.3.2:

Barracuda CloudGen F-Series and Control Center Models

Hardware Systems

F12 Rev A, F18 Rev A/B, F80 Rev A/B, F82 Rev A, F93 Rev A, F180 Rev A/B, F183 Rev A, F183R Rev A, F193 Rev A, F280 Rev B/C, F380 Rev A/B, F400 Rev B/C, F600 Rev C/D, F800 Rev C, F900 Rev B, F1000 Rev A/B

Virtual Systems

VF10, VF25, VF50, VF100, VF250, VF500, VF1000, VF2000, VF4000, VF8000, VC400, VC610, VC820

Virtual and Cloud SystemsVFC1, VFC2, VFC4, VFC8, VFC16, VFC48 (model number represents number of supported cores)
WWAN USB ModemsM30, M40, M41, M42
Secure Connectors

SC20a, SC21a, SC22a, SC23a, SC24a/b, SC25a/b, SC26a, SC27a, SC28a, SC29a, SC30a, SC31a, SC34a, SC35a

FSC20A, FSC21A, FSC24B, FSC25B, FSC30A, FSC31A, FSC34A, FSC35A

Public CloudAWS, Azure, Google Cloud
Virtual PlatformsVM-Ware, Hyper-V, XEN, KVM (Proxmox running with KVM images)

Standard Hardware Systems

Standard Hardware

A standard hardware system is a Barracuda CloudGen Firewall F-Series running on 3rd-party server hardware using an SF license. Consult the Barracuda Networks Technical Support to find out if your specific standard hardware is supported.

Disk Space Requirements

Upgrading to version 8.3.2 requires your disk partitions to have enough free disk space. Firmware 8.3.2 requires the following partition spaces:

Disk Space Requirements FIREWALL:

Hard Drive Partition

Disk Space Required

swap2 GB
boot1 GB
/8 GB
/phion04 GB
/art3 GB

Disk Space Requirements CONTROL CENTER:

Hard Drive Partition

Disk Space Required

swap2 GB
boot1 GB
/10 GB
/phion04 GB
/art10 GB


Migration Path to 8.3.2

You can upgrade to firmware 8.3.2 via 8.0.6 from the following firmware versions:

Current Version
Via 8.0.6
Follow Migration Instructions
7.0.0 - 7.0.4

Yes



Migration from 7.x - 8.0.0 to 8.0.6

7.1.0 EA - 7.1.5Yes
7.2.0 - 7.2.6
Yes
8.0.0Yes
8.0.1 - 8.0.5
YesMigration from 8.0.1/8.0.2/8.0.3/8.0.4/8.0.5 to 8.0.6

Your firewall is now prepared to upgrade to firmware version 8.3.2.

Important Note before Upgrading to Release 8.3.2


If you are connecting from an iOS device via Client-to-Site VPN using IPsec, you must change the settings according to the example in the article Example - Client-to-Site IKEv1 IPsec VPN with PSK.

Otherwise, the iOS device won't be able to connect and report the error "Negotiation with the VPN server failed".


Migration Instructions for 8.3.2

Before upgrading to firmware version 8.3.2, you may first need to complete a few additional steps. Check the following topic(s) and, if applicable, complete the migration steps listed below:
1. Upgrade of Virtual Machines for Forward Error Correction (FEC), and IPS
  • Firmware version 8.3.1 now contains the new VPN feature Forward Error Correction (FEC).
  • The IPS system has been replaced with a new implementation from Barracuda.

In order for these features to work as expected on virtual deployments, the virtual hardware must be upgraded to the newest version to work on the ESXi hypervisor directly after the deployment of the virtual machine. For using FEC, the supported version of your hypervisor must be greater than or equal to version 6.5.

For more information, see Step 2 in How to Deploy a CloudGen Firewall Vx OVA on VMware Hypervisors.

2. VPN, Usage of VPN Next Hop IPs
The following instructions apply only if you just have transformed your firewall from the former 3-layer server-service architecture to the new 2-layer assigned services architecture.

Before firmware version 8.3.0, certain VPN scenarios required you to configure next-hop interface IP addresses for the shared networks. Due to the new 2-layer service architecture, which is represented through the Assigned Services node in the configuration tree, it is no longer necessary to explicitly configure these IP addresses.

However, in this special case, it is necessary to apply some additions to the host firewall rule set.

If you have made changes/additions manually to your host firewall rule set, you must back up these host firewall rules to restore them later.

For updating the host firewall rule set, you have two options:

  1. Add the missing rules manually
  2. Update the host firewall rule set with Copy from Default.
How to Update the Host Firewall Rule Set
Step 1. (optional) In case you have made additions/changes to the host firewall rule set manually:

Create a copy of all these firewall rules.

Option 2.1 (recommended): Add the missing rules to the host firewall rule set manually.

For more information on how to create a pass rule, see How to Create a Pass Access Rule.

  1. Go to CONFIGURATION > Configuration Tree > Box > Infrastructure Service > Host Firewall Rules.
  2. Ensure that Inbound is selected in the top-left corner of the rule list display area.
  3. Click Lock.
  4. Add each of the rules in the list to the Inbound Host Firewall Rule Set.

    vpn_routed_hfw_inbound_rules_to_add.png

  5. Click Outbound in the top-left corner of the rule list display area.

  6. Add each of the rules in the list to the Outbound Host Firewall Rule Set.
    vpn_routed_hfw_outbound_rules_to_add.png

  7. Click Send Changes.
Option 2.2: (Only if you did not complete Option 2.1) Update the host firewall rule set with Copy from Default.

After the transformation to the new 2-layer service architecture, the host firewall rule set can be rebuilt by copying it from the default.

Copy from Default will overwrite your existing host firewall rule set. Any previously added custom rules will be lost!
  1. Log into the firewall.
  2. Go to CONFIGURATION > Configuration Tree > Box > Infrastructure Services.
  3. Right-click Host Firewall Rules.
  4. In the list, click Lock.
    lock_host_firewall_rules.png
  5. Right-click Host Firewall Rules.
    host_firewall_ruleset_copy_from_default.png
  6. In the list, click Copy from Default.
  7. Click Activate in the top-right corner of the window.
Step 3. (optional) In case you have made a copy of individual firewall rules, you must restore them now.

Add your individual firewall rules that you copied before to the host firewall rule set.


How to Migrate to Version 8.3.2

Download the appropriate download file:

If You Migrate from Versions 8.0.0 - 8.2.2 to 8.3.2
  1. Go to the download portal https://dlportal.barracudanetworks.com/#/packages/5674/update.GWAY-8.3.2-0422.tgz.
  2. Download the update package.
If You Migrate from Versions 8.3.0/8.3.1 to 8.3.2
  1. Go to the download portal https://dlportal.barracudanetworks.com/#/packages/5673/patch.GWAY-8.3.2-0422.tgz.
  2. Download the patch package.
Start the Update

You can now update the CloudGen Firewall or Control Center.

For more information, see Updating CloudGen Firewalls and Control Centers.

Previous Article Next Article