Managing Serviceguard Eighteenth Edition, September 2010

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 and15.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 143).
250 Building an HA Cluster Configuration