Using a VDisk as a cluster lock disk

ServiceGuard does not provide a method for specifying alternate links to a cluster lock disk.

For releases prior to 11.31, when you use a virtual disk (VDisk) as your lock disk in an HP 9000 or HP Integrity clustering environment, the nodes in this cluster cannot access the lock disk when both of the following situations apply:

The path that is defined for the FIRST_CLUSTER_LOCK_PV variable is unavailable.
A 50-50 split in the quorum occurs.

To resolve this issue and to maintain redundancy, specify a different path to the lock disk for each node in your HP 9000 or HP Integrity cluster using the FIRST_CLUSTER_LOCK_PV variable in the cluster configuration ASCII file. For example, if you are configuring a two-node cluster, set the path of FIRST_CLUSTER_LOCK_PV on server A to the first SAN Volume Controller node (through one Fibre Channel switch) and set the FIRST_CLUSTER_LOCK_PV for server B to the second SAN Volume Controller node (through another fibre channel switch).

Note: To determine whether the paths to the lock disk are different on different servers, you must inspect the hardware path.