User's Guide: Ivo I

Tivoli IBM Tivoli Composite Application Manager for Microsoft
Applications: Microsoft Cluster Server Agent
Version 6.2.2
User's Guide
SC27-2316-02
Tivoli IBM Tivoli Composite Application Manager for Microsoft

Applications: Microsoft Cluster Server Agent
Version 6.2.2
User's Guide
SC27-2316-02
Note
Before using this information and the product it supports, read the information in Appendix E, Notices, on page 291.
This edition applies to version 6.2.2 of IBM Tivoli Composite Application Manager for Microsoft Applications:
Microsoft Cluster Server Agent (product number 5724-U17) and to all subsequent releases and modifications until
otherwise indicated in new editions.
Copyright IBM Corporation 2007, 2010.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . vii
Chapter 1. Overview of the Microsoft
Cluster Server Agent . . . . . . . . . 1
IBM Tivoli Monitoring overview . . . .
Features of the monitoring agent . . .
Functions of the monitoring agent . . .
New in this release . . . . . . . .
Components of the IBM Tivoli Monitoring
environment . . . . . . . . . .
Agent Management Services . . . . .
User interface options . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
1
2
.
.
.
.
.
.
.
.
.
. 4
. 4
. 4
Chapter 2. Agent-specific installation

and configuration information for the
monitoring agent . . . . . . . . . . . 7
Installing language packs . . . . . . . . . . 7
Windows systems. . . . . . . . . . . . 7
UNIX or Linux systems. . . . . . . . . . 7
Agent-specific installation and configuration. . . . 8
Configuring the monitoring agent after installation 10
Configuration values . . . . . . . . . . 10
Remote installation and configuration . . . . 11
Chapter 3. Workspaces reference . . . 13

About workspaces . . . . . . . . . . .
More information about workspaces . . . . .
Cross-Linked Workspaces. . . . . . . . .
Predefined workspaces . . . . . . . . .
Agent Navigator items . . . . . . . . .
Microsoft Cluster Server Agent Navigator item
Availability Navigator item . . . . . . .
Cluster Dashboard Navigator item. . . . .
Configuration Navigator item . . . . . .
Event Log Navigator item . . . . . . .
Network Interfaces Navigator item . . . .
Networks Navigator item. . . . . . . .
Nodes Navigator item . . . . . . . . .
Resource Groups Navigator item . . . . .
Resources Navigator item . . . . . . .
Structural and Degradation Risk Navigator item
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
13
14
14
15
15
16
17
18
19
19
20
21
23
23
24
Chapter 4. Attributes reference . . . . 27

About attributes . . . . . . . . . . . .
More information about attributes . . . . . .
Attribute groups and attributes for the Microsoft
Cluster Server Agent . . . . . . . . . .
Availability attribute group . . . . . . . .
Cluster Domain attribute group . . . . . .
Cluster Shared Volume attribute group . . . .
Cluster Shared Volume IO attribute group . . .
Cluster Summary attribute group . . . . . .
Configuration attribute group . . . . . . .
CPU Interrupts Rollup attribute group . . . .
Copyright IBM Corp. 2007, 2010
. 27
. 27
.
.
.
.
.
.
.
.
27
31
36
36
39
43
48
50
CPU per Node attribute group . . . . . . . . 52

CPU per Node Rollup attribute group . . . . . 54
Degradation Risk attribute group . . . . . . . 56
Disk attribute group . . . . . . . . . . . 60
Disk MB Rollup attribute group . . . . . . . 64
Disk PCT Rollup attribute group . . . . . . . 66
Enterprise Cluster Summary attribute group . . . 68
Event Log attribute group . . . . . . . . . 74
Global Update Messages attribute group . . . . 77
Memory attribute group . . . . . . . . . . 78
Memory MB Rollup attribute group . . . . . . 83
Memory PCT Rollup attribute group . . . . . . 85
MRR Messages attribute group . . . . . . . . 87
Network Interfaces attribute group . . . . . . 88
Network Interfaces State Rollup attribute group . . 91
Network Performance attribute group . . . . . 93
Network Performance Packets Rollup attribute
group . . . . . . . . . . . . . . . . 98
Network Performance Received Rollup attribute
group . . . . . . . . . . . . . . . . 100
Network Performance Sent Rollup attribute group 102
Network Reconnections attribute group . . . . 104
Networks attribute group . . . . . . . . . 105
Networks Messages attribute group . . . . . . 107
Networks Rollup attribute group . . . . . . . 110
Node To Active Group attribute group . . . . . 112
Nodes attribute group . . . . . . . . . . 115
Nodes State Rollup attribute group . . . . . . 117
Performance Object Status attribute group . . . . 119
Quorum Configuration attribute group . . . . . 124
Resource Control Manager attribute group . . . 126
Resource Group Moves attribute group. . . . . 128
Resource Group To Preferred Node attribute group 129
Resource Group To Resource attribute group . . . 131
Resource Groups attribute group . . . . . . . 133
Resource Groups State Rollup attribute group . . 137
Resource To Dependent Resource attribute group
139
Resource To Possible Owner attribute group . . . 141
Resources attribute group . . . . . . . . . 143
Resources State Rollup attribute group . . . . . 147
Resources Summary attribute group . . . . . . 149
Shared Storage Summary attribute group . . . . 152
Structural Risk attribute group . . . . . . . 154
Thread Pool Status attribute group . . . . . . 156
Disk capacity planning for historical data . . . . 161
Chapter 5. Situations reference. . . . 165

About situations . . . . . . . . . .
More information about situations . . . .
Predefined situations . . . . . . . . .
Availability Navigator item . . . . . . .
KQ5_Process_Down situation . . . . .
KQ5_WMI_Obj_Not_Available situation .
Cluster Dashboard Navigator item . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
165
165
166
167
167
167
168
169
iii
KQ5_MSCS_PMemory_Free_Warn situation .
KQ5_MSCS_PMemory_Free_Crit situation . .
KQ5_MSCS_PNW_Utilization_Warn situation
KQ5_MSCS_PNW_Utilization_Crit situation .
KQ5_MSCS_PCPU_Utilization_Warn situation
KQ5_MSCS_PCPU_Utilization_Crit situation
Configuration Navigator item . . . . . . .
Event Log Navigator item . . . . . . . .
Network Interfaces Navigator item . . . . .
KQ5_MSCS_InterfaceStateUnknown situation
KQ5_MSCS_InterfaceStateUnavail situation .
KQ5_MSCS_InterfaceStateDown situation . .
KQ5_MSCS_InterfaceStateUnreach situation .
Networks Navigator item . . . . . . . .
KQ5_MSCS_Network_StateUnknown situation
KQ5_MSCS_Network_StateUnavail situation
KQ5_MSCS_Network_StateDown situation .
KQ5_MSCS_Network_StateUnreach situation
Nodes Navigator item . . . . . . . . .
KQ5_MSCS_Node_Unknown situation . . .
KQ5_MSCS_Node_Paused situation . . . .
KQ5_MSCS_Node_Down situation . . . .
KQ5_MSCS_Cluster_Unbalanced situation . .
KQ5_MSCS_QrmDiskSpace_Warning situation
KQ5_MSCS_QrmDiskSpace_Critical situation
Resource Groups Navigator item . . . . . .
KQ5_MSCS_RG_Failed situation . . . . .
KQ5_MSCS_RG_Offline situation . . . . .
KQ5_MSCS_RG_PartiallyOnLine situation . .
KQ5_MSCS_RG_Unknown situation. . . .
KQ5_MSCS_Node_Changed situation . . .
Resources Navigator item . . . . . . . .
KQ5_MSCS_Resource_Failed situation . . .
KQ5_MSCS_Resource_Offline situation . . .
KQ5_MSCS_Resource_Pending situation . .
KQ5_MSCS_Resource_Pending_On situation
KQ5_MSCS_Resource_Pending_Off situation
KQ5_MSCS_Resource_Unknown situation . .
KQ5_MSCS_Resource_Initializing situation .
KQ5_MSCS_Resource_Inherited situation . .
. 169
. 169
170
. 170
171
172
. 172
. 172
. 172
172
. 173
. 174
. 174
. 175
175
175
. 176
177
. 177
. 177
. 178
. 178
. 179
180
180
. 181
. 181
. 181
. 182
. 183
. 183
. 184
. 184
. 184
. 185
186
186
. 187
. 187
. 188
188
Chapter 6. Take Action commands

reference . . . . . . . . . . . . . 189
About Take Action commands. . . . . . .
More information about Take Action commands
Predefined Take Action commands . . . . .
Bring Resource Group online action . . . . .
Bring Resource online action . . . . . . .
Take Resource Group offline action . . . . .
Take Resource offline action . . . . . . .
. 189
189
. 189
. 190
. 191
. 192
. 193
Chapter 7. Policies reference. . . . . 195

About policies . . . . . . .
More information about policies .
Predefined policies . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 195
. 195
. 195
Chapter 8. Tivoli Common Reporting

for the monitoring agent . . . . . . 197
Category 1: Performance reports .
iv
Microsoft Cluster Server Agent: User's Guide
. 199
Disk Utilization for Cluster Nodes report . . .

Memory Utilization for Cluster Nodes report
Cluster Hardware Interrupts report . . . . .
CPU Utilization for Cluster Nodes report . . .
Network Interface Activity for Single Cluster
Node report . . . . . . . . . . . . .
Resources Utilization Details for Single Node
report . . . . . . . . . . . . . . .
Resource Utilization Comparison for All Nodes
on Single Cluster report . . . . . . . . .
Cluster Nodes Utilization Summary report . .
Cluster Utilization Summary report . . . . .
Daily Heat Map for Cluster Nodes report . . .
Utilization Heat Map for Single Resource report
Generic Template report . . . . . . . . .
Generic Details Template report . . . . . .
Category 2: Availability reports . . . . . . .
Cluster Nodes Availability report . . . . . .
Cluster Network Interface Availability report
Cluster Resource Group Availability report . .
Cluster Resource Availability report . . . . .
Cluster Network Availability report . . . . .
199
200
201
202
203
204
205
206
208
209
210
210
212
214
214
214
215
216
216
Chapter 9. Troubleshooting . . . . . 219

Gathering product information for IBM Software
Support . . . . . . . . . . . . . .
Built-in troubleshooting features . . . . . .
Problem classification. . . . . . . . . .
Trace logging . . . . . . . . . . . .
Overview of log file management . . . .
Principal trace log files . . . . . . . .
Setting RAS trace parameters . . . . . .
Problems and workarounds . . . . . . .
Installation and configuration troubleshooting
Remote deployment troubleshooting . . .
Agent troubleshooting . . . . . . . .
Workspace troubleshooting . . . . . . .
Situation troubleshooting . . . . . . .
Take Action commands troubleshooting . .
Tivoli Common Reporting troubleshooting .
Support information . . . . . . . . . .
Informational, warning, and error messages . .
Message format . . . . . . . . . .
Microsoft Cluster Server Agent messages . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
219
219
220
220
220
221
223
225
225
230
232
235
242
246
246
249
249
249
250
Appendix A. IBM Tivoli Enterprise

Console event mapping . . . . . . . 253
Appendix B. Discovery Library
Adapter for the monitoring agent . . . 275
About the DLA. . . . . . .
More information about DLAs. .
Book Information . . . . . .
Microsoft Cluster Server DLA data
types represented in CDM . . .
Relationships . . . . . .
MsCluster class. . . . . .
MsClusterNode class . . . .
MsClusterResourceGroup class
MsClusterResource class. . .
. . . .
. . . .
. . . .
model class
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
.
.
.
. 275
. 275
. 275
.
.
.
.
.
.
.
.
.
.
.
.
276
276
278
278
279
280
MsClusterService class .
TMSAgent class . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 281
. 282
Navigating the interface using the keyboard .

Magnifying what is displayed on the screen .
285
Appendix E. Notices . . . . . . . . 291
.
.
.
.
.
.
.
.
Trademarks .
Appendix C. Documentation library

Microsoft Cluster Server Agent library
Prerequisite publications. . . . .
Related publications . . . . . .
Other sources of documentation . .
.
.
.
.
.
.
.
.
.
.
.
.
285
285
286
286
.
.
. 289
. 289
. 293
Index . . . . . . . . . . . . . . . 295
Appendix D. Accessibility . . . . . . 289
Contents
vi
Tables
1.
2.
3.
4.
5.
6.
7.
8.
Cross-linked workspaces within the Microsoft

Cluster Server agent . . . . . . . . . 14
Cross-linked Workspaces to the Microsoft
Hyper-V Server agent . . . . . . . . . 14
Cross-linked Workspaces to Windows OS
agent. . . . . . . . . . . . . . . 14
Capacity planning for historical data logged
by Microsoft Cluster Server Agent . . . . 161
Supported databases . . . . . . . . . 197
Information to gather before contacting IBM
Software Support . . . . . . . . . . 219
Trace log files for troubleshooting agents
221
Problems and solutions for installation and
configuration . . . . . . . . . . . 225
9.
10.
11.
12.
13.
14.
15.
16.
17.
General problems and solutions for

uninstallation . . . . . . . . . . .
Remote deployment problems and solutions
Agent problems and solutions . . . . . .
Workspace problems and solutions . . . .
General situation problems and solutions
Problems with configuring situations that you
solve in the Situation Editor . . . . . .
Problems with configuration of situations that
you solve in the Workspace area . . . . .
Take Action commands problems and
solutions . . . . . . . . . . . . .
Tivoli Common Reporting for Microsoft
Cluster Server Agent problems and solutions .
228
230
232
236
243
244
246
246
247
vii
viii
Chapter 1. Overview of the Microsoft Cluster Server Agent

The IBM Tivoli Composite Application Manager (ITCAM) for Microsoft
Applications: Microsoft Cluster Server Agent software provides you with the
capability to monitor Microsoft Cluster Server, and to perform basic actions with
Microsoft Cluster Server. This chapter provides a description of the features,
components, and interface options for the Microsoft Cluster Server Agent.
IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Microsoft Cluster Server Agent.
IBM Tivoli Monitoring provides a way to monitor the availability and performance
of all the systems in your enterprise from one or several designated workstations.
It also provides useful historical data that you can use to track trends and to
troubleshoot system problems.
You can use IBM Tivoli Monitoring to perform the following tasks:
v Monitor for alerts on the systems that you are managing by using predefined
situations or custom situations.
v Establish your own performance thresholds.
v Trace the causes leading to an alert.
v Gather comprehensive data about system conditions.
v Use policies to perform actions, schedule work, and automate manual tasks.
The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. By
providing a consolidated view of your environment, the Tivoli Enterprise Portal
permits you to monitor and resolve performance issues throughout the enterprise.
See the IBM Tivoli Monitoring publications listed in Prerequisite publications on
page 285 for complete information about IBM Tivoli Monitoring and the Tivoli
Enterprise Portal.
Features of the monitoring agent

The Microsoft Cluster Server Agent software can identify, notify you of, and correct
common problems with the application that it monitors. The software includes the
following features:
v Monitoring
v Data gathering
v Operations management
Functions of the monitoring agent

The Microsoft Cluster Server Agent provides the following functions:
Availability and resource monitoring
Monitors availability for Cluster and Cluster resources
Error/event log Monitoring
Monitor for all events in the MSCS log. No specific situations are planned
for the log monitoring.
Performance monitoring
MSCS does not currently keep Cluster performance attributes
Reporting
Provides a history enablement file that enables the agent to generate
reports for all metrics that are collected.
Cluster Resource Availability
Provides availability monitoring for the cluster servers key monitoring
points: cluster level, cluster nodes, cluster resource groups, cluster
resources, and cluster networks.
Cluster Resources Usage
Provides cluster resource usage across the nodes of the cluster and reports
threats in capacity availability for processor, memory, disk, and networks.
Cluster Dashboard
Provides information about cluster shared volume (CSV), cluster shared
volume I/O, and cluster summary for all clusters in an organization. The
cluster dashboard also provides information about processor utilization
and the utilization of shared storage summary.
Take Actions
Actions are provided to take resource, and the resource group offline and
to take it online.
New in this release

For version 6.2.2 of the Microsoft Cluster Server Agent, the following
enhancements have been made since version 6.2.0 Interim Feature 1:
v Additional supported operating systems as listed in the Microsoft Cluster Server
agent prerequisites topic on the IBM Tivoli Monitoring for Microsoft
Applications Information Center.
v New attribute groups
Cluster Shared Volume
Cluster Shared Volume IO
Cluster Summary
Global Update Messages

MRR Messages
Networks Messages
Network Reconnections
Resource Control Manager
Resources Summary
Resource To Dependent Resource
Shared Storage Summary

v New or changed attributes in the following attribute groups
Event Log
Network Performance
v New workspaces
Enterprise Level Cluster Dashboard
Cluster Dashboard
Network Messages
Resources Summary
v Updated workspaces
Network performance
Event Log
v New views
Bytes Sent/Received
Cluster Capacity Details
Cluster Shared Storage
Enterprise Level Cluster Capacity
IO Read Bytes
IO Write Bytes
Message Queue Status
Messages Sent/Received
Network Messages Sent/Received
Quorum Usage
Resources Summary
Resource To Dependent Resource
Resources Online
System Processor Usage
System Memory Usage
Shared Storage Usage
Top 5 Cluster Systems Having High Processor Usage

Top 5 Cluster Systems Having High Memory Usage
Top 5 Clusters Having High Quorum Usage
Top 5 Clusters Having High Shared Storage Usage
v New situations
KQ5_MSCS_PMemory_Free_Warn
KQ5_MSCS_PMemory_Free_Crit
KQ5_MSCS_PNW_Utilization_Warn
KQ5_MSCS_PNW_Utilization_Crit
KQ5_MSCS_PCPU_Utilization_Warn
KQ5_MSCS_PCPU_Utilization_Crit
v New Take Action commands
Bring Resource Online
Take Resource Offline
Bring Resource Group Online
Take Resource Group Offline
v Updated kq5.baroc file to support TEC event mapping
v Integration with Agent Management Services to monitor the availability of the
agent. Support for Agent Management Services is available on IBM Tivoli
Monitoring V6.2.2, Fix Pack 1, or later.
v Support for native 64-bit agent.

v Integration with IBM Tivoli Application Dependency Discovery Manager
(TADDM).
Components of the IBM Tivoli Monitoring environment

After you install and set up the Microsoft Cluster Server Agent, you have an
environment that contains the client, server, and monitoring agent implementation
for IBM Tivoli Monitoring. This environment contains the following components:
v Tivoli Enterprise Portal client with a Java-based user interface for viewing and
monitoring your enterprise.
v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli
Enterprise Monitoring Server and enables retrieval, manipulation, and analysis
of data from the monitoring agents. The Tivoli Enterprise Portal Server is the
central repository for all user data.
v Tivoli Enterprise Monitoring Server that acts as a collection and control point for
alerts received from the monitoring agents, and collects their performance and
availability data. The Tivoli Enterprise Monitoring Server is also a repository for
historical data.
v IBM Tivoli Enterprise Console is an optional component, which acts as a central
collection point for events from a variety of sources, including events from other
Tivoli software applications, Tivoli partner applications, custom applications,
network management platforms, and relational database systems. You can view
these events through the Tivoli Enterprise Portal (using the event viewer), and
you can forward events from IBM Tivoli Monitoring situations to the IBM Tivoli
Enterprise Console component.
v IBM Tivoli Netcool/OMNIbus is an optional component and an alternative to
the IBM Tivoli Enterprise Console. The Netcool/OMNIbus software is a service
level management (SLM) system that delivers real-time, centralized monitoring
of complex networks and IT domains. The Tivoli Netcool/OMNIbus components
work together to collect and manage network event information.
v Tivoli Common Reporting is a separately installable feature available to users of
Tivoli software that provides a consistent approach to generating and
customizing reports. Some individual products provide reports that are designed
for use with Tivoli Common Reporting, and have a consistent look and feel.
Agent Management Services

Microsoft Cluster Server Agent can be managed by IBM Tivoli Monitoring Agent
Management Services. These services are available in the following IBM Tivoli
Monitoring OS agents: Windows, Linux, and UNIX. The services are designed to
keep Microsoft Cluster Server Agent available, and to provide information about
the status of the product to the Tivoli Enterprise Portal. Support for Agent
Management Services is available on IBM Tivoli Monitoring V6.2.2, Fix Pack 1 or
later. For more information about Agent Management Services, see the IBM Tivoli
Monitoring Administrator's Guide.
User interface options

Installation of the base software and other integrated applications provides the
following interfaces that you can use to work with your resources and data:
Tivoli Enterprise Portal browser client interface
The browser client interface is automatically installed with the Tivoli
Enterprise Portal Server. To start the Tivoli Enterprise Portal browser client
in your Internet browser, enter the URL for a specific Tivoli Enterprise
Portal browser client installed on your Web server.
Tivoli Enterprise Portal desktop client interface
The desktop client interface is a Java-based graphical user interface (GUI)
on a Windows or Linux workstation.
Manage Tivoli Enterprise Monitoring Services window
The window for the Manage Tivoli Enterprise Monitoring Services utility is
used for configuring the agent and starting Tivoli services not designated
to start automatically.
IBM Tivoli Enterprise Console
An event management application that integrates system, network,
database, and application management to help ensure the optimal
availability of an IT service for an organization.
Tivoli Netcool/OMNIbus event list
You can use the event list to monitor and manage alerts. An alert is created
when the ObjectServer receives an event, alarm, message, or data item.
Each alert is made up of columns (or fields) of information that are held in
a row in the ObjectServer alerts.status table. In addition, the Tivoli
Netcool/OMNIbus Web GUI is a Web-based application that processes
network events from one or more data sources and presents the event data
in various graphical formats.
Tivoli Common Reporting
A Web user interface for specifying report parameters and other report
properties, generating formatted reports, scheduling reports, and viewing
reports. The user interface is based on the Tivoli Integrated Portal.
Chapter 2. Agent-specific installation and configuration

information for the monitoring agent
Before installing and configuring the agent, make sure your environment meets the
requirements for the Microsoft Cluster Server Agent. See the Prerequisites topic for
the agent on the IBM Tivoli Monitoring for Microsoft Applications Information
Center at https://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/
index.jsp?topic=/com.ibm.itmfms.doc/welcome.htm.
To install and configure the Microsoft Cluster Server Agent, use the procedures for
installing monitoring agents in the IBM Tivoli Monitoring Installation and Setup
Guide along with the agent-specific information in this chapter.
If you are performing a silent installation using a response file, see the information
about performing a silent installation in the IBM Tivoli Monitoring Installation and
Setup Guide.
Installing language packs

To install a language pack, first make sure that you have already installed the
product in English. Then perform the following steps depending on which
operating system you are using.
Windows systems
1. Double-click lpinstaller.bat in the language pack CD to launch the installation
program.
2.
3.
4.
5.
Select the language of the installer and click OK.

Click Next on the Introduction panel.
Click Add/Update and click Next.
Select the folder in which the National Language Support package
(NLSPackage) files are located.
Note: Usually the NLSPackage files are located in the nlspackage folder where
the installer executable is located.
6. Select the language support for the agent of your choice and click Next.
Note: Hold down the Ctrl key for multiple selections.
7. Select the languages that you want to install and click Next.
8. Examine the installation summary page and click Next to begin installation.
9. Click Finish after installation completes to exit the installer.
10. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server
component, and Eclipse Help Server if any of these components are installed.
UNIX or Linux systems

1. Run the following command to create a temporary directory on the computer.
Make sure that the full path of the directory does not contain any spaces:
mkdir dir_name
2. Mount the language pack CD to the temporary directory you just created.
3. Run the following command to launch the installation program:

cd dir_name
lpinstall.sh ITM Home Directory
4.
5.
6.
7.
Where ITM Home Directory is where you installed IBM Tivoli Monitoring.
Usually it is /opt/IBM/ITM for AIX and Linux.
Select the language of the installer and click OK.
Click Next on the Introduction panel.
Click Add/Update and click Next.
Select the folder in which the National Language Support package
(NLSPackage) files are located.
Note: Usually, the NLSPackage files are located in the nlspackage folder where
the installer executable is located.
8. Select the language support for the agent of your choice and click Next.
Note: Hold down the Ctrl key for multiple selections.
9. Select the languages that you want to install and click Next.
10. Examine the installation summary page and click Next to begin installation.
11. Click Finish after installation completes to exit the installer.
12. Restart the Tivoli Enterprise Portal (if on the Tivoli Enterprise Portal Server) or
restart the Tivoli Enterprise Portal Server (if on the Tivoli Enterprise Portal
Server component).
Agent-specific installation and configuration

In addition to the installation and configuration information in the IBM Tivoli
Monitoring Installation and Setup Guide, use the information in this section to install
and configure the Microsoft Cluster Server Agent.
The agent must be installed and configured in the same way on all nodes in the
cluster. This ensures that the node controls the active agent and the agents cluster
resource. When installing for the first time, go through the installation procedures
found in the IBM Tivoli Monitoring Installation and Setup Guide before creating the
cluster resources. When applying fix packs to multiple nodes, bring the resource
group offline before applying the fix packs, and then bring the resource group back
online.
The starting and stopping of the agent is controlled by the cluster server. Using
IBM Tivoli Monitoring v6.2.1 utilities to manage the agent (start, stop, restart,
remove, configure) conflicts with the cluster server control of the agent. When
using the IBM Tivoli Monitoring v6.2.1 utilities to manage the agent take the
cluster agent resource offline. This ensures that the cluster server does not
automatically restart the agent when the IBM Tivoli Monitoring v6.2.1 utility needs
the agent to be offline. See the Troubleshooting chapter of this document for
related behaviors.
Use the Microsoft Cluster Administrator to create a resource group and resource
to control the agent.
When creating the agent resource group, specify the name and description you
want to use to identify the agent. Use the same preferred nodes sequence as set for
the cluster group controlling the cluster resources.
If agent history is stored at the Tivoli Enterprise Monitoring Agent, a shared disk
resource must be created to store agent history. This disk resource must be added
to the agents resource group so that the node owning the agent resource group
can access the disk.
For Windows 2003 based systems create a generic service cluster resource in the
cluster agent resource group by completing the following steps:
1. Right -click the agent resource group created for the agent, select New, and
then select Resource.
2. Select Generic Service Resource Type and specify a name for the agent
resource.
3. Take the defaults of all possible owners, which should be all nodes in the
cluster.
4. If history is stored at the agent you must create a shared disk resource that is
set as a resource dependency.
5. Specify the service name as kq5cma (the service for: Monitoring Agent for
Microsoft Cluster Server Agent).
6. Take the defaults for all the other settings.
For Windows 2008 based systems create a generic service cluster resource in the
cluster agent resource group by completing the following steps:
1.
2.
3.
4.
Click Configure and select Configure a Service or Application.

Click Next on the High Availability Wizard page.
Select Generic Service and Click Next.
Select Agent Service and Click Next.
5. Type the appropriate details in Service Name and IP address fields.

6. Select Storage.
7. Select Replicate Registry Settings.
8. Select Confirmation.
9. Select Configure High Availability.
10. Select Summary to get the details.
Each node in the cluster has a single instance of the agent installed. Each instance
must be configured in the same way. Use Manage Tivoli Monitoring Services to
configure and set startup agent parameters.
In addition to the standard agent configuration, two parameters that are unique to
the agent are specified :
v
v
Microsoft Cluster Name (Environment variable CTIRA_HOSTNAME)

Shared Agent History Directory (Environment variable CTIRA_HIST_DIR)
The Microsoft Cluster Name configuration parameter is used to create the

Windows system name that appears in the Tivoli Enterprise Portal. The Microsoft
Cluster Name configuration is used to set CTIRA_HOSTNAME, which is the
hostname part of the managed system name. The Managed System Status
workspace of the enterprise view shows the status of each managed system. Note
that this name is case sensitive and must be entered the same way on each node's
agent configuration. Also, use only ASCII characters.
The Shared Agent History Directory field is required if the history configuration
specifies that the collection location is at the Tivoli Enterprise Monitoring Agent.
Chapter 2. Agent-specific installation and configuration information for the monitoring agent
History is then stored on the agent on the shared disk. The Shared Agent History
Directory configuration parameter, CTIRA_HIST_DIR, specifies a directory on a
shared disk controlled by the agent resource group. On the shared disk, create a
directory to store the history because the agent does not create the directory.
For cluster systems that do not support shared disks, history must be stored on the
Tivoli Enterprise Monitoring Server. If history is stored on the Tivoli Enterprise
Monitoring Server, ensure that you select the amount of data so that you do not
overrun the Tivoli Enterprise Monitoring Server. For more information, see the
Disk capacity planning for historical data section in this document.
The agent defaults to a startup type of manual and Log on As system account. The
account that the agent runs under needs to be changed to have authority to use
remote WMI queries. This will help access system attributes like CPU Utilization
across all nodes in the cluster.
The cluster administrator ID, with a format domain_name\administrator_id, is an
example of a user ID that could be used.
Configuring the monitoring agent after installation

In addition to the installation and configuration information in the IBM Tivoli
Monitoring Installation and Setup Guide, use the information in this section to install
and configure the Microsoft Cluster Server Agent.
Configuration values
For both local and remote configuration, provide the configuration values for the
agent to operate. When configuring an agent, a panel is displayed so you can enter
each value. When there is a default value, this value is pre-entered into the field. If
a field represents a password, two entry fields are displayed. You must enter the
same value in each field. The values you type are not displayed to help maintain
the security of these values.
The configuration for this agent is organized into the following groups:
Microsoft Cluster Server Agent Configuration (MSCS)
Null Description for section.
The configuration elements defined in this group are always present in the
agent's configuration.
This group defines information that applies to the entire agent.
Shared Agent History Directory
A shared directory for the cluster that is not a quorum drive where
the agents can locate cluster historical information.
You must not perform any I/O operations while the cluster
operation runs on the quorum disk. If you run a different I/O
operation at the same time, then the operation can interfere with
the cluster operation and the quorum resource can fail. The entire
cluster fails if the quorum resource fails. Therefore, you must create
a separate physical disk to store historical information.
The type is string.
This value is optional.
defaultValue(null)
10
Microsoft Cluster Name

A unique name assigned to the cluster that will be displayed in the
Tivoli Enterprise Portal.
The type is string.
This value is required.
defaultValue(null)
Remote installation and configuration

When installing the agent remotely, you must provide the configuration values for
the agent to operate. See Configuration values on page 10.
See the tacmd describeSystemType section in the IBM Tivoli Monitoring Command
Reference for information on displaying the configuration options that are available
to use with the configureSystem or addSystem commands.
You can install the monitoring agent remotely from the Tivoli Enterprise Portal or
from the command line. To install from the portal, see the IBM Tivoli Monitoring
Installation and Setup Guide.
If using the command line, the following command is an example of remote
configuration for Windows operating systems:
tacmd addSystem -t Q5 -n Primary:sample.node.name:NT
-p MSCS.CTIRA_HIST_DIR=value
MSCS.CTIRA_HOSTNAME=value
Chapter 2. Agent-specific installation and configuration information for the monitoring agent
11
12
Chapter 3. Workspaces reference

This chapter contains an overview of workspaces, references for detailed
information about workspaces, and descriptions of the predefined workspaces
included in this monitoring agent.
About workspaces
A workspace is the working area of the Tivoli Enterprise Portal application
window. At the left of the workspace, is a Navigator that you use to select the
workspace you want to see. As part of the application window, the right side of
the status bar shows the Tivoli Enterprise Portal server name and port number to
which the displayed information applies, and the ID of the current user.
When you select an item in the Navigator tree, a default workspace is displayed.
When you right-click a Navigator item, a menu that includes a Workspace item is
displayed. The Workspace item contains a list of workspaces for that Navigator
item. Each workspace has at least one view. Some views have links to other
workspaces.
The workspaces in the Navigator are shown in a Physical view that shows your
enterprise as a physical mapping or a dynamically populated logical view that is
agent-specific. You can also create a Logical view. The Physical view is the default
view.
This monitoring agent provides predefined workspaces. You cannot modify or
delete the predefined workspaces, but you can create new workspaces by editing
them and saving the changes with a different name.
A table view within a workspace corresponds to a group of attributes; the columns
in the table view show some or all of the attributes available in the attribute group.
More information about workspaces

For more information about creating, customizing, and working with workspaces,
see the Tivoli Enterprise Portal User's Guide.
For a list of the predefined workspaces for this monitoring agent and a description
of each workspace, see the Predefined workspaces section in this chapter and the
information in that section for each individual workspace.
Some attribute groups for this monitoring agent might not be represented in the
predefined workspaces or views for this agent. For a full list of the attribute
groups, see the Attributes reference section.
13
Cross-Linked Workspaces
This section contains cross-links within the Microsoft Cluster Server agent and
from the Microsoft Cluster Server agent to the Microsoft Hyper-V Server agent.
Table 1. Cross-linked workspaces within the Microsoft Cluster Server agent
Source
navigator
item
Source
workspace
name
Source view
name
Local Cluster
Capacity
Dashboard
MS Cluster
Server
Enterprise
Level Cluster
Dashboard
Enterprise
Level Cluster
Capacity
Cluster
Dashboard
Cluster Name
Availability
Cluster
Dashboard
Cluster
Dashboard
Cluster
Capacity
Details
Availability
N/A
Nodes
Cluster
Dashboard
Cluster
Dashboard
Cluster
Capacity
Details
Nodes
N/A
Configuration Cluster
Dashboard
Cluster
Dashboard
Cluster
Capacity
Details
Configuration N/A
Resources
Resource
Groups
Resource
Group
Associations
Resource
Groups to
Resources
Resources
Resource
Name
Resources
Nodes
Nodes
Nodes
Resources
N/A
Resource
Groups
Nodes
Nodes
Nodes
Resource
Groups
N/A
Link name
Target
workspace
name
Filter
Table 2. Cross-linked Workspaces to the Microsoft Hyper-V Server agent
Link name
MSCS to
Hyper-V
agent
Source
navigator
item
Source
workspace
name
Source view
name
Nodes
Nodes
Nodes
Target
workspace
name
Virtual
Machine
Filter
Node Name
Table 3. Cross-linked Workspaces to Windows OS agent
Link name
MSCS to
Windows OS
agent
Source
navigator
item
Source
workspace
name
Source view
name
Nodes
Nodes
Nodes
Target
workspace
name
Virtual
Machine
Filter
Node Name
Predefined workspaces
The Microsoft Cluster Server Agent provides the following predefined workspaces,
which are organized by Navigator item.
v Microsoft Cluster Server Agent Navigator item
Microsoft Cluster Server Agent workspace
Enterprise Level Cluster Dashboard workspace
14
v Availability Navigator item

Availability workspace
Performance Object Status workspace
Thread Pool Status workspace
v Cluster Dashboard Navigator item
Cluster Dashboard workspace
Cluster Shared Volume workspace
v Configuration Navigator item
Cluster Configuration Summary workspace
Configuration workspace
Query Object Status workspace
Quorum Configuration workspace
v Event Log Navigator item
Event Log workspace
v Network Interfaces Navigator item
Network Interfaces workspace
Network Performance workspace
v Networks Navigator item
Network Reconnections workspace
Networks workspace
Networks Messages workspace
v Nodes Navigator item
Node CPU workspace
Node Disks workspace
Node Memory workspace
Nodes workspace
v Resource Groups Navigator item
Resource Group Associations workspace
Resource Group to Possible Node workspace
Resource Groups workspace
v Resources Navigator item
Resource Summary workspace
Resources workspace
v Structural and Degradation Risk Navigator item
Structural and Degradation Risk workspace
Structural Risk workspace
Agent Navigator items

This section contains descriptions of predefined workspaces. The workspaces are
organized by the Navigator item to which the workspaces are relevant.

Microsoft Cluster Server Agent workspace
MS Cluster Server View. This workspace displays the overall status of the
cluster.
15
This workspace contains the following views:

Application Availability
Displays the current availability of all resource groups as an
average.
Average CPU Across All Nodes
Displays the average CPU utilization on all nodes in the cluster.
Processor Load (8hr)
Displays an 8-hour history of the processor load (minimum,
maximum, average and standard deviation) across all nodes in the
cluster.
Message Log
Displays the cluster message log.
Event Log Summary
Displays the Error and Warning events from the Microsoft Cluster
Server event log.
Enterprise Level Cluster Dashboard workspace
The Enterprise Level Cluster Dashboard workspace displays details of the
physical resources that are used by the cluster server system.
Enterprise Level Cluster Capacity
Displays the details of the physical resource that is used by the
cluster server system.
Top 5 Cluster Systems Having High Processor Usage
Displays the percentage of high processor usage of five cluster
systems.
Top 5 Cluster Systems Having High Memory Usage
Displays the percentage of high memory usage of five cluster
systems.
Top 5 Clusters Having High Quorum Usage
Displays the percentage of high quorum usage of five cluster
systems.
Top 5 Clusters Having High Shared Storage Usage
Displays the percentage of high shared storage usage of five cluster
systems.
Availability Navigator item

Availability workspace
The Availability workspace displays the overall health of the application.
Availability
Displays the state of each component in the application. Each
process is displayed using a descriptive name, the name of the
running process, and the state of the process (UP, DOWN, or
PROCESS_DATA_NOT_AVAILABLE). When the state of the
component is DOWN (for a process, or service) it is highlighted
with a red background.
Processor
Displays the amount of CPU used by each process that is a
16
component of the application. This displays the 2 main

components of CPU usage, privileged time which is time spent in
the kernel on behalf of the process and user mode time, which is
the time spent running the process code.
Threads
Displays the number of threads used by each process that is a
component of the application.
Memory
Displays the amount of memory being consumed by each process
that is a component of the application. This total (virtual) size of
the process and the size of the process in memory (working set)
are displayed.
Performance Object Status workspace
This workspace displays the overall health of the application.
This workspace contains the following view:
Performance Object Status
Displays the status of data collection from the application. NO
ERROR indicates that the agent is collecting application data
correctly. If any other views of the agent do not show any data,
then this view helps to identify the cause of the data collection
failure.
Thread Pool Status workspace
This workspace displays information about the Thread Pool Status
attribute group.
Thread Pool Status
Provides information about the Thread Pool Status attribute group
and the status of the internal thread pool that is used to collect
data in an asynchronous manner.
Cluster Dashboard Navigator item

Cluster Dashboard workspace
The Cluster Dashboard workspace provides details of the cluster and its
capacity.
Cluster Capacity Details
Displays details of the capacity of the cluster in the enterprise.
Cluster Shared Storage
Displays information about the Clustered Shared Volume available
in a cluster.
System Processor Usage
Displays processor usage of a particular node in a cluster.
System Memory Usage
Displays memory usage of a particular node in a cluster.
Quorum Usage
Displays quorum usage of a particular node in a cluster.
Shared Storage Usage
Displays shared storage usage of a particular node in a cluster.
17
Cluster Shared Volume workspace

The Cluster Shared Volume workspace provides information about the
Cluster Shared Volume disk that is configured in the cluster environment.
Displays information about the Cluster Shared Volume disk that is
configured in the cluster environment.
Displays information about the I/O activity on all the cluster
shared volume disks of the cluster.
IO Read Bytes
Displays information about the number of read operations that are
sent from the Cluster Shared Volume.
IO Write Bytes
Displays information about the number of write operations that are
sent to the Cluster Shared Volume.
Configuration Navigator item

Cluster Configuration Summary workspace
Displays a summary of the current cluster configuration. The views
typically show the names of key resources, their current state, and the time
they were last checked.
Cluster Configuration
This view displays the current cluster object, including the name of
the cluster.
Networks Summary
This view displays a summary of the network configuration. More
details can be found in the Networks and Network Interface
workspaces. This view is linked to the detailed Network
workspace.
Resource Groups Summary
This view displays a summary of the resource group configuration.
More details can be found in the Resource Group and Resources
workspaces. This view is linked to the detailed Resource Groups
workspace.
Nodes Summary
This view displays a summary of the node configuration. This
view is linked to the detailed Nodes workspace.
Configuration workspace
Provides a visual summary of the cluster state. It shows the state
information for the five key cluster attributes in a bar chart form. Up is
represented as a full bar, down will have no bar at all, and intermediate
states(if any) will be in between.
State of Nodes
This view displays the state of the nodes. It is linked to the
detailed Node workspace.
18
State of Networks
This view displays the state of the networks. It is linked to the
detailed Networks workspace.
State of Network Interfaces
This view displays the state of the network interfaces. It is linked
to the detailed Network Interface workspace.
State of Resource Groups
This view displays the state of the resource groups. It is linked to
the detailed Resource Groups workspace.
State of Resources
This view displays the state of the resources. It is linked to the
detailed Resources workspace.
Query Object Status workspace
The Query Status workspace displays the current status of the data
collection queries.
State of Data Collection Queries
This view displays the current status of the data collection queries.
The query name, the object it queries, the object status, and the
return code from the query are shown here.
Quorum Configuration workspace
The Quorum Configuration Workspace displays the current Quorum
Configuration details.
Quorum Configuration for Microsoft Windows 2003
This view displays the Quorum Configuration details. The
Maintanace File of Quorum and Quorum Log File Size for
Microsoft Windows 2003.
Quorum Configuration for Microsoft Windows 2008
This view displays the Quorum Configuration details. Maximum
and Minimum time (in sec), necessary to decide the Quorum
owner node, Quorum Type and Quorum Path for Microsoft
Windows 2008.
Event Log Navigator item

Event Log workspace
The Event Log workspace shows the details for the recent events logged by
the application to the Windows Event Log. By default, the agent only
displays events that occur after the agent is started. Events are removed
from the Event Log view 1 hour after they occur.
Event Log
Shows the recent Event Log entries for Microsoft Cluster Server.
Network Interfaces Navigator item

Network Interfaces workspace
Provides availability and detail information for the cluster network
interfaces.
19

Network Interfaces State Rollup
This view displays a rollup of the network interface state
information.
Network Interfaces
This view displays the network interface configuration details.
Network Interface State (8hr)
This view graphs the state of the network interfaces over the last
eight hours. This view is populated with data collected from
historical data collection. Start the historical data collection for
these attribute groups to see data for the respected view.
Network Performance workspace
This workspace provides network performance data collected from each
node in the cluster.
Network Interfaces
This view displays the details of each network interface in the
cluster.
Packets per Second Rollup
This view displays the rollup of the network interface packets per
second.
Bytes Received per Second Rollup (8hr)
This view graphs the rollup of the bytes received per second over
eight hours. Data is available after historical data collection for the
attribute group. This view is populated with data collected from
these attribute groups to see data for the respected view
Bytes Sent per Second Rollup (8hr)
This view graphs the rollup of the bytes sent per second over eight
hours. Data is available after historical data collection for the
attribute group. This view is populated with data collected from
Networks Navigator item

Network Reconnections workspace
The Network Reconnections workspace provides information about
reconects between the nodes of the cluster and the queue length of
messages.
Displays the information about the reconnects between the nodes
of the cluster.
Message Queue Length
Displays the queue length of all types of messages.
Networks workspace
This workspace provides detailed information about the cluster networks.
It contains tables with the configuration details and an availability graph of
the network.
20

Network State Rollup
This view displays a rollup of the network state information.
Networks
This view displays the network configuration details.
Network State (8hr)
This view graphs the state of the networks over the last eight
hours. This view is populated with data collected from historical
data collection. Start the historical data collection for these attribute
groups to see data for the respected view.
Networks Messages workspace
The Networks Messages workspace provides information about the cluster
network messages that are sent and received on the network per cluster
node.
Network Messages Sent/Received
Displays information about the cluster network messages that are
sent and received on the network per cluster node.
Bytes Sent/Received
Displays information about the cluster network bytes that are sent
and received on the network per cluster node.
Messages Sent/Received
Displays information about the cluster network messages that are
sent and received on the network per cluster node.
Nodes Navigator item

Node CPU workspace
This workspace contains processor information collected from each node in
the cluster.
CPU per Node
This view displays the details of each processor in the cluster.
CPU per Node Rollup
This view displays the rollup of the percent processor time.
CPU Rollup (8hr)
This view graphs the rollup of the percent processor time over
CPU Interrupts Persec Rollup (8hr)
This view graphs the interrupts per second over eight hours. This
view is populated with data collected from historical data
collection. Start the historical data collection for these attribute
Node Disks workspace
This workspace contains disk information collected from each node in the
cluster.
21
Logical Disks on Nodes

This view displays the disk details of each node in the cluster.
Free Space (MB) on the Logical Disks Rollup
This view displays the rollup of the free space on the disks (in
megabytes).
Free Space in MB on the Logical Disks (8hr)
This view graphs the rollup of free space on the disks (in
megabytes) over eight hours. This view is populated with data
collected from historical data collection. Start the historical data
collection for these attribute groups to see data for the respected
view.
Percent Free Space on the Logical Disks (8hr)
This view graphs the percent free space on the disks over eight
Node Memory workspace
This workspace contains memory information collected from each node in
the cluster.
Memory
This view displays the memory details of each node in the cluster.
Memory MB Rollup
This view displays the rollup of the available megabytes of
memory.
Available Memory (MB) Rollup (8hr)
This view graphs the rollup of the available megabytes of memory
over eight hours. This view is populated with data collected from
The Percent Committed Bytes in Use (8hr)
This view graphs the percent committed bytes used over eight
Nodes workspace
This workspace provides detailed information for the cluster nodes. It also
includes a node availability graph.
Nodes State Rollup
This view displays a rollup of the node state information.
Nodes This view displays the node configuration details.
Nodes State (8hr)
This view graphs the state of the nodes. This view is populated
with data collected from historical data collection. Start the
historical data collection for these attribute groups to see data for
the respected view.
22
Resource Groups Navigator item

Resource Group Associations workspace
This workspace shows the resource group associations between resources
and nodes
Resource Groups to Resources
This view displays the association of resource groups to resources.
Resource Group to Nodes Table
This view displays the association of resource groups to nodes.
Resource Group Node Changes
This view displays a real time graph of the Resource Group Node
Change attribute.
Resource Group to Possible Node workspace
This workspace shows the resource group to its preferred node, and
resource to possible node views.
Resource to Possible Owner
This view displays the association of resource to possible nodes.
Resource Group to Preferred Nodes
This view displays the association of resource group to preferred
nodes.
Resource Groups workspace
The resource group workspace provides availability and detail information
for the cluster resource groups.
State of Resource Groups Rollup
This view displays a rollup of the resource group state information.
Resource Groups
This view displays the resource group configuration details.
Resource Groups State (8hr)
This view graphs the state of the resource groups over the last
Resources Navigator item

Resource Summary workspace
The Resources Summary workspace provides information about the overall
health of the various types of resources available in the cluster
environment.
Dependent Resources Summary
Displays information about resources and its dependent resources.
Resources Summary
Displays information about the cluster resources that are grouped
by the resource type.
23
Total Resources Online

Displays the number of resources that are online.
Resources workspace
The resource workspace provides availability and detail information for the
cluster resources.
Resource State Rollup
This view displays a rollup of the resource state information.
Resources
This view displays the resource configuration details.
Resources States (8hr)
This view graphs the state of the resource over the last eight hours.
This view is populated with data collected from historical data
collection. Start the historical data collection for these attribute

Structural and Degradation Risk workspace
The Structural and Degradation Risk workspace and the Degradation
workspace is an estimate of the potential of degraded performance if one
node fails. Degradation risk is a first-order approximation of the
proportion of the current workload that could not be carried in the event
of a failure (or the degree of over commitment). Commitment is the current
workload of the cluster. For example, in a 2-node active/passive
configuration with a 3GHz node A and a 1.5 GHz node B, where A is
active, the capacity of node A is 3000 (3GHz = 3000MHz), and if A is
currently using 20% CPU, its utilization is (3000*(20%)) = 600. The capacity
of node B is 1500 (1.5GHz = 1500MHz). Therefore node B could carry all of
the current work(1500-600 = 900) being required of A. If A is currently at
80% utilization, its utilization(3000*80%) = 2400, 2400/1500 = 160%
meaning B is over committed by 60%. On clusters with more than two
nodes we introduce the terms Unitary and Uniform Commitment. Unitary
commitment is where the entire load (as in the previous example) of the
failed node is placed on the next node. This represents a resource group
that must be shifted as a whole, and no balancing of the load is possible.
Uniform commitment is where the load may be balanced evenly amongst
the remaining nodes. The actual risk of degraded performance lies
somewhere between these two lines. For both forms of commitment, values
less than or equal to 100%, represent a level of commitment that the cluster
should be able to carry without a loss of performance. In practice, values
near 100% also suffer some degradation. Situations may be created, based
on cluster configuration and customer experience, to fire when either form
of commitment exceeds a threshold (for example 100%).
Degradation Risk Table
This view displays the performance details of the cluster.
Utilization Graph
This view graphs the processor utilization and capacity of the
cluster over eight hours.
24
Commitment Graph
This view graphs the commitment of the cluster processor over
eight hours.
Structural Risk workspace
The Structural Risk workspace tracks the availability of resources, and
calculates the impact of a node failure. Since resources form resource
groups and the resource groups represent applications, a single critical
resource can lead to a failed application. As currently implemented, only
the most at risk resource (in the event of a tie, the first resource) is
displayed. The definition of the structural risk factor is n/m, where n is the
number of active, configured nodes, and m is the number of configured
nodes in the cluster. The cluster-wide structural risk factor is the minimum
over all resources. A 5 node cluster with 2 failed nodes and free-range
failover (no failover limitations) for all resources would have a health
factor of 3/5. Resources are matched to their possible nodes and a relative
health for each resource is calculated. If a resource is configured on 3
nodes and all three nodes are up 3/3 = 100% health, if only two of three
2/3 = 66% health. The Health Less A Node is the hypothetical loss of one
node calculation (n-1)/m, where n is the number of active nodes
configured to support the resource, and m is the number of nodes
configured to support the resource. The Fewest Nodes Resource shows the
resource configured on the fewest nodes and the impact should it lose a
node. Situations may be created based on health thresholds or on the
number of nodes (such as when a resource is on its last node: Available
Nodes equals one).
Structural Risk Table
This view displays structural risk of the cluster.
Structural Risk Graph
This view graphs the structural risk relative health attributes of the
cluster over eight hours.
25
26
Chapter 4. Attributes reference

This chapter contains an overview of attributes, references for detailed information
about attributes, and descriptions of the attributes for each attribute group
included in this monitoring agent.
About attributes
Attributes are the application properties that are being measured and reported by
the Microsoft Cluster Server Agent.
Attributes are organized into groups according to their purpose. The attributes in a
group can be used in the following two ways:
v Chart or table views
Attributes are displayed in chart and table views. The chart and table views use
queries to specify which attribute values to request from a monitoring agent.
You use the Query editor to create a new query, modify an existing query, or
apply filters and set styles to define the content and appearance of a view based
on an existing query.
v Situations
You use attributes to create situations that monitor the state of your operating
system, database, or application. A situation describes a condition you want to
test. When you start a situation, the Tivoli Enterprise Portal compares the values
you have assigned to the situation attributes with the values collected by the
Microsoft Cluster Server Agent and registers an event if the condition is met. You
are alerted to events by indicator icons that are displayed in the Navigator.
More information about attributes

For more information about using attributes and attribute groups, see the Tivoli
Enterprise Portal User's Guide.
For a list of the attributes groups, a list of the attributes in each attribute group,
and descriptions of the attributes for this monitoring agent, see the Attribute
groups and attributes section in this chapter.
Attribute groups and attributes for the Microsoft Cluster Server Agent
This monitoring agent contains the following attribute groups. The table name
depends on the maximum table name limits of the target database being used for
the Tivoli Data Warehouse. If the maximum name is 30 characters, then any
warehouse table name longer than 30 characters is shortened to 30 characters.
v Attribute group name: Availability
Table name: KQ5AVAIL
Warehouse table name: KQ5_AVAILABILITY or KQ5AVAIL
v Attribute group name: Cluster Domain
Table name: KQ5WIN32CO
Warehouse table name: KQ5_CLUSTER_DOMAIN or KQ5WIN32CO
v Attribute group name: Cluster Shared Volume
Table name: KQ5CLUSCSV
27
Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME or

KQ5CLUSCSV
v Attribute group name: Cluster Shared Volume IO
Table name: KQ5CLUCSVP
Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_IO or
KQ5CLUCSVP
v Attribute group name: Cluster Summary
Table name: KQ5CLUSUM
Warehouse table name: KQ5_CLUSTER_SUMMARY or KQ5CLUSUM
v Attribute group name: Configuration
Table name: KQ5B05PHYS
Warehouse table name: KQ5_CONFIGURATION or KQ5B05PHYS
v Attribute group name: CPU Interrupts Rollup
Table name: KQ5D55RLL
Warehouse table name: KQ5_CPU_INTERRUPTS_ROLLUP or KQ5D55RLL
v Attribute group name: CPU per Node
Table name: KQ5D40CPU
Warehouse table name: KQ5_CPU_PER_NODE or KQ5D40CPU
v Attribute group name: CPU per Node Rollup
Warehouse table name: KQ5_CPU_PER_NODE_ROLLUP or KQ5D50RLL
v Attribute group name: Degradation Risk
Table name: KQ5G20RISK
Warehouse table name: KQ5_DEGRADATION_RISK or KQ5G20RISK
v Attribute group name: Disk
Table name: KQ5D80HDD
Warehouse table name: KQ5_DISK or KQ5D80HDD
v Attribute group name: Disk MB Rollup
Warehouse table name: KQ5_DISK_MB_ROLLUP or KQ5D85RLL
v Attribute group name: Disk PCT Rollup
Warehouse table name: KQ5_DISK_PCT_ROLLUP or KQ5D90RLL
v Attribute group name: Enterprise Cluster Summary
Table name: KQ5VCLUSUM
Warehouse table name: KQ5_ENTERPRISE_CLUSTER_SUMMARY or
KQ5VCLUSUM
v Attribute group name: Event Log
Table name: KQ5EVTLOG
Warehouse table name: KQ5_EVENT_LOG or KQ5EVTLOG
v Attribute group name: Global Update Messages
Table name: KQ5CLUSTE1
Warehouse table name: KQ5_GLOBAL_UPDATE_MESSAGES or
KQ5CLUSTE1
v Attribute group name: Memory
Table name: KQ5D60MEM
28
Warehouse table name: KQ5_MEMORY or KQ5D60MEM

v Attribute group name: Memory MB Rollup
Warehouse table name: KQ5_MEMORY_MB_ROLLUP or KQ5D70RLL
v Attribute group name: Memory PCT Rollup
Warehouse table name: KQ5_MEMORY_PCT_ROLLUP or KQ5D75RLL
v Attribute group name: MRR Messages
Table name: KQ5CLUSTE3
Warehouse table name: KQ5_MRR_MESSAGES or KQ5CLUSTE3
v Attribute group name: Network Interfaces
Table name: KQ5F20INT
Warehouse table name: KQ5_NETWORK_INTERFACES or KQ5F20INT
v Attribute group name: Network Interfaces State Rollup
Table name: KQ5F30RLL
Warehouse table name: KQ5_NETWORK_INTERFACES_STATE_ROLLUP or
KQ5F30RLL
v Attribute group name: Network Performance
Table name: KQ5F40NET
Warehouse table name: KQ5_NETWORK_PERFORMANCE or KQ5F40NET
v Attribute group name: Network Performance Packets Rollup
Warehouse table name:
KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP or KQ5F70RLL
v Attribute group name: Network Performance Received Rollup
Warehouse table name:
KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP or KQ5F50RLL
v Attribute group name: Network Performance Sent Rollup
Warehouse table name: KQ5_NETWORK_PERFORMANCE_SENT_ROLLUP
or KQ5F60RLL
v Attribute group name: Network Reconnections
Table name: KQ5NWRECON
Warehouse table name: KQ5_NETWORK_RECONNECTIONS or
KQ5NWRECON
v Attribute group name: Networks
Table name: KQ5E20NET
Warehouse table name: KQ5_NETWORKS or KQ5E20NET
v Attribute group name: Networks Messages
Table name: KQ5NETMESS
Warehouse table name: KQ5_NETWORKS_MESSAGES or KQ5NETMESS
v Attribute group name: Networks Rollup
Table name: KQ5E30RLL
Warehouse table name: KQ5_NETWORKS_ROLLUP or KQ5E30RLL
v Attribute group name: Node To Active Group
29
Table name: KQ5B20LOGI

Warehouse table name: KQ5_NODE_TO_ACTIVE_GROUP or KQ5B20LOGI
v Attribute group name: Nodes
Table name: KQ5D20NODE
Warehouse table name: KQ5_NODES or KQ5D20NODE
v Attribute group name: Nodes State Rollup
Warehouse table name: KQ5_NODES_STATE_ROLLUP or KQ5D30RLL
v Attribute group name: Performance Object Status
Table name: KQ5POBJST
Warehouse table name: KQ5_PERFORMANCE_OBJECT_STATUS or
KQ5POBJST
v Attribute group name: Quorum Configuration
Table name: KQ5MSCLUST
Warehouse table name: KQ5_QUORUM_CONFIGURATION or
KQ5MSCLUST
v Attribute group name: Resource Control Manager
Table name: KQ5CLUSRSC
Warehouse table name: KQ5_RESOURCE_CONTROL_MANAGER or
KQ5CLUSRSC
v Attribute group name: Resource Group Moves
Table name: KQ5B30RLL
Warehouse table name: KQ5_RESOURCE_GROUP_MOVES or KQ5B30RLL
v Attribute group name: Resource Group To Preferred Node
Warehouse table name: KQ5_RESOURCE_GROUP_TO_PREFERRED_NODE
or KQ5B30LOGI
v Attribute group name: Resource Group To Resource
Warehouse table name: KQ5_RESOURCE_GROUP_TO_RESOURCE or
KQ5B25LOGI
v Attribute group name: Resource Groups
Table name: KQ5B10RG
Warehouse table name: KQ5_RESOURCE_GROUPS or KQ5B10RG
v Attribute group name: Resource Groups State Rollup
Table name: KQ5B15RLL
Warehouse table name: KQ5_RESOURCE_GROUPS_STATE_ROLLUP or
KQ5B15RLL
v Attribute group name: Resource To Dependent Resource
Table name: KQ5B25RTDR
Warehouse table name: KQ5_RESOURCE_TO_DEPENDENT_RESOURCE or
KQ5B25RTDR
v Attribute group name: Resource To Possible Owner
Warehouse table name: KQ5_RESOURCE_TO_POSSIBLE_OWNER or
KQ5B35LOGI
30
v Attribute group name: Resources

Table name: KQ5C20RES
Warehouse table name: KQ5_RESOURCES or KQ5C20RES
v Attribute group name: Resources State Rollup
Table name: KQ5C30RLL
Warehouse table name: KQ5_RESOURCES_STATE_ROLLUP or KQ5C30RLL
v Attribute group name: Resources Summary
Table name: KQ5CLUSTER
Warehouse table name: KQ5_RESOURCES_SUMMARY or KQ5CLUSTER
v Attribute group name: Shared Storage Summary
Table name: KQ5CSVSUMM
Warehouse table name: KQ5_SHARED_STORAGE_SUMMARY or
KQ5CSVSUMM
v Attribute group name: Structural Risk
Table name: KQ5G30RLL
Warehouse table name: KQ5_STRUCTURAL_RISK or KQ5G30RLL
v Attribute group name: Thread Pool Status
Table name: KQ5THPLST
Warehouse table name: KQ5_THREAD_POOL_STATUS or KQ5THPLST
The remaining sections of this chapter contain descriptions of these attribute
groups, which are listed alphabetically. The following information is provided for
each attribute group:
Historical group
Whether the attribute group is a historical type that you can roll off to a
data warehouse
Attribute descriptions
Description, type, and Warehouse name for each attribute in the attribute
group
Some attributes are designated as key attributes. A key attribute is an
attribute that is used in warehouse aggregation to identify rows of data
that represent the same object.
Availability attribute group

The Availability attribute group contains the availability data for all processes and
services that make up this application.
Historical group
This attribute group is part of the default historical group, and is eligible for use
with Tivoli Data Warehouse.
The following list contains information about each attribute in the Availability
attribute group:
Node attribute - This attribute is a key attribute.
Description
The managed system name of the agent.
31
Type
String
Warehouse name
NODE
Timestamp attribute
Description
The local time at the agent when the data was collected.
Type
String
Warehouse name
TIMESTAMP
Application Component attribute - This attribute is a key attribute.
Description
The descriptive name of a part of the application.
Type
String
Warehouse name
APPLICATION_COMPONENT or COMPONENT
Name attribute
Description
The name of the process, service, or functionality test. This name
matches the executable name of the process, the service short name
or the name of the process used to test the application.
Type
String with enumerated values. The strings are displayed in the

Tivoli Enterprise Portal. The warehouse and queries return the
values shown in parentheses. The following values are defined:
v N/A (N/A)
Any other values will display the actual value returned by the
agent in the Tivoli Enterprise Portal.
Warehouse name
NAME
Status attribute
Description
The status of the application component.
v For processes 'UP', 'DOWN', 'WARNING', or
'PROCESS_DATA_NOT_AVAILABLE':
'PROCESS_DATA_NOT_AVAILABLE' is displayed for a process
when the matching process is running but the resource use
information cannot be collected for that process.
v For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' is
displayed when the service is not installed.
v For functionality tests: 'PASSED' or 'FAILED' is displayed.
Type
Integer with enumerated values. The strings are displayed in the

v DOWN (0)
v UP (1)
v WARNING (2)
32
v
v
v
v
UNKNOWN (3)
PASSED (4)
FAILED (5)
PROCESS_DATA_NOT_AVAILABLE (6)
Warehouse name
STATUS
Full Name attribute
Description
The full name of the process including the path.
Type

v N/A (N/A)
Warehouse name
FULL_NAME or FULLNAME
Type attribute
Description
The type of the application component. Components are processes,
services, or functionality tests.
Type

v PROCESS (0)
v SERVICE (1)
v FUNCTIONALITY_TEST (2)
Warehouse name
TYPE
Virtual Size attribute
Description
The virtual size (in MB) of the process.
Type
Integer (gauge)
Warehouse name
VIRTUAL_SIZE or VIRTSIZE
Page Faults per Sec attribute
Description
The rate of page faults for the process measured in faults per
second. This attribute only contains valid data for processes.
Type
Integer (gauge)
33
Warehouse name
PAGE_FAULTS_PER_SEC or PAGEFAULTS
Working Set Size attribute
Description
The working set size of the process in MB. This attribute only
contains valid data for processes.
Type
Integer (gauge)
Warehouse name
WORKING_SET_SIZE or WORKSET
Thread Count attribute
Description
The number of threads currently allocated by this process. This
attribute only contains valid data for processes.
Type
Integer (gauge)
Warehouse name
THREAD_COUNT or THREADS
PID attribute
Description
The process ID associated with the process. This attribute only
contains valid data for processes.
Type
Integer (gauge)
Warehouse name
PID
Percent Privileged Time attribute
Description
The percentage of the available CPU time that is being used by this
process for privileged operation.
Type
Integer (gauge)
Warehouse name
PERCENT_PRIVILEGED_TIME or PERCPRIV
Percent User Mode Time attribute
Description
The percentage of the available CPU time that is being used by this
process for user mode operation.
Type
Integer (gauge)
Warehouse name
PERCENT_USER_MODE_TIME or PERCUSER
Percent Processor Time attribute
Description
The percentage of the elapsed time that this process used the
processor to execute instructions.
Type
Integer (gauge)
Warehouse name
PERCENT_PROCESSOR_TIME or PERCPROC
34
Command Line attribute

Description
The program name and any arguments specified on the command
line when the process was started. This has the value N/A if this is
a Service, or Functionality test.
Type

v N/A (N/A)
Warehouse name
COMMAND_LINE or CMDLINE
Functionality Test Status attribute
Description
The return code of the functionality test. When the monitored
application is running correctly, 'SUCCESS' is displayed.
'NOT_RUNNING' is displayed when it is not running correctly.
'N/A' is displayed when the row does not represent a functionality
test.
Type

v SUCCESS (0)
v N/A (1)
v GENERAL_ERROR (2)
v
v
v
v
WARNING (3)
NOT_RUNNING (4)
DEPENDENT_NOT_RUNNING (5)
ALREADY_RUNNING (6)
v PREREQ_NOT_RUNNING (7)
v TIMED_OUT (8)
v DOESNT_EXIST (9)
v UNKNOWN (10)
v DEPENDENT_STILL_RUNNING (11)
v INSUFFICIENT_USER_AUTHORITY (12)
Warehouse name
FUNCTIONALITY_TEST_STATUS or FUNCSTATUS
Functionality Test Message attribute
Description
The text message that corresponds to the Functionality Test Status.
This is only valid for functionality tests.
Type
35

v N/A (N/A)
Warehouse name
FUNCTIONALITY_TEST_MESSAGE or FUNCMSG
Cluster Domain attribute group

Cluster Domain contains details of the windows domain to which the cluster
belongs.
Historical group
This attribute group is not part of the default historical group, and is eligible for
use with Tivoli Data Warehouse.
The following list contains information about each attribute in the Cluster Domain
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Domain attribute
Description
Domain contains name of the windows domain to which the
cluster belongs.
Type
String
Warehouse name
DOMAIN
Cluster Shared Volume attribute group

The Cluster Shared Volume attribute group provides information about all the
cluster shared volume disks configured in the cluster environment.
36
Historical group
The following list contains information about each attribute in the Cluster Shared
Volume attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Cluster Shared Volume Name attribute - This attribute is a key attribute.
Description
The name of the Cluster Shared Volume (CSV).
Type
String
Warehouse name
NAME
Volume Name attribute
Description
The device ID of the Cluster Shared Volume.
Type
String
Warehouse name
VOLUMENAME
Volume Offset attribute
Description
The volume offest of the Cluster Shared Volume.
Type
Integer (gauge) with enumerated values. The strings are displayed

in the Tivoli Enterprise Portal. The warehouse and queries return
the values shown in parentheses. The following values are defined:
v Value_Exceeds_Maximum (2147483647)
v Value_Exceeds_Minimum (-2147483648)
Warehouse name
VOLUMEOFFSET or VOLUMEOFFS
37
CSV Resource Name attribute

Description
The name of the Cluster Shared Volume resource.
Type
String
Warehouse name
CSVRESOURCENAME or C
CSV Resource State attribute
Description
The current state of the Cluster Shared Volume Resource. The
states can be: Unknown(-1), Inherited(0), Initializing(1), Online(2),
Offline(3), Failed(4), Pending(128), OnlinePending(129), and
OfflinePending(130).
Type

v Unknown (-1)
v Inherited (0)
v Initializing (1)
v Online (2)
v Offline (3)
v Failed (4)
v Pending (128)
v OnlinePending (129)
v OfflinePending (130)
Warehouse name
CSVRESOURCESTATE or C0
CSV Node Name attribute
Description
The name of the cluster node that owns the Cluster Shared
Volume.
Type
String
Warehouse name
CSVNODENAME or C1
Backup State attribute
Description
The backup state of the Cluster Shared Volume. The state can be
None(0) or InProgress(1)
Type

v None (0)
38
v InProgress (1)
v (-1)
Warehouse name
BACKUPSTATE or BACKUPSTAT
Description attribute
Description
The description of the Cluster Shared Volume.
Type
String
Warehouse name
DESCRIPTION or DESCRIPTIO
Fault State attribute
Description
The fault state of the Cluster Shared Volume. The states can be:
NoFaults(0), NoDirectIO(1), NoAccess(2), and Maintenance(4)
Type

v NoFaults (0)
v NoDirectIO (1)
v NoAccess (2)
v Maintenance (4)
v (-1)
Warehouse name
FAULTSTATE
Cluster Shared Volume IO attribute group

The Cluster Shared Volume IO displays the information about the I/O activity on
all the cluster shared volume disks of the cluster.
Historical group
The following list contains information about each attribute in the Cluster Shared
Volume IO attribute group:
Description
39
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
IO Read Bytes attribute
Description
The number of bytes read directly from the Cluster Shared Volume
since the service was started.
Type
Integer (counter) with enumerated values. The strings are

displayed in the Tivoli Enterprise Portal. The warehouse and
queries return the values shown in parentheses. The following
values are defined:
Warehouse name
IO_READ_BYTES or IO_READ_BY
IO Reads attribute
Description
The number of read operations that are performed directly from
the Cluster Shared Volume since the service was started.
Type

values are defined:
Warehouse name
IO_READS
IO Write Bytes attribute
Description
The number of bytes written directly to the Cluster Shared Volume
Type
40

values are defined:
Warehouse name
IO_WRITE_BYTES or IO_WRITE_B
IO Writes attribute
Description
The number of write operations that are performed directly to the
Cluster Shared Volume since the service was started.
Type

values are defined:
Warehouse name
IO_WRITES
Metadata IO attribute
Description
The number of metadata operations that are performed against the
Cluster Shared Volume since the service was started.
Type

values are defined:
Warehouse name
METADATA_IO or METADATA_I
Redirected Read Bytes attribute
Description
The number of read bytes that are redirected to the Cluster Shared
Volume through the network since the service was started.
Type

values are defined:
41
Warehouse name
REDIRECTED_READ_BYTES or REDIRECTED
Redirected Reads attribute
Description
The number of read operations that are redirected to the Cluster
Shared Volume through the network since the service was started.
Type

values are defined:
Warehouse name
REDIRECTED_READS or REDIRECTE0
Redirected Write Bytes attribute
Description
The number of write bytes that are redirected to the Cluster Shared
Volume through the network since the service was started.
Type

values are defined:
Warehouse name
REDIRECTED_WRITE_BYTES or REDIRECTE1
Redirected Writes attribute
Description
The number of write operations that are redirected to the Cluster
Shared Volume through the network since the service was started.
Type

values are defined:
Warehouse name
REDIRECTED_WRITES or REDIRECTE2
Name attribute - This attribute is a key attribute.
42
Description
The name of the instance.
Type
String
Warehouse name
NAME
Cluster Summary attribute group

The Cluster Summary attribute group provides information about all clusters in
the enterprise.
Historical group
The following list contains information about each attribute in the Cluster
Summary attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Cluster Name attribute
Description
The name of the cluster in the enterprise.
Type
String
Warehouse name
CLUSTER_NAME or CLUNAME
Current Host Server attribute
Description
The name of the node in the cluster.
Type
String
Warehouse name
NODE_NAME or NODNAME
System Information attribute
43
Description
The system information of a node in the cluster.
Type
String
Warehouse name
SYSTEM_INFORMATION or SYSINFO
Percentage Processor Used attribute
Description
The percentage of the processor that is used by the cluster.
Type

Warehouse name
SYSTEM_PROCESSOR_UTILIZATION or PERCPUT
Precentage Processor Free attribute
Description
The percent of time the processor is idle in the active cluster node.
Type

Warehouse name
SYSTEM_PROCESSOR_IDLE or PCPUIDT
Percentage Memory Used attribute
Description
The percentage of memory that is used by the active cluster node.
Type

Warehouse name
TOTAL_MEMORY_UTILIZATION or TOULMEM
Percentage Memory Free attribute
Description
The percentage of memory that is available on the active cluster
node.
44
Type

Warehouse name
TOTAL_MEMORY_AVAILABLE or TOMEMAL
Quorum Path attribute
Description
The path of the quorum files.
Type
String
Warehouse name
QUORUM_PATH or QUOPATH
Quorum Total Size attribute
Description
The size of the quorum disk in megabytes.
Type

Warehouse name
QUORUM_TOTAL_SIZE or QUOTOSZ
Quorum Utilization attribute
Description
The size of the quorum disk that is used by the cluster in
megabytes.
Type

Warehouse name
QUORUM_UTILIZATION or QUOUDSZ
Quorum Available attribute
Description
The size of the quorum disk that is available in megabytes.
Type
45

Warehouse name
QUORUM_AVAILABLE or QUOFRSP
Percentage Quorum Used attribute
Description
The percentage of the quorum disk that is used by the cluster.
Type

Warehouse name
PERCENTAGE_QUORUM_USED or PRQUOUD
Percentage Quorum Free attribute
Description
The percentage of quorum disk that is available for the cluster.
Type

Warehouse name
PERCENTAGE_QUORUM_FREE or PRQUOFR
Shared Storage Available attribute
Description
The total size of shared storage (shared data disk and cluster
shared volume) that is available in the cluster in megabytes.
Type

Warehouse name
SHARED_STORAGE_AVAILABLE or SHTFRSP
46
Shared Storage Total Size attribute

Description
shared volume) in the cluster in megabytes.
Type

Warehouse name
SHARED_STORAGE_TOTAL_SIZE or SHTTOSZ
Shared Storage Utilization attribute
Description
shared volume) that is used in the cluster in megabytes.
Type

Warehouse name
SHARED_STORAGE_UTILIZATION or SHTUDSZ
Percentage Shared Storage Used attribute
Description
The percentage of the shared storage (shared data disk and cluster
shared volume) that is used by the cluster.
Type

Warehouse name
PERCENTAGE_SHARED_STORAGE_USED or PCTSSUD
Percentage Shared Storage Free attribute
Description
The percentage of shared storage (shared data disk and cluster
shared volume) that is available in the cluster.
Type

47
Warehouse name
PERCENTAGE_SHARED_STORAGE_FREE or PCTSSFR
No of Shared Storage attribute
Description
The total number of shared storage disks in the cluster.
Type

Warehouse name
TOTAL_SHARED_STORAGE or TOSHRST
Percentage Network Used attribute
Description
The percentage of maximum network that is used by the Cluster.
Type

Warehouse name
NETWORK_UTILIZATION or NETWKUD
Domain attribute
Description
The domain name of the cluster.
Type
String
Warehouse name
DOMAIN or CDOMAIN
Configuration attribute group

The cluster attributes.This provides a brief overview of the cluster.Additional
workspaces are provided for the detailed description of each node, network,
network interface, resource, and resource group.
Historical group
48
The following list contains information about each attribute in the Configuration
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Name attribute
Description
The name of this cluster.
Type
String
Warehouse name
NAME
Max Number Nodes attribute
Description
The maximum number of nodes that can participate in this cluster.
Type

Warehouse name
MAX_NUMBER_NODES or MNN
Default Network Role attribute
Description
Specifies the role that the cluster automatically assigns to any
newly discovered or created network: None(0) InternalUse(1)
ClientAccess(2) InternalAndClient(3).
Type

v None (0)
v InternalUse (1)
v ClientAccess (2)
49
v InternalAndClient (3)
Warehouse name
DEFAULT_NETWORK_ROLE or DNR
Description
The cluster description specified at cluster creation and modifiable
by the cluster administrator.
Type
String
Warehouse name
DESCRIPTION or D
CPU Interrupts Rollup attribute group

The rollup of processor interrupts per second.The rollup is a simple statistical
processing of the interrupt data from all nodes of the cluster.
Historical group
The following list contains information about each attribute in the CPU Interrupts
Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of interrupts per second.
Type

50
Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of interrupts per second.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the interrupts per second.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the interrupts per second.
Type

Warehouse name
TOTAL
Standard Deviation attribute
Description
This is the standard deviation of the interrupts per second.
Type
51

Warehouse name
STANDARD_DEVIATION or SD
CPU per Node attribute group

Provides the processor metrics from each processor of each node in the cluster.
Historical group
The following list contains information about each attribute in the CPU per Node
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of the node.
Type
String
Warehouse name
NAME
Processor attribute - This attribute is a key attribute.
Description
The processor name.
Type
String
Warehouse name
PROCESSOR
52
Interrupts attribute
Description
The average number of hardware interrupts that the processor is
receiving and servicing per second.
Type

Warehouse name
INTERRUPTS
Percent Interrupt Time attribute
Description
The percentage of time that the processor spent receiving and
servicing hardware interrupts during the sample interval.
Type

Warehouse name
PERCENT_INTERRUPT_TIME or PIT
Percent Idle Time attribute
Description
The percentage of time during the sample interval that the
processor was idle.
Type

Warehouse name
PERCENT_IDLE_TIME or PIT0
Percent Processor Time attribute
Description
The percentage of time that the processor is executing a non-idle
thread.
Type

53
Warehouse name
PERCENT_PROCESSOR_TIME or PPT
Percent User Time attribute
Description
The percentage of non-idle processor time spent in user mode.
Type

Warehouse name
PERCENT_USER_TIME or PUT
Percent Privileged Time attribute
Description
The percentage of non-idle processor time spent in privileged
mode.
Type

Warehouse name
PERCENT_PRIVILEGED_TIME or PPT0
CPU per Node Rollup attribute group

The percent processor time rollup.The rollup is a simple statistical processing of
the CPU utilization data from available nodes of the cluster.
Historical group
The following list contains information about each attribute in the CPU per Node
54
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum percent processor time.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum percent processor time.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average percent processor time.
Type

55
Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the percent processor time.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the percent processor time.
Type

Warehouse name
Degradation Risk attribute group

Is a characterization of the risk that application performance will degrade in the
event of a node failure.
Historical group
The following list contains information about each attribute in the Degradation
Risk attribute group:
Description
Type
56
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Node Min Capacity attribute
Description
This is the online node with the minimum processing capacity.
Type
String
Warehouse name
NODE_MIN_CAPACITY or NMC
Min Capacity attribute
Description
This is the minimum processing capacity.It is calculated as the sum
of the megahertz rating of each processor on the node.
Type

Warehouse name
MIN_CAPACITY or MC
Node Max Capacity attribute
Description
This is the node with the maximum processing capacity.
Type
String
Warehouse name
NODE_MAX_CAPACITY or NMC0
Max Capacity attribute
Description
This is the maximum processing capacity.It is calculated as the sum
of the megahertz rating of each processor on the node.
Type

57
Warehouse name
MAX_CAPACITY or MC0
Node Min Util attribute
Description
This is the online node with the minimum processor utilization.
Type
String
Warehouse name
NODE_MIN_UTIL or NMU
Min Util attribute
Description
This is the minimum processor utilization.It is calculated as the
capacity (megahertz) of the node multiplied by the percent
processor utilization.
Type

Warehouse name
MIN_UTIL
Node Max Util attribute
Description
This is the node with the maximum processor utilization.
Type
String
Warehouse name
NODE_MAX_UTIL or NMU0
Max Util attribute
Description
This is the maximum processor utilization.It is calculated as the
capacity (megahertz) of the node multiplied by the percent
processor utilization.
Type

Warehouse name
MAX_UTIL
Total Capacity attribute
58
Description
This is the total processing capacity of the cluster, assuming all
nodes are active.
Type

Warehouse name
TOTAL_CAPACITY or TC
Current Capacity attribute
Description
This is the current processing capacity of the cluster.It is the sum of
the processing capacity of active nodes.
Type

Warehouse name
CURRENT_CAPACITY or CC
Degraded Capacity attribute
Description
This is the projected processing capacity based on the current
capacity of the cluster if the highest capacity node failed.
Type

Warehouse name
DEGRADED_CAPACITY or DC
Total Util attribute
Description
This is the sum of processing capacity utilization for all active
nodes in the cluster.
Type

59
Warehouse name
TOTAL_UTIL
Uniform Commitment attribute
Description
Risk (Total Util/Degraded Capacity) as a percentage if the highest
capacity node failed and the load was spread amongst the
remaining nodes uniformly.When the percentage exceeds 100 the
cluster is at risk of not supporting the total cluster utilization.
Type

Warehouse name
UNIFORM_COMMITMENT or UC
Unitary Commitment attribute
Description
Risk ((Max Util + Min Util)/Node Capacity) as a percentage if the
highest capacity node failed and the load was given to the node
with highest available capacity.When the percentage exceeds 100
the cluster is at risk of not supporting the utilization.
Type

Warehouse name
UNITARY_COMMITMENT or UC0
Disk attribute group

Provides disk metrics collected from each node in the cluster.
Historical group
The following list contains information about each attribute in the Disk attribute
group:
60

Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Name of Node attribute - This attribute is a key attribute.
Description
Type
String
Warehouse name
NAME_OF_NODE or NON
Disk attribute - This attribute is a key attribute.
Description
The name of the disk.
Type
String
Warehouse name
DISK
Percent Free Space attribute
Description
The ratio of the free space available on the logical disk unit to the
total usable space provided by the selected logical disk drive.
Type

Warehouse name
PERCENT_FREE_SPACE or PFS
Percent Disk Write Time attribute
Description
The percentage of elapsed time that the selected disk drive is busy
servicing write requests.
Type

61
Warehouse name
PERCENT_DISK_WRITE_TIME or PDWT
Percent Disk Read Time attribute
Description
The percentage of elapsed time that the selected disk drive is busy
servicing read requests.
Type

Warehouse name
PERCENT_DISK_READ_TIME or PDRT
FreeMegabytes attribute
Description
The unallocated space on the disk drive in megabytes.
Type

Warehouse name
FREEMEGABYTES or F
Disk Write Bytes attribute
Description
The rate at which bytes are transferred to the disk during write
operations per second.
Type

Warehouse name
DISK_WRITE_BYTES or DWB
Disk Writes attribute
62
Description
The rate of write operations on the disk per second.
Type

Warehouse name
DISK_WRITES or DW
Disk Read Bytes attribute
Description
The rate at which bytes are transferred from the disk during read
operations per second.
Type

Warehouse name
DISK_READ_BYTES or DRB
Disk Reads attribute
Description
The rate of read operations on the disk per second.
Type

Warehouse name
DISK_READS
Current Disk Queue attribute
Description
The number of requests outstanding on the disk at the time the
performance data is collected.
Type

63
Warehouse name
CURRENT_DISK_QUEUE or CDQ
Disk Transfers attribute
Description
The rate of read and write operations on the disk per second.
Type

Warehouse name
DISK_TRANSFERS or DT
Disk Used Percent attribute
Description
The amount of disk space used as a percent.
Type
Integer (gauge)
Warehouse name
DISK_USED_PERCENT or DUP
Disk Write MB attribute
Description
The rate at which megabytes are transferred to the disk during
write operations per second.
Type
Integer (gauge)
Warehouse name
DISK_WRITE_MB or DWM
Disk Read MB attribute
Description
The rate at which megabytes are transferred from the disk during
read operations per second.
Type
Integer (gauge)
Warehouse name
DISK_READ_MB or DRM
Disk MB Rollup attribute group

The free space on the logical disks in MB.The rollup is a simple statistical
processing of the disk space data from available nodes of the cluster.
Historical group
64
The following list contains information about each attribute in the Disk MB Rollup
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the information.
Type
65

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the information.
Type

Warehouse name
Disk PCT Rollup attribute group

The logical disk space remaining, as a percent.The rollup is a simple statistical
processing of the disk space data from available nodes of the cluster.
Historical group
The following list contains information about each attribute in the Disk PCT Rollup
attribute group:
66
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
Type

Warehouse name
MINIMUM
Average attribute
Description
Type

67
Warehouse name
AVERAGE
Total attribute
Description
Type

Warehouse name
TOTAL
Description
Type

Warehouse name
Enterprise Cluster Summary attribute group

Provides the data that is contained in the Cluster Summary attribute group for all
the monitored Microsoft Cluster Server Agent systems in the enterprise. The data
is collected from each agent in the environment every 1 minutes. The Cluster
Summary attribute group provides information about all clusters in the enterprise.
Historical group
The following list contains information about each attribute in the Enterprise
Cluster Summary attribute group:
Description
68
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of the cluster in the enterprise.
Type
String
Warehouse name
Current Host Server attribute
Description
Type
String
Warehouse name
System Information attribute
Description
The system information of a node in the cluster.
Type
String
Warehouse name
SYSTEM_INFORMATION or SYSINFO
Percentage Processor Used attribute
Description
The percentage of the processor that is used by the cluster.
Type

Warehouse name
SYSTEM_PROCESSOR_UTILIZATION or PERCPUT
Precentage Processor Free attribute
Description
The percent of time the processor is idle in the active cluster node.
Type

69

Warehouse name
SYSTEM_PROCESSOR_IDLE or PCPUIDT
Percentage Memory Used attribute
Description
The percentage of memory that is used by the active cluster node.
Type

Warehouse name
TOTAL_MEMORY_UTILIZATION or TOULMEM
Percentage Memory Free attribute
Description
The percentage of memory that is available on the active cluster
node.
Type

Warehouse name
TOTAL_MEMORY_AVAILABLE or TOMEMAL
Description
The path of the quorum files.
Type
String
Warehouse name
QUORUM_PATH or QUOPATH
Quorum Total Size attribute
Description
The size of the quorum disk in megabytes.
Type
70

Warehouse name
QUORUM_TOTAL_SIZE or QUOTOSZ
Quorum Utilization attribute
Description
The size of the quorum disk that is used by the cluster in
megabytes.
Type

Warehouse name
QUORUM_UTILIZATION or QUOUDSZ
Quorum Available attribute
Description
The size of the quorum disk that is available in megabytes.
Type

Warehouse name
QUORUM_AVAILABLE or QUOFRSP
Percentage Quorum Used attribute
Description
The percentage of the quorum disk that is used by the cluster.
Type

Warehouse name
PERCENTAGE_QUORUM_USED or PRQUOUD
Percentage Quorum Free attribute
71
Description
The percentage of quorum disk that is available for the cluster.
Type

Warehouse name
PERCENTAGE_QUORUM_FREE or PRQUOFR
Description
shared volume) that is available in the cluster in megabytes.
Type

Warehouse name
SHARED_STORAGE_AVAILABLE or SHTFRSP
Description
shared volume) in the cluster in megabytes.
Type

Warehouse name
Description
shared volume) that is used in the cluster in megabytes.
Type
72

Warehouse name
SHARED_STORAGE_UTILIZATION or SHTUDSZ
Percentage Shared Storage Used attribute
Description
The percentage of the shared storage (shared data disk and cluster
shared volume) that is used by the cluster.
Type

Warehouse name
PERCENTAGE_SHARED_STORAGE_USED or PCTSSUD
Percentage Shared Storage Free attribute
Description
The percentage of shared storage (shared data disk and cluster
shared volume) that is available in the cluster.
Type

Warehouse name
PERCENTAGE_SHARED_STORAGE_FREE or PCTSSFR
No of Shared Storage attribute
Description
The total number of shared storage disks in the cluster.
Type

Warehouse name
TOTAL_SHARED_STORAGE or TOSHRST
Percentage Network Used attribute
Description
The percentage of maximum network that is used by the Cluster.
73
Type

Warehouse name
NETWORK_UTILIZATION or NETWKUD
Domain attribute
Description
The domain name of the cluster.
Type
String
Warehouse name
DOMAIN or CDOMAIN
Event Log attribute group

The Event Log attribute group contains any event log entries that pertain to this
application.
Historical group
The following list contains information about each attribute in the Event Log
attribute group:
Description
Type
String
Warehouse name
NODE
Log Name attribute
Description
The name of the event log - Application, System, Security or an
application-specific log
Type
String
Warehouse name
LOG_NAME or LOGNAME
Event Source attribute
Description
The event source defined by the application
Type
74
String
Warehouse name
EVENT_SOURCE or EVTSOURCE
Event Type attribute
Description
Event Type - Error(0), Warning(1), Informational(2),
Audit_Success(3), Audit_Failure(4), Unknown(5)
Type

v Error (0)
v Warning (1)
v Informational (2)
v Audit_Success (3)
v Audit_Failure (4)
v Unknown (5)
Warehouse name
EVENT_TYPE or EVTTYPE
Event ID attribute
Description
The ID of the event
Type
Integer (counter)
Warehouse name
EVENT_ID or EVTID
Event Category attribute
Description
The Category of the event
Type

v None (None)
Warehouse name
EVENT_CATEGORY or EVTCATEG
Message attribute
Description
The event message
Type
String
Warehouse name
MESSAGE
Time Generated attribute
75
Description
The time the event was generated
Type
Timestamp
Warehouse name
TIME_GENERATED or TIMESTAMP
Event Level attribute
Description
The Level value specified in the event. This is an expanded version
of the Event_Type field only available on Windows 2008 or later
Type

v Not_Available (-1)
Warehouse name
EVENT_LEVEL or EVTLEVEL
Event Keywords attribute
Description
A comma-separated list of the keywords specified in the event.
This field only available on Windows 2008 or later
Type

v Not_Available (-1)
Warehouse name
EVENT_KEYWORDS or EVTKEYWDS
Event API Version attribute
Description
The version of the Event Log API used to retrieve this event
Type

values are defined:
v NT_Event_Log (1)
v Windows_Event_Log (2)
Warehouse name
EVENT_API_VERSION or EVTAPIVER
76
Global Update Messages attribute group

The Global Update Messages attribute group provides information about the
Global Update Manager messages that are sent and received on the network.
Historical group
The following list contains information about each attribute in the Global Update
Messages attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Database Update Messages attribute
Description
The number of updated database messages from the cluster that
are sent over the network since the service was started.
Type

values are defined:
Warehouse name
DATABASE_UPDATE_MESSAGES or DATABASE_U
Database Update Messages Delta attribute
Description
The number of new updated messages in the cluster database that
are sent over the network since the data was collected.
Type

77
Warehouse name
DATABASE_UPDATE_MESSAGES_DELTA or DATABASE_0
Update Messages attribute
Description
The number of updated messages from the cluster that are sent
over the network since the service was started.
Type

values are defined:
Warehouse name
UPDATE_MESSAGES or UPDATE_MES
Update Messages Delta attribute
Description
The number of updated messages from the cluster that are sent
over the network since the data was collected.
Type

Warehouse name
UPDATE_MESSAGES_DELTA or UPDATE_ME0
Description
Type
String
Warehouse name
NAME
Memory attribute group

Provides memory metrics collected from each node in the cluster.
Historical group
78
The following list contains information about each attribute in the Memory
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
NAME_OF_NODE or NON
Memory Module attribute
Description
The name of the memory module.Usually a NULL string.
Type
String
Warehouse name
MEMORY_MODULE or MM
Available Memory MB attribute
Description
The amount of available memory in megabytes.
Type

Warehouse name
AVAILABLE_MEMORY_MB or AMM
Percent Committed Bytes In Use attribute
Description
The ratio committed to commit limit.
Type

79

Warehouse name
PERCENT_COMMITTED_BYTES_IN_USE or PCBIU
Cache Bytes attribute
Description
The number of bytes currently being used by the file system cache.
Type

Warehouse name
CACHE_BYTES or CB0
Cache Bytes Peak attribute
Description
The maximum number of cache bytes after the system was last
restarted.
Type

Warehouse name
CACHE_BYTES_PEAK or CBP
Cache Faults attribute
Description
The number of faults per second which occur when a page sought
in the file system cache is not found there and must be retrieved
from elsewhere in the memory (a soft fault) or from the disk (a
hard fault).
Type

80
Warehouse name
CACHE_FAULTS or CF
Page Faults attribute
Description
The number of page faults per second.
Type

Warehouse name
PAGE_FAULTS or PF
Page Reads attribute
Description
The number of page reads per second.
Type

Warehouse name
PAGE_READS
Page Writes attribute
Description
The number of page writes per second.
Type

Warehouse name
PAGE_WRITES or PW
Pages Input attribute
Description
The number of pages read from disk to resolve hard page faults
per second.
Type

81
Warehouse name
PAGES_INPUT or PI
Pages Output attribute
Description
The number of pages written to disk to free up space in physical
memory per second.
Type

Warehouse name
PAGES_OUTPUT or PO
Pool Paged Bytes attribute
Description
The number of bytes in the paged pool, an area of system memory
(physical memory used by the operating system) for objects that
can be written to disk when they are not being used.
Type

Warehouse name
POOL_PAGED_BYTES or PPB
Commit Limit MB attribute
Description
The amount of virtual memory that can be committed without
having to extend the paging file(s) in megabytes.
Type
Integer (gauge)
Warehouse name
COMMIT_LIMIT_MB or CLM
Committed MB attribute
Description
The amount of committed virtual memory in megabytes.
Type
82
Integer (gauge)
Warehouse name
COMMITTED_MB or CM
Cache MB attribute
Description
The number of megabytes currently being used by the file system
cache.
Type
Integer (gauge)
Warehouse name
CACHE_MB
Cache Peak MB attribute
Description
The maximum number of megabytes in the cache after the system
was last restarted.
Type
Integer (gauge)
Warehouse name
CACHE_PEAK_MB or CPM
Pool Paged MB attribute
Description
The number of megabytes in the paged pool, an area of system
memory (physical memory used by the operating system) for
objects that can be written to disk when they are not being used.
Type
Integer (gauge)
Warehouse name
POOL_PAGED_MB or PPM
Memory MB Rollup attribute group

The available memory megabytes rollup.The rollup is a simple statistical
processing of the available memory from available nodes of the cluster.
Historical group
The following list contains information about each attribute in the Memory MB
Description
Type
String
Warehouse name
NODE
Timestamp attribute
83
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
Type

Warehouse name
MINIMUM
Average attribute
Description
Type

Warehouse name
AVERAGE
Total attribute
Description
84
Type

Warehouse name
TOTAL
Description
Type

Warehouse name
Memory PCT Rollup attribute group

The percent committed bytes in use rollup.The rollup is a simple statistical
processing of the committed bytes from available nodes of the cluster.
Historical group
The following list contains information about each attribute in the Memory PCT
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
85
Maximum attribute
Description
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
Type

Warehouse name
MINIMUM
Average attribute
Description
Type

Warehouse name
AVERAGE
Total attribute
Description
Type

86
Warehouse name
TOTAL
Description
Type

Warehouse name
MRR Messages attribute group

The MRR Messages attribute group provides information about the multicast
request-response messages that are sent and received on the network.
Historical group
The following list contains information about each attribute in the MRR Messages
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Messages Outstanding attribute
Description
The number of MRR messages from the cluster that are waiting to
be sent or received in the cluster.
87
Type

Warehouse name
MESSAGES_OUTSTANDING or MESSAGES_O
Messages Sent attribute
Description
The number of MRR messages from the cluster that are sent over
the network since the service was started.
Type

values are defined:
Warehouse name
MESSAGES_SENT or MESSAGES_S
Messages Sent Delta attribute
Description
The number of new MRR messages from the cluster that are sent
over the network since the data was collected.
Type

Warehouse name
MESSAGES_SENT_DELTA or MESSAGES_0
Description
Type
String
Warehouse name
NAME
Network Interfaces attribute group

Provides the configuration details of all the network interfaces in this cluster.
88
Historical group
The following list contains information about each attribute in the Network
Interfaces attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Provides the clustering service-generated name for the network
interface.
Type
String
Warehouse name
NAME
State Raw attribute
Description
State of the network interface: Unknown(-1) Unavailable(0)
Down(1) Unreachable(2) Up(3).
Type

v Unknown (-1)
v
v
v
v
Unavailable (0)
Down (1)
Unreachable (2)
Up (3)
Warehouse name
STATE_RAW
Address attribute
89
Description
Provides the primary network address that the node uses for the
network interface.
Type
String
Warehouse name
ADDRESS
System Name attribute
Description
The scoping nodes system's name.
Type
String
Warehouse name
SYSTEM_NAME or SN
Adapter attribute
Description
Provides the name that is used to uniquely identify the network
interface in the cluster.
Type
String
Warehouse name
ADAPTER
Network Name attribute
Description
The network name to which the network interface is connected.
Type
String
Warehouse name
NETWORK_NAME or NN
Device ID attribute
Description
Provides an address or other identifying information that uniquely
identifies the network interface.
Type
String
Warehouse name
DEVICE_ID
Description
The Network Interface's description.
Type
String
Warehouse name
DESCRIPTION or D
State attribute
Description
The current raw state of the network interface mapped to a
percent: Up(100) Down(0 - for all other mapped states).
Type
90
DEFAULT(2)
Warehouse name
STATE
Network Interfaces State Rollup attribute group

The Network_Interfaces rollup.The rollup is a simple statistical processing of the
resource data from all nodes of the cluster.
Historical group
Interfaces State Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the network interface state
information.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the network interface state
information.
Type
91

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the network interface state information.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the network interface state information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the network interface state
information.
Type

Warehouse name
92
Network Performance attribute group

Provides network performance data collected from each node in the cluster.
Historical group
Performance attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
NAME_OF_NODE or NON
Network Interface attribute - This attribute is a key attribute.
Description
The name of the network interface.
Type
String
Warehouse name
NETWORK_INTERFACE or NI
Bytes Received attribute
Description
The rate at which bytes are received on the interface, including
framing characters per second.
Type

93
Warehouse name
BYTES_RECEIVED or BR
Bytes Sent attribute
Description
The rate at which bytes are sent on the interface, including framing
characters per second.
Type

Warehouse name
BYTES_SENT
Current Bandwidth attribute
Description
The estimate of the current bandwidth of the interface in gigabits
per second.
Type

Warehouse name
CURRENT_BANDWIDTH or CB
Output Queue Length attribute
Description
The length of the output packet queue in packets.
Type

Warehouse name
OUTPUT_QUEUE_LENGTH or OQL
Packets Outbound Discarded attribute
94
Description
The number of outbound packets that were chosen to be discarded
even though no errors had been detected to prevent transmission.
Type

Warehouse name
PACKETS_OUTBOUND_DISCARDED or POD
Packets Outbound Errors attribute
Description
The number of outbound packets that could not be transmitted
because of errors.
Type

Warehouse name
PACKETS_OUTBOUND_ERRORS or POE
Packets attribute
Description
The rate at which packets are sent and received on the network
interface per second.
Type

Warehouse name
PACKETS
Packets Received Discarded attribute
Description
The number of inbound packets that were chosen to be discarded
even though no errors had been detected to prevent delivery to a
higher-layer protocol.
Type

95
Warehouse name
PACKETS_RECEIVED_DISCARDED or PRD
Packets Received Errors attribute
Description
The number of inbound packets that contained errors preventing
delivery to a higher-layer protocol.
Type

Warehouse name
PACKETS_RECEIVED_ERRORS or PRE
Packets Received attribute
Description
The number of packets that are received on the network interface
per second.
Type

Warehouse name
PACKETS_RECEIVED or PR
Packets Sent attribute
Description
The number of packets that are sent on the network interface per
second.
Type

Warehouse name
PACKETS_SENT or PS
96
Bytes Total attribute

Description
The number of bytes sent and received on the interface, including
Type

Warehouse name
BYTES_TOTAL or BT
Received MB attribute
Description
The number of megabytes received on the interface, including
Type
Integer (gauge)
Warehouse name
RECEIVED_MB or RM
Sent MB attribute
Description
The number of megabytes sent on the interface, including framing
characters per second.
Type
Integer (gauge)
Warehouse name
SENT_MB
Current Bandwidth MB attribute
Description
The estimate of the interface's current bandwidth in megabytes per
second.
Type
Integer (gauge)
Warehouse name
CURRENT_BANDWIDTH_MB or CBM
Total MB attribute
Description
The number of megabytes sent and received on the interface,
including framing characters per second.
Type
Integer (gauge)
Warehouse name
TOTAL_MB
Current Bandwidth Gbps attribute
97
Description
The estimate of the interface's current bandwidth in Gigabites per
second.
Type
Real number (gauge) with 2 decimal places of precision with

enumerated values. The strings are displayed in the Tivoli
Enterprise Portal. The warehouse and queries return the values
shown in parentheses. The following values are defined:
Warehouse name
CURRENT_BANDWIDTH_GBPS or CBG
Network Performance Packets Rollup attribute group

The packets processed per second rollup.The rollup is a simple statistical
processing of the packet data from all nodes of the cluster.
Historical group
Performance Packets Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the packets per second.
Type

98
Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the packets per second.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the packets per second.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the packets per second.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the packets per second.
Type
99

Warehouse name
Network Performance Received Rollup attribute group

The bytes received per second rollup.The rollup is a simple statistical processing of
the bytes received from all nodes of the cluster.
Historical group
Performance Received Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the bytes received per second.
Type

Warehouse name
MAXIMUM
100
Minimum attribute
Description
This is the minimum value of the bytes received per second.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the bytes received per second.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the bytes received per second.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the bytes received per second.
Type

101
Warehouse name
Network Performance Sent Rollup attribute group

The bytes sent per second rollup.The rollup is a simple statistical processing of the
bytes sent from all nodes of the cluster.
Historical group
Performance Sent Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the bytes sent per second.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the bytes sent per second.
Type
102

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the bytes sent per second.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the bytes sent per second.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the bytes sent per second.
Type

Warehouse name
103
Network Reconnections attribute group

The Network Reconnections attribute group provides information about the
reconnections between the nodes of the cluster and message queue length.
Historical group
Reconnections attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Normal Message Queue Length attribute
Description
The number of normal messages that are waiting to be sent.
Type

Warehouse name
NORMAL_MESSAGE_QUEUE_LENGTH or NORMAL_MES
Reconnect Count attribute
Description
The number of reconnections between the nodes of the cluster.
Type

104
Warehouse name
RECONNECT_COUNT or RECONNECT_
Unacknowledged Message Queue Length attribute
Description
The number of messages that are not acknowledged.
Type

Warehouse name
UNACKNOWLEDGED_MESSAGE_QUEUE_LENGTH or
UNACKNOWLE
Urgent Message Queue Length attribute
Description
The number of urgent messages that are waiting to be sent.
Type

Warehouse name
URGENT_MESSAGE_QUEUE_LENGTH or URGENT_MES
Description
Type
String
Warehouse name
NAME
Networks attribute group

Provides details of the network configuration.
Historical group
105
The following list contains information about each attribute in the Networks
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of this cluster network.
Type
String
Warehouse name
NAME
State Raw attribute
Description
The state of the cluster network: Unknown(-1) Unavailable(0)
Down(1) Unreachable(2) Up(3).
Type

v Unknown (-1)
v Unavailable (0)
v Down (1)
v Unreachable (2)
v Up (3)
Warehouse name
STATE_RAW
Address attribute
Description
The address for the entire network or subnet.
Type
String
Warehouse name
ADDRESS
106
AddressMask attribute
Description
Provides the mask that distinguishes the network and host
portions of an address.
Type
String
Warehouse name
ADDRESSMASK or A
Role attribute
Description
The role the cluster network plays: None(0) InternalUse(1)
ClientAccess(2) InternalAndClient(3)
Type

v None (0)
v InternalUse (1)
v ClientAccess (2)
v Internal_And_Client (3)
Warehouse name
ROLE
Description
The network's description.
Type
String
Warehouse name
DESCRIPTION or D
State attribute
Description
The current raw state of the cluster network mapped to a percent:
Up(100) Down(0 - for all other mapped states).
Type
DEFAULT(2)
Warehouse name
STATE
Networks Messages attribute group

The Network Messages attribute group provides information about cluster network
messages sent and received on the network per cluster node.
Historical group
107
Messages attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of a node in the cluster.
Type
String
Warehouse name
NAME or NONAME
KB Received attribute
Description
The number of message KB that are received on the network since
the service was started.
Type

values are defined:
Warehouse name
BYTES_RECEIVED or BYTEREC
KB Received Delta attribute
Description
The number of new message KB that are received on the network
since the data was collected.
Type
108

Warehouse name
BYTES_RECEIVED_DELTA or BYTERED
KB Sent attribute
Description
The number of message KB that are sent on the network since the
service was started.
Type

values are defined:
Warehouse name
BYTES_SENT or BYTESNT
KB Sent Delta attribute
Description
The number of new message KB that are sent on the network since
the data was collected.
Type

Warehouse name
BYTES_SENT_DELTA or BYTESND
Messages Received attribute
Description
The number of cluster messages received on the network since the
Type

values are defined:
Warehouse name
MESSAGES_RECEIVED or MESSREC
Messages Received Delta attribute
109
Description
The number of new cluster messages received on the network since
the data was collected.
Type

Warehouse name
MESSAGES_RECEIVED_DELTA or MESSRED
Messages Sent attribute
Description
The number of cluster messages sent on the network since the
Type

values are defined:
Warehouse name
MESSAGES_SENT or MESSSNT
Messages Sent Delta attribute
Description
The number of new cluster messages sent on the network since the
data was collected.
Type

Warehouse name
MESSAGES_SENT_DELTA or MESSSND
Networks Rollup attribute group

The networks state rollup.The rollup is a simple statistical processing of the
network state data from all nodes of the cluster.
110
Historical group
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the network state information.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the network state information.
Type

Warehouse name
MINIMUM
Average attribute
111
Description
This is the average of the network state information.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the network state information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the network state information.
Type

Warehouse name
Node To Active Group attribute group

Provides the node to active group details.
Historical group
112
The following list contains information about each attribute in the Node To Active
Group attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Current RG Node attribute
Description
The name used to identify this node in the cluster.
Type
String
Warehouse name
CURRENT_RG_NODE or CRN
RG Node Changed attribute
Description
The resource group's owning node changed
Type
DEFAULT(2)
Warehouse name
RG_NODE_CHANGED or RNC
Previous RG Node attribute
Description
The node that previously owned the resource group.
Type
DEFAULT(2)
Warehouse name
PREVIOUS_RG_NODE or PRN
State of Node attribute
Description
The current state of the node: Unknown(-1) Up(0) Down(1)
Paused(2) Joining(3).
Type

v Unknown (-1)
v Up (0)
v Down (1)
113
v Paused (2)
v Joining (3)
Warehouse name
STATE_OF_NODE or SON
Description of Node attribute
Description
The node's description.
Type
String
Warehouse name
DESCRIPTION_OF_NODE or DON
Name of Group attribute - This attribute is a key attribute.
Description
The name of this resource group.
Type
String
Warehouse name
NAME_OF_GROUP or NOG
State of Group attribute
Description
The current state of this resource group: Unknown (-1) Online(0)
OffLine(1) Failed(2) PartialOnline(3) Pending(4).
Type

v Unknown (-1)
v On_Line (0)
v Off_Line (1)
v Failed (2)
v Partial_Online (3)
v Pending (4)
Warehouse name
STATE_OF_GROUP or SOG
Description of Group attribute
Description
The resource group's description.
Type
String
Warehouse name
DESCRIPTION_OF_GROUP or DOG
Node Group Names attribute - This attribute is a key attribute.
Description
Combined node name and resource group names for event display.
114
Type
String
Warehouse name
NODE_GROUP_NAMES or NGN
Nodes attribute group

Provides the detailed node information.
Historical group
The following list contains information about each attribute in the Nodes attribute
group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
NAME
State Raw attribute
Description
Type

v Unknown (-1)
v Up (0)
v Down (1)
v Paused (2)
v Joining (3)
115
Warehouse name
STATE_RAW
Major Version attribute
Description
Specifies the integer component of the version of the operating
system installed on the node.
Type
DisplayNumeric
Warehouse name
MAJOR_VERSION or MV
Minor Version attribute
Description
Specifies the decimal component of the version of the operating
system installed on the node.
Type
DisplayNumeric
Warehouse name
MINOR_VERSION or MV0
Build Number attribute
Description
Specifies the build number of the version of the operating system
installed on a node.
Type
DisplayNumeric
Warehouse name
BUILD_NUMBER or BN
Node Highest Version attribute
Description
Specifies the highest version of the cluster service with which the
node can join or communicate.
Type
DisplayNumeric
Warehouse name
NODE_HIGHEST_VERSION or NHV
NodeLowestVersion attribute
Description
Specifies the lowest version of the cluster service with which the
node can join or communicate.
Type
DisplayNumeric
Warehouse name
NODELOWESTVERSION or N
Description
Type
116
String
Warehouse name
DESCRIPTION or D
State attribute
Description
The current raw state of the node mapped to a percent: Up(100)
Down(0 - for all other mapped states).
Type
DEFAULT(2)
Warehouse name
STATE
Nodes State Rollup attribute group

The rollup of the node state.The rollup is a simple statistical processing of the state
data from all nodes of the cluster.
Historical group
The following list contains information about each attribute in the Nodes State
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the node state information.
Type

117
Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the node state information.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the node state information.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the node state information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the node state information.
Type
118

Warehouse name
Performance Object Status attribute group

The Performance Object Status attribute group contains information that reflects
the status of other attribute groups so you can see the status of all of the
performance objects that make up this application all at once. Each of these other
performance attribute groups is represented by a row in this table (or other type of
view). The status for an attribute group reflects the result of the last attempt to
collect data for that attribute group, which allows you to see whether the agent is
performing correctly. Unlike other attribute groups, the Performance Object Status
attribute group does not reflect the state of the monitored application. This
attribute group is most often used to determine why data is not available for one
of the performance attribute groups.
Historical group
The following list contains information about each attribute in the Performance
Object Status attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Query Name attribute - This attribute is a key attribute.
Description
The name of the attribute group.
Type
String
Warehouse name
QUERY_NAME or ATTRGRP
Object Name attribute
119
Description
The name of the performance object.
Type
String
Warehouse name
OBJECT_NAME or OBJNAME
Object Type attribute
Description
The type of the performance object.
Type

v WMI (0)
v
v
v
v
v
v
PERFMON (1)
WMI_ASSOCIATION_GROUP (2)
JMX (3)
SNMP (4)
SHELL_COMMAND (5)
JOINED_GROUPS (6)
v CIMOM (7)
v CUSTOM (8)
v ROLLUP_DATA (9)
v
v
v
v
WMI_REMOTE_DATA (10)
LOG_FILE (11)
JDBC (12)
CONFIG_DISCOVERY (13)
v NT_EVENT_LOG (14)
v FILTER (15)
v SNMP_EVENT (16)
v
v
v
v
PING (17)
DIRECTOR_DATA (18)
DIRECTOR_EVENT (19)
SSH_REMOTE_SHELL_COMMAND (20)
Warehouse name
OBJECT_TYPE or OBJTYPE
Object Status attribute
Description
The status of the performance object.
Type

v ACTIVE (0)
v INACTIVE (1)
120
Warehouse name
OBJECT_STATUS or OBJSTTS
Error Code attribute
Description
The error code associated with the query
Type

v NO_ERROR (0)
v GENERAL_ERROR (1)
v OBJECT_NOT_FOUND (2)
v COUNTER_NOT_FOUND (3)
v NAMESPACE_ERROR (4)
v OBJECT_CURRENTLY_UNAVAILABLE (5)
v
v
v
v
v
COM_LIBRARY_INIT_FAILURE (6)
SECURITY_INIT_FAILURE (7)
PROXY_SECURITY_FAILURE (9)
NO_INSTANCES_RETURNED (10)
ASSOCIATOR_QUERY_FAILED (11)
v REFERENCE_QUERY_FAILED (12)
v NO_RESPONSE_RECEIVED (13)
v CANNOT_FIND_JOINED_QUERY (14)
v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_1_RESULTS
(15)
v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_2_RESULTS
(16)
v QUERY_1_NOT_A_SINGLETON (17)
v QUERY_2_NOT_A_SINGLETON (18)
v NO_INSTANCES_RETURNED_IN_QUERY_1 (19)
v NO_INSTANCES_RETURNED_IN_QUERY_2 (20)
v CANNOT_FIND_ROLLUP_QUERY (21)
v
v
v
v
v
CANNOT_FIND_ROLLUP_ATTRIBUTE (22)
FILE_OFFLINE (23)
NO_HOSTNAME (24)
MISSING_LIBRARY (25)
ATTRIBUTE_COUNT_MISMATCH (26)
v
v
v
v
v
v
v
ATTRIBUTE_NAME_MISMATCH (27)
COMMON_DATA_PROVIDER_NOT_STARTED (28)
CALLBACK_REGISTRATION_ERROR (29)
MDL_LOAD_ERROR (30)
AUTHENTICATION_FAILED (31)
CANNOT_RESOLVE_HOST_NAME (32)
SUBNODE_UNAVAILABLE (33)
121
v
v
v
v
v
SUBNODE_NOT_FOUND_IN_CONFIG (34)
ATTRIBUTE_ERROR (35)
CLASSPATH_ERROR (36)
CONNECTION_FAILURE (37)
FILTER_SYNTAX_ERROR (38)
v
v
v
v
v
v
v
FILE_NAME_MISSING (39)
SQL_QUERY_ERROR (40)
SQL_FILTER_QUERY_ERROR (41)
SQL_DB_QUERY_ERROR (42)
SQL_DB_FILTER_QUERY_ERROR (43)
PORT_OPEN_FAILED (44)
ACCESS_DENIED (45)
v
v
v
v
v
v
TIMEOUT (46)
NOT_IMPLEMENTED (47)
REQUESTED_A_BAD_VALUE (48)
RESPONSE_TOO_BIG (49)
GENERAL_RESPONSE_ERROR (50)
SCRIPT_NONZERO_RETURN (51)
v SCRIPT_NOT_FOUND (52)
v SCRIPT_LAUNCH_ERROR (53)
v CONF_FILE_DOES_NOT_EXIST (54)
v
v
v
v
CONF_FILE_ACCESS_DENIED (55)
INVALID_CONF_FILE (56)
EIF_INITIALIZATION_FAILED (57)
CANNOT_OPEN_FORMAT_FILE (58)
v FORMAT_FILE_SYNTAX_ERROR (59)
v REMOTE_HOST_UNAVAILABLE (60)
v EVENT_LOG_DOES_NOT_EXIST (61)
Warehouse name
ERROR_CODE or ERRCODE
Last Collection Start attribute
Description
The most recent time a data collection of this group started
Type
Timestamp with enumerated values. The strings are displayed in

the Tivoli Enterprise Portal. The warehouse and queries return the
v NOT COLLECTED (0691231190000000)
Warehouse name
LAST_COLLECTION_START or COLSTRT
Last Collection Finished attribute
122
Description
The most recent time a data collection of this group finished
Type
Timestamp with enumerated values. The strings are displayed in

the Tivoli Enterprise Portal. The warehouse and queries return the
v NOT COLLECTED (0691231190000000)
Warehouse name
LAST_COLLECTION_FINISHED or COLFINI
Last Collection Duration attribute
Description
The duration of the most recently completed data collection of this
group in seconds
Type
Real number (counter) with 2 decimal places of precision
Warehouse name
LAST_COLLECTION_DURATION or COLDURA
Average Collection Duration attribute
Description
The average duration of all data collections of this group in
seconds
Type
Real number (counter) with 2 decimal places of precision with

v NO DATA (-100)
Warehouse name
AVERAGE_COLLECTION_DURATION or COLAVGD
Refresh Interval attribute
Description
The interval at which this group is refreshed in seconds
Type
Integer (counter)
Warehouse name
REFRESH_INTERVAL or REFRINT
Number of Collections attribute
Description
The number of times this group has been collected since agent start
Type
Integer (counter)
Warehouse name
NUMBER_OF_COLLECTIONS or NUMCOLL
Cache Hits attribute
123
Description
The number of times an external data request for this group was
satisfied from the cache
Type
Integer (counter)
Warehouse name
CACHE_HITS or CACHEHT
Cache Misses attribute
Description
The number of times an external data request for this group was
not available in the cache
Type
Integer (counter)
Warehouse name
CACHE_MISSES or CACHEMS
Cache Hit Percent attribute
Description
The percentage of external data requests for this group that were
satisfied from the cache
Type
Real number (counter) with 2 decimal places of precision
Warehouse name
CACHE_HIT_PERCENT or CACHPCT
Intervals Skipped attribute
Description
The number of times a background data collection for this group
was skipped because the previous collection was still running
when the next one was due to start
Type
Integer (counter)
Warehouse name
INTERVALS_SKIPPED or INTSKIP
Quorum Configuration attribute group

Provides important details about quorum disks that can help you find the
configuration details.
Historical group
The following list contains information about each attribute in the Quorum
Configuration attribute group:
Description
Type
124
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maintenance File attribute
Description
The location of a maintenance file.
Type
String
Warehouse name
MAINTENANCE_FILE or MAINTENANC
Quorum Log File Size attribute
Description
The size of the quorum log file, in bytes
Type

v NA (0)
Warehouse name
QUORUM_LOG_FILE_SIZE or QUORUMLOGF
Quorum Arbitration Time Maximum attribute
Description
The maximum time (in seconds) that is necessary to decide the
quorum owner node.
Type

v NA (0)
Warehouse name
QUORUM_ARBITRATION_TIME_MAX or QUORUMARB0
Quorum Arbitration Time Minimum attribute
Description
The minimum time (in seconds) that is necessary to decide the
quorum owner node.
Type

v NA (0)
125
Warehouse name
QUORUM_ARBITRATION_TIME_MIN or QUORUMARB1
Quorum Type attribute
Description
The current quorum type that is configured for the Cluster Server.
Type
String
Warehouse name
QUORUM_TYPE or QUORUMTYPE
Description
The path where quorum files are maintained.
Type
String
Warehouse name
QUORUM_PATH or QUORUMPATH
Resource Control Manager attribute group

The Resource Control Manager attribute group provides information about cluster
resources and resource host subsystem processes(rhs.exe).
Historical group
The following list contains information about each attribute in the Resource
Control Manager attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Groups Online attribute
Description
The number of online resource groups of the cluster on the node.
126
Type

Warehouse name
GROUPS_ONLINE or GROUPS_ONL
RHS Processes attribute
Description
The number of running Resource Host Subsystem processes
(rhs.exe).
Type

Warehouse name
RHS_PROCESSES or RHS_PROCES
RHS Restarts attribute
Description
The number of times the Resource Host Subsystem process restarts
(rhs.exe) restarts since the service was started.
Type

values are defined:
Warehouse name
RHS_RESTARTS or RHS_RESTAR
Description
Type
String
Warehouse name
NAME
127
Resource Group Moves attribute group

Provides statistics of the resource groups that change nodes.This metric is designed
to help track the resource groups that bounce from one node to the next.
Historical group
The following list contains information about each attribute in the Resource Group
Moves attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
Type

128
Warehouse name
MINIMUM
Average attribute
Description
Type

Warehouse name
AVERAGE
Total attribute
Description
Type

Warehouse name
TOTAL
Description
Type

Warehouse name
Resource Group To Preferred Node attribute group

Provides resource group to preferred node details.
129
Historical group
To Preferred Node attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Group Name attribute - This attribute is a key attribute.
Description
Type
String
Warehouse name
GROUP_NAME
Group State attribute
Description
The current state of this resource group: Unknown(-1) Online(0)
Type

v Unknown (-1)
v On_Line (0)
v Off_Line (1)
v Failed (2)
v Pending (4)
Warehouse name
GROUP_STATE or GS
Group Description attribute
130
Description
Type
String
Warehouse name
GROUP_DESCRIPTION or GD
Description
Type
String
Warehouse name
NAME_OF_NODE or NON
Description
Type

v Unknown (-1)
v Up (0)
v Down (1)
v Paused (2)
v Joining (3)
Warehouse name
Description
Type
String
Warehouse name
Resource Group To Resource attribute group

Provides the resource group to resource details.
Historical group
To Resource attribute group:
131

Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Group Name attribute - This attribute is a key attribute.
Description
Type
String
Warehouse name
GROUP_NAME
Group State attribute
Description
The current state of this resource group: Unknown(-1) Online(0)
Type

v Unknown (-1)
v On_Line (0)
v Off_Line (1)
v Failed (2)
v Pending (4)
Warehouse name
GROUP_STATE or GS
Group Description attribute
Description
Type
String
Warehouse name
GROUP_DESCRIPTION or GD
Resource Name attribute - This attribute is a key attribute.
132
Description
The name of this cluster resource.
Type
String
Warehouse name
RESOURCE_NAME or RN
Resource State attribute
Description
The current state of the cluster resource: Unknown(-1) Inherited(0)
Initializing(1) Online(2) Offline(3) Failed(4) Pending(128)
OnlinePending(129) OfflinePending(130).
Type

v
v
v
v
v
Unknown (-1)
Inherited (0)
Initializing (1)
Online (2)
Offline (3)
v Failed (4)
v Pending (128)
Warehouse name
RESOURCE_STATE or RS
Resource Description attribute
Description
The resource's description.
Type
String
Warehouse name
RESOURCE_DESCRIPTION or RD
Resource Groups attribute group

Provides the detailed description of the resource groups on the cluster.
Historical group
Groups attribute group:
133
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
NAME
State Raw attribute
Description
The current state of this resource group: Unknown (-1) Online(0)
Type

v Unknown (-1)
v On_Line (0)
v Off_Line (1)
v Failed (2)
v Pending (4)
Warehouse name
STATE_RAW
Persistent State attribute
Description
Specifies whether the resource group should be brought online or
left offline when the cluster service is started.
Type
134

v False (0)
v True (-1)
Warehouse name
PERSISTENT_STATE or PS
Auto FailBack Type attribute
Description
Specifies whether the group should automatically be failed back to
the node identified as its preferred owner when that node comes
back online following a failover: Prevent(0) Allow(1).
Type

v Prevent (0)
v Allow (1)
Warehouse name
AUTO_FAILBACK_TYPE or AFT
Failover Period attribute
Description
Specifies a number of hours during which a maximum number of
failover attempts, specified by the failover threshold, can occur.
Type
Integer (numeric property) with enumerated values. The strings are

values are defined:
Warehouse name
FAILOVER_PERIOD or FP
Failover Threshold attribute
Description
Specifies the maximum number of failover attempts that can be
made on a group within a time interval defined by the failover
period.
Type

values are defined:
135
Warehouse name
FAILOVER_THRESHOLD or FT
Failback Window Start attribute
Description
Provides the earliest time (the local time as kept by the cluster)
that the group can be failed back to the node identified as its
preferred owner node: 12AM(0) 11PM(23) NO(-1).
Type

values are defined:
Warehouse name
FAILBACK_WINDOW_START or FWS
Failback Window End attribute
Description
Provides the latest time that the group can be failed back to the
node identified as its preferred owner node: 12AM(0) 11PM(23)
NO(-1).
Type

values are defined:
Warehouse name
FAILBACK_WINDOW_END or FWE
Description
The resource group description.
Type
String
Warehouse name
DESCRIPTION or D
State attribute
Description
The current raw state of the cluster resource mapped to a percent:
Up(100) Partial Online(50) Down(0 - for all other mapped states).
Type
DEFAULT(2)
Warehouse name
STATE
136
Resource Groups State Rollup attribute group

The rollup of the resource group's state metric.The rollup is a simple statistical
processing of the state data from all nodes of the cluster.
Historical group
Groups State Rollup attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the resource group state information.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the resource group state information.
Type

137
Warehouse name
MINIMUM
Average attribute
Description
This is the average of the resource group state information.
Type

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the resource group state information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the resource group state
information.
Type

Warehouse name
138
Resource To Dependent Resource attribute group

The Resource To Dependent Resource attribute group provides information about
the resources that are dependent on an ascendant resource, and state of the
ascendant and dependent resources.
Historical group
The following list contains information about each attribute in the Resource To
Dependent Resource attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of the cluster resource.
Type
String
Warehouse name
RESOURCE_NAME or RN
Description
The current state of the ascendant resource. The states can be:
Unknown, Inherited, Initializing, Online, Offline, Failed, Pending,
OnlinePending, and OfflinePending.
Type

v Unknown (-1)
v Inherited (0)
v Initializing (1)
v Online (2)
v Offline (3)
v Failed (4)
139
v Pending (128)
Warehouse name
Description
The description of the resource.
Type
String
Warehouse name
Dependent Resource Name attribute - This attribute is a key attribute.
Description
The name of the dependent resource.
Type
String
Warehouse name
DEPENDENT_RESOURCE_NAME or DRN
Dependent Resource State attribute
Description
The current state of the dependent resource. The states can be:
Unknown, Inherited, Initializing, Online, Offline, Failed, Pending,
OnlinePending and OfflinePending.
Type

v Unknown (-1)
v Inherited (0)
v Initializing (1)
v Online (2)
v Offline (3)
v Failed (4)
v Pending (128)
Warehouse name
DEPENDENT_RESOURCE_STATE or DRS
Dependent Resource Description attribute
Description
The description of the dependent resource.
Type
140
String
Warehouse name
DEPENDENT_RESOURCE_DESCRIPTION or DRD
Resource To Possible Owner attribute group

Provides the resource to possible owner details.
Historical group
The following list contains information about each attribute in the Resource To
Possible Owner attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
RESOURCE_NAME or RN
Description
Type

v Unknown (-1)
v Inherited (0)
v Initializing (1)
v Online (2)
v Offline (3)
141
v
v
v
v
Failed (4)
Pending (128)
OnlinePending (129)
OfflinePending (130)
Warehouse name
Description
Type
String
Warehouse name
Description
Type
String
Warehouse name
NAME_OF_NODE or NON
Description
Type

v Unknown (-1)
v Up (0)
v Down (1)
v Paused (2)
v Joining (3)
Warehouse name
Description
Type
String
Warehouse name
142
Resources attribute group

Provides the cluster resource details.
Historical group
The following list contains information about each attribute in the Resources
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
Type
String
Warehouse name
NAME
State Raw attribute
Description
Type

v Unknown (-1)
v Inherited (0)
v Initializing (1)
v Online (2)
v Offline (3)
v Failed (4)
v Pending (128)
143
Warehouse name
STATE_RAW
Type attribute
Description
The type specifies the display name of the resource.
Type
String
Warehouse name
TYPE
Core Resource attribute
Description
If True, then the resource is essential to the cluster and cannot be
deleted.
Type

v False (0)
v True (-1)
Warehouse name
CORE_RESOURCE or CR
Persistent State attribute
Description
Specifies whether the resource should be brought online or left
offline when the cluster service is started.
Type

v False (0)
v True (-1)
Warehouse name
PERSISTENT_STATE or PS
Delete Requires All Nodes attribute
Description
If True, then the resource cannot be deleted unless all nodes are
active.
Type
144

v False (0)
v True (-1)
Warehouse name
DELETE_REQUIRES_ALL_NODES or DRAN
Is Alive Poll Interval attribute
Description
Provides the recommended interval in milliseconds at which the
cluster service should poll the resource to determine if it is
operational.The default value is -1 to indicate that a value was not
specified.
Type

values are defined:
Warehouse name
IS_ALIVE_POLL_INTERVAL or IAPI
Looks Alive Poll Interval attribute
Description
Provides the recommended interval in milliseconds at which the
cluster service should poll the resource to determine if it appears
operational.The default value is -1 to indicate that the value was
not specified.
Type

values are defined:
Warehouse name
LOOKS_ALIVE_POLL_INTERVAL or LAPI
Pending Timeout attribute
Description
Sets the number of milliseconds that a resource monitor will wait
for a resource DLL to update the status of a resource.The status of
the resource is updated in an Online Pending or Offline Pending
state before terminating the resource.
Type

145
Warehouse name
PENDING_TIMEOUT or PT
Restart Action attribute
Description
Describes the action to be taken by the cluster service if the
resource fails: DoNotRestart(0) RestartNoNotify(1) RestartNotify(2).
Type

v DoNotRestart (0)
v RestartNoNotify (1)
v RestartNotify (2)
Warehouse name
RESTART_ACTION or RA
Restart Period attribute
Description
Defines an interval of time in milliseconds, during which a
specified number of restart attempts can be made on a
nonresponsive resource.
Type

values are defined:
Warehouse name
RESTART_PERIOD or RP
Restart Threshold attribute
Description
Specifies the maximum number of restart attempts that can be
made on a resource within an interval defined by the Restart
Period, before the cluster service initiates the action specified by
the Restart Action.
Type

values are defined:
146
Warehouse name
RESTART_THRESHOLD or RT
Retry Period On Failure attribute
Description
Specifies the interval of time in milliseconds that a resource should
remain in a failed state, before the cluster service attempts to
restart it.The default value is -1 to indicate that a value was not
specified.
Type

values are defined:
Warehouse name
RETRY_PERIOD_ON_FAILURE or RPOF
Description
Type
String
Warehouse name
DESCRIPTION or D
State attribute
Description
The current raw state of the cluster resource mapped to a percent:
Up(100) Down(0 - for all other mapped states).
Type
DEFAULT(2)
Warehouse name
STATE
Resources State Rollup attribute group

The rollup of the resource's state.The rollup is a simple statistical processing of the
resource data from all nodes of the cluster.
Historical group
The following list contains information about each attribute in the Resources State
147

Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Maximum attribute
Description
This is the maximum value of the resource state information.
Type

Warehouse name
MAXIMUM
Minimum attribute
Description
This is the minimum value of the resource state information.
Type

Warehouse name
MINIMUM
Average attribute
Description
This is the average of the resource state information.
Type
148

Warehouse name
AVERAGE
Total attribute
Description
This is the sum of the resource state information.
Type

Warehouse name
TOTAL
Description
This is the standard deviation of the resource state information.
Type

Warehouse name
Resources Summary attribute group

The Resources Summary attribute group provides information about cluster
resources grouped by the resource type.
Historical group
The following list contains information about each attribute in the Resources
Description
Type
String
149
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Resource Controls attribute
Description
The total number of resource controls of various cluster resource
types.
Type

Warehouse name
RESOURCE_CONTROLS or RESOURCE_C
Resource Failure attribute
Description
The number of resources that failed since the service was started.
Type

values are defined:
Warehouse name
RESOURCE_FAILURE or RESOURCE_F
Resource Failure Access Violation attribute
Description
The number of resources that failed because of access violation
Type
150

values are defined:
Warehouse name
RESOURCE_FAILURE_ACCESS_VIOLATION or RESOURCE_0
Resource Failure Deadlock attribute
Description
The number of resources that failed because of a deadlock since
the service was started.
Type

values are defined:
Warehouse name
RESOURCE_FAILURE_DEADLOCK or RESOURCE_1
Resources Online attribute
Description
The number of online resources on the active node.
Type

Warehouse name
RESOURCES_ONLINE or RESOURCES_
Resource Type Controls attribute
Description
The number of resource type controls that are handled by the
resource Dynamic Link Library (DLL) on the node.
Type

Warehouse name
RESOURCE_TYPE_CONTROLS or RESOURCE_T
151
Description
Type
String
Warehouse name
NAME
Shared Storage Summary attribute group

The Shared Storage Summary attribute group provides information about all
cluster shared volume and shared disks.
Historical group
The following list contains information about each attribute in the Shared Storage
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Description
The name of the cluster.
Type
String
Warehouse name
Node Name attribute
Description
Type
String
Warehouse name
Shared Storage Path attribute - This attribute is a key attribute.
152
Description
The path of the cluster shared storage.
Type
String
Warehouse name
SHARED_STORAGE_PATH or SHTPATH
Description
The total size of the cluster shared storage in megabytes.
Type

Warehouse name
Description
The size of the shared storage that is avaialble in the cluster in
megabytes.
Type

Warehouse name
SHARED_STORAGE_AVAILABLE or SHTFRSC
Description
The size of shared storage that is used in the cluster in megabytes.
Type

Warehouse name
SHARED_STORAGE_UTILIZATION or SHTUDSP
Shared Storage State attribute
Description
The current state of the Cluster Shared Storage resource. The states
153
can be: Unknown(-1), Inherited(0), Initializing(1), Online(2),

Offline(3), Failed(4), Pending(128), OnlinePending(129), and
OfflinePending(130).
Type

v
v
v
v
v
v
Unknown (-1)
Inherited (0)
Initializing (1)
Online (2)
Offline (3)
Failed (4)
v Pending (128)
Warehouse name
SHARED_STORAGE_STATE or SSS
Structural Risk attribute group

A characterization of the risk of resource failure given the current available nodes.
Historical group
The following list contains information about each attribute in the Structural Risk
attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Lowest Health Resource attribute
154
Description
This is the resource with the minimum health rating.The first one
will be used in case of a tie.
Type
String
Warehouse name
LOWEST_HEALTH_RESOURCE or LHR
Current Health attribute
Description
This is a percentage representing the health rating of the
resource.The percentage is n/m, where n is the number of
currently active nodes that support the resource and m is the total
number of nodes that can support this resource.
Type

Warehouse name
CURRENT_HEALTH or CH
Health Less A Node attribute
Description
This is the health rating, if another node were to be lost from
resource.
Type

Warehouse name
HEALTH_LESS_A_NODE or HLAN
Fewest Nodes Resource attribute
Description
This is the resource with the least number of active nodes
supporting it.The first one will be used in case of a tie.
Type
String
Warehouse name
FEWEST_NODES_RESOURCE or FNR
Available Nodes attribute
Description
This is the number of nodes currently available to support the
resource.
155
Type

Warehouse name
AVAILABLE_NODES or AN
Less A Node attribute
Description
This subtracts one node from available nodes.This can be used in
situations to warn when a resource is at risk.When the value is
zero, resource is down to its last node.
Type

Warehouse name
LESS_A_NODE or LAN
Less A Node Percent attribute
Description
This is the available nodes less one divided by the configured
nodes expressed as a percentage.
Type

Warehouse name
LESS_A_NODE_PERCENT or LANP
Thread Pool Status attribute group

The Thread Pool Status attribute group contains information that reflects the status
of the internal thread pool used to collect data asynchronously.
Historical group
156
The following list contains information about each attribute in the Thread Pool
Status attribute group:
Description
Type
String
Warehouse name
NODE
Timestamp attribute
Description
Type
String
Warehouse name
TIMESTAMP
Thread Pool Size attribute
Description
The number of threads currently existing in the thread pool.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_SIZE or THPSIZE
Thread Pool Max Size attribute
Description
The maximum number of threads allowed to exist in the thread
pool.
Type

values are defined:
v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_MAX_SIZE or TPMAXSZ
Thread Pool Active Threads attribute
157
Description
The number of threads in the thread pool currently active doing
work.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_ACTIVE_THREADS or TPACTTH
Thread Pool Avg Active Threads attribute
Description
The average number of threads in the thread pool simultaneously
active doing work.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_AVG_ACTIVE_THREADS or TPAVGAT
Thread Pool Min Active Threads attribute
Description
The smallest number of threads in the thread pool that have
simultaneously been active doing work.
Type

values are defined:
v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_MIN_ACTIVE_THREADS or TPMINAT
Thread Pool Max Active Threads attribute
Description
The peak number of threads in the thread pool that have
simultaneously been active doing work.
Type
158

values are defined:
v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_MAX_ACTIVE_THREADS or TPMAXAT
Thread Pool Queue Length attribute
Description
The number of jobs currently waiting in the thread pool queue.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_QUEUE_LENGTH or TPQLGTH
Thread Pool Avg Queue Length attribute
Description
The average length of the thread pool queue during this run.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_AVG_QUEUE_LENGTH or TPAVGQL
Thread Pool Min Queue Length attribute
Description
The minimum length the thread pool queue has reached.
Type

values are defined:
v NO DATA (-1)
v NO DATA (-100)
159
Warehouse name
THREAD_POOL_MIN_QUEUE_LENGTH or TPMINQL
Thread Pool Max Queue Length attribute
Description
The peak length the thread pool queue has reached.
Type

values are defined:
v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_MAX_QUEUE_LENGTH or TPMAXQL
Thread Pool Avg Job Wait attribute
Description
The average time a job spends waiting on the thread pool queue in
seconds.
Type

v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_AVG_JOB_WAIT or TPAVJBW
Thread Pool Total Jobs attribute
Description
The number of jobs completed by all threads in the pool since
agent start.
Type

values are defined:
v NO DATA (-1)
v NO DATA (-100)
Warehouse name
THREAD_POOL_TOTAL_JOBS or TPTJOBS
160
Disk capacity planning for historical data

Disk capacity planning for a monitoring agent is a prediction of the amount of disk
space to be consumed for each attribute group with historical data that is being
collected. Required disk storage is an important factor to consider when you are
defining data collection rules and your strategy for historical data collection.
The table in this chapter provides the following information required to calculate
disk space for this monitoring agent:
v Table is the table name as it is displayed in the warehouse database, if the
attribute group is configured to be written to the warehouse. The table name
listed here corresponds to the Table name in Attribute groups and attributes for
the Microsoft Cluster Server Agent on page 27
v Attribute group is the name of the attribute group used to create the table in the
warehouse database if it is short enough to fit in the table naming constraints of
the database being used for the warehouse. The attribute group name listed here
corresponds to the Warehouse table name in Attribute groups and attributes for
the Microsoft Cluster Server Agent on page 27.
v Bytes per instance (agent) is an estimate of the record length for each row or
instance written to the agent disk for historical data collection. This estimate can
be used for agent disk space planning purposes.
v Database bytes per instance (warehouse) is an estimate of the record length for
detailed records written to the warehouse database, if the attribute group is
configured to be written to the warehouse. Detailed records are those that have
been uploaded from the agent for long-term historical data collection. This
estimate can be used for warehouse disk space planning purposes.
v Aggregate bytes per instance (warehouse) is an estimate of the record length for
aggregate records written to the warehouse database, if the attribute group is
configured to be written to the warehouse. Aggregate records are created by the
Summarization agent for attribute groups that have been configured for
summarization. This estimate can be used for warehouse disk space planning
purposes.
In addition to the information in the tables, you must know the number of
instances of data that you plan to collect. An attribute group can have single or
multiple instances of data depending on the application environment that is being
monitored. For example, if your attribute group is monitoring each processor in
your computer and you have a dual processor computer, the number of instances
is two.
The following table contains capacity planning information for the data logged by
IBM Tivoli Composite Application Manager for MS Apps: Microsoft Cluster Server
Agent.
Table 4. Capacity planning for historical data logged by Microsoft Cluster Server Agent
Database
bytes per
instance
(warehouse)
Aggregate
bytes per
instance
(warehouse)
Table
Attribute group
Bytes per
instance
(agent)
KQ5AVAIL
KQ5_AVAILABILITY
3272
3296
3606
KQ5WIN32CO
KQ5_CLUSTER_DOMAIN
140
137
174
KQ5CLUSCSV
KQ5_CLUSTER_SHARED_VOLUME
412
417
571
KQ5CLUCSVP
KQ5_CLUSTER_SHARED_VOLUME_IO
212
218
390
161
Table 4. Capacity planning for historical data logged by Microsoft Cluster Server Agent (continued)
Database
bytes per
instance
(warehouse)
Aggregate
bytes per
instance
(warehouse)
Table
Attribute group
Bytes per
instance
(agent)
KQ5CLUSUM
KQ5_CLUSTER_SUMMARY
460
477
1138
KQ5B05PHYS
KQ5_CONFIGURATION
284
284
360
KQ5D55RLL
KQ5_CPU_INTERRUPTS_ROLLUP
96
97
329
KQ5D40CPU
KQ5_CPU_PER_NODE
216
220
491
KQ5D50RLL
KQ5_CPU_PER_NODE_ROLLUP
96
97
329
KQ5G20RISK
KQ5_DEGRADATION_RISK
516
526
953
KQ5D80HDD
KQ5_DISK
328
339
883
KQ5D85RLL
KQ5_DISK_MB_ROLLUP
96
97
329
KQ5D90RLL
KQ5_DISK_PCT_ROLLUP
96
97
329
KQ5EVTLOG
KQ5_EVENT_LOG
2240
2246
2283
KQ5CLUSTE1
KQ5_GLOBAL_UPDATE_MESSAGES
192
193
338
KQ5D60MEM
KQ5_MEMORY
256
270
931
KQ5D70RLL
KQ5_MEMORY_MB_ROLLUP
96
97
329
KQ5D75RLL
KQ5_MEMORY_PCT_ROLLUP
96
97
329
KQ5CLUSTE3
KQ5_MRR_MESSAGES
188
188
318
KQ5E20NET
KQ5_NETWORKS
488
491
528
KQ5NETMESS
KQ5_NETWORKS_MESSAGES
172
177
430
KQ5E30RLL
KQ5_NETWORKS_ROLLUP
96
97
329
KQ5F20INT
KQ5_NETWORK_INTERFACES
784
789
826
KQ5F30RLL
KQ5_NETWORK_INTERFACES_STATE_ROLLUP
96
97
329
KQ5F40NET
KQ5_NETWORK_PERFORMANCE
344
371
1083
KQ5F70RLL
KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP
96
97
329
KQ5F50RLL
KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP
96
97
329
KQ5F60RLL
KQ5_NETWORK_PERFORMANCE_SENT_ROLLUP
96
97
329
KQ5NWRECON
KQ5_NETWORK_RECONNECTIONS
192
193
386
KQ5D20NODE
KQ5_NODES
784
789
826
KQ5D30RLL
KQ5_NODES_STATE_ROLLUP
96
97
329
KQ5B20LOGI
KQ5_NODE_TO_ACTIVE_GROUP
652
657
694
KQ5POBJST
KQ5_PERFORMANCE_OBJECT_STATUS
352
399
664
KQ5MSCLUST
KQ5_QUORUM_CONFIGURATION
280
282
319
KQ5C20RES
KQ5_RESOURCES
424
435
511
KQ5C30RLL
KQ5_RESOURCES_STATE_ROLLUP
96
97
329
KQ5CLUSTER
KQ5_RESOURCES_SUMMARY
200
203
402
KQ5CLUSRSC
KQ5_RESOURCE_CONTROL_MANAGER
188
188
318
KQ5B10RG
KQ5_RESOURCE_GROUPS
308
314
351
KQ5B15RLL
KQ5_RESOURCE_GROUPS_STATE_ROLLUP
96
97
329
KQ5B30RLL
KQ5_RESOURCE_GROUP_MOVES
96
97
329
KQ5B30LOGI
KQ5_RESOURCE_GROUP_TO_PREFERRED_NODE
484
486
523
162
Table 4. Capacity planning for historical data logged by Microsoft Cluster Server Agent (continued)
Database
bytes per
instance
(warehouse)
Aggregate
bytes per
instance
(warehouse)
Table
Attribute group
Bytes per
instance
(agent)
KQ5B25LOGI
KQ5_RESOURCE_GROUP_TO_RESOURCE
484
486
523
KQ5B25RTDR
KQ5_RESOURCE_TO_DEPENDENT_RESOURCE
484
486
523
KQ5B35LOGI
KQ5_RESOURCE_TO_POSSIBLE_OWNER
484
486
523
KQ5CSVSUMM
KQ5_SHARED_STORAGE_SUMMARY
284
287
441
KQ5G30RLL
KQ5_STRUCTURAL_RISK
296
299
531
KQ5THPLST
KQ5_THREAD_POOL_STATUS
124
168
550
For more information about historical data collection, see the IBM Tivoli Monitoring
Administrator's Guide.
163
164
Chapter 5. Situations reference

This chapter contains an overview of situations, references for detailed information
about situations, and descriptions of the predefined situations included in this
monitoring agent.
About situations
A situation is a logical expression involving one or more system conditions.
Situations are used to monitor the condition of systems in your network. You can
manage situations from Tivoli Enterprise Portal by using the Situation Editor.
The monitoring agents that you use to monitor your system environment are
delivered with a set of predefined situations that you can use as-is or you can
create new situations to meet your requirements. Predefined situations contain
attributes that check for system conditions common to many enterprises.
Using predefined situations can improve the speed with which you can begin
using the Microsoft Cluster Server Agent. You can examine and, if necessary,
change the conditions or values being monitored by a predefined situation to the
conditions or values best suited to your enterprise.
You can display predefined situations and create your own situations using the
Situation Editor. The left frame of the Situation editor initially lists the situations
associated with the Navigator item that you selected. When you click a situation
name or create a new situation, the right frame opens with the following tabs:
Formula
Formula describing condition being tested
Distribution
List of managed systems (operating systems, subsystems, or applications)
to which the situation can be distributed. All of the Microsoft Cluster
Server Agent managed systems are assigned by default.
Expert advice
Comments and instructions to be read in the event workspace
Action
Command to be sent to the system
Until
Options to close the event after a period of time, or when another situation
becomes true
More information about situations

Tivoli Enterprise Portal User's Guide contains more information about predefined
and custom situations and how to use them to respond to alerts.
For a list of the predefined situations for this monitoring agent and a description
of each situation, see the Predefined situations section in this chapter and the
information in that section for each individual situation.
165
Predefined situations
This monitoring agent contains the following predefined situations, which are
organized by Navigator item.
v Microsoft Cluster Server Agent
Not applicable
v Availability
KQ5_Process_Down
KQ5_WMI_Obj_Not_Available
v Cluster Dashboard
KQ5_MSCS_PMemory_Free_Warn
KQ5_MSCS_PMemory_Free_Crit
KQ5_MSCS_PNW_Utilization_Warn
KQ5_MSCS_PNW_Utilization_Crit
KQ5_MSCS_PCPU_Utilization_Warn
KQ5_MSCS_PCPU_Utilization_Crit
v Configuration
Not applicable
v Event Log
Not applicable
v Network Interfaces
KQ5_MSCS_InterfaceStateUnknown
KQ5_MSCS_InterfaceStateUnavail
KQ5_MSCS_InterfaceStateDown
KQ5_MSCS_InterfaceStateUnreach
v Networks
KQ5_MSCS_Network_StateUnknown
KQ5_MSCS_Network_StateUnavail
KQ5_MSCS_Network_StateDown
KQ5_MSCS_Network_StateUnreach
v Nodes
KQ5_MSCS_Node_Unknown
KQ5_MSCS_Node_Paused
KQ5_MSCS_Node_Down
KQ5_MSCS_Cluster_Unbalanced
KQ5_MSCS_QrmDiskSpace_Warning
KQ5_MSCS_QrmDiskSpace_Critical
v Resource Groups
KQ5_MSCS_RG_Failed
KQ5_MSCS_RG_Offline
KQ5_MSCS_RG_PartiallyOnLine
KQ5_MSCS_RG_Unknown
KQ5_MSCS_Node_Changed
v Resources
KQ5_MSCS_Resource_Failed
166
KQ5_MSCS_Resource_Offline
KQ5_MSCS_Resource_Pending
KQ5_MSCS_Resource_Pending_On
KQ5_MSCS_Resource_Pending_Off
KQ5_MSCS_Resource_Unknown
KQ5_MSCS_Resource_Initializing
KQ5_MSCS_Resource_Inherited
v Structural and Degradation Risk
Not applicable
The remaining sections of this chapter contain descriptions of each of these
situations. The situations are organized by Navigator item. The following
information is provided about each situation:
Description
Information about the conditions that the situation tests
Formula
Syntax that contains one or more logical expressions describing the
conditions for the situation to monitor
Distribution
Whether the situation is automatically distributed to instances of the agent
or is available for manual distribution
Run at startup
Whether the situation starts monitoring when the agent starts
Sampling interval
Number of seconds that elapses between one sample of data that the
monitoring agent collects for the server and the next sample
Situation persistence
Whether the conditions specified in the situation evaluate to "true" for the
defined number of occurrences in a row before the situation is raised. The
default of 1 means no persistence-checking takes place.
Severity
Severity of the predefined events: Warning, Informational, or Critical
Clearing conditions
Controls when a true situation closes: after a period of time, when another
situation is true, or whichever occurs first if both are selected.

There are no predefined situations for this Navigator item.
Availability Navigator item

KQ5_Process_Down situation
Description
Microsoft Cluster Server process is not running on this node.
The situation is evaluated for each distinct value of the COMPONENT attribute.
167
Formula
*IF *SCAN KQ5_AVAILABILITY.Name *EQ ClusSvc.exe *AND
KQ5_AVAILABILITY.Status *EQ DOWN
*VALUE
See Attribute groups and attributes for the Microsoft Cluster Server Agent on
page 27 for descriptions of the attributes in this formula.
Distribution
This situation is automatically distributed to instances of this agent.
Run at startup
Yes
Sampling interval
1 minute
The number of times the conditions of the situation must occur for the situation to
be true is 1.
Severity
Informational
Clearing conditions
The situation clears when the condition becomes false.
KQ5_WMI_Obj_Not_Available situation
Description
The Cluster WMI class is currently not available on this node.
The situation is evaluated for each distinct value of the ATTRGRP attribute.
Formula
*IF *VALUE KQ5_PERFORMANCE_OBJECT_STATUS.Object_Status *EQ INACTIVE *OR
*VALUE KQ5_PERFORMANCE_OBJECT_STATUS.Error_Code *EQ NO_INSTANCES_RETURNED
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 5.
Severity
Warning
168
Clearing conditions
Cluster Dashboard Navigator item

KQ5_MSCS_PMemory_Free_Warn situation
Description
Physical memory available is between 5.00% to 10.00%.
The situation is evaluated for each distinct value of the NAME attribute.
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.Total_Memory_Available *GT 5 *AND *VALUE
KQ5_CLUSTER_SUMMARY.Total_Memory_Available *LT 10
Distribution
This situation is available for distribution.
Run at startup
No
Sampling interval
15 minutes
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_PMemory_Free_Crit situation
Description
Physical memory available is less than 6.00%.
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.Total_Memory_Available *LT 6
Distribution
169
Run at startup
Yes
Sampling interval
5 minutes
be true is 1.
Severity
Critical
Clearing conditions
KQ5_MSCS_PNW_Utilization_Warn situation
Description
Network usage is between 40.00% and 65.00%.
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.Network_Utilization *GT 40 *AND *VALUE
KQ5_CLUSTER_SUMMARY.Network_Utilization *LT 65
Distribution
Run at startup
No
Sampling interval
30 minutes
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_PNW_Utilization_Crit situation
Description
Network usage is more than 64.00%.
170
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.Network_Utilization *GT 64
Distribution
Run at startup
No
Sampling interval
10 minutes
be true is 1.
Severity
Critical
Clearing conditions
KQ5_MSCS_PCPU_Utilization_Warn situation
Description
CPU usage is between 59.00% to 90.00%.
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *GT 59 *AND
*VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *LT 90
Distribution
Run at startup
No
Sampling interval
5 minutes
be true is 1.
Severity
Warning
Clearing conditions
171
KQ5_MSCS_PCPU_Utilization_Crit situation
Description
System CPU usage is more than 89.00%.
Formula
*IF *VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *GT 89
Distribution
Run at startup
No
Sampling interval
5 minutes
be true is 1.
Severity
Critical
Clearing conditions
Configuration Navigator item

Event Log Navigator item

Network Interfaces Navigator item

KQ5_MSCS_InterfaceStateUnknown situation
Description
The state of the Network Interface is Unknown.
Formula
*IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ -1
172
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_InterfaceStateUnavail situation
Description
The state of the Network Interface is Unavailable.
Formula
*IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ 0
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
173
KQ5_MSCS_InterfaceStateDown situation
Description
The state of the Network Interface is Down.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_InterfaceStateUnreach situation
Description
The state of the Network Interface is Unreachable.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
174
be true is 1.
Severity
Warning
Clearing conditions
Networks Navigator item

KQ5_MSCS_Network_StateUnknown situation
Description
The state of the network is Unknown.
Formula
*IF *VALUE KQ5_NETWORKS.State_Raw *EQ -1
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Network_StateUnavail situation
Description
The state of the network is Unavailable.
Formula
*IF *VALUE KQ5_NETWORKS.State_Raw *EQ 0
175
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Network_StateDown situation
Description
The state of the network is Down.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
176
KQ5_MSCS_Network_StateUnreach situation
Description
The state of the network is Unreachable.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
Nodes Navigator item

KQ5_MSCS_Node_Unknown situation
Description
The last node operation was unsuccessful (unknown state).
Formula
*IF *VALUE KQ5_NODES.State_Raw *EQ -1
Distribution
Run at startup
Yes
Sampling interval
1 minute
177
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Node_Paused situation
Description
The node is in a paused state.
Formula
*IF *VALUE KQ5_NODES.State_Raw *EQ 2
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Node_Down situation
Description
The node is inactive.
Formula
*IF *VALUE KQ5_NODES.State_Raw *EQ 1
178
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Cluster_Unbalanced situation
Description
The cluster CPU distribution is out of balance.
Formula
*IF *VALUE KQ5_CPU_PER_NODE_ROLLUP.Standard_Deviation *GT 20
Distribution
Run at startup
No
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
179
KQ5_MSCS_QrmDiskSpace_Warning situation
Description
Quorum disk is 75% full and therefore the disk space is low.
The situation will be evaluated for each distinct value of Disk.
Formula
*IF *VALUE KQ5_DISK.Percent_Free_Space *GT 5 *AND *VALUE
KQ5_DISK.Percent_Free_Space *LE 25
Distribution
Run at startup
Yes
Sampling interval
30 minutes
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_QrmDiskSpace_Critical situation
Description
Quorum disk is 95% full and therefore the disk space is low.
The situation will be evaluated for each distinct value of Disk.
Formula
*IF *VALUE KQ5_DISK.Percent_Free_Space *LE 5
Distribution
Run at startup
Yes
Sampling interval
10 minutes
180
be true is 1.
Severity
Critical
Clearing conditions
Resource Groups Navigator item

KQ5_MSCS_RG_Failed situation
Description
The resource group has failed to come online.
Formula
*IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ 2
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Critical
Clearing conditions
KQ5_MSCS_RG_Offline situation
Description
The resource group is offline.
Formula
181
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_RG_PartiallyOnLine situation
Description
The resource group is partially online.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
182
KQ5_MSCS_RG_Unknown situation
Description
The resource group is unknown
Formula
*IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ -1
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Node_Changed situation
Description
The node that the resource group was running on has changed.
The situation is evaluated for each distinct value of the CRN attribute.
Formula
*IF *VALUE KQ5_NODE_TO_ACTIVE_GROUP.RG_Node_Changed *EQ 1
Distribution
Run at startup
No
Sampling interval
30 seconds
183
be true is 1.
Severity
Warning
Clearing conditions
Resources Navigator item

KQ5_MSCS_Resource_Failed situation
Description
The resource has failed to come online.
Formula
*IF *VALUE KQ5_RESOURCES.State_Raw *EQ 4
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Warning
Clearing conditions
KQ5_MSCS_Resource_Offline situation
Description
The resource is offline.
Formula
184
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Resource_Pending situation
Description
The resource is pending state change.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
185
KQ5_MSCS_Resource_Pending_On situation
Description
The resource is pending state change to online.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Resource_Pending_Off situation
Description
The resource is pending state change to offline.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
186
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Resource_Unknown situation
Description
The resource is in an unknown state.
Formula
*IF *VALUE KQ5_RESOURCES.State_Raw *EQ -1
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Resource_Initializing situation
Description
The resource is initializing.
Formula
187
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions
KQ5_MSCS_Resource_Inherited situation
Description
The resource is in an inherited state.
Formula
Distribution
Run at startup
Yes
Sampling interval
1 minute
be true is 1.
Severity
Informational
Clearing conditions

188
Chapter 6. Take Action commands reference

This chapter contains an overview of Take Action commands, references for
detailed information about Take Action commands, and descriptions of the Take
Action commands included in this monitoring agent, if any.
About Take Action commands

Take Action commands can be run from the portal client or included in a situation
or a policy.
When included in a situation, the command runs when the situation becomes true.
A Take Action command in a situation is also referred to as reflex automation.
When you enable a Take Action command in a situation, you automate a response
to system conditions. For example, you can use a Take Action command to send a
command to restart a process on the managed system or to send a text message to
a cell phone.
Advanced automation uses policies to perform actions, schedule work, and
automate manual tasks. A policy comprises a series of automated steps called
activities that are connected to create a workflow. After an activity is completed,
the Tivoli Enterprise Portal receives return code feedback, and advanced
automation logic responds with subsequent activities prescribed by the feedback.
A basic Take Action command displays the return code of the operation in a
message box that is displayed after the action completes or in a log file. After you
close this window, no further information is available for this action.
More information about Take Action commands

For more information about working with Take Action commands, see the Tivoli
Enterprise Portal User's Guide.
For a list of the Take Action commands for this monitoring agent and a description
of each command, see the Predefined Take Action commands section in this
chapter and the information in that section for each individual command.
Predefined Take Action commands

This monitoring agent contains the following Take Action commands:
v Bring Resource Group online
v Bring Resource online
v Take Resource Group offline
v Take Resource offline
The remaining sections of this chapter contain descriptions of these Take Action
commands, which are listed alphabetically. The following information is provided
about each Take Action command:
Description
Which actions the command performs on the system to which it is sent,
and the permissions required for the Take Action command to function
189
Return codes
Information that the Take Action command returns
Bring Resource Group online action

Description
Bring Resource Group online.
System command
To include the Take Action command in a situation or workflow policy, use the
following syntax for the system command:
BRING_RESOURCE_GROUP_ONLINE \
[KQ5_RESOURCE_GROUPS.Name]
You can use attribute substitution to supply the Take Action command arguments
from the situation, for example:
[&{KQ5_RESOURCE_GROUPS.Name}]
You can also use attribute substitution in a workflow policy though the format is
slightly different:
[&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name]
Arguments
v Name: KQ5_RESOURCE_GROUPS.Name
Description: Resource group Name
Default: &KQ5_RESOURCE_GROUPS.Name
Return codes
v Return Code: 1
Return Code Type: GENERAL_ERROR
Operating systems: Windows, Windows (64-bit)
Message ID: KQ500010E
Message: Error bringing the Resource Group online.
v Return Code: 10
Return Code Type: TIMED_OUT
Message ID: KQ500011I
Message: Time-out occured briging Resource Group online.
v Return Code: 0
Return Code Type: OK
Message: The Resource Group is brought online.
v Return Code: 2
Return Code Type: ALREADY_RUNNING
Message: The Resource Group is already running.
190
v Return Code: 9
Return Code Type: WARNING
Message ID: KQ50100W
Message: The service does not exist as an installed service.
Bring Resource online action

Description
Bring Resource online.
System command
BRING_RESOURCE_ONLINE \
[KQ5_RESOURCES.Name]
[&{KQ5_RESOURCES.Name}]
slightly different:
[&WaitOnSituation:KQ5_RESOURCES.Name]
Arguments
v Name: KQ5_RESOURCES.Name
Description: Resource Name
Default: &KQ5_RESOURCES.Name
Return codes
v Return Code: 0
Message: The Resource is brought online.
v Return Code: 2
Return Code Type: ALREADY_RUNNING
Message: The Resource is already running.
v Return Code: 1
Message: Error bringing the resource online.
v Return Code: 10
191

Message: Time-out occured briging resource online.
v Return Code: 9
Take Resource Group offline action

Description
Take Resource Group offline.
System command
TAKE_RESOURCE_GROUP_OFFLINE \
[KQ5_RESOURCE_GROUPS.Name]
[&{KQ5_RESOURCE_GROUPS.Name}]
slightly different:
[&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name]
Arguments
v Name: KQ5_RESOURCE_GROUPS.Name
Description: Resource group Name
Default: &KQ5_RESOURCE_GROUPS.Name
Return codes
v Return Code: 0
Message: The Resource Group is taken offline.
v Return Code: 3
Return Code Type: NOT_RUNNING
Message: The Resource Group is already offline.
v Return Code: 1
192
Message: Error bringing the resource group offline.

v Return Code: 10
Message: Time-out occured briging resource group offline.
v Return Code: 9
Take Resource offline action

Description
Take Resource offline.
System command
TAKE_RESOURCE_OFFLINE \
[KQ5_RESOURCES.Name]
[&{KQ5_RESOURCES.Name}]
slightly different:
[&WaitOnSituation:KQ5_RESOURCES.Name]
Arguments
v Name: KQ5_RESOURCES.Name
Description: Resource Name
Default: &KQ5_RESOURCES.Name
Return codes
v Return Code: 1
Message: Error taking the resource offline.
v Return Code: 0
Message: The Resource is taken offline.
v Return Code: 3
193
Return Code Type: NOT_RUNNING

Message: The Resource is already offline.
v Return Code: 10
Message: Time-out occured taking resource offline.
v Return Code: 9
194
Chapter 7. Policies reference

This chapter contains an overview of policies, references for detailed information
about policies, and descriptions of the predefined policies included in this
monitoring agent, if any.
About policies
Policies are an advanced automation technique for implementing more complex
workflow strategies than you can create through simple automation.
A policy is a set of automated system processes that can perform actions, schedule
work for users, or automate manual tasks. You use the Workflow Editor to design
policies. You control the order in which the policy executes a series of automated
steps, which are also called activities. Policies are connected to create a workflow.
After an activity is completed, Tivoli Enterprise Portal receives return code
feedback and advanced automation logic responds with subsequent activities
prescribed by the feedback.
More information about policies

This monitoring agent does not provide predefined policies. For more information
about working with policies, see the Tivoli Enterprise Portal User's Guide.
For information about using the Workflow Editor, see the IBM Tivoli Monitoring
Administrator's Guide or the Tivoli Enterprise Portal online help.
Predefined policies
The Microsoft Cluster Server Agent does not provide predefined policies.
195
196
Chapter 8. Tivoli Common Reporting for the monitoring agent

This chapter contains descriptions of the reports that are currently available with
the Monitoring Agent for Cluster Server.
See the following additional information about using reports with this monitoring
agent:
v TheIBM Tivoli Monitoring Administrator's Guide, V6.2.2 or later contains
information about prerequisites and importing and running the reports.
v Tivoli Common Reporting troubleshooting on page 246 contains information
about common errors when using Tivoli Common Reporting with this
monitoring agent.
The IBM Tivoli Monitoring reports are historical reports that provide information
about the summarized data that is collected in the Tivoli Data Warehouse. These
reports run only on the IBM Tivoli Monitoring Cluster Server (MSCS) agent v6.2 or
later. Table 5 contains the supported databases.
Table 5. Supported databases
Database
Version
Oracle
Oracle v9.2, 10, 10g Release
DB2
MSSQL
DB2 v8.1 FP10 and higher, v8.2 FP3 and

higher, v9.1 and fix packs
SQL Server 2000 Service Pack 4, SQL Server
2005 Service Pack 2, SQL Server 2008 Service
Pack 1
Ensure that the Daily and Hourly summarization types are enabled for the
following tables:
v KQ5_DISK
v KQ5_MEMORY
v KQ5_CPU_PER_NODE
v KQ5_NETWORK_PERFORMANCE
v KQ5_NODES
v KQ5_NETWORK_INTERFACES
v KQ5_NODE_TO_ACTIVE_GROUP
v KQ5_RESOURCE_GROUP_TO_RESOURCE
v KQ5_ NETWORK
Complete documentation for the Tivoli Common Reporting tool is located at
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/
com.ibm.tivoli.tcr.doc/tcr_welcome.html
Use the following image and directory to install the Tivoli Common Reporting files
on the Tivoli Common Reporting server:
Product image: ITCAMfMSApps622
Package: \REPORTS\KQ5\ClusterReports_v1.0.zip
The reports in this chapter are grouped into the following categories:
197
Category 1: Performance reports

Disk Utilization for Cluster Nodes report
Displays the percentage of disk usage and free space on a
particular node.
Displays the amount of memory available (in MB), the amount of
committed virtual memory (in MB), the percentage of committed
bytes in use, and the cache usage (in MB) by a particular a Cluster
node.
Cluster hardware interrupts report
Displays the average or maximum number of hardware interrupts
that the processor receives and processes per second.
CPU Utilization for Cluster Nodes report
Displays the percentage of time utilized by the processor to run a
non-idle thread.
Network Interface Activity for Single Cluster Node report
Displays the average number of bytes (including the framing
characters) sent and received per second on the network interface
for a single node at a time.
Resources Utilization Details for Single Node report
Displays the disk usage, memory usage, CPU utilization, and
network utilization of a Cluster Node for a period of time.
Resource Utilization Comparison for All Nodes on single Cluster report
Displays the CPU, memory, disk, and network utilization for
maximum 16 Computer Systems or Cluster Nodes.
Cluster Nodes Utilization Summary report
Displays the average CPU, memory, and disk utilization of all the
Cluster Nodes or Computer Systems for the selected Cluster
Server.
Cluster Utilization Summary report
Displays the average CPU, memory, and disk utilization for the
selected Cluster Server.
Daily Heat Map for Cluster Nodes report
Displays the patterns of CPU, disk, and memory utilization by all
Computer Systems (nodes) for the selected Cluster Server on a
particular date.
Displays the patterns of utilization of a particular Computer
System or Cluster Node over a period of time.
Generic Template report
Using this report, you can select an attribute from any table for the
ITM Cluster Server agent and plot the top N resources in the
environment by that attribute.
Generic Details Template report
Displays the average, minimum, and maximum values of the
selected attribute over the period of time.
Category 2: Availability reports
198
Cluster Nodes availability report

Displays the data about the availability of nodes for the Cluster
Server.
Cluster Network Interface availability report
Displays the data about the availability of the network interface for
the Cluster Server nodes.
Cluster Resource group availability report
Displays the data about the availability of the resource group for
the Cluster Server nodes.
Cluster Resource availability report
Displays the availability of the resource for the selected resource
groups.
Cluster Network availability report
Displays the availability of the networks for the Cluster Server.
Category 1: Performance reports

Disk Utilization for Cluster Nodes report
Name
Disk Utilization for Cluster Nodes
Description
This report displays the percentage and average of disk usage and free space on a machine.
Purpose
You can use this report to determine the percentage of disk usage.
199
Parameters
Resource Selection
Name of Cluster
Select the name of the Cluster Server from the Name of Cluster list.
System Name
Select the name of the workstation from the System Name list.
Date Range
Report Period
Select the report period from a predefined date range, such as Last Week, Current
Month, Last 30 Days, and so on. You can also enter a start date, an end date, and the
time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget. You
must select both date and time.
End Date
Select an end date from the calendar and an end time from the time widget. You
must select both date and time.
Display Options
Summarization Type
Select the summarization types, such as Hourly, Daily, Weekly, Monthly, Quarterly,
Yearly, or Default from the list. If you select the Default option, the summarization
type is computed based on the number of days for the date range. If the selected or
required summarization view does not exist in the database, then the view is set to
Hourly or Daily based on the number of days and the chart type.
Shift and Vacation Period
Shift period
If shifts are enabled, the hourly table displays the shift period as 1 or 2, depending
on the peak and off-peak hours that are configured in the data warehouse. The daily
table consists of 1 and 2 corresponding to the peak and off-peak hours, and -1
corresponding to the summarized value for that day. If shifts are not enabled, then
the default value is -1.
Vacation Period
If the vacation period is not enabled, the default value is -1. You can enter the value
1 or 2, if the vacation period is enabled.
Tables or views
used
KQ5_DISK_DV
Output
This report displays the information about the disk utilization. For the selected summarization
type and report period, the stacked bars display the average used and free space (in GB and
percentage). This report is interactive Move the mouse pointer over the bar chart to see the
values in the hover help. Click the Cluster Server to drill down to the Utilization heat map for a
single resource that displays the disk utilization for the same time period. If no data is available
for the selected parameters, an appropriate message is displayed.
Usage
This report is used by the IT administrators to observe the percentage of the used and free disk
space on each Cluster node.

Name
Memory Utilization for Cluster Nodes
Description
This report displays the amount of committed Virtual and Available Memory for
selected machine.
Purpose
You can use this report to determine the amount of memory available, the amount of
virtual memory committed, the percentage of committed bytes in use, and the cache
usage by a particular Cluster node or Computer System.
200
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date,
an end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time
widget. You must select both date and time.
End Date
Select an end date from the calendar and an end time from the time
Display Options
Summarization Type
Select the summarization types, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option,
the summarization type is computed based on the number of days for the
date range. If the selected or required summarization view does not exist
in the database, then the view is set to Hourly or Daily based on the
number of days and the chart type.
Shift period
If shifts are enabled, the hourly table displays the shift period as 1 or 2,
depending on the peak and off-peak hours that are configured in the data
warehouse. The daily table consists of 1 and 2 corresponding to the peak
and off-peak hours, and -1 corresponding to the summarized value for
that day. If shifts are not enabled, then the default value is -1.
Vacation Period
If the vacation period is not enabled, the default value is -1. You can enter
the value 1 or 2, if the vacation period is enabled.
Tables or views used
KQ5_MEMORY_DV
Output
This report displays the information about the memory utilization. This report
contains three bar charts. The first bar chart displays the amount of memory
available (in MB) and the amount of virtual memory committed (in MB). The bar
chart contains two vertical bars with two colors, one bar represents the amount of
memory available (in MB) and the other bar represents the amount of virtual
memory committed (in MB). The second bar chart displays the cache usage (in MB)
by the selected workstation. The third bar chart displays the percentage of
committed bytes in use by the selected workstation. Click the Percent Committed
Bytes In Use bar chart to drill down to the Utilization heat map for a single resource
that displays the memory utilization for the same time period. If no data is available
for the selected parameters, an appropriate message is displayed.
Usage
This report is used by the IT administrators to determine the amount of memory

available, the amount of virtual memory committed, the percentage of committed
bytes in use, and the cache usage by a particular Cluster node or Computer System.
Cluster Hardware Interrupts report

Name
Cluster Hardware Interrupts
Description
This report displays the average number of hardware interrupts that occur on the
machine.
201
You can use this report to determine the average or maximum number of hardware
interrupts that the processor receives and processes per second.
Purpose
Parameters
Name of Cluster
The Cluster Server names will be displayed in a drop down list.
Date Range
Report Period
Start Date
End Date
Display Options
Aggregation Type
An administrator can select the maximum or average number of
interrupts from the Aggregation Type list.
Summarization Type
Select the summarization types, such as Hourly, Daily, Weekly,
Monthly, Quarterly, Yearly, or Default from the list. If you select the
Default option, the summarization type is computed based on the
number of days for the date range. If the selected or required
summarization view does not exist in the database, then the view is
set to Hourly or Daily based on the number of days and the chart
type.
Shift period
Vacation Period
KQ5_CPU_PER_NODE_DV
Output
This report displays the average or maximum number of hardware interrupts that
the processor received and processes per second. An IT administrator can view the
maximum or average number of interrupts for the Computer Systems that are
running under the selected Cluster Server. If no data is available for the selected
parameters, an appropriate message is displayed.
Usage
This report is used by the IT administrators to determine the average or maximum

number of hardware interrupts that the processor receives and processes.
CPU Utilization for Cluster Nodes report

Name
CPU Utilization for Cluster Nodes
Description
This report displays the average percentage of CPU utilization for a particular
machine.
Purpose
You can use this report to determine the percentage of time utilized by the processor
to run a non-idle thread.
202
Parameters
Name of Cluster
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
KQ5_CPU_PER_NODE_DV
Output
This report contains a bar chart that displays the percentage of time utilized by the
processor to run a non-idle thread. Click the bars in the bar chart to drill down to
the Utilization heat map for a single resource that displays the CPU utilization for
the selected Cluster Server for the same time period. If no data is available for the
selected parameters, an appropriate message is displayed.
Usage
This report is used by the IT administrators to determine the percentage of time

utilized by the processor to run a non-idle thread.
Network Interface Activity for Single Cluster Node report

Name
Network Interface Activity for Single Cluster Node
Description
This report displays the average number of bytes that are sent and received on a
particular network interface.
Purpose
You can use this report to view the number of bytes sent and received per second on
the interface.
203
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
KQ5_NETWORK_PERFORMANCE_DV
Output
This report displays the average number of bytes sent and received per second on a
network interface for a single Computer System. This report contains two bar charts.
The Bytes received/sent on Network Interface bar chart displays the number of bytes
sent and received on the interface. The Packets received/sent on Network Interface
bar chart displays the number of Packets sent and received on a particular interface.
Click the bars in the bar chart to drill down to the Resources Utilization Details for
Single Node report that displays the network utilization for the selected resource for
the same time period. If no data is available for the selected parameters, an
appropriate message is displayed.
Usage
This report is used by the IT administrators to determine the average number of

bytes sent and received per second on a network interface for a single node.
Resources Utilization Details for Single Node report

Name
Resources Utilization Details for Single Node
Description
This report displays resource utilization, that is the disk usage, memory usage, CPU
utilization, and network utilization by a particular machine.
Purpose
You can use this report to identify the system performance of a Cluster Server for a
period of time.
204
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
KQ5_MEMORY_DV, KQ5_CPU_PER_NODE_DV,
KQ5_NETWORK_PERFORMANCE_DV, KQ5_DISK_DV
Output
This report contains four line charts that display the disk usage, memory usage, CPU
utilization, and network utilization of a Computer System during the selected time
period. If no data is available for the selected parameters, an appropriate message is
displayed. If the selected summarization type is not enabled for collection, then the
type is set to Hourly or Daily summarization based on the time period. For example,
to view the data for the last 7 days, select the Hourly summarization type. To view
the data for the last 90 days, select the Weekly or Daily summarization type. For best
results, select the Default summarization type.
Usage
This report is used by the IT administrators to view information about the resource
utilization by a node. This report contains a line chart that displays the disk usage,
memory usage, CPU utilization, and network utilization for a Cluster node or
Computer System during the selected time period.
Resource Utilization Comparison for All Nodes on Single

Cluster report
Name
Resource Utilization Comparison for All Nodes on Single Cluster
Description
This report displays the CPU, memory, disk, and network usage for maximum 16
machines.
205
Purpose
You can use this report to identify the system performance problems related to the
overutilization of the system resources, such as memory, disk, and network. Using
this report, you can identify the systems that are performing poorly due to low
physical memory (that causes excessive paging), CPU intensive tasks, or poor load
balancing of applications across the available systems.
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
KQ5_MEMORY_DV, KQ5_CPU_PER_NODE_DV,
KQ5_NETWORK_PERFORMANCE_DV, KQ5_DISK_DV
Output
This report contains three overlaid line charts for the selected systems. Each line in
the line charts represents different systems. The line charts display the information
about the disk, memory, CPU, and network usage for maximum 16 systems during
the selected time period. If the selected summarization type is not enabled for
collection, then the type is set to Hourly or Daily summarization based on the
number of days. If no data is available for the selected parameters, an appropriate
message is displayed.
Usage
This report is used by the IT administrators to get information about the utilization
of the resources. This report contains a line chart that displays the disk, memory,
CPU, and network usage for multiple systems during the selected time period.
Cluster Nodes Utilization Summary report

Name
206
Cluster Nodes Utilization Summary
Description
This report displays the resource utilization, that is CPU, memory, and disk
utilization for a particular machine.
Purpose
You can use this report to identify the utilization of resources by different Cluster
Servers.
Parameters
Name of Cluster
Display Options
Number of Systems to Display
User can choose any integer to filter the number of top resources he
wishes to see.
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
Thresholds
You can enter the threshold values that are represented by the status in the
Threshold field. The default threshold values are:
v Good: Less than or equal to 20
v Fair: Between 20 and 30
v Warning: Between 30 and 50
v Bad: Between 50 and 80
v Critical: Above 80
v No Data: Data is not available
KQ5_MEMORY_DV, KQ5_CPU_PER_NODE_DV, KQ5_DISK_DV
Output
This report contains a table that displays the average CPU, memory, and disk
utilization by all resources. The values are represented by icons and the colors of the
icons represent the threshold specifications. You can filter the list to display the top
Computer Systems or Cluster Nodes that are sorted according to the CPU, disk, or
memory usage.
207
This report is used by the IT administrators to compare the multiple Cluster Server
nodes. Using this report, an IT administrator can identify the CPU, disk, and
memory utilization by a particular Cluster Server node.
Usage
Cluster Utilization Summary report

Name
Cluster Utilization Summary
Description
This report displays the resource utilization, that is CPU, memory, and disk
utilization for a particular Cluster Server.
Purpose
You can use this report to identify the utilization of resources for different Cluster
Servers.
Parameters
Display Options
Number of Systems to Display
wishes to see.
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
Thresholds
208
KQ5_MEMORY_DV, KQ5_CPU_PER_NODE_DV, KQ5_DISK_DV
Output
This report contains a table that displays the CPU, disk, and memory utilization for
all Cluster Servers. The values are represented by icons and the colors of the icons
represent the threshold specifications. Click the name of the Cluster Server in the
table to drill down to the Cluster Nodes Utilization Summary report.
Usage
This report is used by the IT administrators and managers to compare multiple

Cluster Servers. Using this report, an IT administrator can identify the CPU, disk,
and memory utilization for a particular Cluster Server.
Daily Heat Map for Cluster Nodes report

Name
Daily Heat Map for Cluster Nodes
Description
This report displays a heat map that shows a snapshot of all machines (Nodes) on
the Selected date. The first column shows all machines (Nodes) for the selected
cluster server during the selected time period, and the other columns represent
utilization data for each of the 24 hours during the day starting with 0.
Purpose
You can use this report to get a daily snapshot of the health of the Cluster Server.
Parameters
Name of Cluster
Date
Enter a date in the Date field to view the report for that day in the
MM/DD/YYYY format.
For example, 11/24/2008 12:00:00 AM
Attribute
Select an attribute from the Attribute list to plot a heat map for that
attribute. You can select CPU Utilization, Disk Utilization, Memory
Utilization, or All from the Attribute list.
Thresholds
KQ5_MEMORY_HV,KQ5_CPU_PER_NODE_HV,KQ5_DISK_HV
Output
This report contains a heat map that displays a snapshot of all Computer Systems
(nodes) for the selected date. The first column represents the name of the Computer
Systems for the selected Cluster Server and time period, and the other columns
represent the data utilization for each hour during the day starting with 0. The last
column represents the average value of the CPU, disk, or memory utilization for that
Computer Systems or Cluster Nodes. Move the mouse pointer over an icon in the
heat map to see the values in the hover help. If no data is available for the selected
parameters, an appropriate message is displayed.
Usage
This report is used by the IT administrators to view the daily performance of the
Computer Systems or Cluster Nodes that are running under the selected Cluster
Server. Using this report, an IT administrator can monitor the health of the Cluster
Server.
209

Name
Utilization Heat Map for Single Resource
Description
This report displays the patterns of utilization of a particular machine over a period
of time.
Purpose
You can use this report to identify the system performance of Cluster server over a
period of time.
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
Thresholds
KQ5_MEMORY_HV,KQ5_CPU_PER_NODE_HV,KQ5_DISK_HV
Output
This report contains a heat map. The first column represents the dates during the
selected time period and the other columns represent the hours of the day starting
with 0. The last column represents the average value of the CPU, disk, or memory
utilization for that day. Click the name of the Cluster Server to drill down to
Resources Utilization Details for Single Node report that displays the details of CPU,
disk, and memory utilization. You can specify the threshold values in parameters.
Move the mouse pointer over the icons in the heat map to see the values in the
hover help. If no data is available for the selected parameters, an appropriate
message is displayed.
Usage
This report is used by the IT administrators to view the daily performance of the
Computer Systems or Cluster Nodes that are running under the selected Cluster
Server. Using this report, an IT administrator can identify the patterns of the CPU,
disk, or memory utilization for a particular Computer System or Cluster Node over a
period of time.
Generic Template report

Name
210
Generic Template
Description
This report allows you to select any attribute from any table and for any IBM Tivoli
Monitoring Cluster Server or OS agent, and plot the top N resources in the
environment by using the attribute.
Purpose
You can use this report to generate top N report for any attribute in the Cluster
agent table.
Parameters
Attribute Selection
Table or View
All the daily Views of Cluster Servers will be displayed in a drop
down list. Select the daily views of the Cluster Servers from the Table
or View list.
Attribute
Select an attribute for the selected daily views of the Cluster Servers
from the Attribute list.
Date Range
Report Period
Start Date
End Date
Display Options
Number System to display
wishes to see.
Summarization Type
Choose the Summarization Type from the drop down list. The options
are Hourly, Daily, Weekly, Monthly, Quarterly, Yearly and Default. On
selecting Default the summarization type will be computed based on
the number of days for the date range. If the selected or required
summarization view is not present in the database it will default to
hourly or daily summarized data based on the number of days and
chart type. For best results, choose "Default" summarization type.
Shift period
Vacation Period
All the Daily views of the Cluster Server agent.
211
Output
This report contains a table that displays the average of the attributes selected for
each Cluster Server for the selected report period. If the number of Cluster Servers is
less than 20, then a bar is displayed in each row. Therefore, the table will contain 20
rows with bars for each Cluster Server. If there are more than 20 Cluster Servers, the
bar chart displays the top 20 Cluster Servers and the rest of the data is displayed in
a table. This avoids the congestion of bars in the chart. Click the bars in the bar chart
to drill down to the Details report that displays a line chart with the selected
attributes for the selected resource over a period of time. You can also click the name
of the server in the Name of Cluster column of the table to drill down to the Details
report.
Usage
This report is used to view the top N resources in the environment for a Cluster
Server agent attribute.
Generic Details Template report

Name
Generic Details Template
Description
This report allows you to select any attribute from any table for any IBM Tivoli
Monitoring Cluster or OS agent and plot a line chart of the attribute against
timestamp.
Purpose
You can use this report to view the details of the selected attribute. You can drill
down to this report from the Cluster Agent Generic Template report.
212
Parameters
Server Name
User Need to Input the Name of Cluster Server in the Server Name text
box.
Attribute Selection
Table or View
All the daily Views of Cluster Servers will be displayed in a drop
down list. Select the daily views of the Cluster Servers from the Table
or View list.
Attribute
Select an attribute for the selected daily views of the Cluster Servers
from the Attribute list.
Date Range
Report Period
Start Date
End Date
Display Options
Summarization Type
Shift period
Vacation Period
All the Daily views of the Cluster Server agent.
Output
This report contains a line chart and a table that displays the average, minimum, and
maximum values of the selected attribute for the period of time. If the selected
summarization type is not enabled for collection, then the summarization type is set
to Hourly or Daily based on the time period. it defaults to hourly or daily
summarization based on the time period. For example, for last 7 days, hourly data
can show up fine in a line chart. But for last 90 days, weekly or daily summarization
is probably a better choice. For best results, select the Default summarization type.
Usage
This report is used to view the details of an attribute over a period of time for a
particular Cluster Server.
213
Category 2: Availability reports

Cluster Nodes Availability report
Name
Cluster Nodes Availability
Description
This report displays the data about the availability of nodes in percentage for
selected Cluster server.
Purpose
You can use this report to identify the availability of nodes across the Cluster Server.
Parameters
Name of Cluster
Date Range
Report Period
Start Date
End Date
KQ5_NODES
Output
This report displays the availability of nodes (in percentage) for the selected Cluster
Server. Click the nodes in the bar chart to drill down to Network Interface
Availability report. If no data is available for the selected parameters. An appropriate
message is displayed. The values are displayed in the hover help.
Usage
This report is used by the IT administrators to view the summary of availability of

nodes (in percentage) for the Cluster Server agents.
Cluster Network Interface Availability report

Name
Cluster Network Interface Availability
Description
This report displays the data about the availability of the network interface
availability in percentage for the selected machine.
Purpose
You can use this report to identify the availability of the network interface for the
Cluster Server nodes.
214
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
KQ5_Network_Interfaces
Output
This report is used by the IT administrators to identify the availability of the

network interface (in percentage) for the selected Computer System or Cluster Node.
The values are displayed in the hover help. If no data is available for the selected
parameters, an appropriate message is displayed. The table displays the name of the
network interface, IP addresses, system name, adapter name, device ID, and network
name.
Usage

network interface for the selected Cluster Server nodes.
Cluster Resource Group Availability report

Name
Cluster Resource Group Availability
Description
This report displays the data about the availability of the resource group availability
in percentage for the selected machine.
Purpose
You can use this report to identify the availability of the resource group for the
Cluster Server nodes.
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
KQ5_NODE_TO_ACTIVE_GROUP
215
Output
This report displays the availability of the resource group (in percentage) for all
Cluster Server nodes. This report is interactive. Move the mouse pointer over the
chart to see the values in the hover help. Click the bars in the bar chart to drill down
to the Resource Availability report. If no data is available for the selected parameters,
an appropriate message is displayed.
Usage

resource group (in percentage) for all Cluster Server nodes.
Cluster Resource Availability report

Name
Cluster Resource Availability
Description
This report displays the availability of the resource for the selected resource group.
Purpose
You can use this report to identify the availability of the resource for the selected
resource groups.
Parameters
Resource Selection
Name of Cluster
System Name
Date Range
Report Period
Start Date
End Date
Output
This report displays the data for the resource availability (in percentage) for the
selected resource group. If no data is available for the selected parameters, an
appropriate message is displayed. The values are displayed in the hover help.
Usage
This report is used by the IT administrators to view the resource availability (in
percentage) for all nodes.
Cluster Network Availability report

Name
Cluster Network Availability
Description
This report displays the availability of the network in percentage for the selected
Cluster Server.
Purpose
You can use this report to identify the availability of the networks for the Cluster
Server.
216
Parameters
Name of Cluster
Date Range
Report Period
Start Date
End Date
Output
This report displays the data for the resource availability (in percentage) for the
selected resource group. If no data is available for the selected parameters, an
appropriate message is displayed. The values are displayed in the hover help.
Usage
This report is used by the IT administrators to view the resource availability (in
percentage) for all nodes.
217
218
Chapter 9. Troubleshooting
This chapter provides agent-specific troubleshooting information. See the IBM
Tivoli Monitoring Troubleshooting Guide for general troubleshooting information. Also
see Support information on page 249 for other problem-solving options.
Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in the agent prerequisites topic on the IBM Tivoli
Monitoring for Microsoft Applications Information Center.
Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing
with this product, gather the information in Table 6 that relates to the problem.
Table 6. Information to gather before contacting IBM Software Support
Information type
Description
Log files
Collect trace log files from failing systems. Most logs are located in a logs subdirectory
on the host computer. See Trace logging on page 220 for lists of all trace log files and
their locations. See the Tivoli Enterprise Portal User's Guide for general information about
the IBM Tivoli Monitoring environment.
Microsoft Cluster Server

information
Version number and patch level
Operating system
Operating system version number and patch level
Messages
Messages and other information displayed on the screen
Version numbers for

IBM Tivoli Monitoring
Version number of the following members of the monitoring environment:

v IBM Tivoli Monitoring. Also provide the patch level, if available.
v IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft
Cluster Server Agent
Screen captures
Screen captures of incorrect output, if any.
Type of device, manufacturer, model number, serial number
See http://www.ibm.com/software/support/probsub.html for information about

working with IBM Software Support.
Built-in troubleshooting features

The primary troubleshooting feature in the Microsoft Cluster Server Agent is
logging. Logging refers to the text messages and trace data generated by the
Microsoft Cluster Server Agent. Messages and trace data are sent to a file.
Trace data captures transient information about the current operating environment
when a component or application fails to operate as designed. IBM Software
Support personnel use the captured trace information to determine the source of
an error or unexpected condition. See Trace logging on page 220 for more
information.
219
Problem classification
The following types of problems might occur with the Microsoft Cluster Server
Agent:
v Installation and configuration
v General usage and operation
v Display of monitoring data
v Take Action commands
This chapter provides symptom descriptions and detailed workarounds for these
problems, and describes the logging capabilities of the monitoring agent. See the
IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.
Trace logging
Trace logs capture information about the operating environment when component
software fails to operate as intended. The principal log type is the RAS (Reliability,
Availability, and Serviceability) trace log. These logs are in the English language
only. The RAS trace log mechanism is available for all components of IBM Tivoli
Monitoring. Most logs are located in a logs subdirectory on the host computer. See
the following sections to learn how to configure and use trace logging:
v Principal trace log files on page 221
v Examples: using trace logs on page 222
v Setting RAS trace parameters on page 223
Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as
"RAS1".
IBM Software Support uses the information captured by trace logging to trace a
problem to its source or to determine why an error occurred. All components in
the IBM Tivoli Monitoring environment have a default tracing level. The tracing
level can be changed on a per-component level to adjust the type of trace
information collected, the degree of trace detail, the number of trace logs to be
kept, and the amount of disk space used for tracing.
Overview of log file management

Table 7 on page 221 provides the names, locations, and descriptions of RAS1 log
files. The log file names adhere to the following naming convention:
Windows systems
hostname_productcode_program_HEXtimestamp-nn.log
where:
v hostname is the host name of the computer where the monitoring component is
running.
v productcode is the two-character product code. For IBM Tivoli Composite
Application Manager for MS Apps: Microsoft Cluster Server Agent, the product
code is q5.
v program is the name of the program being run.
v HEXtimestamp is a hexadecimal time stamp representing the time at which the
program started.
v nn is a rolling log suffix.
220
Principal trace log files

Table 7 contains locations, file names, and descriptions of trace logs that can help
determine the source of problems with agents.
Table 7. Trace log files for troubleshooting agents
System where log
is located
File name and path
Description
On the Tivoli
Enterprise
Monitoring Server
v Windows: The file in the

install_dir\InstallITM path
Provides details about products that are

installed.
Note: Trace logging is enabled by default. A
configuration step is not required to enable this
tracing.
On the Tivoli
Enterprise
Monitoring Server
The Warehouse_Configuration.log file is in

the following location on Windows systems:
install_dir\InstallITM
Provides details about the configuration of data

warehousing for historical reporting.
On the Tivoli
Enterprise
Monitoring Server
The name of the RAS log file is as follows:
Traces activity on the monitoring server.
v Windows: install_dir\logs\
hostname_ms_timestamp-nn.log
v UNIX: install_dir/logs/
hostname_ms_timestamp-nn.log
Note: File names for RAS1 logs include a
hexadecimal time stamp.
On the Tivoli
Enterprise Portal
Server
The name of the RAS log file is as follows:
Traces activity on the portal server.
v Windows: install_dir\logs\
hostname_cq_HEXtimestamp-nn.log
Note: File names for RAS1 logs include a
hexadecimal time stamp.
On the Tivoli
Enterprise Portal
Server
The teps_odbc.log file is in the following

path:
v Windows: install_dir\InstallITM
When you enable historical reporting, this log

file traces the status of the warehouse proxy
agent.
On the computer
that hosts the
monitoring agent
The RAS1 log files are as follows:
Traces activity of the monitoring agent.
v Windows: hostname_q5_kq5agent
_HEXtimestamp-nn.log in the
install_dir\tmaitm6\logs directory
These log files are in the following
directories:
v Windows: install_dir\tmaitm6\logs
v Linux: install_dir/logs
On Linux systems, the following
additional logs are provided:
hostname_q5_timestamp.log
hostname_q5_ timestamp.pidnnnnn in
the install_dir/logs path, where
nnnnn is the process ID
221
Table 7. Trace log files for troubleshooting agents (continued)

System where log
is located
File name and path
Description
The agent operations log files are as follows: Shows whether the agent was able to connect to
the monitoring server. Shows which situations
instance_hostname_Q5.LG0 is the current log are started and stopped, and shows other events
created when the agent was started.
while the agent is running. A new version of this
file is generated every time the agent is
instance_hostname_Q5.LG1 is the backup of restarted.
the previous log.
IBM Tivoli Monitoring generates one backup
These log files are in the following
copy of the *.LG0 file with the tag .LG1. View
directories depending on the operating
.LG1 to learn the following details regarding the
system that you are using:
previous monitoring session:
v Status of connectivity with the monitoring
server.
v Situations that were running.
v The success or failure status of Take Action
commands.
The Take Action command log files are as
follows:
v host_q5_takeactioncommand.log
The logs are in the following directories:
Traces activity each time a Take Action

command runs. For example, when a
hypothetical start_command Take Action
command runs, IBM Tivoli Monitoring generates
a start_command.log file.
Definitions of variables:
timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as
follows: yyyymmdd hhmm
HEXtimestamp is a hexadecimal representation of the time at which the process was started.
install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can
represent a path on the computer that hosts the monitoring system, the monitoring agent, or the portal.
instance refers to the name of the database instance that you are monitoring.
hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs.
nn represents the circular sequence in which logs are rotated. Ranges from 1-5, by default. But the first is always
retained, because it includes configuration parameters.
productcode specifies the product code, for example, um for Universal Agent or nt for Windows.
See the IBM Tivoli Monitoring Installation and Setup Guide for more information
about the complete set of trace logs that are maintained on the monitoring server.
Examples: using trace logs

You can open trace logs in a text editor to learn some basic facts about your IBM
Tivoli Monitoring environment. The following examples are from the Tivoli
Enterprise Monitoring Server log.
Example one
This excerpt shows the typical log for a failed connection between a
monitoring agent and a monitoring server with the host name server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,
"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to
broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable
to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>
222
Example two
The following excerpts from the trace log for the monitoring server show the
status of an agent, identified here as "Remote node." The name of the
computer where the agent is running is SERVER5B:
(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:Q5 is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:Q5 is OFF-LINE.
Key points regarding the preceding excerpt:

v The monitoring server appends the Q5 product code to the server name
to form a unique name (SERVER5B:Q5) for this instance of the Microsoft
Cluster Server Agent. By using this unique name, you can distinguish
multiple monitoring products that might be running on SERVER5B.
v The log shows when the agent started (ON-LINE) and later stopped
(OFF-LINE) in the environment.
v For the sake of brevity, an ellipsis (...) represents the series of trace log
entries that were generated while the agent was running.
v Between the ON-LINE and OFF-LINE log entries, the agent was
communicating with the monitoring server.
v The ON-LINE and OFF-LINE log entries are always available in the
trace log. All trace levels that are described in Setting RAS trace
parameters provide these entries.
On Windows systems, you can use the following alternate method to view trace
logs:
1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring >
Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise
Monitoring Services window is displayed.
2. Right-click a component and select Advanced > View Trace Log in the menu.
For example, if you want to view the trace log of the Microsoft Cluster Server
agent, right-click the name of that agent in the window. You can also use the
viewer to access remote logs.
Note: The viewer converts time stamps in the logs to a format that is easier to
read.
Setting RAS trace parameters

Objective
Pinpoint a problem by setting detailed tracing of individual components of the
monitoring agent and modules.
Background Information
The Microsoft Cluster Server Agent uses RAS1 tracing and generates the logs
described in Table 7 on page 221. The default RAS1 trace level is ERROR.
Before you begin

See Overview of log file management on page 220 to ensure that you understand
log rolling and can reference the correct log files when you manage log file
generation.
After you finish

Monitor the size of the logs directory. Default behavior can generate a total of 45
MB to 60 MB for each agent that is running on a computer. For example, each
223
database instance that you monitor can generate 45 to 60 MB of log data. See the
"Procedure" section to learn how to adjust file size and numbers of log files to
prevent logging activity from occupying too much disk space.
Regularly prune log files other than the RAS1 log files in the logs directory. Unlike
the RAS1 log files that are pruned automatically, other log types can grow
indefinitely, for example, the logs in Table 7 on page 221 that include a process ID
number (PID).
Use collector trace logs as an additional source of troubleshooting information.
Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use these settings only
temporarily while you are troubleshooting problems. Otherwise, the logs can
occupy excessive amounts of hard disk space.
Procedure
On Windows systems, you can use the graphical user interface to set trace options:
1. Open the Manage Tivoli Enterprise Monitoring Services window.
2. Right-click the icon of the monitoring agent with logging you want to modify.
3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server
Trace Parameters window is displayed.
4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters
field or type a valid string.
The selections are as follows:
v General error tracing. KBB_RAS1=ERROR
v Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)
v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)
Notes: As this example shows, you can set multiple RAS tracing options in a
single statement.
5. Modify the value for 'Maximum Log Size Per File (MB)" to change the log file
size (changes LIMIT value).
6. Modify the value for 'Maximum Number of Log Files Per Session" to change
the number of log files per startup of a program (changes COUNT value).
7. Modify the value for 'Maximum Number of Log Files Total" to change the
number of log files for all startups of a program (changes MAXFILES value).
8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information
that can help you diagnose communications and connectivity problems
between the monitoring agent and the monitoring server.
Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use these settings only
temporarily, while you are troubleshooting problems. Otherwise, the logs
can occupy excessive amounts of hard disk space.
9. Click OK. You see a message reporting a restart of the monitoring agent so that
your changes take effect.
You can also manually edit the RAS1 trace logging parameters using this method:
1. Open the trace options file:
Windows: install_dir\tmaitm6\KQ5ENV
224
2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. For
example, if you want detailed trace logging, set the Maximum Tracing
option:KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of
log files:
v MAXFILES: the total number of files that are to be kept for all startups of a
given program. When this value is exceeded, the oldest log files are
discarded. Default value is 9.
v LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default
value is 5.
Notes: The KBB_RAS1_LOG parameter also provides for the specification of
the log file directory, log file name, and the inventory control file
directory and name. Do not modify these values or log information can
be lost.
4. Restart the monitoring agent so that your changes take effect.
Problems and workarounds

The following sections provide symptoms and workarounds for problems that
might occur with the Microsoft Cluster Server Agent:
v
v
v
v
v
Installation and configuration troubleshooting on page 225

Remote deployment troubleshooting on page 230
Agent troubleshooting on page 232
Workspace troubleshooting on page 235
Situation troubleshooting on page 242
Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in the Microsoft Cluster Server agent
prerequisites topic on the IBM Tivoli Monitoring for Microsoft Applications
Information Center.
This Troubleshooting chapter provides agent-specific troubleshooting information.
See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting
information.
Installation and configuration troubleshooting

This section provides tables that show solutions for installation, configuration, and
uninstallation problems.
Table 8. Problems and solutions for installation and configuration
Problem
Solution
A problem can arise when you install and configure a

new monitoring agent on a computer where other
agents are running as described in this example:
You must reconfigure the previously existing agents to

restore their communication connection with TEMS1. For
example, you can right-click the row for a specific agent
in the Manage Tivoli Enterprise Monitoring Services, and
select Reconfigure. See the IBM Tivoli Monitoring
Installation and Setup Guide for more information about
reconfiguration.
v Agents are running on a computer and

communicating with a Tivoli Enterprise Monitoring
Server, called TEMS1.
v You install a new agent on the same computer and
you want this agent to communicate with a different
monitoring server, called TEMS2.
v When you configure the new agent to communicate
with TEMS2, all the existing agents are reconfigured
to communicate with TEMS2.
225
Table 8. Problems and solutions for installation and configuration (continued)

Problem
Solution
Diagnosing problems with product browse settings

(Windows systems only).
When you have problems with browse settings, perform

the following steps:
1. Click Start > Programs > IBM Tivoli Monitoring >
Manage Tivoli Enterprise Monitoring Services. The
Manage Tivoli Enterprise Monitoring Services window
is displayed.
2. Right-click the Windows agent and select Browse
Settings. A text window is displayed.
3. Click Save As and save the information in the text file.
A message similar to "Unable to find running CMS on

CT_CMSLIST" in the log file is displayed.
If a message similar to "Unable to find running CMS on

CT_CMSLIST" is displayed in the log file, the agent
cannot connect to the monitoring server. Confirm the
following points:
v Do multiple network interface cards (NICs) exist on the
system?
v If multiple NICs exist on the system, find out which
one is configured for the monitoring server. Ensure that
you specify the correct host name and port settings for
communication in the IBM Tivoli Monitoring
environment.
The system is experiencing high CPU usage.
Agent process: View the memory usage of the KQFCMA

process. If CPU usage seems to be excessive, recycle the
monitoring agent.
Network Cards: The network card configurations can
decrease the performance of a system. Each of the stream
of packets that a network card receives (assuming that it
is a broadcast or destined for the under-performing
system) must generate a CPU interrupt and transfer the
data through the I/O bus. If the network card in question
is a bus-mastering card, work can be offloaded and a data
transfer between memory and the network card can
continue without using CPU processing power.
Bus-mastering cards are 32-bit and are based on PCI or
EISA bus architectures.
Two or more Windows system names appear in the

Navigation view for the same cluster.
Check the configuration (cluster name) parameter on each

node of the cluster and ensure that they are identical. If
not, perform the following steps:
1. Take the agent cluster resource offline.
2. Reconfigure all the agents with the Microsoft Cluster
Name.
3. Bring the agent cluster resource back online. Clear the
offline MSN instances.
Remove MSN from Windows system navigation after
applying pending updates.
226

Problem
Solution
Two or more instances of the agent (IBM Tivoli

Monitoring for Cluster Managers: Microsoft Cluster
Servers) appear under the windows system name.
Check the configuration (cluster name) parameter on each

node of the cluster. This name is case sensitive, and if the
case does not match the other nodes, another instance of
the agent is displayed under the Windows system name.
Take the agent cluster resource offline. Reconfigure all the
agents with the Microsoft Cluster Name matching case.
Bring the agent cluster back online. Clear the offline
instances of IBM Tivoli Monitoring for Cluster Managers:
Microsoft Cluster Servers agents. MS Cluster Server
appears after applying pending updates.
When new V6.1 or V6.2 agent support files are added to See "When new agent support files are added to V6.2.1,
the portal server configuration portion of the installation
IBM Tivoli Monitoring V6.2.1 on Windows 2008, the
portal server configuration portion of the installation
hangs" in the "Installation and configuration
troubleshooting" chapter of the IBM Tivoli Monitoring
hangs.
Troubleshooting Guide.
When you install a 32-bit agent of IBM Tivoli Composite There is no solution to this problem.
Application Manager for Microsoft Applications on a
computer that has a preinstalled 64-bit version of the
same agent, the 32-bit agent is not installed. However,
when you run the KinCinfo -i command, the 32-bit
agent is displayed in the list of installed components.
After the installation is completed, the preinstalled
64-bit agent stops running.
If you have installed a 64-bit agent for IBM Tivoli
Composite Application Manager for Microsoft
Applications, information about the agent processes is
not displayed in the Kinviewer window.
There is no solution to this problem.
When you install a 32-bit agent for IBM Tivoli

Applications, under the Install the following features
list, the following message is displayed:
Undefined GSK component:IBM GSKit Security
Interface.
Ignore this message and proceed with the installation.
You have preinstalled agents of IBM Tivoli Composite

Application Manager for Microsoft Applications on your
computer. When you run the IBM Tivoli Composite
Application Manager for Microsoft Applications
installation wizard to upgrade the agent to V6.2.2, the
Select Features window displays a list of all the agent
features that you can install. The installed agents are
selected by default. If you do not want to upgrade the
installed features, you cannot clear the default selection.
Run the setup.exe file of the Windows OS agent V6.2.2 or

later to install the Tivoli Enterprise Monitoring Agent
Framework. Then, upgrade the preinstalled agents of IBM
Tivoli Composite Application Manager for Microsoft
Applications.
While installing the Microsoft Applications agent, you

specified not to install the Tivoli Enterprise Monitoring
Agent Framework. However, the Tivoli Enterprise
Monitoring Agent Framework gets installed.
You have installed two 32-bit Microsoft application

agents and the 32/64-bit Agent Compatibility Package
(ACP) from the 64-bit agent of IBM Tivoli Composite
Application Manager for Microsoft Applications. You
cannot install additional 32-bit Microsoft application
agents on the same managed system.
Reinstall the agent compatibility package from the

installation wizard of the IBM Tivoli Composite
Application Manager for Microsoft Applications V6.2.2,
Fix Pack 1.
227

Problem
Solution
After you upgrade IBM Tivoli Composite Application

Manager for Microsoft Applications from an earlier
version to V6.2.2, the following entries are created in the
Add or Remove Programs windows:
Ignore IBM Tivoli Monitoring for Microsoft

Applications in the Add or Remove Programs window. If
you want to modify or remove the installed agents in IBM
Tivoli Monitoring for Microsoft Applications, use IBM
Tivoli Monitoring from the Add or Remove Programs
window.
v IBM Tivoli Monitoring for Microsoft Applications

v IBM Tivoli Monitoring
The entry for IBM Tivoli Monitoring is removed from
the Add or Remove Programs window if you install a
component of ITCAM for Microsoft Applications, 32-bit
agent in the following situations:
1. You have installed Windows OS, 64-bit on your
computer.
Run the setup.exefile of the Windows OS agent, V6.2.2,

Fix Pack 2 to install the ACP.
Note: You can also install the ACP by running the
setup.exe file of ITCAM for Microsoft Applications, 64-bit
agent.
2. You have installed the 32/64-bit Agent Compatibility

Package (ACP) of ITCAM for Microsoft Applications,
64-bit agent.
Table 9. General problems and solutions for uninstallation
Problem
Solution
On Windows, uninstallation of
IBM Tivoli Monitoring fails to
uninstall the entire environment.
Be sure that you follow the general uninstallation process described in the IBM
Tivoli Monitoring Installation and Setup Guide:
1. Remove Tivoli Enterprise Monitoring Server Application support by
completing the following steps:
a. Use Manage Tivoli Enterprise Monitoring Services.
b. Select Tivoli Enterprise Monitoring Server.
c. Right-click and select Advanced.
d. Select Remove TEMS application support.
e. Select the agent to remove its application support.
2. Uninstall monitoring agents first, as in the following examples:
v Uninstall a single monitoring agent for a specific database.
-ORv Uninstall all instances of a monitoring product, such as IBM Tivoli
Monitoring for Databases.
3. Uninstall IBM Tivoli Monitoring.
The way to remove inactive

managed systems (systems whose
status is OFFLINE) from the
Navigator tree in the portal is not
obvious.
Use the following steps to remove, but not uninstall, an offline managed system
from the Navigator tree:
1. Click the Enterprise icon in the Navigator tree.
2. Right-click, and then click Workspace > Managed System Status.
3. Right-click the offline managed system, and select Clear offline entry.
If you also want to uninstall the monitoring agent, use the procedure described
in the IBM Tivoli Monitoring Installation and Setup Guide.
Cluster Agent Resource does not

run on node.
228
If the agent is uninstalled on a node in the cluster, it must be removed from the
possible node list defined in the agent cluster resource. If the agent is removed
from a node and that is the only node active in the cluster, the agent is not
available.
Table 9. General problems and solutions for uninstallation (continued)

Problem
Solution
IBM Tivoli Monitoring might not

be able to generate a unique
name for monitoring components
because of the truncation of
names that the product
automatically generates.
The length of the name that IBM Tivoli Monitoring generates is limited to 32
characters. Truncation can result in multiple components having the same
32-character name. If this problem happens, shorten the hostname portion of the
name. The Microsoft Cluster Name configuration parameter is used to create the
Windows system name that is displayed in the Tivoli Enterprise Portal. The
Microsoft Cluster Name configuration is used to set CTIRA_HOSTNAME, which
is the hostname part of the managed system name. Follow the instructions in
Chapter 2, Agent-specific installation and configuration information for the
monitoring agent, on page 7 to set CTIRA_HOSTNAME.
You have installed the Windows

OS agent V6.2.2 or later on your
computer. The Windows OS agent
does not start if you uninstall a
32-bit agent for IBM Tivoli
Composite Application Manger
for Microsoft Applications by
using the following methods:
Perform the following steps to resolve this problem:
v The silent_agent.txt file
Note: If IBM Tivoli Monitoring is not displayed in the Add or Remove

Programs window, then run the setup.exe file for IBM Tivoli Composite
Application Manager for Microsoft Applications to install the Tivoli Enterprise
Monitoring Agent Framework. You can find the setup.exe file in the
Agent_64bit\WINDOWS directory.
v The command: tacmd

removeSystem -t <agentcode>
-n <node>
For example, tacmd
removeSystem t qp n
Primary:MachineName:NT
1. In the KGLWICMA.VER and KUIWICLI.VER files in the InstallITM/ver directory,

lower the VRMF values.
For example, if the value is 06220000, then change this value to 06210000.
2. Run the setup.exe file for the Windows OS agent to install the Tivoli
Enterprise Monitoring Agent Framework.
3. Start the Windows OS agent.
v The remove option on the

Tivoli Enterprise Portal
The following error message is
displayed:
The service did not respond to
the start or control request in
a timely fashion. KCICF5100E
Unable to start, see Event Log
for information.
229
Table 9. General problems and solutions for uninstallation (continued)

Problem
Solution
You have a 32-bit agent of

ITCAM for Microsoft
Applications installed on your
computer. If you uninstall the
32-bit agent, two entries of IBM
Tivoli Monitoring are created in
the Add or Remove Programs
window in the following
situations:
Restart the preinstalled agent. Ignore the IBM Tivoli Monitoring entry for
V6.2.1 in the Add or Remove Programs window. To modify or remove the
installed agents, use the IBM Tivoli Monitoring entry for V6.2.2 in the Add or
Remove Programs window.
v With the 32-bit agent, you have

Windows OS agent V6.2.2 or
later installed on a managed
system and you uninstall the
32-bit agent from the Tivoli
Enterprise Portal or by using
the command: tacmd
removeSystem -t <agentCode>
-n <node>
v With the 32-bit agent, you have
64-bit agent of ITCAM for
Microsoft Applications installed
on a managed system and you
uninstall the 32-bit agent using
the silent_agent.txt file.
In both the situations, when you
uninstall the 32-bit agent, the
preinstalled agent stops running.
Remote deployment troubleshooting

Table 10 lists problems that might occur with remote deployment. This section
provides information about troubleshooting remote deployment of the monitoring
agent. See the IBM Tivoli Monitoring Troubleshooting Guide for general
troubleshooting information.
This section describes problems and solutions for remote deployment and removal
of agent software using Agent Remote Deploy process.
Table 10. Remote deployment problems and solutions
Problem
Solution
While you are using the remote deployment feature Do not close or modify this window. It is part of the
to install the Microsoft Cluster Server Agent, an
installation process and is dismissed automatically.
empty command window is displayed on the target
computer. This problem occurs when the target of
remote deployment is a Windows computer. (See the
IBM Tivoli Monitoring Installation and Setup Guide for
more information about the remote deployment
feature.)
KDY1008E error when using remote operations to
remove the last instance of the agent.
230
There are two windows when removing an agent when it is

the last instance. The first asks to remove the instance. The
second asks to uninstall. If you say Yes to the first and then
No to the second for a single-instance agent, you always get
the KDY1008E error. The workaround is to always say Yes in
the second window to uninstall.
Table 10. Remote deployment problems and solutions (continued)

Problem
Solution
The removal of a monitoring agent fails when you

use the remote removal process in the Tivoli
Enterprise Portal desktop or browser.
This problem might occur when you attempt the remote

removal process immediately after you have restarted the
Tivoli Enterprise Monitoring Server. You must allow time for
the monitoring agent to refresh its connection with the Tivoli
Enterprise Monitoring Server before you begin the remote
removal process.
A problem can arise when you try to perform

remote operations to the agent while the agent
cluster resource controlling the agent is online.
Some remote operations might require the agent to be taken

offline. If the cluster resource is online, the cluster server
attempts to bring the agent back online therefore interfering
with the remote operations.
Take the agent cluster resource offline while performing
remote operations. When remote operations are complete,
bring the agent cluster resource back online.
Cannot remotely access the Microsoft Cluster Server

agent on a cluster that does not own the agent
cluster resource.
Use local tools to update and manage these agents. An

alternative to using local tools is to manually move the agent
cluster resource to the node you want to update. Then take
the agent cluster resource offline, update the agent, and then
bring the agent cluster resource back online.
Use the tacmd addBundles command to populate the depot

The install.sh command from a UNIX/ Linux CD
does not allow you to populate an agent depot if the for binaries on different CDs.
agent binaries do not exist on the CD.
For example, to populate a UNIX/Linux depot with
For example, the install.sh command from a UNIX Windows binaries for the IBM Tivoli Monitoring for Cluster
CD does not allow you to populate the depot with
Managers: Microsoft Cluster Servers agent, use the following
Windows agent binaries, because the Windows
command:
binaries are on a separate CD, or in a separate
$ tacmd addBundles -i /q5v610a4.final/image/WINDOWS
location on the same CD.
/Deploy -t q5
KUICAB023I: Are you sure you want to add the following
bundles from the /build12/steve/candle/tables
/TIVOLI/depot depot?
Product Code : Q5
Version : 061000000
Description : Monitoring Agent for Microsoft Cluster
Server
Host Type : WINNT
Host Version : WINNT
Prerequisites:
KUICAB024I: Enter Y for yes or N for no: Y
What are the remote deploy CLI parameters for the
agent?
The IBM Tivoli Monitoring command line is documented in

the IBM Tivoli Monitoring Installation and Setup Guide. Also,
see Chapter 2, Agent-specific installation and configuration
information for the monitoring agent, on page 7 in this
guide.
For the section name, CTIRA_HOSTNAME, the configuration
parameter for remote deploy is as follows:
section.configParameter
For remote configuration of an active node where -m
managed system name is that of the Microsoft Cluster Server
agent the command line is as follows:
tacmd configureSystem -m CTIRA_HOSTNAME:Q5 -p
MSCS.CTIRA_HOSTNAME="new hostname"
MSCS.CTIRA_HIST_DIR="new directory name"
231
Agent troubleshooting
This section lists problems that might occur with agents.
This chapter provides agent-specific troubleshooting information. See the IBM
Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.
Table 11. Agent problems and solutions
Problem
Solution
Log data accumulates too

rapidly.
Check the RAS trace option settings, which are described in Setting RAS trace
parameters on page 223. The trace options settings that you can set on the
KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.
If you want to receive multiple

trace logs for separate
invocations of the same Take
Action command, leaving this
setting on permanently fills the
available disk space.
Do not leave this setting on permanently. By doing so, you create a new log file
for each invocation of the Take Action command and all of them are left on the
agent system.
Multicast warning messages

To troubleshoot multicast cluster issues check the following article in the
from the Cluster Network Driver Microsoft Knowledge Base:
(Clusnet.sys) appear in the
http://support.microsoft.com/kb/307962/
Windows system log.
A second agent is started on a
node other than the node
currently running the agent
under the control of the cluster
agent resource. The second agent
takes over the Managed System
Name in the portal and the
second agent does not relinquish
control of the Managed System
Name.
In a clustered environment, each node of the cluster has an agent configured

with the same Managed System Name. Which node is running the agent is
controlled by the Cluster Server through the Agent Resource.
If by accident a second agent instance on a node not owning the Cluster Agent
Resource is started, the agent for this second node takes over control of the
Managed System Name in the portal.
To return control of the Managed System Name to the node owning the Cluster
Agent resource, complete the following steps:
1. Stop the second instance of the agent on the node not owing the Cluster
Agent resource.
2. Recycle the agent on the node owning the Cluster Agent Resource by using
the Cluster Administrator. (Take the agent cluster resource offline, and then
bring it back online.)
Warning messages from ClusSvc

concerning 'The node lost
communication with cluster node
ComputerName on network xx.'
Event ID 1123 and event ID 1122 might be logged consecutively to the System
log in your cluster. Frequently, these events indicate temporary interruptions in
intra-cluster communication and can be ignored. Refer to the following Microsoft
support article:
http://support.microsoft.com/?kbid=892422
Rollup Error messages in the

agent log file.
232
Rollup Error messages occur when a base WMI query fails and there is no source
data to "roll up." Check the log for the initial WMI error to resolve. The rollup
error disappears when the initial problem is corrected.
Table 11. Agent problems and solutions (continued)

Problem
Solution
Known issue with the Microsoft WMI Cluster Association class provider,
working with Microsoft to resolve. Until a fix is available, the following
workaround has been provided from Microsoft. It sets the Cluster WMI provider
to run in a standalone WMIprvse.exe host. The script also lowers the cache
OR
timeout to 30 seconds. So, if the cluster provider is idle for more than 30 seconds,
then the hosting WMIprvse.exe process is recycled, minimizing the effect of the
WMIPrsve.exe memory increases leak.
to 135MB before recycling.
1. Copy and paste the following into a file and save with a .vbs extension (for
example, wmi_fix.vbs). If the comments (lines beginning with ') cause
problems, remove them.
WMI Error 0x80041006 There
was not enough memory for the
operation.
'===[ Script start ]===================================

Set objLocator = CreateObject("wbemscripting.swbemlocator")
set WMIServices = objLocator.ConnectServer(".","root")
set cachecontrol = WMIServices.Get("__ObjectProviderCacheControl=@")
cachecontrol.ClearAfter = "00000000000025.000000:000"
cachecontrol.Put_ set WMIServices =
objLocator.ConnectServer(".","root\MSCluster")
set ClusProvReg = WMIServices.Get
("__Win32Provider.Name=""MS_CLUSTER_PROVIDER""")
ClusProvReg.HostingModel =
"NetworkServicehost:ClusterProvider" ClusProvReg.Put_
'===[ Script stop ]===================================
2. Run it on each computer on which the agent is running.
3. Reboot.
If the problem persists (this typically happens if there are multiple objects
querying WMI -- like a second agent). Try reducing the cache time from 25
seconds to a lower value.
Agent log files are not in
CANDLEHOME/tmaitm6/logs
directory
If you reset the logging level to "none," and then turns logging back on by
setting the logging level to something other than "none," the Manage Tivoli
Enterprise Monitoring Services utility automatically resets the log directory to
CANDLEHOME/logs.
Logging is not affected. Older logs remain in CANDLEHOME/TMAITM6/logs. New
logs are placed in CANDLEHOME/logs.
You can manually edit the ENV file using Manage Tivoli Enterprise Monitoring
Services:
1. Right-click the agent. Select Advanced > Edit ENV file.
2. Adjust the line prefixed by KBB_RAS1_LOG to the line in the example. You
must substitute ITM_HOME with the path to your IBM Tivoli Monitoring
installation directory.
-ORYou can also add "\TMAITM6" before all "\logs" in the KBB_RAS1_LOG line.
Example:
KBB_RAS1_LOG=ITM_HOME\TMAITM6\logs\$(computername)_q5_kq5agent_$
(sysutcstart)-.log INVENTORY=ITM_HOME\TMAITM6\logs\
$(computername)_q5_kq5agent.inv
COUNT=03 LIMIT=5 PRESERVE=1 MAXFILES=9
Failover Cluster Management

changed to Failover Cluster
Manager.
In Windows 2008 R2, the terminology Failover Cluster Management has been
changed to Failover Cluster Manager. While referring to the Expert Advice for
situations in MSCS agent V6.2.0.1 on all Windows 2008 R2 operating systems, the
term Failover Cluster Management is referring to Failover Cluster Manager.
233

Problem
Solution
A configured and running

instance of the monitoring agent
is not displayed in the Tivoli
Enterprise Portal, but other
instances of the monitoring agent
on the same system do appear in
the portal.
Tivoli Monitoring products use Remote Procedure Call (RPC) to define and
control product behavior. RPC is the mechanism that allows a client process to
make a subroutine call (such as GetTimeOfDay or ShutdownServer) to a server
process somewhere in the network. Tivoli processes can be configured to use
TCP/UDP, TCP/IP, SNA, and SSL as the protocol (or delivery mechanism) for
RPCs that you want.
"IP.PIPE" is the name given to Tivoli TCP/IP protocol for RPCs. The RPCs are
socket-based operations that use TCP/IP ports to form socket addresses. IP.PIPE
implements virtual sockets and multiplexes all virtual socket traffic across a
single physical TCP/IP port (visible from the netstat command).
A Tivoli process derives the physical port for IP.PIPE communications based on
the configured, well-known port for the hub Tivoli Enterprise Monitoring Server.
(This well-known port or BASE_PORT is configured by using the 'PORT:'
keyword on the KDC_FAMILIES / KDE_TRANSPORT environment variable and
defaults to '1918'.)
The physical port allocation method is defined as (BASE_PORT + 4096*N), where
N=0 for a Tivoli Enterprise Monitoring Server process and N={1, 2, ..., 15} for a
non-Tivoli Enterprise Monitoring Server. Two architectural limits result as a
consequence of the physical port allocation method:
v No more than one Tivoli Enterprise Monitoring Server reporting to a specific
Tivoli Enterprise Monitoring Server hub can be active on a system image.
v No more than 15 IP.PIPE processes can be active on a single system image.
A single system image can support any number of Tivoli Enterprise Monitoring
Server processes (address spaces) if each Tivoli Enterprise Monitoring Server on
that image reports to a different hub. By definition, there is one Tivoli Enterprise
Monitoring Server hub per monitoring Enterprise, so this architecture limit has
been simplified to one Tivoli Enterprise Monitoring Server per system image.
No more than 15 IP.PIPE processes or address spaces can be active on a single
system image. With the first limit expressed above, this second limitation refers
specifically to Tivoli Enterprise Monitoring Agent processes: no more than 15
agents per system image.
This limitation can be circumvented (at current maintenance levels, IBM Tivoli
Monitoring V6.1, Fix Pack 4 and later) if the Tivoli Enterprise Monitoring Agent
process is configured to use the EPHEMERAL IP.PIPE process. (This process is
IP.PIPE configured with the 'EPHEMERAL:Y' keyword in the KDC_FAMILIES /
KDE_TRANSPORT environment variable). There is no limitation to the number
of ephemeral IP.PIPE connections per system image. If ephemeral endpoints are
used, the Warehouse Proxy Agent is accessible from the Tivoli Enterprise
Monitoring Server associated with the agents using ephemeral connections either
by running the Warehouse Proxy Agent on the same computer or by using the
Firewall Gateway feature. (The Firewall Gateway feature relays the Warehouse
Proxy Agent connection from the Tivoli Enterprise Monitoring Server computer
to the Warehouse Proxy Agent computer if the Warehouse Proxy Agent cannot
coexist on the same computer.)
234

Problem
Solution
You have installed a 32-bit

Windows OS agent and a 64-bit
agent of ITCAM for Microsoft
Applications on a 64-bit
managed system. If the 64-bit
agent abruptly stops running, the
Agent Management Service
(AMS) fails to restart the agent.
The status of the agent in the
Agents Management Status
view changes to Unmanaged.
There are two possible solutions to this problem:

Solution 1: Restart the 64-bit agent and then restart the AMS by performing
these steps:
The IBM Tivoli Composite

Application Manager for
Microsoft Cluster Server Agent,
V622 displays data for the
attributes groups only on
Windows Server 2008 R2 for the
following attribute groups:
1. Right-click the agent, which is in the unmanaged state, and click Take Action
> Select.
2. From the Name list in the Action panel, select AMS Start Management.
3. In the Destination Systems panel, select the managed system node for the
agent that you want to start.
4. Click OK.
Solution 2: Install the Windows OS agent V6.2.2, Fix Pack 2.
v Clustered Shared Volume

v Clustered Shared Volume IO
v Global update messages
v MRR Messages
v Network Reconnections
v Network Messages
v Resource Control Manager
v Resources Summary
The agent does not display the
data on Windows Server 2003
and Windows Server 2008 for the
above mentioned attribute
groups.
You have installed the ITCAM
Microsoft Applications agent and
the Windows OS agent in the
IPV6 environment. In the Agent
Management Services navigator
item, the IP address in the
Agents Runtime Status view is
displayed in the IPV4 format
instead of the IPV6 format.
Workspace troubleshooting
Table 12 on page 236 shows problems that might occur with workspaces. This
chapter provides agent-specific troubleshooting information. See the IBM Tivoli
Monitoring Troubleshooting Guide for general troubleshooting information.
235
Table 12. Workspace problems and solutions

Problem
Solution
The process application components are

available, but the Availability status shows
PROCESS_DATA_NOT_ AVAILABLE.
This problem occurs because the PerfProc performance object is

disabled. When this condition exists, IBM Tivoli Monitoring
cannot collect performance data for this process. Perform the
following steps to confirm that this problem exists and resolve it:
1. Choose Run in the Windows Start menu.
2. Type perfmon.exe in the Open field of the Run window. The
Performance window is displayed.
3. Click the plus sign (+) in the tool bar located above the right
pane. The Add Counters window is displayed.
4. Look for Process in the Performance object pull-down menu.
5. Perform one of the following actions:
v If you see Process in the pull-down menu, the PerfProc
performance object is enabled and the problem is coming
from a different source.
v If you do not see Process in the pull-down menu, use the
Microsoft utility from the following Web site to enable the
PerfProc performance object:
http://blogs.technet.com/mscom/archive/2008/12/18/
the-mystery-of-the-missing-process-performancecounter-in-perfmon.aspx
The Process performance object becomes visible in the
Performance object pull-down menu of the Add Counters
windows, and IBM Tivoli Monitoring is able to detect
Availability data.
6. Restart the monitoring agent.
The process application components are

available, but the Availability status shows
PROCESS_DATA_NOT_ AVAILABLE.
This problem occurs because the PerfProc performance object is

disabled. When this condition exists, IBM Tivoli Monitoring
cannot collect performance data for this process. Complete the
following steps to confirm that this problem exists and resolve it:
1. Choose Run in the Windows Start menu.
2. Type perfmon.exe in the Open field of the Run window. The
Performance window is displayed.
3. Click the plus sign (+) in the tool bar located above the right
pane. The Add Counters window is displayed.
4. Look for Process in the Performance object pull-down menu.
5. Perform one of the following actions:
v If you see Process in the pull-down menu, the PerfProc
performance object is enabled and the problem is coming
from a different source.
v If you do not see Process in the pull-down menu, use the
Microsoft utility from the following Web site to enable the
PerfProc performance object:
http://blogs.technet.com/mscom/archive/2008/12/18/
the-mystery-of-the-missing-process-performancecounter-in-perfmon.aspx
The Process performance object becomes visible in the
Performance object pull-down menu of the Add Counters
windows, and IBM Tivoli Monitoring is able to detect
Availability data.
6. Restart the monitoring agent.
236
Table 12. Workspace problems and solutions (continued)

Problem
Solution
No Data in Workspace View or Error code =

0x80041003 The current user does not have
permission to perform the action in agent log.
The agent must be started with a valid ID on all nodes of the

cluster. On the computer running the agent, perform the
following steps:
1. Start Manage Tivoli Enterprise Monitoring Services.
2. Select Actions > Change Startup > This Account.
3. Enter the user ID and password that are valid on all nodes of
the cluster.
4. Click OK.
Links from The Microsoft Cluster Server agent

views to other agent views do not populate data
at the target workspace.
The link Symbol named NODE needs to be created to resolve the

expression value.
This can be done by going to the Expression page for the Link
and clicking New at the bottom of the left navigation tree. Type
NODE in the window that is displayed. A NODE item is
displayed under the Link Symbols part of the tree and you can
set its expression to "$AGENT" + ":" + "NODE$" When the
expression is tested (click the test button), the expression resolves
to $AGENT:NODE$.
The Link on the Nodes table in the Nodes workspace is an
example of how the link must be set.
At the bottom of the historical view, you see the

following error: KFWITM220E Request failed
during execution
Ensure that you configure History. In the Historical

Configuration view, ensure that data collection is configured and
started. It takes two collection intervals for the data to first
appear. If you choose 5 minutes, the first point of data shows up
after 5 minutes. On the Tivoli Enterprise Portal Server:
Configuration
1. Select Edit > History Configuration > Select A Product.
2. Choose MS Cluster Server.
3. Select the Groups you want to monitor.
4. Set the Configuration Controls to the levels you want.
5. Click Configure Groups to complete the configuration.
To start the history collection:
1. Select the Groups you want to monitor (repeat step 3 above).
2. Click Start Collection.
Expert Advice pages do not show in a Simplified This problem is caused by IBM JVM 1.4.2. Use the following
Chinese environment situation editor.
workaround to fix this issue:
In the Advanced tab of the IBM 1.4.2 plug-in control panel, set
-Dibm.stream.nio=true as the Java Runtime Parameter for your
Simplified Chinese environment.
237

Problem
Solution
Message IDs are appearing in portal views

instead of English text or the appropriate
language text.
This problem can happen when the Desktop browser is open

during agent installation causing the cnp.bat file to be locked.
CNP.bat was not updated to include the language jar file. To
manually repair this file, complete the following steps:
1. Edit the cnp.bat file.
2. Append to the classpath @set CLASSPATH kq5_resources.jar
to cnp.bat
-Or1. Shut down the Configuration tool.
2. Add Tivoli Enterprise Monitoring Server Application support
for the agent.
Question marks show up for cluster name

configuration parameter and in the host name
field of the Managed System Name.
IBM Tivoli Monitoring V6.1 configuration support is currently

not globalized. English must be used to enter the Cluster Name
in the configuration panel. If non-English characters are used,
including characters using simple diacritic marks, those
characters show up as question marks in the configuration and
in the Tivoli Enterprise Portal. Reconfigure the agent and enter a
new ASCII English Cluster Name to resolve the issue.
Event Log workspace events are unfiltered, are

not collected more than every 60 seconds, and
are removed from the Event Log Views after 1
hour of being received.
All events currently in the Application Event Log are sent to the
Tivoli Enterprise Monitoring Server when the agent starts.
Environment variables that control the behavior of the Event Log
Workspace are stored in the agent ENV file on the Tivoli
Enterprise Monitoring Agent, where the agent is running. These
are the variables:
CDP_DP_CACHE_TTL
This value is the minimum number of seconds before
data (for a particular table) is collected again. By default
this variable is present in the ENV file and the value is
set to 60.
CDP_NT_EVENT_LOG_GET_ALL_ENTRIES_FIRST_TIME
This variable determines whether the agent sends all
events currently in the Application Event Log to the
Tivoli Enterprise Monitoring Server when the agent
starts. Legal values are YES and NO. By default this
variable is present in the ENV file and the value is set to
NO.
CDP_NT_EVENT_LOG_CACHE_TIMEOUT
This variable determines how long in seconds, events
are displayed in the Tivoli Enterprise Monitoring Server
Event Log Views. By default this variable is NOT
present in the ENV file. A default value of 3600 (1 Hour)
is used unless overridden by the presence of this
variable in the agent ENV file. The minimum legal value
is 300.
To view or edit the agent ENV file, on the Tivoli Enterprise
Monitoring agent where the agent is installed, use Manage Tivoli
Enterprise Monitoring Services to select the agent. Right-click
and select Advanced - Edit ENV File. The agent must be
restarted to implement changes.
238

Problem
Solution
The name of the attribute does not display in a

bar chart or graph view.
When a chart or graph view that includes the attribute is scaled

to a small size, a blank space is displayed instead of a truncated
name. To see the name of the attribute, expand the view of the
chart until there is sufficient space to display all characters of the
attribute name.
You start collection of historical data but the data Managing options for historical data collection:
cannot be seen.
v Basic historical data collection populates the Warehouse with
raw data. This type of data collection is turned off by default.
See the IBM Tivoli Monitoring Administrator's Guide for
information about managing this feature including how to set
the interval at which data is collected. By setting a more
frequent interval for data collection you reduce the load on the
system incurred every time data is uploaded.
v You use the Summarization and Pruning monitoring agent to
collect specific amounts and types of historical data. Historical
data is not displayed until the Summarization and Pruning
monitoring agent begins collecting the data. By default, this
agent begins collection at 2 AM daily. At that point, data is
visible in the workspace view. See the IBM Tivoli Monitoring
Administrator's Guide to learn how to modify the default
collection settings.
Historical data collection is unavailable because
of incorrect queries in the Tivoli Enterprise
Portal.
The column, Sort By, Group By, and First/Last functions are not
compatible with the historical data collection feature. Use of
these advanced functions makes a query ineligible for historical
data collection.
Even if data collection has been started, you cannot use the time
span feature if the query for the chart or table includes column
functions or advanced query options (Sort By, Group By, First /
Last).
To ensure support of historical data collection, do not use the
Sort By, Group By, or First/Last functions in your queries.
See the IBM Tivoli Monitoring Administrator's Guide or the Tivoli
Enterprise Portal online help for information about the Historical
Data Collection function.
When you use a long process name in the

situation, the process name is truncated.
Truncation of process or service names for situations in the

Availability table in the portal display is the expected behavior.
100 bytes is the maximum name length.
Regular (non-historical) monitoring data fails to

be displayed.
Check the formation of the queries you use to gather data. For
example, look for invalid SQL statements.
239

Problem
Solution
Historical data is unavailable.
v Local time differences for the Tivoli Enterprise Portal, Tivoli

Enterprise Monitoring Server, and the monitoring agent can
affect history. History is stored at the monitoring agent.
v Check that a directory is present on the shared disk and that
all the agents are configured to use that directory.
v Check for OpenHistoryFiles errors in the agent log to see if
history files are created.
v If there is no shared disk provided for the agent, history must
be stored at the Tivoli Enterprise Monitoring Server. Ensure
that history is set up to be stored at Tivoli Enterprise
Monitoring Server.
v If you have a hub and a remote Tivoli Enterprise Monitoring
Server, historical data collection should be started correctly on
that Tivoli Enterprise Monitoring Server.
Event Message and Event Category attributes in

the Event Log workspace and Event Message
attribute in the Event Log Summary workspace
do not show proper data on the following server
systems:
There is no solution for this problem at this time.
v Windows 2008 Enterprise Edition (32-bit)

v Windows 2008 Datacenter Edition (32-bit)
v Windows 2008 Enterprise Edition (64-bit)
v Windows 2008 Datacenter Edition (64-bit)
v Windows 2008 IA64
The Tivoli Enterprise Portal shows data only for 32-bit
No row of data for 64-bit applications is
applications. There is no solution for this problem at this time.
displayed in the workspaces when the
monitoring agent is running on a 64-bit operating
system.
Navigator items and workspace titles are labeled
with internal names such as Kxx:KXX0000 or
Kxx:KXX0000 rather than the correct names (such
as Disk), where XX and xx represent the
two-character agent code.
Ensure that application support has been added on the

monitoring server, portal server, and portal client.
For more information and instruction on installing application
support, see "Installing and enabling application support" in the
IBM Tivoli Monitoring Installation and Setup Guide.
Install Windows OS agent V6.2.2, Fix Pack 2.

You have installed a 32-bit agent for IBM Tivoli
Applications on a computer where a 64-bit
Windows OS agent V6.2.2, Fix Pack 1 is installed.
On the Tivoli Enterprise Portal, when you
expand the Windows OS node, and select the
Agent Management Services navigator item, the
installation path of the agent is not correctly
displayed in the Agents Management
Definitions view. Also, no data is displayed for
the agent version and the build number in the
Agents Management Status view.
240

Problem
Solution
You have installed the Windows OS agent V6.2.1, Uninstall the agent from your local computer.
Fix Pack 1, or V6.2.2, Fix Pack 2, and the
Microsoft Applications agent on an
Itanium-based managed system. If you remotely
uninstall the agent by using the remove option
on the Tivoli Enterprise Portal or by using the
command:
tacmd removeSystem -t <agentcode> <node>, the
agent is not uninstalled. However, the Tivoli
Enterprise Portal deployment status displays that
the agent is uninstalled.
If the 32-bit OS agent and a 64-bit Microsoft
application agent are installed on the same
managed system, Proxy Agent Services data is
not displayed in the Agents Runtime Status view
of the agent. The Agents Runtime Status view is
available in the Agent Management Services
workspace.
You have installed the ITCAM for Microsoft
Applications agent and the Windows OS agent in
the IPV6 environment. In the Agent
Management Services navigator, the IP address
in the Agents Runtime Status view is displayed
in the IPV4 format instead of the IPV6 format.
241

Problem
Solution
You have installed the Tivoli Enterprise

Reconfigure the history collection and set the collection location
Monitoring Server on z/OS. In the Configuration as TEMA for these attribute groups.
panel of the History Collection Configuration
window, if you have selected TEMS from the
Collection Location list, then the Tivoli
Enterprise Portal does not display historical data
for the following attribute groups:
v Availability
v Resource Groups
v Resource Groups State Rollup
v Resource Group Moves
v Cluster Summary
v
Kq5 Enterprise Cluster Resources
v Resources State Rollup

v Nodes State Rollup
v Cpu per Node
v Cpu per Node Rollup
v Cpu Interrupts Rollup
v Memory
v Memory MB Rollup
v Memory pct Rollup
v Disk
v Disk MB Rollup
v Disk pct Rollup
v Event log
v Networks
v Networks Rollup
v Network Interfaces
v Network Interfaces State Rollup
v Network Performance
v Network Performance Received Rollup
v Network Performance Sent Rollup
v Network Performance Packets Rollup
v Performance Object Status
v Structural Risk
v Thread Pool Status
Situation troubleshooting
This section provides information about both general situation problems and
problems with the configuration of situations. See the IBM Tivoli Monitoring
Troubleshooting Guide for more information about troubleshooting for situations.
242
General situation problems

Table 13 lists general problems that might occur with situations.
Table 13. General situation problems and solutions
Problem
Solution
Monitoring activity requires too much

disk space.
Check the RAS trace logging settings that are described in Setting RAS
trace parameters on page 223. For example, trace logs grow rapidly
when you apply the ALL logging option.
Monitoring activity requires too many

system resources.
Disk capacity planning for historical data on page 161 describes the
performance impact of specific attribute groups. If possible, decrease your
use of the attribute groups that require greater system resources.
A formula that uses mathematical

operators appears to be incorrect. For
example, if you were monitoring a
Linux system, the formula that
calculates when Free Memory falls
under 10 percent of Total Memory does
not work: LT
#Linux_VM_Stats.Total_Memory / 10
This formula is incorrect because situation predicates support only logical

operators. Your formulas cannot have mathematical operators.
Note: The Situation Editor provides alternatives to math operators.
Regarding the example, you can select the % Memory Free attribute and
avoid the need for math operators.
You want to change the appearance of

situations when they are displayed in
the navigation tree.
1. Right-click an item in the navigation tree.

2. Select Situations in the menu. The Situation Editor window is
displayed.
3. Select the situation that you want to modify.
4. Use the State pull-down menu in the lower right of the window to set
the status and appearance of the Situation when it triggers.
Note: The State setting is not related to severity settings in IBM Tivoli
Enterprise Console.
There is no event notification for when a By default, agent status is available in the Enterprise System Status
monitoring agent is down.
workspace. However, by default, an event is not generated for status
change. The following situation definition causes a situation to fire when
any Microsoft Cluster Server agent being monitored goes offline. To
enable the Agent Down situation, complete the following steps:
v Click Edit > Situation Editor > All Managed Systems > MS_Offline.
v Right-click Create another.
v Complete the following:
Name: KQ5_MSCS_Agent_Down
Description: The agent is not running this can be either an agent or

cluster failure.
v Click OK.
v Click Add conditions...
v Click Product.
v Click OK.
v For Product, enter ==Q5
v Click OK.
v Right-click [Any managed system] > Situations.
v Click in the top left Set Situation filter criteria...
v Select Eligible for association and Associated with Monitored
Application.
v Select All Managed Systems > KQ5_MSCS_Agent_Down.
v Right-click KQ5_MSCS_Agent_Down > Associate.
v Click Apply and then click OK.
243
Table 13. General situation problems and solutions (continued)

Problem
Solution
How to create situations for Cluster

Server entries in the Windows system
log.
Use the Windows OS agent to monitor the system log for cluster services
entries. Specify the following values:
1. Attribute Group equal to nt_event_log
2. Attribute Item: Log Name (Unicode) equal to System (case sensitive)
3. Attribute Item: Source equal to source of the log entry, for example,
ClusSvc
4. Attribute Item: Event ID equal to the cluster eventID that you want,
for example, 1009
When a situation is triggered in the

Event Log attribute group, it remains in
the Situation Event Console as long as
the event ID entry is present in the
Event Log workspace. When this event
ID entry is removed from the Event Log
workspace on the Tivoli Enterprise
Portal, the situation is also cleared even
if the actual problem that caused the
event is not resolved, and the event ID
entry is also present in the Windows
Event Viewer.
A timeout occurs on the cache of events for the NT Event Log group.
Increase the cache time of Event Log collection to meet your requirements
by adding the following variable and timeout value to the KXXENV file for
the agent: CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600
If the Expert Advice for a situation

contains a hyperlink to an external
website (for example, a Microsoft
TechNet website) and you click the
hyperlink, the website opens in an
external window. However, the external
window stops responding.
The external window responds after you close the Preview window and
Situation Editor window.
This variable determines how long events from the NT Event Log are
kept.
Problems with configuration of situations

Table 14 lists problems that might occur with configuring situations.
This section provides information for troubleshooting for agents. Be sure to consult
the IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshooting
information.
Table 14. Problems with configuring situations that you solve in the Situation Editor
Problem
Solution
Note: To get started with the solutions in this section, perform these steps:
1. Launch the Tivoli Enterprise Portal.
2. Click Edit > Situation Editor.
3. In the navigation tree, choose the agent whose situation you want to modify.
4. Choose the situation in the list. The Situation Editor view is displayed.
The situation for a specific agent is Open the Situation Editor. Access the All managed servers view. If the situation
not visible in the Tivoli Enterprise is absent, confirm that the monitoring server has been seeded for the agent. If
Portal.
not, seed the server, as described in the IBM Tivoli Monitoring Installation and
Setup Guide.
The monitoring interval is too
long.
244
Access the Situation Editor view for the situation that you want to modify.
Check the Sampling interval area in the Formula tab. Adjust the time interval
as needed.
Table 14. Problems with configuring situations that you solve in the Situation Editor (continued)
Problem
Solution
The situation did not activate at

startup.
Manually recycle the situation as follows:

1. Right-click the situation and choose Stop Situation.
2. Right-click the situation and choose Start Situation.
Note: You can permanently avoid this problem by placing a check mark in the
Run at Startup option of the Situation Editor view for a specific situation.
The situation is not displayed.
Click the Action tab and check whether the situation has an automated
corrective action. This action can occur directly or through a policy. The
situation might be resolving so quickly that you do not see the event or the
update in the graphical user interface.
An Alert event has not occurred

Check the logs, reports, and workspaces.
even though the predicate has been
properly specified.
A situation fires on an unexpected
managed object.
Confirm that you have distributed and started the situation on the correct
managed system.
The product did not distribute the

situation to a managed system.
Click the Distribution tab and check the distribution settings for the situation.
The situation does not fire.
This problem can be caused when incorrect predicates are present in the
formula that defines the situation. For example, the managed object shows a
state that normally triggers a monitoring event, but the situation is not true
because the wrong attribute is specified in the formula.
In the Formula tab, analyze predicates as follows:
1. Click the fx icon in the upper-right corner of the Formula area. The Show
formula window is displayed.
a. Confirm the following details in the Formula area at the top of the
window:
v The attributes that you intend to monitor are specified in the formula.
v The situations that you intend to monitor are specified in the formula.
v The logical operators in the formula match your monitoring goal.
v The numeric values in the formula match your monitoring goal.
b. (Optional) Select the Show detailed formula check box in the lower left
of the window to see the original names of attributes in the application
or operating system that you are monitoring.
c. Click OK to dismiss the Show formula window.
2. (Optional) In the Formula area of the Formula tab, temporarily assign
numeric values that immediately trigger a monitoring event. The triggering
of the event confirms that other predicates in the formula are valid.
Note: After you complete this test, you must restore the numeric values to
valid levels so that you do not generate excessive monitoring data based on
your temporary settings.
See the IBM Tivoli Monitoring Troubleshooting Guide for additional information
about situations that do not fire.
A problem can arise when trying

to make local changes using
Manage Tivoli Enterprise
Monitoring Services that required
the agent to be stopped while the
agent cluster resource controlling
the agent is online.
Some local changes might require the agent to be taken offline. In these cases
the user receives a warning prompt that states the agent must be taken offline
to perform this operation. If the cluster resource is online the cluster server
attempts to bring the agent back online, which interferes with this operation.
Take the agent cluster resource offline while performing operations requiring
the agent to be offline. When the operations are complete, bring the agent
cluster resource back online.
245
Table 15. Problems with configuration of situations that you solve in the Workspace area
Problem
Solution
Situation events are not displayed

in the Events Console view of the
workspace.
Associate the situation with a Navigator item.

Note: The situation does not need to be displayed in the workspace. It is
sufficient that the situation is associated with any Navigator item.
You do not have access to a

situation.
Note: You must have administrator privileges to perform these steps.

1. Select Edit > Administer Users to access the Administer Users window.
2. In the Users area, select the user whose privileges you want to modify.
3. In the Permissions tab, Applications tab, and Navigator Views tab, select
the permissions or privileges that correspond to the user role.
4. Click OK.
A managed system seems to be

offline.
1. Select Physical View and highlight the Enterprise Level of the navigator
tree.
2. Select View > Workspace > Managed System Status to see a list of
managed systems and their status.
3. If a system is offline, check network connectivity and the status of the
specific system or application.
Take Action commands troubleshooting

Table 16 lists general problems that might occur with Take Action commands.
When each Take Action command runs it generates the log file listed in Table 7 on
page 221. This chapter provides agent-specific troubleshooting information.
See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting
information.
Table 16. Take Action commands problems and solutions
Problem
Solution
Take Action commands often require several

minutes to complete.
Allow several minutes. If you do not see a message advising you

of completion, try to run the command manually.
Situations fail to trigger Take Action commands.
Attempt to manually run the Take Action command in the Tivoli

Enterprise Portal. If the Take Action command works, look for
configuration problems in the situation. See Situation
troubleshooting on page 242. If the Take Action command fails,
see IBM Tivoli Monitoring Troubleshooting Guide for general
information about troubleshooting Take Action commands.
Tivoli Common Reporting troubleshooting

Table 17 on page 247 contains a list of problems that might occur with the Tivoli
Common Reporting predefined reports for Microsoft Cluster Server Agent.
For information about troubleshooting for the Tivoli Common Reporting tool, see
com.ibm.tivoli.tcr.doc/tcr_welcome.html.
246
Table 17. Tivoli Common Reporting for Microsoft Cluster Server Agent problems and solutions
Problem
Solution
If a view or a table for the selected

summarization type does not exist in the
database for a report, then the report does
not open and the following error message
is displayed:
Configure the Summarization and Pruning agent properly and generate

data in the database for all Summarization Types.
CTGTRV014E The report cannot be

successfully formatted because it
completed with errors,reference ID
[DESIGNID_141_OBJECTID_3d9a3d9a]
If data source is incorrect and you run a
report, the Tivoli Common Reporting tool
does not display the report in a correct
format and displays the following error
message:
CTGTRV014E The report cannot be
completed with errors, reference ID
[REPORTID_5_OBJECTID_5cc65cc6].
If the .jar files are not added to the Tivoli
Common Reporting tool, then the
following error message is displayed:
CTGTRV014E The report can not be
completed with errors, reference ID
[REPORTID_1049_OBJECTID_dbe0dbe].
Ensure that the parameters:

v Are correctly set while configuring the data source in the Edit Data
Source window of the Tivoli Common Reporting tool.
v Match the parameters of the Summarization and Pruning agent (for
example, Database URL, Driver, User, and Password) that is
connected to a particular database.
Add the .jar files to the appropriate directory of the Tivoli Common
Reporting. These .jar files are put in the JDBC driver while configuring
the Summarization and Pruning agent. The following list gives the
names of the .jar files for different databases:
v The ojdbc14.jar file for the Oracle database
v The sqljdbc.jar and the sqljdbc4.jar files for the SQL Server
database
v The db2jcc_license_cu.jar and the db2jcc.jar files for the DB2
database
Add these .jar files to one of the following locations of the Tivoli
Common Reporting:
Location for the Tivoli Common Reporting V1.1.1.0
C:\Program Files\IBM\tcr\lib\birt-runtime-2_2_1\
ReportEngine\plugins\
org.eclipse.birt.report.data.oda.jdbc_2.2.1.r22x_
v20070919\drivers
Location for the Tivoli Common Reporting V1.2.0.0 and V1.2.0.1
C:\IBM\tivoli\tip\products\tcr\lib\birt-runtime-2_2_1\
ReportEngine\plugins\
org.eclipse.birt.report.data.oda.jdbc_2.2.1.r22x_
v20070919\drivers
Data does not exist in the database for the

selected parameters.
Configure the Summarization and Pruning agent properly and generate

data in the database for all Summarization Types.
A report for multiple servers does not

show correct values in an excel chart.
There is no solution to this problem at this time.
If you open the report in Adobe

PostScript, X and Y axis are not
displayed.
Increase the zoom percentage in Adobe PostScript to display X and Y

axis.
If you open a report in the Adobe

PostScript format, the page numbers do
not display properly.
None.
If you open a report in the Adobe

PostScript format, some part of charts or
data in the report is truncated.
The default size of the report is A4. For the full view of the report, click
11x17 from the Media menu.
247
Table 17. Tivoli Common Reporting for Microsoft Cluster Server Agent problems and solutions (continued)
Problem
Solution
If you open a report in Microsoft Excel

format, then the key values are displayed
as column headings.
None.
You cannot drill down from the charts in

the main report to the subreport in PDF.
If you save a report as PDF, the report gets None.

saved as view.pdf instead of
reportname.pdf.
If you open a report in PDF, the Web
address of the Tivoli Common Reporting
Server is displayed as the title instead of
the report name.
None.
If you try to drill down to a subreport or

sort a column in a report in Microsoft
Excel format, the following error is
displayed:
CTGTRV004E A drill-through report

cannot be formatted because the
drillthrough information cannot be
found.The most likely cause is an
expired HTTP session.
The snapshot report fails to open in PDF.
When you open the snapshot report in the
Microsoft Excel or Adobe PostScript
format, the following error message is
displayed:
None.
Internet Explorer cannot download view

from localhost Internet Explorer was
not able to open this Internet site.
The requested site is either
unavailable or cannot be found.Please
try again later.
Tivoli Common Reporting logs

The Tivoli Common Reporting application uses logger scripts to log errors during
report generation. You can use the SystemOut.log file to monitor the health of the
running application server and the SystemErr.log file to perform problem analysis.
These files are available at the following locations:
On Windows platform
For TCR V1.1.1.0
tcr_install_dir\eWas61\profiles\tcrProfile\logs\tcrServer\
For TCR V1.2.0.0 and V1.2.0.1
tcr_install_dir\tivoli\tip\profiles\TIPProfile\logs\
server1\
On non-Windows platform
For TCR V1.1.1.0
tcr_install_dir/eWas61/profiles/tcrProfile/logs/ tcrServer/
For TCR V1.2.0.0 and V1.2.0.1
tcr_install_dir/tivoli/tip/profiles/TIPProfile/logs/ server1/
248
See the following Web page for more information about logging:
http://www.ibm.com/developerworks/tivoli/library/t-tcr/
ibm_tiv_tcr_report_logging.pdf
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
Online
The following sites contain troubleshooting information:
v Go to the IBM Software Support site at http://www.ibm.com/software/
support/probsub.html and follow the instructions.
v Go to the IBM Tivoli Distributed Monitoring and Application
Management Wiki at http://www.ibm.com/developerworks/wikis/
display/tivolimonitoring/Home. Feel free to contribute to this wiki.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability
workbench that helps you resolve questions and problems with IBM
software products. The ISA provides quick access to support-related
information and serviceability tools for problem determination. To install
the ISA software, go to http://www.ibm.com/software/support/isa.
Informational, warning, and error messages

This chapter introduces message logging and explains how to gather information
from those logs.
Message logging refers to the text and numeric messages created by the software.
These messages relay information about how the system or application is
performing and can alert you to exceptional conditions when they occur. Messages
are sent to an output destination, such as a file, database, or console screen.
If you receive a warning or error message, you can do one of the following:
v Follow the instructions listed in the Detail window of the message if this
information is included there.
v Consult the message details listed in this chapter to see what action you can take
to correct the problem.
v Consult the message log for message ID, text, time, and date of the message, as
well as other data you can use to diagnose the problem.
Message format
Microsoft Cluster Server Agent messages have the following format:
Message ID and text
Explanation
Operator Response
The message ID has the following format:
CCC####severity
where:
249
KQ50001I KQ50003E
CCC
Prefix that indicates the component to which the message applies. The
component is one of the following:
KQ5
####
General Microsoft Cluster Server Agent messages
Number of the message
severity
Severity of the message. There are three levels of severity:
I
Informational messages provide feedback about something that

happened in the product or system that might be important. These
messages can provide guidance when you are requesting a specific
action from the product.
Warning messages call your attention to an exception condition.

The condition might not be an error but can cause problems if not
resolved.
Error messages indicate that an action cannot be completed

because of a user or system error. These messages require user
response.
The Text of the message provides a general statement regarding the problem or
condition that occurred. The Explanation provides additional information about the
message and what might have caused the condition. The Operator Response
provides actions to take in response to the condition, particularly for error
messages (messages with the "E" suffix).
Note: Many message texts and explanations contain variables, such as the specific
name of a server or application. Those variables are represented in this
chapter as symbols, such as "&1." Actual messages contain values for these
variables.
This chapter includes the messages for the following software:
v Microsoft Cluster Server Agent
Microsoft Cluster Server Agent messages

KQ50001I
The Resource is brought online.
Explanation: The Resource is brought online.

Operator response: None.
KQ50002I
The Resource is already running.
Explanation: The Resource is already running.

KQ50003E
Error bringing the resource online.
Explanation: Error bringing the resource online.

250
KQ50004I KQ500012I
KQ50004I
Time-out occured briging resource online.
Explanation: Time-out occured briging resource online.

KQ50005I
The Resource is taken offline.
Explanation: The Resource is taken offline.

KQ50006I
The Resource is already offline.
Explanation: The Resource is already offline.

KQ50004E
Error taking the resource offline.
Explanation: Error taking the resource offline.

KQ50007I
Time-out occured taking resource offline.
Explanation: Time-out occured taking resource offline.

KQ50008I
The Resource Group is brought online.
Explanation: The Resource Group is brought online.

KQ50009I
The Resource Group is already running.
Explanation: The Resource Group is already running.

KQ500010E
Error bringing the Resource Group online.
Explanation: Error bringing the resource group online.

KQ500011I
Time-out occured briging Resource Group online.

KQ500012I
The Resource Group is taken offline.
Explanation: The Resource Group is taken online.

251
KQ500013I KQ50100W
KQ500013I
The Resource Group is already offline.
Explanation: The Resource Group is already running.

KQ500014E
Error bringing the resource group offline.
Explanation: Error bringing the resource group offline.

KQ500015I
Time-out occured briging resource group offline.

KQ50100W
The service does not exist as an installed service.
Explanation: The service does not exist as an installed service.

252
Appendix A. IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli Enterprise
Console. For a description of the event slots for each event class, see the lists in
this appendix. For more information about mapping attribute groups to event
classes, see the IBM Tivoli Monitoring Administrator's Guide.
Generic event mapping provides useful event class and attribute information for
situations that do not have specific event mapping defined. BAROC files are found
on the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB
(that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/
TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console event
synchronization provides a collection of ready-to-use rule sets that you can deploy
with minimal configuration. Be sure to install IBM Tivoli Enterprise Console event
synchronization to access the correct Sentry.baroc, which is automatically included
during base configuration of IBM Tivoli Enterprise Console rules if you indicate
that you want to use an existing rule base. See the IBM Tivoli Monitoring Installation
and Setup Guide for details.
Each of the event classes is a child of KQ5_Base and is defined in the kq5.baroc
(version 6.2.2) file. The KQ5_Base event class can be used for generic rules
processing for any event from the IBM Tivoli Composite Application Manager for
MS Apps: Microsoft Cluster Server Agent.
For events generated by situations in the Availability attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_AVAILABILITY class. This
class contains the following slots:
v node: STRING
v timestamp: STRING
v application_component: STRING
v name: STRING
v name_enum: STRING
v kq5_status: INTEGER
v kq5_status_enum: STRING
v full_name: STRING
v full_name_enum: STRING
v type: INTEGER
v type_enum: STRING
v virtual_size: INTEGER
v
v
v
v
v
v
page_faults_per_sec: INTEGER
working_set_size: INTEGER
thread_count: INTEGER
pid: INTEGER
percent_privileged_time: INTEGER
percent_user_mode_time: INTEGER
v percent_processor_time: INTEGER
v command_line: STRING
v command_line_enum: STRING
253
v
v
v
v
functionality_test_status: INTEGER
functionality_test_status_enum: STRING
functionality_test_message: STRING
functionality_test_message_enum: STRING
For events generated by situations in the Cluster Domain attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_CLUSTER_DOMAIN class.
This class contains the following slots:
v node: STRING
v timestamp: STRING
v domain: STRING
For events generated by situations in the Cluster Shared Volume attribute group,
Tivoli Enterprise Console events are sent using the
ITM_KQ5_CLUSTER_SHARED_VOLUME class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v name: STRING
v volumename: STRING
v volumeoffset: INTEGER
v volumeoffset_enum: STRING
v
v
v
v
csvresourcename: STRING
csvresourcestate: INTEGER
csvresourcestate_enum: STRING
csvnodename: STRING
v backupstate: INTEGER
v backupstate_enum: STRING
v description: STRING
v faultstate: INTEGER
v faultstate_enum: STRING
For events generated by situations in the Cluster Shared Volume IO attribute
group, Tivoli Enterprise Console events are sent using the
ITM_KQ5_CLUSTER_SHARED_VOLUME_IO class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v io_read_bytes: INTEGER
v
v
v
v
v
v
v
io_read_bytes_enum: STRING
io_reads: INTEGER
io_reads_enum: STRING
io_write_bytes: INTEGER
io_write_bytes_enum: STRING
io_writes: INTEGER
io_writes_enum: STRING
v metadata_io: INTEGER
v metadata_io_enum: STRING
254
v
v
v
v
v
redirected_read_bytes: INTEGER
redirected_read_bytes_enum: STRING
redirected_reads: INTEGER
redirected_reads_enum: STRING
redirected_write_bytes: INTEGER
v
v
v
v
redirected_write_bytes_enum: STRING
redirected_writes: INTEGER
redirected_writes_enum: STRING
name: STRING
For events generated by situations in the Cluster Summary attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_CLUSTER_SUMMARY
class. This class contains the following slots:
v node: STRING
v timestamp: STRING
v cluster_name: STRING
v node_name: STRING
v system_information: STRING
v system_processor_utilization: INTEGER
v system_processor_utilization_enum: STRING
v system_processor_idle: INTEGER
v system_processor_idle_enum: STRING
v total_memory_utilization: INTEGER
v total_memory_utilization_enum: STRING
v total_memory_available: INTEGER
v total_memory_available_enum: STRING
v quorum_path: STRING
v quorum_total_size: INTEGER
v
v
v
v
v
quorum_total_size_enum: STRING
quorum_utilization: INTEGER
quorum_utilization_enum: STRING
quorum_available: INTEGER
quorum_available_enum: STRING
v percentage_quorum_used: INTEGER
v percentage_quorum_used_enum: STRING
v
v
v
v
v
v
v
percentage_quorum_free: INTEGER
percentage_quorum_free_enum: STRING
shared_storage_available: INTEGER
shared_storage_available_enum: STRING
shared_storage_total_size: INTEGER
shared_storage_total_size_enum: STRING
shared_storage_utilization: INTEGER
v
v
v
v
shared_storage_utilization_enum: STRING
percentage_shared_storage_used: INTEGER
percentage_shared_storage_used_enum: STRING
percentage_shared_storage_free: INTEGER
255
v
v
v
v
v
percentage_shared_storage_free_enum: STRING
total_shared_storage: INTEGER
total_shared_storage_enum: STRING
network_utilization: INTEGER
network_utilization_enum: STRING
v domain: STRING
For events generated by situations in the Configuration attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_CONFIGURATION class.
v
v
v
v
v
v
v
v
node: STRING
timestamp: STRING
name: STRING
max_number_nodes: INTEGER
max_number_nodes_enum: STRING
default_network_role: INTEGER
default_network_role_enum: STRING
description: STRING
For events generated by situations in the CPU Interrupts Rollup attribute group,
ITM_KQ5_CPU_INTERRUPTS_ROLLUP class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v maximum_enum: STRING
v minimum: INTEGER
v minimum_enum: STRING
v
v
v
v
v
average: INTEGER
average_enum: STRING
total: INTEGER
total_enum: STRING
standard_deviation: INTEGER
v standard_deviation_enum: STRING
For events generated by situations in the CPU per Node attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_CPU_PER_NODE class.
v node: STRING
v timestamp: STRING
v name: STRING
v processor: STRING
v interrupts: INTEGER
v interrupts_enum: STRING
v percent_interrupt_time: INTEGER
v percent_interrupt_time_enum: STRING
256
v
v
v
v
v
percent_idle_time: INTEGER
percent_idle_time_enum: STRING
percent_processor_time: INTEGER
percent_processor_time_enum: STRING
percent_user_time: INTEGER
v percent_user_time_enum: STRING
v percent_privileged_time: INTEGER
v percent_privileged_time_enum: STRING
For events generated by situations in the CPU per Node Rollup attribute group,
ITM_KQ5_CPU_PER_NODE_ROLLUP class. This class contains the following slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v minimum: INTEGER
v average: INTEGER
v average_enum: STRING
v total: INTEGER
v total_enum: STRING
v standard_deviation: INTEGER
For events generated by situations in the Degradation Risk attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_DEGRADATION_RISK
v node: STRING
v timestamp: STRING
v node_min_capacity: STRING
v
v
v
v
v
v
min_capacity: INTEGER
min_capacity_enum: STRING
node_max_capacity: STRING
max_capacity: INTEGER
max_capacity_enum: STRING
node_min_util: STRING
v
v
v
v
v
v
v
min_util: INTEGER
min_util_enum: STRING
node_max_util: STRING
max_util: INTEGER
max_util_enum: STRING
total_capacity: INTEGER
total_capacity_enum: STRING
v current_capacity: INTEGER
v current_capacity_enum: STRING
257
v
v
v
v
v
degraded_capacity: INTEGER
degraded_capacity_enum: STRING
total_util: INTEGER
total_util_enum: STRING
uniform_commitment: INTEGER
v uniform_commitment_enum: STRING
v unitary_commitment: INTEGER
v unitary_commitment_enum: STRING
For events generated by situations in the Disk attribute group, Tivoli Enterprise
Console events are sent using the ITM_KQ5_DISK class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v name_of_node: STRING
v disk: STRING
v percent_free_space: INTEGER
v percent_free_space_enum: STRING
v percent_disk_write_time: INTEGER
v percent_disk_write_time_enum: STRING
v percent_disk_read_time: INTEGER
v
v
v
v
percent_disk_read_time_enum: STRING
freemegabytes: INTEGER
freemegabytes_enum: STRING
disk_write_bytes: INTEGER
v disk_write_bytes_enum: STRING
v disk_writes: INTEGER
v disk_writes_enum: STRING
v
v
v
v
v
disk_read_bytes: INTEGER
disk_read_bytes_enum: STRING
disk_reads: INTEGER
disk_reads_enum: STRING
current_disk_queue: INTEGER
v current_disk_queue_enum: STRING
v disk_transfers: INTEGER
v
v
v
v
disk_transfers_enum: STRING
disk_used_percent: INTEGER
disk_write_mb: INTEGER
disk_read_mb: INTEGER
For events generated by situations in the Disk MB Rollup attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_DISK_MB_ROLLUP class.
v node: STRING
v timestamp: STRING
v maximum: INTEGER
258
v
v
v
v
v
maximum_enum: STRING
minimum: INTEGER
minimum_enum: STRING
average: INTEGER
v
v
v
v
total: INTEGER
total_enum: STRING
standard_deviation_enum: STRING
For events generated by situations in the Disk PCT Rollup attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_DISK_PCT_ROLLUP class.
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v minimum: INTEGER
v average: INTEGER
v total: INTEGER
For events generated by situations in the Enterprise Cluster Summary attribute
ITM_KQ5_ENTERPRISE_CLUSTER_SUMMARY class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v
v
v
v
v
v
cluster_name: STRING
node_name: STRING
system_information: STRING
system_processor_utilization: INTEGER
system_processor_idle: INTEGER
total_memory_utilization: INTEGER
v
v
v
v
v
v
v
total_memory_available: INTEGER
quorum_path: STRING
quorum_total_size: INTEGER
quorum_utilization: INTEGER
quorum_available: INTEGER
percentage_quorum_used: INTEGER
percentage_quorum_free: INTEGER
v shared_storage_available: INTEGER
v shared_storage_total_size: INTEGER
259
v
v
v
v
v
percentage_shared_storage_used: INTEGER
percentage_shared_storage_free: INTEGER
total_shared_storage: INTEGER
network_utilization: INTEGER
v domain: STRING
For events generated by situations in the Event Log attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_EVENT_LOG class. This
v
v
v
v
v
v
v
v
node: STRING
log_name: STRING
event_source: STRING
event_type: INTEGER
event_type_enum: STRING
event_id: INTEGER
event_category: STRING
event_category_enum: STRING
v message: STRING
v time_generated: STRING
v event_level: STRING
v
v
v
v
event_level_enum: STRING
event_keywords: STRING
event_keywords_enum: STRING
event_api_version: INTEGER
v event_api_version_enum: STRING
For events generated by situations in the Global Update Messages attribute group,
ITM_KQ5_GLOBAL_UPDATE_MESSAGES class. This class contains the following
slots:
v node: STRING
v
v
v
v
v
v
timestamp: STRING
database_update_messages: INTEGER
database_update_messages_enum: STRING
database_update_messages_delta: INTEGER
database_update_messages_delta_enum: STRING
update_messages: INTEGER
v
v
v
v
update_messages_enum: STRING
update_messages_delta: INTEGER
update_messages_delta_enum: STRING
name: STRING
For events generated by situations in the Memory attribute group, Tivoli Enterprise
Console events are sent using the ITM_KQ5_MEMORY class. This class contains
the following slots:
v node: STRING
260
v
v
v
v
v
timestamp: STRING
name_of_node: STRING
memory_module: STRING
available_memory_mb: INTEGER
available_memory_mb_enum: STRING
v
v
v
v
v
v
v
percent_committed_bytes_in_use: INTEGER
percent_committed_bytes_in_use_enum: STRING
cache_bytes: INTEGER
cache_bytes_enum: STRING
cache_bytes_peak: INTEGER
cache_bytes_peak_enum: STRING
cache_faults: INTEGER
v
v
v
v
v
v
cache_faults_enum: STRING
page_faults: INTEGER
page_faults_enum : STRING
page_reads: INTEGER
page_reads_enum: STRING
page_writes: INTEGER
v page_writes_enum: STRING
v pages_input: INTEGER
v pages_input_enum: STRING
v
v
v
v
pages_output: INTEGER
pages_output_enum: STRING
pool_paged_bytes: INTEGER
commit_limit_mb: INTEGER
v committed_mb: INTEGER
v cache_mb: INTEGER
v cache_peak_mb: INTEGER
v pool_paged_mb: INTEGER
v pool_paged_bytes_enum: STRING
For events generated by situations in the Memory MB Rollup attribute group,
ITM_KQ5_MEMORY_MB_ROLLUP class. This class contains the following slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v
v
v
v
v
v
v
minimum: INTEGER
average: INTEGER
total: INTEGER
total_enum: STRING
261
For events generated by situations in the Memory PCT Rollup attribute group,
ITM_KQ5_MEMORY_PCT_ROLLUP class. This class contains the following slots:
v
v
v
v
v
v
v
v
node: STRING
timestamp: STRING
maximum: INTEGER
minimum: INTEGER
average: INTEGER
v total: INTEGER
For events generated by situations in the MRR Messages attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_MRR_MESSAGES class.
v node: STRING
v timestamp: STRING
v messages_outstanding: INTEGER
v messages_outstanding_enum: STRING
v messages_sent: INTEGER
v
v
v
v
messages_sent_enum: STRING
messages_sent_delta: INTEGER
messages_sent_delta_enum: STRING
name: STRING
For events generated by situations in the Network Interfaces attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_NETWORK_INTERFACES
v node: STRING
v timestamp: STRING
v name: STRING
v state_raw: INTEGER
v state_raw_enum: STRING
v
v
v
v
v
v
v
address: STRING
system_name: STRING
adapter: STRING
network_name: STRING
device_id: STRING
description: STRING
state: INTEGER
v state_enum: STRING
262
For events generated by situations in the Network Interfaces State Rollup attribute
ITM_KQ5_NETWORK_INTERFACES_STATE_ROLLUP class. This class contains
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v
v
v
v
v
minimum: INTEGER
average: INTEGER
v total: INTEGER
For events generated by situations in the Network Performance attribute group,
ITM_KQ5_NETWORK_PERFORMANCE class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v name_of_node: STRING
v
v
v
v
v
v
v
v
v
network_interface: STRING
bytes_received: INTEGER
bytes_received_enum: STRING
bytes_sent: INTEGER
bytes_sent_enum: STRING
current_bandwidth: INTEGER
current_bandwidth_enum: STRING
output_queue_length: INTEGER
output_queue_length_enum: STRING
v packets_outbound_discarded: INTEGER
v packets_outbound_discarded_enum: STRING
v
v
v
v
v
v
packets_outbound_errors: INTEGER
packets_outbound_errors_enum: STRING
packets: INTEGER
packets_enum: STRING
packets_received_discarded: INTEGER
packets_received_discarded_enum: STRING
v
v
v
v
v
packets_received_errors: INTEGER
packets_received_errors_enum: STRING
packets_received: INTEGER
packets_received_enum: STRING
packets_sent: INTEGER
263
v
v
v
v
v
packets_sent_enum: STRING
bytes_total: INTEGER
bytes_total_enum: STRING
received_mb: INTEGER
sent_mb: INTEGER
v
v
v
v
current_bandwidth_mb: INTEGER
total_mb: INTEGER
current_bandwidth_gbps: REAL
current_bandwidth_gbps_enum: STRING
For events generated by situations in the Network Performance Packets Rollup

attribute group, Tivoli Enterprise Console events are sent using the
ITM_KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP class. This class
contains the following slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v minimum: INTEGER
v average: INTEGER
v
v
v
v
total: INTEGER
total_enum: STRING
For events generated by situations in the Network Performance Received Rollup

ITM_KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP class. This class
contains the following slots:
v node: STRING
v timestamp: STRING
v
v
v
v
v
v
maximum: INTEGER
minimum: INTEGER
average: INTEGER
v
v
v
v
total: INTEGER
total_enum: STRING
For events generated by situations in the Network Performance Sent Rollup

ITM_KQ5_NETWORK_PERFORMANCE_SENT_ROLLUP class. This class contains
264
v
v
v
v
v
node: STRING
timestamp: STRING
maximum: INTEGER
minimum: INTEGER
v
v
v
v
v
v
v
average: INTEGER
total: INTEGER
total_enum: STRING
For events generated by situations in the Network Reconnections attribute group,

ITM_KQ5_NETWORK_RECONNECTIONS class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v normal_message_queue_length: INTEGER
v normal_message_queue_length_enum: STRING
v reconnect_count: INTEGER
v reconnect_count_enum: STRING
v unacknowledged_message_queue_length: INTEGER
v unacknowledged_message_queue_length_enum: STRING
v urgent_message_queue_length: INTEGER
v urgent_message_queue_length_enum: STRING
v name: STRING
For events generated by situations in the Networks attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_NETWORKS class. This
v
v
v
v
v
v
node: STRING
timestamp: STRING
name: STRING
state_raw: INTEGER
state_raw_enum: STRING
address: STRING
v
v
v
v
v
v
addressmask: STRING
role: INTEGER
role_enum: STRING
description: STRING
state: INTEGER
state_enum: STRING
265
For events generated by situations in the Networks Messages attribute group,

ITM_KQ5_NETWORKS_MESSAGES class. This class contains the following slots:
v
v
v
v
v
v
v
v
node: STRING
timestamp: STRING
name: STRING
bytes_received: INTEGER
bytes_received_enum: STRING
bytes_received_delta: INTEGER
bytes_received_delta_enum: STRING
bytes_sent: INTEGER
v bytes_sent_enum: STRING
v bytes_sent_delta: INTEGER
v
v
v
v
v
bytes_sent_delta_enum: STRING
messages_received: INTEGER
messages_received_enum: STRING
messages_received_delta: INTEGER
messages_received_delta_enum: STRING
v messages_sent: INTEGER
v messages_sent_enum: STRING
v messages_sent_delta: INTEGER
v messages_sent_delta_enum: STRING
For events generated by situations in the Networks Rollup attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_NETWORKS_ROLLUP
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v
v
v
v
v
minimum: INTEGER
average: INTEGER
total: INTEGER
For events generated by situations in the Node To Active Group attribute group,
ITM_KQ5_NODE_TO_ACTIVE_GROUP class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v current_rg_node: STRING
v rg_node_changed: INTEGER
266
v
v
v
v
v
rg_node_changed_enum: STRING
previous_rg_node: INTEGER
state_of_node: INTEGER
state_of_node_enum: STRING
description_of_node: STRING
v
v
v
v
v
name_of_group: STRING
state_of_group: INTEGER
state_of_group_enum: STRING
description_of_group: STRING
node_group_names: STRING
For events generated by situations in the Nodes attribute group, Tivoli Enterprise
Console events are sent using the ITM_KQ5_NODES class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v name: STRING
v state_raw_enum: STRING
v major_version: STRING
v minor_version: STRING
v build_number: STRING
v node_highest_version: STRING
v nodelowestversion: STRING
v state: INTEGER
For events generated by situations in the Nodes State Rollup attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_NODES_STATE_ROLLUP
v
v
v
v
v
v
node: STRING
timestamp: STRING
maximum: INTEGER
minimum: INTEGER
v
v
v
v
v
v
average: INTEGER
total: INTEGER
total_enum: STRING
267
For events generated by situations in the Performance Object Status attribute

ITM_KQ5_PERFORMANCE_OBJECT_STATUS class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v query_name: STRING
v
v
v
v
v
object_name: STRING
object_type: INTEGER
object_type_enum: STRING
object_status: INTEGER
object_status_enum: STRING
v error_code: INTEGER
v error_code_enum: STRING
v
v
v
v
v
last_collection_start: STRING
last_collection_start_enum: STRING
last_collection_finished: STRING
last_collection_finished_enum: STRING
last_collection_duration: REAL
v average_collection_duration: REAL
v average_collection_duration_enum: STRING
v refresh_interval: INTEGER
v
v
v
v
number_of_collections: INTEGER
cache_hits: INTEGER
cache_misses: INTEGER
cache_hit_percent: REAL
v intervals_skipped: INTEGER
For events generated by situations in the Quorum Configuration attribute group,
ITM_KQ5_QUORUM_CONFIGURATION class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
268
v
v
v
v
v
maintenance_file: STRING
quorum_log_file_size: INTEGER
quorum_log_file_size_enum: STRING
quorum_arbitration_time_max: INTEGER
quorum_arbitration_time_max_enum: STRING
v
v
v
v
quorum_arbitration_time_min: INTEGER
quorum_arbitration_time_min_enum: STRING
quorum_type: STRING
quorum_path: STRING
For events generated by situations in the Resource Control Manager attribute

ITM_KQ5_RESOURCE_CONTROL_MANAGER class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v groups_online: INTEGER
v
v
v
v
v
groups_online_enum: STRING
rhs_processes: INTEGER
rhs_processes_enum: STRING
rhs_restarts: INTEGER
rhs_restarts_enum: STRING
v name: STRING
For events generated by situations in the Resource Group Moves attribute group,
ITM_KQ5_RESOURCE_GROUP_MOVES class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v minimum: INTEGER
v
v
v
v
v
v
average: INTEGER
total: INTEGER
total_enum: STRING
For events generated by situations in the Resource Group To Preferred Node

ITM_KQ5_RESOURCE_GROUP_TO_PREFERRED_NODE class. This class contains
v node: STRING
v timestamp: STRING
v group_name: STRING
v
v
v
v
v
v
v
group_state: INTEGER
group_state_enum: STRING
group_description: STRING
269
For events generated by situations in the Resource Group To Resource attribute

ITM_KQ5_RESOURCE_GROUP_TO_RESOURCE class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v group_name: STRING
v
v
v
v
v
group_state: INTEGER
group_state_enum: STRING
group_description: STRING
resource_name: STRING
resource_state: INTEGER
v resource_state_enum: STRING
v resource_description: STRING
For events generated by situations in the Resource Groups attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_RESOURCE_GROUPS
v node: STRING
v timestamp: STRING
v name: STRING
v
v
v
v
persistent_state: INTEGER
persistent_state_enum: STRING
auto_failback_type: INTEGER
v
v
v
v
auto_failback_type_enum: STRING
failover_period: INTEGER
failover_period_enum: STRING
failover_threshold: INTEGER
v failover_threshold_enum: STRING
v failback_window_start: INTEGER
v failback_window_start_enum: STRING
v failback_window_end: INTEGER
v failback_window_end_enum: STRING
v state: INTEGER
For events generated by situations in the Resource Groups State Rollup attribute
ITM_KQ5_RESOURCE_GROUPS_STATE_ROLLUP class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
270
v
v
v
v
v
minimum: INTEGER
average: INTEGER
total: INTEGER
For events generated by situations in the Resource To Dependent Resource
ITM_KQ5_RESOURCE_TO_DEPENDENT_RESOURCE class. This class contains
v
v
v
v
v
v
node: STRING
timestamp: STRING
resource_name: STRING
resource_state: INTEGER
resource_state_enum: STRING
resource_description: STRING
v dependent_resource_name: STRING
v dependent_resource_state: INTEGER
v dependent_resource_state_enum: STRING
v dependent_resource_description: STRING
For events generated by situations in the Resource To Possible Owner attribute
ITM_KQ5_RESOURCE_TO_POSSIBLE_OWNER class. This class contains the
following slots:
v node: STRING
v timestamp: STRING
v resource_name: STRING
v resource_state: INTEGER
v resource_state_enum: STRING
v
v
v
v
v
resource_description: STRING
For events generated by situations in the Resources attribute group, Tivoli

Enterprise Console events are sent using the ITM_KQ5_RESOURCES class. This
v
v
v
v
v
v
node: STRING
timestamp: STRING
name: STRING
state_raw: INTEGER
type: STRING
271
v
v
v
v
v
core_resource: INTEGER
core_resource_enum: STRING
persistent_state: INTEGER
persistent_state_enum: STRING
delete_requires_all_nodes: INTEGER
v
v
v
v
v
v
v
delete_requires_all_nodes_enum: STRING
is_alive_poll_interval: INTEGER
is_alive_poll_interval_enum: STRING
looks_alive_poll_interval: INTEGER
looks_alive_poll_interval_enum: STRING
pending_timeout: INTEGER
pending_timeout_enum: STRING
v
v
v
v
v
v
restart_action: INTEGER
restart_action_enum: STRING
restart_period: INTEGER
restart_period_enum: STRING
restart_threshold: INTEGER
restart_threshold_enum: STRING
v retry_period_on_failure: INTEGER
v retry_period_on_failure_enum: STRING
v state: INTEGER
For events generated by situations in the Resources State Rollup attribute group,
ITM_KQ5_RESOURCES_STATE_ROLLUP class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v maximum: INTEGER
v
v
v
v
v
v
average: INTEGER
total: INTEGER
For events generated by situations in the Resources Summary attribute group,

ITM_KQ5_RESOURCES_SUMMARY class. This class contains the following slots:
v node: STRING
v timestamp: STRING
v resource_controls: INTEGER
v resource_controls_enum: STRING
v resource_failure: INTEGER
272
v
v
v
v
v
resource_failure_enum: STRING
resource_failure_access_violation: INTEGER
resource_failure_access_violation_enum: STRING
resource_failure_deadlock: INTEGER
resource_failure_deadlock_enum: STRING
v
v
v
v
v
resources_online: INTEGER
resources_online_enum: STRING
resource_type_controls: INTEGER
resource_type_controls_enum: STRING
name: STRING
For events generated by situations in the Shared Storage Summary attribute group,
ITM_KQ5_SHARED_STORAGE_SUMMARY class. This class contains the following
slots:
v node: STRING
v timestamp: STRING
v cluster_name: STRING
v node_name: STRING
v shared_storage_path: STRING
v shared_storage_total_size: INTEGER
v shared_storage_total_size_enum: STRING
v
v
v
v
shared_storage_available: INTEGER
shared_storage_available_enum: STRING
shared_storage_utilization_enum: STRING
v shared_storage_state: INTEGER
v shared_storage_state_enum: STRING
For events generated by situations in the Structural Risk attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_STRUCTURAL_RISK class.
v
v
v
v
v
v
node: STRING
timestamp: STRING
lowest_health_resource: STRING
current_health: INTEGER
current_health_enum: STRING
health_less_a_node: INTEGER
v
v
v
v
v
v
v
health_less_a_node_enum: STRING
fewest_nodes_resource: STRING
available_nodes: INTEGER
available_nodes_enum: STRING
less_a_node: INTEGER
less_a_node_enum: STRING
less_a_node_percent: INTEGER
v less_a_node_percent_enum: STRING
273
For events generated by situations in the Thread Pool Status attribute group, Tivoli
Enterprise Console events are sent using the ITM_KQ5_THREAD_POOL_STATUS
v
v
v
v
v
v
v
v
node: STRING
timestamp: STRING
thread_pool_size: INTEGER
thread_pool_size_enum: STRING
thread_pool_max_size: INTEGER
thread_pool_max_size_enum: STRING
thread_pool_active_threads: INTEGER
thread_pool_active_threads_enum: STRING
v thread_pool_avg_active_threads: REAL
v thread_pool_avg_active_threads_enum: STRING
v
v
v
v
v
thread_pool_min_active_threads: INTEGER
thread_pool_min_active_threads_enum: STRING
thread_pool_max_active_threads: INTEGER
thread_pool_max_active_threads_enum: STRING
thread_pool_queue_length: INTEGER
v thread_pool_queue_length_enum: STRING
v thread_pool_avg_queue_length: REAL
v thread_pool_avg_queue_length_enum: STRING
274
v
v
v
v
thread_pool_min_queue_length: INTEGER
thread_pool_min_queue_length_enum: STRING
thread_pool_max_queue_length: INTEGER
thread_pool_max_queue_length_enum: STRING
v
v
v
v
thread_pool_avg_job_wait: REAL
thread_pool_avg_job_wait_enum: STRING
thread_pool_total_jobs: INTEGER
thread_pool_total_jobs_enum: STRING
Appendix B. Discovery Library Adapter for the monitoring

agent
This chapter contains information about the Discovery Library Adapter (DLA) for
the Microsoft Cluster Server Agent.
About the DLA

The Tivoli Management Services DLA discovers resources and relationships and
creates a Discovery Library Book file. The Book follows the Discovery Library
IdML schema and is used to populate the Configuration Management Database
(CMDB) and Tivoli Business System Management products. The Tivoli
Management Services DLA discovers Microsoft Cluster Server resources. For all
Microsoft Cluster Server systems that are active and online at the Tivoli Enterprise
Portal Server, information is included in the discovery book for those resources.
The Tivoli Management Services DLA discovers active resources. It is run
on-demand and can be run periodically to discover resources that were not active
during previous discoveries.
The DLA discovers the following cluster resources:
v MsCluster details
v MsClusterNode details
v MsClusterResourceGroup details
v MsClusterResource details
v MsClusterService details
More information about DLAs

The following sources contain additional information about using the DLA
program with all monitoring agents:
v The IBM Tivoli Monitoring Administrator's Guide contains information about using
the Tivoli Management Services Discovery Library Adapter.
v For information about using a DLA with Tivoli Application Dependency
Discovery Manager (TADDM), see the information center at
com.ibm.taddm.doc_7.2/welcome_page/welcome.html
Book Information
The file name of IdML book files generated by the DLA need to follow the IBM
Discovery Library standard The O/P DLA file name follows the format defined in
the IBM Discovery Library SDD1. The unique identity of the Author (DLA) is the
literal string, TMSDISC100., followed by the fully qualified host name (fqhn)
where the DLA runs. Any book that contains the cdm:refresh operation includes
the word "refresh" in the file name after the timestamp of the book.
Example file name (book) in the Discovery Library from a host that contains a
refresh operation:
TMSDISC100-A.ps3498win2k3.2008-09-15T10.18.45Z.refresh.xml
275
Microsoft Cluster Server DLA data model class types represented in

CDM
This section contains information about how the various source application data
objects map to classes in the Common Data Model (CDM) for the Microsoft Cluster
Server Agent.
The following information is provided for each class:
CDM class name
The class name for which the agent provides information
Superior CDM class
CDM class (model object)
Relationships
CDM relationships (hierarchical) between currently identified model
objects
CDM attributes, agent attributes, descriptions, and examples
CDM and agent attributes that are required to create an instance of a
resource, descriptions of the attributes, and examples of the attributes
Relationships
v uses
Source: app.MsFailoverCluster.MsCluster
Target: net.IpNetwork
Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster uses
169.254.187.155-IpAddress
v monitors
Source: appTMSAgent
Target: app.MsFailoverCluster.MsCluster
Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5itmagents.com-WIN2003SP2-MsCluster
v monitors
Source: appTMSAgent
Target: app.MsFailoverCluster.MsClusterNode
Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-V-PS60972K3ENT-MsClusterNode
v monitors
Source: appTMSAgent
Target: app.MsFailoverCluster.MsClusterResource
Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-Majority
Node Set-MsClusterResource
v monitors
Source: appTMSAgent
Target: app.MsFailoverCluster.MsClusterService
Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-ClusSvc.exeMsClusterService
v installedOn
Source: appTMSAgent
276
Target: sys.windows.WindowsOperatingSystem
Example: WIN2003SP2:Q5-TMSAgent installedOn 10.77.66.34OperatingSystem
v installedOn
Source: app.MsFailoverCluster.MsClusterService
Target: sys.windows.WindowsOperatingSystem
Example: WIN2003SP2:Q5-ClusSvc.exe-MsClusterService installedOn
10.77.66.34-OperatingSystem
v realizes
Source: sys.ComputerSystem
Target: app.MsFailoverCluster.MsCluster
Example: 169.254.187.155-ComputerSystem - realizes WIN2003SP2:Q5itmagents.com-WIN2003SP2-MsCluster
v accessedVia
Target: net.IpNetwork
Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster accessedVia
169.254.187.155-IpAddress
v contains
Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster Contains
WIN2003SP2:Q5-V-PS6097-2K3E-MsClusterNode
v contains
Source: app.MsFailoverCluster.MsClusterResourceGroup
Example: WIN2003SP2:Q5-Cluster Group-MsClusterResourceGroup Contains
WIN2003SP2:Q5-Majority Node Set-MsClusterResource
v controls
Source: app.MsFailoverCluster.MsClusterService
Example: WIN2003SP2:Q5-ClusSvc.exe-MsClusterService Controls
WIN2003SP2:Q5-V-PS6097-2K3E-MsClusterNode
v manages
Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster Manages
WIN2003SP2:Q5-Majority Node Set-MsClusterResource
v manages
Target: app.MsFailoverCluster.MsClusterResourceGroup
WIN2003SP2:Q5-Cluster Group-MsClusterResourceGroup
v manages
Appendix B. Discovery Library Adapter for the monitoring agent
277

WIN2003SP2:Q5-CLWIN2K3-SVC-MsClusterResource
MsCluster class
The MsCluster class represents the instance of Microsoft Cluster Server.
CDM class name
app.MsFailoverCluster.MsCluster
Superior CDM class
core.LogicalElement
Relationships
v monitors
v contains
v manages
v CDM attribute: Id (IdML)
Agent attribute: KQ5B05PHYS.Name
Description: MSYSNCLUSTER_NAME - MSCluster
Example: PS3498WIN2K3:Q5- ITMCluster1- MsCluster
v CDM attribute: Domain
Agent attribute: KQ5WIN32CO.DOMAIN
Description: Cluster Domain
Example: win2k3pado
v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.Node
Description: MSYSN
Example: PS3498WIN2K3:Q5
v CDM attribute: MaxNumberOfNodes
Agent attribute: KQ5B05PHYS. Max_Number_Nodes
Description: Maximum number of nodes
Example: 8
v CDM attribute: Label
Agent attribute: KQ5B05PHYS. Name
Description: The name of the Cluster Server
Example: ITMCluster1-MSCluster Server
MsClusterNode class
The MsClusterNode class represents the node in a Cluster.
CDM class name
app.MsFailoverCluster.MsClusterNode
Superior CDM class
core.LogicalElement
Relationships
v monitors
v contains
v controls
Agent attribute: KQ5D20NODE.Name
278
Description: MSYSN CLUSTER_NAME - MSCluster

Example: PS3498WIN2K3:Q5-W2K3- ClusterNode1- MsClusterNode
CDM attribute: ManagedSystemName
Description: MSYSN
CDM attribute: Name
Description: The name of the Cluster
Example: W2K3-ClusterNode1
CDM attribute: Label
Description: The name of the Cluster Server Node
Example: W2K3-ClusterNode1- MSClusterServer Node
CDM attribute: AdminState
Agent attribute: KQ5D20NODE.State_Raw
Description: NODE_STATUS
Example: Unknown, Other, Enabled or Disabled
The MsClusterResourceGroup class represents the resource group owned by a
node in a cluster.
CDM class name
app.MsFailoverCluster.MsClusterResourceGroup
Superior CDM class
core.LogicalElement
Relationships
v contains
v manages
Agent attribute: KQ5B10RG.Name
Description: MSYSN RESOURCE_GROUP_ NAME MsClusterResourceGroup
Example: PS3498WIN2K3:Q5- Cluster GroupMsClusterResourceGroup
Description: MSYSN
v CDM attribute: Name
Agent attribute: KQ5B10RG.Name
Description: The name of the Resource Group
Example: Cluster Group
v CDM attribute: AdminState
Agent attribute: KQ5B10RG.State_Raw
Description: The status of the Resource Group
v CDM attribute: FailbackWindowStart
Agent attribute: KQ5B10RG.Failback_ Window_Start
Description: FAILBACK_WINDOW_ START
279
Example: 12
v CDM attribute: FailbackWindowEnd
Agent attribute: KQ5B10RG.Failback_ Window_End
Description: FAILBACK_WINDOW_END
Example: 11
v CDM attribute: FailoverPeriod
Agent attribute: KQ5B10RG.Failover_Period
Description: FAILOVER_PERIOD
Example: 6
v CDM attribute: FailoverThreshold
Agent attribute: KQ5B10RG.Failover_ Threshold
Description: FAILOVER_THRESHOLD
Example: 10
v CDM attribute: IsPersistentState
Agent attribute: KQ5B10RG.Persistent_State
Description: PERSISTENT_STATE
Example: True or False
v CDM attribute: Description
Agent attribute: KQ5B10RG.Description
Description: The description of the resource group.
Example: The resource group's description.
v CDM attribute: Auto_FailBack_Type
Agent attribute: KQ5B10RG.Auto_ FailBack_Type
Description: AUTO_FAILBACK_TYPE
Example: Prevent or Allows
MsClusterResource class
The MsClusterResource class represents the resource contained in a resource group.
CDM class name
app.MsFailoverCluster.MsClusterResource
Superior CDM class
core.LogicalElement
Relationships
v monitors
v contains
Agent attribute: KQ5C20RES.Name
Description: MSYSN RESOURCE_GROUP - MsClusterResource
Example: PS3498WIN2K3:Q5 - Disk Q: - MsClusterResource
Description: MSYSN
Agent attribute: KQ5C20RES.Name
Description: The name of the Resource
Example: Disk Q
Agent attribute: KQ5C20RES.State_Raw
280
Description: The status of the Resource

CDM attribute: IsAlivePollInterval
Agent attribute: KQ5C20RES.Is_Alive_ Poll_Interval
Description: IS_ALIVE_POLL_INTERVAL
Example: 60000
CDM attribute: LooksAlivePollInterval
Agent attribute: KQ5C20RES.Looks_ Alive_Poll_Interval
Description: LOOKS_ALIVE_POLL _INTERVAL
Example: 5000
CDM attribute: PendingTimeout
Agent attribute: KQ5C20RES.Pending _Timeout
Description: PENDING_TIMEOUT
Example: 180000
CDM attribute: RestartAction
Agent attribute: KQ5C20RES.Restart_Action
Description: RESTART_ACTION
Example: Restart With No Failover, Restart With Failover, No Restart
CDM attribute: RestartPeriod
Agent attribute: KQ5C20RES.Restart_Period
Description: RESTART_PERIOD
Example: 900000
CDM attribute: RetryPeriodOnFailure
Agent attribute: KQ5C20RES.Retry_ Period_On_Failure
Description: RENTRY_PERIOD_ON _FAILURE.
Example: 800000
CDM attribute: RestartThreshold
Agent attribute: KQ5C20RES.Restart_ Threshold
Description: RESTART_THRESHOLD
Example: 3
MsClusterService class
The MsClusterService class represents the Cluster service.
CDM class name
app.MsFailoverCluster.MsClusterService
Superior CDM class
sys.windows.WindowsService
Relationships
v monitors
v installedOn
Agent attribute: KQ5AVAIL. Name
Description: MSYSN CLUSTER_SERVICE_NAME - MsClusterService
Example: PS3498WIN2K3:Q5- ClusSvc.exe - MsClusterService
Description: MSYSN
281
Agent attribute: KQ5AVAIL.Name

Description: The name of the Cluster Service
Example: ClusSvc.exe
v CDM attribute: Started
Agent attribute: KQ5AVAIL. Status
Description: STARTED
Example: True or False
Agent attribute: KQ5AVAIL. Status
Description: The status of the Cluster Services
v CDM attribute: ProcessId
Agent attribute: KQ5AVAIL. PID
Description: CLUSTER_SERVICE_PID
Example: 1364
v CDM attribute: PathName
Agent attribute: KQ5AVAIL.Full_Name
Description: PATH_NAME
Example: C:\WINDOWS\Cluster\ clussvc.exe
v CDM attribute: ServiceType
Agent attribute: KQ5AVAIL.Type
Description: SERVICE_TYPE
Example: Process or Service
TMSAgent class
The class represents a Tivoli Monitoring Services Agent.
CDM class name
app.TMSAgent
Superior CDM class
SoftwareComponent
Relationships
v monitors
v installedOn
Description: MSYSN TMSAgent
Example: PS3867:Q5- TMSAgent
Description: MSYSN
Example: PS3867:Q5
Description: MSYSN The name of the MS Cluster Server Agent
Example: PS3867:Q5- Ms Cluster Server Agent
v CDM attribute: ManagedObjectName
Description: MSYSN
Example: p@PS3867:Q5
282
v CDM attribute: SoftwareVersion

Agent attribute: INODESTS.Version
Description: Version of the Microsoft Cluster Server Agent
Example: 6.2.0 FP1
v CDM attribute: Product Code
Agent attribute: INODESTS.Product
Description: Product code of Microsoft Cluster Server Agent
Example: Q5
v CDM attribute: Affinity
Agent attribute: INODESTS. Affinities
Description: Affinity of Microsoft Cluster Server Agent
Example: 00000000000000000200000 00000000001000000000
v CDM attribute: Label
Description: Label of Microsoft Cluster Server Agent
Example: PS3867:Q5 - MS Cluster Server
283
284

This appendix contains information about the publications related to the Microsoft
Cluster Server Agent. These publications are listed in the following categories:
v Microsoft Cluster Server Agent library
v Prerequisite publications
v Related publications
See the IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Manager
products: Documentation Guide, SC23-8816, for information about accessing and
using publications. You can find the Documentation Guide in the following
information centers:
v IBM Tivoli Monitoring and OMEGAMON XE
v IBM Tivoli Composite Application Manager
To open the Documentation Guide in the information center, select Using the
publications in the Contents pane.
To find a list of new and changed publications, click What's new on the Welcome
page of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. To
find publications from the previous version of a product, click Previous versions
under the name of the product in the Contents pane.
Microsoft Cluster Server Agent library

There is one document specific to the Microsoft Cluster Server Agent: IBM Tivoli
Composite Application Manager for Microsoft Applications: Microsoft Cluster Server
AgentUser's Guide. This publication provides agent-specific information for
configuring, using, and troubleshooting the Microsoft Cluster Server Agent
Use the configuration chapter in this guide with the IBM Tivoli Monitoring
Installation and Setup Guide to set up the software.
Use the information in this guide with the Tivoli Enterprise Portal User's Guide to
monitor Microsoft Cluster Server resources.
Prerequisite publications
To use the information in this publication effectively, you must have some
prerequisite knowledge, which you can obtain from the following IBM Tivoli
Monitoring publications:
v Exploring IBM Tivoli Monitoring
v IBM Tivoli Monitoring Administrator's Guide
v IBM Tivoli Monitoring Agent Builder Users Guide
v
v
v
v
v
v
IBM
IBM
IBM
IBM
IBM
IBM
Tivoli
Tivoli
Tivoli
Tivoli
Tivoli
Tivoli
Monitoring Command Reference

Monitoring: Configuring Tivoli Enterprise Monitoring Server on z/OS
Monitoring Installation and Setup Guide
Monitoring: Messages
Monitoring Troubleshooting Guide
Monitoring: Upgrading from Tivoli Distributed Monitoring
285
v
v
v
v
v
IBM
IBM
IBM
IBM
IBM
Tivoli
Tivoli
Tivoli
Tivoli
Tivoli
Monitoring:
Monitoring:
Monitoring:
Monitoring:
Monitoring:
Upgrading from V5.1.2

i5/OS Agent User's Guide
Linux OS Agent User's Guide
UNIX Log OS Agent User's Guide
UNIX OS Agent User's Guide
v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v IBM Tivoli Monitoring Universal Agent User's Guide
v IBM Tivoli Monitoring Universal Agent API and Command Programming Reference
Guide
v Tivoli Enterprise Portal User's Guide
Related publications
The following documents also provide useful information:
v IBM Tivoli Enterprise Console Adapters Guide
v IBM Tivoli Enterprise Console Event Integration Facility Users Guide
v IBM Tivoli Enterprise Console Reference Manual
v IBM Tivoli Enterprise Console Rule Builders Guide
Other sources of documentation

You can also obtain technical documentation about monitoring products from the
following sources:
v IBM Tivoli Open Process Automation Library (OPAL)
http://www.ibm.com/software/tivoli/opal
OPAL is an online catalog that contains integration documentation as well as
other downloadable product extensions.
v Redbooks
http://www.redbooks.ibm.com/
IBM Redbooks, Redpapers, and Redbooks Technotes provide information about
products from platform and solution perspectives.
v Technotes
Technotes provide the latest information about known product limitations and
workarounds. You can find Technotes through the IBM Software Support Web
site at http://www.ibm.com/software/support.
v Tivoli wikis on the IBM developerWorks Web site
Tivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/
tivoli/Home is the home for interactive wikis that offer best practices and
scenarios for using Tivoli products. The wikis contain white papers contributed
by IBM employees, and content created by customers and business partners.
286
Two of these wikis are of particular relevance to IBM Tivoli Monitoring:

Tivoli Distributed Monitoring and Application Management Wiki at
http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/
Home provides information about IBM Tivoli Monitoring and related
distributed products, including IBM Tivoli Composite Application
Management products.
Tivoli System z Monitoring and Application Management Wiki at
http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/
Home provides information about the OMEGAMON XE products, Tivoli
NetView for z/OS, Tivoli Monitoring Agent for z/TPF, and other System z
monitoring and application management products.
287
288
Appendix D. Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in this product enable users to do the following:
v Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.
In addition, the product documentation was modified to include the following
features to aid accessibility:
v All documentation is available in both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.
Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and are
documented by the operating system. See the documentation provided by your
operating system for more information.
Magnifying what is displayed on the screen

You can enlarge information in the product windows using facilities provided by
the operating systems on which the product is run. For example, in a Microsoft
Windows environment, you can lower the resolution of the screen to enlarge the
font sizes of the text on the screen. See the documentation provided by your
operating system for more information.
289
290
Appendix E. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
291
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
292
IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBMs application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
(your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not be displayed.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at Copyright and
trademark information at www.ibm.com/legal/copytrade.shtml.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix E. Notices
293
294
Index
A
accessibility 289
Adapter attribute 90
Address attribute 89, 106
AddressMask attribute 107
agent
trace logs 221
agents
troubleshooting 232
Application Component attribute 32
attribute groups
Availability 31
Cluster Domain 36
Cluster Shared Volume 36
Cluster Shared Volume IO 39
Cluster Summary 43
Configuration 48
CPU Interrupts Rollup 50
CPU per Node 52
CPU per Node Rollup 54
Degradation Risk 56
Disk 60
Disk MB Rollup 64
Disk PCT Rollup 66
Enterprise Cluster Summary 68
Event Log 74
Global Update Messages 77
list of all 27
Memory 78
Memory MB Rollup 83
Memory PCT Rollup 85
more information 27
MRR Messages 87
Network Interfaces 88
Network Interfaces State Rollup 91
Network Performance 93
Network Performance Packets Rollup 98
Network Performance Received Rollup 100
Network Performance Sent Rollup 102
Network Reconnections 104
Networks 105
Networks Messages 107
Networks Rollup 110
new 2
Node To Active Group 112
Nodes 115
Nodes State Rollup 117
overview 27
Performance Object Status 119
Quorum Configuration 124
Resource Control Manager 126
Resource Group Moves 128
Resource Group To Preferred Node 129
Resource Group To Resource 131
Resource Groups 133
Resource Groups State Rollup 137
Resource To Dependent Resource 139
Resource To Possible Owner 141
Resources 143
Resources State Rollup 147
Resources Summary 149
attribute groups (continued)

Shared Storage Summary 152
Structural Risk 154
Thread Pool Status 156
attributes
Adapter 90
Address 89, 106
AddressMask 107
Application Component 32
Auto FailBack Type 135
Availability 31
Available Memory MB 79
Available Nodes 155
Average 51, 55, 65, 67, 84, 86, 92, 99, 101, 103, 111, 118,
129, 138, 148
Average Collection Duration 123
Backup State 38
Build Number 116
Bytes Received 93
Bytes Sent 94
Bytes Total 97
Cache Bytes 80
Cache Bytes Peak 80
Cache Faults 80
Cache Hit Percent 124
Cache Hits 123
Cache MB 83
Cache Misses 124
Cache Peak MB 83
Cluster Domain 36
Cluster Name 43, 69, 152
Cluster Shared Volume IO 39
Cluster Shared Volume Name 37
Cluster Summary 43
Command Line 35
Commit Limit MB 82
Committed MB 82
Configuration 49
Core Resource 144
CPU Interrupts Rollup 50
CPU per Node 52
CPU per Node Rollup 54
CSV Node Name 38
CSV Resource Name 38
CSV Resource State 38
Current Bandwidth 94
Current Bandwidth Gbps 97
Current Bandwidth MB 97
Current Capacity 59
Current Disk Queue 63
Current Health 155
Current Host Server 43, 69
Current RG Node 113
Database Update Messages 77
Database Update Messages Delta 77
Default Network Role 49
Degradation Risk 56
Degraded Capacity 59
Delete Requires All Nodes 144
Dependent Resource Description 140
295
attributes (continued)
Dependent Resource Name 140
Dependent Resource State 140
Description 39, 50, 90, 107, 116, 136, 147
Description of Group 114
Description of Node 114, 131, 142
Device ID 90
Disk 60, 61
Disk MB Rollup 65
Disk PCT Rollup 66
Disk Read Bytes 63
Disk Read MB 64
Disk Reads 63
Disk Transfers 64
Disk Used Percent 64
Disk Write Bytes 62
Disk Write MB 64
Disk Writes 62
Domain 36, 48, 74
Enterprise Cluster Summary 68
Error Code 121
Event API Version 76
Event Category 75
Event ID 75
Event Keywords 76
Event Level 76
Event Log 74
Event Source 74
Event Type 75
Failback Window End 136
Failback Window Start 136
Failover Period 135
Failover Threshold 135
Fault State 39
Fewest Nodes Resource 155
FreeMegabytes 62
Full Name 33
Functionality Test Message 35
Functionality Test Status 35
Global Update Messages 77
Group Description 130, 132
Group Name 130, 132
Group State 130, 132
Groups Online 126
Health Less A Node 155
Interrupts 53
Intervals Skipped 124
IO Read Bytes 40
IO Reads 40
IO Write Bytes 40
IO Writes 41
Is Alive Poll Interval 145
KB Received 108
KB Received Delta 108
KB Sent 109
KB Sent Delta 109
Last Collection Duration 123
Last Collection Finished 122
Last Collection Start 122
Less A Node 156
Less A Node Percent 156
Log Name 74
Looks Alive Poll Interval 145
Lowest Health Resource 154
Maintenance File 125
Major Version 116
Max Capacity 57
296
Max Number Nodes 49
Max Util 58
Maximum 50, 55, 65, 67, 84, 86, 91, 98, 100, 102, 111, 117,
128, 137, 148
Memory 79
Memory MB Rollup 83
Memory Module 79
Memory PCT Rollup 85
Message 75
Messages Outstanding 87
Messages Received 109
Messages Received Delta 109
Messages Sent 88, 110
Messages Sent Delta 88, 110
Metadata IO 41
Min Capacity 57
Min Util 58
Minimum 51, 55, 65, 67, 84, 86, 91, 99, 101, 102, 111, 118,
128, 137, 148
Minor Version 116
more information 27
MRR Messages 87
Name 32, 42, 49, 52, 78, 88, 89, 105, 106, 108, 115, 127, 134,
143, 151
Name of Group 114
Name of Node 61, 79, 93, 131, 142
Network Interface 93
Network Interfaces State Rollup 91
Network Name 90
Network Performance Packets Rollup 98
Network Performance Received Rollup 100
Network Performance Sent Rollup 102
Networks 106
Networks Rollup 111
new or changed 2
No of Shared Storage 48, 73
Node 31, 36, 37, 39, 43, 49, 50, 52, 54, 56, 61, 65, 66, 68, 74,
77, 79, 83, 85, 87, 89, 91, 93, 98, 100, 102, 104, 106, 108,
111, 113, 115, 117, 119, 124, 126, 128, 130, 132, 133, 137,
139, 141, 143, 148, 149, 152, 154, 157
Node Group Names 114
Node Highest Version 116
Node Max Capacity 57
Node Max Util 58
Node Min Capacity 57
Node Min Util 58
Node Name 152
Node To Active Group 113
NodeLowestVersion 116
Nodes 115
Nodes State Rollup 117
Normal Message Queue Length 104
Number of Collections 123
Object Name 119
Object Status 120
Object Type 120
Output Queue Length 94
overview 27
Packets 95
Packets Outbound Discarded 94
Packets Outbound Errors 95
Packets Received 96
Packets Received Discarded 95
Packets Received Errors 96
Packets Sent 96
Page Faults 81
Page Faults per Sec 33
Page Reads 81
Page Writes 81
Pages Input 81
Pages Output 82
Pending Timeout 145
Percent Committed Bytes In Use 79
Percent Disk Read Time 62
Percent Disk Write Time 61
Percent Free Space 61
Percent Idle Time 53
Percent Interrupt Time 53
Percent Privileged Time 34, 54
Percent Processor Time 34, 53
Percent User Mode Time 34
Percent User Time 54
Percentage Memory Free 44, 70
Percentage Memory Used 44, 70
Percentage Network Used 48, 73
Percentage Processor Used 44, 69
Percentage Quorum Free 46, 71
Percentage Quorum Used 46, 71
Percentage Shared Storage Free 47, 73
Percentage Shared Storage Used 47, 73
Persistent State 134, 144
PID 34
Pool Paged Bytes 82
Pool Paged MB 83
Precentage Processor Free 44, 69
Previous RG Node 113
Processor 52
Query Name 119
Quorum Arbitration Time Maximum 125
Quorum Arbitration Time Minimum 125
Quorum Available 45, 71
Quorum Log File Size 125
Quorum Path 45, 70, 126
Quorum Total Size 45, 70
Quorum Type 126
Quorum Utilization 45, 71
Received MB 97
Reconnect Count 104
Redirected Read Bytes 41
Redirected Reads 42
Redirected Write Bytes 42
Redirected Writes 42
Refresh Interval 123
Resource Control Manager 126
Resource Controls 150
Resource Description 133, 140, 142
Resource Failure 150
Resource Failure Access Violation 150
Resource Failure Deadlock 151
Resource Group Moves 128
Resource Group To Preferred Node 130
Resource Group To Resource 131
Resource Groups 133
Resource Groups State Rollup 137
Resource Name 132, 139, 141
Resource State 133, 139, 141
Resource To Dependent Resource 139
Resource To Possible Owner 141
Resource Type Controls 151
Resources 143
Resources Online 151
Resources State Rollup 147
Resources Summary 149
Restart Action 146
Restart Period 146
Restart Threshold 146
Retry Period On Failure 147
RG Node Changed 113
RHS Processes 127
RHS Restarts 127
Role 107
Sent MB 97
Shared Storage Available 46, 72, 153
Shared Storage Path 152
Shared Storage State 153
Shared Storage Summary 152
Shared Storage Total Size 47, 72, 153
Shared Storage Utilization 47, 72, 153
Standard Deviation 51, 56, 66, 68, 85, 87, 92, 99, 101, 103,
112, 118, 129, 138, 149
State 90, 107, 117, 136, 147
State of Group 114
State of Node 113, 131, 142
State Raw 89, 106, 115, 134, 143
Status 32
Structural Risk 154
System Information 43, 69
System Name 90
Thread Count 34
Thread Pool Active Threads 157
Thread Pool Avg Active Threads 158
Thread Pool Avg Job Wait 160
Thread Pool Avg Queue Length 159
Thread Pool Max Active Threads 158
Thread Pool Max Queue Length 160
Thread Pool Max Size 157
Thread Pool Min Active Threads 158
Thread Pool Min Queue Length 159
Thread Pool Queue Length 159
Thread Pool Size 157
Thread Pool Total Jobs 160
Time Generated 75
Timestamp 32, 36, 37, 40, 43, 49, 50, 52, 55, 57, 61, 65, 67,
69, 77, 79, 83, 85, 87, 89, 91, 93, 98, 100, 102, 104, 106, 108,
111, 113, 115, 117, 119, 125, 126, 128, 130, 132, 134, 137,
139, 141, 143, 148, 150, 152, 154, 157
Total 51, 56, 66, 68, 84, 86, 92, 99, 101, 103, 112, 118, 129,
138, 149
Total Capacity 58
Total MB 97
Total Util 59
Type 33, 144
Unacknowledged Message Queue Length 105
Uniform Commitment 60
Unitary Commitment 60
Update Messages 78
Update Messages Delta 78
Urgent Message Queue Length 105
Virtual Size 33
Volume Name 37
Volume Offset 37
Index
297
Working Set Size 34
Auto FailBack Type attribute 135
Availability
situations 166, 167
workspaces
descriptions 16
list 15
Availability attribute group 31
Availability workspace 16
Available Memory MB attribute 79
Available Nodes attribute 155
Average attribute 51, 55, 65, 67, 84, 86, 92, 99, 101, 103, 111,
118, 129, 138, 148
Average Collection Duration attribute 123
B
Backup State attribute 38
Bring Resource Group online action 190
Bring Resource online action 191
Build Number attribute 116
built-in troubleshooting features 219
Bytes Received attribute 93
Bytes Sent attribute 94
Bytes Total attribute 97
C
Cache Bytes attribute 80
Cache Bytes Peak attribute 80
Cache Faults attribute 80
Cache Hit Percent attribute 124
Cache Hits attribute 123
Cache MB attribute 83
Cache Misses attribute 124
Cache Peak MB attribute 83
calculate historical data disk space 161
capacity planning
Microsoft Cluster Server Agent 161
capacity planning for historical data 161
changes
attribute groups, new 2
attributes 2
baroc file updated 3
situations 3
Take Action commands 3
views 3
workspaces 2, 3
Cluster Configuration Summary workspace 18
Cluster Dashboard
situations 166, 169
workspaces
descriptions 17
list 15
Cluster Dashboard workspace 17
Cluster Domain attribute group 36
Cluster Name attribute 43, 69, 152
Cluster Shared Volume attribute group 36
Cluster Shared Volume IO attribute group 39
Cluster Shared Volume Name attribute 37
Cluster Shared Volume workspace 18
Cluster Summary attribute group 43
Command Line attribute 35
commands
tacmd addSystem 11
298
commands, Take Action 189

Commit Limit MB attribute 82
Committed MB attribute 82
components 4
configuration 7
after installation 8, 10
fields 10
remote 11
values 10
Configuration
situations 166, 172
workspaces
descriptions 18
list 15
Configuration attribute group 48
Configuration workspace 18
configuring the monitoring agent 8, 10
Core Resource attribute 144
CPU Interrupts Rollup attribute group 50
CPU per Node attribute group 52
CPU per Node Rollup attribute group 54
CSV Node Name attribute 38
CSV Resource Name attribute 38
CSV Resource State attribute 38
Current Bandwidth attribute 94
Current Bandwidth Gbps attribute 97
Current Bandwidth MB attribute 97
Current Capacity attribute 59
Current Disk Queue attribute 63
Current Health attribute 155
Current Host Server attribute 43, 69
Current RG Node attribute 113
D
data
trace logs 220
data logged
data provider logs
See agent
Database Update Messages attribute 77
Database Update Messages Delta attribute 77
Default Network Role attribute 49
Degradation Risk attribute group 56
Degraded Capacity attribute 59
Delete Requires All Nodes attribute 144
Dependent Resource Description attribute 140
Dependent Resource Name attribute 140
Dependent Resource State attribute 140
Description attribute 39, 50, 90, 107, 116, 136, 147
Description of Group attribute 114
Description of Node attribute 114, 131, 142
developerWorks Web site 286
Device ID attribute 90
Discovery Library Adapter
MsCluster class
cdm attribute 278
MsClusterNode class
cdm attribute 278, 279
Discovery Library Adapter (continued)

TMSAgent class
Disk attribute 61
Disk attribute group 60
disk capacity planning
See capacity planning
disk capacity planning for historical data
Disk MB Rollup attribute group 64
Disk PCT Rollup attribute group 66
Disk Read Bytes attribute 63
Disk Read MB attribute 64
Disk Reads attribute 63
Disk Transfers attribute 64
Disk Used Percent attribute 64
Disk Write Bytes attribute 62
Disk Write MB attribute 64
Disk Writes attribute 62
DLA (Discovery Library Adapter)
MsCluster class
cdm attribute 278
MsClusterNode class
TMSAgent class
documentation
See publications
Domain attribute 36, 48, 74
161
E
Enterprise Cluster Summary attribute group 68
Enterprise Level Cluster Dashboard workspace 16
environment
features 1
functions 1
Error Code attribute 121
event
mapping 253
Event API Version attribute 76
Event Category attribute 75
Event ID attribute 75
Event Keywords attribute 76
Event Level attribute 76
Event Log
situations 166, 172
workspaces
descriptions 19
list 15
Event Log attribute group 74
Event Log workspace 19
Event Source attribute 74
Event Type attribute 75
F
Failback Window End attribute 136
Failback Window Start attribute 136
Failover Period attribute 135
Failover Threshold attribute 135
Fault State attribute 39

features, Microsoft Cluster Server Agent 1
Fewest Nodes Resource attribute 155
files
agent trace 221
installation trace 221
other trace log 221
trace logs 220
FreeMegabytes attribute 62
Full Name attribute 33
Functionality Test Message attribute 35
Functionality Test Status attribute 35
functions, Microsoft Cluster Server Agent 1
G
gathering support information 219
Global Update Messages attribute group
Group Description attribute 130, 132
Group Name attribute 130, 132
Group State attribute 130, 132
Groups Online attribute 126
77
H
Health Less A Node attribute 155
historical data
calculate disk space 161
capacity planning
Microsoft Cluster Server Agent
disk capacity planning 161
161
I
IBM Software Support
See support
IBM Support Assistant 249
IBM Tivoli Distributed Monitoring and Application
Management Wiki 249
IBM Tivoli Enterprise Console
event mapping 253
information
troubleshooting 219
information, additional
attributes 27
policies 195
situations 165
workspaces 13
installation
log file 221
problems 225
remote 11
silent 7
interface, user 4
Interrupts attribute 53
Intervals Skipped attribute 124
IO Read Bytes attribute 40
IO Reads attribute 40
IO Write Bytes attribute 40
IO Writes attribute 41
Is Alive Poll Interval attribute 145
ISA 249
Index
299
K
KB Received attribute 108
KB Received Delta attribute 108
KB Sent attribute 109
KB Sent Delta attribute 109
KQ5_MSCS_Cluster_Unbalanced situation 179
KQ5_MSCS_InterfaceStateDown situation 174
KQ5_MSCS_InterfaceStateUnavail situation 173
KQ5_MSCS_InterfaceStateUnknown situation 172
KQ5_MSCS_InterfaceStateUnreach situation 174
KQ5_MSCS_Network_StateDown situation 176
KQ5_MSCS_Network_StateUnavail situation 175
KQ5_MSCS_Network_StateUnknown situation 175
KQ5_MSCS_Network_StateUnreach situation 177
KQ5_MSCS_Node_Changed situation 183
KQ5_MSCS_Node_Down situation 178
KQ5_MSCS_Node_Paused situation 178
KQ5_MSCS_Node_Unknown situation 177
KQ5_MSCS_PCPU_Utilization_Crit situation 172
KQ5_MSCS_PCPU_Utilization_Warn situation 171
KQ5_MSCS_PMemory_Free_Crit situation 169
KQ5_MSCS_PMemory_Free_Warn situation 169
KQ5_MSCS_PNW_Utilization_Crit situation 170
KQ5_MSCS_PNW_Utilization_Warn situation 170
KQ5_MSCS_QrmDiskSpace_Critical situation 180
KQ5_MSCS_QrmDiskSpace_Warning situation 180
KQ5_MSCS_Resource_Failed situation 184
KQ5_MSCS_Resource_Inherited situation 188
KQ5_MSCS_Resource_Initializing situation 187
KQ5_MSCS_Resource_Offline situation 184
KQ5_MSCS_Resource_Pending situation 185
KQ5_MSCS_Resource_Pending_Off situation 186
KQ5_MSCS_Resource_Pending_On situation 186
KQ5_MSCS_Resource_Unknown situation 187
KQ5_MSCS_RG_Failed situation 181
KQ5_MSCS_RG_Offline situation 181
KQ5_MSCS_RG_PartiallyOnLine situation 182
KQ5_MSCS_RG_Unknown situation 183
KQ5_Process_Down situation 167
KQ5_WMI_Obj_Not_Available situation 168
L
Last Collection Duration attribute 123
Last Collection Finished attribute 122
Last Collection Start attribute 122
Less A Node attribute 156
Less A Node Percent attribute 156
library, Microsoft Cluster Server Agent 285
list of messages 250
Log Name attribute 74
logged data
logging
agent trace logs 221
built-in features 219
installation log files 221
trace log files 220
Looks Alive Poll Interval attribute 145
Lowest Health Resource attribute 154
M
Maintenance File attribute 125
Major Version attribute 116
Max Capacity attribute 57
300
Max Number Nodes attribute 49

Max Util attribute 58
Maximum attribute 50, 55, 65, 67, 84, 86, 91, 98, 100, 102, 111,
117, 128, 137, 148
Memory attribute group 78
Memory MB Rollup attribute group 83
Memory Module attribute 79
Memory PCT Rollup attribute group 85
Message attribute 75
messages
for Microsoft Cluster Server Agent 250
format 249
overview 249
syntax 249
Messages Outstanding attribute 87
Messages Received attribute 109
Messages Received Delta attribute 109
Messages Sent attribute 88, 110
Messages Sent Delta attribute 88, 110
Metadata IO attribute 41
Microsoft Cluster Server Agent
components 4
features 1
functions 1
performance considerations 243
situations 166, 167
workspaces
descriptions 15
list 14
Microsoft Cluster Server Agent workspace 15
Min Capacity attribute 57
Min Util attribute 58
Minimum attribute 51, 55, 65, 67, 84, 86, 91, 99, 101, 102, 111,
118, 128, 137, 148
Minor Version attribute 116
MRR Messages attribute group 87
MsCluster class
cdm attribute 278
MsClusterclass
cdm attribute 278
MsClusterNode class
cdm attribute 279
MsClusterNodeclass
cdm attribute 278
MsClusterResourceclass
cdm attribute 280
MsClusterResourceGroupclass
cdm attribute 279
MsClusterServiceclass
cdm attribute 281
N
Name attribute 32, 42, 49, 52, 78, 88, 89, 105, 106, 108, 115,
127, 134, 143, 151
Name of Group attribute 114
Name of Node attribute 61, 79, 93, 131, 142
Network Interface attribute 93
Network Interfaces
situations 166, 172
Network Interfaces (continued)

workspaces
descriptions 19
list 15
Network Interfaces attribute group 88
Network Interfaces State Rollup attribute group 91
Network Interfaces workspace 19
Network Name attribute 90
Network Performance attribute group 93
Network Performance Packets Rollup attribute group 98
Network Performance Received Rollup attribute group 100
Network Performance Sent Rollup attribute group 102
Network Performance workspace 20
Network Reconnections attribute group 104
Network Reconnections workspace 20
Networks
situations 166, 175
workspaces
descriptions 20
list 15
Networks attribute group 105
Networks Messages attribute group 107
Networks Messages workspace 21
Networks Rollup attribute group 110
Networks workspace 20
new attribute groups 2
new or changed attributes 2
new or changed situations 3
new or changed Take Action commands 3
new or changed views 3
new or changed workspaces 2, 3
No of Shared Storage attribute 48, 73
Node attribute 31, 36, 37, 39, 43, 49, 50, 52, 54, 56, 61, 65, 66,
68, 74, 77, 79, 83, 85, 87, 89, 91, 93, 98, 100, 102, 104, 106, 108,
111, 113, 115, 117, 119, 124, 126, 128, 130, 132, 133, 137, 139,
141, 143, 148, 149, 152, 154, 157
Node CPU workspace 21
Node Disks workspace 21
Node Group Names attribute 114
Node Highest Version attribute 116
Node Max Capacity attribute 57
Node Max Util attribute 58
Node Memory workspace 22
Node Min Capacity attribute 57
Node Min Util attribute 58
Node Name attribute 152
Node To Active Group attribute group 112
NodeLowestVersion attribute 116
Nodes
situations 166, 177
workspaces
descriptions 21
list 15
Nodes attribute group 115
Nodes State Rollup attribute group 117
Nodes workspace 22
Normal Message Queue Length attribute 104
Number of Collections attribute 123
P
Packets attribute 95
Packets Outbound Discarded attribute 94
Packets Outbound Errors attribute 95
Packets Received attribute 96
Packets Received Discarded attribute 95
Packets Received Errors attribute 96
Packets Sent attribute 96
Page Faults attribute 81
Page Faults per Sec attribute 33
Page Reads attribute 81
Page Writes attribute 81
Pages Input attribute 81
Pages Output attribute 82
Pending Timeout attribute 145
Percent Committed Bytes In Use attribute 79
Percent Disk Read Time attribute 62
Percent Disk Write Time attribute 61
Percent Free Space attribute 61
Percent Idle Time attribute 53
Percent Interrupt Time attribute 53
Percent Privileged Time attribute 34, 54
Percent Processor Time attribute 34, 53
Percent User Mode Time attribute 34
Percent User Time attribute 54
Percentage Memory Free attribute 44, 70
Percentage Memory Used attribute 44, 70
Percentage Network Used attribute 48, 73
Percentage Processor Used attribute 44, 69
Percentage Quorum Free attribute 46, 71
Percentage Quorum Used attribute 46, 71
Percentage Shared Storage Free attribute 47, 73
Percentage Shared Storage Used attribute 47, 73
performance considerations 243
Performance Object Status attribute group 119
Performance Object Status workspace 17
Persistent State attribute 134, 144
PID attribute 34
policies
more information 195
overview 195
Pool Paged Bytes attribute 82
Pool Paged MB attribute 83
Precentage Processor Free attribute 44, 69
Previous RG Node attribute 113
problems and workarounds 225
Processor attribute 52
publications
developerWorks Web site 286
OPAL 286
prerequisite 285
Redbooks 286
related 286
Technotes 286
types 285
wikis 286
purposes
troubleshooting 219
O
Object Name attribute 119
Object Status attribute 120
Object Type attribute 120
OPAL documentation 286
other new function 3
Output Queue Length attribute
Q
94
queries, using attributes 27

Query Name attribute 119
Query Object Status workspace 19
Quorum Arbitration Time Maximum attribute
125
Index
301
Quorum Arbitration Time Minimum attribute

Quorum Available attribute 45, 71
Quorum Configuration attribute group 124
Quorum Configuration workspace 19
Quorum Log File Size attribute 125
Quorum Path attribute 45, 70, 126
Quorum Total Size attribute 45, 70
Quorum Type attribute 126
Quorum Utilization attribute 45, 71
125
R
Received MB attribute 97
Reconnect Count attribute 104
Redbooks 286
Redirected Read Bytes attribute 41
Redirected Reads attribute 42
Redirected Write Bytes attribute 42
Redirected Writes attribute 42
Refresh Interval attribute 123
remote
installation and configuration 11
remote deployment
troubleshooting 230
Resource Control Manager attribute group 126
Resource Controls attribute 150
Resource Description attribute 133, 140, 142
Resource Failure Access Violation attribute 150
Resource Failure attribute 150
Resource Failure Deadlock attribute 151
Resource Group Associations workspace 23
Resource Group Moves attribute group 128
Resource Group to Possible Node workspace 23
Resource Group To Preferred Node attribute group 129
Resource Group To Resource attribute group 131
Resource Groups
situations 166, 181
workspaces
descriptions 23
list 15
Resource Groups attribute group 133
Resource Groups State Rollup attribute group 137
Resource Groups workspace 23
Resource Name attribute 132, 139, 141
Resource State attribute 133, 139, 141
Resource Summary workspace 23
Resource To Dependent Resource attribute group 139
Resource To Possible Owner attribute group 141
Resource Type Controls attribute 151
Resources
situations 166, 184
workspaces
descriptions 23
list 15
Resources attribute group 143
Resources Online attribute 151
Resources State Rollup attribute group 147
Resources Summary attribute group 149
Resources workspace 24
Restart Action attribute 146
Restart Period attribute 146
Restart Threshold attribute 146
Retry Period On Failure attribute 147
RG Node Changed attribute 113
RHS Processes attribute 127
RHS Restarts attribute 127
Role attribute 107
302
S
Sent MB attribute 97
Shared Storage Available attribute 46, 72, 153
Shared Storage Path attribute 152
Shared Storage State attribute 153
Shared Storage Summary attribute group 152
Shared Storage Total Size attribute 47, 72, 153
Shared Storage Utilization attribute 47, 72, 153
silent installation 7
situations
general troubleshooting 243, 244
KQ5_MSCS_Cluster_Unbalanced 179
KQ5_MSCS_InterfaceStateDown 174
KQ5_MSCS_InterfaceStateUnavail 173
KQ5_MSCS_InterfaceStateUnknown 172
KQ5_MSCS_InterfaceStateUnreach 174
KQ5_MSCS_Network_StateDown 176
KQ5_MSCS_Network_StateUnavail 175
KQ5_MSCS_Network_StateUnknown 175
KQ5_MSCS_Network_StateUnreach 177
KQ5_MSCS_Node_Changed 183
KQ5_MSCS_Node_Down 178
KQ5_MSCS_Node_Paused 178
KQ5_MSCS_Node_Unknown 177
KQ5_MSCS_PCPU_Utilization_Crit 172
KQ5_MSCS_PCPU_Utilization_Warn 171
KQ5_MSCS_PMemory_Free_Crit 169
KQ5_MSCS_PMemory_Free_Warn 169
KQ5_MSCS_PNW_Utilization_Crit 170
KQ5_MSCS_PNW_Utilization_Warn 170
KQ5_MSCS_QrmDiskSpace_Critical 180
KQ5_MSCS_QrmDiskSpace_Warning 180
KQ5_MSCS_Resource_Failed 184
KQ5_MSCS_Resource_Inherited 188
KQ5_MSCS_Resource_Initializing 187
KQ5_MSCS_Resource_Offline 184
KQ5_MSCS_Resource_Pending 185
KQ5_MSCS_Resource_Pending_Off 186
KQ5_MSCS_Resource_Pending_On 186
KQ5_MSCS_Resource_Unknown 187
KQ5_MSCS_RG_Failed 181
KQ5_MSCS_RG_Offline 181
KQ5_MSCS_RG_PartiallyOnLine 182
KQ5_MSCS_RG_Unknown 183
KQ5_Process_Down 167
KQ5_WMI_Obj_Not_Available 168
list of all 166, 167
new or changed 3
overview 165
predefined 166
situations, using attributes 27
Software Support 249
Standard Deviation attribute 51, 56, 66, 68, 85, 87, 92, 99, 101,
103, 112, 118, 129, 138, 149
State attribute 90, 107, 117, 136, 147
State of Group attribute 114
State of Node attribute 113, 131, 142
State Raw attribute 89, 106, 115, 134, 143
Status attribute 32
Structural and Degradation Risk
situations 167, 188
workspaces
descriptions 24
list 15
Structural and Degradation Risk workspace 24
Structural Risk attribute group 154
Structural Risk workspace 25

support
gathering information for 219
list of messages 250
messages 249
support assistant 249
syntax
messages 249
System Information attribute 43, 69
System Name attribute 90
T
tacmd addSystem command 11
Take Action commands
Bring Resource Group online 190
Bring Resource online 191
list of all 189
new or changed 3
overview 189
predefined 189
Take Resource Group offline 192
Take Resource offline 193
troubleshooting 246
Take Resource Group offline action 192
Take Resource offline action 193
Technotes 286
Thread Count attribute 34
Thread Pool Active Threads attribute 157
Thread Pool Avg Active Threads attribute 158
Thread Pool Avg Job Wait attribute 160
Thread Pool Avg Queue Length attribute 159
Thread Pool Max Active Threads attribute 158
Thread Pool Max Queue Length attribute 160
Thread Pool Max Size attribute 157
Thread Pool Min Active Threads attribute 158
Thread Pool Min Queue Length attribute 159
Thread Pool Queue Length attribute 159
Thread Pool Size attribute 157
Thread Pool Status attribute group 156
Thread Pool Status workspace 17
Thread Pool Total Jobs attribute 160
Time Generated attribute 75
Timestamp attribute 32, 36, 37, 40, 43, 49, 50, 52, 55, 57, 61,
65, 67, 69, 77, 79, 83, 85, 87, 89, 91, 93, 98, 100, 102, 104, 106,
108, 111, 113, 115, 117, 119, 125, 126, 128, 130, 132, 134, 137,
139, 141, 143, 148, 150, 152, 154, 157
Tivoli Common Reporting
troubleshooting 246
TMSAgent class
TMSAgentclass
cdm attribute 282
Total attribute 51, 56, 66, 68, 84, 86, 92, 99, 101, 103, 112, 118,
129, 138, 149
Total Capacity attribute 58
Total MB attribute 97
Total Util attribute 59
trace logs 220
troubleshooting 219, 225
agents 232
installation 225
installation logs 221
messages 249
remote deployment 230
troubleshooting (continued)
situations 242, 244
Tivoli Common Reporting 246
uninstallation 225
uninstallation logs 221
workspaces 235
Type attribute 33, 144
U
Unacknowledged Message Queue Length attribute
Uniform Commitment attribute 60
uninstallation
log file 221
problems 225
Unitary Commitment attribute 60
Update Messages attribute 78
Update Messages Delta attribute 78
Urgent Message Queue Length attribute 105
user interfaces options 4
105
V
views
Availability workspace 16
Cluster Configuration Summary workspace 18
Cluster Dashboard workspace 17
Cluster Shared Volume workspace 18
Configuration workspace 18
Enterprise Level Cluster Dashboard workspace 16
Event Log workspace 19
Microsoft Cluster Server Agent workspace 15
Network Interfaces workspace 19
Network Performance workspace 20
Network Reconnections workspace 20
Networks Messages workspace 21
Networks workspace 20
new or changed 3
Node CPU workspace 21
Node Disks workspace 21
Node Memory workspace 22
Nodes workspace 22
Performance Object Status workspace 17
Query Object Status workspace 19
Quorum Configuration workspace 19
Resource Group Associations workspace 23
Resource Group to Possible Node workspace 23
Resource Groups workspace 23
Resource Summary workspace 23
Resources workspace 24
Structural and Degradation Risk workspace 24
Structural Risk workspace 25
Thread Pool Status workspace 17
Virtual Size attribute 33
Volume Name attribute 37
Volume Offset attribute 37
W
wikis 286
workarounds 225
agents 232
remote deployment 230
situations 242
Index
303
workarounds (continued)
Tivoli Common Reporting 246
workspaces 235
Working Set Size attribute 34
workspaces
Availability 16
Cluster Configuration Summary 18
Cluster Dashboard 17
Configuration 18
Enterprise Level Cluster Dashboard 16
Event Log 19
list of all 14
more information 13
Networks 20
new or changed 2, 3
Node CPU 21
Node Disks 21
Node Memory 22
Nodes 21, 22
overview 13
predefined 14
Query Object Status 19
Resource Group Associations 23
Resource Group to Possible Node 23
Resource Groups 23
Resource Summary 23
Resources 23, 24
Structural and Degradation Risk 24
Structural Risk 25
troubleshooting 235
304

Printed in USA
SC27-2316-02

User's Guide: Ivo I

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User's Guide: Ivo I

Uploaded by

Copyright:

Available Formats

Tivoli IBM Tivoli Composite Application Manager for Microsoft

Applications: Microsoft Cluster Server Agent

Tivoli IBM Tivoli Composite Application Manager for Microsoft

Chapter 2. Agent-specific installation

Chapter 3. Workspaces reference . . . 13

Chapter 4. Attributes reference . . . . 27

CPU per Node attribute group . . . . . . . . 52

Chapter 5. Situations reference. . . . 165

Chapter 6. Take Action commands

Chapter 7. Policies reference. . . . . 195

Chapter 8. Tivoli Common Reporting

Microsoft Cluster Server Agent: User's Guide

Disk Utilization for Cluster Nodes report . . .

Chapter 9. Troubleshooting . . . . . 219

Appendix A. IBM Tivoli Enterprise

Navigating the interface using the keyboard .

Appendix E. Notices . . . . . . . . 291

Appendix C. Documentation library

Appendix D. Accessibility . . . . . . 289

Microsoft Cluster Server Agent: User's Guide

Cross-linked workspaces within the Microsoft

Copyright IBM Corp. 2007, 2010

General problems and solutions for

Microsoft Cluster Server Agent: User's Guide

Chapter 1. Overview of the Microsoft Cluster Server Agent

IBM Tivoli Monitoring overview

Features of the monitoring agent

Functions of the monitoring agent

New in this release

Global Update Messages

Shared Storage Summary

Microsoft Cluster Server Agent: User's Guide

Top 5 Cluster Systems Having High Processor Usage

v Support for native 64-bit agent.

Components of the IBM Tivoli Monitoring environment

Agent Management Services

User interface options

Microsoft Cluster Server Agent: User's Guide

Chapter 1. Overview of the Microsoft Cluster Server Agent

Microsoft Cluster Server Agent: User's Guide

Chapter 2. Agent-specific installation and configuration

Installing language packs

Select the language of the installer and click OK.

UNIX or Linux systems

3. Run the following command to launch the installation program:

Agent-specific installation and configuration

Microsoft Cluster Server Agent: User's Guide

Click Configure and select Configure a Service or Application.

5. Type the appropriate details in Service Name and IP address fields.

Microsoft Cluster Name (Environment variable CTIRA_HOSTNAME)

The Microsoft Cluster Name configuration parameter is used to create the

Configuring the monitoring agent after installation

Microsoft Cluster Server Agent: User's Guide

Microsoft Cluster Name

Remote installation and configuration

Microsoft Cluster Server Agent: User's Guide

Chapter 3. Workspaces reference

More information about workspaces

Copyright IBM Corp. 2007, 2010

Table 2. Cross-linked Workspaces to the Microsoft Hyper-V Server agent

Table 3. Cross-linked Workspaces to Windows OS agent

Microsoft Cluster Server Agent: User's Guide

v Availability Navigator item