cluster622 user

8/17/2019 Cluster622 User

1/316

Tivoli ® IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent Version 6.2.2

User's Guide

SC27-2316-02


2/316


3/316

Tivoli ® IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Cluster Server Agent Version 6.2.2

User's Guide

SC27-2316-02


4/316

NoteBefore using this information and the product it supports, read the information in Appendix E, “Notices,” on page 291.

This edition applies to version 6.2.2 of IBM Tivoli Composite Application Manager for Microsoft Applications:Microsoft Cluster Server Agent (product number 5724-U17) and to all subsequent releases and modifications untilotherwise indicated in new editions.

© Copyright IBM Corporation 2007, 2010.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/316

Contents

Tables . . . . . . . . . . . . . . . vii

Chapter 1. Overview of the MicrosoftCluster Server Agent . . . . . . . . . 1IBM Tivoli Monitoring overview. . . . . . . . 1Features of the monitoring agent . . . . . . . 1Functions of the monitoring agent . . . . . . . 1New in this release . . . . . . . . . . . . 2Components of the IBM Tivoli Monitoringenvironment . . . . . . . . . . . . . . 4Agent Management Services . . . . . . . . . 4User interface options . . . . . . . . . . . 4

Chapter 2. Agent-specific installationand configuration information for the

monitoring agent . . . . . . . . . . . 7Installing language packs . . . . . . . . . . 7

Windows systems. . . . . . . . . . . . 7UNIX or Linux systems . . . . . . . . . . 7

Agent-specific installation and configuration. . . . 8Configuring the monitoring agent after installation 10

Configuration values . . . . . . . . . . 10Remote installation and configuration . . . . 11

Chapter 3. Workspaces reference . . . 13About workspaces . . . . . . . . . . . . 13More information about workspaces . . . . . . 13Cross-Linked Workspaces . . . . . . . . . . 14Predefined workspaces . . . . . . . . . . 14Agent Navigator items . . . . . . . . . . 15

Microsoft Cluster Server Agent Navigator item 15Availability Navigator item . . . . . . . . 16Cluster Dashboard Navigator item. . . . . . 17Configuration Navigator item . . . . . . . 18Event Log Navigator item . . . . . . . . 19Network Interfaces Navigator item . . . . . 19Networks Navigator item. . . . . . . . . 20Nodes Navigator item . . . . . . . . . . 21Resource Groups Navigator item . . . . . . 23Resources Navigator item . . . . . . . . 23Structural and Degradation Risk Navigator item 24

Chapter 4. Attributes reference . . . . 27About attributes . . . . . . . . . . . . . 27More information about attributes. . . . . . . 27Attribute groups and attributes for the MicrosoftCluster Server Agent . . . . . . . . . . . 27Availability attribute group . . . . . . . . . 31Cluster Domain attribute group . . . . . . . 36Cluster Shared Volume attribute group . . . . . 36Cluster Shared Volume IO attribute group . . . . 39Cluster Summary attribute group . . . . . . . 43Configuration attribute group . . . . . . . . 48CPU Interrupts Rollup attribute group . . . . . 50

CPU per Node attribute group . . . . . . . . 52CPU per Node Rollup attribute group . . . . . 54

Degradation Risk attribute group . . . . . . . 56Disk attribute group . . . . . . . . . . . 60Disk MB Rollup attribute group . . . . . . . 64Disk PCT Rollup attribute group . . . . . . . 66Enterprise Cluster Summary attribute group . . . 68Event Log attribute group . . . . . . . . . 74Global Update Messages attribute group . . . . 77Memory attribute group . . . . . . . . . . 78Memory MB Rollup attribute group . . . . . . 83Memory PCT Rollup attribute group . . . . . . 85MRR Messages attribute group . . . . . . . . 87Network Interfaces attribute group . . . . . . 88Network Interfaces State Rollup attribute group . . 91Network Performance attribute group . . . . . 93

Network Performance Packets Rollup attributegroup . . . . . . . . . . . . . . . . 98Network Performance Received Rollup attributegroup . . . . . . . . . . . . . . . . 100Network Performance Sent Rollup attribute group 102Network Reconnections attribute group . . . . 104Networks attribute group . . . . . . . . . 105Networks Messages attribute group . . . . . . 107Networks Rollup attribute group . . . . . . . 110Node To Active Group attribute group . . . . . 112Nodes attribute group . . . . . . . . . . 115Nodes State Rollup attribute group . . . . . . 117Performance Object Status attribute group . . . . 119Quorum Configuration attribute group . . . . . 124

Resource Control Manager attribute group . . . 126Resource Group Moves attribute group. . . . . 128Resource Group To Preferred Node attribute group 129Resource Group To Resource attribute group . . . 131Resource Groups attribute group . . . . . . . 133Resource Groups State Rollup attribute group . . 137Resource To Dependent Resource attribute group 139Resource To Possible Owner attribute group . . . 141Resources attribute group . . . . . . . . . 143Resources State Rollup attribute group . . . . . 147Resources Summary attribute group . . . . . . 149Shared Storage Summary attribute group . . . . 152Structural Risk attribute group . . . . . . . 154Thread Pool Status attribute group . . . . . . 156

Disk capacity planning for historical data . . . . 161

Chapter 5. Situations reference. . . . 165About situations . . . . . . . . . . . . 165More information about situations . . . . . . 165Predefined situations . . . . . . . . . . . 166Microsoft Cluster Server Agent Navigator item . . 167Availability Navigator item . . . . . . . . . 167

KQ5_Process_Down situation . . . . . . . 167KQ5_WMI_Obj_Not_Available situation . . . 168

Cluster Dashboard Navigator item . . . . . . 169

© Copyright IBM Corp. 2007, 2010 iii


6/316

KQ5_MSCS_PMemory_Free_Warn situation . . 169KQ5_MSCS_PMemory_Free_Crit situation. . . 169KQ5_MSCS_PNW_Utilization_Warn situation 170KQ5_MSCS_PNW_Utilization_Crit situation . . 170KQ5_MSCS_PCPU_Utilization_Warn situation 171KQ5_MSCS_PCPU_Utilization_Crit situation 172

Configuration Navigator item . . . . . . . . 172Event Log Navigator item . . . . . . . . . 172Network Interfaces Navigator item . . . . . . 172

KQ5_MSCS_InterfaceStateUnknown situation 172KQ5_MSCS_InterfaceStateUnavail situation . . 173KQ5_MSCS_InterfaceStateDown situation . . . 174KQ5_MSCS_InterfaceStateUnreach situation . . 174

Networks Navigator item . . . . . . . . . 175KQ5_MSCS_Network_StateUnknown situation 175KQ5_MSCS_Network_StateUnavail situation 175KQ5_MSCS_Network_StateDown situation . . 176KQ5_MSCS_Network_StateUnreach situation 177

Nodes Navigator item . . . . . . . . . . 177KQ5_MSCS_Node_Unknown situation . . . . 177KQ5_MSCS_Node_Paused situation . . . . . 178KQ5_MSCS_Node_Down situation . . . . . 178KQ5_MSCS_Cluster_Unbalanced situation. . . 179KQ5_MSCS_QrmDiskSpace_Warning situation 180KQ5_MSCS_QrmDiskSpace_Critical situation 180

Resource Groups Navigator item . . . . . . . 181KQ5_MSCS_RG_Failed situation . . . . . . 181KQ5_MSCS_RG_Offline situation. . . . . . 181KQ5_MSCS_RG_PartiallyOnLine situation. . . 182KQ5_MSCS_RG_Unknown situation. . . . . 183KQ5_MSCS_Node_Changed situation . . . . 183

Resources Navigator item . . . . . . . . . 184KQ5_MSCS_Resource_Failed situation . . . . 184KQ5_MSCS_Resource_Offline situation . . . . 184KQ5_MSCS_Resource_Pending situation . . . 185

KQ5_MSCS_Resource_Pending_On situation 186KQ5_MSCS_Resource_Pending_Off situation 186KQ5_MSCS_Resource_Unknown situation. . . 187KQ5_MSCS_Resource_Initializing situation . . 187KQ5_MSCS_Resource_Inherited situation . . . 188

