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
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]
In ITNM 3.9 FP3, a new Alcatel5620SamSoapFindToFile collector is introduced for Alcatel SAM 5620 discovery. The collector will request SAM 5620 object's data by sending SOAP request to SAM 5620. The SAM 5620 then will dump the requested data into xml files and FTP'ed them to ITNM server. It also will send a SOAP response to the collector to indicate that the files is successfully transfer. Finally, the collector will pickup the xml files and parse the data. This employed method is called findToFile.
n large network... [More]
IBM Tivoli Network Manger (ITNM IP 3.9) can use the Discovery Library Adapter (DLA) to export data for integration into other systems.
Detailed documentation exists here
Exporting discovery data
One common question with the DLA, is an explanation of this particular "type"
Type should be something like a router or a switch, but what was discovered as a ComputerSystem?
What went wrong with the discovery of this entity? Or is the... [More]
Island nodes in a topology can adversely affect RCA. I've found that creating a view that allows me to quickly find islands helps in addressing these issues with respective departments (SysAdmins, NetAdmins, etc).
Create a reporting view for IslandNodes (SQL for DB2, may need to be adapted to other platforms)
drop view ncim.islandNodes;
The Tivoli Netcool/OMNIbus V7.4 documentation has been updated to describe new functions provided by fix pack 2. The Information Center and the PDF guides now contain the following enhanced or additional information.
Note: Features and enhancements supplied by the fix pack are indicated in the documentation by the following graphical cue:
The following topics describe new LDAP query functionality that allows the ObjectServer to authenticate users in multiple organizational units (OU). Query searches... [More]
J'ai le plaisir d'annoncer la publication du Netcool/OMNIbus 7.4 Pratiques Recommandées en français.
La version française est la cinquième et dernière de la série de nouvelles traductions.
Téléchargez votre copie ici:
IBM Netcool/OMNIbus Best Practices
Using IBM Tivoli Network Manager with the most recent fixpack allows for the use of some great environmental variables for administering and controlling log and trace files.
The online documentation shows the setup or setting of the environmental variables, with references to any conflicts.
Online ITNM 3.9 Log rotation documentation
Take a look at some examples of questions from the field that are frequently seen.
setenv NDE_LOGFILE_MAXSIZE 1000000000
As part of an ongoing effort to improve the effectiveness of Tivoli Netcool/OMNIbus documentation, we have added administrator responses for some of the error messages most frequently reported in PMRs. We welcome your comments on these updates and any suggestions you might have for improving our error message documentation.
The enhanced documentation is available on the Tivoli Netcool/OMNIbus Information Center and in the Error Messages PDF Guide .
The documentation for the following error messages was updated:
IBM Tivoli Network Manager stores all snmp passwords in ncim. snmp version 1 and 2 passwords are moved to snmpV1Sec. snmp version 3 passwords are moved to snmpV3Sec. But how do you find which password was used successfully in the discovery?
The starting place for consistency is to use OQL. Whether your ncim database is DB2, Oracle, Informix or Mysql the OQL connection from the ITNM server is the best.
Documentation on NCIM OQL query