Support Center > Search Results > SecureKnowledge Details
Cluster member detects only itself in 'cphaprob state' output, or detects other member as "ClusterXL inactive or machine is down"
Symptoms
  • After rebooting the cluster members, Member_A detects only itself in the output of 'cphaprob state'.

  • After rebooting the cluster members, Member_A detects Member_B in the output of 'cphaprob state' as "ClusterXL inactive or machine is down."
Cause

During boot, Member_A never receives Cluster Control Protocol (CCP) packets from Member_B.

Before rebooting Member_A, Member_B was stopped, or Check Point services (including ClusterXL) on Member_B were stopped (i.e., the cpstop command was issued).


Solution
Procedure:

  1. Make sure Member_B is up and running and all required Check Point services are running on Member_B (issue the cpstart command).
  2. If Member_A still detects only itself, or still detects Member_B as "ClusterXL inactive or machine is down", then reboot Member_B first.
  3. If Member_A still detects only itself, or still detects Member_B as "ClusterXL inactive or machine is down", then reboot Member_A.

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