ServiceGuard Manager Version A.03.00 Release Notes, December 2002

ServiceGuard Manager Version A.03.00 Release Notes

Compatibility Information and Installation Requirements

Chapter 1 21

If you have installed any of these, the install process automatically does

these things:

• Adds a menu item and a button on the toolbar of NNM, ITO, or OVO

to start ServiceGuard Manager (“ServiceGuard Mgr Launcher”).

• Sends ServiceGuard events to be logged in the Event Log. The

ServiceGuard subagent is responsible for notifying the management

station when status or conﬁguration changes. By default, it is

installed in /usr/lbin/cmsnmpd.

• Adds ServiceGuard messages to the ITO or OVO Message Browser if

assigned, and in the NNM Alarm Browser.

• Modiﬁes the Event Conﬁguration Tool so you can set up automatic

actions and ﬁlter ServiceGuard messages.

• Lets you conﬁgure the data collection to get historical MIB data from

network nodes, including data stored in ServiceGuard MIB objects.

The ServiceGuard subagent services the ServiceGuard MIB objects.

By default, it is installed in /usr/lbin/cmsnmpd.

Then the installation process looks to see if you have OVO or ITO

Version 5.3 or later. If so, it checks to see if you also have ClusterView.

If you do have ClusterView installed, no ﬁles will be overwritten. The

launcher will be installed, so you can open an instance of ServiceGuard

Manager from the OpenView menu.

If you do not have ClusterView, but you do have ITO or OVO, tools are

added to the Tool Bank, ready for an OpenView administrator to assign

them. These tools are listed below.

Assign these tools carefully. Some require root access to the

ServiceGuard nodes, and some can grant it indirectly.

• ServiceGuard Mgr launcher: You can launch ServiceGuard Manager

from OpenView. ServiceGuard Manager is independent of OpenView.

It does not use the OV daemons or object database to discover the

conﬁguration or status of clusters. Instead, it gets information by

connecting to ServiceGuard Version A.11.12 or greater; then

ServiceGuard goes out on its subnets and gathers the information.

• Installs these Tools to work on a selected cluster node:

— HA Info Tools: