- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Announcing Quantum R82.10!
Learn MoreOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hello,
I am looking for a command to change a Standby Member to Active in a R80.10 VSX Cluster without disrupting services.
Thanks
Yes... without VSLS, just execute clusterXL_admin down on the active member. This will cause the Cluster to fail over to the other Cluster Member. You can immediately run clusterXL_admin up on that same member to bring ClusterXL back online. This should bring the 1st Gateway back as the Standby Cluster member.
The procedure would be the same to fail back to the other member once you are done whatever work you are performing.
Sorry, I do not think that executing "clusterXL_admin down -p" will help you in this case.
First of all the "-p" flag is for "permanent", meaning it is intended use is to survive reboot. To simply cause a failover, the
"clusterXL_admin down" should be executed on the Active member. Attention!!! please verify that your cluster is in a good working state before doing it.
Additionally, if your VSX cluster is running in VSLS mode, performing "clusterXL_admin down" in VS0 will not cause the other VS' running on Active member to failover:sk95133
In case of VSLS, use vsx_util to redistribute VS' to the desired target VSX unit before executing "clusterXL_admin down" in VS0.
Regards,
Vladimir
Apologies, I've made an error in my post above and have just corrected it.
The admin_down should be executed on currently active member to cause a failover.
Before you do this, please verify that your clustering, in content of each VS is looking good.
Yes... without VSLS, just execute clusterXL_admin down on the active member. This will cause the Cluster to fail over to the other Cluster Member. You can immediately run clusterXL_admin up on that same member to bring ClusterXL back online. This should bring the 1st Gateway back as the Standby Cluster member.
The procedure would be the same to fail back to the other member once you are done whatever work you are performing.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 21 | |
| 15 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 |
Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Fri 12 Dec 2025 @ 10:00 AM (CET)
Check Mates Live Netherlands: #41 AI & Multi Context ProtocolTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY