Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Parameters for Configuring EMS Resources
NOTE: The default form for parameter names and literal values in the modular package
configuration file is lower case; for legacy packages the default is upper case. There are no
compatibility issues; Serviceguard is case-insensitive as far as the parameters are concerned. This
manual uses lower case, unless the parameter in question is used only in legacy packages, or the
context refers exclusively to such a package.
Serviceguard provides a set of parameters for configuring EMS (Event Monitoring Service) resources.
These are resource_name, resource_polling_interval, resource_start, and
resource_up_value. Configure each of these parameters in the package configuration file for
each resource the package will be dependent on.
The resource_start parameter determines when Serviceguard starts up resource monitoring
for EMS resources. resource_start can be set to either automaticor deferred.
Serviceguard will start up resource monitoring for automatic resources automatically when the
Serviceguard cluster daemon starts up on the node.
Serviceguard will not attempt to start deferred resource monitoring during node startup, but will
start monitoring these resources when the package runs.
The following is an example of how to configure deferred and automatic resources.
resource_name /net/interfaces/lan/status/lan0
resource_polling_interval 60
resource_start deferred
resource_up_value = up
resource_name /net/interfaces/lan/status/lan1
resource_polling_interval 60
resource_start deferred
resource_up_value = up
resource_name /net/interfaces/lan/status/lan0
resource_polling_interval 60
resource_start automatic
resource_up_value = up
NOTE: For a legacy package, specify the deferred resources again in the package control script,
using the DEFERRED_RESOURCE_NAME parameter:
DEFERRED_RESOURCE_NAME[0]="/net/interfaces/lan/status/lan0"
DEFERRED_RESOURCE_NAME[1]="/net/interfaces/lan/status/lan1"
If a resource is configured to be AUTOMATIC in a legacy configuration file, you do not need to
define DEFERRED_RESOURCE_NAME in the package control script.
About Package Dependencies
Starting in Serviceguard A.11.17, a package can have dependencies on other packages, meaning
the package will not start on a node unless the packages it depends on are running on that node.
In Serviceguard A.11.17, package dependencies are supported only for use with certain
applications specified by HP, such as the multi-node and system multi-node packages that HP
supplies for use with Veritas Cluster File System (CFS) on systems that support it.
As of Serviceguard A.11.18, package dependency is no longer restricted; you can make a package
dependent on any other package or packages running on the same cluster node, subject to the
restrictions spelled out in Chapter 6, under dependency_condition (page 228).
As of A.11.19, Serviceguard adds two new capabilities: you can specify broadly where the
package depended on must be running, and you can specify that it must be down. These capabilities
128 Planning and Documenting an HA Cluster