ServiceGuard Manager Version A.02.01 Release Notes, July 2002

ServiceGuard Manager Version A.02.01 Release Notes

Compatibility Information and Installation Requirements

Chapter 124

2. Log in to each node and edit the /etc/snmpd.conf ﬁle to remove your

computer from the list.

3. Stop and re-start the SNMP Master Agent on the node.

a. Find the process ID number, using: ps -ef | grep snmp.

The master agent will show as snmpd, and the subagent will

show as cmsnmpd.

b. Stop that process, using: kill <pid>

c. Restart the agents, using /usr/sbin/snmpd and

/sbin/init.d/cmsnmpd start

Setting up ServiceGuard Manager

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 server highly

available. If there is a failure in the connection, you might see the

“Connection Dropped” message ﬂash 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 server

with ServiceGuard A.11.12 or later. A component of ServiceGuard, the

Cluster Object Manager, polls the available subnets to discover other

ServiceGuard objects. It collects status and conﬁguration information,

and sends the information back to ServiceGuard Manager.

To set up the highly-available connection between ServiceGuard

Manager and 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 (with patches).

See “Creating the Package Conﬁguration” 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.