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
Clustered portal server
When the portal server is clustered and failover or failback occurs, the connected Tivoli Monitoring components operate as if the portal server has been restarted. The components that connect to the portal server include the portal consoles and the Summarization and Pruning Agent (at the start of its summarization and pruning interval).
When a portal client loses connection to the portal server, the user is notified and some views become unavailable. When the portal client reestablishes connection with the portal server, the home workspace is displayed and the Navigator refreshes.
If the Summarization and Pruning Agent is connected to the portal server at the time of portal server failover, it loses the connection and attempts to reestablish contact on the next Summarization and Pruning Agent interval.
Parent topic:
What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment