NOTE: cmquerycl (1m) detects first-level routers in the cluster (by looking for gateways in each node's routing table) and lists them here as polling targets. If you run cmquerycl with the -w full option (for full network probing) it will also verify that the gateways will work correctly for monitoring purposes.

Can be changed while the cluster is running; must be removed if the preceding SUBNET entry is removed.

MAX_CONFIGURED_PACKAGES This parameter sets the maximum number of packages that can be configured in the cluster.

The minimum value is 0, and the maximum value is 300. The default value is 300, and you can change it without halting the cluster.

WEIGHT_NAME, WEIGHT_DEFAULT Default value for this weight for all packages that can have weight; see “Rules and Guidelines” (page 150) under“About Package Weights” (page 144). WEIGHT_NAME specifies a name for a weight that exactly corresponds to a CAPACITY_NAME specified earlier in the cluster configuration file. (A package has weight; a node has capacity.) The rules for forming WEIGHT_NAME are the same as those spelled out for CAPACITY_NAME earlier in this list.

These parameters are optional, but if they are defined, WEIGHT_DEFAULT must follow WEIGHT_NAME, and must be set to a floating-point value between 0 and 1000000. If they are not specified for a given weight, Serviceguard will assume a default value of zero for that weight. In either case, the default can be overridden for an individual package via the weight_name and weight_value parameters in the package configuration file.

For more information and examples, see “Defining Weights” (page 148).

IMPORTANT: CAPACITY_NAME, WEIGHT_NAME, and weight_value must all match exactly.

NOTE: A weight (WEIGHT_NAME, WEIGHT_DEFAULT) has no meaning on a node unless a corresponding capacity (CAPACITY_NAME, CAPACITY_VALUE) is defined for that node.

For the reserved weight and capacity package_limit, the default weight is always one. This default cannot be changed in the cluster configuration file, but it can be overridden for an individual package in the package configuration file.

cmapplyconf will fail if you define a default for a weight but do not specify a capacity of the same name for at least one node in the cluster. You can define a maximum of four WEIGHT_DEFAULTs per cluster.

Can be changed while the cluster is running.

124 Planning and Documenting an HA Cluster

Page 124
Image 124
HP Serviceguard manual Planning and Documenting an HA Cluster