cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post
BLD
Nickel

Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

We are trying to migrate all the configurations in our current R80.10 open server to a new box with R80.30 (open server).

Spent already a few days with all found instructions to no avail. 

We installed the R80.30 upgrade tools in the 80.10 security gateway. The package is installed at /opt/CPupgrade-tools-R80.30

If we run from that path "./migrate export filename.tgz" we get an error.  In the error logs we see that it attempts to run the "pre_upgrade_verifier" (why?). But the package does not contain the pre_upgrade_verifier

[20 Sep 11:02:05] [ExecCommandGetOutput] Going to execute command: '"/opt/CPupgrade-tools-R80.30/bin/././pre_upgrade_verifier" -p "/opt/CPsuite-R80/fw1" -c 6.0.4.8 -t 6.0.5.0'
[20 Sep 11:02:05] [ExecCommandGetOutput] ERR: Command completed with error code -1
[20 Sep 11:02:05] ..<-- ExecCommandGetOutput
[20 Sep 11:02:05] [PreupgradeVerifierRunner::exec] ERR: Preupgrade verifier had failed
[20 Sep 11:02:05] [PreupgradeVerifierRunner::exec] Preupgrade verifier's output:
-------------------------------------
"/opt/CPupgrade-tools-R80.30/bin/././pre_upgrade_verifier" -p "/opt/CPsuite-R80/fw1" -c 6.0.4.8 -t 6.0.5.0: No such file or directory
-------------------------------------

 

If we the copy the pre_upgrade_verifier from "$FWDIR/bin/upgrade_tools/" to "/opt/CPupgrade-tools-R80.30" and we run "migrate" again, pre_upgrade_verifier obviously fails because it does not support being run from 6.0.4.8 to 6.0.5.0

We then tried running "/opt/CPupgrade-tools-R80.30/scripts/migrate_server export -skip_upgrade_tools_check -v R80.30 <output tgz file>". After a few minutes running, it ends with an error, but no indication of a log or anything similar with a description of the error. Disk space has been reduced by 200MB,

Can anybody help with this? Thanks!

0 Kudos
1 Solution

Accepted Solutions
Employee++
Employee++

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

Hi

 

Just making sure you download the correct Upgrade Tools - this image is from R80.30 home page:

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...

 

You should R80.30 Management Server Migration Tool (not the second option - Upgrade Tools package for... )

Upgrade Tools.jpg

 

HTH

Tal

View solution in original post

6 Replies
Admin
Admin

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution
Did you download the latest migration tools from the R80.30 SK?
I usually decompress the tools tarball in a sudirectory of /home/admin FWIW.
0 Kudos
Highlighted
BLD
Nickel

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

Yes. Latest R80.30 upgrade tools. Installed via Gaia and package was placed in path mentioned in our post

0 Kudos
Employee++
Employee++

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

Hi

 

Just making sure you download the correct Upgrade Tools - this image is from R80.30 home page:

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...

 

You should R80.30 Management Server Migration Tool (not the second option - Upgrade Tools package for... )

Upgrade Tools.jpg

 

HTH

Tal

View solution in original post

BLD
Nickel

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

We had used the other one, which is also described as : "Upgrade Tools Package for R80.30" and has newer dates...  Very confusing.

We will give it a try. Thanks Tal!

 

Boris

 
 
0 Kudos
BLD
Nickel

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

Hello Tal.

I can confirm this worked. Configurations seem to have migrated succesfully.

A suggestion:

In the documentation it says we must get the latest versions of "UPGRADE TOOLS" in both servers. 

But when we go to the download page, what we actually have to download is called "MANAGEMENT SERVER MIGRATION TOOL" and it is easy to make the mistake of downloading "UPGRADE TOOLS PACKAGE FOR MANAGEMENT RELEASE FEATURES.

A simple renaming in the documentation or in the download page could save some significant hours of work (and support time).

Best regards,

Boris

0 Kudos
Employee++
Employee++

Re: Migrate Standalone gateway R80.10 to new R80.30 in different box (Open Server)

Jump to solution

Hi Boris

You are right and we are now working to fix this and other issues so that it will be simpler.

Thanks for the useful comments.

Tal

0 Kudos