- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
According to the Release Notes, support for using an 80.10 Management server managing 80.20 security gateways is possible. I don't see anything in the sk116380 jumob hotfix article about this though. So is it already doable, or do I need to wait for some particular Take?
You can maintain a R80.10 Security Management Server or Multi-Domain Security Management without upgrading and manage R80.20 Security Gateways:
The reason I ask is because we just upgraded our management to 80.10 a month or two ago. We now have a new site that wants to upgrade their current 77.30 gateway, and I want to make an informed decision on whether to have them install 80.10 or 80.20 as a fresh install. I understand that we wouldn't get a number of 80.20 benefits while it is managed from an 80.10 but for future upgrading I'd rather not have to go back over all the gateways we have to get from 80.10 to 80.20. Make sense?
It WILL be supported
We have to release a jumbo for R80.10 which after we release it, this R80.10 (using the jumbo) could manage the R80.20. As soon as this jumbo is released, the SK will be updated with the relevant jumbo number. The jiumbo is expected in few weeks.
STILL NOTE: Using R80.10 to manage R80.20 means that the functionality supported will be R80.10 and new features of R80.20 will not work.
Very good question indeed! lets see if someone has wondered into this option already
That doesn't make sense, when you had r77.30 mgmt you could not manage r80.10 gw, when you have r80.10 mgmt you cannot manage r80.20..
It is possible, as mentioned here by Ross Pember but it does not give you the R80.20 features for the gateway.
I just wanted to hear some "real life" experiences from customers, not CP
It WILL be supported
We have to release a jumbo for R80.10 which after we release it, this R80.10 (using the jumbo) could manage the R80.20. As soon as this jumbo is released, the SK will be updated with the relevant jumbo number. The jiumbo is expected in few weeks.
STILL NOTE: Using R80.10 to manage R80.20 means that the functionality supported will be R80.10 and new features of R80.20 will not work.
One of the reasons I feel the need to stay at 80.10 on the management server side regardless of the feature limitation for the gateways is because we use a separate log server located in Azure, and Checkpoint recommends (or states) that the management versions should be the same. As there is no approved upgrade path for Checkpoint services in Azure we are stuck at 80.10 there. If that is not truly a limitation, I would be more inclined to upgrade the management server to 80.20 sooner.
1. R80.20 on public cloud (like Azure) will be released on the new linux kernel (because we want one image and the gw in some cases of modern cpu in cloud needs the new linux). Though for management, its working, we want to simplify and have one version for all instance type in public cloud
2. The r80.20 with new linux kernel for public cloud is in early availability so you are welcome to join the EA and get it. The GA of this variant is expected in November
3. If you do not want EA, wait till around the end of the month, for the r80.10 jumbo... installing that jumbo on r80.10 will enable you to manage r80.20 gw’s going forward (we had to wait for the r80.20 gw ga to complete the r80.10 jumbo to manage r80.20)
I hope this helps understand the alternatives
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY