Managing Serviceguard 13th Edition, February 2007

Configuring Packages and Their Services
Creating the Package Configuration
Chapter 6270
#
#RESOURCE_NAME <Full_path_name>
#RESOURCE_POLLING_INTERVAL <numeric_seconds>
#RESOURCE_START <AUTOMATIC/DEFERRED>
#RESOURCE_UP_VALUE <op> <string_or_numeric> [and <op> <numeric>]
# Access Control Policy Parameters.
#
# Three entries set the access control policy for the package:
# First line must be USER_NAME, second USER_HOST, and third USER_ROLE.
# Enter a value after each.
#
# 1. USER_NAME can either be ANY_USER, or a maximum of
# 8 login names from the /etc/passwd file on user host.
# 2. USER_HOST is where the user can issue Serviceguard commands.
# If using Serviceguard Manager, it is the COM server.
# Choose one of these three values: ANY_SERVICEGUARD_NODE, or
# (any) CLUSTER_MEMBER_NODE, or a specific node. For node,
# use the official hostname from domain name server, and not
# an IP addresses or fully qualified name.
# 3. USER_ROLE must be PACKAGE_ADMIN. This role grants permission
# to MONITOR, plus for administrative commands for the package.
#
# These policies do not effect root users. Access Policies here
# should not conflict with policies defined in the cluster configuration file.
#
# Example: to configure a role for user john from node noir to
# administer the package, enter:
# USER_NAME john
# USER_HOST noir
# USER_ROLE PACKAGE_ADMIN
• PACKAGE_TYPE. The traditional Serviceguard package is the
FAILOVER package. It runs on one node at a time. If there is a failure
on the node where the package is running, Serviceguard can fail the
work over to another node.
MULTI_NODE packages can run on several nodes at the same time.
SYSTEM_MULTI_NODE run on all the nodes in the cluster at the same
time. Both multi-node and system multi-node packages are only
supported for applications specified by HP. For example,
Serviceguard A.11.17 supplies one system multi-node package and
two multi-node packages to be used in VERITAS Cluster File System
configurations.