Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
Installing and Running Serviceguard Manager
Chapter 1 35
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.
Logins, roles and security, Version A.11.15 and earlier:
If you are an experienced Serviceguard user, you may think there is a
similarity between the command-line user’s cmviewcl command and the
way Serviceguard Manager user gets information about remote clusters
with Serviceguard version A.11.15 and earlier. Using Serviceguard
Manager, certain users can also relay the most common administrative
commands to these Serviceguard clusters, and the effect seems the same
as logging into the node and issuing the command on the command line.
Please notice, however, that the permissions and access mechanisms are
actually not the same. In version A.11.15 and earlier, the Serviceguard
Manager user’s permissions depend on his login to the Session Server,
not the cluster node. It is the Session Server that interacts with the
cluster nodes on the user’s behalf, through the Cluster Object Manager, a
Serviceguard API.
A Serviceguard Manager user does not need to directly access target
nodes to do configuration of Serviceguard version 11.16. Users can log
into a Session Server as any user. However, before the user can configure
any object they see in the map or tree they must give a root password for
at least one of the cluster nodes.
If the target node has version A.11.15 or earlier, the Session Server node
must always use user= root to access it. The recommended access
mechanism is to include the Session Server name or IP address in the
target nodes’ cmclnodelist file. A less secure way is to include the
Session Server node in a target node’s .rhosts file. Listing in
cmclnodelist allows contact to Serviceguard alone; a listing in .rhosts
grants wider access.
If the user is logged in as root to a Session Server node with version
A.11.15 or earlier, the Session Server node will also display certain
common administrative commands in the menu. The Session Server
relays these commands to the clusters in the session for the users.