My guess is that you didn't set the same Cluster Global ID on both members during the R77.30 post-installation wizard. This value must match on all members of the cluster or they will refuse to cluster up with each other. Run
cphaconf cluster_id get to check this value on both members, if you need to reset the value on one of the members to match the other, use the
cphaconf cluster_id set <CLUSTER_ID_VALUE> command.
R80.10 gateway clusters use a new feature called “Automatic MAC Magic” by default to automatically derive a unique Cluster Global ID, and prevent conflicts with other gateway clusters on the same network. The status of this new feature can be checked with the cphaprob mmagic command. This feature can also be monitored from a new ClusterXL-based screen of the cpview tool on a R80.10 gateway under Advanced...ClusterXL, and is backward compatible with gateways that had their Cluster IDs configured manually in earlier versions such as R77.30.
My book "Max Power: Check Point Firewall Performance Optimization"
now available via http://maxpowerfirewalls.com.
New 2-day Live "Max Power" Series Course Now Available:
"Gateway Performance Optimization R81.20" at maxpowerfirewalls.com