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

CPUSE build 1669 - What is "New HFoHF behaviour"?

Jump to solution

SK contains a new CPUSE version build 1669:

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...

What is new states:

  • New HFoHF behaviour
  • Support upgrades to R80.30

What is meant by "New HFoHF behaviour"?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Employee+
Employee+

Re: CPUSE build 1669 - What is "New HFoHF behaviour"?

Jump to solution

First of all - your guesses are are very good and almost accurate.

Second - 1669 is currently on gradual deployment so the SK92449 will be updated with exact HFoHF documentation when it gets to 100% GA (will take around a week).

Now to the point: The behaviour in the last years was that when a new HF build was installed, the old one was uninstalled as a first step (automatically by DA).

However, this caused issues to customers who got anothe HF in the middle which was included in the new build. The DA could not uninstall the old build since something was installed on top of it.

The new behaviour: The new take will be installed on top of the old one even if there us an HF in the middle as long as the HF in the middle is included in the new build.

Another advantage: Now you can uninstall last take and get back to previous one (since we didn't really uninstalled it) while untill now you had to uninstall the new take and then install manually the old one.

Hope it clears things and I'll be glad to get feedbacks by email.

Thanks

View solution in original post

3 Replies
Highlighted

Re: CPUSE build 1669 - What is "New HFoHF behaviour"?

Jump to solution

Just a guess but maybe "Hotfix over Hotfix"?  The ability to install a new hotfix take number on top of an older one without CPUSE having to uninstall the old hotfix take first?

 

Book "Max Power 2020: Check Point Firewall Performance Optimization" Third Edition
Now Available at www.maxpowerfirewalls.com
0 Kudos
Highlighted

Re: CPUSE build 1669 - What is "New HFoHF behaviour"?

Jump to solution

Hmmmm - initial behaviour was: manually uninstall HF before installing new HF version. Then we had Jumbo HF behaviour: Installing newer Jumbo started by uninstalling older Jumbo Take. So what we would all need is a behaviour for the situation when e.g. part of a new HF has already been installed in a newer version - for Jumbo Takes, it would be nice to leave out only the package in question from install instead of cancelling the HF install...

But this is only my thought !

0 Kudos
Highlighted
Employee+
Employee+

Re: CPUSE build 1669 - What is "New HFoHF behaviour"?

Jump to solution

First of all - your guesses are are very good and almost accurate.

Second - 1669 is currently on gradual deployment so the SK92449 will be updated with exact HFoHF documentation when it gets to 100% GA (will take around a week).

Now to the point: The behaviour in the last years was that when a new HF build was installed, the old one was uninstalled as a first step (automatically by DA).

However, this caused issues to customers who got anothe HF in the middle which was included in the new build. The DA could not uninstall the old build since something was installed on top of it.

The new behaviour: The new take will be installed on top of the old one even if there us an HF in the middle as long as the HF in the middle is included in the new build.

Another advantage: Now you can uninstall last take and get back to previous one (since we didn't really uninstalled it) while untill now you had to uninstall the new take and then install manually the old one.

Hope it clears things and I'll be glad to get feedbacks by email.

Thanks

View solution in original post