Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6208
monitored_subnet
The LAN subnet that is to be monitored for this package. Replaces legacy
SUBNET which is still supported in the package configuration file for
legacy packages; see “Configuring a Legacy Package” on page 262.
Multiple subnets can be specified on separate lines.
Specifying a subnet as a monitored_subnet means that the package
will not run if the subnet is not up, and will not run on any node not
reachable via that subnet.
Typically you would monitor the ip_subnet, specifying it here as well as
in the ip_subnet parameter (see below), but you may want to monitor
other subnets as well; you can specify any subnet that is configured into
the cluster (via the STATIONARY_IP parameter in the cluster
configuration file). See “Stationary and Relocatable IP Addresses and
Monitored Subnets” on page 71 for more information.
If any monitored_subnet fails, Serviceguard will switch the package to
any other node specified by node_name which can communicate on all the
monitored_subnets defined for this package. See the comments in the
configuration file for more information and examples.
ip_subnet
Specifies an IP subnet used by the package. Replaces SUBNET, which is
still supported in the package control script for legacy packages.
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 (see above) as well.
This parameter can be set for failover packages only.