Managing Serviceguard Sixteenth Edition, March 2009

-w none skips network querying. If you have recently checked the networks, this
option will save time.
Specifying the Address Family for the Heartbeat
To tell Serviceguard to use only IPv4, or only IPv6, addresses for the heartbeat, use the
-h option. For example, to use only IPv6 addresses:
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 138); that discussion also spells out the heartbeat requirements.
The-h and -c options are mutually exclusive.
Full Network Probing
-w full lets you specify full network probing, in which actual connectivity is verified
among all LAN interfaces on all nodes in the cluster, whether or not they are all on the
same subnet.
NOTE: This option must be used to discover actual or potential nodes and subnets
in a cross-subnet configuration. See “Obtaining Cross-Subnet Information” (page 220).
It will also validate IP Monitor polling targets; see “Monitoring LAN Interfaces and
Detecting Failure: IP Level” (page 99), and POLLING_TARGET under “Cluster
Configuration Parameters ” (page 138).
Specifying a Lock Disk
A cluster lock disk, lock LUN, or quorum server, is required for two-node clusters. The
lock must be accessible to all nodes and must be powered separately from the nodes.
See “Cluster Lock” in Chapter 3 for additional information.
To create a lock disk, enter the lock disk information following the cluster name. The
lock disk must be in an LVM volume group that is accessible to all the nodes in the
cluster.
The default FIRST_CLUSTER_LOCK_VG and FIRST_CLUSTER_LOCK_PV supplied
in the ASCII template created with cmquerycl are the volume group and physical
volume name of a disk connected to all cluster nodes; if there is more than one, the
disk is chosen on the basis of minimum failover time calculations. You should ensure
218 Building an HA Cluster Configuration