Managing Serviceguard Eighteenth Edition, September 2010

Both parameters are optional, but if weight_value is specified, weight_name must also
be specified, and must come first. You can define up to four weights, corresponding
to four different capacities, per cluster. To specify more than one weight for this package,
repeat weight_name and weight_value.
NOTE: But if weight_name is package_limit, you can use only that one weight and
capacity throughout the cluster. package_limit is a reserved value, which, if used,
must be entered exactly in that form. It provides the simplest way of managing weights
and capacities; see “Simple Method” (page 188) for more information.
The rules for forming weight_name are the same as those for forming package_name
(page 288). weight_name must exactly match the corresponding CAPACITY_NAME.
weight_value is an unsigned floating-point value between 0 and 1000000 with at most
three digits after the decimal point.
You can use these parameters to override the cluster-wide default package weight that
corresponds to a given node capacity. You can define that cluster-wide default package
weight by means of the WEIGHT_NAME and WEIGHT_DEFAULT parameters in the
cluster configuration file (explicit default). If you do not define an explicit default (that
is, if you define a CAPACITY_NAME in the cluster configuration file with no
corresponding WEIGHT_NAME and WEIGHT_DEFAULT), the default weight is
assumed to be zero (implicit default). Configuring weight_name and weight_value here
in the package configuration file overrides the cluster-wide default (implicit or explicit),
and assigns a particular weight to this package.
For more information, see “About Package Weights” (page 187). See also the discussion
of the relevant parameters under “Cluster Configuration Parameters ” (page 143), in
the cmmakepkg (1m) and cmquerycl (1m) manpages, and in the cluster
configuration and package configuration template files.
New for 11.19.
local_lan_failover_allowed
Specifies whether or not Serviceguard can transfer the package IP address to a standby
LAN card in the event of a LAN card failure on a cluster node.
Legal values are yes and no. Default is yes.
monitored_subnet
A LAN subnet that is to be monitored for this package. Replaces legacy SUBNET which
is still supported in the package configuration file for legacy packages; see “Configuring
a Legacy Package” (page 375).
You can specify multiple subnets; use a separate line for each.
If you specify a subnet as a monitored_subnet the package will not run on any node not
reachable via that subnet. This normally means that if the subnet is not up, the package
296 Configuring Packages and Their Services