Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Editing the Configuration File
Chapter 6316
In a cross-subnet configuration, configure the additional
monitored_subnet_access parameter for each monitored_subnet
as necessary; see “About Cross-Subnet Failover” on page 191 for
more information.
• If this is a Serviceguard Extension for Oracle RAC (SGeRAC)
installation, you can use the cluster_interconnect_subnet
parameter (see page 295).
• If your package will use relocatable IP addresses, enter the
ip_subnet and ip_address. addresses. ip_subnet must be specified
in the cluster configuration file as a STATIONARY_IP.
In a cross-subnet configuration, configure the additional
ip_subnet_node parameter for each ip_subnet as necessary; see
“About Cross-Subnet Failover” on page 191 for more information.
• For each service the package will run, enter values for the following
parameters (see page 297):
— service_name (for example, a daemon or long-running process)
— service_cmd (for example, the command that starts the process)
— service_fail_fast_enabled and service_halt_timeout if
you need to change them from their defaults.
— service_restart if you want the package to restart the service
if it exits. (A value of unlimited can be useful if you want the
service to execute in a loop, rather than exit and halt the
package.)
• To configure the package to monitor a registered EMS resource,
enter values for the following parameters (see page 299):
— resource_name
— resource_polling_interval
— resource_up_value
— resource_start
See “Parameters for Configuring EMS Resources” on page 176 for
more information and an example.
• If the package needs to mount LVM volumes to filesystems, use the
vg parameters to specify the names of the volume groups to be
activated, select the appropriate vgchange_cmd, and use the fs_