Upgrading a Multi-Domain Log Server from 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

Instructions

1

Back up your current configuration (see Backing Up and Restoring).

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.

5

Run the Pre-Upgrade Verifier on all source servers and fix all detected issues before you start the upgrade.

Procedure:

  1. See Installing Software Packages on Gaia and follow the applicable action plan.

  2. Step

    Instructions

    1

    Connect with SmartConsole to the R80.40 Multi-Domain Server that manages the Multi-Domain Log Server.

    2

    From the left navigation panel, click Multi-Domain > Domains.

    3

    From the top toolbar, open the Multi-Domain Log Server object.

    4

    From the left tree, click General.

    5

    In the Platform section > in the Version field, select R80.40.

    6

    Click OK.

  3. Step

    Instructions

    1

    Connect with SmartConsole to each 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.

  4. Step

    Instructions

    1

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

    2

    Log in with the superuser credentials.

    3

    Log in to the Expert mode.

    4

    Make sure that all the required daemons have the correct state:

    mdsstat

    • The state of the FWM, FWD, and CPD daemons must be "up" on all levels.

      These daemons must show their PID, or "pnd".

    • The state of the CPCA daemon must be "N/R" on the MDS level.

    • The state of the CPCA daemon must be "down" on the Domain Log Server level.

    If the state of one of the required daemons (FWM, FWD, or CPD) on a Domain Log Server is "down", then wait for 5-10 minutes, restart that Domain Log Server, and check again. Run these three commands:

    mdsstop_customer <IP Address or Name of Domain Log Server>

    mdsstart_customer <IP Address or Name of Domain Log Server>

    mdsstat

    5

    Go to the main MDS context:

    mdsenv

    6

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

    $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:

      yes | $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL

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

      $MDSDIR/scripts/mds_fix_cmas_clms_version -c ALL -n <Name of Domain Log Server>

    7

    Allow the database synchronization to run:

    $CPDIR/bin/cpprod_util CPPROD_SetValue "FW1/6.0" AfterUpgradeDbsyncIndication 1 1 0

    Restart the Check Point services:

    mdsstop

    mdsstart

    For more information, see sk121718.

    8

    Make sure that all the required daemons have the correct state:

    mdsstat

    • The state of the FWM, FWD, and CPD daemons must be "up" on all levels.

      These daemons must show their PID, or "pnd".

    • The state of the CPCA daemon must be "N/R" on the MDS level.

    • The state of the CPCA daemon must be "down" on the Domain Log Server level.

    If the state of one of the required daemons (FWM, FWD, or CPD) on a Domain Log Server is "down", then wait for 5-10 minutes, restart that Domain Log Server, and check again. Run these three commands:

    mdsstop_customer <IP Address or Name of Domain Log Server>

    mdsstart_customer <IP Address or Name of Domain Log Server>

    mdsstat

  5. Step

    Instructions

    1

    Connect to the command line on the server.

    2

    Log in to the Expert mode.

    3

    Restore the Log Exporter configuration as described in sk127653.

    4

    Reconfigure the Log Exporter:

    cp_log_export reconf

    5

    Restart the Log Exporter:

    cp_log_export restart

    For more information, see the R80.40 Logging and Monitoring Administration Guide > Chapter Log Exporter.

  6. Step

    Instructions

    1

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

    2

    Make sure the management database and configuration were upgraded correctly.

  7. Step

    Instructions

    1

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

    2

    Make sure the management database and configuration were upgraded correctly.