HP Serviceguard manual Ipsubnetnode, Ipaddress, Servicename

This parameter can be set for failover packages only.

Can be added or deleted while the package is running.

ip_subnet_node

In a cross-subnet configuration, specifies which nodes an ip_subnet is configured on. If no

ip_subnet_node are listed under an ip_subnet, it is assumed to be configured on all nodes in this package’s node_name list (page 235).

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 241) and “About Cross-Subnet Failover” (page 154).

New for modular packages. For legacy packages, see “Configuring Cross-Subnet Failover” (page 309).

ip_address

A relocatable IP address on a specified ip_subnet (page 242). Replaces IP, which is still supported in the package control script for legacy packages; see “Configuring a Legacy Package” (page 302).

For more information about relocatable IP addresses, see “Stationary and Relocatable IP Addresses ” (page 67).

This parameter can be set for failover packages only.

Can be added or deleted while the package is running.

CAUTION: HP strongly recommends that you add relocatable addresses to packages only by editing ip_address (or IP [] entries in the control script of a legacy package) and running cmapplyconf (1m).

service_name

A service is a program or function which Serviceguard monitors as long as 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 234). 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_namepatricks-package4-ping

service_cmd"/usr/sbin/ping hasupt22"

service_restartunlimited service_fail_fast_enabled no

service_halt_timeout 300

See the package configuration file for more examples.

Choosing Package Modules 243