Netcool/OMNIbus Knowledge Library rules file components
The Netcool/OMNIbus Knowledge Library rules files integrate with supported devices to deliver event correlation and causal analysis for the IBM Tivoli Netcool suite. The main purpose is to provide root cause analysis to ensure that alarms that need to be addressed quickly are acted on fast and the reason for an alarm occurring is correctly identified.
From the release of Netcool/OMNIbus version 7.4 onwards, the MIB Manager utility is fully supported. The Tivoli Netcool/OMNIbus MIB Manager is an IBM Eclipse-based application that you can use to parse Simple Network Management Protocol (SNMP) management information base (MIB) files, from which you can generate Netcool rules files. It is intended as a replacement for the mib2rules utility.
For more information on generating the Netcool/OMNIbus Knowledge Library content explained in this section see the Tivoli Netcool/OMNIbus MIB Manager section in the IBM Tivoli Netcool/OMNIbus Administering the server components guide.
The following table describes the components of a rules file and the role each part plays in monitoring the activity of a supported device.
NcKL rules file component |
Description |
Example |
|---|---|---|
Alert Group |
This value specifies the alert group under which a trap can be grouped. |
Authentication Status |
Alert Key |
The Alert Key contains a descriptive key that indicates the object instance referenced by the alarm. The major goal of the value for this attributes is to ensure proper deduplication of alarms and compatibility with the Generic Clear Automation. The Alert Key should be the SNMP instance of the managed object which is represented by the alarm. Usually, this can be obtained by extracting the instance from the OID of one of the trap's variable bindings. |
"Sys Name: " + $sysName + ", Location: " + $sysLocation OR "ifEntry" + $ifIndex" |
Description |
This value explains the reason for the trap being triggered. |
An altSwTempExceedThreshold trap signifies that the switch temperature has exceeded maximum safety limits. |
Enterprise |
This value specifies the parent object of the trap. |
altTraps |
Module Name |
This value specifies the name of the MIB with which the rules file integrates. |
BNT-GbESM-1G-L2L3-MIB |
|
This value specifies the object identifier (OID) of the object or trap. |
.1.3.6.1.4.1.1872.2.5.7.3 |
|
This value specifies the SNMP trap version.
The
Object Type value can have the following valid
properties:
|
TRAP-TYPE NOTIFICATION-TYPE |
|
This value specifies the status of trap. |
current oboslete |
Severity |
This value specifies the alert severity that activates the trap to generate alerts. |
(0) CLEAR (1) INDETERMINATE (2) WARNING (3) MINOR (4) MAJOR (5) CRITICAL (6) DISCARD |
Supported Device Name |
This value specifies the name of the devices for which the rules file is valid. |
Layer 2/3 Copper Gigabit Ethernet Switch Module for IBM Blade Center |
Total Number of Traps |
This value specifies the total number of traps that the Netcool/OMNIbus Knowledge Library has for the supported MIB. |
28 |
Traps |
This value specifies the traps that monitor alerts generated by the supported MIB. |
altSwTempExceedThreshold, altSwTempReturnThreshold |
Trap Group |
This value specifies the group under which similar
traps can be grouped. The trap group contains traps in the same |
Group Switch Temperature Status |
Trap Name |
This value specifies the name of the trap. |
altSwTempExceedThreshold |
Variables |
This value specifies the trap attributes, also known as varbinds. A varbind or variable binding is a sequence of two specific fields. The first field is an OID, which addresses a specific parameter. The second field contains the value of the specified parameter. |
|
Vendor |
This value specifies the company that owns the device that the rules files integrate with. |
IBM |
Version |
This value specifies the version of the supported device. |
5.2 |