Managing Serviceguard Nineteenth Edition, Reprinted June 2011

15.13.164.0 lan1 (nodeA)
lan1 (nodeB)
15.13.172.0 lan1 (nodeC)
lan1 (nodeD)
15.13.165.0 lan2 (nodeA)
lan2 (nodeB)
15.13.182.0 lan2 (nodeC)
lan2 (nodeD)
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).
182 Building an HA Cluster Configuration