Managing HP Serviceguard A.11.20.00 for Linux, June 2012

package_name
Any name, up to a maximum of 39 characters, that:
• starts and ends with an alphanumeric character
• otherwise contains only alphanumeric characters or dot (.), dash (-), or underscore (_)
• is unique among package names in this cluster
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. Do not change it. Used in the form of a relative path (for example, sg/
failover) as a parameter to cmmakepkg specify modules to be used in configuring the package.
(The files reside in the $SGCONF/modules directory; see “Understanding the Location of
Serviceguard Files” (page 121) for the location of $SGCONF on your version of Linux.)
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. You can configure only
failover or multi-node packages; see “Types of Package: Failover, Multi-Node, System Multi-Node”
(page 154).
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.
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 node_name
*.
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 159