Managing Serviceguard 13th Edition, February 2007

Serviceguard at a Glance
Using Serviceguard Manager
Chapter 130
Using the Serviceguard Management Application
To open a saved “snapshot” cluster file, specify a filename with the .sgm
extension; you must have view permission on the file and its directory.
To see “live” clusters, from a management station, connect to a
Serviceguard node’s Cluster Object Manager (COM) daemon. (The COM
is automatically installed with Serviceguard.) This node becomes the
session server. It goes out over its subnets, and establishes connections
with the COMs on other Serviceguard nodes. The session server relays
commands from the management station to the target nodes, and relays
the target nodes’ configuration and status data back to the management
station. It also relays operation messages from the target nodes to the
management station.
If the Session Server node is running Serviceguard versions A.11.13
through A.11.17, the Serviceguard Security Patch must be installed and
enabled before the Session Server node can connect to cluster nodes
running A.11.17. See “Editing Security Files” on page 189 for access
requirements.
To connect, you need to specify a valid username and password from the
session server’s /etc/passwd file. List the cluster or clusters you want to
see. Click “unused nodes” to see nodes that are not currently configured
into a cluster, but do have Serviceguard installed.
For the session server to get information from a cluster, the target cluster
must allow it access. The target node will resolve the session server’s
hostname through /etc/hosts or DNS. Access method and non-root
roles changed in Serviceguard Version A.11.16:
In clusters with Serviceguard version A.11.16 and later, the cluster
configuration file or a package configuration file, must have an
Access Control Policy that specifies this triplet: the intended user,
the COM server’s hostname, and a role of at least Monitor.
In earlier versions of Serviceguard, the
/etc/cmcluster/cmclnodelist file must have this pair listed:
COM server’s host_node, and user root. For more information about
earlier versions of Serviceguard, see the appropriate manual and
release notes, posted at: http://docs.hp.com -> High
Availability.