- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
Check Point's Cyber Park is Now Open
Let the Games Begin!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
If you forgot to select "install ClusterXL" in the wizard, you must install the gateway again.
Also a possible cause:
Cluster membership was not enabled completely on the problematic machine.
Perform the following steps in order to make sure that cluster membership is enabled on the problematic machine:
If that doesn't help, here's what you need to do also:
Now check the cluster state via cphapro stat
If this does not help, execute the following SK:
- sk109755
- sk88360
- sk151952
- sk110573
To start
#cpha start
Make sure it is configured to start at boot based on cpconfig
#cpconfig
Select option to "Enable cluster membership for this gateway"
If is says disable it is already enabled.
Also, make sure policy is installed that deems this box is a cluster member.
probably your gateway need a policy firewall where it say that he is part of a cluster too
Hi guys, error persists...
Any other suggestions??
During first time wizard did you check unit is a part of a cluster? what is the output of fw stat?
If you have done (checking unit is a part of a cluster) and you have configured a check point cluster object correctly on the management server with a security policy I suggest to open a tac issue or contact your local partner
have you checked if the coreXL configuration is the same on the cluster members?
if enabled or not, if the number of "fw instance" is equal between members.
I assume that both gateways are identical (appliances, corexl config, software versions etc) and you have configured gateways correctly as a cluster member at first time wizard, and also you have a regular gateway license. Run cpconfig command choose 'enable cluster membership for this gateway', exit from cpconfig menu and reboot the machine. Install policy gateways and then check the status again.
" I assume that both gateways are identical (appliances, corexl config, software versions etc) and you have configured gateways correctly as a cluster member at first time wizard, and also you have a regular gateway license. Run cpconfig command choose 'enable cluster membership for this gateway', exit from cpconfig menu and reboot the machine. Install policy gateways and then check the status again "
The solution above work for me. I just had to install the policy, and after that my cluster went Up. Thanks
If you forgot to select "install ClusterXL" in the wizard, you must install the gateway again.
Also a possible cause:
Cluster membership was not enabled completely on the problematic machine.
Perform the following steps in order to make sure that cluster membership is enabled on the problematic machine:
If that doesn't help, here's what you need to do also:
Now check the cluster state via cphapro stat
If this does not help, execute the following SK:
- sk109755
- sk88360
- sk151952
- sk110573
If you forgot to select "install ClusterXL" in the wizard, you must install the gateway again.
Also a possible cause:
Cluster membership was not enabled completely on the problematic machine.
Perform the following steps in order to make sure that cluster membership is enabled on the problematic machine:
If that doesn't help, here's what you need to do also:
If this does not help, execute the following SK:
- sk109755
- sk88360
- sk151952
- sk110573
I got same issue.
What I to fix it:
1- fw unloadlocal both SG
2- create rule permit src/dst cluster/SG
3- install policy
Tks,
victor cortez
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY