Support Center > Search Results > SecureKnowledge Details
Error: "CPHA: Found another machine with same cluster ID..." in the system console
Symptoms
  • Error on Check Point High Availability (CPHA) module console
  • Error: "CPHA: Found another machine with same cluster ID. There is probably another cluster connected to the same switch/hub as this one. This is an illegal configuration. Each cluster should be connected to another set of switches/hubs"
Cause
There are two or more Check Point High Availability (CPHA) clusters connected to the same switch or hub with the same cluster ID.
Solution

This problem occurs when two separate Management modules are used to create two different Check Point High Availability (CPHA) clusters connected to the same hub or switch.
Each Management module creates the cluster with ID 1 as it was the first cluster it created.
Since both clusters are connected to the same switch or hub, they must have unique cluster ID numbers, or a conflict occurs.

This problem can be resolved by either connecting one of the clusters to a different hub or switch, or by changing the cluster ID of one of the clusters.

The cluster ID can be changed using the Database Tool or Dbedit:

Using the Database Tool:
1) Close all GUI clients.
2) Open the Database Tool (GUIdbedit.exe) and Login
(Login must be the Username and password of an Administrator with Read/Write permission for Policy Editor, Server should be the Management module controlling the affected Cluster)

3) In the Tables Pane open the "Network Objects" branch and select "Network Objects".
4) In the Objects Field on the right, select one of the affected cluster objects
5) In the Object Details Pane at the bottom, find the "cluster_id" field
6) double click "cluster_id" to edit
A pop up box opens

7) replace the value in the field with a different number
8) Click "OK" to close the pop up box.
9) Click FILE > SAVE ALL to save all changes
10) Answer "YES" to the Pop Up Box.
11) Exit the Database Tool
12) Install Policy 


Using dbedit:
1) Close all GUI clients.
2) Execute this command on one of the Management modules:

dbedit -s localhost -u [user] -p [password]

[user] and [password] should be replaced with the username and password of an Administrator with Read/Write permission for the Policy Editor.

3) At the dbedit command prompt, enter this command:

modify network_objects [cluster_name] cluster_id [value]

[cluster_name] is the name of the cluster object and [value] is the new Cluster ID

Example:
modify network_objects ha-sol1 cluster_id 2

4) Update the changes in the database, using this command:

update network_objects [cluster_name]

Example:
update network_objects ha-sol1

5) Exit the dbedit utility:

6) Install Policy
quit

NOTE:
For more information on the Database tool and dbedit utilities refer to Editing the object_5_0.C file using the Database Tool (GUIdbedit) and dbedit utilities

This solution is about products that are no longer supported and it will not be updated

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment