- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Issue when migrating R77.30 to R80.10 Management S...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue when migrating R77.30 to R80.10 Management Server
Issue when migrating R77.30 to R80.10.
we are doing r77.30 to r80.10 migration with clean installation. Pre verification tool showing no error no warning after resolved all warning.
When we try to import database in clean installed r80.10 device. its failed and showing error with IPS_UPGRADE_TOOL.
We are trying with CPUSE tool to upgrade directly. os upgrade Successful and reboot into R80.10 when its goes to importing database till 50 % its looks good . but suddenly reboot and revert to R80.10
Attached screenshot capture from ssh console during upgrade
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some issues with database are not caught in Pre-upgrade verifier. I got one similar to the one in sk118795. The file $FWDIR/log/cpm_for_cpdb-YYYY-MM-DD-HH-MM-SS.ELG had the answer. In the end someone had added the string "any" in the integer field "icmp code" in a custom service object.
Search the logs for "error","fail", "unable", etc. to find the source of the issue. Post them here if you need.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately, the screenshot you provided doesn't provide a whole lot of information about what's going on.
That said, it's possible the IPS database in R77.30 is corrupted.
There are two ways forward:
1. Use the ipsclean process before upgrading--contact the TAC to get the necessary files and procedure
2. Do an Advanced Upgrade instead of using CPUSE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some issues with database are not caught in Pre-upgrade verifier. I got one similar to the one in sk118795. The file $FWDIR/log/cpm_for_cpdb-YYYY-MM-DD-HH-MM-SS.ELG had the answer. In the end someone had added the string "any" in the integer field "icmp code" in a custom service object.
Search the logs for "error","fail", "unable", etc. to find the source of the issue. Post them here if you need.
