This action might not be possible to undo. Are you sure you want to continue?
Reference Guide December 19, 2008
Tivoli Netcool/OMNIbus Knowledge Library
Reference Guide December 19, 2008
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.
Document control page . . . . . . . . v Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library . . 1
Introduction . . . . . . . . . . . . . . 1 What is Netcool/OMNIbus Knowledge Library 2.0? 1 How Netcool/OMNIbus Knowledge Library 2.0 operates ? . . . . . . . . . . . . . . . 2 About the Netcool/OMNIbus Knowledge Library 2.0 installation . . . . . . . . . . . . . . . 4 Accompanying publications . . . . . . . . . 4 Prerequisites for installation . . . . . . . . . 5 IBM Tivoli Netcool product requirements . . . . 5 Other requirements . . . . . . . . . . . 6 Installing Netcool/OMNIbus Knowledge Library 6 Setting up probes to use the updated rules files . 9 Downloading additional third party Integrations Modules . . . . . . . . . . . . . . 14 Uninstalling Netcool/OMNIbus Knowledge Library 2.0. . . . . . . . . . . . . . 15 Known Issues in Netcool/OMNIbus Knowledge Library 2.0. . . . . . . . . . . . . . 16 ATM Forum event sources . . BridgeWater event sources . . Chipcom event sources . . . Ciena event sources . . . . Cisco event sources . . . . . Cisco Latitude event sources. . Cisco Syslog event sources . . Empirix event sources . . . . Enterasys event sources . . . Fore event sources . . . . . Foundry event sources. . . . Huawei event sources . . . . IANA event sources . . . . IBM Director event sources . . IBM event sources . . . . . IBM Vallent event sources . . IEEE event sources . . . . . IETF event sources . . . . . Juniper event sources . . . . Network Harmoni event sources Nortel event sources . . . . NTNTech event sources . . . Rapid City event sources . . . Stratacom event sources . . . Synoptics event sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 20 20 20 20 24 24 33 33 33 34 34 35 35 35 35 35 35 36 37 37 38 38 38 38
Appendix A. Supported event sources
Vendor-specific event sources . . . . . . Adtran event sources . . . . . . . . ADVA AG Optical Networking event sources Allied Telesyn event sources . . . . . . Ascend event sources . . . . . . . . . . . . . . . . . .
19 19 19 19 20
Appendix B. Notices and Trademarks
Notices . . . Trademarks . . . . . . . . . . . . . . . . . . . . . . . . .
. 39 . 41
© Copyright IBM Corp. 2006, 2008
iv IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
2008 v .jsp?topic=/ com. 2006.ibm.0 section added. visit the IBM® Tivoli® Information Center: http://publib.tivoli. Unsupported list of MIBs are removed.doc/welcome_ptsm. TheRelease Notes for IBM Tivoli Netcool/OMNIbus Knowledge library documentation is provided in softcopy format only.ibm.com/infocenter/tivihelp/v8r1/index. 2007 December 19. © Copyright IBM Corp.htm Table 1. To obtain the most recent version.nam. Directory structure and contents of the updated rules files section updated. 2008 New and enhanced list of MIBs added. Enabling the probes to use Netcool/OMNIbus Knowledge Library 2.Document control page Use this information to track changes between versions of this guide. New and enhanced list of MIBs added. Installing Netcool/OMNIbus Knowledge Library section updated. December 14.boulder. Prerequisites for installation section updated. Document modification history Document version 00 01 02 Publication date Comments April 26. 2007 First IBM publication.
vi IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
0 aims to identify which alarms indicate actual failures. root cause analysis is the process of making sense of large numbers of alert. 2008 1 .Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library Welcome to IBM Tivoli Netcool/OMNIbus Knowledge Library 2. IBM Tivoli Netcool/OMNIbus Knowledge Library 2. allowing repair efforts to focus on the issues (or root causes) that truly affect the operation of the infrastructure. 2006.0 installation” on page 4 What is Netcool/OMNIbus Knowledge Library 2. The end result is a reduction of Mean Time To Repair and increased availability of the systems. Loosely defined. and provides unprecedented levels of event correlation and causal analysis for the IBM Tivoli Netcool suite. This document describes the Netcool/OMNIbus Knowledge Library 2.0” on page 16 Introduction This section provides an overview of IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 and its associated publications. or informational messages about normal operations of the infrastructure.0 is a collection of rules files written to a common standard. Root cause analysis has become an issue of paramount importance for the management of communications and information systems infrastructures. Netcool/OMNIbus Knowledge Library 2. prerequisites. and lists the supported event sources. This release notes contains the following sections: v “Introduction” v “Accompanying publications” on page 4 v “Prerequisites for installation” on page 5 v “Installing Netcool/OMNIbus Knowledge Library” on page 6 v “Known Issues in Netcool/OMNIbus Knowledge Library 2. While some events indicate actual failures that require correction. many others are simply symptoms of the actual failures. © Copyright IBM Corp. known issues.0.0?” v “How Netcool/OMNIbus Knowledge Library 2. installation. without the distraction of the symptomatic or informational events. status and informational messages (events) which might be generated by such infrastructures.0 operates ?” on page 2 v “About the Netcool/OMNIbus Knowledge Library 2.0 is positioned to complement the current out-of-the-box event correlation capabilities of IBM Tivoli Netcool/OMNIbus (and IBM Tivoli Network Manager IP Edition where available) by enabling enhanced root cause analysis.0? Netcool/OMNIbus Knowledge Library 2.0 under the following headings: v “What is Netcool/OMNIbus Knowledge Library 2.
0 operates ? Netcool/OMNIbus is a Service Level Management (SLM) system that presents a consistent and consolidated view of the current state of all the Netcool/OMNIbus managed systems to specific users. Instead. A probe parses the collected information.0 improves the capability of the Netcool/OMNIbus in providing more valuable information. Generic Clear automations are designed to correlate and delete any matching pair of problem and resolution alerts. The Netcool/OMNIbus Knowledge Library 2. The Netcool/OMNIbus Knowledge Library 2. Note: Not specifying the device specific rules file of the Netcool/OMNIbus Knowledge Library 2. For more information. refer to “Configuring the probes properties files” on page 11.0 is a collection of such enhanced rules files tuned to specific managed objects that send SNMP based events. v AMOS Extended Event Recognition (for IBM Tivoli Network Manager IP Edition integration): This process provides IBM Tivoli Network Manager IP Edition with 2 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . where this can be determined without the need for correlation.0 makes the probe to use its default rules file.rules file. The Netcool/OMNIbus Knowledge Library 2. The default rules file necessary for the execution of a probe only performs generic grouping of data. rules file and Netcool Knowledge Library The probes used by the Netcool/OMNIbus collect and interpret information from disparate managed objects in a network. Probes.0 specified by the RulesFile property.0 additionally increases the ability of the Tivoli Netcool/OMNIbus ObjectServer automations to correlate alarms and identify root causes by employing the following techniques: v Event Pre-Classification: This process identifies and flags events within the probe rules files to indicate the causal relevance of events. v Intra-Device Correlation: This process enhances probe rules files and adds automations to the ObjectServer to perform correlation beyond deduplication and problem/resolution correlation. using a rules file enhanced to cater SNMP MIB events from a specific device provides sharpened event enrichment and causal analysis.0. How Netcool/OMNIbus Knowledge Library 2. ObjectServer and Netcool Knowledge Library The IBM Tivoli Netcool/OMNIbus ObjectServer currently uses two main types of automation to help reduce the number of events that require operator intervention.Important: From version 2. Netcool/OMNIbus Knowledge Library enables the user to refer vendor related rules files in the snmptrap. 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. refer to “Setting up probes to use the updated rules files” on page 9. For more information. identifying intra-device root causes and symptoms. The rules files specific to vendors are available in: $NC_RULES_HOME/include-snmptrap/. whereas deduplication eliminates duplicate alerts while maintaining an ’occurrence’ count. the probe uses the device specific rules file in the Netcool/OMNIbus Knowledge Library 2. When the device sends the SNMP based events as traps.
or power loss. Root cause events include many events on the physical plane . which does not cause any other fault condition other than that the accounting file can no longer be written to. the virtual circuits (DLCIs) traversing that interface will fail. For example. the virtual circuit failures are deemed symptoms of the Frame Relay interface failure. Examples of informational events include Neighbor Adjacency Establishment events. a Frame Relay interface failure is the root cause of the virtual circuits (DLCIs) failures. IBM believes that there is value in identifying singularities as events are received. by identifying a larger set of events for analysis. An example of a singularity is the Accounting File Full condition on some Cisco equipment.for example. and which does not cause other degraded conditions or failures in related entities. It can be argued that a singularity is equivalent to a root cause. successful call establishment messages. and leaves it to other correlation engines and event management methods to implement the flexibility necessary to provide the system operator a choice of how singularities are finally considered. The event pre-classification mechanism implemented in Netcool/Knowledge Library overcomes these shortcomings.a larger dataset upon which to perform topology-based event correlation. Based on the example above. and/or the accuracy of analysis. Event pre-classification Current root cause analysis/event correlation systems rely on one or more correlation/analysis engines to determine the causal relationships between events. To facilitate pre-classification.0 employs the following guidelines in determining the causal relevance to pre-classify events in the catalog: v Root Cause: An event with a condition that is known not to be caused by any other detectable condition. certain card pulls. if a Frame Relay interface fails. and are forced to perform root cause analysis operations on the full set of events. v Symptom: An event with a condition that was caused by the degraded condition or failure of higher level entities or processes in a system. v Information: A message that indicates non-fault-related conditions which might be of interest to system operators. For example. These existing systems ignore the simple ’common sense’ understanding of the events as they are received. Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 3 . v Singularity: An event with a condition that is not directly caused by any other degraded condition or failure. and recovery messages relating to the physical plane. entries in the catalog are restricted to those events whose causal relevance can be determined from only the data contained within the received event message. A root cause event generally results in a degraded condition or failure of other related entities in a system. This causal type catalog is referenced by a probe’s rules file to determine the causal relevance of a received event before it is forwarded to the ObjectServer. IBM Tivoli Netcool/OMNIbus Knowledge Library 2. a catalog of known events and their causal type is implemented as a lookup table in IBM Tivoli Netcool/OMNIbus Knowledge Library 2. Such events also include messages that indicate the clearing or resolution of previously-occurring fault-related conditions. The first two techniques are described below in further detail. device shutdown.0. This reduces the efficiency of the root cause analysis system. While causal relevance can be determined by any combination of correlation and analysis methods within an engine.
0 installation incorporates a series of automatic and manual processes to add the following to your existing IBM Tivoli Netcool/OMNIbus installation: v New tables to the ObjectServer database for reference by probe rules files.v Unknown: An event that cannot be classified as a root cause. identifying intra-device 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. While they cannot be pre-classified. You will be required to manually configure the relevant probes to use these updated rules files. using a separate table for correlating temporarily-held events. Intra-device correlation Intra-device correlation is implemented as a collection of ObjectServer automations that determine the causal relevance of intra-device events by using algorithms which consider managed object parent/child relationships. symptom. You will be required to manually add conversions for two of these columns from the IBM Tivoli Netcool/OMNIbus Administrator GUI.x.x automations. v Intra-device correlation automations implemented as triggers within a trigger group These triggers get automatically fired to perform correlation beyond deduplication and problem/resolution correlation. Accompanying publications To efficiently install IBM Tivoli Netcool/OMNIbus Knowledge Library 2. see “Adding conversions to the ObjectServer” on page 9.0 and fully realize the benefits delivered. further enhancing performance. singularity or informational event. This allows a more granular control of which events are processed. For more information. or for use with the supplied intra-device correlation automations v New columns to the alerts. – Perform intra-device correlation to identify root causes and symptoms. v Updated rules files that have been enhanced to: – Identify and flag events according to their causal relevance.0 installation The IBM Tivoli Netcool/OMNIbus Knowledge Library 2. If the event is identified as a symptom. About the Netcool/OMNIbus Knowledge Library 2. you must be familiar with the underlying principles of IBM Tivoli Netcool/OMNIbus v7. reducing the load the automations place on the ObjectServer. it will be ignored by the correlation automations. For more information. unknown events may be further analyzed by one or more engines to later determine their true causal relevance. see “Configuring the probes properties files” on page 11. The automations leverage information revealed about the relationships to determine related events and test them for causal relevance.status table. The automations are implemented in the same style as the Generic Clear v7. There are separate automations for determining root causes and symptoms. including the following: v The IBM Tivoli Netcool/OMNIbus components: – The ObjectServer (including the database tables and columns) 4 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
– Probes (including editing probe properties and stopping/restarting probes) – Desktop tools (including event lists. As such.doc/welcome_ptsm. the IBM Tivoli Netcool/OMNIbus Knowledge Library 2. conversions and automations The documents listed below provide reference information on the related concepts of IBM Tivoli Netcool/OMNIbus and IBM Tivoli Netcool/OMNIbus Knowledge Library 2. Documentation on the specific probes discussed within these release notes is available from the IBM Tivoli Netcool Information Center location: http://publib.ibm.x ObjectServer.htm Prerequisites for installation This section describes the software and hardware requirements for an IBM Tivoli Netcool/OMNIbus Knowledge Library 2.x IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 dependencies on other IBM Tivoli Netcool products. filters and views) – Administration tools (including the IBM Tivoli Netcool/OMNIbus Administrator.x directory structure and necessary configuration files v Basic rules file syntax including the use of lookup tables (both inline as well as separate files) v Permissions. IBM Tivoli Netcool/OMNIbus™ Installation and Deployment Guide This book provides instructions for installing and deploying IBM Tivoli Netcool/OMNIbus. Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 5 .com/infocenter/tivihelp/v8r1/index. command line tools and process control.0.tivoli.5 or higher Installation of IBM Tivoli Network Manager IP Edition 3.5 or higher is optional.ibm. IBM Tivoli Netcool product requirements This section describes the IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0 provides enhanced root cause analysis for events held within the IBM Tivoli Netcool/OMNIbus v7. IBM Tivoli Netcool/OMNIbus v7.0 installation.nam. and includes details of the supported platforms and requirements IBM Tivoli Netcool/OMNIbus™ Administration Guide This book describes how to perform administrative tasks using the IBM Tivoli Netcool/OMNIbus Administrator GUI.jsp?topic=/ com. the SQL interactive interface and process control) v The IBM Tivoli Netcool/OMNIbus v7.boulder. IBM Tivoli Netcool/OMNIbus™ Probe and Gateway Guide This book provides general introductory and reference information on probes and gateways.x. IBM Tivoli Network Manager IP Edition 3.0 installation requires prior installation of IBM Tivoli Netcool/OMNIbus v7.
x ObjectServer v IBM Tivoli Netcool/OMNIbus probes for SNMP. Installation steps The installation procedure involves a number of steps to be carried out in the following sequence: 1. your IBM Tivoli Network Manager IP Edition event gateway will already be configured to integrate with. 3. Topology-based event correlation will be enabled for those events that have been appropriately pre-classified by the rules files in the IBM Tivoli Netcool/OMNIbus Knowledge Library 2. “Downloading the installation from IBM” on page 7. Installing Netcool/OMNIbus Knowledge Library This section provides instructions for installing and uninstalling IBM Tivoli Netcool/OMNIbus Knowledge Library.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 These specifications are documented within the IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide. Network Node Manager (NNM) and/or Syslog These probes may be installed on the same or a different machine as the ObjectServer installation.x specification requirements apply to this IBM Tivoli Netcool/OMNIbus Knowledge Library 2.5.x ObjectServer” on page 7.x ObjectServer. Other requirements The following IBM Tivoli Netcool/OMNIbus v7. 6 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . “Configuring the IBM Tivoli Netcool/OMNIbus v7. “Setting up probes to use the updated rules files” on page 9 The sections below document these steps in detail.0. the following IBM Tivoli Netcool products must be installed and running: v IBM Tivoli Netcool/OMNIbus v7. (GI11-8064).0 license keys are not required beyond those relevant to the associated IBM Tivoli Netcool products. 2. Licensing For IBM Tivoli Netcool/OMNIbus Knowledge Library 2. NetView. Prior to installation of IBM Tivoli Netcool/OMNIbus Knowledge Library 2.0.If using IBM Tivoli Network Manager IP Edition in conjunction with the IBM Tivoli Netcool/OMNIbus v7. IBM Tivoli Netcool/OMNIbus Knowledge Library 2. and recognize events generated by. 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. which use the IBM Tivoli software licensing process.0.
0 is distributed as a compressed tar file that can be downloaded from IBM: 1.0.jsp?productID=%20&productName=Netcool/OMNIbus&international= &fileName=netcool-omnibus%20&ppa=&zseries= 2. The RulesFile property in the snmptrap. From a command prompt. v NcoGateInserts.ibm. v removeadvcorr. “Adding conversions to the ObjectServer” on page 9 Configuring the ObjectServer to support intra-device correlations You must perform this task as an IBM Tivoli Netcool/OMNIbus v7.ReleaseID . download the file NcKL-1. v license.gz . case-sensitive commands: Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 7 . For further details.4.com/software/tivoli/howtobuy/how-tobuy. and also create individual subdirectories specific to each supported vendors.0” on page 15on page 19.gz file extractions. If working within a Windows environment.tar.0_B12. Go to the IBM Web site to obtain the file: http://www-01.x user with ISQLWrite permissions.gz.tar.sql .gz. but retains other components for continued use if preferred. “Configuring the ObjectServer to support intra-device correlations” 2. The above steps extract various files related to NcKL 2. For more information.Downloading the installation from IBM IBM Tivoli Netcool/OMNIbus Knowledge Library 2. see “Enabling the probes to use Netcool/OMNIbus Knowledge Library 2. Extract the contents of this file to a temporary location of your choice.x ObjectServer This is a two-stage process that involves: 1.sql . see “Uninstalling Netcool/OMNIbus Knowledge Library 2.Contains exact NcKL release version.This file configures the ObjectServer for the (advanced) intra-device correlations.tar.0” on page 14.rules file enables the probes to use the vendor specific files. Download the file NcKL2.0 components from the ObjectServer. The extracted files include: v advcorr.tar.Extract this file to have updated vendor specific rules files enhanced to support root cause analysis. v rules. run the extracted advcorr. Note: To install Netcool/OMNIbus Netcool Knowledge Library 1. 3.4. Configuring the IBM Tivoli Netcool/OMNIbus v7. Each vendor specific directory contains the vendor specific rules files and lookup files.cfg . you will require a Windows utility that supports *.sql script using one of the following platform-dependent.Contains table which is used to perform topology-based event correlation.This file removes some IBM Tivoli Netcool/OMNIbus Knowledge Library 2.
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 8 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 2..exe -S objectserver_name -U username -P password -i path_to_file\advcorr.. no such tables or triggers exist. at or near 'AdvCorr_LPC_RC' ERROR=Object not found on line 1 of statement 'drop trigger AdvCorr_LPC_Sym. at or near 'AdvCorr_LPC_Sym' ERROR=Object not found on line 4 of statement '-.sql %OMNIHOME%\bin\redist\isql. at or near 'AdvCorrLpcRcCand' (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) (0 rows affected) The advcorr. and an error listing is generated on completion..Drop tables in case they already exist from a previous installation..'..'..AdvCorrLpcRcCand.. at or near 'AdvCorrLpcSymCand' ERROR=Object not found on line 1 of statement 'drop table alerts..x on Windows objectserver_name represents the name assigned to your ObjectServer username and password are your ObjectServer login detailspath_to_file is the directory path to the files extracted in the previous section Required entry $OMNIHOME/bin/nco_sql -server objectserver_name -user username -password password < path_to_file/advcorr. the script attempts to drop intra-device correlation tables (and associated triggers) which might have been created during a previous installation. As this is a first-time installation.sql As part of the configuration..'.x on UNIX %OMNIHOME% represents your installation location of IBM Tivoli Netcool/OMNIbus v7.'..'.sql script creates the following objects in the ObjectServer. at or near 'AdvCorr_SetCauseType' ERROR=Object not found on line 1 of statement 'drop trigger AdvCorr_LPC_RC... These messages are harmless and can be ignored.. Required platform-dependent commands for configuring the ObjectServer Platform UNIX Windows where: $OMNIHOME represents your installation location of IBM Tivoli Netcool/OMNIbus v7. A sample output is shown below: ERROR=Object not found on line 102 of statement '--####################################################################### ######.
status add column NetworkAssurePort int Note: These columns can also be added by using the IBM Tivoli Netcool/OMNIbus Administrator GUI. Setting up probes to use the updated rules files Rules files of the Netcool/OMNIbus Knowledge Library adheres to a common standard and enable event correlation and causal analysis. Conversion details window entries Value 0 1 2 3 4 Conversion Unknown Root cause Symptom Singularity Information Repeat steps 2 and 3 to set up the same conversions for the CauseType column.rules file.status table as a result of the ObjectServer configuration. 3. (SC23-6381).status table Use nco_sql to add the following new attributes to the alerts. Click the Add Conversion button to access the Conversion Details window. clicking the OK button to save each set of entries. These conversions translate Type integer values (0 .4) into descriptive ’causal relevance’ text for display within the event list. which has all the contents suitable for various vendors. For further information on conversions. Select AdvCorrCauseType from the Column drop-down list. the Conversions window should appear. To add the required conversions: 1.status table: Use nco_sql to add the following new attributes to the alerts. Table 3.status table: alter table alerts.Adding conversions to the ObjectServer Conversions are required to support two of the new columns (AdvCorrCauseType and CauseType) that were added to the alerts. substituting CauseType as the Column field entry in step 3. From the IBM Tivoli Netcool/OMNIbus Administrator window.status add column NetworkAssureHost varchar(64) alter table alerts. The RulesFile property in the properties file of the SNMP probe specifies the path to the snmptrap. and then click the Conversions icon. “Extracting the updated rules files” on page 10 Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 9 . On completion. see the IBM Tivoli Netcool/OMNIbus Administration Guide. Enabling the probes to use the rules file of the Netcool/OMNIbus Knowledge Library is a two-stage process that involves: 1. and then make the following entries within the Value and Conversion fields.status add column NetworkAssureAlarmId int alter table alerts. 2. Updating the alerts. click the Visual drop-down list.
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.tar.gz file into the newly-created directory. If working within a Windows environment. By default. To extract the rules files: 1. Note: This location is required for reference within the probe properties files and the extracted rules files. “Configuring the probes properties files” on page 11 Extracting the updated rules files The rules. From the machine(s) on which the probes are installed. Using WinZip creates an extracted directory structure different to the directory structure before the extraction. Note: For the probe to parse the extracted rules files in AIX. Use the the export LDR_CNTRL = MAXDATA=0x40000000 command to increase the process memory limit. Extract the contents of the rules. see “Directory structure and contents of the updated rules files” on page 12. you will need a utility that can uncompress and unpack UNIX tar. and set NC_RULES_HOME env variable respectively: Table 4. You might therefore find it useful to make a note of the path for use in later steps. create a directory within the relevant IBM Tivoli Netcool installation location for your platform. the files in the tar bundle will be extracted into a rules subdirectory for example: /opt/netcool/rules on UNIX. Default locations on various platforms Platform UNIX AIX Windows Default location /opt/netcool /usr/netcool C:\Program Files\Netcool NC_RULES_HOME /opt/netcool/rules /usr/netcool/rules/ C:\Program Files\Netcool\ rules 2. increase the process memory limit to 1. 10 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .25 GB.gz files. Note: Do not use WinZip for uncompressing/unpacking the pack tar. For details of the extracted rules files.tar.2.gz files.
To configure these probes to reference these base rules files: 1. 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) Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 11 .rules" If amending the properties files within a Windows environment. 3. The next two steps require details of the path into which you extracted the updated rules files. For example. or manually from the command line. with the base file syslog. For example. Details on the supported platforms for these probes is provided within the relevant probes documentation.rules.x HP OpenView NNM Version 7. Navigate to the location $OMNIHOME/probes/arch.props syslogd. Using a text editor that is appropriate for your platform (vi for Solaris.x IBM NetView Version 5. Notepad for Windows).Configuring the probes properties files The trap-based probes supported by this installation are associated with the extracted base rules file snmptrap. (This table shows the UNIX defaults. the default location for a Solaris installation is /opt/netcool/omnibus/probes/solaris2.props mttrapd_ems. modify the properties files listed in Table 5 with the specified entries. where arch is the name of the platform on which the probe was installed.x Syslog Syslogd nnm6.x IBM NetView Version 6. and the syslog-based probes.rules" RulesFile : "/opt/netcool/rules/snmptrap.props nv6.rules" RulesFile : "/opt/netcool/rules/snmptrap. you must now stop and restart the probes either automatically using process control (on UNIX) or services (on Windows). 2.props nnm7.props RulesFile : "/opt/netcool/rules/syslog.rules. Required modifications to probes properties files Probe SNMP SNMP EMS File name to edit mttrapd. For the changes to take effect. props HP OpenView NNM Version 6.props nv7.) Table 5.for example: RulesFile : "/usr/netcool/rules/snmptrap.rules" Required modification (UNIX defaults) RulesFile : "/opt/netcool/rules/snmptrap. you can use: v kill -15 to kill the process.props nv5. replace the UNIX RulesFile path with the default path to which the rules files were extracted .x IBM NetView Version 7.rules" MIBFile : "" QuietOutput : 1 If amending the properties files within an AIX environment.props syslog. replace the UNIX RulesFile path /opt/netcool/rules/ with the relevant Windows path.
Full details of these event sources are provided in Appendix A.rules and syslog. “Supported event sources. Directory structure and contents of the updated rules files The IBM Tivoli Netcool/OMNIbus Knowledge Library 2.” on page 19.0 features. This directory contains the common lookup files that any vendor can use. /rules/include-common /rules/include-compat /rules/include-snmptrap /rules/include-snmptrap/commonlookup /rules/include-snmptrap/generic 12 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . (SC23-6381). (SC23-6387). Structure and contents of installed files Directory /rules Description The base IBM Tivoli Netcool/OMNIbus Knowledge Library 2. and the command nco_p_probename [ -option [ value ] .v CTRL+C to stop the probes. lookup table to help convert between hex.rules) and related files. Cisco Enterprise MIBs and Cisco Syslog facilities. This directory contains SNMP trap-based include files that improve the handling of enterprise-specific implementations of the generic SNMP traps. The following files are added to the /opt/netcool/ (or equivalent platformdependent) location as a result of the installation: Table 6. This directory contains include files for processing events from the SNMP trap-based probes.0 directory which contains the base rules files (snmptrap. This directory contains include files that provide probe-independent logic .. 3GPP and TMF814 specific log.for example. ] to restart the probes if they were installed as console applications (on Windows) For further information.. see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.0 installation supplies updated rules files that deliver support for ATM Forum MIBs. IETF RFC-based MIBs. decimal. IEEE MIBs. This directory contains include files to activate support for various IBM Tivoli Netcool/OMNIbus Knowledge Library 2. and the IBM Tivoli Netcool/OMNIbus Administration Guide. and ASCII.
exe). v vendor-preclass.snmptrap. This directory contains include files for processing events from the Syslog-based probes .Table 6. but does not include the Winsyslog probe (nco_p_winsyslog.lookup .This file lists all the lookup files related to that vendor. Structure and contents of installed files (continued) Directory /rules/include-snmptrap/vendor Description This directory identifies the specific vendor and contains the following set of master and preclass files that improve the handling of enterprise-specific implementations of the traps specific to the vendor: v vendor.This file contains the include statement defining the path to the vendor specific rules file of the user in the include-snmptraps directory.rules .master.sev.This file contains the include statement defining the path to the vendor specific lookup file in the include-snmptraps directory. v $vendor-MIB. v vendor.include.include.include.include.user. /rules/include-syslog /rules/include-syslog/regmatch Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 13 .adv.snmptrap.snmptrap.lookup .rules . Note that this includes the Windows version of the Syslog Daemon probe (nco_p_syslogd.snmptrap. v $vendor_MIB. v $vendor-MIB.lookup . /rules/include-snmptrap/nco_tdc This directory contains SNMP trap-based include files that are based on the output of the nco_tdc tool.snmptrap. /rules/include-syslog/cisco-ios This directory contains Syslog-based include files for the processing of syslog messages from various Cisco syslog facilities.include.include. v $vendor-MIB. This directory contains include files that use regular expressions or other matching techniques to make a best guess at the source of an event received by the Syslog-based probe.master.exe).include.This file lists the severity lookup files related to the vendor. v vendor-preclass.rules .lookup .snmptrap.lookup . v $vendor-MIB.snmptrap.This file lists all the rules files related to that vendor.This file contains the include statement defining the path to the vendor specific rules file in the include-snmptraps directory.This file contains the include statement defining the path to the vendor specific lookup file for the advanced traps in the include-snmptraps directory.rules .This file contains all the PreClassification entries related to that vendor.This file maps the PreClassification entries to Object Server.
snmptrap. For example.preclass.tar. following is an updated and uncommented section of the snmptrap. Important: Without the above configurations the probes will only use the generic rules files and ignore the vendor specific rules files.0_B12.master.com/software/tivoli/opal/ncomnibus/ 14 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .master.include. Downloading additional third party Integrations Modules Additional Integration Modules providing inter-operability between the Tivoli portfolio and third party products are available online for download from the IBM Tivoli Open Process Automation Library (OPAL).rules.Note: IBM recommends that any user customizations are made within the user include files.include.rules file when the vendor is IBM: #include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.rules Where vendor is the subdirectory specific to the vendor.lookup #include “$NC_RULES_HOME/include-snmptrap/vendor/vendor. The Netcool/OMNIbus OPAL catalog contains validated Integration Modules developed by IBM under the IBM Tivoli Netcool Technology Program or by partners.include.include.rules #include “$NC_RULES_HOME/include-snmptrap/vendor/vendor.include. In the RulesFile property.) In future upgrades.preclass.4: 1.master. Restart the SNMP Probe for the probes to use the Netcool/OMNIbus Knowledge Library 2.rules file: #include “$NC_RULES_HOME/include-snmptrap/vendor/vendor.user.rules file extracted from the NcKL-2. you can then choose to retain your existing user include files. specify the path to the snmptrap.rules #include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.include. Enabling the probes to use Netcool/OMNIbus Knowledge Library 2. where sometext can be a reference to the event source or probe type.master. uncomment the following lines from the snmptrap.include. Open the properties file of the SNMP probe. To include a set of vendor-specific rules. 3.rules 4. 2.gz.0 Netcool/OMNIbus Knowledge Library 2.ibm. (These are usually in the format sometext. removing the need for updating the new files with your current customizations.0 provides an option to use vendor specific rules files that enable correlation and causal analysis of events specific to the vendors.sometext. The following configurations make the probes to use the rules file of the Netcool/OMNIbus Knowledge Library 2. snmptrap. The IBM Tivoli Netcool/OMNIbus OPAL catalog is available at: http://www-01.lookup #include “$NC_RULES_HOME/include-snmptrap/ibm/ibm.0 instead of the rules file specified for Netcool/OMNIbus Knowledge Library 1.0.
To continue using the rules files and additional columns.Uninstalling Netcool/OMNIbus Knowledge Library 2. run the removeadvcorr.0 To uninstall IBM Tivoli Netcool/OMNIbus Knowledge Library 2. (See ″Configuring the probes properties files″ on Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 15 . 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. Commands to uninstall Netcool/OMNIbus Knowledge Library 2. 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.compat.sql script (extracted from the download) using the relevant platform-dependent.0 Platform UNIX Required entry $OMNIHOME/bin/nco_sql -server objectserver_name -user username -password password < path_to_file/ removeadvcorr.x on UNIX %OMNIHOME% represents your installation location of IBM Tivoli Netcool/OMNIbus v7.x on Windows objectserver_name represents the name assigned to your ObjectServer username and password are your ObjectServer login detailspath_to_file is the directory path to the extracted removeadvcorr.sql file On successful completion.x user with ISQLWrite permissions.exe -S objectserver_name -U username -P password -i path_to_file\removeadvcorr. no further action is required. To continue using the rules files without the columns.rules and syslog. but retains the updated rules files and additional alerts. you must modify the base rules files snmptrap. you must be working as an IBM Tivoli Netcool/OMNIbus v7. To do this.include.sql %OMNIHOME%\bin\redist\isql. From a command prompt. but the starting directory in this path might vary depending on your platform. Based on your preference.status columns.0. you can now take one of the actions detailed below. the following lines are generated: (0 rows affected) (0 rows affected) (0 rows affected) The uninstall process removes the intra-device correlation automations and tables.) Open each rules file and comment out the line: include "/opt/netcool/rules/include-compat/AdvCorr36. (See “Directory structure and contents of the updated rules files” on page 12 for details of the location of these rules files.rules" The include statement above shows the default UNIX path.sql Windows where: $OMNIHOME represents your installation location of IBM Tivoli Netcool/OMNIbus v7.rules. case-sensitive command below: Table 7.
alter alter alter alter alter alter alter alter alter alter alter alter table table table table table table table table table table table table alerts.snmptrap. Known Issues in Netcool/OMNIbus Knowledge Library 2.user. run the commands below. v From the command line of the SQL interactive interface.status alerts. LocalRootObj.rules.status alerts. CorrScore. RemoteObjRelate. AdvCorrServerName.CISCO-LATITUDE-MIB. mpMinSwAlarm sent from the devices loaded with the MIB named CISCO-LATITUDE. by entering the case values of EX_UNITFAULT and EX_CRASH in the latitude. enter and run the commands below in the SQL interactive interface. CauseType.page 15 for further details of these entries. These exceptions are for the traps mpMajHwAlarm.status alerts.status alerts.0: No event is displayed for the EX_UNITFAULT and EX_CRASH exceptions in the Event List.rules and latitude-CISCOLATITUDE.status alerts.) You must then manually remove or drop the columns from the alerts.status alerts.include. RemoteTertObj.status table: Table 8. you can enable their display in the Event List.status alerts. LocalSecObj. AdvCorrServerSerial.status alerts. Columns to be dropped from the alerts.status drop drop drop drop drop drop drop drop drop drop drop drop column column column column column column column column column column column column LocalTertObj. you must stop and restart your probes. 16 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .lookup files.status alerts. LocalPriObj.status table Drop these columns: LocalTertObj LocalObjRelate RemoteTertObj LocalPriObj RemoteObjRelate CorrScore CauseType LocalSecObj AdvCorrCauseType AdvCorrServerName AdvCorrServerSerial LocalRootObj v From the IBM Tivoli Netcool/OMNIbus Administrator window.0 This section contains the known issues that may occur while using the Netcool/OMNIbus Knowledge Library 2. You can find the case values of the EX_UNITFAULT and EX_CRASH exceptions using the value of EX_SI_BASE. Full details on dropping columns are provided in the IBM Tivoli Netcool/OMNIbus Administration Guide. Note: If you revert to the old probe properties files or comment out the include statement in snmptrap. However. CauseType.status alerts.rules and syslog.status table using one of these methods: v From the IBM Tivoli Netcool/OMNIbus Administrator window. mpMajSwAlarm.include.snmptrap.MIB. (SC23-6381). mpMinHwAlarm. LocalObjRelate.status alerts. drop the following columns from the alerts.
Table 9 shows method to calculate the case values of the EX_UNITFAULT and EX_CRASH exceptions. Calculating case values of the EX_UNITFAULT and EX_CRASH exceptions Exception code EX_UNITFAULT EX_CRASH Calculating the case values EX_SI_BASE + 129 EX_SI_BASE + 73 Release Notes for IBM Tivoli Netcool/OMNIbus Knowledge library 17 . Table 9.
18 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
3 and 2. Adtran event sources The following table lists the Adtran specific MIB event sources.mib © Copyright IBM Corp.0 of IBM Tivoli Netcool/OMNIbus Knowledge Library. Supported Allied Telesyn MIB event sources Allied Telesyn MIBs ALLIEDTELESYN-MIB ATKKNBSW-MIB AtiL2-MIB ATSWTCH2-MIB ATI-MIB ATMCCommon-MIB AtiSwitch.2. 1. Supported ADVA AG Optical Networking MIB event sources ADVA AG Optical Networking MIBs FSP2000-R2-MIB Allied Telesyn event sources The following table lists the Allied Telesyn specific MIB event sources. Table 12.0 support.0.1. Supported event sources This appendix contains the vendor specific event sources for which the rules files have been enhanced upto version 2. For example. Table 11.0 enables you to add or remove reference to vendor specific rules in the snmptrap. 1.rules file.Appendix A. v “Vendor-specific event sources” Vendor-specific event sources The following tables list the vendor specific MIB event sources that IBM Tivoli Netcool/OMNIbus Knowledge Library versions 1. The rules files specific to the vendor are available in: $NC_RULES_HOME/include-snmptrap/. files specific to the vendor Adtron are available at: $NC_RULES_HOME/include-snmptrap/adtron/. MIBs added to this release are marked and updated MIBs are marked . Table 10. 2006. Supported Adtran MIB event sources Adtran MIBs ADTRAN-ACTDAXL3-MIB ADTRAN-ADVISOR-MIB ADTRAN-DSU3AR-MIB ADTRAN-ACTDAXL ADTRAN-DSU3AR ADVA AG Optical Networking event sources The following table lists the ADVA AG Optical Networking specific MIB event sources. 2008 19 . 1. NcKL 2.
Supported BridgeWater MIB event sources BridgeWater MIBs BW-NOTIFICATION BW-RADIUS Chipcom event sources The following table lists the Chipcom specific MIB event sources. Table 13. Supported Chipcom MIB event sources Chipcom MIBs CHIPCOM. Supported ATM Forum MIB event sources ATM Forum MIBs ATM-FORUM-MIB ATM-TRACE-MIB ATM-SOFT-PVC-MIB IMA-MIB BridgeWater event sources The following table lists the BridgeWater specific MIB event sources.Ascend event sources The following table lists the Ascend specific MIB event sources. Supported Ciena MIB event sources Ciena MIBs IPI-GSLAMAG-MIB IPI-OAMP-MIB ipi-memmgmt MIB ipi-gslamag MIB IPI-MEMMGMT-MIB internetphotonics-IPI-GSLAMAG ipi-oamp MIB ipi-services MIB Cisco event sources The following table lists the Cisco specific MIB event sources. Supported Ascend MIB event sources Ascend MIBs APS-MIB ATM Forum event sources The following table lists the ATM Forum specific MIB event sources. Table 14. Table 15. Table 17.mib Ciena event sources The following table lists the Ciena specific MIB event sources. Table 18. Table 16. Supported Cisco MIB event sources Cisco MIBs CISCO-CCME CISCO-5800-HEALTH-MON-MIB 20 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
Supported event sources 21 .Table 18. Supported Cisco MIB event sources (continued) Cisco MIBs CISCO-SRST-MIB ACCOUNTING-CONTROL-MIB ACCOUNTING-CONTROL-MIB CISCO-6400-CHASSIS-MIB CISCO-ACCESS-ENVMON-MIB CISCO-ACCESS-ENVMON-MIB CISCO-APS-MIB CISCO-6400-CHASSIS-MIB CISCO-ATM-PVCTRAP-EXTN-MIB CISCO-ATM-IF-MIB CISCO-BGP4-MIB CISCO-BBSM-MIB CISCO-C2900-MIB CISCO-CALL-TRACKER-MIB CISCO-CALL-TRACKER-MIB CISCO-CCME-MIB CISCO-CCME-MIB MPLS-LDP-MIB CISCO-CCM-MIB CISCO-CALLHOME-MIB CISCO-CLUSTER-MIB CISCO-CONFIG-MAN-MIB CISCO-CONFIG-MAN-MIB CISCO-CONTENT-NETWORK-MIB CISCO-CONTENT-NETWORK-MIB CISCO-DIST-DIRECTOR CISCO-DM-MIB CISCO-BITS-CLOCK CISCO-DOCS-REMOTE-QUERY-MIB CISCO-DOCS-REMOTE-QUERY-MIB CISCO-DOT11-CONTEXT-SERVICES CISCO-BULK-FILE CISCO-DS1-EXT CISCO-DSPU-MIB CISCO-DSP-MGMT-MIB CISCO-DSP-MGMT-MIB CISCO-CABLE-QOS-MONITOR CISCO-CABLE-SPECTRUM CISCO-ENTITY-ALARM-MIB CISCO-ENTITY-ALARM-MIB CISCO-ENVMON-MIB CISCO-EXT-SCSI-MIB CISCO-EXT-SCSI-MIB CISCO-ES-STACK-MIB CISCO-FC-FE-MIB CISCO-5800-HEALTH-MON-MIB CISCO-AAA-SERVER-MIB CISCO-AAA-SERVER-MIB CISCO-ALPS-MICISCO-ALPS-MIB CISCO-ATM-DUAL-PHY-MIB CISCO-ATM-DUAL-PHY-MIB CISCO-ATM-PVCTRAP-EXTN-MIBB CISCO-APS-MIB CISCO-ATM-IF-MIB CISCO-BGP4-MIB CISCO-BBSM-MIB CISCO-C2900-MIB CISCO-BSTUN-MIB CISCO-BSTUN-MIB CISCO-C8500-REDUNDANCY-MIB CISCO-C8500-REDUNDANCY-MIB CISCO-CCM-MIB MPLS-LDP-MIB CISCO-CALLHOME-MIB CISCO-CHANNEL CISCO-CLUSTER-MIB CISCOWORKS CISCO-CIPCMPC-MIB CISCO-CIPCMPC-MIB CISCO-CONFIG-COPY-MIB CISCO-CONFIG-COPY-MIB CISCO-CONTENT-ENGINE-MIB CISCO-CONTENT-ENGINE-MIB CISCO-DM-MIB CISCO-DLSW-EXT-MIB CISCO-DLSW-EXT-MIB CISCO-DOCS-EXT-MIB CISCO-DOCS-EXT-MIB CISCO-DOT11-QOS CISCO-CABLE-AVAILABILITY CISCO-CABLE-METERING CISCO-DSPU-MIB CISCO-ENHANCED-IPSEC-FLOW CISCO-ENHANCED-MEMPOOL CISCO-ENTITY-FRU-CONTROL-MIB CISCO-ENTITY-FRU-CONTROL-MIB CISCO-ENTITY-PFE CISCO-ENVMON-MIB CISCO-CASA CISCO-ENTITY-SENSOR-MIB CISCO-ENTITY-SENSOR-MIB CISCO-ES-STACK-MIB CISCO-FABRIC-C12K CISCO-FABRIC-HFR CISCO-CASA-FA CISCO-CAT6K-CROSSBAR Appendix A.
Supported Cisco MIB event sources (continued) Cisco MIBs CISCO-FC-FE-MIB CISCO-FASTHUB-MIB CISCO-FCTRACEROUTE-MIB CISCO-FCTRACEROUTE-MIB CISCO-FCS-MIB CISCO-FIREWALL CISCO-SRST-MIB CISCO-FSPF-MIB CISCO-FLASH-MIB CISCO-GPRS-CHARGING CISCO-CFS CISCO-GPRS-GTP-MIB CISCO-GTP-DIRECTOR CISCO-HC-ALARM CISCO-HEALTH-MONITOR CISCO-ICSUDSU-MIB CISCO-CSG CISCO-IETF-DOT11-QOS-EXT CISCO-IETF-ISNS-MGMT CISCO-IF-THRESHOLD-MIB CISCO-IF-THRESHOLD-MIB CISCO-IPMROUTE-MIB CISCO-IPMROUTE-MIB CISCO-IPSEC-MIB CISCO-IPSEC-MIB CISCO-ISDN-MIB CISCO-ISDN-MIB CISCO-ISCSI-MIB CISCO-L2-DEV-MONITORING CISCO-IETF-SCTP-EXT CISCO-LICENSE-MGR CISCO-LINK-ERROR-MONITOR CISCO-LOCAL-DIRECTOR-MIB CISCO-LOCAL-DIRECTOR-MIB CISCO-MOBILE-IP-MIB CISCO-MOBILE-IP-MIB CISCO-OAM-MIB CISCO-OAM-MIB CISCO-NS-MIB CISCO-OSCP-MIB CISCO-OSCP-MIB CISCO-IETF-VDSL-LINE CISCO-ISCSI-MIB CISCO-OSPF-TRAP CISCO-OUTAGE-MONITOR CISCO-FASTHUB-MIB CISCO-FCPING-MIB CISCO-FCPING-MIB CISCO-FCC-MIB CISCO-FCC-MIB CISCO-FCS-MIB CISCO-FDMI-MIB CISCO-FEATURE-CONTROL CISCO-CDL CISCO-CDMA-AHDLC CISCO-FSPF-MIB CISCO-FLASH-MIB CISCO-GGSN CISCO-GPRS-ACC-PT CISCO-CDMA-PDSN CISCO-GPRS-GTP-MIB CISCO-CIDS CISCO-GATEKEEPER-MIB CISCO-GATEKEEPER-MIB CISCO-CRYPTO-ACCELERATOR CISCO-CIPCSNA CISCO-ICSUDSU-MIB CISCO-HSRP-MIB CISCO-HSRP-MIB CISCO-DDP-IAPP CISCO-DEVICE-EXCEPTIONREPORTING CISCO-IETF-ATM2-PVCTRAP-MIB CISCO-IETF-ATM2-PVCTRAP-MIB CISCO-IP-ENCRYPTION-MIB CISCO-IP-ENCRYPTION-MIB CISCO-IPSEC-FLOW-MONITOR-MIB CISCO-IPSEC-FLOW-MONITOR-MIB CISCO-L2-CONTROL CISCO-IETF-PW CISCO-LATITUDE CISCO-IKE-CONFIGURATION CISCO-IKE-FLOW CISCO-IMAGE-UPGRADE CISCO-ISDNU-IF-MIB CISCO-ISDNU-IF-MIB CISCO-MAC-NOTIFICATION-MIB CISCO-MAC-NOTIFICATION-MIB CISCO-OPTICAL-MONITOR CISCO-IP-LOCAL-POOL CISCO-NS-MIB CISCO-L2-TUNNEL-CONFIG CISCO-OPTICAL-PATCH-MIB CISCO-OPTICAL-PATCH-MIB CISCO-IPSEC-PROVISIONING 22 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 18.
Table 18. Supported event sources 23 . Supported Cisco MIB event sources (continued) Cisco MIBs CISCO-PIM CISCO-POP-MGMT CISCO-PORT-SECURITY CISCO-PORT-STORM-CONTROL CISCO-PROCESS CISCO-PSA-MICROCODE-MIB CISCO-PSA-MICROCODE-MIB CISCO-PPPOE-MIB CISCO-RHINO-MIB CISCO-RPMS CISCO-RSRB-MIB CISCO-RSRB-MIB CISCO-SCSI-MIB CISCO-SCSI-MIB CISCO-SDLLC CISCO-SIBU-STACKABLE-DUALSPEED-HUBMIB CISCO-SIBU-STACKABLE-DUALSPEED-HUBMIB CISCO-SONET-MIB CISCO-SONET-MIB CISCO-SRP-MIB CISCO-SRP-MIB CISCO-SRST CISCO-SSG CISCO-STP-EXTENSIONS-MIB CISCO-STP-EXTENSIONS-MIB CISCO-SYSTEM-EXT-MIB CISCO-SYSTEM-EXT-MIB CISCOTRAP-MIB CISCOTRAP-MIB CISCO-TS-STACK CISCO-VIRTUAL-NW-IF-MIB CISCO-VIRTUAL-NW-IF-MIB CISCO-VISM-TRAPS CISCO-VOICE-APPS-MIB CISCO-VOICE-APPS-MIB CISCO-VSAN-MIB CISCO-VSAN-MIB CISCO-WIRELESS-DOCS-EXT CISCO-IPSEC-SIGNALING CISCO-MVPN CISCO-ITP-GSCCP CISCO-ITP-GSP CISCO-ITP-MLR CISCO-ITP-MONITOR CISCO-PPPOE-MIB CISCO-RF CISCO-RHINO-MIB CISCO-PING CISCO-REPEATER-MIB CISCO-REPEATER-MIB CISCO-ITP-RT CISCO-RSCN-MIB CISCO-RSCN-MIB CISCO-RTTMON-MIB CISCO-RTTMON-MIB CISCO-NETWORK-REGISTRAR CISCO-SIBU-MANAGERS-MIB CISCO-SIBU-MANAGERS-MIB CISCO-SLB-MIB CISCO-SLB-MIB CISCO-SP-MIB CISCO-SP-MIB CISCO-SNA-LLC CISCO-ITP-XUA CISCO-STACK-MIB CISCO-STACK-MIB CISCO-STUN-MIB CISCO-STUN-MIB CISCO-ZS-MIB CISCO-ZS-MIB CISCO-IETF-ISIS CISCO-SYSTEM-MIB CISCO-SYSTEM-MIB CISCO-IVR CISCO-VLAN-MEMBERSHIP-MIB CISCO-VLAN-MEMBERSHIP-MIB CISCO-VOICE-DIAL-CONTROL-MIB CISCO-VOICE-DIAL-CONTROL-MIB Appendix A.
Supported Cisco Latitude MIB event sources Cisco Latitude MIBs CISCO-LATITUDE-MIB Cisco Syslog event sources The following table lists the Cisco Syslog specific MIB event sources. Table 19. Supported Cisco MIB event sources (continued) Cisco MIBs CISCO-WIRELESS-IF-MIB CISCO-WIRELESS-IF-MIB CISCO-WIRELESS-P2MP-RF-METRICSMIB CISCO-WIRELESS-P2MP-RF-METRICSMIB CISCO-WWNMGR-MIB CISCO-WWNMGR-MIB CISCO-WLAN-VLAN-MIB Process-MIB CISCO-VPDN-MGMT CISCO-VTP-MIB CISCO-VTP-MIB CISCO-WIRELESS-P2MP-PHY-MIB CISCO-WIRELESS-P2MP-PHY-MIB CISCO-WLAN-VLAN-MIB Cisco Latitude event sources The following table lists the Cisco Latitude specific MIB event sources. Table 20. Supported Cisco Syslog MIB event sources Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) AAA AAAA ACCESS_IE ADAPTER ADJ AICMGMT AIP ALC ALPS AMDP2_FE ARAP AS5400_ENVM AT ATM_AIM ATMCORE ATMPA ATMSSCOP ATUC AUTOQOS AUTOSEC AAA_CACHE AC ACLMERGE AESOP_AIM AIM ALARM ALIGN AMD79C971_FE AP AS5400 ASPP ATM ATMCES ATMOC3 ATMSIG ATOM_TRANS AUDIT AUTORP AUTOSTATE 24 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 18.
Supported event sources 25 . Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) BAP BCM56XX BGP BOOMERANG BRIMUX BSQ C1400_PCI C1700 C2600C2600_ MAINBOARD_ C29ATM C3600 C542 C54X C6KENV C6KPWR C6SUP C950 CAIM CALL_MGMT CALLRECORD CALLTRKR CARRIER CASA CBUS_ATTN CCA CCPROXY CDNLD_CLIENT CDP CE3 CERF CES_CLIENT CHARLOTTE CHOPIN_ MAINBOARD_ ASYNC_PQII CIOS CIRRUS CLAW CLIENT_CLOCK_ SYNC CLOCK CLS CM622_CM155 CM_MONITOR CMCC CNS BCM3220 BERT BIT BRI BSC BSTUN C1600 C1700_EM ASYNC_PQUICC C2KATM C4GWY_DSPRM C5421 C5RSP C6MSFC C7200_TDM CALL_CONTROL CALLPROG CALLTREAT CAPITOLA_MOD CBUS CBUS_WRITE CCH323 CDM CDNLD_SERVER CDSX_MODULE CES CES_CONN CHOPIN CI CIPDUMP CIRRUS_PM CLEAR CLNS CLOCKSW CLSDR CM_DSPRM CMAPP CMPCTG CNS_AGENT_ CFGCHG Appendix A.Table 20.
Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) CNSES COMP CONTROLLER COT CPE_MMI CPU_NET CTRC CSM CT3 CWAN_RP CWANLC_ATM CWRMP CWRTEST CWTLC_ATM DBCONN DCU DEC21140 DFC_CARRIER DIAG DIALPEER_DBDIALSHELF DISKMIRROR DLSWC DLSWP DMTDSL DNSSERVER DPM DRP DS_MODEM DSA DSC_ENV DSCC4 DSCEXTCLK DSI DSIPPF DSM DSPDD DSPFARM DSPU DSX1 DTP COBALT CONFIG COPS CPAD CPM CRYPTO CWAN_ATM CSM_VOICE CTA CWANLC CWPA CWRSU CWTLC DAS_ENV DBUS DEBUGGER DFC DHCPD DIALER DIRECTOR DLC DLSWMasterSlave DMA DNET DOT1X_MOD DRIP DRVGRP DS_TDM DSC DSC_ REDUNDANCY DSCCLOCK DSCREDCLK DSIP DSLSAR DSP_CONN DSPDUMP DSPRM DSX0 DSXPNM DUAL 26 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 20.
Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) DVLAN E1T1_MODULE EC EGP ENSP ENV_MON ENVM ESWILP_FLTMG ET2_MODULE ETHERNET EVENT_TRACE EXPRESS_SETUP FABRIC FAN FB FBINFO FDDI FIB FLASH FPGA FR_ADJ FR_FRAG FR_VCB FRATM FS_IPHC FTPSERVER FW GBIC GBIC_SECURITY GBIC_SECURITY_UNIQUE GENERAL GIGASTACK GK_OSP GLBP GPRSMIB GRP GRPGEGRPPOS GSI GSRIPC GT64011 DVMRP EARL ECC EHSA ENT_API ENVIRONMENT EPAD ESWITCH ETHC EVENT EXFREE EXPRESSION FALLBACK FASTBLK FB_COREDUMP FCL FECPM FILESYS FM FM FR FR_ELMI FR_LMI FRANK FREEDM FTC_TRUNK FTSP FX1000 GBIC_1000BASET GBIC_SECURITY_ CRYPT GE GET_DATA GK GL2PT GPRSFLTMG GRIP GRP_OC12_CH_DS3 GSHDSL GSR_ENV GT64010 GT96K_FE Appendix A.Table 20. Supported event sources 27 .
Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) GT96K_FEWAN GTP HAL HD HDX HIFN79XX HOOD HPI HTSP HTTPC HW_MEMORY HWMATM_MOD I82559FE IBM2692 IDMGR IDS IF IFS ILACC IMA_LINK INT IOCARD IP_SNMP IPACCESS IPC_DRVR IPCOIR IPC_RSP_CBUS IPDCAPP IPFLOW IPM_DSPRM IPMOBILE IPP IPV6 IPX ISA ISRHOG IVR KERBEROS KEYMAN L2CAC GT96K_TDM GVRP HAWKEYE HDV HEARTBEAT HMM_ASYNC HP100VG HSRP HTTP HUB HW_VPN I82543 IAD2420_VOICEPORT ICC IDNLD IDTATM25 IFINDEX IGRP IMA INDXOBJ INTERFACE_API IP IPA IPC IPCGRP IPC_RPM IPC_URM IPFAST IPM_C54X IPM_NV_EEPROM IPNAT IPRT IPV6FIB IRONBUS ISDN IUA IVR_MSB KERNEL KINEPAK L2R 28 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 20.
Supported event sources 29 .Table 20. Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) L3_MGR LANE LAPB LAPP_ON_MSGS LCB LCCOREDUMP LCLOG LDP LEX LIBTIFF LINEPROTO LLC LNMC LOGIN LPD LRE_LINK M32X MARS_NETCLK MBUF MBUS_SYS MCAST MDS MEMD MGCP MGMT MICA MIMIC MIRROR MISTRAL MLS MODEM MODEM_NV RECORD MONITOR MPC MPLS_TE MPOA MSDP MSPI MXT_FREEDM LANCE LANMGR LAPP_OFF LAT LCCEF LCINFO LD LES_FDDI LIBT2F LINECARD LINK LLIST LOADER LOVE LRE_CPE LRE_UPGRADELSS MAILBOX MBRI MBUS MC3810_DSX1 MCX MDT MEMSCAN MGCP_APP MHA_MODE MIF68840 MIPC MISA MK5 MMODEM MODEM_HIST MODEMCALL MODULES MPA68360 MPLS_ATM_TRANS MPLS_TE_PCALC MROUTE MSG802 MUESLIX NATMIB_HELPER Appendix A.
Table 20. Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) NBAR NETWORK_ CLOCK_SYNCH RONIZATION NHRP NIM NP_BS NP_DSPLIB NP_MD NP_SIGLIB NP_SSM NP_VSM NRP2 NRP2_SE64 NSE NSP_APS NSP_OIR OFFL ON_DIAG OSPF P2IPC PA PAD PAMMBOX PARSE_RC PCMCIAFS PF PGMHOST PIM PKTS PLATFORM_ CAT2950 PLATFORM_ CATALYST2950 PM PM_MODEM_ MAINT PORT POSDW POT1E1 PPP PQUICC PQUICC_ASYNC_NOMEM PQUICC_FE NET_SERV NEVADA NI2 NP NP_DDSM NP_EST NP_MM NP_SPE_DS NP_VPD NRP NRP2_NVMANAGE NRP2EHSA NSP NSP_DISK NSPINT OIR OOBP OSPFv3 P2IPC_TRACE PACK PAGP PAR PARSER PERUSER PGM PIF PIX PLATFORM PLATFORM_ CATALST2955 PLATFORM_ CATALYST2955 PM_MODEM_HIST PMSMPNNI POS POSLC POTS PQII PQUICC_ASYNC PQUICC_ETHER PQUICC_ETHERNET PQUICC_SERIAL 30 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) PRIVATEVLAN PS PW_WATCHER PXF_DMA _VIRTUAL_ PORT RPMXF QEM QM QUICC QUICC_ETHER RAC RADIO_DRIVER RADIX RBCP Regen REGISTORS RESOURCE_MON RIP RM ROUTEMAP_IPC RPA RPM RPM_CONFIG_COPY RPM RPMXF_QUEUE_CFG_GENERAL RPMXFEVENTMGR RS_TDM RSC_CF RSP RSVP RTT RUDP SARMGR SCB SCCP SCP SDLLC SDSL SECURITY SERVICE_MODULE SGBP SGCP_APP SIGSM PRUNING PV PXF QA QLLC QOS QUICC_ASYNC QUICC_SERIAL RADIO RADIUS RAIKO RCMD Regen_ MAINBOARD_ ASYNC_PQUICC REGISTRY RESYNCH RLM RMON RP_MLP RPC RPM_BULK RPM_RED RPMXF_QOS_GENERAL RPMXF_TOASTER RPS RSC RSCPB RSRB RTD S4T68360 SBETH SCHED SDLC SDP SEC SERVER_CLOCK_SYNC SERVICEMODULE SGCP SHELF SIP Appendix A. Supported event sources 31 .Table 20.
Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) SKINNYSERVER SLCI SLOT SMSMF SMRP SNASW SNMP_MGR SONET SONICT SPANTREE SPANTREE_VLAN_SW SPE SRP SSG SSI SSRP STANDBY STRING SUBSYS SW_VLAN SWITCH SWEPA SYSCTLR SYSMGT_RPC TAC TAGCOS TCATM TCPIP TDM_CLOCK_SYNCHRO NIZATION TDP TFIB TIB TLV TN TN3270S TPLUS TRANGE TRUNK_CLOCK TESTPA TI1570 TIGER TMQ TN3270 TOASTER_IPC TR TRUNK TRUNK_DFC SLB SLB_DFPSLC SLIP SLOTDUMP SMB SNAPSHOT SNMP SOI SONETMIB SPAN SPANTREE_FAST SPARC SRCP_APP SSE SSH SSI802 SSSMGR STORM_CONTROL STUN SUNI_DUAL SW56 SWITCH_IF SYS SYSLOG_SERVER T1E1SUNI TAGCON TBRIDGE TCP TDM TDM_CONN 32 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .Table 20.
Table 21. Supported Empirix MIB event sources Empirix MIBs EMP-STATS-MIB endPoint MIB staterr MIB EMP-ERROR-STATS-MIB empirix-EMP-STATS-MIB--EMP-ERROR-ST ATS statistic MIB Enterasys event sources The following table lists the Enterasys specific MIB event sources.Table 20. Supported Cisco Syslog MIB event sources (continued) Cisco Syslog facilities (via Syslog or CISCO-SYSLOG-MIB) TRUNK_SERIAL TTY TUN TXCONN UCODE UNIX URLF VFC VIP VMPS VOICE_RC VOIPAAA VOLANT VPD VPN_HW VRM VSI_M VTSP X25 XCPA YS TSP TTYDRIVER TUNSS UBR7200 UDLD UPS UTIL VINES VIPMLP VOICE_FSM VOICE_UTIL VOIPFIB VPA VPDN VQPCLIENT VRRP VTP WCCP XCCTSP_VOICE XTAGATM Empirix event sources The following table lists the Empirix specific MIB event sources. Appendix A. Table 22. Supported event sources 33 . Supported Enterasys MIB event sources Enterasys MIBs CTRON-SSR-TRAP-MIB Fore event sources The following table lists the Fore specific MIB event sources.
Table 25. Supported Fore MIB event sources Fore MIBs CELLPATH90-MIB fore-switch.mib Foundry event sources The following table lists the Foundry specific MIB event sources. Table 24. Supported Foundry MIB event sources Foundry MIBs Foundry-SN-TRAP-MIB iana-pwe3 MIB foundry-wireless-ap MIB Huawei event sources The following table lists the Huawei specific MIB event sources.Table 23.NEW H3C-POWER-ETH-EXT H3C-QOS-PROFILE HUAWEI-8021X-EXT-MIB HUAWEI-BASE-TRAP-MIB HUAWEI-M8070-MIB HUAWEI-NDEC HUAWEI-POS HUAWEI-SIP HUAWEI-SPLAT-MIX HUAWEI-SPLAT-RSTP HUAWEI-BFD-MIB HUAWEI-ENTITY-EXTENT-MIB HUAWEI-HGMP-MIB HUAWEI-NE80-POS-MIB HUAWEI-NETSTREAM-MIB HUAWEI-RPR-MIB HUAWEI-SYS-MAN-MIB HUAWEI-VPLS-MIB IPV6-MIB RPR-MIB H3C-COMMON-SYSTEM H3C-ENTITY-EXT H3C-FTM H3C-IPSEC-MONITOR H3C-PORT-SECURITY H3C-PPP-OVER-SONET H3C-SYS-MAN HUAWEI-AR46-DEV-ADM HUAWEI-LAG HUAWEI-MPLS-LSR HUAWEI-NEDEVICE-MIB HUAWEI-RMON-EXT HUAWEI-SNA-DLSW HUAWEI-SPLAT-MSTP HUAWEI-SPLAT-TRAP 34 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . Supported Huawei MIB event sources Huawei MIBs L2TP-MIB HUAWEI-CONFIG-MAN-MIB HUAWEI-FLASH-MAN-MIB HUAWEI-NE80-DEVICE-MIB HUAWEI-MSTP-MIB HUAWEI-DC-TRAP-MIB HUAWEI-PERFORMANCE-MIB HUAWEI-TCP-MIB HUAWEI-DEVICE-MIB HUAWEI-NE80-ETHERNET-MIB H3C-CFCARD H3C-CONFIG-MAN H3C-FLASH-MAN H3C-IKE-MONITOR H3C-NMS.
Supported IEEE MIB event sources IEEE MIBs WMAN-IF-MIB CFM-MIB IEEE802dot11-MIB IETF event sources The following table lists the IETF specific MIB event sources. Supported IBM Vallent MIB event sources IBM MIBs TNSQM-MIB IEEE event sources The following table lists the IEEE specific MIB event sources. Table 26. Supported IBM Director MIB event sources IBM MIBs IBM System Raid MIB IBM System Trap MIB IBM System Storage MIB IBM event sources The following table lists the IBM specific MIB event sources. Table 31.include. Supported event sources 35 . Table 27. Table 30. Table 28. snmptrap. Supported IANA MIB event sources IANA MIBs IANA-IANA-ITU-ALARM-TCMIB. Table 29. Supported IBM MIB event sources IBM MIBs metricaAlarmTrap IBM Vallent event sources The following table lists the IBM specific MIB event sources.lookup IBM Director event sources The following table lists the IBM specific MIB event sources.IANA event sources The following table lists the IANA specific MIB event sources. Supported IETF MIB event sources IETF MIBs APS-MIB IETF-FCMGMT IEEE-WMAN-IF IETF-FIBRE-CHANNEL-MGMT (updated ) Appendix A.
Supported IETF MIB event sources (continued) IETF MIBs IETF-HC-ALARM IETF-MPLS-LDP-STD IETF-SNA-NAU IETF-ISIS-MIB DOT3-OAM MIB RFC 2863 (IF-MIB) VRRP-MIB L2TP-MIB IPV6-MIB ADSL-LINE-MIB APPN-TRAP-MIB BGP4-MIB DIAL-CONTROL-MIB DISMAN-PING-MIB DISMAN-SCRIPT-MIB DLSW-MIB DS1-MIB ENTITY-MIB FRNETSERV-MIB IMA-MIB IPOA-MIB ISDN-MIB MIP-MIB MPLS-TE-STD-MIB OSPF-TRAP-MIB RDBMS-MIB RMON-MIB SNMPv2-M2M-MIB UPS-MIB XGCP-MIB IETF-POWER-ETHERNET IETF-PW-STD IETF-PTOPO IETF-MPLS-LSR IETF-DOCS-CABLE-DEVICE-TRAP IETF-RSVP IETF-SNA-SDLC CFM MIB RFC 1657 (BGP4) Entity State MIB (RFC 2737) Entity-State-MIB (RFC 4268) ACCOUNTING-CONTROL-MIB APPN-MIB ATM2-MIB BRIDGE-MIB DISMAN-EVENT-MIB DISMAN-SCHEDULE-MIB DISMAN-TRACEROUTE-MIB DOT12-RPTR-MIB DS3-MIB FRAME-RELAY-DTE-MIB HDSL2-SHDSL-LINE-MIB IPATM-IPMC-MIB IPV6-MIB MAU-MIB MPLS-LSR-STD-MIB MPLS-VPN-MIB Printer-MIB RFC1382-MIB SNMP-REPEATER-MIB TN3270E-RT-MIB VRRP-MIB EFM-CU IETF-DRAFT-MSDP IETF-MPLS-L3VPN-STD IETF-DVMRP-STD RPR-MIB Juniper event sources The following table lists the Juniper specific MIB event sources.Table 31. 36 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
Table 32. Table 33. Supported Juniper MIB event sources Juniper MIBs APS-MIB JUNIPER-RMON JUNIPER-CFGMGMT-MIB JUNIPER-BFD JUNIPER-LDP-MIB JUNIPER-EVENT JUNIPER-PING-MIB JUNIPER-RMON-MIB JUNIPER-SYSLOG JUNIPER-VPN-MIB jnx-bfd MIB jnx-cfgmgmt MIB jnx-coll MIB jnx-js-nat MIB jnx-l2ald MIB jnx-mimstp MIB ospfv3 MIB BGP4-V2-MIB-JUNIPER JUNIPER-BFD-EXP JUNIPER-COLLECTOR-MIB JUNIPER-DFC JUNIPER-MIB JUNIPER-MPLS-LDP JUNIPER-PMon-MIB JUNIPER-SONET-MIB JUNIPER-SP MPLS-MIB jnx-bgp4-v2 MIB jnx-chassis MIB jnx-js-auth MIB jnx-js-screening MIB jnx-ldp MIB jnx-mpls MIB user-aaa MIB Network Harmoni event sources The following table lists the Network Harmoni specific MIB event sources. Supported Nortel MIB event sources Nortel MIBs SWCOMMGMT-MIB BN-LOG-MESSAGE-MIB BAY-STACK-NOTIFICATIONS-MIB S5-CHASSIS-TRAP-MIB SSG-5000-CHASSIS-MIB nortel-TLS TLS-MIB NORTEL-OPTERA-MIB NORTEL-OPTERA-PUB-MIB RAPID-CITY NORTEL-OPTERA Appendix A. Table 34. Supported event sources 37 . Supported Network Harmoni MIB event sources Network Harmoni MIBs agentconfig-mib SYSRES-MIB ipconfig-mib Nortel event sources The following table lists the Nortel specific MIB event sources.
Table 37. Supported Synoptics MIB event sources Synoptics MIBs synoptics-BAY-STACKNOTIFICATIONS synoptics-S5-CHASSIS-TRAP synoptics-BN-LOG-MESSAGE 38 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . Table 38. Supported NTNTech MIB event sources NTNTech MIBs ntntech-nms-traps-MIB Rapid City event sources The following table lists the Rapid City specific MIB event sources. Table 35. Supported Rapid City MIB event sources Rapid City MIBs RAPID-CITY. Table 36.NTNTech event sources The following table lists the NTNTech specific MIB event sources.mib rapidcity-SWCOMMGMT Stratacom event sources The following table lists the Stratacom specific MIB event sources. Supported Stratacom MIB event sources Stratacom MIBs stratacom-SSNG-SYSLOG-MIB Synoptics event sources The following table lists the Synoptics specific MIB event sources.
IBM may not offer the products. NY 10504-1785 U. or service that does not infringe any IBM intellectual property right may be used instead. or service is not intended to state or imply that only that IBM product. Minato-ku Tokyo 106-0032.Appendix B. For license inquiries regarding double-byte (DBCS) information. therefore. However. in writing. Some states do not allow disclaimer of express or implied warranties in certain transactions. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Consult your local IBM representative for information on the products and services currently available in your area. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. program. Japan 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.S. Any functionally equivalent product. or service may be used. or features discussed in this document in other countries. or service. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. The furnishing of this document does not grant you any license to these patents. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. Any reference to an IBM product. services. 2008 39 . © Copyright IBM Corp. You can send license inquiries. BUT NOT LIMITED TO.A. contact the IBM Intellectual Property Department in your country or send inquiries. this statement may not apply to you. Notices and Trademarks This appendix contains the following sections: v Notices v Trademarks Notices This information was developed for products and services offered in the U. This information could include technical inaccuracies or typographical errors. 2006. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. EITHER EXPRESS OR IMPLIED.A. IBM may have patents or pending patent applications covering subject matter described in this document. program. program. Changes are periodically made to the information herein. in writing. program. these changes will be incorporated in new editions of the publication.S. INCLUDING.
40 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide . and products. compatibility or any other claims related to non-IBM products. Information concerning non-IBM products was obtained from the suppliers of those products. some measurements may have been estimated through extrapolation. subject to appropriate terms and conditions. or any equivalent agreement between us. 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. 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. Actual results may vary. Such information may be available. This information contains examples of data and reports used in daily business operations. Furthermore. should contact: IBM Corporation Software Interoperability Coordinator. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. The information herein is subject to change before the products described become available. Dealer prices may vary. brands. MN 55901 U. All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice. This information is for planning purposes only. To illustrate them as completely as possible. the results obtained in other operating environments may vary significantly. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Any performance data contained herein was determined in a controlled environment. including in some cases. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. their published announcements or other publicly available sources.A. Users of this document should verify the applicable data for their specific environment. companies. payment of a fee. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. IBM has not tested those products and cannot confirm the accuracy of performance. the examples include the names of individuals. All IBM prices shown are IBM’s suggested retail prices. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. are current and are subject to change without notice. Therefore.S. IBM International Program License Agreement. Department 49XA 3605 Highway 52 N Rochester. and represent goals and objectives only.Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites.
or function of these programs. Windows. and distribute these sample programs in any form without payment to IBM. for the purposes of developing. or both. Portions of this code are derived from IBM Corp. or both. IBM. or both. Acrobat. Sample Programs. Notices and Trademarks 41 . UNIX is a registered trademark of The Open Group in the United States and other countries. therefore. PostScript. Java and all Java-based trademarks are trademarks of Sun Microsystems. the photographs and color illustrations may not appear. other countries. cannot guarantee or imply reliability. using. other countries. and the Windows logo are trademarks of Microsoft Corporation in the United States. Each copy or any portion of these sample programs or any derivative work. or both. zSeries. _enter the year or years_. other countries. If you are viewing this information softcopy. Inc. Trademarks IBM. All rights reserved. Portable Document Format (PDF). serviceability. Linux is a trademark of Linus Torvalds in the United States.COPYRIGHT LICENSE: This information contains sample application programs in source language. © Copyright IBM Corp. AIX. or both. product. Tivoli. Appendix B. Adobe. other countries. or both. MMX. which illustrate programming techniques on various operating platforms. Intel Inside (logos). These examples have not been thoroughly tested under all conditions. marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. and Netcool are trademarks of International Business Machines Corporation in the United States. Other company. in the United States. other countries. Intel. and Pentium are trademarks of Intel Corporation in the United States. ibm. modify. You may copy. the IBM logo.com. Windows NT. or service names may be trademarks or service marks of others. and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. other countries. must include a copyright notice as follows: © (your company name) (year). Microsoft.
42 IBM Tivoli Netcool/OMNIbus Knowledge Library: Reference Guide .
Printed in USA SC23-6386-02 .