Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Iron

migrate R75.40 to R80.30 Failed

Jump to solution

migrate from R75.40 to R80.30

Export succeeded with migrate tool

Import to R80.30 failed and FWM process does not start

Contents of migrate log

/opt/CPshrd-R80.30/log/migrate-xxxx

[14 Oct 1:52:24] [ExecCommandGetOutput] Going to execute command: '/opt/CPsuite-R80.30/fw1/bin/upgrade_phase -d 41e821a0-3720-11e3-aa6e-0800200c9fde -s end'
[14 Oct 2:10:51] [ExecCommandGetOutput] ERR: Command completed with error code 4
[14 Oct 2:10:51] ..<-- ExecCommandGetOutput
[14 Oct 2:10:51] [CommandRunner::exec] Command's output:
-------------------------------------
Failed to upgrade phase
-------------------------------------
[14 Oct 2:10:51] [CommandRunner::exec] ERR: Command execution had failed
[14 Oct 2:10:51] .<-- CommandRunner::exec
[14 Oct 2:10:51] <-- ConditionalExecutor::exec
[14 Oct 2:10:51] [ActivitiesManager::exec] ERR: Activity 'ConditionalExecutor' failed
[14 Oct 2:10:51] [ActivitiesManager::exec] WRN: Activities execution finished with errors
[14 Oct 2:10:51] [ActivitiesManager::exec] WRN: Activities 'ConditionalExecutor' have failed
[14 Oct 2:10:51] [ActivitiesManager::exec] Designated exit code is 1
[14 Oct 2:10:51] --> CleanupManager::Instance
[14 Oct 2:10:51] <-- CleanupManager::Instance
[14 Oct 2:10:51] --> CleanupManager::DoCleanup
[14 Oct 2:10:51] [CleanupManager::DoCleanup] Starting to perform cleanup
[14 Oct 2:10:51] .--> DirCleaner::exec
[14 Oct 2:10:51] [DirCleaner::exec] Going to remove directory '/opt/CPsuite-R80.30/fw1/tmp/migrate/'
[14 Oct 2:10:51] .<-- DirCleaner::exec
[14 Oct 2:10:51] .--> ImportFailureMarker::exec
[14 Oct 2:10:51] [ImportFailureMarker::exec] Checking if cleaner is active
[14 Oct 2:10:51] [ImportFailureMarker::exec] Cleaner is active, starting cleanup
[14 Oct 2:10:51] [ImportFailureMarker::exec] Checking migrate's exit code
[14 Oct 2:10:51] [ImportFailureMarker::exec] Migration had failed, creating a marker file
[14 Oct 2:10:51] ..--> UpgradeMacroReplacer::Instance
[14 Oct 2:10:51] ..<-- UpgradeMacroReplacer::Instance
[14 Oct 2:10:51] [ImportFailureMarker::exec] Created a marker file
[14 Oct 2:10:51] .<-- ImportFailureMarker::exec
[14 Oct 2:10:51] [CleanupManager::DoCleanup] Completed the cleanup
[14 Oct 2:10:51] <-- CleanupManager::DoCleanup

 

end

 

Please tell me the solution

 

 

1 Solution

Accepted Solutions
Highlighted

Re: migrate R75.40 to R80.30 Failed

Jump to solution

Hi @mukai,

The error messages look a bit like wrong migration tools.

A short question! Do you use the R80.30 migration tools for migrate export? 

Solution:

1) Download R80.30 migration tools to your R75.40 SMS

2) Execute the R80.30 migrate export tool on your R75.40 SMS

3) Import the migrate export file on your R80.30 SMS.

If this does not work, make an intermediate step to R77.20 or better R77.30.

View solution in original post

Tags (1)
6 Replies
Highlighted
Admin
Admin

Re: migrate R75.40 to R80.30 Failed

Jump to solution
Best bet is to involve the TAC.
It's possible you may need to get a particular hotfix and apply a specific procedure to make this succeed.
0 Kudos
Highlighted
Iron

Re: migrate R75.40 to R80.30 Failed

Jump to solution

thank you for your comment
Since there is no support contract, I will investigate a little more.
Is there a valid source of information?

0 Kudos
Highlighted
Employee++
Employee++

Re: migrate R75.40 to R80.30 Failed

Jump to solution

Perhaps @Ofer_Barzvi can shed some light on this?

Highlighted
Iron

Re: migrate R75.40 to R80.30 Failed

Jump to solution

Self-less

I tried many things and did the following:

・Upgrade from R75.40 to R77.20

・Delete unnecessary policy files with the cp_merge delete_policy command

・With reference to sk120119, delete rule A__xxxxxxx in anti_malware_rulebases_rules

I was able to import

cui message




The import operation completed successfully.
Do you wish to start Check Point services? (y/n) [y]?

 

It's difficult to migrate

Highlighted
Admin
Admin

Re: migrate R75.40 to R80.30 Failed

Jump to solution
You will definitely have issues if you do not update the various Threat Prevention signatures prior to taking the export/import.
0 Kudos
Highlighted

Re: migrate R75.40 to R80.30 Failed

Jump to solution

Hi @mukai,

The error messages look a bit like wrong migration tools.

A short question! Do you use the R80.30 migration tools for migrate export? 

Solution:

1) Download R80.30 migration tools to your R75.40 SMS

2) Execute the R80.30 migrate export tool on your R75.40 SMS

3) Import the migrate export file on your R80.30 SMS.

If this does not work, make an intermediate step to R77.20 or better R77.30.

View solution in original post

Tags (1)