1

Back up your current configuration.

2

See the Upgrade Options and Prerequisites.

3

You must upgrade your Multi-Domain Servers.

4

You must close all GUI clients (SmartConsole applications) connected to the source Multi-Domain Log Server.

1

Download the required Upgrade Tools from sk135172.

Note - This is a CPUSE Offline package.

2

Install the required Upgrade Tools with CPUSE.

See Installing Software Packages on Gaia and follow the applicable action plan for the local offline installation.

3

Make sure the package is installed.

Run this command in the Expert mode:

[Expert@MDLS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.30 BuildNumber 1

The output must show the same build number you see in the name of the downloaded package.

Example:

Name of the downloaded package: ngm_upgrade_wrapper_992000043_1.tgz

[Expert@MDLS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.30 BuildNumber 1
992000043
[Expert@MDLS:0]#

1

Connect to the command line on the current Multi-Domain Log Server.

2

Log in with the superuser credentials.

3

Log in to the Expert mode.

4

Run the Pre-Upgrade Verifier.

• If this Multi-Domain Log Server is connected to the Internet, run:

  [Expert@MDLS:0]# $MDS_FWDIR/scripts/migrate_server verify -v R80.30

• If this Multi-Domain Log Server is not connected to the Internet, run:

  [Expert@MDLS:0]# $MDS_FWDIR/scripts/migrate_server verify -v R80.30 -skip_upgrade_tools_check

Syntax options:

• -v R80.30 - Specifies the version, to which you plan to upgrade.
• -skip_upgrade_tools_check - Does not try to connect to Check Point Cloud to check for a more recent version of the Upgrade Tools.

5

Read the Pre-Upgrade Verifier output.

If you need to fix errors:

1. Follow the instructions in the report.
2. Run the Pre-Upgrade Verifier again.

6

Go to the $MDS_FWDIR/scripts/ directory:

[Expert@MDLS:0]# cd $MDS_FWDIR/scripts

7

Export the management database:

• This Multi-Domain Log Server is connected to the Internet, run:

  [Expert@MDLS:0]# ./migrate_server export -v R80.30 [-l | -x] /<Full Path>/<Name of Exported File>.tgz

• This Multi-Domain Log Server is not connected to the Internet, run:

  [Expert@MDLS:0]# ./migrate_server export -v R80.30 -skip_upgrade_tools_check [-l | -x] /<Full Path>/<Name of Exported File>.tgz

Syntax options:

• -v R80.30 - Specifies the version, to which you plan to upgrade.
• -skip_upgrade_tools_check - Does not try to connect to Check Point Cloud to check for a more recent version of the Upgrade Tools.
• -l - Exports the Check Point logs without log indexes in the $FWDIR/log/ directory. Note - The command can export only closed logs (to which the information is not currently written).
• -x - Exports the Check Point logs with their log indexes in the $FWDIR/log/ directory. Note - The command can export only closed logs (to which the information is not currently written).

8

Calculate the MD5 for the exported database files:

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

9

Transfer the exported databases from the current Multi-Domain Log Server to an external storage:

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

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

1

Download the required Upgrade Tools from sk135172.

Note - This is a CPUSE Offline package.

2

Install the required Upgrade Tools with CPUSE.

See Installing Software Packages on Gaia and follow the applicable action plan for the local offline installation.

3

Make sure the package is installed.

Run this command in the Expert mode:

[Expert@MDLS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.30 BuildNumber 1

The output must show the same build number you see in the name of the downloaded package.

Example:

Name of the downloaded package: ngm_upgrade_wrapper_992000043_1.tgz

[Expert@MDLS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.30 BuildNumber 1
992000043
[Expert@MDLS:0]#

1

Connect to the command line on the R80.30 Multi-Domain Log Server.

2

Log in with the superuser credentials.

3

Log in to the Expert mode.

4

Make sure a valid license is installed:

mdsenv

cplic print

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

5

Transfer the exported database from an external storage to the R80.30 Multi-Domain Log Server, to some directory.

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

6

Make sure the transferred file is not corrupted.

Calculate the MD5 for the transferred file and compare it to the MD5 that you calculated on the original Multi-Domain Log Server:

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

7

Go to the $MDS_FWDIR/scripts/ directory:

[Expert@MDLS:0]# cd $MDS_FWDIR/scripts/

8

Import the management database:

• This Multi-Domain Log Server is connected to the Internet, run:

  [Expert@MDLS:0]# ./migrate_server import -v R80.30 [-l | -x] /<Full Path>/<Name of Exported File>.tgz

• This Multi-Domain Log Server is not connected to the Internet, run:

  [Expert@MDLS:0]# ./migrate_server import -v R80.30 -skip_upgrade_tools_check [-l | -x] /<Full Path>/<Name of Exported File>.tgz

Syntax options:

• -v R80.30 - Specifies the version, to which you plan to upgrade.
• -skip_upgrade_tools_check - Does not try to connect to Check Point Cloud to check for a more recent version of the Upgrade Tools.
• -l - Imports the Check Point logs without log indexes in the $FWDIR/log/ directory.
• -x - Imports the Check Point logs with their log indexes in the $FWDIR/log/ directory.

9

Make sure that on all Domain Log Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "down" (the "pnd" state is acceptable):

[Expert@MDLS:0]# mdsstat

If some of the required daemons on a Domain Log Server are in the state "down", wait for 5-10 minutes, restart that Domain Log Server and check again. Run these three commands:

[Expert@MDLS:0]# mdsstop_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstart_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstat

1

Connect with SmartConsole to each R80.30 Domain Management Server that manages the Domain Log Server.

2

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

3

Select all objects.

4

Click Install.

5

Click OK.

1

Connect to the command line on the R80.30 Multi-Domain Log Server.

2

Log in with the superuser credentials.

3

Log in to the Expert mode.

4

Make sure that on all Domain Log Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "down" (the "pnd" state is acceptable):

[Expert@MDLS:0]# mdsstat

If some of the required daemons on a Domain Log Server are in the state "down", wait for 5-10 minutes, restart that Domain Log Server and check again. Run these three commands:

[Expert@MDLS:0]# mdsstop_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstart_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstat

5

Go to the main MDS context:

[Expert@MDLS:0]# mdsenv

6

Upgrade the attributes of all managed objects in all Domain Log Servers at once:

[Expert@MDLS:0]# $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL

Notes:

• Because the command prompts you for a 'yes/no' for each Domain and each object in the Domain, you can explicitly provide the 'yes' answer to all questions with this command:

  [Expert@MDLS:0]# yes | $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL

• You can perform this action on one Multi-Domain Log Server at a time with this command:

  [Expert@MDLS:0]# $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL -n <Name of Multi-Domain Log Server>

7

Make sure that on all Domain Log Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "down" (the "pnd" state is acceptable):

[Expert@MDLS:0]# mdsstat

If some of the required daemons on a Domain Log Server are in the state "down", wait for 5-10 minutes, restart that Domain Log Server and check again. Run these three commands:

[Expert@MDLS:0]# mdsstop_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstart_customer <IP Address or Name of Domain Log Server>

[Expert@MDLS:0]# mdsstat

1

Connect with SmartConsole to the R80.30 Multi-Domain Log Server.

2

Make sure the configuration was upgraded correctly and it works as expected.

1

Connect with SmartConsole to the R80.30 Multi-Domain Server.

2

Make sure the logging works as expected.