- Products
- Learn
- Local User Groups
- Partners
- More
What's New in R82.10?
Watch HereWhen the Agents Attack
A Live Look at Agentic Exposure Validation
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
CheckMates Fest
In the R82 Scalable Platforms Administration Guide's section on ElasticXL, the licensing section (Installing licenses on ElasticXL Cluster Members) has an instruction which confuses me a bit:
In Check Point User Center, generate a license for each appliance using these parameters:
I don't see anywhere in the User Center to use the MAC address when generating a license. Is this just saying to generate a local license for each member to the same IP (magg1)? Or is there some new process to generate the licenses which I'm missing?
Each node needs its own local license using the same IP and installed using the cplic put command.
Thats what it sounds like to me, local license on each member for same IP. but I would double check with Account services, to be sure.
Andy
That's the way I interpret it, but agree it's a bit confusing since the only time I've seen a license generated with a MAC was with a "permanent" license.
Each node needs its own local license using the same IP and installed using the cplic put command.
Each gateway requires a local license.
You should always use the Sync IP address for the locale license:
GW1_1 192.0.2.1
GW1_2 192.0.2.2
GW1_3 192.0.2.3
The MAC address corresponds to the physical appliance.
Afterwards, the license must be installed on each ElasticXL gateway using the “cplic” command:
expert
m 1_1
expert
cplic put -l license-file-GW1_1.lic
m 1_2
expert
cplic put -l license-file-GW1_2.lic
...
Wait, so both of the "parameters" described in the documentation are wrong?
I get that they have to be local licenses. The management can only stick central licenses on systems it's aware of, and part of how ElasticXL operates involves the management not being aware of all of the members of the cluster, therefore central licenses aren't an option. That makes sense.
I didn't use the Sync interface address I used the Management address (which is the same IP for all nodes) and installed using cplic put command on each node
The reason one might choose Sync interface IP addresses versus Management IP is in the case the management IP address might get changed in your environment, thus requiring the licensing to change. The ElasticXL Sync IP addresses will not change and are defined by the ElasticXL initial configuration and new gateway onboarding.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 75 | |
| 17 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Thu 02 Jul 2026 @ 06:00 PM (CST)
Revolucionando la Seguridad con IA Generativa: Prevención Inteligente en Tiempo RealThu 09 Jul 2026 @ 10:00 AM (CEST)
Schutz souveräner Workloads: Check Point & die AWS European Sovereign CloudThu 09 Jul 2026 @ 11:00 AM (CEST)
The Cloud Architects Series: Check Point Edge Protection SD-WAN & SASETue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeThu 02 Jul 2026 @ 06:00 PM (CST)
Revolucionando la Seguridad con IA Generativa: Prevención Inteligente en Tiempo RealAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY