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

Best Practice - Migrate to Different License Type for PAYG or BYOL Public Cloud Firewalls

  • Last updated on

It is not possible to switch between PAYG and BYOL licensed firewalls in the public cloud, by changing the license on the firewall. The firewall must be redeployed with the desired images type. The configuration can then be restored from the PAR file of the source firewall. These instructions are also valid for migrating the from one PAYG firewall to another PAYG firewall instance.

Step 1. Back up the Existing Firewall Configuration

Create a PAR file of the existing firewall. For more information, see How to Back Up and Restore Firewall and Control Center Configurations.

Step 2.  Redeploy Firewall using the Desired Image Type (BYOL or PAYG)

Redeploy the firewall VM or Instance.

  • Single DHCP Interface – For firewalls using a single dhcp interface, the redeployed firewalls can be deployed in parallel to minimize downtime during the migration. Access rules or other configurations using the IP address of the firewall and not the reference to the DHCP interface must be migrated manually after restoring the configuration.

  • Static IP Address or Multiple NICs –If static IP addresses are used, the redeployed firewalls must use the same IP addresses. In this case the old firewall must be deleted before redeploying the new image.

For more information, see Public Cloud.

Step 3. (PAYG only) Export the PAYG License

Restoring the firewall configuration from a PAR file also overwrites the existing licenses with the licenses included in the PAR file. Export the PAYG licenses to be able to restore them after restoring the configuration.

  1. Log in to the redeployed firewall.
  2. Go to CONFIGURATION > Configuration Tree > Box > Box Licenses.
  3. Click Lock.
  4. Select the PAYG license in the Licenses list, click the export icon and click Export to File.
    PAYG_BYOL_migration_01.png
  5. Enter the File name.
  6. Click Save.

You now have a lic file containing the PAYG license stored locally on your computer.

Step 3. Restore the Configuration from PAR File

Restore the configuration from the PAR file created on the replaced firewall.

  1. Go to CONFIGURATION > Configuration Tree > Box.
  2. Right click Box and select Restore from PAR file from the context menu. the Restore from PAR file window opens.
  3. Click OK.
  4. Select the PAR file and click Open.
    PAYG_BYOL_migration_02.png
  5. Click OK.
  6. Click Activate. The Activate Changes window opens.
  7. Click Activate.

Depending on the configuration, a network activation may be required. For more information, see How to Activate Network Changes.

Step 4. License the Firewall

Depending on the license type either restore the PAYG license or activate the BYOL license on the firewall.

PAYG Licenses
  1. Log in to the redeployed firewall.
  2. Go to CONFIGURATION > Configuration Tree > Box > Box Licenses.
  3. Click Lock.
  4. Select all licenses in the Licenses table and click the delete icon. 
  5. Click + and select Import from Files.
    PAYG_BYOL_migration_03.png
  6. Select the license file exported in step 3 and click Open. The Certificate View window opens.
  7. Click OK.  The End User License Agreement window opens.
  8. Select I agree.
  9. Click OK.
  10. Click Send Changes and Activate.
BYOL Licenses

Activate the license by entering the activation code in the licensing element of the general dashboard.

For more information, see How to Activate and License a Stand-alone Virtual or Public Cloud F-Series Firewall or Control Center.

Go to CONTROL > Licenses to verify that the license state is Normal Operation and all licenses and subscriptions are green.

PAYG_BYOL_migration_04.png

Last updated on