Print Download PDF Send Feedback

Previous

Next

Upgrading a Multi-Domain Log Server from R80.20, R80.10, and lower with CPUSE

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

Notes:

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:

  1. Upgrade the Multi-Domain Log Server with CPUSE
  2. Install the management database
  3. Upgrade the attributes of all managed objects in all Domain Log Servers
  4. Test the functionality on R80.30 Multi-Domain Log Server
  5. Test the functionality on R80.30 Multi-Domain Server

Step 1 of 5: 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 2 of 5: 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 3 of 5: 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

Allow the database synchronization to run:

[Expert@MDLS:0]# $CPDIR/bin/cpprod_util CPPROD_SetValue "FW1/6.0" AfterUpgradeDbsyncIndication 1 1 0

Restart the Check Point services:

[Expert@MDLS:0]# mdsstop

[Expert@MDLS:0]# mdsstart

For more information, see sk121718.

8

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 4 of 5: 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 5 of 5: 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.