Integrating NerveCenter with a Network Management Platform - Integrating NerveCenter with CA Unicenter TNG - Unicenter Integration Reference -
How to Configure CA Unicenter TNG to Integrate with the NerveCenter Universal Platform Adapter      Integrating NerveCenter with Tivoli TME

Unicenter Integration Reference

The following section includes information you may need to reference occasionally when integrating NerveCenter and CA Unicenter TNG.

This section includes:

Command line reference for Integrating NerveCenter with Unicenter

During a typical NerveCenter installation, the NerveCenter Universal Platform Adapter is installed as a service or daemon. However, there may be times in which you will want to make changes from the command line. From a command prompt type the following:


   paserver [-u ON|OFF] [-d] [-g] [-h] [-o] [-p] [-r] [-scm a|m|r|s] [-v]
[-tcfg] [-?]

Variable Bindings for NerveCenter Informs

Depending on how its behavior models are designed, a NerveCenter detecting particular network conditions can send Inform packets to CA Unicenter TNG. Although these Inform packets use TCP/IP, they are similar in content to an SNMP trap, containing trap numbers (generic and specific), an enterprise OID, and a variable-binding list. The lengthy varbinds contains information about the alarm that performed the Inform action, such as the name of alarm, the object the alarm was monitoring, and the names of the origin and destination alarm states.

The Unicenter receiving the trap can make use of the information in the variable bindings much the same way it would use variable bindings found in an SNMP trap.

Inform Trap Variable Bindings explains the contents of this variable-binding list.

Inform Trap Variable Bindings

Variable Binding Value

0

The name of the domain where NerveCenter is running

1

The name of the host machine running the NerveCenter Server

2

The name of the managed node associated with the alarm

3

The base object associated with the alarm (for example, ifEntry for a monitored interface)

4

The base object instance associated with the alarm (for example, 4 for the fourth interface)

5

The name of the subobject. This would include the null string if the alarm is not associated with an alarm.

6

The property group assigned to the node or the subobject

7

The name of the alarm

8

The alarm's property

9

The name of the trigger that caused the alarm transition

10

The state of the alarm before the transition

11

The severity of the state of the alarm prior to the transition

12

The state of the alarm after the transition

13

The severity of the state of the alarm after the transition

14

The maximum severity of all active alarms for the managed node before this alarm transition

15

The maximum severity of all active alarms for the managed node after this alarm transition

16

The variable bindings in the poll or trap that caused the transition. These variable bindings are formatted as follows:
Attribute ncTransitionVarBinds = attribute.instance=value;attribute=value;...

17

The identification number of the alarm instance

How to Configure CA Unicenter TNG to Integrate with the NerveCenter Universal Platform Adapter Integrating NerveCenter with Tivoli TME
29 July 2003