Test 2

TivoliRIBM Tivoli Monitoring for Tivoli Enterprise ConsoleUserfs Guide Version
03.09.00 GC32-1959-00
TivoliRIBM Tivoli Monitoring for Tivoli Enterprise ConsoleUserfs Guide Version

03.09.00 GC32-1959-00
Note Before using this information and the product it supports, read the information
in Appendix D, gNotices,h on page 121.First Edition (August 2006) This edition
applies to version 03.09.00 of IBM Tivoli Monitoring for Tivoli Enterprise Console and
to all subsequent releases and modifications until otherwise indicated in new
editions. c Copyright International Business Machines Corporation 2005, 2006. All
rights reserved. US Government Users Restricted Rights . Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . .v
About this guide . . . . . . . . . .vii
Who should read this guide . . . . . . . . .vii
What this guide contains . . . . . . . . . .vii
Publications . . . . . . . . . . . . . .viii
Prerequisite publications . . . . . . . . .viii
Related publications . . . . . . . . . .viii
Accessing terminology online . . . . . . .viii
Accessing publications online . . . . . . .ix
Ordering publications . . . . . . . . . .ix
Accessibility . . . . . . . . . . . . . .ix
Tivoli technical training . . . . . . . . . . .x
Support information . . . . . . . . . . . .x
Conventions used in this guide . . . . . . . .x
Typeface conventions . . . . . . . . . .x
Operating system-dependent variables and paths x
Chapter 1. Overview of the IBM Tivoli Monitoring for Tivoli Enterprise Console .1
IBM Tivoli Monitoring overview . . . . . . . .1
Features of IBM Tivoli Monitoring for Tivoli Enterprise Console . . . . . . . . . . . .1
IBM Tivoli Monitoring for Tivoli Enterprise Console functions . . . . . . . . . . . . . . .1
Components of IBM Tivoli Monitoring for Tivoli Enterprise Console . . . . . . . . . . . .2

User interface options . . . . . . . . . . .2
Chapter 2. Requirements for the monitoring agent . . . . . . . . . . .3
Configuring a silent installation . . . . . . . .7
Windows systems . . . . . . . . . . . .7
Linux and UNIX systems . . . . . . . . .8
Chapter 3. How to use a monitoring agent . . . . . . . . . . . . . . . .9
View real-time data that the agent collects . . . .9
Investigate an event . . . . . . . . . . .10
Recover the operation of a resource . . . . . .10
Customize your monitoring environment . . . .11
Monitor with custom situations that meet your requirements . . . . . . . . . . . . . .12
Collect and view historical data . . . . . . .13
Chapter 4. Workspaces reference . . .15
About workspaces . . . . . . . . . . . .15
More information about workspaces . . . . . .15
Predefined workspaces . . . . . . . . . .15
Tivoli Enterprise Console Navigator item . . . .16
Availability Navigator item . . . . . . . . .16
Event Activity Navigator item . . . . . . . .17
Event Distribution Navigator item . . . . . . .19
Event Throughput Navigator item . . . . . . .20
Chapter 5. Attributes reference . . . .25
About attributes . . . . . . . . . . . . .25
More information about attributes . . . . . . .25
Attribute groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise Console
. . . .25
Availability attribute group . . . . . . . . .26
Event Activity attribute group . . . . . . . .29
Event Activity Base attribute group . . . . . .31
Event Activity Class attribute group . . . . . .32

Event Distribution attribute group . . . . . . .34
Event Distribution Base attribute group . . . . .35
Event Distribution By Class attribute group . . .36
Event Distribution By Class Base attribute group . .38
Event Distribution By Host attribute group . . . .40
Event Distribution By Host Base attribute group . .42
Event Distribution By Source attribute group . . .43
Event Distribution By Source Base attribute group 45
Event Distribution By Status attribute group . . .47
Event Distribution By Status Base attribute group .49
Event Severity attribute group . . . . . . . .50
Event Status attribute group . . . . . . . . .51
Event Throughput attribute group . . . . . . .51
Performance Object Status attribute group . . . .56
Disk capacity planning for historical data . . . .58
Chapter 6. Situations reference . . . .61
About situations . . . . . . . . . . . . .61
More information about situations . . . . . . .61
Predefined situations . . . . . . . . . . .62
Tivoli Enterprise Console Navigator item . . . .63
Availability Navigator item . . . . . . . . .63
KKA_Process_Data_Unavailable situation . . .63
KKA_TEC_Reception_Proc_Down situation . . .64
KKA_TEC_UI_Srvr_Proc_Down situation . . .64
KKA_TEC_Dispatch_Proc_Down situation . . .65
KKA_TEC_Rule_Proc_Down situation . . . .65
KKA_TEC_Server_Proc_Down situation . . . .66
KKA_TEC_Task_Proc_Down situation . . . .66
KKA_TEC_Receptn_Proc_CPU_High situation . .67
KKA_TEC_Receptn_Proc_CPU_Crit situation . .67

KKA_TEC_UI_Srvr_Proc_CPU_High situation . .68
KKA_TEC_UI_Srvr_Proc_CPU_Crit situation . .68
KKA_TEC_Dispatch_Proc_CPU_High situation 69
KKA_TEC_Dispatch_Proc_CPU_Crit situation . .69
KKA_TEC_Rule_Proc_CPU_High situation . . .70
KKA_TEC_Rule_Proc_CPU_Crit situation . . .70
KKA_TEC_Server_Proc_CPU_High situation . .71
KKA_TEC_Server_Proc_CPU_Crit situation . . .71
KKA_TEC_Task_Proc_CPU_High situation . . .72
KKA_TEC_Task_Proc_CPU_Crit situation . . .72
Event Activity Navigator item . . . . . . . .73
Event Distribution Navigator item . . . . . . .73
KKA_TEC_Events_Count_High situation . . .73
KKA_TEC_Fatal_Events_Ct_High situation . . .73
Event Throughput Navigator item . . . . . . .74 c Copyright IBM Corp. 2005, 2006 iii
KKA_TEC_Event_Arriv_Rate_Crit situation . . .74
KKA_TEC_Queued_Crit situation . . . . . .74
KKA_TEC_Waiting_Events_High situation . . .75
KKA_TEC_Parse_Failures situation . . . . .75
Chapter 7. Take Action commands reference . . . . . . . . . . . . . .77
About Take Action commands . . . . . . . .77
More information about Take Action commands . .77
Predefined Take Action commands . . . . . .77
Purge Event Repository action . . . . . . . .78
Purge Reception Log action . . . . . . . . .79
Start TEC Server action . . . . . . . . . .80
Stop TEC Server action . . . . . . . . . .81
Chapter 8. Policies reference . . . . .83
About policies . . . . . . . . . . . . .83
More information about policies . . . . . . .83

Appendix A. IBM Tivoli Enterprise Console event mapping . . . . . . .85
Appendix B. Problem determination . .93
Gathering product information for IBM Software Support . . . . . . . . . . . . . . .93
Built-in problem determination features . . . . .93
Problem classification . . . . . . . . . . .94
Trace logging . . . . . . . . . . . . . .94
Overview of log file management . . . . . .94
Examples of trace logging . . . . . . . .95
Principal trace log files . . . . . . . . .95
Setting RAS trace parameters . . . . . . .99
Setting trace parameters for the Tivoli Enterprise Console server . . . . . . . . . . . .100
Problems and workarounds . . . . . . . .101
Installation and configuration problem determination . . . . . . . . . . . .101
Agent problem determination . . . . . . .103
Problem determination for remote deployment 106
Workspace problem determination . . . . .106
Situation problem determination . . . . . .108
Support information . . . . . . . . . . .111
Using IBM Support Assistant . . . . . . .111
Obtaining fixes . . . . . . . . . . . .112
Receiving weekly support updates . . . . .112
Contacting IBM Software Support . . . . .112
Informational, warning, and error messages . . .114
Message format . . . . . . . . . . . .115
IBM Tivoli Monitoring for Tivoli Enterprise Console messages . . . . . . . . . . .116
Appendix C. Accessibility . . . . . .119
Navigating the interface using the keyboard . . .119
Magnifying what is displayed on the screen . . .119
Appendix D. Notices . . . . . . . .121
Trademarks . . . . . . . . . . . . . .122
Index . . . . . . . . . . . . . . .125
iv IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Tables
1. View real-time data . . . . . . . . . .9
2. Investigating an event . . . . . . . . .10
3. Recover the operation of a resource . . . .11
4. Customizing your monitoring environment 11
5. Monitor with custom situations . . . . . .13
6. Collect and view historical data . . . . . .14
7. Capacity planning for historical data logged by component Tec Health
Agent . . . . . . .58
8. Information to gather before contacting IBM Software Support . . . . . . . . . .93
9. Trace log files for troubleshooting agents 96
10. Problems and solutions for installation and configuration . . . . . . . . . . .101
11. General problems and solutions for uninstallation . . . . . . . . . . .103
12. Agent problems and solutions . . . . . .103
13. Remote deployment problems and solutions 106
14. Workspace problems and solutions . . . .107
15. General situation problems and solutions 108
16. Problems with configuring situations that you solve in the Situation
Editor . . . . . .109
17. Problems with configuration of situations that you solve in the Workspace
area . . . . .110
18. Take Action commands problems and solutions . . . . . . . . . . . . .111
c Copyright IBM Corp. 2005, 2006 v
vi IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
About this guide IBM Tivoli Monitoring for Tivoli Enterprise Console Userfs Guide
provides information about installing and using IBM Tivoli Monitoring for Tivoli
Enterprise Console. Use the configuration chapter in this guide along with IBM Tivoli
Monitoring Installation and Setup Guide to install and set up the software. Use the
information in this guide along with IBM Tivoli Monitoring Userfs Guide to monitor
Tivoli Enterprise Console. Who should read this guide This guide is for system
administrators who install and use the IBM Tivoli Monitoring for Tivoli Enterprise
Console to monitor and manage Tivoli Enterprise Console resources. Readers should
be familiar with the following topics: v Tivoli Enterprise Portal interface v IBM Tivoli
Monitoring application software v IBM Tivoli Enterprise ConsoleR (optional) v Tivoli
Enterprise Console environmentsWhat this guide contains This guide contains the
following chapters: v Chapter 1, gOverview of the IBM Tivoli Monitoring for Tivoli
Enterprise Console,h on page 1 Provides an introduction to the IBM Tivoli
Monitoring for Tivoli Enterprise Console. v Chapter 2, gRequirements for the
monitoring agent,h on page 3 Provides information about the requirements for the
IBM Tivoli Monitoring for Tivoli Enterprise Console. v Chapter 3, gHow to use a
monitoring agent,h on page 9 Provides a list of tasks to achieve when using a
monitoring agent, a list of procedures for performing each task, and references for
where to find information about the procedures. After completing installation and
configuration and becoming familiar with the information in Chapter 1 of this guide,
use this chapter to see how you can use a monitoring agent. v Chapter 4,
gWorkspaces reference,h on page 15 Provides an overview of workspaces,
references to additional information about workspaces, and descriptions of
predefined workspaces in this monitoring agent. v Chapter 5, gAttributes
reference,h on page 25 Provides an overview of attributes, references to additional
information about attributes, descriptions of the attribute groups and attributes in
this monitoring agent, and disk space requirements for historical data. v Chapter 6,
gSituations reference,h on page 61 Provides an overview of situations, references
to additional information about situations, and descriptions of the predefined
situations in this monitoring agent. c Copyright IBM Corp. 2005, 2006 vii
v Chapter 7, gTake Action commands reference,h on page 77 Provides detailed
information about the Take Action commands, references to additional information
about Take Action commands, and descriptions of the Take Action commands
provided in this monitoring agent. v Chapter 8, gPolicies reference,h on page 83
Provides an overview of policies, references for detailed information about policies,
and descriptions of the predefined policies included in this monitoring agent. v
Appendix A, gIBM Tivoli Enterprise Console event mapping,h on page 85 Provides
an overview of the IBM Tivoli Enterprise Console event mapping information for this
monitoring agent. v Appendix B, gProblem determination,h on page 93 Provides
information about troubleshooting the various components of the IBM Tivoli
Monitoring for Tivoli Enterprise Console, information about log files, and information
about your options for obtaining software support. v Appendix C, gAccessibility,h
on page 119 Provides information about the accessibility features in the IBM Tivoli
Monitoring for Tivoli Enterprise Console. v Appendix D, gNotices,h on page 121
Provides IBM and Tivoli notices and trademark information as it applies to the IBM
Tivoli Monitoring for Tivoli Enterprise Console.Publications This section lists
publications relevant to the use of the IBM Tivoli Monitoring for Tivoli Enterprise
Console. It also describes how to access these publications online and how to order
these publications. Prerequisite publications To use the information in this guide
effectively, you must have some knowledge of IBM Tivoli Monitoring products, which
you can obtain from the following documentation: v IBM Tivoli Monitoring
Administratorfs Guide v IBM Tivoli Monitoring Installation and Setup Guide v IBM
Tivoli Monitoring Problem Determination Guide v IBM Tivoli Monitoring Userfs Guide
v IBM Tivoli Monitoring Readme FirstRelated publications The following documents
also provide useful information: v IBM Tivoli Enterprise Console Adapters Guide v
IBM Tivoli Enterprise Console Event Integration Facility Userfs Guide v IBM Tivoli
Enterprise Console Reference Manual v IBM Tivoli Enterprise Console Rule
Developerfs GuideAccessing terminology online The Tivoli Software Glossary
includes definitions for many of the technical terms related to Tivoli software. The
Tivoli Software Glossary is available at the following Tivoli software library Web site:
viii IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm The IBM
Terminology Web site consolidates the terminology from IBM product libraries in one
convenient location. You can access the Terminology Web site at the following Web
address: http://www.ibm.com/ibm/terminology Accessing publications online The
documentation CD contains the publications that are in the product library. The
format of the publications is PDF, HTML, or both. Refer to the readme file on the CD
for instructions on how to access the documentation. IBM posts publications for this
and all other Tivoli products, as they become available and whenever they are
updated, to the Tivoli software information center Web site. Access the Tivoli
software information center by first going to the Tivoli software library at the
following Web address: http://www.ibm.com/software/tivoli/library Click the Tivoli
product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing
window, click ITM Tivoli Monitoring to access your product library at the Tivoli
software information center. Note: If you print PDF documents on other than lettersized paper, set the option in the File Print window that allows Adobe Reader to
print letter-sized pages on your local paper. Ordering publications You can order
many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi You
can also order by telephone by calling one of these numbers: v In the United States:
800-879-2755 v In Canada: 800-426-4968 In other countries, contact your software
account representative to order Tivoli publications. Accessibility Accessibility
features help users with a physical disability, such as restricted mobility or limited
vision, to use software products successfully. With this product, you can use
assistive technologies to hear and navigate the interface. You can also use the
keyboard instead of the mouse to operate most features of the graphical user
interface. For additional information, see Appendix C, gAccessibility,h on page
119. About this guide ix
Tivoli technical training For Tivoli technical training information, refer to the
following IBM Tivoli Education Web site:
http://www.ibm.com/software/tivoli/education/ Support information gSupport
informationh on page 111 describes the following options for obtaining support for
IBM products: v gUsing IBM Support Assistanth on page 111 v gObtaining
fixesh on page 112 v gReceiving weekly support updatesh on page 112 v
gContacting IBM Software Supporth on page 112Conventions used in this guide
This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths. Typeface conventions This guide uses the
following typeface conventions: Bold v Lowercase commands and mixed case

commands that are otherwise difficult to distinguish from surrounding text v
Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields,
folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu
choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating
system considerations:) v Keywords and parameters in textItalic v Words defined in
text v Emphasis of words v New terms in text (except in a definition list) v Variables
and values you must provideMonospace v Examples and code examples v File
names, programming keywords, and other elements that are difficult to distinguish
from surrounding text v Message text and prompts addressed to the user v Text that
the user must type v Values for arguments or command optionsOperating systemdependent variables and paths The direction of the slash for directory paths might
vary in this documentation. No matter which type of slash you see in the
documentation, use the following guidelines for a slash: v If using LinuxR or UNIXR,
use a forward slash (/). x IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
v If using WindowsR, use a backslash (\).The names of environment variables are
not always the same in Windows and other operating systems. For example, %TEMP
% in Windows is equivalent to $TEMP in Linux or UNIX. For environment variables,
use the following guidelines: v If using Linux or UNIX, use $variable. v If using
Windows, use %variable%.Note: If you are using the bash shell on a Windows
system, you can use the UNIX conventions.
About this guide xi
xii IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Chapter 1. Overview of the IBM Tivoli Monitoring for Tivoli Enterprise Console The
IBM Tivoli Monitoring for Tivoli Enterprise Console provides you with the capability to
monitor Tivoli Enterprise Console, and to perform basic actions with Tivoli Enterprise
Console. This chapter provides a description of the features, components, and
interface options for the IBM Tivoli Monitoring for Tivoli Enterprise Console. IBM
Tivoli Monitoring overview IBM Tivoli Monitoring is the base software for the IBM
Tivoli Monitoring for Tivoli Enterprise Console. 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 do the following: v Monitor for alerts on the systems that
you are managing by using predefined situations or custom situations. v Establish
your own performance thresholds. v Trace the causes leading to an alert. v Gather
comprehensive data about system conditions. v Use policies to perform actions,
schedule work, and automate manual tasks.The Tivoli Enterprise Portal is the
interface for IBM Tivoli Monitoring products. By providing a consolidated view of
your environment, the Tivoli Enterprise Portal permits you to monitor and resolve
performance issues throughout the enterprise. See the IBM Tivoli Monitoring
publications listed in gPrerequisite publicationsh on page viii for complete
information about IBM Tivoli Monitoring and the Tivoli Enterprise Portal. Features of
IBM Tivoli Monitoring for Tivoli Enterprise Console The IBM Tivoli Monitoring for Tivoli
Enterprise Console software can identify, notify you of, and correct common
problems with the application that it monitors. The software includes the following
features: v Monitoring v Data gathering v Event management v Operations
managementIBM Tivoli Monitoring for Tivoli Enterprise Console functions IBM Tivoli
Monitoring for Tivoli Enterprise Console provides the following functions: c Copyright
IBM Corp. 2005, 2006 1
Monitoring of Tivoli Enterprise Console Monitor Tivoli Enterprise Console health and
performance, rule base execution, and event activity and distribution.Components
of IBM Tivoli Monitoring for Tivoli Enterprise Console After you install and set up the
IBM Tivoli Monitoring for Tivoli Enterprise Console, you have an environment that
contains the client, server, and monitoring agent implementation for IBM Tivoli
Monitoring that contains the following components: v Tivoli Enterprise Portal client
with a Java-based user interface for viewing and monitoring your enterprise. v Tivoli
Enterprise Portal Server that is placed between the client and the Tivoli Enterprise
Monitoring Server and enables retrieval, manipulation, and analysis of data from the
monitoring agents. The Tivoli Enterprise Portal Server is the central repository for all
user data. v Tivoli Enterprise Monitoring Server acts as a collection and control point
for alerts received from the monitoring agents, and collects their performance and
availability data. The Tivoli Enterprise Monitoring Server is also a repository for
historical data. v Monitoring agent, IBM Tivoli Monitoring for Tivoli Enterprise
Console, installed on the systems or subsystems that you want to monitor. This
monitoring agent collects and distributes data to a Tivoli Enterprise Portal
Server.IBM Tivoli Enterprise Console is an optional component, which acts as a
central collection point for events from a variety of sources, including those from
other Tivoli software applications, Tivoli partner applications, custom applications,
network management platforms, and relational database systems. You can view
these events through the Tivoli Enterprise Portal (using the event viewer), and you
can forward events from IBM Tivoli Monitoring situations to the IBM Tivoli Enterprise
Console component. User interface options Installation of the base software and
other integrated applications provides the following interfaces that you can use to
work with your resources and data: Tivoli Enterprise Portal browser client interface
The browser interface is automatically installed with Tivoli Enterprise Portal. To start
Tivoli Enterprise Portal in your Internet browser, enter the URL for a specific Tivoli
Enterprise Portal browser client installed on your Web server. Tivoli Enterprise Portal
desktop client interface The desktop interface is a Java-based graphical user
interface (GUI) on a Windows or Linux workstation. IBM Tivoli Enterprise Console
Event management application Manage Tivoli Enterprise Monitoring Services
window The window for the Manage Tivoli Enterprise Monitoring Services utility is
used for configuring the agent and starting Tivoli services not already designated to
start automatically.
2 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Chapter 2. Requirements for the monitoring agent This chapter contains information
about the requirements for the IBM Tivoli Monitoring for Tivoli Enterprise Console. In
addition to the requirements described in the IBM Tivoli Monitoring Installation and
Setup Guide, the IBM Tivoli Monitoring for Tivoli Enterprise Console has the following
requirements: v The monitoring agent runs on these operating systems: . AIX 5.1 .
AIX 5.1.0C . AIX 5.2 . AIX 5.3 . Solaris 8 for SPARC . Solaris 9 for SPARC . Solaris 10
for SPARC . HP-UX 11i . Windows 2003 Server . Windows Server 2003 Enterprise
Edition . Windows Server 2003 Datacenter Edition . Red Hat EL Advanced Server 2.1
for IA32 . Red Hat EL Advanced Server 3.0 for IA32 . Red Hat EL Advanced Server
3.0 for zSeries . Red Hat EL Advanced Server 4.0 for IA32 . Red Hat EL Advanced
Server 4.0 for zSeries . United Linux 1/ SuSe 8 for IA32 . United Linux 1/ SuSe 8 for
zSeries . United Linux 1/ SuSe 9 for IA32 . United Linux 1/ SuSe 9 for zSeries If
running this agent on a Windows operating system, the User ID must have
Administrator privileges. v Monitors the following versions: . Tivoli Enterprise
Console Tivoli Enterprise Console 3.9 Fix Pack 5v A single computer that hosts the
hub monitoring server, portal server, and a monitoring agent requires
approximately 300 MB of space. A monitored computer that hosts only the
monitoring agent requires approximately 30 MB of space, including the specific
enablement code for the monitoring agent. More space is required for each
additional monitoring agent that you deploy on the monitored computer.After you
install the IBM Tivoli Monitoring Version 6.1 and the Tivoli Enterprise Portal, you
install the following software that is required for IBM Tivoli Monitoring for Tivoli
Enterprise Console to operate: v IBM Tivoli Monitoring 6.1 Fix Pack 3 v IBM Tivoli
Monitoring for Tivoli Enterprise Console c Copyright IBM Corp. 2005, 2006 3
v IBM Tivoli Monitoring for Tivoli Enterprise Console Support for Tivoli Enterprise
Management Server v IBM Tivoli Monitoring for Tivoli Enterprise Console Support for
Tivoli Enterprise Portal Server v IBM Tivoli Monitoring for Tivoli Enterprise Console
Support for Tivoli Enterprise PortalTo use the search function for this agent's online
help, ensure that you have selected the IBM Eclipse help server check box when
installing the Tivoli Enterprise Portal Server. The 'Searching Agent Help' topic in this
agent's online help contains a link to the Eclipse help, where the search function is
enabled. From the Table of Contents in the left-hand pane of the help, select the
'Searching Agent Help' topic to find the link to the Eclipse help in the right-hand
pane. This agent collects data from the following data sources: Availability The
agent monitors application availability using various mechanisms: v The agent
monitors the status of the processes that make up the application in order to
determine the availability of the application or its subcomponents.Scripts The agent
uses application-specific commands or interfaces to gather metrics. Log files The
agent uses the file system to monitor application log files or other data files to
gather metrics.To be able to run Tivoli Management Environment (TME) tasks, the
agent must be started by a user with sufficient TME privileges. On a Windows
system, use the following steps to modify the startup configuration: 1. Start the
Manage Tivoli Monitoring Services application. 2. Select the IBM Tivoli Monitoring for
Tivoli Enterprise Console agent. 3. From the Actions menu, select Change startup. 4.
In the Log On As field, select This Account. 5. Enter the user ID and password for an
account with sufficient TME privileges for starting tasks and accessing the Tivoli
Management Framework RIM object. 6. Click OK. In addition to configuring the
monitoring agent itself, you must also set up the Tivoli Enterprise Console product
to support monitoring. To complete the configuration, follow these steps: 1. On the
Tivoli Enterprise Console system, set up the TME environment by running the
setup_env.cmd (Windows) or setup_env.sh (Linux or UNIX) script. 2. Create the
working tables the monitoring agent uses to store gathered metrics from the event
repository. Use this command: wagtinit {-c|-r} [-t tablespace] [-p] [-d] The
parameters are as follows: -c Creates the tables and views for the agent. You must
specify either the -c or the -r parameter. 4 IBM Tivoli Monitoring for Tivoli Enterprise
Console: Userfs Guide
-r Removes the tables and views for the agent. You must specify either the -c or the
-r parameter. -t tablespace Specifies the location for the working tables. Replace
tablespace with one of the following values: v For a DB2 or Oracle database, the
name of an existing tablespace. v For an Informix database, the name of an existing
dbspace. v For a SQL Server database, the name of an existing file group. v For a
Sybase database, the name of an existing segment.If you do not specify the -t
parameter, the command uses the default location for the user specified in the
Tivoli Management Framework RIM object. -p Creates the specified SQL statements
without actually creating or removing the tables and views. Use this option in
combination with -c or -r if you want to modify the generated SQL before creating or
removing the tables and views. -d Specifies that the wagtinit command should
output additional debugging messages.The following command creates the required
tables and views in the default location: wagtinit -c Note: The wagtinit command
creates tables and views using the user ID defined in the RIM object. This user ID
must have CREATE VIEW and CREATE TABLE privileges for the command to function.
The database administrator can grant these privileges temporarily and revoke them
after the wagtinit command creates the tables and views. 3. Modify the Tivoli
Enterprise Console configuration to enable gathering of performance metrics.
Configure the following parameters in the $BINDIR/TME/TEC/.tec_config
configuration file: tec_log_metrics=YES|NO Enables or disables the gathering of
performance metrics. Setting this parameter to NO disables the gathering of all
performance metrics. tec_rule_sample_class_size=size The number of performance
metrics counters to keep in memory; one counter is used for each unique event
class name encountered. the minimum valid value for this parameter is 200
counters. Setting this parameter to 0, or omitting it, disables the gathering of event
activity metrics. tec_rule_sample_period=seconds The sample period, in seconds, to
use when monitoring event activity in the Tivoli Enterprise Console rule engine.
Setting this parameter to 0, or omitting it, disables the gathering of event activity
metrics. tec_reception_sample_period=seconds The sample period, in seconds, to
use when gathering performance metrics for Tivoli Enterprise Console event
reception. Setting this parameter to 0 disables the gathering of performance
metrics for event reception. tec_max_log_entries=lines The maximum number of
lines to write to the log files used for Chapter 2. Requirements for the monitoring
agent 5
performance metrics. Each line uses a maximum of approximately 200 bytes of disk
space. As many as two log files are created for each metric attribute group. The
minimum valid value for this parameter is 5000 lines (approximately 1 MB of disk
space). tec_log_metrics_dir=path The directory to use for storing the performance
metrics log files. This value must match the value entered in the agent
configuration. On Windows systems, be sure the path does not include any spaces
(for example, specify C:\Progra~1\... instead of C:\Program Files\...).4. Create the
directory specified by the tec_log_metrics_dir parameter in the .tec_config
configuration file. Make sure the agent user account has sufficient privileges to read
files in this directory. 5. Restart the Tivoli Enterprise Console server.If you are using
a Sybase or SQL Server database, you might also need to modify your database
configuration. Because the event distribution workspaces use a significant amount
of temporary workspace for queries, make sure the tempdb database has sufficient
space allocated. The amount of space required is proportional to the number of
events in the event repository and is increased if you enable the event source and
host dimensions for the event distribution data. The minimum recommended
allocation for the tempdb database is 100MB.Note: If you do not allocate enough
space for the tempdb database, the Tivoli Enterprise Console product might stop
functioning. If this happens, messages in the database log files indicate that there is
insufficient temporary space available. The following configuration values must be
provided for the agent to operate. When configuring an agent, a panel displays that
allows you to type in each value. When there is a default value, this will be preentered into the field. If a field represents a password, there will be 2 entry fields
displayed. You must enter the same value in each field. The values you type will not
be displayed. This helps maintain the security of these values. The following fields
are defined for this agent: v Tab: Event Distribution v Field: Include host dimension v
Type: restricted Flag to indicate whether to include the host dimension in the event
distribution data.v Tab: Event Distribution v Field: Include event source dimension v
Type: restricted Flag to indicate whether to include the event source dimension in
the event distribution data.v Tab: Paths v Field: Log Directory v Type: string
Directory that contains the Tivoli Enterprise Console metric log files. Value must
match tec_log_metrics_dir value in the .tec_config file. Use a fully qualified path that
does not include any environment variable references. On Windows systems, be
sure the path does not include any spaces or long file names.v Tab: Event
Distribution 6 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
v Field: String to represent null values v Type: string Value that represents a NULL or
blank value. This string should be no more than 64 characters in length.v Tab: Event
Distribution v Field: Refresh Interval v Type: numeric The maximum time, in
minutes, that the event distribution data may be cached. A value of 0 indicates that
the distribution is recalculated every time a request is made for the data.When
installing the agent remotely, the configuration values should be provided, as in the
following examples. v On a Windows system: tacmd addSystem -t KA -n
sample.node.name:NT -p event_distribution.KKA_DIST_BY_HOST=value
event_distribution.KKA_DIST_BY_SOURCE=value paths.KKA_LOG_DIR=value
event_distribution.KKA_NULL_STRING=value
event_distribution.KKA_REFRESH_INTERVAL=value v On a Linux system: tacmd
addSystem -t ka -n sample.node.name:LZ -p
event_distribution.KKA_DIST_BY_HOST=value
event_distribution.KKA_DIST_BY_SOURCE=value paths.KKA_LOG_DIR=value
event_distribution.KKA_NULL_STRING=value
event_distribution.KKA_REFRESH_INTERVAL=value To see the supported

configuration values for the parameters, use the tacmd describeSystemType
command: v On a Windows system: tacmd describeSystemType -t KA -p platform v
On a Linux or UNIX system: tacmd describeSystemType -t ka -p platform For more
information about this command, refer to the IBM Tivoli Monitoring documentation.
Configuring a silent installation You can configure a silent installation or
configuration of the monitoring agent by adding the required parameters to the
appropriate configuration file. (For more information on performing a silent
installation or configuration, refer to the IBM Tivoli Monitoring Installation and Setup
Guide.) Windows systems To perform a silent installation of the monitoring agent on
a Windows system, you must modify the silent.txt configuration file (included in the
Windows directory on the product installation CD). Add the following parameters in
the TEMA_CONFIGURATION section, after the [CMA_CONFIG] line: ; The path to the
TEC metrics log files. This value must match the. ; tec_log_metrics_dir value defined
in %BINDIR%\TME\TEC\.tec_config. ; Specify a fully qualified path that does not
contain environment ; variables or spaces (for example, c:\Progra~1\... instead of ;
C:\Program Files\...).
Chapter 2. Requirements for the monitoring agent 7
KKA_LOG_DIR=path ; The refresh interval (in minutes) for event distribution data. A ;
value of 0 indicates that the distribution is recalculated every time ; a request is
made for data (this has a negative performance impact).
KKA_REFRESH_INTERVAL=15 ; Whether the event source dimension should be
included in the ; distribution. Specify DIST_BY_SOURCE_TRUE to include the source ;
or DIST_BY_SOURCE_FALSE to exclude the source dimension. ;
DIST_BY_SOURCE_FALSE is the default value.
KKA_DIST_BY_SOURCE=DIST_BY_SOURCE_FALSE ; Whether the host name dimension
should be included in the ; distribution. Specify DIST_BY_HOST_TRUE to include the
host ; dimension or DIST_BY_HOST_FALSE to exclude the host dimension. ;
DIST_BY_HOST_FALSE is the default value.
KKA_DIST_BY_HOST=DIST_BY_HOST_FALSE ; The value to use to represent NULL or
blank values in the distribution ; data. KKA_NULL_STRING=N/A
Linux and UNIX systems To perform a silent configuration of the monitoring agent on
a Linux or UNIX system, modify the silent_config.txt configuration file in the
$CANDLE_HOME/samples directory. Add the following parameters at the end of the
file: # The path to the TEC metrics log files. This value must match the. #
tec_log_metrics_dir value defined in $BINDIR/TME/TEC/.tec_config. # Specify a fully
qualified path that does not contain environment # variables. KKA_LOG_DIR=path #
The refresh interval (in minutes) for event distribution data. A # value of 0 indicates
that the distribution is recalculated every time # a request is made for data (this
has a negative performance impact). KKA_REFRESH_INTERVAL=15 # Whether the
event source dimension should be included in the # distribution. Specify
DIST_BY_SOURCE_TRUE to include the source # or DIST_BY_SOURCE_FALSE to
exclude the source dimension. # DIST_BY_SOURCE_FALSE is the default value.
KKA_DIST_BY_SOURCE=DIST_BY_SOURCE_FALSE # Whether the host name
dimension should be included in the # distribution. Specify DIST_BY_HOST_TRUE to
include the host # dimension or DIST_BY_HOST_FALSE to exclude the host

dimension. # DIST_BY_HOST_FALSE is the default value.
KKA_DIST_BY_HOST=DIST_BY_HOST_FALSE # The value to use to represent NULL or
blank values in the distribution # data. KKA_NULL_STRING=N/A 8 IBM Tivoli
Monitoring for Tivoli Enterprise Console: Userfs Guide
Chapter 3. How to use a monitoring agent After you have installed and configured a
Tivoli Enterprise Monitoring Agent and the agent is running, you can begin using
this agent to monitor your resources. The following sources of information are
relevant to installation and configuration: v IBM Tivoli Monitoring Installation and
Setup Guide v Chapter 2, gRequirements for the monitoring agenth in the userfs
guide for the agent that you are installing and configuringThis chapter provides
information about how to use a monitoring agent to achieve the following purposes:
v gView real-time data that the agent collectsh v gInvestigate an eventh on
page 10 v gRecover the operation of a resourceh on page 10 v gCustomize your
monitoring environmenth on page 11 v gMonitor with custom situations that
meet your requirementsh on page 12 v gCollect and view historical datah on
page 13For each of these purposes, there is a list of procedures that you perform to
achieve the purpose. For each procedure, there is a cross-reference to where you
can find information about performing that procedure. Information about the
procedures is located in subsequent chapters of this userfs guide and in the
following publications: v IBM Tivoli Monitoring Userfs Guide v IBM Tivoli Monitoring
Administratorfs GuideView real-time data that the agent collects After you install
and configure the Tivoli Enterprise Monitoring Agent, the agent begins monitoring.
Table 1 contains a list of the procedures for viewing the real-time data that the
monitoring agent collects through the predefined situations. The table also contains
a cross-reference to where you can find information about each procedure.
Table 1. View real-time data
Procedure
Where to find information
View the hierarchy of your monitored resources from a system point of view
(Navigator view organized by operating platform, system type, monitoring agents,
and attribute groups).
IBM Tivoli Monitoring Userfs Guide: Navigating through workspaces (in
Monitoring: real-time and event-based chapter)
View the indicators of real or potential problems with the monitored resources
(Navigator view). c Copyright IBM Corp. 2005, 2006 9
Table 1. View real-time data (continued)
Procedure
View changes in the status of the resources that are being monitored (Enterprise
Message Log view).
IBM Tivoli Monitoring Userfs Guide: Using workspaces (in Monitoring: realtime and event-based chapter) Chapter 4, gWorkspaces reference,h on page
15 in this guide
View the number of times an event has been opened for a situation during the past
24 hours (Open Situations Account view).
IBM Tivoli Monitoring Userfs Guide: Using workspaces (in Monitoring: realtime and event-based chapter) Chapter 6, gSituations reference,h on page 61
in this guide
Manipulate the views in a workspace.
IBM Tivoli Monitoring Userfs Guide: Using views (in Monitoring: real-time
and event-based chapter) Chapter 4, gWorkspaces reference,h on page 15 in
this guide Investigate an event When the conditions of a situation have been met,
an event indicator is displayed in the Navigator. When an event occurs, you want to
obtain information about that event so you can correct the conditions and keep your
enterprise running smoothly. Table 2 contains a list of the procedures for
investigating an event and a cross-reference to where you can find information
about each procedure.
Table 2. Investigating an event
Procedure
Determine which situation raised the event and identify the attributes that have
values that are contributing to the alert.
IBM Tivoli Monitoring Userfs Guide: Opening the situation event workspace (in
Monitoring: real-time and event-based chapter, Responding to alerts
section) Chapter 4, gWorkspaces reference,h on page 15 in this guide
Review available advice.
Notify other users that you have taken ownership of the problem related to an event
and are working on it.
IBM Tivoli Monitoring Userfs Guide: Acknowledging a situation event (in
section)
Remove the event from the Navigator.
IBM Tivoli Monitoring Userfs Guide: Closing the situation event workspace (in
section) Recover the operation of a resource When you find out that a resource is
not operating as desired, you can control it manually or automatically using Take
Action commands. 10 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
Table 3 contains a list of the procedures for recovering the operation of a resource
and a cross-reference to where you can find information about each procedure.
Table 3. Recover the operation of a resource
Procedure
Take an action on a resource manually.
IBM Tivoli Monitoring Userfs Guide: v Other views (in Custom workspaces
chapter, Workspace views section) v Take action: Reflex automation (in
Situations for event-based monitoring chapter, Event-based monitoring
overview section)Chapter 7, gTake Action commands reference,h on page 77 in
this guide
Take an action on a system condition automatically by setting up a situation to run a
Take Action command.
IBM Tivoli Monitoring Userfs Guide: Situations for event-based monitoring
chapter v Customize a situation v Create a situation v Specify an action
to take v Distribute the situationChapter 7, gTake Action commands
reference,h on page 77 in this guide
Take multiple actions on system conditions automatically using a policy.
IBM Tivoli Monitoring Userfs Guide: Policies for automation chapter v
Creating a policy v Maintaining policies v Workflows windowChapter 8,
gPolicies reference,h on page 83 in this guide
Take actions across systems, agents, or computers using a policy. Customize your
monitoring environment You can change how your monitoring environment looks by
creating new workspaces with one or more views in it. Table 4 contains a list of the
procedures for customizing your monitoring environment and a cross-reference to
where you can find information about each procedure.
Table 4. Customizing your monitoring environment
Procedure
Display data in tables or charts (views) in the Tivoli Enterprise Portal.
IBM Tivoli Monitoring Userfs Guide: v Custom workspaces v Table and chart
views
Display an overview of changes in the status of situations for your monitored
resources (Message Log View).
IBM Tivoli Monitoring Userfs Guide: Message log view (in Situation event
views: message log, situation event console and graphic chapter) Chapter 3. How
to use a monitoring agent 11
Table 4. Customizing your monitoring environment (continued)
Procedure
Specify which attributes to retrieve for a table or chart so you can retrieve only the
data you want by creating custom queries.
IBM Tivoli Monitoring Userfs Guide: Creating custom queries (in Table and
chart views chapter) Chapter 5, gAttributes reference,h on page 25 in this
guide
Build links from one workspace to another.
IBM Tivoli Monitoring Userfs Guide: v Link from a workspace (in Custom
workspaces chapter) v Link from a table or chart (in Table and chart
views chapter)
Identify which predefined situations started running automatically when you started
the Tivoli Enterprise Management Server.
IBM Tivoli Monitoring Userfs Guide: What the enterprise workspace shows (in
Monitoring: real-time and event-based chapter, Using workspaces section)
Chapter 6, gSituations reference,h on page 61 in this guide
Determine whether to run situations as defined, modify the values in situations, or
create new situations to detect possible problems.
gMonitor with custom situations that meet your requirementsh in this chapter
Chapter 6, gSituations reference,h on page 61 in this guide Monitor with custom
situations that meet your requirements When your environment requires situations
with values that are different from those in the existing situations, or when you
need to monitor conditions not defined by the existing situations, you can create
custom situations to detect problems with resources in two ways: v Create an
entirely new situation v Create a situation by copying and editing a predefined
situationYou can specify the following information for a situation: v Name v Attribute
group and attributes v Qualification to evaluate multiple rows when a situation has a
multiple-row attribute group (display item) v Formula v Take Action commands v Run
at startup v Sampling interval v Persistence v Manual or automatic start v Severity v
Clearing conditions v Expert Advice v When a true situation closes v Available
Managed Systems
Table 5 contains a list of the procedures for monitoring your resources with custom
situations that meet your requirements and a cross-reference to where you can find
information about each procedure.
Table 5. Monitor with custom situations

Procedure
Create an entirely new situation.
IBM Tivoli Monitoring Userfs Guide: Creating a new situation (in Situations
for event-based monitoring chapter, Creating a situation section) Chapter 5,
gAttributes reference,h on page 25 in this guide
Create a situation by copying and editing a predefined situation.
IBM Tivoli Monitoring Userfs Guide: Customize a situation (in Situations for
event-based monitoring chapter) Chapter 6, gSituations reference,h on page
61 in this guide Chapter 5, gAttributes reference,h on page 25 in this guide
Run a situation on a managed system.
IBM Tivoli Monitoring Userfs Guide: Situations for event-based monitoring
chapter v Associating situations with navigator items v Distribute the
situation (in Customizing a situation section) v Starting, stopping or
deleting a situation Collect and view historical data When you collect historical
data, you specify the following configuration requirements: v Attribute groups for
which to collect data v Collection interval v Roll-off interval to a data warehouse, if
any v Where to store the collected data (at the agent or the Tivoli Enterprise
Management Server)Table 6 on page 14 contains a list of the procedures for
collecting and viewing historical data and a cross-reference to where you can find
information about each procedure. Chapter 3. How to use a monitoring agent 13
Table 6. Collect and view historical data
Procedure
Configure and start collecting short-term data (24 hours).
IBM Tivoli Monitoring Userfs Guide: Historical reporting (in Table and chart
views chapter) IBM Tivoli Monitoring Administratorfs Guide gDisk capacity
planning for historical datah on page 58 in this guide
Configure and start collecting longer-term data (more than 24 hours).
View historical data in the Tivoli Enterprise Portal.
Create reports from historical data using third-party reporting tools.
Filter out unwanted data to see specific areas of interest. 14 IBM Tivoli Monitoring
for Tivoli Enterprise Console: Userfs Guide
Chapter 4. Workspaces reference This chapter contains an overview of workspaces,
references for detailed information about workspaces, and descriptions of the
predefined workspaces included in this monitoring agent. About workspaces A

workspace is the working area of the Tivoli Enterprise Portal application window. At
the left of the workspace is a Navigator that you use to select the workspace you
want to see. As you select items in the Navigator, the workspace presents views
pertinent to your selection. Each workspace has at least one view. Every workspace
has a set of properties associated with it. 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. More information about workspaces For more information about creating,
customizing, and working with workspaces, see IBM Tivoli Monitoring Userfs Guide.
For a list of the predefined workspaces for this monitoring agent and a description
of each workspace, refer to the Predefined workspaces section below and the
information in that section for each individual workspace. Some attribute groups for
this agent might not be represented in the predefined workspaces or views for this
agent. For a full list of the attribute groups, see the Attributes reference section.
Predefined workspaces IBM Tivoli Monitoring for Tivoli Enterprise Console provides
the following predefined workspaces, which are organized by Navigator item: v
Tivoli Enterprise Console Navigator item . Tivoli Enterprise Console workspacev
Availability Navigator item . Availability workspace . TEC UI Server Process
workspacev Event Activity Navigator item . Event Activity workspace . Event Activity
By Class - Last 24hrs workspace . Event Activity By Class - Last 1 Week workspace .
Event Activity By Class - Last 1 Month workspace . Event Activity By Class - Last 1
Year workspacev Event Distribution Navigator item c Copyright IBM Corp. 2005,
2006 15
. Event Distribution workspace . Open Events Distribution workspace .
Acknowledged Events Distribution workspace . Closed Events Distribution
workspacev Event Throughput Navigator item . Event Throughput workspace . Event
Throughput - Last 24hrs workspace . Event Throughput - Last 1 Week workspace .
Event Throughput - Last 1 Month workspace . Event Throughput - Last 1 Year
workspaceThe remaining sections of this chapter contain descriptions of each of
these predefined workspaces. The workspaces are organized by the Navigator item
to which the workspaces are relevant. Tivoli Enterprise Console Navigator item Tivoli
Enterprise Console workspace This workspace is not defined. This workspace
contains the following views: Browser This does not display any agent information.
Notepad This does not display any agent information.Availability Navigator item
Availability workspace This workspace shows data related to the Tivoli Enterprise
Console server processes (tec_server, tec_reception, tec_rule, tec_dispatch, and
tec_task). This workspace contains the following views: TEC Processes This view
shows the raw data for the Tivoli Enterprise Console server processes. TEC
Processes Processor Times This view shows the percentage of processor time used
by each of the Tivoli Enterprise Console server processes. TEC Processes Virtual
Sizes This view shows the memory virtual size, in MB, for each of the Tivoli
Enterprise Console server processes. TEC Processes CPU Times This view shows the
percentages of privileged and user-mode CPU time for each of the Tivoli Enterprise
Console server processes.TEC UI Server Process workspace This workspace shows
data related to the Tivoli Enterprise Console user interface server process
(tec_ui_server). This workspace contains the following views: 16 IBM Tivoli

