Managing Serviceguard Fifteenth Edition, reprinted May 2008

Understanding Serviceguard Hardware Configurations
Redundant Network Components
Chapter 2 43
•If a monitored_subnet is configured for PARTIAL
monitored_subnet_access in a package’s configuration file, it must
be configured on at least one of the nodes on the node_name list for
that package. Conversely, if all of the subnets that are being
monitored for this package are configured for PARTIAL access, each
node on the node_name list must have at least one of these subnets
configured.
— As in other configurations, a package will not start on a node
unless the subnets configured on that node, and specified in the
package configuration file as monitored subnets, are up.
For More Information
For more information on the details of configuring the cluster and
packages in a cross-subnet context, see “Obtaining Cross-Subnet
Information” on page 233, “About Cross-Subnet Failover” on page 191
and (for legacy packages only) “Configuring Cross-Subnet Failover” on
page 390.
IMPORTANT Although cross-subnet topology can be implemented on a single site, it is
most commonly used by extended-distance clusters, and specifically
site-aware disaster-tolerant clusters, which require HP add-on
software.
Design and configuration of such clusters are covered in the
disaster-tolerant documentation delivered with Serviceguard. For more
information, see the following documents at http://www.docs.hp.com
-> High Availability:
• Understanding and Designing Serviceguard Disaster Tolerant
Architectures
• Designing Disaster Tolerant HA Clusters Using Metrocluster and
Continentalclusters
• Using Serviceguard Extension for RAC
• The white paper Configuration and Administration of Oracle 10g R2
RAC Database in HP Metrocluster
• The white paper Technical Considerations for Creating a
Serviceguard Cluster that Spans Multiple IP Subnets