Integrating NerveCenter with a Network
Management Platform
-
Integrating NerveCenter with Micromuse Netcool/OMNIbus - Netcool Integration Reference - Variable Bindings for NerveCenter Informs -
Previous: Netcool Integration Reference
Next: Integrating NerveCenter with CA Unicenter TNG
Variable Bindings for NerveCenter Informs
Depending on how its behavior models are designed, a NerveCenter detecting particular network conditions can send Inform packets to Micromuse Netcool/OMNIbus. 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 Netcool 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.
The table below 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 |