Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
the_rock
Legend
Legend
Jump to solution

Migrate_server issue on Azure CP management server

Hey guys,

Apologies I dont have exact error I received when doing migrate_server verification and then export (will update tomorrow when on my corporate laptop), but I wanted to confirm something. Are there any limitations when doing this process on CP management server in Azure? I dont believe there would be, as I followed exactly what below sk outlines.

https://support.checkpoint.com/results/sk/sk135172

I downloaded R81.20 upgrade tools tgz package (though when I tried installing it on R81 Azure server, said newest package was already there) and idea is to do migrate export on R81 and import it into my R81.20 lab mgmt server.

I will upload logs and file as soon as I have access to it, but if anyone knows of any limitations doing this process on Azure side, please be free to share it in the meantime.

Its also worth mentioning I had done this many times for onprem mgmt server and never had an issue, but never on Azure, this was the first time.

Thanks a lot as always!

Andy

0 Kudos
1 Solution

Accepted Solutions
the_rock
Legend
Legend

This is the command that worked, will see if it imports into R81.20 lab

Andy

[Expert@prd9cpmgmt01:0]# $MDS_FWDIR/scripts/migrate_server export -skip_upgrade_tools_check --ignore_warnings -v R81.20 /var/log/Export_for_Upgrade_from_R81_to_R8120.tgz

View solution in original post

0 Kudos
5 Replies
the_rock
Legend
Legend

Quick update. I looked over generated html file and showed below, so I used the flag mentioned to see if it works (running it now)

Pre-Export Verifications Succeeded with Warnings

To export the database, address all the warnings or run the --ignore_warnings flag

 

  •       Upgrade Tools

    • Upgrade Tools Build Number  R81.20 997000713
  •       Logs

    • There are no upgrade logs because pre-export verifications detected configuration issues. Export cannot start until you fix these issues.

     

    [Expert@prd9cpmgmt01:0]# grep -i fail /opt/CPsuite-R81/fw1/log/upgrade_report-2023.09.21_20.08.21.html
    <h1 id="status">Failed to Load the Report</h1>
    statusHeader.innerHTML = "Failed to parse the upgrade data";
    (isOperationFinished(phases.import, dataAllDomains.status)) && isOperationFailed(phases.export, dataAllDomains) )
    // export verification in failed
    // export failed
    statusHeader.innerHTML = "Database Export Failed";
    let failedDomainExport = getFailedDomain(phases.export)[1];
    if (failedDomainExport != "") {
    openBtnsQueue.push(failedDomainExport + getPhaseWithUppercase(phases.export));
    // import verification in failed
    //import failed
    statusHeader.innerHTML = Upgrade_or_Migration + " Failed";
    // open failed domain section by default
    let failedDomainImport = getFailedDomain(phases.import)[1];
    if (failedDomainImport != "") {
    openBtnsQueue.push(failedDomainImport + getPhaseWithUppercase(phases.import));
    // upgrade failed
    domainFailedName = getFailedDomain(phase)[0];
    if (domainFailedName == "") {
    return getDescriptionForGeneralFail(dataAllDomains.description);
    return `Failed: ` + Upgrade_or_Migration + ` of "` + domainFailedName + `".<br>For more details see upgrade logs below`;
    // find the domain in which upgrade had failed
    function getFailedDomain(phase) {
    let isFailedDomain = !isOperationSucceeded(phase, dataPerDomain) && (isOperationFinished(phase, dataPerDomain.status) ||
    if (isFailedDomain) {
    function getDescriptionForGeneralFail(description) {
    description = description.replace(/(failed)/ig, `<span style="color:red;font-weight: bold;">$1</span>`);
    progressText.innerHTML = "Canceled due to a failure in other domain";
    progressText.innerHTML = "Canceled due to a failure in other domain";
    if (isOperationFailed(phase, dataAllDomains)) {
    } else if (dataAllDomains.importPostUpgradeStatus == "IMPORT_POST_UPGRADE_FAILED") {
    // failed
    } else if (dataAllDomains.exportPostUpgradeStatus == "EXPORT_POST_UPGRADE_FAILED") {
    // failed
    if (getFailedDomain(phase)[1] == dataPerDomain.domainId) {
    function isOperationFailed(phase,dataObject) {
    return phase == phases.post_upgrade || phase == phases.info || getFailedDomain(phase)[0] != domainName || ( isEmpty(dataAllDomains.description) && isEmpty(dataPerDomain.description) );
    // in case this is a failed domain and has no end time, show the end time of the general upgrade
    [Expert@prd9cpmgmt01:0]#

     

0 Kudos
G_W_Albrecht
Legend Legend
Legend

Maybe run_cpmdoc.sh will tell you more ?

CCSE / CCTE / CTPS / CCME / CCSM Elite / SMB Specialist
0 Kudos
the_rock
Legend
Legend

This is the command that worked, will see if it imports into R81.20 lab

Andy

[Expert@prd9cpmgmt01:0]# $MDS_FWDIR/scripts/migrate_server export -skip_upgrade_tools_check --ignore_warnings -v R81.20 /var/log/Export_for_Upgrade_from_R81_to_R8120.tgz

0 Kudos
the_rock
Legend
Legend

Was able to import fine into R81.20 lab, just did --ignore_warnings flag again. Thanks guys!

 

Andy

0 Kudos
Sanjay_S
Advisor

Hi All,

Can we use the new IP for the domain as my Lab doesn't have the VLAN extended. Also need to test this first before completely migrate it from MDS to the new SMS. 

> Can we use different IP to the domain we import in the new SMS?

For example if we have the CMA IP: 10.10.1.100 in the existing one. Do we need to use the same IP or can we setup the new one in new SMS.

> Can we rename the CMA name while we import to the new SMS?

Please suggest.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events