Managing Serviceguard A.11.20, March 2013

setting, which defaults to IPv4. See the parameter descriptions under “Cluster Configuration
Parameters ” (page 114) for more information.
IMPORTANT: For important information, see also “About Hostname Address Families: IPv4-Only,
IPv6-Only, and Mixed Mode” (page 111); and “What Happens when You Change the Quorum
Configuration Online” (page 50)
Obtaining Cross-Subnet Information
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. See
“Cross-Subnet Configurations” (page 29) for rules and definitions.
You must use the -w full option to cmquerycl to discover the available subnets.
For example, assume that you are planning to configure four nodes, NodeA, NodeB, NodeC, and
NodeD, into a cluster that uses the subnets 15.13.164.0, 15.13.172.0, 15.13.165.0,
15.13.182.0, 15.244.65.0, and 15.244.56.0.
The following command
cmquerycl –w full –n nodeA –n nodeB –n nodeB –n nodeC –n nodeD
will produce the output such as the following:
Node Names: nodeA
nodeB
nodeC
nodeD
Bridged networks (full probing performed):
1 lan3 (nodeA)
lan4 (nodeA)
lan3 (nodeB)
lan4 (nodeB)
2 lan1 (nodeA)
lan1 (nodeB)
3 lan2 (nodeA)
lan2 (nodeB)
4 lan3 (nodeC)
lan4 (nodeC)
lan3 (nodeD)
lan4 (nodeD)
5 lan1 (nodeC)
lan1 (nodeD)
6 lan2 (nodeC)
lan2 (nodeD)
IP subnets:
IPv4:
15.13.164.0 lan1 (nodeA)
lan1 (nodeB)
15.13.172.0 lan1 (nodeC)
lan1 (nodeD)
15.13.165.0 lan2 (nodeA)
lan2 (nodeB)
Configuring the Cluster 195