t l compositeapplication manageragent for lotus domino

Tivoli® Composite Application Manager Agent for Lotus Domino

User’s Guide

Version 6.2.1

SC27-2346-00

��

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

This edition applies to IBM Tivoli Composite Application Manager Agent for Lotus Domino V6.2.1 (product number5724-V09) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2005, 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

Chapter 1. Overview of the LotusDomino agent . . . . . . . . . . . . 1IBM Tivoli Monitoring overview. . . . . . . . 1Features of the monitoring agent . . . . . . . 1Functions of the monitoring agent . . . . . . . 1New in this release . . . . . . . . . . . . 2Components of the IBM Tivoli Monitoringenvironment . . . . . . . . . . . . . . 3User interface options . . . . . . . . . . . 3

Chapter 2. Agent-specific installationand configuration information for themonitoring agent . . . . . . . . . . . 5Upgrading . . . . . . . . . . . . . . . 5Installing language packs . . . . . . . . . . 5

Windows systems. . . . . . . . . . . . 5UNIX or Linux systems. . . . . . . . . . 6

Configuring the monitoring agent after installation . 6Clearing the Domino Server password . . . . . 6Checking the Access Control List of the database 7Configuring using the Tivoli Enterprise Portal . . 7Windows configuration notes . . . . . . . . 9UNIX and Linux configuration notes . . . . . 10Configuration values . . . . . . . . . . 11Remote monitoring configuration . . . . . . 13Remote installation and configuration . . . . 13

Sending IBM Tivoli Monitoring event messagesfrom IBM Tivoli IntelliWatch (iwsditm utility) . . . 14

Using the command line to run the iwsditmprogram . . . . . . . . . . . . . . 14Using a trigger to run the iwsditm program . . 14Using a batch file to run the iwsditm program . 14

Chapter 3. Workspaces reference . . . 17About workspaces . . . . . . . . . . . . 17More information about workspaces . . . . . . 17Predefined workspaces . . . . . . . . . . 17Agent Navigator items . . . . . . . . . . 18

Lotus Domino Navigator item . . . . . . . 18Availability Navigator item . . . . . . . . 19Cluster Navigator item . . . . . . . . . 19Database Navigator item . . . . . . . . . 20Mail Navigator item . . . . . . . . . . 21Server Navigator item . . . . . . . . . . 22Sessions Navigator item . . . . . . . . . 23

Chapter 4. Attributes reference . . . . 25About attributes . . . . . . . . . . . . . 25More information about attributes . . . . . . . 25Attribute groups and attributes for the LotusDomino agent . . . . . . . . . . . . . 25Availability attribute group . . . . . . . . . 29

Domino Agent attribute group . . . . . . . . 33Domino Calendar attribute group . . . . . . . 35Domino Calendar (Superseded) attribute group . . 37Domino Command attribute group . . . . . . 39Domino Corrupt Failover DB attribute group . . . 45Domino Database attribute group . . . . . . . 46Domino Database (Superseded) attribute group . . 51Domino DB Whitespace attribute group . . . . . 56Domino Group Updates attribute group . . . . . 58Domino ICM attribute group . . . . . . . . 59Domino ICM (Superseded) attribute group . . . . 66Domino IMAP attribute group . . . . . . . . 74Domino IMAP (Superseded) attribute group . . . 77Domino LDAP attribute group . . . . . . . . 80Domino LDAP (Superseded) attribute group . . . 84Domino Log File attribute group . . . . . . . 89Domino Mail attribute group . . . . . . . . 89Domino MAIL (Superseded) attribute group . . . 96Domino Mail By Dest attribute group . . . . . 102Domino Mail By Dest (Superseded) attribute group 104Domino NET TCPIP attribute group. . . . . . 105Domino NET TCPIP (Superseded) attribute group 107Domino Replica attribute group . . . . . . . 109Domino Replica (Superseded) attribute group . . 111Domino Replica Cluster attribute group . . . . 113Domino Replica Cluster (Superseded) attributegroup . . . . . . . . . . . . . . . . 117Domino Replication attribute group . . . . . . 121Domino Server attribute group . . . . . . . 123Domino Server (Superseded) attribute group . . . 126Domino Server Cluster attribute group . . . . . 130Domino SMTP attribute group . . . . . . . 134Domino SMTP (Superseded) attribute group . . . 136Domino Tasks attribute group . . . . . . . . 138Domino Web Retriever attribute group . . . . . 139IW Mail Domain Statistics attribute group . . . . 147IW Mail Incoming Statistics attribute group . . . 148IW Mail Outgoing Statistics attribute group . . . 150IW Mail Size Statistics attribute group . . . . . 151IW Replication Delay Statistics attribute group . . 153IW Replication Statistics attribute group . . . . 154IW Server attribute group . . . . . . . . . 157IW View Performance Statistics attribute group . . 158Performance Object Status attribute group. . . . 160Disk capacity planning for historical data . . . . 163

Chapter 5. Situations reference. . . . 167About situations . . . . . . . . . . . . 167More information about situations . . . . . . 167Predefined situations . . . . . . . . . . . 168Lotus Domino Navigator item . . . . . . . . 169Availability Navigator item . . . . . . . . . 169

KGB_Domino_Serv_Avail_Crit situation . . . 169KGB_Domino_Srv_Clus_Avail_Crit situation 169KGB_Domino_Serv_Config_Crit situation . . . 170

© Copyright IBM Corp. 2005, 2009 iii

KGB_Domino_Srv_Clus_Avail_Warn situation 171Cluster Navigator item . . . . . . . . . . 171Database Navigator item . . . . . . . . . 171

KGB_Domino_Failover_Warn situation . . . . 171KGB_Domino_Whitespace_Pct_Warn situation 172KGB_Domino_DB_Size_Warn situation . . . . 172

Mail Navigator item . . . . . . . . . . . 173KGB_Domino_Mail_Dead_Warn situation . . . 173KGB_Domino_Mail_Waiting_Warn situation . . 173KGB_Domino_Mail_Dead_Warn_2 situation . . 174KGB_Domino_Mail_Waiting_Warn_2 situation 175

Server Navigator item . . . . . . . . . . 175KGB_Domino_Serv_Avail_Idx_Crit situation . . 175KGB_Domino_Serv_Sess_Drop_Crit situation 176KGB_Domino_Srv_Avl_Idx_Crit_2 situation . . 176KGB_Domino_Srv_Ses_Drop_Crit_2 situation 177KGB_Domino_SMTP_Task_Warn situation. . . 177KGB_Domino_Rep_Miss_Crit situation . . . . 178

Sessions Navigator item . . . . . . . . . . 178

Chapter 6. Take Action commandsreference . . . . . . . . . . . . . 179About Take Action commands. . . . . . . . 179More information about Take Action commands 179Predefined Take Action commands . . . . . . 179

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

Chapter 8. Troubleshooting . . . . . 183Gathering product information for IBM SoftwareSupport . . . . . . . . . . . . . . . 183Built-in troubleshooting features . . . . . . . 183Problem classification. . . . . . . . . . . 184

Trace logging . . . . . . . . . . . . . 184Overview of log file management . . . . . 184Examples of trace logging . . . . . . . . 185Principal trace log files . . . . . . . . . 186Setting RAS trace parameters . . . . . . . 191

Problems and workarounds . . . . . . . . 193Installation and configuration troubleshooting 193Remote deployment troubleshooting . . . . 197Agent troubleshooting . . . . . . . . . 197Workspace troubleshooting . . . . . . . . 201Situation troubleshooting . . . . . . . . 203Take Action commands troubleshooting . . . 206

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

Message format . . . . . . . . . . . 207Lotus Domino agent messages. . . . . . . 207

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

Appendix B. Documentation library 229Lotus Domino agent library . . . . . . . . 229Prerequisite publications. . . . . . . . . . 229Related publications . . . . . . . . . . . 230Other sources of documentation . . . . . . . 230

Appendix C. Accessibility . . . . . . 231Navigating the interface using the keyboard . . . 231Magnifying what is displayed on the screen . . . 231

Appendix D. Notices . . . . . . . . 233Trademarks . . . . . . . . . . . . . . 234

Index . . . . . . . . . . . . . . . 237

iv Lotus Domino agent: User’s Guide

Tables

1. Capacity planning for historical data loggedby component Lotus Domino agent . . . . 163

2. Information to gather before contacting IBMSoftware Support . . . . . . . . . . 183

3. Trace log files for troubleshooting agents 1874. Problems and solutions for installation and

configuration . . . . . . . . . . . 1935. General problems and solutions for

uninstallation . . . . . . . . . . . 1966. Remote deployment problems and solutions 197

7. Agent problems and solutions . . . . . . 1988. Workspace problems and solutions . . . . 2019. General situation problems and solutions 203

10. Problems with configuring situations that yousolve in the Situation Editor . . . . . . 204

11. Problems with configuration of situations thatyou solve in the Workspace area . . . . . 205

12. Take Action commands problems andsolutions . . . . . . . . . . . . . 206

© Copyright IBM Corp. 2005, 2009 v

vi Lotus Domino agent: User’s Guide

Chapter 1. Overview of the Lotus Domino agent

IBM® Tivoli® Composite Application Manager Agent for Lotus® Domino® V6.2.1 isa component of ITCAM for Applications, Version 6.2.2, or later.

The Lotus Domino agent provides you with the capability to monitor LotusDomino. This chapter provides a description of the features, components, andinterface options for the Lotus Domino agent.

IBM Tivoli Monitoring overviewIBM Tivoli Monitoring is the base software for the Lotus Domino agent. IBM TivoliMonitoring provides a way to monitor the availability and performance of all thesystems in your enterprise from one or several designated workstations. It alsoprovides useful historical data that you can use to track trends and to troubleshootsystem problems.

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

situations or custom situations.v Establish your own performance thresholds.v Trace the causes leading to an alert.v Gather comprehensive data about system conditions.v Use policies to perform actions, schedule work, and automate manual tasks.

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

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

Features of the monitoring agentThe Lotus Domino agent software can identify and notify you of commonproblems with the application that it monitors. The software includes the followingfeatures:v Monitoringv Data gatheringv Event management for IntelliWatch® events

Functions of the monitoring agentThe Lotus Domino agent provides the following functions:

Resource monitoringCollects monitoring information for Domino statistics, IntelliWatch statisticsand events, and server status. You can monitor Domino servers remotelythrough the local Domino server. Servers in the same domain or

© Copyright IBM Corp. 2005, 2009 1

cross-certified in a different domain can be remotely monitored. Thisincludes the ability to remotely monitor Domino Servers on platforms notcurrently supported.

Availability monitoringProvides availability information separately for the monitored DominoServers. The agent pings the application to determine whether the DominoServer is available.

New in this releaseFor version 6.2.1 of the Lotus Domino agent, the following enhancements havebeen made since version 6.1, including the fix packs:v Support for larger integersv New attribute groups:

– Domino Command– Domino Corrupt Failover DB– Domino DB Whitespace– Domino Group Updates– Domino Log File– Domino Replication– Domino Web Retriever

v New attribute groups support larger integers:– Domino Calendar– Domino Database– Domino ICM– Domino IMAP– Domino LDAP– Domino Mail– Domino Mail By Dest– Domino NET TCPIP– Domino Replica– Domino Replica Cluster– Domino Server– Domino SMTP

v New or changed attributes in the following attribute groups:– Domino Tasks– Domino Server Cluster

v New predefined situations:– KGB_Domino_Rep_Miss_Crit– KGB_Domino_Failover_Warn– KGB_Domino_DB_Size_Warn– KGB_Domino_Whitespace_Pct_Warn– KGB_Domino_Mail_Dead_Warn_2– KGB_Domino_Mail_Waiting_Warn_2– KGB_Domino_Srv_Avl_Idx_Crit_2– KGB_Domino_Srv_Ses_Drop_Crit_2

v New workspace and views:

2 Lotus Domino agent: User’s Guide

– Database Status- Database Corrupt Status view- Database Whitespace Status view

v Updated kgb.baroc file to support TEC event mappingv Ability to check for database corruption in .nsf databases, mail.box databases

and viewsv Domino Cluster Server Availability (failover event monitoring)v Domino Task Monitoringv Domino Statistic Monitoringv Domino Server Log Monitoring for log.nsf and notes.logv Monitors cluster server availabilityv Domino database and mail.box whitespace monitoringv Removed dependency on IntelliWatchv Monitors SMTP port to ensure active listeningv Monitors for the Max Hop Count Exceeded Error in the notes.logv Monitors user groups for adds or deletes

Components of the IBM Tivoli Monitoring environmentAfter you install and set up the Lotus Domino agent, you have an environmentthat contains the client, server, and monitoring agent implementation for IBMTivoli 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 analysisof data from the monitoring agents. The Tivoli Enterprise Portal Server is thecentral repository for all user data.

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

v Tivoli Enterprise Monitoring Agent, Lotus Domino agent (one or more instancesof the monitoring agent). The instances communicate with the systems orsubsystems that you want to monitor. This monitoring agent collects anddistributes data to a Tivoli Enterprise Portal Server.

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

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

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

Chapter 1. Overview of the Lotus Domino agent 3

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

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

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

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


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

Before installing and configuring the agent, make sure your environment meets therequirements for the Lotus Domino agent. See the Prerequisites topic for the agentin the IBM Tivoli Composite Application Manager for Applications informationcenter at http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.2/welcome.htm.

To install and configure the Lotus Domino agent, use the procedures for installingmonitoring agents in the IBM Tivoli Monitoring Installation and Setup Guide alongwith the agent-specific information in this chapter.

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

UpgradingOn Windows, for local upgrades, agent instances are upgraded automatically.During remote upgrades, the previous agent instances are lost. A tool is providedto restore the instances. Run %CANDLE_HOME%\InstallITM\updategbinstance.bat torestore and upgrade the instances.

On AIX, Solaris and Linux, agent instances are upgraded automatically.

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

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

program.2. Select the language of the installer and click OK.3. Click Next on the Introduction panel.4. Click Add/Update and click Next.5. Select the folder in which the National Language Support package

(NLSPackage) files are located.

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

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

Note: Hold down the Ctrl key for multiple selections.7. Select the languages that you want to install and click Next.8. Examine the installation summary page and click Next to begin installation.9. Click Finish after installation completes to exit the installer.


http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.2/welcome.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.2/welcome.htm

10. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server,and Eclipse Help Server if any of these components are installed.

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

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

2. Mount the language pack CD to the temporary directory you just created.3. Run the following command to launch the installation program:

cd dir_namelpinstaller.sh -c ITM Home Directory

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

4. Select the language of the installer and click OK.5. Click Next on the Introduction panel.6. Click Add/Update and click Next.7. Select the folder in which the National Language Support package

(NLSPackage) files are located.

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

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

Note: Hold down the Ctrl key for multiple selections.9. Select the languages that you want to install and click Next.

10. Examine the installation summary page and click Next to begin installation.11. Click Finish after installation completes to exit the installer.12. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server,

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

Configuring the monitoring agent after installationIn addition to the installation and configuration information in the IBM TivoliMonitoring Installation and Setup Guide, use the information in this section to installand configure Lotus Domino agent.

You can configure an instance of the Lotus Domino agent remotely (tacmdcommand), locally on the computer (itmcmd command on UNIX® only), by usingthe Tivoli Enterprise Portal, or by using the Manage Tivoli Enterprise MonitoringServices window. See the IBM Tivoli Monitoring Installation and Setup Guide forinformation about starting these interfaces.

Clearing the Domino Server passwordOn all supported operating systems, and for both local and remote configuration,you must clear the password on the Domino Server being used by the agent forthe agent to start. You can clear the password at any time before starting the LotusDomino agent.

Use the following steps to clear the password:1. Copy your server ID file, not the user ID file, to a Windows computer that has

a Notes® client.


Each Domino server has a server ID file, and if the password of the server IDfile is not cleared the Lotus Domino agent cannot be started.

2. From the Notes client, click File > Security > Switch ID, and select the serverID file.

3. Click File > Security > User Security.4. In ″Security Basics″, select Change Password.5. In the ″Change Your Password″ window, select No Password.6. Confirm the change, and click OK to exit.7. Copy your server ID back to your server computer. On UNIX and Linux, make

sure the ID file is set to the correct user, group, and permissions.

Checking the Access Control List of the databaseTo use Database Corruption monitoring or the Database Space Usage monitoringfeature, the Domino server ID must be in the Access Control List of the databaseyou want to monitor. To check if the Domino server ID is in the Access ControlList, configure and start the Lotus Domino agent first, then check table DatabaseStatus > Database Corruption and Failover in the Tivoli Enterprise Portal. If theState column is Operation not authorized or Access not authorized, that meansthe Domino server ID is not in the Access Control List of the database. To add theDomino server ID to the Access Control List, follow the instructions below:1. Start the Domino Administrator client.2. From the Domino Administrator Server pane, select the server that stores the

databases.3. Click Files and select one or more databases from the Domino data directory.4. Click Tools >Database >Manage ACL.5. Click Add.6. Type the entry, or select it from the Domino Directory by clicking the button

next to the list box. Select Server as the user type, and select an access level.The access level should be at least at Reader level.

7. Click OK.

Configuring using the Tivoli Enterprise PortalConfiguration of an instance of the monitoring agent can be done remotely(tacmd), locally on the machine (itmcmd), or using the Tivoli Enterprise Portal.This configuration requires values to be defined for the agent to operate. Thefollowing fields are defined for this agent:

InstanceThis field uniquely defines the name seen on the monitoring server andportal server for the Domino Server being monitored. Usually the instancename is based off the Domino Server name or domain so that the user caneasily identify the Domino Server being monitored.

Monitored Domino Server NameThis field is the canonical or abbreviated Domino Server name for whichyou want to monitor. This name can be a local server where the agent isinstalled or a remote server not located on this machine.

Local hostname or IP address for Intelliwatch EventsThis field is optional. Use this field if Intelliwatch events are going to bereceived by the monitoring agent. If Intelliwatch events are going to bereceived by the monitoring agent the hostname or IP address of the local

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

machine the monitoring agent is installed on must be entered. Thishostname or IP address must have access outside the machine to thenetwork.

Local port for Intelliwatch EventsThis field is optional, but must be defined if the above hostname and IPaddress is used. This port, which can be any port number that is not usedby other processes, is used for a TCP/IP socket connection to receiveIntelliwatch events. This socket must be open to the network and notblocked by any firewall.

Full directory path to the local notes.ini fileInstalling the Domino monitoring agent on a machine requires you tochoose a local notes.ini file to use so that the monitoring agent can issueAPI requests. The full path does not include the notes.ini file name.

The interval to check databaseThis field indicates the interval to check the databases. The default value is3600, which means that the database check will runs every 3600 seconds. Ifthe field is set to 0, the database check will never run.

