Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Understanding Hardware Configurations for Serviceguard for Linux
Redundant Network Components
Chapter 230
Cross-Subnet Configurations
As of Serviceguard A.11.18 it is possible to configure multiple subnets,
joined by a router, both for the cluster heartbeat and for data, with some
nodes using one subnet and some another.
A cross-subnet configuration allows:
• Automatic package failover from a node on one subnet to a node on
another
• A cluster heartbeat that spans subnets.
Configuration Tasks Cluster and package configuration tasks are
affected as follows:
• You must use the -w full option to cmquerycl to discover actual or
potential nodes and subnets across routers.
• You must configure two new parameters in the package
configuration file to allow packages to fail over across subnets:
— ip_subnet_node - to indicate which nodes the subnet is
configured on
— monitored_subnet_access - to indicate whether the subnet is
configured on all nodes (FULL) or only some (PARTIAL)
(For legacy packages, see “Configuring Cross-Subnet Failover” on
page 286.)
• You should not use the wildcard (*) for node_name in the package
configuration file, as this could allow the package to fail over across
subnets when a node on the same subnet is eligible. Instead, list the
nodes in order of preference.
Restrictions
The following restrictions apply:
• All nodes in the cluster must belong to the same network domain
(that is, the domain portion of the fully-qualified domain name
must be the same).
• The nodes must be fully connected at the IP level.
• A minimum of two heartbeat paths must be configured for each
cluster node.