In This Section: |
Description The cphaconf command configures ClusterXL.
Important - Running this command is not recommended. It should be run automatically, only by the Security Gateway or by Check Point support. The only exception to this rule is running this command with |
Usage
cphaconf [-i <computer id>] [-p <policy id>] [-b <db_id>] [-n <ClusterXL num>] cphaconf stop_all_vs |
Syntax
Parameter |
Description |
---|---|
|
Sets whether ClusterXL Control Protocol (CCP) packets should be sent with a broadcast or multicast destination MAC address. The default behavior is multicast. The setting created using this command will survive reboot. Note: The same value (either broadcast or multicast) should be set on all ClusterXL members. |
|
Stops the ClusterXL product on all Virtual Systems on a VSX Gateway. |
Description The cphaprob
command verifies that the cluster and the cluster members are working properly.
Usage
cphaprob -d <device> -t <timeout(sec)> -s <ok|init|problem> [-p] register |
Syntax
Parameter |
Description |
---|---|
|
Register <device> as a critical process, and add it to the list of devices that must be running for the cluster member to be considered active. |
|
Register all the user defined critical devices listed in <file>. |
|
Unregister a user defined <device> as a critical process. This means that this device is no longer considered critical. |
|
Unregister all the user defined <device>. |
|
Report the status of a user defined critical device to ClusterXL. |
|
View the list of critical devices on a cluster member, and of all the other machines in the cluster. |
|
View the status of a cluster member, and of all the other members of the cluster. |
|
View the state of the cluster member interfaces and the virtual cluster interfaces. |
Description Running cphastart
on a cluster member activates ClusterXL on the member. It does not initiate full synchronization. cpstart
is the recommended way to start a cluster member.
Description Running cphastop
on a cluster member stops the cluster member from passing traffic. State synchronization also stops. It is still possible to open connections directly to the cluster member. In High Availability Legacy mode, running cphastop
may cause the entire cluster to stop functioning.