Managing Serviceguard Eighteenth Edition, September 2010

cmquerycl -v -h ipv6 -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10
• -h ipv4 tells Serviceguard to discover and configure only IPv4 subnets. If it does
not find any eligible subnets, the command will fail.
• -h ipv6 tells Serviceguard to discover and configure only IPv6 subnets. If it does
not find any eligible subnets, the command will fail.
• If you don't use the -h option, Serviceguard will choose the best available
configuration to meet minimum requirements, preferring an IPv4 LAN over IPv6
where both are available. The resulting configuration could be IPv4 only, IPv6
only, or a mix of both. You can override Serviceguard's default choices by means
of the HEARTBEAT_IP parameter, discussed under “Cluster Configuration
Parameters ” (page 143); that discussion also spells out the heartbeat requirements.
• The -h and -c options are mutually exclusive.
Specifying the Cluster Lock
You can use the cmquerycl command line to specify a cluster lock LUN (-L
lock_lun_device), lock disk (-L lock_vg: lock_pv), or quorum server (-q
quorum_server [qs_ip2]). See the cmquerycl (1m) manpage for details.
NOTE: You can specify only one lock disk on the command line; if you need to specify
a second cluster lock disk, you must do so in the cluster configuration file.
For more information, see “Specifying a Lock Disk” (page 246), “Specifying a Lock
LUN” (page 247), and “Specifying a Quorum Server” (page 248).
Generating a Network Template File
As of Serviceguard A.11.20, a separate form of cmquerycl discovers connected LAN
interfaces on each node you specify, and writes it to a file you specify; for example:
cmquerycl -n node1 -n node2 -N mynetwork
You can now edit mynetwork to add IP address and subnet information for new
interfaces which are not yet configured, and then use cmapplyconf (1m) to configure
the new interfaces into the cluster; for example:
cmapplyconf -N mynetwork
IMPORTANT:
• You cannot use cmapplyconf -N if the cluster already exists; in that case, follow
instructions under “Changing the Cluster Networking Configuration while the
Cluster Is Running” (page 367).
• You can only add information to the output file (mynetwork in this example); do
not change the information already in the file.
For more information, see the cmquerycl (1m) and cmapplyconf (1m) manpages.
Configuring the Cluster 245