IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

EIF Information

The following sections describe procedures to assist in creating a high-availability setup using the EIF (Event Integration Facility).


EIF event synchronization with hot standby

To set up event synchronization from the Tivoli Enterprise Console or OMNIbus for a hub monitoring server with hot standby, you must configure the event synchronization to send updates to the secondary monitoring server equipped with hot standby. This setup can be done during the initial installation of event synchronization, or by entering a command at the command-line interface after installation.

For event synchronization with Netcool/OMNIbus, enter the sitconfuser.cmd (for Windows systems) or sitconfuser.sh (for UNIX systems) command in the command line interface. The following example displays the command to add the itm17 monitoring server on a UNIX system:

For more information about the sitconfuser.sh command, see Chapter 4 of the Command Reference.

For event synchronization with the Tivoli Enterprise Console, enter the sitconfsvruser.sh command in the command line interface. The following example displays the command to add the itm17 monitoring server:

For more information about the sitconfsvruser.sh command, see Chapter 3 of the Command Reference.


EIF event synchronization with a clustered monitoring server

There should not be a need for configuration changes in the EIF Event Synchronization setup from the Tivoli Enterprise Console and OMNIbus if you have a clustered monitoring server.

In a Hot Standby environment, the user ID and password for SUF (Situation Update Forwarder) must be defined to both the acting hub and the standby hub.


EIF event forwarding with multiple event destinations

A user can set up multiple event destinations from the command line interface, and can forward events to multiple event destinations using the tacmd createeventdest command to designate additional default event destinations.

The event destination specified during the initial installation and configuration is automatically designated as the default event destination and given id=0, so a different number must be chosen for the id property of any subsequent default event destinations. After a user has specified multiple event destinations, any events that do not have designated event destinations specified (using the TDST= parameter in the SITINFO column of the situation definition) will be forwarded to all designated default event destinations.

The following example displays the code used to define an additional default event destination with an ID of "2".

For more information on the tacmd createeventdest command, see to the Command Reference at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2/itm_cmdref.pdf.


Scenarios for setting up multiple EIF destinations

If you are managing a cluster environment, see EIF event forwarding with multiple event destinations to set up multiple event destinations using the tacmd createeventdest command. For a Hot Standby environment, the event destination table is not currently automatically replicated, so the tacmd createeventdest command must be used to define the same event destinations for both the acting hub monitoring server and the standby hub monitoring server.

+

Search Tips   |   Advanced Search