HP Serviceguard manual Nodename, Autorun, Nodefailfastenabled

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 109) for important information about node names.

See “About Cross-Subnet Failover” (page 154) for considerations affecting cross-subnet packages, which are further explained under “Cross-Subnet Configurations” (page 30). See “Rules for Simple Dependencies” (page 137) for considerations affecting a package that depends on another package, or that is depended on.

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 (1m) command.

auto_run should be set to yes if the package depends on another package, or is depended on; see “About Package Dependencies” (page 137).

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.

node_fail_fast_enabled

Can be set to yes or no. The default is no.

yes means the node on which the package is running will be halted (HP-UX system reset) if the package fails; no means Serviceguard will not halt the system.

If this parameter is set to yes and one of the following events occurs, Serviceguard will halt the system (HP-UX system reset) on the node where the control script fails:

•A package subnet fails and no backup network is available

•A generic resource fails

•An EMS resource fails

•Serviceguard is unable to execute the halt function

•The start or halt function times out

Choosing Package Modules 235