Using Serviceguard Extension for RAC, 9th Edition, September 2010

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for RAC (SGeRAC)

HOSTNAME_ADDRESS_FAMILY IPV4

# IP Monitor Configuration Parameters.

# The following set of three parameters can be repeated as necessary.

# SUBNET is the subnet to be configured whether or not to be monitored

# at IP layer.

# IP_MONITOR is set to ON if the subnet is to be monitored at IP layer.

# IP_MONITOR is set to OFF if the subnet is not to be monitored at IP layer.

# POLLING_TARGET is the IP address to which polling messages are sent

# from each network interface in the subnet.

# Each SUBNET can have multiple polling targets, so multiple

# POLLING_TARGET entries can be specified. If no POLLING_TARGET is

# specified, peer interfaces in the subnet will be polling targets for each other.

# Only subnets with a gateway that is configured to accept

# ICMP Echo Request messages will be included by default with IP_MONITOR

# set to ON, and with its gateway listed as a POLLING_TARGET.

SUBNET 16.89.112.0

IP_MONITOR ON

POLLING_TARGET 16.89.112.1

SUBNET 10.142.1.0

IP_MONITOR OFF

SUBNET 10.142.2.0

IP_MONITOR OFF

SUBNET fec0:0:0:8e01::

IP_MONITOR OFF

SUBNET 3ffe:1000:0:8e01::

IP_MONITOR OFF

SUBNET fec0:0:0:8e02::

IP_MONITOR OFF

SUBNET 3ffe:1000:0:8e02::

IP_MONITOR OFF

# Package Configuration Parameters.

# Enter the maximum number of packages which will be configured in the cluster.

# You can not add packages beyond this limit.

# This parameter is required.

MAX_CONFIGURED_PACKAGES 300

# Optional package default weight parameters. Use WEIGHT_NAME and

# WEIGHT_DEFAULT parameters to define a default value for this weight

# for all packages except system multi-node packages.

# Package weights correspond to node capacities; node capacity

# is checked against the corresponding package weight to determine

# if the package can run on that node.

# WEIGHT_NAME

# specifies a name for a weight that corresponds to a

# capacity specified earlier in this file. Weight is defined for

# a package, whereas capacity is defined for a node. For any given

weight/capacity pair, WEIGHT_NAME, CAPACITY_NAME (and weight_name

# in the package configuration file) must be the same. The rules for

# forming all three are the same. See the discussion of the capacity

# parameters earlier in this file.

# 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 example, if CAPACITY_NAME "memory" is not defined for

# node1, then node1's "memory" capacity is assumed to be infinite.

# Now even if pkgA, pkgB, and pkgC each specify the maximum weight

# of 1000000 for WEIGHT_NAME "memory", all three packages are eligible

# to run at the same time on node1, assuming all other requirements are met.

# WEIGHT_DEFAULT specifies a default weight for this WEIGHT_NAME.

# This is a floating point value between 0 and 1000000.

# Package weight default values are arbitrary as far as Serviceguard is

# concerned; they have meaning only in relation to the corresponding node

# capacities.

# The package weight default parameters are optional. If they are not

# specified, a default value of zero will be assumed. If defined,

# WEIGHT_DEFAULT must follow WEIGHT_NAME. To specify more than one package

Cluster Configuration ASCII File 87