HP Serviceguard manual Specifying a Lock LUN, Cmquerycl -v -n ftsys9 -n ftsys10

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 109), 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.

Do not include the node’s entire domain name; for example, specify ftsys9, not ftsys9.cup.hp.com:

cmquerycl -v -n ftsys9 -n ftsys10

cmquerycl will not print out the re-formation time for a volume group that currently belongs to a cluster. If you want cmquerycl to print the re-formation time for a volume group, run vgchange -c n <vg name> to clear the cluster ID from the volume group. After you are done, do not forget to run vgchange -c y vgname to rewrite the cluster ID back to the volume group; for example:

vgchange -c y /dev/vglock

NOTE: You should not configure a second lock volume group or physical volume unless your configuration specifically requires it. See “Dual Lock Disk” (page 48).

If your configuration requires you to configure a second cluster lock, enter the following parameters in the cluster configuration file:

SECOND_CLUSTER_LOCK_VG /dev/volume-group

SECOND_CLUSTER_LOCK_PV /dev/dsk/block-special-file

where volume-groupis the name of the second volume group and block-special-fileis the physical volume name of a lock disk in the chosen volume group. These lines should be added for each node; for example:

SECOND_CLUSTER_LOCK_VG /dev/vglock

SECOND_CLUSTER_LOCK_PV /dev/dsk/c4t0d0

or (using agile addressing; see “About Device File Names (Device Special Files)” (page 80)):

SECOND_CLUSTER_LOCK_VG /dev/vglock

SECOND_CLUSTER_LOCK_PV /dev/disk/disk100

NOTE: If you are using cDSFs, the device file would be in the /dev/rdisk/ directory; for example /dev/rdisk/disk100. See “About Cluster-wide Device Special Files (cDSFs)” (page 104).

See also “Choosing Cluster Lock Disks” (page 173).

Specifying a Lock LUN

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 also “Cluster Lock

”(page 46); and see “Setting Up a Lock LUN” (page 174) for configuration information and restrictions.

To specify a lock LUN in the cluster configuration file, enter the lock LUN information following each node name, for example:

NODE_NAME hasupt21

NETWORK_INTERFACE lan1

HEARTBEAT_IP 15.13.173.189

NETWORK_INTERFACE lan2

Configuring the Cluster 189