- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- R80.10 R80.30 migration
- 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
R80.10 R80.30 migration
Hi all,
Maybe some help on my issue :
I have 2 SG (5200 appliances), 1 SMS and 1 SmartEvent (both on VmWare vm), all of them running on R80.10.
I'd like to migrate to R80.30. For now, i have build up 2 new vms from scratch, with iso R80.30_T200 (with differents IP) and installed the SmartConsole. Added the SmartEvent server.
I thought I could update the 2 SG (HA mode) with CPUSE (R80.30 Fresh Install and Upgrade for SG and Standalone).
Failover the ClusterXL, migrate the standby SG, switch to the active one, migrate, and reactive the ClusterXL.
But, if this is correct, when should I add the appliances to the SmartConsole R80.30 ? And what about the database and licences ?
Thanks for any advice !
PS ; Sorry for my bad english, i'm french 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
1) What about your Security Management Server database? Would you like to export and import it into an R80.30 machine? If so please follow:
There are 4 options:
Upgrading a Security Management Server from R80.20, R80.10, and lower with CPUSE
Upgrading a Security Management Server from R80.20, R80.10, and lower with Advanced Upgrade
Upgrading a Security Management Server from R80.20, R80.10, and lower with Migration
Upgrading Security Management Servers in Management High Availability from R80.20, R80.10, and lower
2) There are also detailed instructions for Cluster upgrade as well.
3) I would also recommend upgrading to R80.40 which is now the official recommended version:
HTH
Tal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Tal,
Thanks for your reply.
1) I've made snapshots and backups of the 2 SG, backups and export of the SMS and SmartEvent, and export of licences.
But when should I import the database to the new SMS ? Before or after SG upgrade ?
2) Would you recomend a clean install or an upgrade of the SG ?
Regarding licences, can I import them on the new SMS, while having the actual still in production ?
I didn't find the answer on the guide.
Thanks a lot,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Everything is documented in the guide I sent. For example you have a section for Upgrading ClusterXL, VSX Cluster, VRRP Cluster with detailed steps:
In any case import database into the new Security Management Server in a lab environment so that you can test to see that it is working properly. Only then proceed with the rest.
Tal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, i will try this. But i'm stuck with migration tools. I can't find the R80.30 to install on the R80.10 SMS.
It says : You are not entitled to download this file.
No luck ...
Thanks anyway !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Here are some news :
I finally upgraded the SMS and SmartEvent with CPUSE (upgrade), no troubles.
I followed with the standby SG of the cluster, but after reboot, connectivity with the SG was lost in SmartCenter.
FW logs shows traffic drop from the SG to the SmartCenter with InitialPolicy. I have changed cluster version to R80.30, published, but still not installed policy (i'm a bit scared ...).
Do you think this is a normal behavior ?
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
InitialPolicy after upgrade on a Security Gateway is normal,
Test communications with the Security Gateway in SmartConsole - see if trust is still established.
