this list). Used only if a lock disk is used for tie-breaking

 

services. Use FIRST_CLUSTER_LOCK_PV for the first

 

physical lock volume and SECOND_CLUSTER_LOCK_PV

 

for the second physical lock volume, if any. If there is a

 

second physical lock volume, SECOND_CLUSTER_LOCK_PV

 

must be on a separate line. These parameters are used only

 

when you employ a lock disk for tie-breaking services in the

 

cluster.

 

If you need to change the default entries, make sure you

 

enter the physical volume name as it appears on each node

 

in the cluster (the same physical volume may have a different

 

path name on each node).

 

NOTE: If you used the -L lock_vg:lock_pv option of

 

cmquerycl (1m) to specify the cluster lock disk, the

 

correct node-specific paths will already be in the file.

 

If you are creating two cluster locks, enter the physical

 

volume names for both locks. The physical volume group

 

identifier can contain up to 39 characters (bytes).

 

For information about changing the configuration while the

 

cluster is running, see “Updating the Cluster Lock Disk

 

Configuration Online” (page 295). See also “What Happens

 

when You Change the Quorum Configuration Online”

 

(page 49) for important information.

CAPACITY_NAME,

Node capacity parameters. Use the CAPACITY_NAME and

CAPACITY_VALUE

CAPACITY_VALUE parameters to define a capacity for this

 

node. Node capacities correspond to package weights;

 

node capacity is checked against the corresponding

 

package weight to determine if the package can run on that

 

node.

 

CAPACITY_NAME name can be any string that starts and

 

ends with an alphanumeric character, and otherwise

 

contains only alphanumeric characters, dot (.), dash (-),

 

or underscore (_). Maximum length is 39 characters.

 

CAPACITY_NAME must be unique in the cluster.

 

CAPACITY_VALUE specifies a value for the

 

CAPACITY_NAME that precedes it. It must be a floating-point

 

value between 0 and 1000000. Capacity values are

 

arbitrary as far as Serviceguard is concerned; they have

 

meaning only in relation to the corresponding package

 

weights.

 

Capacity definition is optional, but if CAPACITY_NAME is

 

specified, CAPACITY_VALUE must also be specified;

 

CAPACITY_NAME must come first.

 

NOTE: cmapplyconf will fail if any node defines a

 

capacity and any package has min_package_node as

 

its failover_policy (page 237) or automatic as its

 

failback_policy (page 238).

 

To specify more than one capacity for a node, repeat these

 

parameters for each capacity. You can specify a maximum

118 Planning and Documenting an HA Cluster

Page 118
Image 118
HP Serviceguard Cluster is running, see Updating the Cluster Lock Disk, When You Change the Quorum Configuration Online