Configuring integration with Tivoli Netcool/OMNIbus
Ensure that you have Netcool®/OMNIbus Knowledge Library (NcKL) Enhanced Probe Rules for Netcool Configuration Manager installed on your Tivoli® Netcool/OMNIbus server.
Before you begin
Deploy rules specific to Netcool Configuration Manager. These rules have been bundled with Netcool Configuration Manager and deployed on the Netcool Configuration Manager Presentation server during installation, and are located in the <NCM-INSTALL-DIR>/nckl-rules directory.
opt/IBM/tivoli/netcool is the default Network Manager directory.
About this task
Installing rules files specific to Netcool Configuration Manager (not the recommended option)
- From the server where you have installed Netcool Configuration Manager,
copy the following files:
where ncm_install_dir represents the installation location of Netcool Configuration Manager, for example /opt/IBM/tivoli/netcool/ncm
Copy these files to a temporary location on the computer where the Probe for SNMP is installed.
- Extract the contents of the nckl_rules.zip file, and then copy the extracted files to the $NC_RULES_HOME/include-snmptrap/ibm subdirectory.
- If object server failover has already been configured,
proceed to step 4. Otherwise, perform the following steps:
- Go to the folder in which the mttrapd.props has been placed, for example $NCHOME/omnibus/probes/AIX5, where AIX5 is specific to your operating system.
- Edit the mttrapd.props file by
commenting out the backup object server reference:
#ServerBackup : ''
- To ensure that the probe can reference the enhanced lookup
and rules files, edit the $NC_RULES_HOME/snmptrap.rules file
by uncommenting the following
includestatements, as shown:
include "$NC_RULES_HOME/include-snmptrap/ibm/ibm.master.include.lookup include "$NC_RULES_HOME/include-snmptrap/ibm/ibm.master.include.rules" include "$NC_RULES_HOME/include-snmptrap/ibm/ibm-preclass.include.snmptrap.rules"
- Run the probe. If the probe was already running, force
the probe to re-read the rules file so that the changes can take effect,
Locate the PID of the probe by running the following command on the server running the probe. Look for a process named
ps -eaf | grep mttrapd kill -9 PIDNote: If the probe is installed on a different computer from Network Manager or the DASH portal, you must restart the probe manually.