topic Re: R77.30 to R80.40 installer failing in Firewall and Security Management

R77.30 to R80.40 installer failing

Ragnar — Thu, 14 Oct 2021 03:57:28 GMT

HI gurus,

I'm having an issue with building a new cluster member to replace a failed member. I have searched for hours for an article that relates to the problem I am experiencing but have not found a solution.

I have a 4400 appliance which currently looks like it has R77.30 installed.

I have copied the Deployment Agent, Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz and a relevant hotfix into /home/admin.

Installed the DA which was fine.

initially when I tried running the 'installer import local <file>' I was getting an error saying there was no space in /var/log

Now I am getting the following:

gw-3b48fc> installer import local /var/log/upg
_Install_and_Upgrade.tgzort local /var/log/upgrade/Check_Point_R80.40_T294_Fresh_
Preparing package for import. This operation might take a few moments
Note: The selected package will be copied into CPUSE repository
Info: Initiating import of Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz...
Interactive mode is enabled. Press CTRL + C to exit (this will not stop the operation)
Result: Build number of this package is already stored on this machine.
Another build of this package is already stored on the machine.
Please remove all stored builds of this package.

gw-3b48fc> show installer packages all
** ************************************************************************* **
** Connection error. Packages list might be incomplete **
** ************************************************************************* **
** ************************************************************************* **
** Hotfixes **
** ************************************************************************* **
Display name Status
HOTFIX_R77_30 Installed (Legacy)
** ************************************************************************* **
** Majors **
** ************************************************************************* **
Display name Status
Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz Install Failed

Any assistance would be greatly appreciated. I don't need anything that is currently on the appliance I just need to get it to R80.40 to build the config and add it to the cluster

Regards

Re: R77.30 to R80.40 installer failing

S_E_ — Thu, 14 Oct 2021 06:38:10 GMT

Hi,

just trial and error:

Based on our experience, I would install other/newer DA first and reboot the appliance.

And then again the

installer import local ...

installer verify ...

If the issues still appears,

(...it looks like it has R77.30 installed.....)

Try another HF on R77.30 and then procedure again.

Regards

Re: R77.30 to R80.40 installer failing

Boaz_Orshav — Thu, 14 Oct 2021 07:00:50 GMT

It seems that the package is already in the repository and you even tried to install it, hadn't you?

Check_Point_R80.40_T294_Fresh_Install_and_Upgrade.tgz Install Failed

If that is the case, you should not import it again but just try to install

Re: R77.30 to R80.40 installer failing

G_W_Albrecht — Thu, 14 Oct 2021 07:01:31 GMT

According to the Upgrade/Download Wizard

Upgrade from R77.30 to R80.40 :

R80.40 Gaia Fresh Install and upgrade

I would suggest a clean install after a

save configuration <....>

to a file so you can restore the GAiA settings later using

load configuration <....>

save config

Re: R77.30 to R80.40 installer failing

Ragnar — Thu, 14 Oct 2021 23:26:43 GMT

Thanks for all the replies.

I actually got it to successfully install after doing the following:

set fcd revert Gaia_R77.30

Once reverted and rebooted

WinSCP the DA, Install and HF packages across

Installed the DA then install import local <file> which succeeded and is now showing as Available for Install

Regards

Re: R77.30 to R80.40 installer failing

Bob_Zimmerman — Fri, 15 Oct 2021 14:02:07 GMT

In the future, I wouldn't bother with CPUSE. Just use ISOmorphic to image a thumb drive with the version you want to have on the box, then use the thumb drive to wipe and rebuild the box at that version. Doing it that way removes the old version entirely and leaves you with a single "factory default" snapshot at the new version, and a restored instance of that snapshot on the main volume.