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

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

SC Firmware Update

  • Last updated on

The Control Center manages the distribution and update process for SC firmware updates. The admin must first update the firmware package to the Control Center and select the SCs from the list. The Control Center then distributes the file. Afterwards, the admin can trigger the update process and monitor the progress of the update.

In this article:

Step 1. Verify the Compatibility of the SC with the Control Center Firmware

The following table shows the compatibility between the Control Center and SC firmware versions. Upgrade the Control Center before updating the managed SCs.

For more information, see Updating F-Series Firewalls and Control Centers.

SC System Version

Control Center Version

 6.2.1
1.0.0YES

Step 2. Download the Update Package from the Download Portal

Download the update package from the Barracuda Download Portal: https://dlportal.barracudanetworks.com.

Step 3. Import the Update Package into the Control Center

Import the update file to the Control Center.

  1. Log into the Control Center.
  2. Go to CONTROL > Firmware Update.
  3. In the lower half of the screen, click on the Files on NG Control Center tab. 
  4. Click Import Update File and select the update package you downloaded in Step 1.
import_update.png

The file is copied to the Control Center and displayed in the Files on NG Control Center tab

Step 4. Send the Update Package to the Systems

  1. On the Firmware Update page, select the SCs you want to update.
  2. In the Files on NG Control Center tab, select the update package.
  3. Click Create Update Task. The New Update Task window opens.
  4. (optional) Select the Scheduling Mode.
    create_update.png
  5. Click OK.

The update packages are now copied to the selected remote systems. Go to CONTROL > Update Tasks to monitor the progress.

Bild 009.png

Step 5. Execute the Update Package

After the update package has been copied to the SC, trigger the update.

  1. Go to CONTROL > Update Tasks.
  2. In the  column, a green icon is displayed, verifying that the update package was sent successfully.
  3. Right-click the selected SC and select Perform Update.
    FW_Update_01.png
  4. In the Schedule Task window, select Immediate Execution from the Scheduling Mode list and click OK.
    FW_Update_02.png

Wait for the update to finish.

Secure Connectors will reboot after the update has been applied.

Step 6. Migrate the Configuration Version of the Cluster

If you are updating to a new major version, you must migrate the cluster version after the update has completed.

Update the Clusters Individually
  1. Open the cluster you just updated (CONFIGURATION > Configuration Tree > Multi-Range > your range > your cluster).
  2. Right-click on the cluster and select Lock.
  3. Right-click on the cluster and select Migrate Cluster.
  4. Select the new Release version.
  5. Click OK.
  6. Click Activate
Update all the Clusters in a Range

If all clusters in the range are on the same firmware version, you can migrate all clusters simultaneously. 

  1. Open the range containing the clusters you just updated (CONFIGURATION > Configuration Tree > Multi-Range > your range).
  2. Right-click on the range and select Lock.
  3. Right-click on the range and select Migrate Range.
  4. Select the new Release version.
  5. Click OK.
  6. Click Activate.

Troubleshooting / Logs

To troubleshoot updates on the SC you must enable persistent logging and review the /var/phion/logs/installUpdate.log file. Do not permanently enable persistent logging, as it impacts the lifetime of the sdcard.

Last updated on