Managing Serviceguard Eighteenth Edition, September 2010

target polling; see “How the IP Monitor Works”
(page 99) for more information.
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 195) under“About Package Weights”
(page 187). 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 192).
166 Planning and Documenting an HA Cluster