Managing Serviceguard Nineteenth Edition, Reprinted June 2011

IMPORTANT: Restrictions on package names in previous Serviceguard releases were less
stringent. Packages whose names do not conform to the above rules will continue to run, but
if you reconfigure them, you will need to change the name; cmcheckconf and cmapplyconf
will enforce the new rules.
module_name
The module name (for example, failover, service, etc.) Do not change it. Used in the form
of a relative path (for example sg/failover) as a parameter to cmmakepkg to specify modules
to be used in configuring the package. (The files reside in the $SGCONF/modules directory; see
“Where Serviceguard Files Are Kept” (page 149) for an explanation of Serviceguard directories.)
New for modular packages.
module_version
The module version. Do not change it.
New for modular packages.
package_type
The type can be failover, multi_node, or system_multi_node. Default is failover. You
can configure only failover or multi-node packages; see “Types of Package: Failover, Multi-Node,
System Multi-Node” (page 217).
Packages of one type cannot include the base module for another; for example, if package_type
is failover, the package cannot include the multi_node, or system_multi_node module.
package_description
The application that the package runs. This is a descriptive parameter that can be set to any value
you choose, up to a maximum of 80 characters. Default value is Serviceguard Package. New
for 11.19
node_name
The node on which this package can run, or a list of nodes in order of priority, or an asterisk (*)
to indicate all nodes. The default is *.
For system multi-node packages, you must specify *.
If you use a list, specify each node on a new line, preceded by the literal node_name, for example:
node_name <node1>
node_name <node2>
node_name <node3>
The order in which you specify the node names is important. First list the primary node name (the
node where you normally want the package to start), then the first adoptive node name (the best
candidate for failover), then the second adoptive node name, followed by additional node names
in order of preference.
In case of a failover, control of the package will be transferred to the next adoptive node name
listed in the package configuration file, or (if that node is not available or cannot run the package
at that time) to the next node in the list, and so on.
Choosing Package Modules 223