VSX Upgrade from R77.30 to R80.40

[artem_kruhlyi]

Hi All,

We are planning to upgrade our VSX cluster from R77.30 to R80.40. However, I'm a bit confused. When I'm using upgrade wizard, I see only R80.30 as possible version to upgrade. Is it possible to upgrade from R77.30 directly to R80.40 with CPUSE? Which image should I use?

[Mike_A]

I don't think VSX is available for R80.40. 

[Maarten_Sjouw]

Since R77 VSX is part of the maintrain, there is no version since then that does not have VSX embedded. The only exception being GAIA Embedded.

[shlomip]

@artem_kruhlyi ,

For VSX and open Server upgrade to R80.40 please see R80.40 Jumbo Hotfix sk

[artem_kruhlyi]

Hi @shlomip ,

Big thanks for your reply!

I thoroughly read R80.40 Jumbo Hotfix sk and, especially, this: "For an Existing Security Gateway running on Open Servers, a Blink image consisting of R80.40 GA image (Take 294) and R80.40 Jumbo Hotfix is available in the Download section below. For VSX and Standalone configurations, see sk168114."

Also I took a look at sk168114 and found this: "ON a VSX environment, refer to "Minimal Effort" section in R80.40 Installation and Upgrade Guide and follow the Clean install option."

So does it mean that CPUSE upgrade is impossible for R80.40?

Do I have only one option to follow Clean install option in "Minimal Effort" section? Will Clean install with CPUSE transfer all config to new version?

[Bob_Zimmerman]

I've worked with VSX since around 2006, including several years as a VSX specialist in Check Point's call center. Personally, I wouldn't use CPUSE to upgrade VSX. The clean install process is the same as the process to replace a failed cluster member with the addition of 'vsx_util upgrade' on the management. Local config won't be transferred between the members, but VSX generally doesn't have a whole lot of that (and you should be backing it up anyway in case a member fails). Interface and routing config is pushed down from the management, and will be pushed to the new member. It works and gives you a chance to practice replacing a failed member so if it happens, you know everything will go exactly how you expect. Here's the general process:

1. Go through initial configuration. I build config_system files. If you used config_system to build the original, you can use the same file to build the replacement.
2. If you change the volume sizes from their defaults, do it here.
3. Do any OS-level configuration for VS 0. For me, this is bonds, SNMP, and central authentication.
4. 'vsx_util reconfigure' on the management. This establishes SIC and pushes down the VSX config (building the contexts and interfaces) and policies.
5. Do any remaining local configuration. Most notably, any dynamic routing has to be set up after the 'vsx_util reconfigure', because that's when the contexts are built on the firewall. Manual proxy ARP outside VS 0 involves a local.arp file per VS doing manual proxy ARP.

[shlomip · Accepted solution]

@artem_kruhlyi ,

Yes. Specifically for Open Server and VSX the valid option is only Clean Install

[artem_kruhlyi]

Hi @Bob_Zimmerman and @shlomip ,

Many thanks for your answers!

I understood that Clean Install is only one valid option for upgrade VSX to R80.40. Also it's clear that Clean Install is preferable from many points of view.

However, I was thinking about CPUSE upgrade because I would like to perform Zero Downtime or even MVC upgrade. Keeping connectivity and rapid upgrade are vital in my case. If I went Clean Install it would make the upgrade process much more complicated.

So maybe I might go with CPUSE upgrade from R77.30 to R80.30 as it's a valid option for R80.30

[Bob_Zimmerman]

A "Zero Downtime" upgrade is just rebuilding one member at the new version, pushing policy, then shutting down the second member. That's what the VSX clean install method gets you.

CPUSE doesn't seem to have anything to do with MVC. You just need to get a member to R80.40. It will go to Ready state because it sees an older CCP version. Enable cross-version sync with 'cphaconf mvc on', wait a few minutes, then you should be good to fail over. It sounds just like the old "Connectivity Upgrade" or "Full Connectivity Upgrade" methods, just with a different command. It's definitely possible to do this with a clean install.

[artem_kruhlyi]

Hi @shlomip,

I have one more question and maybe you can help me.

How can I reach VSX at OpenServer after Clean Install, if I don't have access to server hardware management console?

[Bob_Zimmerman]

Depends on how you do the clean install. Most clean install methods I know of involve either being physically at the machine (with a burned disc or thumb drive), or having access to the server's LOM.

My memory is a "clean install" done with CPUSE leaves a little of the configuration in place (mostly which interface is for management, what IP it has, and the default route). I would try this in a VM several times before trying it for real on a remote system.