Netcool/Omnibus Integration Troubleshooting; Log Files For Netcool/Omnibus Event Synchronization - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Troubleshooting guide
Table of Contents

Advertisement

probe's log file for error messages. See "Log files for Netcool/OMNIbus Event
Synchronization" for the location of the log file.
You must update the Netcool/OMNIbus ObjectServer database schema with the
IBM Tivoli Monitoring automations before you update the probe's
tivoli_eif.rules file to include the itm_event.rules file or the probe won't start.
See the topic "Updating the OMNIbus database schema" in the IBM Tivoli
Monitoring Installation and Setup Guide for details on this procedure.
If you have updated the OMNIbus database schema with the IBM Tivoli
Monitoring automations but the probe will not start because the BSM_Identity
attribute is not defined, check if the itm_event.rules file has been modified to
include the tbsm_eif_event.rules file or if tivoli_eif.rules is including other
rules files that set the BSM_Identity attribute. If you are not integrating IBM Tivoli
Monitoring, Netcool/OMNIbus, and Tivoli Business Service Manager, comment out
any rules files (like tbsm_eif_event.rules) that are intended for Tivoli Business
Service Manager integration and are setting BSM_Identity. However, if you are
using Tivoli Business Service Manager, ensure you have installed the OMNIbus
automations provided with that product because those automations ensure that
BSM_Identity is added to the ObjectServer database schema.

Netcool/OMNIbus integration troubleshooting

This section contains general troubleshooting information that applies to
Netcool/OMNIbus integration.

Log files for Netcool/OMNIbus Event Synchronization

The following logs contain trace information associated with Netcool/OMNIbus
event synchronization.
IBM Tivoli Monitoring Situation Update Forwarder log file
Netcool/OMNIbus Probe for Tivoli EIF log file
IBM Tivoli Monitoring Netcool/OMNIbus trigger log file
232
IBM Tivoli Monitoring: Troubleshooting Guide
Default location: /tmp/itmsynch/logs/sync_trace.log
To enable more verbose tracing, edit the $EVENT_SYNC_INSTALLDIR/etc/
situpdate.conf file where $EVENT_SYNC_INSTALLDIR is the directory
where the IBM Tivoli Monitoring Event Synchronization component is
installed. Set logLevel=verbose and save the file. Stop and restart the
Situation Update Forwarder using the stopSUF.sh/stopSUF.cmd and
startSUF.sh/startSUF.cmd commands. These commands are located in the
$EVENT_SYNC_INSTALLDIR/bin directory.
Default location: $OMNIHOME/log/tivoli_eif.log where $OMNIHOME is
the directory where Netcool/OMNIbus is installed.
To enable probe tracing, run the probe with the messagelevel configuration
parameter (for example, nco_p_tivoli_eif –messagelevel debug).
Alternatively, set MessageLevel: 'debug' in the probe's properties file
($OMNIHOME/probes/$ARCH/tivoli_eif.props) and restart the probe.
Default location: $OMNIHOME/log/eventsync_debug.log1 where
$OMNIHOME is the directory where Netcool/OMNIbus is installed.
Contains trace of IBM Tivoli Monitoring triggers and procedures. Tracing is
enabled by editing the get_debug_itmsync procedure in the
Netcool/OMNIbus ObjectServer and changing the debug_itmsync flag to 1.
The procedure can be edited using Netcool/OMNIbus Administrator.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Tivoli monitoring 6.2.3 fp1

Table of Contents