Managing Serviceguard Nineteenth Edition, Reprinted June 2011

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 179), “Specifying a Lock LUN” (page 180),
and “Specifying a Quorum Server” (page 180).
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 284).
• 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.
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 181). It will also validate IP Monitor
polling targets; see “Monitoring LAN Interfaces and Detecting Failure: IP Level” (page 70), and
POLLING_TARGET under “Cluster Configuration Parameters ” (page 105).
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 ”
(page 44)for more information.
To specify a lock disk, enter the lock disk information either on the command line, or in the
configuration file. 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 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 that this disk meets your power wiring requirements. If
necessary, choose a disk powered by a circuit which powers fewer than half the nodes in the
cluster.
For more information, see the discussion of these parameters under “Cluster Configuration
Parameters ” (page 105), the cmquerycl (1m) manpage, and the comments in the template
configuration file.
To display the failover times of disks, use the cmquerycl command, specifying all the nodes in
the cluster. The output of the command lists the disks connected to each node together with the
re-formation time associated with each.
Configuring the Cluster 179