Managing Serviceguard Eighteenth Edition, September 2010

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
178 Planning and Documenting an HA Cluster