Cluster ID mismatch across cluster members for Check Point


Check Point


Indeni will identify when two devices are part of a cluster and alert if the cluster ID settings are different.

Remediation Steps

Follow to ensure the cluster ID is configured the same on both members.

How does this work?

The cluster ID can be set in two ways, the old method of modifying the $FWDIR/boot/modules/fwkern.conf file, and the new method of using a new command, called "cphaconf cluster_id". If the cluster ID is configured in both way the old method takes precedence.

Why is this important?

A Check Point cluster has a value used in cluster communication, called cluster ID. It can be the same for several clusters, as long as they do not share any layer 2 segment. If all the members of a cluster do not have the same setting, the cluster will not work correctly. More information can be found in Check Point KB article SK25977:

Without Indeni how would you find this?

An administrator could login and manually run the command.

View Source Code