Managing Serviceguard Sixteenth Edition, March 2009
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 254).
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.
IMPORTANT: See “Cluster Configuration Parameters ” (page 138) for important
information about node names.
See “About Cross-Subnet Failover” (page 188) for considerations when configuring
cross-subnet packages, which are further explained under “Cross-Subnet
Configurations” (page 41).
auto_run
Can be set to yes or no. The default is yes.
For failover packages, yes allows Serviceguard to start the package (on the first available
node listed under node_name) on cluster start-up, and to automatically restart it on an
adoptive node if it fails. no prevents Serviceguard from automatically starting the
package, and from restarting it on another node.
Choosing Package Modules 263