topic Re: Upgrade from 77.30 to 80.10 problem in General Topics

Upgrade from 77.30 to 80.10 problem

Sergey_Popov — Mon, 31 Jul 2017 09:43:48 GMT

Hello. We have issue with upgrade of our software security gateways from 77.30 to 80.10.

I tried to make uprade from CUPSE, Smart Update and from CLI. I have an error

However it is file from official checkpoint site, md5 hash is right.

How can I upgrade the sistem with some custom way?

Re: Upgrade from 77.30 to 80.10 problem

Eyal_Rashelbach — Mon, 31 Jul 2017 10:42:54 GMT

Hi Sergey,

I asked our Support to contact you

Best regards

Eyal Rashelbach

R80 Desk Manager | Solution Center | Check Point Software Technologies

Re: Upgrade from 77.30 to 80.10 problem

Federico_Meine1 — Mon, 31 Jul 2017 12:52:12 GMT

Sergey,

I only had bad experiences with such an upgrade (R77.30 to R80.x).

First make sure that your appliance suports R80.10, make snapshot and backup just in case, save show configuration from gateway, fresh install R80.10, use the same SIC as before, paste show configuration, install policy.

Regards,

Re: Upgrade from 77.30 to 80.10 problem

Sergey_Popov — Mon, 31 Jul 2017 12:59:33 GMT

Is there any way to upgrade without fresh install?

We have some backup scripts on OS, so we don’t want to lose it during fresh installation.

Re: Upgrade from 77.30 to 80.10 problem

PhoneBoy — Mon, 31 Jul 2017 14:05:00 GMT

I would recommend engaging with TAC to troubleshoot what is going on in this case.

Re: Upgrade from 77.30 to 80.10 problem

Pedro_Espindola — Mon, 31 Jul 2017 17:08:13 GMT

Hello Sergey,

I solved this same problem by updating CPUSE Deployment Agent to the latest build and installing the latest Jumbo Hotfix Accumulator for R77.30.

If the Deployment Agent doesn't automatically upgrade when you go to the page in Gaia Web Portal, try to do it manually in CLI: sk92449

Re: Upgrade from 77.30 to 80.10 problem

Sergey_Popov — Wed, 02 Aug 2017 06:27:16 GMT

Thank you. Everything works fine after Deployment Agent upgrade.

Re: Upgrade from 77.30 to 80.10 problem

Bryce_Myers — Thu, 17 Aug 2017 20:26:11 GMT

Great - and with most updates/upgrades moving to CPUSE - if you have a configuration check script, I would recommend making sure your Auto-update is enabled on the Deployment Agent.

clish -c "show installer policy periodically-self-update"

And ensure that is set to "on"

You can also use

cpvinfo /opt/CPda/bin/DAService | grep Build | grep -Po "[0-9]+"

To look at what version of Deployment Agent you're running.