In a migration and upgrade scenario, you perform the procedure on the source Multi-Domain Server and the different target Multi-Domain Server.
Note - This procedure is supported only for a Multi-Domain Server that runs R80.20.M1 or R80.20.M2.
Important - Before you upgrade a Multi-Domain Server:
Step |
Description |
---|---|
1 |
|
2 |
See the Upgrade Options and Prerequisites. |
3 |
In R80 and above, examine the SmartConsole sessions:
|
4 |
You must close all GUI clients (SmartConsole applications) connected to the source Multi-Domain Server. |
5 |
Install the latest version of the CPUSE from sk92449. Note - The default CPUSE does not support the required Upgrade Tools package. |
Workflow:
Step 1 of 12: Get the required Upgrade Tools on the R80.20.M1 / R80.20.M2 Multi-Domain 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:
The output must show the same build number you see in the name of the downloaded package. Example: Name of the downloaded package:
|
Note - The command
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:migrate_server
"
"Timeout. Failed to retrieve Upgrade Tools package. To download the package manually, refer to sk135172.
Step 2 of 12: On the R80.20.M1 / R80.20.M2 Multi-Domain Server, run the Pre-Upgrade Verifier and export the entire management database
Step |
Description |
---|---|
1 |
Connect to the command line on the current Multi-Domain Server. |
2 |
Log in with the superuser credentials. |
3 |
Log in to the Expert mode. |
4 |
Run the Pre-Upgrade Verifier.
Syntax options:
|
5 |
Read the Pre-Upgrade Verifier output. If you need to fix errors:
|
6 |
Go to the
|
7 |
Export the management database:
Syntax options:
|
8 |
Calculate the MD5 for the exported database files:
|
9 |
Transfer the exported databases from the current Multi-Domain Server to an external storage:
Note - Make sure to transfer the file in the binary mode. |
Step 3 of 12: Perform clean install of the new R80.30 Multi-Domain Server
Perform the clean install in one of these ways (do not perform initial configuration in SmartConsole):
Important:
The IP addresses of the source and target Multi-Domain Servers must be the same. If you need to have a different IP address on the R80.30 Multi-Domain Server, you can change it only after the upgrade procedure. Note that you have to issue licenses for the new IP address. For applicable procedure, see sk74020.
Step 4 of 12: Get the required Upgrade Tools on the new R80.30 Multi-Domain 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:
The output must show the same build number you see in the name of the downloaded package. Example: Name of the downloaded package:
|
Note - The command
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:migrate_server
"
"Timeout. Failed to retrieve Upgrade Tools package. To download the package manually, refer to sk135172.
Step 5 of 12: On the new R80.30 Multi-Domain Server, import the entire management database
Step |
Description |
---|---|
1 |
Connect to the command line on the R80.30 Multi-Domain Server. |
2 |
Log in with the superuser credentials. |
3 |
Log in to the Expert mode. |
4 |
Make sure a valid license is installed:
If it is not already installed, then install a valid license now. |
5 |
Transfer the exported database from an external storage to the R80.30 Multi-Domain Server, to some directory. Note - Make sure to transfer the file in the binary mode. |
6 |
Make sure the transferred file is not corrupted. Calculate the MD5 for the transferred file and compare it to the MD5 that you calculated on the original Multi-Domain Server:
|
7 |
Go to the
|
8 |
Import the management database:
Syntax options:
|
9 |
Make sure that on all Domain Management Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "
If some of the required daemons on a Domain Management Server are in the state "
|
Step 6 of 12: Install the R80.30 SmartConsole
Step 7 of 12: Install the management database
Step |
Description |
---|---|
1 |
Connect with SmartConsole to each Domain Management Server. |
2 |
In the top left corner, click Menu > Install database. |
3 |
Select all objects. |
4 |
Click Install. |
5 |
Click OK. |
Step 8 of 12: 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:
Step 9 of 12: Upgrade the attributes of all managed objects in all Domain Management Servers
Step |
Description |
---|---|
1 |
Connect to the command line on the R80.30 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 "
If some of the required daemons on a Domain Management Server are in the state "
|
5 |
Go to the main MDS context:
|
6 |
Upgrade the attributes of all managed objects in all Domain Management Servers at once:
Notes:
|
7 |
Make sure that on all Domain Management Servers, none of the required daemons (FWM, FWD, CPD, and CPCA) are in the state "
If some of the required daemons on a Domain Management Server are in the state "
|
Step 10 of 12: Test the functionality
Step |
Description |
---|---|
1 |
Connect with SmartConsole to the R80.30 Multi-Domain Server. |
2 |
Make sure the management database and configuration were upgraded correctly. |
Step 11 of 12: Disconnect the old Multi-Domain Server from the network
Step 12 of 12: Connect the new Multi-Domain Server to the network