This will halt the package, writing output in the package control script log file,typically /etc/cmcluster/<package_name>/<control_script>.log.1.8
Enabling a package for switching/failing over
After a package has been halted its global switching flag is disabled. This means the package will not be moved to an adoptive node automatically if a failure occurs.# cmmodpkg -e <package_name>This will
nable global switching.1.9
Disabling a package from switching/failing over
# cmmodpkg -d <package_name>This will
able global switching.1.10
Enabling a package to run on a particular node
After a package has failed on one node, that node is disabled. This means the packagewill not be able to run on that node.# cmmodpkg -e -n <node_name> <package_name>This will
nable the package to run on the specified node.1.11
Disabling a package from running on a particular node
# cmmodpkg -d -n <node_name> <package_name>This will
able the package to run on the specified node.
2.0Common MC/ServiceGuard Operations
The following operations are frequently performed in the operation of anMC/ServiceGuard cluster. Additional information regarding the commands listed belowcan be found in the “Managing MC/ServiceGuard” manual, or in the appropriate man() pages.2.1
Checking the status of the cluster
From any active node in the cluster:
Logon as root
cmviewcl -vExpected output with the important items to note: (See the diagram in this document)
Ensure all nodes are part of the cluster by checking the “Node Status” area.
Ensure the AUTO_RUN is enabled for each package to allow it to switch to theadoptive node in the cluster if the primary node fails.
Ensure the “Node Switching Parameters” indicate that each package is running onthe appropriate node for your situation.
Ensure that SWITCHING is enabled for all nodes.