Upgrading a Multi-Domain Log Server from R80.20.M1 or R80.20.M2 with CPUSE

In a CPUSE upgrade scenario, you perform the upgrade procedure on the same Multi-Domain Log Server.

Note - This procedure is supported only for a Multi-Domain Log Server that runs R80.20.M1 or R80.20.M2.

Important - Before you upgrade a Multi-Domain Log Server:

Step	Description
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.

Workflow:

Get the required Upgrade Tools
Upgrade the Multi-Domain Log Server with CPUSE
Install the management database
Upgrade the attributes of all managed objects in all Domain Log Servers
Test the functionality on R80.30 Multi-Domain Log Server
Test the functionality on R80.30 Multi-Domain Server

Step 1 of 6: Get the required Upgrade Tools on the R80.20.M1 / R80.20.M2 Multi-Domain Log Server

Step	Description
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]#`

Step

Description

Download the required Upgrade Tools from sk135172.

Note - This is a CPUSE Offline package.

Install the required Upgrade Tools with CPUSE.

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

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]#

Note - The command migrate_server from these Upgrade Tools always tries to connect to Check Point Cloud over the Internet. This is to make sure you always have the latest version of these Upgrade Tools installed. If the connection to Check Point Cloud fails, this message appears:
"Timeout. Failed to retrieve Upgrade Tools package. To download the package manually, refer to sk135172."

Step 2 of 6: Upgrade the Multi-Domain Log Server with CPUSE

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

Step 3 of 6: Install the management database

Step	Description
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.

Step 4 of 6: Upgrade the attributes of all managed objects in all Domain Log Servers

Step	Description
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`

Step 5 of 6: Test the functionality on R80.30 Multi-Domain Log Server

Step	Description
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.

Step 6 of 6: Test the functionality on R80.30 Multi-Domain Server

Step	Description
1	Connect with SmartConsole to the R80.30 Multi-Domain Server.
2	Make sure the logging works as expected.