Managing HP Serviceguard A.11.20.00 for Linux, June 2012

In a cross-subnet configuration, you also need to specify which nodes the subnet is configured on;
see ip_subnet_node below. See also monitored_subnet_access (page 164) and “About
Cross-Subnet Failover” (page 117).
This parameter can be set for failover packages only.
ip_subnet_node
In a cross-subnet configuration, specifies which nodes an ip_subnet is configured on. If no
ip_subnet_nodes are listed under an ip_subnet, it is assumed to be configured on all nodes
in this package’s node_name list (page 159).
Can be added or deleted while the package is running, with these restrictions:
• The package must not be running on the node that is being added or deleted.
• The node must not be the first to be added to, or the last deleted from, the list of
ip_subnet_nodes for this ip_subnet.
See also monitored_subnet_access (page 164) and “About Cross-Subnet Failover” (page 117).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet Failover”
(page 216).
ip_address
A relocatable IP address on a specified ip_subnet. Replaces IP, which is still supported in the
package control script for legacy packages.
For more information about relocatable IP addresses, see “Stationary and Relocatable IP Addresses
and Monitored Subnets” (page 54).
This parameter can be set for failover packages only.
service_name
A service is a program or function which Serviceguard monitors as long the package is up.
service_name identifies this function and is used by the cmrunserv and cmhaltserv
commands. You can configure a maximum of 30 services per package and 900 services per
cluster.
The length and formal restrictions for the name are the same as for package_name (page 159).
service_name must be unique among all packages in the cluster.
IMPORTANT: Restrictions on service names in previous Serviceguard releases were less stringent.
Packages that specify services whose names do not conform to the above rules will continue to
run, but if you reconfigure them, you will need to change the name; cmcheckconf and
cmapplyconf will enforce the new rules.
Each service is defined by five parameters: service_name, service_cmd, service_restart,
service_fail_fast_enabled, and service_halt_timeout. See the descriptions that
follow.
The following is an example of fully defined service:
service_name patricks-package4-ping]
service_cmd "/usr/sbin/ping hasupt22"
service_restart unlimited
service_fail_fast_enabled no
service_halt_timeout 300
See the package configuration template file for more examples.
For legacy packages, this parameter is in the package control script as well as the package
configuration file.
166 Configuring Packages and Their Services