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.
For upgrade of Security Gateway/Security Cluster:
For Upgrade of Security Management/Multi-Domain Management Server:
- Before you upgrade, make sure there are no hotfixes installed that are not included in the new version to be installed.
- On CloudGuard for AWS (Gateway), after package installation is completed, wait for the Gateway to reboot twice.
- 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.
- 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.
- 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.
- On CloudGuard for Azure, packages are currently not compatible with Dv4 and Dv5 instance types (or any other type without an Azure Resource Disk).
- For Management (Security Management/Multi-Domain Server) upgrades please make sure port 18208 is open in your security group.
- R80.30 and higher.
- Autoscale/VMSS/MIG & Standalone deployments are not supported.
- Upgrading of AWS GeoCluster to R81.20 is not supported.