Table 20. Event status updates in Netcool/OMNIbus are not forwarded to Tivoli
Monitoring (continued)
Possible cause
Resolution
Log files to check
The
Netcool/OMNIbus
Process Agent fails
to execute the
Situation Update
Forwarder
command
(
eventcmd
)
This error can occur if the Situation Update
Forwarder command (
eventcmd
) cannot be
found. The
eventcmd.sh
(UNIX) or
eventcmd.bat
script is located in the
$EVENT_SYNC_INSTALLDIR/omnibus
directory,
where $EVENT_SYNC_INSTALLDIR is the
directory where the IBM Tivoli Monitoring
event synchronization component was
installed on the Netcool/OMNIbus
ObjectServer system.
Use Netcool/OMNIbus Administrator to
view and edit the
eventcmd
procedure and:
1.
Verify the executable path is correct. The
executable path should not have any
spaces. If the Situation Update Forwarder
was installed in a directory with spaces,
change the executable path to a path
without space, for example, on Windows:
C:\Progra~1\IBM\SitForwarder\omnibus\
eventcmd.bat
.
2.
Verify that the host parameter specifies
the host name of the Netcool/OMNIbus
ObjectServer and the user ID and group
ID values are correct especially if the
eventcmd
script will not be run as root by
the Netcool/OMNIbus Process Agent.
Look for errors related
to failing to execute
‘eventcmd’ in the
Process Agent log file
Monitoring events in Netcool/OMNIbus do not have expected
values for the Summary attribute or other attributes set by the
IBM Tivoli Monitoring probe rules
“Default mapping of situation events to OMNIbus events” in the IBM Tivoli
Monitoring Installation and Setup Guide describes how OMNIbus attributes
should be set for monitoring events. If your events do not have the expected
values described in that topic, consider the following possible causes and
resolutions.
Table 21. Monitoring events in Netcool/OMNIbus do not have expected values
Cause
Resolution
The Netcool/OMNIbus Probe for
Tivoli EIF has not been
configured to use the IBM Tivoli
Monitoring probe rules file
(
itm_event.rules
)
1.
Verify that the
itm_event.rules
file has been copied
to the
$OMNIHOME/probes/arch
directory of the EIF
probe, where
$OMNIHOME
is the directory where
Netcool/OMNIbus is installed and
arch
represents
the operating system directory on which the probe is
installed; for example, solaris2 when running on a
Solaris system, and win32 for a Windows system..
2.
Verify that the include statement for
itm_event.rules
has been uncommented in the
probe's master rules file (
tivoli_eif.rules
).
Note:
If you make any changes to the probe rules files,
you must restart the EIF probe.
Chapter 14. Event synchronization troubleshooting
239
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...