Managing HP Serviceguard for Linux Ninth Edition, April 2009

For more information, see “About Package Weights” (page 128). See also the discussion
of the relevant parameters under “Cluster Configuration Parameters ” (page 100), in
the cmmakepkg (1m) and cmquerycl (1m) manpages, and in the cluster
configuration and package configuration template files.
New for 11.19.
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” (page 252).
You can specify multiple subnets; use a separate line for each.
If you specify a subnet as a monitored_subnet the package will not run on any node not
reachable via that subnet. This normally means that if the subnet is not up, the package
will not run. (For cross-subnet configurations, in which a subnet may be configured
on some nodes and not on others, see monitored_subnet_access below, ip_subnet_node
(page 206), and “About Cross-Subnet Failover” (page 141).)
Typically you would monitor the ip_subnet, specifying it here as well as in the ip_subnet
parameter (page 205), 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” (page 71) for more information.
If any monitored_subnet fails, Serviceguard will switch the package to any other node
specified by node_name (page 197) which can communicate on all the monitored_subnets
defined for this package. See the comments in the configuration file for more information
and examples.
monitored_subnet_access
In cross-subnet configurations, specifies whether each monitored_subnet is accessible
on all nodes in the package’s node_name list (page 197), or only some. Valid values are
PARTIAL, meaning that at least one of the nodes has access to the subnet, but not all;
and FULL, meaning that all nodes have access to the subnet. The default is FULL, and
it is in effect if monitored_subnet_access is not specified.
See also ip_subnet_node (page 206) and “About Cross-Subnet Failover” (page 141).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet
Failover” (page 259).
204 Configuring Packages and Their Services