HP Serviceguard Developer's Toolbox Version B.12.00.00 For HP-UX and Linux

# configuration file takes precedence. This allows you to set
# an overall default, but to override it for a particular package.
#
# For example, if you specify WEIGHT_NAME "memory" with WEIGHT_DEFAULT
# 1000 in the cluster configuration file, and you do not specify a weight
# value for "memory" in the package configuration file for pkgA, pkgA's
# "memory" weight will be 1000. If you define a weight value of 2000 for
# "memory" in the configuration file for pkgA, pkgA's "memory" weight
# will be 2000.
#
# If no WEIGHT_NAME/WEIGHT_DEFAULT value is specified in the cluster
# configuration file for a given CAPACITY, and weight_name and weight_value
# are not specified in this package configuration file for that CAPACITY,
# then the weight_value for this package is set to zero or one depending
# on the capacity name. If the capacity name is the reserved capacity
# "package_limit", the weight_value for this package is set to one;
# otherwise, the weight_value is set to zero.
# For example, if you specify CAPACITY "memory" and do not specify
# a WEIGHT_DEFAULT for "memory" in the cluster configuration file,
# and do not specify weight "memory" in the package configuration
# file for pkgA, then pkgA's "memory" weight will be zero.
#
# Note that cmapplyconf will fail if you define a weight in the
# package configuration file and no node in the cluster configuration
# file specifies a capacity of the same name.
#
# Weight can be assigned only to multi-node packages, and failover packages
# with configured_node as the failover_policy and manual as failback policy.
#
# For more information on how to configure default weights and
# node capacities, see the cmquerycl man page, the cluster configuration
# template file, and the Managing Serviceguard manual.
#
# Example :
# weight_name package_limit
# weight_value 10
#
# This overrides the default value of 1 and sets the weight for this
# package to 10
#
# Legal values for weight_name:
# Any string that starts and ends with an alphanumeric character, and
# contains only alphanumeric characters, dot(.), dash(-), or underscore(_)
# in the middle.
# Maximum string length is 39 characters.
#
# Legal values for weight_value:
# Any unsigned floating point string. Only 3 digits after the decimal point
# are significant. Maximum string length is 11 characters.
#
# weight_name
# weight_value
# "monitored_subnet" specifies the addresses of subnets that are to be monitored for this package.
#
# Enter the network subnet name that is to be monitored for this package.
# Repeat this line as necessary for additional subnets. If any of
# the subnets defined goes down, the package will be switched to another
# node that is configured for this package and has all the defined subnets
# available.
#
# "monitored_subnet" replaces "subnet".
#
# The subnet names can be IPv4 or IPv6, or a mix of both.
#
# Example :
# monitored_subnet 192.10.25.0
# (netmask=255.255.255.0)
# monitored_subnet 2001::/64
# (netmask=ffff:ffff:ffff:ffff::)
# monitored_subnet 2001::
# (netmask=ffff:ffff:ffff:ffff::)
# Legal values for monitored_subnet: <Any String>
# "monitored_subnet_access" defines how the monitored_subnet is
# configured in the cluster.
#
#
# monitored_subnet_access defines whether access to a monitored_subnet
# is configured on all of the nodes that can run this package, or only
# some. Possible values are "partial" and "full". "partial" means that
# the monitored_subnet is expected to be configured on one or more of
# the nodes this package can run on, but not all. "full" means that the
# monitored_subnet is expected to be configured on all the nodes that
# this package can run on. "full" is the default. (Specifying "full" is
# equivalent to not specifying the monitored_subnet_access at all.)
#
# The monitored_subnet_access is defined per monitored_subnet entry.
#
# Example :
# monitored_subnet 192.10.25.0
# monitored_subnet_access partial
# 192.10.25.0 is available on one
#
# or more nodes of the cluster,
22 MySQL Toolkit scripts