Managing Serviceguard A.11.20, March 2013

• local_lan_failover_allowed. Use this parameter control whether a package fails or
not when a primary NIC fails on a cluster node and its IP addresses are transferred to a
standby NIC.
Legal values are yes and no. Default is yes.
See the parameter description (page 245) for more information.
• Use the monitored_subnet parameter to specify a subnet that is to be monitored for this
package. If there are multiple subnets, repeat the parameter as many times as needed, on a
new line each time.
In a cross-subnet configuration, configure the additional monitored_subnet_access
parameter for each monitored_subnet as necessary; see “About Cross-Subnet Failover”
(page 160) for more information.
• If this is a Serviceguard Extension for Oracle RAC (SGeRAC) installation, you can use the
cluster_interconnect_subnet parameter (page 245).
• If your package will use relocatable IP addresses, enter the ip_subnet and ip_address
addresses. See the parameter descriptions (page 246) for rules and restrictions.
In a cross-subnet configuration, configure the additional ip_subnet_node parameter for
each ip_subnet as necessary; see “About Cross-Subnet Failover” (page 160) for more
information.
• For each service the package will run, enter values for the following parameters (page 247):
◦ 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 monitor a crucial resource as part of a package using generic resources, enter values for
the following parameters (page 248):
◦ generic_resource_name to identify the generic resource in a package.
◦ generic_resource_evaluation_type to define whether the status of the generic
resource must be evaluated during or before the package is started.
◦ generic_resource_up_criteria to determine the status of a generic resource
based on the specified criterion.
See “Configuring a Generic Resource” (page 139) for more information.
• To configure the package to monitor a registered EMS resource, enter values for the following
parameters (page 250):
◦ resource_name
◦ resource_polling_interval
◦ resource_up_value
◦ resource_start
See “Parameters for Configuring EMS Resources” (page 142) for more information and an
example.
Editing the Configuration File 261