TEC UI Server Process This view shows the raw data for the Tivoli Enterprise Console
user interface server process. TEC UI Server Process Processor Time This view
shows the percentage of processor time used by the Tivoli Enterprise Console user
interface server process. TEC UI Server Process Virtual Size This view shows the
memory virtual size, in MB, for the Tivoli Enterprise Console user interface server
process. TEC UI Server Processes CPU Time This view shows the percentages of
privileged and user-mode CPU time for the Tivoli Enterprise Console user interface
server process.Event Activity Navigator item Event Activity workspace This
workspace shows the Tivoli Enterprise Console real-time event activity data. This
workspace contains the following views: Total Time Spent in TEC Rule This view
shows the total time spent in Tivoli Enterprise Console rule processing for each
event class. The view shows only events with a nonzero total time. Tasks Submitted
For Execution This view shows the number of Tivoli Enterprise Console tasks started
for each event class. Events Input/Output to Rule Engine By Event Class This view
shows the number of events of each class flowing into and out of the Tivoli
Enterprise Console rule engine. These numbers might not match because of
dropped or generated events.Event Activity By Class - Last 24hrs workspace This
workspace shows the same data shown in the real-time Event Activity By Class
workspace over a period of 24 hours, using line charts. This view can be used only if
historical data collection is enabled by the TEPS administrator. The administrator
specifies the collection interval, collection location, and the warehouse interval. This
workspace contains the following views: Total Time Spent in TEC Rule - Last 24hrs
This view shows the total time spent in Tivoli Enterprise Console rule processing for
each event class. Tasks Submitted For Execution - Last 24hrs This view shows the
number of Tivoli Enterprise Console tasks started for each event class. Events
Input/Output to Rule Engine By Event Class - Last 24hrs This view shows the number
of events of each class flowing into and out of the Tivoli Enterprise Console rule
engine. These numbers might not match because of dropped or generated
events.Event Activity By Class - Last 1 Week workspace This workspace shows the
same data shown in the real-time Event Activity Chapter 4. Workspaces reference
17
By Class workspace over a period of one week, using line charts. This view can be
used only if historical data collection is enabled by the TEPS administrator. The
administrator specifies the collection interval, collection location, and the
warehouse interval. This workspace contains the following views: Total Time Spent
in TEC Rule - Last 1 Week This view shows the total time spent in Tivoli Enterprise
Console rule processing for each event class. Tasks Submitted For Execution - Last 1
Week This view shows the number of Tivoli Enterprise Console tasks started for
each event class. Events Input/Output to Rule Engine By Event Class - Last 1 Week
This view shows the number of events of each class flowing into and out of the
Tivoli Enterprise Console rule engine. These numbers might not match because of
dropped or generated events.Event Activity By Class - Last 1 Month workspace This
workspace shows the same data shown in the real-time Event Activity By Class
workspace over a period of one month, using line charts. This view can be used only
if historical data collection is enabled by the TEPS administrator. The administrator
workspace contains the following views: Total Time Spent in TEC Rule - Last 1 Month
This view shows the total time spent in Tivoli Enterprise Console rule processing for
each event class. Tasks Submitted For Execution - Last 1 Month This view shows the
number of Tivoli Enterprise Console tasks started for each event class. Events
Input/Output to Rule Engine By Event Class - Last 1 Month This view shows the
number of events of each class flowing into and out of the Tivoli Enterprise Console
rule engine. These numbers might not match because of dropped or generated
events.Event Activity By Class - Last 1 Year workspace This workspace shows the
same data shown in the real-time Event Activity By Class workspace over a period
of one year, using line charts. This view can be used only if historical data collection
is enabled by the TEPS administrator. The administrator specifies the collection
interval, collection location, and the warehouse interval. This workspace contains
the following views: Total Time Spent in TEC Rule - Last 1 Year This view shows the
total time spent in Tivoli Enterprise Console rule processing for each event class.
Tasks Submitted For Execution - Last 1 Year This view shows the number of Tivoli
Enterprise Console tasks started for each event class. Events Input/Output to Rule
Engine By Event Class - Last 1 Year This view shows the number of events of each
class flowing into and out of the Tivoli Enterprise Console rule engine. These
numbers might not match because of dropped or generated events.
Event Distribution Navigator item Event Distribution workspace This workspace
shows the Tivoli Enterprise Console real-time event distribution data. This
workspace contains the following views: Number of Events For Each Status This
view shows the total number of events in the event repository for each status value
(OPEN, ACKNOWLEDGED, RESPONSE, CLOSED, and CUSTOM). CUSTOM status
includes all events with custom status values. Open Events By Severity This view
shows the total number of open events in the event repository for each severity
(CUSTOM, UNKNOWN, HARMLESS, WARNING, MINOR, CRITICAL, and FATAL). By
default, the numeric status value for open events is 0; this can be modified in the
filter for the view. CUSTOM severity includes all events with custom severity values.
Acknowledged Events By Severity This view shows the total number of
acknowledged events in the event repository for each severity (CUSTOM,
UNKNOWN, HARMLESS, WARNING, MINOR, CRITICAL, and FATAL). By default, the
numeric status value for acknowledged events is 20; this can be modified in the
filter for the view. CUSTOM severity includes all events with custom severity values.
Closed Events By Severity This view shows the total number of closed events in the
event repository for each severity (CUSTOM, UNKNOWN, HARMLESS, WARNING,
MINOR, CRITICAL, and FATAL). By default, the numeric status value for closed events
is 30; this can be modified in the filter for the view. CUSTOM severity includes all
events with custom severity values.Open Events Distribution workspace This
workspace shows data about open events. This workspace contains the following
views: Open Events By Class This view shows the number of open events for each
class. Open Events By Host This view shows the number of open events for each
host. If the event host dimension is not enabled in the agent configuration, the view
shows no data. Open Events By Source This view shows the number of open events
for each source. If the event source dimension is not enabled in the agent
configuration, the view shows no data.Acknowledged Events Distribution workspace
This workspace shows data about acknowledged events. This workspace contains
the following views: Chapter 4. Workspaces reference 19
Acknowledged Events By Class This view shows the number of acknowledged
events for each class. Acknowledged Events By Host This view shows the number of
acknowledged events for each host. If the event host dimension is not enabled in
the agent configuration, the view shows no data. Acknowledged Events by Source
This view shows the number of acknowledged events for each source. If the event
source dimension is not enabled in the agent configuration, the view shows no
data.Closed Events Distribution workspace This workspace shows data about closed
events. This workspace contains the following views: Closed Events By Class This
view shows the number of closed events for each class. Closed Events By Host This
view shows the number of closed events for each host. If the event host dimension
is not enabled in the agent configuration, the view shows no data. Closed Events by
Source This view shows the number of closed events for each source. If the event
source dimension is not enabled in the agent configuration, the view shows no
data.Event Throughput Navigator item Event Throughput workspace This workspace
shows real-time event throughput data. This workspace contains the following
views: Total Processed and Received This view shows the total number of events
received and processed by the Tivoli Enterprise Console server since it was last
started. The total number of events processed includes events in both PROCESSED
and PARSING_FAILED states. Total Queued, Waiting, and Parse Failures This view
shows the total number of events in QUEUED state, the total number of events in
WAITING state, and the total number of events that could not be parsed. This data
can help to identify performance issues with the server or problems in the rule base.
Arrival and Processing Rates This view shows the event arrival rate and the event
processing rate of the monitored Tivoli Enterprise Console server. This data provides
an overview of server performance. Throughput in Sample Period This view shows
the number of events received and processed by the Tivoli Enterprise Console
server during the sample period. It also shows the number of parse failures during
the sample period. 20 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
Average Throughput in Sample Period This view shows the total number of events
received and processed by the Tivoli Enterprise Console server since it was last
started, divided by the number of sample periods that have occurred. It also shows
the same average for waiting events. (A backlog of waiting events might indicate
server performance problems.).Event Throughput - Last 24hrs workspace This
workspace shows the same data shown in the real-time Event Throughput
workspace over a period of 24 hours. This view can be used only if historical data
collection is enabled by the TEPS administrator. The administrator specifies the
collection interval, collection location, and the warehouse interval. This workspace
contains the following views: Total Processed and Received - Last 24hrs This view
shows the total number of events received and processed by the Tivoli Enterprise
Console server since it was last started. The total number of events processed
includes events in both PROCESSED and PARSING_FAILED states. Total Queued,
Waiting, and Parse Failures - Last 24hrs This view shows the total number of events
in QUEUED state, the total number of events in WAITING state, and the total number
of events that could not be parsed. This data can help to identify performance
issues with the server or problems in the rule base. Arrival and Processing Rates
This view shows the event arrival rate and the event processing rate of the
monitored Tivoli Enterprise Console server. This data provides an overview of server
performance. Throughput in Sample Period - Last 24hrs This view shows the number
of events received and processed by the Tivoli Enterprise Console server during the
sample period. It also shows the number of parse failures during the sample period.
Average Throughput in Sample Period - Last 24hrs This view shows the total number
of events received and processed by the Tivoli Enterprise Console server since it
was last started, divided by the number of sample periods that have occurred. It
also shows the same average for waiting events. (A backlog of waiting events might
indicate server performance problems.).Event Throughput - Last 1 Week workspace
This workspace shows the same data shown in the real-time Event Throughput
workspace over a period of one week. This view can be used only if historical data
collection is enabled by the TEPS administrator. The administrator specifies the
collection interval, collection location, and the warehouse interval. This workspace
contains the following views: Total Processed and Received - Last 1 Week This view
shows the total number of events received and processed by the Tivoli Enterprise
Console server since it was last started. The total number of events processed
includes events in both PROCESSED and PARSING_FAILED states. Chapter 4.
Workspaces reference 21
Total Queued, Waiting, and Parse Failures - Last 1 Week This view shows the total
number of events in QUEUED state, the total number of events in WAITING state,
and the total number of events that could not be parsed. This data can help to
identify performance issues with the server or problems in the rule base. Arrival and
Processing Rates This view shows the event arrival rate and the event processing
rate of the monitored Tivoli Enterprise Console server. This data provides an
overview of server performance. Throughput in Sample Period - Last 1 Week This
view shows the number of events received and processed by the Tivoli Enterprise
Console server during the sample period. It also shows the number of parse failures
during the sample period. Average Throughput in Sample Period - Last 1 Week This
view shows the total number of events received and processed by the Tivoli
Enterprise Console server since it was last started, divided by the number of sample
periods that have occurred. It also shows the same average for waiting events. (A
backlog of waiting events might indicate server performance problems.).Event
Throughput - Last 1 Month workspace This workspace shows the same data shown
in the real-time Event Throughput workspace over a period of one month. This view
can be used only if historical data collection is enabled by the TEPS administrator.
The administrator specifies the collection interval, collection location, and the
warehouse interval. This workspace contains the following views: Total Processed
and Received - Last 1 Month This view shows the total number of events received
and processed by the Tivoli Enterprise Console server since it was last started. The
total number of events processed includes events in both PROCESSED and
PARSING_FAILED states. Total Queued, Waiting, and Parse Failures - Last 1 Month
This view shows the total number of events in QUEUED state, the total number of
events in WAITING state, and the total number of events that could not be parsed.
This data can help to identify performance issues with the server or problems in the
rule base. Arrival and Processing Rates This view shows the event arrival rate and
the event processing rate of the monitored Tivoli Enterprise Console server. This
data provides an overview of server performance. Throughput in Sample Period Last 1 Month This view shows the number of events received and processed by the
Tivoli Enterprise Console server during the sample period. It also shows the number
of parse failures during the sample period. Average Throughput in Sample Period Last 1 Month This view shows the total number of events received and processed by
the Tivoli Enterprise Console server since it was last started, divided by the number
of sample periods that have 22 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
occurred. It also shows the same average for waiting events. (A backlog of waiting
events might indicate server performance problems.).Event Throughput - Last 1
Year workspace This workspace shows the same data shown in the real-time Event
Throughput workspace over a period of one year. This view can be used only if
historical data collection is enabled by the TEPS administrator. The administrator
workspace contains the following views: Total Processed and Received - Last 1 Year
This view shows the total number of events received and processed by the Tivoli
Enterprise Console server since it was last started. The total number of events
processed includes events in both PROCESSED and PARSING_FAILED states. Total
Queued, Waiting, and Parse Failures - Last 1 Year This view shows the total number
of events in QUEUED state, the total number of events in WAITING state, and the
total number of events that could not be parsed. This data can help to identify
performance issues with the server or problems in the rule base. Arrival and
Processing Rates This view shows the event arrival rate and the event processing
rate of the monitored Tivoli Enterprise Console server. This data provides an
overview of server performance. Throughput in Sample Period - Last 1 Year This
view shows the number of events received and processed by the Tivoli Enterprise
Console server during the sample period. It also shows the number of parse failures
during the sample period. Average Throughput in Sample Period - Last 1 Year This
view shows the total number of events received and processed by the Tivoli
periods that have occurred. It also shows the same average for waiting events. (A
backlog of waiting events might indicate server performance problems.).
Chapter 4. Workspaces reference 23
Chapter 5. Attributes reference This chapter contains an overview of attributes,

references for detailed information about attributes, and descriptions of the
attributes for each attribute group included in this monitoring agent. About
attributes Attributes are the application properties being measured and reported by
IBM Tivoli Monitoring for Tivoli Enterprise Console. Attributes are organized into
groups according to their purpose. The attributes in a group can be used in the
following two ways: v Chart or table views Attributes are displayed in chart and
table views. The chart and table views use queries to specify which attribute values
to request from a monitoring agent. You use the Query editor to create a new query,
modify an existing query, or apply filters and set styles to define the content and
appearance of a view based on an existing query. v Situations You use attributes to
create situations that monitor the state of your operating system, database, or
application. A situation describes a condition you want to test. When you start a
situation, the Tivoli Enterprise Portal compares the values you have assigned to the
situation attributes with the values collected by IBM Tivoli Monitoring for Tivoli
Enterprise Console and registers an event if the condition is met. You are alerted to
events by indicator icons that are displayed in the Navigator.More information about
attributes For more information about using attributes and attribute groups, see IBM
Tivoli Monitoring Userfs 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, refer to the Attribute groups and attributes section in this chapter.
Attribute groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise Console
This monitoring agent contains the following attribute groups: v Availability v Event
Activity v Event Activity Base v Event Activity Class v Event Distribution v Event
Distribution Base v Event Distribution By Class v Event Distribution By Class Base c
Copyright IBM Corp. 2005, 2006 25
v Event Distribution By Host v Event Distribution By Host Base v Event Distribution
By Source v Event Distribution By Source Base v Event Distribution By Status v
Event Distribution By Status Base v Event Severity v Event Status v Event
Throughput v Performance Object StatusThe remaining sections of this chapter
contain descriptions of these attribute groups, which are listed alphabetically. The
following information is provided for each attribute group: Attributes List of
attributes that belong to the attribute group Historical group Whether the attribute
group is a historical type that you can roll off to a data warehouse Attribute
descriptions Description and type for each attribute in the attribute groupAvailability
attribute group This table contains the availability data for all processes and
services that make up this application. If the warehouse default setting is enabled,
data for this attribute group is stored in the warehouse. Historical group This
attribute group is part of the default historical group. Attribute descriptions The
following list contains information about each attribute in the Availability attribute
group: Node attribute - This attribute is a key attribute. Description The managed
system name of the agent. Type StringTimestamp attribute Description The local
time at the agent when the data was collected. Type StringApplication Component
attribute - This attribute is a key attribute. Description The descriptive name of a
part of the application. Type String

Name attribute Description The name of the process, service, or functionality test.
This name matches the executable name of the process, the service short name or
the name of the process used to test the application. Type StringStatus attribute
Description The status of the application component. v For processes fUPf,
fDOWNf, fWARNINGf, or fPROCESS_DATA_NOT_AVAILABLEf:
fPROCESS_DATA_NOT_AVAILABLEf is displayed for a process when the matching
process is running but the resource use information cannot be collected for that
process. v For services fUPf, fDOWNf, or fUNKNOWNf: fUNKNOWNf is
displayed when the service is not installed. v For functionality tests: fPASSEDf or
fFAILEDf is displayed.Type Integer with enumerated values. The strings are
displayed in the Tivoli Enterprise Portal. The warehouse and queries return the
numbers shown in parentheses. The values defined are: DOWN (0) UP (1) WARNING
(2) UNKNOWN (3) PASSED (4) FAILED (5) PROCESS_DATA_NOT_AVAILABLE (6) Any
other values will display the numeric value in the Tivoli Enterprise Portal.Full Name
attribute Description The full name of the process including the path. Type
StringType attribute Description The type of the application component.
Components are processes, services, or functionality tests. Type Integer with
enumerated values. The strings are displayed in the Tivoli Enterprise Portal. The
warehouse and queries return the numbers shown in parentheses. The values
defined are: PROCESS (0) SERVICE (1) FUNCTIONALITY_TEST (2) Any other values
will display the numeric value in the Tivoli Enterprise Portal.Virtual Size attribute
Description The virtual size (in MB) of the process. Type Integer (Gauge)Page Faults
per Sec attribute Description The rate of page faults for the process measured in
faults per second. This attribute only contains valid data for processes. Type Integer
(Gauge)Working Set Size attribute Chapter 5. Attributes reference 27
Description The working set size of the process in MB. This attribute only contains
valid data for processes. Type Integer (Gauge)Thread Count attribute Description
The number of threads currently allocated by this process. This attribute only
contains valid data for processes. Type Integer (Gauge)PID attribute Description The
process ID associated with the process. This attribute only contains valid data for
processes. Type Integer (Gauge)Percent Privileged Time attribute Description The
percentage of the available CPU time that is being used by this process for
privileged operation. Type Integer (Gauge)Percent User Mode Time attribute
Description The percentage of the available CPU time that is being used by this
process for user mode operation. Type Integer (Gauge)Percent Processor Time
attribute Description The percentage of the elapsed time that this process used the
processor to execute instructions. Type Integer (Gauge)Command Line attribute
Description The program name and any arguments specified on the command line
when the process was started. This has the value N/A if this is a Service, or
Functionality test. Type StringFunctionality Test Status attribute Description The
return code of the functionality test. When the monitored application is running
correctly, fSUCCESSf is displayed. fNOT_RUNNINGf is displayed when it is not
running correctly. fN/Af is displayed when the row does not represent a
functionality test. Type Integer with enumerated values. The strings are displayed in
the Tivoli Enterprise Portal. The warehouse and queries return the numbers shown
in parentheses. The values defined are: N/A (1) 28 IBM Tivoli Monitoring for Tivoli
Enterprise Console: Userfs Guide
SUCCESS (0) GENERAL_ERROR (2) WARNING (3) NOT_RUNNING (4)
DEPENDENT_NOT_RUNNING (5) ALREADY_RUNNING (6) PREREQ_NOT_RUNNING (7)
TIMED_OUT (8) DOESNT_EXIST (9) UNKNOWN (10) Any other values will display the
numeric value in the Tivoli Enterprise Portal.Functionality Test Message attribute
Description The text message that corresponds to the Functionality Test Status. This
is only valid for functionality tests. Type StringEvent Activity attribute group Event
activity by class and severity. If the warehouse default setting is enabled, data for
this attribute group is stored in the warehouse. Historical group This attribute group
is part of the default historical group. Attribute descriptions The following list
contains information about each attribute in the Event Activity attribute group: Node
attribute - This attribute is a key attribute. Description The managed system name
of the agent. Type StringTimestamp attribute Description The local time at the agent
when the data was collected. Type StringSeverity Code attribute - This attribute is a
key attribute. Description Event Severity Code Type DisplayNumericSeverity Text
attribute Description Event Severity text value Type StringSample Time attribute This attribute is a key attribute. Description Time when value was taken Type
TimestampTime Period attribute Chapter 5. Attributes reference 29
Description The actual time period for the sample in seconds Type
DisplayNumericEvent Class attribute - This attribute is a key attribute. Description
Event class Type StringSeverity attribute - This attribute is a key attribute.
Description Numeric severity value Type DisplayNumericTotal Time Rule attribute
Description Total time spent in the Tivoli Enterprise Console rule engine Type Integer
(Counter)Average Time Rule attribute Description Average time spent in the Tivoli
Enterprise Console rule engine Type Integer (Gauge)Number Events In attribute
Description Number of events for each event class and severity that were passed to
the Tivoli Enterprise Console rule engine Type Integer (Counter)Number Events Out
attribute Description Number of events for each event class and severity that were
output from the Tivoli Enterprise Console rule engine Type Integer (Counter)Event
Count Diff attribute Description The difference between the number of events of
each event class and severity entering and exiting the Tivoli Enterprise Console rule
engine Type Integer (Gauge)Number Tasks attribute Description The number of
tasks started for each event class and severity using the exec_task and
exec_program predicates. This number does not include tasks or programs started
using the exec_task_local and exec_program_local predicates. Type Integer
(Counter)
Event Activity Base attribute group Event Activity base. If the warehouse default
setting is enabled, data for this attribute group is not stored in the warehouse.
Historical group This attribute group is not part of the default historical group.
Attribute descriptions The following list contains information about each attribute in
the Event Activity Base attribute group: Node attribute - This attribute is a key
attribute. Description The managed system name of the agent. Type

StringTimestamp attribute Description The local time at the agent when the data
was collected. Type StringSample Time attribute - This attribute is a key attribute.
Description Time when value was taken Type TimestampTime Period attribute
Event class Type StringSeverity attribute - This attribute is a key attribute.
Description Numeric severity value Type DisplayNumericTotal Time Rule attribute
Description Total time spent in the Tivoli Enterprise Console rule engine Type Integer
(Counter)Average Time Rule attribute Description Average time spent in the Tivoli
Enterprise Console rule engine Chapter 5. Attributes reference 31
Type Integer (Gauge)Number Events In attribute Description Number of events for
each event class and severity that were passed to the Tivoli Enterprise Console rule
engine Type Integer (Counter)Number Events Out attribute Description Number of
events for each event class and severity that were output from the Tivoli Enterprise
Console rule engine Type Integer (Counter)Event Count Diff attribute Description
The difference between the number of events of each event class and severity
entering and exiting the Tivoli Enterprise Console rule engine Type Integer
(Gauge)Number Tasks attribute Description The number of tasks started for each
event class and severity using the exec_task and exec_program predicates. This
number does not include tasks or programs started using the exec_task_local and
exec_program_local predicates. Type Integer (Counter)Event Activity Class attribute
group Event activity by event class. If the warehouse default setting is enabled,
data for this attribute group is stored in the warehouse. Historical group This
attribute group is part of the default historical group. Attribute descriptions The
following list contains information about each attribute in the Event Activity Class
attribute group: Node attribute - This attribute is a key attribute. Description The
managed system name of the agent. Type StringTimestamp attribute Description
The local time at the agent when the data was collected. Type StringSample Time
attribute - This attribute is a key attribute. 32 IBM Tivoli Monitoring for Tivoli
Description Timestamp value was taken Type TimestampTime Period attribute
Event Class Type StringTotal Time Rule attribute Description Total time spent in the
Tivoli Enterprise Console rule engine Type Integer (Counter)Average Time Rule
attribute Description Average time spent in the Tivoli Enterprise Console rule engine
Type Integer (Gauge)Number Events In attribute Description Number of events for
each event class and severity passed to the Tivoli Enterprise Console rule engine
Type Integer (Counter)Number Events Out attribute Description Number of events
for each event class and severity exiting the Tivoli Enterprise Console rule engine
Type Integer (Counter)Event Count Diff attribute Description The difference between
the number of events of each event class and severity entering and exiting the
Tivoli Enterprise Console rule engine Type Integer (Gauge)Number Tasks attribute
Description The number of tasks started for each event class and severity using the
exec_task and exec_program predicates. This number does not include tasks or
programs started using the exec_task_local and exec_program_local predicates.
Type Integer (Counter)
Chapter 5. Attributes reference 33
Event Distribution attribute group Event distribution by status, class, severity, host,
and event source, including the string representation of the status value. If the
warehouse default setting is enabled, data for this attribute group is stored in the
warehouse. Historical group This attribute group is part of the default historical
group. Attribute descriptions The following list contains information about each
attribute in the Event Distribution attribute group: Node attribute - This attribute is a
key attribute. Description The managed system name of the agent. Type
was collected. Type StringStatus Code attribute - This attribute is a key attribute.
Description Event Status Code Type DisplayNumericStatus Text attribute Description
Event Status text value Type StringSample Time attribute - This attribute is a key
attribute. Description Time when data was queried from the Tivoli Enterprise
Console event repository Type TimestampStatus attribute - This attribute is a key
attribute. Description Numeric event status value Type DisplayNumericEvent Class
attribute - This attribute is a key attribute. Description Event Class Name Type
StringSeverity attribute - This attribute is a key attribute. 34 IBM Tivoli Monitoring
for Tivoli Enterprise Console: Userfs Guide
Description Numeric severity value Type DisplayNumericSeverity Text attribute
Description Severity text value Type StringHost Name attribute - This attribute is a
key attribute. Description Host name Type StringSource attribute - This attribute is a
key attribute. Description Event source Type StringTotal Events attribute Description
Total number of events for the status, event class, severity, host, and source Type
Integer (Counter)Event Distribution Base attribute group Event distribution by
status, class, severity, host, and event source. If the warehouse default setting is
enabled, data for this attribute group is not stored in the warehouse. Historical
group This attribute group is not part of the default historical group. Attribute
descriptions The following list contains information about each attribute in the Event
Distribution Base attribute group: Node attribute - This attribute is a key attribute.
Description The managed system name of the agent. Type StringTimestamp
attribute Description The local time at the agent when the data was collected. Type
StringSample Time attribute - This attribute is a key attribute. Chapter 5. Attributes
reference 35
Description Time when data was queried from the Tivoli Enterprise Console event
repository Type TimestampStatus attribute - This attribute is a key attribute.
Description Numeric event status value Type DisplayNumericEvent Class attribute This attribute is a key attribute. Description Event Class Name Type StringSeverity
attribute - This attribute is a key attribute. Description Numeric severity value Type
DisplayNumericSeverity Text attribute Description Severity text value Type
StringHost Name attribute - This attribute is a key attribute. Description Host name
Type StringSource attribute - This attribute is a key attribute. Description Event
source Type StringTotal Events attribute Description Total number of events for the
status, event class, severity, host, and source Type Integer (Counter)Event
Distribution By Class attribute group Event distribution by status and event class,
including the string representation of the status value. If the warehouse default
setting is enabled, data for this attribute group is stored in the warehouse. Historical
group This attribute group is part of the default historical group. 36 IBM Tivoli
the Event Distribution By Class attribute group: Node attribute - This attribute is a
key attribute. Description The managed system name of the agent. Type
StringFatal attribute Description Number of events for the status and event class
with FATAL severity value Type Integer (Counter)Critical attribute Description
Number of events for the status and event class with CRITICAL severity value Type
Integer (Counter)
Minor attribute Description Number of events for the status and event class with
MINOR severity value Type Integer (Counter)Warning attribute Description Number
of events for the status and event class with WARNING severity value Type Integer
(Counter)Harmless attribute Description Number of events for the status and event
class with HARMLESS severity value Type Integer (Counter)Unknown attribute
Description Number of events for the status and event class with UNKNOWN
severity value Type Integer (Counter)Custom attribute Description Number of events
for the status and event class with custom severity values Type Integer
(Counter)Total Events attribute Description Total number of events for the status
and event class Type Integer (Counter)Event Distribution By Class Base attribute
group Event distribution by status and event class. If the warehouse default setting
is enabled, data for this attribute group is not stored in the warehouse. Historical
group This attribute group is not part of the default historical group. Attribute
Distribution By Class Base attribute group: Node attribute - This attribute is a key
attribute. Description The managed system name of the agent. 38 IBM Tivoli
Type StringTimestamp attribute Description The local time at the agent when the
data was collected. Type StringSample Time attribute - This attribute is a key

StringFatal attribute Description Number of events for the status and event class
with FATAL severity value Type Integer (Counter)Critical attribute Description
Number of events for the status and event class with CRITICAL severity value Type
Integer (Counter)Minor attribute Description Number of events for the status and
event class with MINOR severity value Type Integer (Counter)Warning attribute
Description Number of events for the status and event class with WARNING severity
value Type Integer (Counter)Harmless attribute Description Number of events for
the status and event class with HARMLESS severity value Chapter 5. Attributes
reference 39
Type Integer (Counter)Unknown attribute Description Number of events for the
status and event class with UNKNOWN severity value Type Integer (Counter)Custom
attribute Description Number of events for the status and event class with custom
severity values Type Integer (Counter)Total Events attribute Description Total
number of events for the status and event class Type Integer (Counter)Event
Distribution By Host attribute group Event distribution by status and host name,
group This attribute group is part of the default historical group. Attribute
Distribution By Host attribute group: Node attribute - This attribute is a key
Event Status text value Type String
Sample Time attribute - This attribute is a key attribute. Description Time when data
was queried from the Tivoli Enterprise Console event repository Type
TimestampStatus attribute - This attribute is a key attribute. Description Numeric
event status value Type DisplayNumericHost Name attribute - This attribute is a key
attribute. Description Event Source Type StringFatal attribute Description Number of
events for the status and host name with FATAL severity value Type Integer
(Counter)Critical attribute Description Number of events for the status and host
name with CRITICAL severity value Type Integer (Counter)Minor attribute
Description Number of events for the status and host name with MINOR severity
value Type Integer (Counter)Warning attribute Description Number of events for the
status and host name with WARNING severity value Type Integer (Counter)Harmless
attribute Description Number of events for the status and host name with
HARMLESS severity value Type Integer (Counter)Unknown attribute Description
Number of events for the status and host name with UNKNOWN severity value Type
Integer (Counter)
Custom attribute Description Number of events for the status and host name with
custom severity values Type Integer (Counter)Total Events attribute Description
Total number of events for the status and host name Type Integer (Counter)Event
Distribution By Host Base attribute group Event Distribution by status and host
name. If the warehouse default setting is enabled, data for this attribute group is
not stored in the warehouse. Historical group This attribute group is not part of the
default historical group. Attribute descriptions The following list contains information
about each attribute in the Event Distribution By Host Base attribute group: Node
when the data was collected. Type StringSample Time attribute - This attribute is a
key attribute. Description Time when data was queried from the Tivoli Enterprise
attribute. Description Numeric event status value Type DisplayNumericHost Name
attribute - This attribute is a key attribute. Description Event Source Type StringFatal
attribute 42 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Description Number of events for the status and host name with FATAL severity
value Type Integer (Counter)Critical attribute Description Number of events for the
status and host name with CRITICAL severity value Type Integer (Counter)Minor
attribute Description Number of events for the status and host name with MINOR
severity value Type Integer (Counter)Warning attribute Description Number of
events for the status and host name with WARNING severity value Type Integer
(Counter)Harmless attribute Description Number of events for the status and host
name with HARMLESS severity value Type Integer (Counter)Unknown attribute
Description Number of events for the status and host name with UNKNOWN severity
value Type Integer (Counter)Custom attribute Description Number of events for the
status and host name with custom severity values Type Integer (Counter)Total
Events attribute Description Total number of events for the status and host name
Type Integer (Counter)Event Distribution By Source attribute group Event
distribution by status and event source, including the string representation of the
status value. If the warehouse default setting is enabled, data for this attribute
group is stored in the warehouse. Chapter 5. Attributes reference 43
Historical group This attribute group is part of the default historical group. Attribute
Distribution By Source attribute group: Node attribute - This attribute is a key
attribute. Description Numeric event status value Type DisplayNumericSource
attribute - This attribute is a key attribute. Description Event Source Type StringFatal
attribute Description Number of events for the status and event source with FATAL
severity value Type Integer (Counter)Critical attribute 44 IBM Tivoli Monitoring for
Tivoli Enterprise Console: Userfs Guide
Description Number of events for the status and event source with CRITICAL
severity value Type Integer (Counter)Minor attribute Description Number of events
for the status and event source with MINOR severity value Type Integer
(Counter)Warning attribute Description Number of events for the status and event
source with WARNING severity value Type Integer (Counter)Harmless attribute
Description Number of events for the status and event source with HARMLESS
severity value Type Integer (Counter)Unknown attribute Description Number of
events for the status and event source with UNKNOWN severity value Type Integer
(Counter)Custom attribute Description Number of events for the status and event
source with custom severity values Type Integer (Counter)Total Events attribute
Description Total number of events for the status and event source Type Integer
(Counter)Event Distribution By Source Base attribute group Event distribution by
status and event source. If the warehouse default setting is enabled, data for this
attribute group is not stored in the warehouse. Historical group This attribute group
is not part of the default historical group. Attribute descriptions The following list
contains information about each attribute in the Event Distribution By Source Base
attribute group: Chapter 5. Attributes reference 45
Node attribute - This attribute is a key attribute. Description The managed system
name of the agent. Type StringTimestamp attribute Description The local time at the
agent when the data was collected. Type StringSample Time attribute - This
attribute is a key attribute. Description Time when data was queried from the Tivoli
Enterprise Console event repository Type TimestampStatus attribute - This attribute
is a key attribute. Description Numeric event status value Type
DisplayNumericSource attribute - This attribute is a key attribute. Description Event
Source Type StringFatal attribute Description Number of events for the status and
event source with FATAL severity value Type Integer (Counter)Critical attribute
Description Number of events for the status and event source with CRITICAL
severity value Type Integer (Counter)Minor attribute Description Number of events
for the status and event source with MINOR severity value Type Integer
(Counter)Warning attribute Description Number of events for the status and event
source with WARNING severity value Type Integer (Counter)Harmless attribute 46
IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Description Number of events for the status and event source with HARMLESS
severity value Type Integer (Counter)Unknown attribute Description Number of
events for the status and event source with UNKNOWN severity value Type Integer
(Counter)Custom attribute Description Number of events for the status and event
source with custom severity values Type Integer (Counter)Total Events attribute
Description Total number of events for the status and event source Type Integer
(Counter)Event Distribution By Status attribute group Event distribution by status,
group This attribute group is part of the default historical group. Attribute
Distribution By Status attribute group: Node attribute - This attribute is a key

Description Event Status Code Type DisplayNumericStatus Text attribute Chapter 5.
Attributes reference 47
Description Event Status text value Type StringSample Time attribute - This
attribute is a key attribute. Description Time when data was queried from the Tivoli
Enterprise Console event repository Type TimestampStatus attribute - This attribute
is a key attribute. Description Numeric event status value Type DisplayNumericFatal
attribute Description Number of events for the status with FATAL severity value Type
Integer (Counter)Critical attribute Description Number of events for the status with
CRITICAL severity value Type Integer (Counter)Minor attribute Description Number
of events for the status with MINOR severity value Type Integer (Counter)Warning
attribute Description Number of events for the status with WARNING severity value
Type Integer (Counter)Harmless attribute Description Number of events for the
status with HARMLESS severity value Type Integer (Counter)Unknown attribute
Description Number of events for the status with UNKNOWN severity value Type
Integer (Counter)Custom attribute Description Number of events for the status with
custom severity values Type Integer (Counter)Total Events attribute 48 IBM Tivoli
Description Total number of events for the status Type Integer (Counter)Event
Distribution By Status Base attribute group Event distribution by status. If the
warehouse default setting is enabled, data for this attribute group is not stored in
the warehouse. Historical group This attribute group is not part of the default
historical group. Attribute descriptions The following list contains information about
each attribute in the Event Distribution By Status Base attribute group: Node
when the data was collected. Type StringSample Time attribute - This attribute is a
key attribute. Description Time when data was queried from the Tivoli Enterprise
attribute. Description Numeric event status value Type DisplayNumericFatal
attribute Description Number of events for the status with FATAL severity value Type
Integer (Counter)Critical attribute Description Number of events for the status with
CRITICAL severity value Type Integer (Counter)Minor attribute Description Number
of events for the status with MINOR severity value Chapter 5. Attributes reference
49
Type Integer (Counter)Warning attribute Description Number of events for the status
with WARNING severity value Type Integer (Counter)Harmless attribute Description
Number of events for the status with HARMLESS severity value Type Integer
(Counter)Unknown attribute Description Number of events for the status with
UNKNOWN severity value Type Integer (Counter)Custom attribute Description
Number of events for the status with custom severity values Type Integer
(Counter)Total Events attribute Description Total number of events for the status
Type Integer (Counter)Event Severity attribute group Event severity values. If the
warehouse default setting is enabled, data for this attribute group is not stored in
the warehouse. Historical group This attribute group is not part of the default
historical group. Attribute descriptions The following list contains information about
each attribute in the Event Severity attribute group: Node attribute - This attribute
is a key attribute. Description The managed system name of the agent. Type
was collected. Type StringSeverity Code attribute - This attribute is a key attribute.
Description Event Severity Code Type DisplayNumericSeverity Text attribute
Description Event Severity text value Type StringEvent Status attribute group Event
status values. If the warehouse default setting is enabled, data for this attribute
group is not stored in the warehouse. Historical group This attribute group is not
part of the default historical group. Attribute descriptions The following list contains
information about each attribute in the Event Status attribute group: Node attribute
- This attribute is a key attribute. Description The managed system name of the
agent. Type StringTimestamp attribute Description The local time at the agent when
the data was collected. Type StringStatus Code attribute - This attribute is a key
attribute. Description Event Status Code Type DisplayNumericStatus Text attribute
Description Event Status text value Type StringEvent Throughput attribute group
Event throughput. If the warehouse default setting is enabled, data for this attribute
group is stored in the warehouse. Historical group This attribute group is part of the
default historical group. Chapter 5. Attributes reference 51
the Event Throughput attribute group: Node attribute - This attribute is a key
was collected. Type StringSample Time attribute - This attribute is a key attribute.
Description Timestamp value was taken Type TimestampTime Period attribute
DisplayNumericReceived attribute Description Number of events received in the
time period Type Integer (Counter)Minimum Received attribute Description The
smallest number of events received during any sample period since the Tivoli
Enterprise Console server was started. Type Integer (Gauge)Maximum Received
attribute Description The largest number of events received during any sample
period since the Tivoli Enterprise Console server was started. Type Integer
(Gauge)Average Received attribute Description The total number of events received
by the Tivoli Enterprise Console server since it was last started, divided by the
number of sample periods that have occurred Type Integer (Gauge)Total Received
attribute 52 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Description The total number of events received since the Tivoli Enterprise Console
server was started. Type Integer (Gauge)Processed attribute Description Number of
events processed in the time period. This includes events in both PROCESSED and
PARSING_FAILED states. Type Integer (Counter)Minimum Processed attribute
Description The lowest number of events processed during any sample period since
the Tivoli Enterprise Console server was started. This includes events in both
PROCESSED and PARSING_FAILED states. Type Integer (Gauge)Maximum Processed
attribute Description The largest number of events processed during any sample
period since the Tivoli Enterprise Console server was started. This includes events in
both PROCESSED and PARSING_FAILED states. Type Integer (Gauge)Average
Processed attribute Description The total number of events processed by the Tivoli
periods that have occurred. This includes events in both PROCESSED and
PARSING_FAILED states. Type Integer (Gauge)Total Processed attribute Description
The total number of events processed since the Tivoli Enterprise Console server was
started. This includes events in both PROCESSED and PARSING_FAILED states. Type
Integer (Gauge)Minimum Waiting attribute Description The smallest number of
events that have been in the WAITING state during any sample period since the
Tivoli Enterprise Console server was started. Type Integer (Gauge)Maximum Waiting
attribute Description The largest number of events that have been in the WAITING
state during any sample period since the Tivoli Enterprise Console server was last
started. Chapter 5. Attributes reference 53
Type Integer (Gauge)Average Waiting attribute Description The total number of
events in the WAITING state, divided by the number of sample periods that have
occurred since the Tivoli Enterprise Console server was last started. Type Integer
(Gauge)Total Waiting attribute Description The total number of events in WAITING
state. Type Integer (Gauge)Arrival Rate attribute Description The number of events
that have been received during the sample period divided by the length (in
seconds) of the sample period. Type Integer (Gauge)Minimum Arrival Rate attribute
Description The lowest arrival rate reported during any sample period since the
Tivoli Enterprise Console server was last started. Type Integer (Gauge)Maximum
Arrival Rate attribute Description The highest arrival rate reported during any
sample period since the Tivoli Enterprise Console server was last started. Type
Integer (Gauge)Average Arrival Rate attribute Description The sum of the arrival
rates for all sample periods since the Tivoli Enterprise Console server was last
started, divided by the number of sample periods that have occurred. Type Integer
(Gauge)Processing Rate attribute Description The number of events that have been
processed during the sample period divided by the length (in seconds) of the
sample period. This includes events in both PROCESSED and PARSING_FAILED
states. Type Integer (Gauge)Minimum Processing Rate attribute Description The
lowest processing rate reported during any sample period since the Tivoli Enterprise
Console server was last started. This includes events in both PROCESSED and
PARSING_FAILED states. 54 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
Type Integer (Gauge)Maximum Processing Rate attribute Description The highest
processing rate reported during any sample period since the Tivoli Enterprise
Console server was last started. This includes events in both PROCESSED and
PARSING_FAILED states. Type Integer (Gauge)Average Processing Rate attribute
Description The sum of the processing rates for all sample periods since the Tivoli
Enterprise Console server was last started, divided by the number of sample periods
that have occurred. This includes events in both PROCESSED and PARSING_FAILED
states. Type Integer (Gauge)Queued attribute Description The number of events in
the QUEUED state during the sample period. Type Integer (Gauge)Minimum Queued
attribute Description The lowest number of events in the QUEUED state during any
Integer (Gauge)Maximum Queued attribute Description The highest number of
events in the QUEUED state during any sample period since the Tivoli Enterprise
Console server was last started. Type Integer (Gauge)Average Queued attribute
Description The sum of the queued event counts for all sample periods since the
Tivoli Enterprise Console server was last started, divided by the number of sample
periods that have occurred. Type Integer (Gauge)Parse Fail attribute Description The
number of events in the PARSING_FAILED state during the sample period. Type
Integer (Counter)Minimum Parse Fail attribute Chapter 5. Attributes reference 55
Description The lowest number of events in the PARSING_FAILED state during any
Integer (Gauge)Maximum Parse Fail attribute Description The highest number of
events in the PARSING_FAILED state during any sample period since the Tivoli
Enterprise Console server was last started. Type Integer (Gauge)Average Parse fail
attribute Description The Total Parse Fail event count divided by the number of
sample periods that have occurred since the Tivoli Enterprise Console server was
last started. Type Integer (Gauge)Total Parse Fail attribute Description The total
number of events that have been in PARSING_FAILED state since the Tivoli
Enterprise Console server was last started. Type Integer (Gauge)Performance Object
Status attribute group This table contains the status of the performance objects that
make up this application. If the warehouse default setting is enabled, data for this
attribute group is stored in the warehouse. Historical group This attribute group is
part of the default historical group. Attribute descriptions The following list contains
information about each attribute in the Performance Object Status attribute group:
Node attribute - This attribute is a key attribute. Description The managed system
name of the agent. Type StringTimestamp attribute Description The local time at the
agent when the data was collected. Type StringQuery Name attribute - This attribute
is a key attribute. 56 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
Description The name of the attribute group. Type StringObject Name attribute
Description The name of the performance object. Type StringObject Type attribute
Description The type of the performance object. Type Integer with enumerated
values. The strings are displayed in the Tivoli Enterprise Portal. The warehouse and
queries return the numbers shown in parentheses. The values defined are: WMI (0)
PERFMON (1) WMI_ASSOCIATION_GROUP (2) JMX (3) SNMP (4) SHELL_COMMAND (5)
JOINED_GROUPS (6) CIMOM (7) CUSTOM (8) ROLLUP_DATA (9) WMI_REMOTE_DATA
(10) LOG_FILE (11) Any other values will display the numeric value in the Tivoli
Enterprise Portal.Object Status attribute Description The status of the performance
object. Type Integer with enumerated values. The strings are displayed in the Tivoli
Enterprise Portal. The warehouse and queries return the numbers shown in
parentheses. The values defined are: ACTIVE (0) INACTIVE (1) Any other values will
display the numeric value in the Tivoli Enterprise Portal.Error Code attribute
Description The error code associated with the query Type Integer with enumerated
values. The strings are displayed in the Tivoli Enterprise Portal. The warehouse and
queries return the numbers shown in parentheses. The values defined are:
NO_ERROR (0) GENERAL_ERROR (1) OBJECT_NOT_FOUND (2) COUNTER_NOT_FOUND
(3) NAMESPACE_ERROR (4) OBJECT_CURRENTLY_UNAVAILABLE (5)
COM_LIBRARY_INIT_FAILURE (6) SECURITY_INIT_FAILURE (7) NOT_USED (8)
PROXY_SECURITY_FAILURE (9) NO_INSTANCES_RETURNED (10)
ASSOCIATOR_QUERY_FAILED (11) REFERENCE_QUERY_FAILED (12)
NO_RESPONSE_RECEIVED (13) CANNOT_FIND_JOINED_QUERY (14)
CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_1_RESULTS (15)
CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_2_RESULTS (16)
QUERY_1_NOT_A_SINGLETON (17) QUERY_2_NOT_A_SINGLETON (18)
NO_INSTANCES_RETURNED_IN_QUERY_1 (19)
NO_INSTANCES_RETURNED_IN_QUERY_2 (20) NO_INSTANCES_RETURNED (21)
CANNOT_FIND_ROLLUP_ATTRIBUTE (22) FILE_OFFLINE (23) Any other values will
display the numeric value in the Tivoli Enterprise Portal.Disk capacity planning for
historical data Disk capacity planning for a monitoring agent is a prediction of the
amount of disk space to be consumed for each attribute group whose historical data
is being collected. Required disk storage is an important factor to consider when
you are defining data collection rules and your strategy for historical data collection.
The tables in this appendix provide the following information required to calculate
disk space for the IBM Tivoli Monitoring, V5.1.2 component software: v Table is the
table name as it would appear in the warehouse database, if the attribute group is
configured to be written to the warehouse. v Attribute group is the name of the
attribute group as it will appear in the warehouse configuration panel . v Bytes per
instance (agent) is an estimate of the record length for each row or instance written
to the agent disk for historical data collection. This estimate can be used for agent
disk space planning purposes. v Database bytes per instance (warehouse) is an
estimate of the record length for detailed records written to the warehouse
database, if the attribute group is configured to be written to the warehouse.
Detailed records are those that have been uploaded from the agent for long-term
historical data collection. This estimate can be used for warehouse disk space
planning purposes. v Aggregate bytes per instance (warehouse) is an estimate of
the record length for aggregate records written to the warehouse database, if the
attribute group is configured to be written to the warehouse. Aggregate records are
created by the Summarization agent for attribute groups that have been configured
for summarization. This estimate can be used for warehouse disk space planning
purposes.In addition to the information in the tables, you must know the number of
instances of data that you plan to collect. An attribute group can have single or
multiple instances of data depending on the application environment that is being
monitored. For example, if your attribute group is monitoring each processor in your
computer and you have a dual processor computer, the number of instances is 2.
The following table contains capacity planning information for the data logged by
the Tec Health Agent component software.
Table 7. Capacity planning for historical data logged by component Tec Health Agent
Table
Attribute group
Bytes per instance (agent)
Database bytes per instance (warehouse)
Aggregate bytes per instance (warehouse)
KKAAVAIL
KKA_AVAILABILITY
3272
3296
3645
KKAECOACTF
KKA_EVENT_ACTIVITY
447
455
630
KKAECOACTC
KKA_EVENT_ACTIVITY_CLASS
184
189
364
KKAECOEDFL
KKA_EVENT_DISTRIBUTION
1065
1071
1123
KKAECOEDCF
KKA_EVENT_DISTRIBUTION_BY_CLASS
451
460
617
KKAECOEDHF
KKA_EVENT_DISTRIBUTION_BY_HOST
642
651
808 58 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Table 7. Capacity planning for historical data logged by component Tec Health Agent
(continued)
Table
Attribute group
Bytes per instance (agent)
Database bytes per instance (warehouse)
Aggregate bytes per instance (warehouse)
KKAECOEDRF
KKA_EVENT_DISTRIBUTION_BY_SOURCE
515
524
681
KKAECOEDSF
KKA_EVENT_DISTRIBUTION_BY_STATUS
387
395
552
KKAECOTHRU
KKA_EVENT_THROUGHPUT
220
249
1423
KKAPOBJST
KKA_PERFORMANCE_OBJECT_STATUS
288
289
326 To enable the historical views for the Tivoli Enterprise Console monitoring
agent, you must enable historical data collection for the following attribute groups:
v KKA_EVENT_ACTIVITY_CLASS (for event activity workspaces such as Event Activity
By Class - Last 24hrs) v KKA_EVENT_THROUGHPUT (for event throughput
workspaces such as Event Throughput - Last 24hrs)For more information about
historical data collection, see the IBM Tivoli Monitoring Administratorfs Guide.
Chapter 6. Situations reference This chapter contains an overview of situations,
references for detailed information about situations, and descriptions of the
predefined situations included in this monitoring agent. About situations A situation
is a logical expression involving one or more system conditions. Situations are used
to monitor the condition of systems in your network. You can manage situations
from Tivoli Enterprise Portal by using the Situation editor. The monitoring agents
that you use to monitor your system environment are delivered with a set of
predefined situations that you can use as-is or you can create new situations to
meet your requirements. Predefined situations contain attributes that check for
system conditions common to many enterprises. Using predefined situations can
improve the speed with which you can begin using the IBM Tivoli Monitoring for
Tivoli Enterprise Console. You can examine and, if necessary, change the conditions
or values being monitored by a predefined situation to those best suited to your
enterprise. You can display predefined situations and create your own situations
using the Situation editor. The left frame of the Situation editor initially lists the
situations associated with the Navigator item that you selected. When you click a
situation name or create a new situation, the right frame opens with the following
tabs: Formula Formula describing condition being tested Distribution List of
managed systems (operating systems, subsystems, or applications) to which the
situation can be distributed. All of the IBM Tivoli Monitoring for Tivoli Enterprise
Console managed systems are assigned by default. Expert advice Comments and
instructions to be read in the event workspace Action Command to be sent to the
system Util Options to close the event after a period of time, or when another
situation becomes trueMore information about situations IBM Tivoli Monitoring
Userfs Guide contains more information about predefined and custom situations
and how to use them to respond to alerts. For a list of the predefined situations for
this monitoring agent and a description of each situation, refer to the Predefined
situations section below and the information in that section for each individual
situation. c Copyright IBM Corp. 2005, 2006 61
Predefined situations This monitoring agent contains the following predefined
situations, which are organized by Navigator item: v Tivoli Enterprise Console . Not
applicablev Availability . KKA_Process_Data_Unavailable .
KKA_TEC_Reception_Proc_Down . KKA_TEC_UI_Srvr_Proc_Down .
KKA_TEC_Dispatch_Proc_Down . KKA_TEC_Rule_Proc_Down .
KKA_TEC_Server_Proc_Down . KKA_TEC_Task_Proc_Down .
KKA_TEC_Receptn_Proc_CPU_High . KKA_TEC_Receptn_Proc_CPU_Crit .
KKA_TEC_UI_Srvr_Proc_CPU_High . KKA_TEC_UI_Srvr_Proc_CPU_Crit .
KKA_TEC_Dispatch_Proc_CPU_High . KKA_TEC_Dispatch_Proc_CPU_Crit .
KKA_TEC_Rule_Proc_CPU_High . KKA_TEC_Rule_Proc_CPU_Crit .
KKA_TEC_Server_Proc_CPU_High . KKA_TEC_Server_Proc_CPU_Crit .
KKA_TEC_Task_Proc_CPU_High . KKA_TEC_Task_Proc_CPU_Critv Event Activity . Not
applicablev Event Distribution . KKA_TEC_Events_Count_High .
KKA_TEC_Fatal_Events_Ct_Highv Event Throughput .
KKA_TEC_Event_Arriv_Rate_Crit . KKA_TEC_Queued_Crit .
KKA_TEC_Waiting_Events_High . KKA_TEC_Parse_FailuresThe remaining sections of
this chapter contain descriptions of each of these situations. The situations are
organized by Navigator item. The following information is provided about each
situation: Description Information about the conditions that the situation tests
Formula Syntax that contains one or more logical expressions describing the
conditions for the situation to monitor 62 IBM Tivoli Monitoring for Tivoli Enterprise
Run at startup Whether the situation is automatically distributed to instances of the
agent or is available for manual distribution. Sampling interval Number of seconds
that elapses between one sample of data that the monitoring agent collects for the
server and the next sample Situation persistence Whether the conditions specified
in the situation evaluate to true for the defined number of occurrences in a row
before the situation is raised. The default of 1 means no persistence checking takes
place. Severity Severity of the event: Warning, Informational, or Critical Clearing
conditions Controls when a true situation closes: after a period of time, when
another situation is true, or whichever occurs first if both are selected.Tivoli
Enterprise Console Navigator item There are no predefined situations for this
Navigator item. Availability Navigator item KKA_Process_Data_Unavailable situation
Description Unable to gather process data for this process. Formula *IF *VALUE
KKA_AVAILABILITY.Type *EQ PROCESS *AND *VALUE KKA_AVAILABILITY.Status *EQ
PROCESS_DATA_NOT_AVAILABLE See gAttribute groups and attributes for IBM Tivoli
Monitoring for Tivoli Enterprise Consoleh on page 25 for descriptions of the
attributes in this formula. Run at startup This situation is automatically distributed
to instances of this agent. Sampling interval 1 minute Situation persistence The
number of times the conditions of the situation must occur for the situation to be
true is 3. Severity Informational Clearing conditions The situation clears when the
condition becomes false. Chapter 6. Situations reference 63
KKA_TEC_Reception_Proc_Down situation Description Tivoli Enterprise Console
reception process is not running. Formula *IF *SCAN KKA_AVAILABILITY.Name *EQ
ftec_receptionf *AND *VALUE KKA_AVAILABILITY.Status *EQ DOWN See gAttribute
groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise Consoleh on
page 25 for descriptions of the attributes in this formula. Run at startup This
situation is available for distribution. Sampling interval 15 minutes Situation
persistence The number of times the conditions of the situation must occur for the
situation to be true is 1. Severity Warning Clearing conditions The situation clears
when the condition becomes false. KKA_TEC_UI_Srvr_Proc_Down situation

