Serviceguard Version A.11.16 Release Notes, 2nd Edition, September 2004

Serviceguard Version A.11.16 Release Notes, Second Edition
Compatibility Information and Installation Requirements
Chapter 1 19
You can, however, create a cmclnodelist file to act as a “bootstrap”
monitor access. Bootstrap files are useful if you are doing a rolling
upgrade, so the nodes with older versions can still access the newer
cluster nodes. Monitor access in a bootstrap file also means the node can
appear in Serviceguard Manager; you can see information about it in
Properties, and you can configure it into a cluster after you give the root
password.
To create a bootstrap file:
1. Create the file /etc/cmcluster/cmclnodelist on the node.
2. Using any ascii editor, add a comment like this:
###################################################
# Do not try to configure access in this file.
# This is for bootstrapping only, before a cluster is configured.
# Once a cluster exists, Serviceguard will ignore this file.
####################################################
3. Below the comment, create monitor access. You can add a number of
<host_node> <user> pairs, but it may be easiest to add a wildcard +
(plus) below the comment. This is equivalent to granting the
view-only Monitor role to Any User from Any Serviceguard Node.
Using Serviceguard A.11.16 to reach earlier versions
For Serviceguard clusters with versions earlier than A.11.16, access is
granted in the cmclnodelist or .rhosts file. Only a root user can
modify these files to grant access.
In pre-A.11.16 clusters, the only role for a non-root user is Monitor.
To monitor a cluster, modify a (pre-A.11.16) cluster node’s cmclnodelist
file. Read-only access is granted by entering the pair <user_hostname>
<NonRootUser_name>. Or, you can enter a + (plus) wild card to allow any
user.
A command line user can issue the cmviewcl command with this entry.
A Serviceguard Manager user can view a cluster in the map and tree,
and read Properties of all the cluster’s objects. A Serviceguard Manager
user can issue administrative commands if they log in to a Session
Server as root. They can issue configuration commands if they give the
root password for one of the cluster’s nodes.