START THE CLUSTER: when all cluster nodes are down use the #cmruncl command to start the cluster.
The command starts all nodes configured in the cluster and verifies the network information.
Use the -v (verbose) option to display the greatest number of messages.
STOP/HALT ENTIRE CLUSTER: use #cmhaltcl to halt the entire cluster. This command causes all nodes in a configured cluster to halt their Serviceguard daemons.
This halts all the cluster nodes.
CHECK STATUS OF CLUSTER: #cmviewcl displays the current status information of a cluster in line output format.
ADDING PREVIOUSLY CONFIGURED NODES TO A RUNNING CLUSTER: use the #cmrunnode command to join one or more nodes to an already running cluster.
Any node you add must already be a part of the cluster configuration.
The -v (verbose) option prints out all the messages:
Get current configuration
#cmgetconf – Get cluster or package configuration information:
you can use -c cluster_name for a specific Name of the cluster.
Before you move a failover package to a new node, it is a good idea to run #cmviewcl -v -l package and look at dependencies. If the package has dependencies, be sure they can be met on the new node.
To move the package, first halt it where it is running using the cmhaltpkg command. This action not only halts the package, but also disables package switching.
After it halts, run the package on the new node using the #cmrunpkg command, then re-enable switching as described under “Start a Package”.
# cmmodpkg –d (diable)
After a package has failed on one node, that node is disabled. This means the package will not be able to run on that node.
The following command will enable the package to run on the specified node.
# cmmodpkg -e -n umhpux9 pkg1
Disabling a package from running on a particular node
# cmmodpkg -d -n umhpux9 pkg1