Managing Serviceguard Nineteenth Edition, Reprinted June 2011

If any monitored_subnet fails, Serviceguard will switch the package to any other node specified
by node_name which can communicate on 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 list (see node_name (page 223)), 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 231) and “About Cross-Subnet Failover” (page 145).
New for modular packages. For legacy packages, see “Configuring Cross-Subnet Failover”
(page 295).
cluster_interconnect_subnet
Can be configured only for a multi-node package in a Serviceguard Extension for Real Application
Cluster (SGeRAC) installation.
NOTE: Serviceguard supports both IPv4 and IPv6 for an cluster_interconnect_subnet,
but before configuring an IPv6 subnet, make sure that your version of Oracle RAC also supports
IPv6 for this subnet.
See the latest version of Using Serviceguard Extension for RAC at http://www.hp.com/go/
hpux-serviceguard-docs for more information, including the status of Oracle RAC support for an
IPv6 cluster_interconnect_subnet.
New for A.11.18 (for both modular and legacy packages).
230 Configuring Packages and Their Services