Managing HP Serviceguard A.11.20.20 for Linux, March 2014

6.1.4.6 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.
If a package is configured with a site_preferred or site_preferred_manual failover
policy and if you want to modify the default NODE_NAME, ensure that the NODE_NAME entries
are grouped by sites. For example, in the following configuration, a package with
site_preferred policy can have NODE_NAME entries in the order node2 , node1 , node 4,
node3 but not node2, node3, node1 and node4.
SITE_NAME A
NODE STATUS STATE
node1 up running
node2 up running
SITE_NAME B
NODE STATUS STATE
node3 up running
node4 up running
IMPORTANT: See “Cluster Configuration Parameters ” (page 90) for important information about
node names.
See “About Cross-Subnet Failover” (page 130) for considerations when configuring cross-subnet
packages, which are further explained under “Cross-Subnet Configurations” (page 27).
6.1.4.7 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.
This is also referred to as package switching, and can be enabled or disabled while the package
is running, by means of the cmmodpkg command.
auto_run should be set to yes if the package depends on another package, or is depended on;
see “About Package Dependencies” (page 113).
For system multi-node packages, auto_run must be set to yes. In the case of a multi-node package,
setting auto_run to yes allows an instance to start on a new node joining the cluster; no means
it will not.
6.1.4.8 node_fail_fast_enabled
Can be set to yes or no. The default is no.
176 Configuring Packages and Their Services