The databases or database directories to checkThis field is optional. The default value is *, which means all the databaseswill be checked. The field can be used to specify which databases ordatabase directories to check. Each path in the field, separated bysemicolon, is relative to the Domino data directory. The path can be aDomino database, a normal Domino directory, or a Domino directory with*. For example, names.nsf; mail; mail2/* means the database names.nsf,all the databases in mail, and all the databases in mail2 including itssubdirectories will be checked.

The databases or database directories to excludeThis field is optional. The field can be used to specify which databases ordatabase directories to exclude. Each entry in the field, separated bysemicolon, is relative to the Domino data directory. The path can be aDomino database, a normal Domino directory, or a Domino directoy with*. If a database is excluded, it will not be checked for corruption, failoveror space usage. This means the Database Status workspace and anysituation you set up will also be exclude automatically. For example,names.nsf; mail; mail2/* means the database names.nsf, all the databasesin mail, and all the databases in mail2 including its subdirectories will notbe checked.

The configuration file to define which views of a database to checkThis field is optional. It is a fully qualified configuration file path of thedatabase view mapping. In this configuration file, you can define whichviews of a database will be checked. By default, only the default view willbe checked. Use the following rules for setting up a configuration file:1. There should be no space characters at the beginning of each line.2. A line that begins with # is a comment.3. Definition line is in format PATH=VIEW[,VIEW]*. Where the left side is

the database path, and the right side is the database view list in whicheach view is separated by a comma. There are three kinds of databasepaths:

* All the nsf databases on the Domino server

test All the nsf databases in test directory, not includingsubdirectories


test\* All the nsf databases in test directory, includingsubdirectories

Configuration file examples:# test1.nsftest1.nsf = view1, view2, view3# the database directorydir1 = view_dir11, view_dir12# the directory including its subdirectorydir2/* = view_dir21, view_dir22

Note: The path separator can be either \ or /

If there are multiple definitions for a database, only the first one will beused to check the database views. For example, in the configuration filethere are three definitions for the database readme:help/readme.nsf = View1help/readme.nsf = View2, View3help/readme.nsf = View4

Only View1 of readme.nsf will be checked.

Semicolon separated database replication strings to includeStrings separated by semicolons. Only reports indications that havedatabase events and events attributes that include these strings.

All replication events are collected. This includes manual, hit, and missedreplication events. For each replication event found, the string is scannedto see if it matches one of the include or exclude strings. If it matches theinclude string it is kept in the returned set of rows. If it matches theexclude string it is eliminated from the returned set of rows. If no includeor exclude strings are configured, all replication events are returned.

Semicolon separated database replication strings to excludeStrings separated by semicolons. Only reports indications that havedatabase events and events attributes that do not include these strings.

All replication events are collected. This includes manual, hit, and missedreplication events. For each replication event found, the string is scannedto see if it matches one of the include or exclude strings. If it matches theinclude string it is kept in the returned set of rows. If it matches theexclude string it is eliminated from the returned set of rows. If no includeor exclude strings are configured, all replication events are returned.

Monitored Domino Server Log FileName of log file to be monitored with fully qualified path.

Log file errors to search forVertical bar separated search strings. The default search strings can beupdated or additional search strings added with | new_search_string.

Note: If you change the search string the Lotus Domino agent must be restartedfor the new string to be included in the search.

Windows configuration notesAfter installing the Lotus Domino agent and before configuring an instance, youmust reboot the Windows computer to update the system environment variables.

See “Configuration values” on page 11 for the values required to configure theLotus Domino agent.


See “Remote installation and configuration” on page 13 for information aboutconfiguring the Lotus Domino agent remotely.

When starting the Domino Server on Windows, the server must be started as aService so the monitoring agent and the Domino Server can be in the same processtree.

Make sure that the notes.ini file contains the NotesProgram and the Directorykeywords. The Lotus Domino agent fails to start if the notes.ini file pointed to bythe configuration parameter, Full path to the local notes.ini file, does not containthe NotesProgram keyword. The NotesProgram keyword is the path to the LotusDomino base directory. The Directory keyword is used to determine the path tothe Domino Serverlock file.

Changing the ping interval for determining the status of theDomino Server on WindowsThe Lotus Domino agent determines the status of the Domino Server by issuingthe NSPingServer API call. This API call runs by default every 30 seconds. If youwant to change the default 30 second interval, you can change theKGB_PING_INTERVAL value using the Tivoli Enterprise Monitoring ServicesConsole, right-clicking, and selecting Advanced > Edit ENV File for the instance tobe modified. The new value must be greater than the default of 30 seconds.

UNIX and Linux configuration notesSee “Configuration values” on page 11 for the values required to configure theLotus Domino agent.

Make sure that the notes.ini file contains the NotesProgram keyword. The LotusDomino agent fails to start if the notes.ini file pointed to by the configurationparameter, Full path to the local notes.ini file, does not contain the NotesProgramkeyword. The NotesProgram keyword is the path to the Lotus Domino basedirectory.

Starting the Lotus Domino agentOn UNIX and Linux operating systems, you must configure and start the LotusDomino agent as the root user. When starting the monitoring agent as root, theinitialization process verifies that the correct softlinks were established in theDomino install directory, and then switches the process to the Notes User IDdefined by the notes.ini file. If the correct softlinks were not established, then theinitialization process creates the necessary softlinks. The final monitoring agentprocess runs as the Notes User ID when communicating with the Notes Server.

See “Remote installation and configuration” on page 13 for information aboutconfiguring the agent remotely.

Note: When using itmcmd commands with multi-instance agents, you mustinclude the -o parameter as follows to start or stop the instance:itmcmd agent -o instance start|stop gb

Changing the ping interval for determining the status of theDomino Server on UNIX or LinuxThe Lotus Domino agent determines the status of the Domino Server by issuingthe NSPingServer API call. This API call runs by default every 30 seconds. Thisping interval can be changed by changing the {instance


name}|KGB_PING_INTERVAL|30| value found in the kgbenv file located in the$CANDLEHOME/config/.ConfigData directory. The new value must be greaterthan the default of 30 seconds.

Uninstalling the monitoring agentTo make sure that configuration softlinks created in the Domino Server installdirectory are removed, you must use the kgbuninstall.sh script to uninstall themonitoring agent. Run the kgbuninstall.sh script that is located at$CANDLEHOME/binArch/gb/bin/kgbuninstall.sh. The value for binArch can be foundby running the cinfo -i command.

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

The configuration fields are not checked for validity until the Lotus Domino agentis started. Therefore, any errors in the fields, such as incorrect path or server namecause the monitoring agent data collection process to fail to start. When thiscondition occurs, no data is returned to the workspaces or the Availabilityworkspace shows incorrect Domino Server status. To resolve the problem look inthe log files for error messages to determine which field was incorrect and causingthe failure. Check the kgbstart_{instance name}.log file first, then check the uniqueinstance kgbclient log file. See “Trace logging” on page 184 for the name of thekgbclient.exe log.

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

Domino Server Configuration (config)Null Description for section.

This section is always present.

This section defines information that applies to the agent.

The databases or database directories not to checkThe Domino database paths separated by a semicolon that will notbe checked.

The type is string.

This value might be optional.

The databases or database directories to checkThe Domino database paths separated by a semicolon that will bechecked.

The type is string.


The interval to check databaseThe interval in which the checking of database corruption anddatabase usage runs.

The type is string.

This value is required.


The configuration file to define which views of a database are to checkThe full path to the configuration file of database view mapping.

The type is string.


Local hostname or IP address for Intelliwatch EventsThe hostname or IP address of the local computer on which theagent is installed.

The type is string.


Local port for IntelliWatch EventsThe port used for a TCP/IP socket connection to receiveIntelliWatch events.

The type is string.


Log file errors to search forEach ICU regular expression separated by a vertical bar will besearched for.

The type is string.


Monitored Domino Server Log FileThe name of the log file to be monitored with fully qualified path.

The type is string.


Semicolon separated database replication strings to excludeOnly reports indications of database events and events attributeswithout these strings.

The type is string.


Semicolon separated database replication strings to includeOnly reports indications of database events and events attributesincluding these strings.

The type is string.


Full path to the local notes.ini fileThe full path to the local notes.ini file.

The type is string.


Monitored Domino Server NameThe canonical or abbreviated Domino Server name that you wantto monitor.

The type is string.



Remote monitoring configurationNote the following information for remote monitoring configuration:1. To monitor a Domino server remotely:

The local Domino server must be in the same Domino domain as the remoteDomino server.–OR–The local Domino server must be cross-certified with the remote Dominoserver if they are not in the same Domino domain.

2. A local Domino installation is required on the computer where the LotusDomino agent resides. This is because the Lotus Domino agent requiresDomino libraries and notes.ini to initialize runtime.

3. There are no differences between configuring remote monitoring and localmonitoring. To configure remote monitoring, specify the remote Domino servername in the configuration fields; specify the other configuration fields with thesame information as local monitoring.

For example, if Domino server serverA/ibm is on computer A, and the LotusDomino agent is deployed on computer B, a Domino server must be installed oncomputer B to provide runtime libraries and notes.ini. The Domino server oncomputer B must be in the same domain as serverA/ibm or cross-certified if not inthe same domain. During agent configuration, serverA/ibm must be used in theserver name field, while the notes.ini path is the path of notes.ini on computer B,not the remote Domino’s notes.ini path.

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

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

On Windows, if the Lotus Domino agent is installed remotely, you must run%CANDLE_HOME%\InstallITM\updategbinstance.bat from the command line.You can run it either before or after you configure a Lotus Domino agent instance.

The following command is an example of remote configuration for Windowsoperating systems:tacmd addSystem -t GB -n Primary:sample.node.name:NT-p config.KGB_CHECK_DB_EXCLUDE_PATH=valueconfig.KGB_CHECK_DB_INCLUDE_PATH=valueconfig.KGB_CHECK_DB_INTERVAL=valueconfig.KGB_CHECK_DB_VIEW_CONFIG_FILE=valueconfig.KGB_IWHOSTNAME=valueconfig.KGB_IWPORT=valueconfig.KGB_LOGERROR=valueconfig.KGB_LOGFILE=valueconfig.KGB_LOG_EXCLUDE=valueconfig.KGB_LOG_INCLUDE=valueconfig.KGB_NOTESINIPATH=valueconfig.KGB_SERVER=valueINSTANCE="inst1”


Sending IBM Tivoli Monitoring event messages from IBM TivoliIntelliWatch (iwsditm utility)

To send IBM Tivoli Monitoring event messages from IBM Tivoli IntelliWatch on aLotus Domino Server, IBM Tivoli IntelliWatch, Version 27.39 or later must beinstalled on the Domino Server.

The iwsditm IntelliWatch program sends IBM Tivoli Monitoring event messages tothe agent that is monitoring the Domino Server. Like other IntelliWatch utilities,the iwsditm program can be run from the command line, a trigger, or a batch fileto be called by IntelliWatch Advanced ServerWatch or IntelliWatch CrashDetection.

Using the command line to run the iwsditm programTo run the iwsditm program from the command line, use the following command:iwsditm /M:"message string" [/S:severity] [/H:hostname] [/P:port]

Where:

/S:severityPriority of the message, optional: 1 = information (default), 2 = warning, 3= alarm.

/H:hostnameHost name for the IBM Tivoli Monitoring agent, optional

/P:port Port for the IBM Tivoli Monitoring agent, optional. The port is the sameport specified in configuring the agent. See the information about the Localport for IntelliWatch Events field in the “Configuration values” on page 11section of this chapter.

Example:iwsditm /M:"Server Not Responding"

Using a trigger to run the iwsditm programWhen configuring a trigger, select the Send ITM Event command from thecommand list. When the trigger fires, this command sends the designated messageto the Lotus Domino agent.1. From the IBM Tivoli IntelliWatch console, Monitor section, "Command" tub,

select the "Create New Command" tool bar.2. Select Program from the list.3. In the Name field, type Send ITM Event.4. In the Program section, type iwsditm.5. In the Parameter field, type /M:MESSAGE.6. Save the command.

Using a batch file to run the iwsditm programUse the following procedures to run the iwsditm program from a batch file thatcan be called by Advanced ServerWatch or Crash Detection.

Called from Advanced ServerWatchTo use the iwsditm program from a batch file that is called from AdvancedServerWatch, perform the following steps:


1. Create a batch file that contains the iwsditm command and uses %1 to pass theAdvanced ServerWatch message. For example:iwsditm /M:%1

2. From the IntelliWatch console Advanced ServerWatch tab, open or create anaction profile by clicking Hub > Profiles > Actions to open the Modify ActionProfile window.

3. In the Notification section, select the Start Program check box.4. In the Program to Run field, type the location of the batch file.5. Click OK.

Called from Crash DetectionTo use the iwsditm program from a batch file that is called from Crash Detection,perform the following steps:1. Create a batch file as described in “Called from Advanced ServerWatch” on

page 14.2. From the IntelliWatch console Parameter Configuration tab, click Monitor >

Crash Detection.3. In the Value column enter the information in the following table:

Name Value

Start Program(1) 1

Start Program(2) 1

Program(1) Batch file location, for example:

C:\Tivoli\IntelliWatch\COMMON\senditm.bat

Program(2) Batch file location, for example:

C:\Tivoli\IntelliWatch\COMMON\senditm.bat

For Start Program(1) and Start Program(2), the value of 1 enables the batch fileprogram.


Chapter 3. Workspaces reference

This chapter contains an overview of workspaces, references for detailedinformation about workspaces, and descriptions of the predefined workspacesincluded in this monitoring agent.

About workspacesA workspace is the working area of the Tivoli Enterprise Portal applicationwindow. At the left of the workspace is a Navigator that you use to select theworkspace you want to see. As part of the application window, the right side ofthe status bar shows the Tivoli Enterprise Portal server name and port number towhich the displayed information applies, and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed.When you right-click a Navigator item, a menu that includes a Workspace item isdisplayed. The Workspace item contains a list of workspaces for that Navigatoritem. Each workspace has at least one view. Some views have links to otherworkspaces.

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

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

More information about workspacesFor more information about creating, customizing, and working with workspaces,see the IBM Tivoli Monitoring User’s Guide.

For a list of the predefined workspaces for this monitoring agent and a descriptionof each workspace, refer to the Predefined workspaces section in this chapter andthe information in that section for each individual workspace.

Some attribute groups for this monitoring agent might not be represented in thepredefined workspaces or views for this agent. For a full list of the attributegroups, see the Attributes reference section.

Predefined workspaces

The Lotus Domino agent provides the following predefined workspaces, which areorganized by Navigator item.v Lotus Domino Navigator item

– Lotus Domino workspace– Lotus Domino(Superseded) workspace

v Availability Navigator item– Availability workspace– Availability(Superseded) workspace


v Cluster Navigator item– Cluster workspace– Cluster(Superseded) workspace

v Database Navigator item– Database workspace– Database Status workspace– Database(Superseded) workspace– IW Replication workspace

v Mail Navigator item– IW Mail workspace– Mail workspace– Mail(Superseded) workspace

v Server Navigator item– IW Server workspace– Server workspace– Server(Superseded) workspace

v Sessions Navigator item– Session(Superseded) workspace– Sessions workspace

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

Lotus Domino Navigator itemLotus Domino workspace

The Lotus Domino workspace displays the following information: Dominomail statistics, server statistics, server availability, and tasks.

This workspace contains the following views:

Mail StatisticsMail delivery, transfer rates, and mail count statistics for Dominomail.

Server StatisticsServer availability index and threshold, transactions, and users forDomino Servers.

Server AvailabilityDomino Server and cluster server status and functionality message.The server status values can be OK, NOT_RUNNING,DOESNT_EXIST or INSUFFICIENT_USER_AUTHORITY.

Tasks Domino task name and status.

Lotus Domino(Superseded) workspaceThe Lotus Domino workspace displays Domino mail statistics, serverstatistics, server availability, and tasks.



Mail Statistics(Superseded)Mail delivery, transfer rates, and mail count statistics for Dominomail.

Server Statistics(Superseded)Server availability index and threshold, transactions, and users forDomino Servers.

Server Availability(Superseded)Domino Server and cluster server status and functionality message.The server status values can be OK, NOT_RUNNING,DOESNT_EXIST or INSUFFICIENT_USER_AUTHORITY.

Tasks(Superseded)Domino task name and status.

Availability Navigator itemAvailability workspace

The Availability workspace displays user, transactions, and availabilitystatistics for servers.


Server AvailabilityDomino Server and cluster server status and functionality message.The server status values can be OK, NOT_RUNNING,DOESNT_EXIST or INSUFFICIENT_USER_AUTHORITY.

Server StatisticsServer availability index, threshold, transactions, and users forDomino Servers.

Data Collection StatusStatus of the performance objects used for data collection.

Availability(Superseded) workspaceThe Availability workspace displays user, transactions, and availabilitystatistics for servers.


Server Availability(Superseded)Domino Server and cluster server status and functionality message.The server status values can be OK, NOT_RUNNING,DOESNT_EXIST or INSUFFICIENT_USER_AUTHORITY.

Server Statistics(Superseded)Server availability index, threshold, transactions, and users forDomino Servers.

Data Collection Status(Superseded)Status of the performance objects used for data collection.

Cluster Navigator itemCluster workspace

The Cluster workspace provides statistics for connections, threads,availability, and requests for Domino clusters.


Chapter 3. Workspaces reference 19

Internet Cluster Manager StatisticsInternet cluster manager connections, threads, availability index,and requests statistics for the Domino Server.

Replication Cluster StatisticsReplica cluster document, KB sent, and KB received statistics forthe Domino Server.

Server Cluster StatisticsServer cluster request, redirect, and probe statistics for the DominoServer.

Cluster(Superseded) workspaceThe Cluster workspace provides statistics for connections, threads,availability, and requests for Domino clusters.


Internet Cluster Manager StatisticsInternet cluster manager connections, threads, availability index,and requests statistics for the Domino Server.

Replication Cluster Statistics(Superseded)Replica cluster document, KB sent, and KB received statistics forthe Domino Server.

Server Cluster Statistics(Superseded)Server cluster request, redirect, and probe statistics for the DominoServer.

Database Navigator itemDatabase workspace

The Database workspace provides database cache, buffer pool, and Notesreplication statistics for the Domino Server.


Notes ReplicationNotes replication statistics for Lotus Domino.

Replica StatisticsReplication statistics for Lotus Domino.

Database StatisticsDatabase cache, buffer pool, and Notes replication statistics for theDomino Server.

Database Status workspaceThe Database Status workspace provides database space usage, corruptionand failover information for the Domino Server.


Database Space UsageThe table provides database space usage information for theDomino Server.

Database Corruption and FailoverThe table provides database corruption, view corruption, andfailover statistics for the Domino server.


Database(Superseded) workspaceThe Database workspace provides database cache, buffer pool, and Notesreplication statistics for the Domino Server.


Notes Replication(Superseded)Notes replication statistics for Lotus Domino.

Replica Statistics(Superseded)Replication statistics for Lotus Domino.

Database Statistics(Superseded)Database cache, buffer pool, and Notes replication statistics for theDomino Server.

IW Replication workspaceThe IW Replication workspace provides IBM Tivoli IntelliWatch replicationstatistics for the Domino Server. This workspace only has data ifIntelliWatch is installed.


Replication StatisticsReplication statistics for the Domino Server, including thefollowing: KB sent and received, counts, and documentstransferred.

Replication Delay StatisticsReplication delay sent and received statistics for the DominoServer.

Mail Navigator itemIW Mail workspace

The IW Mail workspace displays statistics for IBM Tivoli IntelliWatch mail.This workspace only has data if IntelliWatch is installed.


Mail Domain StatisticsMail count statistic for IBM Tivoli IntelliWatch.

Mail Incoming StatisticsIncoming mail minimum, maximum, average, and count statisticsfor IBM Tivoli IntelliWatch.

Mail Size StatisticsMail maximum, average, and count statistics for IBM TivoliIntelliWatch.

Mail Outgoing StatisticsOutgoing mail count and volume statistics for IBM TivoliIntelliWatch.

Mail workspaceThe Mail workspace displays statistics for Domino mail and the Dominocalendar.


Mail By DestinationMail by destination that was transferred, delivered, and routedstatistics for Domino.


Mail FailuresDead mail, total, and transfer failures for Domino.

Calendar StatisticsCalendar appointments, reservations, resources, and user statisticsfor Domino.

Mail StatisticsMail delivery, transfer rates, and mail count statistics for Domino.

Mail(Superseded) workspaceThe Mail workspace displays statistics for Domino mail and the Dominocalendar.


Mail By Destination(Superseded)Mail by destination that was transferred, delivered, and routedstatistics for Domino.

Mail Failures(Superseded)Dead mail, total, and transfer failures for Domino.

Calendar Statistics(Superseded)Calendar appointments, reservations, resources, and user statisticsfor Domino.

Mail Statistics(Superseded)Mail delivery, transfer rates, and mail count statistics for Domino.

Server Navigator itemIW Server workspace

The IW Server workspace provides events and view percent understatistics for IBM Tivoli IntelliWatch servers. This workspace only has dataif IntelliWatch is installed.


Server MessagesEvent message priority and server message for IBM TivoliIntelliWatch.

View PerformanceResponse time for Notes database views.

Server workspaceThe Server workspace displays user, agent runs, transactions, andavailability statistics for servers.


Server UsersPeak users, count, and users active for 30 minutes on the DominoServer.

Server StatisticsServer availability index, threshold, transactions, and users forDomino Servers.

Agent StatisticsDaily agent runs and denials statistics.


Server(Superseded) workspaceThe Server workspace displays user, agent runs, transactions, andavailability statistics for servers.


Server Users(Superseded)Peak users, count, and users active for 30 minutes on the DominoServer.

Server Statistics(Superseded)Server availability index, threshold, transactions, and users forDomino Servers.

Agent Statistics(Superseded)Daily agent runs and denials statistics.

Sessions Navigator itemSession(Superseded) workspace

The Sessions workspace displays statistics for connections, tasks, threads,and KB that are sent and received.


SMTP Statistics(Superseded)SMTP connections and KB statistics that are sent and received.

LDAP Statistics(Superseded)LDAP session connections, tasks, threads, and KB statistics that aresent and received.

NET TCPIP Statistics(Superseded)NET TCPIP connections and KB statistics that are sent andreceived.

IMAP Statistics(Superseded)IMAP connections, tasks, threads, and KB statistics that are sentand received.

Sessions workspaceThe Sessions workspace displays statistics for connections, tasks, threads,and KB that are sent and received.


SMTP StatisticsSMTP connections and KB statistics that are sent and received.

LDAP StatisticsLDAP session connections, tasks, threads, and KB statistics that aresent and received.

NET TCPIP StatisticsNET TCPIP connections and KB statistics that are sent andreceived.

IMAP StatisticsIMAP connections, tasks, threads, and KB statistics that are sentand received.


Chapter 4. Attributes reference

This chapter contains an overview of attributes, references for detailed informationabout attributes, and descriptions of the attributes for each attribute groupincluded in this monitoring agent.

About attributesAttributes are the application properties being measured and reported by the LotusDomino agent.

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

Attributes are displayed in chart and table views. The chart and table views usequeries to specify which attribute values to request from a monitoring agent.You use the Query editor to create a new query, modify an existing query, orapply filters and set styles to define the content and appearance of a view basedon an existing query.

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

More information about attributesFor more information about using attributes and attribute groups, see the IBMTivoli Monitoring User’s Guide.

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

Attribute groups and attributes for the Lotus Domino agentThis monitoring agent contains the following attribute groups. The table namedepends on the maximum table name limits of the target database being used forTivoli Data Warehouse. If the maximum name is 30 characters, then any warehousetable name longer than 30 characters is shortened to the table name.v Attribute group name: Availability

– Table name: KGBAVAIL– Warehouse table name: KGB_AVAILABILITY or KGBAVAIL

v Attribute group name: Domino Agent– Table name: KGBDAGNT– Warehouse table name: KGB_DOMINO AGENT or KGBDAGNT

v Attribute group name: Domino Calendar– Table name: KGBDCAL64


– Warehouse table name: KGB_DOMINO CALENDAR or KGBDCAL64v Attribute group name: Domino Calendar (Superseded)

– Table name: KGBDCAL– Warehouse table name: KGB_DOMINO CALENDAR (SUPERSEDED) or

KGBDCALv Attribute group name: Domino Command

– Table name: KGBDCMD– Warehouse table name: KGB_DOMINO COMMAND or KGBDCMD

v Attribute group name: Domino Corrupt Failover DB– Table name: KGBDCFD– Warehouse table name: KGB_DOMINO CORRUPT FAILOVER DB or

KGBDCFDv Attribute group name: Domino Database

– Table name: KGBDDB64– Warehouse table name: KGB_DOMINO DATABASE or KGBDDB64

v Attribute group name: Domino Database (Superseded)– Table name: KGBDDB– Warehouse table name: KGB_DOMINO DATABASE (SUPERSEDED) or

KGBDDBv Attribute group name: Domino DB Whitespace

– Table name: KGBDDBW– Warehouse table name: KGB_DOMINO DB WHITESPACE or KGBDDBW

v Attribute group name: Domino Group Updates– Table name: KGBDGU– Warehouse table name: KGB_DOMINO GROUP UPDATES or KGBDGU

v Attribute group name: Domino ICM– Table name: KGBDICM64– Warehouse table name: KGB_DOMINO ICM or KGBDICM64

v Attribute group name: Domino ICM (Superseded)– Table name: KGBDICM– Warehouse table name: KGB_DOMINO ICM (SUPERSEDED) or KGBDICM

v Attribute group name: Domino IMAP– Table name: KGBDIMAP64– Warehouse table name: KGB_DOMINO IMAP or KGBDIMAP64

v Attribute group name: Domino IMAP (Superseded)– Table name: KGBDIMAP– Warehouse table name: KGB_DOMINO IMAP (SUPERSEDED) or KGBDIMAP

v Attribute group name: Domino LDAP– Table name: KGBDLDAP64– Warehouse table name: KGB_DOMINO LDAP or KGBDLDAP64

v Attribute group name: Domino LDAP (Superseded)– Table name: KGBDLDAP– Warehouse table name: KGB_DOMINO LDAP (SUPERSEDED) or

KGBDLDAPv Attribute group name: Domino Log File

– Table name: KGBKGBLOG0


– Warehouse table name: KGB_DOMINO LOG FILE or KGBKGBLOG0v Attribute group name: Domino Mail

– Table name: KGBDMAIL64– Warehouse table name: KGB_DOMINO MAIL or KGBDMAIL64

v Attribute group name: Domino MAIL (Superseded)– Table name: KGBDMAIL– Warehouse table name: KGB_DOMINO MAIL (SUPERSEDED) or KGBDMAIL

v Attribute group name: Domino Mail By Dest– Table name: KGBDMBD64– Warehouse table name: KGB_DOMINO MAIL BY DEST or KGBDMBD64

v Attribute group name: Domino Mail By Dest (Superseded)– Table name: KGBDMBD– Warehouse table name: KGB_DOMINO MAIL BY DEST (SUPERSEDED) or

KGBDMBDv Attribute group name: Domino NET TCPIP

– Table name: KGBDNETT64– Warehouse table name: KGB_DOMINO NET TCPIP or KGBDNETT64

v Attribute group name: Domino NET TCPIP (Superseded)– Table name: KGBDNETT– Warehouse table name: KGB_DOMINO NET TCPIP (SUPERSEDED) or

KGBDNETTv Attribute group name: Domino Replica

– Table name: KGBDREP64– Warehouse table name: KGB_DOMINO REPLICA or KGBDREP64

v Attribute group name: Domino Replica (Superseded)– Table name: KGBDREP– Warehouse table name: KGB_DOMINO REPLICA (SUPERSEDED) or

KGBDREPv Attribute group name: Domino Replica Cluster

– Table name: KGBDREPC64– Warehouse table name: KGB_DOMINO REPLICA CLUSTER or KGBDREPC64

v Attribute group name: Domino Replica Cluster (Superseded)– Table name: KGBDREPC– Warehouse table name: KGB_DOMINO REPLICA CLUSTER (SUPERSEDED)

or KGBDREPCv Attribute group name: Domino Replication

– Table name: KGBDRPL– Warehouse table name: KGB_DOMINO REPLICATION or KGBDRPL

v Attribute group name: Domino Server– Table name: KGBDSRV64– Warehouse table name: KGB_DOMINO SERVER or KGBDSRV64

v Attribute group name: Domino Server (Superseded)– Table name: KGBDSRV– Warehouse table name: KGB_DOMINO SERVER (SUPERSEDED) or

KGBDSRVv Attribute group name: Domino Server Cluster

Chapter 4. Attributes reference 27

– Table name: KGBDSRVC– Warehouse table name: KGB_DOMINO SERVER CLUSTER or KGBDSRVC

v Attribute group name: Domino SMTP– Table name: KGBDSMTP64– Warehouse table name: KGB_DOMINO SMTP or KGBDSMTP64

v Attribute group name: Domino SMTP (Superseded)– Table name: KGBDSMTP– Warehouse table name: KGB_DOMINO SMTP (SUPERSEDED) or KGBDSMTP

v Attribute group name: Domino Tasks– Table name: KGBDTASK– Warehouse table name: KGB_DOMINO TASKS or KGBDTASK

v Attribute group name: Domino Web Retriever– Table name: KGBDWR– Warehouse table name: KGB_DOMINO WEB RETRIEVER or KGBDWR

v Attribute group name: IW Mail Domain Statistics– Table name: KGBIMDOM– Warehouse table name: KGB_IW MAIL DOMAIN STATISTICS or

KGBIMDOMv Attribute group name: IW Mail Incoming Statistics

– Table name: KGBIMINC– Warehouse table name: KGB_IW MAIL INCOMING STATISTICS or

KGBIMINCv Attribute group name: IW Mail Outgoing Statistics

– Table name: KGBIMOUT– Warehouse table name: KGB_IW MAIL OUTGOING STATISTICS or

KGBIMOUTv Attribute group name: IW Mail Size Statistics

– Table name: KGBIMSIZ– Warehouse table name: KGB_IW MAIL SIZE STATISTICS or KGBIMSIZ

v Attribute group name: IW Replication Delay Statistics– Table name: KGBIREPD– Warehouse table name: KGB_IW REPLICATION DELAY STATISTICS or

KGBIREPDv Attribute group name: IW Replication Statistics

– Table name: KGBIREP– Warehouse table name: KGB_IW REPLICATION STATISTICS or KGBIREP

v Attribute group name: IW Server– Table name: KGBISERV– Warehouse table name: KGB_IW SERVER or KGBISERV

v Attribute group name: IW View Performance Statistics– Table name: KGBIVPERF– Warehouse table name: KGB_IW VIEW PERFORMANCE STATISTICS or

KGBIVPERFv Attribute group name: Performance Object Status

– Table name: KGBPOBJST


– Warehouse table name: KGB_PERFORMANCE_OBJECT_STATUS orKGBPOBJST

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

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

Attribute descriptionsDescription and type for each attribute in the attribute group

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

Availability attribute group

The Availability attribute group contains the availability data for all processes andservices that make up this application. If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.

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

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

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.

Type String

Timestamp attribute

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

Type String

Application Component attribute - This attribute is a key attribute.

DescriptionThe descriptive name of a part of the application.

Type String

Name attribute

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

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


Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v N/A (N/A)

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

Status attribute

DescriptionThe status of the application component.v For processes ’UP’, ’DOWN’, ’WARNING’, or

’PROCESS_DATA_NOT_AVAILABLE’:’PROCESS_DATA_NOT_AVAILABLE’ is displayed for a processwhen the matching process is running but the resource useinformation cannot be collected for that process.

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

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

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v DOWN (0)v UP (1)v WARNING (2)v UNKNOWN (3)v PASSED (4)v FAILED (5)v PROCESS_DATA_NOT_AVAILABLE (6)


Full Name attribute

DescriptionThe full name of the process including the path.

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


Type attribute

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

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v PROCESS (0)v SERVICE (1)


v FUNCTIONALITY_TEST (2)


Virtual Size attribute

DescriptionThe virtual size (in MB) of the process.

Type Integer (Gauge)

Page Faults per Sec attribute

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


Working Set Size attribute

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


Thread Count attribute

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


PID attribute

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


Percent Privileged Time attribute

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


Percent User Mode Time attribute

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


Percent Processor Time attribute

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


Command Line attribute


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

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


Functionality Test Status attribute

DescriptionThe return code of the functionality test. When the monitoredapplication is running correctly, ’SUCCESS’ is displayed.’NOT_RUNNING’ is displayed when it is not running correctly.’N/A’ is displayed when the row does not represent afunctionality test.

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v SUCCESS (0)v N/A (1)v GENERAL_ERROR (2)v WARNING (3)v NOT_RUNNING (4)v DEPENDENT_NOT_RUNNING (5)v ALREADY_RUNNING (6)v PREREQ_NOT_RUNNING (7)v TIMED_OUT (8)v DOESNT_EXIST (9)v UNKNOWN (10)v DEPENDENT_STILL_RUNNING (11)v INSUFFICIENT_USER_AUTHORITY (12)


Functionality Test Message attribute

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

Type String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v N/A (N/A)v KGB5031I: Responding (KGB5031I)v KGB5032I: Not Responding (KGB5032I)v KGB5036I: Does Not Exist (KGB5036I)


v KGB5039I: The Windows computer must be rebooted.(KGB5039I)

v KGB5040I: Re-cycling Domino agent. (KGB5040I)v KGB5041I: Domino agent is starting and initializing. (KGB5041I)v KGB5042I: Restricted. (KGB5042I)v KGB5037I: kgbconfig.sh must be run on the Lotus Domino agent

(KGB5037I)v KGB5038I: The Lotus Domino agent must be started as the

Domino user. (KGB5038I)v KGB5033I: Responding (KGB5033I)v KGB5034I: Not Responding (KGB5034I)v KGB5035I: Does Not Exist (KGB5035I)v KGB5043I: Some but not all other Domino servers responding in

the cluster. (KGB5043I)v KGB5044I: Only one Domino server responding in the cluster.

(KGB5044I)


Domino Agent attribute group

This attribute group provides statistics for the Lotus Domino agent. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String

Server Name attribute - This attribute is a key attribute.

DescriptionThe server name.

Type String

Daily Access Denials attribute


DescriptionThe number of daily access denials for agents.

Type Integer (Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (2147483647)v Value_Exceeds_Minimum (-2147483648)


Daily Unsuccessful Runs attribute

DescriptionThe number of daily unsuccessful agent runs.



Daily Scheduled Runs attribute

DescriptionThe number of daily scheduled agent runs.



Daily Triggered Runs attribute

DescriptionThe number of daily triggered agent runs.




Domino Calendar attribute group

This attribute group provides calendar statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

Total All Appts Reservations attribute

DescriptionThe total number of appointments and reservations in scheduling.

Type Integer (64-Bit Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)v Value_Exceeds_Minimum (-9223372036854775808)


Total All Users Resources attribute

DescriptionThe total number of users and resources in scheduling.




Total Appts attribute

DescriptionThe total number of appointments in scheduling.



Total Reservations attribute

DescriptionThe total number of reservations in scheduling.



Total Resources attribute

DescriptionThe total number of resources in scheduling.



Total Users attribute

DescriptionThe total number of users in scheduling.




Domino Calendar (Superseded) attribute group

This attribute group provides calendar statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the DominoCalendar (Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String

Total All Appts Reservations attribute

DescriptionThe total number of appointments and reservations in scheduling.



Total All Users Resources attribute

DescriptionThe total number of users and resources in scheduling.




Total Appts attribute

DescriptionThe total number of appointments in scheduling.



Total Reservations attribute

DescriptionThe total number of reservations in scheduling.



Total Resources attribute

DescriptionThe total number of resources in scheduling.



Total Users attribute

DescriptionThe total number of users in scheduling.




Domino Command attribute group



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



Type String

Timestamp attribute


Type String



Type String

Create Document attribute

DescriptionCount of ’CreateDocument’ URLs that have come into the serversince server was last started.



Delete Document attribute

DescriptionCount of ’DeleteDocument’ URLs that have come into the serversince server was last started.

Type Integer (64-Bit Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)


v Value_Exceeds_Minimum (-9223372036854775808)


Edit Document attribute

DescriptionCount of ’EditDocument’ URLs that have come into the serversince server was last started.



Login attribute

DescriptionCount of ’Login’ URLs that have come into the server since serverwas last started.



Navigate attribute

DescriptionCount of ’Navigate’ URLs that have come into the server sinceserver was last started.



Open About attribute

DescriptionCount of ’OpenAbout’ URLs that have come into the server sinceserver was last started.

Type Integer (64-Bit Counter) with enumerated values. The strings are


displayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)v Value_Exceeds_Minimum (-9223372036854775808)


Open Agent attribute

DescriptionCount of ’OpenAgent’ URLs that have come into the server sinceserver was last started.



Open Database attribute

DescriptionCount of ’OpenDatabase’ URLs that have come into the serversince server was last started.



Open Document attribute

DescriptionCount of ’OpenDocument’ URLs that have come into the serversince server was last started.



Open Element attribute


DescriptionCount of ’OpenElement’ URLs that have come into the server sinceserver was last started.



Open Form attribute

DescriptionCount of ’OpenForm’ URLs that have come into the server sinceserver was last started.



Open Help attribute

DescriptionCount of ’OpenHelp’ URLs that have come into the server sinceserver was last started.



Open Icon attribute

DescriptionCount of ’OpenIcon’ URLs that have come into the server sinceserver was last started.




Open Navigator attribute

DescriptionCount of ’OpenNavigator’ URLs that have come into the serversince server was last started.



Open Server attribute

DescriptionCount of ’OpenServer’ URLs that have come into the server sinceserver was last started.



Open View attribute

DescriptionCount of ’OpenView’ URLs that have come into the server sinceserver was last started.



Read Form attribute

DescriptionCount of ’ReadForm’ URLs that have come into the server sinceserver was last started.




Search Site attribute

DescriptionCount of ’SearchSite’ URLs that have come into the server sinceserver was last started.



Search View attribute

DescriptionCount of ’SearchView’ URLs that have come into the server sinceserver was last started.



Total attribute

DescriptionCount of all URLs that have come into the server since server waslast started.



Unknown attribute

DescriptionCount of Unknown URLs that have come into the server sinceserver was last started.

Type Integer (64-Bit Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)




Domino Corrupt Failover DB attribute group

This attribute group provides database corruption statistics for Lotus Domino. Ifthe warehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino CorruptFailover DB attribute group:



Type String

Timestamp attribute


Type String



Type String

DB Name attribute - This attribute is a key attribute.

DescriptionThe database name.

Type String

View attribute - This attribute is a key attribute.

DescriptionThe view name.

Type String

State attribute

DescriptionThe state of the corrupt database or view. Its value could be Accessnot authorized, Cluster failover, Corrupt, Corrupt but fixed, Good,Invalid NSF version, Locked, Not a database, Operation notauthorized, or Unknown.

Type String


Failover Status attribute

DescriptionThe status of failover database.

Type String

Failover DB attribute

DescriptionThe failover database name.

Type String

Failover Server attribute

DescriptionThe failover server name.

Type String

Domino Database attribute group

This attribute group provides database statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

DA Refresh Server Info Count attribute

DescriptionThe directory assistance refresh server information count.





DA Reload Count attribute

DescriptionThe directory assistance reload count.



Buffer Pool Max MB attribute

DescriptionThe buffer pool maximum megabytes.

Type Integer (64-Bit Gauge) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)v Value_Exceeds_Minimum (-9223372036854775808)


Buffer Pool MM Reads attribute

DescriptionThe database buffer pool reads.



Buffer Pool MM Writes attribute

DescriptionThe database buffer pool writes.





Buffer Pool Peak MB attribute

DescriptionThe buffer pool peak megabytes.



Buffer Pool Pct Reads In Buf attribute

DescriptionThe buffer pool percent reads in the buffer.



Db Cache Current Entries attribute

DescriptionThe database cache current entries.



Db Cache High Water Mark attribute

DescriptionThe database cache high water mark.

Type Integer (64-Bit Gauge) with enumerated values. The strings are




Db Cache Hits attribute

DescriptionThe database cache hits.



Db Cache Initial Db Opens attribute

DescriptionThe number of times the database cache has opened databases.



Db Cache Lookups attribute

DescriptionThe number of lookups to the database cache.



Db Cache Max Entries attribute

DescriptionThe maximum number of entries in the database cache.





Db Cache Overcrowd Rej attribute

DescriptionThe number of rejections caused by overcrowding the database.



NSF Pool Peak attribute

DescriptionThe peak number of database NSF pools.



NSF Pool Used attribute

DescriptionThe number of database NSF pools.



NSF Replicate Notes Received attribute

DescriptionThe number of NSF replicate notes received.





NSF Replicate Notes Sent attribute

DescriptionThe number of NSF replicate notes sent.



Domino Database (Superseded) attribute group

This attribute group provides database statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the DominoDatabase (Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String

DA Refresh Server Info Count attribute


DescriptionThe directory assistance refresh server information count.



DA Reload Count attribute

DescriptionThe directory assistance reload count.



Buffer Pool Max MB attribute

DescriptionThe buffer pool maximum megabytes.

Type Integer (Gauge) with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:v Value_Exceeds_Maximum (2147483647)v Value_Exceeds_Minimum (-2147483648)


Buffer Pool MM Reads attribute

DescriptionThe database buffer pool reads.



Buffer Pool MM Writes attribute

DescriptionThe database buffer pool writes.




Buffer Pool Peak MB attribute

DescriptionThe buffer pool peak megabytes.



Buffer Pool Pct Reads In Buf attribute

DescriptionThe buffer pool percent reads in the buffer.



Db Cache Current Entries attribute

DescriptionThe database cache current entries.



Db Cache High Water Mark attribute

DescriptionThe database cache high water mark.

Type Integer (Gauge) with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:v Value_Exceeds_Maximum (2147483647)




Db Cache Hits attribute

DescriptionThe database cache hits.



Db Cache Initial Db Opens attribute

DescriptionThe number of times the database cache has opened databases.



Db Cache Lookups attribute

DescriptionThe number of lookups to the database cache.



Db Cache Max Entries attribute

DescriptionThe maximum number of entries in the database cache.



Db Cache Overcrowd Rej attribute


DescriptionThe number of rejections caused by overcrowding the database.



NSF Pool Peak attribute

DescriptionThe peak number of database NSF pools.



NSF Pool Used attribute

DescriptionThe number of database NSF pools.



NSF Replicate Notes Received attribute

DescriptionThe number of NSF replicate notes received.



NSF Replicate Notes Sent attribute

DescriptionThe number of NSF replicate notes sent.

Type Integer (Gauge) with enumerated values. The strings are displayed


in the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:v Value_Exceeds_Maximum (2147483647)v Value_Exceeds_Minimum (-2147483648)


Domino DB Whitespace attribute group

This attribute group provides database space usage statistics for Lotus Domino. Ifthe warehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

DB Name attribute - This attribute is a key attribute.

DescriptionThe database name.

Type String

DB Whitespace Size (KByte) attribute

DescriptionThe number of kbytes free in the database.




DB Whitespace Percentage (%) attribute

DescriptionThe percent of the database that is not used.



DB Size (KByte) attribute

DescriptionThe database size in kbyte units.



DB Max Size (KByte) attribute

DescriptionThe max database size in kbyte units, where 0 means no limit.



DB Size Limit (KByte) attribute

DescriptionThe database size limit in kbyte units, where 0 means limit is notset.




DB Warning Threshold (KByte) attribute

DescriptionThe database size warning threshold in kbyte units, where 0 meansthreshold is not set.



Domino Group Updates attribute group

This attribute group provides Domino group updates. If the warehouse defaultsetting is enabled, data for this attribute group is stored in Tivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

Group Name attribute - This attribute is a key attribute.

DescriptionThe group name in Domino Directory.

Type String

Change attribute

DescriptionThe group changes in Domino Directory.

Type String


Domino ICM attribute group

This attribute group provides internet cluster manager statistics for Lotus Domino.If the warehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

Availability Index attribute

DescriptionThe current percentage index of a server’s availability. The valuerange is 0 - 100. Zero (0) indicates no available resources; 100indicates that the server is completely available.

Type DisplayNumeric

Cmd Total attribute

DescriptionThe total number of commands received.



Cmd Unknown attribute

DescriptionThe total number of unknown commands received.




Cmd Redirects Successful attribute

DescriptionThe number of successful redirects.



Cmd Redirects Unsuccessful attribute

DescriptionThe number of unsuccessful redirects.



Cmd Redirects Cluster Busy attribute

DescriptionThe number of commands received when all servers are busy.



Receive Error attribute

DescriptionThe total number of commands not received due to error.





Requests Per 1Hour attribute

DescriptionThe number of requests received in the last hour.



Requests Per 1Minute attribute

DescriptionThe number of requests in the last minute.



Requests Per 5Minutes attribute

DescriptionThe number of requests in the last 5 minutes.



Server Running attribute

DescriptionThe server that is running.

Type String

Sess Inbound Accept Queue attribute


DescriptionThe ICM listener work queue of incoming sessions to be processed.



Sess Inbound Active attribute

DescriptionThe current number of ICM server tasks.



Sess Inbound KB Received attribute

DescriptionThe total number of KB received by this ICM server.



Sess Inbound KB Sent attribute

DescriptionThe total number of KB sent by this ICM server.



Sess Inbound Peak attribute

DescriptionThe peak number of ICM server inbound connections.




Sess Inbound SSL attribute

DescriptionThe number of ICM Server inbound SSL connections.



Sess Inbound Total attribute

DescriptionThe total number of ICM server inbound connections (SSL andnon-SSL).



Sess Inbound Total SSL attribute




Sess Outbound Active attribute

DescriptionThe current number of ICM outbound server tasks.





Sess Outbound Active SSL attribute

DescriptionThe current number of ICM outbound SSL connections.



Sess Outbound KB Received attribute




Sess Outbound KB Sent attribute




Sess Outbound Peak attribute

DescriptionThe peak number of ICM outbound server tasks since the serverstart.





Sess Outbound Peak SSL attribute

DescriptionThe peak number of ICM server outbound SSL connections.



Sess Outbound Total attribute

DescriptionThe total number of ICM server outbound connections (SSL andnon-SSL).



Sess Outbound Total SSL attribute

DescriptionThe total number of ICM server outbound SSL connections.



Sess Threads Busy attribute

DescriptionThe number of ICM server tasks currently running.





Sess Threads Idle attribute

DescriptionThe number of ICM server tasks currently idle.



Sess Threads In Thread Pool attribute

DescriptionThe number of ICM server threads in a pool.



Sess Threads Peak attribute

DescriptionThe peak number of ICM server tasks currently running.



Domino ICM (Superseded) attribute group

This attribute group provides internet cluster manager statistics for Lotus Domino.If the warehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.



Attribute descriptionsThe following list contains information about each attribute in the Domino ICM(Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String


DescriptionThe current percentage index of a server’s availability. The valuerange is 0 - 100. Zero (0) indicates no available resources; 100indicates that the server is completely available.

Type DisplayNumeric

Cmd Total attribute

DescriptionThe total number of commands received.



Cmd Unknown attribute

DescriptionThe total number of unknown commands received.

Type Integer (Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (2147483647)




Cmd Redirects Successful attribute

DescriptionThe number of successful redirects.



Cmd Redirects Unsuccessful attribute

DescriptionThe number of unsuccessful redirects.



Cmd Redirects Cluster Busy attribute

DescriptionThe number of commands received when all servers are busy.



Receive Error attribute

DescriptionThe total number of commands not received due to error.




Requests Per 1Hour attribute

DescriptionThe number of requests received in the last hour.



Requests Per 1Minute attribute

DescriptionThe number of requests in the last minute.



Requests Per 5Minutes attribute

DescriptionThe number of requests in the last 5 minutes.





Type String


DescriptionThe ICM listener work queue of incoming sessions to be processed.

Type Integer (Counter) with enumerated values. The strings are





DescriptionThe current number of ICM server tasks.



Sess Inbound Active SSL attribute










Type Integer (Gauge) with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:v Value_Exceeds_Maximum (2147483647)





DescriptionThe peak number of ICM server inbound connections.



Sess Inbound SSL attribute





DescriptionThe total number of ICM server inbound connections (SSL andnon-SSL).








Sess Outbound Active attribute

DescriptionThe current number of ICM outbound server tasks.



Sess Outbound Active SSL attribute

DescriptionThe current number of ICM outbound SSL connections.



Sess Outbound KB Received attribute




Sess Outbound KB Sent attribute




Sess Outbound Peak attribute


DescriptionThe peak number of ICM outbound server tasks since the serverstart.



Sess Outbound Peak SSL attribute

DescriptionThe peak number of ICM server outbound SSL connections.



Sess Outbound Total attribute

DescriptionThe total number of ICM server outbound connections (SSL andnon-SSL).



Sess Outbound Total SSL attribute

DescriptionThe total number of ICM server outbound SSL connections.




DescriptionThe number of ICM server tasks currently running.





DescriptionThe number of ICM server tasks currently idle.



Sess Threads In Thread Pool attribute

DescriptionThe number of ICM server threads in a pool.



Sess Threads Peak attribute

DescriptionThe peak number of ICM server tasks currently running.



Domino IMAP attribute group

This attribute group provides IMAP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.



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



Type String

Timestamp attribute


Type String



Type String

Sess Accept Queue attribute

DescriptionThe IMAP listener work queue of incoming sessions to beprocessed.



Sess Active attribute

DescriptionThe current number of IMAP server tasks.





DescriptionThe total number of KB received by this IMAP server.




DescriptionThe total number of KB sent by this IMAP server



Sess Inbound Non SSL attribute

DescriptionThe number of IMAP server inbound TCP connections (non-SSL).



Sess Peak attribute

DescriptionThe peak number IMAP server tasks since the server started.




DescriptionThe number of IMAP server tasks currently running.





DescriptionThe number of IMAP server tasks currently idle.



Sess Total attribute

DescriptionThe total number of IMAP server tasks since the server started.



Domino IMAP (Superseded) attribute group

This attribute group provides IMAP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino IMAP(Superseded) attribute group:




Type String

Timestamp attribute


Type String



Type String

Sess Accept Queue attribute

DescriptionThe IMAP listener work queue of incoming sessions to beprocessed.



Sess Active attribute

DescriptionThe current number of IMAP server tasks.




DescriptionThe total number of KB received by this IMAP server.





DescriptionThe total number of KB sent by this IMAP server



Sess Inbound Non SSL attribute

DescriptionThe number of IMAP server inbound TCP connections (non-SSL).



Sess Peak attribute

DescriptionThe peak number IMAP server tasks since the server started.




DescriptionThe number of IMAP server tasks currently running.




DescriptionThe number of IMAP server tasks currently idle.






DescriptionThe total number of IMAP server tasks since the server started.



Domino LDAP attribute group

This attribute group provides LDAP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


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



Type String

Timestamp attribute


Type String



Type String




Type String


DescriptionThe LDAP listener work queue of incoming sessions to beprocessed.




DescriptionThe current number of LDAP server tasks.




DescriptionThe number of LDAP server inbound SSL connections.




DescriptionThe total number of KB received by this LDAP server.





DescriptionThe total number of KB sent by this LDAP server.




DescriptionThe session inbound peak.



Sess Inbound Peak SSL attribute

DescriptionThe peak number of LDAP server inbound SSL connections.




DescriptionThe total number of LDAP server inbound connections (SSL andnon-SSL).








Sess Inb Tot SSL Bad Hshake attribute

DescriptionThe number of LDAP server SSL Handshake Failures.



Sess Non SSL attribute

DescriptionThe number of LDAP server TCP connections (non-SSL).



Sess SSL attribute

DescriptionThe number of LDAP server SSL connections.





DescriptionThe total number LDAP server tasks since the server started.




DescriptionThe number of LDAP server tasks currently running.




DescriptionThe number of LDAP server tasks currently idle.



Domino LDAP (Superseded) attribute group

This attribute group provides LDAP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino LDAP(Superseded) attribute group:




Type String

Timestamp attribute


Type String



Type String



Type String


DescriptionThe LDAP listener work queue of incoming sessions to beprocessed.




DescriptionThe current number of LDAP server tasks.










DescriptionThe total number of KB received by this LDAP server.




DescriptionThe total number of KB sent by this LDAP server.




DescriptionThe session inbound peak.



Sess Inbound Peak SSL attribute

DescriptionThe peak number of LDAP server inbound SSL connections.





DescriptionThe total number of LDAP server inbound connections (SSL andnon-SSL).







Sess Inb Tot SSL Bad Hshake attribute

DescriptionThe number of LDAP server SSL Handshake Failures.



Sess Non SSL attribute

DescriptionThe number of LDAP server TCP connections (non-SSL).




Sess SSL attribute

DescriptionThe number of LDAP server SSL connections.




DescriptionThe total number LDAP server tasks since the server started.




DescriptionThe number of LDAP server tasks currently running.




DescriptionThe number of LDAP server tasks currently idle.




Domino Log File attribute group

Data gathered from Domino log file. If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino Log Fileattribute group:



Type String

Timestamp attribute


Type String


DescriptionName of Monitored Domino Server.

Type String

Log File attribute

DescriptionFully qualified log file name.

Type String

Log Message attribute

DescriptionError message found in log file.

Type DEFAULT(2)

Domino Mail attribute group

This attribute group provides mail statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.



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



Type String

Timestamp attribute


Type String



Type String

Dead attribute

DescriptionThe total number of dead (undeliverable) messages in MAIL.BOX.



Average Deliver Time attribute

DescriptionThe average amount of time for mail delivery.

Type Integer (Average over time) with enumerated values. The stringsare displayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (2147483647)v Value_Exceeds_Minimum (-2147483648)


Hold attribute

DescriptionThe total number of mail messages in the message queue on hold.

Type Integer (64-Bit Counter) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:


v Value_Exceeds_Maximum (9223372036854775807)v Value_Exceeds_Minimum (-9223372036854775808)


Waiting attribute

DescriptionThe number of outgoing mail messages currently in MAIL.BOXwaiting.



Current Byte Delivery Rate attribute

DescriptionThe current byte delivery rate for mail.



Current Byte Transfer Rate attribute

DescriptionThe current byte transfer rate for mail.



Current Msg Delivery Rate attribute

DescriptionThe current message delivery rate for mail.

Type Integer (64-Bit Gauge) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)




Current Msg Transfer Rate attribute

DescriptionThe current message transfer rate for mail.



Total Failures attribute

DescriptionThe total number of mail failures.



Total KB Delivered attribute

DescriptionThe total KB of mail delivered.



Total Pending attribute

DescriptionThe number of mail messages pending.




Total Routed attribute

DescriptionThe number of mail messages moved from MAIL.BOX to otherservers.



Waiting For DIR attribute

DescriptionThe number of mail messages in MAIL.BOX waiting for DIR.



Waiting For DNS attribute

DescriptionThe number of mail messages in MAIL.BOX waiting for DNS.



Waiting Recipients attribute

DescriptionThe number of pending mail messages in MAIL.BOX awaitingdelivery to the user’s mail file.




Transferred attribute

DescriptionThe number of mail messages that the router attempted to transfer.



Peak Messages Transferred attribute

DescriptionThe peak number of messages transferred.



Transfer Failures attribute

DescriptionThe number of mail messages that the router was unable totransfer.



Delivered attribute

DescriptionThe number of mail messages that the router moved intoMAIL.BOX.




Average Size Delivered attribute

DescriptionThe average size of mail delivered.



Max Size Delivered attribute

DescriptionThe maximum size of mail delivered.



Total KB Transferred attribute

DescriptionThe total KB of mail transferred.



Total Routed SMTP attribute

DescriptionThe number of mail messages moved from MAIL.BOX usingSMTP.




Total Routed NRPC attribute

DescriptionThe number of mail messages moved from MAIL.BOX usingNRPC.



Domino MAIL (Superseded) attribute group

This attribute group provides mail statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino MAIL(Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String

Dead attribute

DescriptionThe total number of dead (undeliverable) messages in MAIL.BOX.





Average Deliver Time attribute

DescriptionThe average amount of time for mail delivery.



Hold attribute

DescriptionThe total number of mail messages in the message queue on hold.



Waiting attribute

DescriptionThe number of outgoing mail messages currently in MAIL.BOXwaiting.



Current Byte Delivery Rate attribute

DescriptionThe current byte delivery rate for mail.





Current Byte Transfer Rate attribute

DescriptionThe current byte transfer rate for mail.



Current Msg Delivery Rate attribute

DescriptionThe current message delivery rate for mail.



Current Msg Transfer Rate attribute

DescriptionThe current message transfer rate for mail.



Total Failures attribute

DescriptionThe total number of mail failures.





Total KB Delivered attribute

DescriptionThe total KB of mail delivered.



Total Pending attribute

DescriptionThe number of mail messages pending.




DescriptionThe number of mail messages moved from MAIL.BOX to otherservers.



Waiting For DIR attribute

DescriptionThe number of mail messages in MAIL.BOX waiting for DIR.




Waiting For DNS attribute

DescriptionThe number of mail messages in MAIL.BOX waiting for DNS.



Waiting Recipients attribute

DescriptionThe number of pending mail messages in MAIL.BOX awaitingdelivery to the user’s mail file.







Peak Messages Transferred attribute

DescriptionThe peak number of messages transferred.




Transfer Failures attribute

DescriptionThe number of mail messages that the router was unable totransfer.



Delivered attribute

DescriptionThe number of mail messages that the router moved intoMAIL.BOX.



Average Size Delivered attribute

DescriptionThe average size of mail delivered.



Max Size Delivered attribute

DescriptionThe maximum size of mail delivered.





DescriptionThe total KB of mail transferred.



Domino Mail By Dest attribute group

This attribute group provides mail by destination statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino Mail ByDest attribute group:



Type String

Timestamp attribute


Type String



Type String

Destination Server attribute - This attribute is a key attribute.

DescriptionThe name of the mail destination server.

Type String



DescriptionThe total number of routed messages.







Delivered attribute

DescriptionThe total number of messages that was delivered.




DescriptionThe total KB of mail that was transferred.




Domino Mail By Dest (Superseded) attribute group

This attribute group provides mail by destination statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino Mail ByDest (Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String



Type String


DescriptionThe total number of routed messages.









Delivered attribute

DescriptionThe total number of messages that was delivered.




DescriptionThe total KB of mail that was transferred.



Domino NET TCPIP attribute group

This attribute group provides TCPIP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


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



Type String


Timestamp attribute


Type String



Type String

Sessions Est Incoming attribute

DescriptionThe number of Incoming sessions established.



Sessions Est Outgoing attribute

DescriptionThe number of Outgoing sessions established.



Sessions Peak attribute

DescriptionThe peak number of sessions.



KB Received attribute

DescriptionThe number of network KB received.




KB Sent attribute

DescriptionThe number of network KB sent.



KB Received Interval attribute

DescriptionThe number of network bytes received this interval.



KB Sent Interval attribute

DescriptionThe number of network bytes sent this interval.



Domino NET TCPIP (Superseded) attribute group

This attribute group provides TCPIP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.



Attribute descriptionsThe following list contains information about each attribute in the Domino NETTCPIP (Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String

Sessions Est Incoming attribute

DescriptionThe number of Incoming sessions established.



Sessions Est Outgoing attribute

DescriptionThe number of Outgoing sessions established.



Sessions Peak attribute

DescriptionThe peak number of sessions.





DescriptionThe number of network KB received.



KB Sent attribute

DescriptionThe number of network KB sent.



Domino Replica attribute group

This attribute group provides replication statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute



Type String



Type String

Successful attribute

DescriptionThe number of replication attempts that returned no error of anykind.



Failed attribute

DescriptionThe number of attempted replications that returned some kind oferror.



Docs Added attribute

DescriptionThe number of documents added to the server databases throughreplication.



Docs Updated attribute


DescriptionThe number of documents updated in the server databases throughreplication.



Docs Deleted attribute

DescriptionThe number of documents deleted from the server databasesthrough replication.



Domino Replica (Superseded) attribute group

This attribute group provides replication statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino Replica(Superseded) attribute group:



Type String

Timestamp attribute


Type String




Type String


DescriptionThe number of replication attempts that returned no error of anykind.



Failed attribute

DescriptionThe number of attempted replications that returned some kind oferror.




DescriptionThe number of documents added to the server databases throughreplication.




DescriptionThe number of documents updated in the server databases throughreplication.






DescriptionThe number of documents deleted from the server databasesthrough replication.



Domino Replica Cluster attribute group

This attribute group provides Replication Cluster statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

Servers attribute


DescriptionThe number of other servers in the cluster that are receivingreplications from this server.




DescriptionThe number of successful replications since the server started.



Failed attribute

DescriptionThe number of failed replications since the server started.




DescriptionThe number of documents added by the Cluster Replicator.





DescriptionThe number of documents updated by the Cluster Replicator.




DescriptionThe number of documents deleted by the Cluster Replicator.



Retry Waiting attribute

DescriptionThe number of replicas currently waiting for replication retryattempts.



Session KB In attribute

DescriptionThe number of incoming KB to the Cluster Replicator.



Session KB Out attribute


DescriptionThe number of outgoing KB to the Cluster Replicator.



Work Queue Depth Avg attribute

DescriptionThe average number of modified databases in the queue waiting tobe replicated to other servers by the Cluster Replicator.



Work Queue Depth Max attribute

DescriptionThe maximum number of modified databases in the queue waitingto be replicated to other servers by the Cluster Replicator.



Work Queue Depth attribute

DescriptionThe current number of modified databases in the queue waiting tobe replicated to other servers by the Cluster Replicator.




Seconds On Queue attribute

DescriptionThe number of seconds that the Cluster Replicator was on queue.



Seconds On Queue Max attribute

DescriptionThe maximum number of seconds that the Cluster Replicator wason queue.



Domino Replica Cluster (Superseded) attribute group

This attribute group provides Replication Cluster statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino ReplicaCluster (Superseded) attribute group:



Type String

Timestamp attribute


Type String




Type String

Servers attribute

DescriptionThe number of other servers in the cluster that are receivingreplications from this server.




DescriptionThe number of successful replications since the server started.



Failed attribute

DescriptionThe number of failed replications since the server started.




DescriptionThe number of documents added by the Cluster Replicator.





DescriptionThe number of documents updated by the Cluster Replicator.




DescriptionThe number of documents deleted by the Cluster Replicator.



Retry Waiting attribute

DescriptionThe number of replicas currently waiting for replication retryattempts.



Session KB In attribute

DescriptionThe number of incoming KB to the Cluster Replicator.




Session KB Out attribute

DescriptionThe number of outgoing KB to the Cluster Replicator.



Work Queue Depth Avg attribute

DescriptionThe average number of modified databases in the queue waiting tobe replicated to other servers by the Cluster Replicator.



Work Queue Depth Max attribute

DescriptionThe maximum number of modified databases in the queue waitingto be replicated to other servers by the Cluster Replicator.



Work Queue Depth attribute

DescriptionThe current number of modified databases in the queue waiting tobe replicated to other servers by the Cluster Replicator.



Seconds On Queue attribute


DescriptionThe number of seconds that the Cluster Replicator was on queue.



Seconds On Queue Max attribute

DescriptionThe maximum number of seconds that the Cluster Replicator wason queue.



Domino Replication attribute group



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



Type String

Timestamp attribute


Type String




Type String


DescriptionThe name of the destination server for replication.

Type String

Initiated By attribute

DescriptionServer initiating replication.

Type String

Start Time attribute

DescriptionReplication start time.

Type String

End Time attribute

DescriptionReplication end time.

Type String

DB Info attribute

DescriptionName of the Domino database that was replicated.

Type String

Events attribute

DescriptionList of events that occured during this replication, separated bysemicolons.

Type String

Hit Miss attribute

DescriptionReplication occurred, missed, or was manual.

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v hit (1)v miss (2)v manual (3)


Duration attribute

DescriptionThe number of minutes it took replication to complete.




Domino Server attribute group

This attribute group provides server statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


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



Type String

Timestamp attribute


Type String



Type String

Server OS attribute

DescriptionThe operating system for this Domino Server.

Type String

Server Version attribute

DescriptionThe version for this Domino Server.

Type String

Server Build attribute

DescriptionThe build version for this Domino Server.


Type String

Server Start attribute

DescriptionThe server startup.

Type String


DescriptionThe current percentage index for the availability of a server. Thevalue range is 0 - 100. Zero (0) indicates no available resources; 100indicates that the server is completely available.



Availability Threshold attribute

DescriptionThe current setting for the availability threshold for a server. Whena server’s availability index drops below its availability threshold,the server becomes BUSY.



Sessions Dropped attribute

DescriptionThe number of sessions dropped in mid-transaction.



Trans Per Minute Peak attribute

DescriptionThe highest number of transactions to occur during a 1-minuteinterval.




Trans Total attribute

DescriptionThe number of transactions processed since the server started.



Users Peak attribute

DescriptionThe peak number of concurrent users since the server was started.



Users Active 30 Min attribute

DescriptionThe number of users active for 30 minutes.



Users attribute

DescriptionThe number of users with open sessions on the server.





Expansion Factor attribute

DescriptionThe server expansion factor.



Trans Per Minute attribute

DescriptionThe number of server transactions in the last minute.



Response Time attribute

DescriptionDomino server response time.



Domino Server (Superseded) attribute group

This attribute group provides server statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.



Attribute descriptionsThe following list contains information about each attribute in the Domino Server(Superseded) attribute group:



Type String

Timestamp attribute


Type String



Type String

Server OS attribute

DescriptionThe operating system for this Domino Server.

Type String

Server Version attribute

DescriptionThe version for this Domino Server.

Type String

Server Build attribute

DescriptionThe build version for this Domino Server.

Type String

Server Start attribute

DescriptionThe server startup.

Type String


DescriptionThe current percentage index for the availability of a server. Thevalue range is 0 - 100. Zero (0) indicates no available resources; 100indicates that the server is completely available.

Type Integer (Gauge) with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:




Availability Threshold attribute

DescriptionThe current setting for the availability threshold for a server. Whena server’s availability index drops below its availability threshold,the server becomes BUSY.



Sessions Dropped attribute

DescriptionThe number of sessions dropped in mid-transaction.



Trans Per Minute Peak attribute

DescriptionThe highest number of transactions to occur during a 1-minuteinterval.



Trans Total attribute

DescriptionThe number of transactions processed since the server started.




Users Peak attribute

DescriptionThe peak number of concurrent users since the server was started.



Users Active 30 Min attribute

DescriptionThe number of users active for 30 minutes.



Users attribute

DescriptionThe number of users with open sessions on the server.



Expansion Factor attribute

DescriptionThe server expansion factor.




Domino Server Cluster attribute group

This attribute group provides cluster server statistics for Lotus Domino. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



Type String

Open Redir Failover Success attribute

DescriptionThe number of times that a server successfully redirects a client toanother cluster member after the client fails to open a databaseusing the replica ID.



Open Redir Failover Unsucc attribute

DescriptionThe number of times that a server is not able to redirect a client toanother cluster member after the client fails to open a databaseusing the replica ID.





Open Redir Fover By Pth Suc attribute

DescriptionThe number of times a server successfully redirects a client toanother cluster member after the client fails to open a databaseusing the path name.



Open Redir Fover By Pth Unsuc attribute

DescriptionThe number of times a server is not able to redirect a client toanother cluster member after the client fails to open a databaseusing the path name.



Open Redir Load Bal Succ Tot attribute

DescriptionThe number of times that a server successfully redirects a client toanother cluster member after the client tries to open a databaseusing the replica ID when the server is BUSY.



Open Redir Load Bal Unsuc Tot attribute


DescriptionThe number of times that a server is unable to redirect a client toanother cluster member after the client tries to open a databaseusing the replica ID when the server is BUSY.



Open Redir Load Bal Pth Unsuc attribute

DescriptionThe number of times that a server is not able to redirect a client toanother cluster member after the client tries to open a databaseusing the path name when the server is BUSY.



Open Redir Load Bal Pth Succ attribute

DescriptionThe number of times that a server successfully redirects a client toanother cluster member after the client tries to open a databaseusing the path name when the server is BUSY.



Open Req Cluster Busy attribute

DescriptionThe number of times that a client tries to open a database on theserver and on every available member when the server is BUSY.





Open Req Db Out Of Service attribute

DescriptionThe number of times that a client tries to open a database that ismarked as out of service on the server.



Open Req Load Balanced attribute

DescriptionThe number of times a client tries to open a database on the serverwhen the server is BUSY.



Probe Count attribute

DescriptionThe number of times that a server completes a probe request of theother cluster members.



Probe Error attribute

DescriptionThe number of times that a server receives an error when probinganother server.





Domino SMTP attribute group

This attribute group provides SMTP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


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



Type String

Timestamp attribute


Type String



Type String


DescriptionThe SMTP listener work queue of incoming sessions to beprocessed.




DescriptionThe current number SMTP server tasks.





DescriptionThe total number of SMTP server inbound connections (SSL andnon-SSL).




DescriptionThe total number of KB received by this SMTP server.




DescriptionThe total number of KB sent by this SMTP server.




DescriptionThe peak number of SMTP server inbound connections (SSL andnon-SSL).

Type Integer (Gauge) with enumerated values. The strings are displayed


in the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:v Value_Exceeds_Maximum (2147483647)v Value_Exceeds_Minimum (-2147483648)


Sess Inbound KB Received Interval attribute

DescriptionThe total number of KB received this interval by this SMTP server.



Sess Inbound KB Sent Interval attribute

DescriptionThe total number of KB sent this interval by this SMTP server.



Domino SMTP (Superseded) attribute group

This attribute group provides SMTP statistics for Lotus Domino. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


Attribute descriptionsThe following list contains information about each attribute in the Domino SMTP(Superseded) attribute group:



Type String


Timestamp attribute


Type String



Type String


DescriptionThe SMTP listener work queue of incoming sessions to beprocessed.




DescriptionThe current number SMTP server tasks.




DescriptionThe total number of SMTP server inbound connections (SSL andnon-SSL).





DescriptionThe total number of KB received by this SMTP server.




DescriptionThe total number of KB sent by this SMTP server.




DescriptionThe peak number of SMTP server inbound connections (SSL andnon-SSL).



Domino Tasks attribute group

This attribute group provides information about Domino tasks. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


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




Type String

Timestamp attribute


Type String



Type String

Task Name attribute

DescriptionThe task name.

Type String

Task Status attribute

DescriptionThe task status.

Type String

Task Status Duration attribute

DescriptionThe number of minutes the task has been at the current status.

Type String

Domino Web Retriever attribute group



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



Type String

Timestamp attribute


Type String




Type String

Access FTP attribute

DescriptionThe number of FTP retriever accesses.



Access Gopher attribute

DescriptionThe number of Gopher retriever accesses.



Access HTTP attribute

DescriptionThe number of HTTP retriever accesses.




DescriptionThe number of retriever KB received.

Type Integer (64-Bit Gauge) with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouse andqueries return the values shown in parentheses. The followingvalues are defined:v Value_Exceeds_Maximum (9223372036854775807)




KB Sent attribute

DescriptionThe number of retriever KB sent.



Image Cache Hits attribute

DescriptionThe number of successful accesses on retriever image cache.



Image Cache Misses attribute

DescriptionThe number of unsuccessful accesses on retriever image cache.



Log Level attribute

DescriptionWeb retriever logging level.

Type String

Log Messages attribute

DescriptionWeb retriever logging messages. (Yes/No)

Type String


Process Access FTP attribute

DescriptionThe number of retriever process FTP accesses.



Process Access Gopher attribute

DescriptionThe number of retriever process Gopher accesses.



Process Access HTTP attribute

DescriptionThe number of retriever process HTTP accesses.



Process KB Received attribute

DescriptionThe number of KB received by retriever process.



Process KB Sent attribute


DescriptionThe number of KB sent by retriever process.



Process Num Active attribute

DescriptionThe number of active retriever processes.



Process Num Busy attribute

DescriptionThe number of busy retriever processes.



Process Num Idle attribute

DescriptionThe number of idle retriever processes.



Process Num Maximum attribute

DescriptionThe maximum number of retriever processes.




Process State attribute

DescriptionState of retriever processes.

Type String

Process URLs Failed attribute

DescriptionThe number of failed retriever process URLs.



Process URLs Requested attribute

DescriptionThe number of requested retriever process URLs.



Process URLs Succeeded attribute

DescriptionThe number of successful retriever process URLs.




Time Current attribute

DescriptionCurrent time.

Type String

Time Duration attribute

DescriptionElapsed time since retriever started.

Type String

Time Start attribute

DescriptionTime retriever started.

Type String

URLs Failed attribute

DescriptionThe number of retriever URL’s that have failed.



URLs Requested attribute

DescriptionThe number of retriever URL’s that have been requested.



URLs Succeeded attribute

DescriptionThe number of retriever URL’s that have been successfullyaccessed.




Version attribute

DescriptionWeb retriever version.

Type String

VPOOL Max Buf attribute

DescriptionThe number of buffer VPOOL’s which have reached maximumsize.



VPOOL Max Element attribute

DescriptionThe number of element VPOOL’s which have reached maximumsize.



VPOOL Max Marker attribute

DescriptionThe number of marker VPOOL’s which have reached maximumsize.



VPOOL Max Text attribute

DescriptionThe number of text VPOOL’s which have reached maximum size.




VPOOL Max URL attribute

DescriptionThe number of URL VPOOL’s which have reached maximum size.



IW Mail Domain Statistics attribute group

This attribute group provides statistics for IBM Tivoli IntelliWatch incoming andoutgoing mail domains. To see this data, IBM Tivoli IntelliWatch must be installedon the server that is being monitored. If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW Mail DomainStatistics attribute group:



Type String

Timestamp attribute


Type String



Type String


Domain Name attribute

DescriptionThe name of the mail domain user or server.

Type String

Statistic Name attribute

DescriptionThe user defined name.

Type String

Mail Count attribute

DescriptionThe total number of messages.



Mail Size attribute

DescriptionThe total size in bytes.



IW Mail Incoming Statistics attribute group

This attribute group provides statistics for incoming mail. To see this data, IBMTivoli IntelliWatch must be installed on the server that is being monitored. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW MailIncoming Statistics attribute group:




Type String

Timestamp attribute


Type String



Type String

Originating Server attribute

DescriptionThe name of the server that originated the mail.

Type String



Type String

Mail Count Over attribute

DescriptionThe number of times that incoming mail delivery time exceededthe threshold.



Mail Min attribute

DescriptionThe minimum number of seconds for delivery time.



Mail Max attribute


DescriptionThe maximum number of seconds for delivery time.



Mail Avg attribute

DescriptionThe average number of seconds for delivery time.



IW Mail Outgoing Statistics attribute group

This attribute group provides outgoing mail statistics. To see this data, IBM TivoliIntelliWatch must be installed on the server that is being monitored. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW MailOutgoing Statistics attribute group:



Type String

Timestamp attribute


Type String




Type String

Destination Server attribute


Type String



Type String


DescriptionThe total number of messages sent.



Mail Volume attribute

DescriptionThe volume in bytes of outgoing mail.



IW Mail Size Statistics attribute group

This attribute group provides statistics for mail size. To see this data, IBM TivoliIntelliWatch must be installed on the server that is being monitored. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW Mail SizeStatistics attribute group:




Type String

Timestamp attribute


Type String



Type String

Mail Name attribute

DescriptionThe name of the mail user or server.

Type String



Type String


DescriptionThe total number of messages sent.



Mail Max attribute

DescriptionThe maximum message size in bytes.



Mail Avg attribute

DescriptionThe average message size in bytes.




IW Replication Delay Statistics attribute group

This attribute group provides replication delay data. To see this data, IBM TivoliIntelliWatch must be installed on the server that is being monitored. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW ReplicationDelay Statistics attribute group:



Type String

Timestamp attribute


Type String



Type String

Replication Name attribute

DescriptionThe replication name.

Type String


DescriptionThe statistic name.

Type String

Minutes Since Recv attribute


DescriptionThe number of minutes since the last replication was received.



Minutes Since Send attribute

DescriptionThe number of minutes since the last replication was sent.



IW Replication Statistics attribute group

This attribute group provides replication data. To see this data, IBM TivoliIntelliWatch must be installed on the server that is being monitored. If thewarehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String




Type String

Replication Name attribute

DescriptionThe replication name.

Type String



Type String

Pulled KB Received attribute

DescriptionThe number of pulled KB received during replication.



Pulled KB Sent attribute

DescriptionThe number of pulled KB sent during replication.



Pulled Documents Transferred attribute

DescriptionThe pulled documents transferred during replication.




Pushed KB Received attribute

DescriptionThe number of pushed KB received during replication.



Pushed KB Sent attribute

DescriptionThe number of pushed KB sent during replication.



Pushed Documents Transferred attribute

DescriptionThe pushed documents transferred during replication.



Replication Time attribute

DescriptionThe replication time.



Total Missed attribute


DescriptionThe number of missed replications.



Total Successes attribute

DescriptionThe number of replication successes.



IW Server attribute group

This attribute group provides information about IBM Tivoli IntelliWatch events. Tosee this data, IBM Tivoli IntelliWatch must be installed on the server that is beingmonitored. If the warehouse default setting is enabled, data for this attribute groupis stored in Tivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String



DescriptionThe name of the Domino Server running IntelliWatch.

Type String

Event Time attribute

DescriptionTime the event was received

Type Timestamp

Message Priority attribute

DescriptionThe priority of the message: 1=informational, 2=warning, 3=alarm.

Type String

Server Message attribute

DescriptionIBM Tivoli Monitoring event message sent by iwsditm fromIntelliWatch.

Type String

IW View Performance Statistics attribute group

This attribute group provides the response times for Notes database views. To seethis data, IBM Tivoli IntelliWatch must be installed on the server that is beingmonitored. If the warehouse default setting is enabled, data for this attribute groupis stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the IW ViewPerformance Statistics attribute group:



Type String

Timestamp attribute


Type String



Type String




Type String

View Max attribute

DescriptionThe maximum response time in milliseconds.



View Avg attribute

DescriptionThe average response time in milliseconds.



View Count attribute

DescriptionThe number of times the database view was accessed.



View Pct Under Value attribute

DescriptionThe user-specified SLA threshold percent.

Type DisplayNumeric

View Pct Under attribute

DescriptionThe percentage under the user-specified SLA threshold.





Performance Object Status attribute group

The Performance Object Status attribute group contains information that reflectsthe status of other attribute groups so you can see the status of all of theperformance objects that make up this application all at once. Each of these otherperformance attribute groups is represented by a row in this table (or other type ofview). The status for an attribute group reflects the result of the last attempt tocollect data for that attribute group, which allows you to see whether the agent isperforming correctly. Unlike other attribute groups, the Performance Object Statusattribute group does not reflect the state of the monitored application. Thisattribute group is most often used to determine why data is not available for oneof the performance attribute groups. If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


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



Type String

Timestamp attribute


Type String

Query Name attribute - This attribute is a key attribute.

DescriptionThe name of the attribute group.

Type String

Object Name attribute

DescriptionThe name of the performance object.

Type String

Object Type attribute

DescriptionThe type of the performance object.

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


Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v WMI (0)v PERFMON (1)v WMI_ASSOCIATION_GROUP (2)v JMX (3)v SNMP (4)v SHELL_COMMAND (5)v JOINED_GROUPS (6)v CIMOM (7)v CUSTOM (8)v ROLLUP_DATA (9)v WMI_REMOTE_DATA (10)v LOG_FILE (11)v JDBC (12)v CONFIG_DISCOVERY (13)v NT_EVENT_LOG (14)v FILTER (15)


Object Status attribute

DescriptionThe status of the performance object.

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v ACTIVE (0)v INACTIVE (1)


Error Code attribute

DescriptionThe error code associated with the query

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v NO_ERROR (0)v GENERAL_ERROR (1)v OBJECT_NOT_FOUND (2)v COUNTER_NOT_FOUND (3)v NAMESPACE_ERROR (4)v OBJECT_CURRENTLY_UNAVAILABLE (5)v COM_LIBRARY_INIT_FAILURE (6)v SECURITY_INIT_FAILURE (7)v PROXY_SECURITY_FAILURE (9)


v NO_INSTANCES_RETURNED (10)v ASSOCIATOR_QUERY_FAILED (11)v REFERENCE_QUERY_FAILED (12)v NO_RESPONSE_RECEIVED (13)v CANNOT_FIND_JOINED_QUERY (14)v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_1_RESULTS

(15)v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_2_RESULTS

(16)v QUERY_1_NOT_A_SINGLETON (17)v QUERY_2_NOT_A_SINGLETON (18)v NO_INSTANCES_RETURNED_IN_QUERY_1 (19)v NO_INSTANCES_RETURNED_IN_QUERY_2 (20)v CANNOT_FIND_ROLLUP_QUERY (21)v CANNOT_FIND_ROLLUP_ATTRIBUTE (22)v FILE_OFFLINE (23)v NO_HOSTNAME (24)v MISSING_LIBRARY (25)v ATTRIBUTE_COUNT_MISMATCH (26)v ATTRIBUTE_NAME_MISMATCH (27)v COMMON_DATA_PROVIDER_NOT_STARTED (28)v CALLBACK_REGISTRATION_ERROR (29)v MDL_LOAD_ERROR (30)v AUTHENTICATION_FAILED (31)v CANNOT_RESOLVE_HOST_NAME (32)v SUBNODE_UNAVAILABLE (33)v SUBNODE_NOT_FOUND_IN_CONFIG (34)v ATTRIBUTE_ERROR (35)v CLASSPATH_ERROR (36)v CONNECTION_FAILURE (37)v FILTER_SYNTAX_ERROR (38)v FILE_NAME_MISSING (39)v SQL_QUERY_ERROR (40)v SQL_FILTER_QUERY_ERROR (41)v SQL_DB_QUERY_ERROR (42)v SQL_DB_FILTER_QUERY_ERROR (43)v PORT_OPEN_FAILED (44)v ACCESS_DENIED (45)v TIMEOUT (46)v NOT_IMPLEMENTED (47)v REQUESTED_A_BAD_VALUE (48)v RESPONSE_TOO_BIG (49)v GENERAL_RESPONSE_ERROR (50)v SCRIPT_NONZERO_RETURN (51)v SCRIPT_NOT_FOUND (52)


v SCRIPT_LAUNCH_ERROR (53)v IWCONFIG_DB_NOTFOUND (1000)v IWCONFIG_DB_FAILED (1001)


Disk capacity planning for historical dataDisk capacity planning for a monitoring agent is a prediction of the amount of diskspace to be consumed for each attribute group whose historical data is beingcollected. Required disk storage is an important factor to consider when you aredefining data collection rules and your strategy for historical data collection.

The table in this chapter provides the following information required to calculatedisk space for this monitoring agent:v Table is the table name as it is displayed in the warehouse database, if the

attribute group is configured to be written to the warehouse.v Attribute group is the name of the attribute group as it is displayed 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 canbe used for agent disk space planning purposes.

v Database bytes per instance (warehouse) is an estimate of the record length fordetailed records written to the warehouse database, if the attribute group isconfigured to be written to the warehouse. Detailed records are those that havebeen uploaded from the agent for long-term historical data collection. Thisestimate can be used for warehouse disk space planning purposes.

v Aggregate bytes per instance (warehouse) is an estimate of the record length foraggregate records written to the warehouse database, if the attribute group isconfigured to be written to the warehouse. Aggregate records are created by theSummarization agent for attribute groups that have been configured forsummarization. This estimate can be used for warehouse disk space planningpurposes.

In addition to the information in the tables, you must know the number ofinstances of data that you plan to collect. An attribute group can have single ormultiple instances of data depending on the application environment that is beingmonitored. For example, if your attribute group is monitoring each processor inyour computer and you have a dual processor computer, the number of instancesis two.

The following table contains capacity planning information for the data logged byIBM Tivoli Monitoring for Domino.

Table 1. Capacity planning for historical data logged by component Lotus Domino agent

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

KGBAVAIL KGB_AVAILABILITY 3272 3296 3606

KGBDAGNT KGB_DOMINO_AGENT 192 193 290

KGBDCAL KGB_DOMINO_CALENDAR 200 203 330


Table 1. Capacity planning for historical data logged by component Lotus Domino agent (continued)





KGBDCAL64 KGB_DOMINO_CALENDAR64 224 227 426

KGBDCMD KGB_DOMINO_COMMAND 344 362 966

KGBDCFD KGB_DOMINO_CORRUPT_FAILOVER_DB 776 779 816

KGBDDB KGB_DOMINO_DATABASE 248 263 882

KGBDDB64 KGB_DOMINO_DATABASE64 320 335 1066

KGBDDBW KGB_DOMINO_DB_WHITESPACE 300 328 623

KGBDICM KGB_DOMINO_ICM 496 525 1204

KGBDICM64 KGB_DOMINO_ICM64 608 636 1584

KGBDIMAP KGB_DOMINO_IMAP 212 218 462

KGBDIMAP64 KGB_DOMINO_IMAP64 248 254 582

KGBDLDAP KGB_DOMINO_LDAP 336 349 707

KGBDLDAP64 KGB_DOMINO_LDAP64 396 409 915

KGBKGBLOG0 KGB_DOMINO_LOG_FILE 844 855 892

KGBDMAIL KGB_DOMINO_MAIL 264 283 722

KGBDMAIL64 KGB_DOMINO_MAIL64 364 385 1178

KGBDMBD KGB_DOMINO_MAIL_BY_DEST 296 298 407

KGBDMBD64 KGB_DOMINO_MAIL_BY_DEST64 292 294 391

KGBDNETT KGB_DOMINO_NET_TCPIP 196 198 382

KGBDNETT64 KGB_DOMINO_NET_TCPIP64 232 236 510

KGBDREP KGB_DOMINO_REPLICA 196 198 310

KGBDREP64 KGB_DOMINO_REPLICA64 216 218 390

KGBDRPL KGB_DOMINO_REPLICATION 784 789 865

KGBDREPC KGB_DOMINO_REPLICA_CLUSTER 232 243 586

KGBDREPC64 KGB_DOMINO_REPLICA_CLUSTER64 284 295 770

KGBDSRV KGB_DOMINO_SERVER 612 622 914

KGBDSRV64 KGB_DOMINO_SERVER64 664 676 1122

KGBDSRVC KGB_DOMINO_SERVER_CLUSTER 228 238 494

KGBDSMTP KGB_DOMINO_SMTP 200 203 402

KGBDSMTP64 KGB_DOMINO_SMTP64 208 213 442

KGBDTASK KGB_DOMINO_TASKS 476 476 513

KGBDWR KGB_DOMINO_WEB_RETRIEVER 1092 1123 2321

KGBIMDOM KGB_IW_MAIL_DOMAIN_STATISTICS 384 385 476

KGBIMINC KGB_IW_MAIL_INCOMING_STATISTICS 392 395 564

KGBIMOUT KGB_IW_MAIL_OUTGOING_STATISTICS 384 385 476

KGBIMSIZ KGB_IW_MAIL_SIZE_STATISTICS 388 390 520

KGBIREPD KGB_IW_REPLICATION_DELAY_STATISTICS 384 385 452

KGBIREP KGB_IW_REPLICATION_STATISTICS 412 420 616

KGBISERV KGB_IW_SERVER 548 552 589


Table 1. Capacity planning for historical data logged by component Lotus Domino agent (continued)





KGBIVPERF KGB_IW_VIEW_PERFORMANCE_STATISTICS 392 395 564

KGBPOBJST KGB_PERFORMANCE_OBJECT_STATUS 288 289 326

For more information about historical data collection, see the IBM Tivoli MonitoringAdministrator’s Guide.


Chapter 5. Situations reference

This chapter contains an overview of situations, references for detailed informationabout situations, and descriptions of the predefined situations included in thismonitoring agent.

About situationsA situation is a logical expression involving one or more system conditions.Situations are used to monitor the condition of systems in your network. You canmanage situations from Tivoli Enterprise Portal by using the Situation Editor.

The monitoring agents that you use to monitor your system environment aredelivered with a set of predefined situations that you can use as-is or you cancreate new situations to meet your requirements. Predefined situations containattributes that check for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can beginusing the Lotus Domino agent. You can examine and, if necessary, change theconditions or values being monitored by a predefined situation to those best suitedto your enterprise.

You can display predefined situations and create your own situations using theSituation Editor. The left frame of the Situation editor initially lists the situationsassociated with the Navigator item that you selected. When you click a situationname or create a new situation, the right frame opens with the following tabs:

FormulaFormula describing condition being tested

DistributionList of managed systems (operating systems, subsystems, or applications)to which the situation can be distributed. All of the Lotus Domino agentmanaged systems are assigned by default.

Expert adviceComments and instructions to be read in the event workspace

ActionCommand to be sent to the system

Until Options to close the event after a period of time, or when another situationbecomes true

More information about situationsIBM Tivoli Monitoring User’s Guide contains more information about predefined andcustom situations and how to use them to respond to alerts.

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


Predefined situationsThis monitoring agent contains the following predefined situations, which areorganized by Navigator item:v Lotus Domino

– Not applicablev Availability

– KGB_Domino_Serv_Avail_Crit– KGB_Domino_Srv_Clus_Avail_Crit– KGB_Domino_Serv_Config_Crit– KGB_Domino_Srv_Clus_Avail_Warn

v Cluster– Not applicable

v Database– KGB_Domino_Failover_Warn– KGB_Domino_Whitespace_Pct_Warn– KGB_Domino_DB_Size_Warn

v Mail– KGB_Domino_Mail_Dead_Warn– KGB_Domino_Mail_Waiting_Warn– KGB_Domino_Mail_Dead_Warn_2– KGB_Domino_Mail_Waiting_Warn_2

v Server– KGB_Domino_Serv_Avail_Idx_Crit– KGB_Domino_Serv_Sess_Drop_Crit– KGB_Domino_Srv_Avl_Idx_Crit_2– KGB_Domino_Srv_Ses_Drop_Crit_2– KGB_Domino_SMTP_Task_Warn– KGB_Domino_Rep_Miss_Crit

v Sessions– Not applicable

The remaining sections of this chapter contain descriptions of each of thesesituations. The situations are organized by Navigator item. The followinginformation is provided about each situation:

DescriptionInformation about the conditions that the situation tests

FormulaSyntax that contains one or more logical expressions describing theconditions for the situation to monitor

Run at startupWhether the situation is automatically distributed to instances of the agentor is available for manual distribution

Sampling intervalNumber of seconds that elapses between one sample of data that themonitoring agent collects for the server and the next sample


Situation persistenceWhether the conditions specified in the situation evaluate to ″true″ for thedefined number of occurrences in a row before the situation is raised. Thedefault of 1 means no persistence checking takes place.

SeveritySeverity of the predefined events: Warning, Informational, or Critical

Clearing conditionsControls when a true situation closes: after a period of time, when anothersituation is true, or whichever occurs first if both are selected.

Lotus Domino Navigator itemThere are no predefined situations for this Navigator item.

Availability Navigator item

KGB_Domino_Serv_Avail_Crit situation

DescriptionThe Status of the Domino Server is not responding.

The situation will be evaluated for each distinct value of the COMPONENTattribute.

Formula*IF ( ( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Status.bat' *AND *SCANKGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5032' ) *OR ( *VALUEKGB_AVAILABILITY.Name *EQ 'KGB_Domino_Status.sh' *AND *SCANKGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5032' ) )

See “Attribute groups and attributes for the Lotus Domino agent” on page 25 fordescriptions of the attributes in this formula.

Run at startupThis situation is automatically distributed to instances of this agent.

Sampling interval5 minutes

Situation persistenceThe number of times the conditions of the situation must occur for the situation tobe true is 1.

SeverityCritical

Clearing conditionsThe situation clears when the condition becomes false.

KGB_Domino_Srv_Clus_Avail_Crit situation

DescriptionOnly one Domino Server in cluster is responding.

Chapter 5. Situations reference 169


Formula*IF ( ( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Cluster_Status.bat'*AND *SCAN KGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5044' ) *OR( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Cluster_Status.sh' *AND*SCAN KGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5044' ) )


Run at startupThis situation is available for distribution.



SeverityCritical


KGB_Domino_Serv_Config_Crit situation

DescriptionThe kgbconfig.sh script must be run for the Lotus Domino agent.


Formula*IF ( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Status.sh' *AND *SCANKGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5037' )





SeverityCritical



KGB_Domino_Srv_Clus_Avail_Warn situation

DescriptionOne or more Domino Servers in the cluster are not responding.


Formula*IF ( ( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Cluster_Status.bat'*AND *SCAN KGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5043' ) *OR( *VALUE KGB_AVAILABILITY.Name *EQ 'KGB_Domino_Cluster_Status.sh' *AND*SCAN KGB_AVAILABILITY.Functionality_Test_Message *EQ 'KGB5043' ) )





SeverityWarning


Cluster Navigator itemThere are no predefined situations for this Navigator item.

Database Navigator item

KGB_Domino_Failover_Warn situation

DescriptionThe clustered Domino server has a failover status.

The situation will be evaluated for each distinct value of the SN attribute.

Formula*IF *VALUE KGB_DOMINO_CORRUPT_FAILOVER_DB.Failover_Status *EQ 'Success'






SeverityWarning


KGB_Domino_Whitespace_Pct_Warn situation

DescriptionThe Domino database whitespace percent has exceeded 20%.


Formula*IF *VALUE KGB_DOMINO_DB_WHITESPACE.DB_Whitespace_Pct *GT 20





SeverityWarning


KGB_Domino_DB_Size_Warn situation

DescriptionThe Domino database size has exceeded the warning threshold.


Formula*IF *VALUE KGB_DOMINO_DB_WHITESPACE.DB_Size *GT 3145728






SeverityWarning


Mail Navigator item

KGB_Domino_Mail_Dead_Warn situation

DescriptionThis situation is superseded by Domino_Mail_Dead_Warn_2.


Formula*IF *VALUE KGB_DOMINO_MAIL.Dead *GT 50





SeverityWarning


KGB_Domino_Mail_Waiting_Warn situation

DescriptionThis situation is superseded by Domino_Mail_Waiting_Warn_2.



Formula*IF *VALUE KGB_DOMINO_MAIL.Waiting *GT 200





SeverityWarning


KGB_Domino_Mail_Dead_Warn_2 situation

DescriptionNumber of undeliverable messages has exceeded the threshold.


Formula*IF *VALUE KGB_DOMINO_MAIL64.Dead *GT 50





SeverityWarning



KGB_Domino_Mail_Waiting_Warn_2 situation

DescriptionNumber of outgoing mail messages has exceeded the threshold.


Formula*IF *VALUE KGB_DOMINO_MAIL64.Waiting *GT 200





SeverityWarning


Server Navigator item

KGB_Domino_Serv_Avail_Idx_Crit situation

DescriptionThis situation is superseded by Domino_Srv_Avl_Idx_Crit_2.


Formula*IF *VALUE KGB_DOMINO_SERVER.Availability_Index *LT 30





SeverityCritical



KGB_Domino_Serv_Sess_Drop_Crit situation

DescriptionThis situation is superseded by Domino_Srv_Ses_Drop_Crit_2.


Formula*IF *VALUE KGB_DOMINO_SERVER.Sessions_Dropped *GT 15





SeverityCritical


KGB_Domino_Srv_Avl_Idx_Crit_2 situation

DescriptionServer availability index has dropped below the critical level.


Formula*IF *VALUE KGB_DOMINO_SERVER64.Availability_Index *LT 30






SeverityCritical


KGB_Domino_Srv_Ses_Drop_Crit_2 situation

DescriptionNumber of server sessions dropped exceeds the crit threshold.


Formula*IF *VALUE KGB_DOMINO_SERVER64.Sessions_Dropped *GT 15





SeverityCritical


KGB_Domino_SMTP_Task_Warn situation

DescriptionSMTP and SMTP port status monitor.


Formula*IF *MISSING KGB_DOMINO_TASKS.Task_Name *EQ ( 'SMTP Server' )






SeverityWarning


KGB_Domino_Rep_Miss_Crit situation

DescriptionCheck for missed replications.


Formula*IF *VALUE KGB_DOMINO_REPLICATION.Hit_Miss *EQ 'miss'



Sampling intervalNone. Data is analyzed when it becomes available.


SeverityCritical

Clearing conditionsThe situation does not clear automatically.

Sessions Navigator itemThere are no predefined situations for this Navigator item.


Chapter 6. Take Action commands reference

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

About Take Action commandsTake Action commands can be run from the portal client or included in a situationor 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 responseto system conditions. For example, you can use a Take Action command to send acommand to restart a process on the managed system or to send a text message toa cell phone.

Advanced automation uses policies to perform actions, schedule work, andautomate manual tasks. A policy comprises a series of automated steps calledactivities that are connected to create a workflow. After an activity is completed,Tivoli Enterprise Portal receives return code feedback, and advanced automationlogic responds with subsequent activities prescribed by the feedback.

A basic Take Action command displays the return code of the operation in amessage box that is displayed after the action completes or in a log file. After youclose this window, no further information is available for this action.

More information about Take Action commandsFor more information about working with Take Action commands, see the IBMTivoli Monitoring User’s Guide.

Predefined Take Action commandsThe Lotus Domino agent does not provide predefined Take Action commands.


Chapter 7. Policies reference

This chapter contains an overview of policies, references for detailed informationabout policies, and descriptions of the predefined policies included in thismonitoring agent, if any.

About policiesPolicies are an advanced automation technique for implementing more complexworkflow strategies than you can create through simple automation.

A policy is a set of automated system processes that can perform actions, schedulework for users, or automate manual tasks. You use the Workflow Editor to designpolicies. You control the order in which the policy executes a series of automatedsteps, which are also called activities. Policies are connected to create a workflow.After an activity is completed, Tivoli Enterprise Portal receives return codefeedback and advanced automation logic responds with subsequent activitiesprescribed by the feedback.

More information about policiesThis monitoring agent does not provide predefined policies. For more informationabout working with policies, see the IBM Tivoli Monitoring User’s Guide.

For information about using the Workflow Editor, see the IBM Tivoli MonitoringAdministrator’s Guide or the Tivoli Enterprise Portal online help.

Predefined policiesThe Lotus Domino agent does not provide predefined policies.


Chapter 8. Troubleshooting

This chapter provides agent-specific troubleshooting information. See the IBMTivoli Monitoring Troubleshooting Guide for general troubleshooting information. Alsosee “Support information” on page 206 for other problem-solving options.

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in Chapter 2, “Agent-specific installation andconfiguration information for the monitoring agent,” on page 5.

Gathering product information for IBM Software SupportBefore contacting IBM Software Support about a problem you are experiencingwith this product, gather the information in Table 2 that relates to the problem.

Table 2. 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 subdirectoryon the host computer. See “Trace logging” on page 184 for lists of all trace log files andtheir locations. See the IBM Tivoli Monitoring User’s Guide for general information aboutthe IBM Tivoli Monitoring environment.

Lotus Dominoinformation

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 forIBM Tivoli Monitoring

Version number of the following members of the monitoring environment:v IBM Tivoli Monitoring. Also provide the patch level, if available.v IBM Tivoli Composite Application Manager Agent for Lotus Domino V6.2.1

To find these version and patch numbers, perform the following actions depending onyour operating system:

v UNIX

1. Type install_dir/bin/cinfo on the command line.

2. Type 1 to show the products installed and the versions.

v Windows

In Manage Tivoli Monitoring Services, click Browse Settings.

–OR–

Look in install_dir/InstallITM/kincinfo.

Screen captures Screen captures of incorrect output, if any.

(UNIX only) Core dumpfiles

If the system stops on UNIX systems, collect the core dump file from install_dir/bindirectory, where install_dir is the directory where you installed the monitoring agent.

See http://www.ibm.com/software/support/probsub.html for more informationabout working with IBM Software Support.

Built-in troubleshooting featuresThe primary troubleshooting feature in the Lotus Domino agent is logging. Loggingrefers to the text messages and trace data generated by the Lotus Domino agent.Messages and trace data are sent to a file.


http://www.ibm.com/software/support/probsub.html

Trace data captures transient information about the current operating environmentwhen a component or application fails to operate as designed. IBM SoftwareSupport personnel use the captured trace information to determine the source ofan error or unexpected condition. See “Trace logging” for more information.

Problem classificationThe following types of problems might occur with the Lotus Domino agent:v Installation and configurationv General usage and operationv Display of monitoring datav Take Action commands

This chapter provides symptom descriptions and detailed workarounds for theseproblems, as well as describing the logging capabilities of the monitoring agent.See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Trace loggingTrace logs capture information about the operating environment when componentsoftware fails to operate as intended. The principal log type is the RAS (Reliability,Availability, and Serviceability) trace log. These logs are in the English languageonly. The RAS trace log mechanism is available for all components of IBM TivoliMonitoring. Most logs are located in a logs subdirectory on the host computer. Seethe following sections to learn how to configure and use trace logging:v “Principal trace log files” on page 186v “Examples: using trace logs” on page 190v “Setting RAS trace parameters” on page 191

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as″RAS1″.

IBM Software Support uses the information captured by trace logging to trace aproblem to its source or to determine why an error occurred. All components inthe IBM Tivoli Monitoring environment have a default tracing level. The tracinglevel can be changed on a per-component level to adjust the type of traceinformation collected, the degree of trace detail, the number of trace logs to bekept, and the amount of disk space used for tracing.

Overview of log file managementTable 3 on page 187 provides the names, locations, and descriptions of RAS1 logfiles. The log file names adhere to the following naming convention:

Windows systemshostname_productcode_program_HEXtimestamp-nn.log

Linux and UNIX systemshostname_productcode_HEXtimestamp-nn.log

where:v hostname is the host name of the computer where the monitoring component is

running.


v productcode is the two-character product code. For IBM Tivoli Monitoring forDomino, the product code is gb.

v program is the name of the program being run.v HEXtimestamp is a hexadecimal time stamp representing the time at which the

program started.v nn is a rolling log suffix. See “Examples of trace logging” for details of log

rolling.

Examples of trace loggingThe Lotus Domino agent is a multi-instance agent that has logs for the following:v kgbagent.exev kgbclient.exev kgbiwevent.exev kgbstart.sh (UNIX and Linux only)v LG0

On Windows operating systems, when you create an instance, kgbagent.exe iscopied to create an instance-specific copy. If the instance name is amsc282c, thenkgbagent.exe is copied to kgbagent_amsc282c.exe. The same thing happens forkgbclient.exe, which is copied to kgbclient_amsc282c.exe. On UNIX and Linuxoperating systems, when you create an instance, the files are not copied to a newname. Each instance has its own log.

For example, if a IBM Tivoli Monitoring for Domino is running on the Windowssystem ″server01″, the RAS log file for that agent might be named as follows:server01_gb_kgbagent_437fc59-01.log

When a multi-instance agent such as the Lotus Domino agent creates a log file, thefile is named as follows:hostname_pc_instance_name_kgbclient_instance_name_starttime-number.log

For example:AMSC282_gb_amsc282_KGBCLIENT_amsc282_451abecb-01.log

Often, the hostname and the instance name are the same. Also, the client namemight contain the instance name, which helps you differentiate among the manyclients that might be running if there are many instances of the agent running.When that happens, it looks like the same string appears in the log file namemultiple times.

As the program runs, the first log (nn=01) is preserved because it contains programstartup information. The remaining logs ″roll.″ In other words, when the set ofnumbered logs reach a maximum size, the remaining logs are overwritten insequence.

Each time a program is started, a new timestamp is assigned to maintain a shortprogram history. For example, if the IBM Tivoli Monitoring for Domino is startedtwice, it might have log files as follows:v kgbagent.exe

– Windowshostname_gb_instance name_kgbagent_timestamp-nn.log

For example:

Chapter 8. Troubleshooting 185

AMSC282_gb_amsc282c_kgbagent_45267ef7-01.log

– UNIX or Linuxhostname_gb_instance_name_kgbagent_timestamp-nn.log

For example:amsaix20_gb_aix20_kgbagent_45267ef7-01.log

v kgbclient.exe– Windows

hostname_gb_instance_name_KGBCLIENT_instance_name_timestamp-nn.log

For example:AMSC282_gb_amsc282c_KGBCLIENT_amsc282c_45267ef7-01.log

– UNIX or Linuxhostname_gb_instance_name_kgbclient_timestamp-nn.log

For example:amsaix20_gb_aix20_kgbclient_45267ef7-01.log

v kgbiwevent.exe– Windows

hostname_gb_instance_name_kgbiwevent_timestamp-nn.log

For example:AMSC282_gb_server1amsc282_kgbiwevent_4526ad8f-01.log

– UNIX or Linuxhostname_gb_instance_name_kgbiwevent_timestamp-nn.log

For example:amsaix20_gb_aix20_kgbiwevent_aix20_45267ef7-01.log

v kgbstart.shUNIX or Linux onlykgbstart_instance_name.log

For example:kgbstart_pa2kk.log

Other logs, such as logs for Take Action command logs, have a similar syntax as inthe 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 andsend the RAS1 log that matches any problem occurrence that you report.

Principal trace log files

Table 3 on page 187 contains locations, file names, and descriptions of trace logsthat can help determine the source of problems with agents.


Table 3. Trace log files for troubleshooting agents

System where logis located

File name and path Description

On the TivoliEnterpriseMonitoring Server

v Windows: The file in theinstall_dir\InstallITM path

v UNIX: The candle_installation.log file inthe install_dir/logs path

Provides details about products that areinstalled.Note: Trace logging is enabled by default. Aconfiguration step is not required to enable thistracing.

The Warehouse_Configuration.log file is inthe following location on Windows systems:install_dir\InstallITM

Provides details about the configuration of datawarehousing for historical reporting.

The name of the RAS log file is as follows:

v Windows: install_dir\logs\hostname_ms_timestamp-nn.log

v UNIX: install_dir/logs/hostname_ms_timestamp.log

Note: File names for RAS1 logs include ahexadecimal time stamp.

Also on UNIX, a log with a decimal timestamp is provided:hostname_productcode_timestamp.log andhostname_productcode_ timestamp.pidnnnnn inthe install_dir/logs path, where nnnnn is theprocess ID number.

Traces activity on the monitoring server.

On the TivoliEnterprise PortalServer

The name of the RAS log file is as follows:

v Windows: install_dir\logs\hostname_cq_HEXtimestamp-nn.log

v UNIX: install_dir/logs/hostname_cq_HEXtimestamp-nn.log

Note: File names for RAS1 logs include ahexadecimal time stamp.

Also on UNIX, a log with a decimal timestamp is provided:hostname_productcode_timestamp.log andhostname_productcode_ timestamp.pidnnnnn inthe install_dir/logs path, where nnnnn is theprocess ID number.

Traces activity on the portal server.

The teps_odbc.log file is located in thefollowing path

v Windows: install_dir\InstallITM path.

v UNIX: install_dir/logs

When you enable historical reporting, this logfile traces the status of the warehouse proxyagent.


Table 3. Trace log files for troubleshooting agents (continued)



On the computerthat hosts themonitoring agent

The RAS1 log files are as follows:

v Windows:hostname_gb_instance_kgbagent_HEXtimestamp-nn.log in theinstall_dir\tmaitm6\logs directory

v UNIX:hostname_gb_instance_HEXtimestamp-nn.log in theinstall_dir/logs directory

Also on UNIX, a log with a decimal timestamp is provided:hostname_gb_timestamp.log andhostname_gb_ timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn isthe process ID number.

These logs are in the following directories:

v Windows: install_dir\tmaitm6\logs


v Linux: install_dir/logs

Linux also provides the followingadditional logs:

– hostname_gb_timestamp.log

– hostname_gb_ timestamp.pidnnnnn inthe install_dir/logs path, wherennnnn is the process ID number

Traces activity of the monitoring agent.

See “Examples of trace logging” on page 185 inthis chapter for the locations of the LotusDomino agent logs.


Table 3. Trace log files for troubleshooting agents (continued)




The agent operations log files are as follows:

instance_hostname_GB.LG0 is the current logcreated when the agent was started

instance_hostname_GB.LG1 is the backup ofthe previous log

These logs are in the following directorydepending on the operating system that youare using:




For the Lotus Domino agent:

v Windows:instance_name_hostname_GB.LG0

For example:

amsc282B_AMSC282_GB.LG0

v UNIX or Linux:instance_name:hostname.domain_name_depending_on_OS_settings:GB.LG0

For example:

aix20:amsaix20.tivlab.raleigh.ibm.com:GB.LG0

aix202:amsaix20.tivlab.raleigh.ibm.com:GB.LG0

aix202a:amsaix20.tivlab.raleigh.ibm.com:GB.LG0

Shows whether the agent was able to connect tothe monitoring server. Shows which situationsare started and stopped, and shows other eventswhile the agent is running. A new version of thisfile is generated every time the agent isrestarted.

IBM Tivoli Monitoring generates one backupcopy of the *.LG0 file with the tag .LG1. View.LG1 to learn the following details regarding theprevious 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.

If instance_name:hostname.domain_name is greaterthan 32 characters, then the characters that arefarthest to the right are truncated from thedomain name.


The Take Action command log files are asfollows:

v host_gb_instance_takeactioncommand.log

The logs are in the following directories:




Traces activity each time a Take Actioncommand runs. For example, when ahypothetical start_command Take Actioncommand runs, IBM Tivoli Monitoring generatesa 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), asfollows: 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 canrepresent 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 isalways retained, because it includes configuration parameters.

productcode specifies the product codes, for example, um for Universal Agent or nt for Windows.


See the IBM Tivoli Monitoring Installation and Setup Guide for more information onthe complete set of trace logs that are maintained on the monitoring server.

Examples: using trace logsTypically, IBM Software Support applies specialized knowledge to analyze tracelogs to determine the source of problems. You can open trace logs in a text editorto learn some basic facts about your IBM Tivoli Monitoring environment. Thefollowing examples are from the Tivoli Enterprise Monitoring Server log.

Example oneThis excerpt shows the typical log for a failed connection between amonitoring 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 tobroker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK

(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unableto find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

Example twoThe following excerpts from the trace log for the monitoring server show thestatus of an agent, identified here as ″Remote node.″ The name of thecomputer where the agent is running is SERVER5B:

(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:INST1:GB is ON-LINE.. . .(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:INST1:GB is OFF-LINE.

Key points regarding the preceding excerpt:v The monitoring server appends the GB product code to the server name

and instance name to form a unique name (SERVER5B:INST1:GB) for thisinstance of the Lotus Domino agent. This unique name enables you todistinguish multiple monitoring products that might be running onSERVER5B.

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 logentries that were generated while the agent was running.

v Between the ON-LINE and OFF-LINE log entries, the agent wascommunicating with the monitoring server.

v The ON-LINE and OFF-LINE log entries are always available in thetrace log. All trace levels that are described in “Setting RAS traceparameters” on page 191 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 EnterpriseMonitoring Services window is displayed.

2. Right-click a component and select Advanced > View Trace Log in the pop-upmenu. For example, if you want to view the trace log of the Lotus Dominoagent, right-click the name of the that agent in the window. You can also usethe viewer to access remote logs.

Note: The viewer converts time stamps in the logs to a format that is easier toread.


Setting RAS trace parameters

ObjectivePinpoint a problem by setting detailed tracing of individual components of themonitoring agent and modules.

Background InformationThe Lotus Domino agent uses RAS1 tracing and generates the logs described inTable 3 on page 187. The default RAS1 trace level is ERROR.

Before you beginSee “Overview of log file management” on page 184 to ensure that you understandlog rolling and can reference the correct log files when you manage log filegeneration.

After you finishMonitor the size of the logs directory. Default behavior can generate a total of 45 to60 MB for each agent that is running on a computer. For example, each databaseinstance that you monitor can generate 45 to 60 MB of log data. See the″Procedure″ section to learn how to adjust file size and numbers of log files toprevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlikethe RAS1 log files that are pruned automatically, other log types can growindefinitely, for example, the logs in Table 3 on page 187 that include a process IDnumber (PID).

Consider using collector trace logs as an additional source of troubleshootinginformation.

Note: The KDC_DEBUG setting and the Maximum error tracing setting cangenerate a large amount of trace logging. Use them only temporarily, whileyou are troubleshooting problems. Otherwise, the logs can occupy excessiveamounts of hard disk space.

ProcedureOn 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 following are selection examples:v General error tracing. KBB_RAS1=ERRORv Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)

v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

Notes: As this example shows, you can set multiple RAS tracing options in asingle statement.

To set tracing for the Lotus Domino agent, use UNIT:kgb ALL.5. Modify the value for ’Maximum Log Size Per File (MB)″ to change the log file

size (changes LIMIT value).


6. Modify the value for ’Maximum Number of Log Files Per Session″ to changethe 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 thenumber 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 informationthat can help you diagnose communications and connectivity problemsbetween the monitoring agent and the monitoring server.

Note: The KDC_DEBUG setting and the Maximum error tracing setting cangenerate a large amount of trace logging. Use them only temporarily,while you are troubleshooting problems. Otherwise, the logs can occupyexcessive amounts of hard disk space.

9. Click OK. You see a message reporting a restart of the monitoring agent so thatyour changes take effect.

You can also manually edit the RAS1 trace logging parameters using this method:1. Open the trace options file:

Windows: install_dir\tmaitm6\KGBENVUNIX: install_dir/config/gb.ini

2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. Forexample, if you want detailed trace logging, set the Maximum Tracingoption:KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation oflog files:v MAXFILES: the total number of files that are to be kept for all startups of a

given program. When this value is exceeded, the oldest log files arediscarded. Default value is 9.

v LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Defaultvalue 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.

Notes: The KBB_RAS1_LOG parameter also provides for the specification ofthe log file directory, log file name, and the inventory control filedirectory and name. Do not modify these values or log information canbe lost.

For the Lotus Domino agent, on Windows each instance of the agenthas unique trace settings, but the three executable files for one instancedo not have unique trace settings. On UNIX and Linux, trace settingsare global across the instances. There are no trace settings for the LG0log for Windows, UNIX, or Linux.

4. Restart the monitoring agent so that your changes take effect.


Problems and workaroundsThe following sections provide symptoms and workarounds for problems thatmight occur with the Lotus Domino agent:v “Installation and configuration troubleshooting” on page 193v “Remote deployment troubleshooting” on page 197v “Agent troubleshooting” on page 197v “Workspace troubleshooting” on page 201v “Situation troubleshooting” on page 203

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in Chapter 2, “Agent-specific installation andconfiguration information for the monitoring agent,” on page 5.

This chapter provides agent-specific troubleshooting information. See the IBMTivoli Monitoring Troubleshooting Guide for general troubleshooting information.

Installation and configuration troubleshootingThis section provides tables that show solutions for installation, configuration, anduninstallation problems.

Table 4. Problems and solutions for installation and configuration

Problem Solution

(UNIX only) During a command-line installation, youchoose to install a component that is already installed,and you see the following warning:

WARNING - you are about to installthe SAME version of "component_name"

where component_name is the name of the componentthat you are attempting to install.Note: This problem affects UNIX command-lineinstallations. If you monitor only Windowsenvironments, you see this problem if you choose toinstall a product component (for example, a monitoringserver) on UNIX.

You must exit and restart the installation process. Youcannot return to the list where you selected componentsto install. When you run the installer again, do notattempt to install any component that is already installed.

A problem can arise when you install and configure anew monitoring agent on a computer where otheragents are running as described in this example:

v Agents are running on a computer andcommunicating with a Tivoli Enterprise MonitoringServer, called TEMS1.

v You install a new agent on the same computer andyou want this agent to communicate with a differentmonitoring server, called TEMS2.

v When you configure the new agent to communicatewith TEMS2, all the existing agents are reconfiguredto communicate with TEMS2.

You must reconfigure the previously existing agents torestore their communication connection with TEMS1. Forexample, you can right-click the row for a specific agentin the Manage Tivoli Enterprise Monitoring Services, andselect Reconfigure. See the IBM Tivoli MonitoringInstallation and Setup Guide for more information onreconfiguration.


Table 4. 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, performthe following steps:

1. Click Start > Programs > IBM Tivoli Monitoring >Manage Tivoli Enterprise Monitoring Services. TheManage Tivoli Enterprise Monitoring Services windowis displayed.

2. Right-click the Windows agent and select BrowseSettings. 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 SoftwareSupport for analysis.

A message similar to ″Unable to find running CMS onCT_CMSLIST″ in the log file is displayed.

If a message similar to ″Unable to find running CMS onCT_CMSLIST″ is displayed in the Log file, the agent isnot able to connect to the monitoring server. Confirm thefollowing points:

v Do multiple network interface cards (NICs) exist on thesystem?

v If multiple NICs exist on the system, find out whichone is configured for the monitoring server. Ensure thatyou specify the correct host name and port settings forcommunication in the IBM Tivoli Monitoringenvironment.

The system is experiencing high CPU usage. Agent process: View the memory usage of the KGBCMAprocess. If CPU usage seems to be excessive, recycle themonitoring agent.

Network Cards: The network card configurations candecrease the performance of a system. Each of the streamof packets that a network card receives (assuming it is abroadcast or destined for the under-performing system)must generate a CPU interrupt and transfer the datathrough the I/O bus. If the network card in question is abus-mastering card, work can be off-loaded and a datatransfer between memory and the network card cancontinue without using CPU processing power.Bus-mastering cards are generally 32-bit and are based onPCI or EISA bus architectures.

After installing the Lotus Domino agent on a Windowssystem, you receive a message that the Windowscomputer must be rebooted (KGB5039I). Theenvironment variables are not available in the systemenvironment.

Reboot the system to make the system environmentvariables available.

When configuring the Lotus Domino agent, you receivethe following warning message: An agent with thatname already exists.

An instance name that is not valid might have beenprovided, for example ″Agen</″. Provide an instancename that is valid.

When configuring the Lotus Domino agent, you receivea java exception.

Avoid using parameters such as ?,/,&,$ in the instancename, Domino Server name, or notes.ini file name.

Unable to install the agent on a UNIX or Linuxoperating system.

Add a NotesProgram entry to the notes.ini file. Runkgbconfing.sh again and start the agent.


Table 4. Problems and solutions for installation and configuration (continued)

Problem Solution

You receive the following error message whenconfiguring an agent using itmcmd config -A -o xxxxgb: This agent was previously configured using the HostSpecific Configuration option (the -t option on thecommand line). To reconfigure, remember to selectCREATE HOST SPECIFIC CONFIGURATION’ (on theGUI) or use the command line -t option.

This message does not have an adverse impact on theinstance configuration.

When installing locally (install.sh) to a UNIX or Linuxoperating system, you receive the following error string:Initializing ... ./install.sh[24]: <vrmf>: syntaxerror awk: syntax error near line 1 awk: illegalstatement near line 1 awk: syntax error near line 1awk: illegal statement near line 1 Initializing ...chown: cannot access `.=\\265\\263.(': No such fileor directory chmod: cannot access `.=\\265\\263.(':No such file or directory

Ignore this error.

You want to install a 32-bit and 64-bit Lotus Dominoagent on the same UNIX system.

The 32-bit and 64-bit installs must be in differentdirectories. Both installs must not use the defaultcandlehome directory of: /opt/IBM/ITM.

You want to remote deploy or locally install, a 32-bitLotus Domino agent to a 64-bit AIX system.

This is currently not supported by IBM Tivoli Monitoring.

Do the following to workaround this problem:

1. Run the local installation of the Lotus Domino agent

2. Select the 32-bit version under “Product packages areavailable for the following operating systems andcomponent support categories”

3. After installation is complete, edit the gbaix5x3.ver in<install>/registry.

After the last existing runArch = line, add thefollowing lines starting in column 1:

runArch = aix516runArch = aix526runArch = aix536

4. Save the gbaix5x3.ver or file.

When installing the Lotus Domino agent information onthe ″IBM JAVA information″ and ″Choose installationdrive for JAVA″ panels are corrupt.

None. This is a current limitation. Check future releasesor service levels of IBM Tivoli Monitoring for this fix.

On UNIX or Linux, if a Lotus Domino agent instance isconfigured with the same name as the hostname, otherinstances configured using the GUI cannot connect tothe monitoring server.

Configure the instances using itmcmd config fromcommand line.


Table 5. General problems and solutions for uninstallation

Problem Solution

On Windows, uninstallation ofIBM Tivoli Monitoring fails touninstall the entire environment.

Be sure that you follow the general uninstallation process described in the IBMTivoli Monitoring Installation and Setup Guide:

1. Remove Tivoli Enterprise Monitoring Server Application support bycompleting the following steps:

a. Use Manage Tivoli Enterprise Monitoring Services.

b. Select Tivoli Enterprise Monitoring Server.

c. Right-click and select Advanced.

d. Select Remove TEMS application support.

e. Select the agent to remove its application support.

2. Uninstall monitoring agents first, as in the following examples:

v Uninstall a single monitoring agent for a specific database.

-OR-

v Uninstall all instances of a monitoring product, such as IBM TivoliMonitoring for Databases.

3. Uninstall IBM Tivoli Monitoring.

The way to remove inactivemanaged systems (systems whosestatus is OFFLINE) from theNavigator tree in the portal is notobvious.

Use the following steps to remove, but not uninstall, an offline managed systemfrom the Navigator tree:

1. Click the Enterprise icon in the Navigator tree.

2. Right-click, then click Workspace > Managed System Status.

3. Right-click the offline managed system, and select Clear offline entry.

If you also want to uninstall the monitoring agent, use the procedure describedin the IBM Tivoli Monitoring Installation and Setup Guide.

IBM Tivoli Monitoring might notbe able to generate a uniquename for monitoring componentsbecause of the truncation ofnames that the productautomatically generates.

If the agent supports multi-instances, IBM Tivoli Monitoring automaticallycreates a name for each monitoring component by concatenating the subsystemname, host name, and product code separated by colons(subsystem_name:hostname:KGB).Note: When you monitor a multinode system, such as a database, IBM TivoliMonitoring adds a subsystem name to the concatenated name, typically adatabase instance name.The length of the name that IBM Tivoli Monitoringgenerates is limited to 32 characters. Truncation can result in multiplecomponents having the same 32-character name. If this problem happens,shorten the hostname portion of the name as follows:

1. Open the configuration file for the monitoring agent, which is located in thefollowing path:

v On Windows: install_dir\tmaitm6\Kproduct_codeCMA.INI. For example,the product code for the Monitoring Agent for Windows OS is NT. The filename is KNTCMA.INI.

v On UNIX and Linux: itm_home/config/product_code.ini andproduct_code.config. For example, the file names for the MonitoringAgent for UNIX OS is ux.ini and ux.config.

2. Find the line the begins with CTIRA_HOSTNAME=.

3. Type a new name for host name that is a unique, shorter name for the hostcomputer. The final concatenated name including the subsystem name, newhost name, and KGB, cannot be longer than 32 characters.Note: You must ensure that the resulting name is unique with respect to anyexisting monitoring component that was previously registered with the TivoliEnterprise Monitoring Server.

4. Save the file.

5. Restart the agent.


Remote deployment troubleshootingTable 6 lists problems that might occur with remote deployment. This sectionprovides information about troubleshooting remote deployment of the monitoringagent. See the IBM Tivoli Monitoring Troubleshooting Guide for generaltroubleshooting information.

This section describes problems and solutions for remote deployment and removalof agent software using Agent Remote Deploy.

Table 6. Remote deployment problems and solutions

Problem Solution

While you are using the remote deployment featureto install the Lotus Domino agent, an emptycommand window is displayed on the targetcomputer. This problem occurs when the target ofremote deployment is a Windows computer. (See theIBM Tivoli Monitoring Installation and Setup Guide formore information on the remote deploymentfeature.)

Do not close or modify this window. It is part of theinstallation process and is dismissed automatically.

The removal of a monitoring agent fails when youuse the remote removal process in the TivoliEnterprise Portal desktop or browser.

This problem might occur when you attempt the remoteremoval process immediately after you have restarted theTivoli Enterprise Monitoring Server. You must allow time forthe monitoring agent to refresh its connection with the TivoliEnterprise Monitoring Server before you begin the remoteremoval process.

The Domino Server name can be parsed incorrectlywhen remotely deploying the monitoring agentusing the canonical server name.

Use the Domino Server shortname xxx/yy for theconfig.KGB_SERVER input parameter when using the tacmdcommand.

Remotely configuring a Lotus Domino agentinstance overwrites an existing instance instead ofproviding a message that the instance already exists

Use tacmd listSystems before running itmcmd addSystemprior to configuring a new instance.

On Windows, if the Lotus Domino agent isupgraded remotely, the agent instances configuredbefore upgrading are lost.

Run %CANDLE_HOME%\InstallITM\updategbinstance.bat torestore and upgrade the instances.

Remote deployment might fail if the monitoringserver support, portal server support, and the LotusDomino agent support for the desktop and browserclient are installed on the same computer.

Deploy the Lotus Domino agent to a computer withoutmonitoring server support, portal server support, and LotusDomino agent desktop and browser client support. Afterdeploying without support, then install the support ifrequired.

On zLinux servers, you cannot remotely configurethe Lotus Domino agent instance through the portalclient after upgrading to IBM Tivoli Monitoring 6.2.1Interim Fix 2.

Add the following lines to lz.ini under $CANDLEHOME/config:

CTIRA_HOSTNAME=$RUNNINGHOSTNAME$

CTIRA_SYSTEM_NAME=$RUNNINGHOSTNAME$

Then restart the operating system monitoring agent.

Agent troubleshootingThis section lists problems that might occur with agents.

This chapter provides agent-specific troubleshooting information. See the IBMTivoli Monitoring Troubleshooting Guide for general troubleshooting information.


Table 7. Agent problems and solutions

Problem Solution

Log data accumulates toorapidly.

Check the RAS trace option settings, which are described in “Setting RAS traceparameters” on page 191. The trace options settings that you can set on theKBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.

When using the F1 key orselecting Help > Contents andIndex, you receive a message inyour Microsoft® Internet Explorerbrowser that states, ″It seemsjavascript is disabled in yourbrowser, please enable it andreload again, or click here toview without javascript.″ If youselect ’here’, the Tivoli EnterprisePortal V6.1 Help is displayed,but the agent help is not.

Ensure that the local site is added to the trusted site for the browser, and thenenable the javascript.

If you want to receive multipletrace logs for separateinvocations of the same TakeAction command, leaving thissetting on permanently fills theavailable disk space.

Do not leave this setting on permanently. By doing so, you create a new log filefor each invocation of the Take Action command and ALL of them are left on theagent system.

If you see the following errors:

v Functionality Test: Server notResponding

v In the ../logs/hostname_gb_xxxxxxxx.log: TheID file being used is:/local/notesdata/server.idEnter password (press the Esckey to abort):

Follow the steps in Clearing the Domino Server password to clear the passwordon the Domino Server.

Historical data collection is notworking on UNIX operatingsystems.

Starting the Lotus Domino agent as root can prevent historical data collectionfrom working. Check the permissions on the following directory:$CANDLEHOME/interp/gb/hist/instanceName If this directory was created as rootdo one of the following:

v Change the ownership of this directory to the Domino user ID and group forthe InstanceName

—OR—

v Delete the history data file and restart using the InstanceName Domino userID, which recreates the directory with the correct ownership. Do not delete thedirectory.

On UNIX or Linux, startingManage Tivoli EnterpriseMonitoring Services fails andyou receive the followingmessages: The file accesspermissions do not allow thespecified action.install_Dir/bin/CandleManage:install_Dir/logs/CandleManage.log 0403-005Cannot create the specifiedfile. A problem occurred. Seelogs/CandleManage.log fordetails.

The problem is the permissions on the log file CandleManage.log. Thepermissions default to RW R R, or 644. Only the owner has write access. Theowner is the userid that was the first user to start the window. You can changethe permissions of the log file to 666 to allow anyone to write to the log. You canuse the following command to change the permissions:

chmod 666 install_dir/logs/CandleManage.log

Consult your system administrator before changing the file permissions.


Table 7. Agent problems and solutions (continued)

Problem Solution

When starting a Lotus Dominoagent instance using itmcmdagent -o start gb, you receive thefollowing error: itmcmd agent[-l] [ -h install_dir] [ -ooption ] [ -p option ] [-c]start|stop pc Use -c optionto NOT regenerate config file.

Include the instance (-o) in the command: itmcmd agent -o instance start gb,and rerun the command.

kgbstart.sh fails (kgbstart.sh<defunct> process and wherelogs indicate that a library failedto load).

The notes user must define the notes group correctly.

Starting CandleManage fails. Using CandleManage, the Lotus Domino agent (kgb) has to be stopped andstarted using a Notes ID. CandleManage.log on UNIX has permissions rwx rxxrxx (644). If root starts CandleManage the first time, when a non-root ID startsCandleManage the start fails because CandleManage cannot reallocate the logfile. Change the log file permissions to rwx rwx rwx (666) so any user can startCandleManage. (The permissions on the executeable are 777).

In the Availability Workspace,the status of the Domino Server(using the NSPingServer APIcall) is not responding and theDomino Server is up.

Check the kgbclient log for the error message returned by the NSPingServer APIcall.

For UNIX, the log is: hostname_gb_instance_name_kgbclient_timestamp-nn.log

For Windows, the log is: hostname_gb_instance_name_KGBCLIENT_instance_name_timestamp-nn.log

kgbclient process exits and is notrestarted. No data is returned tothe workspaces, The Availabilityworkspace shows that theDomino Server is shutting down.

When the Domino Server is shut down, the Lotus Domino agent data collectionprocess, kgbclient, must also shutdown, and then restart after the Domino Serverhas completely stopped. If the Domino Server process fails to stop within a 5minute time period, then the kgbclient process is not restarted. To correct thiscondition, the Lotus Domino agent must be stopped and restarted manually. Thismight require a forced shutdown of the Domino Server using the nsd script toclean up hung processes that were left behind by the incomplete shutdown ofthe Domino Server.

After restarting the LotusDomino agent, the status DominoAgent is starting andinitializing, is displayed anddoes not change.

Restart the monitoring agent. If the problem continues, check the Lotus Dominoagent log files for any errors.

On Windows, if you delete theLotus Domino agent instancehistory directory$CANDLEHOME\TMAITM6\logs\History\KGB\instance_name, thenthe agent will no longer be ableto create history files after yourestart the agent. The LotusDomino agent will stop soonafter.

Manually recreate the $CANDLEHOME\TMAITM6\logs\History\KGB\instance_namedirectory. Reconfigure the historic data collection, then restart the agent.


Table 7. Agent problems and solutions (continued)

Problem Solution

When configuring an instancenode using NLV characters, afterclicking OK, the window is notdisplayed.

None. This is a current limitation. Check future releases or service levels of IBMTivoli Monitoring for this fix.

There is no ″space″ betweenwords for the strings in thedrop-downlist of AdvancedFilters panel.


Names are truncated on theProperties panel.

Reopening the Properties panel might display the names correctly.

If this does not work, then this is a current limitation with no solution. Checkfuture releases or service levels of IBM Tivoli Monitoring for this fix.

Simplified Chinese usesTraditional Chinese font on theGUI.


All text strings use Traditional Chinese font on the GUI, however, help accessedthrough F1 might appear in Simplified Chinese.

On Unix or Linux, if thenotes.log monitoring does notwork, and inhostname_gb_<instance_name>_kgbagent_timestamp-nn.log there is an error messagesimilar to the following:

(49E59AAB.0051-1:query.cpp,624,"load_agents") Starting IRAagent for attribute groupDomino_Log_File<KGB>

(49E59AAB.0052-1:logmonitorqueryclass.cpp,403,"registerCallbacks") Failed to loadkump610 shared library

1. If there is no Universal Agent on the computer where the Lotus Dominoagent resides, install the latest Universal Agent. If Universal Agent is alreadyinstalled, make sure it is version 6.2.1 or higher.

2. Copy libkum0610.so, libkump610.so, and libkums1API.so of the UniversalAgent to the Agent for Louts Domino’s private library path.cp $CANDLEHOME/tmaitm6/<interp>/lib/libkum0610.so $CANDLEHOME/<interp>/gb/lib

cp $CANDLEHOME/tmaitm6/<interp>/lib/libkump610.so$CANDLEHOME/<interp>/gb/lib

cp $CANDLEHOME/tmaitm6/<interp>/lib/libkums1API.so$CANDLEHOME/<interp>/gb/lib

For example, if the platform is SuSE Linux x86-32, and CANDLEHOME is/opt/IBM/ITM, run the following commands:cp /opt/IBM/ITM/tmaitm6/li6263/lib/libkum0610.so /opt/IBM/ITM/li6263/gb/lib

cp /opt/IBM/ITM/tmaitm6/li6263/lib/libkump610.so /opt/IBM/ITM/li6263/gb/lib

cp /opt/IBM/ITM/tmaitm6/li6263/lib/libkums1API.so /opt/IBM/ITM/li6263/gb/lib

You want to use a name for yourcollection that includes spaces inthe path name.

The path name must be inclosed in quotes ("example name"). For example:

$CANDLEHOME/bin/tacmd addSystem -t gb -n tivp6clp2:KUX -pINSTANCE="tivp6clp2"

config.KGB_CHECK_DB_INCLUDE_PATH="*"

config.KGB_IWHOSTNAME="none"

config.KGB_NOTESINIPATH="/opt/ibm/DD XH/lotus/notesdata"

config.KGB_CHECK_DB_VIEW_CONFIG_FILE="none"

config.KGB_LOG_EXCLUDE="none"

config.KGB_CHECK_DB_EXCLUDE_PATH="none"

config.KGB_LOG_INCLUDE="none"

config.KGB_LOGERROR="Log File is Full | Max Hop Count Exceeded"

config.KGB_SERVER="tivp6clp2/ibm"

config.KGB_CHECK_DB_INTERVAL="3600"

config.KGB_LOGFILE="none"

config.KGB_IWPORT="none"


Workspace troubleshootingTable 8 shows problems that might occur with workspaces. This chapter providesagent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information.

Table 8. Workspace problems and solutions

Problem Solution

The process application components areavailable, but the Availability status showsPROCESS_DATA_NOT_ AVAILABLE.

This problem occurs because the PerfProc performance object isdisabled. When this condition exists, IBM Tivoli Monitoringcannot collect performance data for this process. Do thefollowing 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. ThePerformance window is displayed.

3. Click the plus sign (+) in the tool bar located above the rightpane. 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 PerfProcperformance object is enabled and the problem is comingfrom a different source. You might need to contact IBMSoftware Support.

v If you do not see Process in the pull-down menu, use theMicrosoft utility from the following Web site to enable thePerfProc performance object:

http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/exctrlst-o.asp

The Process performance object becomes visible in thePerformance object pull-down menu of the Add Counterswindows, and IBM Tivoli Monitoring is able to detectAvailability data.

6. Restart the monitoring agent.

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute name.

At the bottom of each view, you see thefollowing Historical workspace KFWITM220Eerror: Request failed during execution.

Ensure that you configure all groups that supply data to theview. In the Historical Configuration view, ensure that datacollection is started for all groups that supply data to the view.


Table 8. Workspace problems and solutions (continued)

Problem Solution

You start collection of historical data but the datacannot be seen.

Managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See the IBM Tivoli Monitoring Administrator’s Guide forinformation on managing this feature including how to set theinterval at which data is collected. By setting a more frequentinterval for data collection you reduce the load on the systemincurred every time data is uploaded.

v You use the Summarization and Pruning monitoring agent tocollect specific amounts and types of historical data. Be awarethat historical data is not displayed until the Summarizationand Pruning monitoring agent begins collecting the data. Bydefault, this agent begins collection at 2 AM daily. At thatpoint, data is visible in the workspace view. See the IBM TivoliMonitoring Administrator’s Guide to learn how to modify thedefault collection settings.

Historical data collection is unavailable becauseof incorrect queries in the Tivoli EnterprisePortal.

The column, Sort By, Group By, and First/Last functions are notcompatible with the historical data collection feature. Use ofthese advanced functions makes a query ineligible for historicaldata collection.

Even if data collection has been started, you cannot use the timespan feature if the query for the chart or table includes columnfunctions or advanced query options (Sort By, Group By, First /Last).

To ensure support of historical data collection, do not use theSort By, Group By, or First/Last functions in your queries.

See the IBM Tivoli Monitoring Administrator’s Guide or the TivoliEnterprise Portal online help for information about the HistoricalData Collection function.

When you use a long process name in thesituation, the process name is truncated.

Truncation of process or service names for situations in theAvailability table in the portal display is the expected behavior.100 bytes is the maximum name length.

Regular (non-historical) monitoring data fails tobe displayed.

Check the formation of the queries you use to gather data. Forexample, look for invalid SQL statements.

No IBM Tivoli IntelliWatch data is displayed. You must have IBM Tivoli IntelliWatch installed to see dataabout this application.

Navigator items and workspace titles are labeledwith internal names such as Kr6:KR60000 orKnt:KNT0000 rather than the correct names (suchas Disk).

Ensure application support has been added on the monitoringserver, portal server, and portal client.

For more information and instruction on installing applicationsupport see ″Installing and enabling application support″ in theIBM Tivoli Monitoring Installation and Setup Guide.

Data collected from superseded attribute groupsare not visible in workspace.

Data is only collected every 30 seconds. If you change from the64-bit version of the workspace to the 32-bit version of theworkspace before 30 seconds, then some of the data is returnedblank.


Situation troubleshootingThis section provides information about both general situation problems andproblems with the configuration of situations. See the IBM Tivoli MonitoringTroubleshooting Guide for more information about troubleshooting for situations.

General situation problemsTable 9 lists general problems that might occur with situations.

Table 9. General situation problems and solutions

Problem Solution

Monitoring activity requires too muchdisk space.

Check the RAS trace logging settings that are described in “Setting RAStrace parameters” on page 191. For example, trace logs grow rapidlywhen you apply the ALL logging option.

Monitoring activity requires too manysystem resources.

“Disk capacity planning for historical data” on page 163 describes theperformance impact of specific attribute groups. If possible, decrease youruse of the attribute groups that require greater system resources.

A formula that uses mathematicaloperators appears to be incorrect. Forexample, if you were monitoring Linux,a formula that calculates when FreeMemory falls under 10 percent of TotalMemory does not work: LT#'Linux_VM_Stats.Total_Memory' / 10

This formula is incorrect because situation predicates support only logicaloperators. Your formulas cannot have mathematical operators.Note: The Situation Editor provides alternatives to math operators.Regarding the example, you can select % Memory Free attribute andavoid the need for math operators.

You want to change the appearance ofsituations when they are displayed inthe Navigation tree.

1. Right-click an item in the Navigation tree.

2. Select Situations in the pop-up menu. The Situation Editor window isdisplayed.

3. Select the situation that you want to modify.

4. Use the State pull-down menu in the lower right of the window to setthe status and appearance of the Situation when it triggers.Note: The State setting is not related to severity settings in IBM TivoliEnterprise Console.

When a situation is triggered in theEvent Log attribute group, it remains inthe Situation Event Console as long asthe event ID entry is present in theEvent Log workspace. When this eventID entry is removed from the Event Logworkspace on the Tivoli EnterprisePortal, the situation is also cleared evenif the actual problem that caused theevent is not resolved, and the event IDentry is also present in the WindowsEvent Viewer.

There is a timeout on the cache of events for the NT Event Log group.Increase the cache time of Event Log collection to meet your requirementsby adding the following variable and timeout value to the KXXENV filefor the agent: CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600

This variable determines how long events from the NT Event Log arekept.

Events cannot be displayed in the TEC(Tivoli Enterprise Console®) view whena situation name is longer than 31 byteslong. The situation name might appeartruncated in the message column.

The situation name must be no more than 31 bytes long and cannotcontain the character -.

Recreate the situation using the specifications above.


Table 9. General situation problems and solutions (continued)

Problem Solution

After changing a situation name, theTEC (Tivoli Enterprise Console) viewdisplays the original situation name inthe message column.

Use Create Another to create a new situation.

–or–Use the situation_fullname in the Event Detail view to check theactual situation name. To access the event detail view:

1. Select the event.

2. Click on Details.

3. Select Attribute list tab and scroll the attribute list panel tosituation_fullname.

In the Situation Formula Editor, textstrings overlap or are not displayedcorrectly.

None. This is a current limitation. Check future releases or service levelsof IBM Tivoli Monitoring for this fix.

When the Lotus Domino agent isupgraded from version 6.1 to 6.2.1, thesituation associations might be lost ifthe monitoring server and portal serverare installed on Windows.

Re-associate the situation manually.

Problems with configuration of situationsTable 10 lists problems that might occur with configuring situations.

This section provides information for troubleshooting for agents. Be sure to consultthe IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshootinginformation.

Table 10. 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 isnot visible in the Tivoli EnterprisePortal.

Open the Situation Editor. Access the All managed servers view. If the situationis absent, confirm that the monitoring server has been seeded for the agent. Ifnot, seed the server, as described in the IBM Tivoli Monitoring Installation andSetup Guide.

The monitoring interval is toolong.

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 intervalas needed.

The situation did not activate atstartup.

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 theRun 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 automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event or theupdate in the graphical user interface.

An Alert event has not occurredeven though the predicate has beenproperly specified.

Check the logs, reports, and workspaces.


Table 10. Problems with configuring situations that you solve in the Situation Editor (continued)

Problem Solution

A situation fires on an unexpectedmanaged object.

Confirm that you have distributed and started the situation on the correctmanaged system.

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for the situation.

The situation does not fire. This problem can be caused when incorrect predicates are present in theformula that defines the situation. For example, the managed object shows astate that normally triggers a monitoring event, but the situation is not truebecause the wrong attribute is specified in the formula.

In the Formula tab, analyze predicates as follows:

1. Click the fx icon in the upper-right corner of the Formula area. The Showformula window is displayed.

a. Confirm the following details in the Formula area at the top of thewindow: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 leftof the window to see the original names of attributes in the applicationor 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 assignnumerical values that immediately trigger a monitoring event. Thetriggering of the event confirms that other predicates in the formula arevalid.Note: After you complete this test, you must restore the numerical valuesto valid levels so that you do not generate excessive monitoring data basedon your temporary settings.

See the IBM Tivoli Monitoring Troubleshooting Guide for additional informationabout situations that do not fire.

Table 11. Problems with configuration of situations that you solve in the Workspace area

Problem Solution

Situation events are not displayedin the Events Console view of theworkspace.

Associate the situation with a workspace.Note: The situation does not need to be displayed in the workspace. It issufficient that the situation be associated with any workspace.

You do not have access to asituation.

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, selectthe permissions or privileges that correspond to the user role.

4. Click OK.

A managed system seems to beoffline.

1. Select Physical View and highlight the Enterprise Level of the navigatortree.

2. Select View > Workspace > Managed System Status to see a list ofmanaged systems and their status.

3. If a system is offline, check network connectivity and the status of thespecific system or application.


Take Action commands troubleshootingTable 12 lists general problems that might occur with Take Action commands.When each Take Action command runs it generates the log file listed in Table 3 onpage 187. This chapter provides agent-specific troubleshooting information.

See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Table 12. Take Action commands problems and solutions

Problem Solution

Take Action commands often require severalminutes to complete.

Allow several minutes. If you do not see a pop-up messageadvising 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 TivoliEnterprise Portal. If the Take Action command works, look forconfiguration problems in the situation. See “Situationtroubleshooting” on page 203. If the Take Action command fails,see IBM Tivoli Monitoring Troubleshooting Guide for generalinformation on troubleshooting Take Action commands.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and follow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to http://www.ibm.com/software/support/isa.

Informational, warning, and error messagesThis chapter introduces message logging and explains how to gather informationfrom 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 isperforming and can alert you to exceptional conditions when they occur. Messagesare sent to an output destination, such as a file, database, or console screen.

If you receive a warning or error message, you can do one of the following:v Follow the instructions listed in the Detail window of the message if this

information is included there.v Consult the message details listed in this chapter to see what action you can take

to correct the problem.v Consult the message log for message ID and text, time and date of the message,

as well as other data you can use to diagnose the problem.




http://www.ibm.com/software/support/isa

Message formatLotus Domino agent messages have the following format:

Message ID and textExplanationOperator Response

The message ID has the following format:CCC####severity

where:

CCC Prefix that indicates the component to which the message applies. Thecomponent is one of the following:

KGB General Lotus Domino agent messages

#### Number of the message

severitySeverity of the message. There are three levels of severity:

I Informational messages provide feedback about something thathappened in the product or system that might be important. Thesemessages can provide guidance when you are requesting a specificaction 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 notresolved.

E Error messages indicate that an action cannot be completedbecause of a user or system error. These messages require userresponse.

The Text of the message provides a general statement regarding the problem orcondition that occurred. The Explanation provides additional information about themessage and what might have caused the condition. The Operator Responseprovides actions to take in response to the condition, particularly for errormessages (messages with the ″E″ suffix).

Note: Many message texts and explanations contain variables, such as the specificname of a server or application. Those variables are represented in thischapter as symbols, such as ″&1.″ Actual messages contain values for thesevariables.

This chapter includes the messages for the following software:v Lotus Domino agent

Lotus Domino agent messages

KGB5023I The Domino Server service was started.

Explanation: The Domino Server service was started.

Operator response: None.

KGB5023I


KGB5024E The Domino Server service was not started.

Explanation: The Domino Server service was not started.


KGB5031I Responding

Explanation: The Domino Server is responding.


KGB5032I Not Responding

Explanation: The Domino Server is not responding.


KGB5033I Responding

Explanation: At least one server in the cluster is responding.


KGB5034I Not Responding

Explanation: All Domino Servers in the cluster are not responding.


KGB5035I Does Not Exist

Explanation: The Domino Server is not in a cluster.


KGB5036I Does Not Exist

Explanation: The notes.ini file was not found using the path specified.

Operator response: Reconfigure the instance for the correct local full path to the notes.ini file.

KGB5037I kgbconfig.sh must be run on the Lotus Domino agent

Explanation: The kgbconfig.sh shell script must be run on the Lotus Domino agent prior to starting the firstinstance.

Operator response: Login to the system where the Lotus Domino agent is installed, and run the kgbconfig.sh shellscript.

KGB5038I The Lotus Domino agent must be started as the Domino user.

Explanation: When starting the Lotus Domino agent, you must use the Domino User ID.

Operator response: Switch to the Domino User ID prior to starting the Lotus Domino agent.

KGB5039I The Windows computer must be rebooted.

Explanation: After installation of the Lotus Domino agent on a Windows computer, the computer must be rebootedto pick up the new environment variables.

Operator response: Reboot the Windows computer, and restart the Lotus Domino agent.

KGB5024E • KGB5039I


KGB5040I Re-cycling Domino agent.

Explanation: The Domino Server is shutting down. The Lotus Domino agent data collection and availability hasstopped until the Domino Server has stopped. After the Domino Server has stopped completely, the monitoring agentdata collection and availability restarts automatically.


KGB5041I Domino agent is starting and initializing.

Explanation: The Lotus Domino agent is in the process of starting. After the monitoring agent has startedcompletely, the agent availability is initialized.


KGB5042I Restricted.

Explanation: The Domino Server is RESTRICTED in the cluster.


KGB5043I Some but not all other Domino servers responding in the cluster.

Explanation: Some Domino servers in the cluster are not available.


KGB5044I Only one Domino server responding in the cluster.

Explanation: Only one Domino server in the cluster is available.


KGB5050E intelliwatch/iwparam.nsf database not found or Domino Server is not responding.

Explanation: The attempt to open the intelliwatch/iwparam.nsf database failed, or the Domino Server is notresponding.

Operator response: Start the Domino Server and make sure the intelliwatch/iwparm.nsf database exists.

KGB5051E A failure occurred writing to the intelliwatch/iwparam.nsf database.

Explanation: The attempt to write to the intelliwatch/iwparam.nsf database failed.

Operator response: Determine the error code from the logs written to the intelliwatch/iwparm.nsf database.

KGB5040I • KGB5051E


Appendix A. IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli EnterpriseConsole. For a description of the event slots for each event class, see the lists inthis appendix. For more information about mapping attribute groups to eventclasses, see the IBM Tivoli Monitoring Administrator’s Guide.

Generic event mapping provides useful event class and attribute information forsituations that do not have specific event mapping defined. BAROC files are foundon the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB(that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console eventsynchronization provides a collection of ready-to-use rule sets that you can deploywith minimal configuration. Be sure to install IBM Tivoli Enterprise Console eventsynchronization to access the correct Sentry.baroc, which is automatically includedduring base configuration of IBM Tivoli Enterprise Console rules if you indicatethat you want to use an existing rulebase. See the IBM Tivoli Monitoring Installationand Setup Guide for details.

Each of the event classes is a child of KGB_Base and is defined in the kgb.barocfile. The KGB_Base event class can be used for generic rules processing for anyevent from the IBM Tivoli Monitoring for Domino.

For events generated by situations in the Availability attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_AVAILABILITY class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv application_component: STRINGv name: STRINGv name_enum: STRINGv kgb_status: INTEGERv kgb_status_enum: STRINGv full_name: STRINGv full_name_enum: 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 command_line_enum: STRING


v functionality_test_status: INTEGERv functionality_test_status_enum: STRINGv functionality_test_message: STRING

For events generated by situations in the Domino Agent attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO AGENT class.This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv daily_access_denials: INTEGERv daily_unsuccessful_runs: INTEGERv daily_scheduled_runs: INTEGERv daily_triggered_runs: INTEGER

For events generated by situations in the Domino Calendar attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO CALENDARclass. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv total_all_appts_reservations: INTEGERv total_all_users_resources: INTEGERv total_appts: INTEGERv total_reservations: INTEGERv total_resources: INTEGERv total_users: INTEGER

For events generated by situations in the Domino Calendar (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOCALENDAR (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv total_all_appts_reservations: INTEGERv total_all_users_resources: INTEGERv total_appts: INTEGERv total_reservations: INTEGERv total_resources: INTEGERv total_users: INTEGER

For events generated by situations in the Domino Command attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO COMMANDclass. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv create_document: INTEGER


v delete_document: INTEGERv edit_document: INTEGERv login: INTEGERv navigate: INTEGERv open_about: INTEGERv open_agent: INTEGERv open_database: INTEGERv open_document: INTEGERv open_element: INTEGERv open_form: INTEGERv open_help: INTEGERv open_icon: INTEGERv open_navigator: INTEGERv open_server: INTEGERv open_view: INTEGERv read_form: INTEGERv search_site: INTEGERv search_view: INTEGERv total: INTEGERv unknown: INTEGER

For events generated by situations in the Domino Corrupt Failover DB attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOCORRUPT FAILOVER DB class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv db_name: STRINGv view: STRINGv state: STRINGv failover_status: STRINGv failover_db: STRINGv failover_server: STRING

For events generated by situations in the Domino Database attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO DATABASEclass. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv da_refresh_server_info_count: INTEGERv da_reload_count: INTEGERv buffer_pool_max_mb: INTEGERv buffer_pool_mm_reads: INTEGERv buffer_pool_mm_writes: INTEGERv buffer_pool_peak_mb: INTEGER

Appendix A. IBM Tivoli Enterprise Console event mapping 213

v buffer_pool_pct_reads_in_buf: INTEGERv db_cache_current_entries: INTEGERv db_cache_high_water_mark: INTEGERv db_cache_hits: INTEGERv db_cache_initial_db_opens: INTEGERv db_cache_lookups: INTEGERv db_cache_max_entries: INTEGERv db_cache_overcrowd_rej: INTEGERv nsf_pool_peak: INTEGERv nsf_pool_used: INTEGERv nsf_replicate_notes_received: INTEGERv nsf_replicate_notes_sent: INTEGER

For events generated by situations in the Domino Database (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINODATABASE (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv da_refresh_server_info_count: INTEGERv da_reload_count: INTEGERv buffer_pool_max_mb: INTEGERv buffer_pool_mm_reads: INTEGERv buffer_pool_mm_writes: INTEGERv buffer_pool_peak_mb: INTEGERv buffer_pool_pct_reads_in_buf: INTEGERv db_cache_current_entries: INTEGERv db_cache_high_water_mark: INTEGERv db_cache_hits: INTEGERv db_cache_initial_db_opens: INTEGERv db_cache_lookups: INTEGERv db_cache_max_entries: INTEGERv db_cache_overcrowd_rej: INTEGERv nsf_pool_peak: INTEGERv nsf_pool_used: INTEGERv nsf_replicate_notes_received: INTEGERv nsf_replicate_notes_sent: INTEGER

For events generated by situations in the Domino DB Whitespace attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO DBWHITESPACE class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv db_name: STRINGv db_whitespace: INTEGER


v db_whitespace_pct: INTEGERv db_size: INTEGERv db_max_size: INTEGERv db_size_limit: INTEGERv db_warning_threshold: INTEGER

For events generated by situations in the Domino Group Updates attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO GROUPUPDATES class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv group_name: STRINGv change: STRING

For events generated by situations in the Domino ICM attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO ICM class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv availability_index: STRINGv cmd_total: INTEGERv cmd_unknown: INTEGERv cmd_redirects_successful: INTEGERv cmd_redirects_unsuccessful: INTEGERv cmd_redirects_cluster_busy: INTEGERv receive_error: INTEGERv requests_per_1hour: INTEGERv requests_per_1minute: INTEGERv requests_per_5minutes: INTEGERv server_running: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGERv sess_inbound_ssl: INTEGERv sess_inbound_total: INTEGERv sess_inbound_total_ssl: INTEGERv sess_outbound_active: INTEGERv sess_outbound_active_ssl: INTEGERv sess_outbound_kb_received: INTEGERv sess_outbound_kb_sent: INTEGERv sess_outbound_peak: INTEGERv sess_outbound_peak_ssl: INTEGER


v sess_outbound_total: INTEGERv sess_outbound_total_ssl: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGERv sess_threads_in_thread_pool: INTEGERv sess_threads_peak: INTEGER

For events generated by situations in the Domino ICM (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOICM (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv availability_index: STRINGv cmd_total: INTEGERv cmd_unknown: INTEGERv cmd_redirects_successful: INTEGERv cmd_redirects_unsuccessful: INTEGERv cmd_redirects_cluster_busy: INTEGERv receive_error: INTEGERv requests_per_1hour: INTEGERv requests_per_1minute: INTEGERv requests_per_5minutes: INTEGERv server_running: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_active_ssl: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGERv sess_inbound_ssl: INTEGERv sess_inbound_total: INTEGERv sess_inbound_total_ssl: INTEGERv sess_outbound_active: INTEGERv sess_outbound_active_ssl: INTEGERv sess_outbound_kb_received: INTEGERv sess_outbound_kb_sent: INTEGERv sess_outbound_peak: INTEGERv sess_outbound_peak_ssl: INTEGERv sess_outbound_total: INTEGERv sess_outbound_total_ssl: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGERv sess_threads_in_thread_pool: INTEGERv sess_threads_peak: INTEGER


For events generated by situations in the Domino IMAP attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO IMAP class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sess_accept_queue: INTEGERv sess_active: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_non_ssl: INTEGERv sess_peak: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGERv sess_total: INTEGER

For events generated by situations in the Domino IMAP (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOIMAP (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sess_accept_queue: INTEGERv sess_active: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_non_ssl: INTEGERv sess_peak: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGERv sess_total: INTEGER

For events generated by situations in the Domino LDAP attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO LDAP class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv server_running: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_active_ssl: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGERv sess_inbound_peak_ssl: INTEGERv sess_inbound_total: INTEGER


v sess_inbound_total_ssl: INTEGERv sess_inb_tot_ssl_bad_hshake: INTEGERv sess_non_ssl: INTEGERv sess_ssl: INTEGERv sess_total: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGER

For events generated by situations in the Domino LDAP (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOLDAP (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv server_running: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_active_ssl: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGERv sess_inbound_peak_ssl: INTEGERv sess_inbound_total: INTEGERv sess_inbound_total_ssl: INTEGERv sess_inb_tot_ssl_bad_hshake: INTEGERv sess_non_ssl: INTEGERv sess_ssl: INTEGERv sess_total: INTEGERv sess_threads_busy: INTEGERv sess_threads_idle: INTEGER

For events generated by situations in the Domino Log File attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO LOG FILE class.This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv log_file: STRINGv log_message: INTEGER

For events generated by situations in the Domino Mail attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO MAIL class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv dead: INTEGER


v average_deliver_time: INTEGERv hold: INTEGERv waiting: INTEGERv current_byte_delivery_rate: INTEGERv current_byte_transfer_rate: INTEGERv current_msg_delivery_rate: INTEGERv current_msg_transfer_rate: INTEGERv total_failures: INTEGERv total_kb_delivered: INTEGERv total_pending: INTEGERv total_routed: INTEGERv waiting_for_dir: INTEGERv waiting_for_dns: INTEGERv waiting_recipients: INTEGERv transferred: INTEGERv peak_messages_transferred: INTEGERv transfer_failures: INTEGERv delivered: INTEGERv average_size_delivered: INTEGERv max_size_delivered: INTEGERv total_kb_transferred: INTEGERv total_routed_smtp: INTEGERv total_routed_nrpc: INTEGER

For events generated by situations in the Domino MAIL (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOMAIL (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv dead: INTEGERv average_deliver_time: INTEGERv hold: INTEGERv waiting: INTEGERv current_byte_delivery_rate: INTEGERv current_byte_transfer_rate: INTEGERv current_msg_delivery_rate: INTEGERv current_msg_transfer_rate: INTEGERv total_failures: INTEGERv total_kb_delivered: INTEGERv total_pending: INTEGERv total_routed: INTEGERv waiting_for_dir: INTEGERv waiting_for_dns: INTEGERv waiting_recipients: INTEGERv transferred: INTEGER


v peak_messages_transferred: INTEGERv transfer_failures: INTEGERv delivered: INTEGERv average_size_delivered: INTEGERv max_size_delivered: INTEGERv total_kb_transferred: INTEGER

For events generated by situations in the Domino Mail By Dest attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO MAIL BYDEST class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv destination_server: STRINGv total_routed: INTEGERv transferred: INTEGERv delivered: INTEGERv total_kb_transferred: INTEGER

For events generated by situations in the Domino Mail By Dest (Superseded)attribute group, Tivoli Enterprise Console events are sent using theITM_KGB_DOMINO MAIL BY DEST (SUPERSEDED) class. This class contains thefollowing slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv destination_server: STRINGv total_routed: INTEGERv transferred: INTEGERv delivered: INTEGERv total_kb_transferred: INTEGER

For events generated by situations in the Domino NET TCPIP attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO NETTCPIP class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sessions_est_incoming: INTEGERv sessions_est_outgoing: INTEGERv sessions_peak: INTEGERv kb_received: INTEGERv kb_sent: INTEGERv kb_received_interval: INTEGERv kb_sent_interval: INTEGER


For events generated by situations in the Domino NET TCPIP (Superseded)attribute group, Tivoli Enterprise Console events are sent using theITM_KGB_DOMINO NET TCPIP (SUPERSEDED) class. This class contains thefollowing slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sessions_est_incoming: INTEGERv sessions_est_outgoing: INTEGERv sessions_peak: INTEGERv kb_received: INTEGERv kb_sent: INTEGER

For events generated by situations in the Domino Replica attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO REPLICA class.This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv successful: INTEGERv failed: INTEGERv docs_added: INTEGERv docs_updated: INTEGERv docs_deleted: INTEGER

For events generated by situations in the Domino Replica (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOREPLICA (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv successful: INTEGERv failed: INTEGERv docs_added: INTEGERv docs_updated: INTEGERv docs_deleted: INTEGER

For events generated by situations in the Domino Replica Cluster attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO REPLICACLUSTER class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv servers: INTEGERv successful: INTEGERv failed: INTEGERv docs_added: INTEGERv docs_updated: INTEGER


v docs_deleted: INTEGERv retry_waiting: INTEGERv session_kb_in: INTEGERv session_kb_out: INTEGERv work_queue_depth_avg: INTEGERv work_queue_depth_max: INTEGERv work_queue_depth: INTEGERv seconds_on_queue: INTEGERv seconds_on_queue_max: INTEGER

For events generated by situations in the Domino Replica Cluster (Superseded)attribute group, Tivoli Enterprise Console events are sent using theITM_KGB_DOMINO REPLICA CLUSTER (SUPERSEDED) class. This class containsthe following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv servers: INTEGERv successful: INTEGERv failed: INTEGERv docs_added: INTEGERv docs_updated: INTEGERv docs_deleted: INTEGERv retry_waiting: INTEGERv session_kb_in: INTEGERv session_kb_out: INTEGERv work_queue_depth_avg: INTEGERv work_queue_depth_max: INTEGERv work_queue_depth: INTEGERv seconds_on_queue: INTEGERv seconds_on_queue_max: INTEGER

For events generated by situations in the Domino Replication attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOREPLICATION class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv destination_server: STRINGv initiated_by: STRINGv start_time: STRINGv end_time: STRINGv db_info: STRINGv events: STRINGv hit_miss: INTEGERv hit_miss_enum: STRINGv kgb_duration: INTEGER


For events generated by situations in the Domino Server attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO SERVER class.This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv server_os: STRINGv server_version: STRINGv server_build: STRINGv server_start: STRINGv availability_index: INTEGERv availability_threshold: INTEGERv sessions_dropped: INTEGERv trans_per_minute_peak: INTEGERv trans_total: INTEGERv users_peak: INTEGERv users_active_30_min: INTEGERv users: INTEGERv expansion_factor: INTEGERv trans_per_minute: INTEGERv response_time: INTEGER

For events generated by situations in the Domino Server (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOSERVER (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv server_os: STRINGv server_version: STRINGv server_build: STRINGv server_start: STRINGv availability_index: INTEGERv availability_threshold: INTEGERv sessions_dropped: INTEGERv trans_per_minute_peak: INTEGERv trans_total: INTEGERv users_peak: INTEGERv users_active_30_min: INTEGERv users: INTEGERv expansion_factor: INTEGER

For events generated by situations in the Domino Server Cluster attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO SERVERCLUSTER class. This class contains the following slots:v node: STRINGv timestamp: STRING


v server_name: STRINGv open_redir_failover_success: INTEGERv open_redir_failover_unsucc: INTEGERv open_redir_fover_by_pth_suc: INTEGERv open_redir_fover_by_pth_unsuc: INTEGERv open_redir_load_bal_succ_tot: INTEGERv open_redir_load_bal_unsuc_tot: INTEGERv open_redir_load_bal_pth_unsuc: INTEGERv open_redir_load_bal_pth_succ: INTEGERv open_req_cluster_busy: INTEGERv open_req_db_out_of_service: INTEGERv open_req_load_balanced: INTEGERv probe_count: INTEGERv probe_error: INTEGER

For events generated by situations in the Domino SMTP attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO SMTP class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_total: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGERv sess_inbound_kb_received_interval: INTEGERv sess_inbound_kb_sent_interval: INTEGER

For events generated by situations in the Domino SMTP (Superseded) attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINOSMTP (SUPERSEDED) class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv sess_inbound_accept_queue: INTEGERv sess_inbound_active: INTEGERv sess_inbound_total: INTEGERv sess_inbound_kb_received: INTEGERv sess_inbound_kb_sent: INTEGERv sess_inbound_peak: INTEGER

For events generated by situations in the Domino Tasks attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_DOMINO TASKS class.This class contains the following slots:v node: STRING


v timestamp: STRINGv server_name: STRINGv task_name: STRINGv task_status: STRINGv task_status_duration: STRING

For events generated by situations in the Domino Web Retriever attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_DOMINO WEBRETRIEVER class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv access_ftp: INTEGERv access_gopher: INTEGERv access_http: INTEGERv kb_received: INTEGERv kb_sent: INTEGERv image_cache_hits: INTEGERv image_cache_misses: INTEGERv log_level: STRINGv log_messages: STRINGv process_access_ftp: INTEGERv process_access_gopher: INTEGERv process_access_http: INTEGERv process_kb_received: INTEGERv process_kb_sent: INTEGERv process_num_active: INTEGERv process_num_busy: INTEGERv process_num_idle: INTEGERv process_num_maximum: INTEGERv process_state: STRINGv process_urls_failed: INTEGERv process_urls_requested: INTEGERv process_urls_succeeded: INTEGERv time_current: STRINGv time_duration: STRINGv time_start: STRINGv urls_failed: INTEGERv urls_requested: INTEGERv urls_succeeded: INTEGERv version: STRINGv vpool_max_buf: INTEGERv vpool_max_element: INTEGERv vpool_max_marker: INTEGERv vpool_max_text: INTEGERv vpool_max_url: INTEGER


For events generated by situations in the IW Mail Domain Statistics attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_IW MAILDOMAIN STATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv domain_name: STRINGv statistic_name: STRINGv mail_count: INTEGERv mail_size: INTEGER

For events generated by situations in the IW Mail Incoming Statistics attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_IW MAILINCOMING STATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv originating_server: STRINGv statistic_name: STRINGv mail_count_over: INTEGERv mail_min: INTEGERv mail_max: INTEGERv mail_avg: INTEGER

For events generated by situations in the IW Mail Outgoing Statistics attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_IW MAILOUTGOING STATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv destination_server: STRINGv statistic_name: STRINGv mail_count: INTEGERv mail_volume: INTEGER

For events generated by situations in the IW Mail Size Statistics attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_IW MAIL SIZESTATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv mail_name: STRINGv statistic_name: STRINGv mail_count: INTEGERv mail_max: INTEGERv mail_avg: INTEGER


For events generated by situations in the IW Replication Delay Statistics attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_IWREPLICATION DELAY STATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv replication_name: STRINGv statistic_name: STRINGv minutes_since_recv: INTEGERv minutes_since_send: INTEGER

For events generated by situations in the IW Replication Statistics attribute group,Tivoli Enterprise Console events are sent using the ITM_KGB_IW REPLICATIONSTATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv replication_name: STRINGv statistic_name: STRINGv pulled_kb_received: INTEGERv pulled_kb_sent: INTEGERv pulled_documents_transferred: INTEGERv pushed_kb_received: INTEGERv pushed_kb_sent: INTEGERv pushed_documents_transferred: INTEGERv replication_time: INTEGERv total_missed: INTEGERv total_successes: INTEGER

For events generated by situations in the IW Server attribute group, TivoliEnterprise Console events are sent using the ITM_KGB_IW SERVER class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv event_time: STRINGv message_priority: STRINGv server_message: STRING

For events generated by situations in the IW View Performance Statistics attributegroup, Tivoli Enterprise Console events are sent using the ITM_KGB_IW VIEWPERFORMANCE STATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv server_name: STRINGv statistic_name: STRINGv view_max: INTEGERv view_avg: INTEGER


v view_count: INTEGERv view_pct_under_value: STRINGv view_pct_under: INTEGER

For events generated by situations in the Performance Object Status attributegroup, Tivoli Enterprise Console events are sent using theITM_KGB_PERFORMANCE_OBJECT_STATUS class. This class contains thefollowing 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. Documentation library

This appendix contains information about the publications related to the LotusDomino agent. These publications are listed in the following categories:v Lotus Domino agent libraryv Prerequisite publicationsv Related publications

See the IBM Tivoli Monitoring and OMEGAMON XE products: Documentation Guide,SC23-8816, for information about accessing and using publications. You can findthe Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON® XEInformation Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm.

To find a list of new and changed publications, click What's new on the Welcomepage of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. Tofind publications from the previous version of a product, click Previousinformation centers on the Welcome page for the product.

Lotus Domino agent libraryThere is one document specific to the Lotus Domino agent: IBM Tivoli CompositeApplication Manager Agent for Lotus Domino User’s Guide. This publication providesagent-specific information for configuring, using, and troubleshooting the LotusDomino agent

Use the configuration chapter in this guide with the IBM Tivoli MonitoringInstallation and Setup Guide to set up the software.

Use the information in this guide with the IBM Tivoli Monitoring User’s Guide tomonitor Lotus Domino resources.

Prerequisite publicationsTo use the information in this publication effectively, you must have someprerequisite knowledge, which you can obtain from the following IBM TivoliMonitoring publications:v Exploring IBM Tivoli Monitoring

v IBM Tivoli Monitoring Administrator’s Guide

v IBM Tivoli Monitoring Agent Builder User’s Guide

v IBM Tivoli Monitoring Command Reference

v IBM Tivoli Monitoring: Configuring Tivoli Enterprise Monitoring Server on z/OS®

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring

v IBM Tivoli Monitoring: Upgrading from V5.1.2

v IBM Tivoli Monitoring User’s Guide

v IBM Tivoli Monitoring: i5/OS® Agent User’s Guide


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm

v IBM Tivoli Monitoring: Linux OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX Log OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX OS Agent User's Guide

v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v IBM Tivoli Monitoring Universal Agent User’s Guide

v IBM Tivoli Monitoring Universal Agent API and Command Programming ReferenceGuide

Related publicationsThe following documents also provide useful information:v IBM Tivoli Enterprise Console Adapters Guide

v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide

v IBM Tivoli Enterprise Console Reference Manual

v IBM Tivoli Enterprise Console Rule Builder’s Guide

Other sources of documentationYou can also obtain technical documentation about Tivoli Monitoring andOMEGAMON XE products from the following sources:v IBM Tivoli Open Process Automation Library (OPAL)

http://www.ibm.com/software/tivoli/opalOPAL is an online catalog that contains integration documentation as well asother downloadable product extensions. This library is updated daily.

v Redbookshttp://www.redbooks.ibm.com/IBM Redbooks®, Redpapers, and Redbooks Technotes provide information aboutproducts from platform and solution perspectives.

v TechnotesYou can find Technotes through the IBM Software Support Web site athttp://www.ibm.com/software/support/probsub.html, or more directly throughyour product Web site, which contains a link to Technotes (under Solve aproblem).Technotes provide the latest information about known product limitations andworkarounds.


http://www.ibm.com/software/tivoli/opal

http://www.redbooks.ibm.com/


Appendix C. Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility 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 productdocumentation of the assistive technology for details on using those technologieswith 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 followingfeatures 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 keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. See the documentation provided by youroperating system for more information.

Magnifying what is displayed on the screenYou can enlarge information on the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. See the documentation provided by youroperating system for more information.


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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, 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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating systems. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingsystem for which the sample programs are written. These examples have not beenthoroughly tested under all conditions. IBM, therefore, cannot guarantee or implyreliability, serviceability, or function of these programs. You may copy, modify, anddistribute these sample programs in any form without payment to IBM for thepurposes of developing, using, marketing, or distributing application programsconforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at ″Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Sun Microsystems, Inc. in the United States,other countries, or both.


Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Appendix D. Notices 235

Index

AAccess FTP attribute 140Access Gopher attribute 140Access HTTP attribute 140accessibility 231agent

trace logs 186agent fails to start 10agents

troubleshooting 197Application Component attribute 29attribute groups

Availability 29Domino Agent 33Domino Calendar 35Domino Calendar (Superseded) 37Domino Command 39Domino Corrupt Failover DB 45Domino Database 46Domino Database (Superseded) 51Domino DB Whitespace 56Domino Group Updates 58Domino ICM 59Domino ICM (Superseded) 66Domino IMAP 74Domino IMAP (Superseded) 77Domino LDAP 80Domino LDAP (Superseded) 84Domino Log File 89Domino Mail 89Domino MAIL (Superseded) 96Domino Mail By Dest 102Domino Mail By Dest (Superseded) 104Domino NET TCPIP 105Domino NET TCPIP (Superseded) 107Domino Replica 109Domino Replica (Superseded) 111Domino Replica Cluster 113Domino Replica Cluster (Superseded) 117Domino Replication 121Domino Server 123Domino Server (Superseded) 126Domino Server Cluster 130Domino SMTP 134Domino SMTP (Superseded) 136Domino Tasks 138Domino Web Retriever 139IW Mail Domain Statistics 147IW Mail Incoming Statistics 148IW Mail Outgoing Statistics 150IW Mail Size Statistics 151IW Replication Delay Statistics 153IW Replication Statistics 154IW Server 157IW View Performance Statistics 158list of all 25more information 25new 2overview 25Performance Object Status 160

attributesAccess FTP 140Access Gopher 140Access HTTP 140Application Component 29Availability 29Availability Index 59, 67, 124, 127Availability Threshold 124, 128Average Deliver Time 90, 97Average Size Delivered 95, 101Buffer Pool Max MB 47, 52Buffer Pool MM Reads 47, 52Buffer Pool MM Writes 47, 52Buffer Pool Pct Reads In Buf 48, 53Buffer Pool Peak MB 48, 53Change 58Cmd Redirects Cluster Busy 60, 68Cmd Redirects Successful 60, 68Cmd Redirects Unsuccessful 60, 68Cmd Total 59, 67Cmd Unknown 59, 67Command Line 31Create Document 39Current Byte Delivery Rate 91, 97Current Byte Transfer Rate 91, 98Current Msg Delivery Rate 91, 98Current Msg Transfer Rate 92, 98DA Refresh Server Info Count 46, 51DA Reload Count 47, 52Daily Access Denials 33Daily Scheduled Runs 34Daily Triggered Runs 34Daily Unsuccessful Runs 34Db Cache Current Entries 48, 53Db Cache High Water Mark 48, 53Db Cache Hits 49, 54Db Cache Initial Db Opens 49, 54Db Cache Lookups 49, 54Db Cache Max Entries 49, 54Db Cache Overcrowd Rej 50, 54DB Info 122DB Max Size (KByte) 57DB Name 45, 56DB Size (KByte) 57DB Size Limit (KByte) 57DB Warning Threshold (KByte) 58DB Whitespace Percentage (%) 57DB Whitespace Size (KByte) 56Dead 90, 96Delete Document 39Delivered 94, 101, 103, 105Destination Server 102, 104, 122, 151Docs Added 110, 112, 114, 118Docs Deleted 111, 113, 115, 119Docs Updated 110, 112, 114, 119Domain Name 148Domino Agent 33Domino Calendar 35Domino Calendar (Superseded) 37Domino Command 39Domino Corrupt Failover DB 45


attributes (continued)Domino Database 46Domino Database (Superseded) 51Domino DB Whitespace 56Domino Group Updates 58Domino ICM 59Domino ICM (Superseded) 67Domino IMAP 75Domino IMAP (Superseded) 77Domino LDAP 80Domino LDAP (Superseded) 84Domino Log File 89Domino Mail 90Domino MAIL (Superseded) 96Domino Mail By Dest 102Domino Mail By Dest (Superseded) 104Domino NET TCPIP 105Domino NET TCPIP (Superseded) 108Domino Replica 109Domino Replica (Superseded) 111Domino Replica Cluster 113Domino Replica Cluster (Superseded) 117Domino Replication 121Domino Server 123Domino Server (Superseded) 127Domino Server Cluster 130Domino SMTP 134Domino SMTP (Superseded) 136Domino Tasks 138Domino Web Retriever 139Duration 122Edit Document 40End Time 122Error Code 161Event Time 158Events 122Expansion Factor 126, 129Failed 110, 112, 114, 118Failover DB 46Failover Server 46Failover Status 46Full Name 30Functionality Test Message 32Functionality Test Status 32Group Name 58Hit Miss 122Hold 90, 97Image Cache Hits 141Image Cache Misses 141Initiated By 122IW Mail Domain Statistics 147IW Mail Incoming Statistics 148IW Mail Outgoing Statistics 150IW Mail Size Statistics 151IW Replication Delay Statistics 153IW Replication Statistics 154IW Server 157IW View Performance Statistics 158KB Received 106, 109, 140KB Received Interval 107KB Sent 107, 109, 141KB Sent Interval 107Log File 89Log Level 141Log Message 89Log Messages 141Login 40

attributes (continued)Mail Avg 150, 152Mail Count 148, 151, 152Mail Count Over 149Mail Max 149, 152Mail Min 149Mail Name 152Mail Size 148Mail Volume 151Max Size Delivered 95, 101Message Priority 158Minutes Since Recv 153Minutes Since Send 154more information 25Name 29Navigate 40new or changed 2Node 29, 33, 35, 37, 39, 45, 46, 51, 56, 58, 59, 67, 75, 77, 80,

85, 89, 90, 96, 102, 104, 105, 108, 109, 111, 113, 117, 121,123, 127, 130, 134, 136, 138, 139, 147, 148, 150, 151, 153,154, 157, 158, 160

NSF Pool Peak 50, 55NSF Pool Used 50, 55NSF Replicate Notes Received 50, 55NSF Replicate Notes Sent 51, 55Object Name 160Object Status 161Object Type 160Open About 40Open Agent 41Open Database 41Open Document 41Open Element 41Open Form 42Open Help 42Open Icon 42Open Navigator 43Open Redir Failover Success 130Open Redir Failover Unsucc 130Open Redir Fover By Pth Suc 131Open Redir Fover By Pth Unsuc 131Open Redir Load Bal Pth Succ 132Open Redir Load Bal Pth Unsuc 132Open Redir Load Bal Succ Tot 131Open Redir Load Bal Unsuc Tot 131Open Req Cluster Busy 132Open Req Db Out Of Service 133Open Req Load Balanced 133Open Server 43Open View 43Originating Server 149overview 25Page Faults per Sec 31Peak Messages Transferred 94, 100Percent Privileged Time 31Percent Processor Time 31Percent User Mode Time 31Performance Object Status 160PID 31Probe Count 133Probe Error 133Process Access FTP 142Process Access Gopher 142Process Access HTTP 142Process KB Received 142Process KB Sent 142Process Num Active 143


attributes (continued)Process Num Busy 143Process Num Idle 143Process Num Maximum 143Process State 144Process URLs Failed 144Process URLs Requested 144Process URLs Succeeded 144Pulled Documents Transferred 155Pulled KB Received 155Pulled KB Sent 155Pushed Documents Transferred 156Pushed KB Received 156Pushed KB Sent 156Query Name 160Read Form 43Receive Error 60, 68Replication Name 153, 155Replication Time 156Requests Per 1Hour 61, 69Requests Per 1Minute 61, 69Requests Per 5Minutes 61, 69Response Time 126Retry Waiting 115, 119Search Site 44Search View 44Seconds On Queue 117, 120Seconds On Queue Max 117, 121Server Build 123, 127Server Message 158Server Name 33, 35, 37, 39, 45, 46, 51, 56, 58, 59, 67, 75,

78, 80, 85, 89, 90, 96, 102, 104, 106, 108, 110, 111, 113, 117,121, 123, 127, 130, 134, 137, 139, 140, 147, 149, 150, 152,153, 154, 157, 158

Server OS 123, 127Server Running 61, 69, 80, 85Server Start 124, 127Server Version 123, 127Servers 113, 118Sess Accept Queue 75, 78Sess Active 75, 78Sess Inb Tot SSL Bad Hshake 83, 87Sess Inbound Accept Queue 61, 69, 81, 85, 134, 137Sess Inbound Active 62, 70, 81, 85, 134, 137Sess Inbound Active SSL 70, 81, 85Sess Inbound KB Received 62, 70, 75, 78, 81, 86, 135, 137Sess Inbound KB Received Interval 136Sess Inbound KB Sent 62, 70, 76, 78, 82, 86, 135, 138Sess Inbound KB Sent Interval 136Sess Inbound Non SSL 76, 79Sess Inbound Peak 62, 71, 82, 86, 135, 138Sess Inbound Peak SSL 82, 86Sess Inbound SSL 63, 71Sess Inbound Total 63, 71, 82, 87, 135, 137Sess Inbound Total SSL 63, 71, 83, 87Sess Non SSL 83, 87Sess Outbound Active 63, 72Sess Outbound Active SSL 64, 72Sess Outbound KB Received 64, 72Sess Outbound KB Sent 64, 72Sess Outbound Peak 64, 72Sess Outbound Peak SSL 65, 73Sess Outbound Total 65, 73Sess Outbound Total SSL 65, 73Sess Peak 76, 79Sess SSL 83, 88Sess Threads Busy 65, 73, 76, 79, 84, 88

attributes (continued)Sess Threads Idle 66, 74, 77, 79, 84, 88Sess Threads In Thread Pool 66, 74Sess Threads Peak 66, 74Sess Total 77, 80, 84, 88Session KB In 115, 119Session KB Out 115, 120Sessions Dropped 124, 128Sessions Est Incoming 106, 108Sessions Est Outgoing 106, 108Sessions Peak 106, 108Start Time 122State 45Statistic Name 148, 149, 151, 152, 153, 155, 158Status 30Successful 110, 112, 114, 118Task Name 139Task Status 139Task Status Duration 139Thread Count 31Time Current 145Time Duration 145Time Start 145Timestamp 29, 33, 35, 37, 39, 45, 46, 51, 56, 58, 59, 67, 75,

78, 80, 85, 89, 90, 96, 102, 104, 106, 108, 109, 111, 113, 117,121, 123, 127, 130, 134, 137, 139, 147, 149, 150, 152, 153,154, 157, 158, 160

Total 44Total All Appts Reservations 35, 37Total All Users Resources 35, 37Total Appts 36, 38Total Failures 92, 98Total KB Delivered 92, 99Total KB Transferred 95, 102, 103, 105Total Missed 156Total Pending 92, 99Total Reservations 36, 38Total Resources 36, 38Total Routed 93, 99, 102, 104Total Routed NRPC 96Total Routed SMTP 95Total Successes 157Total Users 36, 38Trans Per Minute 126Trans Per Minute Peak 124, 128Trans Total 125, 128Transfer Failures 94, 101Transferred 94, 100, 103, 104Type 30Unknown 44URLs Failed 145URLs Requested 145URLs Succeeded 145Users 125, 129Users Active 30 Min 125, 129Users Peak 125, 129Version 146View 45View Avg 159View Count 159View Max 159View Pct Under 159View Pct Under Value 159Virtual Size 31VPOOL Max Buf 146VPOOL Max Element 146VPOOL Max Marker 146

Index 239

attributes (continued)VPOOL Max Text 146VPOOL Max URL 147Waiting 91, 97Waiting For DIR 93, 99Waiting For DNS 93, 100Waiting Recipients 93, 100Work Queue Depth 116, 120Work Queue Depth Avg 116, 120Work Queue Depth Max 116, 120Working Set Size 31

Availabilitysituations 168, 169workspaces

descriptions 19list 17

Availability attribute group 29Availability Index attribute 59, 67, 124, 127Availability Threshold attribute 124, 128Availability workspace 19Availability(Superseded) workspace 19Average Deliver Time attribute 90, 97Average Size Delivered attribute 95, 101

BBuffer Pool Max MB attribute 47, 52Buffer Pool MM Reads attribute 47, 52Buffer Pool MM Writes attribute 47, 52Buffer Pool Pct Reads In Buf attribute 48, 53Buffer Pool Peak MB attribute 48, 53built-in troubleshooting features 183

Ccalculate historical data disk space 163capacity planning

Lotus Domino agent 163capacity planning for historical data 163Change attribute 58changes

attribute groups, new 2attributes 2baroc file updated 3

changing the ping intervalLinux 10UNIX 10Windows 10

clearing the Domino Server password 6Cluster

situations 168, 171workspaces


Cluster workspace 19Cluster(Superseded) workspace 20Cmd Redirects Cluster Busy attribute 60, 68Cmd Redirects Successful attribute 60, 68Cmd Redirects Unsuccessful attribute 60, 68Cmd Total attribute 59, 67Cmd Unknown attribute 59, 67Command Line attribute 31commands

itmcmd 10iwsditm program 14tacmd addSystem 13

commands, Take Action 179components 3configuration 5

after installation 6fields 11Linux 10remote 13UNIX 10values 11Windows 9

configuring the monitoring agent 6Create Document attribute 39Current Byte Delivery Rate attribute 91, 97Current Byte Transfer Rate attribute 91, 98Current Msg Delivery Rate attribute 91, 98Current Msg Transfer Rate attribute 92, 98

DDA Refresh Server Info Count attribute 46, 51DA Reload Count attribute 47, 52Daily Access Denials attribute 33Daily Scheduled Runs attribute 34Daily Triggered Runs attribute 34Daily Unsuccessful Runs attribute 34data

trace logs 184data logged

Lotus Domino agent 163data provider logs

See agentDatabase



Database Status workspace 20Database workspace 20Database(Superseded) workspace 21Db Cache Current Entries attribute 48, 53Db Cache High Water Mark attribute 48, 53Db Cache Hits attribute 49, 54Db Cache Initial Db Opens attribute 49, 54Db Cache Lookups attribute 49, 54Db Cache Max Entries attribute 49, 54Db Cache Overcrowd Rej attribute 50, 54DB Info attribute 122DB Max Size (KByte) attribute 57DB Name attribute 45, 56DB Size (KByte) attribute 57DB Size Limit (KByte) attribute 57DB Warning Threshold (KByte) attribute 58DB Whitespace Percentage (%) attribute 57DB Whitespace Size (KByte) attribute 56Dead attribute 90, 96Delete Document attribute 39Delivered attribute 94, 101, 103, 105Destination Server attribute 102, 104, 122, 151determining the status of the Domino Server

Linux 10UNIX 10Windows 10

disk capacity planningSee capacity planning

disk capacity planning for historical data 163Docs Added attribute 110, 112, 114, 118Docs Deleted attribute 111, 113, 115, 119


Docs Updated attribute 110, 112, 114, 119documentation

See publicationsDomain Name attribute 148Domino Agent attribute group 33Domino Calendar (Superseded) attribute group 37Domino Calendar attribute group 35Domino Command attribute group 39Domino Corrupt Failover DB attribute group 45Domino Database (Superseded) attribute group 51Domino Database attribute group 46Domino DB Whitespace attribute group 56Domino Group Updates attribute group 58Domino ICM (Superseded) attribute group 66Domino ICM attribute group 59Domino IMAP (Superseded) attribute group 77Domino IMAP attribute group 74Domino LDAP (Superseded) attribute group 84Domino LDAP attribute group 80Domino Log File attribute group 89Domino MAIL (Superseded) attribute group 96Domino Mail attribute group 89Domino Mail By Dest (Superseded) attribute group 104Domino Mail By Dest attribute group 102Domino NET TCPIP (Superseded) attribute group 107Domino NET TCPIP attribute group 105Domino Replica (Superseded) attribute group 111Domino Replica attribute group 109Domino Replica Cluster (Superseded) attribute group 117Domino Replica Cluster attribute group 113Domino Replication attribute group 121Domino Server (Superseded) attribute group 126Domino Server attribute group 123Domino Server Cluster attribute group 130Domino Server password, clearing 6Domino SMTP (Superseded) attribute group 136Domino SMTP attribute group 134Domino Tasks attribute group 138Domino Web Retriever attribute group 139Duration attribute 122

EEdit Document attribute 40End Time attribute 122environment

features 1functions 1

Error Code attribute 161event

mapping 211event messages, sending 14Event Time attribute 158Events attribute 122Expansion Factor attribute 126, 129

FFailed attribute 110, 112, 114, 118Failover DB attribute 46Failover Server attribute 46Failover Status attribute 46features, Lotus Domino agent 1files

agent trace 186installation trace 186

files (continued)other trace log 187trace logs 184

Full Name attribute 30Functionality Test Message attribute 32Functionality Test Status attribute 32functions, Lotus Domino agent 1

Ggathering support information 183Group Name attribute 58

Hhistorical data

calculate disk space 163capacity planning

Lotus Domino agent 163disk capacity planning 163

Hit Miss attribute 122Hold attribute 90, 97

IIBM Software Support

See supportIBM Support Assistant 206IBM Tivoli Enterprise Console

event mapping 211Image Cache Hits attribute 141Image Cache Misses attribute 141information

troubleshooting 183information, additional

attributes 25policies 181situations 167Take Action commands 179workspaces 17

Initiated By attribute 122installation

log file 186problems 193remote 13silent 5

instancestarting 10stopping 10

interface, user 3ISA 206itmcmd command 10IW Mail Domain Statistics attribute group 147IW Mail Incoming Statistics attribute group 148IW Mail Outgoing Statistics attribute group 150IW Mail Size Statistics attribute group 151IW Mail workspace 21IW Replication Delay Statistics attribute group 153IW Replication Statistics attribute group 154IW Replication workspace 21IW Server attribute group 157IW Server workspace 22IW View Performance Statistics attribute group 158iwsditm utility 14

Index 241

KKB Received attribute 106, 109, 140KB Received Interval attribute 107KB Sent attribute 107, 109, 141KB Sent Interval attribute 107KGB_Domino_DB_Size_Warn situation 172KGB_Domino_Failover_Warn situation 171KGB_Domino_Mail_Dead_Warn situation 173KGB_Domino_Mail_Dead_Warn_2 situation 174KGB_Domino_Mail_Waiting_Warn situation 173KGB_Domino_Mail_Waiting_Warn_2 situation 175KGB_Domino_Rep_Miss_Crit situation 178KGB_Domino_Serv_Avail_Crit situation 169KGB_Domino_Serv_Avail_Idx_Crit situation 175KGB_Domino_Serv_Config_Crit situation 170KGB_Domino_Serv_Sess_Drop_Crit situation 176KGB_Domino_SMTP_Task_Warn situation 177KGB_Domino_Srv_Avl_Idx_Crit_2 situation 176KGB_Domino_Srv_Clus_Avail_Crit situation 169KGB_Domino_Srv_Clus_Avail_Warn situation 171KGB_Domino_Srv_Ses_Drop_Crit_2 situation 177KGB_Domino_Whitespace_Pct_Warn situation 172

Llegal notices 233library, Lotus Domino agent 229list of messages 207Log File attribute 89Log Level attribute 141Log Message attribute 89Log Messages attribute 141logged data

Lotus Domino agent 163logging

agent trace logs 186, 187built-in features 183installation log files 186trace log files 184

Login attribute 40Lotus Domino



Lotus Domino agentcomponents 3features 1functions 1performance considerations 203

Lotus Domino workspace 18Lotus Domino(Superseded) workspace 18

MMail



Mail Avg attribute 150, 152Mail Count attribute 148, 151, 152Mail Count Over attribute 149Mail Max attribute 149, 152Mail Min attribute 149Mail Name attribute 152

Mail Size attribute 148Mail Volume attribute 151Mail workspace 21Mail(Superseded) workspace 22Max Size Delivered attribute 95, 101Message Priority attribute 158messages

built-in features 183for Lotus Domino agent 207format 207overview 206syntax 207

Minutes Since Recv attribute 153Minutes Since Send attribute 154

NName attribute 29Navigate attribute 40new attribute groups 2new or changed attributes 2Node attribute 29, 33, 35, 37, 39, 45, 46, 51, 56, 58, 59, 67, 75,

77, 80, 85, 89, 90, 96, 102, 104, 105, 108, 109, 111, 113, 117, 121,123, 127, 130, 134, 136, 138, 139, 147, 148, 150, 151, 153, 154,157, 158, 160

notes.ini file 10NotesProgram keyword 10NSF Pool Peak attribute 50, 55NSF Pool Used attribute 50, 55NSF Replicate Notes Received attribute 50, 55NSF Replicate Notes Sent attribute 51, 55

OObject Name attribute 160Object Status attribute 161Object Type attribute 160OPAL documentation 230Open About attribute 40Open Agent attribute 41Open Database attribute 41Open Document attribute 41Open Element attribute 41Open Form attribute 42Open Help attribute 42Open Icon attribute 42Open Navigator attribute 43Open Redir Failover Success attribute 130Open Redir Failover Unsucc attribute 130Open Redir Fover By Pth Suc attribute 131Open Redir Fover By Pth Unsuc attribute 131Open Redir Load Bal Pth Succ attribute 132Open Redir Load Bal Pth Unsuc attribute 132Open Redir Load Bal Succ Tot attribute 131Open Redir Load Bal Unsuc Tot attribute 131Open Req Cluster Busy attribute 132Open Req Db Out Of Service attribute 133Open Req Load Balanced attribute 133Open Server attribute 43Open View attribute 43Originating Server attribute 149

PPage Faults per Sec attribute 31Peak Messages Transferred attribute 94, 100


Percent Privileged Time attribute 31Percent Processor Time attribute 31Percent User Mode Time attribute 31performance considerations 203Performance Object Status attribute group 160PID attribute 31ping interval

changing on Linux 10changing on UNIX 10changing on Windows 10

policiesmore information 181overview 181

Probe Count attribute 133Probe Error attribute 133problems and workarounds 193Process Access FTP attribute 142Process Access Gopher attribute 142Process Access HTTP attribute 142Process KB Received attribute 142Process KB Sent attribute 142Process Num Active attribute 143Process Num Busy attribute 143Process Num Idle attribute 143Process Num Maximum attribute 143Process State attribute 144Process URLs Failed attribute 144Process URLs Requested attribute 144Process URLs Succeeded attribute 144publications

Lotus Domino agent 229OPAL 230prerequisite 229Redbooks 230related 230Technotes 230types 229

Pulled Documents Transferred attribute 155Pulled KB Received attribute 155Pulled KB Sent attribute 155purposes

troubleshooting 183Pushed Documents Transferred attribute 156Pushed KB Received attribute 156Pushed KB Sent attribute 156

Qqueries, using attributes 25Query Name attribute 160

RRead Form attribute 43Receive Error attribute 60, 68Redbooks 230remote

installation and configuration 13remote deployment

troubleshooting 197Replication Name attribute 153, 155Replication Time attribute 156Requests Per 1Hour attribute 61, 69Requests Per 1Minute attribute 61, 69Requests Per 5Minutes attribute 61, 69Response Time attribute 126

Retry Waiting attribute 115, 119root user 10

SSearch Site attribute 44Search View attribute 44Seconds On Queue attribute 117, 120Seconds On Queue Max attribute 117, 121Server



Server Build attribute 123, 127Server Message attribute 158Server Name attribute 33, 35, 37, 39, 45, 46, 51, 56, 58, 59, 67,

75, 78, 80, 85, 89, 90, 96, 102, 104, 106, 108, 110, 111, 113, 117,121, 123, 127, 130, 134, 137, 139, 140, 147, 149, 150, 152, 153,154, 157, 158

Server OS attribute 123, 127Server Running attribute 61, 69, 80, 85Server Start attribute 124, 127Server Version attribute 123, 127Server workspace 22Server(Superseded) workspace 23Servers attribute 113, 118Sess Accept Queue attribute 75, 78Sess Active attribute 75, 78Sess Inb Tot SSL Bad Hshake attribute 83, 87Sess Inbound Accept Queue attribute 61, 69, 81, 85, 134, 137Sess Inbound Active attribute 62, 70, 81, 85, 134, 137Sess Inbound Active SSL attribute 70, 81, 85Sess Inbound KB Received attribute 62, 70, 75, 78, 81, 86, 135,

137Sess Inbound KB Received Interval attribute 136Sess Inbound KB Sent attribute 62, 70, 76, 78, 82, 86, 135, 138Sess Inbound KB Sent Interval attribute 136Sess Inbound Non SSL attribute 76, 79Sess Inbound Peak attribute 62, 71, 82, 86, 135, 138Sess Inbound Peak SSL attribute 82, 86Sess Inbound SSL attribute 63, 71Sess Inbound Total attribute 63, 71, 82, 87, 135, 137Sess Inbound Total SSL attribute 63, 71, 83, 87Sess Non SSL attribute 83, 87Sess Outbound Active attribute 63, 72Sess Outbound Active SSL attribute 64, 72Sess Outbound KB Received attribute 64, 72Sess Outbound KB Sent attribute 64, 72Sess Outbound Peak attribute 64, 72Sess Outbound Peak SSL attribute 65, 73Sess Outbound Total attribute 65, 73Sess Outbound Total SSL attribute 65, 73Sess Peak attribute 76, 79Sess SSL attribute 83, 88Sess Threads Busy attribute 65, 73, 76, 79, 84, 88Sess Threads Idle attribute 66, 74, 77, 79, 84, 88Sess Threads In Thread Pool attribute 66, 74Sess Threads Peak attribute 66, 74Sess Total attribute 77, 80, 84, 88Session KB In attribute 115, 119Session KB Out attribute 115, 120Session(Superseded) workspace 23Sessions


descriptions 23

Index 243

Sessions (continued)workspaces (continued)

list 18Sessions Dropped attribute 124, 128Sessions Est Incoming attribute 106, 108Sessions Est Outgoing attribute 106, 108Sessions Peak attribute 106, 108Sessions workspace 23silent installation 5situations

general troubleshooting 203, 204KGB_Domino_DB_Size_Warn 172KGB_Domino_Failover_Warn 171KGB_Domino_Mail_Dead_Warn 173KGB_Domino_Mail_Dead_Warn_2 174KGB_Domino_Mail_Waiting_Warn 173KGB_Domino_Mail_Waiting_Warn_2 175KGB_Domino_Rep_Miss_Crit 178KGB_Domino_Serv_Avail_Crit 169KGB_Domino_Serv_Avail_Idx_Crit 175KGB_Domino_Serv_Config_Crit 170KGB_Domino_Serv_Sess_Drop_Crit 176KGB_Domino_SMTP_Task_Warn 177KGB_Domino_Srv_Avl_Idx_Crit_2 176KGB_Domino_Srv_Clus_Avail_Crit 169KGB_Domino_Srv_Clus_Avail_Warn 171KGB_Domino_Srv_Ses_Drop_Crit_2 177KGB_Domino_Whitespace_Pct_Warn 172list of all 168more information 167overview 167predefined 168

situations, using attributes 25Software Support 206Start Time attribute 122starting

agent 10instance 10

starting the agentLinux 10UNIX 10

State attribute 45Statistic Name attribute 148, 149, 151, 152, 153, 155, 158Status attribute 30status of the Domino Server

determining on Linux 10determining on UNIX 10determining on Windows 10

stoppinginstance 10

Successful attribute 110, 112, 114, 118support

gathering information for 183list of messages 207messages 206

support assistant 206syntax

messages 207

Ttacmd addSystem command 13Take Action commands

more information 179overview 179troubleshooting 206

Task Name attribute 139

Task Status attribute 139Task Status Duration attribute 139Technotes 230Thread Count attribute 31Time Current attribute 145Time Duration attribute 145Time Start attribute 145Timestamp attribute 29, 33, 35, 37, 39, 45, 46, 51, 56, 58, 59,

67, 75, 78, 80, 85, 89, 90, 96, 102, 104, 106, 108, 109, 111, 113,117, 121, 123, 127, 130, 134, 137, 139, 147, 149, 150, 152, 153,154, 157, 158, 160

Total All Appts Reservations attribute 35, 37Total All Users Resources attribute 35, 37Total Appts attribute 36, 38Total attribute 44Total Failures attribute 92, 98Total KB Delivered attribute 92, 99Total KB Transferred attribute 95, 102, 103, 105Total Missed attribute 156Total Pending attribute 92, 99Total Reservations attribute 36, 38Total Resources attribute 36, 38Total Routed attribute 93, 99, 102, 104Total Routed NRPC attribute 96Total Routed SMTP attribute 95Total Successes attribute 157Total Users attribute 36, 38trace logs 184trademarks 234Trans Per Minute attribute 126Trans Per Minute Peak attribute 124, 128Trans Total attribute 125, 128Transfer Failures attribute 94, 101Transferred attribute 94, 100, 103, 104troubleshooting 183, 193

agents 197built-in features 183installation 193installation logs 186messages 206remote deployment 197situations 203, 204Take Action commands 206uninstallation 193uninstallation logs 186workspaces 201

Type attribute 30

Uuninstallation

log file 186problems 193

uninstalling the monitoring agent 11Unknown attribute 44URLs Failed attribute 145URLs Requested attribute 145URLs Succeeded attribute 145user interfaces options 3Users Active 30 Min attribute 125, 129Users attribute 125, 129Users Peak attribute 125, 129


VVersion attribute 146View attribute 45View Avg attribute 159View Count attribute 159View Max attribute 159View Pct Under attribute 159View Pct Under Value attribute 159views

Availability workspace 19Availability(Superseded) workspace 19Cluster workspace 19Cluster(Superseded) workspace 20Database Status workspace 20Database workspace 20Database(Superseded) workspace 21IW Mail workspace 21IW Replication workspace 21IW Server workspace 22Lotus Domino workspace 18Lotus Domino(Superseded) workspace 18Mail workspace 21Mail(Superseded) workspace 22Server workspace 22Server(Superseded) workspace 23Session(Superseded) workspace 23Sessions workspace 23

Virtual Size attribute 31VPOOL Max Buf attribute 146VPOOL Max Element attribute 146VPOOL Max Marker attribute 146VPOOL Max Text attribute 146VPOOL Max URL attribute 147

WWaiting attribute 91, 97Waiting For DIR attribute 93, 99Waiting For DNS attribute 93, 100Waiting Recipients attribute 93, 100Work Queue Depth attribute 116, 120Work Queue Depth Avg attribute 116, 120Work Queue Depth Max attribute 116, 120workarounds 193

agents 197remote deployment 197situations 203Take Action commands 206workspaces 201

Working Set Size attribute 31workspaces

Availability 19Availability(Superseded) 19Cluster 19Cluster(Superseded) 20Database 20Database Status 20Database(Superseded) 21IW Mail 21IW Replication 21IW Server 22list of all 17Lotus Domino 18Lotus Domino(Superseded) 18Mail 21Mail(Superseded) 22

workspaces (continued)more information 17overview 17predefined 17Server 22Server(Superseded) 23Session(Superseded) 23Sessions 23troubleshooting 201

Index 245

��

Printed in USA

SC27-2346-00