Managing Serviceguard 12th Edition, March 2006

Serviceguard at a Glance
Using Serviceguard Manager
Chapter 1 31
Serviceguard Security Patch installed; the Security must also be enabled
on that node. Also, refer to “Editing Security Files” on page 190 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/hpux/ha.
For information on access policies, refer to “Editing Security Files” on
page 190.
Using Serviceguard Manager, you can create or modify cluster and
package configuration for clusters with Serviceguard Version A.11.16 or
later, if you give the root (UID=0) password for a cluster’s node.