Table 20. Event status updates in Netcool/OMNIbus are not forwarded to Tivoli
Monitoring (continued)
Possible cause Resolution Log files to check
The IBM Tivoli
Monitoring
Situation Update
Forwarder is not
configured to send
status updates to a
hub monitoring
server or the
wrong information
is configured for a
monitoring server.
Review the monitoring servers that are
configured in the Situation Update Forwarder
$EVENT_SYNC_INSTALLDIR/etc/situser.conf
file, where $EVENT_SYNC_INSTALLDIR is
the directory where the Event
Synchronization component is installed on
the Netcool/OMNIbus ObjectServer system.
Updates to the list of monitoring servers and
their user name and password can be made
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.
Look for “Invalid
Tivoli Enterprise
Monitoring Server”
lines in the Situation
Update Forwarder log
file.
Chapter 14. Event synchronization troubleshooting 237
To Next Page
Loading...
Need help?
General
