Serviceguard Manager Version A.05.01 Release Notes, February 2007

Serviceguard Manager Version A.05.01 Release Notes
Installing and Running Serviceguard Manager
Chapter 138
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 A.11.16.xx or
A.11.17.xx. 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.xx 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.xx 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.
If you are updating from an earlier version, think about permissions on
your HP-UX nodes with Serviceguard Version A.11.13.xx, A.11.14.xx,
and A.11.15.xx. Any person who can log in to that node as root may be
able to do administrative commands on any cluster objects on that node’s
subnets. If you do not want access, you can limit the root logins on that
node, or limit that node’s access to particular clusters on its subnets.
Making a Highly Available Connection
If you wish, you can create a Serviceguard package that will keep the
connection between your monitoring station and the Session Server
highly available. If there is a failure in the connection, you might see the
Connection Dropped message flash momentarily, but Serviceguard will
maintain your connection. It will fail the connection over from one node
in a Serviceguard cluster to another node in the same cluster.
Serviceguard Manager gets its information by connecting to a Session
Server with Serviceguard A.11.13.00 and later. A component of
Serviceguard, the Cluster Object Manager, polls the available subnets to
discover other Serviceguard objects. It collects status and configuration
information, and sends the information back to Serviceguard Manager.