Supported Upgrade Paths

Installation Methods

Upgrade Paths

Note - For more information about Security Management Servers and supported managed Security Gateways see sk113113.

Upgrade to R81.20 is available only from these versions:

Current Version

Security Gateways

and

VSX (1)

Management Servers

and

Multi-Domain Servers

Standalone

R81.10,

R81,

R80.40,

R80.30 kernel 3.10,

R80.30 kernel 2.6,

R80.20 kernel 3.10,

R80.20 kernel 2.6

For Scalable Platforms:

R81.10,

R81,

R80.30SP,

R80.20SP

(2)

Not applicable

Not applicable

R80.20.M2,

R80.20.M1

Not applicable

Not applicable

R80.10

(4)

Requires a 2-step

upgrade path (3)(4)

Requires a 2-step

upgrade path (3)(4)

R80

Not applicable

Requires a 2-step

upgrade path (3)

Not applicable

R77.30

(4)(5)

Requires a 2-step

upgrade path (3)(4)(5)

Requires a 2-step

upgrade path (3)(4)(5)

Notes:

  1. Starting from R81.10, VSLS is the only supported mode for new installations of VSX Clusters.

    Upgrade of a VSXClosed Virtual System Extension. Check Point virtual networking solution, hosted on a computer or cluster with virtual abstractions of Check Point Security Gateways and other network devices. These Virtual Devices provide the same functionality as their physical counterparts. ClusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. in the High Availability mode from R81.10 and earlier versions to R81.20 is supported.

    To convert the upgraded VSX Cluster to VSLS, use the "vsx_util to convert" command.

  2. Upgrade from these versions to R81.20 is supported only with specific takes of a Jumbo HotfixClosed Software package installed on top of the current software version to fix a wrong or undesired behavior, and to add a new behavior. Accumulators.

    See sk177624.

    In Maestro environment, it is possible to upgrade Security GroupsClosed A logical group of Security Appliances (in Maestro) / Security Gateway Modules (on Scalable Chassis) that provides Active/Active cluster functionality. A Security Group can contain one or more Security Appliances / Security Gateway Modules. Security Groups work separately and independently from each other. To the production networks, a Security Group appears a single Security Gateway. In Maestro, each Security Group contains: (A) Applicable Uplink ports, to which your production networks are connected; (B) Security Appliances (the Quantum Maestro Orchestrator determines the applicable Downlink ports automatically); (C) Applicable management port, to which the Check Point Management Server is connected. and Quantum Maestro OrchestratorsClosed A scalable Network Security System that connects multiple Check Point Security Appliances into a unified system. Synonyms: Orchestrator, Quantum Maestro Orchestrator, Maestro Hyperscale Orchestrator. Acronym: MHO. (if you decide to upgrade, you must upgrade both).

  3. The required 2-step upgrade path is:

    1. To R80.40

      See the R80.40 Installation and Upgrade Guide.

    2. To R81.20

  4. Before you start the upgrade, you must make sure the GaiaClosed Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. OS edition is 64-bit:

    1. Get the current Gaia OS edition with this Gaia ClishClosed The name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell). command:

      show version all

    2. If the Gaia OS edition is "32-bit", run these Gaia Clish commands:

      set edition 64-bit

      save config

      reboot

  5. To upgrade an R77.30 environment that implements Carrier Security (former Firewall-1 GX), you must follow sk169415:

    1. Upgrade the R77.30 Management ServerClosed Check Point Single-Domain Security Management Server or a Multi-Domain Security Management Server. to the special R80.30-based image.

    2. Upgrade the R80.30 Management Server to R81.

    3. Change the GTP settings.

    4. Upgrade the R77.30 Security Gateway / Cluster to R81.

    5. Upgrade the R81 Management Server to R81.20.

    6. Upgrade the R81 Security Gateway / Cluster to R81.20.

Upgrade Methods

Use these methods to upgrade your Check Point environment to R81.20:

Check Point Product

Gaia Fast Deployment

Clean Install (1)

Gaia Fast Deployment

Upgrade (1)

Central Deployment

in SmartConsole (2)

CPUSE

Clean Install (3)

CPUSE

Upgrade (4)

Advanced

Upgrade (5)

Upgrade

with Migration (6)

Upgrade

with CDT (7)

Security Gateways

VSX Gateways

Security Group Members - Maestro

Security Group Members - Scalable ChassisClosed The container that contains the all the components of a 60000 / 40000 Appliance. Synonym: Chassis.

