Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6296
For each subnet used, specify the subnet address on one line and, on the
following lines, the relocatable IP addresses that the package uses on
that subnet. These will be configured when the package starts and
unconfigured when it halts.
For example, if this package uses subnet 192.10.25.0 and the relocatable
IP addresses 192.10.25.12 and 192.10.25.13, enter:
ip_subnet 192.10.25.0
ip_address 192.10.25.12
ip_address 192.10.25.13
If you want the subnet to be monitored, specify it in the
monitored_subnet parameter as well.
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 on page 295 and “About Cross-Subnet
Failover” on page 191.
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_node are listed
under an ip_subnet, it is assumed to be configured on all nodes in this
package’s node_name list (see node_name on page 288).
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 on page 295 and “About
Cross-Subnet Failover” on page 191.
New for modular packages. For legacy packages, see “Configuring
Cross-Subnet Failover” on page 390.
ip_address A relocatable IP address on a specified ip_subnet (see
page 295). Replaces IP, which is still supported in the package control
script for legacy packages; see “Configuring a Legacy Package” on
page 377.