Managing Serviceguard Seventeenth Edition, First Reprint December 2009

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 176). See also the discussion
of the relevant parameters under “Cluster Configuration Parameters ” (page 139), 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 340).
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
will not run. (For cross-subnet configurations, in which a subnet may be configured
on some nodes and not on others, see monitored_subnet_access below, ip_subnet_node
(page 275), and “About Cross-Subnet Failover” (page 190).)
Typically you would monitor the ip_subnet, specifying it here as well as in the ip_subnet
parameter (see below), but you may want to monitor other subnets as well; you can
monitor any subnet that is configured into the cluster (via the STATIONARY_IP or
HEARTBEAT_IP parameter in the cluster configuration file).
If any monitored_subnet fails, Serviceguard will switch the package to any other node
specified by node_name which can communicate on the monitored_subnets defined for
this package. See the comments in the configuration file for more information and
examples.
272 Configuring Packages and Their Services