The PAR file migration wizard helps you to migrate PAR files created on a supported hardware firewall to the next larger model, or a different revision of the same model. Default values and interface labels are automatically changed to fit the new model. Settings that have been modified by the admin are not migrated. The migration is available for both stand-alone and managed firewalls. There are two types of migrations:
Hardware upgrades to the next higher model – For example, migrating an F80 to an F180.
Supported EOL models to their direct successor – For example, migrating an F201 to an F280 Revision B.
Supported EOL Model Migration
Source Model | Destination Models | Comment |
|---|---|---|
F10 |
| - |
F100 |
|
|
F200 |
| - |
F280 Rev A |
| No Wi-Fi on F380 |
F300 |
| - |
F301 |
| No Wi-Fi on F380 |
Supported Hardware Upgrade Migrations
Source Model | Destination Models | Comment |
|---|---|---|
F18 |
| - |
F80 |
| - |
F180 |
| - |
F280 Rev B |
| No Wi-Fi on F380 |
F380 |
| - |
F400 |
| all sub models |
F600 |
| all sub models |
F800 |
| all sub models |
F900 |
| all sub models |
Video
In this video we show how a standalone F280 Rev A is migrated to a F180 Rev A and a managed F300 is migrated to a F380 Rev A:
Videolink:
https://campus.barracuda.com/Migrating a Stand-alone Firewall to a New Hardware Model
Stand-alone firewalls are migrated when importing the PAR file. The firewall detects the model mismatch of the imported PAR file and guides the user through the migration process. Some configurations cannot be migrated automatically and must be verified or migrated manually by the admin before activating the migrated configuration. If you are migrating a stand-alone high availability cluster, import the PAR file on the primary firewall. The PAR file for the secondary firewall is not migrated; it is created on the primary firewall that has already been migrated.
For more information, see How to Migrate a Standalone Hardware Firewall to a new Model.
Migrating a Managed Firewall to a New Hardware Model
The configuration for managed firewalls are migrated directly on the Control Center. To ensure that no incompatible configuration changes are pushed to the remote firewall during this process, the configuration updates must be blocked. Before starting the migration, verify that the target model supports the current firmware version running on the source firewall. Some configuration nodes, such as repository linked configurations and cluster-level shared services, might have to be migrated manually. To finish the migration, activate the configuration changes, export the PAR file, and deploy the new firewall. When the new firewall is up and installed in place of the old firewall, unblock the configuration updates.
For more information, see How to Migrate Managed Hardware Firewalls to a New Model.