Structural and Degradation Risk Navigator item 188

Chapter 6. Take Action commandsreference . . . . . . . . . . . . . 189About Take Action commands. . . . . . . . 189More information about Take Action commands 189Predefined Take Action commands . . . . . . 189Bring Resource Group online action . . . . . . 190Bring Resource online action . . . . . . . . 191

Take Resource Group offline action . . . . . . 192Take Resource offline action . . . . . . . . 193

Chapter 7. Policies reference. . . . . 195About policies . . . . . . . . . . . . . 195More information about policies . . . . . . . 195Predefined policies . . . . . . . . . . . 195

Chapter 8. Tivoli Common Reportingfor the monitoring agent . . . . . . 197Category 1: Performance reports . . . . . . . 199

Disk Utilization for Cluster Nodes report . . . 199Memory Utilization for Cluster Nodes report 200Cluster Hardware Interrupts report . . . . . 201CPU Utilization for Cluster Nodes report . . . 202Network Interface Activity for Single ClusterNode report . . . . . . . . . . . . . 203Resources Utilization Details for Single Nodereport . . . . . . . . . . . . . . . 204Resource Utilization Comparison for All Nodeson Single Cluster report . . . . . . . . . 205Cluster Nodes Utilization Summary report . . 206Cluster Utilization Summary report . . . . . 208Daily Heat Map for Cluster Nodes report . . . 209Utilization Heat Map for Single Resource report 210Generic Template report . . . . . . . . . 210Generic Details Template report . . . . . . 212

Category 2: Availability reports . . . . . . . 214Cluster Nodes Availability report. . . . . . 214Cluster Network Interface Availability report 214Cluster Resource Group Availability report . . 215Cluster Resource Availability report . . . . . 216Cluster Network Availability report . . . . . 216

Chapter 9. Troubleshooting . . . . . 219Gathering product information for IBM SoftwareSupport . . . . . . . . . . . . . . . 219Built-in troubleshooting features . . . . . . . 219Problem classification. . . . . . . . . . . 220Trace logging . . . . . . . . . . . . . 220

Overview of log file management . . . . . 220Principal trace log files . . . . . . . . . 221Setting RAS trace parameters . . . . . . . 223

Problems and workarounds . . . . . . . . 225Installation and configuration troubleshooting 225Remote deployment troubleshooting . . . . 230

Agent troubleshooting . . . . . . . . . 232Workspace troubleshooting . . . . . . . . 235Situation troubleshooting . . . . . . . . 242Take Action commands troubleshooting . . . 246Tivoli Common Reporting troubleshooting . . 246

Support information . . . . . . . . . . . 249Informational, warning, and error messages . . . 249

Message format . . . . . . . . . . . 249Microsoft Cluster Server Agent messages . . . 250

Appendix A. IBM Tivoli EnterpriseConsole event mapping . . . . . . . 253

Appendix B. Discovery LibraryAdapter for the monitoring agent . . . 275About the DLA. . . . . . . . . . . . . 275More information about DLAs. . . . . . . . 275Book Information . . . . . . . . . . . . 275Microsoft Cluster Server DLA data model classtypes represented in CDM . . . . . . . . . 276

Relationships . . . . . . . . . . . . 276MsCluster class. . . . . . . . . . . . 278MsClusterNode class . . . . . . . . . . 278MsClusterResourceGroup class . . . . . . 279MsClusterResource class . . . . . . . . . 280

iv Microsoft Cluster Server Agent: User's Guide


7/316

MsClusterService class . . . . . . . . . 281TMSAgent class . . . . . . . . . . . 282

Appendix C. Documentation library 285Microsoft Cluster Server Agent library . . . . . 285Prerequisite publications. . . . . . . . . . 285Related publications . . . . . . . . . . . 286

Other sources of documentation . . . . . . . 286

Appendix D. Accessibility . . . . . . 289

Navigating the interface using the keyboard . . . 289Magnifying what is displayed on the screen . . . 289

Appendix E. Notices . . . . . . . . 291Trademarks . . . . . . . . . . . . . . 293

Index . . . . . . . . . . . . . . . 295

Contents v


8/316

vi Microsoft Cluster Server Agent: User's Guide


9/316

Tables

1. Cross-linked workspaces within the MicrosoftCluster Server agent . . . . . . . . . 14

2. Cross-linked Workspaces to the MicrosoftHyper-V Server agent . . . . . . . . . 143. Cross-linked Workspaces to Windows OS

agent. . . . . . . . . . . . . . . 144. Capacity planning for historical data logged

by Microsoft Cluster Server Agent . . . . 1615. Supported databases . . . . . . . . . 1976. Information to gather before contacting IBM

Software Support . . . . . . . . . . 2197. Trace log files for troubleshooting agents 2218. Problems and solutions for installation and

configuration . . . . . . . . . . . 225

9. General problems and solutions foruninstallation . . . . . . . . . . . 228

10. Remote deployment problems and solutions 23011. Agent problems and solutions . . . . . . 23212. Workspace problems and solutions . . . . 23613. General situation problems and solutions 24314. Problems with configuring situations that you

solve in the Situation Editor . . . . . . 24415. Problems with configuration of situations that

you solve in the Workspace area . . . . . 24616. Take Action commands problems and

solutions . . . . . . . . . . . . . 24617. Tivoli Common Reporting for Microsoft

Cluster Server Agent problems and solutions . 247

© Copyright IBM Corp. 2007, 2010 vii


10/316

viii Microsoft Cluster Server Agent: User's Guide


11/316

Chapter 1. Overview of the Microsoft Cluster Server Agent

The IBM Tivoli Composite Application Manager (ITCAM) for MicrosoftApplications: Microsoft Cluster Server Agent software provides you with the

capability to monitor Microsoft Cluster Server, and to perform basic actions withMicrosoft Cluster Server. This chapter provides a description of the features,components, and interface options for the Microsoft Cluster Server Agent.

IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Microsoft Cluster Server Agent.IBM Tivoli Monitoring provides a way to monitor the availability and performanceof 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 totroubleshoot system problems.

You can use IBM Tivoli Monitoring to perform the following tasks:v Monitor for alerts on the systems that you are managing by using predefined

situations or custom situations.

v Establish your own performance thresholds.

v Trace the causes leading to an alert.

v Gather comprehensive data about system conditions.

v Use policies to perform actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. Byproviding a consolidated view of your environment, the Tivoli Enterprise Portalpermits you to monitor and resolve performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” onpage 285 for complete information about IBM Tivoli Monitoring and the TivoliEnterprise Portal.

Features of the monitoring agent

The Microsoft Cluster Server Agent software can identify, notify you of, and correctcommon problems with the application that it monitors. The software includes thefollowing features:

v Monitoring

v Data gathering

v Operations management

Functions of the monitoring agent

The Microsoft Cluster Server Agent provides the following functions:

Availability and resource monitoringMonitors availability for Cluster and Cluster resources

Error/event log MonitoringMonitor for all events in the MSCS log. No specific situations are plannedfor the log monitoring.

© Copyright IBM Corp. 2007, 2010 1


12/316

Performance monitoringMSCS does not currently keep Cluster performance attributes

ReportingProvides a history enablement file that enables the agent to generatereports for all metrics that are collected.

Cluster Resource Availability

Provides availability monitoring for the cluster servers’ key monitoringpoints: cluster level, cluster nodes, cluster resource groups, clusterresources, and cluster networks.

Cluster Resources UsageProvides cluster resource usage across the nodes of the cluster and reportsthreats in capacity availability for processor, memory, disk, and networks.

Cluster DashboardProvides information about cluster shared volume (CSV), cluster sharedvolume I/O, and cluster summary for all clusters in an organization. Thecluster dashboard also provides information about processor utilizationand the utilization of shared storage summary.

Take ActionsActions are provided to take resource, and the resource group offline andto take it online.

New in this release

For version 6.2.2 of the Microsoft Cluster Server Agent, the followingenhancements have been made since version 6.2.0 Interim Feature 1:

v Additional supported operating systems as listed in the Microsoft Cluster Serveragent prerequisites topic on the IBM Tivoli Monitoring for MicrosoftApplications Information Center.

v New attribute groups

– Cluster Shared Volume– Cluster Shared Volume IO

– Cluster Summary

– Global Update Messages

– MRR Messages

– Networks Messages

– Network Reconnections

– Resource Control Manager

– Resources Summary

– Resource To Dependent Resource

– Shared Storage Summaryv New or changed attributes in the following attribute groups

– Event Log

– Network Performance

v New workspaces

– Enterprise Level Cluster Dashboard

– Cluster Dashboard

– Cluster Shared Volume

– Network Messages

2 Microsoft Cluster Server Agent: User's Guide


13/316



v Updated workspaces

– Network performance

– Event Log

v New views

– Bytes Sent/Received

– Cluster Capacity Details

– Cluster Shared Storage

– Cluster Shared Volume

– Cluster Shared Volume IO

– Enterprise Level Cluster Capacity

– IO Read Bytes

– IO Write Bytes

– Message Queue Status

– Messages Sent/Received

– Network Messages Sent/Received


– Quorum Usage


– Resource To Dependent Resource

– Resources Online

– System Processor Usage

– System Memory Usage

– Shared Storage Usage

– Top 5 Cluster Systems Having High Processor Usage

– Top 5 Cluster Systems Having High Memory Usage– Top 5 Clusters Having High Quorum Usage

– Top 5 Clusters Having High Shared Storage Usage

v New situations

– KQ5_MSCS_PMemory_Free_Warn

– KQ5_MSCS_PMemory_Free_Crit

– KQ5_MSCS_PNW_Utilization_Warn

– KQ5_MSCS_PNW_Utilization_Crit

– KQ5_MSCS_PCPU_Utilization_Warn

– KQ5_MSCS_PCPU_Utilization_Crit

v

New Take Action commands– Bring Resource Online

– Take Resource Offline

– Bring Resource Group Online

– Take Resource Group Offline

v Updated kq5.baroc file to support TEC event mapping

v Integration with Agent Management Services to monitor the availability of theagent. Support for Agent Management Services is available on IBM TivoliMonitoring V6.2.2, Fix Pack 1, or later.

Chapter 1. Overview of the Microsoft Cluster Server Agent 3


14/316

v Support for native 64-bit agent.

v Integration with IBM Tivoli Application Dependency Discovery Manager(TADDM).

Components of the IBM Tivoli Monitoring environment

After you install and set up the Microsoft Cluster Server Agent, you have anenvironment that contains the client, server, and monitoring agent implementationfor IBM Tivoli Monitoring. This environment contains the following components:

v Tivoli Enterprise Portal client with a Java™-based user interface for viewing andmonitoring your enterprise.

v Tivoli Enterprise Portal Server that is placed between the client and the TivoliEnterprise Monitoring Server and enables retrieval, manipulation, and analysisof data from the monitoring agents. The Tivoli Enterprise Portal Server is thecentral repository for all user data.

v Tivoli Enterprise Monitoring Server that acts as a collection and control point foralerts received from the monitoring agents, and collects their performance andavailability data. The Tivoli Enterprise Monitoring Server is also a repository forhistorical data.

v IBM Tivoli Enterprise Console is an optional component, which acts as a centralcollection point for events from a variety of sources, including events from otherTivoli® software applications, Tivoli partner applications, custom applications,network management platforms, and relational database systems. You can viewthese events through the Tivoli Enterprise Portal (using the event viewer), andyou can forward events from IBM Tivoli Monitoring situations to the IBM TivoliEnterprise Console component.

v IBM Tivoli Netcool/OMNIbus is an optional component and an alternative tothe IBM Tivoli Enterprise Console. The Netcool/OMNIbus software is a servicelevel management (SLM) system that delivers real-time, centralized monitoringof complex networks and IT domains. The Tivoli Netcool/OMNIbus componentswork together to collect and manage network event information.

v Tivoli Common Reporting is a separately installable feature available to users of Tivoli software that provides a consistent approach to generating andcustomizing reports. Some individual products provide reports that are designedfor use with Tivoli Common Reporting, and have a consistent look and feel.

Agent Management Services

Microsoft Cluster Server Agent can be managed by IBM Tivoli Monitoring AgentManagement Services. These services are available in the following IBM TivoliMonitoring OS agents: Windows, Linux, and UNIX. The services are designed tokeep Microsoft Cluster Server Agent available, and to provide information aboutthe status of the product to the Tivoli Enterprise Portal. Support for Agent

Management Services is available on IBM Tivoli Monitoring V6.2.2, Fix Pack 1 orlater. For more information about Agent Management Services, see the IBM Tivoli Monitoring Administrator's Guide.

User interface options

Installation of the base software and other integrated applications provides thefollowing interfaces that you can use to work with your resources and data:

Tivoli Enterprise Portal browser client interfaceThe browser client interface is automatically installed with the Tivoli



15/316

Enterprise Portal Server. To start the Tivoli Enterprise Portal browser clientin your Internet browser, enter the URL for a specific Tivoli EnterprisePortal browser client installed on your Web server.

Tivoli Enterprise Portal desktop client interfaceThe desktop client interface is a Java-based graphical user interface (GUI)on a Windows® or Linux® workstation.

Manage Tivoli Enterprise Monitoring Services windowThe window for the Manage Tivoli Enterprise Monitoring Services utility isused for configuring the agent and starting Tivoli services not designatedto start automatically.

IBM Tivoli Enterprise ConsoleAn event management application that integrates system, network,database, and application management to help ensure the optimalavailability of an IT service for an organization.

Tivoli Netcool/OMNIbus event listYou can use the event list to monitor and manage alerts. An alert is createdwhen the ObjectServer receives an event, alarm, message, or data item.Each alert is made up of columns (or fields) of information that are held ina row in the ObjectServer alerts.status table. In addition, the TivoliNetcool/OMNIbus Web GUI is a Web-based application that processesnetwork events from one or more data sources and presents the event datain various graphical formats.

Tivoli Common ReportingA Web user interface for specifying report parameters and other reportproperties, generating formatted reports, scheduling reports, and viewingreports. The user interface is based on the Tivoli Integrated Portal.

Chapter 1. Overview of the Microsoft Cluster Server Agent 5


16/316



17/316

Chapter 2. Agent-specific installation and configurationinformation for the monitoring agent

Before installing and configuring the agent, make sure your environment meets therequirements for the Microsoft Cluster Server Agent. See the Prerequisites topic forthe agent on the IBM Tivoli Monitoring for Microsoft Applications InformationCenter at https://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itmfms.doc/welcome.htm.

To install and configure the Microsoft Cluster Server Agent, use the procedures forinstalling monitoring agents in the IBM Tivoli Monitoring Installation and SetupGuide along with the agent-specific information in this chapter.

If you are performing a silent installation using a response file, see the informationabout performing a silent installation in the IBM Tivoli Monitoring Installation andSetup Guide.

Installing language packs

To install a language pack, first make sure that you have already installed theproduct in English. Then perform the following steps depending on whichoperating system you are using.

Windows systems1. Double-click lpinstaller.bat in the language pack CD to launch the installation

program.

2. Select the language of the installer and click OK.

3. Click Next on the Introduction panel.

4. Click Add/Update and click Next.

5. Select the folder in which the National Language Support package(NLSPackage) files are located.

Note: Usually the NLSPackage files are located in the nlspackage folder wherethe installer executable is located.

6. Select the language support for the agent of your choice and click Next.

Note: Hold down the Ctrl key for multiple selections.

7. Select the languages that you want to install and click Next.

8. Examine the installation summary page and click Next to begin installation.

9. Click Finish after installation completes to exit the installer.10. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server

component, and Eclipse Help Server if any of these components are installed.

UNIX or Linux systems1. Run the following command to create a temporary directory on the computer.

Make sure that the full path of the directory does not contain any spaces:

mkdir dir_name

2. Mount the language pack CD to the temporary directory you just created.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itmfa.doc/welcome.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itmfa.doc/welcome.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itmfa.doc/welcome.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itmfa.doc/welcome.htm


18/316

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

cd dir_namelpinstall.sh ITM Home Directory

Where ITM Home Directory is where you installed IBM Tivoli Monitoring.Usually it is /opt/IBM/ITM for AIX and Linux.

4. Select the language of the installer and click OK.

5. Click Next on the Introduction panel.

6. Click Add/Update and click Next.

7. Select the folder in which the National Language Support package(NLSPackage) files are located.

Note: Usually, the NLSPackage files are located in the nlspackage folder wherethe installer executable is located.

8. Select the language support for the agent of your choice and click Next.

Note: Hold down the Ctrl key for multiple selections.

9. Select the languages that you want to install and click Next.

10. Examine the installation summary page and click Next to begin installation.11. Click Finish after installation completes to exit the installer.

12. Restart the Tivoli Enterprise Portal (if on the Tivoli Enterprise Portal Server) orrestart the Tivoli Enterprise Portal Server (if on the Tivoli Enterprise PortalServer component).

Agent-specific installation and configuration

In addition to the installation and configuration information in the IBM Tivoli Monitoring Installation and Setup Guide, use the information in this section to installand configure the Microsoft Cluster Server Agent.

The agent must be installed and configured in the same way on all nodes in thecluster. This ensures that the node controls the active agent and the agents clusterresource. When installing for the first time, go through the installation proceduresfound in the IBM Tivoli Monitoring Installation and Setup Guide before creating thecluster resources. When applying fix packs to multiple nodes, bring the resourcegroup offline before applying the fix packs, and then bring the resource group backonline.

The starting and stopping of the agent is controlled by the cluster server. UsingIBM® Tivoli Monitoring v6.2.1 utilities to manage the agent (start, stop, restart,remove, configure) conflicts with the cluster server control of the agent. Whenusing the IBM Tivoli Monitoring v6.2.1 utilities to manage the agent take thecluster agent resource offline. This ensures that the cluster server does not

automatically restart the agent when the IBM Tivoli Monitoring v6.2.1 utility needsthe agent to be offline. See the Troubleshooting chapter of this document forrelated behaviors.

Use the Microsoft® Cluster Administrator to create a resource group and resourceto control the agent.

When creating the agent resource group, specify the name and description youwant to use to identify the agent. Use the same preferred nodes sequence as set forthe cluster group controlling the cluster resources.



19/316

If agent history is stored at the Tivoli Enterprise Monitoring Agent, a shared diskresource must be created to store agent history. This disk resource must be addedto the agent’s resource group so that the node owning the agent resource groupcan access the disk.

For Windows 2003 based systems create a generic service cluster resource in thecluster agent resource group by completing the following steps:

1. Right -click the agent resource group created for the agent, select New, andthen select Resource.

2. Select Generic Service Resource Type and specify a name for the agentresource.

3. Take the defaults of all possible owners, which should be all nodes in thecluster.

4. If history is stored at the agent you must create a shared disk resource that isset as a resource dependency.

5. Specify the service name as kq5cma (the service for: Monitoring Agent forMicrosoft Cluster Server Agent).

6. Take the defaults for all the other settings.

For Windows 2008 based systems create a generic service cluster resource in thecluster agent resource group by completing the following steps:

1. Click Configure and select Configure a Service or Application.

2. Click Next on the High Availability Wizard page.

3. Select Generic Service and Click Next.

4. Select Agent Service and Click Next.

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

6. Select Storage.

7. Select Replicate Registry Settings.

8. Select Confirmation.

9. Select Configure High Availability.

10. Select Summary to get the details.

Each node in the cluster has a single instance of the agent installed. Each instancemust be configured in the same way. Use Manage Tivoli Monitoring Services toconfigure and set startup agent parameters.

In addition to the standard agent configuration, two parameters that are unique tothe agent are specified :

v Microsoft Cluster Name (Environment variable CTIRA_HOSTNAME)

v Shared Agent History Directory (Environment variable CTIRA_HIST_DIR)

The Microsoft Cluster Name configuration parameter is used to create theWindows system name that appears in the Tivoli Enterprise Portal. The MicrosoftCluster Name configuration is used to set CTIRA_HOSTNAME, which is thehostname part of the managed system name. The Managed System Statusworkspace of the enterprise view shows the status of each managed system. Notethat this name is case sensitive and must be entered the same way on each node'sagent configuration. Also, use only ASCII characters.

The Shared Agent History Directory field is required if the history configurationspecifies that the collection location is at the Tivoli Enterprise Monitoring Agent.

Chapter 2. Agent-specific installation and configuration information for the monitoring agent 9


20/316

History is then stored on the agent on the shared disk. The Shared Agent HistoryDirectory configuration parameter, CTIRA_HIST_DIR, specifies a directory on ashared disk controlled by the agent resource group. On the shared disk, create adirectory to store the history because the agent does not create the directory.

For cluster systems that do not support shared disks, history must be stored on theTivoli 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 notoverrun the Tivoli Enterprise Monitoring Server. For more information, see theDisk capacity planning for historical data section in this document.

The agent defaults to a startup type of manual and Log on As system account. Theaccount that the agent runs under needs to be changed to have authority to useremote WMI queries. This will help access system attributes like CPU Utilizationacross all nodes in the cluster.

The cluster administrator ID, with a format domain_name\administrator_id, is anexample of a user ID that could be used.

Configuring the monitoring agent after installationIn addition to the installation and configuration information in the IBM Tivoli

Monitoring Installation and Setup Guide, use the information in this section to installand configure the Microsoft Cluster Server Agent.

Configuration valuesFor both local and remote configuration, provide the configuration values for theagent to operate. When configuring an agent, a panel is displayed so you can entereach value. When there is a default value, this value is pre-entered into the field. If a field represents a password, two entry fields are displayed. You must enter thesame value in each field. The values you type are not displayed to help maintainthe security of these values.

The configuration for this agent is organized into the following groups:

Microsoft Cluster Server Agent Configuration (MSCS)Null Description for section.

The configuration elements defined in this group are always present in theagent's configuration.

This group defines information that applies to the entire agent.

Shared Agent History DirectoryA shared directory for the cluster that is not a quorum drive wherethe agents can locate cluster historical information.

You must not perform any I/O operations while the clusteroperation runs on the quorum disk. If you run a different I/Ooperation at the same time, then the operation can interfere withthe cluster operation and the quorum resource can fail. The entirecluster fails if the quorum resource fails. Therefore, you must createa separate physical disk to store historical information.

The type is string.

This value is optional.

defaultValue(null)



21/316

Microsoft Cluster NameA unique name assigned to the cluster that will be displayed in theTivoli Enterprise Portal.

The type is string.

This value is required.

defaultValue(null)

Remote installation and configurationWhen installing the agent remotely, you must provide the configuration values forthe agent to operate. See “Configuration values” on page 10.

See the tacmd describeSystemType section in the IBM Tivoli Monitoring CommandReference for information on displaying the configuration options that are availableto use with the configureSystem or addSystem commands.

You can install the monitoring agent remotely from the Tivoli Enterprise Portal orfrom the command line. To install from the portal, see the IBM Tivoli MonitoringInstallation and Setup Guide.

If using the command line, the following command is an example of remoteconfiguration for Windows operating systems:

tacmd addSystem -t Q5 -n Primary:sample.node.name:NT-p MSCS.CTIRA_HIST_DIR=value

MSCS.CTIRA_HOSTNAME=value

Chapter 2. Agent-specific installation and configuration information for the monitoring agent 11


22/316



23/316

Chapter 3. Workspaces reference

This chapter contains an overview of workspaces, references for detailedinformation about workspaces, and descriptions of the predefined workspaces

included in this monitoring agent.

About workspaces

A workspace is the working area of the Tivoli Enterprise Portal applicationwindow. At the left of the workspace, is a Navigator that you use to select theworkspace you want to see. As part of the application window, the right side of the status bar shows the Tivoli Enterprise Portal server name and port number towhich 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 Navigatoritem. Each workspace has at least one view. Some views have links to otherworkspaces.

The workspaces in the Navigator are shown in a Physical view that shows yourenterprise as a physical mapping or a dynamically populated logical view that isagent-specific. You can also create a Logical view. The Physical view is the defaultview.

This monitoring agent provides predefined workspaces. You cannot modify ordelete the predefined workspaces, but you can create new workspaces by editingthem and saving the changes with a different name.

A table view within a workspace corresponds to a group of attributes; the columnsin the table view show some or all of the attributes available in the attribute group.

More information about workspaces

For more information about creating, customizing, and working with workspaces,see the Tivoli Enterprise Portal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a descriptionof each workspace, see the Predefined workspaces section in this chapter and theinformation in that section for each individual workspace.

Some attribute groups for this monitoring agent might not be represented in the

predefined workspaces or views for this agent. For a full list of the attributegroups, see the Attributes reference section.



24/316

Cross-Linked Workspaces

This section contains cross-links within the Microsoft Cluster Server agent andfrom the Microsoft Cluster Server agent to the Microsoft Hyper-V Server agent.

Table 1. Cross-linked workspaces within the Microsoft Cluster Server agent

Link name

Source

navigatoritem

Source

workspacename

Source viewname

Target

workspacename Filter

Local ClusterCapacityDashboard

MS ClusterServer

EnterpriseLevel ClusterDashboard

EnterpriseLevel ClusterCapacity

ClusterDashboard

Cluster Name

Availability ClusterDashboard

ClusterDashboard

ClusterCapacityDetails

Availability N/A

Nodes ClusterDashboard

ClusterDashboard

ClusterCapacityDetails

Nodes N/A

Configuration Cluster

Dashboard

Cluster

Dashboard

Cluster

CapacityDetails

Configuration N/A

Resources ResourceGroups

ResourceGroupAssociations

ResourceGroups toResources

Resources ResourceName

Resources Nodes Nodes Nodes Resources N/A

ResourceGroups

Nodes Nodes Nodes ResourceGroups

N/A

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

Link name

Sourcenavigatoritem

Sourceworkspacename

Source viewname

Targetworkspacename Filter

MSCS toHyper-Vagent

Nodes Nodes Nodes VirtualMachine

Node Name

Table 3. Cross-linked Workspaces to Windows OS agent

Link name

Sourcenavigatoritem

Sourceworkspacename

Source viewname

Targetworkspacename Filter

MSCS toWindows OS

agent

Nodes Nodes Nodes VirtualMachine

Node Name

Predefined workspaces

The Microsoft Cluster Server Agent provides the following predefined workspaces,which are organized by Navigator item.

v Microsoft Cluster Server Agent Navigator item

– Microsoft Cluster Server Agent workspace

– Enterprise Level Cluster Dashboard workspace



25/316

v Availability Navigator item

– Availability workspace

– Performance Object Status workspace

– Thread Pool Status workspace

v Cluster Dashboard Navigator item

– Cluster Dashboard workspace

– Cluster Shared Volume workspace

v Configuration Navigator item

– Cluster Configuration Summary workspace

– Configuration workspace

– Query Object Status workspace

– Quorum Configuration workspace

v Event Log Navigator item

– Event Log workspace

v Network Interfaces Navigator item

– Network Interfaces workspace

– Network Performance workspace

v Networks Navigator item

– Network Reconnections workspace

– Networks workspace

– Networks Messages workspace

v Nodes Navigator item

– Node CPU workspace

– Node Disks workspace

– Node Memory workspace

– Nodes workspace

v Resource Groups Navigator item– Resource Group Associations workspace

– Resource Group to Possible Node workspace

– Resource Groups workspace

v Resources Navigator item

– Resource Summary workspace

– Resources workspace

v Structural and Degradation Risk Navigator item

– Structural and Degradation Risk workspace

– Structural Risk workspace

Agent Navigator items

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

Microsoft Cluster Server Agent Navigator item

Microsoft Cluster Server Agent workspaceMS Cluster Server View. This workspace displays the overall status of thecluster.

Chapter 3. Workspaces reference 15


26/316

This workspace contains the following views:

Application AvailabilityDisplays the current availability of all resource groups as anaverage.

Average CPU Across All NodesDisplays the average CPU utilization on all nodes in the cluster.

Processor Load (8hr)Displays an 8-hour history of the processor load (minimum,maximum, average and standard deviation) across all nodes in thecluster.

Message LogDisplays the cluster message log.

Event Log SummaryDisplays the Error and Warning events from the Microsoft ClusterServer event log.

Enterprise Level Cluster Dashboard workspaceThe Enterprise Level Cluster Dashboard workspace displays details of thephysical resources that are used by the cluster server system.


Enterprise Level Cluster CapacityDisplays the details of the physical resource that is used by thecluster server system.

Top 5 Cluster Systems Having High Processor UsageDisplays the percentage of high processor usage of five clustersystems.

Top 5 Cluster Systems Having High Memory UsageDisplays 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 clustersystems.

Top 5 Clusters Having High Shared Storage UsageDisplays the percentage of high shared storage usage of five clustersystems.

Availability Navigator item

Availability workspaceThe Availability workspace displays the overall health of the application.


AvailabilityDisplays the state of each component in the application. Eachprocess is displayed using a descriptive name, the name of therunning process, and the state of the process (UP, DOWN, orPROCESS_DATA_NOT_AVAILABLE). When the state of thecomponent is DOWN (for a process, or service) it is highlightedwith a red background.

ProcessorDisplays the amount of CPU used by each process that is a



27/316

component of the application. This displays the 2 maincomponents of CPU usage, privileged time which is time spent inthe kernel on behalf of the process and user mode time, which isthe time spent running the process code.

ThreadsDisplays 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 processthat 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 workspaceThis workspace displays the overall health of the application.

This workspace contains the following view:

Performance Object StatusDisplays the status of data collection from the application. NO

ERROR indicates that the agent is collecting application datacorrectly. If any other views of the agent do not show any data,then this view helps to identify the cause of the data collectionfailure.

Thread Pool Status workspaceThis workspace displays information about the Thread Pool Statusattribute group.


Thread Pool StatusProvides information about the Thread Pool Status attribute groupand the status of the internal thread pool that is used to collect

data in an asynchronous manner.

Cluster Dashboard Navigator item

Cluster Dashboard workspaceThe Cluster Dashboard workspace provides details of the cluster and itscapacity.


Cluster Capacity DetailsDisplays details of the capacity of the cluster in the enterprise.

Cluster Shared StorageDisplays information about the Clustered Shared Volume available

in a cluster.

System Processor UsageDisplays processor usage of a particular node in a cluster.

System Memory UsageDisplays memory usage of a particular node in a cluster.

Quorum UsageDisplays quorum usage of a particular node in a cluster.

Shared Storage UsageDisplays shared storage usage of a particular node in a cluster.



28/316

Cluster Shared Volume workspaceThe Cluster Shared Volume workspace provides information about theCluster Shared Volume disk that is configured in the cluster environment.


Cluster Shared VolumeDisplays information about the Cluster Shared Volume disk that is

configured in the cluster environment.

Cluster Shared Volume IODisplays information about the I/O activity on all the clustershared volume disks of the cluster.

IO Read BytesDisplays information about the number of read operations that aresent from the Cluster Shared Volume.

IO Write BytesDisplays information about the number of write operations that aresent to the Cluster Shared Volume.

Configuration Navigator itemCluster Configuration Summary workspace

Displays a summary of the current cluster configuration. The viewstypically show the names of key resources, their current state, and the timethey were last checked.


Cluster ConfigurationThis view displays the current cluster object, including the name of the cluster.

Networks SummaryThis view displays a summary of the network configuration. Moredetails can be found in the Networks and Network Interfaceworkspaces. This view is linked to the detailed Networkworkspace.

Resource Groups SummaryThis view displays a summary of the resource group configuration.More details can be found in the Resource Group and Resourcesworkspaces. This view is linked to the detailed Resource Groupsworkspace.

Nodes SummaryThis view displays a summary of the node configuration. Thisview is linked to the detailed Nodes workspace.

Configuration workspaceProvides a visual summary of the cluster state. It shows the stateinformation for the five key cluster attributes in a bar chart form. Up isrepresented as a full bar, down will have no bar at all, and intermediatestates(if any) will be in between.


State of NodesThis view displays the state of the nodes. It is linked to thedetailed Node workspace.



29/316

State of NetworksThis view displays the state of the networks. It is linked to thedetailed Networks workspace.

State of Network InterfacesThis view displays the state of the network interfaces. It is linkedto the detailed Network Interface workspace.

State of Resource GroupsThis view displays the state of the resource groups. It is linked tothe detailed Resource Groups workspace.

State of ResourcesThis view displays the state of the resources. It is linked to thedetailed Resources workspace.

Query Object Status workspaceThe Query Status workspace displays the current status of the datacollection queries.


State of Data Collection Queries

This view displays the current status of the data collection queries.The query name, the object it queries, the object status, and thereturn code from the query are shown here.

Quorum Configuration workspaceThe Quorum Configuration Workspace displays the current QuorumConfiguration details.


Quorum Configuration for Microsoft Windows 2003This view displays the Quorum Configuration details. TheMaintanace File of Quorum and Quorum Log File Size forMicrosoft Windows 2003.

Quorum Configuration for Microsoft Windows 2008This view displays the Quorum Configuration details. Maximumand Minimum time (in sec), necessary to decide the Quorumowner node, Quorum Type and Quorum Path for MicrosoftWindows 2008.

Event Log Navigator item

Event Log workspaceThe Event Log workspace shows the details for the recent events logged bythe application to the Windows Event Log. By default, the agent onlydisplays 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 LogShows the recent Event Log entries for Microsoft Cluster Server.

Network Interfaces Navigator item

Network Interfaces workspaceProvides availability and detail information for the cluster networkinterfaces.



30/316


Network Interfaces State RollupThis view displays a rollup of the network interface stateinformation.

Network InterfacesThis view displays the network interface configuration details.

Network Interface State (8hr)This view graphs the state of the network interfaces over the lasteight hours. This view is populated with data collected fromhistorical data collection. Start the historical data collection forthese attribute groups to see data for the respected view.

Network Performance workspaceThis workspace provides network performance data collected from eachnode in the cluster.


Network InterfacesThis view displays the details of each network interface in thecluster.

Packets per Second RollupThis view displays the rollup of the network interface packets persecond.

Bytes Received per Second Rollup (8hr)This view graphs the rollup of the bytes received per second overeight hours. Data is available after historical data collection for theattribute group. This view is populated with data collected fromhistorical data collection. Start the historical data collection forthese attribute groups to see data for the respected view

Bytes Sent per Second Rollup (8hr)

This view graphs the rollup of the bytes sent per second over eighthours. Data is available after historical data collection for theattribute group. This view is populated with data collected fromhistorical data collection. Start the historical data collection forthese attribute groups to see data for the respected view.

Networks Navigator item

Network Reconnections workspaceThe Network Reconnections workspace provides information aboutreconects 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 nodesof the cluster.

Message Queue LengthDisplays the queue length of all types of messages.

Networks workspaceThis workspace provides detailed information about the cluster networks.It contains tables with the configuration details and an availability graph of the network.



31/316


Network State RollupThis view displays a rollup of the network state information.

NetworksThis view displays the network configuration details.

Network State (8hr)This view graphs the state of the networks over the last eighthours. This view is populated with data collected from historicaldata collection. Start the historical data collection for these attributegroups to see data for the respected view.

Networks Messages workspaceThe Networks Messages workspace provides information about the clusternetwork messages that are sent and received on the network per clusternode.


Network Messages Sent/ReceivedDisplays information about the cluster network messages that aresent and received on the network per cluster node.

Bytes Sent/ReceivedDisplays information about the cluster network bytes that are sentand received on the network per cluster node.

Messages Sent/ReceivedDisplays information about the cluster network messages that aresent and received on the network per cluster node.

Nodes Navigator item

Node CPU workspaceThis workspace contains processor information collected from each node inthe cluster.


CPU per NodeThis view displays the details of each processor in the cluster.

CPU per Node RollupThis view displays the rollup of the percent processor time.

CPU Rollup (8hr)This view graphs the rollup of the percent processor time overeight hours. This view is populated with data collected fromhistorical data collection. Start the historical data collection for

these attribute groups to see data for the respected view.CPU Interrupts Persec Rollup (8hr)

This view graphs the interrupts per second over eight hours. Thisview is populated with data collected from historical datacollection. Start the historical data collection for these attributegroups to see data for the respected view.

Node Disks workspaceThis workspace contains disk information collected from each node in thecluster.




32/316

Logical Disks on NodesThis view displays the disk details of each node in the cluster.

Free Space (MB) on the Logical Disks RollupThis view displays the rollup of the free space on the disks (inmegabytes).

Free Space in MB on the Logical Disks (8hr)

This view graphs the rollup of free space on the disks (inmegabytes) over eight hours. This view is populated with datacollected from historical data collection. Start the historical datacollection for these attribute groups to see data for the respectedview.

Percent Free Space on the Logical Disks (8hr)This view graphs the percent free space on the disks over eighthours. This view is populated with data collected from historicaldata collection. Start the historical data collection for these attributegroups to see data for the respected view.

Node Memory workspaceThis workspace contains memory information collected from each node inthe cluster.


MemoryThis view displays the memory details of each node in the cluster.

Memory MB RollupThis 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 memoryover eight hours. This view is populated with data collected from

historical data collection. Start the historical data collection forthese attribute groups to see data for the respected view.

The Percent Committed Bytes in Use (8hr)This view graphs the percent committed bytes used over eighthours. This view is populated with data collected from historicaldata collection. Start the historical data collection for these attributegroups to see data for the respected view.

Nodes workspaceThis workspace provides detailed information for the cluster nodes. It alsoincludes a node availability graph.


Nodes State RollupThis view displays a rollup of the node state information.

Nodes This view displays the node configuration details.

Nodes State (8hr)This view graphs the state of the nodes. This view is populatedwith data collected from historical data collection. Start thehistorical data collection for these attribute groups to see data forthe respected view.



33/316

Resource Groups Navigator item

Resource Group Associations workspaceThis workspace shows the resource group associations between resourcesand nodes


Resource Groups to ResourcesThis view displays the association of resource groups to resources.

Resource Group to Nodes TableThis view displays the association of resource groups to nodes.

Resource Group Node ChangesThis view displays a real time graph of the Resource Group NodeChange attribute.

Resource Group to Possible Node workspaceThis workspace shows the resource group to its preferred node, andresource to possible node views.


Resource to Possible OwnerThis view displays the association of resource to possible nodes.

Resource Group to Preferred NodesThis view displays the association of resource group to preferrednodes.

Resource Groups workspaceThe resource group workspace provides availability and detail informationfor the cluster resource groups.


State of Resource Groups Rollup

This view displays a rollup of the resource group state information.Resource Groups

This view displays the resource group configuration details.

Resource Groups State (8hr)This view graphs the state of the resource groups over the lasteight hours. This view is populated with data collected fromhistorical data collection. Start the historical data collection forthese attribute groups to see data for the respected view.

Resources Navigator item

Resource Summary workspace

The Resources Summary workspace provides information about the overallhealth of the various types of resources available in the clusterenvironment.


Dependent Resources SummaryDisplays information about resources and its dependent resources.

Resources SummaryDisplays information about the cluster resources that are grouped

by the resource type.



34/316

Total Resources OnlineDisplays the number of resources that are online.

Resources workspaceThe resource workspace provides availability and detail information for thecluster resources.


Resource State RollupThis view displays a rollup of the resource state information.

ResourcesThis view displays the resource configuration details.

Resources States (8hr)This view graphs the state of the resource over the last eight hours.This view is populated with data collected from historical datacollection. Start the historical data collection for these attributegroups to see data for the respected view.

Structural and Degradation Risk Navigator item

Structural and Degradation Risk workspaceThe Structural and Degradation Risk workspace and the Degradationworkspace is an estimate of the potential of degraded performance if onenode fails. Degradation risk is a first-order approximation of theproportion of the current workload that could not be carried in the eventof a failure (or the degree of over commitment). Commitment is the currentworkload of the cluster. For example, in a 2-node active/passiveconfiguration with a 3GHz node A and a 1.5 GHz node B, where A isactive, the capacity of node A is 3000 (3GHz = 3000MHz), and if A iscurrently using 20% CPU, its utilization is (3000*(20%)) = 600. The capacityof 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 twonodes we introduce the terms Unitary and Uniform Commitment. Unitarycommitment is where the entire load (as in the previous example) of thefailed node is placed on the next node. This represents a resource groupthat must be shifted as a whole, and no balancing of the load is possible.Uniform commitment is where the load may be balanced evenly amongstthe remaining nodes. The actual risk of degraded performance liessomewhere between these two lines. For both forms of commitment, valuesless than or equal to 100%, represent a level of commitment that the clustershould be able to carry without a loss of performance. In practice, valuesnear 100% also suffer some degradation. Situations may be created, basedon cluster configuration and customer experience, to fire when either form

of commitment exceeds a threshold (for example 100%).


Degradation Risk TableThis view displays the performance details of the cluster.

Utilization GraphThis view graphs the processor utilization and capacity of thecluster over eight hours.



35/316

Commitment GraphThis view graphs the commitment of the cluster processor overeight hours.

Structural Risk workspaceThe Structural Risk workspace tracks the availability of resources, andcalculates the impact of a node failure. Since resources form resource

groups and the resource groups represent applications, a single criticalresource can lead to a failed application. As currently implemented, onlythe most at risk resource (in the event of a tie, the first resource) isdisplayed. The definition of the structural risk factor is n/m, where n is thenumber of active, configured nodes, and m is the number of configurednodes in the cluster. The cluster-wide structural risk factor is the minimumover all resources. A 5 node cluster with 2 failed nodes and free-rangefailover (no failover limitations) for all resources would have a healthfactor of 3/5. Resources are matched to their possible nodes and a relativehealth for each resource is calculated. If a resource is configured on 3nodes and all three nodes are up 3/3 = 100% health, if only two of three2/3 = 66% health. The Health Less A Node is the hypothetical loss of onenode calculation (n-1)/m, where n is the number of active nodes

configured to support the resource, and m is the number of nodesconfigured to support the resource. The Fewest Nodes Resource shows theresource configured on the fewest nodes and the impact should it lose anode. Situations may be created based on health thresholds or on thenumber of nodes (such as when a resource is on its last node: AvailableNodes equals one).


Structural Risk TableThis view displays structural risk of the cluster.

Structural Risk GraphThis view graphs the structural risk relative health attributes of the

cluster over eight hours.



36/316



37/316

Chapter 4. Attributes reference

This chapter contains an overview of attributes, references for detailed informationabout attributes, and descriptions of the attributes for each attribute group

included in this monitoring agent.

About attributes

Attributes are the application properties that are being measured and reported bythe Microsoft Cluster Server Agent.

Attributes are organized into groups according to their purpose. The attributes in agroup can be used in the following two ways:

v Chart or table views

Attributes are displayed in chart and table views. The chart and table views usequeries to specify which attribute values to request from a monitoring agent.

You use the Query editor to create a new query, modify an existing query, orapply filters and set styles to define the content and appearance of a view basedon an existing query.

v Situations

You use attributes to create situations that monitor the state of your operatingsystem, database, or application. A situation describes a condition you want totest. When you start a situation, the Tivoli Enterprise Portal compares the valuesyou have assigned to the situation attributes with the values collected by theMicrosoft Cluster Server Agent and registers an event if the condition is met. Youare alerted to events by indicator icons that are displayed in the Navigator.

More information about attributes

For more information about using attributes and attribute groups, see the TivoliEnterprise Portal User's Guide.

For a list of the attributes groups, a list of the attributes in each attribute group,and descriptions of the attributes for this monitoring agent, see the Attributegroups and attributes section in this chapter.

Attribute groups and attributes for the Microsoft Cluster Server Agent

This monitoring agent contains the following attribute groups. The table namedepends on the maximum table name limits of the target database being used forthe Tivoli Data Warehouse. If the maximum name is 30 characters, then any

warehouse table name longer than 30 characters is shortened to 30 characters.

v Attribute group name: Availability

– Table name: KQ5AVAIL

– Warehouse table name: KQ5_AVAILABILITY or KQ5AVAIL

v Attribute group name: Cluster Domain

– Table name: KQ5WIN32CO

– Warehouse table name: KQ5_CLUSTER_DOMAIN or KQ5WIN32CO

v Attribute group name: Cluster Shared Volume

– Table name: KQ5CLUSCSV



38/316

– Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME orKQ5CLUSCSV

v Attribute group name: Cluster Shared Volume IO

– Table name: KQ5CLUCSVP

– Warehouse table name: KQ5_CLUSTER_SHARED_VOLUME_IO orKQ5CLUCSVP

v Attribute group name: Cluster Summary– Table name: KQ5CLUSUM

– Warehouse table name: KQ5_CLUSTER_SUMMARY or KQ5CLUSUM

v Attribute group name: Configuration

– Table name: KQ5B05PHYS

– Warehouse table name: KQ5_CONFIGURATION or KQ5B05PHYS

v Attribute group name: CPU Interrupts Rollup

– Table name: KQ5D55RLL

– Warehouse table name: KQ5_CPU_INTERRUPTS_ROLLUP or KQ5D55RLL

v Attribute group name: CPU per Node

– Table name: KQ5D40CPU– Warehouse table name: KQ5_CPU_PER_NODE or KQ5D40CPU

v Attribute group name: CPU per Node Rollup


– Warehouse table name: KQ5_CPU_PER_NODE_ROLLUP or KQ5D50RLL

v Attribute group name: Degradation Risk

– Table name: KQ5G20RISK

– Warehouse table name: KQ5_DEGRADATION_RISK or KQ5G20RISK

v Attribute group name: Disk

– Table name: KQ5D80HDD

– Warehouse table name: KQ5_DISK or KQ5D80HDDv Attribute group name: Disk MB Rollup


– Warehouse table name: KQ5_DISK_MB_ROLLUP or KQ5D85RLL

v Attribute group name: Disk PCT Rollup


– Warehouse table name: KQ5_DISK_PCT_ROLLUP or KQ5D90RLL

v Attribute group name: Enterprise Cluster Summary

– Table name: KQ5VCLUSUM

– Warehouse table name: KQ5_ENTERPRISE_CLUSTER_SUMMARY orKQ5VCLUSUM

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 orKQ5CLUSTE1

v Attribute group name: Memory

– Table name: KQ5D60MEM



39/316

– Warehouse table name: KQ5_MEMORY or KQ5D60MEM

v Attribute group name: Memory MB Rollup


– Warehouse table name: KQ5_MEMORY_MB_ROLLUP or KQ5D70RLL

v Attribute group name: Memory PCT Rollup


– Warehouse table name: KQ5_MEMORY_PCT_ROLLUP or KQ5D75RLL

v Attribute group name: MRR Messages

– Table name: KQ5CLUSTE3

– Warehouse table name: KQ5_MRR_MESSAGES or KQ5CLUSTE3

v Attribute group name: Network Interfaces

– Table name: KQ5F20INT

– Warehouse table name: KQ5_NETWORK_INTERFACES or KQ5F20INT

v Attribute group name: Network Interfaces State Rollup

– Table name: KQ5F30RLL

– Warehouse table name: KQ5_NETWORK_INTERFACES_STATE_ROLLUP or

KQ5F30RLLv Attribute group name: Network Performance

– Table name: KQ5F40NET

– Warehouse table name: KQ5_NETWORK_PERFORMANCE or KQ5F40NET

v Attribute group name: Network Performance Packets Rollup


– Warehouse table name:KQ5_NETWORK_PERFORMANCE_PACKETS_ROLLUP or KQ5F70RLL

v Attribute group name: Network Performance Received Rollup


– Warehouse table name:KQ5_NETWORK_PERFORMANCE_RECEIVED_ROLLUP or KQ5F50RLL

v Attribute group name: Network Performance Sent Rollup


– Warehouse table name: KQ5_NETWORK_PERFORMANCE_SENT_ROLLUPor KQ5F60RLL

v Attribute group name: Network Reconnections

– Table name: KQ5NWRECON

– Warehouse table name: KQ5_NETWORK_RECONNECTIONS orKQ5NWRECON

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

Chapter 4. Attributes reference 29


40/316

– Table name: KQ5B20LOGI

– Warehouse table name: KQ5_NODE_TO_ACTIVE_GROUP or KQ5B20LOGI

v Attribute group name: Nodes

– Table name: KQ5D20NODE

– Warehouse table name: KQ5_NODES or KQ5D20NODE

v Attribute group name: Nodes State Rollup


– Warehouse table name: KQ5_NODES_STATE_ROLLUP or KQ5D30RLL

v Attribute group name: Performance Object Status

– Table name: KQ5POBJST

– Warehouse table name: KQ5_PERFORMANCE_OBJECT_STATUS orKQ5POBJST

v Attribute group name: Quorum Configuration

– Table name: KQ5MSCLUST

– Warehouse table name: KQ5_QUORUM_CONFIGURATION orKQ5MSCLUST

v

Attribute group name: Resource Control Manager– Table name: KQ5CLUSRSC

– Warehouse table name: KQ5_RESOURCE_CONTROL_MANAGER orKQ5CLUSRSC

v Attribute group name: Resource Group Moves

– Table name: KQ5B30RLL

– Warehouse table name: KQ5_RESOURCE_GROUP_MOVES or KQ5B30RLL

v Attribute group name: Resource Group To Preferred Node


– Warehouse table name: KQ5_RESOURCE_GROUP_TO_PREFERRED_NODEor KQ5B30LOGI

v Attribute group name: Resource Group To Resource


– Warehouse table name: KQ5_RESOURCE_GROUP_TO_RESOURCE orKQ5B25LOGI

v Attribute group name: Resource Groups

– Table name: KQ5B10RG

– Warehouse table name: KQ5_RESOURCE_GROUPS or KQ5B10RG

v Attribute group name: Resource Groups State Rollup

– Table name: KQ5B15RLL

– Warehouse table name: KQ5_RESOURCE_GROUPS_STATE_ROLLUP or

KQ5B15RLLv Attribute group name: Resource To Dependent Resource

– Table name: KQ5B25RTDR

– Warehouse table name: KQ5_RESOURCE_TO_DEPENDENT_RESOURCE orKQ5B25RTDR

v Attribute group name: Resource To Possible Owner


– Warehouse table name: KQ5_RESOURCE_TO_POSSIBLE_OWNER orKQ5B35LOGI



41/316

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 orKQ5CSVSUMM

v Attribute group name: Structural Risk

– Table name: KQ5G30RLL

– Warehouse table name: KQ5_STRUCTURAL_RISK or KQ5G30RLL

v Attribute group name: Thread Pool Status– Table name: KQ5THPLST

– Warehouse table name: KQ5_THREAD_POOL_STATUS or KQ5THPLST

The remaining sections of this chapter contain descriptions of these attributegroups, which are listed alphabetically. The following information is provided foreach attribute group:

Historical groupWhether the attribute group is a historical type that you can roll off to adata warehouse

Attribute descriptions

Description, type, and Warehouse name for each attribute in the attributegroup

Some attributes are designated as key attributes. A key attribute is anattribute that is used in warehouse aggregation to identify rows of datathat represent the same object.

Availability attribute group

The Availability attribute group contains the availability data for all processes andservices that make up this application.

Historical groupThis attribute group is part of the default historical group, and is eligible for usewith Tivoli Data Warehouse.

Attribute descriptionsThe following list contains information about each attribute in the Availabilityattribute group:

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.



42/316

Type String

Warehouse nameNODE

Timestamp attribute

Description

The local time at the agent when the data was collected.Type String

Warehouse nameTIMESTAMP

Application Component attribute - This attribute is a key attribute.

DescriptionThe descriptive name of a part of the application.

Type String

Warehouse nameAPPLICATION_COMPONENT or COMPONENT

Name attribute

DescriptionThe name of the process, service, or functionality test. This namematches the executable name of the process, the service short nameor the name of the process used to test the application.

Type String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v N/A (N/A)

Any other values will display the actual value returned by theagent in the Tivoli Enterprise Portal.

Warehouse nameNAME

Status attribute

DescriptionThe status of the application component.

v For processes 'UP', 'DOWN', 'WARNING', or'PROCESS_DATA_NOT_AVAILABLE':'PROCESS_DATA_NOT_AVAILABLE' is displayed for a processwhen the matching process is running but the resource useinformation cannot be collected for that process.

v

For services 'UP', 'DOWN', or 'UNKNOWN': 'UNKNOWN' isdisplayed when the service is not installed.

v For functionality tests: 'PASSED' or 'FAILED' is displayed.

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v DOWN (0)

v UP (1)

v WARNING (2)



43/316

v UNKNOWN (3)

v PASSED (4)

v FAILED (5)

v PROCESS_DATA_NOT_AVAILABLE (6)


Warehouse nameSTATUS

Full Name attribute

DescriptionThe full name of the process including the path.

Type String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v N/A (N/A)


Warehouse nameFULL_NAME or FULLNAME

Type attribute

DescriptionThe type of the application component. Components are processes,services, or functionality tests.


v

PROCESS (0)v SERVICE (1)

v FUNCTIONALITY_TEST (2)


Warehouse nameTYPE

Virtual Size attribute

DescriptionThe virtual size (in MB) of the process.

Type Integer (gauge)

Warehouse nameVIRTUAL_SIZE or VIRTSIZE

Page Faults per Sec attribute

DescriptionThe rate of page faults for the process measured in faults persecond. This attribute only contains valid data for processes.




44/316

Warehouse namePAGE_FAULTS_PER_SEC or PAGEFAULTS

Working Set Size attribute

DescriptionThe working set size of the process in MB. This attribute onlycontains valid data for processes.


Warehouse nameWORKING_SET_SIZE or WORKSET

Thread Count attribute

DescriptionThe number of threads currently allocated by this process. Thisattribute only contains valid data for processes.


Warehouse nameTHREAD_COUNT or THREADS

PID attribute

DescriptionThe process ID associated with the process. This attribute onlycontains valid data for processes.


Warehouse namePID

Percent Privileged Time attribute

Description

The percentage of the available CPU time that is being used by thisprocess for privileged operation.


Warehouse namePERCENT_PRIVILEGED_TIME or PERCPRIV

Percent User Mode Time attribute

DescriptionThe percentage of the available CPU time that is being used by thisprocess for user mode operation.


Warehouse namePERCENT_USER_MODE_TIME or PERCUSER

Percent Processor Time attribute

DescriptionThe percentage of the elapsed time that this process used theprocessor to execute instructions.


Warehouse namePERCENT_PROCESSOR_TIME or PERCPROC



45/316

Command Line attribute

DescriptionThe program name and any arguments specified on the commandline when the process was started. This has the value N/A if this isa Service, or Functionality test.

Type String with enumerated values. The strings are displayed in the

Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v N/A (N/A)


Warehouse nameCOMMAND_LINE or CMDLINE

Functionality Test Status attribute

DescriptionThe 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 functionalitytest.


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)


Warehouse nameFUNCTIONALITY_TEST_STATUS or FUNCSTATUS

Functionality Test Message attribute

DescriptionThe text message that corresponds to the Functionality Test Status.This is only valid for functionality tests.

Type String with enumerated values. The strings are displayed in the



46/316

Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v N/A (N/A)


Warehouse nameFUNCTIONALITY_TEST_MESSAGE or FUNCMSG

Cluster Domain attribute group

Cluster Domain contains details of the windows domain to which the cluster belongs.

Historical groupThis attribute group is not part of the default historical group, and is eligible foruse with Tivoli Data Warehouse.

Attribute descriptionsThe following list contains information about each attribute in the Cluster Domainattribute group:

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.

Type String

Warehouse nameNODE

Timestamp attribute

DescriptionThe local time at the agent when the data was collected.

Type String

Warehouse nameTIMESTAMP

Domain attribute

DescriptionDomain contains name of the windows domain to which thecluster belongs.

Type String

War

cluster622 user

Documents