1

Back up your current configuration.

2

See the Upgrade Options and Prerequisites.

3

In R80 and above, examine the SmartConsole sessions:

1. Connect with the SmartConsole to the Security Management Server.
2. From the left navigation panel, click Manage & Settings > Sessions > View Sessions.
3. You must publish or discard all sessions, for which the Changes column shows a number greater than zero.

   Right-click on such session and select Publish or Discard.

4

You must close all GUI clients (SmartConsole applications) connected to the source Security Management Server.

1

Download the R80.20 Management Server Migration Tool from the R80.20 Home Page SK.

2

Transfer the R80.20 Management Server Migration Tool package to the current Security Management Server to some directory (for example, /var/log/path_to_migration_tool/).

Note - Make sure to transfer the file in the binary mode.

1

Connect to the command line on the current Security Management Server.

2

Log in to the Expert mode.

3

Go to the directory, where you put the R80.20 Management Server Migration Tool package:

[Expert@MGMT:0]# cd /var/log/path_to_migration_tool/

4

Extract the R80.20 Management Server Migration Tool package:

[Expert@MGMT:0]# tar zxvf <Name of Management Server Migration Tool Package>.tgz

5

Important - This step applies only when you upgrade from R77.30 (or lower).

Run the Pre-Upgrade Verifier (PUV).

1. Run this command and use the applicable syntax based on the instructions on the screen:

   [Expert@MGMT:0]# ./pre_upgrade_verifier -h

2. Read the Pre-Upgrade Verifier output.

   If you need to fix errors:

   i) Follow the instructions in the report.

   ii) In a Management High Availability environment, if you made changes, synchronize the Management Servers immediately after these changes.

   iii) Run the Pre-Upgrade Verifier again.

6

Export the management database:

• If Endpoint Policy Management blade is disabled on this Security Management Server:

  [Expert@MGMT:0]# yes | nohup ./migrate export [-l | -x] [-n] /<Full Path>/<Name of Exported File> &

• If Endpoint Policy Management blade is enabled on this Security Management Server:

  [Expert@MGMT:0]# yes | nohup ./migrate export [-l | -x] [-n] [--include-uepm-msi-files] /<Full Path>/<Name of Exported File> &

Notes:

• yes | nohup ... & - are mandatory parts of the syntax.
• See the R80.20 CLI Reference Guide - Chapter Security Management Server Commands - Section migrate.
• See sk133312.

7

This step applies only to R7x and R80 versions.

If SmartEvent Software Blade is enabled, then export the Events database.

See sk110173.

8

Calculate the MD5 for the exported database files:

[Expert@MGMT:0]# md5sum /<Full Path>/<Name of Database File>.tgz

9

Transfer the exported databases from the current Security Management Server to an external storage:

/<Full Path>/<Name of Database File>.tgz

Note - Make sure to transfer the file in the binary mode.

1

Connect to the command line on the R80.20 Security Management Server.

2

Log in to the Expert mode.

3

Make sure a valid license is installed:

cplic print

If it is not already installed, then install a valid license now.

4

Transfer the exported databases from an external storage to the R80.20 Security Management Server, to some directory.

Note - Make sure to transfer the files in the binary mode.

5

Make sure the transferred files are not corrupted. Calculate the MD5 for the transferred files and compare them to the MD5 that you calculated on the original Security Management Server:

[Expert@MGMT:0]# md5sum /<Full Path>/<Name of Database File>.tgz

6

Go to the $FWDIR/bin/upgrade_tools/ directory:

[Expert@MGMT:0]# cd $FWDIR/bin/upgrade_tools/

7

Import the management database:

• If Endpoint Policy Management blade is disabled on this Security Management Server:

  [Expert@MGMT:0]# yes | nohup ./migrate import [-l | -x] [-n] /<Full Path>/<Name of Exported File>.tgz &

• If Endpoint Policy Management blade is enabled on this Security Management Server:

  [Expert@MGMT:0]# yes | nohup ./migrate import [-l | -x] [-n] [--include-uepm-msi-files] /<Full Path>/<Name of Exported File>.tgz &

Notes:

• yes | nohup ... & - are mandatory parts of the syntax.
• See the R80.20 CLI Reference Guide - Chapter Security Management Server Commands - Section migrate.
• See sk133312.

If you upgrade from R80 (or higher) version, and the IP addresses of the source and target Security Management Servers are different:

1. Issue licenses for the new IP address in your Check Point User Center account.
2. Install the new licenses on the R80.20 Security Management Server.

If you upgrade from R77.30 (or lower) version to R80.20, then the IP addresses of the source and target Security Management Servers must be the same.

• If you need to have a different IP address on the R80.20 Security Management Server, you can change it only after the upgrade procedure. Note that you have to issue licenses for the new IP address.

8

This step applies only if you upgraded from R7x and R80 versions.

If SmartEvent Software Blade is enabled, then import the Events database.

See sk110173.

9

Restart the Check Point services:

[Expert@MGMT:0]# cpstop

[Expert@MGMT:0]# cpstart

1

Connect with SmartConsole to the R80.20 Security Management Server.

2

In the top left corner, click Menu > Install database.

3

Select all objects.

4

Click Install.

5

Click OK.

1

Connect with the SmartConsole to the R80.20 Security Management Server.

2

In the SmartConsole, from the left navigation panel, click Logs & Monitor.

3

At the top, click + to open a new tab.

4

In the bottom left corner, in the External Apps section, click SmartEvent Settings & Policy.

The Legacy SmartEvent client opens.

5

In the top left corner, click Menu > Actions > Install Event Policy.

6

Confirm.

7

Wait for these messages to appear:

SmartEvent Policy Installer installation complete

SmartEvent Policy Installer installation succeeded

8

Click Close.

9

Close the Legacy SmartEvent client.

1

Connect with the SmartConsole to the R80.20 Security Management Server.

2

Make sure the management database and configuration were upgraded correctly.