Professional Documents
Culture Documents
Version 2.0_B12
Reference Guide
December 19, 2008
SC23-6386-02
Tivoli Netcool/OMNIbus Knowledge Library
®
Version 2.0_B12
Reference Guide
December 19, 2008
SC23-6386-02
Note
Before using this information and the product it supports, read the information in Appendix B, “Notices and Trademarks,”
on page 39.
Edition notice
This edition applies to version 2.0_B12 of Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library
(SC23-6386-02) and to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC23-6386-01.
© Copyright International Business Machines Corporation 2006, 2008.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Document control page . . . . . . . . v ATM Forum event sources . . . . . . . . 20
BridgeWater event sources . . . . . . . . 20
Release Notes for IBM Tivoli Chipcom event sources . . . . . . . . . 20
Ciena event sources . . . . . . . . . . 20
Netcool/OMNIbus Knowledge library . . 1 Cisco event sources . . . . . . . . . . . 20
Introduction . . . . . . . . . . . . . . 1 Cisco Latitude event sources. . . . . . . . 24
What is Netcool/OMNIbus Knowledge Library 2.0? 1 Cisco Syslog event sources . . . . . . . . 24
How Netcool/OMNIbus Knowledge Library 2.0 Empirix event sources . . . . . . . . . . 33
operates ? . . . . . . . . . . . . . . . 2 Enterasys event sources . . . . . . . . . 33
About the Netcool/OMNIbus Knowledge Library 2.0 Fore event sources . . . . . . . . . . . 33
installation . . . . . . . . . . . . . . . 4 Foundry event sources. . . . . . . . . . 34
Accompanying publications . . . . . . . . . 4 Huawei event sources . . . . . . . . . . 34
Prerequisites for installation . . . . . . . . . 5 IANA event sources . . . . . . . . . . 35
IBM Tivoli Netcool product requirements . . . . 5 IBM Director event sources . . . . . . . . 35
Other requirements . . . . . . . . . . . 6 IBM event sources . . . . . . . . . . . 35
Installing Netcool/OMNIbus Knowledge Library 6 IBM Vallent event sources . . . . . . . . 35
Setting up probes to use the updated rules files . 9 IEEE event sources . . . . . . . . . . . 35
Downloading additional third party Integrations IETF event sources . . . . . . . . . . . 35
Modules . . . . . . . . . . . . . . 14 Juniper event sources . . . . . . . . . . 36
Uninstalling Netcool/OMNIbus Knowledge Network Harmoni event sources . . . . . . 37
Library 2.0. . . . . . . . . . . . . . 15 Nortel event sources . . . . . . . . . . 37
Known Issues in Netcool/OMNIbus Knowledge NTNTech event sources . . . . . . . . . 38
Library 2.0. . . . . . . . . . . . . . 16 Rapid City event sources . . . . . . . . . 38
Stratacom event sources . . . . . . . . . 38
Appendix A. Supported event sources 19 Synoptics event sources . . . . . . . . . 38
Vendor-specific event sources . . . . . . . . 19
Adtran event sources . . . . . . . . . . 19 Appendix B. Notices and Trademarks 39
ADVA AG Optical Networking event sources . . 19 Notices . . . . . . . . . . . . . . . . 39
Allied Telesyn event sources . . . . . . . . 19 Trademarks . . . . . . . . . . . . . . 41
Ascend event sources . . . . . . . . . . 20
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/
com.ibm.tivoli.nam.doc/welcome_ptsm.htm
Table 1. Document modification history
Document Publication Comments
version date
00 April 26, 2007 First IBM publication.
01 December 14, New and enhanced list of MIBs added.
2007
02 December 19, Prerequisites for installation section updated.
2008
Installing Netcool/OMNIbus Knowledge Library section
updated.
This document describes the Netcool/OMNIbus Knowledge Library 2.0 and its
associated publications, prerequisites, installation, known issues, and lists the
supported event sources.
Introduction
This section provides an overview of IBM Tivoli Netcool/OMNIbus Knowledge
Library 2.0 under the following headings:
v “What is Netcool/OMNIbus Knowledge Library 2.0?”
v “How Netcool/OMNIbus Knowledge Library 2.0 operates ?” on page 2
v “About the Netcool/OMNIbus Knowledge Library 2.0 installation” on page 4
Root cause analysis has become an issue of paramount importance for the
management of communications and information systems infrastructures. Loosely
defined, root cause analysis is the process of making sense of large numbers of
alert, status and informational messages (events) which might be generated by
such infrastructures.
While some events indicate actual failures that require correction, many others are
simply symptoms of the actual failures, or informational messages about normal
operations of the infrastructure. Netcool/OMNIbus Knowledge Library 2.0 aims to
identify which alarms indicate actual failures, allowing repair efforts to focus on
the issues (or root causes) that truly affect the operation of the infrastructure,
without the distraction of the symptomatic or informational events. The end result
is a reduction of Mean Time To Repair and increased availability of the systems.
The probes used by the Netcool/OMNIbus collect and interpret information from
disparate managed objects in a network. A probe parses the collected information,
and sends the parsed data to the ObjectServer in a format as directed by the rules
file and to the expectations of the ObjectServer fields.
The default rules file necessary for the execution of a probe only performs generic
grouping of data. Instead, using a rules file enhanced to cater SNMP MIB events
from a specific device provides sharpened event enrichment and causal analysis.
The Netcool/OMNIbus Knowledge Library 2.0 is a collection of such enhanced
rules files tuned to specific managed objects that send SNMP based events. For
more information, refer to “Setting up probes to use the updated rules files” on
page 9.
When the device sends the SNMP based events as traps, the probe uses the device
specific rules file in the Netcool/OMNIbus Knowledge Library 2.0 specified by the
RulesFile property. For more information, refer to “Configuring the probes
properties files” on page 11.
Note: Not specifying the device specific rules file of the Netcool/OMNIbus
Knowledge Library 2.0 makes the probe to use its default rules file.
The IBM Tivoli Netcool/OMNIbus ObjectServer currently uses two main types of
automation to help reduce the number of events that require operator intervention.
Generic Clear automations are designed to correlate and delete any matching pair
of problem and resolution alerts, whereas deduplication eliminates duplicate alerts
while maintaining an ’occurrence’ count.
Event pre-classification
Intra-device correlation
There are separate automations for determining root causes and symptoms. The
symptom-detecting automations will process an event at least once before the
event is processed by the root-cause-detecting automations. If the event is
identified as a symptom, it will be ignored by the correlation automations. This
allows a more granular control of which events are processed, reducing the load
the automations place on the ObjectServer. The automations are implemented in
the same style as the Generic Clear v7.x automations, using a separate table for
correlating temporarily-held events, further enhancing performance.
You will be required to manually configure the relevant probes to use these
updated rules files. For more information, see “Configuring the probes properties
files” on page 11.
Accompanying publications
To efficiently install IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 and
fully realize the benefits delivered, you must be familiar with the underlying
principles of IBM Tivoli Netcool/OMNIbus v7.x, including the following:
v The IBM Tivoli Netcool/OMNIbus components:
– The ObjectServer (including the database tables and columns)
The documents listed below provide reference information on the related concepts
of IBM Tivoli Netcool/OMNIbus and IBM Tivoli Netcool/OMNIbus Knowledge
Library 2.0.
This book provides instructions for installing and deploying IBM Tivoli
Netcool/OMNIbus, and includes details of the supported platforms and
requirements
This book describes how to perform administrative tasks using the IBM Tivoli
Netcool/OMNIbus Administrator GUI, command line tools and process control.
This book provides general introductory and reference information on probes and
gateways. Documentation on the specific probes discussed within these release
notes is available from the IBM Tivoli Netcool Information Center location:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/
com.ibm.tivoli.nam.doc/welcome_ptsm.htm
Note: IBM Tivoli Netcool/Knowledge Library will not enable AMOS Extended
Event Recognition with versions of IBM Tivoli Network Manager IP Edition earlier
than 3.5.
Other requirements
The following IBM Tivoli Netcool/OMNIbus v7.x specification requirements apply
to this IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 installation:
v Supported operating system platforms
v Java Runtime Environment (JRE) requirements
v User interface requirements
v Disk space requirements
v Browser requirements on Windows platforms
Licensing
For IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 license keys are not
required beyond those relevant to the associated IBM Tivoli Netcool products,
which use the IBM Tivoli software licensing process.
Installation steps
The above steps extract various files related to NcKL 2.0, and also create individual
subdirectories specific to each supported vendors. Each vendor specific directory
contains the vendor specific rules files and lookup files. The RulesFile property in
the snmptrap.rules file enables the probes to use the vendor specific files. For more
information, see “Enabling the probes to use Netcool/OMNIbus Knowledge
Library 2.0” on page 14.
If working within a Windows environment, you will require a Windows utility that
supports *.tar.gz file extractions.
From a command prompt, run the extracted advcorr.sql script using one of the
following platform-dependent, case-sensitive commands:
username and password are your ObjectServer login detailspath_to_file is the directory path to
the files extracted in the previous section
The advcorr.sql script creates the following objects in the ObjectServer, to aid in
determining the causal relevance of events:
v Intra-device correlation (AdvCorr) tables within the alerts database
v Supplementary automations implemented as an AdvCorr trigger group and
three related triggers
v Additional columns in the alerts.status table
Repeat steps 2 and 3 to set up the same conversions for the CauseType column,
substituting CauseType as the Column field entry in step 3.
Use nco_sql to add the following new attributes to the alerts.status table:
alter table alerts.status add column NetworkAssureAlarmId int
alter table alerts.status add column NetworkAssureHost varchar(64)
alter table alerts.status add column NetworkAssurePort int
Note: These columns can also be added by using the IBM Tivoli
Netcool/OMNIbus Administrator GUI.
The RulesFile property in the properties file of the SNMP probe specifies the path
to the snmptrap.rules file, which has all the contents suitable for various vendors.
Enabling the probes to use the rules file of the Netcool/OMNIbus Knowledge
Library is a two-stage process that involves:
1. “Extracting the updated rules files” on page 10
The rules.tar.gz file extracted from the download contains updated rules files to
support the following IBM Tivoli Netcool/OMNIbus probes:
v SNMP probe
v SNMP EMS (Element Management System) probe
v Probe for HP OpenView Network Node Manager (NNM)
v Probe for IBM NetView
v Syslog probe
v Syslogd probe
Note: The updated rules files must be extracted into a specific location on each
machine where these probes are installed.
2. Extract the contents of the rules.tar.gz file into the newly-created directory. If
working within a Windows environment, you will need a utility that can
uncompress and unpack UNIX tar.gz files.
Note: Do not use WinZip for uncompressing/unpacking the pack tar.gz files.
Using WinZip creates an extracted directory structure different to the directory
structure before the extraction.
By default, the files in the tar bundle will be extracted into a rules subdirectory -
for example: /opt/netcool/rules on UNIX.
Note: This location is required for reference within the probe properties files and
the extracted rules files. You might therefore find it useful to make a note of the
path for use in later steps.
For details of the extracted rules files, see “Directory structure and contents of the
updated rules files” on page 12.
Note: For the probe to parse the extracted rules files in AIX, increase the process
memory limit to 1.25 GB. Use the the export LDR_CNTRL =
MAXDATA=0x40000000 command to increase the process memory limit.
The trap-based probes supported by this installation are associated with the
extracted base rules file snmptrap.rules, and the syslog-based probes, with the base
file syslog.rules.
props
HP OpenView nnm6.props RulesFile : "/opt/netcool/rules/snmptrap.rules"
NNM Version 6.x
HP OpenView nnm7.props
NNM Version 7.x
IBM NetView nv5.props RulesFile : "/opt/netcool/rules/snmptrap.rules"
Version 5.x
IBM NetView nv6.props
Version 6.x
IBM NetView nv7.props
Version 7.x
Syslog syslog.props RulesFile : "/opt/netcool/rules/syslog.rules"
Syslogd syslogd.props
If amending the properties files within an AIX environment, replace the UNIX
RulesFile path with the default path to which the rules files were extracted - for
example:
RulesFile : "/usr/netcool/rules/snmptrap.rules"
If amending the properties files within a Windows environment, replace the
UNIX RulesFile path /opt/netcool/rules/ with the relevant Windows path.
Details on the supported platforms for these probes is provided within the
relevant probes documentation.
3. For the changes to take effect, you must now stop and restart the probes either
automatically using process control (on UNIX) or services (on Windows), or
manually from the command line. For example, you can use:
v kill -15 to kill the process, and process control to automatically restart the
probes (on UNIX)
v The Services window to stop and start services if the probes were installed as
services (on Windows)
For further information, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway
Guide, (SC23-6387), and the IBM Tivoli Netcool/OMNIbus Administration Guide,
(SC23-6381).
The following files are added to the /opt/netcool/ (or equivalent platform-
dependent) location as a result of the installation:
Table 6. Structure and contents of installed files
Directory Description
/rules The base IBM Tivoli Netcool/OMNIbus Knowledge
Library 2.0 directory which contains the base rules
files (snmptrap.rules and syslog.rules) and related
files.
/rules/include-common This directory contains include files that provide
probe-independent logic - for example, 3GPP and
TMF814 specific log, lookup table to help convert
between hex, decimal, and ASCII.
/rules/include-compat This directory contains include files to activate
support for various IBM Tivoli Netcool/OMNIbus
Knowledge Library 2.0 features.
/rules/include-snmptrap This directory contains include files for processing
events from the SNMP trap-based probes.
/rules/include-snmptrap/common- This directory contains the common lookup files
lookup that any vendor can use.
/rules/include-snmptrap/generic This directory contains SNMP trap-based include
files that improve the handling of enterprise-specific
implementations of the generic SNMP traps.
#include “$NC_RULES_HOME/include-snmptrap/vendor/vendor.master.include.rules
#include “$NC_RULES_HOME/include-snmptrap/vendor/vendor.preclass.include.
snmptrap.rules
Where vendor is the subdirectory specific to the vendor.
For example, following is an updated and uncommented section of the
snmptrap.rules file when the vendor is IBM:
#include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.master.include.lookup
#include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.master.include.rules
#include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.preclass.include.
snmptrap.rules
4. Restart the SNMP Probe for the probes to use the Netcool/OMNIbus
Knowledge Library 2.0.
Important: Without the above configurations the probes will only use the generic
rules files and ignore the vendor specific rules files.
http://www-01.ibm.com/software/tivoli/opal/ncomnibus/
From a command prompt, run the removeadvcorr.sql script (extracted from the
download) using the relevant platform-dependent, case-sensitive command below:
Table 7. Commands to uninstall Netcool/OMNIbus Knowledge Library 2.0
Platform Required entry
UNIX $OMNIHOME/bin/nco_sql -server objectserver_name -user
username -password password < path_to_file/
removeadvcorr.sql
Windows %OMNIHOME%\bin\redist\isql.exe -S objectserver_name -U
username -P password -i path_to_file\removeadvcorr.sql
where:
username and password are your ObjectServer login detailspath_to_file is the directory
path to the extracted removeadvcorr.sql file
The uninstall process removes the intra-device correlation automations and tables,
but retains the updated rules files and additional alerts.status columns. Based on
your preference, you can now take one of the actions detailed below.
To continue using the rules files and additional columns, no further action is
required.
To continue using the rules files without the columns, you must modify the
base rules files snmptrap.rules and syslog.rules. (See “Directory structure and
contents of the updated rules files” on page 12 for details of the location of these
rules files.) Open each rules file and comment out the line:
include "/opt/netcool/rules/include-compat/AdvCorr36.include.compat.rules"
The include statement above shows the default UNIX path, but the starting
directory in this path might vary depending on your platform.
If you no longer require the rules files or columns, you must edit the trap-based
and syslog-based probe properties files so that they no longer reference the rules
files. To do this, open each probe properties file and comment out each line that
was manually added as part of the IBM Tivoli Netcool/OMNIbus Knowledge
Library 2.0 installation process. (See ″Configuring the probes properties files″ on
v From the IBM Tivoli Netcool/OMNIbus Administrator window, enter and run
the commands below in the SQL interactive interface.
v From the command line of the SQL interactive interface, run the commands
below.
alter table alerts.status drop column LocalTertObj;
alter table alerts.status drop column LocalObjRelate;
alter table alerts.status drop column RemoteTertObj;
alter table alerts.status drop column LocalPriObj;
alter table alerts.status drop column RemoteObjRelate;
alter table alerts.status drop column CorrScore;
alter table alerts.status drop column CauseType;
alter table alerts.status drop column CauseType;
alter table alerts.status drop column LocalSecObj;
alter table alerts.status drop column AdvCorrServerName;
alter table alerts.status drop column AdvCorrServerSerial;
alter table alerts.status drop column LocalRootObj;
Note: If you revert to the old probe properties files or comment out the include
statement in snmptrap.rules and syslog.rules, you must stop and restart your
probes.
You can find the case values of the EX_UNITFAULT and EX_CRASH exceptions using
the value of EX_SI_BASE.
MIBs added to this release are marked and updated MIBs are marked .
v “Vendor-specific event sources”
NcKL 2.0 enables you to add or remove reference to vendor specific rules in the
snmptrap.rules file. The rules files specific to the vendor are available in:
$NC_RULES_HOME/include-snmptrap/. For example, files specific to the vendor
Adtron are available at: $NC_RULES_HOME/include-snmptrap/adtron/.
NIZATION
TDP TESTPA
TFIB TI1570
TIB TIGER
TLV TMQ
TN TN3270
TN3270S TOASTER_IPC
TPLUS TR
TRANGE TRUNK
TRUNK_CLOCK TRUNK_DFC
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM’s suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks of
International Business Machines Corporation in the United States, other countries,
or both.
Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based
trademarks are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, other countries, or both.
Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation
in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Printed in USA
SC23-6386-02