Managing Serviceguard Seventeenth Edition, First Reprint December 2009

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.
IMPORTANT: The purpose of cmnotdisk.conf is to exclude specific devices, usually
CD and DVD drives, that Serviceguard does not recognize and which should not be
probed. Make sure you do not add a DEVICE_FILE entry in cmnotdisk.conf for
any device that should be probed; that is, disk devices being managed by LVM or LVM2.
Excluding any such device will cause cmquerycl to fail.
Setting Up and Running the Quorum Server
If you will be using a Quorum Server rather than a lock disk or LUN, the Quorum
Server software must be installed on a system other than the nodes on which your
cluster will be running, and must be running during cluster configuration.
For detailed discussion, recommendations, and instructions for installing, updating,
configuring, and running the Quorum Server, see HP Serviceguard Quorum Server Version
A.04.00 Release Notes at http://www.docs.hp.com -> High Availability ->
Quorum Server.
Preparing Your Systems 209