IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > The clustering of IBM Tivoli Monitoring components > What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Console event integration
When Tivoli Monitoring is configured to forward events to the Tivoli Enterprise Console event server, it sends a “MASTER_RESET” event to the event server every time the hub is restarted. This behavior also occurs after failover or failback for a clustered hub. The purpose of this event is to signal to the event server that the monitoring server restarted all its situations and that the event server receives a new set of currently triggered situations. As a result of the default Tivoli Enterprise Console rule for Tivoli Monitoring integration, all the events that came from the hub Tivoli Enterprise Monitoring server are closed. Although this closing of events ensures that both Tivoli Monitoring and Tivoli Enterprise Console have consistent triggered situations and events, this behavior might not be desirable in some environments. For example, this behavior closes pure events that are not reopened until the next pure event occurs. In such cases, you can filter out the MASTER_RESET event either at the hub (event integration facility configuration file) or at the event server using the Tivoli Enterprise Console rules. In this case, the rules must process duplicate events caused by the restarted situations.
Parent topic:
What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment