HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

Defining the Lock LUN
Use cmquerycl -L to create a cluster configuration file that defines the lock LUN.
• If the pathname for the lock LUN is the same on all nodes, use a command such as:
cmquerycl -C $SGCONF/config.ascii -L /dev/dsk/c0t1d1 -n <node1> -n
<node2>
• If the pathname for the lock LUN is different on some nodes, you must specify the path on
each node; for example (all on one line):
cmquerycl -C $SGCONF/config.ascii -n <node1> -L /dev/dsk/c0t1d1 -n
<node2> -L /dev/dsk/c0t1d2
These commands create a configuration file which you can apply to the cluster configuration when
you are ready to do so; see “Distributing the Binary Configuration File ” (page 198). See also
“Specifying a Lock LUN” (page 189).
CAUTION: Once you have specified the lock LUN in the cluster configuration file, running
cmapplyconf (1m) or cmdeploycl (1m) will destroy any data on the LUN.
Excluding Devices from Probing
When you run cmquerycl (1m) or cmdeploycl (1m) to configure the cluster, Serviceguard
probes disk devices (devices with paths that begin with /dev/dsk/ and /dev/disk) to see if
they are configured under the LVM, LVM2, or VxVM volume manager. By design, devices such as
CD and DVD drives are omitted, but occasionally such a device may use a description string that
Serviceguard does not recognize. The description string appears in the Description field of the
output of ioscan -funC disk, and you can see what types of device Serviceguard will exclude
from probing by looking at the TYPE field of the file /etc/cmcluster/cmignoretypes.conf.
NOTE: You should not edit cmignoretypes.conf
If Serviceguard does not recognize a device, you will see an error such as the following when you
run cmquerycl:
Error reading device /dev/dsk/c0t0d0 0x8
Note: Disks were discovered which are not in use by either LVM or VxVM.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
In this example, Serviceguard did not recognize the type of the device identified by /dev/dsk/
c0t0d0. You can fix the problem by adding a line for this device to the file /etc/cmcluster/
cmnotdisk.conf; in this example, you would add:
DEVICE_FILE="/dev/dsk/c0t0d0"
Now when you run cmquerycl, if you still have disks that are not being managed by LVM, LVM2
or VxVM, you will see output such as the following:
cmquerycl -C test.conf -n pig
Note: Disks were discovered which are not in use by either LVM or VxVM.
Use pvcreate(1M) to initialize a disk for LVM or,
use vxdiskadm(1M) to initialize a disk for VxVM.
176 Building an HA Cluster Configuration