Support Center > Search Results > SecureKnowledge Details
How to manually obtain the latest Upgrade Tools package for upgrade from/to Management Feature Release
Symptoms
  • One of the following messages appear during upgrade:

    "No Upgrade Tools package is installed for version. To download the package manually, refer to sk135172. Restart verify/export/import process using -skip_upgrade_tools_check flag"

    "Timeout. Failed to retrieve Upgrade Tools package. To download the package manually, refer to sk135172. Restart verify/export/import process using -skip_upgrade_tools_check flag"

    "Your Upgrade Tools package is not up-to-date or failed to be retrieved automatically. To download the package manually, refer to sk135172. Restart verify/export/import process using -skip_upgrade_tools_check flag"

    "Failed to retrieve the latest Upgrade Tools package. To download the package manually, refer to sk135172."

Solution

Important Note: For the complete overview and the technical procedure, refer to sk137677

Introduction

Upgrade paths

Source \ Destination R80.20 R80.20.M2 R80.30
R80.20.M1 V V V
R80.20 N/A V X
R80.20.M2 N/A N/A V


In some cases, updating the Upgrade Tools manually to the latest is required to perform the upgrade. The cases are as follow:

  1. Poor Internet connectivity between Management Server and Check Point Download Center.
  2. Management machines that are disconnected from the Internet.
  3. CPUSE -> Software Updates Policy -> "Automatically update Deployment Agent (recommended)" checkbox is cleared.


To manually install the latest version of Check Point Upgrade Tools Package:

  1. Make sure your Deployment Agent is up-to-date. To download latest Deployment Agent, refer to sk92449.

  2. Download the relevant Check Point Upgrade Tools Package from the table below:

    Target Version
    Download Link
    R80.20 GA  (TGZ)
    R80.20.M2 (TGZ)
    R80.30  (TGZ)


  3. Import the Check Point Upgrade Tools Package using the "Import Package" button:


  4. Make sure the package is installed. To do so, from the Expert mode, run:

    cpprod_util CPPROD_GetValue CPupgrade-tools-<version> BuildNumber 1

    where <version> can be R80.20, R80.20.M2 or R80.30 

    Example:

    cpprod_util CPPROD_GetValue CPupgrade-tools-R80.30 BuildNumber 1

    The output must show the same build number you see in the name of the downloaded package.


Advanced Upgrade Only

If you encountered one of the above error messages (see "Symptoms"), use the '-skip_upgrade_tools_check' flag during any migration operation after updating the Upgrade Tools package to the latest.

  • The Verify command should be:

    [Expert@HostName:0]# $MDS_FWDIR/scripts/migrate_server verify -skip_upgrade_tools_check -v <version>

    where <version> can be R80.20R80.20.M2 or R80.30

    Example:

    [Expert@HostName:0]# $MDS_FWDIR/scripts/migrate_server verify -skip_upgrade_tools_check -v R80.20.M2


  • The Export command should be:

    [Expert@HostName:0]# $MDS_FWDIR/scripts/migrate_server export -skip_upgrade_tools_check -v <version> <output tgz file>


  • The Import command should be:

    [Expert@HostName:0]# $MDS_FWDIR/scripts/migrate_server import -skip_upgrade_tools_check -v <version> <export tgz file>

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment