Table of Contents
Advertisement
Table 20. Event status updates in Netcool/OMNIbus are not forwarded to Tivoli
Monitoring (continued)
Possible cause
Resolution
The IBM Tivoli
Review the monitoring servers that are
Monitoring
configured in the Situation Update Forwarder
Situation Update
$EVENT_SYNC_INSTALLDIR/etc/situser.conf
Forwarder is not
file, where $EVENT_SYNC_INSTALLDIR is
configured to send
the directory where the Event
status updates to a
Synchronization component is installed on
hub monitoring
the Netcool/OMNIbus ObjectServer system.
server or the
wrong information
Updates to the list of monitoring servers and
is configured for a
their user name and password can be made
monitoring server.
using $EVENT_SYNC_INSTALLDIR/bin/
sitconfuser.sh (UNIX) or sitconfuser.cmd
(Windows). The Situation Update Forwarder
must be restarted using
$EVENT_SYNC_INSTALLDIR/bin/stopSUF.sh
(UNIX) or stopSUF.cmd (Windows) and then
startSUF.sh (UNIX) or startSUF.cmd
(Windows) after any changes are made.
If a monitoring server is not listed in the
situser.conf file, use the sitconfuser
command to add the monitoring server.
If a monitoring server is listed in the
situser.conf file, it may have the wrong
form of the host name. If just the host name
is listed (for example, server1), use the
sitconfuser command to add the fully
qualified host name (for example,
server1.ibm.com) and vice versa.
If the monitoring server user name or
password have changed recently, use the
sitconfuser command to update the
monitoring server's information.
See the IBM Tivoli Monitoring Command
Reference for details on the syntax of the
sitconfuser command.
Chapter 14. Event synchronization troubleshooting
Log files to check
Look for "Invalid
Tivoli Enterprise
Monitoring Server"
lines in the Situation
Update Forwarder log
file.
237
Advertisement
Table of Contents
Troubleshooting
