Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5168
# If set in a package configuration file, PACKAGE_ADMIN applies
to that
# package only.
#
# Conflicting or redundant policies will cause an error while
applying
# the configuration, and stop the process. The maximum number
of access
# policies that can be configured in the cluster is 200.
#
#
# Example: to configure a role for user john from node noir to
# administer a cluster and all its packages, enter:
# USER_NAME john
# USER_HOST noir
# USER_ROLE FULL_ADMIN
USER_NAME root
USER_HOST ANY_SERVICEGUARD_NODE
USER_ROLE full_admin
The man page for the cmquerycl command lists the definitions of all the
parameters that appear in this file. Many are also described in the
“Planning” chapter. Modify your $SGCONF/clust1.config file to your
requirements, using the data on the cluster configuration worksheet.
In the file, keywords are separated from definitions by white space.
Comments are permitted, and must be preceded by a pound sign (#) in
the far left column. See the man page for the cmquerycl command for
more details.
Specifying Maximum Number of Configured Packages
Serviceguard preallocates memory and threads at cluster startup time. It
calculates these values based on the number of packages specified in the
MAX_CONFIGURED_PACKAGES parameter in the cluster configuration file.
This value must be equal to or greater than the number of packages
currently configured in the cluster. The default is 0, which means that
you must enter a value if you wish to use packages. The absolute
maximum number of packages per cluster is 150. Serviceguard reserves
6MB of lockable memory when you configure packages plus
approximately 80KB for each package.