3900 Gateways and R82.10 GA

[Alex-]

OK, we *just* installed a few 3900 in ClusterXL and now ElasticXL is supported.

So, a few questions:

- Will new appliances shipped from now on be shipped with the new GA R82.10 version?

- Will the "special" R82.10 version for ARM series continue to get their distinct hotfixes or will it be recommended to reimage them with R82.10 GA?

- For systems ordered but still in shipping, can we image them with R82.10 GA upon arrival?

- Does the R82 SmartConsole with the latest recommended hotfix support 3900 in ElasticXL now it's supported?

[_Val_]

I think it would make sense to start a new thread for these questions.

[Alex-]

You're the admin. 😉

[PhoneBoy · Accepted solution]

I forked this into a new thread 🙂
Just for clarity, there are two "versions" of R82.10:

• GA1 (shipped specifically for the 3900s without "GA2" functionality, as listed in sk183199)
• GA2 (released for other platforms in sk183506)

Based on past experience, I would expect that we will switch over to R82.10 GA2 shortly.
That doesn't mean there won't be 3900s with GA1 loaded on them in the channel, and they will certainly accept GA2 (either via upgrade or via clean install)--just make sure you use the 3900-specific image in the SK.
While individual fixes may (still) be available for GA1, I would expect JHFs to be released only for GA2.

[Alex-]

We received a mail from Check Point with clarifications.

R82.10 Take 271 (the GA1) won't be further developed.

R82.10 Take 464 (the GA2) is recommended for replacement of the Take 271 and will received future hotfixes.

[PhoneBoy]

I received a similar email internally: Please note that all future Jumbo Hotfix (HF) releases, including bug fixes and feature enhancements, will be provided only for R82.10 T464.

[Nenad_Odic]

great and what about situation like this,i have clusterxl of two 3970 with r82.10 take 271 and SMS vm that is r82 take 60.

i can upgrade my GW s  but what about the mgmt?

so in documents there is this :

Alignment of R82 JHF Takes

R82 Jumbo HFA Take #	Alignment To R82.10
R82 JHF Take 43	R82.10 Take 464

So if i want to upgrade SMS i have to uninstall take 60 and 44 to be aligned for this upgrade?

Or just to install another VM and export import db.

Or just to wait for alignment to be reached?

please advise, i got these warnings at verifying update on my current sms r82 take 60:

R82.10 Gaia Clean Install and upgrade

Recently downloaded

24-Dec-2025 | Available for install

R82.10 Gaia Clean Install and Upgrade For Security Gateway, Security Management, Standalone and Scalable Platform.

Package Name

Check_Point_R82.10_T464_Gaia_Install_and_Upgrade.tgz

Package Size

5264.4 MB

Upgrade tool:

999001080

Verification results

3 Warnings | Upgrade is allowed

Verification warnings:

1.  
2. Policy Auditor features will be deprecated and unavailable in R82.10 and higher. If you require Policy Auditor functionality, do not upgrade beyond R82.
3. A Jumbo Hotfix Accumulator (HFA) Take 60 is installed on this server. Read more about the Jumbo (HFA) that aligns with your current Jumbo (HFA) in sk164258

[PhoneBoy]

You can upgrade the gateways.
The management is good as-is.
The take mentioned is a minimum (meaning all future JHFs of the same release will be aligned).

[Alex-]

We have some 3900 shipped with the GA1 installed as ClusterXL, and as they're not yet in production, we took the effort to switch them to ElasticXL and this is how it went:

1. Install the latest CPUSE for ARM devices on all systems if required
2. Ensure both systems running Take 271 run JHF Take 22 or the verifier will fail
3. Import the Clean Install and Upgrade package in CPUSE
4. Perform a Clean Install, management and credentials will be preserved
5. FTW the device as ElasticXL
6. Establish SIC, install policy
7. Repeat 1-4 for second node, don't perform FTW
8. Node 2 will appear as REQUEST TO JOIN
9. Add it in the stack from the first node, run Insights to monitor the process
10. From there, the installation stalled with messages from the second node: "Not enough space to create Lightshot"
11. Delete the lightshot on the second node, seemingly created for the upgrade from Take 271 to Take 464
12. Reboot the node, it will come back as REQUEST TO JOIN
13. Remove the second node from the Primary ElasticXL and add it again
14. Process completed and after reboot, the second node was Active in the ElasticXL stack

In short, when you Clean Install to the Take 464, delete the created lightshot before creating the whole stack. You won't revert to Take 271 anyway since it was the launch version which won't be developed any further.