- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
So while i was away from work for 2 weeks, someone patched our firewall cluster (R81.10) with the latest JHF without installing this JHF on the SMS server.
How bad is this in regards to which inconsistency or issues that can happen?
Can i just continue to install the JHF on the SMS without risk, or do i need to take some things into account?
Whilst not recommended it should be fine for JHFs in most scenarios.
Hi Chris,
Thanks for letting know, but i wonder what the potential downside of this scenario could be.
Can you maybe explain a little bit?
Would depend on the inclusions in a particular JHF but I wouldn't make a habit of doing it in this order, especially if the difference in JHF level is significant.
More generally it likely comes down to compatibility testing, mandating the order somewhat limits the amount of testing needed and hence reduces the potential for issues if that order is adhered to logically.
What take is on the SMS? I always make them the same version. Sometimes there are few days in between and never got an issue. Maybe if you have a plain R81.20 without jumbo it could cause an issue if you upgrade only gateways.
On otherhand I know some people never update SMS and only fw (what I don't recommend).
While all members of a cluster should run the same jumbo (except when you're actively updating the cluster), there's no real dependency between jumbo on the management and jumbo on the firewalls. I've even had some managements stuck at R81.10 with firewalls at R81.20 for a few years. This is a supported configuration.
Supported for/between select major versions as documented and with limitations like not being able to use features of the newer version.
It's perfectly fine to install a JHF on a gateway before the Management. There is no dependency, unless one is specifically stated for using a specific feature.
Often, customers might install a JHF on a specific gateway to resolve some issue, and it's not mandatory to install that JHF on the Management.
We do recommend to install JHFs regularly on the Management to get periodic important fixes, but that's unrelated to the JHF on the gateway.
The below post is from a while back, but explains things pretty well:
https://community.checkpoint.com/t5/Management/Management-JHF-Did-You-Know/m-p/56880
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 28 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION