Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
Installing and Running Serviceguard Manager
Chapter 136
If you are updating from an earlier version, think about permissions on
your HP-UX nodes with Serviceguard Version A.11.13, A.11.14, and
A.11.15. 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 or 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.
To set up the highly-available connection between Serviceguard
Manager and Session Server nodes in a cluster, follow these steps:
Create the package in a cluster with Serviceguard. For viewing, use
Serviceguard A.11.12 or later. For administration commands, use
Serviceguard A.11.13 or later.
See Creating the Package Configuration chapter in the Serviceguard
manual. All Serviceguard manuals are posted on the web and you can
view or print them there. Go to http://www.docs.hp.com and click
High Availability; the products are listed alphabetically.
1. Get an IP address to use as the package’s relocatable address. You
can use nslookup to be sure the package name and IP address are
correctly associated in your DNS table.
2. When naming the package, choose one that your users will recognize,
such as Clus3Srvr. The first time a user opens Serviceguard
Manager they will see the Connect dialog box. They can type this
name in for the server connection. After that, the name will appear
in a list every time that user opens Serviceguard Manager.
3. Make only these two modifications to the package configuration file
template, and leave the defaults for the other fields: