Managing HP Serviceguard A.11.20.00 for Linux, June 2012

15.244.65.0 lan3 (nodeA)
lan3 (nodeB)
15.244.56.0 lan4 (nodeC)
lan4 (nodeD)
IPv6:
3ffe:1111::/64 lan3 (nodeA)
lan3 (nodeB)
3ffe:2222::/64 lan3 (nodeC)
lan3 (nodeD)
Possible Heartbeat IPs:
15.13.164.0
15.13.164.1 (nodeA)
15.13.164.2 (nodeB)
15.13.172.0 15.13.172.158 (nodeC)
15.13.172.159 (nodeD)
15.13.165.0 15.13.165.1 (nodeA)
15.13.165.2 (nodeB)
15.13.182.0 15.13.182.158 (nodeC)
15.13.182.159 (nodeD)
Route connectivity(full probing performed):
1 15.13.164.0
15.13.172.0
2 15.13.165.0
15.13.182.0
3 15.244.65.0
4 15.244.56.0
In the Route connectivity section, the numbers on the left (1-4) identify which subnets are
routed to each other (for example, 15.13.164.0 and 15.13.172.0).
IMPORTANT: Note that in this example subnet 15.244.65.0, used by NodeA and NodeB, is
not routed to 15.244.56.0, used by NodeC and NodeD.
But subnets 15.13.164.0 and 15.13.165.0, used by NodeA and NodeB, are routed respectively
to subnets 15.13.172.0 and 15.13.182.0, used by NodeC and NodeD. At least one such
routing among all the nodes must exist for cmquerycl to succeed.
For information about configuring the heartbeat in a cross-subnet configuration, see the
HEARTBEAT_IP parameter discussion under “Cluster Configuration Parameters ” (page 80).
Identifying Heartbeat Subnets
The cluster configuration file includes entries for IP addresses on the heartbeat subnet. HP
recommends that you use a dedicated heartbeat subnet, and configure heartbeat on other subnets
as well, including the data subnet.
The heartbeat can be on an IPv4 or an IPv6 subnet.
The heartbeat can comprise multiple IPv4 subnets joined by a router. In this case at least two
heartbeat paths must be configured for each cluster node. See also the discussion of
HEARTBEAT_IP (page 83), and “Cross-Subnet Configurations” (page 23).
Specifying Maximum Number of Configured Packages
This value must be equal to or greater than the number of packages currently configured in the
cluster. The count includes all types of packages: failover, multi-node, and system multi-node. The
maximum number of packages per cluster is 300. The default is the maximum.
NOTE: Remember to tune kernel parameters on each node to ensure that they are set high enough
for the largest number of packages that will ever run concurrently on that node.
142 Building an HA Cluster Configuration