Using a volume as a clustered-system lock disk

For releases earlier than to 11.31, when you use a volume as your lock disk in an HP 9000 or HP Integrity environment, the nodes in this system 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 maintain redundancy, specify a different path to the lock disk for each node in your HP 9000 or HP Integrity system by using the FIRST_CLUSTER_LOCK_PV variable in the system configuration ASCII file. For example, if you are configuring a two-node system:

• Set the path of FIRST_CLUSTER_LOCK_PV on server A to the first system node (through one Fibre Channel switch).
• Set the FIRST_CLUSTER_LOCK_PV for server B to the second system node (through another Fibre Channel switch).