Support Center > Search Results > SecureKnowledge Details
In-Place Upgrade packages for CloudGuard Network Technical Level


The tables in this article list In-Place Upgrade for CloudGuard Network upgrade ackages.

For more information about CloudGuard, including documentation and known limitations, see sk132552 - Check Point CloudGuard solutions.


For instructions on CPUSE packages usage, refer to sk92449 - Check Point Upgrade Service Engine (CPUSE) 
Refer to the Installation and Upgrade Guide for the version you are upgrading to.

  1. Before you upgrade, make sure there are no hotfixes installed that are not included in the new version to be installed.
  2. On CloudGuard for AWS (Gateway), after package installation is completed, wait for the Gateway to reboot twice.
  3. After upgrade has completed, it is important to visit the Security Gateway object in SmartConsole to allow it to update it's version and then install policy.
  4. When upgrading a Security Cluster to R80.40 and higher, only Multi-Version Cluster (MVC) upgrade method is supported. Refer to sk107042 - ClusterXL upgrade methods and paths for additional information.
  5. An issue was identified in the former Azure upgrade packages (pre rev3) that may cause a connectivity issue after a machine reboot. Contact Check Point support for the fix.
  6. On CloudGuard for Azure, packages are currently not compatible with Dv4 and Dv5 instance types (or any other type without an Azure Resource Disk).
  7. For Management (Security Management/Multi-Domain Server) upgrades please make sure port 18208 is open in your security group. 

Supported Configurations

  1. R80.30 and higher.
  2. Autoscale/VMSS/MIG & Standalone deployments are not supported.
  3. Upgrading of AWS GeoCluster to R81.20 is not supported.

Additional Resources

Give us Feedback
Please rate this document