Managing Serviceguard Eighteenth Edition, September 2010
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 297)
and “About Cross-Subnet Failover” (page 201).
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 289).
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 297) and “About Cross-Subnet Failover” (page 201).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet
Failover” (page 383).
ip_address
A relocatable IP address on a specified ip_subnet (page 298). Replaces IP, which is still
supported in the package control script for legacy packages; see “Configuring a Legacy
Package” (page 375).
For more information about relocatable IP addresses, see “Stationary and Relocatable
IP Addresses ” (page 90).
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 288). service_name must be unique among all packages in the cluster.
Choosing Package Modules 299