User's Guide - Beta 1 Draft

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent vnext User's Guide - Beta 1 Draft SC27-2316-05

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent vnext User's Guide - Beta 1 Draft SC27-2316-05

Note Before using this information and the product it supports, read the information in Notices on page 357. This edition applies to vnext 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 2008, 2013. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents Tables............... v Chapter 1. Overview of the agent.... 1 IBM Tivoli Monitoring........... 1 Functions of the monitoring agent....... 1 New in this release............ 2 Components of the IBM Tivoli Monitoring environment.............. 2 Agent Management Services......... 3 User interface options........... 3 Data sources.............. 4 Chapter 2. Agent installation and configuration............ 7 Requirements.............. 7 Language pack installation......... 7 Installing language packs on Windows systems.. 7 Installing language packs on UNIX or Linux systems............... 8 Silent installation of language packs on Windows, UNIX, or Linux systems......... 8 Prerequisites checking........... 10 Running as a non-administrator user...... 11 Agent-specific installation and configuration... 11 Configuration values.......... 13 Remote installation and configuration.... 14 Chapter 3. Workspaces reference... 15 Predefined workspaces.......... 15 Workspace descriptions.......... 16 Microsoft Cluster Server Navigator item.... 16 Availability Navigator item........ 17 Cluster Dashboard Navigator item...... 18 Configuration Navigator item....... 19 Event Log Navigator item........ 20 Network Interfaces Navigator item..... 21 Networks Navigator item......... 21 Nodes Navigator item.......... 22 Resource Groups Navigator item...... 23 Resources Navigator item........ 23 Structural and Degradation Risk Navigator item 24 Cross-linked workspaces.......... 25 Chapter 4. Attributes reference.... 27 Attribute groups for the monitoring agent.... 27 Attributes in each attribute group....... 31 Availability attribute group........ 32 CAU Configuration attribute group..... 36 CAU Last Run attribute group....... 41 Cluster Domain attribute group...... 44 Cluster Shared Volume attribute group.... 45 Cluster Shared Volume Block Redirection attribute group............ 47 Cluster Shared Volume Cache attribute group.. 52 Cluster Shared Volume Coordinator attribute group............... 61 Cluster Shared Volume File System attribute group............... 66 Cluster Shared Volume IO attribute group... 88 Cluster Shared Volume Manager attribute group 92 Cluster Summary attribute group...... 101 Cluster Topology attribute group...... 107 Configuration attribute group....... 108 CPU Interrupts Rollup attribute group.... 110 CPU per Node attribute group....... 111 CPU per Node Rollup attribute group.... 114 Degradation Risk attribute group...... 116 Disk attribute group.......... 120 Disk MB Rollup attribute group...... 125 Disk PCT Rollup attribute group...... 127 Enterprise Cluster Summary attribute group.. 129 Event Log attribute group........ 135 Global Update Messages attribute group... 137 Memory attribute group......... 139 Memory MB Rollup attribute group..... 144 Memory PCT Rollup attribute group.... 146 MRR Messages attribute group...... 148 Network Interfaces attribute group..... 150 Network Interfaces State Rollup attribute group 152 Network Performance attribute group.... 154 Network Performance Packets Rollup attribute group............... 160 Network Performance Received Rollup attribute group............... 162 Network Performance Sent Rollup attribute group............... 164 Network Reconnections attribute group... 165 Networks attribute group........ 167 Networks Messages attribute group..... 169 Networks Rollup attribute group...... 172 Node To Active Group attribute group.... 174 Nodes attribute group......... 177 Nodes State Rollup attribute group..... 179 Performance Object Status attribute group... 181 Quorum Configuration attribute group.... 186 Resource Control Manager attribute group.. 188 Resource Group Moves attribute group.... 189 Resource Group To Preferred Node attribute group............... 191 Resource Group To Resource attribute group 193 Resource Groups attribute group...... 195 Resource Groups State Rollup attribute group 198 Resource To Dependent Resource attribute group............... 200 Resource To Possible Owner attribute group.. 202 Resources attribute group........ 204 Resources State Rollup attribute group.... 209 Resources Summary attribute group..... 211 Shared Storage Summary attribute group... 213 Structural Risk attribute group...... 216 Copyright IBM Corp. 2008, 2013 iii

Thread Pool Status attribute group..... 218 Disk capacity planning for historical data.... 221 Chapter 5. Situations reference.... 225 Predefined situations........... 225 Situation descriptions........... 227 Microsoft Cluster Server Navigator item... 227 Availability Navigator item........ 227 Cluster Dashboard Navigator item..... 228 Configuration Navigator item....... 232 Event Log Navigator item........ 232 Network Interfaces Navigator item..... 232 Networks Navigator item........ 233 Nodes Navigator item......... 235 Resource Groups Navigator item...... 237 Resources Navigator item........ 239 Structural and Degradation Risk Navigator item 243 Chapter 6. Take Action commands reference............. 245 Predefined Take Action commands...... 245 Take Action command descriptions...... 245 Bring Resource Group online action..... 246 Bring Resource online action....... 247 Delete Resource Group action....... 248 Move Resource Group action....... 249 Pause Node action.......... 251 Resume Node action.......... 252 Take Resource Group offline action..... 253 Take Resource offline action....... 255 Chapter 7. Policies reference..... 257 Predefined policies........... 257 Chapter 8. Tivoli Common Reporting for the monitoring agent...... 259 Cognos-based report packages........ 259 Prerequisites............. 259 Importing Cognos report packages..... 261 Cognos data models and reports...... 262 Chapter 9. Troubleshooting..... 269 Trace logging............. 270 Overview of log file management..... 270 Principal trace log files......... 271 Examples: Using trace logs........ 273 RAS trace parameters......... 274 Setting trace parameters for the Tivoli Enterprise Console server............ 276 Problems and workarounds........ 277 Installation and configuration troubleshooting 277 Remote deployment troubleshooting.... 280 Agent troubleshooting......... 283 Workspace troubleshooting........ 289 Situation troubleshooting........ 295 Take Action commands troubleshooting... 299 Tivoli Common Reporting troubleshooting.. 299 Support information........... 301 Informational, warning, and error messages overview............... 301 Message format........... 302 Agent messages........... 302 Appendix A. Event mapping..... 309 Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent............ 339 DLA data model class types represented in CDM 339 DLA data model classes for Microsoft Cluster Server agent.............. 339 MsCluster class............ 340 MsClusterNode class.......... 341 MsClusterResourceGroup class...... 342 MsClusterResource class......... 343 MsClusterService class......... 344 IpNetwork class........... 345 TMSAgent class........... 346 Appendix C. Integration with Tivoli Business Service Manager..... 349 Components for integrating with Tivoli Business Service Manager............ 349 Tasks to integrate the agent with Tivoli Business Service Manager............ 350 Installing the Discovery Library Toolkit on the Tivoli Business Service Manager...... 350 Configuring the Tivoli Event Integration Facility (EIF) probe to enrich events....... 350 Creating a service in Tivoli Business Service Manager.............. 351 Creating a data source mapping for each data source............... 352 Configuring additional IBM Tivoli Monitoring web services............. 352 Viewing data in the Tivoli Enterprise Portal.. 352 Appendix D. Documentation library 353 Prerequisite publications.......... 353 Related publications........... 354 Other sources of documentation....... 354 Notices.............. 357 Trademarks.............. 359 Index............... 361 iv Microsoft Cluster Server agent: User's Guide

Tables 1. Mechanisms used to gather attributes.... 5 2. Cross-linked workspaces within the Microsoft Cluster Server agent......... 25 3. Cross-linked workspaces to the Microsoft Hyper-V Server agent......... 26 4. Cross-linked workspaces to Windows OS agent 26 5. Capacity planning for historical data logged by the Microsoft Cluster Server agent... 222 6. Cluster Server Agent Reports Prerequisite Scanner report........... 263 7. Resource Utilization Details for Single Node report.............. 263 8. Cluster Nodes Availability report..... 264 9. Cluster Resource Group Availability report 265 10. Disk Utilization for Cluster Nodes report 266 11. Memory Utilization for Cluster Nodes report 267 12. Information to gather before contacting IBM Software Support.......... 269 13. Trace log files for troubleshooting agents 271 14. Problems and solutions for installation and configuration........... 278 15. General problems and solutions for uninstallation........... 279 16. Remote deployment problems and solutions 281 17. Agent problems and solutions...... 283 18. Workspace problems and solutions.... 290 19. Situation problems and solutions..... 295 20. Take Action commands problems and solutions............. 299 21. Tivoli Common Reporting for Microsoft Cluster Server agent problems and solutions. 299 Copyright IBM Corp. 2008, 2013 v

vi Microsoft Cluster Server agent: User's Guide

Chapter 1. Overview of the agent The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent provides you with the capability to monitor Microsoft Cluster Server. You can also use the agent to take basic actions with the Microsoft Cluster Server. IBM Tivoli Monitoring is the base software for the Microsoft Cluster Server agent. The Microsoft Cluster Server agent monitors the following functions: v Availability and resources v Performance v Error and event log v Historical data IBM Tivoli Monitoring 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 achieve 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 take actions, schedule work, and automate manual tasks. The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. You can use the consolidated view of your environment as seen in the Tivoli Enterprise Portal to monitor and resolve performance issues throughout the enterprise. See the IBM Tivoli Monitoring publications listed in Prerequisite publications on page 353 for complete information about IBM Tivoli Monitoring and the Tivoli Enterprise Functions of the monitoring agent 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 provides the ability to generate reports for all metrics collected. Copyright IBM Corp. 2008, 2013 1

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 Cluster shared volume, cluster shared volume I/O, cluster summary for all clusters in an organization along with its CPU utilization, and summary of shared storage usage. Take Actions Actions are provided for taking resource and resource group offline and online. New in this release For the Microsoft Cluster Server agent, the following enhancements have been made since version 6.3, including the fix packs: v New attribute groups: CAU Configuration CAU Last Run v Updated the kq5.baroc file to support IBM Tivoli Enterprise Console event mapping changes v Added the Prerequisite Scanner report to verify the availability of tables and views in the Tivoli Data Warehouse for the predefined reports 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 Tivoli Monitoring. This Tivoli Monitoring environment contains the following components: Tivoli Enterprise Portal client The portal has a user interface based on Java for viewing and monitoring your enterprise. Tivoli Enterprise Portal Server The portal server 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. Tivoli Enterprise Monitoring Server The monitoring server 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. Tivoli Enterprise Monitoring Agent, Microsoft Cluster Server agent This monitoring agent collects data and distributes the data to the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal, Tivoli Data Warehouse, and Tivoli Integrated IBM Tivoli Netcool/OMNIbus Tivoli Netcool/OMNIbus is an optional component and the recommended event management component. The Netcool/OMNIbus software is a service level management (SLM) system that delivers real-time, centralized monitoring of complex networks and IT domain events. Event information is tracked in a high-performance, in-memory database and presented to specific users through individually configurable filters and views. The software includes automation functions that you can use to perform intelligent processing on managed events. You can use this software to forward events for Tivoli Monitoring situations to Tivoli Netcool/OMNIbus. 2 Microsoft Cluster Server agent: User's Guide

IBM Tivoli Enterprise Console The Tivoli Enterprise Console is an optional component that acts as a central collection point for events from various 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 (by using the event viewer), and you can forward events from Tivoli Monitoring situations to the Tivoli Enterprise Console component. If you do not already use Tivoli Enterprise Console and need an event management component, you can choose to use IBM Tivoli Netcool/OMNIbus. IBM Tivoli Common Reporting 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. IBM Tivoli Application Dependency Discovery Manager (TADDM) TADDM delivers automated discovery and configuration tracking capabilities to build application maps that provide real-time visibility into application complexity. IBM Tivoli Business Service Manager The Tivoli Business Service Manager component delivers real-time information to help you respond to alerts effectively based on business requirements. Optionally, you can use this component to meet service-level agreements (SLAs). Use the Tivoli Business Service Manager tools to help build a service model that you can integrate with Tivoli Netcool/OMNIbus alerts or optionally integrate with data from an SQL data source. Optional components provide access to data from other IBM Tivoli applications such as Tivoli Monitoring and TADDM. Agent Management Services You can use IBM Tivoli Monitoring Agent Management Services to manage the Microsoft Cluster Server agent. Agent Management Services is available for the following IBM Tivoli Monitoring OS agents: Windows, Linux, and UNIX. The services are designed to keep the Microsoft Cluster Server agent available, and to provide information about the status of the product to the Tivoli Enterprise For more information about Agent Management Services, see Agent Management Services in the IBM Tivoli Monitoring Administrator's Guide. IBM Tivoli Monitoring V6.2.2, Fix Pack 2 or later provides support for Agent Management Services. User interface options Installation of the base IBM Tivoli Monitoring software and other integrated applications provides various interfaces that you can use to work with your resources and data. The following interfaces are available: Tivoli Enterprise Portal user interface You can run the Tivoli Enterprise Portal as a desktop application or a browser application. The client interface is a graphical user interface (GUI) based on Java on a Windows or Linux workstation. The browser application is automatically installed with the Tivoli Enterprise Portal Server. The desktop application is installed by using the Tivoli Monitoring installation media or with a Java Web Start application. 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. Command-line interface You can use Tivoli Monitoring commands to manage the Tivoli Monitoring components and their Chapter 1. Overview of the agent 3

configuration. You can also run commands at the Tivoli Enterprise Console event server or the Tivoli Netcool/OMNIbus ObjectServer to configure event synchronization for enterprise situations. Manage Tivoli Enterprise Monitoring Services window You can use the window for the Manage Tivoli Enterprise Monitoring Services utility to configure the agent and start Tivoli services not designated to start automatically. IBM Tivoli Netcool/OMNIbus event list You can use the Netcool/OMNIbus event list to monitor and manage events. An event is created when the Netcool/OMNIbus ObjectServer receives an event, alert, message, or data item. Each event is made up of columns (or fields) of information that are displayed in a row in the ObjectServer alerts.status table. The Tivoli Netcool/OMNIbus web GUI is also a web-based application that processes network events from one or more data sources and presents the event data in various graphical formats. IBM Tivoli Enterprise Console You can use the Tivoli Enterprise Console to help ensure the optimal availability of an IT service for an organization. The Tivoli Enterprise Console is an event management application that integrates system, network, database, and application management. If you do not already use Tivoli Enterprise Console and need an event management component, you can choose to use Tivoli Netcool/OMNIbus. IBM Tivoli Common Reporting Use the Tivoli Common Reporting web user interface for specifying report parameters and other report properties, generating formatted reports, scheduling reports, and viewing reports. This user interface is based on the Tivoli Integrated IBM Tivoli Application Dependency Discovery Manager The Discovery Management Console is the TADDM client user interface for managing discoveries. IBM Tivoli Business Service Manager The Tivoli Business Service Manager console provides a graphical user interface that you can use to logically link services and business requirements within the service model. The service model provides an operator with a second-by-second view of how an enterprise is performing at any moment in time or how the enterprise performed over a time period. Data sources Monitoring agents collect data from specific data sources. The Microsoft Cluster Server agent collects data from the following sources: WMI You can use Windows Management Instrumentation (WMI) to monitor and control managed resources throughout the network. Resources include hard drives, file systems, operating system settings, processes, services, shares, registry settings, networking components, event logs, users, and groups. WMI is built into clients with Windows 2000 or later, and can be installed on any 32-bit Windows client. Perfmon You can use the Windows Performance Monitor, or Perfmon, to view various system and application performance metrics for collection and use by management applications. You typically view system metrics on a Windows system through the 'perfmon' application. Availability You can use the agent to monitor availability of the application and related components in the following ways: v Monitor the status of the processes. v Monitor the Windows services used by the application. 4 Microsoft Cluster Server agent: User's Guide

Scripts You can use the agent s application-specific commands and interfaces to gather metrics. Windows Event Log You can use the agent to collect Windows Event Log entries related to the monitored resource and forward them to IBM Tivoli Monitoring. The following table shows each Microsoft Cluster Server agent attribute group and the mechanism that is used to gather the attributes. Table 1. Mechanisms used to gather attributes Attribute group Availability CAU Configuration CAU Last Run Cluster Domain Cluster Shared Volume Cluster Shared Volume Block Redirection Cluster Shared Volume Cache Cluster Shared Volume Coordinator Cluster Shared Volume File System Cluster Shared Volume Manager Cluster Shared Volume IO Cluster Summary Cluster Topology Configuration CPU Interrupts Rollup CPU per Node CPU per Node Rollup Degradation Risk Disk Disk MB Rollup Disk PCT Rollup Enterprise Cluster Summary Event Log Global Update Messages Memory Memory MB Rollup Memory PCT Rollup MRR Messages Network Interfaces Network Interfaces State Rollup Network Performance Network Performance Packets Rollup Network Performance Received Rollup Collection source Operating system Script Script WMI WMI Perfmon Perfmon Perfmon Perfmon Perfmon Perfmon Script Script WMI WMI WMI WMI Script WMI WMI WMI Script Windows Event Log Perfmon WMI WMI WMI Perfmon Script WMI WMI WMI WMI Chapter 1. Overview of the agent 5

Table 1. Mechanisms used to gather attributes (continued) Attribute group Collection source Network Performance Sent Rollup WMI Network Reconnections Perfmon Networks Script Networks Messages WMI Networks Rollup WMI Node To Active Group WMI Nodes WMI Nodes State Rollup WMI Performance Object Status Operating system Quorum Configuration WMI Resource Control Manager Perfmon Resource Group Moves WMI Resource Group To Preferred Node WMI Resource Group To Resource WMI Resource Groups Script Resource Groups State Rollup WMI Resource To Dependent Resource WMI Resource To Possible Owner WMI Resources Script Resources State Rollup WMI Resources Summary Perfmon Shared Storage Summary Script Structural Risk Script 6 Microsoft Cluster Server agent: User's Guide

Chapter 2. Agent installation and configuration Agent installation and configuration requires the use of the IBM Tivoli Monitoring Installation and Setup Guide and agent-specific installation and configuration information. To install and configure the Microsoft Cluster Server agent, use the Installing monitoring agents procedures in the IBM Tivoli Monitoring Installation and Setup Guide along with the agent-specific installation and configuration information. If you are installing silently by using a response file, see Performing a silent installation of IBM Tivoli Monitoring in the IBM Tivoli Monitoring Installation and Setup Guide. With the self-describing agent capability, new or updated IBM Tivoli Monitoring agents using IBM Tivoli Monitoring V6.2.3 or later can become operational after installation without having to perform additional product support installation steps. To take advantage of this capability, see Enabling self-describing agent capability at the hub monitoring server in the IBM Tivoli Monitoring Installation and Setup Guide. Also, see Self-describing monitoring agents in the IBM Tivoli Monitoring Administrator's Guide. Requirements Before installing and configuring the agent, make sure your environment meets the requirements for the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. For information about system requirements, see the Prerequisites topic or the system requirements topic in the ITCAM for Microsoft Applications Information Center (http://publib.boulder.ibm.com/infocenter/ tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html). Language pack installation The steps for installing language packs depend on which operating system and mode of installation you are using. To install a language pack for the agent support files on the Tivoli Enterprise Monitoring Server, the Tivoli Enterprise Monitoring Agent, and the Tivoli Enterprise Portal Server, make sure that you installed the product in the English language. Then use the steps for the operating system or mode of installation you are using: v Installing language packs on Windows systems v Installing language packs on UNIX or Linux systems on page 8 v Silent installation of language packs on Windows, UNIX, or Linux systems on page 8 Installing language packs on Windows systems You can install the language packs on a Windows system. Before you begin First, make sure that you installed the product in the English language. Procedure 1. On the language pack CD, double-click the lpinstaller.bat file to start the installation program. 2. Select the language of the installer and click OK. 3. In the Introduction panel, click Next Copyright IBM Corp. 2008, 2013 7

4. Click Add/Update and click Next. 5. Select the folder where the National Language Support package (NLSPackage) files are located. Typically, the NLSPackage files are located in the nlspackage folder where the installer executable file is located. 6. Select the language support for the agent of your choice and click Next. To make multiple selections, press Ctrl and select the language that you want. 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. After installation completes, click Finish to exit the installer. 10. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any of these components are installed. Installing language packs on UNIX or Linux systems You can install the language packs on a UNIX or Linux system. Before you begin First, make sure that you installed the product in the English language. Procedure 1. Enter the mkdir command to create a temporary directory on the computer, for example, mkdir dir_name. Make sure that the full path of the directory does not contain any spaces. 2. Mount the language pack CD to the temporary directory that you created. 3. Enter the following command to start the installation program: cd dir_name lpinstaller.sh -c install_dir where install_dir is where you installed IBM Tivoli Monitoring. Typically, the directory name is /opt/ibm/itm for UNIX and Linux systems. 4. Select the language of the installer and click OK. 5. In the Introduction panel, click Next. 6. Click Add/Update and click Next. 7. Select the folder where the National Language Support package (NLSPackage) files are located. Typically, the NLSPackage files are located in the nlspackage folder where the installer executable file is located. 8. Select the language support for the agent of your choice and click Next. To make multiple selections, press Ctrl and select the language that you want. 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. After installation completes, click Finish to exit the installer. 12. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any of these components are installed. Silent installation of language packs on Windows, UNIX, or Linux systems You can use the silent-mode installation method to install the language packs. In silent mode, the installation process obtains the installation settings from a predefined response file. It does not prompt you for any information. Before you begin First, make sure that you installed the product in the English language. 8 Microsoft Cluster Server agent: User's Guide

Procedure 1. Copy and paste the ITM_Agent_LP_silent.rsp response file template as shown in Response file example. 2. Change the following parameter settings: NLS_PACKAGE_FOLDER Folder where the National Language Support package (NLSPackage) files are located. Typically, the NLSPackage files are located in the nlspackage folder, for example: NLS_PACKAGE_FOLDER = //tmp//lp//nlspackage. PROD_SELECTION_PKG Name of the language pack to install. Several product components can be included in one language package. You might want to install only some of the available components in a language pack. BASE_AGENT_FOUND_PKG_LIST Agent for which you are installing language support. This value is usually the same as PROD_SELECTION_PKG. LANG_SELECTION_LIST Language you want to install. 3. Enter the command to install the language pack with a response file (silent installation): v For Windows systems: lpinstaller.bat -f path_to_response_file v For UNIX or Linux systems: lpinstaller.sh -c candle_home -f path_to_response_file where candle_home is the IBM Tivoli Monitoring base directory. Response file example # IBM Tivoli Monitoring Agent Language Pack Silent Installation Operation # #This is a sample response file for silent installation mode for the IBM Tivoli #Monitoring Common Language Pack Installer. #. #This file uses the IBM Tivoli Monitoring Common Agent Language Pack with the #install package as an example. #Note: #This response file is for the INSTALLATION of language packs only. #This file does not support UNINSTALLATION of language packs in silent mode. #------------------------------------------------------------------------------- #------------------------------------------------------------------------------- #To successfully complete a silent installation of the the example of Common Agent #localization pack, complete the following steps: # #1.Copy ITM_Agent_LP_silent.rsp to the directory where lpinstaller.bat or #lpinstaller.sh is located (IBM Tivoli Monitoring Agent Language Pack build #location). # #2.Modify the response file so that it is customized correctly and completely for #your site. # Complete all of the following steps in the response file. # #3.After customizing the response file, invoke the silent installation using the #following command: #For Windows: # lpinstaller.bat -f <path_to_response_file> #For UNIX and Linux: # lpinstaller.sh -c <candle_home> -f <path_to_response_file> #Note:<candle_home> is the IBM Tivoli Monitoring base directory. #-------------------------------------------------------------------------------- Chapter 2. Agent installation and configuration 9

#-------------------------------------------------------------------------------- #Force silent install mode. #-------------------------------------------------------------------------------- INSTALLER_UI=silent #--------------------------------------------------------------------------------- #Run add and update actions. #--------------------------------------------------------------------------------- CHOSEN_INSTALL_SET=ADDUPD_SET #--------------------------------------------------------------------------------- #NLS Package Folder, where the NLS Packages exist. #For Windows: # Use the backslash-backslash(\\) as a file separator (for example, #C:\\zosgmv\\LCD7-3583-01\\nlspackage). #For UNIX and Linux: # Use the slash-slash (//) as a file separator (for example, #//installtivoli//lpsilenttest//nlspackage). #--------------------------------------------------------------------------------- #NLS_PACKAGE_FOLDER=C:\\zosgmv\\LCD7-3583-01\\nlspackage NLS_PACKAGE_FOLDER=//tmp//LP//nlspackage #--------------------------------------------------------------------------------- #List the packages to process; both variables are required. #Each variable requires that full paths are specified. #Separate multiple entries with a semicolon (;). #For Windows: # Use the backslash-backslash(\\) as a file separator. #For Unix and Linux: # Use the slash-slash (//) as a file separator. #--------------------------------------------------------------------------------- #PROD_SELECTION_PKG=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkg #BASE_AGENT_FOUND_PKG_LIST=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkg PROD_SELECTION_PKG=//tmp//LP//nlspackage//kex_nls.nlspkg;//tmp//LP//nlspackage// koq_nls.nlspkg BASE_AGENT_FOUND_PKG_LIST=//tmp//LP//nlspackage//kex_nls.nlspkg;// tmp//lp//nlspackage//koq_nls.nlspkg #-------------------------------------------------------------------------------- #List the languages to process. #Separate multiple entries with semicolons. #-------------------------------------------------------------------------------- LANG_SELECTION_LIST=pt_BR;fr;de;it;ja;ko;zh_CN;es;zh_TW Prerequisites checking The prerequisite checker utility verifies whether all the prerequisites that are required for the agent installation are met. The prerequisite checker creates a log file that contains a report of all the prerequisites checks when the prerequisite checker was run. For the Microsoft Cluster Server agent, the prerequisite checker verifies the following requirements: v Memory v Disk v Operating systems v Microsoft Cluster Server availability Additionally, the prerequisite checker verifies whether the user, who installs the agent, is a member of the Administrators group. For detailed information about installation prerequisites, see the Prerequisites topic for the agent in the IBM Tivoli Composite Application Manager for Microsoft Applications Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/ welcome_msapps63.html). 10 Microsoft Cluster Server agent: User's Guide

You can run the prerequisite checker in stand-alone mode or remotely. For more information about the prerequisite checker, see "Prerequisite Checking for IBM Tivoli Monitoring Agents" in the IBM Tivoli Monitoring Installation and Setup Guide. Running as a non-administrator user You can run the monitoring agent for the Cluster Server as a non-administrator user. However, some functionality is unavailable. To create a non-administrator user, create a new domain user, and set up registry permissions for the new user as follows: v Full access to the HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory v Read access to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib directory Note: Provide the specified access rights on all the nodes in a cluster. If you define these permissions for the domain user, data is displayed for all the Perfmon-based attribute groups. See Data sources on page 4 for a list of all the Perfmon-based attributes. However, on the Tivoli Enterprise Portal, display of data varies according to the operating system as follows: v Partial data is displayed on Windows 2003 systems. v No data is displayed on Windows 2008 R2 systems. Agent-specific installation and configuration In addition to the installation and configuration information in the IBM Tivoli Monitoring Installation and Setup Guide, use the agent-specific installation and configuration information to install 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 cluster server. Using IBM Tivoli Monitoring v6.2 utilities to manage the agent (start, stop, restart, remove, configure) conflicts with cluster server control of the agent. When using the IBM Tivoli Monitoring v6.2 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 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 agent's resource group so that the node owning the agent resource group can access the disk. You must add the cluster agent service as a resource in the Cluster Server so that the agent can monitor the Cluster Server. Before adding the agent service as a resource, ensure that you have completed the following steps: v The startup type for the agent is set to Manual. v The agent is stopped on each node in the cluster. Chapter 2. Agent installation and configuration 11

To add the agent service as a resource in the Cluster Server that runs on a Windows 2003 Server, complete the following steps: 1. Right-click the agent resource group that is created for the agent. Select New and then select Resource. 2. Select Generic Service as a resource type, and specify a name for the agent resource. 3. Ensure that the Possible Owners list contains all the nodes in the cluster. 4. If historical data 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. Retain the default settings in all the other windows, and click Finish. To add the agent service as a resource in the Cluster Server that runs on a Windows 2008 Server, complete the following steps: 1. Open the Failover Cluster Management window. 2. In the left pane, right-click Services and Applications, and then click More Actions > Create Empty Service or Application. The new service is displayed in the Services and Applications list. 3. Rename the newly created service. 4. Right-click the new service and click Add Resource > Generic Service. 5. In the New Resource Wizard window, select Monitoring Agent for Microsoft Cluster Server and click Next. 6. Click Next in the subsequent windows till you see the Finish button. 7. Click Finish. The agent service is added as a resource. 8. Right-click Monitoring Agent for Microsoft Cluster Server and click Bring Resource Online. To add the agent service as a resource in the Cluster Server that runs on a Windows 2012 Server, complete the following steps: 1. Open the Failover Cluster Management window. 2. In the left pane, right-click Roles and then click Create Empty Role. The role represents a resource group. 3. Rename the newly created role. 4. Right-click the new role and click Add Resource > Generic Service. 5. In the New Resource Wizard window, select Monitoring Agent for Microsoft Cluster Server and click Next. 6. Click Next in the subsequent windows till you see the Finish button. 7. Click Finish. The agent service is added as a resource. 8. Right-click Monitoring Agent for Microsoft Cluster Server and click Bring Resource Online. After completing these steps, the agent is started automatically on the preferred node in the cluster, and the agent starts monitoring the cluster. Ensure that the agent is stopped on the other nodes in the cluster. Each node in the cluster has a single instance of the agent installed. Use Manage Tivoli Monitoring Services to configure and set startup agent parameters. In addition to the standard agent configuration, the following two parameters that are unique to the agent are specified : v Microsoft Cluster Name (Environment variable CTIRA_HOSTNAME) v Shared Agent History Directory (Environment variable CTIRA_HIST_DIR) Configure the CTIRA_HOSTNAME environment variable by completing the following steps: 12 Microsoft Cluster Server agent: User's Guide

1. In the Manage Tivoli Enterprise Monitoring Services window, right-click Monitoring Agent for Microsoft Cluster Server, and then click Advanced. 2. Click Edit Variables. The Monitoring Agent for Microsoft Cluster Server: Override Local Variable Settings window opens. 3. Click Add. The Add Environment Setting Override window opens. 4. From the Variable list, select CITRA_HOSTNAME. 5. In the Value field, delete %Computername%, and type a cluster name. Note: Do not delete the TYPE=REG_EXPAND_SZ value. 6. Click OK. Similarly, you can configure the CTIRA_HIST_DIR environment variable. The Microsoft Cluster Name configuration parameter is used to create the Windows system name that appears in the Tivoli Enterprise 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. 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 beacuse 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. Configuration values For both local and remote configuration, you provide the configuration values for the agent to operate. When you are configuring an agent, a panel is displayed so you can enter each value. When a default value exists, 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 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 (CTIRA_HIST_DIR) A shared directory for the cluster that is not a quorum drive where the agents can locate cluster historical information. Chapter 2. Agent installation and configuration 13

The type is string. This value is optional. Default value: None Microsoft Cluster Name (CTIRA_HOSTNAME) A unique name assigned to the cluster that will be displayed in the Tivoli Enterprise The type is string. This value is required. Default value: None Remote installation and configuration You can install the monitoring agent remotely from the Tivoli Enterprise Portal or from the command line. When installing the agent remotely, you must provide the configuration values for the agent to operate. See Configuration values on page 13. To install from the portal, see the IBM Tivoli Monitoring Installation and Setup Guide. To remotely install or configure an agent through the Tivoli Enterprise Portal, you must have installed the application support for that agent (Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal). You must also have installed the agent bundle into the Remote Deploy Depot. For information about displaying the configuration options that are available to use with the configuresystem or addsystem commands see "tacmd describesystem" in the IBM Tivoli Monitoring Command Reference. If you are using the command line, the following command is an example of remote installation and 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 14 Microsoft Cluster Server agent: User's Guide

Chapter 3. Workspaces reference A workspace is the working area of the Tivoli Enterprise Portal application window. The Navigator tree contains a list of the workspaces provided by the agent. About workspaces Use the Navigator tree to select the workspace you want to see. As part of the application window, 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. You can also use the Workspace Gallery tool as described in the Tivoli Enterprise Portal User's Guide to open workspaces. The workspaces in the Navigator are displayed 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. Workspace views can be any combination of query-based views, event views, and special purpose views. Additional information about workspaces For more information about creating, customizing, and working with workspaces, see "Using workspaces" in 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 Predefined workspaces and the information about 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 Attribute groups for the monitoring agent on page 27. Predefined workspaces The Microsoft Cluster Server agent provides predefined workspaces, which are organized by Navigator item. v Microsoft Cluster Server Navigator item Microsoft Cluster Server workspace Enterprise Level Cluster Dashboard workspace v Availability Navigator item Availability workspace Performance Object Status workspace Thread Pool Status workspace v Cluster Dashboard Navigator item Copyright IBM Corp. 2008, 2013 15

Cluster Dashboard workspace Cluster Shared Volume workspace Cluster Shared Volume Block Redirection and Volume Coordinator Statistics workspace Cluster Shared Volume Cache and Volume manager Statistics workspace Cluster Shared Volume File System Statistics workspace Cluster Topology 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 Workspace descriptions Each workspace description provides information about the workspace such as the purpose and a list of views in the workspace. Workspaces are listed under Navigator items. Microsoft Cluster Server Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Microsoft Cluster Server workspace MS Cluster Server View. This workspace displays the overall status of the cluster. 16 Microsoft Cluster Server agent: User's Guide

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 eight 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. This workspace contains the following views: 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 The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Availability workspace The Availability workspace displays the overall health of the application. This workspace contains the following views: 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 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 Chapter 3. Workspaces reference 17

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. This workspace contains the following view: 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 The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Cluster Dashboard workspace The Cluster Dashboard workspace provides details of the cluster and its capacity. This workspace contains the following views: 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. Cluster Shared Volume workspace The Cluster Shared Volume workspace provides information about the Cluster Shared Volume disk that is configured in the cluster environment. Data is not displayed for Windows 2003 cluster. This workspace contains the following views: Cluster Shared Volume Displays information about the Cluster Shared Volume disk that is configured in the cluster environment. Cluster Shared Volume IO Displays information about the I/O activity on all the cluster shared volume disks of the cluster. Data is displayed only for Windows 2008 cluster. IO Read Bytes Displays information about the number of read operations that are sent from the Cluster Shared Volume. Data is displayed only for Windows 2008 cluster. IO Write Bytes Displays information about the number of write operations that are sent to the Cluster Shared Volume. Data is displayed only for Windows 2008 cluster. Cluster Shared Volume Block Redirection and Volume Coordinator Statistics workspace The Cluster Shared Volume Block Redirection and Volume Coordinator Statistics workspace provides information about the CSV block redirection and CSV coordinator in the cluster environment.data is not displayed for Windows 2003 and 2008 cluster. This workspace contains the following views: Cluster Shared Volume Block Redirection Summary Displays information about the CSV block redirection in the cluster environment. Cluster Shared Volume Coordinator Summary Displays information about the CSV coordinator in the cluster environment. 18 Microsoft Cluster Server agent: User's Guide

CSV Block Read and write operations Displays information about number of read and write operations that are completed on the CSV. CSV Coordinator Read and Write operations Displays the number of read and write operations that are redirected to the coordinator node. Cluster Shared Volume Cache and Volume manager Statistics workspace The Cluster Shared Volume Cache and Volume manager Statistics workspace provides information about the CSV cache and CSV manager in the cluster environment.data is not displayed for Windows 2003 and 2008 cluster. This workspace contains the following views: Cluster Shared Volume Cache Summary Displays information about the CSV cache in the cluster environment. Cluster Shared Volume Manager Summary Displays information about the CSV manager in the cluster environment. Percent Cache utilization Displays information about the percent of total configured cache that is currently used.data is displayed only for the cache enabled CSV. Cluster Shared Volume File System Statistics workspace The Cluster Shared Volume File System Statistics workspace provides information about the Cluster Shared Volume (CSV) file system in the cluster environment.data is not displayed for Windows 2003 and 2008 cluster. This workspace contains the following views: CSV File System Summary Displays information about the CSV file System in the cluster environment. CSV IO Read Write Operations Displays information about the I/O read and write operations that are completed on the CSV. Read and Write Latency Displays information about the latency of read and write operations in the CSV file system. Cluster Topology workspace The Cluster Topology workspace provides information about the cluster topology that includes nodes in the cluster, resource groups that are managed by each node, and resources in each resource group. This workspace contains the following view: Cluster Topology Displays the cluster topology that includes nodes in the cluster, resource groups that are managed by each node, and resources in each resource group. Configuration Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. 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. This workspace contains the following views: 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. Chapter 3. Workspaces reference 19

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. This workspace contains the following views: State of Nodes This view displays the state of the nodes. It is linked to the detailed Node workspace. 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. This workspace contains the following view: 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. This workspace contains the following views: 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 and Microsoft Windows 2012 This view displays the Quorum Configuration details. Maximum and Minimum time (in sec), necessary to decide the Quorum owner node, Quorum and Quorum Path for Microsoft Windows 2008 and Microsoft Windows 2012. Event Log Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. 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. This workspace contains the following view: Event Log Shows the recent Event Log entries for Microsoft Cluster Server. 20 Microsoft Cluster Server agent: User's Guide

Network Interfaces Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Network Interfaces workspace Provides availability and detail information for the cluster network interfaces. This workspace contains the following views: 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. Network Performance workspace This workspace provides network performance data collected from each node in the cluster. This workspace contains the following views: 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. 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. Networks Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Network Reconnections workspace The Network Reconnections workspace provides information about reconects between the nodes of the cluster and the queue length of messages. This workspace contains the following views: Network Reconnections 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. This workspace contains the following views: 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. 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. This workspace contains the following views: Network Messages Sent/Received Displays information about the cluster network messages that are sent and received on the network per cluster node. Chapter 3. Workspaces reference 21

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 The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Node CPU workspace This workspace contains processor information collected from each node in the cluster. This workspace contains the following views: 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 eight hours. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. CPU Interrupts Persec Rollup (8hr) This view graphs the interrupts per second over eight hours. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. Node Disks workspace This workspace contains disk information collected from each node in the cluster. This workspace contains the following views: 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 displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. Percent Free Space on the Logical Disks (8hr) This view graphs the percent free space on the disks over eight hours. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. Node Memory workspace This workspace contains memory information collected from each node in the cluster. This workspace contains the following views: 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 displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. The Percent Committed Bytes in Use (8hr) This view graphs the percent committed bytes used over eight hours. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. 22 Microsoft Cluster Server agent: User's Guide

Nodes workspace This workspace provides detailed information for the cluster nodes. It also includes a node availability graph. This workspace contains the following views: 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. Resource Groups Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Resource Group Associations workspace This workspace shows the resource group associations between resources and nodes This workspace contains the following views: 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. This workspace contains the following 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. This workspace contains the following views: 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 eight hours. Resources Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. Resource Summary workspace The Resources Summary workspace provides information about the overall health of the various types of resources available in the cluster environment. This workspace contains the following views: 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. Total Resources Online Displays the number of resources that are online. Chapter 3. Workspaces reference 23

Resources workspace The resource workspace provides availability and detail information for the cluster resources. This workspace contains the following views: 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. Structural and Degradation Risk Navigator item The workspace descriptions are organized by the Navigator item to which the workspaces are relevant. 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%). This workspace contains the following views: 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. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. Commitment Graph This view graphs the commitment of the cluster processor over eight hours. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. 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 = 24 Microsoft Cluster Server agent: User's Guide

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). This workspace contains the following views: 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. This view displays data only when historical data collection is configured, and historical data is collected at the Tivoli Enterprise Monitoring Server. 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 and to the Windows OS agent. Table 2. Cross-linked workspaces within the Microsoft Cluster Server agent Link name Local Cluster Capacity Dashboard Availability Nodes Configuration navigator item workspace name MS Cluster Server Enterprise Level Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Dashboard Resources Resource Groups Resource Group Associations view name Enterprise Level Cluster Capacity Cluster Capacity Details Cluster Capacity Details Cluster Capacity Details Resource Groups to Resources Target workspace name Cluster Dashboard Availability Nodes Configuration Resources Filter Resources Nodes Nodes Nodes Resources N/A Resource Groups Nodes Nodes Nodes Resource Groups N/A Cluster Cluster Dashboard Cluster Topology Cluster Topology Enterprise Level Cluster Dashboard N/A Nodes Resource Groups Resources CSV Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Dashboard Cluster Name N/A N/A N/A Cluster Topology Cluster Topology Nodes N/A Cluster Topology Cluster Topology Resource Groups N/A Cluster Topology Cluster Topology Resources N/A Cluster Topology Cluster Topology Cluster Shared Volume Resource Name N/A Chapter 3. Workspaces reference 25

Table 3. Cross-linked workspaces to the Microsoft Hyper-V Server agent Link name MSCS to Hyper-V agent navigator item workspace name view name Target workspace name Filter Nodes Nodes Nodes Virtual Machine Node Name Table 4. Cross-linked workspaces to Windows OS agent Link name MSCS to Windows OS agent navigator item workspace name view name Target workspace name Filter Nodes Nodes Nodes Virtual Machine Node Name 26 Microsoft Cluster Server agent: User's Guide

Chapter 4. Attributes reference Attributes are the application properties that are being measured and reported by the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. About attributes Attributes are organized into attribute groups. Attributes in an attribute group relate to a single object such as an application, or to a single kind of data such as status information. Attributes in a group can be used in queries, query-based views, situations, policy workflows, take action definitions, and launch application definitions. Chart or table views and situations are two examples of how attributes in a group can be used: 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 Properties editor to 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 values you assign to the situation attributes are compared 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. Additional 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 attribute groups, a list of the attributes in each attribute group, and descriptions of the attributes for this monitoring agent, see Attribute groups for the monitoring agent and Attributes in each attribute group on page 31. Attribute groups for the monitoring agent The Microsoft Cluster Server 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, 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: CAU Configuration Table name: KQ5CAUCONF Warehouse table name: KQ5_CAU_CONFIGURATION or KQ5CAUCONF v Attribute group name: CAU Last Run Table name: KQ5CAULRUN Warehouse table name: KQ5_CAU_LAST_RUN or KQ5CAULRUN v Attribute group name: Cluster Domain Copyright IBM Corp. 2008, 2013 27

Table name: KQ5WIN32CO Warehouse table name: KQ5_CLUSTER_DOMAIN or KQ5WIN32CO v Attribute group name: Cluster Shared Volume Table name: KQ5CLUSCSV Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME or KQ5CLUSCSV v Attribute group name: Cluster Shared Volume Block Redirection Table name: KQ5CLUSTE7 Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_BLOCK_REDIRECTION or KQ5CLUSTE7 v Attribute group name: Cluster Shared Volume Cache Table name: KQ5CLUSTE6 Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_CACHE or KQ5CLUSTE6 v Attribute group name: Cluster Shared Volume Coordinator Table name: KQ5CLUSTE4 Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_COORDINATOR or KQ5CLUSTE4 v Attribute group name: Cluster Shared Volume File System Table name: KQ5CLUSTE0 Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_FILE_SYSTEM or KQ5CLUSTE0 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 Shared Volume Manager Table name: KQ5CLUSTE2 Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_MANAGER or KQ5CLUSTE2 v Attribute group name: Cluster Summary Table name: KQ5CLUSUM Warehouse table name: KQ5_CLUSTER_SUMMARY or KQ5CLUSUM v Attribute group name: Cluster Topology Table name: KQ5TOPOCLS Warehouse table name: KQ5_CLUSTER_TOPOLOGY or KQ5TOPOCLS 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 Table name: KQ5D50RLL 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 28 Microsoft Cluster Server agent: User's Guide

v Attribute group name: Disk Table name: KQ5D80HDD Warehouse table name: KQ5_DISK or KQ5D80HDD v Attribute group name: Disk MB Rollup Table name: KQ5D85RLL Warehouse table name: KQ5_DISK_MB_ROLLUP or KQ5D85RLL v Attribute group name: Disk PCT Rollup Table name: KQ5D90RLL 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 Warehouse table name: KQ5_MEMORY or KQ5D60MEM v Attribute group name: Memory MB Rollup Table name: KQ5D70RLL Warehouse table name: KQ5_MEMORY_MB_ROLLUP or KQ5D70RLL v Attribute group name: Memory PCT Rollup Table name: KQ5D75RLL 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 Table name: KQ5F70RLL Warehouse table name: KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP or KQ5F70RLL v Attribute group name: Network Performance Received Rollup Table name: KQ5F50RLL Warehouse table name: KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP or KQ5F50RLL Chapter 4. Attributes reference 29

v Attribute group name: Network Performance Sent Rollup Table name: KQ5F60RLL 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 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 Table name: KQ5D30RLL 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 Table name: KQ5B30LOGI Warehouse table name: KQ5_RESOURCE_GROUP_TO_PREFERRED_NODE or KQ5B30LOGI v Attribute group name: Resource Group To Resource Table name: KQ5B25LOGI 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 30 Microsoft Cluster Server agent: User's Guide

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 Table name: KQ5B35LOGI Warehouse table name: KQ5_RESOURCE_TO_POSSIBLE_OWNER or KQ5B35LOGI 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 Attributes in each attribute group Attributes in each Microsoft Cluster Server agent attribute group collect data that the agent uses for monitoring. The descriptions of the attribute groups contain the following information: Historical group Whether the attribute group is a historical type that you can roll off to a data warehouse. Attribute descriptions Information such as description, type, source, and warehouse name, as applicable, 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. The information sometimes uses C programming code syntax for if-then-else clauses to describe how an attribute is derived, for example: (CPU_Pct <0) (Memory_Pct <0)?0:1 This example means that if the CPU_Pct attribute is less than 0 or if the Memory_Pct attribute is less than 0, then the attribute is set to 0. Otherwise, the attribute is set to 1. Chapter 4. Attributes reference 31

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 eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Availability attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Application Component attribute: This attribute is a key attribute. The descriptive name of a part of the application. The source for this attribute is the agent. APPLICATION_COMPONENT or COMPONENT Name attribute 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. with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v N/A (N/A) The source for this attribute is the agent. NAME Status attribute The status of the application component. v For processes 'UP', 'DOWN', 'WARNING', or 'PROCESS_DATA_NOT_AVAILABLE': 'PROCESS_DATA_NOT_AVAILABLE' is 32 Microsoft Cluster Server agent: User's Guide

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. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v DOWN (0) v UP (1) v WARNING (2) v UNKNOWN (3) v PASSED (4) v FAILED (5) v PROCESS DATA NOT AVAILABLE (6) The source for this attribute is the agent. STATUS Full Name attribute The full name of the process including the path. with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v N/A (N/A) The source for this attribute is collected from the operating system. The data is gathered from the Windows process. The data is limited to 256 bytes. FULL_NAME or FULLNAME attribute The type of the application component. Components are processes, services, or functionality tests. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v PROCESS (0) v SERVICE (1) v FUNCTIONALITY TEST (2) The source for this attribute is the agent. TYPE Chapter 4. Attributes reference 33

Virtual Size attribute The virtual size (in MB) of the process. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - Private Bytes.. VIRTUAL_SIZE or VIRTSIZE Page Faults per Sec attribute The rate of page faults for the process measured in faults per second. This attribute only contains valid data for processes. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - Page Faults/sec.. PAGE_FAULTS_PER_SEC or PAGEFAULTS Working Set Size attribute The working set size of the process in MB. This attribute only contains valid data for processes. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - Working Set.. WORKING_SET_SIZE or WORKSET Thread Count attribute The number of threads currently allocated by this process. This attribute only contains valid data for processes. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - Thread Count.. THREAD_COUNT or THREADS PID attribute The process ID associated with the process. This attribute only contains valid data for processes. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - ID Process.. PID Percent Privileged Time attribute 34 Microsoft Cluster Server agent: User's Guide

The percentage of the available CPU time that is being used by this process for privileged operation. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - % Privileged Time.. PERCENT_PRIVILEGED_TIME or PERCPRIV Percent User Mode Time attribute The percentage of the available CPU time that is being used by this process for user mode operation. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process - % User Time.. PERCENT_USER_MODE_TIME or PERCUSER Percent Processor Time attribute The percentage of the elapsed time that this process used the processor to execute instructions. Integer (32-bit gauge) The source for this attribute is Collected from the operating system. It is gathered from the Perfmon counter Process -% Processor Time.. PERCENT_PROCESSOR_TIME or PERCPROC Command Line attribute 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. with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v N/A (N/A) The source for this attribute is Collected from the operating system. It is gathered from the process.. COMMAND_LINE or CMDLINE Functionality Test Status attribute 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. Chapter 4. Attributes reference 35

Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v SUCCESS (0) v N/A (1) v GENERAL ERROR (2) v WARNING (3) v NOT RUNNING (4) v DEPENDENT NOT RUNNING (5) v 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) The source for this attribute is the agent. FUNCTIONALITY_TEST_STATUS or FUNCSTATUS Functionality Test Message attribute The text message that corresponds to the Functionality Test Status. This is only valid for functionality tests. with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v N/A (N/A) The source for this attribute is the agent. FUNCTIONALITY_TEST_MESSAGE or FUNCMSG CAU Configuration attribute group The CAU Configuration attribute group provides information about the configuration parameters that are used by the CAU. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the CAU Configuration attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. 36 Microsoft Cluster Server agent: User's Guide

NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Resource Group Name attribute The name of the resource group in which the CAU services are added. The source for this attribute is Script data. RESOURCE_GROUP_NAME or RGN Owner Node attribute The name of the current owner node of the CAU resource group. The source for this attribute is Script data. OWNER_NODE Status attribute The status of the CAU resource group. The source for this attribute is Script data. STATUS Start Date attribute The date and time when the CAU was started. The source for this attribute is Script data. START_DATE CAU Plugin Name attribute The name of the CAU plug-in that indicates whether the CAU is configured to install Windows updates or hotfixes. The source for this attribute is Script data. Chapter 4. Attributes reference 37

CAU_PLUGIN_NAME or CPN CAU Plugin Arguments attribute The parameters that are provided to the CAU plug-in to install Windows updates or hotfixes. The source for this attribute is Script data. CAU_PLUGIN_ARGUMENTS or CPA Node Order attribute The sequence in which the cluster nodes are updated. The source for this attribute is Script data. NODE_ORDER Max Retries Per Node attribute The maximum number of retry attempts that are made per node by the update process. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MAX_RETRIES_PER_NODE or MRPN Max Failed Nodes attribute The maximum number of nodes on which updating can fail.if one more node fails, the Updating Run stops. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. MAX_FAILED_NODES or MFN Require All Nodes Online attribute 38 Microsoft Cluster Server agent: User's Guide

A Boolean value that indicates whether all the nodes are online and reachable before starting the Updating Run. The source for this attribute is Script data. REQUIRE_ALL_NODES_ONLINE or RANO Warn After attribute The duration (in minutes) after which a warning is generated if the update process is not completed. The source for this attribute is Script data. WARN_AFTER Stop After attribute The duration (in minutes) after which the Updating Run stops.the Updating Run must be completed within the specified duration that includes running of the scripts before and after the update process. The source for this attribute is Script data. STOP_AFTER Reboot Timeout Minutes attribute The time (in minutes) within which a node must restart during the Updating Run.If the restart time of the node exceeds the reboot timeout value, the Updating Run for the node is marked as failed. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. REBOOT_TIMEOUT_MINUTES or RTM Enable Firewall Rules attribute A Boolean value that indicates whether the firewall rules are enabled. The source for this attribute is Script data. ENABLE_FIREWALL_RULES or EFR Chapter 4. Attributes reference 39

Days of Week attribute The days of a week on which the Updating Run is scheduled. The source for this attribute is Script data. DAYS_OF_WEEK or DOW Weeks of Month attribute The weeks of a month on which the Updating Run is scheduled. The source for this attribute is Script data. WEEKS_OF_MONTH or WOM Interval Weeks attribute The duration (in weeks) after which the Updating Run starts. The source for this attribute is Script data. INTERVAL_WEEKS or IW PreUpdate Script attribute The name and path of the Windows PowerShell script file that is run on a node before starting the update process, and before putting the node in the maintenance mode. The source for this attribute is Script data. PREUPDATE_SCRIPT or PS PostUpdate Script attribute The name and path of the Windows PowerShell script file that is run after completing the update process on a node, and after the node is brought out of the maintenance mode. The source for this attribute is Script data. POSTUPDATE_SCRIPT or PS0 Configuration Name attribute The name of the configuration. The source for this attribute is Script data. 40 Microsoft Cluster Server agent: User's Guide

CONFIGURATION_NAME or CN CAU Last Run attribute group The CAU Last Run attribute group provides information about the last run update process and the updates. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the CAU Last Run attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute The name of the cluster. The source for this attribute is Script data. NAME Run Completion Time attribute The date and time when the last Updating Run was completed. The source for this attribute is Script data. RUN_COMPLETION_TIME or RCT Run ID attribute The ID of the last Updating Run. The source for this attribute is Script data. RUN_ID Chapter 4. Attributes reference 41

Duration attribute The completion time of the last Updating Run. The source for this attribute is Script data. DURATION Installed Updates attribute The number of updates that are installed. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. INSTALLED_UPDATES or IU Failed Updates attribute The number of updates that failed to install. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. FAILED_UPDATES or FU Canceled Updates attribute The number of updates that are canceled. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. CANCELED_UPDATES or CU 42 Microsoft Cluster Server agent: User's Guide

Update Run Status attribute The overall status of the last Updating Run. The source for this attribute is Script data. UPDATE_RUN_STATUS or URS Node Name attribute The name of the node. The source for this attribute is Script data. NODE_NAME Result attribute The result of the last Updating Run execution on the specified node. The source for this attribute is Script data. RESULT Update ID attribute The ID of the update. The source for this attribute is Script data. UPDATE_ID Update Title attribute The title of the update. The source for this attribute is Script data. UPDATE_TITLE or UT Update Timestamp attribute The timestamp when the update was installed. The source for this attribute is Script data. UPDATE_TIMESTAMP or UT0 Update attribute Chapter 4. Attributes reference 43

The description of the update. The source for this attribute is Script data. UPDATE_DESCRIPTION or UD Error Code attribute The error code of the last Updating Run. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. ERROR_CODE Cluster Domain attribute group Cluster Domain contains details of the windows domain to which the cluster belongs. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Domain attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Domain attribute Domain contains name of the windows domain to which the cluster belongs. 44 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - ROOT\CIMV2\ Win32_ComputerSystemDomain. 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.this attribute group is not available in Windows 2003 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Cluster Shared Volume Name attribute: This attribute is a key attribute. The name of the Cluster Shared Volume (CSV). The source for this attribute is Script data. NAME Volume Name attribute The device ID of the Cluster Shared Volume. The source for this attribute is Script data. VOLUMENAME Volume Offset attribute The volume offest of the Cluster Shared Volume. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Chapter 4. Attributes reference 45

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. VOLUMEOFFSET or VOLUMEOFFS CSV Resource Name attribute The name of the Cluster Shared Volume resource. The source for this attribute is Script data. CSVRESOURCENAME or C CSV Resource State attribute 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). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) The source for this attribute is Script data. CSVRESOURCESTATE or C0 CSV Node Name attribute The name of the cluster node that owns the Cluster Shared Volume. The source for this attribute is Script data. CSVNODENAME or C1 Backup State attribute 46 Microsoft Cluster Server agent: User's Guide

The backup state of the Cluster Shared Volume. The state can be None(0) or InProgress(1) Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v None (0) v InProgress (1) v NA (-1) The source for this attribute is Script data. BACKUPSTATE or BACKUPSTAT attribute The description of the Cluster Shared Volume. The source for this attribute is Script data. DESCRIPTION or DESCRIPTIO Fault State attribute The fault state of the Cluster Shared Volume. The states can be: NoFaults(0), NoDirectIO(1), NoAccess(2), and Maintenance(4) Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NoFaults (0) v NoDirectIO (1) v NoAccess (2) v Maintenance (4) v NA (-1) The source for this attribute is Script data. FAULTSTATE Cluster Shared Volume Block Redirection attribute group The Cluster Shared Volume Block Redirection attribute group provides information about the block level I/O redirection activities on the coordinator node. This attribute group is not available in Windows 2003 and 2008 cluster. Chapter 4. Attributes reference 47

Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume Block Redirection attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP IO Read Bytes attribute The amount of data (in bytes) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Read - Bytes. IO_READ_BYTES or IO_READ_BY IO Read MB attribute The amount of data (in MB) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes / (1024 * 1024)). 48 Microsoft Cluster Server agent: User's Guide

IO_READ_MB or IO_READVBR IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Read - Bytes/sec. IO_READ_BYTES_PER_SEC or IO_READ_B0 IO Read KB per sec attribute The amount of data (in KB) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_per_sec / 1024). IO_READ_KB_PER_SEC or IO_READKPS IO Reads attribute The number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Reads. IO_READS IO Reads per sec attribute Chapter 4. Attributes reference 49

The number of read operations per second that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Reads/sec. IO_READS_PER_SEC or IO_READS_P IO Write Bytes attribute The amount of data (in bytes) that is written to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Write - Bytes. IO_WRITE_BYTES or IO_WRITE_B IO Write MB attribute The amount of data (in MB) that is written to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes / (1024 * 1024)). IO_WRITE_MB or IO_WRT_VBR IO Write Bytes per sec attribute The amount of data (in bytes) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with 50 Microsoft Cluster Server agent: User's Guide

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Write - Bytes/sec. IO_WRITE_BYTES_PER_SEC or IO_WRITE_0 IO Write KB per sec attribute The amount of data (in KB) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes_per_sec / 1024). IO_WRITE_KB_PER_SEC or IO_WRITEKB IO Writes attribute The number of write operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Writes. IO_WRITES IO Writes per sec attribute The number of write operations per second that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) Chapter 4. Attributes reference 51

v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Block Redirection\*\IO Writes/sec. IO_WRITES_PER_SEC or IO_WRITES_ Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Cluster Shared Volume Cache attribute group The Cluster Shared Volume Cache attribute group provides information about the I/O activities of the CSV Cache. This attribute group is not available in Windows 2003 and 2008 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume Cache attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Cache IO Read Bytes attribute The amount of data (in bytes) that is read from the cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 52 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Cache IO Read - Bytes. CACHE_IO_READ_BYTES or CACHE_IO_R Cache IO Read MB attribute The amount of data (in MB) that is read from the cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Cache_IO_Read_Bytes / (1024 * 1024)). CACHE_IO_READ_MB or CACHE_IORK Cache IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Cache IO Read - Bytes/sec. CACHE_IO_READ_BYTES_PER_SEC or CACHE_IO_0 Cache IO Read KB per sec attribute The amount of data (in KB) that is read per second from the cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Cache_IO_Read_Bytes_per_sec / 1024). Chapter 4. Attributes reference 53

CACHE_IO_READ_KB_PER_SEC or CACHE_IRPK Cache Read attribute The number of read operations that are completed on the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Cache Read. CACHE_READ Cache Read per sec attribute The number of read operations that are completed per second on the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Cache Read/Sec. CACHE_READ_PER_SEC or CACHE_REA0 Cache Size Configured MB attribute The configured size (in MB) of the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Cache_Size_Configured_Bytes / (1024 * 1024)). CACHE_SIZE_CONFIGURED or CACHE_SIZE Cache Size Current MB attribute 54 Microsoft Cluster Server agent: User's Guide

The current size (in MB) of the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Cache_Size_Current_Bytes / (1024 * 1024)). CACHE_SIZE_CURRENT or CACHE_SIZ0 Percent Current CSV Cache Size attribute The percentage of current cache size. Real number (32-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: The source for this attribute is derived: (Cache_Size_Current / Cache_Size_Configured) * 100. PERCENT_CURRENT_CSV_CACHE_SIZE or VOLUME_PAU Cache State attribute The current state of the CSV cache. A value of 0 indicates that the cache is disabled, and a value of 1 indicates that the cache is enabled. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v Disabled (0) v Enabled (1) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Cache State. CACHE_STATE or CACHE_STAT Disk IO Read Bytes attribute The amount of data (in bytes) that is read from the CSV. Chapter 4. Attributes reference 55

Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Disk IO Read - Bytes. DISK_IO_READ_BYTES or DISK_IO_RE Disk IO Read MB attribute The amount of data (in MB) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Disk_IO_Read_Bytes / (1024 * 1024)). DISK_IO_READ_MB or DISK_IORKB Disk IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Disk IO Read - Bytes/Sec. DISK_IO_READ_BYTES_PER_SEC or DISK_IO_R0 Disk IO Read KB per sec attribute The amount of data (in KB) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with 56 Microsoft Cluster Server agent: User's Guide

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Disk_IO_Read_Bytes_per_Sec / 1024). DISK_IO_READ_KB_PER_SEC or DISK_IORKP Disk IO Reads attribute The number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Disk IO Reads. DISK_IO_READS or DISK_IO_R1 Disk IO Reads per sec attribute The number of read operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Disk IO Reads/Sec. DISK_IO_READS_PER_SEC or DISK_IO_R2 IO Read Bytes attribute The amount of data (in bytes) that is read from the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) Chapter 4. Attributes reference 57

v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\IO Read - Bytes. IO_READ_BYTES or IO_READ_BY IO Read MB attribute The amount of data (in MB) that is read from the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes / (1024 * 1024)). IO_READ_MB or IO_RDKBCS IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\IO Read - Bytes/sec. IO_READ_BYTES_PER_SEC or IO_READ_B0 IO Read KB per sec attribute The amount of data (in KB) that is read per second from the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 58 Microsoft Cluster Server agent: User's Guide

The source for this attribute is derived: (IO_Read_Bytes_per_sec / 1024). IO_READ_KB_PER_SEC or IO_READKBP IO Reads attribute The number of read operations that are completed on the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\IO Reads. IO_READS IO Reads per sec attribute The number of read operations that are completed per second on the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\IO Reads/sec. IO_READS_PER_SEC or IO_READS_P LRU Cache Size Current MB attribute The current size (in MB) of the Least Recently Used (LRU) cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (LRU_Cache_Size_Current_Bytes / (1024 * 1024)). LRU_CACHE_SIZE_CURRENT or LRU_CACHE_ Chapter 4. Attributes reference 59

LRU Cache Size Target MB attribute The size (in MB) of the target LRU cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (LRU_Cache_Size_Target_Bytes / (1024 * 1024)). LRU_CACHE_SIZE_TARGET or LRU_CACHE0 Partial Read attribute The number of data block read operations that are partially cached to the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Partial Read. PARTIAL_READ or PARTIAL_RE Partial Read per sec attribute The number of data block read operations per second that are partially cached to the CSV cache. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Cache\*\Partial Read/sec. PARTIAL_READ_PER_SEC or PARTIAL_R0 Name attribute: This attribute is a key attribute. 60 Microsoft Cluster Server agent: User's Guide

The name of the instance. The source for this attribute is PerfMon. NAME Cluster Shared Volume Coordinator attribute group The Cluster Shared Volume Coordinator Node attribute group provides information about the I/O activities on the coordinator node. This attribute group is not available in Windows 2003 and 2008 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume Coordinator attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Create File attribute The number of files that are created on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\Create File. CREATE_FILE or CREATE_FIL Create File per sec attribute The number of files that are created per second on the CSV. Chapter 4. Attributes reference 61

Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\Create File/sec. CREATE_FILE_PER_SEC or CREATE_FI0 IO Read Bytes attribute The amount of data (in bytes) that was read and redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Read - Bytes. IO_READ_BYTES or IO_READ_BY IO Read MB attribute The amount of data(in MB) that was read and redirected to the coordinator node. Integer (64-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes / (1024 * 1024)). IO_READ_MB or IO_READ_VC IO Read Bytes per sec attribute The amount of data (in bytes) that was read per second and redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with 62 Microsoft Cluster Server agent: User's Guide

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Read Bytes/sec. IO_READ_BYTES_PER_SEC or IO_READ_B0 IO Read KB per sec attribute The amount of data (in KB) that was read per second and redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_per_sec / 1024). IO_READ_KB_PER_SEC or IO_READBKP IO Reads attribute The number of read operations that are redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Reads. IO_READS IO Reads per sec attribute The number of read operations that are redirected per second to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: Chapter 4. Attributes reference 63

v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Reads/sec. IO_READS_PER_SEC or IO_READS_P IO Write Bytes per sec attribute The amount of data (in bytes) that is written per second to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Write - Bytes/sec. IO_WRITE_BYTES_PER_SEC or IO_WRITEBP IO Write KB per sec attribute The amount of data (in KB) that is written per second to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes_per_sec / 1024). IO_WRITE_KB_PER_SEC or IO_WRITEBK IO Writes attribute The number of write operations that are redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 64 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Writes. IO_WRITES IO Writes per sec attribute The number of write operations that are redirected per second to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Writes/sec. IO_WRITES_PER_SEC or IO_WRITES_ IO Writes Bytes attribute The amount of data (in bytes) that was written and redirected to the coordinator node. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\IO Writes - Bytes. IO_WRITES_BYTES or IO_WRITES0 IO Writes MB attribute The amount of data(in MB) that was written and redirected to the coordinator node. Integer (64-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Writes_Bytes / (1024 * 1024)). Chapter 4. Attributes reference 65

IO_WRITES_MB or IO_WRITEVC Metadata IO attribute The number of metadata operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\Metadata IO. METADATA_IO or METADATA_I Metadata IO per sec attribute The number of metadata operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Coordinator\*\Metadata IO/sec. METADATA_IO_PER_SEC or METADATA_0 Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Cluster Shared Volume File System attribute group The Cluster Shared Volume File System attribute group provides information about the I/O activities on the Cluster Shared Volume (CSV) file system. This attribute group is not available in Windows 2003 and 2008 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. 66 Microsoft Cluster Server agent: User's Guide

Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume File System attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Create File attribute The number of files that are created on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Create File. CREATE_FILE or CREATE_FIL Create File per sec attribute The number of files that are created per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Create File/sec. CREATE_FILE_PER_SEC or CREATE_FI0 Files Invalidated During Resume attribute Chapter 4. Attributes reference 67

The number of files that were invalidated because the CSV failed to recover the state after it was resumed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Files Invalidated - During Resume. FILES_INVALIDATED_DURING_RESUME or FILES_INVA Files Invalidated Other attribute The number of files that were invalidated because of reasons other than failure to recover the state after the CSV was resumed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Files Invalidated - Other. FILES_INVALIDATED_OTHER or FILES_INV0 Files Opened attribute The number of files that were opened on the CSV including the number of times the CSV was opened. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Files Opened. FILES_OPENED or FILES_OPEN Flushes attribute 68 Microsoft Cluster Server agent: User's Guide

The number of flushes that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Flushes. FLUSHES Flushes per sec attribute The number of flushes that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Flushes/sec. FLUSHES_PER_SEC or FLUSHES_PE IO Read Avg Queue Length attribute The average number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Read Avg. Queue Length. IO_READ_AVG_QUEUE_LENGTH or IO_READ_AV IO Read Bytes attribute The amount of data (in bytes) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with Chapter 4. Attributes reference 69

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Read Bytes. IO_READ_BYTES or IO_READ_BY IO Read MB attribute The amount of data (in MB) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes / (1024 * 1024)). IO_READ_MB or IO_READS_K IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Read Bytes/sec. IO_READ_BYTES_PER_SEC or IO_READ_B0 IO Read KB per sec attribute The amount of data (in KB) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) 70 Microsoft Cluster Server agent: User's Guide

v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_per_sec / 1024). IO_READ_KB_PER_SEC or IO_READ_BP IO Read Latency attribute The average time between sending a read request to the CSV and receiving a response. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Read Latency. IO_READ_LATENCY or IO_READ_LA IO Read Queue Length attribute The number of read operations on the CSV that are waiting to be processed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Read Queue Length. IO_READ_QUEUE_LENGTH or IO_READ_QU IO Reads attribute The number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 71

The source for this attribute is Perfmon - Cluster CSV File System\*\IO Reads. IO_READS IO Reads per sec attribute The number of read operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Reads/sec. IO_READS_PER_SEC or IO_READS_P IO Single Reads attribute The number of read operations that are completed on the CSV, and that are forwarded to the storage stack by using the original I/O Request Package (IRP). Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Single Reads. IO_SINGLE_READS or IO_SINGLE_ IO Single Reads per sec attribute The number of read operations that are completed per second on the CSV, and that are forwarded to the storage stack by using the original IRP. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 72 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV File System\*\IO Single Reads/sec. IO_SINGLE_READS_PER_SEC or IO_SINGLE0 IO Single Writes attribute The number of write operations that are completed on the CSV, and that are forwarded to the storage stack by using the original IRP. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Single Writes. IO_SINGLE_WRITES or IO_SINGLE1 IO Single Writes per sec attribute The number of write operations that are completed per second on the CSV, and that are forwarded to the storage stack by using the original IRP. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Single Writes/sec. IO_SINGLE_WRITES_PER_SEC or IO_SINGLE2 IO Split Reads attribute The number of read operations that are completed on the CSV, and that are forwarded to the storage stack by creating multiple child IRPs. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 73

The source for this attribute is Perfmon - Cluster CSV File System\*\IO Split Reads. IO_SPLIT_READS or IO_SPLIT_R IO Split Reads per sec attribute The number of read operations that are completed per second on the CSV, and that are forwarded to the storage stack by creating multiple child IRPs. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Split Reads/sec. IO_SPLIT_READS_PER_SEC or IO_SPLIT_0 IO Split Writes attribute The number of write operations that are completed on the CSV, and that are forwarded to the storage stack by creating multiple child IRPs. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Split Writes. IO_SPLIT_WRITES or IO_SPLIT_W IO Split Writes per sec attribute The number of write operations that are completed per second on the CSV, and that are forwarded to the storage stack by creating multiple child IRPs. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 74 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV File System\*\IO Split Writes/sec. IO_SPLIT_WRITES_PER_SEC or IO_SPLIT_1 IO Write Avg Queue Length attribute The average number of write operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Write Avg. Queue Length. IO_WRITE_AVG_QUEUE_LENGTH or IO_WRITE_A IO Write Bytes attribute The amount of data (in bytes) that is written to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Write Bytes. IO_WRITE_BYTES or IO_WRITE_B IO Write MB attribute The amount of data (in MB) that is written to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes / (1024 * 1024)). Chapter 4. Attributes reference 75

IO_WRITE_MB or IO_WRITS_K IO Write Bytes per sec attribute The amount of data (in bytes) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Write Bytes/sec. IO_WRITE_BYTES_PER_SEC or IO_WRITE_0 IO Write KB per sec attribute The amount of data (in KB) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes_per_sec / 1024). IO_WRITE_KB_PER_SEC or IO_WRITE_P IO Write Latency attribute The average time between sending a write request to the CSV by using a direct I/O operation and receiving a response. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Write Latency. IO_WRITE_LATENCY or IO_WRITE_L IO Write Queue Length attribute 76 Microsoft Cluster Server agent: User's Guide

The number of write operations on the CSV that are waiting to be processed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Write Queue Length. IO_WRITE_QUEUE_LENGTH or IO_WRITE_Q IO Writes attribute The number of write operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Writes. IO_WRITES IO Writes per sec attribute The number of write operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\IO Writes/sec. IO_WRITES_PER_SEC or IO_WRITES_ Metadata IO attribute The number of metadata operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with Chapter 4. Attributes reference 77

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Metadata IO. METADATA_IO or METADATA_I Metadata IO per sec attribute The number of metadata operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Metadata IO/sec. METADATA_IO_PER_SEC or METADATA_0 Read Latency attribute The average time between sending a read request to the file system and receiving a response about request completion. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Read Latency. READ_LATENCY or READ_LATEN Read Queue Length attribute The number of read operations on the CSV that are waiting to be processed. Real number (64-bit gauge) with three decimal places of precision with 78 Microsoft Cluster Server agent: User's Guide

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Read Queue Length. READ_QUEUE_LENGTH or READ_QUEUE Reads attribute The number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Reads. READS Reads per sec attribute The number of read operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Reads/sec. READS_PER_SEC or READS_PER_ Redirected Read Bytes attribute The amount of data (in bytes) that was redirected to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 79

The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Read Bytes. REDIRECTED_READ_BYTES or REDIRECTED Redirected Read KB attribute The amount of data (in KB) that was redirected to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Redirected_Read_Bytes / 1024). REDIRECTED_READ_KILOBYTES or REDIRECTD1 Redirected Read Bytes per sec attribute The amount of data (in bytes) that was redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Read Bytes/sec. REDIRECTED_READ_BYTES_PER_SEC or REDIRECTE0 Redirected Read KB per sec attribute The amount of data (in KB) that was redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Redirected_Read_Bytes_per_sec / 1024). 80 Microsoft Cluster Server agent: User's Guide

REDIRECTED_READ_KB_PER_SEC or REDIRECTEP Redirected Read Latency attribute The average time between redirecting a read request to the CSV and receiving a response. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Read Latency. REDIRECTED_READ_LATENCY or REDIRECTE1 Redirected Read Queue Length attribute The number of read operations on the CSV that are waiting to be redirected. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Read Queue Length. REDIRECTED_READ_QUEUE_LENGTH or REDIRECTE2 Redirected Reads attribute The number of read operations that are redirected to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Reads. REDIRECTED_READS or REDIRECTE3 Chapter 4. Attributes reference 81

Redirected Reads per sec attribute The number of read operations that are redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Reads/sec. REDIRECTED_READS_PER_SEC or REDIRECTE4 Redirected Reads Avg Queue Length attribute The average number of read requests that are processed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Reads Avg. Queue Length. REDIRECTED_READS_AVG_QUEUE_LENGTH or REDIRECTE5 Redirected Write Bytes attribute The amount of data (in bytes) that was written and redirected to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Write Bytes. REDIRECTED_WRITE_BYTES or REDIRECTE6 Redirected Write KB attribute The amount of data (in KB) that was written and redirected to the CSV. 82 Microsoft Cluster Server agent: User's Guide

Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Redirected_Write_Bytes / 1024). REDIRECTED_WRITE_KB or REDIRECTEW Redirected Write Bytes per sec attribute The amount of data (in bytes) that was written and redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Write Bytes/sec. REDIRECTED_WRITE_BYTES_PER_SEC or REDIRECTE7 Redirected Write KB per sec attribute The amount of data (in KB) that was written and redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (Redirected_Write_Bytes_per_sec / 1024). REDIRECTED_WRITE_KB_PER_SEC or REDIRECTWP Redirected Write Latency attribute The average time between redirecting a write request to the CSV and receiving a response. Real number (64-bit gauge) with three decimal places of precision with Chapter 4. Attributes reference 83

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Write Latency. REDIRECTED_WRITE_LATENCY or REDIRECTE8 Redirected Write Queue Length attribute The number of write operations on the CSV that are waiting to be redirected. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Write Queue Length. REDIRECTED_WRITE_QUEUE_LENGTH or REDIRECTE9 Redirected Writes attribute The number of write operations that are redirected to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Writes. REDIRECTED_WRITES or REDIRECT10 Redirected Writes per sec attribute The number of write operations that are redirected per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 84 Microsoft Cluster Server agent: User's Guide

v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Writes/sec. REDIRECTED_WRITES_PER_SEC or REDIRECT11 Redirected Writes Avg Queue Length attribute The average number of write requests that are redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Redirected Writes Avg. Queue Length. REDIRECTED_WRITES_AVG_QUEUE_LENGTH or REDIRECT12 Volume Pause Count Disk attribute The number of times the CSV was paused because of disk errors. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Volume Pause Count - Disk. VOLUME_PAUSE_COUNT_DISK or VOLUME_PAU Volume Pause Count Network attribute The number of times the CSV was paused because of network problems. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 85

The source for this attribute is Perfmon - Cluster CSV File System\*\Volume Pause Count - Network. VOLUME_PAUSE_COUNT_NETWORK or VOLUME_PA0 Volume Pause Count Other attribute The number of times the CSV was paused because of reasons other than direct I/O failure or network issues. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Volume Pause Count - Other. VOLUME_PAUSE_COUNT_OTHER or VOLUME_PA1 Volume Pause Count Total attribute The total number of times the CSV was paused. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Volume Pause Count - Total. VOLUME_PAUSE_COUNT_TOTAL or VOLUME_PA2 Volume State attribute The state of the CSV.The CSV state can be Init (0), Paused (1), Draining (2), down-level (3), or Active (4). Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v Init (0) v Paused (1) v Draining (2) v down-level (3) v Active (4) 86 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV File System\*\Volume State. VOLUME_STATE or VOLUME_STA Write Latency attribute The average time between sending a write request to the file system and receiving a response about the request completion. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Write Latency. WRITE_LATENCY or WRITE_LATE Write Queue Length attribute The number of write operations on the CSV that are waiting to be processed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Write Queue Length. WRITE_QUEUE_LENGTH or WRITE_QUEU Writes attribute The number of write operations that are completed. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 87

The source for this attribute is Perfmon - Cluster CSV File System\*\Writes. WRITES Writes per sec attribute The number of write operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV File System\*\Writes/sec. WRITES_PER_SEC or WRITES_PER Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME 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.this attribute group is not available in Windows 2003 and Windows 2012 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume IO attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. 88 Microsoft Cluster Server agent: User's Guide

TIMESTAMP IO Read Bytes attribute The number of bytes read directly from the Cluster Shared Volume since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\IO Read Bytes. IO_READ_BYTES or IO_READ_BY IO Reads attribute The number of read operations that are performed directly from the Cluster Shared Volume since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\IO Reads. IO_READS IO Write Bytes attribute The number of bytes written directly to the Cluster Shared Volume since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\IO Write Bytes. IO_WRITE_BYTES or IO_WRITE_B IO Writes attribute Chapter 4. Attributes reference 89

The number of write operations that are performed directly to the Cluster Shared Volume since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\IO Writes. IO_WRITES Metadata IO attribute The number of metadata operations that are performed against the Cluster Shared Volume since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\Metadata IO. METADATA_IO or METADATA_I Redirected Read Bytes attribute The number of read bytes that are redirected to the Cluster Shared Volume through the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\Redirected Read Bytes. REDIRECTED_READ_BYTES or REDIRECTED Redirected Reads attribute The number of read operations that are redirected to the Cluster Shared Volume through the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the 90 Microsoft Cluster Server agent: User's Guide

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\Redirected Reads. REDIRECTED_READS or REDIRECTE0 Redirected Write Bytes attribute The number of write bytes that are redirected to the Cluster Shared Volume through the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\Redirected Write Bytes. REDIRECTED_WRITE_BYTES or REDIRECTE1 Redirected Writes attribute The number of write operations that are redirected to the Cluster Shared Volume through the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Shared Volumes\*\Redirected Writes. REDIRECTED_WRITES or REDIRECTE2 Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Chapter 4. Attributes reference 91

Cluster Shared Volume Manager attribute group The Cluster Shared Volume Manager attribute group provides information about the redirected I/O activities on the CSV. This attribute group is not available in Windows 2003 and 2008 cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Shared Volume Manager attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Direct IO Failure Redirection attribute The number of times the I/O operations were redirected through the network because of direct I/O errors. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\Direct IO Failure Redirection. DIRECT_IO_FAILURE_REDIRECTION or DIRECT_IO_ Direct IO Failure Redirection per sec attribute The number of times the I/O operations were redirected per second through the network because of direct I/O errors. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) 92 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\Direct IO Failure Redirection/sec. DIRECT_IO_FAILURE_REDIRECTION_PER_SEC or DIRECT_IO0 IO Read per sec Redirected attribute The number of read operations that was redirected per second through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Read/sec - Redirected. IO_READ_PER_SEC_REDIRECTED or IO_READ_PE IO Read Bytes attribute The amount of data (in bytes) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Read - Bytes. IO_READ_BYTES or IO_READ_BY IO Read MB attribute The amount of data (in MB) that is read from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) Chapter 4. Attributes reference 93

The source for this attribute is derived: (IO_Read_Bytes / (1024 * 1024)). IO_READ_MB or IO_READS_L IO Read Bytes per sec attribute The amount of data (in bytes) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Read Bytes/sec. IO_READ_BYTES_PER_SEC or IO_READ_B0 IO Read KB per sec attribute The amount of data (in KB) that is read per second from the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_per_sec / 1024). IO_READ_KB_PER_SEC or IO_READBPS IO Read Bytes per sec Redirected attribute The amount of data (in bytes) that was read and redirected per second through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Read Bytes/sec - Redirected. 94 Microsoft Cluster Server agent: User's Guide

IO_READ_BYTES_PER_SEC_REDIRECTED or IO_READ_B1 IO Read KB per sec Redirected attribute The amount of data (in KB) that was read and redirected per second through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_per_sec_Redirected / 1024). IO_READ_KB_PER_SEC_REDIRECTED or IO_READKBR IO Read Bytes Redirected attribute The amount of data (in bytes) that was read and redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Read Bytes - Redirected. IO_READ_BYTES_REDIRECTED or IO_READ_B2 IO Read KB Redirected attribute The amount of data (in KB) that was read and redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Read_Bytes_Redirected / 1024). IO_READ_KB_REDIRECTED or IO_READR IO Reads attribute Chapter 4. Attributes reference 95

The number of read operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Reads. IO_READS IO Reads per sec attribute The number of read operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Reads/sec. IO_READS_PER_SEC or IO_READS_P IO Reads Redirected attribute The number of read operations that are redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Reads - Redirected. IO_READS_REDIRECTED or IO_READS_R IO Write Bytes attribute The amount of data (in bytes) that is written to the CSV. 96 Microsoft Cluster Server agent: User's Guide

Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Write - Bytes. IO_WRITE_BYTES or IO_WRITE_B IO Write MB attribute The amount of data (in MB) that is written to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes / (1024 * 1024)). IO_WRITE_MB or IO_WRITESL IO Write Bytes per sec attribute The amount of data (in bytes) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Write - Bytes/sec. IO_WRITE_BYTES_PER_SEC or IO_WRITEPS IO Write KB per sec attribute The amount of data (in KB) that is written per second to the CSV. Real number (64-bit gauge) with three decimal places of precision with Chapter 4. Attributes reference 97

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes_per_sec / 1024). IO_WRITE_KB_PER_SEC or IO_WRITEKP IO Write Bytes per sec Redirected attribute The amount of data (in bytes) that was written and redirected per second through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Write Bytes/sec - Redirected. IO_WRITE_BYTES_PER_SEC_REDIRECTED or IO_WRITE_1 IO Write KB per sec Redirected attribute The amount of data (in KB) that was written and redirected per second through the network. Real number (32-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: The source for this attribute is derived: (IO_Write_Bytes_per_sec_Redirected / 1024). IO_WRITE_KB_PER_SEC_REDIRECTED or IO_WRITEPR IO Write Bytes Redirected attribute The amount of data (in bytes) that was written and redirected through the network. Real number (64-bit gauge) with three decimal places of precision with 98 Microsoft Cluster Server agent: User's Guide

enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Write Bytes - Redirected. IO_WRITE_BYTES_REDIRECTED or IO_WRITE_2 IO Write KB Redirected attribute The amount of data (in KB) that was written and redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is derived: (IO_Write_Bytes_Redirected / 1024). IO_WRITE_KB_REDIRECTED or IO_WRITER IO Writes attribute The number of write operations that are completed on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Writes. IO_WRITES IO Writes per sec attribute The number of write operations that are completed per second on the CSV. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) Chapter 4. Attributes reference 99

v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Writes/sec. IO_WRITES_PER_SEC or IO_WRITES_ IO Writes per sec Redirected attribute The number of write operations that are redirected per second through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Writes/sec - Redirected. IO_WRITES_PER_SEC_REDIRECTED or IO_WRITES0 IO Writes Redirected attribute The number of write operations that are redirected through the network. Real number (64-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Value Exceeds Maximum (9223372036854775807) v Value Exceeds Minimum (-9223372036854775808) The source for this attribute is Perfmon - Cluster CSV Volume Manager\*\IO Writes - Redirected. IO_WRITES_REDIRECTED or IO_WRITES1 Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME 100 Microsoft Cluster Server agent: User's Guide

Cluster Summary attribute group The Cluster Summary attribute group provides information about all clusters in the enterprise. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Summary attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Cluster Name attribute The name of the cluster in the enterprise. The source for this attribute is Script data. CLUSTER_NAME or CLUNAME Current Host Server attribute The name of the node in the cluster. The source for this attribute is Script data. NODE_NAME or NODNAME System Information attribute The system information of a node in the cluster. The source for this attribute is Script data. SYSTEM_INFORMATION or SYSINFO Percentage Processor Used attribute The percentage of the processor that is used by the cluster. Chapter 4. Attributes reference 101

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SYSTEM_PROCESSOR_UTILIZATION or PERCPUT Precentage Processor Free attribute The percent of time the processor is idle in the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SYSTEM_PROCESSOR_IDLE or PCPUIDT Percentage Memory Used attribute The percentage of memory that is used by the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. TOTAL_MEMORY_UTILIZATION or TOULMEM Percentage Memory Free attribute The percentage of memory that is available on the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 102 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Script data. TOTAL_MEMORY_AVAILABLE or TOMEMAL Quorum Path attribute The path of the quorum files.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. The source for this attribute is Script data. QUORUM_PATH or QUOPATH Quorum Total Size attribute The size of the quorum disk in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. QUORUM_TOTAL_SIZE or QUOTOSZ Quorum Utilization attribute The size of the quorum disk that is used by the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. QUORUM_UTILIZATION or QUOUDSZ Quorum Available attribute The size of the quorum disk that is available in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 103

v NA (-1) The source for this attribute is Script data. QUORUM_AVAILABLE or QUOFRSP Percentage Quorum Used attribute The percentage of the quorum disk that is used by the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_QUORUM_USED or PRQUOUD Percentage Quorum Free attribute The percentage of quorum disk that is available for the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_QUORUM_FREE or PRQUOFR Shared Storage Available attribute The total size of shared storage (shared data disk and cluster shared volume) that is available in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. 104 Microsoft Cluster Server agent: User's Guide

SHARED_STORAGE_AVAILABLE or SHTFRSP Shared Storage Total Size attribute The total size of shared storage (shared data disk and cluster shared volume) in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. SHARED_STORAGE_TOTAL_SIZE or SHTTOSZ Shared Storage Utilization attribute The total size of shared storage (shared data disk and cluster shared volume) that is used in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. SHARED_STORAGE_UTILIZATION or SHTUDSZ Percentage Shared Storage Used attribute The percentage of the shared storage (shared data disk and cluster shared volume) that is used by the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_SHARED_STORAGE_USED or PCTSSUD Percentage Shared Storage Free attribute The percentage of shared storage (shared data disk and cluster shared volume) Chapter 4. Attributes reference 105

that is available in the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_SHARED_STORAGE_FREE or PCTSSFR No of Shared Storage attribute The total number of shared storage disks in the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. TOTAL_SHARED_STORAGE or TOSHRST Percentage Network Used attribute The percentage of maximum network that is used by the Cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. NETWORK_UTILIZATION or NETWKUD Domain attribute The domain name of the cluster. The source for this attribute is Script data. DOMAIN or CDOMAIN 106 Microsoft Cluster Server agent: User's Guide

Cluster Topology attribute group The Cluster Topology attribute group provides information about the cluster topology that includes nodes in the cluster, resource groups that are managed by each node, and resources in each resource group. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Cluster Topology attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Node Name attribute The name of the node. The source for this attribute is Script data. NODE_NAME or TOPNAME Node ID attribute: This attribute is a key attribute. The ID of the node. The source for this attribute is Script data. NODE_ID or TOPNOID Node attribute The type of node, such as node, resource group, or resource. The source for this attribute is Script data. NODE_TYPE or TOPTYPE Node Status attribute Chapter 4. Attributes reference 107

The current status of the node, such as online, offline, or failed. No data is displayed for this attribute when the value for the Node attribute is cluster because the WMI class does not provide the cluster status. The source for this attribute is Script data. NODE_STATUS or TOPSTAT Connect To Node attribute The node that is the parent of the current node. The source for this attribute is Script data. CONNECT_TO_NODE or TOPCONO Connection attribute The connection type of the node. The source for this attribute is Script data. CONNECTION_TYPE or TOPCOTY 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Configuration attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute 108 Microsoft Cluster Server agent: User's Guide

The name of this cluster. The source for this attribute is WMI - root\mscluster\mscluster_cluster Name. NAME Max Number Nodes attribute The maximum number of nodes that can participate in this cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\mscluster\mscluster_cluster MaxNumberOfNodes. MAX_NUMBER_NODES or MNN Default Network Role attribute Specifies the role that the cluster automatically assigns to any newly discovered or created network: None(0) InternalUse(1) ClientAccess(2) InternalAndClient(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v None (0) v InternalUse (1) v ClientAccess (2) v InternalAndClient (3) The source for this attribute is WMI - root\mscluster\mscluster_cluster DefaultNetworkRole. DEFAULT_NETWORK_ROLE or DNR attribute The cluster description specified at cluster creation and modifiable by the cluster administrator. The source for this attribute is WMI - root\mscluster\mscluster_cluster. DESCRIPTION or D Chapter 4. Attributes reference 109

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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the CPU Interrupts Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of interrupts per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of interrupts per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. 110 Microsoft Cluster Server agent: User's Guide

MINIMUM Average attribute This is the average of the interrupts per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the interrupts per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the interrupts per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD CPU per Node attribute group Provides the processor metrics from each processor of each node in the cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the CPU per Node attribute group: Chapter 4. Attributes reference 111

Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name of the node. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name Name. NAME Processor attribute: This attribute is a key attribute. The processor name. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name Name. PROCESSOR Interrupts attribute The average number of hardware interrupts that the processor is receiving and servicing per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ 112 Microsoft Cluster Server agent: User's Guide

Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name InterruptsPersec. INTERRUPTS Percent Interrupt Time attribute The percentage of time that the processor spent receiving and servicing hardware interrupts during the sample interval. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name PercentInterruptTime. PERCENT_INTERRUPT_TIME or PIT Percent Idle Time attribute The percentage of time during the sample interval that the processor was idle. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name PercentIdleTime. PERCENT_IDLE_TIME or PIT0 Percent Processor Time attribute The percentage of time that the processor is executing a non-idle thread. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name PercentProcessorTime. Chapter 4. Attributes reference 113

PERCENT_PROCESSOR_TIME or PPT Percent User Time attribute The percentage of non-idle processor time spent in user mode. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name PercentUserTime. PERCENT_USER_TIME or PUT Percent Privileged Time attribute The percentage of non-idle processor time spent in privileged mode. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOs_Processor from root\mscluster\ MSCluster_Node :Name PercentPrivilegedTime. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the CPU per Node Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE 114 Microsoft Cluster Server agent: User's Guide

Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum percent processor time. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum percent processor time. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average percent processor time. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Chapter 4. Attributes reference 115

Total attribute This is the sum of the percent processor time. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the percent processor time. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Degradation Risk attribute group Is a characterization of the risk that application performance will degrade in the event of a node failure. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Degradation Risk attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. 116 Microsoft Cluster Server agent: User's Guide

TIMESTAMP Node Min Capacity attribute This is the online node with the minimum processing capacity. The source for this attribute is Script data. NODE_MIN_CAPACITY or NMC Min Capacity attribute This is the minimum processing capacity.it is calculated as the sum of the megahertz rating of each processor on the node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MIN_CAPACITY or MC Node Max Capacity attribute This is the node with the maximum processing capacity. The source for this attribute is Script data. NODE_MAX_CAPACITY or NMC0 Max Capacity attribute This is the maximum processing capacity.it is calculated as the sum of the megahertz rating of each processor on the node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MAX_CAPACITY or MC0 Node Min Util attribute This is the online node with the minimum processor utilization. Chapter 4. Attributes reference 117

The source for this attribute is Script data. NODE_MIN_UTIL or NMU Min Util attribute This is the minimum processor utilization.it is calculated as the capacity (megahertz) of the node multiplied by the percent processor utilization. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MIN_UTIL Node Max Util attribute This is the node with the maximum processor utilization. The source for this attribute is Script data. NODE_MAX_UTIL or NMU0 Max Util attribute This is the maximum processor utilization.it is calculated as the capacity (megahertz) of the node multiplied by the percent processor utilization. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MAX_UTIL Total Capacity attribute This is the total processing capacity of the cluster, assuming all nodes are active. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 118 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Script data. TOTAL_CAPACITY or TC Current Capacity attribute This is the current processing capacity of the cluster.it is the sum of the processing capacity of active nodes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. CURRENT_CAPACITY or CC Degraded Capacity attribute This is the projected processing capacity based on the current capacity of the cluster if the highest capacity node failed. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. DEGRADED_CAPACITY or DC Total Util attribute This is the sum of processing capacity utilization for all active nodes in the cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. Chapter 4. Attributes reference 119

TOTAL_UTIL Uniform Commitment attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. UNIFORM_COMMITMENT or UC Unitary Commitment attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. UNITARY_COMMITMENT or UC0 Disk attribute group Provides disk metrics collected from each node in the cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Disk attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE 120 Microsoft Cluster Server agent: User's Guide

Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name of Node attribute: This attribute is a key attribute. The name of the node. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name Name. NAME_OF_NODE or NON Disk attribute: This attribute is a key attribute. The name of the disk. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name Name. DISK Percent Free Space attribute The ratio of the free space available on the logical disk unit to the total usable space provided by the selected logical disk drive. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name PercentFreeSpace. PERCENT_FREE_SPACE or PFS Percent Disk Write Time attribute The percentage of elapsed time that the selected disk drive is busy servicing write requests. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Chapter 4. Attributes reference 121

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name PercentDiskWriteTime. PERCENT_DISK_WRITE_TIME or PDWT Percent Disk Read Time attribute The percentage of elapsed time that the selected disk drive is busy servicing read requests. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name PercentDiskReadTime. PERCENT_DISK_READ_TIME or PDRT FreeMegabytes attribute The unallocated space on the disk drive in megabytes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name FreeMegabytes. FREEMEGABYTES or F Disk Write Bytes attribute The rate at which bytes are transferred to the disk during write operations per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the 122 Microsoft Cluster Server agent: User's Guide

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name DiskWriteBytesPersec. DISK_WRITE_BYTES or DWB Disk Writes attribute The rate of write operations on the disk per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name DiskWritesPersec. DISK_WRITES or DW Disk Read Bytes attribute The rate at which bytes are transferred from the disk during read operations per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name DiskReadBytesPersec. DISK_READ_BYTES or DRB Disk Reads attribute The rate of read operations on the disk per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 123

The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name DiskReadsPersec. DISK_READS Current Disk Queue attribute The number of requests outstanding on the disk at the time the performance data is collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name CurrentDiskQueueLength. CURRENT_DISK_QUEUE or CDQ Disk Transfers attribute The rate of read and write operations on the disk per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfDisk_LogicalDisk from root\mscluster\ MSCluster_Node :Name DiskTransfersPersec. DISK_TRANSFERS or DT Disk Used Percent attribute The amount of disk space used as a percent. Integer (32-bit gauge) The source for this attribute is derived: 100 - Percent_Free_Space. DISK_USED_PERCENT or DUP 124 Microsoft Cluster Server agent: User's Guide

Disk Write MB attribute The rate at which megabytes are transferred to the disk during write operations per second. Integer (32-bit gauge) The source for this attribute is derived: Disk_Write_Bytes / 1048576. DISK_WRITE_MB or DWM Disk Read MB attribute The rate at which megabytes are transferred from the disk during read operations per second. Integer (32-bit gauge) The source for this attribute is derived: Disk_Read_Bytes / 1048576. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Disk MB Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 125

The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute 126 Microsoft Cluster Server agent: User's Guide

This is the standard deviation of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Disk PCT Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. Chapter 4. Attributes reference 127

MAXIMUM Minimum attribute This is the minimum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 128 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Enterprise Cluster Summary attribute group Provides the data that is contained in the Cluster Summary attribute group for all the monitored Microsoft Cluster Server 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Enterprise Cluster Summary attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Cluster Name attribute The name of the cluster in the enterprise. The source for this attribute is Script data. CLUSTER_NAME or CLUNAME Current Host Server attribute The name of the node in the cluster. The source for this attribute is Script data. NODE_NAME or NODNAME Chapter 4. Attributes reference 129

System Information attribute The system information of a node in the cluster. The source for this attribute is Script data. SYSTEM_INFORMATION or SYSINFO Percentage Processor Used attribute The percentage of the processor that is used by the cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SYSTEM_PROCESSOR_UTILIZATION or PERCPUT Precentage Processor Free attribute The percent of time the processor is idle in the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SYSTEM_PROCESSOR_IDLE or PCPUIDT Percentage Memory Used attribute The percentage of memory that is used by the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. TOTAL_MEMORY_UTILIZATION or TOULMEM 130 Microsoft Cluster Server agent: User's Guide

Percentage Memory Free attribute The percentage of memory that is available on the active cluster node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. TOTAL_MEMORY_AVAILABLE or TOMEMAL Quorum Path attribute The path of the quorum files.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. The source for this attribute is Script data. QUORUM_PATH or QUOPATH Quorum Total Size attribute The size of the quorum disk in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. QUORUM_TOTAL_SIZE or QUOTOSZ Quorum Utilization attribute The size of the quorum disk that is used by the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) Chapter 4. Attributes reference 131

The source for this attribute is Script data. QUORUM_UTILIZATION or QUOUDSZ Quorum Available attribute The size of the quorum disk that is available in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. QUORUM_AVAILABLE or QUOFRSP Percentage Quorum Used attribute The percentage of the quorum disk that is used by the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_QUORUM_USED or PRQUOUD Percentage Quorum Free attribute The percentage of quorum disk that is available for the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_QUORUM_FREE or PRQUOFR Shared Storage Available attribute 132 Microsoft Cluster Server agent: User's Guide

The total size of shared storage (shared data disk and cluster shared volume) that is available in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. SHARED_STORAGE_AVAILABLE or SHTFRSP Shared Storage Total Size attribute The total size of shared storage (shared data disk and cluster shared volume) in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. SHARED_STORAGE_TOTAL_SIZE or SHTTOSZ Shared Storage Utilization attribute The total size of shared storage (shared data disk and cluster shared volume) that is used in the cluster in megabytes.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. SHARED_STORAGE_UTILIZATION or SHTUDSZ Percentage Shared Storage Used attribute The percentage of the shared storage (shared data disk and cluster shared volume) that is used by the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Chapter 4. Attributes reference 133

Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_SHARED_STORAGE_USED or PCTSSUD Percentage Shared Storage Free attribute The percentage of shared storage (shared data disk and cluster shared volume) that is available in the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. PERCENTAGE_SHARED_STORAGE_FREE or PCTSSFR No of Shared Storage attribute The total number of shared storage disks in the cluster.this attribute is not available in Windows 2003 cluster.on the portal, the value is displayed as NA for Windows 2003 cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. TOTAL_SHARED_STORAGE or TOSHRST Percentage Network Used attribute The percentage of maximum network that is used by the Cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. 134 Microsoft Cluster Server agent: User's Guide

NETWORK_UTILIZATION or NETWKUD Domain attribute The domain name of the cluster. The source for this attribute is Script data. DOMAIN or CDOMAIN Event Log attribute group The Event Log attribute group contains any event log entries that pertain to this application. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Event Log attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Log Name attribute The name of the event log - Application, System, Security or an application-specific log LOG_NAME or LOGNAME Event attribute The event source defined by the application EVENT_SOURCE or EVTSOURCE Event attribute Event - Error(0), Warning(1), Informational(2), Audit_Success(3), Audit_Failure(4), Unknown(5) Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Error (0) v Warning (1) v Informational (2) v Audit Success (3) v Audit Failure (4) Chapter 4. Attributes reference 135

v Unknown (5) EVENT_TYPE or EVTTYPE Event ID attribute The ID of the event Integer (32-bit counter) EVENT_ID or EVTID Event Category attribute The Category of the event with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v None (None) EVENT_CATEGORY or EVTCATEG Message attribute The event message MESSAGE Time Generated attribute The time the event was generated Timestamp TIME_GENERATED or TIMESTAMP Event Level attribute The Level value specified in the event. This is an expanded version of the Event_ field only available on Windows 2008 or later with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Not Available (-1) EVENT_LEVEL or EVTLEVEL Event Keywords attribute 136 Microsoft Cluster Server agent: User's Guide

A comma-separated list of the keywords specified in the event. This field only available on Windows 2008 or later with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Not Available (-1) EVENT_KEYWORDS or EVTKEYWDS Event API Version attribute The version of the Event Log API used to retrieve this event Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NT Event Log (1) v Windows Event Log (2) EVENT_API_VERSION or EVTAPIVER 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Global Update Messages attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Database Update Messages attribute Chapter 4. Attributes reference 137

The number of updated database messages from the cluster that are sent over the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Global Update Manager Messages\\Database Update Messages. DATABASE_UPDATE_MESSAGES or DATABASE_U Database Update Messages Delta attribute The number of new updated messages in the cluster database that are sent over the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Global Update Manager Messages\\Database Update Messages Delta. DATABASE_UPDATE_MESSAGES_DELTA or DATABASE_0 Update Messages attribute The number of updated messages from the cluster that are sent over the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Global Update Manager Messages\\Update Messages. UPDATE_MESSAGES or UPDATE_MES Update Messages Delta attribute The number of updated messages from the cluster that are sent over the network since the data was collected. 138 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Global Update Manager Messages\\Update Messages Delta. UPDATE_MESSAGES_DELTA or UPDATE_ME0 Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Memory attribute group Provides memory metrics collected from each node in the cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Memory attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name of Node attribute: This attribute is a key attribute. The name of the node. Chapter 4. Attributes reference 139

The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name Name. NAME_OF_NODE or NON Memory Module attribute The name of the memory module.usually a NULL string. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name Name. MEMORY_MODULE or MM Available Memory MB attribute The amount of available memory in megabytes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name AvailableMBytes. AVAILABLE_MEMORY_MB or AMM Percent Committed Bytes In Use attribute The ratio committed to commit limit. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PercentCommittedBytesInUse. PERCENT_COMMITTED_BYTES_IN_USE or PCBIU Cache Bytes attribute The number of bytes currently being used by the file system cache. 140 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name CacheBytes. CACHE_BYTES or CB0 Cache Bytes Peak attribute The maximum number of cache bytes after the system was last restarted. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name CacheBytesPeak. CACHE_BYTES_PEAK or CBP Cache Faults attribute 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). Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name CacheFaultsPerSec. CACHE_FAULTS or CF Page Faults attribute The number of page faults per second. Chapter 4. Attributes reference 141

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PageFaultsPersec. PAGE_FAULTS or PF Page Reads attribute The number of page reads per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PageReadsPersec. PAGE_READS Page Writes attribute The number of page writes per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PageWritesPersec. PAGE_WRITES or PW Pages Input attribute The number of pages read from disk to resolve hard page faults per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the 142 Microsoft Cluster Server agent: User's Guide

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PagesInputPersec. PAGES_INPUT or PI Pages Output attribute The number of pages written to disk to free up space in physical memory per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PagesOutputPersec. PAGES_OUTPUT or PO Pool Paged Bytes attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_PerfOS_Memory from root\mscluster\ MSCluster_Node :Name PoolPagedBytes. POOL_PAGED_BYTES or PPB Commit Limit MB attribute The amount of virtual memory that can be committed without having to extend the paging file(s) in megabytes. Chapter 4. Attributes reference 143

Integer (32-bit gauge) The source for this attribute is derived: Commit_Limit / 1048576. COMMIT_LIMIT_MB or CLM Committed MB attribute The amount of committed virtual memory in megabytes. Integer (32-bit gauge) The source for this attribute is derived: Committed_Bytes / 1048576. COMMITTED_MB or CM Cache MB attribute The number of megabytes currently being used by the file system cache. Integer (32-bit gauge) The source for this attribute is derived: Cache_Bytes / 1048576. CACHE_MB Cache Peak MB attribute The maximum number of megabytes in the cache after the system was last restarted. Integer (32-bit gauge) The source for this attribute is derived: Cache_Bytes_Peak / 1048576. CACHE_PEAK_MB or CPM Pool Paged MB attribute 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. Integer (32-bit gauge) The source for this attribute is derived: Pool_Paged_Bytes / 1048576. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Memory MB Rollup attribute group: Node attribute: This attribute is a key attribute. 144 Microsoft Cluster Server agent: User's Guide

The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 145

The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Memory PCT Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. 146 Microsoft Cluster Server agent: User's Guide

NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. Chapter 4. Attributes reference 147

AVERAGE Total attribute This is the sum of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the MRR Messages attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. 148 Microsoft Cluster Server agent: User's Guide

The source for this attribute is the agent. TIMESTAMP Messages Outstanding attribute The number of MRR messages from the cluster that are waiting to be sent or received in the cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Multicast Request-Response Messages\\Messages Outstanding. MESSAGES_OUTSTANDING or MESSAGES_O Messages Sent attribute The number of MRR messages from the cluster that are sent over the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Multicast Request-Response Messages\\Messages Sent. MESSAGES_SENT or MESSAGES_S Messages Sent Delta attribute The number of new MRR messages from the cluster that are sent over the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 149

The source for this attribute is Perfmon - Cluster Multicast Request-Response Messages\\Messages Sent Delta. MESSAGES_SENT_DELTA or MESSAGES_0 Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Network Interfaces attribute group Provides the configuration details of all the network interfaces in this cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Interfaces attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. Provides the clustering service-generated name for the network interface. The source for this attribute is Script data. NAME State Raw attribute State of the network interface: Unknown(-1) Unavailable(0) Down(1) Unreachable(2) Up(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise 150 Microsoft Cluster Server agent: User's Guide

The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Unavailable (0) v Down (1) v Unreachable (2) v Up (3) The source for this attribute is Script data. STATE_RAW Address attribute Provides the primary network address(ipv4 or IPV6) that the node uses for the network interface. The source for this attribute is Script data. ADDRESS System Name attribute The scoping nodes system's name. The source for this attribute is Script data. SYSTEM_NAME or SN Adapter attribute Provides the name that is used to uniquely identify the network interface in the cluster. The source for this attribute is Script data. ADAPTER Network Name attribute The network name to which the network interface is connected. The source for this attribute is Script data. NETWORK_NAME or NN Device ID attribute Provides an address or other identifying information that uniquely identifies the network interface. Chapter 4. Attributes reference 151

The source for this attribute is Script data. DEVICE_ID attribute The Network Interface's description. The source for this attribute is Script data. DESCRIPTION or D State attribute The current raw state of the network interface mapped to a percent: Up(100) Down(0 - for all other mapped states). DEFAULT(2) The source for this attribute is Script data. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Interfaces State Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the network interface state information. 152 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the network interface state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the network interface state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the network interface state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 153

The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the network interface state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Network Performance attribute group Provides network performance data collected from each node in the cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Performance attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name of Node attribute: This attribute is a key attribute. The name of the node. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name Name. 154 Microsoft Cluster Server agent: User's Guide

NAME_OF_NODE or NON Network Interface attribute: This attribute is a key attribute. The name of the network interface. The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name Name. NETWORK_INTERFACE or NI Bytes Received attribute The rate at which bytes are received on the interface, including framing characters per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name BytesReceivedPersec. BYTES_RECEIVED or BR Bytes Sent attribute The rate at which bytes are sent on the interface, including framing characters per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name BytesSentPersec. BYTES_SENT Current Bandwidth attribute The estimate of the current bandwidth of the interface in gigabits per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Chapter 4. Attributes reference 155

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name CurrentBandwidth. CURRENT_BANDWIDTH or CB Output Queue Length attribute The length of the output packet queue in packets. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name OutputQueueLength. OUTPUT_QUEUE_LENGTH or OQL Packets Outbound Discarded attribute The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent transmission. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsOutboundDiscarded. PACKETS_OUTBOUND_DISCARDED or POD Packets Outbound Errors attribute The number of outbound packets that could not be transmitted because of errors. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 156 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsOutboundErrors. PACKETS_OUTBOUND_ERRORS or POE Packets attribute The rate at which packets are sent and received on the network interface per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsPersec. PACKETS Packets Received Discarded attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsReceivedDiscarded. PACKETS_RECEIVED_DISCARDED or PRD Packets Received Errors attribute The number of inbound packets that contained errors preventing delivery to a higher-layer protocol. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 157

The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsReceivedErrors. PACKETS_RECEIVED_ERRORS or PRE Packets Received attribute The number of packets that are received on the network interface per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsReceivedPersec. PACKETS_RECEIVED or PR Packets Sent attribute The number of packets that are sent on the network interface per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name PacketsSentPersec. PACKETS_SENT or PS Bytes Total attribute The number of bytes sent and received on the interface, including framing characters per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 158 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - root\cimv2\ Win32_PerfFormattedData_Tcpip_NetworkInterface from root\mscluster\ MSCluster_Node :Name BytesTotalPersec. BYTES_TOTAL or BT Received MB attribute The number of megabytes received on the interface, including framing characters per second. Integer (32-bit gauge) The source for this attribute is derived: Bytes_Received / 1048576. RECEIVED_MB or RM Sent MB attribute The number of megabytes sent on the interface, including framing characters per second. Integer (32-bit gauge) The source for this attribute is derived: Bytes_Sent / 1048576. SENT_MB Current Bandwidth MB attribute The estimate of the interface's current bandwidth in megabytes per second. Integer (32-bit gauge) The source for this attribute is derived: Current_Bandwidth / 8388608. CURRENT_BANDWIDTH_MB or CBM Total MB attribute The number of megabytes sent and received on the interface, including framing characters per second. Integer (32-bit gauge) The source for this attribute is derived: Bytes_Total / 1048576. TOTAL_MB Current Bandwidth Gbps attribute The estimate of the interface's current bandwidth in Gigabites per second. Real number (32-bit gauge) with two decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: Chapter 4. Attributes reference 159

The source for this attribute is derived: Current_Bandwidth/1000000000. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Performance Packets Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the packets per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the packets per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the 160 Microsoft Cluster Server agent: User's Guide

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the packets per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the packets per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the packets per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. Chapter 4. Attributes reference 161

STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Performance Received Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the bytes received per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the bytes received per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 162 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the bytes received per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the bytes received per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the bytes received per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Chapter 4. Attributes reference 163

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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Network Performance Sent Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the bytes sent per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the bytes sent per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. 164 Microsoft Cluster Server agent: User's Guide

MINIMUM Average attribute This is the average of the bytes sent per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the bytes sent per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the bytes sent per second. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Chapter 4. Attributes reference 165

Attribute descriptions The following list contains information about each attribute in the Network Reconnections attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Normal Message Queue Length attribute The number of normal messages that are waiting to be sent. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Network Reconnections\*\ Normal Message Queue Length. NORMAL_MESSAGE_QUEUE_LENGTH or NORMAL_MES Reconnect Count attribute The number of reconnections between the nodes of the cluster. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Network Reconnections\*\ Reconnect Count. RECONNECT_COUNT or RECONNECT_ Unacknowledged Message Queue Length attribute 166 Microsoft Cluster Server agent: User's Guide

The number of messages that are not acknowledged. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Network Reconnections\*\ Unacknowledged Message Queue Length. UNACKNOWLEDGED_MESSAGE_QUEUE_LENGTH or UNACKNOWLE Urgent Message Queue Length attribute The number of urgent messages that are waiting to be sent. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Network Reconnections\*\ Urgent Message Queue Length. URGENT_MESSAGE_QUEUE_LENGTH or URGENT_MES Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Networks attribute group Provides details of the network configuration. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Networks attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. Chapter 4. Attributes reference 167

NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name of this cluster network. The source for this attribute is Script data. NAME State Raw attribute The state of the cluster network: Unknown(-1) Unavailable(0) Down(1) Unreachable(2) Up(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Unavailable (0) v Down (1) v Unreachable (2) v Up (3) The source for this attribute is Script data. STATE_RAW Address attribute The address (IPV4 or IPV6) for the entire network or subnet. The source for this attribute is Script data. ADDRESS AddressMask attribute Provides the mask that distinguishes the network and host portions of an address.incase of IPV6, prefix length will be displyed. 168 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Script data. ADDRESSMASK or A Role attribute The role the cluster network plays: None(0) InternalUse(1) ClientAccess(2) InternalAndClient(3) Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v None (0) v InternalUse (1) v ClientAccess (2) v Internal And Client (3) The source for this attribute is Script data. ROLE attribute The network's description. The source for this attribute is Script data. DESCRIPTION or D State attribute The current raw state of the cluster network mapped to a percent: Up(100) Down(0 - for all other mapped states). DEFAULT(2) The source for this attribute is Script data. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Networks Messages attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. Chapter 4. Attributes reference 169

The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name of a node in the cluster. The source for this attribute is Script data. NAME or NONAME KB Received attribute The number of message KB that are received on the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. BYTES_RECEIVED or BYTEREC KB Received Delta attribute The number of new message KB that are received on the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. BYTES_RECEIVED_DELTA or BYTERED KB Sent attribute 170 Microsoft Cluster Server agent: User's Guide

The number of message KB that are sent on the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. BYTES_SENT or BYTESNT KB Sent Delta attribute The number of new message KB that are sent on the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. BYTES_SENT_DELTA or BYTESND Messages Received attribute The number of cluster messages received on the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MESSAGES_RECEIVED or MESSREC Messages Received Delta attribute The number of new cluster messages received on the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Chapter 4. Attributes reference 171

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MESSAGES_RECEIVED_DELTA or MESSRED Messages Sent attribute The number of cluster messages sent on the network since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. MESSAGES_SENT or MESSSNT Messages Sent Delta attribute The number of new cluster messages sent on the network since the data was collected. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. 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. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Networks Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. 172 Microsoft Cluster Server agent: User's Guide

The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the network state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the network state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the network state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 173

The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the network state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the network state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Node To Active Group attribute group Provides the node to active group details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Node To Active Group attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute 174 Microsoft Cluster Server agent: User's Guide

The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Current RG Node attribute The name used to identify this node in the cluster. The source for this attribute is WMI - nullname. CURRENT_RG_NODE or CRN RG Node Changed attribute The resource group's owning node changed DEFAULT(2) The source for this attribute is WMI - nullname. RG_NODE_CHANGED or RNC Previous RG Node attribute The node that previously owned the resource group. DEFAULT(2) The source for this attribute is WMI - nullname. PREVIOUS_RG_NODE or PRN State of Node attribute The current state of the node: Unknown(-1) Up(0) Down(1) Paused(2) Joining(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Up (0) v Down (1) v Paused (2) v Joining (3) The source for this attribute is WMI - nullstate. STATE_OF_NODE or SON of Node attribute Chapter 4. Attributes reference 175

The node's description. The source for this attribute is WMI - null. DESCRIPTION_OF_NODE or DON Name of Group attribute: This attribute is a key attribute. The name of this resource group. The source for this attribute is WMI - nullname. NAME_OF_GROUP or NOG State of Group attribute The current state of this resource group: Unknown (-1) Online(0) OffLine(1) Failed(2) PartialOnline(3) Pending(4). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v On Line (0) v Off Line (1) v Failed (2) v Partial Online (3) v Pending (4) The source for this attribute is WMI - nullstate. STATE_OF_GROUP or SOG of Group attribute The resource group's description. The source for this attribute is WMI - null. DESCRIPTION_OF_GROUP or DOG Node Group Names attribute: This attribute is a key attribute. Combined node name and resource group names for event display. The source for this attribute is derived: Name_of_Group+ "@" + Current_RG_Node. 176 Microsoft Cluster Server agent: User's Guide

NODE_GROUP_NAMES or NGN Nodes attribute group Provides the detailed node information. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Nodes attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name used to identify this node in the cluster. The source for this attribute is WMI - root\mscluster\mscluster_node Name. NAME State Raw attribute The current state of the node: Unknown(-1) Up(0) Down(1) Paused(2) Joining(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Up (0) v Down (1) v Paused (2) v Joining (3) The source for this attribute is WMI - root\mscluster\mscluster_node State. STATE_RAW Major Version attribute Chapter 4. Attributes reference 177

Specifies the integer component of the version of the operating system installed on the node. DisplayNumeric The source for this attribute is WMI - root\mscluster\mscluster_node MajorVersion. MAJOR_VERSION or MV Minor Version attribute Specifies the decimal component of the version of the operating system installed on the node. DisplayNumeric The source for this attribute is WMI - root\mscluster\mscluster_node MinorVersion. MINOR_VERSION or MV0 Build Number attribute Specifies the build number of the version of the operating system installed on a node. DisplayNumeric The source for this attribute is WMI - root\mscluster\mscluster_node BuildNumber. BUILD_NUMBER or BN Node Highest Version attribute Specifies the highest version of the cluster service with which the node can join or communicate. DisplayNumeric The source for this attribute is WMI - root\mscluster\mscluster_node NodeHighestVersion. NODE_HIGHEST_VERSION or NHV NodeLowestVersion attribute Specifies the lowest version of the cluster service with which the node can join or communicate. DisplayNumeric The source for this attribute is WMI - root\mscluster\mscluster_node NodeLowestVersion. NODELOWESTVERSION or N attribute 178 Microsoft Cluster Server agent: User's Guide

The node's description. The source for this attribute is WMI - root\mscluster\mscluster_node. DESCRIPTION or D State attribute The current raw state of the node mapped to a percent: Up(100) Down(0 - for all other mapped states). DEFAULT(2) The source for this attribute is WMI - root\mscluster\mscluster_node State. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Nodes State Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the node state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 179

The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the node state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the node state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the node state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the node state information. 180 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Performance Object Status attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Query Name attribute: This attribute is a key attribute. The name of the attribute group. QUERY_NAME or ATTRGRP Object Name attribute The name of the performance object. Chapter 4. Attributes reference 181

OBJECT_NAME or OBJNAME Object attribute The type of the performance object. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v WMI (0) v PERFMON (1) v WMI ASSOCIATION GROUP (2) v JMX (3) v SNMP (4) v SHELL COMMAND (5) v JOINED GROUPS (6) v CIMOM (7) v CUSTOM (8) v ROLLUP DATA (9) v WMI REMOTE DATA (10) v LOG FILE (11) v JDBC (12) v CONFIG DISCOVERY (13) v NT EVENT LOG (14) v FILTER (15) v SNMP EVENT (16) v PING (17) v DIRECTOR DATA (18) v DIRECTOR EVENT (19) v SSH REMOTE SHELL COMMAND (20) OBJECT_TYPE or OBJTYPE Object Status attribute The status of the performance object. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v ACTIVE (0) v INACTIVE (1) OBJECT_STATUS or OBJSTTS Error Code attribute The error code that is associated with the query. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise 182 Microsoft Cluster Server agent: User's Guide

The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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 COM LIBRARY INIT FAILURE (6) v SECURITY INIT FAILURE (7) v PROXY SECURITY FAILURE (9) v NO INSTANCES RETURNED (10) v 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 CANNOT FIND ROLLUP ATTRIBUTE (22) v FILE OFFLINE (23) v NO HOSTNAME (24) v MISSING LIBRARY (25) v ATTRIBUTE COUNT MISMATCH (26) v ATTRIBUTE NAME MISMATCH (27) v COMMON DATA PROVIDER NOT STARTED (28) v CALLBACK REGISTRATION ERROR (29) v MDL LOAD ERROR (30) v AUTHENTICATION FAILED (31) v CANNOT RESOLVE HOST NAME (32) v SUBNODE UNAVAILABLE (33) v SUBNODE NOT FOUND IN CONFIG (34) v ATTRIBUTE ERROR (35) v CLASSPATH ERROR (36) v CONNECTION FAILURE (37) v FILTER SYNTAX ERROR (38) v FILE NAME MISSING (39) v SQL QUERY ERROR (40) v SQL FILTER QUERY ERROR (41) v SQL DB QUERY ERROR (42) v SQL DB FILTER QUERY ERROR (43) v PORT OPEN FAILED (44) v ACCESS DENIED (45) v TIMEOUT (46) v NOT IMPLEMENTED (47) v REQUESTED A BAD VALUE (48) v RESPONSE TOO BIG (49) v GENERAL RESPONSE ERROR (50) v SCRIPT NONZERO RETURN (51) v SCRIPT NOT FOUND (52) v SCRIPT LAUNCH ERROR (53) v CONF FILE DOES NOT EXIST (54) Chapter 4. Attributes reference 183

v CONF FILE ACCESS DENIED (55) v INVALID CONF FILE (56) v EIF INITIALIZATION FAILED (57) v CANNOT OPEN FORMAT FILE (58) v FORMAT FILE SYNTAX ERROR (59) v REMOTE HOST UNAVAILABLE (60) v EVENT LOG DOES NOT EXIST (61) v PING FILE DOES NOT EXIST (62) v NO PING DEVICE FILES (63) v PING DEVICE LIST FILE MISSING (64) v SNMP MISSING PASSWORD (65) v DISABLED (66) v URLS FILE NOT FOUND (67) v XML PARSE ERROR (68) v NOT INITIALIZED (69) v ICMP SOCKETS FAILED (70) v DUPLICATE CONF FILE (71) ERROR_CODE or ERRCODE Last Collection Start attribute The most recent time a data collection of this group started. Timestamp with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NOT COLLECTED (0691231190000000) v NOT COLLECTED (0000000000000001) LAST_COLLECTION_START or COLSTRT Last Collection Finished attribute The most recent time a data collection of this group finished. Timestamp with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NOT COLLECTED (0691231190000000) v NOT COLLECTED (0000000000000001) LAST_COLLECTION_FINISHED or COLFINI Last Collection Duration attribute The duration of the most recently completed data collection of this group in seconds. Real number (32-bit counter) with two decimal places of precision 184 Microsoft Cluster Server agent: User's Guide

LAST_COLLECTION_DURATION or COLDURA Average Collection Duration attribute The average duration of all data collections of this group in seconds. Real number (32-bit counter) with two decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NO DATA (-100) AVERAGE_COLLECTION_DURATION or COLAVGD Refresh Interval attribute The interval at which this group is refreshed in seconds. Integer (32-bit counter) REFRESH_INTERVAL or REFRINT Number of Collections attribute The number of times this group has been collected since agent start. Integer (32-bit counter) NUMBER_OF_COLLECTIONS or NUMCOLL Cache Hits attribute The number of times an external data request for this group was satisfied from the cache. Integer (32-bit counter) CACHE_HITS or CACHEHT Cache Misses attribute The number of times an external data request for this group was not available in the cache. Integer (32-bit counter) CACHE_MISSES or CACHEMS Cache Hit Percent attribute The percentage of external data requests for this group that were satisfied from the cache. Real number (32-bit counter) with two decimal places of precision CACHE_HIT_PERCENT or CACHPCT Intervals Skipped attribute Chapter 4. Attributes reference 185

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. Integer (32-bit counter) INTERVALS_SKIPPED or INTSKIP Quorum Configuration attribute group Provides important details about quorum disks that can help you find the configuration details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Quorum Configuration attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maintenance File attribute The location of a maintenance file. The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterMaintenanceFile. MAINTENANCE_FILE or MAINTENANC Quorum Log File Size attribute The maximum size of the quorum log file set, in bytes Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NA (0) 186 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterQuorumLogFileSize. QUORUM_LOG_FILE_SIZE or QUORUMLOGF Quorum Arbitration Time Maximum attribute The maximum time (in seconds) that is necessary to decide the quorum owner node. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NA (0) The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterQuorumArbitrationTimeMax. QUORUM_ARBITRATION_TIME_MAX or QUORUMARB0 Quorum Arbitration Time Minimum attribute The minimum time (in seconds) that is necessary to decide the quorum owner node. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NA (0) The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterQuorumArbitrationTimeMin. QUORUM_ARBITRATION_TIME_MIN or QUORUMARB1 Quorum attribute The current quorum type that is configured for the Cluster Server. The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterQuorum. QUORUM_TYPE or QUORUMTYPE Quorum Path attribute The path where quorum files are maintained. The source for this attribute is WMI - ROOT\MSCluster\ MSCluster_ClusterQuorumPath. Chapter 4. Attributes reference 187

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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Control Manager attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Groups Online attribute The number of online resource groups of the cluster on the node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resource Control Manager\\Groups Online. GROUPS_ONLINE or GROUPS_ONL RHS Processes attribute The number of running Resource Host Subsystem processes (rhs.exe). Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are 188 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Perfmon - Cluster Resource Control Manager\\RHS Processes. RHS_PROCESSES or RHS_PROCES RHS Restarts attribute The number of times the Resource Host Subsystem process restarts (rhs.exe) restarts since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resource Control Manager\\RHS Restarts. RHS_RESTARTS or RHS_RESTAR Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Group Moves attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. Chapter 4. Attributes reference 189

The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the information. 190 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD Resource Group To Preferred Node attribute group Provides resource group to preferred node details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Group To Preferred Node attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Group Name attribute: This attribute is a key attribute. Chapter 4. Attributes reference 191

The name of this resource group. The source for this attribute is WMI - nullname. GROUP_NAME Group State attribute The current state of this resource group: Unknown(-1) Online(0) OffLine(1) Failed(2) PartialOnline(3) Pending(4). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v On Line (0) v Off Line (1) v Failed (2) v Partial Online (3) v Pending (4) The source for this attribute is WMI - nullstate. GROUP_STATE or GS Group attribute The resource group's description. The source for this attribute is WMI - null. GROUP_DESCRIPTION or GD Name of Node attribute: This attribute is a key attribute. The name used to identify this node in the cluster. The source for this attribute is WMI - nullname. NAME_OF_NODE or NON State of Node attribute The current state of the node: Unknown(-1) Up(0) Down(1) Paused(2) Joining(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Up (0) 192 Microsoft Cluster Server agent: User's Guide

v Down (1) v Paused (2) v Joining (3) The source for this attribute is WMI - nullstate. STATE_OF_NODE or SON of Node attribute The node's description. The source for this attribute is WMI - null. DESCRIPTION_OF_NODE or DON Resource Group To Resource attribute group Provides the resource group to resource details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Group To Resource attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Group Name attribute: This attribute is a key attribute. The name of this resource group. The source for this attribute is WMI - nullname. GROUP_NAME Group State attribute Chapter 4. Attributes reference 193

The current state of this resource group: Unknown(-1) Online(0) OffLine(1) Failed(2) PartialOnline(3) Pending(4). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v On Line (0) v Off Line (1) v Failed (2) v Partial Online (3) v Pending (4) The source for this attribute is WMI - nullstate. GROUP_STATE or GS Group attribute The resource group's description. The source for this attribute is WMI - null. GROUP_DESCRIPTION or GD Resource Name attribute: This attribute is a key attribute. The name of this cluster resource. The source for this attribute is WMI - nullname. RESOURCE_NAME or RN Resource State attribute 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). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) 194 Microsoft Cluster Server agent: User's Guide

The source for this attribute is WMI - nullstate. RESOURCE_STATE or RS Resource attribute The resource's description. The source for this attribute is WMI - null. RESOURCE_DESCRIPTION or RD Resource Groups attribute group Provides the detailed description of the resource groups on the cluster. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Groups attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name of this resource group. The source for this attribute is Script data. NAME State Raw attribute The current state of this resource group: Unknown (-1) Online(0) OffLine(1) Failed(2) PartialOnline(3) Pending(4). Chapter 4. Attributes reference 195

Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v On Line (0) v Off Line (1) v Failed (2) v Partial Online (3) v Pending (4) The source for this attribute is Script data. STATE_RAW Persistent State attribute Specifies whether the resource group should be brought online or left offline when the cluster service is started. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v False (0) v True (-1) The source for this attribute is Script data. PERSISTENT_STATE or PS Auto FailBack attribute 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). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Prevent (0) v Allow (1) The source for this attribute is Script data. AUTO_FAILBACK_TYPE or AFT Failover Period attribute Specifies a number of hours during which a maximum number of failover attempts, specified by the failover threshold, can occur. 196 Microsoft Cluster Server agent: User's Guide

Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. FAILOVER_PERIOD or FP Failover Threshold attribute Specifies the maximum number of failover attempts that can be made on a group within a time interval defined by the failover period. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. FAILOVER_THRESHOLD or FT Failback Window Start attribute 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). Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. FAILBACK_WINDOW_START or FWS Failback Window End attribute 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). Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) Chapter 4. Attributes reference 197

The source for this attribute is Script data. FAILBACK_WINDOW_END or FWE attribute The resource group description. The source for this attribute is Script data. DESCRIPTION or D State attribute The current raw state of the cluster resource mapped to a percent: Up(100) Partial Online(50) Down(0 - for all other mapped states). DEFAULT(2) The source for this attribute is Script data. STATE 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource Groups State Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the resource group state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the 198 Microsoft Cluster Server agent: User's Guide

Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the resource group state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the resource group state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the resource group state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. Chapter 4. Attributes reference 199

TOTAL Standard Deviation attribute This is the standard deviation of the resource group state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource To Dependent Resource attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Resource Name attribute: This attribute is a key attribute. The name of the cluster resource. The source for this attribute is WMI - nullname. RESOURCE_NAME or RN Resource State attribute 200 Microsoft Cluster Server agent: User's Guide

The current state of the ascendant resource. The states can be: Unknown, Inherited, Initializing, Online, Offline, Failed, Pending, OnlinePending, and OfflinePending. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) The source for this attribute is WMI - nullstate. RESOURCE_STATE or RS Resource attribute The description of the resource. The source for this attribute is WMI - null. RESOURCE_DESCRIPTION or RD Dependent Resource Name attribute: This attribute is a key attribute. The name of the dependent resource. The source for this attribute is WMI - nullname. DEPENDENT_RESOURCE_NAME or DRN Dependent Resource State attribute The current state of the dependent resource. The states can be: Unknown, Inherited, Initializing, Online, Offline, Failed, Pending, OnlinePending and OfflinePending. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Inherited (0) v Initializing (1) v Online (2) v Offline (3) Chapter 4. Attributes reference 201

v Failed (4) v Pending (128) v OnlinePending (129) v OfflinePending (130) The source for this attribute is WMI - nullstate. DEPENDENT_RESOURCE_STATE or DRS Dependent Resource attribute The description of the dependent resource. The source for this attribute is WMI - null. DEPENDENT_RESOURCE_DESCRIPTION or DRD Resource To Possible Owner attribute group Provides the resource to possible owner details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resource To Possible Owner attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Resource Name attribute: This attribute is a key attribute. The name of this cluster resource. The source for this attribute is WMI - nullname. RESOURCE_NAME or RN Resource State attribute 202 Microsoft Cluster Server agent: User's Guide

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). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) The source for this attribute is WMI - nullstate. RESOURCE_STATE or RS Resource attribute The resource's description. The source for this attribute is WMI - null. RESOURCE_DESCRIPTION or RD Name of Node attribute: This attribute is a key attribute. The name used to identify this node in the cluster. The source for this attribute is WMI - nullname. NAME_OF_NODE or NON State of Node attribute The current state of the node: Unknown(-1) Up(0) Down(1) Paused(2) Joining(3). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v Unknown (-1) v Up (0) v Down (1) v Paused (2) v Joining (3) Chapter 4. Attributes reference 203

The source for this attribute is WMI - nullstate. STATE_OF_NODE or SON of Node attribute The node's description. The source for this attribute is WMI - null. DESCRIPTION_OF_NODE or DON Resources attribute group Provides the cluster resource details. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resources attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Name attribute: This attribute is a key attribute. The name of this cluster resource. The source for this attribute is Script data. NAME State Raw attribute 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). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise 204 Microsoft Cluster Server agent: User's Guide

The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) The source for this attribute is Script data. STATE_RAW attribute The type specifies the display name of the resource. The source for this attribute is Script data. TYPE Core Resource attribute If True, then the resource is essential to the cluster and cannot be deleted. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v False (0) v True (-1) The source for this attribute is Script data. CORE_RESOURCE or CR Persistent State attribute Specifies whether the resource should be brought online or left offline when the cluster service is started. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v False (0) v True (-1) Chapter 4. Attributes reference 205

The source for this attribute is Script data. PERSISTENT_STATE or PS Delete Requires All Nodes attribute If True, then the resource cannot be deleted unless all nodes are active. Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v False (0) v True (-1) The source for this attribute is Script data. DELETE_REQUIRES_ALL_NODES or DRAN Is Alive Poll Interval attribute Provides the recommended interval in milliseconds at which the cluster service should poll the resource to determine if it is operational. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. IS_ALIVE_POLL_INTERVAL or IAPI Looks Alive Poll Interval attribute Provides the recommended interval in milliseconds at which the cluster service should poll the resource to determine if it appears operational. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. LOOKS_ALIVE_POLL_INTERVAL or LAPI Pending Timeout attribute 206 Microsoft Cluster Server agent: User's Guide

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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. PENDING_TIMEOUT or PT Restart Action attribute Describes the action to be taken by the cluster service if the resource fails: DoNotRestart(0) RestartNoNotify(1) RestartNotify(2). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v DoNotRestart (0) v RestartNoNotify (1) v RestartNotify (2) The source for this attribute is Script data. RESTART_ACTION or RA Restart Period attribute Defines an interval of time in milliseconds, during which a specified number of restart attempts can be made on a nonresponsive resource. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. RESTART_PERIOD or RP Restart Threshold attribute 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. Chapter 4. Attributes reference 207

Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. RESTART_THRESHOLD or RT Retry Period On Failure attribute 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. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NA (-1) The source for this attribute is Script data. RETRY_PERIOD_ON_FAILURE or RPOF attribute The resource's description. The source for this attribute is Script data. DESCRIPTION or D State attribute The current raw state of the cluster resource mapped to a percent: Up(100) Down(0 - for all other mapped states). DEFAULT(2) The source for this attribute is Script data. STATE Monitored Resource attribute The name of the resource that is added in a cluster. 208 Microsoft Cluster Server agent: User's Guide

The source for this attribute is Script data. MONITORED_RESOURCE or MONRESOUR 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resources State Rollup attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Maximum attribute This is the maximum value of the resource state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullmax. MAXIMUM Minimum attribute This is the minimum value of the resource state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are Chapter 4. Attributes reference 209

The source for this attribute is WMI - nullmin. MINIMUM Average attribute This is the average of the resource state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullave. AVERAGE Total attribute This is the sum of the resource state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nulltot. TOTAL Standard Deviation attribute This is the standard deviation of the resource state information. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is WMI - nullstddev. STANDARD_DEVIATION or SD 210 Microsoft Cluster Server agent: User's Guide

Resources Summary attribute group The Resources Summary attribute group provides information about cluster resources grouped by the resource type. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Resources Summary attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Resource Controls attribute The total number of resource controls of various cluster resource types. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resource Controls. RESOURCE_CONTROLS or RESOURCE_C Resource Failure attribute The number of resources that failed since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resource Failure. Chapter 4. Attributes reference 211

RESOURCE_FAILURE or RESOURCE_F Resource Failure Access Violation attribute The number of resources that failed because of access violation since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resource Failure Access Violation. RESOURCE_FAILURE_ACCESS_VIOLATION or RESOURCE_0 Resource Failure Deadlock attribute The number of resources that failed because of a deadlock since the service was started. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resource Failure Deadlock. RESOURCE_FAILURE_DEADLOCK or RESOURCE_1 Resources Online attribute The number of online resources on the active node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resources Online. RESOURCES_ONLINE or RESOURCES_ Resource Controls attribute 212 Microsoft Cluster Server agent: User's Guide

The number of resource type controls that are handled by the resource Dynamic Link Library (DLL) on the node. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Perfmon - Cluster Resources\*\Resource Controls. RESOURCE_TYPE_CONTROLS or RESOURCE_T Name attribute: This attribute is a key attribute. The name of the instance. The source for this attribute is PerfMon. NAME Shared Storage Summary attribute group The Shared Storage Summary attribute group provides information about all cluster shared volume and shared disks. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Shared Storage Summary attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Cluster Name attribute The name of the cluster. Chapter 4. Attributes reference 213

The source for this attribute is Script data. CLUSTER_NAME or CLUNAME Node Name attribute The name of the node in the cluster. The source for this attribute is Script data. NODE_NAME or NODNAME Shared Storage Path attribute: This attribute is a key attribute. The path of the cluster shared storage. The source for this attribute is Script data. SHARED_STORAGE_PATH or SHTPATH Shared Storage Total Size attribute The total size of the cluster shared storage in megabytes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SHARED_STORAGE_TOTAL_SIZE or SHTTOSZ Shared Storage Available attribute The size of the shared storage that is avaialble in the cluster in megabytes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SHARED_STORAGE_AVAILABLE or SHTFRSC Shared Storage Utilization attribute 214 Microsoft Cluster Server agent: User's Guide

The size of shared storage that is used in the cluster in megabytes. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. SHARED_STORAGE_UTILIZATION or SHTUDSP Shared Storage State attribute The current state of the Cluster Shared Storage resource. The states can be: Unknown(-1), Inherited(0), Initializing(1), Online(2), Offline(3), Failed(4), Pending(128), OnlinePending(129), and OfflinePending(130). Integer with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: 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) The source for this attribute is Script data. SHARED_STORAGE_STATE or SSS Percentage Shared Storage Utilization attribute The percentage of shared storage that is used in the cluster. Real number (32-bit gauge) with three decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: The source for this attribute is Script data. PERCENTAGE_SHARED_STORAGE_UTILIZATION or SHTFPER Chapter 4. Attributes reference 215

Structural Risk attribute group A characterization of the risk of resource failure given the current available nodes. Historical group This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Structural Risk attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Lowest Health Resource attribute This is the resource with the minimum health rating.the first one will be used in case of a tie. The source for this attribute is Script data. LOWEST_HEALTH_RESOURCE or LHR Current Health attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. CURRENT_HEALTH or CH Health Less A Node attribute This is the health rating, if another node were to be lost from resource. 216 Microsoft Cluster Server agent: User's Guide

Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. HEALTH_LESS_A_NODE or HLAN Fewest Nodes Resource attribute This is the resource with the least number of active nodes supporting it.the first one will be used in case of a tie. The source for this attribute is Script data. FEWEST_NODES_RESOURCE or FNR Available Nodes attribute This is the number of nodes currently available to support the resource. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. AVAILABLE_NODES or AN Less A Node attribute 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. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. LESS_A_NODE or LAN Chapter 4. Attributes reference 217

Less A Node Percent attribute This is the available nodes less one divided by the configured nodes expressed as a percentage. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are The source for this attribute is Script data. 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 This attribute group is eligible for use with Tivoli Data Warehouse. Attribute descriptions The following list contains information about each attribute in the Thread Pool Status attribute group: Node attribute: This attribute is a key attribute. The managed system name of the agent. The source for this attribute is the agent. NODE Timestamp attribute The local time at the agent when the data was collected. The source for this attribute is the agent. TIMESTAMP Thread Pool Size attribute The number of threads currently existing in the thread pool. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) 218 Microsoft Cluster Server agent: User's Guide

THREAD_POOL_SIZE or THPSIZE Thread Pool Max Size attribute The maximum number of threads allowed to exist in the thread pool. Integer (32-bit numeric property) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_MAX_SIZE or TPMAXSZ Thread Pool Active Threads attribute The number of threads in the thread pool currently active doing work. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_ACTIVE_THREADS or TPACTTH Thread Pool Avg Active Threads attribute The average number of threads in the thread pool simultaneously active doing work. Real number (32-bit gauge) with two decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NO DATA (-1) v NO DATA (-100) THREAD_POOL_AVG_ACTIVE_THREADS or TPAVGAT Thread Pool Min Active Threads attribute The smallest number of threads in the thread pool that have simultaneously been active doing work. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) Chapter 4. Attributes reference 219

THREAD_POOL_MIN_ACTIVE_THREADS or TPMINAT Thread Pool Max Active Threads attribute The peak number of threads in the thread pool that have simultaneously been active doing work. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_MAX_ACTIVE_THREADS or TPMAXAT Thread Pool Queue Length attribute The number of jobs currently waiting in the thread pool queue. Integer (32-bit gauge) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_QUEUE_LENGTH or TPQLGTH Thread Pool Avg Queue Length attribute The average length of the thread pool queue during this run. Real number (32-bit gauge) with two decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NO DATA (-1) v NO DATA (-100) THREAD_POOL_AVG_QUEUE_LENGTH or TPAVGQL Thread Pool Min Queue Length attribute The minimum length the thread pool queue has reached. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) 220 Microsoft Cluster Server agent: User's Guide

THREAD_POOL_MIN_QUEUE_LENGTH or TPMINQL Thread Pool Max Queue Length attribute The peak length the thread pool queue has reached. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_MAX_QUEUE_LENGTH or TPMAXQL Thread Pool Avg Job Wait attribute The average time a job spends waiting on the thread pool queue in seconds. Real number (32-bit gauge) with two decimal places of precision with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are shown in parentheses. The following values are defined: v NO DATA (-1) v NO DATA (-100) THREAD_POOL_AVG_JOB_WAIT or TPAVJBW Thread Pool Total Jobs attribute The number of jobs completed by all threads in the pool since agent start. Integer (32-bit counter) with enumerated values. The strings are displayed in the Tivoli Enterprise The warehouse and queries return the values that are v NO DATA (-1) v NO DATA (-100) THREAD_POOL_TOTAL_JOBS or TPTJOBS 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 by the historical data in each attribute group that is collecting historical data. Required disk storage is an important factor when you are defining data collection rules and your strategy for historical data collection. The Capacity planning for historical data table provides the following information, which is required to calculate disk space for this monitoring agent: Chapter 4. Attributes reference 221

Table 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 for the monitoring agent on page 27. Attribute group Name of the attribute group that is used to create the table in the warehouse database if it is short enough to fit in the table naming constraints of the database that is being used for the warehouse. The attribute group name listed here corresponds to the Warehouse table name in Attribute groups for the monitoring agent on page 27. Bytes per row (agent) Estimate of the record length for each row or instance that is written to the agent disk for historical data collection. This estimate can be used for agent disk space planning purposes. Database bytes per row (warehouse) Estimate of the record length for detailed records that are written to the warehouse database, if the attribute group is configured to be written to the warehouse. Detailed records are records that have been uploaded from the agent for long-term historical data collection. This estimate can be used for warehouse disk-space planning purposes. Aggregate bytes per row (warehouse) Estimate of the record length for aggregate records that are 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 rows of data that you plan to collect. An attribute group can have single or multiple rows of data, depending on the application environment that is being monitored. For example, if your attribute group monitors each processor in your computer and you have a dual processor computer, the number of rows is two. Table 5. Capacity planning for historical data logged by the Microsoft Cluster Server agent Database bytes per row (warehouse) Table Attribute group Bytes per row (agent) KQ5AVAIL KQ5_AVAILABILITY 3272 3296 3606 KQ5CAUCONF KQ5_CAU_CONFIGURATION 1248 1264 1301 KQ5CAULRUN KQ5_CAU_LAST_RUN 3192 3207 3244 KQ5WIN32CO KQ5_CLUSTER_DOMAIN 140 137 174 KQ5CLUSCSV KQ5_CLUSTER_SHARED_VOLUME 412 417 571 KQ5CLUSTE7 272 377 1026 KQ5_CLUSTER_SHARED_VOLUME_BLOCK_ REDIRECTION KQ5CLUSTE6 KQ5_CLUSTER_SHARED_VOLUME_CACHE 376 603 1915 KQ5CLUSTE4 KQ5_CLUSTER_SHARED_VOLUME_ 304 429 1266 COORDINATOR KQ5CLUSTE0 KQ5_CLUSTER_SHARED_VOLUME_FILE_ 700 1283 4635 SYSTEM KQ5CLUCSVP KQ5_CLUSTER_SHARED_VOLUME_IO 212 218 390 KQ5CLUSTE2 KQ5_CLUSTER_SHARED_VOLUME_MANAGER 380 615 1978 KQ5CLUSUM KQ5_CLUSTER_SUMMARY 460 477 1138 KQ5TOPOCLS KQ5_CLUSTER_TOPOLOGY 460 462 499 KQ5B05PHYS KQ5_CONFIGURATION 284 284 360 Aggregate bytes per row (warehouse) 222 Microsoft Cluster Server agent: User's Guide

Table 5. Capacity planning for historical data logged by the Microsoft Cluster Server agent (continued) Database bytes per row (warehouse) Table Attribute group Bytes per row (agent) 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 2446 2455 2507 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 96 97 329 KQ5_NETWORK_INTERFACES_STATE_ ROLLUP KQ5F40NET KQ5_NETWORK_PERFORMANCE 344 371 1083 KQ5F70RLL KQ5_NETWORK_PERFORMANCE_PACKETS_ 96 97 329 ROLLUP KQ5F50RLL KQ5_NETWORK_PERFORMANCE_RECEIVED_ 96 97 329 ROLLUP KQ5F60RLL KQ5_NETWORK_PERFORMANCE_SENT_ 96 97 329 ROLLUP 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 524 536 612 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 Aggregate bytes per row (warehouse) Chapter 4. Attributes reference 223

Table 5. Capacity planning for historical data logged by the Microsoft Cluster Server agent (continued) Database bytes per row (warehouse) Table Attribute group Bytes per row (agent) KQ5B30LOGI KQ5_RESOURCE_GROUP_TO_PREFERRED_ 484 486 523 NODE KQ5B25LOGI KQ5_RESOURCE_GROUP_TO_RESOURCE 484 486 523 KQ5B25RTDR 484 486 523 KQ5_RESOURCE_TO_DEPENDENT_ RESOURCE KQ5B35LOGI KQ5_RESOURCE_TO_POSSIBLE_OWNER 484 486 523 KQ5CSVSUMM KQ5_SHARED_STORAGE_SUMMARY 288 304 509 KQ5G30RLL KQ5_STRUCTURAL_RISK 296 299 531 KQ5THPLST KQ5_THREAD_POOL_STATUS 124 168 550 Aggregate bytes per row (warehouse) For more information about historical data collection, see Managing historical data in the IBM Tivoli Monitoring Administrator's Guide. 224 Microsoft Cluster Server agent: User's Guide

Chapter 5. Situations reference 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 the Tivoli Enterprise Portal by using the Situation Editor or from the command-line interface using the tacmd commands for situations. You can manage private situations in the private configuration XML file. About situations The monitoring agents that you use to monitor your system environment include a set of predefined situations that you can use as-is. You can also 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 IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. You can 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 Situation editor initially lists the situations associated with the Navigator item that you selected. When you click a situation name or create a situation, a panel opens with the following tabs: Formula Formula describing the condition being tested. Distribution List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed. All 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. EIF Until Customize forwarding of the event to an Event Integration Facility receiver. (Available when the Tivoli Enterprise Monitoring Server is configured to forward events.) Options to close the event after a period of time, or when another situation becomes true. Additional information about situations The 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 and information about each individual situation for this monitoring agent, see Predefined situations. Predefined situations The monitoring agent contains predefined situations, which are organized by Navigator item. v Microsoft Cluster Server Not applicable v Availability Copyright IBM Corp. 2008, 2013 225

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 KQ5_MSCS_StorageSpace_Warning KQ5_MSCS_StorageSpace_Critical 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 KQ5_MSCS_Resource_Offline KQ5_MSCS_Resource_Pending KQ5_MSCS_Resource_Pending_On KQ5_MSCS_Resource_Pending_Off KQ5_MSCS_Resource_Unknown 226 Microsoft Cluster Server agent: User's Guide

KQ5_MSCS_Resource_Initializing KQ5_MSCS_Resource_Inherited v Structural and Degradation Risk Not applicable Situation descriptions Each situation description provides information about the situation that you can use to monitor the condition of systems in your network. The situation descriptions provide the following information: Information about the conditions that the situation tests. Formula Syntax that contains one or more logical expressions that describe 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 elapse 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 one means that 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, when another situation is true, or whichever occurs first if both are selected. Microsoft Cluster Server Navigator item No predefined situations are included for this Navigator item. Availability Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_Process_Down situation Microsoft Cluster Server process is not running on this node. The situation is evaluated for each distinct value of the COMPONENT attribute. Formula *IF *SCAN KQ5_AVAILABILITY.Name *EQ ClusSvc.exe *AND *VALUE KQ5_AVAILABILITY.Status *EQ DOWN *AND *SCAN KQ5_AVAILABILITY.Application_Component *EQ MSCS See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Chapter 5. Situations reference 227

Distribution This situation is automatically distributed to instances of this agent. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_WMI_Obj_Not_Available situation 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 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 5. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. Cluster Dashboard Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_PMemory_Free_Warn situation 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 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 15 minutes 228 Microsoft Cluster Server agent: User's Guide

Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_PMemory_Free_Crit situation Physical memory available is less than 6.00%. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CLUSTER_SUMMARY.Total_Memory_Available *LT 6 See Attributes in each attribute group on page 31 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 5 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_PNW_Utilization_Warn situation Network usage is between 40.00% and 65.00%. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CLUSTER_SUMMARY.Network_Utilization *GT 40 *AND *VALUE KQ5_CLUSTER_SUMMARY.Network_Utilization *LT 65 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_PNW_Utilization_Crit situation Network usage is more than 64.00%. Chapter 5. Situations reference 229

The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CLUSTER_SUMMARY.Network_Utilization *GT 64 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 10 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_PCPU_Utilization_Warn situation CPU usage is between 59.00% to 90.00%. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *GT 59 *AND *VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *LT 90 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 5 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_PCPU_Utilization_Crit situation System CPU usage is more than 89.00%. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CLUSTER_SUMMARY.System_Processor_Utilization *GT 89 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No 230 Microsoft Cluster Server agent: User's Guide

Sampling interval 5 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_StorageSpace_Warning situation The shared disk space is low because it is 75% used. The situation will be evaluated for each distinct value of Shared_Storage_Path. Formula *IF *VALUE KQ5_SHARED_STORAGE_SUMMARY.Percentage_Shared_Storage_Utilization *GE 75 *AND *VALUE KQ5_SHARED_STORAGE_SUMMARY.Percentage_Shared_Storage_Utilization *LT 95 See Attributes in each attribute group on page 31 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 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_StorageSpace_Critical situation The shared disk space is low because it is 95% used. The situation will be evaluated for each distinct value of Shared_Storage_Path. Formula *IF *VALUE KQ5_SHARED_STORAGE_SUMMARY.Percentage_Shared_Storage_Utilization *GE 95 See Attributes in each attribute group on page 31 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 10 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. Chapter 5. Situations reference 231

Configuration Navigator item No predefined situations are included for this Navigator item. Event Log Navigator item No predefined situations are included for this Navigator item. Network Interfaces Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_InterfaceStateUnknown situation The state of the Network Interface is Unknown. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ -1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_InterfaceStateUnavail situation The state of the Network Interface is Unavailable. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ 0 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_InterfaceStateDown situation 232 Microsoft Cluster Server agent: User's Guide

The state of the Network Interface is Down. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ 1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_InterfaceStateUnreach situation The state of the Network Interface is Unreachable. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORK_INTERFACES.State_Raw *EQ 2 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. Networks Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_Network_StateUnknown situation The state of the network is Unknown. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORKS.State_Raw *EQ -1 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Chapter 5. Situations reference 233

Distribution This situation is automatically distributed to instances of this agent. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Network_StateUnavail situation The state of the network is Unavailable. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORKS.State_Raw *EQ 0 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Network_StateDown situation The state of the network is Down. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORKS.State_Raw *EQ 1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning 234 Microsoft Cluster Server agent: User's Guide

Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Network_StateUnreach situation The state of the network is Unreachable. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NETWORKS.State_Raw *EQ 2 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. Nodes Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_Node_Unknown situation The last node operation was unsuccessful (unknown state). The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NODES.State_Raw *EQ -1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Node_Paused situation The node is in a paused state. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NODES.State_Raw *EQ 2 Chapter 5. Situations reference 235

See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Node_Down situation The node is inactive. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_NODES.State_Raw *EQ 1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Cluster_Unbalanced situation The cluster CPU distribution is out of balance. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_CPU_PER_NODE_ROLLUP.Standard_Deviation *GT 20 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. 236 Microsoft Cluster Server agent: User's Guide

Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_QrmDiskSpace_Warning situation 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 See Attributes in each attribute group on page 31 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 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_QrmDiskSpace_Critical situation 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 See Attributes in each attribute group on page 31 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 10 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. Resource Groups Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_RG_Failed situation The resource group has failed to come online. Chapter 5. Situations reference 237

The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ 2 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Critical Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_RG_Offline situation The resource group is offline. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ 1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_RG_PartiallyOnLine situation The resource group is partially online. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ 3 See Attributes in each attribute group on page 31 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 238 Microsoft Cluster Server agent: User's Guide

Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_RG_Unknown situation The resource group is unknown The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCE_GROUPS.State_Raw *EQ -1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Node_Changed situation 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 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is available for distribution. Run at startup No Sampling interval 30 seconds Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. Resources Navigator item The situation descriptions are organized by the Navigator item to which the situations are relevant. KQ5_MSCS_Resource_Failed situation Chapter 5. Situations reference 239

The resource has failed to come online. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 4 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Warning Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Offline situation The resource is offline. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 3 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Pending situation The resource is pending state change. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 128 See Attributes in each attribute group on page 31 for descriptions of the attributes in this formula. Distribution This situation is automatically distributed to instances of this agent. Run at startup Yes 240 Microsoft Cluster Server agent: User's Guide

Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Pending_On situation The resource is pending state change to online. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 129 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Pending_Off situation The resource is pending state change to offline. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 130 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Unknown situation The resource is in an unknown state. Chapter 5. Situations reference 241

The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ -1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Initializing situation The resource is initializing. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 1 See Attributes in each attribute group on page 31 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 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. KQ5_MSCS_Resource_Inherited situation The resource is in an inherited state. The situation is evaluated for each distinct value of the NAME attribute. Formula *IF *VALUE KQ5_RESOURCES.State_Raw *EQ 0 See Attributes in each attribute group on page 31 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 242 Microsoft Cluster Server agent: User's Guide

Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Error conditions Informational Clearing conditions The situation clears when the condition becomes false. Structural and Degradation Risk Navigator item No predefined situations are included for this Navigator item. Chapter 5. Situations reference 243

244 Microsoft Cluster Server agent: User's Guide

Chapter 6. Take Action commands reference Take Action commands can be run from the portal client or included in a situation or a policy. About Take Action commands 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. In advanced automation, policies are used to take 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 that are prescribed by the feedback. A basic Take Action command shows the return code of the operation in a message box that is displayed after the action is completed or in a log file. After you close this window, no further information is available for this action. Additional information about Take Action commands For more information about working with Take Action commands, see Take Action commands in 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 Predefined Take Action commands and the information for each individual command. Predefined Take Action commands Not all agents have predefined Take Action commands. But you can create Take Action commands for any agent. This monitoring agent contains the following Take Action commands: v Bring Resource Group online v Bring Resource online v Delete Resource Group v Move Resource Group v Pause Node v Resume Node v Take Resource Group offline v Take Resource offline Take Action command descriptions Each Take Action command description provides information you can use to decide whether to run the Take Action command or whether to include the Take Action command in a situation or a policy. The descriptions of the Take Action commands provide the following information: Copyright IBM Corp. 2008, 2013 245

Actions the command performs on the system to which it is sent, and the permissions required for the Take Action command to function. Return codes Information that the Take Action command returns. Bring Resource Group online action 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: BRING_RESOURCE_GROUP_ONLINE \ [&{KQ5_RESOURCE_GROUPS.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: BRING_RESOURCE_GROUP_ONLINE \ [&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCE_GROUPS.Name : Resource group Name Default: &KQ5_RESOURCE_GROUPS.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ500010E Message: Error bringing the Resource Group online. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500011I Message: Time-out occurred bringing Resource Group online. v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ50008I Message: The Resource Group is brought online. v Return Code: 2 Return Code : ALREADY_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50009I Message: The Resource Group is already running. v Return Code: 9 246 Microsoft Cluster Server agent: User's Guide

Usage Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes resource group name as a parameter. Bring Resource online action Bring Resource 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_ONLINE \ [KQ5_RESOURCES.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: BRING_RESOURCE_ONLINE \ [&{KQ5_RESOURCES.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: BRING_RESOURCE_ONLINE \ [&WaitOnSituation:KQ5_RESOURCES.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCES.Name : Resource Name Default: &KQ5_RESOURCES.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ50001I Message: The Resource is brought online. v Return Code: 2 Return Code : ALREADY_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50002I Message: The Resource is already running. v Return Code: 1 Chapter 6. Take Action commands reference 247

Usage Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ50003E Message: Error bringing the resource online. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ50004I Message: Time-out occurred bringing resource online. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes resource name as a parameter. Delete Resource Group action Delete the resource group that is passed as a parameter. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: DELETE_RESOURCE_GROUP \ [KQ5_RESOURCE_GROUPS.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: DELETE_RESOURCE_GROUP \ [&{KQ5_RESOURCE_GROUPS.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: DELETE_RESOURCE_GROUP \ [&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCE_GROUPS.Name : Resource group Name Default: &KQ5_RESOURCE_GROUPS.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 248 Microsoft Cluster Server agent: User's Guide

Usage Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ500033I Message: The Resource Group is deleted. v Return Code: 2 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500034I Message: This Resource Group does not exist in cluster. v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ500035E Message: Unable to delete Resource Group. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500036I Message: Time-out occurred in deleting Resource Group. v Return Code: 3 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500038I Message: Delete Resource Group is not supported on any Windows 2003 edition. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes resource group name as a parameter. Move Resource Group action Move the resource group, which is passed as a parameter, to a specified node. If a node name is not specified, the resource group is moved to the best possible node. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: MOVE_RESOURCE_GROUP \ [KQ5_RESOURCE_GROUPS.Name] [KQ5_NODES.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: Chapter 6. Take Action commands reference 249

MOVE_RESOURCE_GROUP \ [&{KQ5_RESOURCE_GROUPS.Name}] \ [&{KQ5_NODES.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: MOVE_RESOURCE_GROUP \ [&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name] \ [&WaitOnSituation:KQ5_NODES.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCE_GROUPS.Name : Resource group Name Default: &KQ5_RESOURCE_GROUPS.Name v Name: KQ5_NODES.Name : Node Name Default: &KQ5_NODES.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ500029I Message: The Resource Group is moved. v Return Code: 2 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500030I Message: This Resource Group does not exist in cluster. v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ500031E Message: No eligible node found for moving Resource Group. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500032I Message: Time-out occurred in moving Resource Group. v Return Code: 3 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500039I Message: This Node does not exist in cluster. v Return Code: 4 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500040I Message: Given Node is not preferred node for this resource group. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) 250 Microsoft Cluster Server agent: User's Guide

Usage Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes two parameters as resource group name and node name. If a node name is not specified, the resource group is moved to the best possible node. Pause Node action Pause the node that is passed as a parameter. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: PAUSE_NODE \ [KQ5_NODES.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: PAUSE_NODE \ [&{KQ5_NODES.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: PAUSE_NODE \ [&WaitOnSituation:KQ5_NODES.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_NODES.Name : Node Name Default: &KQ5_NODES.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ500025I Message: The Node is paused. v Return Code: 3 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500026I Message: The Node is already paused. v Return Code: 1 Return Code : GENERAL_ERROR Chapter 6. Take Action commands reference 251

Usage Operating systems: Windows, Windows (64-bit) Message ID: KQ500027E Message: Error in pausing the Node. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500028I Message: Time-out occurred in pausing Node. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50101W Message: This Node does not exist in cluster. v Return Code: 2 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ51011 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes node name as a parameter. Resume Node action Resume the node that is passed as a parameter. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: RESUME_NODE \ [KQ5_NODES.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: RESUME_NODE \ [&{KQ5_NODES.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: RESUME_NODE \ [&WaitOnSituation:KQ5_NODES.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_NODES.Name : Node Name Default: &KQ5_NODES.Name 252 Microsoft Cluster Server agent: User's Guide

Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ500021I Message: The Node is resumed. v Return Code: 2 Return Code : ALREADY_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500022I Message: The Node is already running. v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ500023E Message: Error in resuming the Node. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500024I Message: Time-out occurred in resuming Node. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50101W Message: This Node does not exist in cluster. v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! Usage This Take Action takes node name as a parameter. Take Resource Group offline action Take Resource Group offline. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: TAKE_RESOURCE_GROUP_OFFLINE \ [KQ5_RESOURCE_GROUPS.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: TAKE_RESOURCE_GROUP_OFFLINE \ [&{KQ5_RESOURCE_GROUPS.Name}] Chapter 6. Take Action commands reference 253

You can also use attribute substitution in a workflow policy though the format is slightly different: TAKE_RESOURCE_GROUP_OFFLINE \ [&WaitOnSituation:KQ5_RESOURCE_GROUPS.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCE_GROUPS.Name : Resource group Name Default: &KQ5_RESOURCE_GROUPS.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ500012I Message: The Resource Group is taken offline. v Return Code: 3 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ500013I Message: The Resource Group is already offline. v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ500014E Message: Error bringing the Resource Group offline. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ500015I Message: The preset time to take the Resource Group offline has timed out. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 2 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ51011 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! Usage This Take Action takes resource group name as a parameter. 254 Microsoft Cluster Server agent: User's Guide

Take Resource offline action Take Resource offline. System command To include the Take Action command in a situation or workflow policy, use the following syntax for the system command: TAKE_RESOURCE_OFFLINE \ [KQ5_RESOURCES.Name] You can use attribute substitution to supply the Take Action command arguments from the situation, for example: TAKE_RESOURCE_OFFLINE \ [&{KQ5_RESOURCES.Name}] You can also use attribute substitution in a workflow policy though the format is slightly different: TAKE_RESOURCE_OFFLINE \ [&WaitOnSituation:KQ5_RESOURCES.Name] Authorization User must be a member of the Administrators group. Command arguments v Name: KQ5_RESOURCES.Name : Resource Name Default: &KQ5_RESOURCES.Name Destination systems _EnDDESTINATIONS_NONE_OR_LIST_EnD Return codes v Return Code: 1 Return Code : GENERAL_ERROR Operating systems: Windows, Windows (64-bit) Message ID: KQ50004E Message: Error taking the resource offline. v Return Code: 0 Return Code : OK Operating systems: Windows, Windows (64-bit) Message ID: KQ50005I Message: The Resource is taken offline. v Return Code: 3 Return Code : NOT_RUNNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50006I Message: The Resource is already offline. v Return Code: 10 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ50007I Message: Time-out occurred taking resource offline. v Return Code: 9 Return Code : WARNING Operating systems: Windows, Windows (64-bit) Message ID: KQ50100W Message: Operation unsuccessful. v Return Code: 2 Return Code : GENERAL_ERROR Chapter 6. Take Action commands reference 255

Usage Operating systems: Windows, Windows (64-bit) Message ID: KQ51011 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 8 Return Code : TIMED_OUT Operating systems: Windows, Windows (64-bit) Message ID: KQ51012 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! v Return Code: 12 Return Code : INSUFFICIENT_USER_AUTHORITY Operating systems: Windows, Windows (64-bit) Message ID: KQ51013 Message: WARNING::NO MESSAGE FOUND FOR THIS RETURN CODE!!!!! This Take Action takes resource name as a parameter. 256 Microsoft Cluster Server agent: User's Guide

Chapter 7. Policies reference Policies are used as an advanced automation technique for implementing more complex workflow strategies than you can create through simple automation. All agents do not provide predefined policies, but you can create policies for any agent. A policy is a set of automated system processes that can take 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, the Tivoli Enterprise Portal receives return-code feedback, and advanced automation logic responds with subsequent activities prescribed by the feedback. For more information about working with policies, see Automation with policies in 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 Not all agents have predefined policies. But you can create policies for any agent. The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent does not provide predefined policies. Copyright IBM Corp. 2008, 2013 257

258 Microsoft Cluster Server agent: User's Guide

Chapter 8. Tivoli Common Reporting for the monitoring agent You can use the Tivoli Common Reporting application to generate reports for the Microsoft Cluster Server agent. For more information about Tivoli Common Reporting, such as prerequisites, importing reports, and running reports, see the IBM Tivoli Monitoring Administrator's Guide V6.2.3. IBM Tivoli Monitoring for Microsoft Applications reports are historical reports that include summarized data that is collected in the Tivoli Data Warehouse. These reports are built to run only against the IBM Tivoli Monitoring for Microsoft Cluster Server agent. The reports can be administered and run on Tivoli Common Reporting V1.3, V2.1, V2.1.1, Fix Pack 6, and V3.1. For more information about Tivoli Common Reporting, see the developerworks website (http://www.ibm.com/developerworks/spaces/tcr). This version of Tivoli Common Reporting includes Cognos Business Intelligence and Reporting V8.4. Cognos-based report packages The Cognos-based Tivoli Common Reporting tool is used to create, view, and manage reports for the Tivoli group of products. You can use the Cognos reports to analyze resource information such as availability, utilization, performance, and so on. With Cognos reports, you can evaluate the key metrics of the computers that are on the managed environment of your organization. You can use the Tivoli Common Reporting tool to: v Create custom reports by using the drag-and-drop feature integrated with the web-based editor. v Schedule, share, secure, and administer reports in a single interface. v Save the report in HTML, PDF, Excel, XML, or CSV file formats. v Share reports by email or save the reports in a file system for later use. The following databases are supported for all reports: v DB2 V9.5 and V9.7, Fix Pack 2 v Oracle 10g and 11g v SQL Server 2005 and 2008 You can use Tivoli Common Reporting V1.3, V2.1, V2.1.1, Fix Pack 6, and V3.1 software that is shipped with IBM Tivoli Monitoring V6.2.3, or later to administer, run, and edit Cognos reports. For more information about Tivoli Common Reporting, see the Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ic-home.html). Prerequisites Before you run the Cognos-based reports, ensure that the prerequisites that are required for installing and running Tivoli Common Reporting packages are met. Procedure 1. Install Tivoli Common Reporting. For more information, see the documentation in the IBM Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/ topic/com.ibm.tivoli.tcr.doc_211/ic-home.html). Copyright IBM Corp. 2008, 2013 259

To ensure that Tivoli Common Reporting is running, go to: https://machine_name:port_number/ibm/console/. 2. Obtain the reports package from the product media and extract the package. The Cognos reports are available in the following package: Product Media root/reports/kq5/ ITCAMMA_ClusterServer_V710_Cognos_Reports. 3. Copy this package in a directory on any drive of the same computer where the Tivoli Common Reporting Server is installed, and extract the package in the same directory. The directory contents include: v Database scripts required to prepare the Tivoli Data Warehouse for Cognos reports. v A report installer that imports the reports into Tivoli Common Reporting and sets up the database connection. 4. Open the setup.batch file, and verify that the specified drive is the same drive where the Tivoli Common Reporting Server is installed. If the specified drive is not correct, edit the setup.batch file to specify the correct drive. For example, change the TCR_DEFAULT_DIR=C:\IBM\tivoli\tip to TCR_DEFAULT_DIR=F:\IBM\tivoli\tip if the Tivoli Common Reporting Server is installed on the F drive. 5. Configure historical collection for Microsoft Cluster Server agent and the IBM Tivoli Warehouse Summarization and Pruning Agent. After IBM Tivoli Monitoring V6.2.3, Fix Pack 1, or later is installed and the Microsoft Cluster Server agent is installed and configured, configure historical collection. Also, configure the Warehouse Summarization and Pruning agent with or without shifts enabled. For more information about how to enable historical collection and configure the Warehouse Summarization and Pruning agent in IBM Tivoli Monitoring, see the following documentation: v http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/ history_manage_intro.htm v http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/ history_manage_collection.htm Note: Historical collection and daily and hourly summarization must be enabled for all attribute groups of Microsoft Cluster Server agent. To ensure that the required views are present, run the following query against the Tivoli Data Warehouse: v DB2: Select distinct "VIEWNAME" from SYSCAT.VIEWS where "VIEWNAME" like %V v Oracle: Select distinct "OBJECT_NAME" from OBJ where "OBJECT_TYPE" like %V v MS SQL Server: Select distinct "NAME" from SYS.OBJECTS where "TYPE_DESC" like %V 6. Prepare the Tivoli Data Warehouse to support Cognos dimensions. Preparing the Tivoli Data Warehouse for Tivoli Common Reporting includes creating the IBM_TRAM dimensions, which are required for running the Cognos reports and using the data models. See "Creating shared dimension tables and populating the time dimensions table" in the IBM Tivoli Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/ tcr_reports_dimensionsshared.htm). 7. Connect to the Tivoli Data Warehouse by using the database client over Open Database Connectivity (ODBC). Cognos uses ODBC to connect to the database. Install a database client on the Tivoli Common Reporting Server and connect it to the Tivoli Data Warehouse. See "Connecting to the Tivoli Data Warehouse using the database client over ODBC" in the IBM Tivoli Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/ tcr_tdwconnect.htm). Important: All prerequisites described here must be met or the reports cannot run. 260 Microsoft Cluster Server agent: User's Guide

Importing Cognos report packages You must import the Cognos report package that contains the Microsoft Cluster Server agent data model and reports into Tivoli Common Reporting. Before you import the Cognos report package, ensure that all the prerequisites have been met. Otherwise, reports cannot run. For Tivoli Common Reporting V1.3, use one of the following options to import the Cognos report package: v Importing by running the reports installer For information about running the reports installer to import the Cognos report package, see "Installing and running IBM Cognos reports" in the IBM Tivoli Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.2, Fix Pack 2 Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/ tcr_install_itm.htm) v Importing manually For information about manually importing the reports package, see Importing report packages at the IBM Tivoli Systems Management Information Center (http://pic.dhe.ibm.com/ infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/ttcr_cog_import.html). For Tivoli Common Reporting V2.1, or later, see "Importing report packages" at the Tivoli Common Reporting Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/ com.ibm.tivoli.tcr.doc_211/ttcr_import.html). If you are using a schema other than ITMUSER, you must complete the following steps for the data model and reports to run: 1. Verify that you have completed the following steps: a. Altered the schema name in the database scripts when you prepared the Tivoli Data Warehouse for Cognos dimensions in Step 6 on page 260 of Prerequisites on page 259. b. Installed the reports package by using the Reports installer as explained in "Importing reports by using the report installer" topic in the IBM Tivoli Monitoring Administrator's Guide. To verify that you have installed the reports package, go to Tivoli Common Reporting and make sure you can see "ITCAMMA ClusterServer V710 Cognos Reports" in the Public Folders of IBM Cognos Connection. 2. Install and configure the Cognos Framework Manager, which is the data modeling tool. See the instructions at the Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/ infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_configure_frameworkmgr.html). 3. Open the Framework Manager. Select File > Open. Browse to the extracted ITCAMMA ClusterServer V710 Cognos Reports reports package. Browse to the model folder and select the ITCAMMA ClusterServer V710 Cognos Reports.cpf file. 4. If you are prompted to enter login credentials, enter your tipadmin user ID and password. 5. After the IBM Tivoli Monitoring for Cluster Servers data model in the Framework Manager opens, expand Data s under Tivoli Reporting and Analytics Model in the Project Viewer. 6. Select TDW under Data s. 7. When you select TDW, the Properties view is updated with information about the Tivoli Data Warehouse data source. By default, the Properties view is located at the bottom center of the screen. If the Properties view is not visible, select View > Properties. 8. In the Properties, edit the Schema field. Change it from ITMUSER to your schema name. 9. Save the project. 10. In the Project Viewer, expand Packages. 11. Right-click ITCAMMA ClusterServer V710 Cognos Reports. 12. Select Publish Packages. The Publish Wizard opens. 13. Keep the default selection and click Next. 14. Click Next on the next screen. Chapter 8. Tivoli Common Reporting for the monitoring agent 261

15. Clear the Verify the package before publishing check box. 16. Click Publish. A window is displayed that alerts you that A package with that name already exists and asks Do you want to publish this package? 17. Click Yes. 18. Go back to Tivoli Common Reporting and check if the Modified field of "ITCAMMA ClusterServer V710 Cognos Reports" in the Public Folders of IBM Cognos Connection shows the time of publishing. After completing these steps, you can run any report from the IBM Tivoli Monitoring for ITCAMMA ClusterServer V710 Cognos Reports package. Cognos data models and reports When all the prerequisites are met, you can use the Tivoli Integrated Portal interface to create, modify, and manage Cognos reports. In Tivoli Common Reporting, the historical data that is collected by the agent is used to build ad hoc reports and queries. The package that you import into Tivoli Common Reporting contains a Cognos data model. All the reports that you create in Tivoli Common Reporting are based on the data model. Cognos data models are virtual star schema models that contain facts and dimensions. Facts are measurable quantities that can be aggregated, such as CPU utilization and number of processors. Dimensions are the main identifiers by which facts can be grouped, aggregated, and organized. For example, time and server are dimensions by which the fact CPU utilization can be grouped. The facts in the data model are organized into the folders by their summarization type, such as Daily and Hourly. The Daily and the Hourly folders contain attribute groups that correspond to tables or views in the data warehouse. Each attribute group contains a group of facts and measures. The data model is built on top of the data warehouse to organize data. The data model contains the Tivoli Reporting and Analytics Model (TRAM) Shared Dimensions, which are shared across Tivoli by products such as Time. To create reports in Tivoli Common Reporting tool, you can use one of the following report authoring tools: v Query Studio: A web-based product that is used mostly for ad hoc reporting. Users can create simple queries and reports, and apply basic formatting to the reports. v Report Studio: A web-based tool that is used by technical users and professional report writers for creating advanced reports. Users can retrieve data from multiple databases and create sophisticated reports that have multiple pages and multiple queries. Reports for the monitoring agent You can verify whether the reporting functionality is installed and configured correctly by running the reports for the Microsoft Cluster Server agent. The Microsoft Cluster Server agent reporting package that you imported into Tivoli Common Reporting includes five reports. Note: Before you run the reports, ensure that the database connection with the Tivoli Data Warehouse is defined and tested. By using these reports, you can monitor the reporting activity and see what a typical Cognos report includes. These reports are available in the Common Reporting panel in Tivoli Common Reporting. The following tables describe these reports. 262 Microsoft Cluster Server agent: User's Guide

Table 6. Cluster Server Agent Reports Prerequisite Scanner report Name Cluster Server Agent Reports Prerequisite Scanner report This report provides the availability status of tables and views in the Tivoli Data Warehouse for each predefined report. Purpose You can use this report to verify whether all the tables and views that are required for running the predefined reports are available in the Tivoli Data Warehouse. The report also contains links to the appropriate documentation for enabling historical collection and summarization and pruning, creating IBM_TRAM schema, populating time and other shared directions, and so on. Parameters Specify values for the following parameters: v Database type, such as DB2, Oracle, or SQL v Report type such as show falling sections only to view only those reports for which tables and views are not available in the Tivoli Data Warehouse or show all sections to view all reports v Summarization type, such as Hourly, Daily, Monthly, and All Output This report shows the availability status of all the tables and views in the Tivoli Data Warehouse according to reports. The report also shows other information, such as prerequisites for Tivoli Common Reporting shared dimensions and IBM Tivoli Monitoring shared dimensions. Note: Images are not displayed correctly when you run this report in the Tivoli Common Reporting server V3.1. To view images, extract the report package and copy all the images in the package to the following locations: v TCR Server Installation Drive\Program Files\IBM\JazzSM\profile\installedApps\ JazzSMNode01Cell\IBM Cognos.ear\p2pd.war\tivoli\tcr_common\images v TCR Server Installation Drive\Program Files\IBM\JazzSM\reporting\cognos\webcontent\ tivoli\tcr_common\images Usage The administrators can use this report to verify whether the tables and views that are required for running the reports are available in the Tivoli Data Warehouse. Sometimes, the reports cannot be run because of insufficient data in the Tivoli Data Warehouse. The report displays the useful links to the appropriate documentation that administrators can refer to for populating the tables with data, such as running the database scripts. Table 7. Resource Utilization Details for Single Node report Name Resource Utilization Details for Single Node report This report displays resource utilization such as disk usage, memory usage, CPU utilization, and network utilization of a specified computer. Purpose You can use this report to evaluate the system performance of a Cluster Server within a specified duration. Chapter 8. Tivoli Common Reporting for the monitoring agent 263

Table 7. Resource Utilization Details for Single Node report (continued) Parameters 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. Alternatively, you can 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. Summarization Selection Summarization 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 calculated according to the number of days in the date range.. Shift Period If the shift period is enabled, the hourly tables display the shift period as 1 (off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours that are configured in the data warehouse. In the daily tables, the value 1 corresponds to peak hours, the value 2 corresponds to off-peak hours, and the value -1 corresponds to the summarized value for that day. If the shift period is disabled, the default value is -1. Vacation Period If the vacation period is disabled, the default value is -1 (All Days). If the vacation period is enabled, you can enter the value 0 (Work Days) or 1 (Vacation Days). Display Options Name of cluster Select the name of the Cluster Server from the Name of Cluster list. System Name Select the workstation from the System Name list. Tables/Views Used Output Usage v v KQ5_MEMORY_DV, KQ5_CPU_PER_NODE_%V KQ5_NETWORK_PERFORMANCE_DV, KQ5_DISK_%V This report contains the five line charts that display the disk usage, memory usage, percent committed bytes in use, CPU utilization, and network utilization of a computer within a specified duration. The tables below the charts display the same information. If no data is available for the specified parameters, an appropriate message is displayed. The administrators can use this report to evaluate the resource utilization by a node. The resource utilization contains information such as disk usage, memory usage, CPU utilization, and network utilization that helps administrators to take any corrective or preventive action if required. Table 8. Cluster Nodes Availability report Name Cluster Nodes Availability report This report displays the data about the availability of nodes for the Cluster Server. Purpose You can use this report to identify the availability of nodes across the Cluster Server. 264 Microsoft Cluster Server agent: User's Guide

Table 8. Cluster Nodes Availability report (continued) Parameters 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. Alternatively, you can 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. Summarization Selection Summarization 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. Shift Period If the shift period is enabled, the hourly tables display the shift period as 1 (off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours that are configured in the data warehouse. In the daily tables, the value 1 corresponds to peak hours, the value 2 corresponds to off-peak hours, and the value -1 corresponds to the summarized value for that day. If the shift period is disabled, the default value is -1. Vacation Period If the vacation period is disabled, the default value is -1 (All Days). If the vacation period is enabled, you can enter the value 0 (Work Days) or 1 (Vacation Days). Display Options Name of cluster Select the name of the Cluster Server from the Name of Cluster list. System Name Select the workstation from the System Name list. You can select a single workstation or all the workstations (by selecting All) from the list. Number of Systems Specify the number of systems. Tables or views used Output Usage KQ5_Nodes_%V This report displays the availability of nodes (in percentage) for the selected Cluster Server. The values are displayed in the hover help. The IT administrators can use this report to view the summary of availability of nodes (in percentage) for the Cluster Server agents. Table 9. Cluster Resource Group Availability report Name Cluster Resource Group Availability report This report displays the information about the availability of the resource group 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. Chapter 8. Tivoli Common Reporting for the monitoring agent 265

Table 9. Cluster Resource Group Availability report (continued) Parameters 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. Alternatively, you can 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. Summarization Selection Summarization 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. Shift Period If the shift period is enabled, the hourly tables display the shift period as 1 (off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours that are configured in the data warehouse. In the daily tables, the value 1 corresponds to peak hours, the value 2 corresponds to off-peak hours, and the value -1 corresponds to the summarized value for that day. If the shift period is disabled, the default value is -1. Vacation Period If the vacation period is disabled, the default value is -1 (All Days). If the vacation period is enabled, you can enter the value 0 (Work Days) or 1 (Vacation Days). Display Options Name of cluster Select the name of the Cluster Server from the Name of Cluster list. System Name Select the workstation from the System Name list. Tables or views used Output Usage KQ5_NODE_TO_ACTIVE_GROUP_%V 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. The IT administrators can use this report to identify the availability of the resource group (in percentage) for all Cluster Server nodes. Table 10. Disk Utilization for Cluster Nodes report Name Disk Utilization for Cluster Nodes report This report displays the percentage of disk usage and free space on a particular node. Purpose You can use this report to determine the percentage of disk usage. 266 Microsoft Cluster Server agent: User's Guide

Table 10. Disk Utilization for Cluster Nodes report (continued) Parameters 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. Alternatively, you can 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. Summarization Selection Summarization 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. Shift Period If the shift period is enabled, the hourly tables display the shift period as 1 (off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours that are configured in the data warehouse. In the daily tables, the value 1 corresponds to peak hours, the value 2 corresponds to off-peak hours, and the value -1 corresponds to the summarized value for that day. If the shift period is disabled, the default value is -1. Vacation Period If the vacation period is disabled, the default value is -1 (All Days). If the vacation period is enabled, you can enter the value 0 (Work Days) or 1 (Vacation Days). Display Options Name of cluster Select the name of the Cluster Server from the Name of Cluster list. System Name Select the workstation from the System Name list. Tables or views used Output Usage KQ5_DISK_%V 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. The IT administrators can use this report to observe the percentage of the used and free disk space on each Cluster node. Table 11. Memory Utilization for Cluster Nodes report Name Memory Utilization for Cluster Nodes report This report 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. 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. Chapter 8. Tivoli Common Reporting for the monitoring agent 267

Table 11. Memory Utilization for Cluster Nodes report (continued) Parameters 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. Alternatively, you can 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. Summarization Selection Summarization 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. Shift Period If the shift period is enabled, the hourly tables display the shift period as 1 (off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours that are configured in the data warehouse. In the daily tables, the value 1 corresponds to peak hours, the value 2 corresponds to off-peak hours, and the value -1 corresponds to the summarized value for that day. If the shift period is disabled, the default value is -1. Vacation Period If the vacation period is disabled, the default value is -1 (All Days). If the vacation period is enabled, you can enter the value 0 (Work Days) or 1 (Vacation Days). Display Options Name of cluster Select the name of the Cluster Server from the Name of Cluster list. System Name Select the workstation from the System Name list. Tables or views used Output Usage KQ5_MEMORY_%V 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 currently used by the selected workstation. The IT administrators and managers can use this report to compare the overall performance of multiple applications on different servers for a selected period of time. 268 Microsoft Cluster Server agent: User's Guide

Chapter 9. Troubleshooting Problems can be related to IBM Tivoli Monitoring or the specific agent that you are using. For general troubleshooting information, see the IBM Tivoli Monitoring Troubleshooting Guide. For other problem-solving options, see Support information on page 301. You can resolve some problems by ensuring that your system matches the system requirements listed in the Prerequisites topic for the agent in the ITCAM for Microsoft Applications Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/ welcome_msapps63.html). The following activities can help you find a solution to the problem you are having: v Gathering product information for IBM Software Support v Using logging on page 270 v Consulting the lists of identified problems and workarounds on page 270 Gathering product information for IBM Software Support Before contacting IBM Software Support about a problem you are experiencing with this product, gather the information shown in Table 12. Table 12. Information to gather before contacting IBM Software Support Information type Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectory on the host computer. See Principal trace log files on page 271 for lists of all trace log files and their locations. For general information about the IBM Tivoli Monitoring environment, see the Tivoli Enterprise Portal User's Guide. Microsoft Cluster Server information Operating system Messages Version numbers for IBM Tivoli Monitoring Screen captures Version number and patch level Operating system version number and patch level Messages and other information displayed on the screen 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 of incorrect output, if any You can use the pdcollect tool to collect the most commonly used information from a system. This tool gathers log files, configuration information, version information, and other data. For more information about using this tool, see the "pdcollect tool" in the IBM Tivoli Monitoring Troubleshooting Guide. For information about working with IBM Software Support, see IBM Support Portal Service Requests and PMRs (http://www.ibm.com/support/entry/portal/open_service_request/software/ Software_support_(general)). Copyright IBM Corp. 2008, 2013 269

Using logging Logging is the primary troubleshooting feature in the Microsoft Cluster Server agent. Logging refers to the text messages and trace data that is 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 for more information. Consulting the lists of identified problems and workarounds Known problems are organized into types such as those in the following list to make them easier to locate: v Installation and configuration v General usage and operation v Display of monitoring data v Take Action commands Information about symptoms and detailed workarounds for these types of problems is located in Problems and workarounds on page 277. For general troubleshooting information, see the IBM Tivoli Monitoring Troubleshooting Guide. Trace logging Trace logs are used to capture information about the operating environment when component software fails to operate as designed. 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 information to learn how to configure and use trace logging: v Principal trace log files on page 271 v Examples: Using trace logs on page 273 v Setting RAS trace parameters by using the GUI on page 274 Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as "RAS1." IBM Software Support personnel use 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 Knowing the naming conventions for log files helps you to find the files. Agent log file naming conventions Table 13 on page 271 provides the names, locations, and descriptions of IBM Tivoli Monitoring general RAS1 log files. The log file names for the Microsoft Cluster Server agent adhere to the following naming convention: 270 Microsoft Cluster Server agent: User's Guide

Windows systems hostname_productcode_program_hextimestamp-nn.log Where: hostname Host name of the computer where the monitoring component is running. productcode Two-character product code. For IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent, the product code is q5. program Name of the program being run. HEXtimestamp Hexadecimal time stamp representing the time at which the program started. nn Rolling log suffix. Principal trace log files Trace log files are located on various systems. Table 13 contains locations, file names, and descriptions of trace logs that can help determine the source of problems with agents. Table 13. Trace log files for troubleshooting agents System where log is located File name and path On the Tivoli Enterprise Monitoring Server On the computer that hosts the Warehouse Proxy agent v v Windows: The file in the install_dir\installitm path UNIX and Linux: The candle_installation.log file in the install_dir/logs path The configuration log file for the Warehouse Proxy agent is in the following path depending on the operating system that you are using: v v Windows: install_dir\ InstallITM\ Warehouse_Configuration.log UNIX: install_dir/logs/ KHDCFG.log Provides details about products that are installed. Note: Trace logging is enabled by default. A configuration step is not required to enable this tracing. Provides details about the configuration of data warehousing for historical reporting. Chapter 9. Troubleshooting 271

Table 13. Trace log files for troubleshooting agents (continued) System where log is located File name and path On the Tivoli Enterprise Monitoring Server The name of the RAS log file is as follows: v v Windows: install_dir\logs\ hostname_ms_timestamp-nn.log UNIX and Linux: install_dir/logs/ hostname_ms_timestamp-nn.log Note: File names for RAS1 logs include a hexadecimal time stamp. Traces activity on the monitoring server. On the Tivoli Enterprise Portal Server Also on UNIX systems, a log with a decimal time stamp is provided: hostname_productcode_timestamp.log and hostname_productcode_ timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID. The name of the RAS log file is as follows: v v v Windows: install_dir\logs\ hostname_cq_hextimestamp-nn.log UNIX: install_dir /logs/hostname_cq_hextimestampnn.log Linux: install_dir /logs/hostname_cq_hextimestampnn.log Note: File names for RAS1 logs include a hexadecimal time stamp. Traces activity on the portal server. When you enable historical reporting, the teps_odbc.log log file traces the status of the warehouse proxy agent. On the computer that hosts the monitoring agent Also on UNIX systems, a log with a decimal time stamp is provided: hostname_productcode_timestamp.log and hostname_productcode_ timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID. The teps_odbc.log file is located in the following path: v Windows: install_dir\installitm The RAS1 log files for Windows is hostname_q5_instance_name_ kq5agent_hextimestamp-nn.log. On the Windows operating system, the logs are in the following directories: v v For a 32-bit agent: install_dir\tmaitm6\logs For a 64-bit agent: install_dir\tmaitm6_x64\logs Traces activity of the monitoring agent. 272 Microsoft Cluster Server agent: User's Guide

Table 13. Trace log files for troubleshooting agents (continued) System where log is located File name and path On the computer that hosts the monitoring agent On the computer that hosts the monitoring agent The agent operations log files are as follows: instance_hostnameq5.lg0 is the current log created when the agent was started. instance_hostname_q5.lg1 is the backup of the previous log. On Windows operating system, the logs are in the following directories: v v For a 32-bit agent: install_dir\tmaitm6\logs For a 64-bit agent: install_dir\tmaitm6_x64\logs The Take Action command log files are as follows: v host_q5_ takeactioncommand.log The logs are in the following directories: v Windows: install_dir\tmaitm6\ logs Shows whether the agent could connect to the monitoring server. Shows which situations are started and stopped, and shows other events while the agent is running. A new version of this file is generated every time the agent is restarted. IBM Tivoli Monitoring generates one backup copy of the *.LG0 file with the tag.lg1. View the.lg1 tag to learn the following details regarding the previous monitoring session: v v v Status of connectivity with the monitoring server Situations that were running The success or failure status of Take Action commands 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: v timestamp is a time stamp with a format that includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm v HEXtimestamp is a hexadecimal representation of the time at which the process was started. v 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. v instance refers to the name of the database instance that you are monitoring. v instance_name refers to the name of the agent instance. v hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs. v nn represents the circular sequence in which logs are rotated. this value includes a range from 1-5, bydefault. The first is always retained because it includes configuration parameters. v productcode specifies the product code, for example, um for Universal Agent or nt for Windows systems. 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. IBM Software Support applies specialized knowledge to analyze trace logs to determine the source of problems. The following examples are from the Tivoli Enterprise Monitoring Server log. Chapter 9. Troubleshooting 273

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> 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. See the following key points about the preceding excerpts: 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 IBM Tivoli Composite Application Manager for Microsoft Applications: 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 by using the GUI provide these entries. On Windows systems, you can use the following alternate method to view trace logs: 1. In the Windows Start menu, click 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 click Advanced > View Trace Log in the menu. For example, if you want to view the trace log of the IBM Tivoli Composite Application Manager for Microsoft Applications: 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. RAS trace parameters Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules See Overview of log file management on page 270 to ensure that you understand log rolling and can reference the correct log files when you manage log file generation. Setting RAS trace parameters by using the GUI On Windows systems, you can use the graphical user interface to set trace options. 274 Microsoft Cluster Server agent: User's Guide

About this task The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent uses RAS1 tracing and generates the logs described in Table 13 on page 271. The default RAS1 trace level is ERROR. Procedure 1. Open the Manage Tivoli Enterprise Monitoring Services window. 2. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed. 3. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string. v General error tracing. KBB_RAS1=ERROR v Intensive error tracing. KBB_RAS1=ERROR (UNIT:kq5 ALL) v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kq5 ALL) (UNIT:kra ALL) Note: As this example shows, you can set multiple RAS tracing options in a single statement. 4. Modify the value for Maximum Log Size Per File (MB) to change the log file size (changes LIMIT value). 5. 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). 6. 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). 7. 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. 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. 8. Click OK. You see a message reporting a restart of the monitoring agent so that your changes take effect. What to do next Monitor the size of the logs directory. Default behavior can generate a total of 45-60 MB for each agent that is running on a computer. For example, each database instance that you monitor can generate 45-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 13 on page 271 that include a process ID (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. Manually setting RAS trace parameters You can manually edit the RAS1 trace logging parameters. Chapter 9. Troubleshooting 275

About this task The Microsoft Cluster Server agent uses RAS1 tracing and generates the logs described in Table 13 on page 271. The default RAS1 trace level is ERROR. Procedure 1. Open the trace options file: v Windows systems: For a 32-bit agent: install_dir\tmaitm6\kqlenv For a 64-bit agent: install_dir\tmaitm6_x64\kqlenv 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:kq5 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 specific program. When this value is exceeded, the oldest log files are discarded. The default value is 9. v LIMIT: The maximum size, in megabytes (MB) of a RAS1 log file. The default value is 5. v IBM Software Support might guide you to modify the following parameters: COUNT: The number of log files to keep in the rolling cycle of one program startup. The default is 3. PRESERVE: The number of files that are not to be reused in the rolling cycle of one program startup. The default value is 1. Note: 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. What to do next Monitor the size of the logs directory. Default behavior can generate a total of 45-60 MB for each agent that is running on a computer. For example, each database instance that you monitor can generate 45-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 13 on page 271 that include a process ID (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. Setting trace parameters for the Tivoli Enterprise Console server In addition to the trace information captured by IBM Tivoli Monitoring, you can also collect additional trace information for the Tivoli Enterprise Console components that gather event server metrics. 276 Microsoft Cluster Server agent: User's Guide

About this task To collect this information, modify the.tec_diag_config file on the Tivoli Enterprise Console event server. Use the steps in the following procedure to modify the event server trace parameters. Procedure 1. Open the $BINDIR/TME/TEC/.tec_diag_config file in an ASCII editor. 2. Locate the entries that configure trace logging for the agent components on the event server. Two entries are included, one for tec_reception and one for tec_rule: # to debug Agent Utils tec_reception Agent_Utils error /tmp/tec_reception SP # to debug Agent Utils tec_rule Agent_Utils error /tmp/tec_rule 3. To gather additional trace information, modify these entries to specify a trace level of trace2: # to debug Agent Utils tec_reception Agent_Utils trace2 /tmp/tec_reception SP # to debug Agent Utils tec_rule Agent_Utils trace2 /tmp/tec_rule 4. In addition, modify the Highest_level entries for tec_rule and tec_reception: tec_reception Highest_level trace2 SP tec_rule Highest_level trace2 Problems and workarounds The known problems and workarounds are organized into types of problems that might occur with the Microsoft Cluster Server agent, for example, installation and configuration problems and workspace problems. Note: You can resolve some problems by ensuring that your system matches the system requirements listed in the Prerequisites topic for the agent in the IBM Tivoli Composite Application Manager for Microsoft Applications Information Center. For general troubleshooting information, see the IBM Tivoli Monitoring Troubleshooting Guide. Installation and configuration troubleshooting Problems can occur during installation, configuration, and uninstallation of the agent. The problems and solutions in Table 14 on page 278 can occur during installation, configuration, and uninstallation of the agent. Chapter 9. Troubleshooting 277

Table 14. Problems and solutions for installation and configuration Problem Solution Diagnosing problems with product browse settings (Windows systems only). When you have problems with browse settings, complete 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. The system is experiencing high CPU usage. Two or more Windows system names are displayed in the Navigation view for the same cluster. If requested, you can forward this file to IBM Software Support for analysis. 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 v Do multiple network interface cards (NICs) exist on the system? 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. Agent process: View the memory usage of the kq5agent process. If CPU usage seems to be excessive, restart the monitoring agent. Network cards: The network card configurations can decrease the performance of a system. Each 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. Check the configuration (cluster name) parameter on each node of the cluster and ensure that they are identical. If not, complete 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. 278 Microsoft Cluster Server agent: User's Guide

Table 14. Problems and solutions for installation and configuration (continued) Problem Solution Two or more instances of the agent (IBM Tivoli Monitoring for Cluster Managers: Microsoft Cluster Servers) appear under the windows system name. You have installed two 32-bit Microsoft Application agents and the 32/64-bit Agent Compatibility Package (ACP) from the 64-bit agent of ITCAM for Microsoft Applications. You cannot install additional 32-bit Microsoft application agents on the same managed system. When you use the Installation Launch Pad to install a 32-bit agent on a 32-bit computer, the following message is displayed: The following components cannot be installed because the installation action failed. IBM Tivoli Composite Application Manager for Microsoft Applications V6.2.3 for Windows on 64-bit AMD and Intel systems (x64) 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 is displayed after applying pending updates. Run the setup.exe file of the Windows OS agent V6.2.2, Fix Pack 2 to install the 32/64-bit Agent Compatibility Pack (ACP). You can also reinstall the ACP from the 64-bit agent folder of ITCAM for Microsoft Applications V6.2.2. No action is required. You can ignore this message and continue with the installation. Table 15. General problems and solutions for uninstallation Problem Solution 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. The Cluster agent resource does not run on node. To uninstall the monitoring agent, use the procedure described in the IBM Tivoli Monitoring Installation and Setup Guide. 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. Chapter 9. Troubleshooting 279

Table 15. 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. 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 ITCAM for Microsoft Applications by using the following methods: v The silent_agent.txt file v The command: tacmd removesystem -t agentcode -n node For example, tacmd removesystem t qp n Primary:MachineName:NT v The Remove option on the Tivoli Enterprise 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. 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: v 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> 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. 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 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 installation and configuration, on page 7 to set CTIRA_HOSTNAME. Use the following steps to resolve this problem: 1. In the KGLWICMA.VER and KUIWICLI.VER files in the InstallITM/ver directory, lower the current VRMF values. For example, if the current value is 06220000, 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. Note: If IBM Tivoli Monitoring is not displayed in the Add or Remove Programs window, run the setup.exe file for ITCAM for Microsoft Applications to install the Tivoli Enterprise Monitoring Agent Framework. You can find the setup.exe file in the Agent_64bit\WINDOWS directory. 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. Remote deployment troubleshooting Problems can occur with remote deployment and removal of agent software using the Agent Remote Deploy process. Table 16 on page 281 contains problems and solutions related to remote deployment. 280 Microsoft Cluster Server agent: User's Guide

Table 16. Remote deployment problems and solutions Problem While you are using the remote deployment feature to install the Microsoft Cluster Server agent, an 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. The removal of a monitoring agent fails when you use the remote removal process in the Tivoli Enterprise Portal desktop or browser. A problem can arise when you try to operate the agent remotely while the agent cluster resource controlling the agent is online. Cannot remotely access the Microsoft Cluster Server agent on a cluster that does not own the agent cluster resource. The install.sh command from a UNIX or Linux CD does not allow you to populate an agent depot if the agent binaries do not exist on the CD. For example, the install.sh command from a UNIX CD does not allow you to populate the depot with Windows agent binaries, because the Windows binaries are on a separate CD, or in a separate location on the same CD. Solution Do not close or modify this window. It is part of the installation process and is dismissed automatically. 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 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. This problem might occur when you attempt the remote removal process immediately after you restart 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. 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 operating the agent remotely. When remote operations are complete, bring the agent cluster resource back online. 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 bring the agent cluster resource back online. Use the tacmd addbundles command to populate the depot for binaries on different CDs. For example, to populate a UNIX or Linux depot with Windows binaries for the IBM Tivoli Monitoring for Cluster Managers: Microsoft Cluster Servers Agent, use the following command: $ tacmd addbundles -i /q5v610a4.final/image/ WINDOWS/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 : Monitoring Agent for Microsoft Cluster Server Host : WINNT Host Version : WINNT Prerequisites: KUICAB024I: Enter Y for yes or N for no: Y Chapter 9. Troubleshooting 281

Table 16. Remote deployment problems and solutions (continued) Problem Solution 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 installation and configuration, on page 7 in this guide. For the section name, CTIRA_HOSTNAME, the configuration parameter for remote deploy is as follows: section.configparameter 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: 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 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" No solution is available for this problem at this time. The agent does not display the data on Windows Server 2003 and Windows Server 2008 for the above mentioned attribute groups. 282 Microsoft Cluster Server agent: User's Guide

Table 16. Remote deployment problems and solutions (continued) Problem Solution Remote installation (CLI and GUI) of Microsoft Cluster Server agent fails on IPv6 network. The agent gets installed on a computer but fails to configure and start. The agent appears offline on the Tivoli Enterprise You must reconfigure the Microsoft Cluster Server agent to Tivoli Enterprise Monitoring Server. To reconfigure the Microsoft Cluster Server agent, use the following steps: 1. Open the Manage Tivoli Enterprise Monitoring Services window. 2. Right-click Microsoft Cluster Server agent that you want to configure with the IPv6 network, and then click Advanced. 3. Click Edit Variable. The following message is displayed: The service must be stopped before editing variables. Do you want to stop the service now? 4. Click Yes. The Edit Variable window opens. 5. Click Add. 6. Enter the following details in the respective fields: v Variable Name: CT_CMSLIST v Variable Value: IP6.PIPE:ITM-IPV6;IP6.PIPE:<IP of the TEMS machine>. For example: IP6.PIPE:ITM-IPV6;IP6.PIPE: FE80::215:5DFF:FE44:4012 7. Click Ok. 8. Right-click Microsoft Cluster Server agent and then click Start. Agent troubleshooting A problem can occur with the agent after it has been installed. Table 17 contains problems and solutions that can occur with the agent after it has been installed. Table 17. Agent problems and solutions Problem Log data accumulates too rapidly. Multicast warning messages from the Cluster Network Driver (Clusnet.sys) appear in the Windows system log. Solution Check the RAS trace option settings, which are described in Setting RAS trace parameters by using the GUI on page 274. The trace option settings that you can set on the KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data. To troubleshoot multicast cluster issues check the following article in the Microsoft Knowledge Base: Multicast support enabled for the cluster heartbeat (http://support.microsoft.com/kb/307962/). Chapter 9. Troubleshooting 283

Table 17. Agent problems and solutions (continued) Problem Solution 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. Warning messages from ClusSvc concerning 'The node lost communication with cluster node ComputerName on network xx.' Rollup Error messages in the agent log file. 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. Restart 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.) 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. See the following Microsoft support article: Overview of event ID 1123 and event ID 1122 logging in Windows 2000-based and Windows Server 2003-based server clusters Rollup error messages occur when a base WMI query fails and no source data is available to "roll up." Check the log for the initial WMI error to resolve. The rollup error disappears when the initial problem is corrected. 284 Microsoft Cluster Server agent: User's Guide

Table 17. Agent problems and solutions (continued) Problem WMI Error 0x80041006 There was not enough memory for the operation. OR WMIPrsve.exe memory increases to 135MB before recycling. Solution The issue is a known issue with the Microsoft WMI Cluster Association class provider, which IBM Software Support is 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 timeout to 30 seconds. So, if the cluster provider is idle for more than 30 seconds, the hosting WMIprvse.exe process is recycled, minimizing the effect of the leak. 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. '===[ 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 where the agent is running. 3. Restart the system. If the problem persists (which typically happens if there are multiple objects querying WMI, such as a second agent), try reducing the cache time from 25 seconds to a lower value. Chapter 9. Troubleshooting 285

Table 17. Agent problems and solutions (continued) Problem Agent log files are not in the CANDLEHOME/tmaitm6/logs directory. Solution If you reset the logging level to "none," and then turn 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. -OR- Failover Cluster Management changed to Failover Cluster Manager. You 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 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. 286 Microsoft Cluster Server agent: User's Guide

Table 17. Agent problems and solutions (continued) Problem 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 are displayed in the portal. Solution IBM Tivoli Monitoring products use Remote Procedure Call (RPC) to define and control product behavior. RPC is the mechanism that a client process uses 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 another type of monitoring server process. Two architectural limits result as a consequence of the physical port allocation method: v 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. 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, one Tivoli Enterprise Monitoring Server hub is available per monitoring enterprise, so this architecture limit has been reduced 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. Continued on next row. Chapter 9. Troubleshooting 287

Table 17. Agent problems and solutions (continued) Problem Continued from previous row. 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. 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. On the z/os operating system, while configuring all attributes in the History Collection Configuration window, if you select TEMS in the Collection Location field, the attribute group tables are not created in the Warehouse database. Solution 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). The number of ephemeral IP.PIPE connections per system image has no limitation. 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.) There are two possible solutions to this problem: Solution 1: Restart the 64-bit agent and then use the following steps to restart the AMS: 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 management that you want to start. 4. Click OK. Solution 2: Install the Windows OS agent V6.2.2, Fix Pack 2. Some local changes might require the agent to be taken offline. In these cases, you receive a warning prompt that states the agent must be taken offline to make these changes. 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 during operations requiring the agent to be offline. When the operations are complete, bring the agent cluster resource back online. In the History Collection Configuration window, select TEMA in the Collection Location field. 288 Microsoft Cluster Server agent: User's Guide

Table 17. Agent problems and solutions (continued) Problem In the xxxagent.exe Properties window, the following information is not updated: v Copyright v File Version v Product Version This problem occurs on both Windows 32-bit and 64-bit operating systems. Note: On Windows 2003 systems, the agent information is shown in the Version tab; however, on Windows 2008 systems, the agent information is shown in the Details tab. You have configured the monitoring agent version 6.3 on the Tivoli Enterprise Monitoring Server by using the self-describing agent feature. You are using IBM Tivoli Monitoring version 6.2.3 or version 6.2.3 Fix Pack 1. On the Tivoli Enterprise Portal, if you open a situation by using the Situation Editor and view the advance options for the situation, you can see <none selected> in the Display Item window. Resources/Resource Groups are unable to fetch data Solution There is no solution to this problem at this time. Recycle the Tivoli Enterprise Portal Server. Complete the following steps to recycle the Tivoli Enterprise Portal Server on Windows systems: 1. On the computer where the Tivoli Enterprise Portal Server is installed, click Start > Programs > Manage Tivoli Enterprise Monitoring Services. 2. Right-click the Tivoli Enterprise Portal Server service and click Recycle. To recycle the Tivoli Enterprise Portal Server on UNIX systems, use the following commands from the bin directory of /opt/ibm/itm (or where you have installed IBM Tivoli Monitoring) in the order shown below: v./itmcmd agent stop cq v./itmcmd agent start cq Remove special characters if any from the Resource/Resource Group names. Cluster Resources/Resource Groups must not contain special characters. As per Microsoft recommendations Cluster Resources can contain only A-Z, a-z, 0-9, spaces, and underscores Workspace troubleshooting Problems can occur with general workspaces and agent-specific workspaces. Table 18 on page 290 contains problems and solutions related to workspaces. Chapter 9. Troubleshooting 289

Table 18. Workspace problems and solutions Problem The process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE. No Data in Workspace View or Error code = 0x80041003 The current user does not have permission to perform the action in agent log. Links from The Microsoft Cluster Server agent views to other agent views do not populate data at the target workspace. Solution This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Use the following steps to confirm that this problem exists and to resolve it: 1. In the Windows Start menu, click Run. 2. perfmon.exe in the Open field of the Run window. The Performance window is displayed. 3. Click the plus sign (+) in the toolbar located above the right pane. The Add Counters window is displayed. 4. Look for Process in the Performance object menu. 5. Complete one of the following actions: v If you see Process in the menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM Software Support. v If you do not see Process in the menu, use the Microsoft utility from the Microsoft.com Operations website to enable the PerfProc performance object. The Process performance object becomes visible in the Performance object menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data. 6. Restart the monitoring agent. The agent must be started with a valid ID on all nodes of the cluster. On the computer running the agent, use 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. The link Symbol named NODE must be created to resolve the expression value. To create the link Symbol, go to the Expression page for the Link and click New at the end of the navigation tree. 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. 290 Microsoft Cluster Server agent: User's Guide

Table 18. Workspace problems and solutions (continued) Problem At the end of the historical view, you see the following error: KFWITM220E Request failed during execution. Expert Advice pages do not show in a Simplified Chinese environment situation editor. Message IDs are appearing in portal views instead of English text or the appropriate language text. Question marks show up for the cluster name configuration parameter and in the Host Name field of the Managed System Name. Solution 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. Select 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. This problem is caused by IBM JVM 1.4.2. Use the following 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. 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 -Or- 1. Shut down the Configuration tool. 2. Add Tivoli Enterprise Monitoring Server Application support for the agent. IBM Tivoli Monitoring V6.1 configuration support is available only in the English language. 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 Reconfigure the agent and enter a new ASCII English Cluster Name to resolve the issue. Chapter 9. Troubleshooting 291

Table 18. Workspace problems and solutions (continued) Problem 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. The name of the attribute does not display in a bar chart or graph view. At the end of each view, you see the following Historical workspace KFWITM220E error: Request failed during execution. Solution 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 variables are stored: 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 that 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. 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 sufficient space is available to display all characters of the attribute name. Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view. 292 Microsoft Cluster Server agent: User's Guide

Table 18. Workspace problems and solutions (continued) Problem You start collection of historical data but the data cannot be seen. Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Solution Use the following managing options for historical data collection: v v Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. For information about managing this feature including how to set the interval at which data is collected, see Managing historical data in the IBM Tivoli Monitoring Administrator's Guide. By setting a more frequent interval for data collection, you reduce the load on the system incurred every time data is uploaded. Use the Summarization and Pruning 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 a.m. daily. At that point, data is visible in the workspace view. For information about how to modify the default collection settings, see Managing historical data in the IBM Tivoli Monitoring Administrator's Guide. The Sort By, Group By, and First/Last functions column 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 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. When you use a long process name in the situation, the process name is truncated. For information about the historical data collection function, See Managing historical data in the IBM Tivoli Monitoring Administrator's Guide or the Tivoli Enterprise Portal online help. Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. The maximum name length is 100 bytes. Chapter 9. Troubleshooting 293

Table 18. Workspace problems and solutions (continued) 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. No row of data for 64-bit applications is 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 instead of the correct names (such as Disk), where XX and xx represent the two-character agent code. You have installed a 32-bit agent for ITCAM for Microsoft 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. If the 32-bit OS agent and a 64-bit Microsoft Application agent are installed on the same managed system, Agent Management Service data is not displayed in the Agent's Runtime Status view of the agent. The Agent's Runtime Status view is available in the Agent Management Services workspace. You have installed the Tivoli Enterprise Monitoring Server on z/os. In the Configuration 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 Performance Object Status v Event Log v v v v Check that a directory is present on the shared disk and that all the agents are configured to use that directory. Check for OpenHistoryFiles errors in the agent log to see if history files are created. If no shared disk is 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. If you have a hub and a remote Tivoli Enterprise Monitoring Server, start historical data collection correctly on that Tivoli Enterprise Monitoring Server. The Tivoli Enterprise Portal shows data only for 32-bit applications. No solution is available for this problem at this time. Ensure that application support has been added on the monitoring server, portal server, and portal client. For more information about installing application support, see Installing and enabling application support in the IBM Tivoli Monitoring Installation and Setup Guide. Upgrade the Windows OS agent from V6.2.2, Fix Pack 1 to V6.2.2, Fix Pack 2. No solution is available for this problem at this time. Reconfigure history collection, and set the collection location as TEMA for these attribute groups. 294 Microsoft Cluster Server agent: User's Guide

Table 18. Workspace problems and solutions (continued) Problem When the ITCAM for Microsoft Cluster Server agent collects data for the Quorum Configuration workspace on a Windows 2008 system, no values are displayed in the Quorum Configuration for Microsoft Windows 2003 view. Similarly, when the agent collects data on a Windows 2003 system, no values are displayed in the Quorum Configuration for Microsoft Windows 2008 view. On the Tivoli Enterprise Portal, when you open the Cluster Shared Volume workspace in the Cluster Dashboard navigator item, data is not always displayed for attribute groups of the Cluster Shared Volume workspace. Sometimes, the data is displayed, but sometimes the data is not displayed. Solution There is no solution to this problem. This problem is due to incorrect functioning of the WMI classes in Windows systems. There is no solution to this problem. Situation troubleshooting Problems can occur with situations and situation configuration. Table 19 contains problems and solutions for situations. Table 19. Situation problems and solutions Problem Monitoring activity requires too much disk space. Solution Check the RAS trace logging settings that are described in Setting RAS trace parameters by using the GUI on page 274. 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 221 describes the performance impact of specific attribute groups. If possible, decrease your use of the attribute groups that require greater system resources. 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. Click Situations in the menu. The Situation Editor window is displayed. 3. Select the situation that you want to modify. 4. Use the State 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. Chapter 9. Troubleshooting 295

Table 19. Situation problems and solutions (continued) Problem No event notification is given when a monitoring agent is down. Cannot create situations for Cluster Server entries in the Windows system log. 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. Solution By default, agent status is available in the Enterprise System Status workspace. However, by default, an event is not generated for a 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 v v v v v v v v v v Click Edit > Situation Editor > All Managed Systems > MS_Offline. Right-click Create another. Complete the following: Name: KQ5_MSCS_Agent_Down : The agent is not running. This can be either an agent or cluster failure. Click OK. Click Add conditions Click Product. Click OK. For Product, enter ==Q5. Click OK. Right-click Any managed system] > Situations. in the top left of the window, click 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. 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: 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 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 KpcENV file for the agent (where pc is the two-letter product code): CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600 This variable determines how long events from the NT Event Log are kept. 296 Microsoft Cluster Server agent: User's Guide

Table 19. Situation problems and solutions (continued) Problem 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. Associations of custom situations with navigator items break after upgrading the agent support. The situation for a specific agent is not visible in the Tivoli Enterprise The monitoring interval is too long. The situation did not activate at startup. The situation is not displayed. An Alert event did not occur even though the predicate was correctly specified. A situation fires on an unexpected managed object. The product did not distribute the situation to a managed system. Solution The external window responds after you close the Preview window and Situation Editor window. Create the associations again by completing the following steps: 1. Right-click the navigator item, and then click Situations. A list of situations that are associated with the navigator item is displayed. Note: If the custom situation that you want to associate is available in the list, ignore further steps. 2. Click Set Situation filter criteria. 3. Select the Eligible for Association check box, and then click OK. A list of situations is displayed. 4. Right-click the situation that you want to associate with the navigator item, and then click Associate. The situation is associated with the navigator item. Open the Situation Editor. Access the All managed servers view. If the situation is not displayed, confirm that the monitoring server has been seeded for the agent. If not, seed the server, as described in the IBM Tivoli Monitoring Installation and Setup Guide. 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 required. Manually recycle the situation as follows: 1. Right-click the situation and select Stop Situation. 2. Right-click the situation and select Start Situation. Note: You can permanently avoid this problem by selecting the Run at Startup check box of the Situation Editor view for a specific situation. 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. Check the logs, reports, and workspaces. Confirm that you distributed and started the situation on the correct managed system. Click the Distribution tab and check the distribution settings for the situation. Chapter 9. Troubleshooting 297

Table 19. Situation problems and solutions (continued) Problem The situation does not fire. Solution 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. 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. Situation events are not displayed in the Events Console view of the workspace. See the IBM Tivoli Monitoring Troubleshooting Guide for additional information about situations that do not fire. 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. 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. 298 Microsoft Cluster Server agent: User's Guide

Table 19. Situation problems and solutions (continued) Problem You do not have access to a situation. A managed system seems to be offline. Solution Note: You must have administrator privileges to complete these steps. 1. Click 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. 1. Select Physical View and click the Enterprise Level of the navigator tree. 2. Click 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 Problems can occur with Take Action commands. Table 20 contains problems and solutions that can occur with Take Action commands. When each Take Action command runs, it generates a log file listed in Table 13 on page 271. Table 20. Take Action commands problems and solutions Problem Take Action commands often require several minutes to complete. The Delete Resource Group Take Action command does not work on Windows Server 2003. Solution Allow several minutes. If you do not see a message advising you of completion, try to run the command manually. The Delete Resource Group Take Action command is not supported on Windows Server 2003. Tivoli Common Reporting troubleshooting Problems can occur with the Tivoli Common Reporting predefined reports for the Microsoft Cluster Server agent. Table 21 contains problems and solutions that can occur with the Tivoli Common Reporting predefined reports for IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. See the Tivoli Common Reporting Information Center (http://publib.boulder.ibm.com/ infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html) for more information about troubleshooting for the Tivoli Common Reporting tool. Table 21. Tivoli Common Reporting for Microsoft Cluster Server agent problems and solutions Problem Solution When you simultaneously query two tables in the Query Studio interface, no data is displayed. However, when you query the two tables separately, data is displayed. This problem occurs when a relationship between the tables is not defined. To resolve this problem, ensure that all the ad hoc queries have at least one identifier. Chapter 9. Troubleshooting 299

Table 21. Tivoli Common Reporting for Microsoft Cluster Server agent problems and solutions (continued) Problem Solution When you create an ad hoc query by dragging some columns in the Query Studio interface, the following error message is displayed: RQP-DEF-0177 An error occurred while performing operation sqlpreparewithoptions status= -232. If a view or a table for the selected summarization type does not exist in the database for a report, the report does not open and the following error message is displayed: RQP-DEF-0177 An error occurred while performing operation sqlpreparewithoptions status= -56. When you run a report, the report is not displayed in the correct format and the following error message is displayed: RQP-DEF-0177 An error occurred while performing operation sqlpreparewithoptions status= -16. If data is not available in the database for the selected parameters, the following error message is displayed after querying these parameters: Empty data set No data returned by query. Try another set of parameters. Reports are not generated correctly in the Microsoft Excel format. When you view a report spanning multiple pages in the PDF format, the report parameters section is displayed at the top of each page. Charts are not displayed correctly in Microsoft Excel 2007. Labels for some charts are displayed in the HTML output, but are not displayed in the PDF output. This is an SQL error related to arithmetic flow. This error is generated because the average or the sum for certain columns is more than the threshold size that is defined in the database. To resolve this error, use the limited columns and add a standard timestamp while creating an ad hoc query. To resolve this problem, complete the following tasks: v Verify that the summarization and pruning agent is working correctly. v Generate data for all the summarization types. v Verify that the warehouse is collecting historical data. This problem occurs due to incorrect data source. To resolve this problem, complete the following tasks: v v Verify that the datasource configuration parameters are configured correctly. Verify that the specified values for the parameters of the summarization and pruning agent such as database URL, driver user, and password match with the values of these parameters on the database. To resolve this error, complete the following tasks: v Configure the summarization and pruning agent and verify that it is working correctly. v Generate data for all the summarization types in the database. There are some limitations to generate reports in the Microsoft Excel format. To view these limitations, see the IBM Cognos Business Intelligence Information Center (http://publib.boulder.ibm.com/infocenter/cbi/ v10r1m0/topic/ com.ibm.swg.im.cognos.ug_cr_rptstd.10.1.0.doc/ ug_cr_rptstd_id32474excel_limitations.html). No solution is available for this problem at this time. No solution is available for this problem at this time. The font size is rendered differently in the HTML and the PDF output. In the PDF output, some fonts are not displayed because of the large font size. To resolve this issue, reduce the font size by completing the following steps: 1. Open the report in Report Studio. 2. Click the chart. 3. In the chart properties, select Font. 4. Modify the font properties, such as family, size, weight, and style. 5. Save the settings, and run the report in the PDF format. 300 Microsoft Cluster Server agent: User's Guide

Table 21. Tivoli Common Reporting for Microsoft Cluster Server agent problems and solutions (continued) Problem If you drag some columns to the report area during an ad hoc query, the following error message is displayed: UDA-SQL-0115 Inappropriate SQL request.uda-sql-0564 [Microsoft OLE DB Provider for SQL Server]Deferred prepare could not be completed.uda-sql-0564 [Microsoft OLE DB Provider for SQL Server]Statement(s) could not be prepared. (SQLSTATE=42000, SQLERRORCODE=8180) UDA-SQL-0564 [Microsoft OLE DB Provider for SQL Server]Invalid column name '<column name>'. (SQLSTATE=42S22, SQLERRORCODE=207) The ad hoc query does not work for the following columns: v SUM_Cache_State v MIN_Cache_State v MAX_Cache_State v AVG_Cache_State v SUM_Volume_State v MIN_Volume_State v MAX_Volume_State v AVG_Volume_State Solution No solution is available for this problem at this time. 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 websites contain troubleshooting information: v Go to the IBM Software Support website (http://www.ibm.com/support/entry/portal/ software) and follow the instructions. v Go to the Application Performance Management Wiki (http://www.ibm.com/developerworks/ servicemanagement/apm/index.html). 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 the IBM Support Assistant website (http://www.ibm.com/software/support/isa). Informational, warning, and error messages overview 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 actions: 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 topic to see what action you can take to correct the problem. Chapter 9. Troubleshooting 301

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 The message format contains a message ID and text, an explanation, and an operator response. IBM Tivoli Composite Application Manager for Microsoft Applications: 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: CCC Prefix that indicates the component to which the message applies. The following components are used: KQ5 General Microsoft Cluster Server agent messages #### Number of the message severity Severity of the message. Three levels of severity are used: I W E 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 the possible cause for 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 topic as symbols, such as "&1." Actual messages contain values for these variables. Agent messages The following messages apply to IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. KQ50001I The Resource is brought online. Explanation: The Resource is brought online. Operator response: None. 302 Microsoft Cluster Server agent: User's Guide

KQ50002I The Resource is already running. Explanation: The Resource is already running. Operator response: None. KQ50003E Error bringing the resource online. Explanation: Error bringing the resource online. Operator response: None. KQ50004I Time-out occurred bringing resource online. Explanation: Time-out occurred bringing resource online. Operator response: None. KQ50005I The Resource is taken offline. Explanation: The Resource is taken offline. Operator response: None. KQ50006I The Resource is already offline. Explanation: The Resource is already offline. Operator response: None. KQ50004E Error taking the resource offline. Explanation: Error taking the resource offline. Operator response: None. KQ50007I Time-out occurred taking resource offline. Explanation: Time-out occurred taking resource offline. Operator response: None. KQ50008I The Resource Group is brought online. Chapter 9. Troubleshooting 303

Explanation: The Resource Group is brought online. Operator response: None. KQ50009I The Resource Group is already running. Explanation: The Resource Group is already running. Operator response: None. KQ500010E Error bringing the Resource Group online. Explanation: Error bringing the Resource Group online Operator response: None. KQ500011I Time-out occurred bringing Resource Group online. Explanation: The preset time to bring the Resource Group online has timed out. Operator response: None. KQ500012I The Resource Group is taken offline. Explanation: The Resource Group is taken offline. Operator response: None. KQ500013I The Resource Group is already offline. Explanation: The Resource Group is already offline. Operator response: None. KQ500014E Error bringing the Resource Group offline. Explanation: Error bringing the Resource Group offline. Operator response: None. KQ500015I The preset time to take the Resource Group offline has timed out. Explanation: Time-out occurred bringing Resource Group offline. 304 Microsoft Cluster Server agent: User's Guide

Operator response: None. KQ500021I The Node is resumed. Explanation: The Node is resumed. Operator response: None. KQ500022I The Node is already running. Explanation: The Node is already running. Operator response: None. KQ500023E Error in resuming the Node. Explanation: Error in resuming the Node. Operator response: None. KQ500024I Time-out occurred in resuming Node. Explanation: Time-out occurred in resuming Node. Operator response: None. KQ500025I The Node is paused. Explanation: The Node is paused. Operator response: None. KQ500026I The Node is already paused. Explanation: The Node is already paused. Operator response: None. KQ500027E Error in pausing the Node. Explanation: Error in pausing the Node. Operator response: None. Chapter 9. Troubleshooting 305

KQ500028I Time-out occurred in pausing Node. Explanation: Time-out occurred in pausing Node. Operator response: None. KQ50100W Operation unsuccessful. Explanation: Operation unsuccessful. Operator response: None. KQ500029I The Resource Group is moved. Explanation: The Resource Group is moved. Operator response: None. KQ500030I This Resource Group does not exist in cluster. Explanation: This Resource Group does not exist in cluster. Operator response: None. KQ500031E No eligible node found for moving Resource Group. Explanation: No eligible node found for moving Resource Group. Operator response: None. KQ500032I Time-out occurred in moving Resource Group. Explanation: Time-out occurred in moving Resource Group. Operator response: None. KQ500039I This Node does not exist in cluster. Explanation: This Node does not exist in cluster. Operator response: None. KQ500040I Given Node is not preferred node for this resource group. 306 Microsoft Cluster Server agent: User's Guide

Explanation: Given Node is not preferred node for this resource group. Operator response: None. KQ500033I The Resource Group is deleted. Explanation: The Resource Group is deleted. Operator response: None. KQ500034I This Resource Group does not exist in cluster. Explanation: This Resource Group does not exist in cluster. Operator response: None. KQ500035E Unable to delete Resource Group. Explanation: Unable to delete Resource Group. Operator response: None. KQ500036I Time-out occurred in deleting Resource Group. Explanation: Time-out occurred in deleting Resource Group. Operator response: None. KQ500038I Delete Resource Group is not supported on any Windows 2003 edition. Explanation: Delete Resource Group is not supported on any Windows 2003 edition. Operator response: None. KQ50101W This Node does not exist in cluster. Explanation: This Node does not exist in cluster. Operator response: None. Chapter 9. Troubleshooting 307

308 Microsoft Cluster Server agent: User's Guide

Appendix A. Event mapping The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to Tivoli Netcool/OMNIbus or Tivoli Enterprise Console. EIF events specify an event class, and the event data is specified as name-value pairs that identify the name of an event slot and the value for the slot. An event class can have subclasses. IBM Tivoli Monitoring provides the base event class definitions and a set of base slots that are included in all monitoring events. Agents extend the base event classes to define subclasses that include agent-specific slots. For Microsoft Cluster Server agent events, the event classes correspond to the agent attribute groups, and the agent-specific slots correspond to the attributes in the attribute group. The situation editor in the Tivoli Enterprise Portal can be used to perform custom mapping of data to EIF slots instead of using the default mapping described in this topic. For more information about EIF slot customization, see the Tivoli Enterprise Portal User's Guide. Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorder of Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agent and is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/ TECLIB for Windows systems and install_dir/tables/tems_hostname/teclib for UNIX systems) when application support for the agent is installed. The BAROC file for the agent and the base BAROC files provided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see Setting up event forwarding to Tivoli Enterprise Console in the IBM Tivoli Monitoring Installation and Setup Guide. Each of the event classes is a child of KQ5_Base and is defined in the kq5.baroc (version vnext) file. The KQ5_Base event class can be used for generic rules processing for any event from the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. For events that are generated by situations in the Availability attribute group, events are sent by using the ITM_KQ5_AVAILABILITY event class. This event 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 page_faults_per_sec: INTEGER v working_set_size: INTEGER v thread_count: INTEGER v pid: INTEGER v percent_privileged_time: INTEGER Copyright IBM Corp. 2008, 2013 309

v percent_user_mode_time: INTEGER v percent_processor_time: INTEGER v command_line: STRING v command_line_enum: STRING v functionality_test_status: INTEGER v functionality_test_status_enum: STRING v functionality_test_message: STRING v functionality_test_message_enum: STRING For events that are generated by situations in the CAU Configuration attribute group, events are sent by using the ITM_KQ5_CAU_CONFIGURATION event class. This event class contains the following slots: v node: STRING v timestamp: STRING v resource_group_name: STRING v owner_node: STRING v kq5_status: STRING v start_date: STRING v cau_plugin_name: STRING v cau_plugin_arguments: STRING v node_order: STRING v max_retries_per_node: INTEGER v max_retries_per_node_enum: STRING v max_failed_nodes: INTEGER v max_failed_nodes_enum: STRING v require_all_nodes_online: STRING v warn_after: STRING v stop_after: STRING v reboot_timeout_minutes: INTEGER v reboot_timeout_minutes_enum: STRING v enable_firewall_rules: STRING v days_of_week: STRING v weeks_of_month: STRING v interval_weeks: STRING v preupdate_script: STRING v postupdate_script: STRING v configuration_name: STRING For events that are generated by situations in the CAU Last Run attribute group, events are sent by using the ITM_KQ5_CAU_LAST_RUN event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v run_completion_time: STRING v run_id: STRING v kq5_duration: STRING v installed_updates: INTEGER 310 Microsoft Cluster Server agent: User's Guide

v installed_updates_enum: STRING v failed_updates: INTEGER v failed_updates_enum: STRING v canceled_updates: INTEGER v canceled_updates_enum: STRING v update_run_status: STRING v node_name: STRING v result: STRING v update_id: STRING v update_title: STRING v update_timestamp: STRING v update_description: STRING v error_code: INTEGER v error_code_enum: STRING For events that are generated by situations in the Cluster Domain attribute group, events are sent by using the ITM_KQ5_CLUSTER_DOMAIN event class. This event class contains the following slots: v node: STRING v timestamp: STRING v domain: STRING For events that are generated by situations in the Cluster Shared Volume attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME event class. This event 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 csvresourcename: STRING v csvresourcestate: INTEGER v csvresourcestate_enum: STRING v csvnodename: STRING v backupstate: INTEGER v backupstate_enum: STRING v description: STRING v faultstate: INTEGER v faultstate_enum: STRING For events that are generated by situations in the Cluster Shared Volume Block Redirection attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_BLOCK_REDIRECTION event class. This event class contains the following slots: v node: STRING v timestamp: STRING v io_read_bytes: REAL v io_read_bytes_enum: STRING Appendix A. Event mapping 311

v io_read_mb: REAL v io_read_mb_enum: STRING v io_read_bytes_per_sec: REAL v io_read_bytes_per_sec_enum: STRING v io_read_kb_per_sec: REAL v io_read_kb_per_sec_enum: STRING v io_reads: REAL v io_reads_enum: STRING v io_reads_per_sec: REAL v io_reads_per_sec_enum: STRING v io_write_bytes: REAL v io_write_bytes_enum: STRING v io_write_mb: REAL v io_write_mb_enum: STRING v io_write_bytes_per_sec: REAL v io_write_bytes_per_sec_enum: STRING v io_write_kb_per_sec: REAL v io_write_kb_per_sec_enum: STRING v io_writes: REAL v io_writes_enum: STRING v io_writes_per_sec: REAL v io_writes_per_sec_enum: STRING v name: STRING For events that are generated by situations in the Cluster Shared Volume Cache attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_CACHE event class. This event class contains the following slots: v node: STRING v timestamp: STRING v cache_io_read_bytes: REAL v cache_io_read_bytes_enum: STRING v cache_io_read_mb: REAL v cache_io_read_mb_enum: STRING v cache_io_read_bytes_per_sec: REAL v cache_io_read_bytes_per_sec_enum: STRING v cache_io_read_kb_per_sec: REAL v cache_io_read_kb_per_sec_enum: STRING v cache_read: REAL v cache_read_enum: STRING v cache_read_per_sec: REAL v cache_read_per_sec_enum: STRING v cache_size_configured: REAL v cache_size_configured_enum: STRING v cache_size_current: REAL v cache_size_current_enum: STRING v percent_current_csv_cache_size: REAL 312 Microsoft Cluster Server agent: User's Guide

v percent_current_csv_cache_size_enum: STRING v cache_state: INTEGER v cache_state_enum: STRING v disk_io_read_bytes: REAL v disk_io_read_bytes_enum: STRING v disk_io_read_mb: REAL v disk_io_read_mb_enum: STRING v disk_io_read_bytes_per_sec: REAL v disk_io_read_bytes_per_sec_enum: STRING v disk_io_read_kb_per_sec: REAL v disk_io_read_kb_per_sec_enum: STRING v disk_io_reads: REAL v disk_io_reads_enum: STRING v disk_io_reads_per_sec: REAL v disk_io_reads_per_sec_enum: STRING v io_read_bytes: REAL v io_read_bytes_enum: STRING v io_read_mb: REAL v io_read_mb_enum: STRING v io_read_bytes_per_sec: REAL v io_read_bytes_per_sec_enum: STRING v io_read_kb_per_sec: REAL v io_read_kb_per_sec_enum: STRING v io_reads: REAL v io_reads_enum: STRING v io_reads_per_sec: REAL v io_reads_per_sec_enum: STRING v lru_cache_size_current: REAL v lru_cache_size_current_enum: STRING v lru_cache_size_target: REAL v lru_cache_size_target_enum: STRING v partial_read: REAL v partial_read_enum: STRING v partial_read_per_sec: REAL v partial_read_per_sec_enum: STRING v name: STRING For events that are generated by situations in the Cluster Shared Volume Coordinator attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_COORDINATOR event class. This event class contains the following slots: v node: STRING v timestamp: STRING v create_file: REAL v create_file_enum: STRING v create_file_per_sec: REAL v create_file_per_sec_enum: STRING Appendix A. Event mapping 313

v io_read_bytes: REAL v io_read_bytes_enum: STRING v io_read_mb: REAL v io_read_mb_enum: STRING v io_read_bytes_per_sec: REAL v io_read_bytes_per_sec_enum: STRING v io_read_kb_per_sec: REAL v io_read_kb_per_sec_enum: STRING v io_reads: REAL v io_reads_enum: STRING v io_reads_per_sec: REAL v io_reads_per_sec_enum: STRING v io_write_bytes_per_sec: REAL v io_write_bytes_per_sec_enum: STRING v io_write_kb_per_sec: REAL v io_write_kb_per_sec_enum: STRING v io_writes: REAL v io_writes_enum: STRING v io_writes_per_sec: REAL v io_writes_per_sec_enum: STRING v io_writes_bytes: REAL v io_writes_bytes_enum: STRING v io_writes_mb: REAL v io_writes_mb_enum: STRING v metadata_io: REAL v metadata_io_enum: STRING v metadata_io_per_sec: REAL v metadata_io_per_sec_enum: STRING v name: STRING For events that are generated by situations in the Cluster Shared Volume File System attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_FILE_SYSTEM event class. This event class contains the following slots: v node: STRING v timestamp: STRING v create_file: REAL v create_file_enum: STRING v create_file_per_sec: REAL v create_file_per_sec_enum: STRING v files_invalidated_during_resume: REAL v files_invalidated_during_resume_enum: STRING v files_invalidated_other: REAL v files_invalidated_other_enum: STRING v files_opened: REAL v files_opened_enum: STRING v flushes: REAL 314 Microsoft Cluster Server agent: User's Guide

v flushes_enum: STRING v flushes_per_sec: REAL v flushes_per_sec_enum: STRING v io_read_avg_queue_length: REAL v io_read_avg_queue_length_enum: STRING v io_read_bytes: REAL v io_read_bytes_enum: STRING v io_read_mb: REAL v io_read_mb_enum: STRING v io_read_bytes_per_sec: REAL v io_read_bytes_per_sec_enum: STRING v io_read_kb_per_sec: REAL v io_read_kb_per_sec_enum: STRING v io_read_latency: REAL v io_read_latency_enum: STRING v io_read_queue_length: REAL v io_read_queue_length_enum: STRING v io_reads: REAL v io_reads_enum: STRING v io_reads_per_sec: REAL v io_reads_per_sec_enum: STRING v io_single_reads: REAL v io_single_reads_enum: STRING v io_single_reads_per_sec: REAL v io_single_reads_per_sec_enum: STRING v io_single_writes: REAL v io_single_writes_enum: STRING v io_single_writes_per_sec: REAL v io_single_writes_per_sec_enum: STRING v io_split_reads: REAL v io_split_reads_enum: STRING v io_split_reads_per_sec: REAL v io_split_reads_per_sec_enum: STRING v io_split_writes: REAL v io_split_writes_enum: STRING v io_split_writes_per_sec: REAL v io_split_writes_per_sec_enum: STRING v io_write_avg_queue_length: REAL v io_write_avg_queue_length_enum: STRING v io_write_bytes: REAL v io_write_bytes_enum: STRING v io_write_mb: REAL v io_write_mb_enum: STRING v io_write_bytes_per_sec: REAL v io_write_bytes_per_sec_enum: STRING Appendix A. Event mapping 315

v io_write_kb_per_sec: REAL v io_write_kb_per_sec_enum: STRING v io_write_latency: REAL v io_write_latency_enum: STRING v io_write_queue_length: REAL v io_write_queue_length_enum: STRING v io_writes: REAL v io_writes_enum: STRING v io_writes_per_sec: REAL v io_writes_per_sec_enum: STRING v metadata_io: REAL v metadata_io_enum: STRING v metadata_io_per_sec: REAL v metadata_io_per_sec_enum: STRING v read_latency: REAL v read_latency_enum: STRING v read_queue_length: REAL v read_queue_length_enum: STRING v reads: REAL v reads_enum: STRING v reads_per_sec: REAL v reads_per_sec_enum: STRING v redirected_read_bytes: REAL v redirected_read_bytes_enum: STRING v redirected_read_kilobytes: REAL v redirected_read_kilobytes_enum: STRING v redirected_read_bytes_per_sec: REAL v redirected_read_bytes_per_sec_enum: STRING v redirected_read_kb_per_sec: REAL v redirected_read_kb_per_sec_enum: STRING v redirected_read_latency: REAL v redirected_read_latency_enum: STRING v redirected_read_queue_length: REAL v redirected_read_queue_length_enum: STRING v redirected_reads: REAL v redirected_reads_enum: STRING v redirected_reads_per_sec: REAL v redirected_reads_per_sec_enum: STRING v redirected_reads_avg_queue_length: REAL v redirected_reads_avg_queue_length_enum: STRING v redirected_write_bytes: REAL v redirected_write_bytes_enum: STRING v redirected_write_kb: REAL v redirected_write_kb_enum: STRING v redirected_write_bytes_per_sec: REAL 316 Microsoft Cluster Server agent: User's Guide

v redirected_write_bytes_per_sec_enum: STRING v redirected_write_kb_per_sec: REAL v redirected_write_kb_per_sec_enum: STRING v redirected_write_latency: REAL v redirected_write_latency_enum: STRING v redirected_write_queue_length: REAL v redirected_write_queue_length_enum: STRING v redirected_writes: REAL v redirected_writes_enum: STRING v redirected_writes_per_sec: REAL v redirected_writes_per_sec_enum: STRING v redirected_writes_avg_queue_length: REAL v redirected_writes_avg_queue_length_enum: STRING v volume_pause_count_disk: REAL v volume_pause_count_disk_enum: STRING v volume_pause_count_network: REAL v volume_pause_count_network_enum: STRING v volume_pause_count_other: REAL v volume_pause_count_other_enum: STRING v volume_pause_count_total: REAL v volume_pause_count_total_enum: STRING v volume_state: INTEGER v volume_state_enum: STRING v write_latency: REAL v write_latency_enum: STRING v write_queue_length: REAL v write_queue_length_enum: STRING v writes: REAL v writes_enum: STRING v writes_per_sec: REAL v writes_per_sec_enum: STRING v name: STRING For events that are generated by situations in the Cluster Shared Volume IO attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_IO event class. This event class contains the following slots: v node: STRING v timestamp: STRING v io_read_bytes: INTEGER v io_read_bytes_enum: STRING v io_reads: INTEGER v io_reads_enum: STRING v io_write_bytes: INTEGER v io_write_bytes_enum: STRING v io_writes: INTEGER v io_writes_enum: STRING Appendix A. Event mapping 317

v metadata_io: INTEGER v metadata_io_enum: STRING v redirected_read_bytes: INTEGER v redirected_read_bytes_enum: STRING v redirected_reads: INTEGER v redirected_reads_enum: STRING v redirected_write_bytes: INTEGER v redirected_write_bytes_enum: STRING v redirected_writes: INTEGER v redirected_writes_enum: STRING v name: STRING For events that are generated by situations in the Cluster Shared Volume Manager attribute group, events are sent by using the ITM_KQ5_CLUSTER_SHARED_VOLUME_MANAGER event class. This event class contains the following slots: v node: STRING v timestamp: STRING v direct_io_failure_redirection: REAL v direct_io_failure_redirection_enum: STRING v direct_io_failure_redirection_per_sec: REAL v direct_io_failure_redirection_per_sec_enum: STRING v io_read_per_sec_redirected: REAL v io_read_per_sec_redirected_enum: STRING v io_read_bytes: REAL v io_read_bytes_enum: STRING v io_read_mb: REAL v io_read_mb_enum: STRING v io_read_bytes_per_sec: REAL v io_read_bytes_per_sec_enum: STRING v io_read_kb_per_sec: REAL v io_read_kb_per_sec_enum: STRING v io_read_bytes_per_sec_redirected: REAL v io_read_bytes_per_sec_redirected_enum: STRING v io_read_kb_per_sec_redirected: REAL v io_read_kb_per_sec_redirected_enum: STRING v io_read_bytes_redirected: REAL v io_read_bytes_redirected_enum: STRING v io_read_kb_redirected: REAL v io_read_kb_redirected_enum: STRING v io_reads: REAL v io_reads_enum: STRING v io_reads_per_sec: REAL v io_reads_per_sec_enum: STRING v io_reads_redirected: REAL v io_reads_redirected_enum: STRING v io_write_bytes: REAL 318 Microsoft Cluster Server agent: User's Guide

v io_write_bytes_enum: STRING v io_write_mb: REAL v io_write_mb_enum: STRING v io_write_bytes_per_sec: REAL v io_write_bytes_per_sec_enum: STRING v io_write_kb_per_sec: REAL v io_write_kb_per_sec_enum: STRING v io_write_bytes_per_sec_redirected: REAL v io_write_bytes_per_sec_redirected_enum: STRING v io_write_kb_per_sec_redirected: REAL v io_write_kb_per_sec_redirected_enum: STRING v io_write_bytes_redirected: REAL v io_write_bytes_redirected_enum: STRING v io_write_kb_redirected: REAL v io_write_kb_redirected_enum: STRING v io_writes: REAL v io_writes_enum: STRING v io_writes_per_sec: REAL v io_writes_per_sec_enum: STRING v io_writes_per_sec_redirected: REAL v io_writes_per_sec_redirected_enum: STRING v io_writes_redirected: REAL v io_writes_redirected_enum: STRING v name: STRING For events that are generated by situations in the Cluster Summary attribute group, events are sent by using the ITM_KQ5_CLUSTER_SUMMARY event class. This event 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 quorum_total_size_enum: STRING v quorum_utilization: INTEGER v quorum_utilization_enum: STRING Appendix A. Event mapping 319

v quorum_available: INTEGER v quorum_available_enum: STRING v percentage_quorum_used: INTEGER v percentage_quorum_used_enum: STRING v percentage_quorum_free: INTEGER v percentage_quorum_free_enum: STRING v shared_storage_available: INTEGER v shared_storage_available_enum: STRING v shared_storage_total_size: INTEGER v shared_storage_total_size_enum: STRING v shared_storage_utilization: INTEGER v shared_storage_utilization_enum: STRING v percentage_shared_storage_used: INTEGER v percentage_shared_storage_used_enum: STRING v percentage_shared_storage_free: INTEGER v percentage_shared_storage_free_enum: STRING v total_shared_storage: INTEGER v total_shared_storage_enum: STRING v network_utilization: INTEGER v network_utilization_enum: STRING v domain: STRING For events that are generated by situations in the Cluster Topology attribute group, events are sent by using the ITM_KQ5_CLUSTER_TOPOLOGY event class. This event class contains the following slots: v node: STRING v timestamp: STRING v node_name: STRING v node_id: STRING v node_type: STRING v node_status: STRING v connect_to_node: STRING v connection_type: STRING For events that are generated by situations in the Configuration attribute group, events are sent by using the ITM_KQ5_CONFIGURATION event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v max_number_nodes: INTEGER v max_number_nodes_enum: STRING v default_network_role: INTEGER v default_network_role_enum: STRING v description: STRING For events that are generated by situations in the CPU Interrupts Rollup attribute group, events are sent by using the ITM_KQ5_CPU_INTERRUPTS_ROLLUP event class. This event class contains the following slots: 320 Microsoft Cluster Server agent: User's Guide

v node: STRING v timestamp: STRING v maximum: INTEGER v maximum_enum: STRING v minimum: INTEGER v minimum_enum: STRING v average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the CPU per Node attribute group, events are sent by using the ITM_KQ5_CPU_PER_NODE event class. This event class contains the following slots: 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 v percent_idle_time: INTEGER v percent_idle_time_enum: STRING v percent_processor_time: INTEGER v percent_processor_time_enum: STRING v percent_user_time: INTEGER v percent_user_time_enum: STRING v percent_privileged_time: INTEGER v percent_privileged_time_enum: STRING For events that are generated by situations in the CPU per Node Rollup attribute group, events are sent by using the ITM_KQ5_CPU_PER_NODE_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER Appendix A. Event mapping 321

v standard_deviation_enum: STRING For events that are generated by situations in the Degradation Risk attribute group, events are sent by using the ITM_KQ5_DEGRADATION_RISK event class. This event class contains the following slots: v node: STRING v timestamp: STRING v node_min_capacity: STRING v min_capacity: INTEGER v min_capacity_enum: STRING v node_max_capacity: STRING v max_capacity: INTEGER v max_capacity_enum: STRING v node_min_util: STRING v min_util: INTEGER v min_util_enum: STRING v node_max_util: STRING v max_util: INTEGER v max_util_enum: STRING v total_capacity: INTEGER v total_capacity_enum: STRING v current_capacity: INTEGER v current_capacity_enum: STRING v degraded_capacity: INTEGER v degraded_capacity_enum: STRING v total_util: INTEGER v total_util_enum: STRING v uniform_commitment: INTEGER v uniform_commitment_enum: STRING v unitary_commitment: INTEGER v unitary_commitment_enum: STRING For events that are generated by situations in the Disk attribute group, events are sent by using the ITM_KQ5_DISK event class. This event 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 percent_disk_read_time_enum: STRING v freemegabytes: INTEGER v freemegabytes_enum: STRING v disk_write_bytes: INTEGER 322 Microsoft Cluster Server agent: User's Guide

v disk_write_bytes_enum: STRING v disk_writes: INTEGER v disk_writes_enum: STRING v disk_read_bytes: INTEGER v disk_read_bytes_enum: STRING v disk_reads: INTEGER v disk_reads_enum: STRING v current_disk_queue: INTEGER v current_disk_queue_enum: STRING v disk_transfers: INTEGER v disk_transfers_enum: STRING v disk_used_percent: INTEGER v disk_write_mb: INTEGER v disk_read_mb: INTEGER For events that are generated by situations in the Disk MB Rollup attribute group, events are sent by using the ITM_KQ5_DISK_MB_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Disk PCT Rollup attribute group, events are sent by using the ITM_KQ5_DISK_PCT_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING Appendix A. Event mapping 323

For events that are generated by situations in the Enterprise Cluster Summary attribute group, events are sent by using the ITM_KQ5_ENTERPRISE_CLUSTER_SUMMARY event class. This event 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 quorum_total_size_enum: STRING v quorum_utilization: INTEGER v quorum_utilization_enum: STRING v quorum_available: INTEGER v quorum_available_enum: STRING v percentage_quorum_used: INTEGER v percentage_quorum_used_enum: STRING v percentage_quorum_free: INTEGER v percentage_quorum_free_enum: STRING v shared_storage_available: INTEGER v shared_storage_available_enum: STRING v shared_storage_total_size: INTEGER v shared_storage_total_size_enum: STRING v shared_storage_utilization: INTEGER v shared_storage_utilization_enum: STRING v percentage_shared_storage_used: INTEGER v percentage_shared_storage_used_enum: STRING v percentage_shared_storage_free: INTEGER v percentage_shared_storage_free_enum: STRING v total_shared_storage: INTEGER v total_shared_storage_enum: STRING v network_utilization: INTEGER v network_utilization_enum: STRING v domain: STRING For events that are generated by situations in the Event Log attribute group, events are sent by using the ITM_KQ5_EVENT_LOG event class. This event class contains the following slots: v node: STRING 324 Microsoft Cluster Server agent: User's Guide

v log_name: STRING v event_source: STRING v event_type: INTEGER v event_type_enum: STRING v event_id: INTEGER v event_category: STRING v event_category_enum: STRING v message: STRING v time_generated: STRING v event_level: STRING v event_level_enum: STRING v event_keywords: STRING v event_keywords_enum: STRING v event_api_version: INTEGER v event_api_version_enum: STRING For events that are generated by situations in the Global Update Messages attribute group, events are sent by using the ITM_KQ5_GLOBAL_UPDATE_MESSAGES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v database_update_messages: INTEGER v database_update_messages_enum: STRING v database_update_messages_delta: INTEGER v database_update_messages_delta_enum: STRING v update_messages: INTEGER v update_messages_enum: STRING v update_messages_delta: INTEGER v update_messages_delta_enum: STRING v name: STRING For events that are generated by situations in the Memory attribute group, events are sent by using the ITM_KQ5_MEMORY event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name_of_node: STRING v memory_module: STRING v available_memory_mb: INTEGER v available_memory_mb_enum: STRING v percent_committed_bytes_in_use: INTEGER v percent_committed_bytes_in_use_enum: STRING v cache_bytes: INTEGER v cache_bytes_enum: STRING v cache_bytes_peak: INTEGER v cache_bytes_peak_enum: STRING v cache_faults: INTEGER Appendix A. Event mapping 325

v cache_faults_enum: STRING v page_faults: INTEGER v page_faults_enum: STRING v page_reads: INTEGER v page_reads_enum: STRING v page_writes: INTEGER v page_writes_enum: STRING v pages_input: INTEGER v pages_input_enum: STRING v pages_output: INTEGER v pages_output_enum: STRING v pool_paged_bytes: INTEGER v pool_paged_bytes_enum: STRING v commit_limit_mb: INTEGER v committed_mb: INTEGER v cache_mb: INTEGER v cache_peak_mb: INTEGER v pool_paged_mb: INTEGER For events that are generated by situations in the Memory MB Rollup attribute group, events are sent by using the ITM_KQ5_MEMORY_MB_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Memory PCT Rollup attribute group, events are sent by using the ITM_KQ5_MEMORY_PCT_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING 326 Microsoft Cluster Server agent: User's Guide

v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the MRR Messages attribute group, events are sent by using the ITM_KQ5_MRR_MESSAGES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v messages_outstanding: INTEGER v messages_outstanding_enum: STRING v messages_sent: INTEGER v messages_sent_enum: STRING v messages_sent_delta: INTEGER v messages_sent_delta_enum: STRING v name: STRING For events that are generated by situations in the Network Interfaces attribute group, events are sent by using the ITM_KQ5_NETWORK_INTERFACES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v state_raw: INTEGER v state_raw_enum: STRING v address: STRING v system_name: STRING v adapter: STRING v network_name: STRING v device_id: STRING v description: STRING v state: INTEGER For events that are generated by situations in the Network Interfaces State Rollup attribute group, events are sent by using the ITM_KQ5_NETWORK_INTERFACES_STATE_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING Appendix A. Event mapping 327

For events that are generated by situations in the Network Performance attribute group, events are sent by using the ITM_KQ5_NETWORK_PERFORMANCE event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name_of_node: STRING v network_interface: STRING v bytes_received: INTEGER v bytes_received_enum: STRING v bytes_sent: INTEGER v bytes_sent_enum: STRING v current_bandwidth: INTEGER v current_bandwidth_enum: STRING v output_queue_length: INTEGER v output_queue_length_enum: STRING v packets_outbound_discarded: INTEGER v packets_outbound_discarded_enum: STRING v packets_outbound_errors: INTEGER v packets_outbound_errors_enum: STRING v packets: INTEGER v packets_enum: STRING v packets_received_discarded: INTEGER v packets_received_discarded_enum: STRING v packets_received_errors: INTEGER v packets_received_errors_enum: STRING v packets_received: INTEGER v packets_received_enum: STRING v packets_sent: INTEGER v packets_sent_enum: STRING v bytes_total: INTEGER v bytes_total_enum: STRING v received_mb: INTEGER v sent_mb: INTEGER v current_bandwidth_mb: INTEGER v total_mb: INTEGER v current_bandwidth_gbps: REAL v current_bandwidth_gbps_enum: STRING For events that are generated by situations in the Network Performance Packets Rollup attribute group, events are sent by using the ITM_KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP event class. This event class contains the following slots: v node: STRING v timestamp: STRING v maximum: INTEGER v maximum_enum: STRING v minimum: INTEGER 328 Microsoft Cluster Server agent: User's Guide

v minimum_enum: STRING v average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Network Performance Received Rollup attribute group, events are sent by using the ITM_KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Network Performance Sent Rollup attribute group, events are sent by using the ITM_KQ5_NETWORK_PERFORMANCE_SENT_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Network Reconnections attribute group, events are sent by using the ITM_KQ5_NETWORK_RECONNECTIONS event class. This event class contains the following slots: v node: STRING v timestamp: STRING v normal_message_queue_length: INTEGER v normal_message_queue_length_enum: STRING Appendix A. Event mapping 329

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 that are generated by situations in the Networks attribute group, events are sent by using the ITM_KQ5_NETWORKS event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v state_raw: INTEGER v state_raw_enum: STRING v address: STRING v addressmask: STRING v role: INTEGER v role_enum: STRING v description: STRING v state: INTEGER For events that are generated by situations in the Networks Messages attribute group, events are sent by using the ITM_KQ5_NETWORKS_MESSAGES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v bytes_received: INTEGER v bytes_received_enum: STRING v bytes_received_delta: INTEGER v bytes_received_delta_enum: STRING v bytes_sent: INTEGER v bytes_sent_enum: STRING v bytes_sent_delta: INTEGER v bytes_sent_delta_enum: STRING v messages_received: INTEGER v messages_received_enum: STRING v messages_received_delta: INTEGER v 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 that are generated by situations in the Networks Rollup attribute group, events are sent by using the ITM_KQ5_NETWORKS_ROLLUP event class. This event class contains the following slots: v node: STRING 330 Microsoft Cluster Server agent: User's Guide

v timestamp: STRING v maximum: INTEGER v maximum_enum: STRING v minimum: INTEGER v minimum_enum: STRING v average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Node To Active Group attribute group, events are sent by using the ITM_KQ5_NODE_TO_ACTIVE_GROUP event class. This event class contains the following slots: v node: STRING v timestamp: STRING v current_rg_node: STRING v rg_node_changed: INTEGER v previous_rg_node: INTEGER v state_of_node: INTEGER v state_of_node_enum: STRING v description_of_node: STRING v name_of_group: STRING v state_of_group: INTEGER v state_of_group_enum: STRING v description_of_group: STRING v node_group_names: STRING For events that are generated by situations in the Nodes attribute group, events are sent by using the ITM_KQ5_NODES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v state_raw: INTEGER 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 description: STRING v state: INTEGER For events that are generated by situations in the Nodes State Rollup attribute group, events are sent by using the ITM_KQ5_NODES_STATE_ROLLUP event class. This event class contains the following slots: v node: STRING Appendix A. Event mapping 331

v timestamp: STRING v maximum: INTEGER v maximum_enum: STRING v minimum: INTEGER v minimum_enum: STRING v average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Performance Object Status attribute group, events are sent by using the ITM_KQ5_PERFORMANCE_OBJECT_STATUS event class. This event class contains the following slots: v node: STRING v timestamp: STRING v query_name: STRING v object_name: STRING v object_type: INTEGER v object_type_enum: STRING v object_status: INTEGER v object_status_enum: STRING v error_code: INTEGER v error_code_enum: STRING v last_collection_start: STRING v last_collection_start_enum: STRING v last_collection_finished: STRING v last_collection_finished_enum: STRING v last_collection_duration: REAL v average_collection_duration: REAL v average_collection_duration_enum: STRING v refresh_interval: INTEGER v number_of_collections: INTEGER v cache_hits: INTEGER v cache_misses: INTEGER v cache_hit_percent: REAL v intervals_skipped: INTEGER For events that are generated by situations in the Quorum Configuration attribute group, events are sent by using the ITM_KQ5_QUORUM_CONFIGURATION event class. This event class contains the following slots: v node: STRING v timestamp: STRING v maintenance_file: STRING v quorum_log_file_size: INTEGER 332 Microsoft Cluster Server agent: User's Guide

v quorum_log_file_size_enum: STRING v quorum_arbitration_time_max: INTEGER v quorum_arbitration_time_max_enum: STRING v quorum_arbitration_time_min: INTEGER v quorum_arbitration_time_min_enum: STRING v quorum_type: STRING v quorum_path: STRING For events that are generated by situations in the Resource Control Manager attribute group, events are sent by using the ITM_KQ5_RESOURCE_CONTROL_MANAGER event class. This event class contains the following slots: v node: STRING v timestamp: STRING v groups_online: INTEGER v groups_online_enum: STRING v rhs_processes: INTEGER v rhs_processes_enum: STRING v rhs_restarts: INTEGER v rhs_restarts_enum: STRING v name: STRING For events that are generated by situations in the Resource Group Moves attribute group, events are sent by using the ITM_KQ5_RESOURCE_GROUP_MOVES event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Resource Group To Preferred Node attribute group, events are sent by using the ITM_KQ5_RESOURCE_GROUP_TO_PREFERRED_NODE event class. This event class contains the following slots: v node: STRING v timestamp: STRING v group_name: STRING v group_state: INTEGER v group_state_enum: STRING v group_description: STRING v name_of_node: STRING Appendix A. Event mapping 333

v state_of_node: INTEGER v state_of_node_enum: STRING v description_of_node: STRING For events that are generated by situations in the Resource Group To Resource attribute group, events are sent by using the ITM_KQ5_RESOURCE_GROUP_TO_RESOURCE event class. This event class contains the following slots: v node: STRING v timestamp: STRING v group_name: STRING v group_state: INTEGER v group_state_enum: STRING v group_description: STRING v resource_name: STRING v resource_state: INTEGER v resource_state_enum: STRING v resource_description: STRING For events that are generated by situations in the Resource Groups attribute group, events are sent by using the ITM_KQ5_RESOURCE_GROUPS event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v state_raw: INTEGER v state_raw_enum: STRING v persistent_state: INTEGER v persistent_state_enum: STRING v auto_failback_type: INTEGER v auto_failback_type_enum: STRING v failover_period: INTEGER v failover_period_enum: STRING v 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 description: STRING v state: INTEGER For events that are generated by situations in the Resource Groups State Rollup attribute group, events are sent by using the ITM_KQ5_RESOURCE_GROUPS_STATE_ROLLUP event class. This event class contains the following slots: v node: STRING v timestamp: STRING v maximum: INTEGER v maximum_enum: STRING 334 Microsoft Cluster Server agent: User's Guide

v minimum: INTEGER v minimum_enum: STRING v average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Resource To Dependent Resource attribute group, events are sent by using the ITM_KQ5_RESOURCE_TO_DEPENDENT_RESOURCE event class. This event 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 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 that are generated by situations in the Resource To Possible Owner attribute group, events are sent by using the ITM_KQ5_RESOURCE_TO_POSSIBLE_OWNER event class. This event 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 resource_description: STRING v name_of_node: STRING v state_of_node: INTEGER v state_of_node_enum: STRING v description_of_node: STRING For events that are generated by situations in the Resources attribute group, events are sent by using the ITM_KQ5_RESOURCES event class. This event class contains the following slots: v node: STRING v timestamp: STRING v name: STRING v state_raw: INTEGER v state_raw_enum: STRING v type: STRING v core_resource: INTEGER v core_resource_enum: STRING Appendix A. Event mapping 335

v persistent_state: INTEGER v persistent_state_enum: STRING v delete_requires_all_nodes: INTEGER v delete_requires_all_nodes_enum: STRING v is_alive_poll_interval: INTEGER v is_alive_poll_interval_enum: STRING v looks_alive_poll_interval: INTEGER v looks_alive_poll_interval_enum: STRING v pending_timeout: INTEGER v pending_timeout_enum: STRING v restart_action: INTEGER v restart_action_enum: STRING v restart_period: INTEGER v restart_period_enum: STRING v restart_threshold: INTEGER v restart_threshold_enum: STRING v retry_period_on_failure: INTEGER v retry_period_on_failure_enum: STRING v description: STRING v state: INTEGER v monitored_resource: STRING For events that are generated by situations in the Resources State Rollup attribute group, events are sent by using the ITM_KQ5_RESOURCES_STATE_ROLLUP event class. This event 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 average: INTEGER v average_enum: STRING v total: INTEGER v total_enum: STRING v standard_deviation: INTEGER v standard_deviation_enum: STRING For events that are generated by situations in the Resources Summary attribute group, events are sent by using the ITM_KQ5_RESOURCES_SUMMARY event class. This event class contains the following slots: v node: STRING v timestamp: STRING v resource_controls: INTEGER v resource_controls_enum: STRING v resource_failure: INTEGER v resource_failure_enum: STRING 336 Microsoft Cluster Server agent: User's Guide

v resource_failure_access_violation: INTEGER v resource_failure_access_violation_enum: STRING v resource_failure_deadlock: INTEGER v resource_failure_deadlock_enum: STRING v resources_online: INTEGER v resources_online_enum: STRING v resource_type_controls: INTEGER v resource_type_controls_enum: STRING v name: STRING For events that are generated by situations in the Shared Storage Summary attribute group, events are sent by using the ITM_KQ5_SHARED_STORAGE_SUMMARY event class. This event 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 shared_storage_available: INTEGER v shared_storage_available_enum: STRING v shared_storage_utilization: INTEGER v shared_storage_utilization_enum: STRING v shared_storage_state: INTEGER v shared_storage_state_enum: STRING v percentage_shared_storage_utilization: REAL v percentage_shared_storage_utilization_enum: STRING For events that are generated by situations in the Structural Risk attribute group, events are sent by using the ITM_KQ5_STRUCTURAL_RISK event class. This event class contains the following slots: v node: STRING v timestamp: STRING v lowest_health_resource: STRING v current_health: INTEGER v current_health_enum: STRING v health_less_a_node: INTEGER v health_less_a_node_enum: STRING v fewest_nodes_resource: STRING v available_nodes: INTEGER v available_nodes_enum: STRING v less_a_node: INTEGER v less_a_node_enum: STRING v less_a_node_percent: INTEGER v less_a_node_percent_enum: STRING Appendix A. Event mapping 337

For events that are generated by situations in the Thread Pool Status attribute group, events are sent by using the ITM_KQ5_THREAD_POOL_STATUS event class. This event class contains the following slots: v node: STRING v timestamp: STRING v thread_pool_size: INTEGER v thread_pool_size_enum: STRING v thread_pool_max_size: INTEGER v thread_pool_max_size_enum: STRING v thread_pool_active_threads: INTEGER v thread_pool_active_threads_enum: STRING v thread_pool_avg_active_threads: REAL v thread_pool_avg_active_threads_enum: STRING v thread_pool_min_active_threads: INTEGER v thread_pool_min_active_threads_enum: STRING v thread_pool_max_active_threads: INTEGER v thread_pool_max_active_threads_enum: STRING v 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 v thread_pool_min_queue_length: INTEGER v thread_pool_min_queue_length_enum: STRING v thread_pool_max_queue_length: INTEGER v thread_pool_max_queue_length_enum: STRING v thread_pool_avg_job_wait: REAL v thread_pool_avg_job_wait_enum: STRING v thread_pool_total_jobs: INTEGER v thread_pool_total_jobs_enum: STRING 338 Microsoft Cluster Server agent: User's Guide

Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent The Tivoli Management Services Discovery Library Adapter (DLA) discovers resources and relationships, and creates a Discovery Library Book file for the agent. About the DLA The Book file follows the Discovery Library IdML schema and is used to populate the Configuration Management Database (CMDB) and Tivoli Business Service Manager 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 Microsoft Cluster Server components. 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 TADDM Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/ com.ibm.taddm.doc_7.2/welcome_page/welcome.html). DLA data model class types represented in CDM The 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 Class name for which the agent is providing information 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 DLA data model classes for Microsoft Cluster Server agent Each agent that uses the Discovery Library Adapter has DLA data model classes defined for the agent. The Microsoft Cluster Server agent agent has the following Discovery Library Adapter data model classes: v MsCluster class v MsClusterNode class v MsClusterResourceGroup class Copyright IBM Corp. 2008, 2013 339

v MsClusterResource class v MsClusterService class v IpNetwork class v TMSAgent class MsCluster class The MsCluster class represents an instance of the Microsoft Cluster Server. CDM class name app.msfailovercluster.mscluster Relationships uses v : app.msfailovercluster.mscluster v Target: net.ipnetwork v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster uses 169.254.187.155- IpAddress monitors v : apptmsagent v Target: app.msfailovercluster.mscluster v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-itmagents.com-WIN2003SP2- MsCluster realizes v : sys.computersystem v Target: app.msfailovercluster.mscluster v Example: 169.254.187.155-ComputerSystem realizes WIN2003SP2:Q5-itmagents.com- WIN2003SP2-MsCluster accessedvia v : app.msfailovercluster.mscluster v Target: net.ipnetwork v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster accessedvia 169.254.187.155-IpAddress contains v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster contains WIN2003SP2:Q5-V- PS6097-2K3E-MsClusterNode manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- Majority Node Set-MsClusterResource manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusterresourcegroup v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- Cluster Group-MsClusterResourceGroup 340 Microsoft Cluster Server agent: User's Guide

manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusterresource v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- CLWIN2K3-SVC-MsClusterResource CDM attributes, agent attributes, descriptions, and examples v CDM attribute: Domain Agent attribute: KQ5WIN32CO.DOMAIN : The name of the cluster domain. Example: win2k3pado v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: MaxNumberOfNodes Agent attribute: KQ5B05PHYS. Max_Number_Nodes : The maximum number of nodes that can be added in a cluster. Example: 8 v CDM attribute: Label Agent attribute: KQ5B05PHYS. Name : 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 Relationships monitors v : apptmsagent v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-V-PS6097-2K3ENT-MsClusterNode contains v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster contains WIN2003SP2:Q5-V- PS6097-2K3E-MsClusterNode controls v : app.msfailovercluster.msclusterservice v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster controls WIN2003SP2:Q5-V- PS6097-2K3E-MsClusterNode manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- Majority Node Set-MsClusterResource Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent 341

CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: Name Agent attribute: KQ5D20NODE.Name : The name of the Cluster Server node. Example: W2K3-ClusterNode1 v CDM attribute: Label Agent attribute: KQ5D20NODE.Name : The label of the Cluster Server node. Example: W2K3-ClusterNode1- MSClusterServer Node v CDM attribute: AdminState Agent attribute: KQ5D20NODE.State_Raw : The current state of the Cluster Server node. Example: Unknown, Other, Enabled, or Disabled MsClusterResourceGroup class The MsClusterResourceGroup class represents the resource group that is owned by a node in a cluster. CDM class name app.msfailovercluster.msclusterresourcegroup Relationships contains v : app.msfailovercluster.msclusterresourcegroup v Target: app.msfailovercluster.msclusterresource v Example: WIN2003SP2:Q5-Cluster Group-MsClusterResourceGroup contains WIN2003SP2:Q5-Majority Node Set-MsClusterResource manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusterresourcegroup v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- Cluster Group-MsClusterResourceGroup CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: Name Agent attribute: KQ5B10RG.Name : The name of the resource group. Example: Cluster Group v CDM attribute: AdminState Agent attribute: KQ5B10RG.State_Raw : The current state of the resource group. Example: Unknown, Other, Enabled, or Disabled v CDM attribute: FailbackWindowStart Agent attribute: KQ5B10RG.Failback_Window_Start 342 Microsoft Cluster Server agent: User's Guide

: The earliest time by when the resource group can fail back to the node that was identified as a preferred owner of the cluster. Example: 12 v CDM attribute: FailbackWindowEnd Agent attribute: KQ5B10RG.Failback_Window_End : The latest time up to when the resource group can fail back to the node that was identified as a preferred owner of the cluster. Example: 11 v CDM attribute: FailoverPeriod Agent attribute: KQ5B10RG.Failover_Period : The time (in hours) during which the number of failover attempts are counted. Example: 6 v CDM attribute: FailoverThreshold Agent attribute: KQ5B10RG.Failover_Threshold : The maximum number of failover attempts that occur during the failover period. Example: 10 v CDM attribute: IsPersistentState Agent attribute: KQ5B10RG.Persistent_State : The state of the resource group when the Cluster service is started. Example: True or False v CDM attribute: Agent attribute: KQ5B10RG. : The description of the resource group. Example: v CDM attribute: Auto_FailBack_ Agent attribute: KQ5B10RG.Auto_FailBack_ : An enumerated value that indicates whether the resource group can fail back to the node that was identified as a preferred owner of the cluster. Example: Prevent or Allow MsClusterResource class The MsClusterResource class represents the resource that is contained in a resource group. CDM class name app.msfailovercluster.msclusterresource Relationships monitors v : apptmsagent v Target: app.msfailovercluster.msclusterresource v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-Majority Node Set-MsClusterResource contains v : app.msfailovercluster.msclusterresourcegroup v Target: app.msfailovercluster.msclusterresource v Example: WIN2003SP2:Q5-Cluster Group-MsClusterResourceGroup contains WIN2003SP2:Q5-Majority Node Set-MsClusterResource manages v : app.msfailovercluster.mscluster v Target: app.msfailovercluster.msclusterresource Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent 343

v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster manages WIN2003SP2:Q5- CLWIN2K3- SVC-MsClusterResource CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: Name Agent attribute: KQ5C20RES.Name : The name of the resource. Example: Disk Q v CDM attribute: AdminState Agent attribute: KQ5C20RES.State_Raw : The current state of the resource. Example: Unknown, Other, Enabled, or Disabled v CDM attribute: IsAlivePollInterval Agent attribute: KQ5C20RES.Is_Alive_Poll_Interval : The frequency (in milliseconds) at which the Cluster service checks whether the resource is active. Example: 60000 v CDM attribute: LooksAlivePollInterval Agent attribute: KQ5C20RES.Looks_Alive_Poll_Interval : The frequency (in milliseconds) at which the Cluster service checks whether the resource appears to be active. Example: 5000 v CDM attribute: PendingTimeout Agent attribute: KQ5C20RES.Pending_Timeout : The amount of time (in milliseconds) the Cluster service waits before failing the resource. Example: 180000 v CDM attribute: RestartAction Agent attribute: KQ5C20RES.Restart_Action : The action that the Cluster service must take if the resource fails. Example: Restart With No Failover, Restart With Failover, No Restart v CDM attribute: RestartPeriod Agent attribute: KQ5C20RES.Restart_Period : The time interval (in milliseconds) during which a failed resource can be restarted. Example: 900000 v CDM attribute: RetryPeriodOnFailure Agent attribute: KQ5C20RES.Retry_Period_On_Failure : The time interval (in milliseconds) for which the Cluster service waits before attempting to restart a failed resource. Example: 800000 v CDM attribute: RestartThreshold Agent attribute: KQ5C20RES.Restart_Threshold : The number of restart attempts that are permitted to restart a failed resource during the restart period. Example: 3 MsClusterService class The MsClusterService class represents the Cluster service. 344 Microsoft Cluster Server agent: User's Guide

CDM class name app.msfailovercluster.msclusterservice Relationships monitors v : apptmsagent v Target: app.msfailovercluster.msclusterservice v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-ClusSvc.exe-MsClusterService installedon v : app.msfailovercluster.msclusterservice v Target: sys.windows.windowsoperatingsystem v Example: WIN2003SP2:Q5-ClusSvc.exe-MsClusterService installedon 10.77.66.34- OperatingSystem controls v : app.msfailovercluster.msclusterservice v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-ClusSvc.exe-MsClusterService controls WIN2003SP2:Q5-V-PS6097-2K3EMsClusterNode CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: Name Agent attribute: KQ5AVAIL.Name : The name of the Cluster service. Example: ClusSvc.exe v CDM attribute: Started Agent attribute: KQ5AVAIL.Status : A Boolean value that indicates whether the Cluster service is started. Example: True or False v CDM attribute: AdminState Agent attribute: KQ5AVAIL.Status : The current state of the Cluster service. Example: Unknown, Other, Enabled, or Disabled v CDM attribute: ProcessId Agent attribute: KQ5AVAIL.PID : The ID of the Cluster service. Example: 1364 v CDM attribute: PathName Agent attribute: KQ5AVAIL.Full_Name : The path of the Cluster service. Example: C:\WINDOWS\Cluster\clussvc.exe v CDM attribute: Service Agent attribute: KQ5AVAIL. : The type of the Cluster service. Example: Process or Service IpNetwork class The IPNetwork class represents the networks that are used in a cluster. Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent 345

CDM class name Net.IpNetwork Relationships uses v : app.msfailovercluster.mscluster v Target: net.ipnetwork v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster uses 169.254.187.155- IpAddress accessedvia v : app.msfailovercluster.mscluster v Target: net.ipnetwork v Example: WIN2003SP2:Q5-itmagents.com-WIN2003SP2-MsCluster accessedvia 169.254.187.155- IpAddress CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3498WIN2K3:Q5 v CDM attribute: Name Agent attribute: KQ5E20NET.Name : The name of the network. Example: Cluster Network 1 v CDM attribute: Agent attribute: KQ5E20NET.Role : The type of the network. Example: Public or Internal or Public and Internal v CDM attribute: AdminState Agent attribute: KQ5E20NET.State : The current state of the network. Example: Unknown, Other, Enabled, or Disabled v CDM attribute: SubnetAddress Agent attribute: KQ5E20NET.Address : The IP address of the subnet. Example: 192.168.6.0 v CDM attribute: Netmask Agent attribute: KQ5E20NET.AddressMask : The IP address of the netmask. Example: 255.255.255.0 TMSAgent class The TMSAgent class represents a Tivoli Monitoring Services agent. CDM class name app.tmsagent Relationships monitors v : apptmsagent v Target: app.msfailovercluster.mscluster 346 Microsoft Cluster Server agent: User's Guide

v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-itmagents.com-WIN2003SP2- MsCluster monitors v : apptmsagent v Target: app.msfailovercluster.msclusternode v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-V-PS6097-2K3ENT-MsClusterNode monitors v : apptmsagent v Target: app.msfailovercluster.msclusterresource v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-Majority Node Set-MsClusterResource monitors v : apptmsagent v Target: app.msfailovercluster.msclusterservice v Example: WIN2003SP2:Q5-TMSAgent monitors WIN2003SP2:Q5-ClusSvc.exe-MsClusterService installedon v : apptmsagent v Target: sys.windows.windowsoperatingsystem v Example: WIN2003SP2:Q5-TMSAgent installedon 10.77.66.34-OperatingSystem CDM attributes, agent attributes, descriptions, and examples v CDM attribute: ManagedSystemName Agent attribute: INODESTS.Node : The name of the managed system. Example: PS3867:Q5 v CDM attribute: Name Agent attribute: INODESTS.Node : The name of the Tivoli Monitoring Services agent. Example: WIN2K3WEB:Q5 v CDM attribute: ManagedObjectName Agent attribute: INODESTS.Node : The name of the IBM Tivoli Monitoring component that provides data for the management of the Cluster Server instance. Example: p@ps3867:q5 v CDM attribute: SoftwareVersion Agent attribute: INODESTS.Version : The version of the Microsoft Cluster Server agent. Example: 6.2.0 FP1 v CDM attribute: Product Code Agent attribute: INODESTS.Product : The product code of Microsoft Cluster Server agent. Example: Q5 v CDM attribute: Affinity Agent attribute: INODESTS. Affinities : The affinity of the Microsoft Cluster Server agent. Example: 00000000000000000200000 00000000001000000000 v CDM attribute: Label Agent attribute: INODESTS.Node : The label of the Microsoft Cluster Server agent. Example: PS3867:Q5 - MS Cluster Server Appendix B. Discovery Library Adapter for the Microsoft Cluster Server agent 347

348 Microsoft Cluster Server agent: User's Guide

Appendix C. Integration with Tivoli Business Service Manager Microsoft Cluster Server agent provides data to create, update the status of, and view IBM Tivoli Business Service Manager services. The Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkit provides data for the Tivoli Business Service Manager service models. The Tivoli Event Integration Facility (EIF) probe updates the status of these services, and you use the Tivoli Enterprise Portal to view the data for the services. To implement the integration of the agent with Tivoli Business Service Manager, perform the integration tasks. Components for integrating with Tivoli Business Service Manager The data for integrating with Tivoli Business Service Manager is supplied through the following components: Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkit, Tivoli Event Integration Facility (EIF) probe, and Tivoli Enterprise Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkit By using data from the Tivoli Management Services Discovery Library Adapter, you can build Tivoli Business Service Manager service models that include resources monitored by the Microsoft Cluster Server agent. The DLA files can be imported directly into Tivoli Business Service Manager using the Discovery Library Toolkit or they can be loaded into IBM Tivoli Application Dependency Discovery Manager (TADDM) and then fed into Tivoli Business Service Manager using the Discovery Library Toolkit. See the following sources for more information about the DLA and Discovery Library Toolkit: v Resources and relationships that are discovered by the Microsoft Cluster Server agent and included in Tivoli Management Services DLA files: Appendix B, Discovery Library Adapter for the Microsoft Cluster Server agent, on page 339 v Using the Tivoli Management Services DLA: IBM Tivoli Monitoring Administrator's Guide v Using the Discovery Library Toolkit: Tivoli Business Service Manager Customization Guide Tivoli Event Integration Facility (EIF) probe Situation events detected by the Microsoft Cluster Server agent can update the status of services in Tivoli Business Service Manager. The situation events are forwarded from IBM Tivoli Monitoring to the Netcool/OMNIbus Probe for the Tivoli Event Integration Facility. The Microsoft Cluster Server agent provides a probe rules file that updates its events with information to identify the affected service in Tivoli Business Service Manager. The EIF probe then forwards the events to the Netcool/OMNIbus ObjectServer. Tivoli Business Service Manager monitors the Netcool/OMNIbus ObjectServer for new events and updates the status of affected services. See the following sources for more information about event integration: v Installation (using an existing EIF probe and Netcool/OMNIbus ObjectServer installation or using Tivoli Business Service Manager to install these components): Netcool/OMNIbus Information Center or the Tivoli Business Service Manager Installation Guide. Copyright IBM Corp. 2008, 2013 349

v Setting up event integration between IBM Tivoli Monitoring, the EIF probe, and the Netcool/OMNIbus ObjectServer: IBM Tivoli Monitoring Installation and Setup Guide. v Configuring the EIF probe to use the Microsoft Cluster Server agent rules file after the EIF probe has been installed and configured for event integration with IBM Tivoli Monitoring: Configuring the Tivoli Event Integration Facility (EIF) probe to enrich events Tivoli Enterprise Portal You can use the integration of the Tivoli Enterprise Portal with Tivoli Business Service Manager to view the services in the Tivoli Business Service Manager console. For more detailed examination and analysis, you can easily link from the Tivoli Business Service Manager console to the Tivoli Enterprise Portal to view the data within the Microsoft Cluster Server agent. Tasks to integrate the agent with Tivoli Business Service Manager To integrate the Microsoft Cluster Server agent with Tivoli Business Service Manager, you must install and configure the required components. Then, you can view the data in the Tivoli Enterprise To integrate the Microsoft Cluster Server agent with Tivoli Business Service Manager and view the data, complete the following tasks: v Install the Discovery Library Toolkit on thetivoli Business Service Manager server. v Configure the Tivoli Event Integration Facility (EIF) probe to enrich Microsoft Cluster Server agent events. v Create a service in the Tivoli Business Service Manager console that you want to monitor. v Create a data source mapping for each data source that you want to access within the Tivoli Business Service Manager. v Configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal Server. v View data in the Tivoli Enterprise Portal for the services that you have created to monitor through Tivoli Business Service Manager. Installing the Discovery Library Toolkit on the Tivoli Business Service Manager You must install the Discovery Library Toolkit on the Tivoli Business Service Manager server. The Discovery Library Toolkit imports data from the DLA files and TADDM, which includes information about the hardware and the applications that are discovered by the source. See "Installing the Discovery Library Toolkit" in the Tivoli Business Service Manager Installation Guide. Configuring the Tivoli Event Integration Facility (EIF) probe to enrich events The Netcool/OMNIbus Probe for Tivoli Event Integration Facility (EIF) forwards the Microsoft Cluster Server agent events that are received from IBM Tivoli Monitoring to the Netcool/OMNIbus ObjectServer. Tivoli Business Service Manager monitors the Netcool/OMNIbus ObjectServer for new events, and updates the status of affected services. The Microsoft Cluster Server agent provides a probe rules include file that updates its events with information to identify the affected service in Tivoli Business Service Manager. 350 Microsoft Cluster Server agent: User's Guide

Before you begin Install and configure the Netcool/OMNIbus ObjectServer and EIF probe and set up event integration between IBM Tivoli Monitoring and Netcool/OMNIbus. About this task To enable event enrichment, configure the EIF probe to use the rules file for the agent. Procedure 1. Locate the Microsoft Cluster Server agent rules file (kq5_tbsm.rules) on a computer system where the Microsoft Cluster Server agent, Tivoli Enterprise Monitoring Server, or Tivoli Enterprise Portal Server is installed. The file is in the following locations: v On Windows systems The file is in the installdir\cms\teclib directory of the monitoring server, in the installdir\cnps\teclib directory of the portal server, or in the installdir\tmaitm6\eiflib directory of the agent, where installdir is the IBM Tivoli Monitoring or ITCAM for Microsoft Applications installation directory. v On Linux and UNIX systems The file is in the installdir/tables/cicatrsq/teclib directory of the monitoring server or in the installdir/platform/xx/teclib directory of the agent, where installdir is the IBM Tivoli Monitoring or ITCAM for Microsoft Applications directory, platform is the architecture directory for the agent, and xx is the product code for the agent. 2. Copy the kq5_tbsm.rules file to the following directory on the computer system where the EIF probe is installed: v On Windows systems %OMNIHOME%\probes\arch v On UNIX systems $OMNIHOME/probes/arch Where: OMNIHOME System-defined variable defining the installation location of Netcool/OMNIbus arch Operating system directory where the probe is installed; for example, solaris2 when running on a Solaris system, and win32 for a Windows system. 3. Edit the tivoli_eif.rules file and uncomment the include statement for kq5_tbsm.rules. (The tivoli_eif.rules file is located in the same directory as the kq5_tbsm.rules file.) If you are using a version of the tivoli_eif.rules file without an include statement for kq5_tbsm.rules, add the following line after the include statement for itm_event.rules: include "kq5_tbsm.rules" 4. Restart the EIF probe. Creating a service in Tivoli Business Service Manager You must create a service in the Tivoli Business Service Manager console for each service that you want to monitor. To create the services that you want to monitor in the Tivoli Business Service Manager console, see "Configuring services" in the IBM Tivoli Business Service Manager Service Configuration Guide. Appendix C. Integration with Tivoli Business Service Manager 351

Creating a data source mapping for each data source You can create a data source mapping for each data source that you want to access within Tivoli Business Service Manager. Also, you can create the data fetchers and use the data to create incoming status rules that are populated in your service templates. For more information, see "Data sources" and "Data fetchers" in the IBM Tivoli Business Service Manager Service Configuration Guide. Configuring additional IBM Tivoli Monitoring web services You can configure additional IBM Tivoli Monitoring web services for each Tivoli Enterprise Portal Server. To configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal server, see "Configure TBSM charts" in the IBM Tivoli Business Service Manager Scenarios Guide. Viewing data in the Tivoli Enterprise Portal From Tivoli Business Service Manager, you can open the Tivoli Enterprise Portal and view the Microsoft Cluster Server agent. You can also launch Tivoli Business Service Manager from the Tivoli Enterprise For more information about launching applications, see "Launching to and from applications" in the Tivoli Business Service Manager Customization Guide. 352 Microsoft Cluster Server agent: User's Guide

Appendix D. Documentation library A variety of publications are relevant to the use of the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent. The IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Manager products: Documentation Guide contains information about accessing and using publications. You can find the Documentation Guide in the following information centers: v IBM Tivoli Monitoring and OMEGAMON XE (http://publib.boulder.ibm.com/infocenter/tivihelp/ v15r1/index.jsp) v IBM Tivoli Composite Application Manager (http://publib.boulder.ibm.com/infocenter/tivihelp/ v24r1/index.jsp) 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 in the information center 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. IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent library The documentation for this agent and other product components is located in the IBM Tivoli Composite Application Manager for Microsoft Applications Information Center (http://publib.boulder.ibm.com/ infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html). One document is specific to the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent: IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent User s Guide. This publication provides agent-specific information for configuring, using, and troubleshooting the Microsoft Cluster Server agent. The Offering Guide also provides information about installing and configuring the component products in the offering. The Prerequisites topic in the information center contains information about the prerequisites for each component. Use the information in the user's guide for the agent 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. See the following publications to gain the required prerequisite knowledge: v IBM Tivoli Monitoring Administrator's Guide v IBM Tivoli Monitoring Agent Builder User's Guide v IBM Tivoli Monitoring Command Reference v Configuring IBM Tivoli Enterprise Monitoring Server on z/os Copyright IBM Corp. 2008, 2013 353

v IBM Tivoli Monitoring Installation and Setup Guide v IBM Tivoli Monitoring High Availability Guide for Distributed Systems v IBM Tivoli Monitoring: Messages v IBM Tivoli Monitoring Troubleshooting Guide v IBM Tivoli Monitoring Universal Agent User's Guide v IBM Tivoli Universal Agent API and Command Programming Reference Guide v IBM Tivoli Monitoring: i5/os Agent User's Guide v IBM Tivoli Monitoring: Linux OS Agent User's Guide v IBM Tivoli Monitoring: UNIX OS Agent User's Guide v IBM Tivoli Monitoring: UNIX Logs OS Agent User's v IBM Tivoli Monitoring: Windows OS Agent User's Guide v Tivoli Enterprise Portal User's Guide v IBM Tivoli Performance Analyzer User's Guide v IBMTivoli Warehouse Proxy Agent User's Guide v IBMTivoli Warehouse Summarization and Pruning Agent User's Guide Related publications The publications in related information centers provide useful information. See the following information centers, which you can find by accessing Tivoli Documentation Central (http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/home): v IBM Tivoli Monitoring v IBM Tivoli Netcool/OMNIbus v IBM Tivoli Application Dependency Discovery Manager v IBM Tivoli Enterprise Console Other sources of documentation You can obtain additional technical documentation about monitoring products from other sources. See the following sources of technical documentation about monitoring products: v Service Management Connect (SMC) See the introductory information about SMC (http://www.ibm.com/developerworks/ servicemanagement/). For information about Tivoli products, see the Application Performance Management community on SMC (http://www.ibm.com/developerworks/servicemanagement/apm/index.html). Connect, learn, and share with Service Management professionals. Get access to developers and product support technical experts who provide their perspectives and expertise. You can use SMC for these purposes: Become involved with transparent development, an ongoing, open engagement between external users and developers of Tivoli products where you can access early designs, sprint demos, product roadmaps, and pre-release code. Connect one-on-one with the experts to collaborate and network about Tivoli and Integrated Service Management. Benefit from the expertise and experience of others using blogs. Collaborate with the broader user community using wikis and forums. 354 Microsoft Cluster Server agent: User's Guide

v IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/ ismlibrary/) is an online catalog that contains integration documentation as well as other downloadable product extensions. v IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks publications, Redpapers, and Redbooks technotes that provide information about products from platform and solution perspectives. v Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBM Software Support website, provide the latest information about known product limitations and workarounds. v Tivoli wikis Tivoli Wiki Central (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. Two of these wikis are of particular relevance to IBM Tivoli Monitoring: Tivoli Distributed Monitoring and Application Management Wiki (http://www-10.lotus.com/ldd/ tivmonitorwiki.nsf) provides information about IBM Tivoli Monitoring and related distributed products, including IBM Tivoli Composite Application Manager products. Tivoli System z Monitoring and Application Management Wiki (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. Appendix D. Documentation library 355

356 Microsoft Cluster Server agent: User's Guide

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. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, 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. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corp. 2008, 2013 357

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 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 IBM s application programming interfaces. 358 Microsoft Cluster Server agent: User's Guide

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: IBM 2009. Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. 2009. 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. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows 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. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. Notices 359

360 Microsoft Cluster Server agent: User's Guide

Index A activities 257 Adapter attribute 151 additional information attributes 27 situations 225 Take Action commands 245 Workspaces 15 Address attribute 151, 168 AddressMask attribute 168 agent functions 1 problems and workarounds 283 Agent Management Services 3 Application Component attribute 32 attribute group 31 attribute groups Availability 32 CAU Configuration 36 CAU Last Run 41 Cluster Domain 44 Cluster Shared Volume 45 Cluster Shared Volume Block Redirection 48 Cluster Shared Volume Cache 52 Cluster Shared Volume Coordinator 61 Cluster Shared Volume File System 66 Cluster Shared Volume IO 88 Cluster Shared Volume Manager 92 Cluster Summary 101 Cluster Topology 107 Configuration 108 CPU Interrupts Rollup 110 CPU per Node 111 CPU per Node Rollup 114 Degradation Risk 116 Disk 120 Disk MB Rollup 125 Disk PCT Rollup 127 Enterprise Cluster Summary 129 Event Log 135 Global Update Messages 137 list of all 27 Memory 139 Memory MB Rollup 144 Memory PCT Rollup 146 MRR Messages 148 Network Interfaces 150 Network Interfaces State Rollup 152 Network Performance 154 Network Performance Packets Rollup 160 Network Performance Received Rollup 162 Network Performance Sent Rollup 164 Network Reconnections 165 Networks 167 Networks Messages 169 Networks Rollup 172 Node To Active Group 174 Nodes 177 Nodes State Rollup 179 overview 27 Performance Object Status 181 attribute groups (continued) Quorum Configuration 186 Resource Control Manager 188 Resource Group Moves 189 Resource Group To Preferred Node 191 Resource Group To Resource 193 Resource Groups 195 Resource Groups State Rollup 198 Resource To Dependent Resource 200 Resource To Possible Owner 202 Resources 204 Resources State Rollup 209 Resources Summary 211 Shared Storage Summary 213 Structural Risk 216 Thread Pool Status 218 attributes 31 Adapter 151 additional information 27 Address 151, 168 AddressMask 168 Application Component 32 Auto FailBack 196 Availability 32 Available Memory MB 140 Available Nodes 217 Average 111, 115, 126, 128, 145, 147, 153, 161, 163, 165, 173, 180, 190, 199, 210 Average Collection Duration 185 Backup State 47 Build Number 178 Bytes Received 155 Bytes Sent 155 Bytes Total 158 Cache Bytes 140 Cache Bytes Peak 141 Cache Faults 141 Cache Hit Percent 185 Cache Hits 185 Cache IO Read Bytes 52 Cache IO Read Bytes per sec 53 Cache IO Read KB per sec 53 Cache IO Read MB 53 Cache MB 144 Cache Misses 185 Cache Peak MB 144 Cache Read 54 Cache Read per sec 54 Cache Size Configured MB 54 Cache Size Current MB 55 Cache State 55 Canceled Updates 42 CAU Configuration 36 CAU Last Run 41 CAU Plugin Arguments 38 CAU Plugin Name 37 Cluster Domain 44 Cluster Name 101, 129, 213 Cluster Shared Volume 45 Cluster Shared Volume Block Redirection 48 Cluster Shared Volume Cache 52 Copyright IBM Corp. 2008, 2013 361

attributes (continued) Cluster Shared Volume Coordinator 61 Cluster Shared Volume File System 67 Cluster Shared Volume IO 88 Cluster Shared Volume Manager 92 Cluster Shared Volume Name 45 Cluster Summary 101 Cluster Topology 107 Command Line 35 Commit Limit MB 143 Committed MB 144 Configuration 108 Configuration Name 40 Connect To Node 108 Connection 108 Core Resource 205 CPU Interrupts Rollup 110 CPU per Node 111 CPU per Node Rollup 114 Create File 61, 67 Create File per sec 61, 67 CSV Node Name 46 CSV Resource Name 46 CSV Resource State 46 Current Bandwidth 155 Current Bandwidth Gbps 159 Current Bandwidth MB 159 Current Capacity 119 Current Disk Queue 124 Current Health 216 Current Host Server 101, 129 Current RG Node 175 Database Update Messages 138 Database Update Messages Delta 138 Days of Week 40 Default Network Role 109 Degradation Risk 116 Degraded Capacity 119 Delete Requires All Nodes 206 Dependent Resource 202 Dependent Resource Name 201 Dependent Resource State 201 47, 109, 152, 169, 179, 198, 208 of Group 176 of Node 176, 193, 204 Device ID 151 Direct IO Failure Redirection 92 Direct IO Failure Redirection per sec 92 Disk 120, 121 Disk IO Read Bytes 55 Disk IO Read Bytes per sec 56 Disk IO Read KB per sec 56 Disk IO Read MB 56 Disk IO Reads 57 Disk IO Reads per sec 57 Disk MB Rollup 125 Disk PCT Rollup 127 Disk Read Bytes 123 Disk Read MB 125 Disk Reads 123 Disk Transfers 124 Disk Used Percent 124 Disk Write Bytes 122 Disk Write MB 125 Disk Writes 123 Domain 44, 106, 135 Duration 42 attributes (continued) Enable Firewall Rules 39 Enterprise Cluster Summary 129 Error Code 44, 182 Event API Version 137 Event Category 136 Event ID 136 Event Keywords 137 Event Level 136 Event Log 135 Event 135 Event 135 Failback Window End 197 Failback Window Start 197 Failed Updates 42 Failover Period 196 Failover Threshold 197 Fault State 47 Fewest Nodes Resource 217 Files Invalidated During Resume 68 Files Invalidated Other 68 Files Opened 68 Flushes 69 Flushes per sec 69 FreeMegabytes 122 Full Name 33 Functionality Test Message 36 Functionality Test Status 35 Global Update Messages 137 Group 192, 194 Group Name 192, 193 Group State 192, 194 Groups Online 188 Health Less A Node 216 Installed Updates 42 Interrupts 112 Interval Weeks 40 Intervals Skipped 186 IO Read Avg Queue Length 69 IO Read Bytes 48, 57, 62, 69, 89, 93 IO Read Bytes per sec 49, 58, 62, 70, 94 IO Read Bytes per sec Redirected 94 IO Read Bytes Redirected 95 IO Read KB per sec 49, 58, 63, 70, 94 IO Read KB per sec Redirected 95 IO Read KB Redirected 95 IO Read Latency 71 IO Read MB 48, 58, 62, 70, 93 IO Read per sec Redirected 93 IO Read Queue Length 71 IO Reads 49, 59, 63, 71, 89, 96 IO Reads per sec 50, 59, 63, 72, 96 IO Reads Redirected 96 IO Single Reads 72 IO Single Reads per sec 72 IO Single Writes 73 IO Single Writes per sec 73 IO Split Reads 73 IO Split Reads per sec 74 IO Split Writes 74 IO Split Writes per sec 74 IO Write Avg Queue Length 75 IO Write Bytes 50, 75, 89, 96 IO Write Bytes per sec 50, 64, 76, 97 IO Write Bytes per sec Redirected 98 IO Write Bytes Redirected 98 IO Write KB per sec 51, 64, 76, 97 362 Microsoft Cluster Server agent: User's Guide

attributes (continued) IO Write KB per sec Redirected 98 IO Write KB Redirected 99 IO Write Latency 76 IO Write MB 50, 75, 97 IO Write Queue Length 77 IO Writes 51, 64, 77, 90, 99 IO Writes Bytes 65 IO Writes MB 65 IO Writes per sec 51, 65, 77, 99 IO Writes per sec Redirected 100 IO Writes Redirected 100 Is Alive Poll Interval 206 KB Received 170 KB Received Delta 170 KB Sent 171 KB Sent Delta 171 Last Collection Duration 184 Last Collection Finished 184 Last Collection Start 184 Less A Node 217 Less A Node Percent 218 Log Name 135 Looks Alive Poll Interval 206 Lowest Health Resource 216 LRU Cache Size Current MB 59 LRU Cache Size Target MB 60 Maintenance File 186 Major Version 178 Max Capacity 117 Max Failed Nodes 38 Max Number Nodes 109 Max Retries Per Node 38 Max Util 118 Maximum 110, 115, 125, 127, 145, 147, 152, 160, 162, 164, 173, 179, 190, 198, 209 Memory 139 Memory MB Rollup 144 Memory Module 140 Memory PCT Rollup 146 Message 136 Messages Outstanding 149 Messages Received 171 Messages Received Delta 171 Messages Sent 149, 172 Messages Sent Delta 149, 172 Metadata IO 66, 77, 90 Metadata IO per sec 66, 78 Min Capacity 117 Min Util 118 Minimum 110, 115, 126, 128, 145, 147, 153, 160, 162, 164, 173, 180, 190, 199, 209 Minor Version 178 Monitored Resource 208 MRR Messages 148 Name 32, 41, 52, 61, 66, 88, 91, 100, 109, 112, 139, 150, 167, 168, 170, 177, 189, 195, 204, 213 Name of Group 176 Name of Node 121, 139, 154, 192, 203 Network Interface 155 Network Interfaces 150 Network Interfaces State Rollup 152 Network Name 151 Network Performance 154 Network Performance Packets Rollup 160 Network Performance Received Rollup 162 Network Performance Sent Rollup 164 attributes (continued) Network Reconnections 166 Networks 167 Networks Messages 169 Networks Rollup 172 No of Shared Storage 106, 134 Node 32, 36, 41, 44, 45, 48, 52, 61, 67, 88, 92, 101, 107, 108, 110, 112, 114, 116, 120, 125, 127, 129, 135, 137, 139, 145, 146, 148, 150, 152, 154, 160, 162, 164, 166, 167, 169, 172, 174, 177, 179, 181, 186, 188, 189, 191, 193, 195, 198, 200, 202, 204, 209, 211, 213, 216, 218 Node Group Names 176 Node Highest Version 178 Node ID 107 Node Max Capacity 117 Node Max Util 118 Node Min Capacity 117 Node Min Util 117 Node Name 43, 107, 214 Node Order 38 Node Status 108 Node To Active Group 174 Node 107 NodeLowestVersion 178 Nodes 177 Nodes State Rollup 179 Normal Message Queue Length 166 Number of Collections 185 Object Name 181 Object Status 182 Object 182 Output Queue Length 156 overview 27 Owner Node 37 Packets 157 Packets Outbound Discarded 156 Packets Outbound Errors 156 Packets Received 158 Packets Received Discarded 157 Packets Received Errors 157 Packets Sent 158 Page Faults 141 Page Faults per Sec 34 Page Reads 142 Page Writes 142 Pages Input 142 Pages Output 143 Partial Read 60 Partial Read per sec 60 Pending Timeout 207 Percent Committed Bytes In Use 140 Percent Current CSV Cache Size 55 Percent Disk Read Time 122 Percent Disk Write Time 121 Percent Free Space 121 Percent Idle Time 113 Percent Interrupt Time 113 Percent Privileged Time 35, 114 Percent Processor Time 35, 113 Percent User Mode Time 35 Percent User Time 114 Percentage Memory Free 102, 131 Percentage Memory Used 102, 130 Percentage Network Used 106, 134 Percentage Processor Used 101, 130 Percentage Quorum Free 104, 132 Percentage Quorum Used 104, 132 Index 363

attributes (continued) Percentage Shared Storage Free 105, 134 Percentage Shared Storage Used 105, 133 Percentage Shared Storage Utilization 215 Performance Object Status 181 Persistent State 196, 205 PID 34 Pool Paged Bytes 143 Pool Paged MB 144 PostUpdate Script 40 Precentage Processor Free 102, 130 PreUpdate Script 40 Previous RG Node 175 Processor 112 Query Name 181 Quorum Arbitration Time Maximum 187 Quorum Arbitration Time Minimum 187 Quorum Available 103, 132 Quorum Configuration 186 Quorum Log File Size 186 Quorum Path 103, 131, 187 Quorum Total Size 103, 131 Quorum 187 Quorum Utilization 103, 131 Read Latency 78 Read Queue Length 78 Reads 79 Reads per sec 79 Reboot Timeout Minutes 39 Received MB 159 Reconnect Count 166 Redirected Read Bytes 79, 90 Redirected Read Bytes per sec 80 Redirected Read KB 80 Redirected Read KB per sec 80 Redirected Read Latency 81 Redirected Read Queue Length 81 Redirected Reads 81, 90 Redirected Reads Avg Queue Length 82 Redirected Reads per sec 82 Redirected Write Bytes 82, 91 Redirected Write Bytes per sec 83 Redirected Write KB 82 Redirected Write KB per sec 83 Redirected Write Latency 83 Redirected Write Queue Length 84 Redirected Writes 84, 91 Redirected Writes Avg Queue Length 85 Redirected Writes per sec 84 Refresh Interval 185 Require All Nodes Online 39 Resource Control Manager 188 Resource Controls 211 Resource 195, 201, 203 Resource Failure 211 Resource Failure Access Violation 212 Resource Failure Deadlock 212 Resource Group Moves 189 Resource Group Name 37 Resource Group To Preferred Node 191 Resource Group To Resource 193 Resource Groups 195 Resource Groups State Rollup 198 Resource Name 194, 200, 202 Resource State 194, 201, 203 Resource To Dependent Resource 200 Resource To Possible Owner 202 attributes (continued) Resource Controls 213 Resources 204 Resources Online 212 Resources State Rollup 209 Resources Summary 211 Restart Action 207 Restart Period 207 Restart Threshold 207 Result 43 Retry Period On Failure 208 RG Node Changed 175 RHS Processes 188 RHS Restarts 189 Role 169 Run Completion Time 41 Run ID 41 Sent MB 159 Shared Storage Available 104, 133, 214 Shared Storage Path 214 Shared Storage State 215 Shared Storage Summary 213 Shared Storage Total Size 105, 133, 214 Shared Storage Utilization 105, 133, 215 Standard Deviation 111, 116, 127, 128, 146, 148, 154, 161, 163, 165, 174, 180, 191, 200, 210 Start Date 37 State 152, 169, 179, 198, 208 State of Group 176 State of Node 175, 192, 203 State Raw 150, 168, 177, 195, 204 Status 32, 37 Stop After 39 Structural Risk 216 System Information 101, 130 System Name 151 Thread Count 34 Thread Pool Active Threads 219 Thread Pool Avg Active Threads 219 Thread Pool Avg Job Wait 221 Thread Pool Avg Queue Length 220 Thread Pool Max Active Threads 220 Thread Pool Max Queue Length 221 Thread Pool Max Size 219 Thread Pool Min Active Threads 219 Thread Pool Min Queue Length 220 Thread Pool Queue Length 220 Thread Pool Size 218 Thread Pool Status 218 Thread Pool Total Jobs 221 Time Generated 136 Timestamp 32, 37, 41, 44, 45, 48, 52, 61, 67, 88, 92, 101, 107, 108, 110, 112, 115, 116, 121, 125, 127, 129, 137, 139, 145, 147, 148, 150, 152, 154, 160, 162, 164, 166, 168, 170, 173, 175, 177, 179, 181, 186, 188, 189, 191, 193, 195, 198, 200, 202, 204, 209, 211, 213, 216, 218 Total 111, 116, 126, 128, 146, 148, 153, 161, 163, 165, 174, 180, 190, 199, 210 Total Capacity 118 Total MB 159 Total Util 119 33, 205 Unacknowledged Message Queue Length 167 Uniform Commitment 120 Unitary Commitment 120 Update 44 Update ID 43 364 Microsoft Cluster Server agent: User's Guide

attributes (continued) Update Messages 138 Update Messages Delta 138 Update Run Status 43 Update Timestamp 43 Update Title 43 Urgent Message Queue Length 167 Virtual Size 34 Volume Name 45 Volume Offset 45 Volume Pause Count Disk 85 Volume Pause Count Network 85 Volume Pause Count Other 86 Volume Pause Count Total 86 Volume State 86 Warn After 39 Weeks of Month 40 Working Set Size 34 Write Latency 87 Write Queue Length 87 Writes 87 Writes per sec 88 Auto FailBack attribute 196 Availability situations 227 workspaces descriptions 17 Availability attribute group 32 Availability workspace 17 Available Memory MB attribute 140 Available Nodes attribute 217 Average attribute 111, 115, 126, 128, 145, 147, 153, 161, 163, 165, 173, 180, 190, 199, 210 Average Collection Duration attribute 185 B Backup State attribute 47 Bring Resource Group online action 246 Bring Resource online action 247 Build Number attribute 178 Bytes Received attribute 155 Bytes Sent attribute 155 Bytes Total attribute 158 C Cache Bytes attribute 140 Cache Bytes Peak attribute 141 Cache Faults attribute 141 Cache Hit Percent attribute 185 Cache Hits attribute 185 Cache IO Read Bytes attribute 52 Cache IO Read Bytes per sec attribute 53 Cache IO Read KB per sec attribute 53 Cache IO Read MB attribute 53 Cache MB attribute 144 Cache Misses attribute 185 Cache Peak MB attribute 144 Cache Read attribute 54 Cache Read per sec attribute 54 Cache Size Configured MB attribute 54 Cache Size Current MB attribute 55 Cache State attribute 55 calculate historical data disk space 221 Canceled Updates attribute 42 capacity planning for historical data 221 CAU Configuration attribute group 36 CAU Last Run attribute group 41 CAU Plugin Arguments attribute 38 CAU Plugin Name attribute 37 Cluster Configuration Summary workspace 19 Cluster Dashboard situations 228 workspaces descriptions 18 Cluster Dashboard workspace 18 Cluster Domain attribute group 44 Cluster Name attribute 101, 129, 213 Cluster Shared Volume attribute group 45 Cluster Shared Volume Block Redirection and Volume Coordinator Statistics workspace 18 Cluster Shared Volume Block Redirection attribute group 48 Cluster Shared Volume Cache and Volume manager Statistics workspace 19 Cluster Shared Volume Cache attribute group 52 Cluster Shared Volume Coordinator attribute group 61 Cluster Shared Volume File System attribute group 66 Cluster Shared Volume File System Statistics workspace 19 Cluster Shared Volume IO attribute group 88 Cluster Shared Volume Manager attribute group 92 Cluster Shared Volume Name attribute 45 Cluster Shared Volume workspace 18 Cluster Summary attribute group 101 Cluster Topology attribute group 107 Cluster Topology workspace 19 Command Line attribute 35 commands tacmd addsystem 14 Take Action 245 Commit Limit MB attribute 143 Committed MB attribute 144 components 2 IBM Tivoli Monitoring 2 configuration 11 agent 7 fields 13 problems and workarounds 277 remote 14 values 13 Configuration situations 232 workspaces descriptions 19 Configuration attribute group 108 Configuration Name attribute 40 Configuration workspace 20 configuring the monitoring agent 7 Connect To Node attribute 108 Connection attribute 108 Core Resource attribute 205 CPU Interrupts Rollup attribute group 110 CPU per Node attribute group 111 CPU per Node Rollup attribute group 114 Create File attribute 61, 67 Create File per sec attribute 61, 67 CSV Node Name attribute 46 CSV Resource Name attribute 46 CSV Resource State attribute 46 Current Bandwidth attribute 155 Current Bandwidth Gbps attribute 159 Current Bandwidth MB attribute 159 Current Capacity attribute 119 Index 365

Current Disk Queue attribute 124 Current Health attribute 216 Current Host Server attribute 101, 129 Current RG Node attribute 175 D data collection 4 data sources 4 Database Update Messages attribute 138 Database Update Messages Delta attribute 138 Days of Week attribute 40 Default Network Role attribute 109 Degradation Risk attribute group 116 Degraded Capacity attribute 119 Delete Requires All Nodes attribute 206 Delete Resource Group action 248 Dependent Resource attribute 202 Dependent Resource Name attribute 201 Dependent Resource State attribute 201 attribute 47, 109, 152, 169, 179, 198, 208 of Group attribute 176 of Node attribute 176, 193, 204 descriptions 227 detailed 274 developerworks website 354 Device ID attribute 151 Direct IO Failure Redirection attribute 92 Direct IO Failure Redirection per sec attribute 92 Discovery Library Adapter 349 See DLA Discovery Library Toolkit 349 installing 350 Disk attribute 121 Disk attribute group 120 disk capacity planning for historical data 221 Disk IO Read Bytes attribute 55 Disk IO Read Bytes per sec attribute 56 Disk IO Read KB per sec attribute 56 Disk IO Read MB attribute 56 Disk IO Reads attribute 57 Disk IO Reads per sec attribute 57 Disk MB Rollup attribute group 125 Disk PCT Rollup attribute group 127 Disk Read Bytes attribute 123 Disk Read MB attribute 125 Disk Reads attribute 123 Disk Transfers attribute 124 Disk Used Percent attribute 124 Disk Write Bytes attribute 122 Disk Write MB attribute 125 Disk Writes attribute 123 DLA 339, 349 data model 339 classes 339 documentation See publications Domain attribute 44, 106, 135 Duration attribute 42 E Enable Firewall Rules attribute 39 enhancements 2 Enterprise Cluster Summary attribute group 129 Enterprise Level Cluster Dashboard workspace 17 Error Code attribute 44, 182 event mapping 309 Event API Version attribute 137 Event Category attribute 136 Event ID attribute 136 Event Keywords attribute 137 Event Level attribute 136 Event Log situations 232 workspaces descriptions 20 Event Log attribute group 135 Event Log workspace 20 Event attribute 135 Event attribute 135 F Failback Window End attribute 197 Failback Window Start attribute 197 Failed Updates attribute 42 Failover Period attribute 196 Failover Threshold attribute 197 Fault State attribute 47 Fewest Nodes Resource attribute 217 Files Invalidated During Resume attribute 68 Files Invalidated Other attribute 68 Files Opened attribute 68 Flushes attribute 69 Flushes per sec attribute 69 FreeMegabytes attribute 122 Full Name attribute 33 Functionality Test Message attribute 36 Functionality Test Status attribute 35 G Global Update Messages attribute group 137 Group attribute 192, 194 Group Name attribute 192, 193 Group State attribute 192, 194 Groups Online attribute 188 H Health Less A Node attribute 216 historical data calculate disk space 221 disk capacity planning 221 I IBM Tivoli Monitoring 2 overview 1 include file 351 installation 11 agent 7 problems and workarounds 277 remote 14 Installed Updates attribute 42 installing language packs 7 installing the monitoring agent 7 Integrated Service Management Library documentation 354 366 Microsoft Cluster Server agent: User's Guide

interface user 3 Interrupts attribute 112 Interval Weeks attribute 40 Intervals Skipped attribute 186 IO Read Avg Queue Length attribute 69 IO Read Bytes attribute 48, 57, 62, 69, 89, 93 IO Read Bytes per sec attribute 49, 58, 62, 70, 94 IO Read Bytes per sec Redirected attribute 94 IO Read Bytes Redirected attribute 95 IO Read KB per sec attribute 49, 58, 63, 70, 94 IO Read KB per sec Redirected attribute 95 IO Read KB Redirected attribute 95 IO Read Latency attribute 71 IO Read MB attribute 48, 58, 62, 70, 93 IO Read per sec Redirected attribute 93 IO Read Queue Length attribute 71 IO Reads attribute 49, 59, 63, 71, 89, 96 IO Reads per sec attribute 50, 59, 63, 72, 96 IO Reads Redirected attribute 96 IO Single Reads attribute 72 IO Single Reads per sec attribute 72 IO Single Writes attribute 73 IO Single Writes per sec attribute 73 IO Split Reads attribute 73 IO Split Reads per sec attribute 74 IO Split Writes attribute 74 IO Split Writes per sec attribute 74 IO Write Avg Queue Length attribute 75 IO Write Bytes attribute 50, 75, 89, 96 IO Write Bytes per sec attribute 50, 64, 76, 97 IO Write Bytes per sec Redirected attribute 98 IO Write Bytes Redirected attribute 98 IO Write KB per sec attribute 51, 64, 76, 97 IO Write KB per sec Redirected attribute 98 IO Write KB Redirected attribute 99 IO Write Latency attribute 76 IO Write MB attribute 50, 75, 97 IO Write Queue Length attribute 77 IO Writes attribute 51, 64, 77, 90, 99 IO Writes Bytes attribute 65 IO Writes MB attribute 65 IO Writes per sec attribute 51, 65, 77, 99 IO Writes per sec Redirected attribute 100 IO Writes Redirected attribute 100 Is Alive Poll Interval attribute 206 K KB Received attribute 170 KB Received Delta attribute 170 KB Sent attribute 171 KB Sent Delta attribute 171 KQ5_MSCS_Cluster_Unbalanced situation 236 KQ5_MSCS_InterfaceStateDown situation 233 KQ5_MSCS_InterfaceStateUnavail situation 232 KQ5_MSCS_InterfaceStateUnknown situation 232 KQ5_MSCS_InterfaceStateUnreach situation 233 KQ5_MSCS_Network_StateDown situation 234 KQ5_MSCS_Network_StateUnavail situation 234 KQ5_MSCS_Network_StateUnknown situation 233 KQ5_MSCS_Network_StateUnreach situation 235 KQ5_MSCS_Node_Changed situation 239 KQ5_MSCS_Node_Down situation 236 KQ5_MSCS_Node_Paused situation 235 KQ5_MSCS_Node_Unknown situation 235 KQ5_MSCS_PCPU_Utilization_Crit situation 230 KQ5_MSCS_PCPU_Utilization_Warn situation 230 KQ5_MSCS_PMemory_Free_Crit situation 229 KQ5_MSCS_PMemory_Free_Warn situation 228 KQ5_MSCS_PNW_Utilization_Crit situation 229 KQ5_MSCS_PNW_Utilization_Warn situation 229 KQ5_MSCS_QrmDiskSpace_Critical situation 237 KQ5_MSCS_QrmDiskSpace_Warning situation 237 KQ5_MSCS_Resource_Failed situation 240 KQ5_MSCS_Resource_Inherited situation 242 KQ5_MSCS_Resource_Initializing situation 242 KQ5_MSCS_Resource_Offline situation 240 KQ5_MSCS_Resource_Pending situation 240 KQ5_MSCS_Resource_Pending_Off situation 241 KQ5_MSCS_Resource_Pending_On situation 241 KQ5_MSCS_Resource_Unknown situation 241 KQ5_MSCS_RG_Failed situation 237 KQ5_MSCS_RG_Offline situation 238 KQ5_MSCS_RG_PartiallyOnLine situation 238 KQ5_MSCS_RG_Unknown situation 239 KQ5_MSCS_StorageSpace_Critical situation 231 KQ5_MSCS_StorageSpace_Warning situation 231 KQ5_Process_Down situation 227 KQ5_WMI_Obj_Not_Available situation 228 L language packs 7 installing 7 silent installation 7 Last Collection Duration attribute 184 Last Collection Finished attribute 184 Last Collection Start attribute 184 Less A Node attribute 217 Less A Node Percent attribute 218 list of messages 302 Log Name attribute 135 Looks Alive Poll Interval attribute 206 Lowest Health Resource attribute 216 LRU Cache Size Current MB attribute 59 LRU Cache Size Target MB attribute 60 M Maintenance File attribute 186 Major Version attribute 178 Max Capacity attribute 117 Max Failed Nodes attribute 38 Max Number Nodes attribute 109 Max Retries Per Node attribute 38 Max Util attribute 118 Maximum attribute 110, 115, 125, 127, 145, 147, 152, 160, 162, 164, 173, 179, 190, 198, 209 Memory attribute group 139 Memory MB Rollup attribute group 144 Memory Module attribute 140 Memory PCT Rollup attribute group 146 Message attribute 136 messages contents 302 for IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent 302 format 302 Messages Outstanding attribute 149 Messages Received attribute 171 Messages Received Delta attribute 171 Index 367

Messages Sent attribute 149, 172 Messages Sent Delta attribute 149, 172 Metadata IO attribute 66, 77, 90 Metadata IO per sec attribute 66, 78 Microsoft Cluster Server situations 227 workspaces descriptions 16 Microsoft Cluster Server agent performance considerations 295 Microsoft Cluster Server workspace 16 Min Capacity attribute 117 Min Util attribute 118 Minimum attribute 110, 115, 126, 128, 145, 147, 153, 160, 162, 164, 173, 180, 190, 199, 209 Minor Version attribute 178 Monitored Resource attribute 208 Move Resource Group action 249 MRR Messages attribute group 148 N Name attribute 32, 41, 52, 61, 66, 88, 91, 100, 109, 112, 139, 150, 167, 168, 170, 177, 189, 195, 204, 213 Name of Group attribute 176 Name of Node attribute 121, 139, 154, 192, 203 Network Interface attribute 155 Network Interfaces situations 232 workspaces descriptions 21 Network Interfaces attribute group 150 Network Interfaces State Rollup attribute group 152 Network Interfaces workspace 21 Network Name attribute 151 Network Performance attribute group 154 Network Performance Packets Rollup attribute group 160 Network Performance Received Rollup attribute group 162 Network Performance Sent Rollup attribute group 164 Network Performance workspace 21 Network Reconnections attribute group 165 Network Reconnections workspace 21 Networks situations 233 workspaces descriptions 21 Networks attribute group 167 Networks Messages attribute group 169 Networks Messages workspace 21 Networks Rollup attribute group 172 Networks workspace 21 new in this release 2 No of Shared Storage attribute 106, 134 Node attribute 32, 36, 41, 44, 45, 48, 52, 61, 67, 88, 92, 101, 107, 108, 110, 112, 114, 116, 120, 125, 127, 129, 135, 137, 139, 145, 146, 148, 150, 152, 154, 160, 162, 164, 166, 167, 169, 172, 174, 177, 179, 181, 186, 188, 189, 191, 193, 195, 198, 200, 202, 204, 209, 211, 213, 216, 218 Node CPU workspace 22 Node Disks workspace 22 Node Group Names attribute 176 Node Highest Version attribute 178 Node ID attribute 107 Node Max Capacity attribute 117 Node Max Util attribute 118 Node Memory workspace 22 Node Min Capacity attribute 117 Node Min Util attribute 117 Node Name attribute 43, 107, 214 Node Order attribute 38 Node Status attribute 108 Node To Active Group attribute group 174 Node attribute 107 NodeLowestVersion attribute 178 Nodes situations 235 workspaces descriptions 22 Nodes attribute group 177 Nodes State Rollup attribute group 179 Nodes workspace 23 Normal Message Queue Length attribute 166 Number of Collections attribute 185 O Object Name attribute 181 Object Status attribute 182 Object attribute 182 operating systems 7 Output Queue Length attribute 156 overview IBM Tivoli Monitoring 1 Owner Node attribute 37 P Packets attribute 157 Packets Outbound Discarded attribute 156 Packets Outbound Errors attribute 156 Packets Received attribute 158 Packets Received Discarded attribute 157 Packets Received Errors attribute 157 Packets Sent attribute 158 Page Faults attribute 141 Page Faults per Sec attribute 34 Page Reads attribute 142 Page Writes attribute 142 Pages Input attribute 142 Pages Output attribute 143 Partial Read attribute 60 Partial Read per sec attribute 60 Pause Node action 251 Pending Timeout attribute 207 Percent Committed Bytes In Use attribute 140 Percent Current CSV Cache Size attribute 55 Percent Disk Read Time attribute 122 Percent Disk Write Time attribute 121 Percent Free Space attribute 121 Percent Idle Time attribute 113 Percent Interrupt Time attribute 113 Percent Privileged Time attribute 35, 114 Percent Processor Time attribute 35, 113 Percent User Mode Time attribute 35 Percent User Time attribute 114 Percentage Memory Free attribute 102, 131 Percentage Memory Used attribute 102, 130 Percentage Network Used attribute 106, 134 Percentage Processor Used attribute 101, 130 Percentage Quorum Free attribute 104, 132 Percentage Quorum Used attribute 104, 132 Percentage Shared Storage Free attribute 105, 134 Percentage Shared Storage Used attribute 105, 133 368 Microsoft Cluster Server agent: User's Guide

Percentage Shared Storage Utilization attribute 215 performance considerations 295 Performance Object Status attribute group 181 Performance Object Status workspace 17 Persistent State attribute 196, 205 PID attribute 34 policies 257 Pool Paged Bytes attribute 143 Pool Paged MB attribute 144 PostUpdate Script attribute 40 Precentage Processor Free attribute 102, 130 prerequisite checker 10 prerequisite publications 353 prerequisites 10 PreUpdate Script attribute 40 Previous RG Node attribute 175 probe rules file include 351 problems and workarounds 277 agent-specific 283 agent-specific workspaces 289 configuration 277 install 277 remote deployment 280 situations 295 Take Action commands 299 Tivoli Common Reporting 299 workspaces 289 Processor attribute 112 publications 353, 354 developerworks website 354 IBM Tivoli Monitoring 353 Integrated Service Management Library 354 prerequisite 353 Redbooks 354 related 354 Technotes 354 wikis 354 Q queries, using attributes 27 Query Name attribute 181 Query Object Status workspace 20 Quorum Arbitration Time Maximum attribute 187 Quorum Arbitration Time Minimum attribute 187 Quorum Available attribute 103, 132 Quorum Configuration attribute group 186 Quorum Configuration workspace 20 Quorum Log File Size attribute 186 Quorum Path attribute 103, 131, 187 Quorum Total Size attribute 103, 131 Quorum attribute 187 Quorum Utilization attribute 103, 131 R Read Latency attribute 78 Read Queue Length attribute 78 Reads attribute 79 Reads per sec attribute 79 Reboot Timeout Minutes attribute 39 Received MB attribute 159 Reconnect Count attribute 166 Redbooks 354 Redirected Read Bytes attribute 79, 90 Redirected Read Bytes per sec attribute 80 Redirected Read KB attribute 80 Redirected Read KB per sec attribute 80 Redirected Read Latency attribute 81 Redirected Read Queue Length attribute 81 Redirected Reads attribute 81, 90 Redirected Reads Avg Queue Length attribute 82 Redirected Reads per sec attribute 82 Redirected Write Bytes attribute 82, 91 Redirected Write Bytes per sec attribute 83 Redirected Write KB attribute 82 Redirected Write KB per sec attribute 83 Redirected Write Latency attribute 83 Redirected Write Queue Length attribute 84 Redirected Writes attribute 84, 91 Redirected Writes Avg Queue Length attribute 85 Redirected Writes per sec attribute 84 Refresh Interval attribute 185 remote installation and configuration 14 remote deployment problems and workarounds 280 Require All Nodes Online attribute 39 requirements 7 Resource Control Manager attribute group 188 Resource Controls attribute 211 Resource attribute 195, 201, 203 Resource Failure Access Violation attribute 212 Resource Failure attribute 211 Resource Failure Deadlock attribute 212 Resource Group Associations workspace 23 Resource Group Moves attribute group 189 Resource Group Name attribute 37 Resource Group to Possible Node workspace 23 Resource Group To Preferred Node attribute group 191 Resource Group To Resource attribute group 193 Resource Groups situations 237 workspaces descriptions 23 Resource Groups attribute group 195 Resource Groups State Rollup attribute group 198 Resource Groups workspace 23 Resource Name attribute 194, 200, 202 Resource State attribute 194, 201, 203 Resource Summary workspace 23 Resource To Dependent Resource attribute group 200 Resource To Possible Owner attribute group 202 Resource Controls attribute 213 Resources situations 239 workspaces descriptions 23 Resources attribute group 204 Resources Online attribute 212 Resources State Rollup attribute group 209 Resources Summary attribute group 211 Resources workspace 24 response file template 7 Restart Action attribute 207 Restart Period attribute 207 Restart Threshold attribute 207 Result attribute 43 Resume Node action 252 Retry Period On Failure attribute 208 RG Node Changed attribute 175 RHS Processes attribute 188 Index 369

RHS Restarts attribute 189 Role attribute 169 Run Completion Time attribute 41 Run ID attribute 41 S Sent MB attribute 159 Shared Storage Available attribute 104, 133, 214 Shared Storage Path attribute 214 Shared Storage State attribute 215 Shared Storage Summary attribute group 213 Shared Storage Total Size attribute 105, 133, 214 Shared Storage Utilization attribute 105, 133, 215 silent installation 7 silent installation of language packs 7 situations 227 additional information predefined, defined 225 KQ5_MSCS_Cluster_Unbalanced 236 KQ5_MSCS_InterfaceStateDown 233 KQ5_MSCS_InterfaceStateUnavail 232 KQ5_MSCS_InterfaceStateUnknown 232 KQ5_MSCS_InterfaceStateUnreach 233 KQ5_MSCS_Network_StateDown 234 KQ5_MSCS_Network_StateUnavail 234 KQ5_MSCS_Network_StateUnknown 233 KQ5_MSCS_Network_StateUnreach 235 KQ5_MSCS_Node_Changed 239 KQ5_MSCS_Node_Down 236 KQ5_MSCS_Node_Paused 235 KQ5_MSCS_Node_Unknown 235 KQ5_MSCS_PCPU_Utilization_Crit 230 KQ5_MSCS_PCPU_Utilization_Warn 230 KQ5_MSCS_PMemory_Free_Crit 229 KQ5_MSCS_PMemory_Free_Warn 228 KQ5_MSCS_PNW_Utilization_Crit 229 KQ5_MSCS_PNW_Utilization_Warn 229 KQ5_MSCS_QrmDiskSpace_Critical 237 KQ5_MSCS_QrmDiskSpace_Warning 237 KQ5_MSCS_Resource_Failed 240 KQ5_MSCS_Resource_Inherited 242 KQ5_MSCS_Resource_Initializing 242 KQ5_MSCS_Resource_Offline 240 KQ5_MSCS_Resource_Pending 240 KQ5_MSCS_Resource_Pending_Off 241 KQ5_MSCS_Resource_Pending_On 241 KQ5_MSCS_Resource_Unknown 241 KQ5_MSCS_RG_Failed 237 KQ5_MSCS_RG_Offline 238 KQ5_MSCS_RG_PartiallyOnLine 238 KQ5_MSCS_RG_Unknown 239 KQ5_MSCS_StorageSpace_Critical 231 KQ5_MSCS_StorageSpace_Warning 231 KQ5_Process_Down 227 KQ5_WMI_Obj_Not_Available 228 overview 225 predefined 225 problems and workarounds 295 Situation Editor 225 situations, using attributes 27 Standard Deviation attribute 111, 116, 127, 128, 146, 148, 154, 161, 163, 165, 174, 180, 191, 200, 210 Start Date attribute 37 State attribute 152, 169, 179, 198, 208 State of Group attribute 176 State of Node attribute 175, 192, 203 State Raw attribute 150, 168, 177, 195, 204 Status attribute 32, 37 Stop After attribute 39 Structural and Degradation Risk situations 245 workspaces descriptions 24 Structural and Degradation Risk workspace 24 Structural Risk attribute group 216 Structural Risk workspace 24 support list of messages 302 System Information attribute 101, 130 System Name attribute 151 T tacmd addsystem command 14 Take Action commands additional information 245 Bring Resource Group online 246 Bring Resource online 247 Delete Resource Group 248 Move Resource Group 249 overview 245 Pause Node 251 predefined 245, 257 problems and workarounds 299 Resume Node 252 Take Resource Group offline 253 Take Resource offline 255 take actions descriptions 245 Take Resource Group offline action 253 Take Resource offline action 255 Technotes 354 Thread Count attribute 34 Thread Pool Active Threads attribute 219 Thread Pool Avg Active Threads attribute 219 Thread Pool Avg Job Wait attribute 221 Thread Pool Avg Queue Length attribute 220 Thread Pool Max Active Threads attribute 220 Thread Pool Max Queue Length attribute 221 Thread Pool Max Size attribute 219 Thread Pool Min Active Threads attribute 219 Thread Pool Min Queue Length attribute 220 Thread Pool Queue Length attribute 220 Thread Pool Size attribute 218 Thread Pool Status attribute group 218 Thread Pool Status workspace 18 Thread Pool Total Jobs attribute 221 Time Generated attribute 136 Timestamp attribute 32, 37, 41, 44, 45, 48, 52, 61, 67, 88, 92, 101, 107, 108, 110, 112, 115, 116, 121, 125, 127, 129, 137, 139, 145, 147, 148, 150, 152, 154, 160, 162, 164, 166, 168, 170, 173, 175, 177, 179, 181, 186, 188, 189, 191, 193, 195, 198, 200, 202, 204, 209, 211, 213, 216, 218 Tivoli Business Service Manager components for integrating with 349 configuring additional IBM Tivoli Monitoring web services 352 creating a service 351 creating data source mapping 352 installing Discovery Library Toolkit 350 integration 349 launching from Tivoli Enterprise Portal 352 370 Microsoft Cluster Server agent: User's Guide

Tivoli Business Service Manager (continued) Tivoli Enterprise Portal Tivoli Integration Facility (EIF) probe 349 viewing data in Tivoli Enterprise Portal 352 Tivoli Business Service Managerintegration tasks 350 Tivoli Common Reporting problems and workarounds 299 Tivoli Enterprise Console event mapping 309 Tivoli Event Integration Facility (EIF) probe configuring 351 Total attribute 111, 116, 126, 128, 146, 148, 153, 161, 163, 165, 174, 180, 190, 199, 210 Total Capacity attribute 118 Total MB attribute 159 Total Util attribute 119 tracing 274 troubleshooting 269 agent-specific 283 agent-specific workspaces 289 installation 277 problems and workarounds 277 remote deployment 280 situations 295 Take Action commands 299 Tivoli Common Reporting 299 uninstallation 277 workspaces 289 attribute 33, 205 U Unacknowledged Message Queue Length attribute 167 Uniform Commitment attribute 120 Unitary Commitment attribute 120 Update attribute 44 Update ID attribute 43 Update Messages attribute 138 Update Messages Delta attribute 138 Update Run Status attribute 43 Update Timestamp attribute 43 Update Title attribute 43 Urgent Message Queue Length attribute 167 user interface options 3 V views Availability workspace 17 Cluster Configuration Summary workspace 19 Cluster Dashboard workspace 18 Cluster Shared Volume Block Redirection and Volume Coordinator Statistics workspace 18 Cluster Shared Volume Cache and Volume manager Statistics workspace 19 Cluster Shared Volume File System Statistics workspace 19 Cluster Shared Volume workspace 18 Cluster Topology workspace 19 Configuration workspace 20 Enterprise Level Cluster Dashboard workspace 17 Event Log workspace 20 Microsoft Cluster Server workspace 16 Network Interfaces workspace 21 Network Performance workspace 21 Network Reconnections workspace 21 views (continued) Networks Messages workspace 21 Networks workspace 21 Node CPU workspace 22 Node Disks workspace 22 Node Memory workspace 22 Nodes workspace 23 Performance Object Status workspace 17 Query Object Status workspace 20 Quorum Configuration workspace 20 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 24 Thread Pool Status workspace 18 Virtual Size attribute 34 Volume Name attribute 45 Volume Offset attribute 45 Volume Pause Count Disk attribute 85 Volume Pause Count Network attribute 85 Volume Pause Count Other attribute 86 Volume Pause Count Total attribute 86 Volume State attribute 86 W Warn After attribute 39 Weeks of Month attribute 40 wikis 354 workarounds 277 Workflow Editor 257 Working Set Size attribute 34 workspaces Availability 17 Cluster Configuration Summary 19 Cluster Dashboard 18 Cluster Shared Volume 18 Cluster Shared Volume Block Redirection and Volume Coordinator Statistics 18 Cluster Shared Volume Cache and Volume manager Statistics 19 Cluster Shared Volume File System Statistics 19 Cluster Topology 19 Configuration 19, 20 descriptions 16 Enterprise Level Cluster Dashboard 17 Event Log 20 Microsoft Cluster Server 16 Network Interfaces 21 Network Performance 21 Network Reconnections 21 Networks 21 Networks Messages 21 Node CPU 22 Node Disks 22 Node Memory 22 Nodes 22, 23 Performance Object Status 17 predefined 15 problems and workarounds 289 Query Object Status 20 Quorum Configuration 20 Resource Group Associations 23 Resource Group to Possible Node 23 Index 371

workspaces (continued) Resource Groups 23 Resource Summary 23 Resources 23, 24 Structural and Degradation Risk 24 Structural Risk 24 Thread Pool Status 18 Workspaces additional information 15 overview 15 Write Latency attribute 87 Write Queue Length attribute 87 Writes attribute 87 Writes per sec attribute 88 372 Microsoft Cluster Server agent: User's Guide

Printed in USA SC27-2316-05