IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Agent Installation Guides > Windows Agent Installation Guide > Agent installation and configuration
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Set up the agent in a cluster environment
You can install and set up the monitoring agent in a Microsoft Cluster Server environment by following these instructions.
The IBM Tivoli Monitoring Installation and Setup Guide contains an overview of clustering. This agent monitors information that is both affected (shared disks, processes …), and not affected (memory, CPU …) by cluster resources as the resources are failed over from node to node in the cluster. Therefore, the agent actively runs on all nodes in the cluster. The agent was not modified to distinguish the differences between cluster affected and non-affected resources. History for those attributes that can move from node to node is only maintained for the time that the node owns the resource.
Resources not currently owned by the node might not show at all or may show with values of zero. In most cases the information is not shown on the node that does not own the resource. The physical disk attributes are examples of a monitored resource. The node that does not own the resource shows the disk but the attributes value as Zero while the logical disk information and attributes are only shown by the owning node. When the logical disk fails over, the system interface and the agent require an amount of time to discover the fail over.
Monitor the system log for cluster services entries by specifying the following values:
- The Attribute Group equal to NT_Event_Log
- Attribute Item: Log Name (Unicode) equal to System (case sensitive)
- Attribute Item: Source equal to source of the log entry, for example ClusSvc
- Attribute Item: Category equal to source of the log entry, for example Failover Mgr
- Attribute Item: Event ID equal to the desired cluster eventID, for example:
- 1201 - the cluster service brought the resource group online
- 1204 - the cluster service brought the resource group offline
Parent topic:
Agent installation and configuration