Upgrading one Multi-Domain Server from R80.20.M1 with CPUSE

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

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

Important - Before you upgrade a Multi-Domain Server:

Step	Description
1	Back up your current configuration.
2	See the Upgrade Options and Prerequisites.
3	You must close all GUI clients (SmartConsole applications) connected to the source Multi-Domain Server.
4	Install the latest version of the CPUSE from sk92449. Note - The default CPUSE does not support the required Upgrade Tools package.

Workflow:

Get the required Upgrade Tools
Upgrade the Multi-Domain Server with CPUSE
Install the R80.20 SmartConsole
Install the management database
Upgrade the Multi-Domain Log Server, dedicated Log Servers, and dedicated SmartEvent Servers
Upgrade the attributes of all managed objects in all Domain Management Servers
Test the functionality

Step 1 of 7: Get the required Upgrade Tools

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@MDS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.20 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@MDS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.20 BuildNumber 1` `992000043` `[Expert@MDS: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@MDS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.20 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@MDS:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.20 BuildNumber 1
992000043
[Expert@MDS: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 7: Upgrade the Multi-Domain Server with CPUSE

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

Step 3 of 7: Install the R80.20 SmartConsole

See Installing SmartConsole.

Step 4 of 7: Install the management database

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

Step 5 of 7: Upgrade the Multi-Domain Log Server, dedicated Log Servers, and dedicated SmartEvent Servers

If your Multi-Domain Server manages Multi-Domain Log Servers, dedicated Log Servers, or dedicated SmartEvent Servers, you must upgrade these dedicated servers to the same version as the Multi-Domain Server:

For Multi-Domain Log Servers - Upgrade of a Multi-Domain Log Server from R80.20.M1 is not supported. You must perform a clean install of R80.20 Multi-Domain Log Server.
For Log Servers - see Upgrading a Dedicated Log Server from R80.10 and lower
For SmartEvent Servers - see Upgrading a Dedicated SmartEvent Server from R80.10 and lower

Step 6 of 7: Upgrade the attributes of all managed objects in all Domain Management Servers

Step	Description
1	Connect to the command line on the R80.20 Multi-Domain Server.
2	Log in with the superuser credentials.
3	Log in to the Expert mode.
4	Make sure that on all Domain Management Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "`down`" (the "`pnd`" state is acceptable): `[Expert@MDS:0]# mdsstat` If some of the required daemons on a Domain Management Server are in the state "`down`", wait for 5-10 minutes, restart that Domain Management Server and check again. Run these three commands: `[Expert@MDS:0]# mdsstop_customer <`IP Address or Name of Domain Management Server`>` `[Expert@MDS:0]# mdsstart_customer <`IP Address or Name of Domain Management Server`>` `[Expert@MDS:0]# mdsstat`
5	Go to the main MDS context: `[Expert@MDS:0]# mdsenv`
6	Upgrade the attributes of all managed objects in all Domain Management Servers at once: `[Expert@MDS: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@MDS:0]# yes \| $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL` You can perform this action on one Multi-Domain Server at a time with this command: `[Expert@MDS:0]# $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL -n <`Name of Multi-Domain Server`>`
7	Make sure that on all Domain Management Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "`down`" (the "`pnd`" state is acceptable): `[Expert@MDS:0]# mdsstat` If some of the required daemons on a Domain Management Server are in the state "`down`", wait for 5-10 minutes, restart that Domain Management Server and check again. Run these three commands: `[Expert@MDS:0]# mdsstop_customer <`IP Address or Name of Domain Management Server`>` `[Expert@MDS:0]# mdsstart_customer <`IP Address or Name of Domain Management Server`>` `[Expert@MDS:0]# mdsstat`

Step 7 of 7: Test the functionality

Step	Description
1	Connect with the SmartConsole to the R80.20 Multi-Domain Server.
2	Make sure the management database and configuration were upgraded correctly.