Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6254
• RESOURCE_UP_VALUE. Enter the value or values that determine when
the resource is considered to be up. During monitoring, if a different
value is found for the resource, the package will fail.
• RESOURCE_START. The RESOURCE_START option is used to determine
when Serviceguard should start up resource monitoring for EMS
resources. The RESOURCE_START option can be set to either
AUTOMATIC or DEFERRED. If AUTOMATIC is specified, Serviceguard will
start up resource monitoring for these resources automatically when
the Serviceguard cluster daemon starts up on the node. If resources
are configured AUTOMATIC, you do not need to define
DEFERRED_RESOURCE_NAME in the package control script.
If DEFERRED is selected, Serviceguard does not attempt to start
resource monitoring for these DEFERRED resources during node start
up. However, these DEFERRED resources must be specified in the
package control script.
The following is an example of how to configure DEFERRED and
AUTOMATIC resources. In the package configuration file, specify
resources as follows:
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/lan2
RESOURCE_POLLING_INTERVAL 60
RESOURCE_START AUTOMATIC
RESOURCE_UP_VALUE = UP
Access Control Policy is a new feature with Serviceguard version 11.16.
With it, you can allow non-root users to administer packages and
clusters. Cluster-wide roles are defined in the cluster configuration file.
Package-specific roles are defined in the package configuration file.