Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
chvgms
Explorer

Upgrade from R80.10 from 80.40

Hi,

what is the recommended best practice to upgrade from R80.10 to R80.40 which is running in ClusterXL model.

 

Thanks,

Sridhar

0 Kudos
8 Replies
PhoneBoy
Admin
Admin

Best to follow the install and upgrade guide: https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_Installation_and_Upgrade_Gui...
There are also several threads on CheckMates about this as well.
If you can provide more details about your environment, we can provide more specific advice.

the_rock
Authority
Authority

Personally, I always follow below document, and same applies to R80.40. Zero downtime upgrade, in my opinion, is the best option out there.

 

https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_Installation_and_Upgrade_Gui...

0 Kudos
genisis__
Advisor

Believe I've replied to a similar question in the forum, but for my pennies worth, I would do a clean build on standby member, ensure mvc is turned on and failover after SIC/Policy push etc has been done, including checking to ensure you have an active/standby status.

 

0 Kudos
the_rock
Authority
Authority

O yea, good point for mvc...I forgot about that, though I never had to change that ever before, but still...better be safe than sorry : )

0 Kudos
genisis__
Advisor

I believe the MVC pretty much does the same as changing the ccp mode, but its just easier to do.  I've done a number of three node clusters during the working day using this (R77.30 to R80.40) and its worked a treat.

0 Kudos
RamGuy239
Advisor

Utilising multi-version clustering is the same as doing a full connectivity upgrade and not a zero-downtime upgrade? The only difference is that mvc has replaced cpha cu making it even easier and more seamless compared to before.

I would always go with full connectivity upgrade over a zero-downtime upgrade. It's basically you typing cphacu start as one additional step and it ensures that you will have all the traffic synchronised before doing the failover.

https://sc1.checkpoint.com/documents/R80.30/WebAdminGuides/EN/CP_R80.30_Installation_and_Upgrade_Gui...


But this information is out-of-date. On R80.40+ this is known as multi-version clustering on R80.40+ and has replaced full connectivity upgrade entirely. But it achieves the same thing and is the recommended approach. It has just been made smart, easier and more seamless.

https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_Installation_and_Upgrade_Gui...


Can't really think of any reason why someone would go with zero downtime upgrade over multi-version clustering upgrade / full connectivity upgrade, to be honest.

@chvgms You have to remember that R80.40 comes with 3.10 kernel and a new XFS filesystem. For you to get the new filesystem you will have to do a full re-install for ISO/USB instead of doing a cpuse or blink upgrade. If you do the upgrade you will be stuck with EXT3 filesystem. A full re-install is the only way to get it. A good thing to keep in mind.

the_rock
Authority
Authority

I think argument can be made for both methods, but I do see your point...its definitely true that with FCU, all connections are maintained and synced.

0 Kudos
genisis__
Advisor

Basically use MVC. From a filesystem prospective, yes doing a clean build gives you XFS, but on a gateway this is not really that important from what I can tell.  The main thing is the kernel update.

I would still do a clean build anyway, if the option is available to do so.