Description Tivoli Enterprise Console UI server process is not running. Formula *IF
*SCAN KKA_AVAILABILITY.Name *EQ ftec_ui_serverf *AND *VALUE
KKA_AVAILABILITY.Status *EQ DOWN See gAttribute groups and attributes for IBM
Tivoli Monitoring for Tivoli Enterprise Consoleh on page 25 for descriptions of the
attributes in this formula. Run at startup This situation is available for distribution.
Sampling interval 15 minutes Situation persistence The number of times the
conditions of the situation must occur for the situation to be true is 1. Severity
Warning Clearing conditions The situation clears when the condition becomes false.
KKA_TEC_Dispatch_Proc_Down situation Description Tivoli Enterprise Console
dispatch process is not running. Formula *IF *SCAN KKA_AVAILABILITY.Name *EQ
ftec_dispatchf *AND *VALUE KKA_AVAILABILITY.Status *EQ DOWN See gAttribute
situation to be true is 1. Severity Warning Clearing conditions The situation clears
when the condition becomes false. KKA_TEC_Rule_Proc_Down situation Description
Tivoli Enterprise Console rule process is not running. Formula *IF *SCAN
KKA_AVAILABILITY.Name *EQ ftec_rulef *AND *VALUE KKA_AVAILABILITY.Status *EQ
DOWN See gAttribute groups and attributes for IBM Tivoli Monitoring for Tivoli
Enterprise Consoleh on page 25 for descriptions of the attributes in this formula.
Run at startup This situation is available for distribution. Sampling interval 15
minutes Situation persistence The number of times the conditions of the situation
must occur for the situation to be true is 1. Severity Warning Clearing conditions
The situation clears when the condition becomes false. Chapter 6. Situations
reference 65
KKA_TEC_Server_Proc_Down situation Description Tivoli Enterprise Console server
process is not running. Formula *IF *SCAN KKA_AVAILABILITY.Name *EQ
ftec_serverf *AND *VALUE KKA_AVAILABILITY.Status *EQ DOWN See gAttribute
situation to be true is 1. Severity Critical Clearing conditions The situation clears
when the condition becomes false. KKA_TEC_Task_Proc_Down situation Description
Tivoli Enterprise Console task process is not running. Formula *IF *SCAN
KKA_AVAILABILITY.Name *EQ ftec_taskf *AND *VALUE KKA_AVAILABILITY.Status
*EQ DOWN See gAttribute groups and attributes for IBM Tivoli Monitoring for Tivoli
Enterprise Consoleh on page 25 for descriptions of the attributes in this formula.
Run at startup This situation is available for distribution. Sampling interval 15
minutes Situation persistence The number of times the conditions of the situation
The situation clears when the condition becomes false. 66 IBM Tivoli Monitoring for
KKA_TEC_Receptn_Proc_CPU_High situation Description CPU usage of the TEC
reception process is high. Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ
ftec_receptionf ) *AND ( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
KKA_AVAILABILITY.Percent_Processor_Time *LT 80 ) *AND ( *VALUE
KKA_AVAILABILITY.Percent_Processor_Time *GE 20 ) ) See gAttribute groups and
attributes for IBM Tivoli Monitoring for Tivoli Enterprise Consoleh on page 25 for
descriptions of the attributes in this formula. Run at startup This situation is
automatically distributed to instances of this agent. Sampling interval 15 minutes
Situation persistence The number of times the conditions of the situation must
occur for the situation to be true is 1. Severity Warning Clearing conditions The
situation clears when the condition becomes false. KKA_TEC_Receptn_Proc_CPU_Crit
situation Description CPU usage of the TEC reception process is critically high.
Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_receptionf ) *AND
( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
occur for the situation to be true is 1. Severity Critical Chapter 6. Situations
reference 67
Clearing conditions The situation clears when the condition becomes false.
KKA_TEC_UI_Srvr_Proc_CPU_High situation Description CPU usage of the TEC UI
server process is high. Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ
ftec_ui_serverf ) *AND ( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
situation clears when the condition becomes false. KKA_TEC_UI_Srvr_Proc_CPU_Crit
situation Description CPU usage of the TEC UI server process is critically high.
Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_ui_serverf ) *AND
( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
occur for the situation to be true is 1. 68 IBM Tivoli Monitoring for Tivoli Enterprise
Severity Critical Clearing conditions The situation clears when the condition
becomes false. KKA_TEC_Dispatch_Proc_CPU_High situation Description CPU usage
of the TEC dispatch process is high. Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name
*EQ ftec_dispatchf ) *AND ( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND
( *VALUE KKA_AVAILABILITY.Percent_Processor_Time *LT 80 ) *AND ( *VALUE
situation clears when the condition becomes false. KKA_TEC_Dispatch_Proc_CPU_Crit
situation Description CPU usage of the TEC dispatch process is critically high.
Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_dispatchf ) *AND ( *VALUE
KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
Chapter 6. Situations reference 69
occur for the situation to be true is 1. Severity Critical Clearing conditions The
situation clears when the condition becomes false. KKA_TEC_Rule_Proc_CPU_High
situation Description CPU usage of the TEC rule process is high. Formula *IF
( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_rulef ) *AND ( *VALUE
situation clears when the condition becomes false. KKA_TEC_Rule_Proc_CPU_Crit
situation Description CPU usage of the TEC rule process is critically high. Formula *IF
( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_rulef ) *AND ( *VALUE
automatically distributed to instances of this agent. 70 IBM Tivoli Monitoring for
Critical Clearing conditions The situation clears when the condition becomes false.
KKA_TEC_Server_Proc_CPU_High situation Description CPU usage of the TEC server

process is high. Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_serverf )
*AND ( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
situation clears when the condition becomes false. KKA_TEC_Server_Proc_CPU_Crit
situation Description CPU usage of the TEC server process is critically high. Formula
*IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_serverf ) *AND ( *VALUE
descriptions of the attributes in this formula. Chapter 6. Situations reference 71
Run at startup This situation is automatically distributed to instances of this agent.
KKA_TEC_Task_Proc_CPU_High situation Description CPU usage of the TEC task
process is high. Formula *IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_taskf )
*AND ( *VALUE KKA_AVAILABILITY.Status *EQ UP ) *AND ( *VALUE
situation clears when the condition becomes false. KKA_TEC_Task_Proc_CPU_Crit
situation Description CPU usage of the TEC task process is critically high. Formula
*IF ( ( *SCAN KKA_AVAILABILITY.Name *EQ ftec_taskf ) *AND ( *VALUE
KKA_AVAILABILITY.Percent_Processor_Time *GE 80 ) ) 72 IBM Tivoli Monitoring for
See gAttribute groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise
Consoleh on page 25 for descriptions of the attributes in this formula. Run at
startup This situation is automatically distributed to instances of this agent.
Event Activity Navigator item There are no predefined situations for this Navigator
item. Event Distribution Navigator item KKA_TEC_Events_Count_High situation
Description The number of events in the event repository is high. Formula *IF *SUM
KKA_EVENT_DISTRIBUTION_BY_STATUS_BASE.Total_Events *GT 15000 See
gAttribute groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise
startup This situation is available for distribution. Sampling interval 15 minutes
situation clears when the condition becomes false. KKA_TEC_Fatal_Events_Ct_High
situation Description The number of open events with FATAL severity is high.
Chapter 6. Situations reference 73
Formula *IF ( (*VALUE KKA_EVENT_DISTRIBUTION_BY_STATUS_BASE.Fatal *GT 2000
*AND *VALUE KKA_EVENT_DISTRIBUTION_BY_STATUS_BASE.Status *EQ 0) ) See
gAttribute groups and attributes for IBM Tivoli Monitoring for Tivoli Enterprise
startup This situation is available for distribution. Sampling interval 15 minutes
occur for the situation to be true is 1. Severity Critical Clearing conditions The
situation clears when the condition becomes false. Event Throughput Navigator item
KKA_TEC_Event_Arriv_Rate_Crit situation Description The Event Arrival rate is
unusually high. Formula *IF *VALUE KKA_EVENT_THROUGHPUT.Arrival_Rate *GT 100
startup This situation is available for distribution. Sampling interval None. Data is
analyzed when it becomes available. Situation persistence The number of times the
Critical Clearing conditions The situation does not clear. KKA_TEC_Queued_Crit
situation Description The number of events in QUEUED state is high. 74 IBM Tivoli
Formula *IF *VALUE KKA_EVENT_THROUGHPUT.Queued *GT 5000 See gAttribute
situation is available for distribution. Sampling interval None. Data is analyzed when
it becomes available. Situation persistence The number of times the conditions of
the situation must occur for the situation to be true is 1. Severity Critical Clearing
conditions The situation does not clear. KKA_TEC_Waiting_Events_High situation
Description The number of events in WAITING state is high. Formula *IF *VALUE
KKA_EVENT_THROUGHPUT.Total_Waiting *GT 1000 See gAttribute groups and
available for distribution. Sampling interval None. Data is analyzed when it becomes
available. Situation persistence The number of times the conditions of the situation
The situation does not clear. KKA_TEC_Parse_Failures situation Description The Tivoli
Enterprise Console received events it could not parse Formula *IF *VALUE
KKA_EVENT_THROUGHPUT.Parse_Fail *GE 1 Chapter 6. Situations reference 75
startup This situation is available for distribution. Sampling interval None. Data is
analyzed when it becomes available. Situation persistence The number of times the
Critical Clearing conditions The situation does not clear. 76 IBM Tivoli Monitoring for
Chapter 7. Take Action commands reference This chapter contains an overview of
Take Action commands, references for detailed information about Take Action
commands, and descriptions of the Take Action commands included in this
monitoring agent, if any. About Take Action commands Take Action commands can
be run from the desktop or included in a situation or a policy. When included in a
situation, the command runs when the situation becomes true. A Take Action
command in a situation is also referred to as reflex automation. When you enable a
Take Action command in a situation, you automate a response to system conditions.
For example, you can use a Take Action command to send a command to restart a
process on the managed system or to send a text message to a cell phone.
Advanced automation uses policies to perform actions, schedule work, and
automate manual tasks. A policy comprises a series of automated steps called
activities that are connected to create a workflow. After an activity is completed,
Tivoli Enterprise Portal receives return code feedback, and advanced automation
logic responds with subsequent activities prescribed by the feedback. A basic Take
Action command displays the return code of the operation in a message box that is
displayed after the action completes. After you close this window, no further
information is available for this action. More information about Take Action
commands For more information about working with Take Action commands, see
IBM Tivoli Monitoring Userfs Guide. For a list of the Take Action commands for this
monitoring agent and a description of each command, refer to the Predefined Take
Action commands section below and the information in that section for each
individual command. Predefined Take Action commands This monitoring agent
contains the following Take Action commands: v Purge Event Repository v Purge
Reception Log v Start TEC Server v Stop TEC ServerThe remaining sections of this
chapter contain descriptions of these Take Action commands, which are listed
alphabetically. The following information is provided about each Take Action
command: Description Which actions the command performs on the system to
which is it sent c Copyright IBM Corp. 2005, 2006 77
Arguments List of parameters, if any, for the Take Action command with a short
description and the default value (if any) for each one Return codes Information that
the Take Action command returnsPurge Event Repository action Description This
action purges the Tivoli Enterprise Console event repository using the specified
options. Arguments v Name: Records Description: A commit is performed after
deleting this number of events. Default: 100v Name: Seconds Description: Events
older than this value (in seconds) are deleted. Default: 0v Name: Class Description:
Events with this class name are deleted. Default: v Name: Severity Description:
Events with this severity are deleted. Specify the severity using all uppercase
letters. If you do not specify a severity value, all events with FATAL, CRITICAL,
MINOR, WARNING, HARMLESS, and UNKNOWN severity are deleted. Only one value
should be specified; if you specify more than one value, only the first is used.
Default: v Name: Status Description: Events with this status are deleted. Specify the
status using all uppercase letters. If you do not specify a status value, all events
with OPEN, CLOSED, RESPONSE, and ACK status are deleted. Only one value should
be specified; if you specify more than one value, only the first is used. Default: v
Name: DataWarehouse Description: If this option is set to TRUE (all uppercase),
events not yet processed by the data warehouse extract, transform, and load (ETL)
process are deleted. Default: Return codes Return Code: 0 Return Code Type: OK
Message ID: KKA0005I Message: The event repository was purged successfully.
Return Code: 2 Return Code Type: GENERAL_ERROR Message ID: KKA0006E
Message: Error purging event repository. 78 IBM Tivoli Monitoring for Tivoli
Return Code: 5 Return Code Type: DEPENDENT_NOT_RUNNING Message ID:
KKA0010E Message: Error while checking the Tivoli object dispatcher (oserv) status.
Return Code: 7 Return Code Type: PREREQ_NOT_RUNNING Message ID: KKA0009E
Message: Error sourcing the Tivoli environment on monitored system. Return Code:
8 Return Code Type: DOESNT_EXIST Message ID: KKA0011E Message: Error locating
wtdbclear command on monitored system. Purge Reception Log action Description
This action purges the Tivoli Enterprise Console reception log using the specified
options. Do not use this option while the event server is running. Arguments v
Name: Records Description: A commit is performed after deleting this number of
events. Default: 100v Name: Seconds Description: Events older than this value (in
seconds) are deleted. Default: 0v Name: Force Description: If this option is set to
TRUE (all uppercase), queued and waiting events from the reception log are
deleted. Default: Return codes Return Code: 0 Return Code Type: OK Message ID:
KKA0007I Message: The reception log was purged successfully. Return Code: 2
Return Code Type: GENERAL_ERROR Message ID: KKA0008E Message: Error purging
event reception log. Return Code: 5 Return Code Type: DEPENDENT_NOT_RUNNING
Message ID: KKA0010E Message: Error while checking the Tivoli object dispatcher
(oserv) status. Return Code: 7 Return Code Type: PREREQ_NOT_RUNNING
Chapter 7. Take Action commands reference 79
Message ID: KKA0009E Message: Error sourcing the Tivoli environment on
monitored system.
Return Code: 8 Return Code Type: DOESNT_EXIST Message ID: KKA0011E Message:
Error locating wtdbclear command on monitored system. Start TEC Server action
Description This action starts the Tivoli Enterprise Console server using the specified
options. Arguments v Name: Server Description: This is the name (in name registry
format) of the Tivoli Enterprise Console server to started. To specify a remote server,
use the format @EventServer#tmr, where tmr is the name of a Tivoli region. The
default server is the local event server. Default: Return codes Return Code: 0 Return
Code Type: OK Message ID: KKA0001I Message: The Tivoli Enterprise Console event
server was started successfully. Return Code: 2 Return Code Type: GENERAL_ERROR
Message ID: KKA0002E Message: Error starting Tivoli Enterprise Console event
server. Return Code: 5 Return Code Type: DEPENDENT_NOT_RUNNING Message ID:
KKA0010E Message: Error while checking the Tivoli object dispatcher (oserv) status.
Return Code: 6 Return Code Type: ALREADY_RUNNING Message ID: KKA0014E
Message: The Tivoli Enterprise Console event server is already running. Return
Code: 7 Return Code Type: PREREQ_NOT_RUNNING Message ID: KKA0009E Message:
Error sourcing the Tivoli environment on monitored system. Return Code: 8 Return
Code Type: DOESNT_EXIST 80 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
Message ID: KKA0012E Message: Error locating wstartesvr command on monitored
system.
Stop TEC Server action Description This action stops the Tivoli Enterprise Console
server using the specified options. Arguments v Name: Server Description: This is
the name (in name registry format) of the Tivoli Enterprise Console server to be
stopped. To specify a remote server, use the format @EventServer#tmr, where tmr
is the name of a Tivoli region. The default server is the local event server. Default:
Return codes Return Code: 0 Return Code Type: OK Message ID: KKA0003I Message:
The Tivoli Enterprise Console event server was stopped successfully. Return Code: 2
Return Code Type: GENERAL_ERROR Message ID: KKA0004E Message: Error stopping
Tivoli Enterprise Console event server. Return Code: 4 Return Code Type:
NOT_RUNNING Message ID: KKA0015E Message: The Tivoli Enterprise Console event
server is not running. Return Code: 5 Return Code Type: DEPENDENT_NOT_RUNNING
Message ID: KKA0010E Message: Error while checking the Tivoli object dispatcher
(oserv) status. Return Code: 7 Return Code Type: PREREQ_NOT_RUNNING Message
ID: KKA0009E Message: Error sourcing the Tivoli environment on monitored system.
Return Code: 8 Return Code Type: DOESNT_EXIST Message ID: KKA0013E Message:
Error locating wstopesvr command on monitored system. Chapter 7. Take Action
commands reference 81
Chapter 8. Policies reference This chapter contains an overview of policies,
references for detailed information about policies, and descriptions of the
predefined policies included in this monitoring agent, if any. About policies Policies
are an advanced automation technique for implementing more complex workflow
strategies than you can create through simple automation. A policy is a set of
automated system processes that can perform actions, schedule work for users, or
automate manual tasks. You use the Workflow Editor to design policies. You control
the order in which the policy executes a series of automated steps, which are also
called activities. Policies are connected to create a workflow. After an activity is
completed, Tivoli Enterprise Portal receives return code feedback and advanced
automation logic responds with subsequent activities prescribed by the feedback.
More information about policies This agent does not provide predefined policies. For
more information about working with policies, see the IBM Tivoli Monitoring Userfs
Guide. For information about using the Workflow Editor, see the IBM Tivoli
Monitoring Administratorfs Guide or the Tivoli Enterprise Portal online help. c

Copyright IBM Corp. 2005, 2006 83
Appendix A. IBM Tivoli Enterprise Console event mapping Each event class
corresponds to an attribute group in the IBM Tivoli Enterprise Console. For a
description of the event slots for each event class, see the list below. For more
information about mapping attribute groups to event classes, see the IBM Tivoli
Monitoring Administratorfs Guide. Generic event mapping provides useful event
class and attribute information for situations that do not have specific event
mapping defined. BAROC files are found on the Tivoli Enterprise Monitoring Server
in the installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows
systems and install_dir/tables/TEMS_hostname/TECLIB for Linux or UNIX systems).
IBM Tivoli Enterprise Console event synchronization provides a collection of readyto-use rule sets that you can deploy with minimal configuration. Be sure to install
IBM Tivoli Enterprise Console event synchronization to access the correct
Sentry.baroc, which is automatically included during base configuration of IBM Tivoli
Enterprise Console rules if you indicate that you want to use an existing rulebase.
See the IBM Tivoli Monitoring Installation and Setup Guide for details. Each of the
event classes is a child of KKA_Base and is defined in the kka.baroc file. The
KKA_Base event class can be used for generic rules processing for any event from
the IBM Tivoli Monitoring for Tivoli Enterprise Console. For events generated by
situations on the AVAILABILITY attribute group, Tivoli Enterprise Console events will
be sent using the ITM_KKA_AVAILABILITY class. This class contains the following
slots: v node: STRINGv timestamp: STRINGv application_component: STRINGv
name: STRINGv kka_status: INTEGERv kka_status_enum: STRINGv full_name:
STRINGv type: INTEGERv type_enum: STRINGv virtual_size: INTEGERv
page_faults_per_sec: INTEGERv working_set_size: INTEGERv thread_count:
INTEGERv pid: INTEGERv percent_privileged_time: INTEGERv
percent_user_mode_time: INTEGERv percent_processor_time: INTEGERv
command_line: STRINGv functionality_test_status: INTEGERv
functionality_test_status_enum: STRINGv functionality_test_message: STRING
c Copyright IBM Corp. 2005, 2006 85
For events generated by situations on the EVENT_ACTIVITY attribute group, Tivoli
Enterprise Console events will be sent using the ITM_KKA_EVENT_ACTIVITY class.
This class contains the following slots: v node: STRINGv timestamp: STRINGv
severity_code: STRINGv severity_text: STRINGv sample_time: STRINGv time_period:
STRINGv event_class: STRINGv kka_severity: STRINGv total_time_rule: INTEGERv
average_time_rule: INTEGERv number_events_in: INTEGERv number_events_out:
INTEGERv event_count_diff: INTEGERv number_tasks: INTEGERFor events generated
by situations on the EVENT_ACTIVITY_BASE attribute group, Tivoli Enterprise
Console events will be sent using the ITM_KKA_EVENT_ACTIVITY_BASE class. This
class contains the following slots: v node: STRINGv timestamp: STRINGv
sample_time: STRINGv time_period: STRINGv event_class: STRINGv kka_severity:
STRINGv total_time_rule: INTEGERv average_time_rule: INTEGERv
number_events_in: INTEGERv number_events_out: INTEGERv event_count_diff:

INTEGERv number_tasks: INTEGERFor events generated by situations on the
EVENT_ACTIVITY_CLASS attribute group, Tivoli Enterprise Console events will be
sent using the ITM_KKA_EVENT_ACTIVITY_CLASS class. This class contains the
following slots: v node: STRINGv timestamp: STRINGv sample_time: STRINGv
time_period: STRINGv event_class: STRINGv total_time_rule: INTEGERv
average_time_rule: INTEGERv number_events_in: INTEGERv number_events_out:
INTEGERv event_count_diff: INTEGER
v number_tasks: INTEGERFor events generated by situations on the
EVENT_DISTRIBUTION attribute group, Tivoli Enterprise Console events will be sent
using the ITM_KKA_EVENT_DISTRIBUTION class. This class contains the following
slots: v node: STRINGv timestamp: STRINGv status_code: STRINGv status_text:
STRINGv sample_time: STRINGv kka_status: STRINGv event_class: STRINGv
kka_severity: STRINGv severity_text: STRINGv host_name: STRINGv kka_source:
STRINGv total_events: INTEGERFor events generated by situations on the
EVENT_DISTRIBUTION_BASE attribute group, Tivoli Enterprise Console events will be
sent using the ITM_KKA_EVENT_DISTRIBUTION_BASE class. This class contains the
kka_status: STRINGv event_class: STRINGv kka_severity: STRINGv severity_text:
STRINGv host_name: STRINGv kka_source: STRINGv total_events: INTEGERFor
events generated by situations on the EVENT_DISTRIBUTION_BY_CLASS attribute
group, Tivoli Enterprise Console events will be sent using the
ITM_KKA_EVENT_DISTRIBUTION_BY_CLASS class. This class contains the following
STRINGv sample_time: STRINGv kka_status: STRINGv event_class: STRINGv fatal:
INTEGERv critical: INTEGERv minor: INTEGERv warning: INTEGER
Appendix A. IBM Tivoli Enterprise Console event mapping 87
v harmless: INTEGERv unknown: INTEGERv custom: INTEGERv total_events:
INTEGERFor events generated by situations on the
EVENT_DISTRIBUTION_BY_CLASS_BASE attribute group, Tivoli Enterprise Console
events will be sent using the ITM_KKA_EVENT_DISTRIBUTION_BY_CLASS_BASE class.
sample_time: STRINGv kka_status: STRINGv event_class: STRINGv fatal: INTEGERv
critical: INTEGERv minor: INTEGERv warning: INTEGERv harmless: INTEGERv
unknown: INTEGERv custom: INTEGERv total_events: INTEGERFor events generated
by situations on the EVENT_DISTRIBUTION_BY_HOST attribute group, Tivoli
Enterprise Console events will be sent using the
ITM_KKA_EVENT_DISTRIBUTION_BY_HOST class. This class contains the following
STRINGv sample_time: STRINGv kka_status: STRINGv host_name: STRINGv fatal:
INTEGERv critical: INTEGERv minor: INTEGERv warning: INTEGERv harmless:
INTEGERv unknown: INTEGERv custom: INTEGERv total_events: INTEGERFor events
generated by situations on the EVENT_DISTRIBUTION_BY_HOST_BASE attribute
group, Tivoli Enterprise 88 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
Console events will be sent using the
ITM_KKA_EVENT_DISTRIBUTION_BY_HOST_BASE class. This class contains the
kka_status: STRINGv host_name: STRINGv fatal: INTEGERv critical: INTEGERv minor:
INTEGERv warning: INTEGERv harmless: INTEGERv unknown: INTEGERv custom:
INTEGERv total_events: INTEGERFor events generated by situations on the
EVENT_DISTRIBUTION_BY_SOURCE attribute group, Tivoli Enterprise Console events
will be sent using the ITM_KKA_EVENT_DISTRIBUTION_BY_SOURCE class. This class
contains the following slots: v node: STRINGv timestamp: STRINGv status_code:
STRINGv status_text: STRINGv sample_time: STRINGv kka_status: STRINGv
kka_source: STRINGv fatal: INTEGERv critical: INTEGERv minor: INTEGERv warning:
INTEGERv harmless: INTEGERv unknown: INTEGERv custom: INTEGERv total_events:
INTEGERFor events generated by situations on the
EVENT_DISTRIBUTION_BY_SOURCE_BASE attribute group, Tivoli Enterprise Console
events will be sent using the ITM_KKA_EVENT_DISTRIBUTION_BY_SOURCE_BASE
class. This class contains the following slots: v node: STRINGv timestamp: STRINGv
sample_time: STRINGv kka_status: STRINGv kka_source: STRING
v fatal: INTEGERv critical: INTEGERv minor: INTEGERv warning: INTEGERv harmless:
INTEGERv unknown: INTEGERv custom: INTEGERv total_events: INTEGERFor events
generated by situations on the EVENT_DISTRIBUTION_BY_STATUS attribute group,
Tivoli Enterprise Console events will be sent using the
ITM_KKA_EVENT_DISTRIBUTION_BY_STATUS class. This class contains the following
STRINGv sample_time: STRINGv kka_status: STRINGv fatal: INTEGERv critical:
INTEGERv minor: INTEGERv warning: INTEGERv harmless: INTEGERv unknown:
INTEGERv custom: INTEGERv total_events: INTEGERFor events generated by
situations on the EVENT_DISTRIBUTION_BY_STATUS_BASE attribute group, Tivoli
Enterprise Console events will be sent using the
ITM_KKA_EVENT_DISTRIBUTION_BY_STATUS_BASE class. This class contains the
kka_status: STRINGv fatal: INTEGERv critical: INTEGERv minor: INTEGERv warning:
INTEGERv harmless: INTEGERv unknown: INTEGERv custom: INTEGERv total_events:
INTEGER
For events generated by situations on the EVENT_SEVERITY attribute group, Tivoli
Enterprise Console events will be sent using the ITM_KKA_EVENT_SEVERITY class.
severity_code: STRINGv severity_text: STRINGFor events generated by situations on
the EVENT_STATUS attribute group, Tivoli Enterprise Console events will be sent
using the ITM_KKA_EVENT_STATUS class. This class contains the following slots: v
node: STRINGv timestamp: STRINGv status_code: STRINGv status_text: STRINGFor
events generated by situations on the EVENT_THROUGHPUT attribute group, Tivoli

Enterprise Console events will be sent using the ITM_KKA_EVENT_THROUGHPUT
class. This class contains the following slots: v node: STRINGv timestamp: STRINGv
sample_time: STRINGv time_period: STRINGv received: INTEGERv
minimum_received: INTEGERv maximum_received: INTEGERv average_received:
INTEGERv total_received: INTEGERv processed: INTEGERv minimum_processed:
INTEGERv maximum_processed: INTEGERv average_processed: INTEGERv
total_processed: INTEGERv minimum_waiting: INTEGERv maximum_waiting:
INTEGERv average_waiting: INTEGERv total_waiting: INTEGERv arrival_rate:
INTEGERv minimum_arrival_rate: INTEGERv maximum_arrival_rate: INTEGERv
average_arrival_rate: INTEGERv processing_rate: INTEGERv
minimum_processing_rate: INTEGERv maximum_processing_rate: INTEGERv
average_processing_rate: INTEGERv queued: INTEGERv minimum_queued: INTEGER
v maximum_queued: INTEGERv average_queued: INTEGERv parse_fail: INTEGERv
minimum_parse_fail: INTEGERv maximum_parse_fail: INTEGERv average_parse_fail:
INTEGERv total_parse_fail: INTEGERFor events generated by situations on the
PERFORMANCE_OBJECT_STATUS attribute group, Tivoli Enterprise Console events
will be sent using the ITM_KKA_PERFORMANCE_OBJECT_STATUS class. This class
contains the following slots: v node: STRINGv timestamp: STRINGv query_name:
STRINGv object_name: STRINGv object_type: INTEGERv object_type_enum: STRINGv
object_status: INTEGERv object_status_enum: STRINGv error_code: INTEGERv
error_code_enum: STRING
Appendix B. Problem determination This appendix provides agent-specific problem
determination information. See the IBM Tivoli Monitoring Problem Determination
Guide for general problem determination information. Also see gSupport
informationh on page 111 for other problem-solving options.Note: You can resolve
some problems by ensuring that your system matches the system requirements
listed in Chapter 2, gRequirements for the monitoring agent,h on page 3.
Gathering product information for IBM Software Support Before contacting IBM
Software Support about a problem you are experiencing with this product, gather
the following information that relates to the problem:
Table 8. Information to gather before contacting IBM Software Support
Information type
Description
Log files
Collect trace log files from failing systems. Most logs are located in a logs
subdirectory on the host computer. See gTrace loggingh on page 94 for lists of all
trace log files and their locations. See the IBM Tivoli Monitoring Userfs Guide for
general information about the IBM Tivoli Monitoring environment.
Tivoli Enterprise Console information

v Version number and patch level
Operating system
Operating system version number and patch level
Messages
Messages and other information displayed on the screen
Version numbers for IBM Tivoli Monitoring
Version number of the following members of the monitoring environment: v IBM
Tivoli Monitoring. Also provide the patch level, if available. v IBM Tivoli Monitoring
for Tivoli Enterprise Console
Screen captures
Screen captures of incorrect output, if any.
(Linux and UNIX only) Core dump files
If the system stops on a Linux or UNIX system, collect the core dump file from
install_dir/bin directory, where install_dir is the directory oath where you installed
the monitoring agent. Upload files for review to the following FTP site:
ftp.emea.ibm.com. Log in as anonymous and place your files in the directory that
corresponds to the IBM Tivoli Monitoring component that you use. See gContacting
IBM Software Supporth on page 112 for more information about working with IBM
Software Support. Built-in problem determination features The primary
troubleshooting feature in the IBM Tivoli Monitoring for Tivoli Enterprise Console is
logging. Logging refers to the text messages and trace data generated by the IBM
Tivoli Monitoring for Tivoli Enterprise Console. Messages and trace data are sent to
a file. Trace data captures transient information about the current operating
environment when a component or application fails to operate as designed. IBM
Software Support personnel use the captured trace information to determine the
source of an error or unexpected condition. See gTrace loggingh on page 94 for
more information. c Copyright IBM Corp. 2005, 2006 93
Problem classification The following types of problems might occur with the IBM
Tivoli Monitoring for Tivoli Enterprise Console: v Installation and configuration v
General usage and operation v Display of monitoring data v Take Action
commandsThis appendix provides symptom descriptions and detailed workarounds
for these problems, as well as describing the logging capabilities of the monitoring
agent. See the IBM Tivoli Monitoring Problem Determination Guide for general
problem determination information. Trace logging Trace logs capture information
about the operating environment when component software fails to operate as
intended. The principal log type is the RAS (Reliability, Availability, and
Serviceability) trace log. These logs are in the English language only. The RAS trace
log mechanism is available for all components of IBM Tivoli Monitoring. Most logs
are located in a logs subdirectory on the host computer. See the following sections
to learn how to configure and use trace logging: v gPrincipal trace log filesh on
page 95 v gExamples: using trace logsh on page 98 v gSetting RAS trace
parametersh on page 99Note: The documentation refers to the RAS facility in IBM
Tivoli Monitoring as "RAS1". IBMR Software Support uses the information captured
by trace logging to trace a problem to its source or to determine why an error
occurred. The default configuration for trace logging, such as whether trace logging
is enabled or disabled and trace level, depends on the source of the trace logging.
Trace logging is always enabled. Overview of log file management Table 9 on page
96 provides the names, locations, and descriptions of RAS1 log files. The log file
names adhere to the following naming convention: Windows systems
hostname_productcode_program_HEXtimestamp-nn.log Linux and UNIX systems
hostname_productcode_HEXtimestamp-nn.log where: v hostname is the host name
of the machine on which the monitoring component is running. v productcode is the
two-character product code. For IBM Tivoli Monitoring for Tivoli Enterprise Console,
the product code is ka. v program is the name of the program being run. v
HEXtimestamp is a hexadecimal timestamp representing the time at which the
program started. 94 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
v nn is a rolling log suffix. See gExamples of trace loggingh for details of log
rolling.Examples of trace logging For example, if a Tivoli Enterprise Console
monitoring agent is running on the Windows system server01, the RAS log file
for the IBM Tivoli Monitoring for Tivoli Enterprise Console might be named as
follows: server01_ka_kkaagent_437fc59-01.log For long-running programs, the nn
suffix is used to maintain a short history of log files for that startup of the program.
For example, the kkaagent program might have a series of log files as follows:
server01_ka_kkaagent_437fc59-01.log server01_ka_kkaagent_437fc59-02.log
server01_ka_kkaagent_437fc59-03.log As the program runs, the first log (nn=01) is
preserved because it contains program startup information. The remaining logs
roll." In other words, when the set of numbered logs reach a maximum size, the
remaining logs are overwritten in sequence. Each time a program is started, a new
timestamp is assigned to maintain a short program history. For example, if the IBM
Tivoli Monitoring for Tivoli Enterprise Console is started twice, it might have log files
as follows: server01_ka_kkaagent_437fc59-01.log server01_ka_kkaagent_437fc5902.log server01_ka_kkaagent_437fc59-03.log server01_ka_kkaagent_537fc59-01.log
server01_ka_kkaagent_537fc59-02.log server01_ka_kkaagent_537fc59-03.log Each
program that is started has its own log file. For example, on a Windows system, the
IBM Tivoli Monitoring for Tivoli Enterprise Console would have agent logs in this
format: server01_ka_kkaagent_437fc59-01.log Other logs, such as logs for Take
Action command logs, have a similar syntax as in the following Windows example:
host_productcode_takeactioncommand.log Only one log file is produced per Take
Action command.Note: When you communicate with IBM Software Support, you
must capture and send the RAS1 log that matches any problem occurrence that you
report. Principal trace log files Table 9 on page 96 contains locations, file names,
and descriptions of trace logs that can help determine the source of problems with
agents. Appendix B. Problem determination 95
Table 9. Trace log files for troubleshooting agents

System where log is located
File name and path
Description
On the Tivoli Enterprise Monitoring Server
v On Windows: The file in the install_dir\InstallITM path. v On Linux or UNIX: The
candle_installation.log file in the install_dir/logs path.
Provides details about products that are installed. Note: Trace logging is enabled by
default. A configuration step is not required to enable this tracing.
The Warehouse_Configuration.log file is located as follows: v Windows:
install_dir\InstallITM v Linux and UNIX: install_dir/Install
Provides details about the configuration of data warehousing for historical reporting.
The name of the RAS log file is as follows: v On Windows:
install_dir\logs\hostname_productcode_HEXtimestamp-nn.log v On Linux or UNIX:
install_dir/logs/hostname_productcode_HEXtimestamp-nn.logNote: File names for
RAS1 logs include a hexadecimal time stamp. Also on Linux and UNIX, a log with a
decimal time stamp is provided: hostname_productcode_timestamp.log and
hostname_productcode_ timestamp.pidnnnnn in the install_dir/logs path, where
nnnnn is the process ID number.
Traces activity on the monitoring server.
On the Tivoli Enterprise Portal Server
The name of the RAS log file is as follows: v On Windows:
install_dir\logs\hostname_cq_HEXtimestamp-nn.log v On Linux or UNIX:
install_dir/logs/hostname_cq_HEXtimestamp-nn.logNote: File names for RAS1 logs
include a hexadecimal time stamp. Also on Linux and UNIX, a log with a decimal
time stamp is provided: hostname_productcode_timestamp.log and
hostname_productcode_ timestamp.pidnnnnn in the install_dir/logs path, where
nnnnn is the process ID number.
Traces activity on the portal server.
The teps_odbc.log file is located in the following path on
Windows:install_dir\InstallITM path. On Linux or UNIX, the file is located in the
following path: install_dir/logs
When you enable historical reporting, this log file traces the status of the warehouse
proxy agent. 96 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
Table 9. Trace log files for troubleshooting agents (continued)
System where log is located
File name and path

Description
On the computer that hosts the monitoring agent
The RAS1 log files are as follows: v On Windows:
hostname_ka_kkaagent_HEXtimestamp-nn.log in the install_dir\tmaitm6\logs
directory v On Linux or UNIX: hostname_ka_HEXtimestamp-nn.log in the
install_dir/logs directoryAlso on Linux and UNIX, a log with a decimal time stamp is
provided: hostname_productcode_timestamp.log and hostname_productcode_
timestamp.pidnnnnn in the install_dir/logs path, where nnnnn is the process ID
number.
Traces activity of the monitoring agent.
The *.LG0 file is located in the install_dir\tmaitm6\logs (Windows) or install_dir/logs
(Linux or UNIX) directory.
Shows whether agent was able to connect to the monitoring server. Shows which
situations are started and stopped, and shows other events while the agent is
running. A new version of this file is generated every time the agent is restarted.
IBM Tivoli Monitoring generates one backup copy of the *.LG0 file with the tag .LG1.
View .LG1 to learn the following details regarding the previous monitoring session: v
Status of connectivity with the monitoring server. v Situations that were running. v
The success or failure status of Take Action commands.
The log files are as follows: v On Windows: The
host_productcode_takeactioncommand.log file (where takeactioncommand is the
name of the Take Action command) is located in the install_dir\tmaitm6\logs
directory. v On Linux and UNIX: The takeactioncommand.log file (where
takeactioncommand is the name of the Take Action command) is located in the
install_dir/logs directory.
Traces activity each time a Take Action command runs. For example, when a
hypothetical start_command Take Action command runs, IBM Tivoli Monitoring
would generate a start_command.log file.
Definitions of variables: timestamp is time stamp whose format includes year (y),
month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm
HEXtimestamp is a hexadecimal representation of the time at which the process
was started. install_dir represents the directory path where you installed the IBM
Tivoli Monitoring component. install_dir can represent a path on the computer that
host the monitoring system, the monitoring agent, or the portal. instance refers to
the name of the database instance that you are monitoring. hostname refers to the
name of the computer on which the IBM Tivoli Monitoring component runs. nn
represents the circular sequence in which logs are rotated. Ranges from 1-5, by
default, though the first is always retained, since it includes configuration
parameters. productcode specifies the product codes, for example, um for Universal
Agent or nt for Windows. Appendix B. Problem determination 97
See the IBM Tivoli Monitoring Installation and Setup Guide for more information on
the complete set of trace logs that are maintained on the monitoring server.
Examples: using trace logs Typically IBM Software Support applies specialized
knowledge to analyze trace logs to determine the source of problems. However, you
can open trace logs in a text editor to learn some basic facts about your IBM Tivoli
Monitoring environment. The following examples are from the Tivoli Enterprise
Monitoring Server log. Example one This excerpt shows the typical log for a failed
connection between a monitoring agent and a monitoring server with the host name
server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup")
status=1c020006, "location server unavailable",
ncs/KDC1_STC_SERVER_UNAVAILABLE (Thursday, August 11, 2005, 08:21:35{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to broker at ip.pipe::
status=0, "success", ncs/KDC1_STC_OK (Thursday, August 11, 2005, 08:21:35{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable to find running CMS
on CT_CMSLIST <IP.PIPE:#server1a> Example two The following excerpts from the
trace log for the monitoring server show the status of an agent, identified here as
Remote node. The name of the computer where the agent is running is
SERVER5B: (42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote
node SERVER5B:KA is ON-LINE. . . . (42C3079B.00006A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:KA is OFF-LINE.
Key points regarding the preceding excerpt: v The monitoring server appends the
KA product code to the server name to form a unique name (SERVER5B:KA) for this
instance of IBM Tivoli Monitoring for Tivoli Enterprise Console. This unique name
enables you to distinguish multiple monitoring products that might be running on
SERVER5B. v The log shows when the agent started (ON-LINE) and later stopped
(OFF-LINE) in the environment. v For the sake of brevity an ellipsis (...) represents
the series of trace log entries that were generated while the agent was running. v
Between the ON-LINE and OFF-LINE log entries, the agent was communicating with
the monitoring server. v The ON-LINE and OFF-LINE log entries are always available
in the trace log. All trace levels that are described in gSetting RAS trace
parametersh on page 99 provide these entries.On Windows, you can use the
following alternate method to view trace logs: 1. In the Windows Start menu, choose
Program Files > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring
Services. The Manage Tivoli Enterprise Monitoring Services window is displayed. 2.
Right-click a component and select Advanced > View Trace Log in the pop-up menu.
For example, if you want to view the trace log of the Tivoli Enterprise Console agent,
right-click on the name of the that agent in the window. You can also use the viewer
to access remote logs.Note: The viewer converts time stamps in the logs to a format
that is easier to read.
Setting RAS trace parameters Objective Pinpoint a problem by setting detailed
tracing of individual components of the monitoring agent and modules. Background
Information The IBM Tivoli Monitoring for Tivoli Enterprise Console uses RAS1 tracing
and generates the logs described in Table 9 on page 96. The default RAS1 trace
level is ERROR. Before you begin See gOverview of log file managementh on
page 94 to ensure that you understand log rolling and can reference the correct log
files when you manage log file generation. After you finish Monitor the size of the
logs directory. Default behavior can generate a total of 45 to 60 MB for each agent
that is running on a computer. For example, each database instance that you
monitor could generate 45 to 60 MB of log data. See the "Procedure" section to
learn how to adjust file size and numbers of log files to prevent logging activity from
occupying too much disk space. Regularly prune log files other than the RAS1 log
files in the logs directory. Unlike the RAS1 log files which are pruned automatically,
other log types can grow indefinitely, for example, the logs in Table 9 on page 96
that include a process ID number (PID). Consider using collector trace logs as an
additional source of problem determination information. Note: The KDC_DEBUG
setting and the Maximum error tracing setting can generate a large amount of trace
logging. Use them only temporarily, while you are troubleshooting problems.
Otherwise, the logs can occupy excessive amounts of hard disk space. Procedure On
Windows systems, you can use the graphical user interface to set trace options: 1.
Open the Manage Tivoli Enterprise Monitoring Services window. 2. Right-click the
icon of the monitoring agent whose logging you want to modify. 3. Select Advanced
> Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters
window is displayed. 4. Select a new trace setting in the pull-down menu in the
Enter RAS1 Filters field or type a valid string. The selections are as follows: v
General error tracing. KBB_RAS1=ERROR v Intensive error tracing.
KBB_RAS1=ERROR (UNIT:kqz ALL) v Maximum error tracing. KBB_RAS1=ERROR
(UNIT:kqz ALL) (UNIT:kra ALL)Note: As this example shows, you can set multiple RAS
tracing options in a single statement.5. Modify the value for 'Maximum Log Size Per
File (MB)" to change the log file size (changes LIMIT value). Appendix B. Problem
determination 99
6. Modify the value for 'Maximum Number of Log Files Per Session" to change the
number of log files per startup of a program (changes COUNT value). 7. Modify the
value for 'Maximum Number of Log Files Total" to change the number of log files for
all startups of a program (changes MAXFILES value). 8. (Optional) Click Y (Yes) in the
KDC_DEBUG Setting menu to log information that can help you diagnose
communications and connectivity problems between the monitoring agent and the
monitoring server. Note: The KDC_DEBUG setting and the Maximum error tracing
setting can generate a large amount of trace logging. Use them only temporarily,
while you are troubleshooting problems. Otherwise, the logs can occupy excessive
amounts of hard disk space. 9. Click OK. You see a message reporting a restart of
the monitoring agent so that your changes take effect.You can also manually edit
the RAS1 trace logging parameters (use this method on Linux and UNIX systems): 1.
Open the trace options file: v Windows systems: install_dir\tmaitm6\KKAENV v Linux
and UNIX systems: install_dir/config/ka.ini2. Edit the line that begins with
KBB_RAS1= to set trace logging preferences. For example, if you want detailed
trace logging, set the Maximum Tracing option:KBB_RAS1=ERROR (UNIT:kqz ALL)
(UNIT:kra ALL) 3. Edit the line that begins with KBB_RAS1_LOG= to manage the
generation of log files: v MAXFILES: the total number of files that are to be kept for
all startups of a given program. Once this value is exceeded, the oldest log files are
discarded. Default value is 9. v LIMIT: the maximum size, in megabytes (MB) of a

RAS1 log file. Default value is 5. v IBM Software Support might guide you to modify
the following parameters: . COUNT: the number of log files to keep in the rolling
cycle of one program startup. Default is 3. . PRESERVE: the number of files that are
not to be reused in the rolling cycle of one program startup. Default value is 1.Note:
The KBB_RAS1_LOG parameter also provides for the specification of the log file
directory, log file name, and the inventory control file directory and name. Do not
modify these values or log information can be lost. 4. Restart the monitoring agent
so that your changes take effect.Setting trace parameters for the Tivoli Enterprise
Console server In addition to the trace information captured by IBM Tivoli
Monitoring, you can also collect additional trace information for the Tivoli Enterprise
Console components that gather event server metrics. To do this, modify the
.tec_diag_config file on the Tivoli Enterprise Console event server. To modify the
event server trace parameters: 1. Open the $BINDIR/TME/TEC/.tec_diag_config file
in an ASCII editor. 100 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs
Guide
2. Locate the entries that configure trace logging for the agent components on the
event server. There are two entries, one for tec_reception and one for tec_rule: # to
debug Agent Utils tec_reception Agent_Utils error /tmp/tec_reception # to debug
Agent Utils tec_rule Agent_Utils error /tmp/tec_rule 3. To gather additional trace
information, modify these entries to specify a trace level of trace2: # to debug
Agent Utils tec_reception Agent_Utils trace2 /tmp/tec_reception # to debug Agent
Utils tec_rule Agent_Utils trace2 /tmp/tec_rule 4. In addition, modify the
Highest_level entries for tec_rule and tec_reception: tec_reception Highest_level
trace2 tec_rule Highest_level trace2 Problems and workarounds The following
sections provide symptoms and workarounds for problems that might occur with the
IBM Tivoli Monitoring for Tivoli Enterprise Console: v gInstallation and configuration
problem determinationh on page 101 v gAgent problem determinationh on page
103 v gWorkspace problem determinationh on page 106 v gProblem
determination for remote deploymenth on page 106 v gSituation problem
determinationh on page 108Note: You can resolve some problems by ensuring that
your system matches the system requirements listed in Chapter 2, gRequirements
for the monitoring agent,h on page 3.This appendix provides agent-specific
problem determination information. See the IBM Tivoli Monitoring Problem
Determination Guide for general problem determination information. Installation
and configuration problem determination This section provides tables that show
solutions for installation, configuration, and uninstallation problems.
Table 10. Problems and solutions for installation and configuration
Problem
Solution
A problem can arise when you install and configure a new monitoring agent to a
computer where other agents are running as described in this example: v Agents
are running on computer and communicating with a Tivoli Enterprise Monitoring
Server, called TEMS1. v You install a new agent on the same computer and you want
this agent to communicate with a different monitoring server, called TEMS2. v When
you configure the new agent to communicate with TEMS2, all the existing agents
are re-configured to communicate with TEMS2.
You must reconfigure the previously existing agents to restore their communication
connection with TEMS1. For example, you can right-click the row for a specific agent
in the Manage Tivoli Enterprise Monitoring Services, and select Reconfigure. See the
IBM Tivoli Monitoring Installation and Setup Guide for more information on
reconfiguration. Appendix B. Problem determination 101
Table 10. Problems and solutions for installation and configuration (continued)
Problem
Solution
Diagnosing problems with product browse settings (Windows systems only).
When you have problems with browse settings, perform the following steps: 1. Click
on Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring
Services. The Manage Tivoli Enterprise Monitoring Services is displayed. 2. Rightclick the Windows agent and select Browse Settings. A text window is displayed. 3.
Click Save As and save the information in the text file. If requested, you can forward
this file to IBM Software Support for analysis.
A message similar to Unable to find running CMS on CT_CMSLIST in the log file
is displayed.
If a message similar to Unable to find running CMS on CT_CMSLIST is displayed
in the Log file, the agent is not able to connect to the monitoring server. Confirm the
following points: v Do multiple network interface cards (NICs) exist on the system? v
If multiple NICs exist on the system, find out which one is configured for the
monitoring server. Ensure that you specify the correct host name and port settings
for communication in the IBM Tivoli Monitoring environment.
The system is experiencing high CPU usage.
Agent process: View the memory usage of the KKACMA process. If CPU usage seems
to be excessive, recycle the monitoring agent. Network Cards: The network card
configurations can decrease the performance of a system. Each of the stream of
packets that a network card receives (assuming it is a broadcast or destined for the
under-performing system) must generate a CPU interrupt and transfer the data
through the I/O bus. If the network card in question is a bus-mastering card, work
can be off-loaded and a data transfer between memory and the network card can
continue without using CPU processing power. Bus-mastering cards are generally
32-bit and are based on PCI or EISA bus architectures. 102 IBM Tivoli Monitoring for
Table 11. General problems and solutions for uninstallation
Problem
Solution
On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire
environment.
Be sure that you follow the general uninstallation process described in the IBM Tivoli
Monitoring Installation and Setup Guide: 1. Remove Tivoli Enterprise Monitoring
Server Application support by completing the following steps: - a. Use Manage Tivoli
Enterprise Monitoring Services b. Select Tivoli Enterprise Monitoring Server c. Right
Click and select advanced d. Select Remove TEMS application support e. Select the
agent to remove its application support2. Uninstall monitoring agents first, as in the
following examples: v Uninstall a single monitoring agent for a specific database.
-OR- v Uninstall all instances of a monitoring product, such as IBM Tivoli Monitoring
for Databases.3. Uninstall IBM Tivoli Monitoring.
Systems are inactive, show a status of OFFLINE and a dimmed appearance, and the
way to remove inactive managed systems from the Enterprise navigation tree in the
portal is not obvious.
When you want to remove a managed system from the navigation tree, right-click
the appropriate workspace from which you want to remove the item, and select
Remove managed system. The managed system will not reappear until it is
reconnected.
After the remote removal from the Tivoli Enterprise Portal of a running instance, the
instancefs name is still listed in the Start List.
Bring up the configure list to remove the instance name from the Start list. Unique
names for monitoring components IBM Tivoli Monitoring might not be able to
generate a unique name for monitoring components due to the truncation of names
that the product automatically generates. Agent problem determination This section
lists problems that might occur with agents. This appendix provides agent-specific
problem determination information. See the IBM Tivoli Monitoring Problem
Determination Guide for general problem determination information.
Table 12. Agent problems and solutions
Problem
Solution
Log data accumulates too rapidly.
Check the RAS trace option settings, which are described in gSetting RAS trace
parametersh on page 99. The trace options settings that you can set on the
KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.
Appendix B. Problem determination 103
Table 12. Agent problems and solutions (continued)
Problem
Solution
When using the F1 key or selecting Help --> Contents and Index, you receive a
message in your Microsoft Internet Explorer browser which states, It seems
javascript is disabled in your browser, please enable it and reload again, or click
here to view without javascript. If you select fheref, the Tivoli Enterprise Portal
V6.1 Help is displayed, but the agent help is not.
Ensure that the local site is added to the browserfs trusted site and then enable
the javascript.
If you want to receive multiple trace logs for separate invocations of the same Take
Action command, leaving this setting on permanently fills the available disk space.
Do not leave this setting permanently. By doing so, you create a new log file for
each invocation of the take action and ALL of them will be left on the agent system.
Online Help Search cannot find any agent online help.
To search the online help for this agent the user must use the IBM Eclipse help
search function and not the search function in the web based help online help. To
use the search function for this agentfs online help, ensure that you have selected
the IBM Eclipse help server check box when installing the Tivoli Enterprise Portal
Server. The fSearching Agent Helpf topic in this agentfs online help contains a
link to the Eclipse help, where the search function is enabled. From the Table of
Contents in the left-hand pane of the help, select the fSearching Agent Helpf
topic to find the link to the Eclipse help in the right-hand pane.
The wagtinit command fails.
The wagtinit command creates tables and views using the user ID defined in the
Tivoli Management Framework RIM object. This user ID must have CREATE VIEW and
CREATE TABLE privileges for the command to function. The database administrator
can grant these privileges temporarily and then revoke them after the wagtinit
command finishes.
No data appears in the Event Distribution workspaces.
Check the agent configuration: v Make sure the required working tables have been
created on the monitored Tivoli Enterprise Console System. To create the working
tables, run the wagtinit command. v Make sure the agent is started by a user ID
with sufficient TME privileges:For more information, see Chapter 2, gRequirements
for the monitoring agent,h on page 3.
The Tivoli Enterprise Console Server agent node in the Tivoli Enterprise Portal is not
available.
Restart the Monitoring Agent for Tivoli Enterprise Console. To do this, use the
Manage Tivoli Enterprise Monitoring Services window. 104 IBM Tivoli Monitoring for
Problem
Solution
Event Activity and Event Throughput data do not appear in the workspaces.
This can be caused by a mismatch between the log directory specified in the agent
configuration and the directory specified in the Tivoli Enterprise Console
configuration. To correct this problem: 1. On the Tivoli Enterprise Console server,
check the value specified for the tec_log_metrics_dir parameter in the
$BINDIR/TME/TEC/.tec_config file. 2. On the system where the monitoring agent is
installed, start the Manage Tivoli Monitoring Services application. 3. Right-click
Monitoring Agent For Tivoli Enterprise Console. 4. Click Configure (Reconfigure on
Windows systems). 5. Click OK until you see the IBM Tivoli Monitoring for Tivoli
Enterprise Console window. 6. In the Log Directory field, type the path to the log
directory specified in the Tivoli Enterprise Console configuration.Note: After you
start the Tivoli Enterprise Portal, there might be a delay of as long as 10 minutes
before data appears in the workspaces.
The error message "Error while checking the Tivoli object dispatcher (oserv) status"
appears when you attempt to run a Take Action command.
Make sure the agent is started by a user ID with sufficient TME privileges. For more
information, see Chapter 2, gRequirements for the monitoring agent,h on page 3.
Historical views are not working properly.
Check for configuration problems: 1. Make sure the Warehouse Proxy Agent and the
historical data collection are properly configured. For more information, refer to the
IBM Tivoli Monitoring Administratorfs Guide. 2. Right-click any of the historical
views (for example, Events Input/Output to Rule Engine By Event Class - Last 24hrs).
3. Click Properties. 4. In the left pane of the Properties window, select each historical
view you want to configure. 5. In the right pane of the Properties window, click Click
here to assign query. The Query Editor window opens with a query selected in the
right pane. 6. Click OK twice. 7. Refresh the Tivoli Enterprise Portal, or switch to
another workspace and then back to the workspace containing the historical view.
In the status-based Event Distribution workspaces (OPEN, ACKNOWLEDGED, and
CLOSED), the "events by host" and "events by source" views do not show any data.
Make sure you have enabled the host and event source dimensions for collection of
event distribution data: 1. Right-click Monitoring Agent For Tivoli Enterprise Console.
2. Click Configure (Reconfigure on Windows systems). 3. Click OK until you see the
IBM Tivoli Monitoring for Tivoli Enterprise Console window. 4. Select the Event
Distribution tab. 5. To include the event source dimension, click Include event
source dimension and then select Yes. 6. To include the host dimension, click Include
host dimension and then select Yes. 7. Click OK. 8. Restart the agent.
Some situations do not fire even when their conditions are true.
Check the affected situations to ensure they have been started. By default, some
situations are not enabled automatically at startup. Appendix B. Problem
determination 105
Problem
Solution
When using a Sybase or Microsoft SQL Server database, the Tivoli Enterprise
Console product stops functioning, and messages in the database log file indicate
that there is insufficient temporary space available.
Because the event distribution workspaces use a significant amount of temporary
workspace for queries, make sure the tempdb database has sufficient space
allocated. The amount of space required is proportional to the number of events in
the event repository and is increased if you enable the event source and host
dimensions for the event distribution data. The minimum recommended allocation
for the tempdb database is 100MB. Problem determination for remote deployment
Table 13 lists problems that might occur with remote deployment. This appendix
provides agent-specific problem determination information. See the IBM Tivoli
Monitoring Problem Determination Guide for general problem determination
information. This section describes problems and solutions for remote deployment
and removal of agent software Agent Remote Deploy:
Table 13. Remote deployment problems and solutions
Problem
Solution
While you are using the remote deployment feature to install IBM Tivoli Monitoring
for Tivoli Enterprise Console, an empty command window is displayed on the target
computer. This problem occurs when the target of remote deployment is a Windows
computer. (See the IBM Tivoli Monitoring Installation and Setup Guide for more
information on the remote deployment feature.)
Do not close or modify this window. It is part of the installation process and will be
dismissed automatically.
The removal of a monitoring agent fails when you use the remote removal process
in the Tivoli Enterprise Portal desktop or browser.
This problem might happen when you attempt the remote removal process
immediately after you have restarted the Tivoli Enterprise Monitoring Server. You
must allow time for the monitoring agent to refresh its connection with the Tivoli
Enterprise Monitoring Server before you begin the remote removal process.
Workspace problem determination Table 14 on page 107 shows problems that might
occur with workspaces. This appendix provides agent-specific problem
determination information. See the IBM Tivoli Monitoring Problem Determination
Guide for general problem determination information. 106 IBM Tivoli Monitoring for
Table 14. Workspace problems and solutions
Problem
Solution
The process application components are available, but the Availability status shows
PROCESS_DATA_NOT_ AVAILABLE.
This problem occurs because the PerfProc performance object is disabled. When this
condition exists, IBM Tivoli Monitoring cannot collect performance data for this
process. Do the following to confirm that this problem exists and resolve it: 1.
Choose Run in the Windows Start menu. 2. Type perfmon.exe in the Open field of
the Run window. The Performance window is displayed. 3. Click the plus sign (+) in
the tool bar located above the right pane. The Add Counters window is displayed. 4.
Look for Process in the Performance object pull-down menu. 5. Perform one of the
following actions: v If you see Process in the pull-down menu, the PerfProc
performance object is enabled and the problem is coming from a different source.
You might need to contact IBM Software Support. v If you do not see Process in the
pull-down menu, use the Microsoft utility from the following Web site to enable the
PerfProc performance object:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing /exctrlst-o.asp
The Process performance object becomes visible in the Performance object pulldown menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect
Availability data.6. Restart the monitoring agent
You see the following message: KFWIT083W Default link is disabled for the selected
object; please verify link and link anchor definitions.
You see this message because some links do not have default workspaces. Rightclick the link to access a list of workspaces to select.
The name of the attribute does not display in a bar chart or graph view.
When a chart or graph view that includes the attribute is scaled to a small size, a
blank space is displayed instead of a truncated name. To see the name of the
attribute, expand the view of the chart until there is sufficient space to display all
characters of the attributefs name.
You start collection of historical data but the data cannot be seen.
Managing options for historical data collection: v Basic historical data collection
populates the Warehouse with raw data. This type of data collection is turned off by
default. See the IBM Tivoli Monitoring Administratorfs Guide for information on
managing this feature including how to set the interval at which data is collected.
By setting a more frequent interval for data collection you reduce the load on the
system incurred every time data is uploaded. v You use the Summarization and
Pruning monitoring agent to collect specific amounts and types of historical data. Be
aware that historical data is not displayed until the Summarization and Pruning
monitoring agent begins collecting the data. By default, this agent begins collection
at 2 AM daily. At that point, data is visible in the workspace view. See the IBM Tivoli
Monitoring Administratorfs Guide to learn how to modify the default collection
settings. Appendix B. Problem determination 107
Table 14. Workspace problems and solutions (continued)
Problem
Solution
Historical data collection is unavailable because of incorrect queries in the Tivoli
Enterprise Portal.
The column, Sort By, Group By, and First/Last functions are not compatible with the
historical data collection feature. Use of these advanced functions will make a query
ineligible for historical data collection. Even if data collection has been started, you
cannot use the time span feature if the query for the chart or table includes any
column functions or advanced query options (Sort By, Group By, First / Last). To
ensure support of historical data collection, do not use the Sort By, Group By, or
First/Last functions in your queries. See the IBM Tivoli Monitoring Administratorfs
Guide the Tivoli Enterprise Portal online Help for information on the Historical Data
Collection function.
When you use a long process name in the situation, the process name is truncated.
Truncation of process or service names for situations in the Availability table in the
portal display is the expected behavior. 100 bytes is the maximum name length.
Regular (non-historical) monitoring data fails to be displayed.
Check the formation of the queries you use to gather capture data. For example,
look for invalid SQL statements. Situation problem determination This section
provides information about both general situation problems and problems with the
configuration of situations. See the IBM Tivoli Monitoring Problem Determination
Guide for more information about problem determination for situations. General
situation problems Table 15 lists problems that might occur with situations.
Table 15. General situation problems and solutions
Problem
Solution
Monitoring activity requires too much disk space.
Check the RAS trace logging settings that are described in gSetting RAS trace
parametersh on page 99. For example, trace logs grow rapidly when you apply the
ALL logging option.
Monitoring activity requires too many system resources.
gDisk capacity planning for historical datah on page 58 describes the

performance impact of specific attribute groups. If possible, decrease your use of
the attribute groups that require greater system resources.
A formula that uses mathematical operators appears to be incorrect. For example, if
you are monitoring Linux, a formula that calculates when Free Memory falls under
10 percent of Total Memory does not work: LT #fLinux_VM_Stats.Total_Memoryf /
10
This formula is incorrect because situation predicates support only logical operators.
Your formulas cannot have mathematical operators. Note: The Situation Editor
provides alternatives to math operators. Regarding the example, you can select %
Memory Free attribute and avoid the need for math operators. 108 IBM Tivoli
Table 15. General situation problems and solutions (continued)
Problem
Solution
IBM Tivoli Monitoring is configured to provide data to the optional product IBM Tivoli
Enterprise Console. However, a either a predefined situation that has been edited or
a user created situation displays the severity UNKNOWN in IBM Tivoli Enterprise
Console.
For a situation to have the correct severity in IBM Tivoli Enterprise Console for those
situations that are not mapped, you need to ensure that an entry exists in the
tecserver.txt file for the situation and that SEVERITY is specified. See the
"Configuring Tivoli Enterprise Console Integration" chapter in the IBM Tivoli
Monitoring Administratorfs Guide for more information.
You want to change the appearance of situations when they are displayed in the
Navigation tree.
1. Right-click an item in the Navigation tree. 2. Select Situations in the pop-up
menu. The Situation Editor window is displayed. 3. Select the situation that you
want to modify. 4. Use the Status pull-down menu in the lower right of the window
to set the status and appearance of the Situation when it triggers. Note: This status
setting is not related to severity settings in IBM Tivoli Enterprise Console. Problems
with configuration of situations Table 16 lists problems that might occur with
situations. This section provides information for problem determination for agents.
Be sure to consult the IBM Tivoli Monitoring Problem Determination Guide for more
general problem determination information.
Table 16. Problems with configuring situations that you solve in the Situation Editor
Problem
Solution
Note: To get started with the solutions in this section, perform these steps: 1.
Launch the Tivoli Enterprise Portal. 2. Click Edit > Situation Editor. 3. In the tree
view, choose the agent whose situation you want to modify. 4. Choose the situation
in the list. The Situation Editor view is displayed.
The situation for a specific agent is not visible in the Tivoli Enterprise Portal.
Open the Situation Editor. Access the All managed servers view. If the situation is
absent, confirm that the monitoring server has been seeded for the agent. If not,
seed the server, as described in the IBM Tivoli Monitoring Installation and Setup
Guide.
The monitoring interval is too long.
Access the Situation Editor view for the situation that you want to modify. Check the
Sampling interval area in the Formula tab. Adjust the time interval as needed.
The situation did not activate at startup.
Manually recycle the situation as follows: 1. Right-click the situation and choose
Stop Situation. 2. Right-click the situation and choose Start Situation.Note: You can
permanently avoid this problem by placing a check mark in the Run at Startup
option of the Situation Editor view for a specific situation.
The situation is not displayed.
Click the Action tab and check whether the situation has an automated corrective
action. This action can occur directly or through a policy. The situation might be
resolving so quickly that you do not see the event or the update in the graphical
user interface.
An Alert event has not occurred even though the predicate has been properly
specified.
Check the logs, reports, and workspaces. Appendix B. Problem determination 109
Table 16. Problems with configuring situations that you solve in the Situation Editor
(continued)
Problem
Solution
A situation fires on an unexpected managed object.
Confirm that you have distributed and started the situation on the correct managed
system.
The product did not distribute the situation to a managed system.
Click the Distribution tab and check the distribution settings for the situation.
The situation does not fire. Incorrect predicates are present in the formula that
defines the situation. For example, the managed object shows a state that normally
triggers a monitoring event, but the situation is not true because the wrong
attribute is specified in the formula.
In the Formula tab, analyze predicates as follows: 1. Click the fx icon in the upperright corner of the Formula area. The Show formula window is displayed. a. Confirm
the following details in the Formula area at the top of the window: v The attributes
that you intend to monitor are specified in the formula. v The situations that you
intend to monitor are specified in the formula. v The logical operators in the formula
match your monitoring goal. v The numerical values in the formula match your
monitoring goal.b. (Optional) Click the Show detailed formula check box in the lower
left of the window to see the original names of attributes in the application or
operating system that you are monitoring. c. Click OK to dismiss the Show formula
window.2. (Optional) In the Formula area of the Formula tab, temporarily assign
numerical values that will immediately trigger a monitoring event. The triggering of
the event confirms that other predicates in the formula are valid. Note: After you
complete this test, you must restore the numerical values to valid levels so that you
do not generate excessive monitoring data based on your temporary settings.
Table 17. Problems with configuration of situations that you solve in the Workspace
area
Problem
Solution
Situation events are not displayed in the Events Console view of the workspace.
Associate the situation with a workspace. Note: The situation does not need to be
displayed in the workspace. It is sufficient that the situation be associated with any
workspace.
You do not have access to a situation.
Note: You must have administrator privileges to perform these steps. 1. Select Edit
> Administer Users to access the Administer Users window. 2. In the Users area,
select the user whose privileges you want to modify. 3. In the Permissions tab,
Applications tab, and Navigator Views tab, select the permissions or privileges that
correspond to the userfs role. 4. Click OK.
A managed system seems to be offline.
1. Select Physical View and highlight the Enterprise Level of the navigator tree. 2.
Select View > Workspace > Managed System Status to see a list of managed
systems and their status. 3. If a system is offline, check network connectivity and
status of the specific system or application. Take Action commands problem
determination Table 18 on page 111 lists general problems that might occur with
Take Action commands. When each Take Action command runs it generates the log
file listed in Table 9 on page 96. This appendix provides agent-specific problem
determination information. 110 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
See the IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.
Table 18. Take Action commands problems and solutions
Problem
Solution
Take Action commands often require several minutes to complete.
Allow several minutes. If you do not see a pop-up message advising you of
completion, try to run the command manually.
Situations fail to trigger Take Action commands.
Attempt to manually run the Take Action command in the Tivoli Enterprise Portal. If
the Take Action command works, look for configuration problems in the situation.
See gSituation problem determinationh on page 108. If the Take Action command
fails, see IBM Tivoli Monitoring Problem Determination Guide for general information
on troubleshooting Take Action commands. Support information If you have a
problem with your IBM software, you want to resolve it quickly. This section
describes the following options for obtaining support for IBM software products: v
gUsing IBM Support Assistanth v gObtaining fixesh on page 112 v gReceiving
weekly support updatesh on page 112 v gContacting IBM Software Supporth on
page 112Using IBM Support Assistant The IBM Support Assistant is a free, standalone application that you can install on any workstation. You can then enhance the
application by installing product-specific plug-in modules for the IBM products you
use. The IBM Support Assistant saves you time searching product, support, and
educational resources. The IBM Support Assistant helps you gather support
information when you need to open a problem management record (PMR), which
you can then use to track the problem. The product-specific plug-in modules provide
you with the following resources: v Support links v Education links v Ability to
submit problem management reportsIf your product does not use IBM Support
Assistant, use the links to support topics in your information center. In the
navigation frame, check the links for resources listed in the ibm.com and related
resources section where you can search the following resources: v Support and
assistance (includes search capability of IBM Technotes and IBM Downloads for
interim fixes and workarounds) v Training and certification v IBM developerWorks v
IBM Redbooks v General product information
If you cannot find the solution to your problem in the information center, search the
following Internet resources for the latest information that might help you resolve
your problem: v Forums and newsgroups v Google.comObtaining fixes A product fix
might be available to resolve your problem. To determine what fixes are available
for your IBM software product, follow these steps: 1. Go to the Software support
Web site at http://www.ibm.com/software/support. 2. Click the Download tab. 3.
Select the operating system in the Operating system menu. 4. Type search terms in
the Enter search terms field. 5. As appropriate, use other search options to further
define your search. 6. Click Search. 7. From the list of downloads returned by your
search, click the name of a fix to read the description of the fix and to optionally
download the fix.For more information about the types of fixes that are available,
see the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html. Receiving weekly
support updates To receive weekly e-mail notifications about fixes and other
software support news, follow these steps: 1. Go to the IBM Software Support Web
site at http://www.ibm.com/software/support. 2. Click My account in the upper right
corner of the page. 3. Click Subscribe to IBM e-news. (If you have already
subscribed and want to modify your subscription preferences, click Modify
subscriptions and follow the instructions on screen.) 4. Follow the instructions on
screen to provide the following data: v Your personal contact information. v Your
areas of interest. v The types of subscriptions and regional versions that you want
to receive.5. Review the subscription confirmation to confirm your settings.If you
experience problems with the My support feature, you can obtain help in one of the
following ways: Online Send an e-mail message to erchelp@ca.ibm.com, describing
your problem. By phone Call 1-800-IBM-4You (1-800-426-4968).Contacting IBM
Software Support IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the type
of product you have: v For IBM distributed software products (including, but not
limited to, TivoliR, LotusR, and RationalR products, as well as DB2R and
WebSphereR products that run on Windows, or UNIX operating systems), enroll in
Passport Advantage in one of the following ways: Online Go to the Passport
Advantage Web site at http://www306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm . By phone
For the phone number to call in your country, go to the IBM Software Support Web
site at http://techsupport.services.ibm.com/guides/contacts.html and click the name
of your geographic region.v For customers with Subscription and Support (S & S)
contracts, go to the Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login. v For customers with IBMLink, CATIA,
Linux, OS/390, iSeries, pSeries, zSeries, and other support agreements, go to the
IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006. v For IBM eServer
software products (including, but not limited to, DB2 and WebSphere products that
run in zSeries, pSeries, and iSeries environments), you can purchase a software
maintenance agreement by working directly with an IBM sales representative or an
IBM Business Partner. For more information about support for eServer software
products, go to the IBM Technical Support Advantage Web site at
http://www.ibm.com/servers/eserver/techsupport.html.If you are not sure what type
of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378)
in the United States. From other countries, go to the contacts page of the IBM
Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of

your geographic region for phone numbers of people who provide support for your
location. To contact IBM Software support, follow these steps: 1. gDetermining the
business impacth 2. gDescribing problems and gathering informationh on page
114 3. gSubmitting problemsh on page 114Determining the business impact
When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria: Severity 1 The problem has a
critical business impact. You are unable to use the program, resulting in a critical
impact on operations. This condition requires an immediate solution. Severity 2 The
problem has a significant business impact. The program is usable, but it is severely
limited. Appendix B. Problem determination 113
Severity 3 The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable. Severity 4 The
problem has minimal business impact. The problem causes little impact on
operations, or a reasonable circumvention to the problem was
implemented.Describing problems and gathering information When describing a
problem to IBM, be as specific as possible. Include all relevant background
information so that IBM Software Support specialists can help you solve the problem
efficiently. To save time, know the answers to these questions: v What software
versions were you running when the problem occurred? v Do you have logs, traces,
and messages that are related to the problem symptoms? IBM Software Support is
likely to ask for this information. v Can you re-create the problem? If so, what steps
were performed to re-create the problem? v Did you make any changes to the
system? For example, did you make changes to the hardware, operating system,
networking software, and so on. v Are you currently using a workaround for the
problem? If so, be prepared to explain the workaround when you report the
problem.See gGathering product information for IBM Software Supporth on page
93 for further tips for gathering information for IBM Software Support. Submitting
problems You can submit your problem to IBM Software Support in one of two ways:
Online Click Submit and track problems on the IBM Software Support site
athttp://www.ibm.com/software/support/probsub.html. Type your information into
the appropriate problem submission form. By phone For the phone number to call in
your country, go to the contacts page of the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region.If the problem you submit is for a software defect or for
missing or inaccurate documentation, IBM Software Support creates an Authorized
Program Analysis Report (APAR). The APAR describes the problem in detail.
Whenever possible, IBM Software Support provides a workaround that you can
implement until the APAR is resolved and a fix is delivered. IBM publishes resolved
APARs on the Software Support Web site daily, so that other users who experience
the same problem can benefit from the same resolution. Informational, warning, and
error messages This appendix introduces message logging and explains how to
gather information from those logs. Message logging refers to the text and numeric
messages created by the software. These messages relay information about how
the system or application is performing and can alert you to exceptional conditions
when they occur. Messages are sent to an output destination, such as a file,
database, or console screen. 114 IBM Tivoli Monitoring for Tivoli Enterprise Console:
Userfs Guide
If you receive a warning or error message, you can do one of the following: v Follow
the instructions listed in the Detail window of the message if this information is
included there. v Consult the message details listed in this appendix to see what
action you can take to correct the problem. v Consult the message log for message
ID and text, time and date of the message, as well as other data you can use to
diagnose the problem.Message format IBM Tivoli Monitoring for Tivoli Enterprise
Console messages have the following format:Message ID and text Explanation
Operator Response The message ID has the following format: CCC####severity
where: CCC Prefix that indicates the component to which the message applies. The
component is one of the following: KKA General IBM Tivoli Monitoring for Tivoli
Enterprise Console messages#### Number of the message severity Severity of the
message. There are three levels of severity: I Informational messages provide
feedback about something that happened in the product or system that might be
important. These messages can provide guidance when you are requesting a
specific action from the product. W Warning messages call your attention to an
exception condition. The condition might not be an error but can cause problems if
not resolved. E Error messages indicate that an action cannot be completed
because of a user or system error. These messages require user response.The Text
of the message provides a general statement regarding the problem or condition
that occurred. The Explanation provides additional information about the message
and what might have caused the condition. The Operator Response provides actions
to take in response to the condition, particularly for error messages (messages with
the E suffix).Note: Many message texts and explanations contain variables,
such as the specific name of a server or application. Those variables are
represented in this appendix as symbols, such as &1. Actual messages contain
values for these variables. This appendix includes the messages for the following
software: v IBM Tivoli Monitoring for Tivoli Enterprise Console
IBM Tivoli Monitoring for Tivoli Enterprise Console messages KKA0001I The Tivoli
Enterprise Console event server was started successfully. Explanation: The Tivoli
Enterprise Console event server was either started successfully, or it was already
started. Operator response: None. KKA0002E Error starting Tivoli Enterprise Console
event server. Explanation: An error occurred during startup of the Tivoli Enterprise
Console event server. Operator response: Check the event server log to determine
the cause of the problem. KKA0003I The Tivoli Enterprise Console event server was
stopped successfully. Explanation: The Tivoli Enterprise Console server was either
stopped successfully, or it was already stopped. Operator response: None.
KKA0004E Error stopping Tivoli Enterprise Console event server. Explanation: An
error occurred while stopping the Tivoli Enterprise Console event server. Operator
response: Check the event server log to determine the cause of the problem.
KKA0005I The event repository was purged successfully. Explanation: The requested
purge operation for the Tivoli Enterprise Console event repository was completed
successfully. Operator response: None. KKA0006E Error purging event repository.

Explanation: An error occurred while performing the requested purge of the Tivoli
Enterprise Console event repository. Operator response: Check the Tivoli Enterprise
Console server log to determine the cause of the problem. KKA0007I The reception
log was purged successfully. Explanation: The requested purge operation for the
Tivoli Enterprise Console reception log was completed successfully. Operator
response: None. KKA0008E Error purging event reception log. Explanation: An error
occurred while performing the requested purge of the Tivoli Enterprise Console
reception log. Operator response: Check the Tivoli Enterprise Console server log to
determine the cause of the problem. KKA0009E Error sourcing the Tivoli
environment on monitored system. Explanation: An error occurred while attempting
to source the Tivoli environment. This might indicate that the setup_env.sh or
setup_env.cmd file could not be found. Operator response: Confirm that the
setup_env.sh file (for Linux or UNIX systems) or setup_env.cmd file (for Windows
systems) is present on the monitored system. KKA0001I . KKA0009E
KKA0010E Error while checking the Tivoli object dispatcher (oserv) status.
Explanation: An error occurred while checking the status of the Tivoli object
dispatcher (oserv) process. Operator response: Confirm that the Tivoli object
dispatcher (oserv) process is running on the monitored system. KKA0011E Error
locating wtdbclear command on monitored system. Explanation: An error occurred
while attempting to locate the wtdbclear command on the monitored system.
Operator response: Confirm that the wtdbclear command is present on the
monitored system. KKA0012E Error locating wstartesvr command on monitored
system. Explanation: An error occurred while attempting to locate the wstartesvr
command on the monitored system. Operator response: Confirm that the wstartesvr
command is present on the monitored system. If this command is not present, this
probably indicates that the Tivoli Enterprise Console server is not installed.
KKA0013E Error locating wstopesvr command on monitored system. Explanation: An
error occurred while attempting to locate the wstopesvr command on the monitored
system. Operator response: Check to ensure that the wstopesvr command is
present on the monitored system. If this command is not present, this probably
indicates that the Tivoli Enterprise Console server is not installed. KKA0014E The
Tivoli Enterprise Console event server is already running. Explanation: The Tivoli
Enterprise Console event server is already running on the monitored system.
Operator response: None. KKA0015E The Tivoli Enterprise Console event server is
not running. Explanation: The Tivoli Enterprise Console event server is not running
on the monitored system. The event server has already been stopped. Operator
response: None.
KKA0010E . KKA0015E
Appendix C. Accessibility Accessibility features help users with physical disabilities,

such as restricted mobility or limited vision, to use software products successfully.
The major accessibility features in this product enable users to do the following: v
Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product. v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen. In addition, the product documentation
was modified to include the following features to aid accessibility: v All
documentation is available in both HTML and convertible PDF formats to give the
maximum opportunity for users to apply screen-reader software. v All images in the
documentation are provided with alternative text so that users with vision
impairments can understand the contents of the images.Navigating the interface
using the keyboard Standard shortcut and accelerator keys are used by the product
and are documented by the operating system. Refer to the documentation provided
by your operating system for more information. Magnifying what is displayed on the
screen You can enlarge information on the product windows using facilities provided
by the operating systems on which the product is run. For example, in a MicrosoftR
Windows environment, you can lower the resolution of the screen to enlarge the
font sizes of the text on the screen. Refer to the documentation provided by your
operating system for more information. c Copyright IBM Corp. 2005, 2006 119
Appendix D. Notices This information was developed for products and services
offered in the U.S.A. IBM may not offer the products, services, or features discussed
in this document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any IBM intellectual
property right may be used instead. However, it is the userfs responsibility to
evaluate and verify the operation of any non-IBM product, program, or service. IBM
may have patents or pending patent applications covering subject matter described
in this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to:IBM Director of Licensing
IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license
inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:IBM World
Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106,
Japan The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not
allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you. This information could include technical
inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the
publication. IBM may make improvements and/or changes in the product(s) and/or
the program(s) described in this publication at any time without notice. Any
references in this information to non-IBM Web sites are provided for convenience
only and do not in any manner serve as an endorsement of those Web sites. The
materials at those Web sites are not part of the materials for this IBM product and
use of those Web sites is at your own risk. c Copyright IBM Corp. 2005, 2006 121
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you. Licensees of this program who
wish to have information about it for the purpose of enabling: (i) the exchange of
information between independently created programs and other programs
(including this one) and (ii) the mutual use of the information which has been
exchanged, should contact:IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX
78758 U.S.A. Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee. The licensed program
described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program
License Agreement or any equivalent agreement between us. This information
contains examples of data and reports used in daily business operations. To
illustrate them as completely as possible, the examples include the names of
individuals, companies, brands, and products. All of these names are fictitious and
any similarity to the names and addresses used by an actual business enterprise is
entirely coincidental. COPYRIGHT LICENSE: This information contains sample
application programs in source language, which illustrate programming techniques
on various operating systems. You may copy, modify, and distribute these sample
programs in any form without payment to IBM, for the purposes of developing,
using, marketing or distributing application programs conforming to the application
programming interface for the operating system for which the sample programs are
written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. You may copy, modify, and distribute these sample programs in any form
without payment to IBM for the purposes of developing, using, marketing, or
distributing application programs conforming to IBMfs application programming
interfaces. If you are viewing this information in softcopy form, the photographs and
color illustrations might not appear. Trademarks DB2, developerWorks, eServer, IBM,
IBMLink, the IBM logo, iSeries, Lotus, OS/390, Passport Advantage, pSeries, Rational,
Redbooks, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli Enterprise Console,
WebSphere, and zSeries are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both.
Microsoft, and Windows are registered trademarks of Microsoft Corporation in the
United States, other countries, or both. 122 IBM Tivoli Monitoring for Tivoli
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries. Other company, product, and service names may be trademarks or
service marks of others. Appendix D. Notices 123
Index Aaccessibility ix, 119 Acknowledged Events Distribution workspace 19
actionsSee Take Action commands agenttrace logs 95 agentsproblem determination
103 Application Component attribute 26 Arrival Rate attribute 54 attribute
groupsAvailability 26 Event Activity 29 Event Activity Base 31 Event Activity Class
32 Event Distribution 34 Event Distribution Base 35 Event Distribution By Class 36
Event Distribution By Class Base 38 Event Distribution By Host 40 Event Distribution
By Host Base 42 Event Distribution By Source 43 Event Distribution By Source Base
45 Event Distribution By Status 47 Event Distribution By Status Base 49 Event
Severity 50 Event Status 51 Event Throughput 51 list of all 25 more information 25
overview 25 Performance Object Status 56 attributesApplication Component 26
Arrival Rate 54 Availability 26 Average Arrival Rate 54 Average Parse fail 56 Average
Processed 53 Average Processing Rate 55 Average Queued 55 Average Received 52
Average Time Rule 30, 31, 33 Average Waiting 54 Command Line 28 Critical 37, 39,
41, 43, 44, 46, 48, 49 Custom 38, 40, 42, 43, 45, 47, 48, 50 Error Code 57 Event
Activity 29 Event Activity Base 31 Event Activity Class 32 Event Class 30, 31, 33, 34,
36, 37, 39 Event Count Diff 30, 32, 33 Event Distribution 34 Event Distribution Base
35 Event Distribution By Class 37 Event Distribution By Class Base 38 Event
Distribution By Host 40 Event Distribution By Host Base 42 Event Distribution By
Source 44 attributes (continued)Event Distribution By Source Base 45 Event
Distribution By Status 47 Event Distribution By Status Base 49 Event Severity 50
Event Status 51 Event Throughput 52 Fatal 37, 39, 41, 42, 44, 46, 48, 49 Full Name
27 Functionality Test Message 29 Functionality Test Status 28 Harmless 38, 39, 41,
43, 45, 46, 48, 50 Host Name 35, 36, 41, 42 Maximum Arrival Rate 54 Maximum
Parse Fail 56 Maximum Processed 53 Maximum Processing Rate 55 Maximum
Queued 55 Maximum Received 52 Maximum Waiting 53 Minimum Arrival Rate 54
Minimum Parse Fail 55 Minimum Processed 53 Minimum Processing Rate 54
Minimum Queued 55 Minimum Received 52 Minimum Waiting 53 Minor 38, 39, 41,
43, 45, 46, 48, 49 more information 25 Name 27 Node 26, 29, 31, 32, 34, 35, 37,
38, 40, 42, 44, 46, 47, 49, 50, 51, 52, 56 Number Events In 30, 32, 33 Number
Events Out 30, 32, 33 Number Tasks 30, 32, 33 Object Name 57 Object Status 57
Object Type 57 overview 25 Page Faults per Sec 27 Parse Fail 55 Percent Privileged
Time 28 Percent Processor Time 28 Percent User Mode Time 28 Performance Object
Status 56 PID 28 Processed 53 Processing Rate 54 Query Name 56 Queued 55
Received 52 Sample Time 29, 31, 32, 34, 35, 37, 39, 41, 42, 44, 46, 48, 49, 52
Severity 30, 31, 34, 36 Severity Code 29, 50 Severity Text 29, 35, 36, 51 Source 35,
36, 44, 46 Status 27, 34, 36, 37, 39, 41, 42, 44, 46, 48, 49 Status Code 34, 37, 40,
44, 47, 51 Status Text 34, 37, 40, 44, 47, 51 Thread Count 28 c Copyright IBM Corp.
2005, 2006 125
attributes (continued)Time Period 29, 31, 33, 52 Timestamp 26, 29, 31, 32, 34, 35,
37, 39, 40, 42, 44, 46, 47, 49, 50, 51, 52, 56 Total Events 35, 36, 38, 40, 42, 43, 45,
47, 48, 50 Total Parse Fail 56 Total Processed 53 Total Received 52 Total Time Rule
30, 31, 33 Total Waiting 54 Type 27 Unknown 38, 40, 41, 43, 45, 47, 48, 50 Virtual
Size 27 Warning 38, 39, 41, 43, 45, 46, 48, 50 Working Set Size 27
Availabilitysituations 62, 63 workspacesdescriptions 16 list 15 Availability attribute
group 26 Availability workspace 16 Average Arrival Rate attribute 54 Average Parse
fail attribute 56 Average Processed attribute 53 Average Processing Rate attribute
55 Average Queued attribute 55 Average Received attribute 52 Average Time Rule
attribute 30, 31, 33 Average Waiting attribute 54 Bbooksfeedback viii online viii
ordering viii see publications ix built-in problem determination features 93
Ccalculate historical data disk space 58 capacity planningTec Health Agent 58
capacity planning for historical data 58 Closed Events Distribution workspace 20
collecting data 13 Command Line attribute 28 commands, Take Action 77
components 2 configuration 3 conventionsoperating system x typeface x Critical
attribute 37, 39, 41, 43, 44, 46, 48, 49 Custom attribute 38, 40, 42, 43, 45, 47, 48,
50 customer supportSee Software Support customizingmonitoring environment 11
situations 12 Ddatacollecting 13 trace logs 94 viewing 13 data loggedTec Health
Agent 58 data provider logsSee agent detecting problems, modifying situation
values 12 directory names, notation x disk capacity planningSee capacity planning
disk capacity planning for historical data 58 Eeducation 111 see Tivoli technical
training x environmentcustomizing 11 features 1 functions 1 monitoring real-time 9
real-time monitoring 9 environment variables, notation x Error Code attribute 57
eventmapping 85 Event Activitysituations 62, 73 workspacesdescriptions 17 list 15
Event Activity attribute group 29 Event Activity Base attribute group 31 Event
Activity By Class - Last 1 Month workspace 18 Event Activity By Class - Last 1 Week
workspace 17 Event Activity By Class - Last 1 Year workspace 18 Event Activity By
Class - Last 24hrs workspace 17 Event Activity Class attribute group 32 Event
Activity workspace 17 Event Class attribute 30, 31, 33, 34, 36, 37, 39 Event Count
Diff attribute 30, 32, 33 Event Distributionsituations 62, 73 workspacesdescriptions
19 list 15 Event Distribution attribute group 34 Event Distribution Base attribute
group 35 Event Distribution By Class attribute group 36 Event Distribution By Class
Base attribute group 38 Event Distribution By Host attribute group 40 Event
Distribution By Host Base attribute group 42 Event Distribution By Source attribute
group 43 Event Distribution By Source Base attribute group 45 Event Distribution By
Status attribute group 47 Event Distribution By Status Base attribute group 49
Event Distribution workspace 19 Event Severity attribute group 50 Event Status
attribute group 51 Event Throughputsituations 62, 74 workspacesdescriptions 20
Event Throughput (continued)workspaces (continued)list 16 Event Throughput - Last
1 Month workspace 22 Event Throughput - Last 1 Week workspace 21 Event
Throughput - Last 1 Year workspace 23 Event Throughput - Last 24hrs workspace 21
Event Throughput attribute group 51 Event Throughput workspace 20
eventsinvestigating 10 workspaces 10 FFatal attribute 37, 39, 41, 42, 44, 46, 48, 49
features, IBM Tivoli Monitoring for Tivoli Enterprise Console 1 filesagent trace 95
installation trace 95 other trace log 96 trace logs 94 fixes, obtaining 112 Full Name
attribute 27 Functionality Test Message attribute 29 Functionality Test Status

attribute 28 functions, IBM Tivoli Monitoring for Tivoli Enterprise Console 1
Ggathering support information 93 HHarmless attribute 38, 39, 41, 43, 45, 46, 48,
50 historical datacalculate disk space 58 capacity planningTec Health Agent 58 disk
capacity planning 58 historical data, collecting and viewing 13 Host Name attribute
35, 36, 41, 42 IIBM Redbooks 111 IBM Software SupportSee support IBM Support
Assistant 111 IBM Tivoli Enterprise Consoleevent mapping 85 IBM Tivoli Monitoring
for Tivoli Enterprise Consolecomponents 2 features 1 functions 1 performance
considerations 108 informationproblem determination 93 information,
additionalattributes 25 policies 83 procedural 9 situations 61 information, additional
(continued)Take Action commands 77 workspaces 15 installationlog file 95 more
information 9 problems 101 interface, user 2 investigating an event 10
KKKA_Process_Data_Unavailable situation 63 KKA_TEC_Dispatch_Proc_CPU_Crit
situation 69 KKA_TEC_Dispatch_Proc_CPU_High situation 69
KKA_TEC_Dispatch_Proc_Down situation 65 KKA_TEC_Event_Arriv_Rate_Crit situation
74 KKA_TEC_Events_Count_High situation 73 KKA_TEC_Fatal_Events_Ct_High
situation 73 KKA_TEC_Parse_Failures situation 75 KKA_TEC_Queued_Crit situation 74
KKA_TEC_Reception_Proc_Down situation 64 KKA_TEC_Receptn_Proc_CPU_Crit
situation 67 KKA_TEC_Receptn_Proc_CPU_High situation 67
KKA_TEC_Rule_Proc_CPU_Crit situation 70 KKA_TEC_Rule_Proc_CPU_High situation 70
KKA_TEC_Rule_Proc_Down situation 65 KKA_TEC_Server_Proc_CPU_Crit situation 71
KKA_TEC_Server_Proc_CPU_High situation 71 KKA_TEC_Server_Proc_Down situation
66 KKA_TEC_Task_Proc_CPU_Crit situation 72 KKA_TEC_Task_Proc_CPU_High situation
72 KKA_TEC_Task_Proc_Down situation 66 KKA_TEC_UI_Srvr_Proc_CPU_Crit situation
68 KKA_TEC_UI_Srvr_Proc_CPU_High situation 68 KKA_TEC_UI_Srvr_Proc_Down
situation 64 KKA_TEC_Waiting_Events_High situation 75 Llegal notices 121 list of
messages 116 logged dataTec Health Agent 58 loggingagent trace logs 95, 96 builtin features 93 installation log files 95 trace log files 94 Mmanualsfeedback viii online
viii ordering viii see publications ix Maximum Arrival Rate attribute 54 Maximum
Parse Fail attribute 56 Maximum Processed attribute 53 Maximum Processing Rate
attribute 55 Maximum Queued attribute 55 Maximum Received attribute 52
Maximum Waiting attribute 53 messagesbuilt-in features 93 Index 127
messages (continued)for IBM Tivoli Monitoring for Tivoli Enterprise Console 116
format 115 overview 114 syntax 115 Minimum Arrival Rate attribute 54 Minimum
Parse Fail attribute 55 Minimum Processed attribute 53 Minimum Processing Rate
attribute 54 Minimum Queued attribute 55 Minimum Received attribute 52 Minimum
Waiting attribute 53 Minor attribute 38, 39, 41, 43, 45, 46, 48, 49 modifying
situation values to detect problems 12 monitoring agentusing 9 monitoring, viewing
the real-time environment 9 NName attribute 27 Node attribute 26, 29, 31, 32, 34,
35, 37, 38, 40, 42, 44, 46, 47, 49, 50, 51, 52, 56 notationenvironment variables x
path names x typeface x Number Events In attribute 30, 32, 33 Number Events Out
attribute 30, 32, 33 Number Tasks attribute 30, 32, 33 OObject Name attribute 57
Object Status attribute 57 Object Type attribute 57 online publicationsaccessing ix
Open Events Distribution workspace 19 operation of resource, recovering 10
ordering publications ix PPage Faults per Sec attribute 27 Parse Fail attribute 55
path names, notation x Percent Privileged Time attribute 28 Percent Processor Time
attribute 28 Percent User Mode Time attribute 28 performance considerations 108

Performance Object Status attribute group 56 PID attribute 28 policiesmore
information 83 overview 83 problem determination 93, 101 agents 103 built-in
features 93 describing problems 114 determining business impact 113 installation
101 installation logs 95 messages 114 remote deployment 106 problem
determination (continued)situations 108, 109 submitting problems 114 Take Action
commands 110 uninstallation 101 uninstallation logs 95 workspaces 106 problem
resolution 111 problemsdetecting 12 problems and workarounds 101 procedures 9
Processed attribute 53 Processing Rate attribute 54 publicationsaccessing online ix
feedback viii online viii ordering viii, ix Purge Event Repository action 78 Purge
Reception Log action 79 purposescollecting data 13 customizing monitoring
environment 11 investigating events 10 monitoring with custom situations 12
problem determination 93 recovering resource operation 10 viewing data 13
viewing real-time monitoring environment 9 Qqueries, using attributes 25 Query
Name attribute 56 Queued attribute 55 Rreal-time data, viewing 9 Received
attribute 52 recovering the operation of a resource 10 Redbooks, IBM 111 remote
deploymentproblem determination 106 requirements 3 resource, recovering
operation 10 SSample Time attribute 29, 31, 32, 34, 35, 37, 39, 41, 42, 44, 46, 48,
49, 52 Severity attribute 30, 31, 34, 36 Severity Code attribute 29, 50 Severity Text
attribute 29, 35, 36, 51 situationsgeneral problem determination 108, 109
KKA_Process_Data_Unavailable 63 KKA_TEC_Dispatch_Proc_CPU_Crit 69
KKA_TEC_Dispatch_Proc_CPU_High 69 KKA_TEC_Dispatch_Proc_Down 65
KKA_TEC_Event_Arriv_Rate_Crit 74 KKA_TEC_Events_Count_High 73
KKA_TEC_Fatal_Events_Ct_High 73 KKA_TEC_Parse_Failures 75 KKA_TEC_Queued_Crit
74 128 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide
situations (continued)KKA_TEC_Reception_Proc_Down 64
KKA_TEC_Receptn_Proc_CPU_Crit 67 KKA_TEC_Receptn_Proc_CPU_High 67
KKA_TEC_Rule_Proc_CPU_Crit 70 KKA_TEC_Rule_Proc_CPU_High 70
KKA_TEC_Rule_Proc_Down 65 KKA_TEC_Server_Proc_CPU_Crit 71
KKA_TEC_Server_Proc_CPU_High 71 KKA_TEC_Server_Proc_Down 66
KKA_TEC_Task_Proc_CPU_Crit 72 KKA_TEC_Task_Proc_CPU_High 72
KKA_TEC_Task_Proc_Down 66 KKA_TEC_UI_Srvr_Proc_CPU_Crit 68
KKA_TEC_UI_Srvr_Proc_CPU_High 68 KKA_TEC_UI_Srvr_Proc_Down 64
KKA_TEC_Waiting_Events_High 75 list of all 62 more information 61 overview 61
predefined 62 values, modifying 12 situations, using attributes 25 software support
111 Software Supportcontacting 112 describing problems 114 determining business
impact 113 receiving weekly updates 112 submitting problems 114 Source attribute
35, 36, 44, 46 Start TEC Server action 80 Status attribute 27, 34, 36, 37, 39, 41, 42,
44, 46, 48, 49 Status Code attribute 34, 37, 40, 44, 47, 51 Status Text attribute 34,
37, 40, 44, 47, 51 Stop TEC Server action 81 supportgathering information for 93
IBM Support Assistant 111 list of messages 116 messages 114 Support Assistant
111 syntaxmessages 115 TTake Action commands 10 list of all 77 more information
77 overview 77 predefined 77 problem determination 110 Purge Event Repository
78 Purge Reception Log 79 Start TEC Server 80 Stop TEC Server 81 TEC UI Server
Process workspace 16 Thread Count attribute 28 Time Period attribute 29, 31, 33,
52 Timestamp attribute 26, 29, 31, 32, 34, 35, 37, 39, 40, 42, 44, 46, 47, 49, 50, 51,
52, 56 Tivoli Enterprise Consolesituations 62, 63 workspacesdescriptions 16 list 15

Tivoli Enterprise Console workspace 16 Tivoli software information center ix Tivoli
technical training x Total Events attribute 35, 36, 38, 40, 42, 43, 45, 47, 48, 50 Total
Parse Fail attribute 56 Total Processed attribute 53 Total Received attribute 52 Total
Time Rule attribute 30, 31, 33 Total Waiting attribute 54 trace logs 94 trademarks
122 training, Tivoli technical x troubleshooting 93 Type attribute 27 typeface
conventions x Uuninstallationlog file 95 problems 101 Unknown attribute 38, 40, 41,
43, 45, 47, 48, 50 user interfaces options 2 using a monitoring agentpurposes 9
Vvalues, modifying situations 12 variables, notation for x viewing data 13 viewing
real-time monitoring environment 9 viewsAcknowledged Events Distribution
workspace 19 Availability workspace 16 Closed Events Distribution workspace 20
Event Activity By Class - Last 1 Month workspace 18 Event Activity By Class - Last 1
Week workspace 17 Event Activity By Class - Last 1 Year workspace 18 Event
Activity By Class - Last 24hrs workspace 17 Event Activity workspace 17 Event
Distribution workspace 19 Event Throughput - Last 1 Month workspace 22 Event
Throughput - Last 1 Week workspace 21 Event Throughput - Last 1 Year workspace
23 Event Throughput - Last 24hrs workspace 21 Event Throughput workspace 20
Open Events Distribution workspace 19 TEC UI Server Process workspace 16 Tivoli
Enterprise Console workspace 16 Virtual Size attribute 27 WWarning attribute 38,
39, 41, 43, 45, 46, 48, 50 workarounds 101 agents 103 remote deployment 106
situations 108 Take Action commands 110 workspaces 106 Working Set Size
attribute 27 workspaces_EnDNAVIGATOR_ITEM_EnD 16, 17, 19, 20 Acknowledged
Events Distribution 19 Availability 16 Index 129
workspaces (continued)Closed Events Distribution 20 event 10 Event Activity 17
Event Activity By Class - Last 1 Month 18 Event Activity By Class - Last 1 Week 17
Event Activity By Class - Last 1 Year 18 Event Activity By Class - Last 24hrs 17 Event
Distribution 19 Event Throughput 20 Event Throughput - Last 1 Month 22 Event
Throughput - Last 1 Week 21 Event Throughput - Last 1 Year 23 Event Throughput Last 24hrs 21 list of all 15 more information 15 Open Events Distribution 19
overview 15 predefined 15 problem determination 106 TEC UI Server Process 16
Tivoli Enterprise Console 16
Printed in USA GC32-1959-00

Test 2

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Test 2

Hochgeladen von

Copyright:

Verfügbare Formate

TivoliRIBM Tivoli Monitoring for Tivoli Enterprise ConsoleUserfs Guide Version

TivoliRIBM Tivoli Monitoring for Tivoli Enterprise ConsoleUserfs Guide Version

Components of IBM Tivoli Monitoring for Tivoli Enterprise Console . . . . . . . . . . . .2

Event Activity Class attribute group . . . . . .32

KKA_TEC_Receptn_Proc_CPU_Crit situation . .67

More information about policies . . . . . . .83

following typeface conventions: Bold v Lowercase commands and mixed case

event_distribution.KKA_REFRESH_INTERVAL=value To see the supported

include the host # dimension or DIST_BY_HOST_FALSE to exclude the host

Table 5. Monitor with custom situations

predefined workspaces included in this monitoring agent. About workspaces A

(tec_ui_server). This workspace contains the following views: 16 IBM Tivoli

Chapter 5. Attributes reference This chapter contains an overview of attributes,

26 IBM Tivoli Monitoring for Tivoli Enterprise Console: Userfs Guide

attribute. Description The managed system name of the agent. Type

attribute. Description Numeric event status value Type DisplayNumericEvent Class

Distribution By Status attribute group: Node attribute - This attribute is a key

when the condition becomes false. KKA_TEC_UI_Srvr_Proc_Down situation

KKA_TEC_Server_Proc_CPU_High situation Description CPU usage of the TEC server

Monitoring Administratorfs Guide or the Tivoli Enterprise Portal online help. c

number_events_in: INTEGERv number_events_out: INTEGERv event_count_diff:

events generated by situations on the EVENT_THROUGHPUT attribute group, Tivoli

Tivoli Enterprise Console information

Table 9. Trace log files for troubleshooting agents

File name and path

discarded. Default value is 9. v LIMIT: the maximum size, in megabytes (MB) of a

gDisk capacity planning for historical datah on page 58 describes the

http://techsupport.services.ibm.com/guides/contacts.html and click the name of

successfully. Operator response: None. KKA0006E Error purging event repository.

Appendix C. Accessibility Accessibility features help users with physical disabilities,

attribute 27 Functionality Test Message attribute 29 Functionality Test Status

attribute 28 Percent User Mode Time attribute 28 performance considerations 108

52, 56 Tivoli Enterprise Consolesituations 62, 63 workspacesdescriptions 16 list 15

Printed in USA GC32-1959-00

Das könnte Ihnen auch gefallen