- 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
Hello all,
I'm playing with my personal remote lab currently in preparation for a project at $DAYJOB to deploy three 9800's in an ElasticXL cluster and I have a question about the Sync interfaces, given that sync plays an even more important part in an ElasticXl cluster. We're looking at using a pair of sfp+ 10gbe ports per gateway for our sync, does anyone know what the supported process is to configure an ElastiXL cluster this way?
I've poked around at the appliances in my lab and noticed that there's a bond interface for Sync with the 1gbe sync port added to, I'm assuming that when I initially configure the SMO for the cluster that I can just add the two sfp+ interfaces to the sync bond and be fine, would that be correct? I'd change things up in my lab, but it's a 7 hour drive away at a friend's colo right now.
Regards,
Zack.
|
Important:
ElasticXL Cluster renames the physical interfaces on the appliances:
|
Does ElasticXL Cluster support a bond of Sync interfaces?
Yes - the default configuration is a Bond called "Sync" that contains the eth1-Sync ("Sync") interface of the Security Appliance.
By design, this interface is hidden.
So indeed bond should already be there. I am not sure if you add a SFP it will automatic add it to the SYNC. It think it picks it during the initial config. It should be possible if I read this know limitation. I would just indeed to add via gaia clish
| PMTR-107433 | ElasticXL | Adding an unassigned interface to or from Sync bond leads to the flags reset and, as a result, it disrupts the ElasticXL detection and ElasticXL drops the packets. |
For confirmation, here's my lab ElasticXL cluster:
[Expert@DallasticXL-s01-01:0]# clish -c "show configuration" | grep 1024
add bonding group 1024
set bonding group 1024 mode active-backup
set bonding group 1024 primary eth1-Sync
set bonding group 1024 xmit-hash-policy layer2
add bonding group 1024 interface eth1-Sync
Note that you should both add the interfaces you want to use and set one of them to be primary (or change the bond to a mode which doesn't have a primary). You should probably also remove eth1-Sync once you have done so.
The sync bond comes up as bonding group 1024 so I believe you can just add / remove interfaces to / from that, yes.
Thanks, that's what I was guessing, but I wasn't entirely sure.
For confirmation, here's my lab ElasticXL cluster:
[Expert@DallasticXL-s01-01:0]# clish -c "show configuration" | grep 1024
add bonding group 1024
set bonding group 1024 mode active-backup
set bonding group 1024 primary eth1-Sync
set bonding group 1024 xmit-hash-policy layer2
add bonding group 1024 interface eth1-Sync
Note that you should both add the interfaces you want to use and set one of them to be primary (or change the bond to a mode which doesn't have a primary). You should probably also remove eth1-Sync once you have done so.
Thanks for confirming that, I had more or less the same process in mind.
|
Important:
ElasticXL Cluster renames the physical interfaces on the appliances:
|
Does ElasticXL Cluster support a bond of Sync interfaces?
Yes - the default configuration is a Bond called "Sync" that contains the eth1-Sync ("Sync") interface of the Security Appliance.
By design, this interface is hidden.
So indeed bond should already be there. I am not sure if you add a SFP it will automatic add it to the SYNC. It think it picks it during the initial config. It should be possible if I read this know limitation. I would just indeed to add via gaia clish
| PMTR-107433 | ElasticXL | Adding an unassigned interface to or from Sync bond leads to the flags reset and, as a result, it disrupts the ElasticXL detection and ElasticXL drops the packets. |
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