ClusterXL Members in the High Availability modes

ClusterXL Members in the Load Sharing modes

VSX Cluster Members

VRRP Cluster Members

Primary Security Management ServerClosed Dedicated Check Point server that runs Check Point software to manage the objects and policies in a Check Point environment within a single management Domain. Synonym: Single-Domain Security Management Server.

Secondary Security Management Server

Primary Multi-Domain Security Management Server

Secondary Multi-Domain Security Management Server

Primary Multi-Domain Log ServerClosed Dedicated Check Point server that runs Check Point software to store and process logs in a Multi-Domain Security Management environment. The Multi-Domain Log Server consists of Domain Log Servers that store and process logs from Security Gateways that are managed by the corresponding Domain Management Servers. Acronym: MDLS.

Secondary Multi-Domain Log ServerClosed Dedicated Check Point server that runs Check Point software to store and process logs.

Primary CloudGuard ControllerClosed Provisions SDDC services as Virtual Data Centers that provide virtualized computer networking, storage, and security.

Secondary CloudGuard Controller

Primary Endpoint Security Management Server

Secondary Endpoint Security Management Server

Dedicated Log Server

Dedicated SmartEvent ServerClosed Dedicated Check Point server with the enabled SmartEvent Software Blade that hosts the events database.

Full High Availability Cluster Members

StandaloneClosed Configuration in which the Security Gateway and the Security Management Server products are installed and configured on the same server. Server

Notes:

  1. Gaia Fast Deployment:

    Performs a multi-step upgrade or clean install with one image.

    This image already contains a specific base version, a designated role (for example, a Security Gateway), and Hotfixes / Jumbo Hotfix AccumulatorClosed Collection of hotfixes combined into a single package. Acronyms: JHA, JHF, JHFA..

    You can see and install this image with CPUSE in Gaia Portal or Gaia Clish.

    For more information, see sk120193.

  2. Central Deployment in SmartConsole:

    • You perform a remote installation of an upgrade package from SmartConsole.

    • You install the package from the local repository on the Management Server or from Check Point Cloud.

    • You can install the package on several targets at the same time.

    • For instructions, see the R81.20 Security Management Administration Guide.

  3. CPUSE Clean Install:

    • You perform a local installation of the higher version from scratch in Gaia Portal or Gaia Clish.

    • You install the package from the local repository in Gaia OS or from Check Point Cloud.

    • Requires these steps to preserve the configuration and database:

      1. Export the data before the installation.

      2. Import the data after the installation.

    • For instructions, see the R81.20 Installation and Upgrade Guide.

  4. CPUSE Upgrade (In-place Upgrade):

    • You perform a local installation of an upgrade package in Gaia Portal or Gaia Clish.

    • You install the package from the local repository in Gaia OS or from Check Point Cloud.

    • Keeps the current configuration and database.

    • For instructions, see the R81.20 Installation and Upgrade Guide.

  5. Advanced Upgrade:

    • Intended for Management Servers only.

    • You perform a local installation of an upgrade package in Gaia Portal or Gaia Clish.

    • You install the package from the local repository in Gaia OS or from Check Point Cloud.

    • Requires these steps:

      1. Export of the current management database from the server.

      2. Upgrade of the server with CPUSE (In-place Upgrade or Clean Install).

      3. Import of the exported management database.

    • For instructions, see the R81.20 Installation and Upgrade Guide.

  6. Upgrade with Migration:

    • Intended for Management Servers only.

    • Requires these steps:

      1. Export of the current management database from the server.

      2. Installation of a different server with a higher version (Clean Install).

      3. Import of the exported management database.

    • For instructions, see the R81.20 Installation and Upgrade Guide.

  7. Upgrade with CDT (Central Deployment Tool):

    • Intended for Security Gateways and Cluster Members only.

    • You perform a remote installation of an upgrade package from the Management Server.

    • You install the package from the local repository on the Management Server.

    • You can install the package on several targets at the same time.

    • For more information, see sk111158.

  8. The minimum required unpartitioned disk space is the highest value of one of these:

    • Size of the current root partition.

    • The used space in the current root partition plus 3 GB.

    • If the used space is more than 90% of the root partition, then 110% of the size of the current root partition.

    Important:

    • At least 20 GB of free disk space is required in the root partition for an Upgrade to succeed.

    • At least 10 GB of free disk space is required in the /var/log partition for a Clean Install or Upgrade to succeed.