reports - ibm€¦ · sfsfsf's picture sfsfsf commented on january 12, 2012 permalink...

You are in: Tivoli Netcool OMNIbus > Home > Reference > Reports

Reports0 people like this

|Updated January 3, 2013 by ZaneBray|Tags:

omnibus-tcr,reference,reports

Page Actions ▼

This page includes topics on Tivoli Netcool/OMNIbus reports:

Tivoli Common Reporting Event Reports for OMNIbus (BIRT)

Tivoli Common Reporting Event Reports for OMNIbus (Cognos engine)

Comments

There are no comments.

You are in: Tivoli Netcool OMNIbus > Home > Reference > Reports > Tivoli Common Reporting Event Reportsfor OMNIbus (BIRT)

Tivoli Common Reporting Event Reports forOMNIbus (BIRT)0 people like this


best-practices,event-reports,omnibus

Page Actions ▼

The Tivoli Netcool/OMNIbus BIRT (Business Intelligence and Reporting Tools)reports for TCR are historicalreports, reporting against event data collected in Tivoli Data Warehouse (TDW) V2.1. This data is transferredfrom the Tivoli Netcool/OMNIbus ObjectServer to TDW using the Tivoli Netcool/OMNIbus ODBC Gateway.These reports are available via OPAL download.

The reports can be administered and run on Tivoli Common Reporting V1.1.1 and V1.2 software. The reportscan be edited with the BIRT designer.

NB: For version 2.1 of the reports for use with the Cognos engine of TCR 2.1, see Tivoli Common ReportingEvent Reports for OMNIbus (Cognos engine) in this wiki.

Prerequisites

An instance of the Tivoli Netcool/OMNIbus ObjectServer must be running;An instance of the TDW database must be running. The database must be initialized for receipt of data fromthe ObjectServer by using theNetcool/OMNIbus TDW scripts.There must be an instance of the Tivoli Netcool/OMNIbus ODBC Gateway running in reporter mode,transferring events from the ObjectServer to the TDW database. See the documentation for that gatewayfor details on its configuration.Tivoli Common Reporting must be installed and running. To ensure that it is running, go to

https://<machine_name>:<port_number>/ibm/console/logon.jsp.

Where <port_number> is the HTTPS access port for either Tivoli Integrated Portal (TIP) - the foundationserver for TCR V1.2, or Integrated Solutions Console (ISC) - the foundation server for TCR V1.1.1. Thedefault port number for TIP is 16316, and the default for ISC is 30343

Shipped reports

The following reports are available within the download:

Name Description Purpose

Ack EventDetails

This report shows a detailed break-down of theaverage acknowledgement times within a NetworkManagement environment for aspecific user or group.

The report assists operators and managersin pinpointing and addressing discrepanciesin acknowledgement rates across thenetwork.

Ack EventSummary

This report shows the average acknowledgementtimes within a Network Management environment forall users and groups.

The report assists operators and managersin pinpointing and addressing discrepanciesin acknowledgement rates across thenetwork.

EventsDetails

This report displays a detailed report of all events of aselected Node, Class, Location, Manager, AlertGroupor Severity over a user-specified time period.

The report assists operators and managerin providing coverage of the number ofevents for specific criteria in eventmanagement.

EventsSummary

This report displays the highest event-generatingelements based on either Node, Class, Location,

Help identify low performance of asystem/server over a period of time.

Manager, AlertGroup or Severity over a user-specifiedtime period

Perf DetailsThis report generates a supplementary drill-downreport of a selected operator, group, Class or Managerover a user-specified time period.

This report can help identify the mostoverloaded owner, class or event manager,and assist in identifying performanceissues.

PerfSummary

This report generates a bar chart and supplementarydrill-down table displaying the number of eventshandled by either an owner, Class or Manager over auser-specified time period

This report can help identify the mostoverloaded owner, class or event manager,and assist in identifying performance issues

Get AllDetails

This report retrieves all event details associated with aspecific node.

It allows users to track detailed informationabout specific nodes and devices that havegenerated events.

Get AllJournals

This report retrieves all journal entries associated witha specific node.

It allows users to track journal or statechange information about specific nodesand devices that have generated events.

Comments

1-1 of 1

PreviousNext

sfsfsf's Picturesfsfsf commented on January 12, 2012 Permalink

"The reports can be administered and run on Tivoli Common Reporting V1.1.1 and V1.2 software. The reportscan be edited with the BIRT designer."

No support for TCR 2.x?

Edited on January 12, 2012Show

102550items per page

PreviousNext

You are in: Tivoli Netcool OMNIbus > Home > Reference > Reports > TivoliCommon Reporting Event Reports for OMNIbus (Cognos engine)

Tivoli Common Reporting EventReports for OMNIbus (Cognosengine)0 people like this


omnibus-tcr

Page Actions ▼

A package of event reports for Tivoli Common Reporting (TCR) are availablein the ISM Library. The reports are designed for use with TivoliNetcool/OMNIbus and the Tivoli Netcool/OMNIbus Gateway for JDBCand a database that has been set up using the Tivoli Netcool/OMNIbusGateway for JDBC configuration scripts (Reporting Mode). The packagecontains the reports ready for installation into TCR and instructions.

For users with a customized event table and database schema the TCR modelupon which the reports are based has been included. A description of themodel and guidance on how to update the model is available atModelling_Netcool_OMNIbus_Data.pdf in the files section of the Networkand Service Assurance community.

Setting up the data source connection

Version 2.1 of the Event Reports for Netcool/OMNIbus use the Cognosreporting engine. This engine uses native database drivers: either databasespecific drivers or ODBC drivers. These drivers need to be installed on themachine running the TCR server. Once the drivers are installed the stepsdescribed in tcr_readme.pdf in the report package can be followed. Selectthe data source type for your drivers. E.g. "DB2" if you have the DB2 clientinstalled, or "ODBC" if you have the ODBC drivers for your database, etc.

The Cognos reporting engine does not use JDBC. So while you can use theJDBC gateway to insert event data into your database, you must use thenative/ODBC drivers for TCR to read the data out.

The TCR developerWorks group includes a link to the TCR You Tube channel.

This channel includes a video entitled "Configuring a TCR Cognos-based DB2connection" if you follow this video remember that the connection name mustbe "Reporter".

Accessing the correct DB2 schema

If you are using DB2, the Netcool/OMNIbus reporting tables will be createdwithin a DB2 schema. The schema normally has the same name as the userthat ran the gateway configuration scripts (Reporting Mode). When you setup the TCR data source connection you will set up a sign on that allows TCRto log in to DB2. The user name used for the sign on should match the nameof the schema containing the Netcool/OMNIbus reporting tables. The easiestway of doing this is to use the same DB2 user to run the gatewayconfiguration scripts and set up the sign on, and not to create any extraschemas. If you do need to use a different user you can create a set of aliasesso that the DB2 user used by TCR can access the Netcool/OMNIbus tables. Inthe following commands replace 'old' with the name of the schemacontaining the Netcool/OMNIbus tables and 'new' with the name of the DB2user used in the TCR sign on.

CREATE ALIAS new.REPORTER_CLASSES FOR old.REPORTER_CLASSESCREATE ALIAS new.REPORTER_CONVERSIONS FORold.REPORTER_CONVERSIONSCREATE ALIAS new.REPORTER_DETAILS FOR old.REPORTER_DETAILSCREATE ALIAS new.REPORTER_GROUPS FOR old.REPORTER_GROUPSCREATE ALIAS new.REPORTER_JOURNAL FOR old.REPORTER_JOURNALCREATE ALIAS new.REPORTER_MEMBERS FOR old.REPORTER_MEMBERSCREATE ALIAS new.REPORTER_NAMES FOR old.REPORTER_NAMESCREATE ALIAS new.REPORTER_STATUS FOR old.REPORTER_STATUSCREATE ALIAS new.REP_AUDIT FOR old.REP_AUDITCREATE ALIAS new.REP_AUDIT_ACK FOR old.REP_AUDIT_ACKCREATE ALIAS new.REP_AUDIT_OWNERGID FORold.REP_AUDIT_OWNERGIDCREATE ALIAS new.REP_AUDIT_OWNERUID FORold.REP_AUDIT_OWNERUIDCREATE ALIAS new.REP_AUDIT_SEVERITY FORold.REP_AUDIT_SEVERITYCREATE ALIAS new.REP_REFERENCE_DATE FORold.REP_REFERENCE_DATECREATE ALIAS new.REP_SEVERITY_TYPES FORold.REP_SEVERITY_TYPESCREATE ALIAS new.REP_TIME_PERIODS FOR old.REP_TIME_PERIODSCREATE ALIAS new.STATUS_VW FOR old.STATUS_VW

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools

Tools0 people like this


tools

Page Actions ▼

This page includes topics on Tivoli Netcool/OMNIbus tools:

Event Generator

Connecting with Jython

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > EventGenerator > Event Tables

Event Tables0 people like this

|Updated July 19, 2011 by BrianCar|Tags:

event-generator,tables,tools

Page Actions ▼

Name Description

WUQMonitors

WUQ Voicemonitor

ITNMDeviceStatus

ITNM devicestatus

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > EventGenerator > FAQ

FAQ0 people like this

|Updated August 4, 2011 by Pimmy|Tags:

event-generator,faq,tools

Page Actions ▼

On what operating platforms can this tool be used?

The Event Generator is a Java application which means it is platformindependent. However in order to use it on a x64 (64-bit) machine, you haveto ensure that you use a x86 (32-bit) version of Java. The Event Generatorhas been successfully tested on Windows, Linux and SolarisSPARC.

Please note that on Windows 7 x64, the installer would fail. Therefore youneed to manually copy the files and configure the Java runtime environment.I will update the installer to be Win7 x64 compatible soon.

What Java should I use?

Only 32-bit version of Java 1.6 or later. You can check your java by opening aCMD window ('Start'->'Run'->Type cmd->Press Enter) and typing `java-version`.

How much space is required for the installation?

Without the Java Runtime Environment the installation takes just above 1Mb.

I want to send events to different than 'alerts.status' table.

This is possible for version 1.0.1 onwards, however the user should manually

edit the event table XML file and modify the default value for 'dbTarget'. Theevent table XML files are located in $EGEN_HOME/props/ directory.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > EventGenerator > Bug Report

Bug Report0 people like this


bug-report,event-generator,tools

Page Actions ▼

Put title of bug number 1 here:

Submitted:

Description:

Comment:

Example bug report:

01/VII/2009

Description:

There is something wrong with the tool. It happens only when I perform thefollowing steps:

Step 1.Step 2.Step 3.

After that the tool crashes.

Comment:

This will be fixed in the next release scheduled 03/III/2010

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > EventGenerator

Event Generator1 person likes this

1|Updated July 18, 2012 by Pimmy|Tags:

event-generator,tools

Page Actions ▼

NETCOOL/Event Generator aims to provide all NETCOOL users with theability to send simulated custom defined events to an existing Object Server.This tool is very useful for testing automations, triggers, etc as well asfeeding demo software with fake events.

The user can define the format and the content of the events via a graphicaltool or directly into an XML file. Unlimited number of event tables fordifferent projects can be created.

1. Download

Current version: v1.0.1.b3, July 2011

Search for "Event Generator" in the IBM Integrated Service ManagementLibrary site. If you do not yet have access please contact your accountmanager, sales representative or technical account manager (or channelsteam if you are a partner).

2. Users Guide

Available in PDF format

3. Event Tables

Predefined event tables for various projects

4. FAQ

Search for already asked questions or submit a new one.

5. Bug report

View reported problems or submit a new bug

Comments

1-1 of 1

PreviousNext

MattWatt commented on March 8, 2017 Permalink

IBM Integrated Service Management Library can be found here =>https://www.ibm.com/software/brandcatalog/ismlibrary/

Show


PreviousNext

You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools >Connecting with Jython

Connecting with Jython0 people like this


connecting,jython,tools

Page Actions ▼

Jython script to show how to connect to Netcool OMNIbus.

For download: See attachment

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > Perlscript to export Omnibus SQL Query output into CSV

Perl script to export Omnibus SQLQuery output into CSV2 people like this

2|Updated January 27, 2013 by Alaa Farrag|Tags:

netcool,omnibus

Page Actions ▼

Perl script to export Omnibus Objectserver SQL Query output into CSV format. The script uses thenco_sql (isql) to execute the query instead of using DBI perl module that might not be installed on theomnibus machine.

omnibus2csv.pl

Comments

1-1 of 1

PreviousNext

droscigno commented on January 30, 2014 Permalink

Thanks! Nice script.

Show


PreviousNext

You are in: Tivoli Netcool OMNIbus > Home > Reference > Tools > PerlScript to report Objectserver triggers

Perl Script to report Objectservertriggers0 people like this

|Updated September 18, 2014 by Alaa Farrag|Tags:

netcool,objectserver,omnibus,triggers

Page Actions ▼

This script can be used to generate a report with all the Objectservertriggers grouped by trigger status (enabled/disabled), trigger type(Insert/Reinsert/Update/Delete/temporal/signal), trigger order (before orafter db action) and database table. The triggers are also sorted by theirpriorities.

The report is useful in investigating the enabled triggers on a certainobjectserver as close as possible to their execution sequence.

The script respect the text formatting of the triggers code as it has beenwritten during development.

You can include or exclude the triggers code from the report using "-c"option. You can also report only the enabled triggers using the -e option. Thescript uses the nco_sql (isql) to access the objectserver instead of using DBIperl module that might not be installed on the omnibus machine.

Usage: ./autoReport.pl [-s <Objectserver Name> -u <username> -p<password>] [-e] [-a]Usage: -e => to only print the enabled triggersUsage: -c => to include the triggers code in the output reportUsage: -a => to print database triggers for alert.status table onlyExample: ./autoReport.pl -s NCOMS -u root -p generic -e -a

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating > IBM OMNIbus 7.4 - Send SMSalerts in OMNIbus with communication provider Twilio and PHP

IBM OMNIbus 7.4 - Send SMS alerts in OMNIbuswith communication provider Twilio and PHP1 person likes this

1|Updated January 18, 2013 by svaziphil|Tags: NonePage Actions ▼

Introduction:

Tivoli Netcool/OMNIbus is a service level management (SLM) system that delivers real-time, centralizedmonitoring of complex networks and IT domains. With scalability that exceeds millions of events per day,Netcool/OMNIbus offers around-the-clock management and automation to help you deliver continuous uptimeof business services and applications, optimize operations costs and efficiency, and improve time to market.

OMNIbus features a extensive automation capability which is handled by triggers. These triggers can becalled by Database events (database triggers), by a signal (signal triggers) and by a time interval (temporaltriggers) . One of the things these triggers can do is to call external procedures which we will need in thistutorial.

It is sometimes a requirement by the customer that some of the triggers are able to send an sms. Thesefunctionality is not included and not documented in OMNIbus but is easily achievable.

In this tutorial we will create a trigger calling a procedure which calls a php script that will send the sms. InOMNIbus there is an existing trigger which send out emails of critical alerts that have not been acknowledgewithin 30 minutes. We will configure OMNIbus to send as a next step to send an sms for alerts that have notbeen acknowledged after 45 minutes.

We don't want to be bothered with purchasing, maintaining and configuring hardware and just use an smsgateway to send out sms. There are several companies that offer this service. One of the big ones is Twilio.Twilio is a cloud communications IaaS (Infrastructure as a Service) company and opens much morepossibilities than just sending sms. Software developers can programmatically make and receive phone callsand send and receive text messages using its web service APIs.

For our purpose we only need the part to send sms. The API of Twilio allows to use several languages such asJava, Perl, Rubi, python, PHP and more. We will use PHP in this case. PHP is well known for web applications,but since version 4.3 onwards, PHP is fully capable of performing scripts running by system command line aswell. And that is exactly what we need for our purpose.

Tip: With the Twilio trial account you can send test messages for free.

Pre-requisites and environment for this tutorial

An installation of IBM Netcool/OMNIbus 7.4 on Linux (CentOS 6.3 in this example) all components onone server.I have tested this tutorial with OMNIbus 7.3 and it did not work. There seems to be a bug. I havehowever not applied any fixpack and have not tested OMNIbus 7.3.1.

You will need to be connected Internet in order to install some of the software and to send sms requeststo the gateway.

Note: CentOS is nearly equivalent to Red Hat Enterprise Linux but is not an IBM supported OS. I am usingCentOS for licensing reasons and for this demonstration, CentOS works fine.

Assumptions

You are familiar with the basics of Netcool/OMNIbus and Linux.

Software used in this tutorial:

IBM Netcool OMNIbus 7.4 (installed with the user root)Simnet Probe installedPHP 5.3.3PEAR 1.9.4 (an Extension and Application Repository of PHP)Twilio PHP helper libraries

If you are familiar with PHP you probably wonder by now why no http Server such as Apache or IISmentioned. The answer is, we simply don't need one . We will use the CLI (Command Line version) of PHPwhich does not require a http server.

Steps

Set up an trial account with Twilio1. Install PHP and PEAR2. Install Twilio libraries3. Test Twilio.4. Create a test procedure and trigger5. Create procedure to send sms6.

1. Set up a Twilio trial account

Open twilio.com and click on the red big button "get started". This will guide you through the sign up for theaccount. You will not need to give credit card information. During the process you will verify your handphone number. This will be the number you can send test messages to. After that you will need to choose yourTwilio number. This number will be used to send messages (from).

Before you get to the Twilio dashboard you can test to send an sms to the verified number or send an sms. Ifyour number is not a USA or Canadian number this might not work at this stage. Don't worry, if it does notwork, we fix that later. Continue to complete the sign up.

If you could not send the test sms, you must set your outbound permissions by visiting the Global Permissionspage (https://www.twilio.com/user/account/international/sms) . Check for your country and tick to enable it.

2. Download and install PHP and PEAR

First we need to install PHP and PEAR. The minimum versions we need is PHP 4.3 and PEAR 1.9.3 . If youuse RHEL 6 or CentOS 6 you should be fine.Check if PHP and PEAR are installed: Open a terminal and execute the command php -version and pearversion. If these 2 commands do not display the required minimum have a look at appendix 1 and 2 where isdescribed how to install PHP and PEAR.

Configure php.ini

Open the file /etc/php.ini with a text editor. php.ini is the configuration file of php. You can leave most thingsby default. But the php.ini file of by default is configured for a production environment and does not showerrors. For our development phase we want to turn display errors to on.

In php.ini search for the line display_errors = Off and change this to On

Now that we have PHP and PEAR ready, let us do a simple demonstration of how to write a shell script withPHP. Open your favorite text editor (e.g. gedit, vi or vim) and save a file called hello.php. with the scriptbelow:

#!/usr/bin/php -q<?phpecho "Hello world\n";?>

In the terminal execute php hello.php . The file you created is by default not executable. If we ad thisfunctionality, we can run the hello.php directly.chmod +x hello.php and try the same again with the command ./hello.php.

Study the commands in the screen shot bbelow:

If this all works fine, you are set up to use PHP-CLI.

3. Install the Twilio PHP helper Libraries :

For PHP to make use of the API of Twilio we need to add the Twilio libraries for PHPMake sure connected to the Internet and execute the following two commands:

[root@omnibus73-lin1 ]# pear channel-discover twilio.github.com/pear[root@omnibus73-lin1 ]# pear install twilio/Services_Twilio

Debug: If at this point you get an error such as: https://twilio.github.com/pearsss/channel.xml" (Connectionto `twilio.github.com:443' failed: No connection could be made because the target machine actively refusedit.Then you probably have a too low version of PEAR installed. Check with the command "pear version" andmake sure it is above 1.9.3.

4. Test Twilio

Now we have everything in place to execute PHP scripts and with the help of the PEAR and Twilio librarieswe can now send sms via Twilio to mobile numbers. Lets test that in the simplest possible way.

Create a folder in /root called php-scripts (/root/php-scripts). To create the PHP scripts I suggest you use atext editor that provides syntax highlighting such as gedit or Komodo Edit.Tip: gedit provides syntax highlighting by setting View->Highlight Mode->scripts->php.

Save the following code with your text editor a file called test-sms.php in the path /root/php-scripts.

#!/usr/bin/php -q<?phprequire "Services/Twilio.php";

// Set our AccountSid and AuthToken from twilio.com/user/account$AccountSid = "AC4d9edaaaaaaaaf7df76afddddddd9cc5"; //replace with your ID$AuthToken = "63f7coooo06555555a7544714e4a5a2e"; //replace with your token

// Instantiate a new Twilio Rest Client$client = new Services_Twilio($AccountSid, $AuthToken);

//Your Twilio Number or Outgoing Caller ID$from = '+1 917-512-1234'; // replace with your Outgoing Called ID

//Your with Twilio verified number$to = "+60163454321"; // replace with your verified number

// Send a new outgoing SMS$body = "Bad news, the server is down and it needs your help";$client->account->sms_messages->create($from, $to, $body);echo "Sent message\n";?>

Note: Your $AccountSid and $AuthToken can be found in your Twilio "dashboard" menu(https://www.twilio.com/user/account) and the phone numbers in your "numbers" menu(https://www.twilio.com/user/account/phone-numbers/incoming)

Make the file again executable with the command chmod +x and execute the script with ./test-sms.php.Note that you should be in the path /root/php-scripts. Have a look a the screen shot below.

This will send you an sms with the content: "Sent from your Twilio trial account - Congratulations,sending sms with PHP and Twilio is working"

Debug: If this does not work, it will most probably throw some errors. (if there are no errors, check thephp.ini settings explained earlier).Check the $from and $to phone number, the Account ID and the Token.

5. Prepare OMNIbus

Now that we are able to send sms messages with a php script via Twilio, we need to make sure therequirements in OMNIbus are met to get the triggers and external procedures working.

We installed OMNIbus with the root user. Check if the user root is a member of the group ncoadmin:

Important: If there is no group ncoadmin and or the user root is not assigned to this group, you must correctthis before continuing.

To run the PHP script that will send the sms messages, OMNIbus need to use an external procedure. ExternalProcedures requires the process control agent dameon (nco_pad) running on the server where the executablecommand (php script) is stored. Since nco_pad will run the process, we need to configure the agent with avalid user name and password. In our case that will be root. And the credentials are places in the props fileon the Object server (NCOMS.props) The password must be encrypted with nco_pa_crypt.

Open a terminal and cd into /opt/IBM/tivoli/netcool/omnibus/bin/ and execute the command ./nco_pa_cryptyourpassword (the password you use for root).

Keep the encrypted password handy as we are going to add that now int o NCOMS.props.

Note: NCOMS is the name of the object server in this environment. If you have another name for your objectserver, you need to make changes in your object server props file..

With your text editor open the file /opt/IBM/tivoli/netcool/omnibus/bin/NCOMS.props and look for thelines:

PA.Password: ''PA.Username: 'root'PasswordEncryption: 'DES'

Make sure that PA.Username: is 'root' and the PasswordEncryption is 'DES'. For the password, add the textyou received as output from the earlier executed nco_pa_crypt. Example:

PA.Password: 'ENENBKBFBKEJGKGEHCBMBNBE'PA.Username: 'root'PasswordEncryption: 'DES'

6. Test a sample temporal trigger with external procedure

This is an optional step, but it can be useful to test your settings before you configure the actual script you

want to use. In OMNIbus it can be tricky at first to get everything correct configured. With this test, you getan immediate result to see if your external procedure will work and if something goes wrong it will be easierto debug.

1. Check if your services are running with

ps -ef | grep nco

You should see at least these two lines:

nco_pad -name NCO_PAnco_objserv -name NCOMS

Start the OMNIbus Administrator (/opt/IBM/tivoli/netcool/omnibus/bin/nco_config. )

Login to your Object Server (double click)

Create Trigger Group.

This is optional. You could as well assign the trigger we are going to do to an existing group. But forcompleteness of this tutorial and to separate our triggers from others I suggest to create a group.

Open (1) Automation and select (2) Trigger Groups. Click on (3) Add Trigger Group. Fill in (4)sms_tutorial as group name

Create a shell script

We create a very simple shell script that writes text to a file. Open your text editor and save a file calledwrite_text to /root/php-scripts with this content:

#!/bin/shecho "Procedure working and writes ever 10 seconds a new line" >> /root/php-scripts/text.txt;

Make sure that the file is executable by applying the command in the terminal chmod +x to the file

Create an External Procedure

(1) Select Procedures, (2) click Add External Procedure and give it the name (3) write_text. Choose thefile (4) /root/php-scripts/write_text as executable. (5) User ID is 0 (root) Group ID is the ID of thencoadmin group (in my case 501). You need to check the ID . Execute cat /etc/group |grep ncoadmin andthis will show you the ID:

Create a Trigger

We will create this trigger to call every 10 seconds a external procedure called write_text.

(1) Select Triggers , (2) Add a Temporal Trigger, (3) Give the name write_text, (4) select group namesms_tutorial. (5) Select the time every 10 seconds. (6) Tick State to Debug and Enabled.

Click the Action tab and enter the code

beginexecute write_text;end

Click OK.

Go back to the path /root/php-scripts/ and check if there is a file created called text.txt. ( after about 10seconds) . Wait for a few more seconds and open the file. You should have multiple lines "Procedureworking and writes ever 10 seconds a new line"

7. Create the Trigger to send sms

Lets do a quick recap.

- We have installed PHP, PEAR , tested and made sure PHP is working from the command line- We have installed the Twilio libraries and sent manually with a test script an SMS- We have configured OMNIbus to execute external procedures and tested this with a simple trigger.

Now for the sample we are going to create, we need again three parts.1. A external procedure that will call the PHP script and passes some arguments,2. A Trigger with some action and sql statement to pull data of the database.3. A PHP script that accepts the arguments and send out the sms.

OMNIbus has a ready to use sample of a trigger that is sending emails of critical situations that are notacknowledge withing 30 minutes. This temporal trigger is set to run every 10 seconds.We take this trigger as the base and adapt this to send sms for a similar occasion. The trigger is calledmail_on_critical and the connecting external procedure is called send_email. You can have a look at themfor reference.

For our sample we just want to have two of the database fields, the Node and Summary.

Create the PHP script

The PHP script will take two arguments, concatenate them into a string and send the sms.

Lets have a look at the PHP script we will use. Save this as send_sms.php in /root/php-scripts/ and make isexecutable with chmod +x.

#!/usr/bin/php -q<?php

require "Services/Twilio.php";

// Set our AccountSid and AuthToken from twilio.com/user/account$AccountSid = "AC4d9edae55555af7df76afd97233d9cc5"; //replace with your ID$AuthToken = "63f7c0c8955555521a7544714e4a5a2e"; //replace with your token

// Instantiate a new Twilio Rest Client$client = new Services_Twilio($AccountSid, $AuthToken);

//Your Twilio Number or Outgoing Caller ID$from = '+1 917-512-1234'; // replace with your Outgoing Called ID

//Your with Twilio verified number$to = "+60163454321"; // replace with your verified number

// to pass arguments from the command line use $_SERVER["argv"][0]// to create an array of arguments$_SERVER["argv"][0];

$stringData = $_SERVER['argv'][1] ." " . $_SERVER['argv'][2] ;

// Send a new outgoing SMS$client->account->sms_messages->create($from, $to, $stringData);

?>

2. Create the External Procedure:

- Click on "create external Procedure" and name the procedure send_sms.- Add the two parameters- Name Node, Data Type Char , Length 255.- Name Summary, Data Type Char , Length 255.- Executable: /root/php-scripts/send_sms.php- Arguments: '\''+Node+'\'','\''+Summary+'\'' (all single quotes)

3. Create the Trigger

Create a temporal trigger called sms_on_critical, assign the Trigger group sms_tutorial and run it every 10seconds.

Go to the tab Action and add the code:

begin

for each row critical in alerts.statuswhere critical.Severity = 5and critical.LastOccurrence <= ( getdate() - (30) )

beginexecute send_sms(critical.Node, critical.Summary) ;update alerts.status via critical.Identifier set Grade=2;end;

end

Note: In order to get some fast results, we send sms for critical alerts that are not acknowledge within 30seconds "critical.LastOccurrence <= ( getdate() - (30) )".If you for example you want to change that to 45 minutes you can change this line to "critical.LastOccurrence<= ( getdate() - (60* 45) )"

Within a few second you will receive sms or multiple sms with the contents such as "Sent from your Twiliotrial account - London Machine has gone offline"

While this may not be exactly what you want, this tutorial should give you enough information to customizethe triggers and procedures to fit your needs.

8. Resources

Command-line PHP? Yes, you can!: http://www.ibm.com/developerworks/opensource/library/os-php-command/Introduction to SMS Messaging: http://www.developershome.com/sms/smsIntro.aspTwilio: http://www.twilio.com/

PHP Hypertext Preprocessor: http://www.php.net/PHP CLI: http://www.php-cli.com/PEAR: http://pear.php.net/Komodo Edit: http://www.activestate.com/komodo-edit

Appendix

1. Install PHP

In the terminal execute yum install php53. This will install a later version (PHP 5.3.3) instead the defaultversion 5.1.

[root@omnibus73-lin1 ]# yum install php53

This will check the packages and resolve the dependencies. Select y to start the installation.

Check if PHP is installed:

[root@omnibus73-lin1 ]# php - version

2. Install PEAR

If you install PEAR with yum you probably will get a version which is below the required 1.9.3. We will get theinstallation file directly from the PEAR website and install PEAR manually. Execute

[root@omnibus73-lin1 ]# wget http://pear.php.net/go-pear.phar

This will download the file go-pear.phar.While in the same path, execute the file go-pear.phar with php to install PEAR.

[root@omnibus73-lin1 ]# php go-pear.phar

This will open the installation dialog. Please use all the default settings

Once installed we can test PEAR with the command pear version

[root@omnibus73-lin1 ]# pear version

Author of this tutorial.

Philipp Feer is part of the Tivoli Technical Enablement Support Team in IDR, located in Kuala Lumpur,Malaysia.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Building a Smarter Logistics by OMNIbus and CognosBusiness Analytics

Building a Smarter Logistics byOMNIbus and Cognos BusinessAnalytics0 people like this

|Updated November 13, 2012 by NateWu|Tags: NonePage Actions ▼

Background

The traffic jam and the high temperature has been headache problems to logistic owners inMumbai. In this real case, we will describe how we developed a smarter logistic solution thatsolved these troublesome problems and help logistic owners to make sure their products areshipped on time and no harm by using IBM Tivoli Netcool OMNIbus and Cognos BusinessAnalytics.

Introduction to Authors

Nate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been workingon globalization testing for Tivoli Netcool/OMNIbus for several releases. He has deepknowledge in Tivoli Netcool/OMNIbus application and published several technical papers onthis area on SSPD, TechNote and Tivoli Developer Works.

Christy Ting is a certified administrator for Cognos 10 BI and IBM accredited advisory projectmanager. She has rich experience in leading different IBM products from different brands toachieve IBM globalization standard inlcuding Tivoli, Cognos and SPSS.

Sanil Nambiar is a Technical Sales consultant from GTS, India. He along with his peers in hisgroup has been instrumental in developing various Smarter Planet Assets under SmartLogistics, Smart Buildings, Smart Telecom Infrastructure and has experience in building theseassets using IBM SW like Tivoli Netcool, Maximo EAM, TSRM, Cognos, Netcool Impact, andWebsphere. These solutions are in production in large Telecom Service providers andEnterprises in India

Building a Smarter Logistics by OMNIbus and Cognos Business Analytics.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Building a Smarter Security Management with IBMSecurity System

Building a Smarter SecurityManagement with IBM SecuritySystem0 people like this

|Updated January 31, 2013 by NateWu|Tags: NonePage Actions ▼

Background

The network security management, i.e. assets monitoring, attacks detection and response,event collection, event correlation, etc..., has been headache problems to security operationcenters in Taipei. In this real case, we will describe how we developed a smarter networksecurity management solution that solved these troublesome problems and help securityoperation centers to make sure their assets are safely protected by using IBM Tivoli SecurityInformation and Event Manager, Tivoli Security Operations Manager, Tivoli Endpoint Manager,Tivoli Netcool OMNIbus, and Tivoli Network Manager.


Paul Tseng is an experienced Tivoli Security Products deploymentprofessional and has been working on globalization testing for Tivoli SecurityProducts for several releasesNate Wu is a certified Tivoli Netcool/OMNIbus deployment professional andhas been working on globalization testing for Tivoli Netcool/OMNIbus forseveral releases.Wen Liau is management consultant from IBM Tivoli Software Group.

Building a Smarter Security Management with IBM Security System.pdf

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Building a Smarter Supervisor System by OMNIbusand IBM Tivoli Monitoring

Building a Smarter SupervisorSystem by OMNIbus and IBMTivoli Monitoring0 people like this

|Updated January 31, 2013 by NateWu|Tags: NonePage Actions ▼

BackgroundThe stability and performance of critical servers for overseas banking corporations is a seriousproblem. In this real case, we will describe how we developed a smarter supervisor solution thatmonitors and controls thousands critical servers with hundreds Key Performance Indicators(KPI). Thesolution solved the serious problem and help banking corporation keep systems stable efficiently andeffectively by using IBM Tivoli Netcool OMNIbus and IBM Tivoli Monitoring.

Introduction to AuthorsNate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been working onglobalization testing for Tivoli Netcool/OMNIbus for several releases.Ellen Chen has rich experience in Globalization project management. She's led and delivered over 100testing projects. Her areas of expertise include globalization verification testing, translationverification testing, and translation management.Wen Liau is management consultant from IBM Tivoli Software Group.

Building a Smarter Supervisor System by OMNIbus and IBM TivoliMonitoring.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Transforming a smarter building by adopting IBMNetcool OMNIbus and smarter planet solution

Transforming a smarter buildingby adopting IBM Netcool OMNIbusand smarter planet solution0 people like this


BackgroundWith rising energy costs and the overall economic environment, commercial property owners are facedwith a significant challenge: maintaining reliability and efficiency of their facilities while demonstratingenvironmental responsibility.

This case study is a real implementation that took place in Mumbai city about how we transformed abuilding, into a smarter one by adopting IBM smarter planet solution.

Introduction to AuthorsNate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been working onglobalization testing for Tivoli Netcool/OMNIbus for several releases. He has deep knowledge in TivoliNetcool/OMNIbus application and published several technical papers on this area on SSPD, TechNoteand Tivoli Developer Works.

Christy Ting is a certified administrator for Cognos 10 BI and IBM accredited advisory projectmanager. She has rich experience in leading different IBM products from different brands to achieveIBM globalization standard inlcuding Tivoli, Cognos and SPSS.

Sanil Nambiar is a Technical Sales consultant from GTS, India. He along with his peers in his group hasbeen instrumental in developing various Smarter Planet Assets under Smart Logistics, SmartBuildings, Smart Telecom Infrastructure and has experience in building these assets using IBM SW likeTivoli Netcool, Maximo EAM, TSRM, Cognos, Netcool Impact, and Websphere. These solutions are inproduction in large Telecom Enterprises in India.

Transforming a smarter building by adopting IBM Netcool OMNIbus andsmarter planet solution.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Developing a Smarter Network Management Solutionfor Telecommunication Organization

Developing a Smarter NetworkManagement Solution forTelecommunication Organization0 people like this


Background

The telecommunication company in Taiwan need to control all of the IP Network stuffs including Mobile,Wireline, Multimedia, CDMA, WiMax networks in one central portal. In this case, we will describe how wedeveloped a smarter solution that solved troublesome problems and help the organization to make sure theirproducts and services are stable and in high performance by using IBM solutions.


Nate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been working on globalizationtesting for Tivoli Netcool/OMNIbus for several releases.

Christy Ting is a certified administrator for Cognos 10 BI and is skillful in its application in real case.

Wen Liau is management consultant from IBM Tivoli Software Group.

Developing a Smarter Network Management Solution for TelecommunicationOrganization.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > Elevating a Vigorous Supervisor Solution for anInformation Technology Support Organization

Elevating a Vigorous SupervisorSolution for an InformationTechnology Support Organization0 people like this


Summary

In this real case, we developed a smarter supervisor solution that monitors and controls more than 150System z servers in an information technology support organization in UK. Through the use of an IntegratedService Management solution for the data center, the organization automated systems management toreduce the time and cost of systems support and gain greater visibility and control of its environment.

With the solution, the team uncovered repeated problems to help it prevent future issues - a key in improvinguser satisfaction and also enables the IT team to expand its services. By using this solution, the organizationcan save more than US$300,000 by eliminating the outsourcing of monitoring and first-level support.

Authors

[email protected], [email protected], [email protected],[email protected]

Elevating a Vigorous Supervisor Solution for an Information TechnologySupport Organization.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > The New Smarter Cloud Network AdministrationSolution for Next Generation Telecommunication Services

The New Smarter Cloud NetworkAdministration Solution for NextGeneration TelecommunicationServices0 people like this


BackgroundThe exponential growth in cloud network technology recent years leads the fast turnover of networkstructures. To stay at the forefront of market, network service providers compelled to continually introducesophisticated new services, and integrate with their existing devices to build a converging networkenvironment. Maintaining reliability and performance across different network facilities in the complexnetworking structure became one of the major challenges of enterprise owners and operators.

In this case, we will demonstrate how we implement the smarter performance management system for nextgeneration networks in a telecom company in Taiwan.


Austin Chang is a certified Tivoli Monitoring administration professional and has been working on globalizationtesting for several Tivoli Monitoring products.

Nate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been working on globalizationtesting for Tivoli Netcool/OMNIbus for several releases. He has deep knowledge in Tivoli Netcool/OMNIbusapplication and published several technical papers on this area on SSPD, TechNote and Tivoli DeveloperWorks.

Wen Liau is management consultant from IBM Tivoli Software Group

The New Smarter Cloud Network Administration Solution for Next GenerationTelecommunication Services.pdf

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases > The Advanced Meter Data Management Solution forNext Generation Utility Service

The Advanced Meter DataManagement Solution for NextGeneration Utility Service0 people like this


Background

In Malta, more than half of drinking water is provided by seawater desalination plant that is powered byelectricity. However, local electricity is generated completely by imported mineral fuel, which causes the rise ofelectricity price. In the meantime, the continuously sea-level is also threatening the safety of preciousunderground water resources. In order to rise up against these complicated challenges and provide safe andstable energy with fair price while preserving the environment, a transformation is required.

In this case, we will demonstrate how IBM helped Malta’s utility service provider become the first country withintegrated advanced meter infrastructure (AMI) for both electricity and water.


Paul Tseng is a Tivoli Security product professional and has been working on globalization testing for manyTivoli Security products.

Nate Wu is a certified Tivoli Netcool/OMNIbus deployment professional and has been working on globalizationtesting for Tivoli Netcool/OMNIbus for several releases.

Wen Liau is a management consultant from IBM Tivoli Software Group.

The Advanced Meter Data Management Solution for Next Generation UtilityService.pdf

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Smarter Use Cases

Smarter Use Cases0 people like this


This section includes Tivoli Netcool OMNIbus real cases. You can add yourown real cases for other users for references.

Building a Smarter Logistics by OMNIbus and Cognos Business Analytics

Building a Smarter Supervisor System by OMNIbus and IBM TivoliMonitoring

Building a Smarter Security Management with IBM Security System

Transforming a smarter building by adopting IBM Netcool OMNIbus andsmarter planet solution

The Advanced Meter Data Management Solution for Next Generation UtilityService

The New Smarter Cloud Network Administration Solution for NextGeneration Telecommunication Services

Elevating a Vigorous Supervisor Solution for an Information TechnologySupport Organization

Developing a Smarter Network Management Solution for TelecommunicationOrganization

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Tivoli OMNIbus and WebSphere Business Events Integration

Tivoli OMNIbus and WebSphereBusiness Events Integration0 people like this


business-events-integration,integration-scenarios,omnibus-and-websphere

Page Actions ▼

This article demonstrates how IBM® Tivoli® OMNIbus and IBMWebSphere® Business Events can share events and communicate with eachother. The OMNIbus Message Bus Integration Probe can be used to receiveevents from WebSphere Business Events so that they show up in theOMNIbus event list. Also, the OMNIbus Message Bus Integrationunidirectional Gateway can be used to send events to WebSphere BusinessEvents by using Java Messaging Service (JMS). Filtering can be set up so thatonly events with certain criteria are propagated. The value proposition of thisintegration is simply the ability for these two products to share informationthat can be very valuable considering that they both serve as central hubs forevents whether they are application-level events or operational events. Forexample, with this integration capability, both WebSphere Business Eventsand OMNIbus events can be viewed in a unified console (the OMNIbus eventlist). Read the entire article.

This article references the following files:

wbe2nvpairs.xslwbepl2nvpairs.xslwbm2nvpairs.xslexample-wbe.xsl

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating > Tivoli Netcool OMNIbus Gateway Integrations

Tivoli Netcool OMNIbus Gateway Integrations0 people like this

|Updated May 10, 2012 by Patrick Bullen|Tags:

best-practices,gateway-integrations,ibm-blog-l3,omnibus

Page Actions ▼

Please see also IBM Tivoli Netcool/OMNIbus Gateways on Information Center.

Tier -Passport

AdvantageGateway Name

GatewayType

Target System BinaryPlatformsSupported

Description

IBM TivoliNetcoolOMNIbusGateway Tier1

Gateway forMessageBus ( XML/ESB)

Universal /ESB

XML event destinations- WESB , TIBCO ESB ,MQ etc. The Gatewaysupports JMS, HTTP/HTTPS,MQTT and file based transports

nco_g_xml

Solaris, HP-UX, AIX,Linux,Windows,ZLinux

The IBM Tivoli Netcool/OMNIbus Message Bus Integration allows you toprocess XML messages either stored in a file or transmitted using a JMS-compliant message bus, such as Websphere ESB.

The integration comprises a Message Bus Gateway and a Message BusProbe. You can use the probe to acquire XML messages and store themas event records in the Netcool/OMNIbus ObjectServer. You can use thegateway to read events from the Netcool/OMNIbus ObjectServer, andsend them as XML messages using a JMS-compliant message bus, orwrite them to a file.


Gateway for JDBC Database

Any JDBC compliantdatabase. The gatewayhas been tested on thefollowing systems.

DB2® LUW 9.5 and 9.7DB2 z/OS® 10Informix® 11.5 and11.7Microsoft® SQL Server2005& 2008MySQL 5.0 and 5.1Oracle 10g and 11gSybase 12.5 and 15.5

nco_g_jdbc


The IBM Tivoli Netcool/OMNIbus Gateway for JDBC uses the standardJava™ Database Connectivity (JDBC) API to exchange alerts betweenNetcool/OMNIbus ObjectServers and external databases. Itcommunicates with the supported databases using Java Type 4 JDBCdrivers supplied by the database vendors.

The Gateway for JDBC can be used as a replacement for the Tivoli®Netcool/OMNIbus Gateway for ODBC and the Tivoli Netcool/OMNIbusGateway for Oracle.

The Gateway for JDBC has the following features:

Reporting and audit modes of operation.Store and forward (SAF) capability using persistent event cache anddata forwarding.Resynchronization on startup.Scalability provided by multiple database connections.Arbitrary table transfers.Migration from existing target databases using bidirectionalresynchronization.


Gateway for TivoliEIF

EIF N/A nco_g_tivoli_eif


The Gateway for Tivoli EIFGateway for Tivoli EIF is used to forwardevents from IBM Tivoli Netcool/OMNIbus to applications that acceptevents in EIF format.

You use the gateway when the applications receive events from IBMTivoli Netcool/OMNIbus and other event sources through the EventIntegration Facility (EIF) interface. The gateway consists of areader/writer and a writer. The reader/writer extracts alerts from asource ObjectServer and the writer forwards the alert data toapplications.


Gateway for Oracle DatabaseOracle version 10g or11g

nco_g_oracle

Solaris, HP-UX, HP-UXIntegrity, AIX,Linux, ZLinuxWindows

NOTE: The Oracle Gateway is now superseded by the JDBCGateway. Customers are advised to upgrade to the JDBC Gatewayto make use of the new features and functionality.

The Gateway for Oracle writes to three tables within the Oracle databaseto record all transactions that have occurred within the alerts selectedby an ObjectServer reader. These tables are Status, Journal, and Details.


Gateway for SNMPForwarder

Universal N/A nco_g_snmp


The SNMP Writer Gateway forwards alerts as SNMP traps. This allowsNetcool/OMNIbus to generate traps that are forwarded to anothermanagement platform such as SunNet Manager or HP Network NodeManager.


Gateway for Socket Universal N/A nco_g_socket


The Socket Writer gateway forwards alerts using a TCP connection. Anyprogram that listens to that socket receives the alerts.


Gateway for FlatFile

Universal N/A nco_g_file


The IBM Tivoli Netcool/OMNIbus Flat File Writer Gateway is aunidirectional gateway that reads alerts from the Netcool®/OMNIbus™ObjectServer, and writes the details to a flat file. The gateway canreceive insert, update, and delete notification information from multipletables within the ObjectServer.

IBM TivoliNetcoolOMNIbusGateway Tier1 3rd Party A

Gateway for ODBC Database Compatibility page nco_g_odbc

Solaris, HP-UX, AIX,Linux,Windows

NOTE: The ODBC Gateway is now superseded by the JDBCGateway. Existing customers are advised to upgrade to the JDBCGateway to make use of the new features and functionality.

The Open Database Connectivity (ODBC) writer uses three databasetables to record all transactions that have occurred within the alertsselected by an ObjectServer reader. These tables are status, journal, anddetails. Before running the ODBC Gateway, you must create thesedatabase tables. The scripts required for creating the database aresupplied in separate patches.


Gateway forClarify/Amdocs

CRMAmdocs CRM version7.5

nco_g_clarify Solaris

The Gateway for Amdocs CRM will implement the integration betweenTivoli Netcool/OMNIbus and Amdocs CRM. The Gateway for AmdocsCRM uses TAL to provide a uniform ticketing gateway framework and tointegrate with Amdocs CRM the gateway uses the Amdocs CBO API.

The gateway provides the following functions:

The Gateway for Amdocs CRM creates and updates Amdocs CRMcases based on alert data.The Gateway for Amdocs CRM changes the ticket status of thecreated Amdocs CRM cases based on values specified in theamdocscrm.rdrwtr.tblrep.def file.The Gateway for Amdocs CRM sends created cases to queues basedon values specified in the amdocscrm.map file.The Gateway for Amdocs CRM provides bidirectional support toenable the Amdocs server to forward updated status requests to theObjectServer.


Gateway forHP/PeregrineService Center

TroubleTicketService Center 6.2, HPServiceManager 7.xand 7.2

nco-g-peregrineSolaris, HP-UX, AIX,Linux

The Gateway for HP OpenView ServiceCenter is a fully functionalbidirectional gateway.

Alerts forwarded from the ObjectServer through the gateway formServiceCenter Incident Management tickets. Both systems worktogether to create and update alerts and tickets. Any change made to aalert or a ServiceCenter Incident Management ticket is reflected in itsassociated alert or ticket.


Gateway forRemedy ARS

TroubleTicket ARS 7.0 , 7.1, 7.5 & 7.6 nco-g-remedySolaris, HP-UX, AIX,Linux

The Gateway for Remedy ARS converts alerts into Remedy help desktrouble tickets. Trouble tickets are updated, according to a predefinedmapping throughout the lifetime of the alert. Remedy Express(MagicServicedesk) is not supported via this Gateway .


Gateway for SiebeleCommunications

CRMSiebel Communicationsversion 7.8.2.0

nco_g_siebel Solaris

The Gateway for Siebel Communications allows IBM TivoliNetcool/OMNIbus users to automatically create, update, and closeservice requests and their corresponding activities in Siebel. Thegateway receives notification when alerts in the ObjectServer arecreated, modified, or deleted. The gateway also receives notificationwhen a journal entry has been added to an alert. Filters can be used todetermine which alerts are sent to the gateway. The Gateway for SiebelCommunications is bidirectional, which means that alerts pass out of theObjectServer into Siebel, and if they are modified in Siebel, thosechanges can be sent back to the ObjectServer.

EntitlementunderOMNIbus

Gateway forObjectserver Bi-Directional

ObjectServer

IBM TivoliNetcool/OMNIbusObjectServer 7.2 andabove

nco_g_objserv_bi


The ObjectServer Gateway is used to replicate table data (for example,alert-related data) between different IBM Tivoli Netcool/OMNIbusObjectServers.

ObjectServer Gateways consist of readers and writers. Readers extractalerts from a source ObjectServer. Writers send the alert data to a targetObjectServer. An ObjectServer Gateway can be unidirectional orbidirectional. ObjectServer Gateways can be used to:

Maintain a backup ObjectServer.Replicate alerts between different Network Operations Centers(NOCs).Create a tiered architecture


Gateway forObjectserver Uni-Directional

ObjectServer

IBM TivoliNetcool/OMNIbusObjectServer 7.2 andabove

nco_g_objserv_uni


The ObjectServer Gateway is used to replicate table data (for example,alert-related data) between different IBM Tivoli Netcool/OMNIbusObjectServers.

ObjectServer Gateways consist of readers and writers. Readers extractalerts from a source ObjectServer. Writers send the alert data to a targetObjectServer. An ObjectServer Gateway can be unidirectional orbidirectional. ObjectServer Gateways can be used to:

Maintain a backup ObjectServer.Replicate alerts between different Network Operations Centers(NOCs).Create a tiered architecture


GatewayIntegration Modulefor TSRM

TroubleTicketTivoli Service RequestManager (TSRM) 6.2

n/a


IBM Tivoli Netcool/OMNIbus Integration with Tivoli Service RequestManager provides bidirectional communication betweenNetcool/OMNIbus and Tivoli Service Request Manager (TSRM) usingTivoli Directory Integrator (TDI).[This integration is only supportedfor TSRM 6.2]


Gateway for TivoliService RequestManager

TroubleTicket

Tivoli Service RequestManager (TSRM) v7.1Fix Pack 4 (BaseServices 7115) andlater

nco_g_tsrm


The Gateway for TSRM provides bidirectional communication betweenNetcool/OMNIbus and Tivoli Service Request Manager (TSRM).Thegateway supports IBM Tivoli Service Request Manager (SRM) version7.1 (Fix Pack 4 and later) and IBM Maximo Base Services (MBS) version7.1.1.5.This is a native gateway which has been built from ground up tointegrate with TSRM .The EIF and TDI components are no longerrequired and instead the gateway interfaces with the MEA Adapter onthe TSRM . Existing customers who are using the TSRM integrationmodule are advised to upgrade to this version


GatewayIntegration Modulefor TDW

Universal TDW 2.1 n/a


The Tivoli Netcool/OMNIbus-TDW Integration enables event informationstored in the ObjectServer to be forwarded to, and stored in, TDW 2.1 ina suitable format for the generation of reports using Tivoli CommonReporter (TCR) scripts.Tivoli Netcool/OMNIbus TCR reports - suppliedas a compressed (zip) file. Available to download from here.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating > Tivoli Netcool Knowledge Library (NcKL)

Tivoli Netcool Knowledge Library (NcKL)2 people like this

2|Updated January 5, 2012 by CraigWigley|Tags:

ibm-blog-l3,integration-scenarios,knowledge-library

Page Actions ▼

Please see also IBM Tivoli Netcool/OMNIbus Knowledge Library on Information Center.

Netcool/Knowledge Library (NcKL) is a collection of rules files written to a common standard, and provides unprecedented levels of eventcorrelation and causal analysis for the Netcool suite. Netcool/Knowledge Library complements the out-of-the-box event correlation capabilities ofNetcool/OMNIbus (and Netcool/Precision IP (where available) by enabling enhanced root cause analysis. Netcool/Knowledge Library aims toidentify which alarms indicate actual failures, allowing repair efforts to focus on the issues (or root causes) that truly affect the operation of theinfrastructure, without the distraction of the symptomatic or informational events. The end result is a reduction of Mean Time To Repair andincreased availability.

Netcool/Knowledge Library (NcKL) is available for download from Passport Advantage using the following part number : CZIA1EN - NetcoolKnowledge Library (NcKL) Enhanced Probe Rules V3.0 Multiplatform EnglishDocumentation for NcKL is here

The table below lists the MIBs supported in the latest release (V3.0) of the Netcool Knowledge Library.

NOTE: The device list below, is not comprehensive. Please contact your network equipment provider for a list ofsupported MIBS for your device.

VENDOR Supported MIBS DEVICE LIST (Not Comprehensive)

ACME Packet

ap-ems.mibap-env-monitor.mibap-license.mibap-security.mibap-slog.mibap-smgmt.mibap-swinventory.mib

Acme Packet Net-Net 4000 release 5.0, 5.1Acme Packet Net-Net 3000/4000 release 6.2.0Acme Packet Net-Net 9000 release 7.0.0

ADTRAN

ADTRAN-ACTDAXL3-MIBADTRAN-ADVISOR-MIBADTRAN-DS1-MIBADTRAN-DSU3AR-MIB

Adtran ACTDAXL3Adtran ADVISORAdtran DS1 Adtran DSU3AR

ADVA FSP2000-R2-MIB Fiber Service Platform (FSP) 2000

ALLIEDTELESYN

ALLIEDTELESYN-MIBATI-MIBATKKNBSW-MIBATMCCommon-MIBAtiL2-MIBAtiSwitch.mibATSWTCH2-MIB

Allied Telesyn-FirewallAllied Telesyn-Layer 2 SwitchesAllied Telesyn-NBase SwitchAllied Telesyn-Next Generation atswitch Switch

Ascend APS-MIB Ascend SONET Linear Automatic Protection Switching (APS)

ATM Forum

ATM-FORUM-MIBATM-SOFT-PVC-MIBATM-TRACE-MIBIMA-MIB

ATM Forum ATM UNI 4.0 InterfacesATM Forum Soft PVCATM Forum Inverse Multiplexing for ATM (IMA) interfaces

BridgeWaterBW-NOTIFICATIONBW-RADIUS

Bridgewater Radius

ChipCOM CHIPCOM.mib

Ethernet Management Module (EMM) 4.01Token Ring Management Module (TRMM) 3.0FDDI Management Module (FMM) 2.0Distributed Management Module (DMM) 1.0Ethernet to Ethernet Bridge Module (EEBM) 2.13Ethernet to Ethernet Bridge Box (EEBB) 2.13Ethernet Interconnect Module (EIM) 1.0

CIENA

IPI-GSLAMAG-MIBIPI-MEMMGMT-MIBIPI-OAMP-MIBinternetphotonics-IPI-GSLAMAGipi-memmgmt MIB ipi-oamp MIBipi-gslamag MIBipi-services MIB

CN-4200 5.0, 6.2Multiwave

Cisco Systems

ACCOUNTING-CONTROL-MIBCISCO-5800-HEALTH-MON-MIBCISCO-6400-CHASSIS-MIBCISCO-AAA-SERVER-MIBCISCO-ACCESS-ENVMON-MIBCISCO-ALPS-MICISCO-ALPS-MIBCISCO-APPLIANCE-REDUNDANCY-MIBCISCO-APS-MIB

Cisco LAN Switches

Catalyst 1600, 1900, 2820, 5000, 2900, 2900 XL, 2900XL LRE, 2926, 4000, 2948, 2948g, 2948G-L3, 2950,2950 LRE, 2955, 2970, 2980g, 2980ga, 3500 XL, 3550,3560, 3750, 4000, 4003, 4006, 4908 g, 4912, 4912g,5002, 5500, 5505, 5509, 6000/7600 OS, 6000/7600 IOS,6006, 6009, 6503, 6504, 6506, 6509, 6513, 8510 CSR,

CISCO-ATM-DUAL-PHY-MIBCISCO-ATM-IF-MIBCISCO-ATM-PVCTRAP-EXTN-MIBCISCO-AUTH-FRAMEWORK-MIBCISCO-BAMSP3-MIBCISCO-BBSM-MIBCISCO-BGP4-MIBCISCO-BITS-CLOCKCISCO-BSTUN-MIBCISCO-BULK-FILECISCO-C2900-MIB CISCO-C8500-REDUNDANCY-MIBCISCO-CABLE-AVAILABILITYCISCO-CABLE-METERINGCISCO-CABLE-QOS-MONITORCISCO-CABLE-SPECTRUM-MIBCISCO-CALLHOME-MIB-CISCO-CALL-TRACKER-MIB-CISCO-CASA -CISCO-CASA-FA-CISCO-CAT6K-CROSSBAR-MIB -CISCO-CCME-MIB-CISCO-CCM-MIB CISCO-CCM-MIB -CISCO-CDL -CISCO-CDMA-AHDLC-CISCO-CDMA-PDSN -CISCO-CEF-MIB -CISCO-CFS -CISCO-CHANNEL-CISCO-CIDS -CISCO-CIPCMPC-MIB-CISCO-CIPCSNA -CISCO-CLUSTER-MIB-CISCO-CONFIG-COPY-MIB -CISCO-CONFIG-COPY-MIB-CISCO-CONFIG-MAN-MIB-CISCO-CONTENT-ENGINE-MIB-CISCO-CONTENT-NETWORK-MIB-CISCO-CRYPTO-ACCELERATOR-CISCO-CSG -CISCO-DATA-COLLECTION-MIB -CISCO-DDP-IAPP -CISCO-DEVICE-EXCEPTIONREPORTING-CISCO-DIST-DIRECTOR -CISCO-DLSW-EXT-MIB-CISCO-DM-MIB -CISCO-DOCS-EXT-MIB-CISCO-DOCS-REMOTE-QUERY-MIB-CISCO-DOT11-CONTEXT-SERVICES-CISCO-DOT11-IF-MIB -CISCO-DOT11-QOS-CISCO-DOT3-OAM-MIB-CISCO-DS1-EXT-CISCO-DSP-MGMT-MIB -CISCO-DSPU-MIB-CISCO-EIGRP-MIB -CISCO-ENHANCED-IPSEC-FLOW-CISCO-ENHANCED-MEMPOOL -CISCO-ENHANCED-SLB-MIB -CISCO-ENTITY-ALARM-MIB -CISCO-ENTITY-DIAG-MIB -CISCO-ENTITY-FRU-CONTROL MIB -CISCO-ENTITY-PFE-CISCO-ENTITY-SENSOR-MIB -CISCO-ENVMON-MIB-CISCO-EPM-NOTIFICATION MIB-CISCO-ES-STACK-MIB-CISCO-ETHER-CFM-MIB-CISCO-EXT-SCSI-MIB-CISCO-FABRIC-C12K -CISCO-FABRIC-HFR-CISCO-FASTHUB-MIB -CISCO-FCC-MIB-CISCO-FC-FE-MIB -CISCO-FCPING-MIB-CISCO-FCS-MIB -CISCO-FCSP-MIB -CISCO-FCTRACEROUTE-MIB -CISCO-FDMI-MIB-CISCO-FEATURE-CONTROL -CISCO-FIREWALL-CISCO-FLASH-MIB -CISCO-FLEX-LINKS-MIB -CISCO-FSPF-MIB -CISCO-GATEKEEPER-MIB-CISCO-GENERAL-TRAPS-MIB -CISCO-GGSN-CISCO-GGSN-SERVICE-AWARE MIB -

8510 MSR, 8540 CSR, 8540 MSRLightStream 1010

Cisco Workgroup Concentrators

C6400 NRP, C6400 NSP

Cisco Secure and VPN Products

ACE Applicance, ACE, Adaptive Security Appliance,Firewall Service ModuleGlobal Site SelectorPix Security ApplianceC1710, C1721

Cisco Storage Networking

MDS 9000 FamilySN 5400 Family

Cisco Voice, Telephony & Messaging Software Products

Call ManagerCisco Unity ExpressPGW, HSI, BAMSMetro Ethernet Products ME 6524, ME3400/2400Catalyst 3750me

Cisco Service Routing Products

SCE 8000

Data Center Switching

Nexus 1000v/2000/5000/7000 Series

CiscoPro Workgroup Switches CPW 1220/1420

Cisco Optical Transport Products

ONS 15501, ONS 15530/40

Cisco Wireless LAN

c1400, c1300, c1240, c1210, c1130, c1100, c350,Aironet 1200, 350, 340Cisco Wireless Solution Engine

Broadband or IP Services

Cisco Network Registrar

Cisco TelePresence Products

TelePresence System

Cisco Access Products

C800, C805c 1003, c 1004, c 1005, c 1020, c 1417,c 1601/1602/1603/1604/1605,c 1701/1711/1720/1750/1751/1760,c 2000,c 2102/2202/25xx/261x/3620/3640/4500/4700/7000/7010/7200/75xx/10000/12000/AS 5xxx/ AGS+/AccessPro EC/RC cs500/cIGS/c38106xxx DSLAM FAMILYc7304/c 10000c76xx,c 10720/ ubr 7200XR12000/CRS-1

CISCO-GOLDWING-MIB -CISCO-GOLDWING-PMMAIN-MIB-CISCO-GPRS-ACC-PT-CISCO-GPRS-CHARGING -CISCO-GPRS-GTP-MIB-CISCO-GSLB-DNS-MIB-CISCO-GSLB-HEALTH-MON-MIB -CISCO-GSLB-SYSTEM-MIB -CISCO-GTP-DIRECTOR-CISCO-HC-ALARM -CISCO-HEALTH-MONITOR-CISCO-HSRP-MIB -CISCO-ICSUDSU-MIB-CISCO-IEEE-CFM-MIB -CISCO-IETF-ATM2-PVCTRAP-MIB-CISCO-IETF-DHCP-SERVER-EXT-MIB -CISCO-IETF-DHCP-SERVER-MIB -CISCO-IETF-DOT11-QOS-EXT -CISCO-IETF-FRR-MIB -CISCO-IETF-ISIS -CISCO-IETF-ISNS-MGMT-CISCO-IETF-MSDP-MIB -CISCO-IETF-PIM-EXT-MIB -CISCO-IETF-PIM-MIB -CISCO-IETF-PW-CISCO-IETF-SCTP-EXT -CISCO-IETF-VDSL-LINE-CISCO-IF-EXTENSION-MIB -CISCO-IF-THRESHOLD-MIB-CISCO-IKE-CONFIGURATION -CISCO-IKE-FLOW-CISCO-IMAGE-UPGRADE -CISCO-IP-ENCRYPTION-MIB-CISCO-IP-LOCAL-POOL -CISCO-IPMROUTE-MIB-CISCO-IPSEC-FLOW-MONITOR-MIB-CISCO-IPSEC-MIB-CISCO-IPSEC-PROVISIONING -CISCO-IPSEC-SIGNALING-CISCO-ISCSI-MIB -CISCO-ISDN-MIB-CISCO-ISDNU-IF-MIB -CISCO-ITP-GRT-MIB -CISCO-ITP-GSCCP -CISCO-ITP-GSP-CISCO-ITP-MLR -CISCO-ITP-MONITOR-CISCO-ITP-RT -CISCO-ITP-SP-MIB -CISCO-ITP-XUA -CISCO-IVR-CISCO-L2-CONTROL-MIB-CISCO-L2-DEV-MONITORING-CISCO-L2-TUNNEL-CONFIG-MIB-CISCO-L4L7MODULE-RESOURCE-LIMIT-MIB-CISCO-LATITUDE -CISCO-LICENSE-MGR-CISCO-LINK-ERROR-MONITOR-CISCO-LOCAL-DIRECTOR-MIB-CISCO-LWAPP-DOT11-CLIENT-MIB -CISCO-LWAPP-IDS-MIB -CISCO-LWAPP-MESH-BATTERY-MIB -CISCO-LWAPP-MESH-MIB -CISCO-LWAPP-MESH-STATS-MIB -CISCO-LWAPP-MFP-MIB -CISCO-LWAPP-MOBILITY-MIB-CISCO-LWAPP-ROGUE-MIB -CISCO-LWAPP-WEBAUTH-MIB -CISCO-MAC-NOTIFICATION-MIB-CISCO-MOBILE-IP-MIB CISCO-MODEM-MGMT-MIB -CISCO-MODULE-AUTO-SHUTDOWN-MIB -CISCO-MVPN-CISCO-NBAR-PROTOCOL-DISCOVERY-MIBCISCO-NETWORK-REGISTRARCISCO-NETWORK-REGISTRAR-MIBCISCO-NS-MIBCISCO-NTP-MIBCISCO-OAM-MIBCISCO-OPTICAL-MONITORCISCO-OPTICAL-PATCH-MIBCISCO-OSCP-MIB CISCO-OSPF-TRAPCISCO-OUTAGE-MONITORCISCO-PAE-MIBCISCO-PIM CISCO-PINGCISCO-POP-MGMTCISCO-PORT-SECURITY-MIBCISCO-PORT-STORM-CONTROL-MIB

CISCO-PPPOE-MIBCISCO-PROCESSCISCO-PSA-MICROCODE-MIBCISCO-PSM-MIBCISCO-RADIUS-MIBCISCO-REMOTE-ACCESS-MONITOR-MIBCISCO-REPEATER-MIBCISCO-RESILIENT-ETHERNET PROTOCOL-MIBCISCO-RF-MIBCISCO-RF-SUPPLEMENTAL-MIBCISCO-RHINO-MIBCISCO-RPMSCISCO-RSCN-MIBCISCO-RSRB-MIBCISCO-RTTMON-MIBCISCO-SCSI-MIBCISCO-SDLLCCISCO-SERVICE-CONTROL-LINK-MIBCISCO-SERVICE-CONTROL-RDR-MIBCISCO-SERVICE-CONTROL-SUBSCRIBERS-MIB-CISCO-SIBU-MANAGERS-MIB-CISCO-SIBU-STACKABLE-DUALSPEED-HUBMIBCISCO-SLB-EXT-MIBCISCO-SLB-MIBCISCO-SNA-LLCCISCO-SONET-MIBCISCO-SP-MIBCISCO-SRP-MIBCISCO-SRST-MIBCISCO-SSGCISCO-STACK-MIBCISCO-STACKWISE-MIBCISCO-STP-EXTENSIONS-MIBCISCO-STUN-MIBCISCO-STUN-MIBCISCO-SVC-INTERFACE-MIBCISCO-SYS-INFO-LOG-MIBCISCO-SYSTEM-EXT-MIBCISCO-SYSTEM-MIBCISCO-TAP2-MIBCISCO-TAP-MIBCISCO-TELEPRESENCE-CALL-MIBCISCO-TELEPRESENCE-MIBCISCO-TELNET-SERVER-MIBCISCO-TRANSPATH-MIBCISCOTRAP-MIBCISCO-TS-STACKCISCO-UNITY-EXPRESS-MIBCISCO-VIRTUAL-NW-IF-MIBCISCO-VIRTUAL-SWITCH-MIBCISCO-VISM-TRAPSCISCO-VLAN-MEMBERSHIP-MIBCISCO-VOICE-APPS-MIBCISCO-VOICE-CONNECTIVITYCISCO-VOICE-DIAL-CONTROL-MIBCISCO-VOICE-DNIS-MIBCISCO-VPDN-MGMT-MIBCISCO-VSAN-MIBCISCO-VTP-MIBCISCO-WIRELESS-DOCS-EXTCISCO-WIRELESS-IF-MIBCISCO-WIRELESS-NOTIFICATION MIBCISCO-WIRELESS-P2MP-LINK-METRICS-MIBCISCO-WIRELESS-P2MP-PHY-MIB CISCO-WLAN-VLAN-MIBCISCOWORKSCISCO-WWNMGR-MIBCISCO-ZS-MIBESSWITCH-MIBMPLS-LDP-MIBNOVELL-IPX-MIBONS15501-MIB Process-MIB

Empirix eventsources

EMP-ACTIVEPROBE-MIBEMP-ERROR-STATS-MIBEMP-STATS-MIBempirix-EMP-STATS-MIBEMP-ERROR-ST ATSendPoint MIBstatistic MIBstaterr MIB

Hammer XMS 2.4

Enterasys eventsources

CTRON-SSR-TRAP-MIB Cabletron Smart Switch Router

Fore eventsources

CELLPATH90-MIBfore-switch.mib

Fore CellPath 90 ATM Access MultiplexerFore ATM Switch

FoundryNetworks

Foundry-SN-TRAP-MIBfoundry-wireless-ap MIBiana-pwe3 MIB

BigIron RX 2.2.01FastIron GS 2.4.00FastIron SuperXFoundry Wireless Access PointFESXFWSX 2.5.00IronPoint 1.4.01NetIron IMR 3.0.00NetIron XMR/MLX 3.1.00ServerIron 450/850 9.5.00ServerIron 100/400/800/GTE 9.4.00

Hatteras

HN-ACC-MIBHN-ALARM-MIBHN-BDP-MIB HN-BITS-MIBHN-BONDING-MIB HN-CFM-MIBHN-DB-MIB HN-DEVICE-MIBHN-DS1-MIB HN-DS3-MIBHN-ETHERNET-MIB HN-FAN-MIBHN-HSMODULE-MIB HN-LACP-MIBHN-OAM-MIB HN-PME-MIBHN-POWERFEED-MIB HN-PRIV-MIBHN-SERVICE-MIB HN-SFP-MIBHN-STACKPORT-MIB HN-SYSTEM-MIBHN-TDR-MIB HN-TRAFFIC-MIB

Hatteras HN400/HN4000 7.2.2

Huawei

L2TP-MIB HUAWEI-BFD-MIBHUAWEI-CONFIG-MAN-MIB HUAWEI-ENTITY-EXTENT-MIBHUAWEI-FLASH-MAN-MIB HUAWEI-HGMP-MIBHUAWEI-NE80-DEVICE-MIB HUAWEI-NE80-POS-MIBHUAWEI-MSTP-MIB HUAWEI-NETSTREAM-MIBHUAWEI-DC-TRAP-MIB HUAWEI-RPR-MIBHUAWEI-PERFORMANCE-MIB HUAWEI-SYS-MAN-MIBHUAWEI-TCP-MIB HUAWEI-VPLS-MIBHUAWEI-DEVICE-MIB IPV6-MIBHUAWEI-NE80-ETHERNET-MIBRPR-MIBH3C-CFCARD H3C-COMMON-SYSTEMH3C-CONFIG-MAN H3C-ENTITY-EXTH3C-FLASH-MAN H3C-FTMH3C-IKE-MONITOR H3C-IPSEC-MONITORH3C-NMS.NEW H3C-PORT-SECURITYH3C-POWER-ETH-EXT H3C-PPP-OVER-SONETH3C-QOS-PROFILE H3C-SYS-MANHUAWEI-8021X-EXT-MIB HUAWEI-AR46-DEV-ADMHUAWEI-BASE-TRAP-MIB HUAWEI-LAGHUAWEI-M8070-MIB HUAWEI-MPLS-LSRHUAWEI-NDEC HUAWEI-NEDEVICE-MIBHUAWEI-POS HUAWEI-RMON-EXTHUAWEI-SIP HUAWEI-SNA-DLSWHUAWEI-SPLAT-MIX HUAWEI-SPLAT-MSTPHUAWEI-SPLAT-RSTP HUAWEI-SPLAT-TRAP

Huawei AR-SeriesHuawei NE-SeriesHuawei S-Series

IANA IANA-PWE3-MIB Pseudowire Management Emulation Edge-to-Edge (PWE3)

IBM DirectorIBM System Raid MIBIBM System Storage MIBIBM System Trap MIB

IBM System RaidIBM System StorageIBM System State

IBM TivoliTivoli Netcool Performance Manager forWirelessTivoli Netcool Service Quality Manager

metricaAlarmTrap.mibTNSQM-MIB

IEEECFM-MIBIEEE802dot11-MIBWMAN-IF-MIB

IEEE 802.11IEEE 802.16 Base StationIEEE Connectivity Fault Management (CFM) Module

APPN-TRAP-MIBAPS-MIBIETF MIBsATM2-MIB BGP4-MIBBRIDGE-MIB CFM MIBDIAL-CONTROL-MIB DISMAN-EVENT-MIBDISMAN-PING-MIB DISMAN-SCHEDULE-MIBDISMAN-SCRIPT-MIB DISMAN-TRACEROUTE-MIBDLSW-MIB DOT12-RPTR-MIBDOT3-OAM MIB DS1-MIBDS3-MIB EFM-CUEntity State MIB (RFC 2737) ENTITY-MIBEntity-State-MIB (RFC 4268) FRNETSERV-MIBFRAME-RELAY-DTE-MIB IEEE-WMAN-IFHDSL2-SHDSL-LINE-MIB IETF-DRAFT-MSDPIETF-DOCS-CABLE-DEVICE-TRAPIETF-FCMGMTIETF-DVMRP-STD IETF-HC-ALARMIETF-FIBRE-CHANNEL-MGMTIETF-MPLS-L3VPN-STDIETF-ISIS-MIB IETF-MPLS-LSR

IETF-MPLS-LDP-STD IETF-PTOPOIETF-POWER-ETHERNET IETF-RSVPIETF-PW-STD IETF-SNA-SDLCIETF-SNA-NAU IPATM-IPMC-MIBIMA-MIB IPV6-MIBIPOA-MIB ISDN-MIBIPV6-MIB APPN-MIB MAU-MIBL2TP-MIB MPLS-LSR-STD-MIBMIP-MIB MPLS-VPN-MIBMPLS-TE-STD-MIB PIM-MIBOSPF-TRAP-MIB RDBMS-MIBPrinter-MIB RFC 2863 (IF-MIB)RFC 1657 (BGP4) RMON-MIBRFC1382-MIB SNMP-REPEATER-MIBRPR-MIB TN3270E-RT-MIBSNMPv2-M2M-MIB VRRP-MIBUPS-MIB XGCP-MIBVRRP-MIB

InfineraINFINERA-NOTIFICATION-MIB INFINERA-TRAP-MIB

Infinera ATN R1.0Infinera DTN R5.0Infinera FIS R6.0

Juniper

APS-MIB BGP4-V2-MIB-JUNIPER APS-MIB-JUNIDVMRP-STD-MIB-JUNIjnx-bfd MIBjnx-bgp4-v2 MIBjnx-cfgmgmt MIBjnx-chassis MIBjnx-coll MIBjnx-js-auth MIBjnx-js-nat MIBjnx-js-screening MIBjnx-l2ald MIBjnx-ldp MIBjnx-mimstp MIBjnx-mpls MIBJuniper-ADDRESS-POOL-MIBJUNIPER-BFD JUNIPER-DFCJUNIPER-CFGMGMT-MIBJUNIPER-COLLECTOR-MIBJuniper-CLI-MIBJuniper-DHCP-MIBJuniper-DOS-PROTECTION-PLATFORM-MIBJuniper-DVMRP-MIBJuniper-ERX-System-MIBJUNIPER-EVENTJUNIPER-MPLS-LDPJuniper-FILE-XFER-MIBJuniper-IP-MIB JUNIPER-L2CP-FEATURES-MIBJUNIPER-LDP-MIB JUNIPER-MIB Juniper-LOG-MIBJUNIPER-MIMSTP-MIBJuniper-MROUTER-MIBJuniper-PACKET-MIRROR-MIBJUNIPER-PING-MIB JUNIPER-PMon-MIBJuniper-RADIUS-CLIENT-MIBJuniper-REDUNDANCY-MIBJUNIPER-RMONJUNIPER-BFD-EXPJUNIPER-RMON-MIB JUNIPER-SONET-MIBJUNIPER-SECURE-ACCESS-PORT-MIBJUNIPER-SYRAH-MIBJUNIPER-SYSLOG JUNIPER-SP Juniper-System-lock-MIBJuniper-System-MIB Juniper-UNI-ATM-MIBJuniper-UNI-SONET-MIB JUNIPER-VIRTUALCHASSIS-MIBJUNIPER-VPN-MIB MPLS-MIB ospfv3 MIBuser-aaa MIB

EX-Series, E-Series, J-series, M-series, MX-series, SRX-series, WX-series,T-series and any other Juniper Networks network elements that supportJUNOS 9.4 (or below).E-Series and any other Juniper Networks network elements that supportJUNOSe 10.3 (or below), as well as BX-Series (4.1).BX-Series and any other Juniper Networks network elements that supportBX-OS 4.1.

Networkharmoni

agentconfig-mibipconfig-mibSYSRES-MIB

Nortel Networks

BAY-STACK-NOTIFICATIONS-MIBSWCOMMGMT-MIBBN-LOG-MESSAGE-MIBTLS-MIBNORTEL-OPTERA-MIBNORTEL-OPTERA-PUB-MIBSSG-5000-CHASSIS-MIBS5-CHASSIS-TRAP-MIB

Nortel OPTera 80Nortel Transparent LAN Service

NTNTech ntntech-nms-traps-MIB Ntntech Network Management Services

Rapid CityRAPID-CITY.mibRapidcity-SWCOMMGMT

Nortel Ethernet Routing Switch 8600 (ERS8600)

Sandvine SANDVINE-MIB

Network Demographics Server (NDS) 5.51Policy Traffic Switch (PTS) 5.51Service Definition Manager (SDM) 5.51Subscriber Policy Broker (SPB) 5.51

Stratacom stratacom-SSNG-SYSLOG-MIBCisco Voice Interworking Service Module (VISM)Cisco CNS Notification Engine (CNOTE)

SynopticsSynoptics-BAY-STACK-NOTIFICATIONSsynoptics-BN-LOG-MESSAGEsynoptics-S5-CHASSIS-TRAP

BayNetworks Synoptics 5000 ChassisNortel Bay Stack ProductsNortel Log Message Facility

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating > Tivoli Netcool OMNIbus IntegrationModules on ISM

Tivoli Netcool OMNIbus Integration Modules on ISM0 people like this

|Updated January 5, 2012 by CraigWigley|Tags:

integration-modules,integration-scenarios,opal

Page Actions ▼

The Integrated Service Management Library is a worldwide on-line catalog designed to provide users with a centrallocation for technically validated production ready ITSM integrated extensions provided by IBM and IBM BusinessPartners. A number of integrations developed by IBM and its Partners are available to download from ISM. ISMprovides access to a number of catalogs that contain down-loadable integrated extensions, automation packages, andsupporting documentation from IBM and Tivoli Business Partners Worldwide

For Netcool/OMNIbus the ISM integrations consist of integration packs for OMNIbus as well as network integrationmodules (Rules files and Include files) for commonly used probes like the SNMP, Syslog and TL1.

Please refer to the IBM Tivoli Netcool/OMNIbus Integration Best Practices guide for guidance on how you can createrules files for OMNIbus Probes.

Integration Partner Integration TypeDeveloped andSupported By

1 ACME PacketNetcool/OMNIbus Integration Module for Acme PacketNet-Net

IBM

2 ACME PacketNetcool/OMNIbus Integration Module for Tellabs 8000Network Manager

IBM

3 ADVA Optical NetworkingNetcool/OMNIbus Integration Module for ADVA OpticalNetworking FSP Network Manager

IBM

4 AirwaveNetcool/OMNIbus Integration Module for the AirWaveManagement Platform

IBM

5 Alarm Point SystemsAlarmPoint Professional Adapter for TivoliNetcool/OMNIBus

Alarm Point Systems

6 Alarm Point Systems [AlarmPoint Adapter for Tivoli Netcool/OMNIbus Alarm Point Systems

7 Alcatel-LucentAlcatel-Lucent My Teamwork Advanced CommunicationServer

Alcatel-Lucent

8 AnritsuNetcool/OMNIbus Integration Module for AnritsuMasterClaw

IBM

9Applied NeuralTechnologies

ANB's DataNforcer Integration with IBM's TivoliNetcool/Omnibus

Applied NeuralTechnologies

10 AvayaNetcool/OMNIbus Integration Module for AvayaCommunication Manager

IBM

11Ayehu SoftwareTechnologies Ltd

EyeShare CSM - Critical Situation Management forNetcool/OMNIbus

Ayehu SoftwareTechnologies Ltd

12 BroadsoftNetcool/OMNIbus Integration Module for BroadSoft'sBroadWorks Platform

IBM

13 Cellex Networks Cellex - Customer Experience Management Solutions Cellex Networks

14 Ciena Netcool/OMNIbus Integration Module for Ciena CN 2300 IBM

15 CienaNetcool/OMNIbus Integration Module for Ciena CN 4200(SNMP)

IBM

16 CienaNetcool/OMNIbus Integration Module for Ciena CN 4200(TL1)

IBM

17 Ciena Netcool/OMNIbus Integration Module for Ciena CN 4300 IBM

18 CienaNetcool/OMNIbus Integration Module for Ciena DN 7000Series

IBM

19 CiscoNetcool/OMNIbus Integration Module for Cisco NexusProduct Family

IBM

20 COMPTEL CORPORATION Comptel Interconnect Billing™ COMPTEL CORPORATION

21 COMPTEL CORPORATION Comptel Policy Control™ COMPTEL CORPORATION

22 COMPTEL CORPORATION Comptel Provisioning and Activation™ COMPTEL CORPORATION

23 COMPTEL CORPORATION Comptel Rater™ COMPTEL CORPORATION

24 COMPTEL CORPORATION Comptel Roaming Management™ COMPTEL CORPORATION

25 COMPTEL CORPORATION Comptel Data Retention™ COMPTEL CORPORATION

26 COMPTEL CORPORATION Comptel Convergent Mediation™ COMPTEL CORPORATION

27 COMPTEL CORPORATION Comptel Charging™ COMPTEL CORPORATION

28 ConteXtream ConteXtream Dynamic Media Adaption ConteXtream

29 CovergenceCovergence Session Manager integration with IBM TivoliNetcool OMNIbus

Covergence

30 Elutions Inc. Maestro™ for Energy and Asset Management Elutions Inc.

31 EmpirixNetcool/OMNIbus Integration Module for Empirix HammerXMS

IBM

32 EntuityEye of the Storm ® Tivoli Netcool/OMNIbus IntegrationModule

Entuity

33 EXFONetcool/OMNIbus Integration Module for EXFO ServiceAssurance BrixWorx

IBM

34 Fenavic Fenavic Suite Fenavic

35 Foundry NetworksNetcool/OMNIbus Integration Module for FoundryNetworks

IBM

36 FujitsuNetcool/OMNIbus Integration Module for FujitsuFLASHWAVE

IBM

37 FujitsuNetcool/OMNIbus Integration Module for FujitsuNETSMART 1500

IBM

38Gamatronic ElectronicIndustries LTD

G4-Tivoli Control, Management and Monitoring UnitGamatronic ElectronicIndustries LTD

39 HatterasNetcool/OMNIbus Integration Module for HatterasNetworks HN4000/HN400

IBM

40 HuaweiNetcool/OMNIbus Integration Module for HuaweiTechnologies iManager I2000

IBM

41 HuaweiNetcool/OMNIbus Integration Module for HuaweiTechnologies AR- and S-Series

IBM

42 HuaweiNetcool/OMNIbus Integration Module for HuaweiTechnologies NetEngine Series

IBM

43 IBMNetcool/OMNIbus Integration Module for Tellabs7190/7194 Management System

IBM

44 IBMTivoli Common Reporting Event Reports for TivoliNetcool/OMNIbus

IBM

45 IBM Tivoli Event Flows Best Practices Integration for SOA IBM

46 IBM IBM Tivoli Netcool/OMNIbus Integration Best Practices IBM

47 InfineraNetcool/OMNIbus Integration Module for Infinera ATN andDTN

IBM

48 InfineraNetcool/OMNIbus Integration Module for Infinera FaultIntegration Server

IBM

49 Intelliden, IncIntelliden Solution Integration for IBM TivoliNetcool/OMNIbus™

Intelliden, Inc

50 IptiviaIptivia RouteDynamics integration with IBM Tivoli/NetcoolOmnibus®

Iptivia

51 JuniperNetcool/OMNIbus Integration Module for JuniperNetworks Intrusion Detection and Prevention (IDP)

IBM

52 JuniperNetcool/OMNIbus Integration Module for JuniperNetworks JUNOSe

IBM

53 JuniperNetcool/OMNIbus Integration Module for JuniperNetworks JUNOS

IBM

54 JuniperNetcool/OMNIbus Integration Module for JuniperNetworks NetScreen-Security Manager

IBM

55 JuniperNetcool/OMNIbus Integration Module for JuniperNetworks NetScreen ScreenOS

IBM

56 Keymile Netcool/OMNIbus Integration Module for KEYMILE UNEM IBM

57 Meta4 LtdMetaforSys Concerto Self-service monitoring frameworkv1.2

Meta4 Ltd

58 MIR3, Inc. inEnterprise for IBM Tivoli® Netcool/OMNIibus MIR3, Inc.

59 MIR3, Inc. Automated Notification for Netcool/OMNIbus MIR3, Inc.

60 Mobile Complete, Inc.DeviceAnywhere Monitoring / Netcool/OMNIbusIntegrated Solution

Mobile Complete, Inc.

61 Mobixell Networks Event Managment for Mobixell's Ad-It Mobixell Networks

62 NECNetcool/OMNIbus Integration Module for NEC PNMSj forPasolink

IBM

63 Nera Networks Netcool/OMNIbus Integration Module for Nera NetMaster IBM

64 NetIQ Corporation AppManager Connector for Netcool/OMNIbus NetIQ Corporation

65 NetscoutNetcool/OMNIbus Integration Module for NetScoutnGenius Performance Manager

IBM

66 Opalis Software Inc. Opalis Integration Pack for IBM Tivoli Netcool/OMNIbus Opalis Software Inc.

67 Optinuity, Inc. Optinuity C2O Tivoli Netcool/OMNIbus template Optinuity, Inc.

68 PacketLight Networks LTDNetcool/OMNIbus Integration with PL SNMP Agent Rev1.5

PacketLight Networks LTD

69 Panduit Corp. PanView Intelligent Physical Layer Management Solution Panduit Corp.

70RAD DataCommunications Ltd.

Netcool/OMNIbus Integration Module for RADview-EMSRAD DataCommunications Ltd.

71 RADCOMNetcool/OMNIbus Integration Module for RADCOMOmni-Q

IBM

72 Riverbed Technology Inc.Riverbed Steelhead Integration with IBM TivoliNetcool/OMNIbus

Riverbed Technology Inc.

73 Rocket Software, Inc.Rocket Integrated Network Management integration withIBM Netcool/OMNIbus

Rocket Software, Inc.

74 Soprano Design Pty Ltd Soprano Mobile Enterprise Messaging Suite Soprano Design Pty Ltd

75 Splunk, Inc.Splunk IT Search Engine integration with TivoliNetcool/OMNIbus

Splunk, Inc.

76 Sunrise TelecomIBM Tivoli Netcool/OMNIbus Integration for SunriseTelecom TAMS

Sunrise Telecom

77 SymmetricomNetcool/OMNIbus Integration Module for SymmetricomV-Factor QoE Platform

IBM

78 TektronixNetcool/OMNIbus Integration Module for TektronixGeoProbe

IBM

79 TellabsNetcool/OMNIbus Integration Module for Tellabs 8890Management System

Tellabs

80 Trilliant Trilliant Smart Grid SecureMesh Network Management Trilliant

81 Tropic NetworksNetcool/OMNIbus Integration Module for Tropic NetworksTRX-24000

IBM

82 Wily Technology Inc.Wily Introscope PowerPack for IBM Websphere ApplicationServer Netcool/OMNIbus integration

Wily Technology Inc.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Tivoli Netcool OMNIbus Probe Integrations > Beginner’s Guide to WritingRules Files

Beginner’s Guide to Writing RulesFiles0 people like this

|Updated October 11, 2013 by AzmanDzamiri|Tags: NonePage Actions ▼

Use this guide to quickly write rules files that:

provide improved Alarm Presentation,1. accurately De-duplicate events,2. and Generic-Clear compliant to correlate Problems/Resolutions.3.

Setting the standards for the following object server fields and almosteverything else comes for free:@Node - The entity that the alarm refers to (could be symbolic DNS name, IPAddress, MAC Address, or any user comprehensible name)

@NodeAlias - This should be the logical address of the entity, eg host : port.It is recommended to set this to the value required to enable a right-clickdesktop tool to be able to connect to the entity. Failing that it will probablybe the same as @Node

@Manager - "<name of probe> on "+hostname()

@Agent - This is subordinate to the Manager field, should include name ofvendor and system name, eg Marconi-EMOS or Dan.com-someMIbName.(use Vendor-System to allow impact etc to use a standard format)

@Class - Used to determine which set of tools are available when you rightclick on this event. The Class number can be obtained from thealerts.objclass table.

@AlertGroup - This is the descriptive name of the type of the problem eg"power status", "link status" etc. This should be set to the same value in aproblem and resolution so the generic clear will work.

@AlertKey - This is the *logical* name of the managed object instance, eg"which power supply is down", "which port is down" etc. We put the new

human readable name of the managed object into the summary field.

@Severity - Use common sense when assigning severity ideally map the datasource severity directly. (Note: resolution events should be set to severity 1,the generic clear will set them to 0 later)

@Summary - Explain the problem, keep it nice and compact. Also includethe managed object instance text: eg "Port down ( Host x, Card 7, port 12 )".Use double spaces as they look better. Capitalise each word in thedescription.

@Type - Set to 1 for a problem, 2 for resolution, and on old systems you canset to greater than 10 for an expiry time.

@LastOccurrence / @FirstOccurrence - set these to either “getdate” (i.e.now), or to the time stamp information in the event if it exists.

Finally you should then be able to set @Identifier to:@Identifier = @Node + " " + @AlertKey + " " + @AlertGroup + " " +@Type + " " + @Agent + " " + @Manager

If the fields have been set correctly this will de-duplicate the alarmscorrectly.

Lookup Tables: Not all of the information that we’d like to store in theObject Server is available within the event, but a lot can be derived from thefields in the event. To do this you should create lookup tables mapping thefields. For example @AlertGroup (“power status” “link status” etc), mayactually be an integer in the event, so should be converted into morereadable text in the rules file to make the events easier to understand.

GenericClear: The following fields are used by the generic clear automation;@AlertGroup, @AlertKey, @Severity, @Type and @Identifier.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Tivoli Netcool OMNIbus Probe Integrations

Tivoli Netcool OMNIbus ProbeIntegrations1 person likes this

1|Updated October 6, 2014 by DonW|Tags: NonePage Actions ▼

Many integrations can be implemented through a universal or standardsbased integration either directly or through an intermediate application orscript formatting the events for input to one of our universal probes. You willneed to identify what interfaces are supported by the equipment to bemanaged for northbound alerting .e.g. 3GPP, SNMP, Syslog, Logfile, ASCIIPipe or telnet. This information is usually available from the product vendor.If there is a universal Netcool probe that can read events from the identifiedinterface, then you may just need to produce a rules file specific to themanaged system.

Note - Probes are not individually entitled. The appropriate probe or probesmay be deployed for event collection against each entitled Device, BasicDevice or EMS. These definitions are available within the announcementletter and latest product version licenses.

Universal probe list

Utility probe list

Vendor specific probes

The Netcool Knowledge Library (NcKL) provides a wide range of preparedrules for standard based MIBs, vendor extensions, and syslog definitions.

The ISM Library (formerly OPAL) includes pages for compatible rules filesand partner integrations.

Specific Ericsson probes were withdrawn in 2012 and are not longersupported. [Original announcement] Generic alternatives areavailable for many of the original items, others may require specificservices based integration.

Platform and Netcool/OMNIbus version support

Most probes are supported on all platforms that are supported by theunderlying version of the prerequisite Netcool/OMNIbus probe baseinstallation.Please refer to the Software Product Compatibility Reports (SPCR) forplatforms supported by Netcool/OMNIbus versions.A small number of probes are only available on specific platforms due totechnical limitations. The individual probe documentation on theInformation Center documents any limitations on platform support forthat probe.Probes are version agnostic with the Netcool/OMNIbus Objectserver.

**Universal Probes

Interface Type Probe Name

3GPP Corba 3GPP V3.2

Application or process output - ASCII Exec

CEI/SOA (IBM Common Event Infrastructure CEI

Console output - ASCII Standard/Stdin

EIF (IBM Event Integration Facility) Tivoli EIF

Email (IMAP, POP3) Email

HTTP error log HTTP

JDBC compliant table JDBC

Log file - ASCII Generic Log File

ODBC compliant table (being replaced by JDBC) ODBC

Oracle tables (being replaced by JDBC) Oracle

Pipe - ASCII FIFO

SNMP traps (V1, V2, V3 support) SNMP

Syslog daemon Syslogd

Syslog files Syslog

TCP Socket - ASCII Multi-headed Socket

TL1 (ITU Transaction Language/1) TL1

XML over JMS, HTTP/HTTPS, MQTT and data file

connectionsMessageBus

**Utility probes

The utility probes may be implemented to verify that remote devices are accessible and active either by heartbeatgeneration from the device, or by ping from a central location.

Function Probe Name

The Heartbeat Probe simply generates a standard eventat a predetermined interval.

Heartbeat

The Ping Probe may can be used to monitorreachability for any device which supports the ICMPprotocol

Ping

**Vendor specific probes

Please see the new Vendor specific probe integrations on InformationCenter for information on current certified device details

Comments

1-6 of 6

PreviousNext

Ken Tyler commented on July 17, 2014 Permalink

Don, thanks for the info. I have not been able to find any of the probe-specific documentation on the Knowledge Center. The only thing I can find isreferences to probes in the OMNIbus installation guides for the variousversions.Ken

Ken Tyler commented on July 17, 2014 Permalink

I stand corrected. I was able to locate the documentation with a bit of effort. For any one else who find the Knowledge Center challenging, here is thelink: https://ibm.biz/BdFEDA.

Edited on July 17, 2014

IanMcArthur commented on September 5, 2014 Permalink

I am struggling to find any documentation for an SMTP probe and whetherwe need to use ITCAM rather than ISM now that we have upgraded toversion 7.3.1. Any pointers would be appreciated. Cheers Ian

DonW commented on October 6, 2014 Permalink

SMTP is documented as the email probe. The move from ISM to ITCAM isnot related to an OMNIbus version. The old ISMs should continue tofunction, but were subsumed into ITCAM for Transactions several years ago.

DonW commented on October 6, 2014 Permalink

The Information Center link to the vendor specific probes has been repaired.

SBarger commented on June 30, 2016 Permalink

Hi Don! Can you please list out the "preferred" method order to receiveevents from sources? Lets say, for instance, that a source had the ability tosend all of the different types of events (vendor specific, EIF, posteifmsg,snmp, syslog, etc)...What would be the "best practice" order of receivingevents into Netcool and Probes...and why? Thanks!!

Show


PreviousNext

You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Integrations GA Releases

Integrations GA Releases1 person likes this

1|Updated November 7, 2013 by SeanSoon|Tags: NonePage Actions ▼

This page contains the links to the latest and the old release announcements:

Tivoli Netcool/Omnibus Integrations Release 3 2013Tivoli Netcool/Omnibus Integrations Release 2 2013Tivoli Netcool/Omnibus Integrations Release 1 2013Tivoli Netcool/Omnibus Integrations Release 3 2012

Tivoli Netcool/Omnibus Integrations Release 2 2012Tivoli Netcool/Omnibus Integrations Release 1 2012

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >How to forward SNMP traps from Q1labs Qradar SIEM to Mttrapd probe.

How to forward SNMP traps fromQ1labs Qradar SIEM to Mttrapdprobe.0 people like this

|Updated October 29, 2013 by MunirahLebaiLutfi|Tags: NonePage Actions ▼

This wiki show the steps on how to forward snmp traps from IBM SecurityQradar SIEM to Mttrapd probe.

Login to IBM Security Qradar SIEM web client.1.

Go to Admin tab → System Configuration.2.

Under System Configuration, choose System Settings.3.

On the System settings window, Fill up the SNMP version (eitherSNMPv2c/SNMPv3).

For SNMPv2c, operator just has to fill 3 fields as below:a. Destination host – The host name of where Mttrapd probe is installed and running.b. Destination port – The port number of where Mttrapd probe is listening too.c. Community – The community string.

4.

For SNMPv3, operator has to fill 5 fields and choose 3 options fromdropdown menu as below: a. Destination host – The host name of where Mttrapd probe is installed and running. b. Destination port – The port number of where Mttrapd probe is listening too. c. Username – The username defined in mttrapd.conf file. d. Security level – [NOAUTH_NOPRIV, AUTH_NOPRIV, AUTH_PRIV] e. Authentication Protocol – [MD5, SHA] f. Authentication Password – Either MD5 / SHA authentication password. g. Privacy Protocol – [DES, BLOWFISH, AES256, AES128] h. Privacy Password – Password respective privacy protocol as listed in (g).

Once operator click on 'Save', below message will be displayed:5.

Go to Admin tab → Deploy Changes to deploy the changes just done onthe system configuration.

6.

From Mttrapd probe log, operator can see traps from IBM SecurityQradar SIEM are forwarded to the Mttrapd probe.

7.

To enable raw capture, update probe properties file for RawCapture tovalue '1'.

8.

Acronyms/Abbreviations:SIEM – Security Information & Event ManagementSNMP - Simple Network Management ProtocolMD5 - Message Digest 5 (algorithm)SHA - Secure Hash AlgorithmAES - Advanced Encryption StandardDES - Data Encryption Standard

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Integrating >Configuring Tivoli OMNIbus to use PAM for external authentication (Solaris)

Configuring Tivoli OMNIbus to usePAM for external authentication(Solaris)0 people like this

|Updated October 30, 2013 by MunirahLebaiLutfi|Tags:

gateway,ldap,pam,probe

Page Actions ▼

Pluggable Authentication Modules (PAM) is an integrated UNIX® loginframework. PAM is used by system entry components, such as thedtlogin display manager of the Common Desktop Environment, toauthenticate users logging into a UNIX system. PAM can also be used byPAM-aware applications for authentication. These applications include theObjectServer, the process agent, and gateways. You can set up PAMauthentication either by using external authentication sources, such as NISand LDAP, or by using a single, central ObjectServer.Restriction: The PAM module that is provided in the Tivoli®Netcool/OMNIbus installation does not support external authentication to athird-partyauthentication system. This PAM module is intended for use only whensetting up a single, central ObjectServer as an authentication source.

(Option 1) Configuring Tivoli Netcool/OMNIbus to use PAM for externalauthentication-------------------------------------------------------------------------------------------------------------------On UNIX and Linux®, you can configure ObjectServers, process agents, andgateways to use a PAM framework with external authentication modulessuch as NIS and LDAP.

(Option 2) Configuring an ObjectServer as a PAM authentication source-------------------------------------------------------------------------------------------------To configure an ObjectServer to control PAM authentication, you must set upyour ObjectServers to defer authentication and password management toa single, central ObjectServer, and then enable external authentication for

each ObjectServer and user on your system.

This procedure outline the steps that are necessary to configure omnibus,process agent and socket gateway services to use PAM for externalauthentication (Option 1) for Solaris 10.

For (Option 2), please refer to OMNIbus 7.3.1 Installation and DeploymentGuide for more details:Document: omn_pdf_ins_master_731.pdfSection: Chapter 12. Tivoli Netcool/OMNIbus user access security > Useraccess security > PAM authentication (UNIX and Linux).

Type of user required: System root or sudo root user.

1. Update the PAM configuration file (Solaris 10):This PAM configuration file (pam.conf) controls the PAM stacks for PAMenabled services. The format of each entry is as follows:<service_name> <module_type> <control_flag> <module_path>[module_options]Where:<service_name> is: The name of the PAM enabled service.<module_type> is one of: auth, account, password, session<control_flag> is one of: required, requisite, sufficient, optional<module_path> is:The path to the module. If the field does not begin with '/', then /usr/lib/security/ is prefixed.[module_options] is: An optional field. Consult the specified modulesdocumentation for valid options.

(Required for the Object Server/OMNIbus):Service Name: nco_objservModule Type: auth, account, password

(Required for the Process Agent (PA)):Service Name: netcoolModule Type: auth

(Required for the Gateway):Service Name: <gateway binary name>(eg. nco_g_socket for socket gateway)Module Type: auth, account

For Gateway: Update the entries below in /etc/pam.conf for object server,process agent and socket gateway services (Gateway support PAMauthentication).For Probe: Update the entries below in /etc/pam.conf for object server andprocess agent service (Probe does not support PAM authentication).

# PAM Configuration for the Object Server.service module_type control_flag module_path optionsnco_objserv auth requisite pam_authtok_get.so.1nco_objserv auth required pam_dhkeys.so.1nco_objserv auth required pam_unix_cred.so.1nco_objserv auth required pam_unix_auth.so.1nco_objserv account requisite pam_roles.so.1nco_objserv account required pam_unix_account.so.1nco_objserv password required pam_dhkeys.so.1nco_objserv password requisite pam_authtok_get.so.1nco_objserv password requisite pam_authtok_check.so.1nco_objserv password required pam_authtok_store.so.1

# PAM Configuration for the Process Agent.service module_type control_flag module_path optionsnetcool auth requisite pam_authtok_get.so.1netcool auth required pam_dhkeys.so.1netcool auth required pam_unix_cred.so.1netcool auth required pam_unix_auth.so.1

# PAM Configuration for the Socket Gateway.service module type control_flag module_path optionsnco_g_socket auth requisite pam_authtok_get.so.1nco_g_socket auth required pam_dhkeys.so.1nco_g_socket auth required pam_unix_cred.so.1nco_g_socket auth required pam_unix_auth.so.1nco_g_socket account requisite pam_roles.so.1nco_g_socket account required pam_unix_account.so.1

2. Configure Object Server user for external authentication (Solaris10):From the SQL interactive interface (nco_sql), use the CREATE USERcommand to create user.-The user name entered is identical to the name stored in the externalauthentication repository.-No password is specified.-The PAM keyword is set to TRUE.

2.1. If not already started, bring up object server 'NCOMS' in backgroundprocess at the host server.$OMNIHOME/bin/nco_objserv -name NCOMS &NOTE:On UNIX and Linux, the default value for object server security mode is“PAM”.Otherwise, please set below properties in the object server props file beforestarting theobject server:

Sec.ExternalAuthentication : 'PAM'Sec.UsePam : TRUE

2.2. Log into sql interactive interface for object server 'NCOMS' with defaultuser root andempty password:$OMNIHOME/bin/nco_sql -server NCOMS -user "root" -password ""

2.3. Create a user with username identical to the LDAP username.Syntax: create user '<ldap user>' id <any id number> full name '<fullname>' PAM TRUE;Example if LDAP username is thomas:1>create user 'thomas' id 888 full name 'Thomas Anderson' PAM TRUE;2>go

2.4.Assign the user in default 'System' group which has the 'SuperUser' role.'SuperUser' role has all available permissions.1>alter group 'System' assign members 'thomas';2>go

2.5.Check the password of LDAP username is label to NIS and enable LDAPuser.1>select UserName,Passwd from security.users;2>goUserName Passwd-----------------------------------rootthomas NIS1> alter user 'thomas' set ENABLED true;2> go1> exit

2.6. Again, log into sql interactive interface (nco_sql) for object server'NCOMS'. This time,use the LDAP user created at step 2.3:$OMNIHOME/bin/nco_sql -server NCOMS -user "thomas" -password"<actual_John_Anderson_LDAP_password>"Login to the ObjectServer with LDAP credentials should be successful at thispoint.

3. Configure object servers, process agent and gateway to use PAMauthentication.

This step configuring the ObjectServer to use PAM authentication:On UNIX and Linux, the default value is PAM.Set property below in the object server properties file.Sec.ExternalAuthentication: PAM

This step configuring the process agent to use PAM authentication:Ignore this now and run it when you bring up the Process Agent, run$NCHOME/omnibus/bin/nco_pad command, append command-line-authenticate PAM

This step configuring the socket gateway to use PAM authentication (Forgateway only):Set property below in the gateway props file.Location in Unix: $OMNIHOME/etc/NCO_GATE.props file.Gate.UsePamAuth: True

Acronyms/Abbreviations:PAM - Pluggable Authentication ModuleLDAP - Lightweight Directory Access ProtocolSQL - Standard Query Language

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation

How-to documentation0 people like this

|Updated January 3, 2013 by ZaneBray|Tags: NonePage Actions ▼

The following Tivoli Netcool/OMNIbus sections are included in this How-tosection:

Installing and Configuring

Administering

Performance and Tuning

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > IBM Tivoli Netcool - postdeployment hostname or IP change

IBM Tivoli Netcool - postdeployment hostname or IPchange1 person likes this

1|Updated February 25, 2013 by Gkaur|Tags:

hostname,ip,virtual,virtualization,virualisation,vm

Page Actions ▼

This publication contains the hostname or IP address changes required bythe following IBM Tivoli Netcool products and components on deployment:

IBM Autonomic Deployment Engine;Tivoli Integrated Portal (WebGUI, Impact GUI parts, Topoviz/ITNM);Tivoli Netcool/OMNIbus 7.x (includes ObjectServer, Gateways, Probes,WebGUI);Tivoli Netcool/Impact 6.1;IBM Tivoli Network Manager 3.9.

This publication is intended for Netcool Administrators or technical staff thatare responsible for deploying or administering Tivoli Netcool environments.

Click here to read the entire document.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Installing andConfiguring > How to set probe to use specific JRE

How to set probe to use specific JRE0 people like this

|Updated July 10, 2012 by Mahyuddin|Tags: NonePage Actions ▼

Beginning Nonnative version 10.0, probe by default is using JRE installed together with Omnibus. However some probes require to use other version of JREor JRE from other vendor (exp: Oracle). To set probe to use specific JRE other than JRE packaged with Omnibus installation, follow these steps:-

Setup for Unix platforms

Edit $OMNIHOME/probes/java/nco_p_<probe>.env file and add the following line.

JAVA_HOME="<location of jre>"

Example:-

For java binary located at /usr/lib/jvm/jre-1.6.0-ibm.x86_64/bin/java. To set probe to use this JRE, the JAVA_HOME setting will be...

JAVA_HOME="/usr/lib/jvm/jre-1.6.0-ibm.x86_64"

Some probes does not provide the .env file. If the script does not exist, create the script following steps from Default Probe Environment File for Probe'sEnvironment Setting.

To check if the setup works

Run probe with -version command. Check sample below on blue highlighted part. Before probe use default IBM JRE version 1.6.7. After change, probe useIBM JRE version 1.6.0.

Output before set the JAVA_HOME:-

$ nco_p_alcatel_5529_oad_v6 -versionUsing IBM JavaVersion 1.6.7Netcool/OMNIbus oad probe - Version 7.3.1(C) Copyright IBM Corp. 1994, 2007Netcool/OMNIbus Probe API Library Version 7.3.1Release ID: 2.0.2JAR Build Date: Wed Oct 5 11:07:30 BST 2011 on rhat3es-build1 (Linux 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 13 17:56:20EDT 2006)API Release ID: 5.21.27Software Compile Date: Tue Jul 12 07:18:57 UTC 2011 on rhat3es-build1 (Linux 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 1317:56:20 EDT 2006)

Output after set the JAVA_HOME to /usr/lib/jvm/jre-1.6.0-ibm.x86_64:-

$ nco_p_alcatel_5529_oad_v6 -versionUsing IBM JavaVersion 1.6.0Netcool/OMNIbus oad probe - Version 7.3.1(C) Copyright IBM Corp. 1994, 2007Netcool/OMNIbus Probe API Library Version 7.3.1Release ID: 2.0.2JAR Build Date: Wed Oct 5 11:07:30 BST 2011 on rhat3es-build1 (Linux 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 13 17:56:20EDT 2006)API Release ID: 5.21.27Software Compile Date: Tue Jul 12 07:18:57 UTC 2011 on rhat3es-build1 (Linux 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 1317:56:20 EDT 2006)

Extra note for Corba type probes that using IBM Orb

This guide does not apply for Corba type probes that using IBM Orb. The reason is probe require IBM Orb that packaged together with IBM JRE installed withOmnibus installation. Thus, the robe must use IBM JRE. Check the Summary table of probe's reference guide to confirm whether probe is using VisibrokerOrb or IBM Orb.

Example for ECI Lightsoft probe:-

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Installing and Configuring > Probe Encryption SetupExamples

Probe Encryption Setup Examples0 people like this

|Updated June 4, 2012 by fadhli|Tags:

ibm-blog-l3,omnibus-probes-encrypt,probes

Page Actions ▼

The encryption can be implemented in 2 directions: Probe to Object Server and Probe to target system. The nco_aes_crypt utility to encrypt anddecrypt string values can also be used as a solution to hide plaintext values for any password property that is not utilizing nco_g_crypt tool.

A) Authenticating against Omnibus Object Server

1.Ensure Object Server is started in secure mode.

fernande@klomni01:/export/home/omni_int/v731/omnibus/bin$ ./nco_objserv -secure

Netcool/OMNIbus Object Server - Version 7.3.1

(C) Copyright IBM Corp. 1994, 2007

Server 'NCOMS' initialised - entering RUN state.

2.Probe property settings of concern.

#########################################################################

#To make alterations to the default value for any properties

#append the new values here:-

#########################################################################

ConfigCryptoAlg : 'AES' <- default (for backward compatibility)

MessageLevel : 'debug'

AuthUserName : 'ric' <- Step1

ConfigKeyFile : '/export/home/omni_int/v731/etc/security/keys/netcool.keygen' <- Step2

AuthPassword : '@44:wUMib8i4aHPDhd3Yhq8wxbTG+wfZ2miZftX4iCkL5PM=@' <- Step3

(Step 1 - AuthUserName)

- Create a user ex. "ric" or use existing user, usually "root"

- assign a password to it via Omnibus Admin console

(Step 2 - ConfigKeyFile)

- Generate config key file

$OMNIHOME/bin/nco_keygen -o $NCHOME/etc/security/keys/netcool.keygen

devtest11.hursley.ibm.com:/home/fernande/netcool/omnibus-v7.2.1-solaris/omnibus/probes>more $NCHOME/etc/security/keys/netcool.keygen

128:Ã}ß¤ëC©´õZyÓb

(Step 3 - AuthPassword)

- Generate password (ex. abcd1234), based on user assigned in Step 2

devtest11.hursley.ibm.com:/home/fernande/netcool/omnibus-v7.2.1-solaris/omnibus/probes>$NCHOME/omnibus/bin/nco_aes_crypt -c AES -k$NCHOME/etc/security/keys/netcool.keygen abcd1234

@44:WqJBI99bPrts3Enh+tMNjRId4kqmRhTqXAhdSk3QAGE=@

3.Execute probe

fernande@klomni01:/export/home/omni_int/v731/omnibus/probes$ ./nco_p_simnet

B) Authenticating against Target System

1.Probe property settings of concern (example: VPO probe).

######################################################################### To make alterations to the default value for any properties# append the new values here:-######################################################################## #ConfigCryptoAlg : 'AES' <- default (for backward compatibility)MessageLevel : 'debug'Opcuser : 'OpcAdmin'ConfigKeyFile : '/export/home/omni_int/v731/etc/security/keys/netcool.keygen' <- Step1Opcpassword : '@44:wUMib8i4aHPDhd3Yhq8wxbTG+wfZ2miZftX4iCkL5PM=@' <- Step2

(Step 1 – ConfigKeyFile) * same as above

- Generate config key file

$OMNIHOME/bin/nco_keygen -o $NCHOME/etc/security/keys/netcool.keygendevtest11.hursley.ibm.com:/home/fernande/netcool/omnibus-v7.2.1-solaris/omnibus/probes>more $NCHOME/etc/security/keys/netcool.keygen

128:Ã}ß¤ëC©´õZyÓb

(Step 2 - Opcpassword)

- Generate password (ex. abcd1234), based on user assigned in Step 1

devtest11.hursley.ibm.com:/home/fernande/netcool/omnibus-v7.2.1-solaris/omnibus/probes>$NCHOME/omnibus/bin/nco_aes_crypt -c AES -k $NCHOME/etc/security/keys/netcool.keygen abcd1234

@44:WqJBI99bPrts3Enh+tMNjRId4kqmRhTqXAhdSk3QAGE=@

2.Execute probe.

fernande@klomni01:/export/home/omni_int/v731/omnibus/probes$ ./nco_p_vpo_Sparc_Solaris

More info:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.netcool_OMNIbus.doc_7.3.1%2Fomnibus%2Fwip%2Fprobegtwy%2Fconcept%2Fomn_prb_securemode.html

http://publib.boulder.ibm.com/infocenter/ieduasst/tivv1r0/index.jsp?topic=/com.ibm.iea.netcoolomnibus/netcoolomnibus/7.2.1/security/aes_propertyvalue_encrypt/player.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.netcool_OMNIbus.doc_7.3.1%2Fomnibus%2Fwip%2Fadmin%2Freference%2Fomn_adm_propsfileencryption.html

* Credits to Eric Fernandez, ex-L3 Omnibus Integrations team member.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > How to run multiple instancesof probe as Windows service

How to run multiple instances ofprobe as Windows service0 people like this

|Updated June 25, 2012 by haeloong|Tags: NonePage Actions ▼

Problem/Issue:How to run multiple instances of probe as Windows service?

Symptom:NA

Fix/Workaround:The probe can be configured to run in multiple instances provided that youhave setup the Windows services with unique instance and name.

The command %OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL/INSTANCE <instance> /CMDLINE "-name <name>"where:1. instance specifies the unique instance name be installed as a service in theWindows Services2. name specifies the unique name used in the files set for .props, .rules and.log

Procedures to create multiple unique GLF probe instances in theWindow ServicesStep 1: Create the necessary set of files for each unique GLF probe:a. Define 2 unique set of the .props and .rules files for each GLF probes asfollow:%OMNIHOME%\omnibus\probes\win32\glf_01.props%OMNIHOME%\omnibus\probes\win32\glf_01.rules%OMNIHOME%\omnibus\probes\win32\glf_02.props%OMNIHOME%\omnibus\probes\win32\glf_02.rules

By default, the following properties will be reflected and using the defined

unique name that installed and registered as service in Windows Services.You MUST NOT make any changes to these default properties.

For glf_01.props:-Name : "glf_01"MessageLog : "$OMNIHOME/log/glf_01.log"PropsFile : "$OMNIHOME/probes/win32/glf_01.props"RulesFile : "$OMNIHOME/probes/win32/glf_01.rules"RawCaptureFile : "$OMNIHOME/var/glf_01.cap"RecoveryFile : "$OMNIHOME/var/glf_01.reco"

For glf_02.props:-Name : "glf_02"MessageLog : "$OMNIHOME/log/glf_02.log"PropsFile : "$OMNIHOME/probes/win32/glf_02.props"RulesFile : "$OMNIHOME/probes/win32/glf_02.rules"RawCaptureFile : "$OMNIHOME/var/glf_02.cap"RecoveryFile : "$OMNIHOME/var/glf_02.reco"

Step 2: Run the following commands to install the instances asWindows services as shown in the screenshot below:

%OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL /INSTANCEGLF_INSTANCE_01 /CMDLINE "-name glf_01"%OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL /INSTANCEGLF_INSTANCE_02 /CMDLINE "-name glf_02"

image

Step 3: Verify the instances created through Services Windows

(services.msc) as shown in screenshots below: image

image

Step 4: Or verify the service through the Registry Editor (regedit.exe)as shown in screenshot below:

image

Step 5: Start the service:By default, the installed instances in Windows Services are startedautomatically. You may change it to Manual.You may start the probe instance either througha. the Windows Services dialog box, ORb. the command line: sc start "NCOGLFProbe$GLF_INSTANCE_01"

Step 6: Stop the service:You may stop the probe instance either througha. the Windows Services dialog box, ORb. the command line: sc stop "NCOGLFProbe$GLF_INSTANCE_01"

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > Default Probe EnvironmentFile for Probe's Environment Setting

Default Probe Environment Filefor Probe's Environment Setting0 people like this

|Updated July 10, 2012 by Mahyuddin|Tags: NonePage Actions ▼

This entry to complement the previous entries on using Probe's Environmentfile to meet some objectives as (but not limited) below:-

How to set probe to use specific JRE1.

How to turn on Visibroker logging for OMNIbus Integrations Probes2.

How to turn on Nonnative logging for OMNIbus Integrations Probes3.

How to turn on IBM Orb trace logging for OMNIbus Integrations Probes4.

The default environment files have been pre-configured to load all jars under<OMNIHOME>/probes/java/ directory. User anyway can enhance this fileto only load specific jars required by probe to run.

Deployment steps:-

Copy the nco_p_probe_name.env to <OMNIHOME>/probes/java/directory.

1.

Rename the file following the name of the probe.

Example the environment file is for probe nco_p_alcatel_5620_corbaprobe. Then rename the nco_p_probe_name.env file tonco_p_alcatel_5620_corba.env.

2.

Edit or append the content of the environment file to your need.3.

Download link:-

nco_p_probe_name.env

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > How to Force Probe to UseSpecific .NET Version

How to Force Probe to Use Specific.NET Version0 people like this

|Updated September 13, 2012 by fadhli|Tags:

microsoft,omnibus,probe-integrations

Page Actions ▼

Why need to enforce which .NET version to use?

Some issues on Microsoft .NET Framework API are impacting probe which require forcing ofusing specific .NET version as a workaround.

Examples:

1) Defect in .NET 3.5 causes probe to misbehave in East-Asian locale when event data volumereaches 2GB. Users of East-Asian languages must either enable UTF-8 mode in this probe orupgrade .NET Framework in probe machine to version 4.0.

2) The design of .NET Framework 4.0 to use strict rendering may cause probe fail to retrieveEventDescription if eventlog does not has its description in system locale. Use .NETFramework 3.5 which is non-strict rendering in design as a workaround.

Example of forcing probe to use .NET v4.0

1) Copy the following XML lines to a new file:

<configuration>

<startup>

<supportedRuntime version="v4.0"/>

</startup>

</configuration>

2) Save the file in the same location as the probe .exe file, adding .config to the .exe's file

name. For example, if your probe is saved at C:/IBM/Tivoli/Netcool/omnibus/probes/win32

/nco_p_wineventlog.exe, you must save the XML file as C:/IBM/Tivoli/Netcool/omnibus/probes

/win32/nco_p_wineventlog.exe.config.

3) Run your probe as normal. .NET will automatically load the .exe.config file and the

application will run against .NET 4.

Note:

- If the <supportedRuntime> element is not present in the application configuration file, the

version of the runtime used to build the application is used.

- The first three .NET versions specified by "v1.0.3705", "v1.1.4322", and "v2.0.50727" with

.NET Framework version 3.0 and 3.5 use version 2.0.50727 of the CLR.

- Beginning with the .NET Framework 4, only the major and minor version numbers arerequired.

Reference:

http://msdn.microsoft.com/en-us/library/w4atty68.aspx

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation> Installing and Configuring > How to Identify Which .NET Framework Probe isUsing

How to Identify Which .NETFramework Probe is Using0 people like this

|Updated August 31, 2012 by fadhli|Tags: NonePage Actions ▼

1) Use Process Explorer from Sysinternals to open current running process.

Download link: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

2) Double-click on the probe name (Example: nco_p_wineventlog).

3) Check the .NET version from .NET Assemblies tab.

Note:

- The first three versions of the CLR are specified by "v1.0.3705", "v1.1.4322", and"v2.0.50727".

- The .NET Framework version 3.0 and 3.5 use version 2.0.50727 of the CLR.

- Beginning with the .NET Framework version 4, only the major and minor versionnumbers are required (that is, "v4.0" instead of "v4.0.30319").

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Installing and Configuring > SCOM 2012 Quick Start Guide and Configuration to Trigger Alerts

SCOM 2012 Quick Start Guide and Configuration to Trigger Alerts0 people like this

|Updated March 18, 2013 by CraigWigley|Tags:

alerts,scom,scom2012

Page Actions ▼

Overview of Microsoft System Center 2012 - Operations Manager (SCOM 2012)

1) Product and License from Microsoft.

2) Enable users to monitor services, devices, and operations for many computers in a single console.

3) Gain rapid insight into the state of the IT environment and the IT services running across different systems and workloads.

4) Provide numerous views that show state, health, and performance information, as well as alerts generated for availability, performance, configuration and security situations.

5) Generally, Management Server and Operations Console are the main feature of SCOM 2012.

6) Management Server is supported in Windows Server 2008 R2 SP1.

7) Operations Console is supported in

Windows Vista, Windows 7Windows Server 2008Windows Server 2008 R2Windows Server 2008 R2 SP1

8) To begin monitoring, computers running Windows, UNIX, or Linux operating systems must be discovered using Operations Console.

9) Comprehensive monitoring requires that an agent be installed on the discovered computer.

10) Agents supported in Windows platforms:

Windows Server 2003 SP2Windows Server 2008 SP2Windows Server 2008 R2Windows Server 2008 R2 SP1Windows XP Professional x64 Edition SP2Windows XP Professional SP3Windows Vista SP2Windows 7 POSReadyWindows XP Embedded StandardWindows XP Embedded EnterpriseWindows XP Embedded POSReadyWindows 7 Professional for Embedded SystemsWindows 7 Ultimate for Embedded Systems

11) Agents supported in UNIX or Linux platforms:

HP-UX 11i v2 and v3 (PA-RISC and IA64)Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)

12) SCOM 2012 can monitor computers without installing an agent as well. However this is applicable only to Windows-based computer that is discovered by using Operations Console.

13) All alerts generated from the monitoring services will be forwarded to the database. End users can log into Operations Console to view the alerts details from the Active Alert GUI.

14) Types of alerts generated are generally associated with availability, performance, configuration and security situations of the monitored computers.

15) Overall, SCOM 2012 offers many other features. All requirements by feature and supported configurations are published in the TechNet Library from Microsoft site.

QuickStart Guide for SCOM 2012 Deployment

1. Please check Microsoft website for the official pre-requisites for deployment.

For this QuickStart Guide example, download the following requirement packages:

Microsoft Windows Server 2008 R2 SP1Microsoft Framework .NET 4.0Microsoft Report ViewerMicrosoft SQL Server 2008 R2Microsoft SCOM 2012

2. Install Windows Server 2008 R2 SP1

3. Add the .NET 3.5.1 feature to windows. Use the Server Manager UI, or use PowerShell:

Open PowerShell (as an administrator) and run the following:

Import-Module ServerManager

< then >

Add-WindowsFeature NET-Framework-Core

4. Install .NET 4.0

5. Install the Report Viewer

6. Install and setup Active Directory

In AD, create the following accounts and groups, according to your naming convention:

<DOMAIN>\OMAA - OM Server action account

<DOMAIN>\OMDAS - OM Config and Data Access service account

<DOMAIN>\OMWRITE - OM Reporting Write account

<DOMAIN>\OMREAD - OM Reporting Read account

<DOMAIN>\SQLSVC - SQL 2008 service account

<DOMAIN>\SCOMAdmins - OM Administrators security group

<DOMAIN>\Chris - My personal account

Add the “OMAA” account and the “OMDAS” account to the “SCOMAdmins” global group.

Add the domain user accounts for yourself or your team to the “SCOMAdmins” group.

Note: Make sure the “SCOMAdmins” domain global group is added to the Local Administrators group on each server.

7. Install Microsoft SQL Server 2008 R2

Note : Please write down the DB password

8. Install SCOM 2012.

If you can launch and browse SCOM 2012 console after the installation, the software is ready.

9. Install and setup OMNIbus ObjectServer/SCOM 2012 Probe to connect to SCOM 2012 and retrieve events, as described in the reference guide.

10. Import management pack and use EventCreate tool to generate alerts into SCOM “Active Alerts” GUI.

Note : Alternate way to trigger alerts is to setup unit monitoring. Check Microsoft TechNet Library for details on unit monitoring configurations.

11. SCOM 2012 probe should be able to process generated events.

Using EventCreate tool to generate a simple alert in SCOM 2012

1) Create an xml file name “IBMNetcoolTest.xml”.

2) Content of the file:

<?xml version="1.0" encoding="utf-8" ?><ManagementPack xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ContentReadable="true"><Manifest><Identity><ID>IBMNetcoolTest</ID><Version>1.0.0.0</Version></Identity><Name>IBM.Netcool.Test</Name><References><Reference Alias="SystemCenter"><ID>Microsoft.SystemCenter.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference><Reference Alias="MicrosoftWindowsLibrary6050000"><ID>Microsoft.Windows.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference><Reference Alias="System"><ID>System.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference><Reference Alias="Health"><ID>System.Health.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference></References></Manifest><Monitoring><Rules><Rule ID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97" Enabled="true" Target="MicrosoftWindowsLibrary6050000!Microsoft.Windows.Computer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100"><Category>Custom</Category><DataSources><DataSource ID="DS" TypeID="MicrosoftWindowsLibrary6050000!Microsoft.Windows.EventProvider"><ComputerName>$Target/Property[Type="MicrosoftWindowsLibrary6050000!Microsoft.Windows.Computer"]/NetworkName$</ComputerName><LogName>Application</LogName><Expression><And><Expression><SimpleExpression><ValueExpression><XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery></ValueExpression><Operator>Equal</Operator><ValueExpression><Value Type="UnsignedInteger">999</Value></ValueExpression></SimpleExpression></Expression><Expression><SimpleExpression><ValueExpression><XPathQuery Type="String">PublisherName</XPathQuery></ValueExpression><Operator>Equal</Operator><ValueExpression><Value Type="String">EventCreate</Value></ValueExpression></SimpleExpression></Expression></And></Expression></DataSource></DataSources><WriteActions><WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert"><Priority>1</Priority><Severity>2</Severity><AlertName /><AlertDescription /><AlertOwner /><AlertMessageId>$MPElement[Name="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage"]$</AlertMessageId><AlertParameters /><Suppression /><Custom1 /><Custom2 /><Custom3 /><Custom4 /><Custom5 /><Custom6 /><Custom7 /><Custom8 /><Custom9 /><Custom10 /></WriteAction></WriteActions></Rule></Rules></Monitoring><Presentation><Folders><Folder ID="Folder_453dc9b52c2740edaf2998a5157545e4" Accessibility="Public" ParentFolder="SystemCenter!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" /></Folders><StringResources><StringResource ID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage" /></StringResources></Presentation><LanguagePacks><LanguagePack ID="ENU" IsDefault="false"><DisplayStrings><DisplayString ElementID="IBMNetcoolTest"><Name>IBM.Netcool.Test</Name></DisplayString><DisplayString ElementID="Folder_453dc9b52c2740edaf2998a5157545e4"><Name>IBM.Netcool.Test</Name></DisplayString><DisplayString ElementID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97">

<Name>Alert for event 999</Name></DisplayString><DisplayString ElementID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage"><Name>Alert for event 999</Name></DisplayString></DisplayStrings></LanguagePack></LanguagePacks></ManagementPack>

3) In Operations Console, import the management pack:

Administration → Management Packs (right-click) → Import Management Packs → Add → Add from disk (if ask to search online catalog for dependencies – click No) → Install → Status is “Imported”if successful → Close

4) Verify that the imported management pack is listed as “IBM.Netcool.Test” with version “1.0.0.0”.

5) Run Windows Command Prompt as Administrator

6) Type Eventcreate.exe /t error /id 999 /l application /d “this is the description”

7) Go back to Operations Console → Monitoring → Active Alerts GUI.

A new alert with name “Alert for event 999” should be listed.

Creating a Windows services unit monitor to trigger an alert in SCOM 2012

1) Another way to trigger alerts is to create a Windows service unit monitor.

2) In the Operations console, select:

Authoring → Management Pack Objects → Monitors (right-click) → Create a Monitor → Unit Monitor

3) On the Monitor Type page, expand:

Windows Services → Basic Service Monitor → Select a destination management pack at the bottom (You may create a new management pack by clicking the “New” button next to the drop-downlist.) → Next

4) On the General Properties page, enter a value for Name and Description.

Click the “Select...” button and choose Windows Computer as the monitor target.

In the parent monitor drop-down, select Availability and check “Monitor is enabled”.

Click Next.

5) On the Service Details page, select the Computer name and the service to be monitored. Click OK and Next.

6) On the Configure Health page, ensure the health state is Healthy when the service is running;

and the health state is Critical when the service is not running. Click Next.

7) On the Configure Alerts page, check “Generate alerts for this monitor”.

In the Generate an alert drop-down, select “The monitor is in a critical health state”.

Check “Automatically resolve the alert when the monitor returns to a health state”.

Enter a value for Alert name and Alert description.

Select Priority and Severity for the triggered alert and click Create.

8) Verify that a Windows service unit monitoring is created in Authoring → Management Pack Objects → Monitors → Windows Computer → Entity Health → Availability → The monitored service

9) In Windows Desktop, go to Administrative Tools → Services → Stop the monitored service.

10) Go back to Operations Console → Monitoring → Active Alerts GUI.

A new alert should be triggered due to stoppage of the monitored service.

*Acronyms / Abbreviations

AD – Active Directory

DB – Database

GUI – Graphical User Interface

IT – Information Technology

OM – Operations Manager

SCOM – System Center Operations Manager

<DOMAIN> – Domain Name

Comments

<DOMAIN>\OMAA OM Server action account

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Installing and Configuring > SCOM 2012 Quick Start Guide and Configuration to Trigger Alerts.

SCOM 2012 Quick Start Guide and Configuration to Trigger Alerts.0 people like this

|Updated September 26, 2012 by MunirahLebaiLutfi|Tags: NonePage Actions ▼

This blog is a brief introduction on SCOM 2012, quick start guide and configuration to trigger alerts in the target.

Overview of Microsoft System Center 2012 - Operations Manager (SCOM 2012) 1) Product and License from Microsoft. 2) Enable users to monitor services, devices, and operations for many computers in a single console. 3) Gain rapid insight into the state of the IT environment and the IT services running across different systems and workloads. 4) Provide numerous views that show state, health, and performance information, as well as alerts generated for availability, performance, configuration and security situations. 5) Generally, Management Server and Operations Console are the main feature of SCOM 2012. 6) Management Server is supported in Windows Server 2008 R2 SP1. 7) Operations Console is supported in

Windows Vista, Windows 7

Windows Server 2008

Windows Server 2008 R2

Windows Server 2008 R2 SP1

8) To begin monitoring, computers running Windows, UNIX, or Linux operating systems must be discovered using Operations Console. 9) Comprehensive monitoring requires that an agent be installed on the discovered computer. 10) Agents supported in Windows platforms:

Windows Server 2003 SP2

Windows Server 2008 SP2

Windows Server 2008 R2

Windows Server 2008 R2 SP1

Windows XP Professional x64 Edition SP2

Windows XP Professional SP3

Windows Vista SP2

Windows 7 POSReady

Windows XP Embedded Standard

Windows XP Embedded Enterprise

Windows XP Embedded POSReady

Windows 7 Professional for Embedded Systems

Windows 7 Ultimate for Embedded Systems

11) Agents supported in UNIX or Linux platforms:

HP-UX 11i v2 and v3 (PA-RISC and IA64)

Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)

Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)

Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)

IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)

12) SCOM 2012 can monitor computers without installing an agent as well. However this is applicable only to Windows-based computer that is discovered by using Operations Console. 13) All alerts generated from the monitoring services will be forwarded to the database. End users can log into Operations Console to view the alerts details from the Active Alert GUI. 14) Types of alerts generated are generally associated with availability, performance, configuration and security situations of the monitored computers. 15) Overall, SCOM 2012 offers many other features. All requirements by feature and supported configurations are published in the TechNet Library from Microsoft site.

QuickStart Guide for SCOM 2012 Deployment1. Please check Microsoft website for the official pre-requisites for deployment. For this QuickStart Guide example, download the following requirement packages:

Microsoft Windows Server 2008 R2 SP1

Microsoft Framework .NET 4.0

Microsoft Report Viewer

Microsoft SQL Server 2008 R2

Microsoft SCOM 2012

2. Install Windows Server 2008 R2 SP1.3. Add the .NET 3.5.1 feature to windows. Use the Server Manager UI, or use PowerShell: Open PowerShell (as an administrator) and run the following:

Import-Module ServerManager

< then >

Add-WindowsFeature NET-Framework-Core4. Install .NET 4.05. Install the Report Viewer6. Install and setup Active Directory

In AD, create the following accounts and groups, according to your naming convention:

<DOMAIN>\OMDASOM Config and Data Accessservice account

<DOMAIN>\OMWRITE OM Reporting Write account

<DOMAIN>\OMREAD OM Reporting Read account

<DOMAIN>\SQLSVC SQL 2008 service account

<DOMAIN>\SCOMAdminsOM Administrators securitygroup

<DOMAIN>\Chris My personal account

Add the “OMAA” account and the “OMDAS” account to the “SCOMAdmins” global group.

Add the domain user accounts for yourself or your team to the “SCOMAdmins” group.

7. Install Microsoft SQL Server 2008 R2.Note : Please write down the DB password.

8. Install SCOM 2012. If you can launch and browse SCOM 2012 console after the installation, the software is ready.

9. Install and setup OMNIbus ObjectServer/SCOM 2012 Probe to connect to SCOM 2012 and retrieve events, as described in the reference guide.10. Import management pack and use EventCreate tool to generate alerts into SCOM “Active Alerts” GUI.Note : Alternate way to trigger alerts is to setup unit monitoring. Check Microsoft TechNet Library for details on unit monitoring configurations.

11. SCOM 2012 probe should be able to process generated events.

Using EventCreate tool to generate a simple alert in SCOM 2012

1) Create an xml file name “IBMNetcoolTest.xml”.2) Content of the file:

<?xml version="1.0" encoding="utf-8" ?> <ManagementPack xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ContentReadable="true"> <Manifest><Identity><ID>IBMNetcoolTest</ID><Version>1.0.0.0</Version></Identity><Name>IBM.Netcool.Test</Name> <References> <Reference Alias="SystemCenter"><ID>Microsoft.SystemCenter.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference> <Reference Alias="MicrosoftWindowsLibrary6050000"><ID>Microsoft.Windows.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference> <Reference Alias="System"><ID>System.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference> <Reference Alias="Health"><ID>System.Health.Library</ID><Version>6.0.5000.0</Version><PublicKeyToken>31bf3856ad364e35</PublicKeyToken></Reference></References></Manifest> <Monitoring> <Rules> <Rule ID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97" Enabled="true" Target="MicrosoftWindowsLibrary6050000!Microsoft.Windows.Computer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100"><Category>Custom</Category> <DataSources> <DataSource ID="DS" TypeID="MicrosoftWindowsLibrary6050000!Microsoft.Windows.EventProvider"><ComputerName>$Target/Property[Type="MicrosoftWindowsLibrary6050000!Microsoft.Windows.Computer"]/NetworkName$</ComputerName><LogName>Application</LogName> <Expression> <And> <Expression> <SimpleExpression> <ValueExpression><XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery></ValueExpression><Operator>Equal</Operator> <ValueExpression><Value Type="UnsignedInteger">999</Value></ValueExpression></SimpleExpression></Expression> <Expression> <SimpleExpression> <ValueExpression><XPathQuery Type="String">PublisherName</XPathQuery></ValueExpression><Operator>Equal</Operator> <ValueExpression><Value Type="String">EventCreate</Value></ValueExpression></SimpleExpression></Expression></And></Expression></DataSource></DataSources> <WriteActions> <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert"><Priority>1</Priority><Severity>2</Severity><AlertName /><AlertDescription /><AlertOwner /><AlertMessageId>$MPElement[Name="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage"]$</AlertMessageId><AlertParameters /><Suppression /><Custom1 /><Custom2 /><Custom3 /><Custom4 /><Custom5 /><Custom6 /><Custom7 /><Custom8 /><Custom9 /><Custom10 /></WriteAction></WriteActions></Rule></Rules></Monitoring> <Presentation> <Folders><Folder ID="Folder_453dc9b52c2740edaf2998a5157545e4" Accessibility="Public" ParentFolder="SystemCenter!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" /></Folders> <StringResources><StringResource ID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage" /></StringResources></Presentation> <LanguagePacks> <LanguagePack ID="ENU" IsDefault="false"> <DisplayStrings> <DisplayString ElementID="IBMNetcoolTest"><Name>IBM.Netcool.Test</Name></DisplayString> <DisplayString ElementID="Folder_453dc9b52c2740edaf2998a5157545e4"><Name>IBM.Netcool.Test</Name>

</DisplayString> <DisplayString ElementID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97"><Name>Alert for event 999</Name></DisplayString> <DisplayString ElementID="MomUIGeneratedRulee3dae0ea254f4d7dabf5804e832a9f97.AlertMessage"><Name>Alert for event 999</Name></DisplayString></DisplayStrings></LanguagePack></LanguagePacks></ManagementPack>

3) In Operations Console, import the management pack:Administration → Management Packs (right-click) → Import Management Packs → Add → Add from disk (if ask to search online catalog for dependencies – click No) → Install → Status is “Imported” ifsuccessful → Close4) Verify that the imported management pack is listed as “IBM.Netcool.Test” with version “1.0.0.0”.5) Run Windows Command Prompt as Administrator6) Type Eventcreate.exe /t error /id 999 /l application /d “this is the description”7) Go back to Operations Console → Monitoring → Active Alerts GUI.A new alert with name “Alert for event 999” should be listed.

Creating a Windows services unit monitor to trigger an alert in SCOM 20121) Another way to trigger alerts is to create a Windows service unit monitor.2) In the Operations console, select: Authoring → Management Pack Objects → Monitors (right-click) → Create a Monitor → Unit Monitor3) On the Monitor Type page, expand: Windows Services → Basic Service Monitor → Select a destination management pack at the bottom (You may create a new management pack by clicking the “New” button next to the drop-downlist.) → Next4) On the General Properties page, enter a value for Name and Description. Click the “Select...” button and choose Windows Computer as the monitor target. In the parent monitor drop-down, select Availability and check “Monitor is enabled”. Click Next.5) On the Service Details page, select the Computer name and the service to be monitored. Click OK and Next.6) On the Configure Health page, ensure the health state is Healthy when the service is running; and the health state is Critical when the service is not running. Click Next.7) On the Configure Alerts page, check “Generate alerts for this monitor”. In the Generate an alert drop-down, select “The monitor is in a critical health state”. Check “Automatically resolve the alert when the monitor returns to a health state”. Enter a value for Alert name and Alert description. Select Priority and Severity for the triggered alert and click Create.8) Verify that a Windows service unit monitoring is created in Authoring → Management Pack Objects → Monitors → Windows Computer → Entity Health → Availability → The monitored service9) In Windows Desktop, go to Administrative Tools → Services → Stop the monitored service.10) Go back to Operations Console → Monitoring → Active Alerts GUI. A new alert should be triggered due to stoppage of the monitored service.

*Acronyms / AbbreviationsAD – Active DirectoryDB – DatabaseGUI – Graphical User InterfaceIT – Information TechnologyOM – Operations ManagerSCOM – System Center Operations Manager<DOMAIN> – Domain Name

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > How to run multiple Probeinstances with Process Agent in Windows services

How to run multiple Probeinstances with Process Agent inWindows services0 people like this

|Updated December 28, 2012 by haeloong|Tags: NonePage Actions ▼How to run multiple Probe instances with Process Agent in Windows services

You can configure the Process Agent to start/stop its service and all probeinstance services, then you can remove the hassle to start/stop each probeinstance service.

Take GLF Probe as an example, and here are the steps involved:

Step 1: Register the PA as service using commandcommand:%OMNIHOME%\bin\nco_pa.exe /INSTALL

Step 2: Replace the blue command in the nco_pa.conf...nco_process 'GLF_01'{Command 'C:/WINDOWS/system32/sc.exe startNCOGLFProbe$GLF_01' run as 0# Command 'C:\ibm\netcool\omnibus\probes\win32\nco_p_glf.exe -nameGLF_01' run as 0Host = 'IBM-L3CHB3K'Managed = TrueRestartMsg = '${NAME} running as ${EUID} has been restored on${HOST}.'AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'RetryCount = 0ProcessType = PaPA_AWARE}

nco_process 'GLF_02'{

Command 'C:/WINDOWS/system32/sc.exe startNCOGLFProbe$GLF_02' run as 0# Command 'C:\ibm\netcool\omnibus\probes\win32\nco_p_glf.exe -nameGLF_02' run as 0Host = 'IBM-L3CHB3K'Managed = TrueRestartMsg = '${NAME} running as ${EUID} has been restored on${HOST}.'AlertMsg = '${NAME} running as ${EUID} has died on ${HOST}.'RetryCount = 0ProcessType = PaPA_AWARE}...

Step 4: Create the service for each probe registered in the PA configurationcommand:%OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL /INSTANCE <ID>/CMDLINE "-name <probe name>"

example:%OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL /INSTANCE GLF_01/CMDLINE "-name GLF_01"%OMNIHOME%\probes\win32\nco_p_glf.exe /INSTALL /INSTANCE GLF_02/CMDLINE "-name GLF_02"

Step 5: Create a dependency service on process agent service for each probeservice.command:sc config <PROBE SERVICE NAME> depend= <PROCESS AGENT NAME>

example:sc config NCOGLFProbe$GLF_01 depend= NCOProcessAgent

sc config NCOGLFProbe$GLF_02 depend= NCOProcessAgent

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation> Installing and Configuring > Configure Alcatel OSOS probe to retrievenotifications from multiple AS

Configure Alcatel OSOS probe toretrieve notifications from multipleAS0 people like this

|Updated December 31, 2012 by Mahyuddin|Tags:

ibm-blog-l3

Page Actions ▼

Issue:

Alcatel OSOS probe not able to retrieve event of multiple NMS (AS ids) from singleIOO.

Problem:

Generic OS-to-OS interface (IOO) is having capability to manage multiple ASinstances. However IOO it self is only single instance. Thus it only can handlesingle request at a time and forward ALARM_NOTIFICATION from single AS at atime. Figure 1 show on the impossible setup that customer try to implement.

Some scenarios we tried or taken into consideration but failed (so you don't haveto run the same test):-

Send request for AS_1, then send another request for AS_2.

Failed. The latest request will overwrite the previous request. For this case,probe will start receiving ALARM_NOTIFICATION from AS_2 and stopreceiving ALARM_NOTIFICATION from AS_1 after the 2nd request made.

1.

Multiple probe's instances or threads connecting to single IOO. Each ofinstances request for different AS. i.e. Probe instance 1 request for AS_1 andprobe instace 2 request for AS_2.

Failed. IOO is single instance and process single request at a time. Multiplerequest from multiple connection will overwrite the request each other.

2.

Set SubscriptionFilter property to empty (''). Empty is the default value.

Failed. Probe receive event from default AS_1 only.

3.

Set SubscriptionFilter property to “asIdentityFilter={3|2}”.

Failed. IOO only forward ALARM_NOTIFICATION from AS_3 only.

4.

Solution:

Configure multiple instances of IOO and multiple instances of probes and distinctlyconnect to IOO instances. The configuration layout for solution in Figure 2.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > Steps to forward SystemDirector Events to Tivoli EIF Probe & SNMP Probe

Steps to forward System DirectorEvents to Tivoli EIF Probe & SNMPProbe0 people like this

|Updated December 31, 2012 by MunirahLebaiLutfi|Tags: NonePage Actions ▼

Please click on link below to download the pdf file:

Steps to Forward System Director Events to Tivoli EiF & SNMP Probe.

Comments

1-1 of 1

PreviousNext

champye commented on January 22, 2014 Permalink

Hi very interesting document, but do you know how we can get theexhaustive list of alerts generated by the FSM, or at least the format ofAlerts.

Show


Previous

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Installing and Configuring > Huawei T2000 probe Failover- How it works and what to configure

Huawei T2000 probe Failover -How it works and what toconfigure0 people like this

|Updated December 31, 2012 by Mahyuddin|Tags: NonePage Actions ▼

The description in official Huawei T2000 probe reference guide for Failoverfeature is quite lengthy and might lead to different interpretation base onwho/how people read it. Below is the short version of it:-

Properties require for Failover:-

Retry set to "true"1. EnableFailover set to "true"2. For Primary EMS connection, configure either:-

IORFile, orORBInitialHost and ORBInitialPort, orNamingContextIORFile

3.

For Secondary EMS connection, configure either:-SecondaryIORFile, orSecondaryORBInitialHost and SecondaryORBInitialPort, orSecondaryNamingContextIORFile

4.

How the Failover works:-

At start up, probe will try to connect to Primary EMS first following thissequence base on which one found configured first:-

IORFileORBInitialHost and ORBInitialPortNamingContextIORFile

1.

If above fail, and Retry set to "true" and EnableFailover set "true",probe will wait (sleep) for "ServerSwitchingTime" before retry with theSecondary EMS following this sequence base on which one foundconfigured first:-

SecondaryIORFile

2.

SecondaryORBInitialHost and SecondaryORBInitialPortSecondaryNamingContextIORFile

If #2 fail, probe will retry with #1 and continue the flip-flop until thereis successful connection.

3.

Abbreviations:

EMS: Event Management SystemIOR: Interoperable Object ReferenceORB: Object Request Broker

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Installing and Configuring > How to integrate Probe ExtensionPackage with the Internet of Things using IBM Node-RED via WebSocket

How to integrate Probe Extension Package with the Internet ofThings using IBM Node-RED via WebSocket0 people like this

|Updated December 1, 2015 by HongYong|Tags: NonePage Actions ▼

Probe Extension Package integrates with the Internet of Things using IBM Node-RED

The Probe Extension Package uses Node-RED to integrate IBM Netcool/OMNIbus with the Internet of Things. It provides two Node-RED nodes that allowyou to send events from any data source to any IBM probe that supports the event factory facility. For example, you can configure a Netcool/OMNIbusSocket Probe or a Netcool/OMNIbus Generic Log File Probe to run in passive mode listening to incoming HTTP requests from Node-RED. The details ofconfiguring these probes are documented in reference guide of Probe Extension Package. Besides, Message Bus probe that supports WebSocket transportcan be configured to listen to events from Node-RED nodes. The steps are described as below.

RequirementsThe integration with the Internet of Things has the following requirements:

Netcool/OMNIbus V7.4 or later.1. Node.js installed and configured to use the node: http://nodejs.org2. Node-RED installed and configured to use the node: http://nodered.org3. Configure Message Bus Probe to use WebSocket transport and details in Message Bus Probe reference guide.4.

Configuring the probeTo configure the integration Internet of Things, follow these steps:

Ensure that you have followed the instructions in “Extracting the Probe Extension Package and configuring a probe to use the additional rules”1. Ensure that the prerequisite software is installed and running.2. Copy the nodered.props file and nodered.rules file from the $PROBE_EXT/iot/nodered directory to the following directory: $OMNIHOME/probes/arch/. The nodered.props file is intended as reference to help you to edit the probe properties file.

3.

Set the RulesFile property of the properties file of the probe that you will be using to listen to requests from the Node-RED to the following path:$OMNIHOME/probes/arch/nodered.rules

4.

Refer to Probe Extension Package reference guide for mapping Netcool/OMNIbus fields in Node-RED5. Start Node-RED.6. Start the probe.7.

Optional, import the following example flow to setup websocket in Node-RED.

[{"id":"90fad746.0db78","type":"websocket-listener","path":"testing_ext","wholemsg":"false"},{"id":"fe1e8418.4129a","type":"websocket in","name":"wsin","server":"90fad746.0db78","client":"","x":276,"y":175,"z":"5bd74e46.2586a8","wires":[["2f1c4e43.2a6e02"]]},{"id":"676d6636.f924f","type":"websocket out","name":"ws out","server":"90fad746.0db78","client":"","x":874,"y":334,"z":"5bd74e46.2586a8","wires":[]},{"id":"2f1c4e43.2a6e02","type":"debug","name":"","active":true,"console":"false","complete":"payload","x":736,"y":169,"z":"5bd74e46.2586a8","wires":[]},{"id":"c020811a.fca6c8","type":"inject","name":"Inject Event","topic":"","payload":"{\"field1\": \"MyNode\",\"field2\":\"MyManager\",\"field3\":\"testObject123\",\"field4\":\"Test Alarm Summary\",\"field5\":true}","payloadType":"string","repeat":"","crontab":"","once":false,"x":169,"y":337,"z":"5bd74e46.2586a8","wires":[["d4264be4.383398"]]},{"id":"d0281ae2.192a38","type":"event field map","name":"Event Field Map","severitymap2":"field5","severityrules":[{"t":"eq","sev":"5","v":"bad"},{"t":"eq","sev":"0","v":"OK"},{"t":"true","sev":"3"},{"t":"false","sev":"2"},{"t":"else","sev":"1"}],"node":"{{field1}}","manager":"{{field2}}","alertgroup":"alertgroup","alertkey":"{{field3}}","summary":"{{field4}}","optfields":[{"t":"NodeAlias","v":"NodeFriendlyName"}],"outputs":1,"x":608,"y":336,"z":"5bd74e46.2586a8","wires":[["676d6636.f924f"]]},{"id":"d4264be4.383398","type":"json","name":"","x":380,"y":337,"z":"5bd74e46.2586a8","wires":[["d0281ae2.192a38"]]},{"id":"9cee05de.162d5","type":"inject","name":"Inject Clear","topic":"","payload":"{\"field1\": \"MyNode\",\"field2\":\"MyManager\",\"field3\":\"testObject123\",\"field4\":\"Test Alarm Summary\",\"field5\":\"OK\"}","payloadType":"string","repeat":"","crontab":"","once":false,"x":171,"y":412,"z":"5bd74e46.2586a8","wires":[["d4264be4.383398"]]}]

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Administering > V7.4 FP1, Setting up Netcool OMNIbusWeb GUI integration features in Jazz for Service Management

V7.4 FP1, Setting up NetcoolOMNIbus Web GUI integrationfeatures in Jazz for ServiceManagement0 people like this

|Updated March 10, 2014 by BryanHobbert|Tags:

dash,jazzsm,netcool/omnibus

Page Actions ▼

This document provides a technical introduction to creating dashboards thatvisualize data from the OMNIbus Web GUI navigational model on the IBMDashboard Application Services Hub (DASH). DASH is deployed in Jazz forService Management. This document shows how OMNIbus Web GUI hasexposed its navigational model data via UI data providers.

To open the document, click the Attachments tab below.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Administering > V7.4 FP2, Setting up Netcool OMNIbusWeb GUI integration features in Jazz for Service Management

V7.4 FP2, Setting up NetcoolOMNIbus Web GUI integrationfeatures in Jazz for ServiceManagement0 people like this

|Updated March 10, 2014 by BryanHobbert|Tags: NonePage Actions ▼

This document provides a technical introduction to creating dashboards thatvisualize data from the OMNIbus Web GUI navigational model on the IBMDashboard Application Services Hub (DASH). DASH is deployed in Jazz forService Management. This document shows how OMNIbus Web GUI hasexposed its navigational model data via UI data providers.

To open the document, click the Attachments tab below.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Administering

Administering0 people like this


administering,best-practices

Page Actions ▼

The following topics are available on this page:

Tivoli Common Reporting Event Reports for OMNIbus

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > How-to documentation > Performance and Tuning > How to increaseperformance for old socket type probes reading events from multiple sources

How to increase performance for old socket type probesreading events from multiple sources0 people like this


ibm-blog-l3

Page Actions ▼

Issue:

Events delayed from reaching ObjectServer on event retrieval from multiple host configuration.

Problem:

Most of old socket type probes (e.g: nco_t_dms) applied sequential design instead of multi-head (multi-threaded) on event retrieval andprocessing.

When probe is configured to retrieve events from multiple hosts, what probe do is it sequentially go through each of the hosts and tryto read an event from the opened connection until success or ReadTimeout.

It will be quick if there is event(s) waiting on the socket waiting to get picked up. However if there is no event, probe will wait till itsReadTimeout before move to next host.

This round-robin approach cause huge delay in uneven situation where some host produce more frequent events, while other producelesser events. Example of illustration if Figure 1 shows that with all events come at the same time the last events from Host D will getdelayed for 160 seconds!.

Solution:

Run multiple instances of probe. Each probe only connecting to 1 host and process events from single host. Any delay or behavior ofthe events from one host will not impact other host.

Table 1 below list the properties need to be unique among the instances. This example is base on nco_t_dms probe. Other probe mighthave other properties set. But you should get the idea on what need to be unique.

Note that probe need to run with -name command line option so that prop can pickup the specific instance properties. Otherwise runprobe with -propsfile command line option for probe to pickup the renamed properties file.

Properties Instance 1 Instance 2 Instance 3 Instance 4

Name* dms_1 dms_2 dms_3 dms_4

MessageLog* $OMNIHOME/log/dms_1.log $OMNIHOME/log/dms_2.log $OMNIHOME/log/dms_3.log $OMNIHOME/log/dms_4.log

PropsFile*$OMNIHOME/tsm/<arch>/dms_1.props

$OMNIHOME/tsm/<arch>/dms_2.props



Host/HostsFile <Host A> <Host B> <Host C> <Host D>

Table 1: List of minimum properties need to made unique on multiple instances run.

* : There is no need to configure MessageLog and PropsFile properties when probe run with -name <instance_name> configured, andMessageLog and PropsFile left as default (hash out). The probe will automatically use <instance_name> name for the log, propertiesand rules file.

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > How-todocumentation > Performance and Tuning

Performance and Tuning0 people like this


best-practices,performance-and-tuning

Page Actions ▼

This page includes performance and tuning topics for Tivoli NetcoolOMNIbus.

Perform JOIN operation on OMNIbus ObjectServer Tables using NetcoolImpact

How to increase performance for old socket type probes reading eventsfrom multiple sources

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > 3rd Party System Studies > Mappability of Trapgen data type to CASpectrum v9 value formatter on OneClick Event Tab

Mappability of Trapgen data type to CA Spectrum v9 valueformatter on OneClick Event Tab0 people like this

|Updated March 13, 2013 by SeanSoon|Tags:

ibm-blog-l3

Page Actions ▼

The mappability study was conducted by running Trapgen tool to send SNMP traps to CA spectrum system, and recording the viabilityof each basic SNMP variable type to be mapped to value formatter in OneClick event tab, in other words, this is a study on whether anSNMP variable type can be printed on GUI screen using which formatters.

'Yes' denotes the formatter usage is promising for the variable type, but that does not necessarily means the format is always suitablefor the variable type, considering value range limit and readability that can be affected by the formatter.

'No' is simply not possible whatsoever.

Trapgenvs.

OneClickEvent Tab

Integer{I #}

UnsignedInteger{U #}

UnsignedLong{L #}

Boolean{B #}

Double{R #}

Text String{S #}

Octet String{O #}

TaggedOctetString{X #}

TaggedOctetString{x #}

Object ID{o #}

STRING No No No No No Yes Yes Yes Yes YesCOUNTER Yes Yes Yes No No Yes No No No NoGAUGE Yes Yes Yes No No Yes No No No NoINTEGER Yes Yes Yes No No Yes No No No NoADDRESS No No No No No Yes Yes Yes Yes YesOID No No No No No Yes Yes Yes Yes YesTIMETICK Yes Yes Yes No No Yes No No No No

HEX No No No No No

Yes, butsometimes

garbage if thehex value is

non-printableASCII Yes Yes Yes Yes

Trapgenvs.

OneClickEvent Tab

DateTime{D #}

DateTime{G #}

DateTime{K #}

IP Address{A #}

HexValue{H #}

Event Table(MIB table

attr){T <evt tablefilename> #}

Event Table(OID table)

{Y <evt tablefilename> #}

Event Table(Integer bit table

){Z <evt tablefilename> #}

STRING No No Yes Yes NoCOUNTER Yes Yes No No YesGAUGE Yes Yes No No YesINTEGER Yes Yes No No YesADDRESS No No No No NoOID No No No No NoTIMETICK Yes Yes No No Yes

HEX No No

Cause Java Error

formatting event: java.lang.

ArrayIndexOutOfBoundException:4 Yes No

Note: Gray cells are not yet studied, you are welcome to try them out and report the result here.

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > 3rd PartySystem Studies

3rd Party System Studies0 people like this

|Updated March 13, 2013 by SeanSoon|Tags: NonePage Actions ▼

This page is dedicated to the study of 3rd party systems that may be (or maynot be) currently integrating with Omnibus probes or gateways.

If you want to share with customers or vendors the information listed here,

please do it with utmost discretion. Light

CA Spectrum

Mappability of Trapgen data type to CA Spectrum v9 value formatter onOneClick Event Tab

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Links todocumentation

Links to documentation0 people like this

|Updated May 31, 2013 by Keith Jeremy Posner|Tags:

related-links

Page Actions ▼

This page contains links to related topics on Tivoli Netcool/OMNIbus:

Tivoli Documentation Central

Tivoli Netcool/OMNIbus official product documentation

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive

Archive0 people like this

|Updated November 1, 2012 by CraigWigley|Tags: NonePage Actions ▼

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive > Lostand found > TBSM 6.1 Sizing Guide

TBSM 6.1 Sizing Guide0 people like this

|Updated June 27, 2012 by katie|Tags: NonePage Actions ▼

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive > Lost and found > How to Determine Which Version ofMicrosoft .NET Framework Installed

How to Determine Which Version of Microsoft .NETFramework Installed0 people like this

|Updated October 5, 2012 by fadhli|Tags:

microsoft,probe-integrations,wineventlog

Page Actions ▼

Probes with dependency on Microsoft .Net Framework may have a minimum level of .Net version to run. To check what version of .Net installed on the

machine, follow steps below:

1) Run command "regedit" from console to open Registry Editor

2) Look for HKEY_LOCAL_MACHINE\Microsoft\NET Framework Setup\NDP

3) All installed .NET Framework versions are listed under NDP drop-down list

Example:

Screenshot from my workstation (I have .Net v3.5 SP1 installed):

Reference for each Microsoft .Net version numbers: http://blogs.msdn.com/b/astebner/archive/2005/07/12/438245.aspx

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive > Lostand found

Lost and found0 people like this


This section contains pages that have yet to be categorised.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Creating SMC Email Signatures

Creating SMC Email Signatures0 people like this

|Updated June 30, 2012 by CraigWigley|Tags: NonePage Actions ▼

Further to the previous blog entry on email signatures it has come to lightthat different user profiles may require different usage of SMC HTMLsignatures. Here I explore some options with sizes to allow users to selectoptions that they feel more applicable to them. I will be in touch with theDeveloperWorks team to see if we can reduce the footprint of the imageryfurther (we are using dynamic links into their icons).

Textual SMC URL

- 2 KBytes smcsig1.html

<hr>Craig Wigley, Team Lead, Tivoli Netcool Best Practices IBM United Kingdom Ltd | <a href=mailto:[email protected]><color=blue>[email protected]</a><color=black> | <a href="http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Tivoli Solutions Engineering -Best Practices/page/Welcome"><color=blue>Tivoli Netcool Best Practices Wiki</a> <a href="http://www.ibm.com/developerworks/servicemanagement/nsa"><color=blue>Service Management Connect -Network & Service Assurance</a><hr> 

Single SMC community icon

- 6 KBytes (1 KByte basic + 5 KBytes for community icon) smcsig2.html

<hr>Craig Wigley, Team Lead, Tivoli Netcool Best Practices IBM United Kingdom Ltd | <a href=mailto:[email protected]><color=blue>[email protected]</a><color=black> | <a href="http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Tivoli Solutions Engineering -Best Practices/page/Welcome"><color=blue>Tivoli Netcool Best Practices Wiki</a><a href=http://www.ibm.com/developerworks/servicemanagement/nsa/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icons_network_smex.png" width="24" height="24"></a><hr>

Multiple SMC community icons

- 16 KBytes (1 KByte basic + 3 x 5 KByte community icons) smcsig3.html

<hr>Craig Wigley, Team Lead, Tivoli Netcool Best Practices IBM United Kingdom Ltd | <a href=mailto:[email protected]><color=blue>[email protected]</a><color=black> | <a href="http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Tivoli Solutions Engineering -Best Practices/page/Welcome"><color=blue>Tivoli Netcool Best Practices Wiki</a><a href=http://www.ibm.com/developerworks/servicemanagement/nsa/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icons_network_smex.png" width="24" height="24"></a><a href=http://www.ibm.com/developerworks/servicemanagement/bsm/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icon_bsm_smex.png" width="24" height="24"></a><a href=http://www.ibm.com/developerworks/servicemanagement/cvm/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icon_cloud_smex.png" width="24" height="24"></a><hr> 

SMC banner and single community icon

- 26 KBytes (1 KByte basic + 20 KBytes SMC banner + 5 KBytes forcommunity icon) smcsig5.html

<hr>Craig Wigley, Team Lead, Tivoli Netcool Best Practices IBM United Kingdom Ltd | <a href=mailto:[email protected]><color=blue>[email protected]</a><color=black> | <a href="http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Tivoli Solutions Engineering -Best Practices/page/Welcome"><color=blue>Tivoli Netcool Best Practices Wiki</a> <a href="http://www.ibm.com/developerworks/servicemanagement"><img src="https://www.ibm.com/developerworks/mydeveloperworks/blogs/7d5ebce8-2dd8-449c-a58e-4676134e3eb8/resource/530x125.jpg" width="560" height="120"></img></a> <a href=http://www.ibm.com/developerworks/servicemanagement/nsa/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icons_network_smex.png" width="24" height="24"></a><hr> 

SMC banner and multiple community icons

- 36 KBytes (1 KByte basic + 20 KBytes SMC banner + 3 x 5 KBytecommunity icons) smcsig6.html

<hr>Craig Wigley, Team Lead, Tivoli Netcool Best Practices IBM United Kingdom Ltd | <a href=mailto:[email protected]><color=blue>[email protected]</a><color=black> | <a href="http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Tivoli Solutions Engineering -Best Practices/page/Welcome"><color=blue>Tivoli Netcool Best Practices Wiki</a> <a href="http://www.ibm.com/developerworks/servicemanagement"><img src="https://www.ibm.com/developerworks/mydeveloperworks/blogs/7d5ebce8-2dd8-449c-a58e-4676134e3eb8/resource/530x125.jpg" width="560" height="120"></img></a> <a href=http://www.ibm.com/developerworks/servicemanagement/nsa/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icons_network_smex.png" width="24" height="24"></a><a href=http://www.ibm.com/developerworks/servicemanagement/bsm/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icon_bsm_smex.png" width="24" height="24"></a><a href=http://www.ibm.com/developerworks/servicemanagement/cvm/index.html><img src="https://www.ibm.com/developerworks/servicemanagement/i/icon_cloud_smex.png" width="24" height="24"></a><hr> 

Comments

You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Copyright and Notices

Copyright and Notices0 people like this


best-practices,copyright-and-notices,omnibus

Page Actions ▼

© Copyright IBM Corporation 2008, 2009

IBM United States of America

Produced in the United States of America

All Rights Reserved

IBM, the IBM logo, and ibm.com, DB2 and Tivoli are trademarks orregistered trademarks of International Business Machines Corporation in theUnited States, other countries, or both. If these and other IBM trademarkedterms are marked on their first occurrence in this information with atrademark symbol (® or ™), these symbols indicate U.S. registered orcommon law trademarks owned by IBM at the time this information waspublished. Such trademarks may also be registered or common lawtrademarks in other countries. A current list of IBM trademarks is availableon the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks of SunMicrosystems, Inc. in the United States, other countries or both.

Other company, product and service names may be trademarks or servicemarks of others.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPAPER "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may notapply to you.

Information in this paper as to the availability of products (including portlets)was believed accurate as of the time of publication. IBMcannot guarantee that identified products (including portlets) will continue tobe made available by their suppliers.

This information could include technical inaccuracies or typographicalerrors. Changes may be made periodically to the information herein;these changes may be incorporated in subsequent versions of the paper. IBMmay make improvements and/or changes in the product(s) and/or theprogram(s) described in this paper at any time without notice.

Any references in this document to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsementof those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may have patents or pending patent applications covering subjectmatter described in this document. The furnishing of this documentdoes not give you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of LicensingIBM Corporation4205 South Miami BoulevardResearch Triangle Park, NC 27709 U.S.A.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive > Tivoli Netcool OMNIbus Probe Integrations - old

Tivoli Netcool OMNIbus Probe Integrations - old2 people like this

2|Updated June 25, 2015 by johnstlee|Tags:

integration-scenarios,omnibus,probe-integrations

Page Actions ▼

Please refer to Tivoli Netcool/OMNIbus Integrations - Probes on IBM Knowledge Center for the list of supported probes.

Please also refer to the NcKL and OPAL peer pages for compatible rules files.If an IBM developed probe is not available, an integration may be achieved either by using one of the universal probes and/or formatting the events into a format compatible with one of our universal probes. You willneed to identify what interfaces are supported by Stratus for northbound alerting .e.g. SNMP, Syslog, Logfile, ASCII Pipe or telnet . This information is usually available from the product vendor. If there is a universalNetcool probe that can read events from the identified interface, then you may just need to produce a rules file specific to the managed system.

Universal Probes

Interface Type Probe NameProbe binary

name

SNMP traps SNMP probe nco_p_mttrapd

Syslog files Syslog Probe nco_p_syslog

Log file - ASCII Generic Log File Probe nco_p_glf

TCP - ASCIIMulti-headed SocketProbe

nco_p_socket

Pipe - ASCII FIFO probe nco_p_fifo

ODBC complianttable

Probe for ODBC nco_p_odbc

EIF Tivoli EIF Probe nco_p_eif

XML file /XML OverJMS

MessageBus Probe nco_p_xml

POP3 Email Email Probe nco_p_email

Oracle tables Probe for Oracle nco_p_oracle

Console Output -ASCII

Standard/Stdin probe nco_p_stdin

Console Output -ASCII

Exec Probe nco_p_exec

Note:~~~~~~~**1.Some probes are only available on specific platforms due to technical limitations . Always check with Product Management on availability on other platforms2. Pricing Metrics are available from Tivoli product license information3. Probes are version agnostic with the OMNIbus Objectserver.3. Probes need a base installation of OMNIbus to function. A probe will only be supported on a specific platform , only if that version of the OS, is supported by the underlying version of OMNIbus.Please refer to the IBM® Software Product Compatibility Reports website for platforms supported by Netcool/OMNIbus versions.

Other Probes

Some of the integrations listed below may have been deprecated and is no longer supported. Please refer to the list on IBM Knowledge Center.

Probe Name Target Systems Binary NamePlatformsSupported

Description

Alcatel DSCDex Alcatel DSC DEX Voice Switches nco_t_dscdexSolaris, HP-UX,AIX, Linux

The TSM for Alcatel DSC DEX acquires event data from the Alcatel DSC DEX range ofvoice switches by connecting to a Alcatel DSC DEX system and intercepting the eventstream. The messages on the event stream are read, parsed into Netcool/OMNIbusalerts, and forwarded to the ObjectServer.

Avaya Definity G3 Definity G3 Version 9 nco_t_definity_g3Solaris, HP-UX,AIX, Linux

The Avaya Definity G3 system monitors the functioning of Private Branch Exchanges(PBXs) used to connect private and public telephone networks. The TSM for AvayaDefinity G3 is a multi-headed TSM that can connect to either a single device or tomultiple devices.

Lucent ECP Lucent ECP release 29 nco_p_lucent_ecpSolaris, HP-UX,AIX, Linux

Lucent Executive Cellular Processor (ECP) is a multi-service switching system. It formsa part of the Lucent 7 R/E Networks architecture which provides packet and voicenetwork functions.The Probe for Lucent ECP acquires event data from the Lucent ECPswitch. It connects to the system using TCP/IP.

"Alcatel-Lucent 5ESS " Lucent 5e r15 nco_p_5essSolaris, HP-UX,AIX, Linux

Lucent 5ESS is a multi-service switching system. It forms a part of theLucent 7 R/E Networks architecture which provides packet and voicenetwork functionality.5ESS switch output messages are generated either inresponse to input messages, or to inform support personnel of systemconditions or automatic operations that have been performed by the system.Examples of the uses of information given in output messages includelocating trouble, reporting subsystem status, or supplying information onaudit results.

The Probe for Lucent 5ESS acquires event data by from the Lucent 5ESSswitch. It connects to the system using TCP/IP.

Lucent ITM-SCLucent ITM-SC 10.3 using the G2Protocol/ Optical EMS

nco_p_lucent_g2itm_scSolaris, HP-UX,AIX, Linux

Lucent G2 is a protocol common to Lucent management solutions. It is usedby the Lucent TIM interface to collect data from the Lucent IntegratedTransport Management - Network Manager (ITM-NM). The Probe forLucent ITM-NM /OMS collects data from the Lucent TIM interface.

The Lucent G2 ITM/NM probe can also collect data from the LucentIntegrated Transport Management - Subnetwork Controller (ITM-SC).

"Alcatel-Lucent 1000E10/OCB-283 "

Alcatel 1000 E10/OCB-283 nco_p_alcatel_ocb283Solaris, HP-UX,AIX, Linux

The Alcatel OCB-283 is a network element manager that operates real-timeservers and Alcatel switches. It collects data from network elements andforwards it to applications, enables basic remote access to networkelements, and manages data security and integrity.

"Alcatel-Lucent ITM-NM/OMS "

OMS 3.0 and above nco_p_lucent_g2itm_nmSolaris, HP-UX,AIX, Linux

Lucent G2 is a protocol common to Lucent management solutions. It is usedby the Lucent TIM interface to collect data from the Lucent IntegratedTransport Management - Network Manager (ITM-NM). The Probe forLucent ITM-NM /OMS collects data from the Lucent TIM interface.

The Lucent G2 ITM/NM probe can also collect data from the LucentIntegrated Transport Management - Subnetwork Controller (ITM-SC).

"Lucent NFM " Lucent NBA Server nco_p_lucent_nfmSolaris, HP-UX,AIX, Linux

The Lucent Network Fault Management (NFM) system is an elementmanager for the Lucent Surepay components MAS, eMS, and RMS. Thesystem collects and processes alarm messages from these devices and thenforwards them to the Probe for Lucent NFM . The probe interfaces with theLucent NFM system using the Northbound Application (NBA) server of theNFM system.

"Alcatel-Lucent OS-OS/IOO "

IOO 5.0- 5.4 , 9.0 and 9.1 nco_p_alcatel_ososSolaris, HP-UX,AIX, Linux,Zlinux

Alcatel Os-Os Probe plugs onto Alcatel's API. This module is non-standard onthe 1353 NMS and involves a cost. Note :1353SH is only available on HPUX.The Netcool/OMNNIbus OSOS Probe only supports the AVA interface, notthe CSV option. Alcatel's 1353SH 3.1 manage: 1641SM, 1641SMC, 1651SM,1661SMC, 1664SM, 1654SL, 1664SL, 1610OA, 1664OA, 9600LH, 9600UH,9600LM, 9600UM , 1350 OMS.

"Alcatel-Lucent 5620SAM "

SAM 4.0 , 5.0 , 6.0, 6.1, 7.0,8.0,9.0 nco_p_alcatel_5620_samSolaris, HP-UX,AIX, Linux,Windows

The Alcatel 5620 Service Area Manager (SAM) is a network managementsystem that is used to manage network nodes. Distributed Alcatel 5620 SAMelements are monitored by the Alcatel 5620 SAM database using GUI andnetwork management components through a Java-based application. TheProbe for Alcatel 5620 SAM acquires data from Alcatel 5620 SAM using aJava Messaging System (JMS).Elements managed by the SAM are :

> Alcatel 7750 Service Router (SR)Releases 2.1, 3.0 and 4.0> Alcatel 7710 Service Router (SR)Release 3.0> Alcatel 7450 Ethernet Service Switch(ESS) Releases 2.0, 3.0 and 4.0> Alcatel 7250 Service Access Switch(SAS) Releases 1.0 and 2.0> Telco T5C 24G, 24GT, 24T, 24F and48T variants running BiNOS 6.3> Alcatel Omnistack 6200 and the AlcatelOmniSwitch 6850"

Alcatel-Lucent SAM(CORBA)

Alcatel-Lucent 5620 ServiceAware Manager (SAM) versionR8.0

nco_p_alcatel_5620_sam_3gpp_v8Solaris, HP-UX,AIX, Linux,Zlinux

The Probe for Alcatel-Lucent 5620 SAM 3GPP v8 collects alarms fromAlcatel-Lucent 5620 SAM using a 3rd Generation Partnership Project (3GPP)Common Object Request Broker Architecture (CORBA) interface.

The CORBA probe manages the eNodeB , while the JMS probe managesevents from the MME.

"Alcatel-Lucent 5620Logfile "

4.0 and 4.1 nco_p_alcatel_5620_logfileSolaris, HP-UX,AIX, Linux

The Probe for Alcatel 5620 Logfile was originally called the Probe forNewbridge 46020. This probe is no longer supported ; IBM recommend thatyou use the Probe for Alcatel 5620 NM CORBA to interface with Alcatel5620 NM.

"Alcatel-Lucent 5529OAD "

Alcatel 5529 OAD R4.0, 5.0, 5.1.1,6.0 and 6.0.1

nco_p_alcatel_5529_oadSolaris, HP-UX,AIX, Linux,Windows

"Alcatel-LucentNaviscore "

Lucent NaviScore 9.1 nco_p_lucent_naviscore_tmf814 Solaris, HP-UX

Lucent NavisCore is an element management software that provides acentralized service and network management system to control Lucent'smultiservice switching product functions.

The Probe for Lucent NaviScore 9.1 acquires data from the LucentNaviScore 9.1 software using a Common Object Request BrokerArchitecture (CORBA) interface.

"Alcatel-Lucent OMC-R(3GPP) "

Evolium A1353UR OMC-R Version 3 nco_p_alcatel_omcr_3gpp Solaris, HP-UX

The Alcatel-Lucent Evolium (TM) 1353 UMTS OMC-R performs networksurveillance, quality of service monitoring and radio networkplanning/optimization for the UTRAN part of UMTS mobile networks. Thissolution is based on 3GPP standards, RNO (Radio Network Optimizer)embedded in OMC-R , Ready for UMTS evolution: HSDPA, HSUPA...

The Alcatel OMC-R (Operation and Maintenance Center-Radio) systemmanages radio devices. The Alcatel OMC-R probe collects alarms from anAlcatel OMC-R management system using a 3rd Generation PartnershipProject (3GPP) Common Object Request Broker Architecture (CORBA)interface.

"Alcatel-Lucent 5620NM CORBA "

Alcatel 5620 NM version 4.1, 5.0, 5.1,5.2, 5.3, 6.1, 6.2, 6.3, 7.0, 8.0 and 9.0

nco_p_alcatel_5620_corba Solaris, HP-UX

"The Alcatel 5620 Network Manager is a network management system that providesaccess to network performance, fault management, diagnostic, and accounting data. ACORBA interface provides access to the network data managed by the Alcatel 5620Network Manager through an object-oriented management information base. 5620 NMsupports new Ethernet and IPapplications based on the Alcatel 7670 Routing SwitchPlatform (RSP) Release 3.0, the Alcatel 7750 Service Router (SR) Release 2.0, andtheAlcatel 7450 Ethernet Service Switch (ESS) Release 1.0."

"Alcatel-Lucent OMC-R(Q3 Interface) " for9153 OMCR

1353 RA OMCR / 9153 OMCR(3G)version B62, B9, B10 and B11

nco_p_alcatel_omcr1353ra_b62 Solaris

"The Alcatel-Lucent Evolium (TM) 1353/9153 Operation & Maintenance Center forRadio provides Network Element (NE) management for Alcatel-Lucent BSS voice anddata services, including GPRS and EDGE.The Probe for Alcatel OMC-R (Q3) allowsyou to retrieve alarms from the Alcatel OMC-R device via a Q3 interface."

Alcatel-Lucent XMC1300

Alcatel-Lucent 1330 XMC nco_p_alcatel_xmc_corbaSolaris, HP-UX,AIX, Linux

The Alcatel-Lucent 1300 Cross-Domain Management Center (XMC) is an elementmanagement system (EMS) that provides several standard interfaces for operationssupport, one of which is the 3rd Generation Partnership Project Release 6 (3GPP R6)specification.

The Probe for Alcatel-Lucent 1300 XMC (CORBA) acquires events from the Alcatel-Lucent 1300 XMC using a Common Object Request Broker Architecture (CORBA)3GPP interface. The probe connects to the CORBA interface using an InteroperableObject Reference (IOR) file.

HTTP Server Error LogAny HTTP server with standard errorlog (for example, Netscape EnterpriseServer or Apache Server)

nco_p_httperrlogSolaris, HP-UX,AIX, Linux

The HTTP Server Error Log is used by the majority of Web servers to log all errors thatoccur on the Web server. The log file contains a separate line for each error. The Probefor HTTP Server Error Log reads the error messages stored in this log file.

Heartbeat ProbeNone. Stand-alone probe whichgenerates heartbeat events.

nco_p_heartbeat

Solaris, HP-UX,HPUXINtegrity, AIX,Linux,ZLinux,

The Heartbeat Probe does not gather data from any third party system, but generates astandard event at a predetermined interval, for a predetermined amount of time. It isused to check that a remote site can be accessed and also as a test probe when eventsare required to be generated.

Ericsson MarconiSystemX

Marconi System X nco_t_systemxSolaris, HP-UX,AIX, Linux,

The Marconi Communications range of System X switches provide Public Networkswitching for a wide range of network operators. The TSM for Marconi System Xhandles scheduled and unsolicited report types generated by the Marconi System Xswitch.

ECI Telematics Telematics INF management system nco_p_telematicsSolaris, HP-UX,AIX, Linux,

The ECI Telecom Data Networking/Internet Business Unit (formerly Telematics) provideswide area networking solutions designed for voice and data communications. Solutionsare provided for public and private network service providers. The Telematics INFmanagement system is used for management of Telematics X.25 and Frame Relayequipment.

The Probe for Telematics acquires data by connecting to the Telematics INFmanagement system and intercepting the console message stream.The Probe forTelematics connects directly into the INF management system through TCP/IP and thenacquires events in real time. It can connect to the Telematics INF management systemthrough telnet, tip, or rsh.

Alcatel-LucentWavestar SNMS

Lucent WaveStar SNMS EMS Version10

nco_p_lucent_snms Solaris

" Alcatel-Lucent SNMS is a network management system for the WaveStar productfamily. It provides Element Management Layer (EML) functions for many WaveStarproducts. These functions include configuration, fault, performance, and securitymanagement.The Probe for Alcatel-Lucent SNMS (CORBA) collects events from theWaveStar SNMS system using the G7 CORBA interface"

Alcatel-Lucent 9353Wireless ManagementSystem (9353WMS)/WNMS

OAM/WMS 6.0and UTRANUA07/OAM07

nco_p_alcatel_wnms Solaris,HP-UX

The Alcatel-Lucent 9353 Wireless Management System (9353 WMS) enables networkadministrators to manage Alcatel-Lucent's W-CDMA/HSPA access network equipmentand additionally, some ATM-based infrastructure equipment. This system is carrier-grade, is composed of wireless-aware specialized applications (for example the Alcatel-Lucent 9352 WPS and the Alcatel-Lucent 9359 NPO). The Probe for Alcatel-Lucent

9353 WMScollects alarms from an 9353 WMS management system using a 3rdGeneration Partnership Project (3GPP) Common Object Request Broker Architecture(CORBA) interface.

BMC Patrol Agent version 3.6, 3.7 and 3.8 nco_p_patrolSolaris, AIX,Linux, Windows

The probe for BMC Patrol connects directly to the BMC agents and acquires event datausing the same method as the BMC Patrol console using the Patrol API. The agentsgather Patrol events and forward them to the console and/or the probe for BMC Patrol.probe .

"Freshwater Sitescope " Sitescope website log files nco_p_sitescopeSolaris, HP-UX,AIX, Linux,Windows

The Probe for Sitescope reads daily log files produced by the Sitescope web sitemonitoring and reporting application. By default, the Sitescope application produces logfiles with names corresponding to the date.

CA Spectrum Spectrum 8.1 and 9.0 nco_p_spectrumSolaris, HP-UX,Linux

The SpectroSERVER acts as a network management server for the SpectrumEnterprise Manager. The Spectrum Enterprise Manager is an element manager thatuses the SpectroSERVER to manage CA Aprisma and third party devices. The Probefor CA Spectrum (CORBA) collects alarm information from the SpectroSERVER andsends them to Netcool/OMNIbus.

Castlerock SNMPC N/A nco_p_mttrapd N/A SNMPC supports SNMP for northbound event integration. Use SNMP probe

"Ciena On Center "ON-Center Network and ServiceManagement Suite 8.3.1

nco_p_ciena_oncenter Solaris, HP-UX

Ciena ON-Center Supports full Fault, Configuration, Accounting, Performance andSecurity (FCAPS) across the Ciena network element portfolio. The Probe for Ciena ON-Center collects events from the Ciena ON-Center Element Management System (EMS)CORBA interface.

Cisco WAN ManagerSNMP events from Cisco WANManager.

nco_p_rttrapd SolarisThe Cisco RTTrapd Info Mediator acquires data from the Cisco WAN Manager or CiscoCNS Notification Engine products.

"Cisco TransportManager -CTM(CORBA) "

Cisco CTM Release 6.0, 7.0 , 8.0 ,8.5and 9.0

nco_p_cisco_ctm_corbaSolaris, HP-UX,Linux

The Cisco Transport Manager (CTM) system is an optical transport domain manager. Ituses open interfaces to operations support systems (OSSs) using industry-standardprotocols. The Probe for Cisco CTM (CORBA) acquires data from the Cisco CTMsystem using a Common Object Request Broker Architecture (CORBA) interface.

"Oracle Probe " Oracle versions 8.1.7 to 10.0.1.2 nco_p_oracleSolaris, HP-UX,AIX, Linux,

"The Probe for Oracle extracts data from a table in an Oracle database and can be usedfor bespoke and mainstream element management systems that store event data inRDBMS tables.The probe works by logging into the database and monitoring the contents of a tabledefined by the probe properties. The probe automatically makes a copy of the table andcreates three triggers in the database. The triggers make a copy of each insert, update,and delete and pass the row into the copy of the probed table. The data is deleted fromthe copied table after it has been processed by the probe."

"ODBC Probe "Sybase, Informix, MySQL, DB2 andMicrosoft SQL Databases

nco_p_odbcSolaris, HP-UX,AIX, Linux,Windows

The Generic ODBC Probe acquires event data from any database table for which youhave installed an ODBC driver. The probe monitors a database table and creates anIBM Tivoli Netcool/OMNIbus alert for each row in the table.

"ECI/eNM " ECI eNM SDH Switch+D122 nco_p_eci_eNMSolaris, HP-UX,AIX, Linux

The (ECI Network Manager) eNM Management System monitors Synchronous DigitalHierarchy (SDH) equipment. ECI-SDH networks are supported in a service?orientednetwork management environment by the eNM. The system allows administrators tomonitor and control faults, performance and security, and to support networkconfigurations with end-to-end management capabilities. The Probe for ECI eNMsupports ECI devices that generate eci.dat log files containing events whose minimumlength is 100 characters. IBM does not maintain a list of compatible ECI devices.

"ECI Lightsoft CORBA " ECI Lightsoft EMS 2.1 , 3.x and 4.x nco_p_eci_lightsoft_tmf814 Solaris, HP-UX

ECI Lightsoft is a network management system that provides both element managementand network management functions for telecommunications networks. The Probe forECI Lightsoft (CORBA) acquires data from ECI Lightsoft using a Common ObjectRequest Broker Architecture (CORBA) interface.

"Ericsson AXE 10 " AXE10 Exchange nco_t_axe10Solaris, HP-UX,AIX, Linux

"The Ericsson AXE10 exchange is a digital switching system for public telephonenetworks. It serves both fixed and mobile services. The TSM retrieves events from theAXE10 Event stream via a terminal connection "

"Ericsson ACP 1000 " ACP 1000 nco_p_acp1000Solaris, HP-UX,AIX, Linux

The ACP1000 probe can connect to an ACP1000 switch through telnet, tip or rsh.TheACP1000 probe acquires event data at regular intervals from the device alarm bufferand the supervisory alarm buffer.

"Ericsson MD110 " Ericsson MD110 PABX nco_p_md110Solaris, HP-UX,AIX, Linux

"The Ericsson MD110 is a PABX device that is designed to provide cordlesscommunication for users in an office environment.The MD110 probe acquires event databy connecting to the Ericsson MD110 PABX switch and reading its event log. "

"Ericsson Xmate " Ericsson XMATE nco_p_xmateSolaris, HP-UX,AIX, Linux

"XMATE is an AXE10 switch manager. XMATE manages various types of eventsgenerated by the AXE 10 switch .The Probe for Ericsson Xmate reads directly from alog file that contains AXE10 events"

"Ericsson BNSI " Ericsson BNSI Interface nco_p_ericsson_BNSISolaris, HP-UX,AIX, Linux

"The Ericsson Basic Network Surveillance Interface (BNSI) is a protocol for forwardingalarm information from an alarm surveillance system . The Probe for Ericsson BNSIconnects to a single host on a specified port and reads alarms from the Ericsson BNSI"

"Ericsson 3GPP (OSS-RC/RANOS/CNOS) "

OSS-RC versions 2.x, 3.x, 4.x, 5.x6.x, 7.x , 8.x ,10.x and 11.x

nco_p_ericsson_oss_rc Solaris, HP-UX"The Ericsson Operation and Support System Radio and Core (OSS-RC) is an elementmanager for the Ericsson 3G core network. The Probe for Ericsson OSS-RC connectsto Ericsson OSS-RC RANOS, and CN-OSS using the standard CORBA interface"

Fujitsu Netsmart SNMP Network Integration Module available for download from OPAL.

Hewlett PackardOpenView NNM

NNM 6.x, NNM 7.x, NNM8 andNNM9i

nco_p_nnm, nco_p_nnm_ws ( forNNM8 and NNM9i)

Solaris, HP-UX,Linux, Windows

The Probe for HP NNM i-series version 8/9 subscribes to NNM for eventinformation and reports incidents to Netcool OMNIbus. The subscription andresynchronization events streams can be filtered and the probe can be configuredto subscribe to the XML event descriptions sent by the HP NNM API.

"OPCOM" N/A nco_p_opcomSolaris, HP-UX,AIX, Linux

The Operator Communications Facility (OPCOM) is a subsystem of VMS/OpenVMS ,which monitors the system and application events from a single console. The Probe forOPCOM logs onto the OPCOM system and reads the console messages.

Compaq Tandem HP Tandem NonStop systems nco_p_tandemSolaris, HP-UX,AIX, Linux

"The probe connects to the tandem machine on a specified port. Once it connects itperforms a chat in sequence to allow the probe to receive ems alarms. The effectivelyhardcoded commands detailed in the docs (the default EMS command was ""ems"") arenow removed and you can specify any login sequence you may like and the probe willparse the tandem alarms as and when they appear. So the customer can completelycustomise the way the probe connects and what commands( TACL Commands) it runsto read the output of. "

Hewlett Packard HPVantage PointOperations /OVO/OMU

HP VPO/OVO Versions 6.x, 7.x,8.xand 9.x

nco_p_vpo Solaris, HP-UX

NOTE : The Probe for HP OVO/OMU is only available through a services engagementPlease contact IBM Product Management for more information on implementation TheHP OpenView for Operations /VantagePoint Operations (VPO) is a software applicationthat provides central operations and event management. The Probe for HP OVOconsists of a central management server, which interacts with intelligent software agentsinstalled on the managed nodes. The HP Operations server receives events from logfiles, SNMP traps, MPE/iX consoles, the ITO message interface, and monitored objectssuch as disk space, swap space, and CPU utilization.

Samsung BSM Samsung Base Station Manager nco_p_samsung_bsm SolarisThe Probe for Samsung BSM acquires data from the Samsung Radio Access Network(RAN). It is based on the multiheaded socket probe template and connects to the targetdevice through a socket.

"Huawei T2000CORBA"

Huawei T2000 on iMAPV200R007C01 (for CORBA interface )

nco_p_huawei_T2000_corbaSolaris, HP-UX,Linux

"iManager T2000 is the Element Management System (EMS) across all opticalplatforms from Huawei including SONET, SDH, DWDM and OTN with a unified controlplane architecture.The Probe for Huawei T2000 (CORBA) gathers events from HuaweiT2000 using a Common Object Request Broker Architecture (CORBA) interface. TheT2000 probe is also supported against the CORBA interface for the Huawei U2000.Please use the Huawei U2000 probe to integrate with the MTOSI/XML interface of theU2000."

Huawei U2000 CORBAHuawei U2000 V1R1, Huawei U2000V1R2 (for CORBA interface ) )

nco_p_huawei_T2000_corbaSolaris, HP-UX,Linux

"iManager U2000 that is the integrated network management system (NMS) combinesall-IP and FMC, and manages carrier equipment and access equipment in a centralizedmanner.The Probe for Huawei U2000 (CORBA) gathers events from Huawei U2000using a Common Object Request Broker Architecture (CORBA) interface."

Huawei U2000 XMLHuawei U2000 V1R2( for XMLinterface)

nco_p_u2000Solaris, HP-UXPA-RISC, AIX,Linux, Windows

"iManager U2000 that is the integrated network management system (NMS) combinesall-IP and FMC, and manages carrier equipment and access equipment in a centralizedmanner.The Probe for Huawei U2000 (XML) gathers events from Huawei U2000 using aMTOSI/XML interface."

Huawei N2000 CORBA

Huawei N2000 on iMAP V200R003 orlater N2000UMS:V200R012C02B030

nco_p_huawei_N2000_corbaSolaris, HP-UX,Linux

"The Huawei N2000 system is a sub-network level management system that providesboth element management and network management functionality fortelecommunications networks. The Probe for Huawei N2000 (CORBA) acquires datafrom the Huawei N2000 system using a Common Object Request Broker Architecture

N2000DMS:V300R003

N2000BMS:V200R011C02

(CORBA) interface. "

Huawei M2000 CORBAHuawei M2000 (CORBA) V200R800 ,V2R9 and V2R10 for LTE

nco_p_huawei_M2000_corbaSolaris, HP-UX,Linux

"The iManager M2000 is a wireless network management system used to manageHuawei WCDMA, CDMA2000 and GSM mobile communication networks. iManagerM2000 is used for the operation and maintenance of subnets and can manage theaccess network, core network and other networking products separately or on a unifiedbasis. It manages Huawei's mobile network equipment for broadband and nextgeneration networks, such as?Msoftx3000 and BSC.The Probe for Huawei M2000(CORBA) collects alarms from the Huawei M2000 (CORBA) managementsystem using a 3rd Generation Partnership Project (3GPP) Common Object RequestBroker Architecture (CORBA) interface"

"Tivoli EIF" N/A nco_p_tivoli_eif

Solaris, HP-UX,HP-UXIntegrity AIX,Linux, ZLinuxWindows

A range of Tivoli® products generates Event Integration Facility (EIF) messages. TheProbe for Tivoli EIF can receive EIF events sent from any of these Tivoli devices andsends them to the ObjectServer.

"IBM CEI /SOA"Common Event Infrastructure (CEI)running on WebSphere ApplicationServer (WAS) version 6.0 or 6.1

nco_p_tivoli_ceiSolaris, Linux,Windows

he Tivoli Common Event Infrastructure (CEI) forms part of the WebSphere ApplicationServer (WAS). CEI is based on the Common Base Event (CBE) specification andprovides a set of APIs and infrastructure for the creation, transmission, persistence, anddistribution of network CBE formatted events. The Probe for Tivoli Common EventInfrastructure enables CEI messages to be sent to the Netcool/OMNIbus ObjectServer.

"Kodiak EMS CORBA" Kodiak EMS (CORBA) version 5.4 nco_p_kodiak_ems_corba Solaris, HP-UX

The Probe for Kodiak EMS (CORBA) manages network entities generated by theKodiak Real-Time Exchange (RTX) to provide various voice network functions. TheProbe for Kodiak EMS (CORBA) acquires data from the Kodiak EMS using a CORBAinterface.

"Fujitsu ICS CORBA " N/A nco_p_fujitsu_ics Solaris No Longer Supported due to full product discontinuation by vendor

"Ericsson-MarconiServiceOn Access"

Marconi ServiceOn Access version6.1

nco_p_marconi_serviceon_accessSolaris, HP-UX,AIX, Linux

"The Marconi ServiceOn Access network management system is used for planning,operating, and supporting networks. It is designed primarily to monitor ServiceOnAccess switches.The Probe for Marconi ServiceOn Access connects to MarconiServiceOn Access using a telnet session to a port."

"Ericsson-MarconiEMOS"

Marconi ServiceOn EM-OS version 9. nco_p_emosSolaris, HP-UX,AIX, Linux

"The Marconi Communications ServiceOn Equipment Management Operations System(EM-OS) is a network management system that offers control to network operators. TheEM-OS network management system is a package of software and hardware, whichenables operators to control and configure their network from any point along it.TheProbe for Marconi EM-OS acquires event data from Marconi EM-OS switches. Theprobe reads alarms either through a direct connection to the serial port of theworkstation controlling the switches, or through a telnet to a terminal server"

"Ericsson ServiceOnOptical NetworkManager NM / MarconiMV38/PSB MNR"

PSB versions 2.2, 3.2, 4.1, 4.2 and4.3

nco_p_marconi_psb Solaris, HP-UX

"The Marconi ServiceOn Optical Network Management System (ONMS) manages thealarm life cycle. It can manage alerts from the time they are raised, until acknowledgedand cleared. The Probe for Marconi PSB collects events from the Marconi ServiceOnOptical Network Management System by connecting to the Practical Service andBusiness (PSB) interface using the CORBA naming service running on the Marconi PSBhost."

"Ericsson ServiceonOptical EM / MarconiMV36/PFM"

PFM versions 1.6 , 2.1 and 2.3 nco_p_pfmSolaris, HP-UX,AIX, Linux,

"The Marconi Practical Fault Management (PFM) interface is an optional managementinterface for the Marconi MV36 element manager. The MV36 element manager providesfunctions at the Element Management Layer and support to the Network ManagementLayer. The MV36 can be used stand-alone or in conjunction with the MV38 networkcontrol manager and manages the MSH series of multiplexers and cross-connects, andthe SmartPhotoniX optical systems. The Probe for Marconi PFM acquires data byopening a socket connection to the MV36 system through the pfm-export TCP service."

"Probe for MicrosoftSystem Center forOperations 2007"

SCOM 2007 SP1 Net 3.0

SCOM 2007 R2 .

nco-p-scom2007 Windows

Microsoft System Center Operations Manager (SCOM) 2007 is an event andperformance management tool for Windows Server System. It provides systemdiagnostic functionality that includes indicating potential problems in applications andrecommending possible resolutions. The Probe for Microsoft System Center OperationsManager 2007 uses the SCOM Connector Framework and receives and acknowledgesevents from the SCOM server. The probe can also resolve alerts in the SCOM server.NOTE : The SCOM probe is no longer supported on the UNIX platforms for newcustomers. Existing customers are being urged to upgrade to the Windows version ofthe probe. Please contact Product Management for further guidance.

"Microsoft OperationsManager (MOM)" Microsoft Operations Manager (MOM)

2005 SP1nco_p_mom Windows

Microsoft Operations Manager (MOM) 2005 is an event and performance managementtool for Windows Server System. It provides system diagnostic functionality that includesindicating potential problems in applications and recommending possibleresolutions.The Probe for Microsoft Operations Manager receives and acknowledgesevents from the MOM server. The probe can also resolve alerts in the MOM server andretrieve knowledge based information stored on the MOM server. NOTE : The MOMprobe is no longer supported on the UNIX platforms for new customers. Existingcustomers are being urged to upgrade to the Windows version of the probe. Pleasecontact Product Management for further guidance.

"Radius" N/A nco_p_radiusSolaris, HP-UX,AIX, Linux

Remote Authentication Dial-In User Service (RADIUS) is a client/server protocol andsoftware. RADIUS enables remote access servers to communicate with a central serverto authenticate dial-in users and authorize their access to the requested system orservice. The Probe for RADIUS acquires event data by reading the RADIUS accountingfile. The probe also supports off-line replaying of existing accounting files and theprocessing of log files.

"Enterprise SNMP EMSProbe"

SNMP V1 , V2 and V3 nco_p_mttrapd


The SNMP probe and the SNMP EMS probe were architecturally very similar probes .The SNMP EMS probe provided the added functionality of SNMP GET and SETcommands. The SNMP EMS probe has now been renamed to the SNMP probe. Pleaserefer to the description for the SNMP Probe.

"Multi-headed Socket" N/A nco_p_socket


The IBM Tivoli Netcool/OMNIbus Socket Probe can be configured to work in eitherClient mode or Server mode. In Server mode, the probe is a multiheaded probe thatacts as a single process concurrent server; the probe can handle a limited number ofmultiple connections to it through a TCP port. In Client mode, the probe connects to asocket to which a device writes its events.

"PDS Snyder" PDS Snyder nco_t_pdsSolaris, HP-UX,AIX, Linux

"The TSM for PDS Snyder reads event streams issued by digital cross-connectionswitches that use the PDS Snyder message protocol, such as the Alcatel DSC CS1Land the Tellabs Titan 532L. It can also make connections to multiple devices."

"Motorola OMC-R(Iden)"

Motorola OMC-R iDEN SR 16 , SR 17 nco_p_motorola_omcr_idenSolaris, HP-UX,AIX, Linux

"Motorola Operations & Maintenance Center - Radio (OMC-R) is part of Motorola's NSSadvanced Network Management Portfolio and serves as the interface point of thenetwork to other management platforms. The suite is targeted at Wireless operators formanagement of GSM, analog, CDMA, switching and intelligent networks, with supportfor products such as Motorola iDEN.The probe for Motorola OMC-R connects to theMulticasting Buffer System (MCB) using a TCP/IP connection and acquires alert data.The acquired alert data can be an OMCR event or an MCB MUX event"

"Motorola AdvancedElement ManagementSystem- AEMS/MUNO"

Motorola Universal NetworkOperations (UNO) device / MotorolaAEMS Releases 20 , 21, 22, 23 and24

nco_p_motorola_munoSolaris, HP-UX,AIX, Linux

The Probe for Motorola AEMS MUNO is a Socket Probe that connects to the MotorolaAEMS device using host and port combination.

"Motorola OMC-R(3GPP)"

Motorola OMCR server versionGSR-7, GSR-8, or GSR-9

nco_p_motorola_omcr_3gpp /

nco_p_motorola_omcr_3gpp_V5Solaris

"The Motorola 3GPP OMCR server is part of the Motorola NSS advanced NetworkManagement Portfolio and serves as the interface point of the network to othermanagement platforms.The Probe for Motorola 3GPP OMC-R 3GPP connects to thesystem through a CORBA interface"

"Siemens EWSDLogfile"

Siemenns EWSD nco_p_ewsdSolaris, HP-UX,AIX, Linux

The Siemens EWSD system supports both switched telephony and data applications.Siemens EWSD switches provide a wide variety of business and residential servicesencompassing ISDN, CLASS, SS7, Centrex, and Advanced Intelligent Networkcapabilities.

"Siemens SMN-OS" Siemens SMN_OS EMS nco_p_siemens_snmos Solaris , HP-UX

Siemens Synchronous Digital Hierarchy Management Network Operations System(SMN-OS) is a network element management system. The Generic Interface FaultManagement (GIF/FM) process provides an interface between Siemens SMN-OS andNetcool/OMNIbus.The Probe for Siemens SMN-OS connects to the GIF/FM interface toretrieve the Siemens SMN-OS events.

"Siemens TNMS(SNMP)"

All SNMP V1, V2c, and V3 traps andinforms

nco_p_siemens_tnms_snmpSolaris, HP-UX,AIX, Linux

"The Siemens Telecommunication Network Management System (TNMS) is amanagement system for optical transport networks. It provides integrated managementfor the whole optical transport network portfolio from the access to the core layersupporting all the related technologies such as PDH, SDH, DWDM, and IP. TheSiemens TNMS SNMP interface provides a means to monitor and control Siemensnetwork devices.

The Probe for Siemens TNMS SNMP Interface monitors SNMP traps and events onboth UDP and TCP sockets concurrently. It supports SNMP V1, V2c, and V3 traps andinforms"

Siemens TNMS(CORBA)

Siemens TNMS versions 9 , 10 , 11,12 and 13

nco_p_siemens_tnms_corba Solaris

The Siemens TNMS system is a sub-network level management system that providesboth element management and network management functions for telecommunicationsnetworks.

The Probe for Siemens TNMS (CORBA) acquires data from the Siemens TNMS systemusing a CommonObject Request Broker Architecture (CORBA) interface.

Nokia-SiemensNetact/NMS2000

OSS 3, OSS 4.2, OSS 5.x, 6.0 and7.0

nco_p_nms2000Solaris, HP-UX,AIX, Linux

The Probe for Nokia NMS 2000 collects events generated by Plesiochronous DigitalHierarchy (PDH) and Synchronous Digital Hierarchy (SDH) transmission systems thatthe Nokia NMS 2000 system monitors.

Nokia-Siemens NetActfor Broadband

Nokia NetAct for Broadband versions3.2, 3.3, and 3.4

nco_p_netact_bbSolaris, HP-UX,AIX, Linux

Nokia NetAct for Broadband is a Simple Network Management Protocol (SNMP) Faultand Provisioning Management tool for its Digital Subscriber Line (DSL) andAsynchronous Transfer Mode (ATM) broadband networks. Nokia NetAct for Broadbandcovers all the main operator processes such as network monitoring, development,optimization, service management, reporting, and system management.

The Probe for Nokia NetAct for Broadband reads alarms produced by Nokia NetAct forBroadband. TheASCII Alarm Interface can be used by a third party management systemto receive alarm event information from the network managed by Nokia NetAct forBroadband.

Nokia-Siemens NetActfor Wireless (3GPP)

OSS3, OSS4.3 and OSS 5.2, 5.3, 6.0and 7.0

nco_p_nokia_netact_3gpp Solaris, HP-UX

Nokia NetAct 3GPP is a networking and service management system. It provides faultand performance management, service provisioning, support for multiple wirelessnetwork technologies, and customer management interfaces. It operates across theradio-access and core sub-networks of next-generation wireless Internet networks.

The Probe for Nokia NetAct 3GPP (CORBA) collects alarms from Nokia NetAct using a3rd Generation Partnership Project (3GPP) Common Object Request BrokerArchitecture (CORBA) interface. The probe acquires data from Nokia NetAct devicesthat support 3GPP version 4.3.0. IBM does not maintain a list of compatible Nokiadevices.

Nokia-SiemensSwitch/Radio/@vantageCommander (CORBA)

SCR13,14 and 15 @C9.0nco_p_siemens_corba_v1 /nco_p_siemens_corbav2

Solaris, HP-UX

Siemens 3rd Generation Partnership Project (3GPP) is a Common Object RequestBroker Architecture (CORBA) interface shared by the Siemens SwitchCommander,Siemens RadioCommander, and Siemens @vantageCommander. The Probe forSiemens 3GPP (CORBA) collects alarms from the Siemens 3GPP interface.

Nokia-SiemensRadioCommander (Q3)

RC8.0 - BR8 / UMR4

RC8.5 - BR8 / UMR5

RC9.0 - BR9 / UMR6

RC9.5 - UMR6.5

RC10.0 - BR10 / UMR7

nco_p_siemens_rc_brXXvYY Solaris

The Siemens Radio Commander provides a mature concept for mobile networkmanagement by merging operation and maintenance for the different radio technologiesof the second and third generation and their enhanced technologies like GPRS, EDGEand HSDPA on one single platform.Radio Commander manages network elements asfollows: Base Station Controller (BSC), Base Transceiver Station (BTS), Transcodingand Rate Adaptation Unit (TRAU), as well as Radio Network Controller (RNC) andNodeB

The Probe for Siemens RadioCommander (Q3) allows you to connect the SiemensRadioCommander device to the ObjectServer using a Q3 interface.

Nokia-SiemensSwitchCommander(Q3)

SCR 12 , SCR13 and SCR14 nco_p_siemens_sc_scr12 Windows

Switch Commander of Siemens is a operation and maintenance center, that managesGSM, GPRS and UMTS systems in parallel.The Switch Commander provides O&Mfunctions to network elements such as:

Mobile Switching Center (MSC)

MSC Server (MSC-S) and Media Gateway (MGW) of the Release 4 Architecture

Signaling Transfer Point

Service GPRS Support Node (SGSN)

Gateway GPRS Support Node (GGSN)

Intelligent Packet Solution (IPS)

Glenayre VMS Glenayre VMS nco_p_glenayrevmsSolaris, HP-UX,AIX, Linux

The IBM Tivoli Netcool/OMNIbus Probe for Glenayre VMS allows connection toGlenayre systems such as the MVP 2120 and MVP 4240 system. The MVP 2120 andMVP 4240 systems integrate with central office switches, cellular switches, and PBXs toprovide enhanced services such as voice messaging, fax messaging, and personalcommunication services, including voice activated dialing.

The Probe for Glenayre VMS connects to the Glenayre system using a TCP/IPconnection. It is a multi-headed probe that can acquire alert data from multiple hosts.

Ascom Timeview Ascom Timeview NMS nco_p_timeviewSolaris, HP-UX,AIX, Linux

The Ascom TimeView Network Management Systems allows you to configure, monitor,administer, and maintain LINK+ and SYNCHRONY TX-3 networks from a single site orfrom multiple sites. Ascom Timeview is a multi-tasking system capable of performingmultiple management functions concurrently.

The Probe for Ascom TimeView acquires event data from the Ascom Timeview NMS logfile.

Comverse TrilogueInfinity

Comverse TRILOGUE Infinity 3.x nco_p_comverseSolaris, HP-UX,AIX, Linux

The Comverse TRILOGUE INfinity system provides a range of messaging services,such as letting a caller know the line is engaged, or letting a mobile phone user knowthat they have new messages. The system includes specialized hardware that can beconnected to both mobile and standard phone switches. Each Comverse TRILOGUEINfinity system is connected to its own element manager, known as a TRILOGUEManager (TRM).

ECI eNM ECI eNM nco_p_eci_eNMSolaris, HP-UX,AIX, Linux

The ECI Network Manager (eNM) Management System monitors synchronous digitalhierarchy (SDH) equipment. ECI-SDH networks are supported in a service-orientednetwork management environment by the eNM. The system allows administrators tomonitor and control faults, performance and security, and to support networkconfigurations with end-to-end management capabilities.

Probe for ECI eNM supports ECI devices that generate eci.dat log files containingevents whose minimum length is 100 characters.

Dantel Pointmaster Dantel Pointmaster nco_p_pointmasterSolaris, HP-UX,AIX, Linux

The Dantel PointMaster is used as an alarm point concentrator for environmental alarmsthroughout a network. The Probe for Dantel PointMaster is a multi-headed probe thatacquires alert data from each Dantel PointMaster system.

Nortel DMSModels 100, 250, 300, 500, GSP,MTX

nco_t_dmsSolaris, HP-UX,AIX, Linux

The Nortel DMS Supernode exchange is a digital switching system for public telephonenetworks that serves both fixed and mobile services. The Nortel DMS system isdesigned for a range of applications from smaller switches to large transit exchanges.The Nortel DMS system can be used to implement many different platforms.

The TSM for Nortel DMS monitors any DMS Supernode switch (including the 100, 250,300, and 500 models), Super Data Node Managers (SDMs), and CS2k switches.TheDMS TSM can connect to the DMS switch through a direct TCP connection to aspecified port (23 by default) of through a terminal server attached to a serial port on theswitch.

Nortel Meridian Nortel Meridian nco_p_meridian Solaris

Nortel Meridian is a telephone switch communications system that uses PrivateBranch``Exchanges (PBXs). The system can deliver voice, data, image, and videocommunications to the desktop. The system also supports ethernet and limited SNMPmanagement. The Nortel Meridian probe connects to the Meridian system using telnet,rsh or tip. The``default connection method is telnet.

Nortel Base StationSubsystem Manager(BSSM)

Nortel BSSM nco_p_nortel_bssmSolaris, HP-UX,AIX, Linux

The Nortel Base Station Subsystem Manager (BSSM) is the Operations, Administration,and Maintenance (OAM) platform for the CDMA Network. The Nortel BSSM providesaccess to network elements ranging from large hardware systems like the Nortel BaseStation Transceiver Subsystem (BTS), to smaller components like the Nortel SelectorBank Subsystem (SBS), for configuration, monitoring, and troubleshooting.

The Probe for Nortel BSSM collects alarms from the log files in the Nortel BSSM systemthrough a socket connection.

Nortel EV-DO Nortel EV-Do Logfile nco_p_nortel_evdoSolaris, HP-UX,AIX, Linux

Nortel EV-DO (Evolution Data Optimized) is a packet data system. The Probe for NortelEV-DO reads the log files in which Nortel EV-DO stores alert data.

Nortel IEMS / GebandIEMS

Nortel IEMS Succession SN08 , ISN9U , ISN 10, CVM 11 , CVM 12 andCVM13

nco_p_nortel_iemsSolaris, HP-UX,AIX, Linux,Zlinux, Windows

Nortel Integrated Element Management System (IEMS) is a software solution for voiceover packet networks providing network management functions. The Probe for NortelIEMS monitors SNMP traps and events generated by a Nortel IEMS server on both UDPand TCP sockets concurrently.

Nortel Digital FaultManagement (DFMS)

Nortel Digital Facility ManagementSystem

nco_p_dfmsSolaris, HP-UX,AIX, Linux

The Nortel Digital Facility Management System (DFMS) provides end-to-endsurveillance, monitoring, and control for complex digital transport networks. Together, orworking with Bellcore's Network Monitoring and Administration (NMA) system, theyintegrate facility maintenance across all levels of the digital hierarchy. This simplifiescontrol center functions such as trouble detection, service restoration, recordkeepingand statistical reporting.

The Nortel Digital Facility Management Probe connects to a remote computer that isrunning DFMS software through a Telnet connection. The received data can either be insingle or multiple lines. Single line events include a timestamp and end with the severity.Multi line events include a timestamp which is usually followed by an indicator of theactual node

Nortel EIF Nortel EIF Interface nco_p_eifSolaris, HP-UX,AIX, Linux

The Probe for Nortel EIF is for the netWORKS External Interface for Fault andperformance data (EIF). The netWORKS EIF is designed as an optional feature to allowan external system to obtain significant faults, performance data, and access to the faultand performance databases.

IBM MetricaPerformance Manager

IBM Tivoli Metrica /NPR 3.5 nco_p_metricaSolaris, HP-UX,AIX, Linux

Metrica/NPR is a performance and traffic analysis for on fixed-line and wirelessnetworks. IBM Tivoli Netcool/OMNIbus Probe for Metrica/NPR is a dual function probethat connects to a socket or a UNIX FIFO.

Fibermux LightwatchLightwatch for Fibermux CrossbowHubs

nco_p_lightwatchSolaris, HP-UX,AIX, Linux

IBM Tivoli Netcool/OMNIbus Probe for Fibermux LightWatch is a network managementsolution that monitors ADC Kentrox (formerly Fibermux) communications equipment andtheir attached networks, providing graphics-based control.The Probe for Fibermux LightWatch is a multi-platform probe that reads the flat log file oftheLightWatch and parses the values using specified value and line separators. Theprobe creates elements according to the resulting parsed data.

Nortel EAI EAI V5 and V6; Nortel OMEA nco_p_nortel_eaiSolaris, HP-UX,AIX, Linux

The Nortel Preside External Alarm Interface (EAI) is used to connect Nortel Presideelement managers.The Probe for Nortel EAI is a unidirectional interface thatresynchronizes historical data with the element manager at configurable intervals. TheNortel EAI sends the probe all network events and network element messages in realtime. The probe processes these events and forwards them to the ObjectServer.

Nortel Magellan NMS 10.3-10.7 nco_p_nortel_magellan_nmsSolaris, HP-UX,AIX, Linux

The Nortel Magellan NMS is a network management system designed for serviceproviders that provides carrier-grade management solutions. It can be used to manageNortel Passport and Nortel DPN devices and the networks that those devices support. Italso has application interfaces that allow you to integrate it with other systems.

The Probe for Nortel Magellan NMS is a single headed probe that connect to the NortelMagellan NMS device through a TCP or telnet connection.

Nortel Multi-serviceData Manager /MDM

MDM 14.1 - 16.2 nco_p_mdm Windows

The Nortel Preside Multiservice Data Manager (MDM) is a suite of service managementapplications from Nortel Networks, initially designed to manage Passport networks.MDM is used by operators to integrate, monitor and control Passport network elements.Preside MDM applications can be part of an overall management platform or canoperate as a standalone system.

The probe acquires data by connecting to the General Management Data Router(GMDR) API of the Nortel MDM system. This API allows the probe access to all alarminformation from all of the devices managed by MDM.

Nortel Preside Wireless(3GPP)

Nortel PWI 3GPP version with thePacket Core running on OAM release4.x (PC04)

nco_p_nortel_pwi_3gpp_pc04 Solaris, HP-UX

Nortel Preside for Wireless Internet (PWI) 3GPP Server is a networking and servicemanagement system. It provides fault and performance management, serviceprovisioning, support for multiple wireless network technologies, and customermanagement interfaces. It operates across the radio-access and core sub-networks ofnext-generation wireless Internet networks. Nortel PWI supports a collection of devices(for example, UTRAN, RNC, SGSN, and SIG) defined in a Packet Core. Each device inthe packet is managed by the Operations Management and Maintenance (OAM)management platform software.

Nortel PWI has been renamed Nortel Wireless Network Management System Nortel (W-NMS). The Probe for Nortel PWI 3GPP acquires data from Nortel PWI and NortelW-NMS.

Nortel OAM5 CORBA Nortel OAM (3GPP) v5.0.1 nco_p_nortel_oam5 Solaris, HP-UX

Nortel GPRS/UMTS OA& M 3GPP Server is a networking and service managementsystem. It provides fault and performance management, service provisioning, supportfor multiple wireless network technologies, and customer management interfaces. Itoperates across the radio-access and core sub-networks of next-generation wirelessInternet networks.

The OAM5 probe retrieves events from the Nortel W-NMS 3GPP OA&M CORBAinterfaces for Fault Management

Nortel CDMA NetworkManager(CNM)

CNM 2.0 , CNM 3.0 and CNM 4.0 nco_p_nortel_cnm Solaris,HP-UX

Nortel CNM (CDMA Network manager) is a networking and service managementsystem that provides a real-time view of the service provisioning, order managment,fault and performance management for an enterprise customer's network. This systemsupports multiple wireless network technologies, and customer management interfacesfor the creation, delivery, and playback of multimedia over GSM and CDMA2000wireless networks. The Probe for Nortel CNM collects alarms from Nortel CNM systemusing a 3GPP2 CORBA (Common Object Request Broker Architecture) interface forCDMA2000 networks.

Nortel CDMA ElementManagement System (C-EMS)

Nortel C-EMS versions 14, 15, 16 and17

nco_p_nortel_cems Solaris,HP-UX

Nortel C-EMS (CDMA Element Management System) is a networking and servicemanagement system that provides a real-time view and control point for networkelements of multiple vendors. This system supports multiple wireless networktechnologies, and customer management interfaces for the creation, delivery, andplayback of multimedia over GSM and CDMA2000 wireless networks.The Probe forNortel C-EMS collects alarms from Nortel C-EMS system through a 3GPP2 interface forCDMA2000 networks.

Nortel OMC-R Probe(Q3)

Nortel OMCR version 14 nco_p_nortel_omcr_v14 Solaris

The operation functions that can be used from an OMC-R terminal belong to functionscorrespond to the provisioning of the configuration parameters of the network elements,as well as the full-centralized management of the software releases of BSCs, TCUs andBTSs equipment for the BSS subsystem and PCUs of the GPRS subsystem. NOTE :The OMCR Q3 Probe is only supported till version 14 . The Netcool EXEC probe canbe used to retrieve events from the OMCR ASCII interface for version 15, and above.

Nortel OMEA N/A n/a n/a Uses the EAI interface - see Nortel EAI probe

OpenService /Logmatrix NerveCenter

Open NerveCenter version 3.5 and4.1

nco_p_nervecentre

Solaris, HP-UX,AIX,Linux,ZLinux,Windows

NerveCenter is a client/server application. The client program provides the NerveCenteruser interface. The server program performs all the NerveCenter monitoring andprocessing. The server program also saves to the NerveCenter database all thebehavior model components you modify or create as you use NerveCenter to manageyour network. Before you can use the NerveCenter client, the NerveCenter server mustbe running. The server program is configured to start automatically when the server'shost computer boots or is started by an administrator. The NerveCenter client programruns in either administrator or operator mode, depending on your user ID or group. Asan administrator, you can customize NerveCenter and save all your changes to thedatabase. When you use NerveCenter with operator privileges, you can monitor devicesand reset NerveCenter alarms, but you cannot modify the database.

Cisco ACS N/A N/A N/A

"Cisco ACS is an authentication, authorization, and accounting (AAA) server that formspart of the Cisco Self-Defending Network Initiative. It connects Anti-Virus, Firewall, andNetwork Access devices.

Cisco ACS can be integrated into OMNIbus using the Netcool Syslog probe . NOte : Theold Cisco ACS probe is no longer in support

Cisco PIX/ASA N/A N/A N/A

The Cisco PIX Security Appliance has evolved to the Cisco ASA 5500 Series AdaptiveSecurity Appliances. We do not support a dedicated probe for the Cisco PIX Applianceany longer. The SNMP rules for the Cisco ASA/PIX are available though NetcoolKnowledge Library.

Checkpoint Firewall-1 N/A nco_p_firewall1 Solaris, Linux

Check Point FireWall-1 is a suite of transparent enterprise security applications. Itprovides security, authentication, encryption, network address translation, and contentscreening for Internet, intranet, and extranet environments.The Probe for Check PointFireWall-1 is a multi-threaded log reader that can read from multiple Check PointFirewall-1 servers, Provider-1 servers, Customer Log Modules (CLMs) or Multi-site LogModules (MLMs).

IBM Internet SecuritySystems (ISS) pRSiteProtector

ISS Siteprotector 2.0 SP6 nco_p_iss_siteprotectorSolaris,Windows

The Internet Security Systems (ISS) SiteProtector is the preferred management platformfor ISS based security solutions. ISS SiteProtector is based on a Microsoft SQLdatabase. It contains a large number of tables containing data for a wide range ofhardware and capabilities.The Probe for ISS SiteProtector acquires event data from the ISS SiteProtectordatabase and sends new data records as events to the ObjectServer.

Siemens NetManager N/A n/a n/a Supports SNMP -use the SNMP EMS probe for integration

SunManagementCenter(SUNMC)

Sun Management Center 3.0 , 3.5 ,3.6.1 and 4.0

nco_p_sunmcSolaris, HP-UX,AIX, Linux,Windows

Sun Management Center (Sun MC) software is a monitoring and management solutionthat provides an integrated and comprehensive management of Sun products, theirsubsystems, and components..The Probe for Sun Management Center uses the SunManagement Center Java API to connect remotely to the Sun Management Center.

Tekelec Eagle STP Eagle STP nco_p_eaglestp

The Eagle STP product line is a carrier grade packet switch for Intelligent Networkcontrol configuration. The Probe for Tekelec Eagle STP is a multiheaded probe that canbe attached to one or more STP devices using a TCP connection to a specific IPaddress and port.

Tekelec LSMS N/A nco_p_tekelec_lsmsSolaris, HP-UX,AIX, Linux

The Tekelec Local Services Management System (LSMS) forms a part of the TekelecEagle 5 Local Number Portability (LNP) voice network system.The Probe for TekelecLSMS acquires data through a TCP connection. The probe can be attached to morethan one host and can acquire events from each host to which it is attached.

Tellabs MetrowatchDCS

Tellabs MetroWatch DCS FP5.0 AMLNBI

nco_p_tellabs_metrowatchSolaris, HP-UX,AIX, Linux

Tellabs MetroWatch is an element manager that provides the TMN-based elementmanagement layer functionality required to manage, provision, and maintain networks ofTellabs 5500 NGX transport switches. The network elements managed by TellabsMetroWatch generate alarms in XMI format.

The probe connects to the element manager using a TCP port and reads the alarms asthey are generated

Tellabs 8000/8100 /Intelligent NetworkManager/Ericsson DXX

Tellabs 8100 versions R12, R13A,and R14, and Tellabs 8000 versionsR15, R16, R17, SR2.0, SR2.0.1 andSR2.1

nco_p_tellabs_8100Solaris, HP-UX,AIX, Linux

The Tellabs 8000 System is used by public network operators and service providers tobuild or enhance their networks. Typical applications managed though Tellabs 8000include cellular transport solutions and business service solutions.

The system comprises a range of network elements, terminating units, and a networkmanagement system, the Tellabs 8000 Manager. The Tellabs 8000 Manager is used tocentralize control of a wide range of components including modems, networkterminating units, and backbone nodes. Operators can use the Tellabs 8000 Manager tofix problems around their system from a single management center.

The Tellabs 8000 intelligent manager includes support for the following Tellabs solutionsand product families:Tellabs ® Mobile SolutionsTellabs ® Optical SolutionsTellabs ® Business SolutionsTellabs ® 3700 Multimedia ControllerTellabs ® 5500 Digital Cross-Connect SystemTellabs ® 5320 L Digital Cross-Connect SystemTellabs ® 6300 Managed Transport SystemTellabs ® 7100 Optical Transport SystemTellabs ® 7300 Metro Ethernet Switching SeriesTellabs ® 8100 Managed Access SystemTellabs ® 8600 Managed Edge SystemTellabs ® 8800 Multiservice Router SeriesTellabs ® SmartCore ® 9000 Series

Tellabs 2100 Tellabs 6300 Network Manager nco_p_nm2100Solaris, HP-UX,AIX, Linux,Zlinux

The Tellabs FOCUS NM2100 network manager is a telecommunications managementsystem for element-level and network-level management of the Tellabs FOCUS productline. It combines wavelength-division multiplexing (WDM) and synchronous digitalhierarchy (SDH) equipments into an integrated managed transmission solution formanaging network traffic. The alarm management in the FOCUS NM2100 system isbased on TeMIP's handling of the Open Systems Interconnection (OSI) formatted alarminformation generated by network elements.

The IBM Tivoli Netcool/OMNIbus Probe for Tellabs FOCUS NM2100 builds a connectionto the NM2100 device and sends new data records as events to the ObjectServer via aTCP/IP connection.

TL1 TSM N/A nco-t_tl1Solaris, HP-UX,AIX, Linux

The TL1 TSM acquires data from TL1 autonomous messages and response messages.TL1 Network Elements (NEs):

• generate autonomous messages to report alarms or events

• send response messages in reply to requests from Operations Support Systems(OSSs)

The TL1 TSM passes autonomous messages, responses, and acknowledgements toNetcool/OMNIbus, and uses the response messages for heartbeating andresynchronizing connections to the NEs."

Mttrapd SNMP Probe SNMP V1 , V2 and V3 nco_p_mttrapd


Receives traps independently of trap processing using an internal queue mechanism.Handles high trap rates and high burst rates using two buffers: one buffer is for all of thesockets that the probem onitors, and the another buffer is an internal queue between thereader and writer sides of the probe. Supports SNMPV1 traps, V2c traps, and V3 traps .Supports SNMP V2c and V3 traps and informs. Uses a USM-based V3 security model

Syslog / Syslogd N/A nco_p_syslog / nco_p_syslogd


There are two probes that acquire data from syslogd: Syslog Probe and Syslogd Probe.Both probes parse the syslog messages in the same way; they differ in how they acquiredata. The Syslog Probe acquires syslogd data from the system log file or from a namedpipe. The Syslogd Probe acquires syslogd data directly from a UDP port

Multi-Headed WindowsEventLog

Windows NT and Windows 2000 nco_p_mhntlog WindowsThe Probe for Microsoft Windows NT Event Log monitors any specified event log fileson any specified Windows NT or Windows 2000 host. NB: The Probe for WindowsEvent Log is not currently supported on Windows 2008.

Probe for MicrosoftWindows Event Log

Windows 2003 and above nco_p_wineventlog.bat Windows

The Probe for Microsoft Windows Event Log monitors any specified eventlog files on any specified supported Windows host.

The Probe for Microsoft Event Log can monitor forwarded events stored inany forwarded event log folder. Remote event extraction is supported byretrieving events from the Forwarded Events folder.

Ping N/A nco_p_ping


The IBM Tivoli Netcool/OMNIbus Ping Probe is used for general purpose applications onUNIX® platforms and does not require any special hardware. It can be used to monitorany device which supports the ICMP protocol, such as switches, routers, PCs, andUNIX hosts.

Email Probe N/A nco_p_email


The E-mail Probe monitors either an IMAP or a POP3 mail server from which it getsevents in the form of e-mails. It retrieves these events (e-mails) based on matching aregular expression with a particular header field in the e-mail.

Exec Probe N/A nco_p_exec

Solaris, HP-UX,HP-UXIntegrity AIX,Linux, ZLinux

The Exec probe is a generic probe that has built in chat in - out capabilities. It has anexposed parser with many definable features that include a termination character, breakcharacter and message size.

FIFO Probe N/A nco_p_fifoSolaris, HP-UX,AIX, Linux

The FIFO Probe acquires event data from a pipe called the FIFO file. When it readsevent data from the FIFO, it processes the data, one line at a time, as events. If theFIFO specified by the FifoName property does not exist, the probe will not create it.

Generic Logfile Probe N/A nco_p_glf

Solaris, HP-UX,HP-UXIntegrity AIX,Linux, Zlinux,Windows

The IBM Tivoli Netcool/OMNIbus Generic Log File Probe is a multi-platform probe thatreads a flat log file and parses the values using specified value, line, and characterseparators. The probe creates dynamic, numbered elements according to the resultingparsed data.

Standard Input /Stdin N/A nco_p_stdin

Solaris, HP-UX,HP-UXIntegrity AIX,Linux, Zlinux,Windows

The Standard Input Probe takes event data from Standard Input (stdin) and sends it tothe ObjectServer.

ZTE M31 NetNumenWCDMA Corba (Ranand CN)

ZTE NetNumen M31-R V3.10 nco-p-zte-corba-wcdma Solaris

ZTE NetNumen WCDMA controls different interconnected networks and performsintegrated network fault management, fault location, performance analysis, andenhancing of integrated management level. The centralized reporting function providesmultiple views of the network and helps compare their performance. The Probe for ZTENetNumen WCDMA (CORBA) collects alarms from ZTE NetNumen M31-R V3.10 usinga 3rd Generation Partnership Project (3GPP) Common Object Request BrokerArchitecture (CORBA) interface. The probe supports both RAN EMS and CN EMS.

Alcatel-LucentWMS/WNMS

Alcatel-Lucent WNMS V6.0 nco_p_alcatel_wnms Solaris,HP-UX

The IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent WNMS gathers events fromthe Alcatel-Lucent WNMS servers using a Common Object Request Broker Architecture(CORBA) interface. CORBA is an Object Management Group specification that providesa standard interface definition between objects in a distributed environment; that is, itallows applications to communicate with one another regardless of where they arelocated or who has designed them

The Probe for Alcatel-Lucent WNMS is in compliance with the following 3GPPstandards:

# 32.111-3 V6.3.0 - Alarm IRP# 32.303 V6.4.0 - Notification IRP

# 32.363 V6.3.0 - EPIRP IRP

Alcatel-Lucent 9753OMC-R WIMAX

Alcatel-Lucent 9753 OMC CORBA -Release W3

nco_p_alcatel-9753_omc Solaris,HP-UX

The 9753 WiMAX OMC WR (Alcatel-Lucent 9753 WiMAX OMC WR) system managesradio devices. The Probe for Alcatel-Lucent 9753 OMC WR collects alarms from an9753 WiMAX OMC WR management system using a 3rd Generation PartnershipProject (3GPP) Common Object Request Broker Architecture (CORBA) interface.

Probe for MessageBus(XML)

XML event sources. Currently theintegration supports JMS and file.

nco_p_xmlSolaris, HP-UX,AIX, Linux,Zlinux, Windows

The IBM Tivoli Netcool/OMNIbus Message Bus Integration allows you to process XMLmessages either stored in a file or transmitted using a JMS-compliant message bus,such as Websphere ESB.

The integration comprises a Message Bus Gateway and a Message Bus Probe. You canuse the probe to acquire XML messages and store them as event records in theNetcool/OMNIbus ObjectServer. You can use the gateway to read events from theNetcool/OMNIbus ObjectServer, and send them as XML messages using a JMS-compliant message bus, or write them to a file.

Probe for ZTENetNumen N31

ZTE Netnumen N31-V4.0.1 nco_p_zten31_fixednms_corba Solaris, HP-UX

ZTE Netnumen N31 is a fixed integrated network operation and maintenance system. Itcontrols different interconnected networks and performs integrated network faultmanagement, fault location, performance analysis, and enhancing of integratedmanagement level. The centralized reporting function provides multiple views of thenetwork and helps compare their performance.

The Probe for ZTE NetNumen N31 (CORBA) reads events from ZTE NetNumen N31Fixed NMS -V4.0.1.34.33 using a 3rd Generation Partnership Project (3GPP) CommonObject Request Broker Architecture (CORBA) interface.

The probe supports the following ZTE Network Elements:

# N31(NGN)# N31(IP)

# N31(AN)

# N31(VAS)

Probe for ZTENetNumen M31 CDMA

ZTE M31 CDMA version 2.0.0 nco_p_zte_m31Solaris, HP-UX,Linux

The ZTE M31 CDMA system controls different interconnected networks and performsintegrated network fault management, fault location, and performance analysis. Thecentralized reporting function provides multiple views of the network and helps comparetheir performance. The Probe for ZTE M31 CDMA collects alarms from the ZTE M31CDMA system using a Common Object Request Broker Architecture (CORBA)interface.

Probe for ZTE E300and ZTE T3

ZTE E300 and ZTE T3 nco_p_zte_e300Solaris, HP-UX,Linux

The ZTE E300 and ZTE T3 systems control different interconnected networks andperform integrated network fault management, fault location, and performance analysis.The centralized reporting function provides multiple views of the network and helpscompare their performance. The Probe for ZTE E300 (CORBA) collects alarms from theZTE E300 (CORBA) and ZTE T3 systems using a Common Object Request BrokerArchitecture (CORBA) interface

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Netcool OMNIbus 7.3.1

Netcool OMNIbus 7.3.10 people like this


best-practices,general

Page Actions ▼

This page provides links to previous versions of Tivoli Netcool/OMNIbus BestPractice documentation.

Documentation downloads (PDF):

IBM Tivoli Netcool/OMNIbus 7.3.1 Best Practices

IBM Tivoli Netcool/OMNIbus WebGUI 7.3.1 Dashboard Best Practices Guide

IBM Tivoli Netcool/OMNIbus 7.3.1 JDBC Gateway High Availability SoftwareImplementation

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Release Plan

Release Plan0 people like this

|Updated January 16, 2012 by CraigWigley|Tags: NonePage Actions ▼

Notices

References in this material to IBM products, programs, or services do notimply that they will be available in all countries in which IBM operates. Thismaterial, including any plans contained in the material, may change at anytime at IBM's sole discretion, based on market opportunities or other factors,and are not intended to be a commitment to future content, includingproduct or feature availability, in any way. Statements regarding IBM's futuredirection or intent are subject to change or withdrawal without notice andrepresent goals and objectives only. Please refer to Terms of Use for moreinformation.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Product Roadmap

Product Roadmap0 people like this


Notices


Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Early Designs

Early Designs0 people like this


Notices


Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Sprint Demos > OMNIbus Web GUI 2015 Development

OMNIbus Web GUI 2015Development0 people like this

|Updated April 22, 2015 by BhratPatel|Tags:

omnibus,webgui

Page Actions ▼

This page contains demonstration videos to show the latest developmentwork done by the OMNIbus Web GUI team.

The videos are included as attachments to this page.

Notices


Comments

1-3 of 3

PreviousNext

sgodfr3 commented on April 23, 2015 Permalink

Hello...is there suppose to be audio with these videos? I downloaded acouple and could not hear any audio with them. Not sure if it's my system ornot. Thanks.

BhratPatel commented on April 23, 2015 Permalink

Hi Scott. Yes there should be audio. What application are you using to playthe videos?

sgodfr3 commented on April 23, 2015 Permalink

It works on my Win7 KVM, my Linux media player was having issues, Thanks.

Show


PreviousNext

You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Sprint Demos

Sprint Demos0 people like this

|Updated April 22, 2015 by SteveHowell|Tags: NonePage Actions ▼

Notices


Content

OMNIbus Web GUI 2015 Development

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Milestone Downloads

Milestone Downloads0 people like this


Notices


Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases > Beta program

Beta program0 people like this

|Updated June 27, 2012 by DonW|Tags:

omnibus

Page Actions ▼

IBM Tivoli Netcool/OMNIbus Beta Announcement

The Netcool Event Management team are pleased to announce a BetaProgram for Tivoli Netcool/OMNIbus. The Beta Program is designed toprovide Customers and business partners with the opportunity to gainexperience exploring the product.

The Beta Program team are looking for existing Tivoli Netcool/OMNIbusCustomers worldwide, including those upgrading from IBM Tivoli EnterpriseConsole (TEC). The Program will provide access to early code and support -enabling the selected participants to install and pilot the product in their ownenvironments. Participants will have the opportunity to provide feedbackwhich will be delivered to development and may influence future productreleases. In return, participants are expected to report on their experiencesand participate in reference activities for the product.

This Beta Program plans to provide beta-level code to program participants.Beta and GA versions of the product publications will also be provided asthey become available. Beta Program support for participant installation anddeployment will continue for one month after the General Availability date ofthis product.

The increasing deployment of smart assets across the infrastructure resultsin greater complexity and escalating event volumes requiring fast effectiveconsolidated management in order to maintain high levels of end-end serviceavailability demanded in today's increasingly mobile global businessenvironment. Recognizing these key business needs, the new release of TivoliNetcool/OMNIbus is focussed on these key areas:-

MobilityCloudIntegration

Consumability

In order to ensure that we can provide timely interaction and support duringthe program the number of participants will be limited through a selectionprocess running during July. Please contact your IBM account or technicalrepresentative for more information.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Archive >Future Releases

Future Releases0 people like this


Notices


The following list provides details on future release contents for IBM TivoliNetcool/OMNIbus:

Release Plan

Product Roadmap

Early Designs

Sprint Demos

Milestone Downloads

Discuss the future of Tivoli Netcool/OMNIbus in the discussion forum.

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Tivoli NetcoolOMNIbus V7.4 Error Messages

Tivoli Netcool OMNIbus V7.4 ErrorMessages0 people like this

|Updated September 20, 2013 by John_Coss|Tags:

documentation,error,messages,netcool,omnibus,omnibus74servmessages.csv,omnibus74webguimessages.csv

Page Actions ▼Enhanced error message documentation, with detailed administratorresponses, is now available in the troubleshooting section of theInformation Center and in a troubleshooting appendix to theAdministration Guide (PDF, 2.2 MB).

The documented messages were identified as those most frequently reportedin problem reports/PMRs. The enhanced documentation provides you withsolutions for these errors.

The full error message catalog is available in the following CSV files attachedto this wiki entry:

OMNIbus74ServMessages.csvOMNIbus74WebGUIMessages.csv

Note: The field delimiter in both CSV files is the # character (known as the'hash', 'number', or 'pound' sign).

The Tivoli Netcool/OMNIbus documentation team:Daniel BrownJohn Coss

Comments


You are in: Tivoli Netcool OMNIbus > Home > Reference > Product videos

Product videos0 people like this

|Updated January 13, 2014 by DanielBrown|Tags:

netcool/omnibus,videos

Page Actions ▼

This page contains download versions of the video clips that are available onthe Tivoli Netcool/OMNIbus YouTube playlist at http://bit.ly/13tTypg

The following videos are available. To download a video, save the attached.zip archives to your machine. Then, extract the content and run the .mp4file.

Managing cloud environments (dan_cloud.zip)This video gives a demonstration of the cloud functionality that is included inTivoli Netcool/OMNIbus V7.4. Using the example of a fictional company thatis running a virtual in one of its data centers, It shows how events thatoriginate in hypervisors can be correlated with events that originate invirtual machines (VMs), with the hypervisor events identified as the rootcauses of the events from the VMs. The severity of the root cause events israised to critical, while the symptom events (that is, the events that originateon the VMs) are given a lower severity. This shows network operators whichevents to focus on and also which events will be resolved once the root causeevent is cleared. The Event Viewer can visualize this relationship, with theroot cause events at the root of a tree structure that contains the symptomevents.

Event reporting (omnibus_demo_reports.zip)This video shows how you can use Tivoli Netcool/OMNIbus and TivoliCommon Reporting to generate reports that give you insight into the eventsthat are received by your event management infrastructure.

Integration with Endpoint Manager (omnibus_demo_endpoint.zip)This video shows a scenario where Tivoli Netcool/OMNIbus and IBMEndpoint Manager are integrated to monitor actions that are requiredfollowing the deployment of fix packs to servers in an IT infrastructure.

Using thresholds for event monitoring (omnibus_demo_xiny.zip)This video shows how to use Tivoli Netcool/OMNIbus for "X events in Yseconds" threshold monitoring. Our company is interested only in events that

occur in specific numbers over specific time periods, thereby breachingpredetermined thresholds. The demo shows a dashboard that is configuredfor this "X in Y" monitoring, where the network operators are interested onlyin alerts that occur more than X times over Y seconds.

Comments


reports - ibm€¦ · sfsfsf's picture sfsfsf commented on january 12, 2012 permalink...

Documents