- 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
We are migrating to a clustered pair of 15600 appliances with R81.10 to a clustered pair of 19100 appliances with R81.20. We followed a procedure of setting up the 19100s in a lab with an SMS server that had the production SMS database imported and we configure the appliances, pushed policy, did extensive testing such as failover, mock traffic to test internal and external access to make sure the config was correct and then did a cutover from the old to new appliances. On the night of the cutover, we ran into an issue for the first time ever following the above procedure which was that some updateable objects used in our policy were not processing traffic and management wants us to follow a different procedure since we had to fall back and they do not want this issue to happen again.
New Procedure (The appliances will be reset and configured)
Any issues with the above procedure or anything to add or change? I would like to the failover to the standby 19100, run our complete connectivity tests before I power down the last 15600 and bring up the second 19100. Would I just run cphastop, cpstop or clusuterXL_admin down on the active 15600? Also, I will do a "get interfaces without topology" but will I run into an issue with different appliances defined in the same cluster? Thanks
This is process I followed many times, never had an issue.
https://community.checkpoint.com/t5/Security-Gateways/Replace-Upgrade-Cluster/td-p/69216
In regard to failover from the old primary appliance to the new appliance, there may be a preference for not powering it down until we validate the new appliance with extensive testing after the failover. Therefore, should I do a cpstop or will cphastop work to force new appliance from standby to primary instead of shutting down the old appliance.
You may shutdown the switch ports.
you might have to use MVC (Multi-Version Cluster) in the guide it is to be used when the Gaia versions are different. in your case the hardware is also different. but I have tested it with different hardware as well. You might want to use the mvc command on the 19k appliance and see if the cluster is back online after the policy is pushed and the topology is fetched. this way you will have active/standby and no downtime when failing over to new member.
otherwise you will have to shutdown the switch ports which will involve a small downtime. but if any issues on the new member, then it will take time to bring the old one back up.
I would suggest go with the same version on the 19k as well and upgrade once everything is stable, just to be on the safe side.
Thats recommended way, for sure.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaThu 26 Nov 2026 @ 10:00 AM (CET)
The Cloud Architects Series: Cloud Security State in 2026 – Lessons Learned and a Look AheadWed 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