Upgrading a Multi-Domain Log Server from R80.20 and higher with CPUSE

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

Notes: This procedure is supported only for servers that run R80.20.M1, R80.20, R80.20.M2, or R80.30 versions. For additional information related to this upgrade, see sk163814.

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. Get the required Upgrade Tools on the server

   Important - See Management Server Migration Tool and Upgrade Tools to understand if your server can download and install the latest version of the Upgrade Tools automatically.

   Step	Instructions
   1	Download the R80.40 Upgrade Tools from the sk135172. (See Management Server Migration Tool and Upgrade Tools.) Note - This is a CPUSE Offline package.
   2	Install the R80.40 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: cpprod_util CPPROD_GetValue CPupgrade-tools-R80.40 BuildNumber 1 The output must show the same build number you see in the name of the downloaded TGZ package. Example Name of the downloaded package: ngm_upgrade_wrapper_993000222_1.tgz [Expert@HostName:0]# cpprod_util CPPROD_GetValue CPupgrade-tools-R80.40 BuildNumber 1 993000222 [Expert@HostName: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.

2. Upgrade the Multi-Domain Log Server with CPUSE

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

3. Update the version of the Multi-Domain Log Server object

   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.

4. Install the management database on each Domain Log Server on Multi-Domain Log Server

   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.

5. Upgrade the attributes of all managed objects in all Domain Log Servers

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

6. Reconfigure the Log Exporter

   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.

7. Test the functionality on the R80.40 Multi-Domain Log Server

   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.

8. Test the functionality on the R80.40 Multi-Domain Server

   Step	Instructions
   1	Connect with SmartConsole to the R80.40 Multi-Domain Server that manages the Multi-Domain Log Server.
   2	Make sure the logging works as expected.