- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
When the Agents Attack
A Live Look at Agentic Exposure Validation
Bridge the CAASM Gap
with Exposure Management
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
CheckMates Fest
First, let me say, VSLS is the preferred mode for everything, regardless.
Classic HA mode means that you run all VSs active on one member, and they all fail over if there is something wrong, event with only one of them.
If you want a failover per VS, this is VSLS. And with manual distribution, you can have all VSs active on your preferred cluster member. VSLS allows that too while keeping per VS failover if something goes wrong.
Would R81.10 VSX Administration Guide be enough?
Quoting from there:
Virtual System Load Sharing (VSLS):
Note - This is the only mode available for a VSX Cluster that was installed as R81.10 or higher.
R81.10 JHF T75 fixed a related issue with Bond interface failure.
HA is actually facilitated with VSLS now days.
Note:
The only mode available for a VSX Cluster that was installed as R81.10 and higher is Virtual System Load Sharing (VSLS).
The High Availability mode is available only if you upgrade a VSX Cluster from R81 or lower to R81.10.
Chris,
So if i do a fresh installation with r81.10 or high the only option i have is VSLS. Do u have any documentation or SK that i can refer to.
Thanks
The source for the above statements is the R81.10 VSX admin guide, please refer:
Would R81.10 VSX Administration Guide be enough?
Quoting from there:
Virtual System Load Sharing (VSLS):
Note - This is the only mode available for a VSX Cluster that was installed as R81.10 or higher.
@Chris_Atkinson Just to clarify, if a cluster was in HA mode and then upgraded, it will still be able to run HA, also in the guide. I just do not see the point of keeping it that way 🙂
@_Val_ Don't worry I 100% agree, HA is now a subset config of VSLS exactly as you describe. 🙂
First, let me say, VSLS is the preferred mode for everything, regardless.
Classic HA mode means that you run all VSs active on one member, and they all fail over if there is something wrong, event with only one of them.
If you want a failover per VS, this is VSLS. And with manual distribution, you can have all VSs active on your preferred cluster member. VSLS allows that too while keeping per VS failover if something goes wrong.
Thanks Val , that sound like a good idea to setup the VSX in VSLS mode and manually make all the VS's active on one cluster member. And that way i can have failover per VS.
Correct.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 32 | |
| 20 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 3 |
Wed 10 Jun 2026 @ 01:00 PM (EDT)
Deep Dive: When the Agents Attack: A Live Look at Agentic Exposure ValidationThu 11 Jun 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #8: Say Yes to AI Without Saying Yes to RiskFri 12 Jun 2026 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 47: Continuous Threat Exposure ManagementTue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningWed 10 Jun 2026 @ 01:00 PM (EDT)
Deep Dive: When the Agents Attack: A Live Look at Agentic Exposure ValidationThu 11 Jun 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #8: Say Yes to AI Without Saying Yes to RiskFri 12 Jun 2026 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 47: Continuous Threat Exposure ManagementTue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningThu 18 Jun 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point WAF - The Next Generation of AI powered protectionAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY