Welcome to the Network and Service Assurance Blog, where you can read the perspectives from network and service assurance experts. This Blog provides insights into the network and service assurance solution, as well as technical details about specific IBM
How to configure HP Operation
Manager to monitor a process and send the events to HPOM Probe
Configuring HP Operation Manager
is an example of creating a Management Threshold Policy to monitor a
process on the management server. HPOM will send a message to the
JAVA GUI when the threshold is reached and this message will be sent
to HPOM Probe when Server MSI is enabled.
: HPOM V9.10, Administration GUI V9.0.2 needs to be installed on the
example process to be monitored is... [More]
It is not uncommon to find yourself in a situation where you need to determine the port used by a particular probe. This troubleshooting wiki shows the instruction to achieve that on a Linux platform (it can also apply to other Unix platforms as long as the netstat command supports the -p option). For more details, please refer to here .
The document is written based on the TNPM 1.3.1 and TIP 2.1
Filenames and download links are as follow :-
Installer File Name
Tivoli Integrated Portal (TIP) 2.2
TNPM (Wireline)1.3.2 - support for IE9 and Firefox ESR10 TNPM Wireline 1.3.2 now supports Internet Explorer 9 and Firefox ESR10 browsers. To enable this support, user needs to apply the interim fix 184.108.40.206-TIV-TNPM-IF0006, TIP 2.2.0 fix pack 7 (TIP 220.127.116.11) and TCR 2.1.1 interim fix 6. Details of the IFixes and Fix Packs are as follow: IFix / Fix Pack File name Link to IBM Fix Central DV patch: TNPM 1.3.2 Interim Fix 6 18.104.22.168-TIV-TNPM-IF0006... [More]
Are you struggling to find the information you need on the information center? This short video show you how to use the search functionality that is embedded in the information center. It shows you how to set up a search scope, which restricts the search and returns search results only from the documentation for your products and versions. An example is shown, restricting the search to the documentation for Tivoli Netcool/OMNIbus V7.3.1 and Netcool/Impact V6.1. The video also shows you how to perform simple searches, for single terms, and... [More]
We begin with the following Layer 2 network topology, which is the result of discovering five network devices using SNMP. Initially, there are no events associated with these devices as the devices can be reached by the ncp_poller, i.e. the Default Chassis Ping poll policy always succeeds for these devices.
To simulate ping failure, we can block ping packets from reaching some of the above devices. If ITNM is running on a Linux machine, we can use iptables to achieve this.
The default firewall that comes with a Linux host is the... [More]
Suppose we are to create a Layer 2 network topology comprising four devices connected in such a way as shown in the following diagram:
We can use the GenericCsv collector to create the above network topology within ITNM. To do this, go into the directory containing the GenericCsv collector and copy the entire GenericCsv directory to another directory, e.g. CsvCollector:
cp -a GenericCsv CsvCollector
We need to edit GenericCsvCollector.cfg to enable the collector.... [More]
It is useful to be able to restart an ITNM process without bringing down the other processes and restarting them all over again. For instance, the event gateway, i.e. ncp_g_event, will have to be restarted if its configuration file is modified, or one or more of its stitchers are changed.
To inspect the ncp_g_event process being managed by ncp_ctrl, enter the following command:
ncp_oql -domain NCOMS -service Ctrl -username admin -password "" \
-query "select * from services.inTray where... [More]
Before we begin, it is important to ensure that the Default Chassis Ping polling policy is enabled, as shown in the following:
We shall start with the following network view. There are five devices in the topology, which are either non-existent, or unreachable by ITNM since they are behind firewall. These devices have been discovered by ITNM using a collector.
To ensure that the ITNM poller, i.e. ncp_poller, can reach these devices for simulated polling, we create virtual IP addresses for these devices. On a Linux system,... [More]
One of the ways to understand ITNM collector discovery is to actually run a collector and perform a discovery the devices managed by the collector. ITNM 3.9 default installation contains the GenericCsv collector, which can be used out of the box.
The GenericCsv collector is a collector which is written in Perl. This collector uses a few CSV files as its data files, in contrast to communicating with an external data source, such as an EMS, to obtain data. Nevertheless, it is still an excellent code base for creating a real life collector... [More]
Conversions in the ObjectServer is a handy way to provide for user-friendly text, often mapping numeric values to strings. These are then most commonly used for display on event lists. But what happens when you wish to customize conversions? If you guessed that you will need to update the conversions in the ObjectServer (log into OMNIbus Administrator -> Visual -> Conversions) , you would be only half-right. The reason for this is Web GUI intercepts conversions from the ObjectServer to provide multi-lingual support, thereby masking... [More]
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... [More]
Tivoli Netcool OMNIbus 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: ... [More]