IBM Tivoli Composite Application Manager for Microsoft
Applications: Microsoft Cluster Server Agent
vNext
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
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.
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
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. . . 353Related publications . . . 354
Other sources of documentation . . . 354
Notices . . . 357
Trademarks . . . 359
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
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 Portal.
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
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 Portal.
IBM Tivoli Netcool/OMNIbus
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 Portal. 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
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 Portal.
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.
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 Collection source
Availability Operating system
CAU Configuration Script
CAU Last Run Script
Cluster Domain WMI
Cluster Shared Volume WMI
Cluster Shared Volume Block Redirection Perfmon
Cluster Shared Volume Cache Perfmon
Cluster Shared Volume Coordinator Perfmon Cluster Shared Volume File System Perfmon
Cluster Shared Volume Manager Perfmon
Cluster Shared Volume IO Perfmon
Cluster Summary Script
Cluster Topology Script
Configuration WMI
CPU Interrupts Rollup WMI
CPU per Node WMI
CPU per Node Rollup WMI
Degradation Risk Script
Disk WMI
Disk MB Rollup WMI
Disk PCT Rollup WMI
Enterprise Cluster Summary Script
Event Log Windows Event Log
Global Update Messages Perfmon
Memory WMI
Memory MB Rollup WMI
Memory PCT Rollup WMI
MRR Messages Perfmon
Network Interfaces Script
Network Interfaces State Rollup WMI
Network Performance WMI
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
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.
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_dirwhere 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
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.
#---#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
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:
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)
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 Portal. The Microsoft Cluster Name configuration is used to set
CTIRA_HOSTNAME, which is the hostname part of the managed system name. The Managed System Status workspace of the enterprise view shows the status of each managed system. Note that this name is case sensitive and must be entered the same way on each node's agent configuration. Also, use only ASCII characters.
The Shared Agent History Directory field is required if the history configuration specifies that the
collection location is at the Tivoli Enterprise Monitoring Agent. 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 Description for section.
The configuration elements defined in this group are always present in the agent's configuration. This group defines information that applies to the entire agent.
Shared Agent History Directory (CTIRA_HIST_DIR)
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 Portal.
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
configureSystemor addSystem commands see "tacmd describeSystemType" 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
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
– 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
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
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
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
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 Type 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
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
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)
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
