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
This example will show you how to create ITNM 3.9 right click tools in Network views to access a URL with CGI parameters that contain a selected link information. In this example I will show you how to create a URL right click tool to show link connectivity information for a selected link. There is an out of the box ITNM right click tool that shows the connectivity information for a selected device but this tool is not available for a selected link (instead there is a pop-up tooltip that might not be easy to use for some customers):
MIB Manager, which was previously shipped in the ISM Library, is now shipped with OMNIbus 7.4.0 in the ProbeSupport feature. We recognise, however, that some customers may wish to use MIB Manager but may not, or not yet, wish to install the full OMNIbus 7.4.0. At the technote below you can find instructions for extracting MIB Manager from the OMNIbus 7.4.0 installer so that it can be installed separately.
New flash training modules released for Tivoli Netcool/Impact v6.1
Server backup & Server restoration
See all Tivoli IEA content here:
Since the introduction of Dashboard Application Services Hub (DASH), many people have asked what are the plans for Web GUI to support it. Can we build dashboards in DASH that visualize OMNIbus data? When will this be available? How can we do it?
I'm pleased to say that with the release of OMNIbus Web GUI fix pack 1, some integration with DASH is possible. Whilst it won't be until the next full release of OMNIbus that Web GUI will deploy into, and make full use of all of the DASH capabilities, we are introducing a good, solid... [More]
IBM Tivoli Network Manager IP Edition (ITNM) 3.8 Fix Pack 7 became available on Sept 12, 2013.
This fix pack is a cumulative fix deliverable, and addresses many APARs and internally found issues since the release of ITNM 3.8 Fix Pack 6. For specific details and to download this fix pack, here is the link --
Additionally, for your reference, ITNM 3.9 Fix Pack 3 is the latest available fix pack on ITNM 3.9 and is available here:
As part of an ongoing effort to improve the effectiveness of Tivoli Netcool/OMNIbus documentation, we have restructured the error message documentation in the Tivoli Netcool/OMNIbus V7.4 information center.
Enhanced error message documentation, with detailed administrator responses, is now available in the Troubleshooting section of the Information Center and in a troubleshooting appendix to the Administration Guide (PDF, 2.2 MB).
The documented messages were identified as those most frequently reported in problem... [More]
For automatic failover and failback of probes between Object Servers, both Object Servers must have identical alerts.status tables. Both the column type and column size must be the same, and the ordinal position of each column must match.
Reordering columns beetween Object Servers can be a difficult task. It isn't possible to delete and recreate columns manually, since deleting any column also deletes an object that reference that column such as triggers or tools. Instead, the Backup Object Server should be recreated and cloned... [More]
I'm pleased to announce that the Collector developer guide has been updated for the ITNM 4.1 release and is now available for download from the Tivoli Network Manager wiki .
The 'guide' now consists of a generic guide CollectorDeveloperGuide.pdf , and programming language specific Collector framework guides for Perl and Java; perlCollectorPOD.tar.gz and CollectorJavaDoc.zip respectively. These are found within the CollectorDevGuide_v1.5_For_ITNM_v4.1.tar.gz archive.
Note: The guide is... [More]
Enhancements to the OMNIbus ObjectServer native LDAP support in version 7.4.0 fixpack 2 allows amongst other things: authentication with users in multiple OU's and use of sAMAccountName.
I will discuss the model currently used by the ObjectServer to authenticate with LDAP, restrictions with this and how they are addressed by the fixpack. I will also provide snippets of configuration, concentrating on the differences between the old and new models. Full details of how to configure can be found in the Netcool OMNIbus... [More]
The Tivoli Netcool/Impact product can be used as an OSLC facade for third party products that don't have their own OSLC service provider capability. In this recorded demo, we take you through using Impact to provide hover preview capability to TBSM as an OSLC consumer for the Netcool/OMNIbus product, enabling the ITM event information to be displayed inside a new hover preview window inside TBSM.
To watch a video and learn more, visit the Netcool/Impact 6.1.1 Solution Wiki
IBM Tivoli Network Manager 3.9 fixpack 3 is seeing a surge in the use of the adaptive polling or rapid polling feature.
Some information on the scenario and some of the numbers used with this application. And why you see three minutes in the documentation, yet you won't find that timer.....
Adaptive polling documentation
This is a common scenario.
Device fails a chassis ping from the ITNM poller
Operators are alerted via the event list or other mechanism to take an immediate action to a... [More]
This article describes how to configure a Web GUI map to launch another Web GUI map in a portlet page.
In Web GUI 7.4.0, a map can be configured to launch (or change the context) of an Event Viewer or AEL portlet with the "Update Event List (using wires)" launch action. This action can also be used to configure custom wires between maps such that clicking an element in one map may launch a portlet page containing another map. This article describes how to do this.
Step 1: Configure the map... [More]
In ITNM 3.9 FP3 release, one of the enhancement included is to support LLDP layer two discovery (remote neighbor information) for devices with Extended LLDP mib. This enhancement work involves two agents:
– LLDP agent (existing)
– DefaultLLDP agent (new)
LLDP agent only supports Cisco devices discovery with LLDP enabled and DefaultLLDP agent will support non-Cisco devices discovery with LLDP... [More]
As stated in the introduction of Alcatel5620SamSoapFindToFile collector ( click here ), this collector uses new findToFile method, which uses FTP service for SAM 5620 discovery. This article will explain on troubleshooting the FTP service while running the collector discovery.
(1) Change the collector's debug level to level 4 to display the SOAP communication between the collector and SAM 5620. Please remember that by running the collector in debug level 4, it will reduce the collector discovery performance. Only run the... [More]
The new AlcatelSam5620SoapFindToFile collector included in ITNM3.9 FP3 contains new features:
· findToFile method
· new object support for layer two link discovery
· support devices with multi-shelf configuration
(a) findToFile method: For the introduction of findToFile method, please refer here for the AlcatelSam5620SoapFindToFile collector... [More]