Serviceguard Manager Version A.04.00 Release Notes, June 2004

Serviceguard Manager Version A.04.00 Release Notes
Installing and Running Serviceguard Manager
Chapter 134
Bootstrapping a new A.11.16 node If you have a cluster on an
A.11.16 node, be sure to configure at least one Access Control Policy if
you want to see the cluster and its nodes in Serviceguard Manager. Once
a cluster is configured, Serviceguard will only check access in the
cluster’s configuration files. It will ignore the .rhosts file and the
cmclnodelist file.
If no cluster is configured, you can create a cmclnodelist file to act as a
“bootstrap” for access. Once done, you will be able to see information
about the node on the Serviceguard Manager map and tree, and in
Properties. If it is not a part of a cluster now, it will still show up in the
Unused Nodes list. To configure it later, you can connect to a Session
Server with Serviceguard version A.11.16, select the node from Unused
Nodes, and select Configuration from the Actions menu.
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 so Serviceguard can
discover and display the node as an unused node.
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. It will allow any session on the node’s
subnet to query the cluster and display its information in any session
of Serviceguard Manager.
Alternately, you can list any number of <hostname> <username>
pairs. Hostname can be any Session Server’s name, and user can be
any name in that Session Server’s /etc/passwd file.
Now you will be able to see your new A.11.16 node in a Serviceguard
Manager session. If the Session Server also has version A.11.16, you can
configure this node into a cluster. You will be prompted for the node’s root
password.