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
Situations
Situations might be affected by failures on the hub, the remote monitoring server, and at the agent. During a hub cluster failover, situations are affected in the same way as a restart of the hub or a disconnection of the hub from the other components.
When a remote monitoring server loses connection with the hub and then reestablishes contact, the server synchronizes after reconnection. This process involves restarting all the situations under that remote monitoring server’s responsibility. Polled situations are triggered on the next polling interval, but pure events that were opened before the failure are lost. Use an event management product, such as Tivoli NetCool/OMNIbus or Tivoli Enterprise Console, as the focal point for storing and manipulating historical events from all event sources.
If you have agents directly connected to the hub, the situations distributed to them are stopped when connection is lost, and the situations are restarted when the agent reconnects to the hub. This behavior also applies for agents that are connected to a remote monitoring server and lose connection to it.
Parent topic:
What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment