Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5 185
• USER_HOST is the node where USER_NAME will issue Serviceguard
commands.
NOTE The commands must be issued on USER_HOST but can take effect on
other nodes; for example patrick can use bit’s command line to
start a package on gryf (assuming bit and gryf are in the same
cluster).
Choose one of these three values for USER_HOST:
— ANY_SERVICEGUARD_NODE - any node on which Serviceguard is
configured, and which is on a subnet with which nodes in this
cluster can communicate (as reported by cmquerycl -w full).
NOTE If you set USER_HOST to ANY_SERVICEGUARD_NODE, set USER_ROLE
to MONITOR; users connecting from outside the cluster cannot
have any higher privileges (unless they are connecting via rsh or
ssh; this is treated as a local connection).
Depending on your network configuration,
ANY_SERVICEGUARD_NODE can provide wide-ranging read-only
access to the cluster.
— CLUSTER_MEMBER_NODE - any node in the cluster
— A specific node name - Use the hostname portion (the first of
four parts) of a fully-qualified domain name that can be resolved
by the name service you are using; it should also be in each
node’s /etc/hosts. Do not use an IP addresses or the
fully-qualified domain name. If there are multiple hostnames
(aliases) for an IP address, one of those must match USER_HOST.
See “Configuring Name Resolution” on page 146 for more
information.
• USER_ROLE must be one of these three values:
— MONITOR
— FULL_ADMIN
— PACKAGE_ADMIN