🔧 R81.20 → R82+: A Practical In-Place Upgrade Guide for Check Point Gateways

[samirshah1]

Planning a Check Point Security Gateway upgrade from Gaia R81.20 to R82+?

This Method of Procedure provides a structured upgrade path covering preparation, backups, gateway upgrades, Jumbo Hotfix installation, MVC considerations, validation, and rollback.

A practical reference for engineers looking to make the upgrade process more predictable and easier to execute.

[todd]

Thank you for sharing the detailed upgrade steps. This is extremely helpful!

[C0rwin]

Thanks. Nice but not complete ex.::

- installation policy order - Access Policy first, then TP

- disable MVC at the end

BR

Daniel

[samirshah1]

In my opinion, disabling MVC is optional if you plan to upgrade in the future

[emmap]

MVC only needs to be enabled on the upgraded member in a cluster upgrade, so having it remain on after an upgrade isn't relevent to a future version upgrade. Also it's in the upgrade documentation to disable it after the upgrade, and HCP does (or used to) throw a warning on it being left enabled.

[Alex-]

What's the impact of leaving MVC on? I've seen installs where it's permanently turned on. No impact on anything reported.

Maybe some extra processing at the clustering level?

[emmap]

I've never seen any issues with leaving it enabled - and basically all R81.20 installs have it enabled because the JHF turns it on. So it doesn't seem to cause any issues that I have noticed. Caveat: Yet.

[Christopher_Ham]

Yes and no, as far as order AP goes first, MVC is optional. 

Aside from that, the document is very thorough; the best part is CDT when it works, and it's usually my first option