Tivoli Monitoring: Linux OS Agent


Version 6.1.0

User’s Guide

IBM Confidential SC32-9447-00

 Tivoli Monitoring: Linux OS Agent
®


Version 6.1.0

User’s Guide

IBM Confidential SC32-9447-00

 IBM Confidential

Note
Before using this information and the product it supports, read the information in Appendix D, “Notices,” on page 97.

First Edition (November 2005)

This edition applies to version 6.1 of the IBM Tivoli Monitoring: Linux OS Agent (5724-C04) and to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
IBM Confidential

Contents
Tables . . . . . . . . . . . . . . . v Attribute groups and attributes for the Monitoring
Agent for Linux OS. . . . . . . . . . . . 24
About this guide . . . . . . . . . . vii CPU attributes . . . . . . . . . . . . 24
CPU Averages attributes . . . . . . . . . 25
Who should read this guide . . . . . . . . . vii
CPU Config attributes . . . . . . . . . . 26
What this guide contains . . . . . . . . . . vii
Disk attributes . . . . . . . . . . . . 27
Publications . . . . . . . . . . . . . . viii
Disk I/O attributes . . . . . . . . . . . 28
Prerequisite publications . . . . . . . . . viii
Disk Usage Trends attributes . . . . . . . 29
Related publications . . . . . . . . . . viii
I/O Ext attributes . . . . . . . . . . . 30
Accessing terminology online . . . . . . . viii
Network attributes . . . . . . . . . . . 31
Accessing publications online . . . . . . . ix
NFS Statistics attributes . . . . . . . . . 33
Ordering publications . . . . . . . . . . ix
OS Config attributes . . . . . . . . . . 36
Accessibility . . . . . . . . . . . . . . ix
Process attributes . . . . . . . . . . . 37
Tivoli technical training . . . . . . . . . . ix
Process User Info attributes . . . . . . . . 39
Support information . . . . . . . . . . . . x
RPC Statistics attributes . . . . . . . . . 41
Conventions used in this guide . . . . . . . . x
Sockets Detail attributes . . . . . . . . . 42
Typeface conventions . . . . . . . . . . x
Sockets Status attributes . . . . . . . . . 43
Operating system-dependent variables and paths x
Swap Rate attributes . . . . . . . . . . 44
System Statistics attributes . . . . . . . . 45
Chapter 1. Overview of the Monitoring User Login attributes . . . . . . . . . . 46
Agent for Linux OS . . . . . . . . . . 1 VM Stats attributes . . . . . . . . . . . 47
IBM Tivoli Monitoring overview . . . . . . . . 1 Disk capacity planning for historical data . . . . 47
Features of the Monitoring Agent for Linux OS . . . 1
Monitoring Agent for Linux OS components . . . . 2 Chapter 6. Situations reference . . . . 51
User interface options . . . . . . . . . . . 2 About situations . . . . . . . . . . . . . 51
More information about situations . . . . . . . 51
Chapter 2. Requirements for the Predefined situations . . . . . . . . . . . 52
monitoring agent . . . . . . . . . . . 5 Linux_Fragmented_File_System situation . . . 52
Linux_High_CPU_Overload situation . . . . . 52
Chapter 3. How to use the Monitoring Linux_High_CPU_System situation . . . . . 52
Linux_High_Packet_Collisions situation . . . . 53
Agent for Linux OS . . . . . . . . . . 7
Linux_High_RPC_Retransmit situation . . . . 53
View real-time data about Linux . . . . . . . . 7
Linux_High_Zombies situation . . . . . . . 53
Investigate an event . . . . . . . . . . . . 8
Linux_Low_Pct_Inodes situation . . . . . . 53
Recover the operation of a resource . . . . . . . 8
Linux_Low_percent_space situation . . . . . 53
Customize your monitoring environment . . . . . 9
Linux_Low_Space_Available situation . . . . 53
Monitor with custom situations that meet your
Linux_Network_Status situation . . . . . . 53
requirements . . . . . . . . . . . . . . 10
Linux_NFS_Buffer_High situation . . . . . . 54
Collect and view historical data. . . . . . . . 11
Linux_NFS_Getattr_High situation . . . . . 54
Linux_NFS_rdlink_high situation . . . . . . 54
Chapter 4. Workspaces reference . . . 13 Linux_NFS_Read_High situation . . . . . . 54
About workspaces . . . . . . . . . . . . 13 Linux_NFS_Writes_High situation . . . . . . 54
More information about workspaces . . . . . . 13 Linux_Packets_Error situation . . . . . . . 54
Predefined workspaces . . . . . . . . . . 13 Linux_Process_High_Cpu situation . . . . . 54
Capacity Usage Information group . . . . . 14 Linux_Process_stopped situation . . . . . . 55
Disk Usage workspace. . . . . . . . . . 15 Linux_RPC_Bad_Calls situation. . . . . . . 55
Network group . . . . . . . . . . . . 16 Linux_System_Thrashing situation . . . . . . 55
Process group . . . . . . . . . . . . 17
System Information group . . . . . . . . 18 Chapter 7. Take Action commands
Users workspace . . . . . . . . . . . 21
reference . . . . . . . . . . . . . . 57
About Take Action commands . . . . . . . . 57
Chapter 5. Attributes reference . . . . 23 More information about Take Action commands . . 57
About attributes . . . . . . . . . . . . . 23 Predefined Take Action commands . . . . . . 57
More information about attributes . . . . . . . 23 Sample_kill_Process action . . . . . . . . 58

© Copyright IBM Corp. 2005 iii

 IBM Confidential

Chapter 8. Policies reference . . . . . 59 Agent problem determination . . . . . . . 84

About policies . . . . . . . . . . . . . 59 Tivoli Enterprise Portal problem determination 86
More information about policies . . . . . . . 59 Problem determination for remote deployment 87
Predefined policies . . . . . . . . . . . . 59 Situation problem determination . . . . . . 87
Support information . . . . . . . . . . . 90
Appendix A. IBM Tivoli Enterprise Searching knowledge bases . . . . . . . . 90
Obtaining fixes . . . . . . . . . . . . 91
Console event mapping . . . . . . . 61 Receiving weekly support updates . . . . . 91
Contacting IBM Software Support . . . . . . 92
Appendix B. Problem determination . . 73
Gathering product information for IBM Software Appendix C. Accessibility . . . . . . 95
Support . . . . . . . . . . . . . . . 73 Navigating the interface using the keyboard . . . 95
Built-in problem determination features . . . . . 73 Magnifying what is displayed on the screen . . . 95
Problem classification . . . . . . . . . . . 74
Trace logging . . . . . . . . . . . . . . 74
Overview of log file management . . . . . . 74
Appendix D. Notices . . . . . . . . . 97
Examples of trace logging . . . . . . . . 75 Trademarks . . . . . . . . . . . . . . 99
Principal trace log files . . . . . . . . . 75
Setting RAS trace parameters . . . . . . . 78 Index . . . . . . . . . . . . . . . 101
Problems and workarounds . . . . . . . . . 79
Installation and configuration problem
determination . . . . . . . . . . . . 79

iv IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Tables
1. Requirements for the Monitoring Agent for 13. Problems and solutions for installation and
Linux OS . . . . . . . . . . . . . . 5 configuration . . . . . . . . . . . . 80
2. Viewing real-time data about Linux . . . . . 7 14. General problems and solutions for
3. Investigating an event . . . . . . . . . 8 uninstallation . . . . . . . . . . . . 83
4. Recovering the operation of a resource . . . . 9 15. Agent problems and solutions . . . . . . 84
5. Customizing your monitoring environment 9 16. Tivoli Enterprise Portal problems and solutions 86
6. Monitoring with custom situations . . . . . 11 17. Remote deployment problems and solutions 87
7. Collecting and viewing historical data . . . 12 18. Specific situation problems and solutions 87
8. Capacity planning for historical data . . . . 48 19. Problems with configuring situations that you
9. Overview of Distributed Monitoring migrated solve in the Situation Editor . . . . . . . 88
situations . . . . . . . . . . . . . 61 20. Problems with configuration of situations that
10. Overview of event slots to event classes 62 you solve in the Workspace area . . . . . 89
11. Information to gather before contacting IBM 21. Problems with configuration of situations that
Software Support . . . . . . . . . . 73 you solve in the Manage Tivoli Enterprise
12. Trace log files for troubleshooting agents 76 Monitoring Services window . . . . . . . 90

© Copyright IBM Corp. 2005 v

 IBM Confidential

vi IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

About this guide

The IBM Tivoli Monitoring: Linux OS Agent User’s Guide provides information about
using IBM® Tivoli® Monitoring: Linux® OS Agent.

Use the requirements chapter in this guide along with the IBM Tivoli Monitoring
Installation and Setup Guide to install and set up the software.

Use the information in this guide along with the IBM Tivoli Monitoring User’s Guide
to monitor Linux.

Who should read this guide

This guide is for system administrators who install and use the Monitoring Agent
for Linux OS to monitor and manage Linux resources.

Readers must be familiar with the following topics:

v Tivoli Enterprise™ Portal interface
v IBM Tivoli Monitoring application software
v IBM Tivoli Enterprise Console® (optional)
v Linux operating systems

What this guide contains

This guide contains the following chapters:
v Chapter 1, “Overview of the Monitoring Agent for Linux OS,” on page 1
Provides an introduction to the Monitoring Agent for Linux OS.
v Chapter 2, “Requirements for the monitoring agent,” on page 5
Provides requirement information specific to the Monitoring Agent for Linux OS.
v Chapter 3, “How to use the Monitoring Agent for Linux OS,” on page 7
Provides a list of tasks to perform when using the monitoring agent, a list of
procedures for completing each task, and references for where to find
information about the procedures. After completing installation and
configuration and becoming familiar with the information in Chapter 1 of this
guide, use this chapter to see how you can use the monitoring agent.
v Chapter 4, “Workspaces reference,” on page 13
Provides an overview of workspaces, references to additional information about
workspaces, and descriptions of predefined workspaces in this monitoring agent.
v Chapter 5, “Attributes reference,” on page 23
Provides an overview of attributes, references to additional information about
attributes, descriptions of the attribute groups and attributes in this monitoring
agent, and disk space requirements for historical data.
v Chapter 6, “Situations reference,” on page 51
Provides an overview of situations, references to additional information about
situations, and descriptions of the predefined situations in this monitoring agent.
v Chapter 7, “Take Action commands reference,” on page 57

© Copyright IBM Corp. 2005 vii

 IBM Confidential

Provides detailed information about the Take Action commands, references to

additional information about Take Action commands, and descriptions of the
Take Action commands provided in this monitoring agent.
v Chapter 8, “Policies reference,” on page 59
Provides an overview of policies, references for detailed information about
policies, and descriptions of the predefined policies included in this monitoring
agent.
v Appendix A, “IBM Tivoli Enterprise Console event mapping,” on page 61
Provides an overview of the IBM Tivoli Enterprise Console event mapping
information for this monitoring agent.
v Appendix B, “Problem determination,” on page 73
Provides information about troubleshooting the various components of the
Monitoring Agent for Linux OS, information about log files and messages, and
information about your options for obtaining software support.
v Appendix C, “Accessibility,” on page 95
Provides information about the accessibility features in the Monitoring Agent for
Linux OS.
v Appendix D, “Notices,” on page 97
Provides IBM and Tivoli notices and trademark information as it applies to the
Monitoring Agent for Linux OS.

Publications
This section lists publications relevant to the use of the Monitoring Agent for Linux
OS. It also describes how to access these publications online and how to order
these publications.

Prerequisite publications
To use the information in this guide effectively, you must have some knowledge of
IBM Tivoli Monitoring products, which you can obtain from the following
documentation:
v IBM Tivoli Monitoring Administrator’s Guide
v IBM Tivoli Monitoring Installation and Setup Guide
v IBM Tivoli Monitoring Problem Determination Guide
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring
v IBM Tivoli Monitoring User’s Guide
v Introducing IBM Tivoli Monitoring Version 6.1

Related publications
The 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 Developer’s Guide

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

viii IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

Ordering publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications.

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.

For additional information, see Appendix C, “Accessibility,” on page 95.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education/

About this guide ix

 IBM Confidential

Support information
“Support information” on page 90 describes the following options for obtaining
support for IBM products:
v “Searching knowledge bases” on page 90
v “Obtaining fixes” on page 91
v “Contacting IBM Software Support” on page 92

Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths.

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Operating system-dependent variables and paths

The direction of the slash for directory paths might vary in this documentation. No
matter which type of slash you see in the documentation, use the following
guidelines for a slash:
v If using UNIX®, use a forward slash (/).
v If using Windows®, use a backslash (\).

The names of environment variables are not always the same in Windows and
UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX.

For environment variables, use the following guidelines:

v If using UNIX, use $variable.
v If using Windows, use %variable%.
x IBM Tivoli Monitoring: Linux OS Agent: User’s Guide
IBM Confidential

Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

About this guide xi

 IBM Confidential

xii IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 1. Overview of the Monitoring Agent for Linux OS

The Monitoring Agent for Linux OS provides you with the capability to monitor
Linux, and to perform basic actions with Linux. This chapter provides a
description of the features, components, and interface options for the Monitoring
Agent for Linux OS.

IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Monitoring Agent for Linux OS.
IBM Tivoli Monitoring provides a way to monitor the availability and performance
of all the systems in your enterprise from one or several designated workstations.
It also provides useful historical data that you can use to track trends and to
troubleshoot system problems.

You can use IBM Tivoli Monitoring to do the following:

v Monitor for alerts on the systems that you are managing by using predefined
situations or custom situations.
v Establish your own performance thresholds.
v Trace the causes leading to an alert.
v Gather comprehensive data about system conditions.
v Use policies to perform actions, schedule work, and automate manual tasks.

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

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” on

page viii for complete information about IBM Tivoli Monitoring and the Tivoli
Enterprise Portal.

Features of the Monitoring Agent for Linux OS

As part of the Tivoli Enterprise Portal for Distributed Systems, the Monitoring
Agent for Linux OS offers a central point of management of Linux-based
environments. It provides a comprehensive means for gathering exactly the
information you need to detect problems early and to prevent them. Information is
standardized across all systems, and you can monitor servers from a single
workstation. The Tivoli Enterprise Portal lets you easily collect and analyze specific
information.

The Monitoring Agent for Linux OS is an intelligent, remote monitoring agent that
resides on managed resources. It assists you in anticipating trouble and warns
systems administrators when critical events take place on their systems. With the
Monitoring Agent for Linux OS, systems administrators can set threshold levels
and flags as desired to alert them when the system reaches these thresholds.

For Tivoli Enterprise Portal, information appears in named workspaces. Tivoli

Enterprise Portal refers to this tabular format for information as a table view.
Information can also be displayed in the workspace as charts, graphs, or other
formats that you can specify.

© Copyright IBM Corp. 2005 1

 IBM Confidential

The Monitoring Agent for Linux OS provides the following benefits:

v Simplifies application and system management by managing applications,
platforms, and resources across your environment.
v Helps to increase profits by providing you with real-time access to reliable,
up-to-the-minute data that allows you to make faster, better-informed operating
decisions.
v Scales and ports to new platforms by supporting a wide variety of platforms.
v Improves system performance by letting you integrate, monitor, and manage
your system, network, console, and mission-critical applications. A monitoring
agent alerts the Tivoli Enterprise Monitoring Server when conditions on the
system network meet threshold-based conditions. These alerts notify your
systems administrator to limit and control database usage. You can view data
gathered by the Tivoli Enterprise Monitoring Server in tables and charts for the
status of your distributed database systems.
v Enhances efficiency by monitoring diverse platforms and networks from a single
PC screen. Depending on your Tivoli Enterprise Portal configuration, you can
collect and monitor data across platforms. Management agents gather and filter
status information at the managed resource rather than at the hub, eliminating
unnecessary data transmission and sending only data that is relevant to changes
in status conditions. The Monitoring Agent for Linux OS helps you monitor and
gather the consistent, accurate, and timely information you require to effectively
perform your job.

Monitoring Agent for Linux OS components

After you install and set up the Monitoring Agent for Linux OS, you have an
environment that contains the client, server, and monitoring agent implementation
for IBM Tivoli Monitoring that contains the following components:
v Tivoli Enterprise Portal client with a Java-based user interface for viewing and
monitoring your enterprise.
v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli
Enterprise Monitoring Server and enables retrieval, manipulation, and analysis
of data from the monitoring agents.
v Tivoli Enterprise Monitoring Server, which acts as a collection and control point
for alerts received from the monitoring agents, and collects their performance
and availability data.
v Management agent, the Monitoring Agent for Linux OS, installed on the systems
or subsystems that you want to monitor. This monitoring agent collects and
distributes data to a Tivoli Enterprise Portal Server.

For both of the IBM Tivoli Monitoring environments (IBM Tivoli Monitoring 5.x
and IBM Tivoli Monitoring 6.1), IBM Tivoli Enterprise Console is an optional
component, which acts as a central collection point for events from a variety of
sources, including those from other Tivoli software applications, Tivoli partner
applications, custom applications, network management platforms, and relational
database systems. You can view these events through the Tivoli Enterprise Portal
(using the event viewer), and you can forward events from IBM Tivoli Monitoring
situations to the IBM Tivoli Enterprise Console component.

User interface options

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

2 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Tivoli Enterprise Portal browser client interface

The browser interface is automatically installed with Tivoli Enterprise
Portal. To start Tivoli Enterprise Portal in your Internet browser, enter the
URL for a specific Tivoli Enterprise Portal browser client installed on your
Web server.
Tivoli Enterprise Portal desktop client interface
The desktop interface is a Java-based graphical user interface (GUI) on a
Windows workstation.
IBM Tivoli Enterprise Console
Event management application
Manage Tivoli Enterprise Monitoring Services window
The window for the Manage Tivoli Enterprise Monitoring Services utility is
used for configuring the agent and starting Tivoli services not already
designated to start automatically.

Chapter 1. Overview of the Monitoring Agent for Linux OS 3

 IBM Confidential

4 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 2. Requirements for the monitoring agent

This chapter contains information about the following topics and procedures
relevant to the installation and configuration of the Monitoring Agent for Linux
OS.

In addition to the requirements described in the IBM Tivoli Monitoring Installation

and Setup Guide, the Monitoring Agent for Linux OS has the requirements listed in
Table 1.
Table 1. Requirements for the Monitoring Agent for Linux OS
Operating system Linux
Operating system versions v Linux on zSeries
– RHEL AS 3.0 (31-bit or 64-bit)
– RHEL AS 4.0 (31-bit or 64-bit)
– SLES 8 (31-bit or 64-bit)
– SLES 9 (31-bit or 64-bit)
v Linux on Intel® (32-bit)
– RHEL AS/ES 2.1
– RHEL AS/ES 3.0
– RHEL AS/ES 4.0
– SLES 8
– SLES 9

The Linux version must support the Korn shell (ksh) and
Motif Window Manager (libmotif) for installation of the
monitoring agent.
Memory v 256 MB RAM at a minimum although 512 MB or
higher for better performance
Disk space v 100 MB of disk space for the base monitoring agent
v Historical data disk space: see “Disk capacity planning
for historical data” on page 47
Other requirements v TCP/IP
v The monitoring agent must have the permissions
necessary to perform requested actions. For example, if
the user ID you used to log onto the system to install
the monitoring agent (locally or remotely) does not
have the permission to perform a particular action
being monitored by the monitoring agent (such as
running a particular command), the monitoring agent
will be unable to perform the requested action.

© Copyright IBM Corp. 2005 5

 IBM Confidential

6 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 3. How to use the Monitoring Agent for Linux OS

After you have installed and configured the Monitoring Agent for Linux OS, you
can begin using this monitoring agent to monitor your resources.

This chapter provides information about how to use the Monitoring Agent for
Linux OS to perform the following tasks:
v “View real-time data about Linux”
v “Investigate an event” on page 8
v “Recover the operation of a resource” on page 8
v “Customize your monitoring environment” on page 9
v “Monitor with custom situations that meet your requirements” on page 10
v “Collect and view historical data” on page 11

For each of these tasks, there is a list of procedures that you perform to complete
the task. For the procedures, there is a cross-reference to where you can find
information about performing that procedure. Information about the procedures is
located in subsequent chapters and appendixes of this user’s guide and in the IBM
Tivoli Monitoring documentation.

View real-time data about Linux

After you install, configure, and start the Monitoring Agent for Linux OS, the
monitoring agent begins monitoring.

Table 2 contains a list of the procedures for viewing the real-time data about Linux
that the monitoring agent collects. The table also contains a cross-reference to
where you can find information about each procedure.
Table 2. Viewing real-time data about Linux
Procedure Where to find information
View the hierarchy of your monitored IBM Tivoli Monitoring User’s Guide:
resources from a system point of view ″Navigating through workspaces″ (in
(Navigator view organized by operating ″Monitoring: real-time and event-based″
platform, system type, monitoring agents, chapter)
and attribute groups).
View the indicators of real or potential
problems with the monitored resources
(Navigator view).
View changes in the status of the resources IBM Tivoli Monitoring User’s Guide: ″Using
that are being monitored (Enterprise workspaces″ (in ″Monitoring: real-time and
Message Log view). event-based″ chapter)
View the status of the agents in the Chapter 4, “Workspaces reference,” on page
managed enterprise that you are monitoring 13 in this guide
(Monitoring Agent Status view).

© Copyright IBM Corp. 2005 7

 IBM Confidential

Table 2. Viewing real-time data about Linux (continued)

Procedure Where to find information
View the number of times an event has been IBM Tivoli Monitoring User’s Guide: ″Using
opened for a situation during the past 24 workspaces″ (in ″Monitoring: real-time and
hours (Open Situations Count view). event-based″ chapter)

Chapter 4, “Workspaces reference,” on page

13 in this guide

Chapter 6, “Situations reference,” on page 51

in this guide
Manipulate the views in a workspace. IBM Tivoli Monitoring User’s Guide: ″Using
views″ (in ″Monitoring: real-time and
event-based″ chapter)

Investigate an event
When the conditions of a situation have been met, an event indicator is displayed
in the Navigator. When an event occurs, you want to obtain information about that
event so you can correct the conditions and keep your enterprise running
smoothly. The situation must be associated with a Navigator Item in order to
appear.

Table 3 contains a list of the procedures for investigating an event and a

cross-reference to where you can find information about each procedure.
Table 3. Investigating an event
Procedure Where to find information
Determine which situation raised the event IBM Tivoli Monitoring User’s Guide: ″Opening
and identify the attributes that have values the situation event workspace″ (in
that are contributing to the alert. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)
Review available advice. Chapter 4, “Workspaces reference,” on page
13 in this guide
Notify other users that you have taken IBM Tivoli Monitoring User’s Guide:
ownership of the problem related to an ″Acknowledging an situation event″ (in
event and are working on it. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)
Remove the event from the Navigator. IBM Tivoli Monitoring User’s Guide: ″Closing
the situation event workspace″ (in
″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)

Recover the operation of a resource

When you find out that a resource is not operating as desired, you can control it
manually or automatically using Take Action commands.

Table 4 on page 9 contains a list of the procedures for recovering the operation of a
resource and a cross-reference to where you can find information about each
procedure.

8 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 4. Recovering the operation of a resource

Procedure Where to find information
Take an action on a resource manually. IBM Tivoli Monitoring User’s Guide:
v ″Other views″ (in ″Custom workspaces″
chapter, ″Workspace views″ section)
v ″Take action – Reflex automation″ (in
Situations for event-based monitoring″
chapter, ″Event-based monitoring
overview″ section)

Chapter 7, “Take Action commands

reference,” on page 57 in this guide
Take an action on a system condition IBM Tivoli Monitoring User’s Guide:
automatically by setting up a situation to ″Situations for event-based monitoring″
run a Take Action command. chapter
v ″Customizing a situation″
v ″Creating a situation″
v ″Specify an action to take″
v ″Distribute the situation″

Chapter 7, “Take Action commands

reference,” on page 57 in this guide
Take multiple actions on system conditions IBM Tivoli Monitoring User’s Guide: ″Policies
automatically using a policy. for automation″ chapter
v ″Creating a policy″
v ″Maintaining policies″
Take actions across systems, monitoring v ″Workflows window″
agents, or computers using a policy.
Chapter 8, “Policies reference,” on page 59 in
this guide

Customize your monitoring environment

You can change how your monitoring environment looks by creating new
workspaces with one or more views in it.

Table 5 contains a list of the procedures for customizing your monitoring

environment and a cross-reference to where you can find information about each
procedure.
Table 5. Customizing your monitoring environment
Procedure Where to find information
Display data in tables or charts (views) in IBM Tivoli Monitoring User’s Guide:
Tivoli Enterprise Portal. v ″Custom workspaces″
v ″Table and chart views″
Display an overview of changes in the status IBM Tivoli Monitoring User’s Guide: ″Message
of the situations for your monitored log view″ (in ″Situation event views:
resources (Message Log View). message log, situation event console,
graphic, and Tivoli Enterprise Console″
chapter)

Chapter 3. How to use the Monitoring Agent for Linux OS 9

 IBM Confidential

Table 5. Customizing your monitoring environment (continued)

Procedure Where to find information
Specify which attributes to retrieve for a IBM Tivoli Monitoring User’s Guide: ″Creating
table or chart so you can retrieve only the custom queries″ (in ″Table and chart views″
data you want by creating custom queries. chapter)

Chapter 5, “Attributes reference,” on page 23

in this guide
Build links from one workspace to another. IBM Tivoli Monitoring User’s Guide:
v ″Link from a workspace″ (in ″Custom
workspaces″ chapter)
v ″Link from a table or chart″ (in ″Table and
chart views″ chapter)
Identify which predefined situations started IBM Tivoli Monitoring User’s Guide: ″What
running automatically when you started the the enterprise workspace shows″ (in
Tivoli Enterprise Monitoring Server. ″Monitoring: real-time and event-based″
chapter, ″Using workspaces″ section)

Chapter 6, “Situations reference,” on page 51

in this guide
Determine whether to run situations as Chapter 6, “Situations reference,” on page 51
defined, modify the values in situations, or in this guide
create new situations to detect possible
problems.

Monitor with custom situations that meet your requirements

When your environment requires situations with values that are different from
those in existing situations, or when you need to monitor conditions not defined
by the existing situations, you can create custom situations to detect problems with
resources in two ways:
v Create an entirely new situation
v Create a situation by copying and editing a predefined situation

Note: When you create and run a situation, an IBM Tivoli Enterprise Console
event is created. For information on how to define event severities from
forwarded IBM Tivoli Monitoring situations and other event information,
see the IBM Tivoli Monitoring Administrator’s Guide.

You can specify the following information for a situation:

v Name
v Attribute group and attributes
v Qualification to evaluate multiple rows when a situation has a multiple-row
attribute group (display item)
v Formula
v Take Action commands
v Run at startup
v Sampling interval
v Persistence
v Severity
v Clearing conditions

10 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

v Expert Advice
v When a true situation closes
v Available Managed Systems

Table 6 contains a list of the procedures for monitoring your resources with custom
situations that meet your requirements and a cross-reference to where you can find
information about each procedure.
Table 6. Monitoring with custom situations
Procedure Where to find information
Create an entirely new situation. IBM Tivoli Monitoring User’s Guide: ″Creating
a new situation″ (in ″Situations for
event-based monitoring″ chapter, ″Creating a
situation″ section)

Chapter 5, “Attributes reference,” on page 23

in this guide
Create a situation by copying and editing a IBM Tivoli Monitoring User’s Guide:
predefined situation. ″Customizing a situation″ (in ″Situations for
event-based monitoring″ chapter)

Chapter 6, “Situations reference,” on page 51

in this guide

Chapter 5, “Attributes reference,” on page 23

in this guide
Run a situation on a managed system. IBM Tivoli Monitoring User’s Guide:
″Situations for event-based monitoring″
chapter
v ″Associate situations with navigator
items″
v ″Distribute the situation″ (in ″Customizing
a situation″ section)
v ″Start, stop, or delete a situation″

Collect and view historical data

When you collect historical data, you specify the following configuration
requirements:
v Attribute groups for which to collect data
v Collection interval
v Summarization and pruning of attribute groups
v Roll-off interval to a data warehouse, if any
v Where to store the collected data (at the agent or the Tivoli Enterprise
Monitoring Server)

Table 7 on page 12 contains a list of the procedures for collecting and viewing
historical data and a cross-reference to where you can find information about each
procedure.

Chapter 3. How to use the Monitoring Agent for Linux OS 11

 IBM Confidential

Table 7. Collecting and viewing historical data

Procedure Where to find information
Configure and start collecting short-term IBM Tivoli Monitoring User’s Guide:
data (24 hours). ″Historical reporting″ (in ″Table and chart
views″ chapter)
Configure and start collecting longer-term
data (more than 24 hours). IBM Tivoli Monitoring Administrator’s Guide
View historical data in the Tivoli Enterprise
Portal. “Disk capacity planning for historical data”
on page 47
Create reports from historical data using
third-party reporting tools.
Filter out unwanted data to see specific
areas of interest.

12 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 4. Workspaces reference

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

About workspaces
A workspace is the working area of the Tivoli Enterprise Portal application
window. At the left of the workspace is a Navigator that you use to select the
workspace you want to see.

As you select items in the Navigator, the workspace presents views pertinent to
your selection. Each workspace has at least one view. Some views have links to
workspaces. Every workspace has a set of properties associated with it.

This monitoring agent provides predefined workspaces. You cannot modify or

delete the predefined workspaces, but you can create new workspaces by editing
them and saving the changes with a different name.

More information about workspaces

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

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

Predefined workspaces
The Monitoring Agent for Linux OS provides the following predefined workspaces:
v Capacity Usage Information
– Capacity Usage Information
– Virtual Memory Usage Trends
– CPU Averages
v Disk Usage
– Disk Usage
v Network
– Network
– Sockets Information
– NFS Statistics
– RPC Statistics
v Process
– Process
– Process User Information
v System Information
– System Information

© Copyright IBM Corp. 2005 13

 IBM Confidential

– Disk IO Extended Rate

– Disk IO Rate
– Virtual Memory Statistics
– System Configuration
v Users
– Users

The remaining sections of this chapter contain descriptions of each of these

predefined workspaces, which are organized alphabetically within the group.

Capacity Usage Information group

The Capacity Usage Information group has the following associated workspaces:
v Capacity Usage Information (default workspace)
v Virtual Memory Usage Trends workspace
v CPU Averages workspace

Capacity Usage Information workspace

The Capacity Usage Information workspace reflects the health of your system by
providing CPU, disk, and swap space usage statistics.

The Capacity Usage Information workspace is comprised of three views:

v Disk Space Usage (bar chart)
v Disk Usage Averages (bar chart)
v CPU Usage Trends (table view)

The Disk Space Usage view displays the current percentage of space used on the
disk, and the percentage of space available. The Disk Usage Averages view
displays the rate of disk usage (in bytes per hour) and amount of time until that
disk is full, based on current rate (or moving average or low water mark). The
CPU Usage Trends displays the system’s trends in disk usage, such as the space
used and available, high water mark information, moving average, and other
information in table form. Dramatic changes in the disk usage rate ″near capacity″
readings in the Days Until Full Disk column might require administrative
intervention. Based on the information that this workspace provides, you can make
changes, set up situations, and verify that the changes are improving performance.

Use the Capacity Usage Information workspace to determine how soon the
monitored system will reach its storage capacity. To determine disk usage, review
the Days until Full Disk at Current Rate and Days Until Full Disk columns. These
columns indicated the number of days until the disk is full. To determine swap
space usage, review the information in the Swap Space Usage Trends in the Virtual
Memory Usage Trends workspace. The information in that Swap Space Usage
Trends view indicate the predicted number of days until the swap space is
completely used.

CPU Averages workspace

The CPU Averages workspace shows the average CPU usage and shows trends
that might indicate whether the usage is increasing. The workspace is comprised of
three views:
v Current Overall CPU Usage (bar chart)
v CPU Averages (CPU usage trends) (bar chart)
v CPU Usage Trends (table view)

14 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

The Current Overall CPU Usage chart shows the current CPU usage as percentages
by category: user CPU, user nice, system CPU, idle CPU, and I/O wait. The CPU
Averages chart shows the CPU moving averages over the past hour. The CPU
Usage Trends table displays details about the CPU usage categories, such as the
current and moving usage averages of user nice CPU, user CPU, system CPU, idle
CPU, and wait CPU. Based on the information that this workspace provides, you
can make changes, set up situations, and verify that the changes are improving
performance.

Use this workspace to determine when it might be beneficial to do a systems

upgrade.

Virtual Memory Usage Trends workspace

The Virtual Memory Usage Trends workspace provides information about current
memory usage and usage and swap space usage trends. This workspace is
comprised of three views:
v Current Virtual Memory Usage (bar chart)
v Virtual Memory Averages (bar chart)
v Swap Space Usage Trends (table view)

The Current Virtual Memory Usage chart shows the current swap space used and
available, and memory used and available. The Virutal Memory Usage chart shows
hourly updates on memory averages. The Swap Space Usage Trends table shows
the moving averages of both the total swap space and swap space used, the swap
space used per hour, and provides an indication as to when the swap space will be
full. It also displays the low water mark for free real memory. Based on the
information that this workspace provides, you can make changes, set up situations,
and verify that the changes are improving performance.

Use the Virtual Memory Usage Trends workspace to determine how soon the
monitored system will reach swap space capacity. The columns in the Swap Space
Usage Trends column indicated the predicted number of days until the swap space
is completely used.

Disk Usage workspace

The Disk Usage workspace reflects the health of storage space within your
monitored systems. This workspace is comprised of four views:
v Space Used Percent (bar chart)
v Inodes Used Percent (bar chart)
v Disk Usage (table view)
v Disk Space (bar chart)

The three charts that comprise this workspace provide “at a glance” percentages of
the space used, percentages of the inodes used, and amounts of disk space used
and available for each monitored disk. The Disk Usage table captures this
information, as well as mount point and file system data, in tabular form. Based on
the information that this workspace provides, you can make changes, set up
situations, and verify that the changes are improving performance.

The most vital part of a file is the inode – a data structure containing all of the
information that describes the file, including file size, permissions, location on disk,
owners, groups, filetype, and checksum. The Inodes Used Percent chart reflects the
percent of inode space currently allocated to files for each monitored disk. If the
Inodes Used Percent measure of a disk reaches a critical condition, use the Disk

Chapter 4. Workspaces reference 15

 IBM Confidential

Usage workspace to determine the number of inodes free, the number of inodes
used, and the number of total inodes allocated. The Total Inodes measure helps
you determine the number of inodes you need to add or subtract to optimize
system performance.

Network group
The Network group has the following associated workspaces:
v Network (default workspace)
v Sockets Information
v NFS Statistics
v RPC Statistics

Network workspace
The Network workspace reflects the health of the network components within your
monitored systems. This workspace is comprised of three views:
v Network Errors (bar chart)
v Network Activity (bar chart)
v Network Devices (table view)

The Network Errors chart shows the number of input errors, output errors, and
collisions for the sampling period. The Network Activity chart shows the number
of packets received and transmitted per second. The Network Devices table reflects
your network’s performance based on its transmission, reception, and collision
data. Based on the information that this workspace provides, you can make
changes, set up situations, and verify that the changes are improving performance.

Use the Network Activity chart to gain a sense of throughput, that is, the rate of
packets received and transmitted by the monitored interface. Use the Network
Errors chart to measure the health of this throughput. This chart provides counts of
input and output errors, as well as collision counts for each interface.

NFS Statistics workspace

The NFS Statistics workspace provides statistics on the operations involving the
Network File System (NFS), such as the number and type of calls being made, and
the percentages those types of calls make up in relation to total calls. The views
are:
v Network Errors (bar chart)
v RPC Network Activity (bar chart)
v NFS Statistics (table view)

The Network Errors chart provides information about the input errors, output
errors, and collisions. The RPC Network Activity chart displays information about
RPC calls, including the number of total server calls received, calls rejected, call
authorization failures, invalid client requests, and packets with malformed headers.
It also shows the number of calls retransmitted and the number of times
authentication is refreshed. The NFS Statistics table provides information about
calls, including the number of null calls, setattr calls, root calls, write cache calls,
and much more. Based on the information that this workspace provides, you can
make changes, set up situations, and verify that the changes are improving
performance.

16 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

NFS statistics provide an overview of how your Network File System is

performing and a snapshot of NFS server and client activity. Use this table in
conjunction with the Network tables to help with performance tuning and
monitoring.

RPC Statistics workspace

The RPC Statistics workspace provides statistics on the number and type of remote
procedure calls being made to the server and clients, including statistics on the
number of calls that are not valid or had to be retransmitted. The views are:
v Network Errors (bar chart)
v RPC Network Activity (bar chart)
v RPC Statistics (table view)

The Network Errors chart provides information about the input errors, output
errors, and collisions. The RPC Network Activity chart displays information about
RPC calls, including the number of total server calls received, calls rejected, call
authorization failures, invalid client requests, and packets with malformed headers.
It also shows the number of calls retransmitted and the number of times
authentication is refreshed. The RPC Statistics table provides information about
RPC calls, including the number of server calls rejected, invalid client requests,
packets with malformed headers, and calls retransmitted. Based on the information
that this workspace provides, you can make changes, set up situations, and verify
that the changes are improving performance.

RPC statistics provide an overview of how your Network File System is

performing and a snapshot of NFS server and client activity. Use this table in
conjunction with the Network tables to help with performance tuning and
monitoring.

Sockets Information workspace

The Sockets Information workspace reflects the health of the socket connections
within your monitored systems. This workspace is comprised of four views:
v Sockets Used by Protocol (bar chart)
v Network Activity (bar chart)
v Socket Services Information (table view)

The Sockets Used by Protocol chart shows a count of the sockets currently in use
and the high water mark for each protocol during the sampling period. The
Network Activity chart shows the number of packets received and transmitted per
second. The Socket Services Information table provides a detailed perspective of
each socket that you are monitoring. Based on the information that this workspace
provides, you can make changes, set up situations, and verify that the changes are
improving performance.

A socket represents a single connection between exactly two pieces of software.

Socket interfaces can be divided into three categories: stream, datagram, and raw.
Libraries implementing sockets for Internet Protocol use TCP for streams, UDP for
datagrams, and IP itself for raw sockets. The Sockets Used by Protocol chart
reflects the current usage of these three protocols, as well as the high water mark
for each.

Process group
The Process group has the following associated workspaces:
v Process (default workspace)

Chapter 4. Workspaces reference 17

 IBM Confidential

v Process user information (a linked workspace)

Process workspace
The Process workspace reflects the health of specific processes within your
monitored systems. This workspace includes three views:
v Process CPU Percent Usage (bar chart)
v Process + Child CPU Percent Usage (bar chart)
v Process Information Detail (table view)

The Process CPU Percent Usage chart displays the percentage of CPU time spent
in kernel mode and spent in user mode by process. The Process + Child CPU
Percent Usage chart displays the cumulative percentage of CPU time spent in
kernel mode and spent in user mode. The Process Information Detail table lists in
tabular form a wide range of process characteristics such as data set size, kernel
scheduling priority, the number of pages of memory, and the number of page
faults. Based on the information that this workspace provides, you can make
changes, set up situations, and verify that the changes are improving performance.

You might encounter a runaway process that steals so many CPU cycles that the
monitored system slows down. Use the Process Information Detail table view to
identify (by Process ID) and quantify (by page count) the specific process. If the
process is out of control, you might want to kill it.

A related workspace, the Process User Information workspace, can be accessed by

clinking the link icon in the Process Information Detail table.

Process User Information workspace

The Process User Information workspace identifies process owners of your
monitored Linux system and details their usage. This workspace is comprised of
three views:
v Process CPU Percent Usage (bar chart)
v Process + Child CPU Percent Usage (bar chart)
v Process User Information (table view)

The Process CPU Percent Usage chart displays the percent of CPU time spent in
kernel mode and spent in user mode by process. The Process + Child CPU Percent
Usage chart displays the cumulative percent of CPU time spent in kernel mode
and spent in user mode. The Process User Information table provides in tablular
form the names of effective groups, file system groups, real groups, and saved
groups for your monitored systems. Based on the information that this workspace
provides, you can make changes, set up situations, and verify that the changes are
improving performance.

The Process User Information workspace complements the Process workspace. You
can link from a specific process in order to view the Process User Information table
view. This table view identifies, in detail, the owner of the process.

System Information group

The System Information group has the following related workspaces:
v System Information (default workspace)
v Disk IO Extended Rate
v Disk IO Rate
v Virtual Memory Statistics

18 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

v System Configuration

Disk IO Extended Rate workspace

The Disk IO Extended Rate workspace provides detailed input/output statistics
and calculations, including the queue length and size in sectors of read and write
requests, the rate of those requests, and wait times associated with requests. This
workspace is comprised of two views:
v Disk Service Time (bar chart)
v Disk Activity (bar chart)
v Disk IO Extended Rate (table view)

The Disk Service Time chart shows the average disk service time in milliseconds.
The Disk Activity chart shows the read sectors and write sectors per second. The
Disk IO Extended Rate table details the I/O data and calculated values associated
with disk activity. Based on the information that this workspace provides, you can
make changes, set up situations, and verify that the changes are improving
performance.

Note: The attributes associated with this workspace are only available for systems
with a 2.4 (or higher) kernel.

The Disk IO Extended Rate workspace complements the Disk IO Rate workspace.
Use this workspace to explore the calculated rates associated with disk
input/output activity.

Disk IO Rate workspace

The Disk IO Rate workspace provides input/output statistics, including the
transfer rates, block read rates, and block write rates of your monitored systems.
This workspace is comprised of three views:
v Disk IO Rate (bar chart)
v Disk IO Rate (table view)
v Disk Space Usage (bar chart)

The Disk IO Rate chart provides “at a glance” rate details associated with disk
reads, writes, and transfers. The Disk IO Rate table includes transfer rates, block
read rates, and block write rates for your monitored systems. The Disk Space
Usage displays the available and used space in megabytes. Based on the
information that this workspace provides, you can make changes, set up situations,
and verify that the changes are improving performance.

Note: The attributes associated with this workspace are only available for systems
with a 2.4 (or higher) kernel.

Use the Disk IO Rate workspace to determine the transfers (input/output requests)
per second that are issued to a device. For additional information about
input/output characteristics, see the Disk IO Extended Rate workspace.

System Configuration workspace

The System Configuration workspace displays information about CPU usage, the
processor’s configuration, and operating system level. It contains three views:
v CPU Usage (bar chart)
v Processor Configuration Information (table view)
v OS Version Information (table view)

Chapter 4. Workspaces reference 19

 IBM Confidential

The CPU Usage chart shows the percentages of CPU usage, by user CPU, user
nice, system, and idle categories. The Processor Configuration Information table
lists the processor ID, its cache size, clock speed, and manufacturing information
such as the model name and number. The OS Version Information table shows the
operating system name, OS vendor information, and version information.

Use this workspace to understand the details of your system configuration.

System Information workspace

The System Information workspace reflects the health of your monitored systems
by displaying data associated with CPU usage, system loads, and process creation.
This workspace is comprised of five views:
v System Load (bar chart)
v Paging Rates (bar chart)
v CPU Usage (bar chart)
v System Statistics (table view)
v Virtual Memory Statistics (bar chart)

The System Load chart depicts the load on your monitored system’s processor
during the previous one, five, and fifteen minutes. The Paging Rates chart shows
the rate at which paging is occurring. The CPU Usage bar chart shows the
aggregate or average CPU usage for a multiprocessor system. An additional
column is displayed for a dual processor system (CPU 0 and CPU1). The System
Statistics table lists in tabular form the source data of these charts and gauge. The
Virtual Memory Statistics chart depicts the current usage and availability of a
variety of memory categories (buffered, cached, shared, and swapped). Based on
the information that this workspace provides, you can make changes, set up
situations, and verify that the changes are improving performance.

A load average is a simple measure of how much work a computer is doing. The
higher the number of processes over a given period of time, the higher the load
average. A load average of one, on most systems, indicates the capacity of one
processor. (On a two-processor system, a load average of two indicates capacity.) In
reality, however, CPU power is not typically the limiting factor for most
applications. A load of two to four times the number of processors is reasonable.
Use the System Load chart to review system load measured during the last one,
five, and fifteen minute intervals.

Virtual Memory Statistics workspace

The Virtual Memory Statistics workspace provides a snapshot of your monitored
systems memory usage. This workspace is comprised of four views:
v Context Switches Percent Change (needle gauge)
v Context Switches Per Second (needle gauge)
v Virtual Memory Information (table view)
v Virtual Memory Statistics (bar chart)

The Context Switches Percent Change gauge reflects the percent change in the
number of context switches per second. The Context Switches Per Sec gauge shows
the number of context switches per second. The Virtual Memory Information table
presents the Virtual Memory Statistics chart information in tabular form. The
Virtual Memory Statistics chart depicts the current usage and availability of a
variety of memory categories (buffered, cached, shared, and swapped). Based on
the information that this workspace provides, you can make changes, set up
situations, and verify that the changes are improving performance.

20 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

The Virtual Memory Statistics chart displays the current usage and availability of
system memory. Of particular interest is the availability of unused swap space
(swap space free) and memory space (memory free). When these measures
approach critical conditions, review the processes to identify those that are
“hogging” memory.

Users workspace
The Users workspace identifies logged in users. This workspace is comprised of
three views:
v Process User Information (table view)
v User Login Information (table view)
v Total User Logins (needle gauge)

The Process User Information table provides in tabular form the names of effective
groups, file system groups, real groups, and saved groups for your monitored
systems. The User Login Information table lists users, their login time, and their
idle time. The Total User Logins gauge displays the number of users logged into
the monitored system during the monitoring period. Based on the information that
this workspace provides, you can make changes, set up situations, and verify that
the changes are improving performance.

The Users workspace provides login information on the current users, including
the elapsed amount of time since they issued commands. In addition, this
workspace provides links to the Process workspace and the Process User
Information workspace. This linking allows you to monitor/troubleshoot the
processes of specific users.

Chapter 4. Workspaces reference 21

 IBM Confidential

22 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 5. Attributes reference

This chapter contains information about the following topics:
v Overview of attributes
v References for detailed information about attributes
v Descriptions of the attributes for each attribute group included in this
monitoring agent
v Disk space requirements for historical data

About attributes
Attributes are the application properties being measured and reported by the
Monitoring Agent for Linux OS, such as the amount of memory usage or the
message ID. Some agents have fewer than 100 attributes, while others have over
1000.

Attributes are organized into groups according to their purpose. The attributes in a
group can be used in the following two ways:
v Chart or table views
Attributes are displayed in chart and table views. The chart and table views use
queries to specify which attribute values to request from a monitoring agent.
You use the Query editor to create a new query, modify an existing query, or
apply filters and set styles to define the content and appearance of a view based
on an existing query.
v Situations
You use attributes to create situations that monitor the state of your operating
system, database, or application. A situation describes a condition you want to
test. When you start a situation, the Tivoli Enterprise Portal compares the values
you have assigned to the situation attributes with the values collected by the
Monitoring Agent for Linux OS and registers an event if the condition is met.
You are alerted to events by indicator icons that appear in the Navigator.

Some of the attributes in this chapter are listed twice, with the second attribute
having a ″(Unicode)″ designation after the attribute name. These Unicode attributes
were created to provide access to globalized data. Use the globalized attribute
names because this is where the monitoring agent is putting the data. If you were
using a previous Candle® OMEGAMON® release of this monitoring agent, you
must run the Application Migration Tool to create globalized attributes for your
customized queries, situations, and policies. See the IBM Tivoli Monitoring
Installation and Setup Guide for more information.

More information about attributes

For more information about using attributes and attribute groups, see the IBM
Tivoli 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, refer to the Attribute
groups and attributes section in this chapter.

© Copyright IBM Corp. 2005 23

 IBM Confidential

Attribute groups and attributes for the Monitoring Agent for Linux OS
This monitoring agent contains the following attribute groups:
v CPU
v CPU Averages
v CPU Config
v Disk
v Disk I/O
v Disk Usage Trends
v I/O Ext
v Network
v NFS Statistics
v OS Config
v Process
v Process User Info
v RPC Statistics
v Sockets Detail
v Sockets Status
v Swap Rate
v System Statistics
v User Login
v VM Stats (Memory)

The following sections contain descriptions of these attribute groups, which are
listed alphabetically. Each description contains a list of attributes in the attribute
group.

CPU attributes
Use the CPU attributes to monitor processor characteristics such as idle time,
system CPU time, and user CPU time.

Busy CPU The percentage of time the CPU was busy. Valid entry is an integer.

CPU ID The processor ID. Valid entry is an integer in the range 0 to 999. Use this
attribute to determine the processor ID. In a symmetrical multiprocessor system
(SMP) with more than one processor, the CPU report shows CPU ID as ″aggregate″
on the first row. This means the data row return aggregated CPU statistics.

Idle CPU Percentage of idle CPU time during the sampling period. Valid entry is
an integer in the range 0 to 100. Use this attribute to determine how efficiently the
entire system or each processor of the SMP system is operating. The Idle CPU
value should be low if the system load is heavy, and high if the system load is
light. If the system load is heavy and the Idle CPU value is high, an I/O problem
might exist. If the Idle CPU value is small, or zero, and the User percentage is
larger (greater than 30%), the system might be compute-bound or in a loop.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM® workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

24 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

System CPU Percentage of system CPU time during the sampling period. Valid
entry is an integer in the range 0 to 100. Use this attribute to determine the
percentage of system or per processor CPU time devoted to executing Linux
system kernel code. System CPU time includes time spent executing system calls
and performing administrative functions.

System Name Name of the host system. Valid entry is an alphanumeric text string
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

User CPU Percentage of user CPU time during the sampling period. Valid entry is
an integer in the range 0 to 100. Use this attribute to determine the percentage of
system or per processor CPU time devoted to user processes. User CPU time
includes time spent executing both user program and library functions. It does not
include CPU time spent executing system calls. The ratio between user and system
CPU time varies, depending on the kinds of programs executing. If user CPU is
extremely high and adversely affecting system performance, you might want to
determine which user programs are preventing the CPU from functioning at its
normal speed.

User Nice CPU Percentage of user nice CPU time during the sampling period.
Valid entry is an integer in the range 0 to 100.

User Sys Pct Of the total CPU time, the percentage consumed by users. Valid entry
is an integer in the range of 0 to 100.

Wait IO The percentage of time the CPU was in a wait input/output state. Valid
entry is an integer in the range of 0 to 100.

CPU Averages attributes

Use the CPU Averages attributes to monitor CPU usage, System CPU time, idle
CPU time, user CPU time, and user nice CPU time characteristics.

CPU Usage Current Average The current average of CPU usage, expressed as a
percentage. Valid entry is an integer between 0 and 100, such as 85 for 85%.

CPU Usage Moving Average The moving average of CPU usage, expressed as a
percentage. Valid entry is an integer between 0 and 100.

Days to CPU Upgrade The number of days until CPU Usage Moving average hits
100% rate. Valid entry is an integer.

Idle CPU Current Average The current average of the system’s idle CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

Idle CPU Moving Average The moving average of the system’s idle CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Chapter 5. Attributes reference 25

 IBM Confidential

System CPU Current Average The current average of the system CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

System CPU Moving Average The moving average of the system CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

User CPU Current Average The current average of the user CPU time, expressed
as a percentage. Valid enty is an integer between 0 and 100.

User CPU Moving Average The moving average of the user CPU time, expressed
as a percentage. Valid entry is an integer between 0 and 100.

User Nice CPU Current Average The current average of the user nice CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

User Nice CPU Moving Average The moving average of the user nice CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

Wait CPU Current Average The current average of the wait CPU time, expressed
as a percentage. Valid entry is an integer between 0 and 100.

Wait CPU Moving Average The moving current average of the wait CPU time,
expressed as a percentage. Valid entry is an integer between 0 and 100.

CPU Config attributes

Use CPU Config attributes to obtain information about the Linux CPU
configuration, such as the CPU model, family, and cache size.

Cache Size The size of the processor cache in kilobytes. Valid entry is an integer.

Clock Speed The speed of the processor clock in megahertz. Valid entry is an
integer.

CPU Family The family number of the processor. Valid entry is an integer.

CPU Model The model number of the processor. Valid entry is an integer.

CPU ID The identification number of the processor. Valid entry is an integer.

Model Name The model name of the processor. Valid entry is an alphanumeric
text string with a maximum length of 128 characters.

System name The name of the host system. Valid entry is an alphanumeric text
string with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

26 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Vendor ID The identification of the processor’s vendor or manufacturer. Valid

entry is an alphanumeric text string with a maximum length of 64 characters.

Disk attributes
Use Disk attributes to monitor disk characteristics such as inode size, inodes used,
mount point, and space available.

Disk Name The name of the physical disk partition where the file system is
mounted. This is the physical location of the disk. Valid entry is an alphanumeric
text string, with a maximum length of 32 characters.

FS Type The file system type, such as hsfs, nfs, tmpfs, and ufs. Valid entries are up
to eight letters or numbers.

Inodes Free The number of inodes currently available on your file system. Use this
attribute to avoid a pending crisis. Corrective action can include freeing up
unneeded space or deleting temporary files. If the value for Inodes Free is less than
100, this is a critical condition. Notify your system administrator immediately.

Inodes Used The number of inodes currently allocated to files on the file system.
This value equals the Total Inodes value minus the Inodes Free value.

Inodes Used Percent The percentage of inodes currently allocated to files,

calculated by dividing the Inodes Used value by the Total Inodes value. Valid
entries: integers between 0 and 100, such as 85 for 85%.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Mount Point The path name of the directory to which a file system is mounted.
This is the virtual name for the directory. Valid entry is a string up to 256
characters representing a directory path.

Mount Point (Unicode) The path name of the directory to which a file system is
mounted. This is the virtual name for the directory. Valid entry is a string up to
256 bytes representing a directory path. This attribute is globalized.

Size The total size of a file system, expressed in megabytes. For example, 1000
represents one gigabyte. Valid entry is an integer of up to 99999999.

Space Available The amount of unused space currently available to

non-superusers on a file system, expressed in megabytes. For example, 40000
represents 40 megabytes. Valid entry is an integer of up to 99999999.

Space Used The amount of disk space currently in use on a file system, expressed
in megabytes. Valid entries For example, 5000 represents 5 gigabytes. Valid entry is
an integer of up to 99999999.

Space Used Percent The space currently used on the file system, expressed as a
percentage of the sum of used and available space. The Space Used Percent reflects

Chapter 5. Attributes reference 27

 IBM Confidential

the percent of disk space which is available to non-superusers. A high value in this
column alerts you to critical disk space conditions. Valid entries: integers between
0 and 100, such as 80 for 80%.

System Name The host name of a monitored system. Valid entry is an

alphanumeric text string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Total Inodes The number of inodes allocated on a file system. Valid entry is an
integer. For example, a value of 163817 indicates that the number of inodes
allocated is 163,817.

Use this attribute when a file system needs additional or fewer inodes assigned to
it. Viewing the current number of inodes assigned helps you determine the
number of inodes you need to add or subtract to optimize performance in your
system.

Disk I/O attributes

Use Disk I/O attributes to monitor disk input/output characteristics, including
transfer rates, block read rates, and block write rates.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Blk Rds per sec Indicates the amount of data read from the drive expressed in a
number of blocks per second. A block is of indeterminate size. Valid entry is an
integer.

Blk wrtn per sec Indicates the amount of data written to the drive expressed in a
number of blocks per second. A block is of indeterminate size. Valid entry is an
integer.

Blks read The total number of blocks read. Valid entry is an integer.

Blks wrtn The total number of blocks written. Valid entry is an integer.

Dev Major The major number of the device. Valid entry is an integer.

Dev Minor The distinctive minor number for device. Valid entry is an integer.

Dev Name The name of the device as it appears under the dev subdirectory.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

28 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Transfers per sec Indicates the number of transfers per second that were issued to
the device. A transfer is an I/O request to the device. Multiple logical requests can
be combined into a single I/O request to the device. A transfer is of indeterminate
size. Valid entry is an integer.

Disk Usage Trends attributes

Use Disk Usage Trends attributes to monitor disk usage characteristics, such as
high water/low water usage rates and days until the disk is full.

Days Full Disk Curr The number of days until the disk is full based on the
current rate of disk usage. Valid entry is an integer. Note: -1 indicates N/A.

Days Full Disk Peak The number of days until the disk is full based on the peak
rate of disk usage. Valid entry is an integer. Note: -1 indicates N/A.

Days Until Full Disk The number of days until the disk is full based on the
moving average rate of disk usage. Valid entry is an integer. Note: -1 indicates
N/A.

Disk Name The name of the physical disk partition where the file system is
mounted. This is the physical location of the disk. Valid entry is an alphanumeric
text string, with a maximum length of 32 characters.

Disk Usage Moving Average The bytes per hour of disk usage averaged over all
previous samples. Valid entry is an integer.

Disk Usage Rate The bytes per hour of disk usage over the last sample period.
Valid entry is an integer.

Highwater DU Rate The bytes per hour rate that represents the high water mark
of disk usage. Valid entry is an integer.

Highwater Time The date and time that the disk usage reaches a high water mark.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Low Water Full Disk Curr The number of days until the disk is full based on the
disk usage rate that represents the low water mark. Valid entry is an integer.

Space Available The amount of unused space currently available to

non-superusers on a file system, expressed in megabytes. For example, 40,000
represents 40 megabytes. Valid entry is an integer.

This disk space does not include any space which is reserved for superuser. A low
value in this column, relative to the disk size, alerts you to critical disk space
conditions.

If this value is low for one or more file systems, relative to the disk size, you might
need to evaluate reconfiguring the file system to distribute the files more evenly
across disks.

Chapter 5. Attributes reference 29

 IBM Confidential

Space Used The amount of disk space currently in use on a file system, expressed
in megabytes. For example, 5000 represents five megabytes. Valid entry is an
integer.

System Name The host name of a monitored system. Valid entry is an

alphanumeric text string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

I/O Ext attributes

Use I/O Ext attributes to monitor a wide variety of disk input/output
characteristics, including read request rates, write request rates, and service time
measures.

Note: These attributes are only available for systems with a 2.4 (or higher) kernel.

Avg req queue length The average queue length of the requests that were issued
to the device. Valid entry is an integer.

Avg req size The average size (in sectors) of the requests that were issued to the
device. Valid entry is an integer.

Avg svc time The average service time (in milliseconds) for I/O requests that were
issued to the device. Valid entry is an integer.

Avg wait time The average time (in milliseconds) for I/O requests issued to the
device to be served. Valid entry is an integer.

Cpu Util Percentage of CPU time during which I/O requests were issued to the
device. Valid entry is an integer.

Device Name Name of the device as appears under the dev subdirectory. Valid
entry is an alphanumeric text string, with a maximum length of 64 characters.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Read req per sec The number of read requests that were issued, per second, to the
device. Valid entry is an integer.

Read reqm per sec The number of read requests merged, per second, that were
issued to the device. Valid entry is an integer.

Read sect per sec The number of sectors read, per second, from the device. Valid
entry is an integer.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

30 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Write req per sec The number of write requests that were issued, per second, to
the device. Valid entry is an integer.

Write reqm per sec The number of write requests merged that were issued, per
second, to the device. Valid entry is an integer.

Write sect per sec The number of sectors written to the device, per second. Valid
entry is an integer.

Network attributes
Use Network attributes to monitor information about what is happening in the
network, such as the frequency of collisions, I/O errors, buffer overruns, and
carrier losses. Many of these attributes can be used to identify the completeness of
network transmissions.

Bytes Received Per Second The number of bytes received per second by the
interface. Valid entry is an integer in the range 0 to 2147483647.

Bytes Transmitted Per Second The number of bytes received per second by the
interface. Valid entry is an integer in the range 0 to 2147483647.

Carrier Losses The number of carrier losses that occurred in the interface. Valid
entry is an integer.

Collision Percent Of the total number of packets transmitted in this sample period,
the percentage involved in a collision. Valid entry is an integer.

Collision rate The number of times a packet collided with another packet per
minute. Valid entry is an integer.

Collisions The number of times during the sampling period that a packet
transmitted by the network interface collided with another packet. This occurs
when another interface on the same local network transmits a packet at nearly the
same time. Valid entry is an integer in the range 0 to 100. Use this attribute to
determine if a network interface has an unacceptable number of packet collisions.
Packet collisions cause the interface to retransmit the packet. With this increased
traffic, the likelihood of future collisions increases. This can result in a steady
increase of network traffic to critical levels.

Input Errors The number of packets received with errors in the interface. Valid
entry is an integer.

Input Error rate The number of packets with errors received per minute by the
interface. Valid entry is an integer.

Input FIFO Buffer Overruns The number of input FIFO buffer overruns that
occurred during the sampling period. Valid entry is an integer.

Input Packets Dropped The number of input packets dropped by the device
driver. Valid entry is an integer.

Interface DNS Name The Dynamic Name Server (DNS) entry associated with the
IP address of the network interface. Valid entry is an alphanumeric text string,

Chapter 5. Attributes reference 31

 IBM Confidential

with a maximum length of 32 characters. Example: www.company.com indicates

that the DNS will resolve the name www.company.com to mean the IP address for
the interface.

Interface IP Address The Internet Protocol (IP) address of the network interface. A
gateway component will have more than one interface, each with a separate
address. Valid entries: Internet protocol addresses in the form a.b.c.d. where a, b, c,
and d are integers in the range 0 to 255. Example: 197.128.55.55 indicates the
network interface uses the IP address 197.128.55.55.

Interface Status This attribute indicates if a network interface is currently

available. Valid entries for each Network interface are as shown:
UP Indicates the interface is in service
DOWN
Indicates the interface is not in service

These values are case-sensitive.

KBytes Received Count The number of kilobytes received since the network
interface was configured. Valid entry is an integer in the range 0 to 2147483647.
Example: If a low number of packets are being received, data traffic might need to
be rerouted.

KBytes Transmitted Count The number of kilobytes transmitted by an interface

since boot time. Valid entry is an integer in the range 0 to 2147483647. Example: A
high value might indicate an overloaded interface. A low value might indicate a
device that is not being used much, which can carry an additional load, if required.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Network Interface Name Identifies the network interface adapter. Valid entries are
alphanumeric text strings comprised of ″Interface Name, Unit Number″ where:
v The name is a two-character representation of the adapter, based on the
hardware, operating system, and installation procedure.
v The unit represents the physical adapter number installed in the system with a
typical range 0 to 7.

Output Error rate The number of packet transmission errors per minute during the
monitoring interval. Valid entry is an integer.

Output FIFO Buffer Overruns The number of output FIFO buffer overruns that
occurred during the sampling period. Valid entry is an integer.

Output Packets Dropped The number of output packets dropped by the device
driver. Valid entry is an integer.

Packet Framing Errors The number of packet framing errors that occurred in the
interface. Valid entry is an integer.

32 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Packets Received Count The number of packets received by the interface during
the sampling period. Valid entry is an integer in the range 0 to 99999999.

Packets Received per sec The number of packets received per second by the
interface. Valid entry is an integer in the range 0 to 2147483647.

Packets Transmitted The number of packets transmitted by the interface during

the sampling period. Valid entry is an integer in the range 0 to 99999999.

Packets Transmitted per sec The number of packets transmitted per second by the
interface. Valid entry is an integer in the range 0 to 2147483647.

System Name The host name of a monitored system. Valid entry is an

alphanumeric text string, with a maximum length of 64 characters. Host names
vary from system to system. Check with your system administrator for a list of all
host names on your system.

Timestamp The date and time the agent collects information as set on the
monitored system.

Total Error Percent Of the total number of packets received and transmitted, the
percentage that were in error during this sample period. Valid entry is an integer.

Transmission Unit Maximum The maximum packet size (in bytes) for the
specified network interface. This is a fixed value. Valid entry is an integer in the
range 0 to 99999999. Use this attribute to determine the minimum, maximum or
average packet size used by a network interface. This information can help you
determine the size used by a network interface.

This information can help you determine the data transfer capabilities of various
network interfaces, and alleviate bottlenecks by rerouting traffic from devices that
appear to be overloaded, to other network interfaces that can handle additional
data traffic.

NFS Statistics attributes

Use NFS Statistics to monitor characteristics of Network File System (NFS) such as
the number of calls, lookups, and operations.

Access Pct Of the total number of calls made to the NFS server, the percentage that
were access calls. Valid entry is an integer.

File System Info Pct Of the total number of calls made to the NFS server, the
percentage that were calls to obtain information about the file system. Valid entry
is an integer.

File System Statistics Calls Pct Of the total number of calls made to the NFS
server, the percentage that involved a request for file system statistics. Valid entry
is an integer.

Link Calls Pct Of the total number of calls made to the NFS server, the percentage
that were link calls. Valid entry is an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be

Chapter 5. Attributes reference 33

 IBM Confidential

empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Location The location of the origin of the call in the Network File System. Valid
entry is an integer. A value of 1 represents the server, a value of 2 represents the
client.

Make Node Calls Pct Of the total number of calls made to the NFS server, the
percentage that were make node (mknod) calls. Valid entry is an integer.

NFS Access The number of access calls made to the NFS server. Valid entry is an
integer.

NFS Commit The number of file commit calls made to the NFS server. Valid entry
is an integer.

NFS Commit Pct Of the total number of calls made to the NFS server, the
percentage that were file commit calls. Valid entry is an integer.

NFS File Creates The number of file create calls made to the NFS server. Valid
entry is an integer.

NFS File Creates Pct Of the total number of calls made to the NFS server, the
percentage that contained file creation operations. Valid entry is an integer in the
range of 0 to 100.

NFS File System Info The number of file system information calls made to the
NFS server. Valid entry is an integer.

NFS File System Statistics Calls The number of calls made to the NFS server
which requested statistics of the file system. Valid entry is an integer.

NFS Get Attribute Calls The number of calls made to the NFS server which
contained a get attribute (getattr) operation. Valid entry is an integer.

NFS Get Attribute Calls Pct Of the total number of calls made to the NFS server,
the percentage that contained get attribute (getattr) operations. Valid entry is an
integer in the range of 0 to 100.

NFS Link Calls The total number of link calls made to the NFS server. Valid entry
is an integer.

NFS lookups The number of lookups made on the NFS server. Valid entry is an
integer.

NFS lookups Pct Of the total number of calls made to the NFS server, the
percentage that were lookups. Valid entry is an integer.

NFS Make Directory Calls The number of make directory calls made to the NFS
server. Valid entry is an integer.

NFS Make Directory Calls Pct Of the total number of calls made to the NFS
server, the percentage that were make directory calls. Valid entry is an integer.

NFS Make Node Calls The number of make node (mknod) calls made to the NFS
server. Valid entry is an integer.

34 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

NFS Null Calls The number of calls made to the NFS server from NFS clients
which contained no data. Valid entry is an integer in the range of 0 to 100.

NFS Null Call Percentage Of the total number of calls made to the NFS server, the
percentage that contained no data. Valid entry is an integer.

NFS Path Conf Calls The number of calls made to the NFS server that involved
path configuration (pathconf) calls to obtain configuration values for files. Valid
entry is an integer.

NFS Read Calls The number of read calls made to the NFS server. Valid entry is
an integer.

NFS Read Calls Pct Of the total number of calls made to the NFS server, the
percentage that were read calls. Valid entry is an integer.

NFS Read Dir Calls Plus The number of read directory plus (readdirplus) calls
made to the NFS server to return the name, the file ID, attributes, and file handle.
Valid entry is an integer.

NFS Read Directory Calls The number of read directory calls made to the NFS
server. Valid entry is an integer.

NFS Read Link Calls The number of read link (readlink) calls made to the NFS
server. Valid entry is an integer.

NFS Read Link Pct Of the total number of calls made to the NFS server, the
percentage that were read link calls. Valid entry is an integer.

NFS Remove Directory Calls The number of remove directory calls made to the
NFS server. Valid entry is an integer.

NFS Remove File Calls The number of file removal calls made to the NFS server.
Valid entry is an integer.

NFS Remove File Calls Pct Of the total number of calls made to the NFS server,
the percentage that were file removal calls. Valid entry is an integer.

NFS Rename File Calls The number of file rename calls made to the NFS server.
Valid entry is an integer.

NFS root Calls The number of calls made to the NFS server which contained root
calls. Valid entry is an integer.

NFS root Calls Pct Of the total number of calls made to the NFS server, the
percentage that were root calls. Valid entry is an integer.

NFS Set Attribute Calls The number of calls made to the NFS server which
contained a set attribute (setattr) operation. Valid entry is an integer.

NFS Set Attribute Calls Pct Of the total number of calls made to the NFS server,
the percentage that contained a set attribute (setattr) operation. Valid entry is an
integer.

Chapter 5. Attributes reference 35

 IBM Confidential

NFS Symbol Link Calls The total number of symbol link calls made to the NFS
server. Symbolic links are files that act as a pointer to another file or directory.
Valid entry is an integer.

NFS Version The software version associated with the NFS server. Valid entry is
an integer. A value of 2 represents version 2, 3 represents version 3, 4 represents
version 4.

NFS Write Cache Calls The number of write cache calls made to the NFS server.
Valid entry is an integer.

NFS Write Cache Calls Pct Of the total number of calls made to the NFS server,
the percentage that were write cache calls. Valid entry is an integer.

NFS Writes The number of write calls made to the NFS server. Valid entry is an
integer.

NFS Writes Pct Of the total number of calls made to the NFS server, the
percentage that were write calls. Valid entry is an integer.

Path Conf Calls Pct Of the total number of calls made to the NFS server, the
percentage that involved use of the pathconf command to obtain configuration
values for files. Valid entry is an integer.

Read Dir Calls Plus Pct Of the total number of calls made to the NFS server, the
percentage that were read directory plus (readdirplus) calls.

Read Directory Calls Pct Of the total number of calls made to the NFS server, the
percentage that were read directory calls. Valid entry is an integer.

Remove Directory Calls Pct Of the total number of calls made to the NFS server,
the percentage that were remove directory calls. Valid entry is an integer.

Rename File Calls Pct Of the total number of calls made to the NFS server, the
percentage that were file rename calls. Valid entry is an integer.

Symbol Link Calls Pct Of the total number of calls made to the NFS server, the
percentage that were symbol link calls. Valid entry is an integer.

System Name The host name of a monitored system. Valid entry is an

alphanumeric text string, with a maximum length of 64 characters. Example: Host
names vary from system to system. Check with your system administrator for a
list of all host names on your system.

Timestamp The date and time the agent collects information as set on the
monitored system.

OS Config attributes
Use OS Config attributes to obtain information about the Linux operating system
configuration, such as the version of Linux in use and the vendor.

gcc version The version of the GNU Compiler Collection (GCC) used to compile
the kernel. Valid entry is an alphanumeric text string with a maximum of 32
characters.

36 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

OS Name The name of the operating system. Valid entry is an alphanumeric text
string with a maximum of 64 characters.

OS Vendor The name of the operating system’s vendor or manufacturer. Valid

entry is an alphanumeric text string with a maximum of 128 characters.

OS Version The version of the operating system. Valid entry is an alphanumeric

text string with a maximum of 128 characters.

System Name The host name of the system. Valid entry is an alphanumeric text
string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Process attributes
Use Process attributes to monitor process characteristics such as data set size,
kernel scheduling priority, the number of pages of memory, and the number of
page faults.

Data Set Size The size of the data set based on the number of pages. Valid entry is
an integer.

Dirty Pages Pages that have been modified (dirty) in buffer (main memory), but
not yet copied to the cache. Valid entry is an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Nice The standard Linux nice level (-20 represents the highest level). Valid entry is
an integer in the range -20 to 19.

Parent Process ID The identifier for the parent process. Valid entry is an integer.

Priority The kernel scheduling priority (0 represents the highest priority). Valid
entry is an integer between 100 and 0.

Proc CMD Line The process command line string. Valid entry is an alphanumeric
text string, with a maximum length of 256 characters.

Proc CMD Line (Unicode) The process command line string. Valid entry is an
alphanumeric text string, with a maximum length of 512 bytes. This attribute is
globalized.

Proc CPU The ID of the process CPU. Valid entry is an integer.

Proc System CPU The percentage of CPU time spent in kernel mode by process.
Valid entry is an integer between 0 and 100.

Proc User CPU The percentage of CPU time spent in user mode by process. Valid
entry is an integer between 0 and 100.

Chapter 5. Attributes reference 37

 IBM Confidential

Process Command Name The name of the process command. Valid entry is an
alphanumeric text string, with a maximum length of 32 characters.

Process Command Name (Unicode) The name of the process command. Valid
entry is an alphanumeric text string, with a maximum length of 64 bytes. This
attribute is globalized.

Process ID The identifier of the process. Valid entry is an integer.

Resident Set Size The number of pages the process has in real memory. Valid
entry is an integer.

Shared Lib Set Size The number of pages of shared library set (mmap’d) memory.
mmap is a system API that lets you map a file or device into memory. The mapped
pages can be shared so that other processes can access them. Valid entry is an
integer.

Shared Memory The number of pages of shared (mmap’d) memory. mmap is a

system API that lets you map a file or device into memory. The mapped pages can
be shared so that other processes can access them. Valid entry is an integer.

State The state of the process (Sleeping, Disk, Running, Zombie, Trace, Dead, or
N/A). Valid entry is an integer between -1 and 5:
0 Sleeping
1 Disk
2 Running
3 Zombie
4 Trace
5 Dead
-1 N/A

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Text Resident Size The number of pages of text resident (mmap’d) memory. mmap
is a system API that lets you map a file or device into memory. The mapped pages
can be shared so that other processes can access them. Valid entry is an integer.

Threads The number of threads started for this process (valid only on the 2.6
kernel or higher). Valid entry is an integer.

Timestamp The date and time the agent collects information as set on the
monitored system.

Total Busy CPU Pct The percentage of time the CPU is busy, as a summation of
user CPU and system CPU utilization for this process and for children of this
process. Valid entry is an integer between 1 and 100.

Tot Major faults The total number of major page faults (including child processes)
since the start of the process. Valid entry is an integer.

38 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Tot Minor faults The total number of minor page faults (including child processes)
since the start of the process. Valid entry is an integer.

Tot Proc System CPU The percentage of cumulative CPU time spent in kernel
mode by process. Valid entry is an integer between 0 and 100.

Tot Proc User CPU The percentage of cumulative CPU time spent in user mode by
process. Valid entry is an integer between 0 and 100.

Total Size Memory The number of pages that the process has in real memory.
Valid entry is an integer.

User Sys CPU Pct Of the total system CPU usage, the percentage that was user
CPU usage. Valid entry is an integer between 0 and 100.

VM Data The data size (in kilobytes) of the virtual memory. Valid entry is an
integer.

VM Data MB The data size (in megabytes) of the virtual memory. Valid entry is an
integer.

VM Exe Size The executable size (in kilobytes) of the virtual memory. Valid entry
is an integer.

VM Exe Size MB The executable size (in megabytes) of the virtual memory. Valid
entry is an integer.

VM Lib Size The library size (in kilobytes) of the virtual memory. This
measurement represents all pages, including unused. Valid entry is an integer.

VM Lib Size MB The library size (in megabytes) of the virtual memory. This
measurement represents all pages, including unused. Valid entry is an integer.

VM Lock The size (in kilobytes) of locked pages of the virtual memory. Valid entry
is an integer.

VM Lock MB The size (in megabytes) of locked pages of the virtual memory. Valid
entry is an integer.

VM Size The size (in kilobytes) of the virtual memory. Valid entry is an integer.

VM Size MB The size (in megabytes) of the virtual memory. Valid entry is an
integer.

VM Stack The stack size (in kilobytes) of the virtual memory. Valid entry is an
integer.

VM Stack MB The stack size (in megabytes) of the virtual memory. Valid entry is
an integer.

Process User Info attributes

Use Process User Info attributes to monitor characteristics associated with effective
groups, file system groups, real groups, and saved groups.

Chapter 5. Attributes reference 39

 IBM Confidential

Eff group The effective group name. Valid entry is an alphanumeric text string,
with a maximum length of 16 characters.

Eff group (Unicode) The effective group name. Valid entry is an alphanumeric text
string, with a maximum length of 64 bytes. This attribute is globalized.

Eff group ID The identifier of the effective group. Valid entry is an integer.

Eff User ID The identifier of the effective user. Valid entry is an integer.

Eff User name The name of the effective user. Valid entry is an alphanumeric text
string, with a maximum length of 16 characters.

Eff User name (Unicode) The name of the effective user. Valid entry is an
alphanumeric text string, with a maximum length of 64 bytes. This attribute is
globalized.

File Sys Group The name of the file system group. Valid entry is an alphanumeric
text string, with a maximum length of 16 characters.

File Sys Group (Unicode) The name of the file system group. Valid entry is an
alphanumeric text string, with a maximum length of 64 bytes. This attribute is
globalized.

File Sys Group ID The identifier of the file system group. Valid entry is an integer.

FS User ID The identifier of the file system user. Valid entry is an integer.

FS User name The name of the file system user. Valid entry is an alphanumeric
text string, with a maximum length of 16 characters.

FS User name (Unicode) The name of the file system user. Valid entry is an
alphanumeric text string, with a maximum length of 64 bytes. This attribute is
globalized.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Process ID The identifier associated with the process. Valid entry is an integer.

Real Group The name of the real group. Valid entry is an integer.

Real Group (Unicode) The name of the real group. Valid entry is an alphanumeric
text string with a maximum of 64 bytes. This attribute is globalized.

Real Group ID The identifier of the real group. Valid entry is an integer.

Real User ID The identifier of the real user. Valid entry is an integer.

Real User Name The name of the real user. Valid entry is an alphanumeric text
string, with a maximum of 16 characters.

40 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Real User Name (Unicode) The name of the real user. Valid entry is an
alphanumeric text string, with a maximum length of 64 bytes. This attribute is
globalized.

Saved Group The name of the saved group. Valid entry is an alphanumeric text
string, with a maximum length of 16 characters.

Saved Group U The name of the saved group. Valid entry is an alphanumeric text
string, with a maximum length of 64 characters.

Saved Group ID The identifier of the saved group. Valid entry is an integer.

Saved User ID The identifier of the saved user. Valid entry is an integer.

Saved User Name The name of the saved user. Valid entry is an alphanumeric text
string, with a maximum length of 16 characters.

Saved User Name (Unicode) The name of the saved user. Valid entry is an
alphanumeric text string, with a maximum length of 64 bytes. This attribute is
globalized.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

RPC Statistics attributes

Use RPC Statistics to monitor remote procedure call (RPC) characteristics, such as
the number of RPC server calls (including the number of rejected calls), packets
that are not valid, and client calls.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

RPC Client Calls The number of calls to the server made by the server’s clients.
Valid entry is an integer.

RPC Client Calls Retransmitted The number of client calls that needed to be
transmitted again. Valid entry is an integer.

RPC Client Times Authentication Refreshed The number of times the

authentication of a client was refreshed. Valid entry is an integer.

RPC Server Total Calls The total number of calls made to the server (both valid
and not valid). Valid entry is an integer.

RPC Server Calls Rejected The number of calls made to the server, which were
rejected. Valid entry is an integer.

RPC Server Packets Bad Clt The number of packets that were received at the
server, which had client requests that were not valid. Valid entry is an integer.

Chapter 5. Attributes reference 41

 IBM Confidential

RPC Server Packets Bad Auth The number of packets that were received at the
server with authorizations that were not valid. Valid entry is an integer.

RPC Server Packets with Malformed Header The number of packets that were
received at the server with header records that were not properly formatted. Valid
entry is an integer.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Sockets Detail attributes

Use Sockets Detail attributes to monitor characteristics associated with socket
details, including user ID, local and foreign addresses, socket states, and socket
protocols.

Foreign Address The address of the remote end of the socket. Like ″netstat″ *
indicates that the address is unassigned/unavailable. Valid entry is an
alphanumeric text string, with a maximum length of 16 characters.

Foreign Port The number of the foreign port. Valid entry is an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Local Address The address of the local end of the socket, presented as a dotted IP
address. Valid entry is an alphanumeric text string, with a maximum length of 16
characters.

Local Port The local port number. Valid entry is an integer. Note: -1 = N/A.

Local Service The local port number translated to a service name from the
etc/services subdirectory. Valid entry is an alphanumeric text string, with a
maximum length of 64 characters.

Receive Queue The count of bytes not copied by the user program connected to
this socket. Valid entry is an integer. Note: -1 = N/A.

Send Queue The count of bytes not acknowledged by the remote host. Valid entry
is an integer.

Socket Inode The inode used by the socket. Valid entry is an integer.

Socket Owner Name (Unicode) The user name associated with the user ID that
owns or started the socket connection. Valid entry is an alphanumeric text string,
with a maximum length of 64 bytes. This attribute is globalized.

Socket Protocol Indicates the sockets using this protocol. ″Total″ includes UNIX
domain sockets not displayed here. Valid entry is an integer:
0 TCP

42 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

1 UDP
2 RAW
3 UNIX
-1 TOTAL
-2 N/A

Socket State The state of the socket. Valid entry is an integer:

1 ESTABLISHED
2 SYN_SENT
3 SYN_RECV
4 FIN_WAIT1
5 FIN_WAIT2
6 TIME_WAIT
7 CLOSED
8 CLOSED_WAIT
9 LAST_ACK
10 LISTEN
11 CLOSING
12 UNKNOWN

Socket UID The user ID of the owner of the socket. Valid entry is an integer.

System Name The host name of the monitored system. Valid entry is an
alphanumeric text string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Sockets Status attributes

The Sockets Status attributes refer to characteristics associated with the status of
the Linux system sockets, including protocol names and high water marks used by
protocols.

Highest Sockets Used The high water mark of sockets used by this protocol. Valid
entry is an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Socket Protocol Indicates the sockets using this protocol. ″Total″ includes UNIX
domain sockets not displayed here. Valid entry is an integer:
0 TCP
1 UDP

Chapter 5. Attributes reference 43

 IBM Confidential

2 RAW
3 UNIX
4 FRAG
-1 TOTAL
-1 N/A

Sockets in Use Sockets in use by protocol. Valid entry is an integer. Note: -1

indicates N/A.

System Name The host name of the monitored system. Valid entry is an
alphanumeric text string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Swap Rate attributes

Use Swap Rate attributes to monitor swap space characteristics, including usage
rates and ″days till full″ data.

Days to Peak Space Full The minimum number of days until swap space is
completely used (peak rate based). Valid entry is an integer.

Days to Swap Space Full The predicted number of days until swap space is
completely used (moving average). Valid entry is an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Low Free Memory The lowest level that free real memory has reached, expressed
in kilobytes. Valid entry is an integer.

Moving Total Swap Space The moving average of total swap space, expressed in
megabytes. Valid entry is an integer.

Peak Swap Space Used The peak swap space used based on snap shots, expressed
in megabytes. Valid entry is an integer.

Swap Space Used The moving average of swap space used, expressed in
megabytes. Valid entry is an integer.

Swap Usage Rate The swap space usage rate, expressed in bytes per hour. Valid
entry is an integer.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

44 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

System Statistics attributes

Use the System Statistics attributes to monitor characteristics associated with
system performance such as the number of logged in users, the number of
processes per second, and system load statistics.

Ctxt Switches per sec The number of context switches per second. Valid entry is
an integer.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Major Faults per sec The total number of major faults per second. These are page
faults that required loading of pages from the disk. Valid entry is an integer. This
attribute is valid only for systems with a 2.4 (or higher) kernel.

Number of Users The current number of users logged in. Valid entry is an integer.

Pages Faults per sec The total number of pages faults per second (both major and
minor). Valid entry is an integer. This attribute is valid only for systems with a 2.4 (or
higher) kernel.

Pages paged in The total number of pages paged in. Valid entry is an integer.

Pages paged in per sec The total number of pages paged in per second. Valid
entry is an integer.

Pages paged out The total number of pages paged out. Valid entry is an integer.

Pages paged out per sec The total number of pages paged out per second. Valid
entry is an integer.

Pages Swap in per sec The total number of pages swapped in per second. Valid
entry is an integer.

Pages Swapped in The total number of pages swapped in. Valid entry is an
integer.

Pages Swapped out The total number of pages swapped out. Valid entry is an
integer.

Pages Swap out per sec The total number of pages swapped out per second. Valid
entry is an integer.

Pct Change Ctxt Switches The percentage change in the number of context
switches per second. Valid entry is an integer in the range -100 to 100.

Pct Change Processes The percentage change in the number of processes per
second. Valid entry is an integer in the range -100 to 100.

Processes per sec The number of processes created per second. Valid entry is an
integer.

Chapter 5. Attributes reference 45

 IBM Confidential

System Load 1 min The load on the system for the last minute. Valid entry is an
integer in the range 0 to 100.

System Load 5 min The load on the system for the last five minutes. Valid entry is
an integer in the range 0 to 100.

System Load 15 min The load on the system for the last fifteen minutes. Valid
entry is an integer in the range 0 to 100.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

System Uptime The system uptime in number of seconds. Valid entry is an integer.

Timestamp The date and time the agent collects information as set on the
monitored system.

User Login attributes

Use the User Login attributes to monitor user characteristics such as idle time, user
name, location, and login time.

From Hostname The host name associated with the user’s login. Valid entry is an
alphanumeric text string, with a maximum length of 256 characters.

Idle Time The number of minutes that have passed since a user last entered a
command. Valid entry is a numeric value expressed as minutes in the range 0 to
20160. Use this attribute to check idle time.

Line The terminal device type or line to which the user is connected. Valid entry is
an alphanumeric text string, with a maximum length of 16 characters.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Login PID The login ID of the user. Valid entry is an integer.

Login Time The date and time the user logged in.

System Name The host name of the monitored system. Valid entry is an
alphanumeric text string, with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

User Name The full name of a user. Valid entry is an alphanumeric text string,
with a maximum length of 32 characters.

User Name (Unicode) The name of the user logging in to access the system. Valid
entry is a text string up to 64 bytes. This attribute is globalized.

46 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

VM Stats attributes
Use the VM Stats attributes to monitor characteristics such as the size of cached,
free, and shared memory.

Linux VM ID The virtual machine user ID used internally to link the monitoring
agent workspace to a z/VM workspace. Valid entry is an alphanumeric text string
with a maximum length of 32 characters. The contents of this attribute might be
empty depending on the platform the Monitoring Agent for Linux OS is running
on and the availability of dependent products.

Memory Cached The size (in megabytes) of physical memory cached. Valid entry
is an integer.

Memory Free The size (in megabytes) of physical memory free. Valid entry is an
integer.

Memory in Buffers The size (in megabytes) of physical memory in buffers. Valid
entry is an integer.

Memory Used The size (in megabytes) of physical memory used. Valid entry is an
integer.

Shared Memory The size (in megabytes) of physical memory shared. Valid entry is
an integer.

Swap Space Free The size (in megabytes) of swap space free. Valid entry is an
integer.

Swap Space Used The size (in megabytes) of swap space used. Valid entry is an
integer.

System Name Name of the host system. Valid entry is an alphanumeric text string,
with a maximum length of 64 characters.

Timestamp The date and time the agent collects information as set on the
monitored system.

Total Memory The total size (in megabytes) of physical memory. Valid entry is an
integer.

Total Swap Space The total size (in megabytes) of swap space. Valid entry is an
integer.

Disk capacity planning for historical data

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

Calculate expected disk space consumption by multiplying the number of bytes

per instance by the expected number of instances, and then multiplying that
product by the number of samples.Table 8 on page 48 provides the following
information required to calculate disk space for the Monitoring Agent for Linux
OS:

Chapter 5. Attributes reference 47

 IBM Confidential

v DB table name is the table name as it would appear in the warehouse database, if
the attribute group is configured to be written to the warehouse.
v Bytes per instance (agent) is an estimate of the record length for each row or
instance written to the agent disk for historical data collection. This estimate can
be used for agent disk space planning purposes.
v Bytes per instance (warehouse) is an estimate of the record length for detailed
records written to the warehouse database, if the attribute group is configured to
be written to the warehouse. Detailed records are those that have been uploaded
from the agent for long-term historical data collection. This estimate can be used
for warehouse disk space planning purposes.
v Bytes per summarized instance (warehouse) is an estimate of the record length for
aggregate records written to the warehouse database, if the attribute group is
configured to be written to the warehouse. Aggregate records are created by the
Summarization agent for attribute groups that have been configured for
summarization. This estimate can be used for warehouse disk space planning
purposes.
v Expected number of instances is a guideline that can be different for each attribute
group, because it is the number of instances of data that the agent will return for
a given attribute group, and depends upon the application environment that is
being monitored. For example, if your attribute group is monitoring each
processor on your machine and you have a dual processor machine, the number
of instances is 2.
The IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can
be used to estimate the amount of disk space used at the agent and in the
warehouse database for historical data collection of an attribute group.
Table 8. Capacity planning for historical data
Bytes per
Bytes per summarized
Attribute Bytes per instance instance Expected number of
Group DB table name instance (agent) (warehouse) (warehouse) instances
CPU LNXCPU 228 249 665 Multiple, typically 1-4
CPU Averages LNXCPUAVG 324 346 1102 Multiple, typically 1-4
CPU LNXCPUCON 312 335 372 Multiple, typically 1-4
Configuration
Disk LNXDISK 484 514 863 Multiple, typically 2
Disk I/O LNXDSKIO 248 273 493 Multiple, typically 2
Disk Usage LNXDU 204 232 581 Multiple, typically 2
Trends
I/O Ext LNXIOEXT 360 389 987 Multiple, typically 2
Network LNXNET 264 307 890 Multiple, typically 3
NFS Statistics LNXNFS 320 387 1720 Multiple, typically 1-4
OS Config LNXOSCON 440 460 497 Multiple, typically 1
Processes LNXPROC 1268 1324 2588 Multiple, typically 100-1000
Process User LNXPUSR 796 838 875 Multiple, typically about 5
Info
RPC Statistics LNXRPC 152 177 319 Single
Sockets Detail LNXSOCKD 312 341 456 Multiple, typically 10-100
Sockets Status LNXSOCKS 132 152 228 Multiple, typically 10-100

48 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 8. Capacity planning for historical data (continued)

Bytes per
Bytes per summarized
Attribute Bytes per instance instance Expected number of
Group DB table name instance (agent) (warehouse) (warehouse) instances
Swap Rate LNXSWPRT 148 172 326 Single
System LNXSYS 304 340 1106 Single
Statistics
User Login LNXLOGIN 524 548 585 Multiple, typically about 5
VM Statistics LNXVM 264 290 684 Single
(Memory)

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

Chapter 5. Attributes reference 49

 IBM Confidential

50 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 6. Situations reference

This chapter contains an overview of situations, references for detailed information
about situations, and descriptions of the predefined situations included in this
monitoring agent.

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

The IBM Tivoli Monitoring agents that you use to monitor your system
environment are shipped with a set of predefined situations that you can use as-is
or you can create new situations to meet your requirements. Predefined situations
contain attributes that check for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can begin
using the Monitoring Agent for Linux OS. You can examine and, if necessary,
change the conditions or values being monitored by a predefined situation to those
best suited to your enterprise.

Note: The predefined situations provided with this monitoring agent are not
read-only. Do not edit these situations and save over them. Software updates
will write over any of the changes that you make to these situations.
Instead, clone the situations that you want to change to suit your enterprise.

You can display predefined situations and create your own situations using the
Situation editor. The left frame of the Situation editor initially lists the situations
associated with the Navigator item that you selected. When you click a situation
name or create a new situation, the right frame opens with the following tabs:
Formula
Condition being tested
Distribution
List of managed systems (operating systems, subsystems, or applications)
to which the situation can be distributed.
Expert Advice
Comments and instructions to be read in the event workspace
Action
Command to be sent to the system
Until Duration of the situation

More information about situations

The IBM Tivoli Monitoring User’s Guide contains more information about predefined
and custom situations and how to use them to respond to alerts.

For a list of the predefined situations for this monitoring agent and a description
of each situation, refer to the Predefined situations section below and the
information in that section for each individual situation.

© Copyright IBM Corp. 2005 51

 IBM Confidential

Predefined situations
This monitoring agent contains the following predefined situations:

The remaining sections of this chapter contain descriptions of each of these

predefined situations. The situations are organized alphabetically.
v Linux_Fragmented_File_System
v Linux_High_CPU_Overload
v Linux_High_CPU_System
v Linux_High_Packet_Collisions
v Linux_High_RPC_Retransmit
v Linux_High_Zombies
v Linux_Low_Pct_Inodes
v Linux_Low_percent_space
v Linux_Low_Space_Available
v Linux_Network_Status
v Linux_NFS_Buffer_High
v Linux_NFS_Getattr_High
v Linux_NFS_rdlink_high
v Linux_NFS_Read_High
v Linux_NFS_Writes_High
v Linux_Packets_Error
v Linux_Process_High_Cpu
v Linux_Process_stopped
v Linux_RPC_Bad_Calls
v Linux_System_Thrashing

Linux_Fragmented_File_System situation
Monitors the percentage of i-nodes to disk space. An exception condition occurs
when the percentage of i-nodes to disk space used is high, which could indicate
high disk fragmentation on the disk.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Used_Percent LT 85 AND
VALUE Linux_Disk.Inodes_Used_Percent GT 80

Linux_High_CPU_Overload situation
Monitors the percentage of time the processor is busy. An exception condition
occurs when the percentage is extremely high.

This situation has the following formula.

IF VALUE Linux_CPU.Idle_CPU LT 10.0 AND VALUE Linux_CPU.CPU_ID EQ Aggregate

Linux_High_CPU_System situation
Monitors the percentage of processor time that is used for system calls to check for
runaway processes. An exception condition occurs when the percentage is high.

This situation has the following formula.

52 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

IF VALUE Linux_CPU.CPU_ID EQ Aggregate AND VALUE

Linux_CPU.System_CPU GT 80.0

Linux_High_Packet_Collisions situation
Monitors the percentage of packet collisions during data transmission. An
exception condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Network.Collision_Percent GT 10

Linux_High_RPC_Retransmit situation
Monitors the percentage of retransmits because of RPC Server calls. An exception
condition occurs when the percentage is extremely high.

This situation has the following formula.

IF PCTCHANGE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 10

Linux_High_Zombies situation
Monitors the number of processes in zombie state. An exception condition occurs
when the number is high.

This situation has the following formula.

IF VALUE Linux_Process.State EQ Zombie AND COUNT Linux_Process.State GT 20

Linux_Low_Pct_Inodes situation
Monitors the percentage of available i-nodes. An exception condition occurs when
the number is low.

This situation has the following formula.

IF VALUE Linux_Disk.Inodes_Used_Percent GT 80

Linux_Low_percent_space situation
Monitors the percentage of space available on a file system. An exception condition
occurs when the percentage is low.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Available_Percent LT 15

Linux_Low_Space_Available situation
Monitors the available space on a file system. An exception condition occurs when
the amount of space is low.

This situation has the following formula.

IF VALUE Linux_Disk.Space_Available LT 7

Linux_Network_Status situation
Monitors whether the Network Interface Card is up or not. An exception condition
occurs when the network interface card is not up.

This situation has the following formula.

IF VALUE Linux_Network.Interface_Status NE UP

Chapter 6. Situations reference 53

 IBM Confidential

Linux_NFS_Buffer_High situation
Monitors the number of RPC retransmissions with no duplicate
acknowledgements. An exception condition occurs when the number of
retransmissions is high.

This situation has the following formula.

IF VALUE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 60 AND
PCTCHANGE Linux_RPC_Statistics.RPC_Client_Times_Authentication_Refreshed GT 5

Linux_NFS_Getattr_High situation
Monitors the percentage of NFS server calls to read client attributes. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Get_Attribute_Calls_Pct GT 40

Linux_NFS_rdlink_high situation
Monitors the percentage of NFS server calls for read link operations. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Read_Link_Pct GT 10

Linux_NFS_Read_High situation
Monitors the percentage of NFS server calls for read operations. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Read_Calls_Pct GT 30

Linux_NFS_Writes_High situation
Monitors the percentage of NFS server calls for write operations. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_NFS_Statistics.NFS_Writes_Pct GT 15

Linux_Packets_Error situation
Monitors the percentage of network packets in error. An exception condition occurs
when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Network.Total_Error_Percent GT 10

Linux_Process_High_Cpu situation
Monitors the percentage of processor time used by a process. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF VALUE Linux_Process.Busy_CPU_Pct GT 60.0

54 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Linux_Process_stopped situation
Monitors the number of stopped processes on the system. An exception condition
occurs when the number is high.

This situation has the following formula.

IF VALUE Linux_Process.State NE Running AND
VALUE Linux_Process.State NE Sleeping

Linux_RPC_Bad_Calls situation
Monitors the percentage of rejected RPC server or client calls. An exception
condition occurs when the percentage is high.

This situation has the following formula.

IF ( ( VALUE Linux_RPC_Statistics.RPC_Client_Calls_Retransmitted GT 30
) OR ( VALUE Linux_RPC_Statistics.RPC_Server_Calls_Rejected GT 30 ) )

Linux_System_Thrashing situation
Monitors the swap space paging activity on the system. An exception condition
occurs when the activity is extremely high.

This situation has the following formula.

IF ( ( VALUE Linux_System_Statistics.Pages_paged_out_per_sec GT 400.0 )
OR ( *VALUE Linux_System_Statistics.Pages_paged_in_per_sec GT 400.0 ) )

Chapter 6. Situations reference 55

 IBM Confidential

56 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 7. Take Action commands reference

This chapter contains an overview of Take Action commands, references for
detailed information about Take Action commands, and a description of the Take
Actions command included in this monitoring agent.

About Take Action commands

Take Action commands can be run from the desktop or included in a situation or a
policy.

When included in a situation, the command executes when the situation becomes
true. A Take Action command in a situation is also referred to as reflex automation.
When you enable a Take Action command in a situation, you automate a response
to system conditions. For example, you can use a Take Action command to send a
command to restart a process on the managed system or to send a text message to
a cell phone.

Advanced automation uses policies to perform actions, schedule work, and

automate manual tasks. A policy comprises a series of automated steps called
activities that are connected to create a workflow. After an activity is completed,
Tivoli Enterprise Portal receives return code feedback, and advanced automation
logic responds with subsequent activities prescribed by the feedback.

More information about Take Action commands

For more information about working with Take Action commands, see the IBM
Tivoli Monitoring User’s Guide.

Predefined Take Action commands

This monitoring agent contains the following Take Action command:

Sample_kill_Process

The remaining section of this chapter contains a description of this Take Action
command. The following information is provided about the Take Action command:
Description
Which actions the command performs on the system to which it is sent
Arguments
List of arguments, if any, for the Take Action with a short description and
default value for each one
Destination systems
Where the command is to be executed: on the Managed System
(monitoring agent) where the agent resides or on the Managing System
(Tivoli Enterprise Monitoring Server) to which it is connected
Usage notes
Additional relevant notes for using the Take Actions

© Copyright IBM Corp. 2005 57

 IBM Confidential

Sample_kill_Process action
Description
Kills the process named in the parameter supplied and enables you to issue ad-hoc
commands from the Tivoli Enterprise Portal that the Monitoring Agent for Linux
OS will execute on your behalf.

Arguments
Process ID
The Process ID (PID) of the process you would like to kill.

Destination systems
Managed system

Usage notes
The kill command is executed directly by the remote Monitoring Agent for Linux
OS. Because it is easy to kill processes unintentionally, you need to exercise caution
if the monitoring agent is run as superuser (root).

58 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Chapter 8. Policies reference

This chapter contains an overview of policies and references for detailed
information about policies.

About policies
Policies are an advanced automation technique for implementing more complex
workflow strategies than you can create through simple automation.

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

Note: For monitoring agents that provide predefined policies, predefined policies
are not read-only. Do not edit these policies and save over them. Software
updates will write over any of the changes that you make to these policies.
Instead, clone the policies that you want to change to suit your enterprise.

More information about policies

For more information about working with policies, see the IBM Tivoli Monitoring
User’s Guide.

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

For a list of the policies for this monitoring agent and a description of each policy,
refer to the “Predefined policies” section below and the information in that section
for each individual policy.

Predefined policies
There are no predefined policies for this monitoring agent.

© Copyright IBM Corp. 2005 59

 IBM Confidential

60 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Appendix A. IBM Tivoli Enterprise Console event mapping

Specific event mapping is provided for those monitoring agents that support
Distributed Monitoring migration. The specific event mapping creates Distributed
Monitoring events for Distributed Monitoring migrated situations. For a list of
these situations and their related event classes, see Table 9.

Generic event mapping provides useful event class and attribute information for
situations that do not have specific event mapping defined. Each event class
corresponds to an attribute group in the monitoring agent. For a description of the
event slots for each event class, see Table 10 on page 62. For more information
about mapping attribute groups to event classes, see the IBM Tivoli Monitoring
Administrator’s Guide.

BAROC files are found on the Tivoli Enterprise Monitoring Server in the
installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows
systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM
Tivoli Enterprise Console event synchronization provides a collection of
ready-to-use rule sets that you can deploy with minimal configuration. Be sure to
install IBM Tivoli Enterprise Console event synchronization to access the correct
Sentry.baroc, which is automatically included during base configuration of IBM
Tivoli Enterprise Console rules if you indicate that you want to use an existing
rulebase. See the IBM Tivoli Monitoring Installation and Setup Guide for details.
Table 9. Overview of Distributed Monitoring migrated situations
Situation IBM Tivoli Enterprise Console event class
LZ_USInodes* Sentry2_0_inodes
Sentry2_0_inodesused
LZ_USIUsPct* Sentry2_0_inodesusedpct
LZ_USDkUPct* Sentry2_0_diskusedpct
LZ_USDskAva* Sentry2_0_diskavail
LZ_USDskUsd* Sentry2_0_diskused
LZ_USTvDBSp* Sentry2_0_tivdbspace
LZ_USDIORtK* Sentry2_0_diskioratek
LZ_USRCPTmo* Sentry2_0_rpctmout
LZ_USNtInEr* Sentry2_0_netinerr
LZ_USNtInEX* Sentry2_0_netinerrx
LZ_USNetIn* Sentry2_0_netinerr
LZ_USNetInX* Sentry2_0_netinx
LZ_USBadNFS* Sentry2_0_badnfs
LZ_USBadNFS* Sentry2_0_badnfs
LZ_USNetCol* Sentry2_0_netcoll
LZ_USNCPct* Sentry2_0_netcollpct
LZ_USNCPctX* Sentry2_0_netcollpctx
LZ_USNetOEr* Sentry2_0_netouterr
LZ_USNetOEX* Sentry2_0_netouterrx

© Copyright IBM Corp. 2005 61

 IBM Confidential

Table 9. Overview of Distributed Monitoring migrated situations (continued)

Situation IBM Tivoli Enterprise Console event class
LZ_USNetOut* Sentry2_0_netouterr
LZ_USNetOX* Sentry2_0_netoutx
LZ_USBadRPC* Sentry2_0_badrpc
LZ_USSwpAva* Sentry2_0_swapavail
LZ_USCPUIdl* Sentry2_0_cpuidle
LZ_USCPUSys* Sentry2_0_cpusys
LZ_USCPUUsr* Sentry2_0_cpuusr
LZ_USCPUSdu* Sentry2_0_cpusdu
LZ_USCPUSpu* Sentry2_0_cpuspu
LZ_USZombie* Sentry2_0_zombies
LZ_USLdAv15* Sentry2_0_loadavgfifteenm
LZ_USLdAv5* Sentry2_0_loadavgonem
LZ_USLdAv1* Sentry2_0_loadavgonem
LZ_USPgIns* Sentry2_0_pageins
LZ_USPgOuts* Sentry2_0_pageouts
LZ_USACPUBu* Sentry2_0_avgcpubusy
LZ_UDskAva* universal_diskavail
LZ_UDskUsd* universal_diskused
LZ_UDskUPct* universal_diskusedpct
LZ_UIndsFre* universal_diskusedpct
LZ_UIndsUsd* universal_diskusedpct
LZ_ULoadAvg* universal_loadavg
LZ_UPageOut* universal_pageouts
LZ_USwapAva* universal_swapavail

Each of the event classes is a child of KLZ_Base. The KLZ_Base event class can be
used for generic rules processing for any event from the Monitoring Agent for
Linux OS.
Table 10. Overview of event slots to event classes
IBM Tivoli Enterprise Console event class event slots
ITM_Linux_User_Login Linux_User_Login attribute group
v system_name: STRING
v timestamp: STRING
v user_name: STRING
v login_pid: INTEGER
v line: STRING
v login_time: STRING
v idle_time: STRING
v from_hostname: STRING
v user_name_u: STRING
v linux_vm_id: STRING

62 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_Disk Linux_Disk attribute group
v system_name: STRING
v timestamp: STRING
v disk_name: STRING
v mount_point: STRING
v size: INTEGER
v space_used: INTEGER
v space_available: INTEGER
v total_inodes: INTEGER
v inodes_used: INTEGER
v inodes_free: INTEGER
v space_used_percent: INTEGER
v inodes_used_percent: INTEGER
v fs_type: STRING
v space_available_percent: STRING
v mount_point_u: STRING
v linux_vm_id: STRING
ITM_Linux_Disk_Usage_Trends Linux_Disk_Usage_Trends attribute group
v system_name: STRING
v timestamp: INTEGER
v disk_name: STRING
v space_used: INTEGER
v space_available: INTEGER
v disk_usage_rate: INTEGER
v highwater_du_rate: INTEGER
v highwater_time: STRING
v disk_usage_moving_average: INTEGER
v days_until_full_disk: INTEGER
v days_full_disk_curr: INTEGER
v low_water_full_disk_curr: STRING
v days_full_disk_peak: INTEGER
v linux_vm_id: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 63

 IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_Network Linux_Network attribute group
v system_name: STRING
v timestamp: INTEGER
v network_interface_name: STRING
v interface_ip_address: STRING
v interface_dns_name: STRING
v interface_status: INTEGER
v transmission_unit_maximum: INTEGER
v kbytes_received_count: INTEGER
v bytes_received_per_sec: INTEGER
v kbytes_transmitted_count: INTEGER
v bytes_transmitted_per_sec: INTEGER
v packets_received_count: INTEGER
v packets_received_per_sec: INTEGER
v packets_transmitted_per_sec: INTEGER
v input_errors: INTEGER
v output_errors: INTEGER
v collisions: INTEGER
v collision_rate: INTEGER
v collision_percent: INTEGER
v input_error_rate: INTEGER
v output_error_rate: INTEGER
v total_error_percent: INTEGER
v input_packets_dropped: INTEGER
v output_packets_dropped: INTEGER
v input_fifo_buffer_overruns: INTEGER
v output_fifo_buffer_overruns: INTEGER
v packet_framing_errors: INTEGER
v carrier_losses: INTEGER
v linux_vm_id: STRING
ITM_Linux_CPU User attribute group
v system_name: STRING
v timestamp: STRING
v cpu_id: INTEGER
v user_cpu: REAL
v user_nice_cpu: REAL
v system_cpu: REAL
v idle_cpu: REAL
v busy_cpu: REAL
v wait_io_cpu: REAL
v user_sys_pct: INTEGER
v linux_vm_id: STRING

64 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_CPU_Averages Linux_CPU_Averages attribute group
v system_name: STRING
v timestamp: STRING
v days_to_cpu_upgrade: REAL
v cpu_usage_current_average: REAL
v cpu_usage_moving_average: REAL
v user_nice_cpu_current_average: REAL
v user_nice_cpu_moving_average: REAL
v user_cpu_current_average: REAL
v user_cpu_moving_average: REAL
v system_cpu_current_average: REAL
v system_cpu_moving_average: REAL
v idle_cpu_current_average: REAL
v idle_cpu_moving_average: REAL
v wait_cpu_current_average: REAL
v wait_cpu_moving_average: REAL
v linux_vm_id: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 65

 IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_Process Linux_Process attribute group
v system_name: STRING
v timestamp: INTEGER
v process_id: REAL
v parent_process_id: INTEGER
v process_command_name: STRING
v state: INTEGER
v proc_system_cpu: REAL
v proc_user_cpu: REAL
v tot_proc_system_cpu: REAL
v tot_proc_user_cpu: REAL
v priority: INTEGER
v nice: INTEGER
v total_size_memory: INTEGER
v resident_set_size: INTEGER
v shared_memory: INTEGER
v text_resident_size: INTEGER
v shared_lib_set_size: INTEGER
v data_set_size: INTEGER
v dirty_pages: INTEGER
v vm_size: INTEGER
v vm_lock: INTEGER
v vm_data: INTEGER
v vm_stack: INTEGER
v vm_exe_size: INTEGER
v vm_lib_size: INTEGER
v tot_minor_faults: INTEGER
v tot_major_faults: INTEGER
v proc_cmd_line: STRING
v proc_cmd_line_u: STRING
v proc_cpu: INTEGER
v linux_vm_id: STRING
v user_sys_cpu_pct: INTEGER
v process_command_name_u: STRING
v total_busy_cpu_pct: REAL
v busy_cpu_pct: REAL
v vm_size_mb: REAL
v vm_lock_mb: REAL
v vm_data_mb: REAL
v vm_stack_mb: REAL
v vm_exe_size_mb: REAL
v vm_lib_size_mb: REAL
v threads: INTEGER

66 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_Process_User_Info Linux_Process_User_Info attribute group
v system_name: STRING
v timestamp: STRING
v process_id: INTEGER
v real_user_name: STRING
v eff_user_name: STRING
v saved_user_name: STRING
v fs_user_name: STRING
v real_group: STRING
v eff_group: STRING
v saved_group: STRING
v file_sys_group: STRING
v real_user_id: INTEGER
v eff_user_id: INTEGER
v saved_user_id: INTEGER
v fs_user_id: INTEGER
v real_group_id: INTEGER
v eff_group_id: INTEGER
v saved_group_id: INTEGER
v file_sys_group_id: INTEGER
v real_user_name_u: STRING
v eff_user_name_u: STRING
v saved_user_name_u: STRING
v fs_user_name_u: STRING
v real_group_u: STRING
v eff_group_u: STRING
v saved_group_u: STRING
v file_sys_group_u: STRING
v linux_vm_id: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 67

 IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_System_Statistics Linux_System_Statistics attribute group
v system_name: STRING
v timestamp: STRING
v ctxt_switches_per_sec: INTEGER
v pct_change_ctxt_switches: REAL
v processes_per_sec: INTEGER
v pct_change_processes: REAL
v number_of_users: INTEGER
v system_load_1min: REAL
v system_load_5min: REAL
v system_load_15min: REAL
v system_uptime: INTEGER
v linux_vm_id: STRING
v pages_paged_in: INTEGER
v pages_paged_in_per_sec: REAL
v pages_paged_out: INTEGER
v pages_paged_out_per_sec: REAL
v pages_swapped_in: INTEGER
v pages_swap_in_per_sec: REAL
v pages_swapped_out: INTEGER
v pages_swap_out_per_sec: REAL
v page_faults_per_sec: INTEGER
v major_faults_per_sec: INTEGER
ITM_Linux_Swap_Rate Linux_Swap_Rate attribute group
v system_name: STRING
v timestamp: STRING
v moving_total_swap_space: INTEGER
v swap_space_used: INTEGER
v swap_usage_rate: INTEGER
v days_to_swap_space_full: INTEGER
v peak_swap_space_used: INTEGER
v days_to_peak_space_full: INTEGER
v low_free_memory: INTEGER
v linux_vm_id: STRING

68 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_VM_Stats Linux_VM_Stats attribute group
v system_name: STRING
v timestamp: STRING
v total_swap_space: REAL
v swap_space_used: REAL
v swap_usage_free: REAL
v total_memory: REAL
v memory_used: REAL
v memory_free: REAL
v shared_memory: REAL
v memory_in_buffers: REAL
v memory_cached: REAL
v linux_vm_id: STRING
ITM_Linux_Sockets_Status Linux_Sockets_Status attribute group
v system_name: STRING
v timestamp: STRING
v socket_protocol: INTEGER
v sockets_in_use: INTEGER
v highest_sockets_used: INTEGER
v linux_vm_id: STRING
ITM_Linux_Sockets_Detail Linux_Sockets_Detail attribute group
v system_name: STRING
v timestamp: STRING
v socket_protocol: INTEGER
v receive_queue: INTEGER
v send_queue: INTEGER
v local_address: STRING
v local_port: INTEGER
v local_service: STRING
v foreign_address: STRING
v socket_state: INTEGER
v socket_uid: INTEGER
v socket_inode: INTEGER
v foreign_port: INTEGER
v socket_owner_name_u: STRING
v linux_vm_id: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 69

 IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_Disk_IO Linux_Disk_IO attribute group
v system_name: STRING
v timestamp: STRING
v transfers_per_sec: REAL
v blk_rds_per_sec: REAL
v blk_wrtn_per_sec: REAL
v blks_read: INTEGER
v blks_wrtn: INTEGER
v dev_major: INTEGER
v dev_minor: INTEGER
v dev_name: STRING
v linux_vm_id: STRING
ITM_Linux_IO_Ext Linux_IO_Ext attribute group
v system_name: STRING
v timestamp: STRING
v device_name: STRING
v read_reqm_per_sec: REAL
v write_reqm_per_sec: REAL
v read_req_per_sec: REAL
v write_req_per_sec: REAL
v read_sect_per_sec: REAL
v write_sect_per_sec: REAL
v avg_req_size: REAL
v avg_req_queue_length: REAL
v avg_wait_time: REAL
v avg_svc_time: REAL
v cpu_util: REAL
v linux_vm_id: STRING
ITM_Linux_RPC_Statistics Linux_RPC_Statistics attribute group
v system_name: STRING
v timestamp: STRING
v rpc_server_total_calls: INTEGER
v rpc_server_calls_rejected: INTEGER
v rpc_server_packets_bad_auth: INTEGER
v rpc_server_packets_bad_clt: INTEGER
v rpc_server_packets_with_malformed_
header: INTEGER
v rpc_client_calls: INTEGER
v rpc_client_calls_retransmitted: INTEGER
v rpc_client_times_authentication_refreshed:
INTEGER
v linux_vm_id: STRING

70 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_NFS_Statistics Linux_NFS_Statistics attribute group
v location: INTEGER
v nfs_version: INTEGER
v nfs_null_calls: INTEGER
v nfs_null_call_percentage: INTEGER
v nfs_get_attribute_calls: INTEGER
v nfs_get_attribute_calls_pct: INTEGER
v nfs_set_attribute_calls: INTEGER
v nfs_set_attrib_calls_pct: INTEGER
v nfs_root_calls: INTEGER
v nfs_root_calls_pct: INTEGER
v nfs_lookups: INTEGER
v nfs_lookups_pct: INTEGER
v nfs_read_link_calls: INTEGER
v nfs_read_link_pct: INTEGER
v nfs_read_calls: INTEGER
v nfs_read_calls_pct: INTEGER
v nfs_write_cache_calls: INTEGER
v nfs_write_cache_calls_pct: INTEGER
v nfs_writes: INTEGER
v nfs_writes_pct: INTEGER
v nfs_file_creates: INTEGER
v nfs_file_creates_pct: INTEGER
v nfs_remove_file_calls: INTEGER
v nfs_remove_file_calls_pct: INTEGER
v nfs_rename_file_calls: INTEGER
v rename_file_calls_pct: INTEGER
v nfs_link_calls: INTEGER
v link_calls_pct: INTEGER
v nfs_symbolic_link_calls: INTEGER
v symbolic_link_calls_pct: INTEGER
v nfs_make_directory_calls: INTEGER
v nfs_make_directory_calls_pct: INTEGER
v nfs_remove_directory_calls: INTEGER
v remove_directory_calls_pct: INTEGER
v nfs_read_directory_calls: INTEGER
v read_directory_calls_pct: INTEGER
v nfs_file_system_statistics_calls: INTEGER
v file_system_statistics_calls_pct: INTEGER
v nfs_access: INTEGER
v access_pct: INTEGER
v nfs_make_node_calls: INTEGER
v make_node_calls_pct: INTEGER
v nfs_read_dir_calls_plus: INTEGER
v read_dir_calls_plus_pct: INTEGER
Continued on the next page.

Appendix A. IBM Tivoli Enterprise Console event mapping 71

 IBM Confidential

Table 10. Overview of event slots to event classes (continued)

IBM Tivoli Enterprise Console event class event slots
ITM_Linux_NFS_Statistics continued v nfs_file_system_info: INTEGER
v file_system_info_pct: INTEGER
v nfs_path_conf_calls: INTEGER
v path_conf_calls_pct: INTEGER
v nfs_commit: INTEGER
v nfs_commit_pct: INTEGER
v system_name: INTEGER
v timestamp: STRING
v linux_vm_id: STRING
ITM_Linux_CPU_Config Linux_CPU_Config attribute group
v system_name: STRING
v timestamp: STRING
v cpu_id: INTEGER
v vendor_id: STRING
v cpu_family: INTEGER
v cpu_model: INTEGER
v model_name: STRING
v clock_speed: REAL
v cache_size: INTEGER
ITM_Linux_OS_Config Linux_OS_Config attribute group
v system_name: STRING
v timestamp: STRING
v os_name: STRING
v os_version: STRING
v gcc_version: STRING
v os_vendor: STRING

72 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Appendix B. Problem determination

This appendix explains how to troubleshoot the IBM Tivoli Monitoring: Linux OS
Agent. Troubleshooting, or problem determination, is the process of determining
why a certain product is malfunctioning.

Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in Chapter 2, “Requirements for the monitoring
agent,” on page 5.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information. Also see “Support information” on page 90 for other
problem-solving options.

Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing
with this product, gather the following information that relates to the problem:
Table 11. Information to gather before contacting IBM Software Support
Information type Description
Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectory
on the host computer. See “Trace logging” on page 74 for lists of all trace log files and
their locations. See the IBM Tivoli Monitoring User’s Guide for general information about
the IBM Tivoli Monitoring environment.
Linux information v Version number and patch level
v Sample application data file (if monitoring a file)
Operating system Operating system version number and patch level
Messages Messages and other information displayed on the screen
Version numbers for Version number of the following members of the monitoring environment:
IBM Tivoli Monitoring v IBM Tivoli Monitoring. Also provide the patch level, if available.
v IBM Tivoli Monitoring: Linux OS Agent
Screen captures Screen captures of incorrect output, if any.
Core dump files If the system stops on UNIX or Linux systems, collect core dump file from install_dir/bin
directory, where install_dir is the directory path where you installed the monitoring agent.

Upload files for review to the following FTP site: ftp.emea.ibm.com. Log in as
anonymous and place your files in the directory that corresponds to the IBM Tivoli
Monitoring component that you use. See “Contacting IBM Software Support” on
page 92 for more information about working with IBM Software Support.

Built-in problem determination features

The primary troubleshooting feature in the IBM Tivoli Monitoring: Linux OS Agent
is logging. Logging refers to the text messages and trace data generated by the IBM
Tivoli Monitoring: Linux OS Agent. Messages and trace data are sent to a file.

Trace data captures transient information about the current operating environment
when a component or application fails to operate as designed. IBM Software

© Copyright IBM Corp. 2005 73

 IBM Confidential

Support personnel use the captured trace information to determine the source of
an error or unexpected condition. See “Trace logging” for more information.

Problem classification
The following types of problems might occur with the IBM Tivoli Monitoring:
Linux OS Agent:
v Installation and configuration
v General usage and operation
v Display of monitoring data
v Take Action commands

This appendix provides symptom descriptions and detailed workarounds for these
problems, as well as describing the logging capabilities of the monitoring agent.
See the IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.

Trace logging
Trace logs capture information about the operating environment when component
software fails to operate as intended. The principal log type is the RAS (Reliability,
Availability, and Serviceability) trace log. These logs are in the English language
only. The RAS trace log mechanism is available for all components of IBM Tivoli
Monitoring. Most logs are located in a logs subdirectory on the host computer. See
the following sections to learn how to configure and use trace logging:
v “Principal trace log files” on page 75
v “Examples: using trace logs” on page 77
v “Setting RAS trace parameters” on page 78

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 a
problem to its source or to determine why an error occurred. The default
configuration for trace logging, such as whether trace logging is enabled or
disabled and trace level, depends on the source of the trace logging. Trace logging
is always enabled.

Note: When you communicate with IBM Software Support, you must capture and
send the RAS1 log that matches any problem occurrence that you report.
Table 12 on page 76 can help you identify files that are relevant to your
problem determination efforts.

Overview of log file management

Table 12 on page 76 provides the names, locations, and descriptions of RAS1 log
files. The log file names adhere to the following naming convention:
hostname_product_program_timestamp-nn.log

where:
v hostname is the host name of the machine on which the monitoring component is
running.

74 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

v product is the two-character product code. For Monitoring Agent for Linux OS,
the product code is lz.
v program is the name of the program being run.
v timestamp is an 8-character hexadecimal timestamp 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 logging

For example, if a Linux monitoring agent is running on computer ″server01″, the
RAS log file for the Monitoring Agent for Linux OS might be named as follows:
server01_lz_klzagent_437fc59-01.log

For long-running programs, the nn suffix is used to maintain a short history of log
files for that startup of the program. For example, the klzagent program might
have a series of log files as follows:
server01_lz_klzagent_437fc59-01.log
server01_lz_klzagent_437fc59-02.log
server01_lz_klzagent_437fc59-03.log

As the program runs, the first log (nn=01) is preserved because it contains program
startup information. The remaining logs ″roll." In other words, when the set of
numbered logs reach a maximum size, the remaining logs are overwritten in
sequence.

Each time a program is started, a new timestamp is assigned to maintain a short

program history. For example, if the Monitoring Agent for Linux OS is started
twice, it might have log files as follows:
server01_lz_klzagent_437fc59-01.log
server01_lz_klzagent_437fc59-02.log
server01_lz_klzagent_437fc59-03.log

server01_lz_klzagent_537fc59-01.log
server01_lz_klzagent_537fc59-02.log
server01_lz_klzagent_537fc59-03.log

Each program that is started has its own log file. For example, the Monitoring
Agent for Linux OS would have agent logs in this format:
server01_lz_klzagent_437fc59-01.log

Other logs, such as logs for collector processes and Take Action commands, have a
similar syntax as in the following example:
server01_lz_ifstat_447fc59-01.log

where ifstat is the program name.

Note: When you communicate with IBM Software Support, you must capture and
send the RAS1 log that matches any problem occurrence that you report.

Principal trace log files

Table 12 on page 76 contains locations, file names, and descriptions of trace logs
that can help determine the source of problems with agents.

Appendix B. Problem determination 75

 IBM Confidential

Table 12. Trace log files for troubleshooting agents

System where log File name and path Description
is located
On the computer The RAS1 log files are named Traces activity of the monitoring agent.
that hosts the hostname_lz_program_timestamp-nn.log and are Note: Other logs, such as logs for collector
monitoring agent located in the install_dir/logs path. processes and Take Action commands (if
Note: File names for RAS1 logs include a available), have a similar syntax and are
See “Definitions of hexadecimal time stamp. located in this directory path.
variables” on page
77 for descriptions Also on UNIX, a log with a decimal time stamp
of the variables in is provided: hostname_lz_timestamp.log and
the file names in hostname_lz_timestamp.pidnnnnn in the
column two. install_dir/logs path, where nnnnn is the
process ID number.
The *.LG0 file is located in the install_dir/logs A new version of this file is generated
path. every time the agent is restarted. IBM Tivoli
Monitoring generates one backup copy of
the *.LG0 file with the tag .LG1. View .LG0
to learn the following details regarding the
current 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.
On the Tivoli On UNIX: The candle_installation.log file in the Provides details about products that are
Enterprise install_dir/logs path. installed.
Monitoring Server Note: Trace logging is enabled by default.
On Windows: The file in the A configuration step is not required to
See “Definitions of install_dir\InstallITM path. enable this tracing.
variables” on page
77 for descriptions The Warehouse_Configuration.log file is located Provides details about the configuration of
of the variables in in the following path on Windows: data warehousing for historical reporting.
the file names in install_dir\InstallITM.
column two. The RAS1 log file is named Traces activity on the monitoring server.
hostname_ms_timestamp-nn.log and is located in
the following path:
v On Windows: install_dir\logs
v On UNIX: install_dir/logs
Note: File names for RAS1 logs include a
hexadecimal time stamp

Also on UNIX, a log with a decimal time stamp

is provided: hostname_ms_timestamp.log and
hostname_ms_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the
process ID number.

76 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

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

System where log File name and path Description
is located
On the Tivoli The RAS1 log file is named Traces activity on the portal server.
Enterprise Portal hostname_cq_timestamp-nn.log and is located in
Server the following path:
v On Windows: install_dir\logs
See “Definitions of
variables” for v On UNIX: install_dir/logs
descriptions of the Note: File names for RAS1 logs include a
variables in the hexadecimal time stamp
file names in
column two. Also on UNIX, a log with a decimal time stamp
is provided: hostname_cq_timestamp.log and
hostname_cq_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the process ID
number.
The TEPS_ODBC.log file is located in the following When you enable historical reporting, this
path on Windows: install_dir\InstallITM. log file traces the status of the warehouse
proxy agent.
Definitions of variables for RAS1 logs:
v hostname is the host name of the machine on which the agent is running.
v install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can
represent a path on the computer that hosts the monitoring server, the monitoring agent, or the portal server.
v product is the two character product code. For Monitoring Agent for Linux OS, the product code is lz.
v program is the name of the program being run.
v timestamp is an eight-character hexadecimal time stamp representing the time at which the program started.
v nn is a rolling log suffix. See “Examples of trace logging” on page 75 for details of log rolling.

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

Examples: using trace logs

Typically IBM Software Support applies specialized knowledge to analyze trace
logs to determine the source of problems. However, you can open trace logs in a
text editor such as vi to learn some basic facts about your IBM Tivoli Monitoring
environment. You can use the ls -ltr command to list the log files in the
install_dir/logs directories, sorted by time they were last updated.
Example one
This excerpt shows the typical log for a failed connection between a
monitoring agent and a monitoring server with the host name server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,
"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to
broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable
to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>
Example two
The following excerpts from the trace log for the monitoring server show the
status of an agent, identified here as ″Remote node.″ The name of the
computer where the agent is running is SERVER5B:
(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:LZ is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:LZ is OFF-LINE.

Key points regarding the preceding excerpt:

Appendix B. Problem determination 77

 IBM Confidential

v The monitoring server appends the LZ product code to the server name
to form a unique name (SERVER5B:KLZ) for this instance of Monitoring
Agent for Linux OS. This unique name enables you to distinguish
multiple monitoring products that might be running on SERVER5B.
v The log shows when the agent started (ON-LINE) and later stopped
(OFF-LINE) in the environment.
v For the sake of brevity an ellipsis (...) represents the series of trace log
entries that were generated while the agent was running.
v Between the ON-LINE and OFF-LINE log entries, the agent was
communicating with the monitoring server.
v The ON-LINE and OFF-LINE log entries are always available in the
trace log. All trace levels that are described in “Setting RAS trace
parameters” provide these entries.

Setting RAS trace parameters

Objective
Pinpoint a problem by setting detailed tracing of individual components of the
monitoring agent and modules.

Background Information
Monitoring Agent for Linux OS uses RAS1 tracing and generates the logs
described in Table 12 on page 76. The default RAS1 trace level is ERROR.

RAS1 tracing has control parameters to manage to the size and number of RAS1
logs. Use the procedure described in this section to set the parameters.

Note: The KBB_RAS1_LOG parameter also provides for the specification of the
log file directory, log file name, and the inventory control file directory and
name. Do not modify these values or log information can be lost.

Before you begin

See “Overview of log file management” on page 74 to ensure that you understand
log rolling and can reference the correct log files when you managing log file
generation.

After you finish

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

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike
the RAS1 log files which are pruned automatically, other log types can grow
indefinitely, for example, the logs in Table 12 on page 76 that include a process ID
number (PID).

Consider using collector trace logs (described in Table 12 on page 76) as an

additional source of problem determination information.

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

78 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Procedure
Specify RAS1 trace options in the install_dir/config/lz.ini file. You can
manually edit the configuration file to set trace logging:
1. Open the trace options file: /install_dir/config/lz.ini.
2. Edit the line that begins with KBB_RAS1= to set trace logging preferences.
For example, if you want detailed trace logging, set the Maximum Tracing
option:
export KBB_RAS1=’ERROR (UNIT:klz ALL) (UNIT:kra ALL)’
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of
log files:
v Edit the following parameters to adjust the number of rolling log files and
their size.
– MAXFILES: the total number of files that are to be kept for all startups of
a given program. Once this value is exceeded, the oldest log files are
discarded. Default value is 9.
– LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default
value is 5.
v IBM Software Support might guide you to modify the following parameters:
– COUNT: the number of log files to keep in the rolling cycle of one
program startup. Default value is 3.
– PRESERVE: the number of files that are not to be reused in the rolling
cycle of one program startup. Default value is 1.

Note: The KBB_RAS1_LOG parameter also provides for the specification of

the log file directory, log file name, and the inventory control file
directory and name. Do not modify these values or log information can
be lost.
4. Restart the monitoring agent so that your changes take effect.

Problems and workarounds

The following sections provide symptoms and workarounds for problems that
might occur with Monitoring Agent for Linux OS:
v “Installation and configuration problem determination” on page 79
v “Agent problem determination” on page 84
v “Tivoli Enterprise Portal problem determination” on page 86
v “Problem determination for remote deployment” on page 87
v “Situation problem determination” on page 87

Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in Chapter 2, “Requirements for the monitoring
agent,” on page 5.
This appendix provides agent-specific problem determination information. See the
IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.

Installation and configuration problem determination

This section provides tables that show solutions for installation, configuration, and
uninstallation problems.

Appendix B. Problem determination 79

 IBM Confidential

Table 13. Problems and solutions for installation and configuration

Problem Solution
When you upgrade to IBM Tivoli Monitoring, you Fixpacks for Candle, Version 350, are delivered as each
might need to apply fixpacks to Candle, Version monitoring agent is upgraded to IBM Tivoli Monitoring.
350, agents. Note: The IBM Tivoli Monitoring download image or CD
provides application fixpacks for the monitoring agents that are
installed from that CD (for example, the agents for operating
systems such as Windows, Linux, UNIX, and i5/OS). The
upgrade software for other agents is located on the download
image or CDs for that specific monitoring agent, such as the
agents for database applications.

If you do not upgrade the monitoring agent to IBM Tivoli

Monitoring, the agent continues to work. However, you must
upgrade to have all the functionality that IBM Tivoli
Monitoring offers.
Presentation files and customized Omegamon DE The upgrade from version 350 to IBM Tivoli Monitoring
screens for Candle monitoring agents need to be handles export of the presentation files and the customized
upgraded to a new Linux on z/Series system. Omegamon DE screens.
Installation of Monitoring Agent for Linux OS on Solve this problem as follows:
the Linux S390 R2.6 64-bit operating system fails 1. Run the following command before running any installation
with a message similar to the following: LINUX or configuration command for the agent:
MONITORING AGENT V610Rnnn unable to install
export JAVA_COMPILER=NONE
agent, where nnn is the release number.
2. Install the following two RPM (Red Hat Package Manager)
files:
v compat-libstdc++-295-2......s390x.rpm
v compat-libstdc++-33-3.......s390x.rpm It requires the two
s390x.rpm files, in addition to the s390.rpm files.
You can obtain the required RPM files from the CD for Red
Hat As 4.0 s390x.
During a command-line installation, you choose to You must exit and restart the installation process. You cannot
install a component that is already installed, and return to the list where you selected components to install.
you see the following warning: When you run the installer again, do not attempt to install any
WARNING - you are about to install component that is already installed.
the SAME version of "component"

where component is the name of the component

that you are attempting to install.
Note: This problem affects UNIX command-line
installations. If you monitor only Windows
environments, you would see this problem if you
choose to install a product component (for
example, a monitoring server) on UNIX.
The product fails to do a monitoring activity that The monitoring agent must have the permissions necessary to
requires read, write, or execute permissions. For perform requested actions. For example, if the user ID you
example, the product might fail to run a Take used to log onto the system to install the monitoring agent
Action command or read a log. (locally or remotely) does not have the permission to perform a
monitoring operation (such as running a command), the
monitoring agent is not able perform the operation.
While installing the agent from a CD, the This error is caused by low disk space. Although the install.sh
following message is displayed and you are not script indicates that it is ready to install the agent software, the
able to continue the installation: script considers the size of all tar files, not the size of all the
install.sh warning: unarchive of files that are contained within the tar file.Run the df -k
"/cdrom/unix/cienv1.tar" may command to check whether the file systems have enough space
have failed to install agents.

80 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 13. Problems and solutions for installation and configuration (continued)
Problem Solution
Installing as root: The product has been installed When you install the product as root the files in the
as root, which is not recommended. Without install_dir directory are owned by root. You must change the
re-installing the product, how can you change status of the files as follows:
from root to a different user account? 1. While logged on as root, run the
install_dir/bin/UnSetRoot script, as in this example:
UnSetRoot [ -h CANDLEHOME ] userID
The script resets all the files under the install_dir
directory.
2. Run the install_dir/bin/SetPerm command. SetPerm sets
root permission for specific IBM Tivoli Monitoring agent
files.

About installing as root: Normally, do not use the root user

account to install or to start the Monitoring Agents for UNIX,
for Linux, and for UNIX Logs. If you use the root user account
to install the product, the files do not receive the correct
permissions, and product behavior is unpredictable.

To create a stable installation of the product, use one of the

following options:
v Create a user account with all the authority and permissions
to install and run commands. For example, create a tivoli
user account.
—OR—
v Use any user account other than root that has the required
authority and permissions.
Cannot locate the KDCB0_HOSTNAME setting. Go to install_dir/config and edit the corresponding .ini file.
Set the KDCB0_HOSTNAME parameter followed by the IP
address. If you use multiple network interface cards (NICs),
give the Primary IP address of the network interface.
The Monitoring Agent for Linux OS repeatedly You can collect data to analyze this problem as follows:
restarts. 1. Access the install_dir/config/lz.ini file, which is
described in “Setting RAS trace parameters” on page 78.
2. Add the following line: KBB_SIG1=trace –dumpoff
Agents in the monitoring environment use Configure both the monitoring server and the Warehouse proxy
different communication protocols. For example, server to accept multiple protocols, as described in the IBM
some agents have security enabled and others do Tivoli Monitoring Installation and Setup Guide.
not.
Creating a firewall partition file: The partition file How it works: When the agents start, they search
enables an agent to connect to the monitoring KDCPARTITION.TXT for the following matches:
server through a firewall. v An entry that matches the partition name OUTSIDE.
v An entry that also includes a valid external address.
For more information, see the IBM Tivoli Monitoring Installation
and Setup Guide.
You see the following error: Confirm that the password within the Tivoli Enterprise
Hub not registered with location Monitoring Server is correct.
broker. Error-code 1195.

Appendix B. Problem determination 81

 IBM Confidential

Table 13. Problems and solutions for installation and configuration (continued)
Problem Solution
The Monitoring Agent for Linux OS is started and Perform the following steps:
running but not displaying data in the Tivoli 1. Open the Manage Tivoli Enterprise Monitoring Services
Enterprise Portal. window.
2. Right-click the name of the monitoring server.
3. Select Advanced > Add TEMS Application Support in the
pop-up menu. Add application support if any for any agent
that is missing from the list. See in IBM Tivoli Monitoring
Installation and Setup Guide for more information on
adding application support.
4. Check the log files to see whether there are connection
problems like those mentioned in “Agent unable to
connect” on page 85.
5. If there are no connection problems, check whether the
agent has terminated.
6. If the agent is not terminated, confirm that you have added
application support for the Monitoring Agent for Linux OS
in the Tivoli Enterprise Monitoring Server as follows:
v Verify that the following entries are available in the
install_dir\candle_installation.log
file:install_dir\Install\IBM Tivoli Monitoring timestamp.log
... Browser Client support for ITM Agent for Linux
... Desktop Client support for ITM Agent for Linux

If the candle_installation.log file does not have the

above entries for Monitoring Agent for Linux OS, add
application support for this monitoring agent. See in IBM
Tivoli Monitoring Installation and Setup Guide for more
information on adding application support.
v Verify that the following files are available in the
directory:
install_dir\ATTRLIB\klz.atr
install_dir\CNPS\CMSATR\klz.atr
install_dir\SQLLIB\klz.sql
install_dir\CNPS\SQLLIB\klz.sql

You successfully migrate a Candle monitoring Copy the attribute files for the upgraded Candle monitoring
agent to IBM Tivoli Monitoring, Version 6.1.0. agent to install_dir\tmaitm6\attrlib on the computer where
However, when you configure historical data you have installed the Warehouse Proxy. The Warehouse Proxy
collection, you see an error message that includes, must be able to access the short attribute names for tables and
Attribute name may be invalid, or attribute columns. That way, if the longer versions of these names
file not installed for warehouse agent. exceed the limits of the Warehouse database, the shorter names
can be substituted.

82 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 14. General problems and solutions for uninstallation

Problem Solution
On Windows, uninstallation of Be sure that you follow the general uninstallation process described in the IBM
IBM Tivoli Monitoring fails to Tivoli Monitoring Installation and Setup Guide:
uninstall the entire environment. 1. Uninstall monitoring agents first, as in the following examples:
v Uninstall a single monitoring agent for a specific database.
—OR—
v Uninstall all instances of a monitoring product, such as IBM Tivoli
Monitoring for Databases.
2. Uninstall IBM Tivoli Monitoring.
The way to remove inactive When you want to remove a managed system from the navigation tree,
managed systems (systems whose right-click the item that you want to remove, and select Remove managed
status is OFFLINE) from the system.
Enterprise navigation tree in the
portal is not obvious.

Unique names for monitoring components

IBM Tivoli Monitoring might not be able to generate a unique name for monitoring
components due to the truncation of names that the product automatically
generates.

IBM Tivoli Monitoring automatically creates a name for each monitoring

component by concatenating the host name and product code separated by colons
(hostname:LZ).

Note: When you monitor a multinode system, such as a database, IBM Tivoli
Monitoring adds a subsystem name to the concatenated name, typically a
database instance name.
The length of the name that IBM Tivoli Monitoring generates is limited to 32
characters. Truncation can result in multiple components having the same
32-character name. If this problem happens, shorten the hostname portion of the
name as follows:
1. Open the configuration file for the monitoring agent, which is located in the
following path: install_dir/config/lz.ini.

Note: When you modify the lz.ini file, your configuration changes affect only
the instance Monitoring Agent for Linux OS that is running on the
computer. If you want your configuration changes to affect all agents
that run on the computer, modify the install_dir/config/env.config
file.
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 host
computer. The final concatenated name including the subsystem name, new
host name, and LZ, cannot be longer than 32 characters.

Note: You must ensure that the resulting name is unique with respect to any
existing monitoring component that was previously registered with the
Tivoli Enterprise Monitoring Server.
4. Save the file.
5. Restart the agent.
6. If you do not find the files mentioned in Step 1, perform the workarounds
listed in the next paragraph.

Appendix B. Problem determination 83

 IBM Confidential

If you cannot find the CTIRA_HOSTNAME environment variable, you must add
it to the configuration file of the monitoring agent:
v On Windows: Use the Advanced > Edit Variables option.
v On UNIX and Linux: Add the variable to the config/product_code.ini file.

Agent problem determination

This section lists problems that might occur with agents.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.
Table 15. Agent problems and solutions
Problem Solution
When you edit the configuration The original configuration settings might include non-ASCII characters. These
for an existing monitoring agent, values were stored incorrectly and result in the incorrect display. Enter new
the values displayed are not values using only ASCII characters.
correct.

84 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 15. Agent problems and solutions (continued)

Problem Solution
Agent unable to connect: The This error message means that the agent is not able to connect to the computer
agent is started, but no reports are where the Tivoli Enterprise Monitoring Server is running. The reason might be
displayed on Tivoli Enterprise any one of the following:
Monitoring Server. The log file Computer where the Tivoli Enterprise Monitoring Server is running is down
includes the following error: Ping the computer where the Tivoli Enterprise Monitoring Server is running
Unable to find running CMS on and make sure that it is up and running.
CMSLIST or Endpoint unavailable Tivoli Enterprise Monitoring Server is not running
If the Tivoli Enterprise Monitoring Server is not running, recycle the Tivoli
Enterprise Monitoring Server and verify whether the agent is connecting.
Multiple NIC Cards on the computer where the Tivoli Enterprise Monitoring
Server is running.
If multiple NICs are installed on the computer where the Tivoli Enterprise
Monitoring Server is running, identify the Primary NIC and use the
hostname or IP address.
Verify that the Tivoli Enterprise Monitoring Server has been configured with
the Primary NIC’s IP address or hostname.
If you are using hostname, make sure that /etc/hosts has a valid entry for
the Primary NICs host name and its IP address.
On the Tivoli Enterprise Monitoring Server set the KDCB0_HOSTNAME
variable to the primary IP address of the computer. Use the same address to
configure the agent.
To connect to the Tivoli Enterprise Monitoring Server, configure the agent
with Primary NIC’s IP address or host name of the computer where the
Tivoli Enterprise Monitoring Server is running.
While configuring the agent, make sure that the port number that you are
connecting to is correct. If you are not using the default port number, make
sure that you are using the same port number used in Tivoli Enterprise
Monitoring Server. For more information, see the IBM Tivoli Monitoring
Installation and Setup Guide.
Agent is behind the Firewall
If you use a Firewall, identify whether you have any one of the following
scenarios:
v Hub monitoring server INSIDE, and agents OUTSIDE
v Hub and remote monitoring servers INSIDE, agents OUTSIDE
v Hub monitoring server INSIDE, remote monitoring server and agents
OUTSIDE
See Creating a firewall partition file for information about the
KDC_PARTITION file that enables communication across a firewall. For
additional information, see the IBM Tivoli Monitoring Installation and Setup
Guide.
Connecting to the monitoring server through a Virtual Private Network
(VPN)
In some cases, the agent or a remote monitoring server needs to connect to
the hub monitoring server through a VPN. You must configure the
communication channel (pipe) to be ephemeral, as in the following example:
KDC_FAMILIES=ip.pipe port:port_number
ephemeral:y ip use:n sna use:n

Appendix B. Problem determination 85

 IBM Confidential

Table 15. Agent problems and solutions (continued)

Problem Solution
The agent’s process, klzagent uses In most cases, the problem occurs during the backup. Any one of the following
a large amount of system scenarios can cause this problem.
resources.
The agent is running during the backup
After backing up, the agent is started during system startup.
Multiple agents are running at the same time.
The computer that hosts the Tivoli Enterprise Monitoring Server was
rebooted and the agent has been installed by the root user account.
The agent is running during the backup
During the backup, some of the service might be interrupted or not be
available or locked for some amount of time. While the backup process
is going on, the Monitoring Agent for Linux OS, which is running
parallel, might wait for resources to be freed by the backup process.
When the backup is completed and you are viewing the agent, high
CPU at this point is expected, because the agent is in an uncertain state
(backup usually stops several kernel services that could cause this
state). For this reason, it is advisable to stop all agents before the
backup run, because there might be lost information, file, or API
connections. Stop the agent before the backup process starts.
The agent is started during system boot up:
If you use scripts to stop and start the agent, do not start the agent
from an init process script when you restart the system.
The computer that hosts the Tivoli Enterprise Monitoring Server was
rebooted and the agent has been installed by the root user account.
Verify whether the log file has the following information:
Unable to find running Tivoli Enterprise Monitoring Server on CMSLIST

If the Monitoring Agent for Linux OS log file has this information, see Agent
unable to connect.

Tivoli Enterprise Portal problem determination

Table 16 lists problems that might occur with the Tivoli Enterprise Portal. This
appendix provides agent-specific problem determination information. See the IBM
Tivoli Monitoring Problem Determination Guide for general problem determination
information.
Table 16. Tivoli Enterprise Portal problems and solutions
Problem Solution
Historical data collection is The column, Sort By, Group By, and First/Last functions are not compatible with
unavailable because of the historical data collection feature. Use of these advanced functions will make a
incorrect queries in the Tivoli query ineligible for historical data collection.
Enterprise Portal.
Even if data collection has been started, you cannot use the time span feature if the
query for the chart or table includes any column functions or advanced query
options (Sort By, Group By, First / Last).

To ensure support of historical data collection, do not use the Sort By, Group By, or
First/Last functions in your queries.

See the IBM Tivoli Monitoring Administrator’s Guide the Tivoli Enterprise Portal
online Help for information on the Historical Data Collection function.

86 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 16. Tivoli Enterprise Portal problems and solutions (continued)

Problem Solution
When you use a long process Truncation of process names in the portal display is the expected behavior. 64 bytes
name in the situation, the is the maximum name length.
process name is truncated.
You see the following You see this message because some links do not have default workspaces.
message: KFWITM083W Default Right-click the link to access a list of workspaces to select.
link is disabled for the
selected object; please
verify link and link anchor
definitions.

Problem determination for remote deployment

Table 17 lists problems that might occur with remote deployment. This appendix
provides agent-specific problem determination information. See the IBM Tivoli
Monitoring Problem Determination Guide for general problem determination
information.

This section describes problems and solutions for remote deployment and removal
of agent software Agent Remote Deploy:
Table 17. Remote deployment problems and solutions
Problem Solution
The removal of a monitoring agent fails when you This problem might happen when you attempt the remote
use the remote removal process in the Tivoli removal process immediately after you have restarted the
Enterprise Portal desktop or browser. Tivoli Enterprise Monitoring Server. You must allow time for
the monitoring agent to refresh its connection with the Tivoli
Enterprise Monitoring Server before you begin the remote
removal process.

Situation problem determination

This section provides information about both general situation problems and
problems with the configuration of situations. See the IBM Tivoli Monitoring
Problem Determination Guide for more information about problem determination for
situations.

General situation problems

Table 18 lists problems that might occur with specific situations.
Table 18. Specific situation problems and solutions
Problem Solution
You want to change the appearance of 1. Right-click an item in the Navigation tree.
situations when they are displayed in a
2. Select Situations in the pop-up menu. The Situation Editor window is
Workspace view.
displayed.
3. Select the situation that you want to modify.
4. Use the Status pull-down menu in the lower right of the window to
set the status and appearance of the Situation when it triggers.
Note: This status setting is not related to severity settings in IBM
Tivoli Enterprise Console.
Monitoring activity requires too much Check the RAS trace logging settings that are described in “Setting RAS
disk space. trace parameters” on page 78. For example, trace logs grow rapidly when
you apply the ALL logging option.

Appendix B. Problem determination 87

 IBM Confidential

Table 18. Specific situation problems and solutions (continued)

Problem Solution
A formula that uses mathematical This formula is incorrect because situation predicates support only logical
operators appears to be incorrect. For operators. Your formulas cannot have mathematical operators.
example, if you were monitoring Linux, Note: The Situation Editor provides alternatives to math operators.
a formula that calculates when Free Regarding the example, you can select % Memory Free attribute and
Memory falls under 10 percent of Total avoid the need for math operators.
Memory does not work: LT
#’Linux_VM_Stats.Total_Memory’ / 10
If you are running a Version 350 Access the database detail. In the ″release″ section change the version
Monitoring Agent for Linux OS and you setting for the agent from 610 to 350. To enable Unicode and other
choose to alter the views to include a features, upgrade the monitoring agent to IBM Tivoli Monitoring, Version
Version 610 UNICODE attribute, be 6.1.0.
aware that data for this attribute is not
displayed and you see a blank column
in this view.
Situations that you create display the For a situation to have the correct severity in TEC for those situations
severity UNKNOWN in IBM Tivoli which are not mapped, you need to ensure that an entry exists in the
Enterprise Console. tecserver.txt file for the situation and that SEVERITY is specified.

See the “Configuring Tivoli Enterprise Console integration” chapter in the

IBM Tivoli Monitoring Administrator’s Guide for more information.
You see the 'Unable to get attribute Ensure that the agent attribute files are installed on the Tivoli Enterprise
name' error in the Tivoli Enterprise Monitoring Server.
Monitoring Server log after creating a
situation. The following example shows a typical log entry when you have this
problem:
(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \
Unable to get attribute name for tablename/column \
<UAG524400.UA4>. Ignored.

Problems with configuration of situations

Table 19 lists problems that might occur with situations.

This section provides information for problem determination for agents. Be sure to
consult the IBM Tivoli Monitoring Problem Determination Guide for more general
problem determination information.
Table 19. Problems with configuring situations that you solve in the Situation Editor
Problem Solution
Note: To get started with the solutions in this section, perform these steps:
1. Launch the Tivoli Enterprise Portal.
2. Click Edit > Situation Editor.
3. In the tree view, choose the agent whose situation you want to modify.
4. Choose the situation in the list. The Situation Editor view is displayed.
The situation for a specific agent is Open the Situation Editor. Access the All managed servers view. If the situation
not visible in the Tivoli Enterprise is absent, confirm that application support for Monitoring Agent for Linux OS
Portal. has been added to the monitoring server. If not, add application support to the
server, as described in the IBM Tivoli Monitoring Installation and Setup Guide.
The monitoring interval is too Access the Situation Editor view for the situation that you want to modify.
long. Check the Sampling interval area in the Formula tab. Adjust the time interval
as needed.

88 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Table 19. Problems with configuring situations that you solve in the Situation Editor (continued)
Problem Solution
The situation did not activate at Manually recycle the situation as follows:
startup. 1. Right-click the situation and choose Stop Situation.
2. Right-click the situation and choose Start Situation.
Note: You can permanently avoid this problem by placing a check mark in the
Run at Startup option of the Situation Editor view for a specific situation.
The situation is not displayed. Click the Action tab and check whether the situation has an automated
corrective action. This action can occur directly or through a policy. The
situation might be resolving so quickly that you do not see the event or the
update in the graphical user interface.
An Alert event has not occurred Check the logs, reports, and workspaces.
even though the predicate has been
properly specified.
A situation fires on an unexpected Confirm that you have distributed and started the situation on the correct
managed object. managed system.
The product did not distribute the Click the Distribution tab and check the distribution settings for the situation.
situation to a managed system.
The situation does not fire. In the Formula tab, analyze predicates as follows:
1. Click the fx icon in the upper-right corner of the Formula area. The Show
Incorrect predicates are present in
formula window is displayed.
the formula that defines the
situation. For example, the a. Confirm the following details in the Formula area at the top of the
managed object shows a state that window:
normally triggers a monitoring v The attributes that you intend to monitor are specified in the formula.
event, but the situation is not true v The situations that you intend to monitor are specified in the formula.
because the wrong attribute is v The logical operators in the formula match your monitoring goal.
specified in the formula. v The numerical values in the formula match your monitoring goal.
b. (Optional) Click the Show detailed formula check box in the lower left
of the window to see the original names of attributes in the application
or operating system that you are monitoring.
c. Click OK to dismiss the Show formula window.
2. (Optional) In the Formula area of the Formula tab, temporarily assign
numerical values that will immediately trigger a monitoring event. The
triggering of the event confirms that other predicates in the formula are
valid.
Note: After you complete this test, you must restore the numerical values
to valid levels so that you do not generate excessive monitoring data based
on your temporary settings.

Table 20. Problems with configuration of situations that you solve in the Workspace area
Problem Solution
Situation events are not displayed Associate the situation with a workspace.
in the Events Console view of the Note: The situation does not need to be displayed in the workspace. It is
workspace. sufficient that the situation be associated with any workspace.
You do not have access to a Note: You must have administrator privileges to perform these steps.
situation. 1. Select Edit > Administer Users to access the Administer Users window.
2. In the Users area, select the user whose privileges you want to modify.
3. In the Permissions tab, Applications tab, and Navigator Views tab, select
the permissions or privileges that correspond to the user’s role.
4. Click OK.

Appendix B. Problem determination 89

 IBM Confidential

Table 20. Problems with configuration of situations that you solve in the Workspace area (continued)
Problem Solution
A managed system seems to be 1. Select Physical View and highlight the Enterprise Level of the navigator
offline. tree.
2. Select View > Workspace > Managed System Status to see a list of
managed systems and their status.
3. If a system is offline, check network connectivity and status of the specific
system or application.

Table 21. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services
window
Problem Solution
After an attempt to restart the Check the system status and check the appropriate IBM Tivoli Monitoring logs.
agents in the Tivoli Enterprise
Portal, the agents are still not
running.
The Tivoli Enterprise Monitoring Check the system status and check the appropriate IBM Tivoli Monitoring logs.
Server is not running.
The managed objects you created Check the managed system distribution on both the situation and the managed
are firing on incorrect managed object settings sheets.
systems.

Support information
If you have a problem with your IBM software, you have the following options for
obtaining support for software products:
v “Searching knowledge bases”
v “Obtaining fixes” on page 91
v “Receiving weekly support updates” on page 91
v “Contacting IBM Software Support” on page 92

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

90 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:

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

To search for information on IBM products through the Internet (for example, on
Google), be sure to consider the following types of documentation:
v IBM technotes
v IBM downloads
v IBM Redbooks
v IBM developerWorks
v Forums and newsgroups

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the Software support Web site at
http://www.ibm.com/software/support.
2. Click the Download tab.
3. Select the operating system in the Operating system menu.
4. Type search terms in the Enter search terms field.
5. As appropriate, use other search options to further define your search.
6. Click Search.
7. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click My account in the upper right corner of the page.
3. Click Subscribe to IBM e-news. (If you have already subscribed and want to
modify your subscription preferences, click Modify subscriptions and follow
the instructions on screen.)
4. Follow the instructions on screen to provide the following data:
v Your personal contact information.

Appendix B. Problem determination 91

 IBM Confidential

v Your areas of interest.

v The types of subscriptions and regional versions that you want to receive.
5. Review the subscription confirmation to confirm your settings.

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus, and Rational products, as well as DB2 and WebSphere products that run
on Windows, or UNIX operating systems), enroll in Passport Advantage in one
of the following ways:
Online
Go to the Passport Advantage Web site at
http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries, z/Series,
and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer software products (including, but not limited to, DB2 and
WebSphere products that run in z/Series, pSeries, and iSeries environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact” on page 93
2. “Describing problems and gathering information” on page 93
3. “Submitting problems” on page 93

92 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.
See “Gathering product information for IBM Software Support” on page 73 for
further tips for gathering information for IBM Software Support.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site at
http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the

Appendix B. Problem determination 93

 IBM Confidential

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

94 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Appendix C. Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in this product enable users to do the following:
v Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following

features to aid accessibility:
v All documentation is available in both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.

Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and are
documented by the operating system. Refer to the documentation provided by
your operating system for more information.

Magnifying what is displayed on the screen

You can enlarge information on the product windows using facilities provided by
the operating systems on which the product is run. For example, in a Microsoft®
Windows environment, you can lower the resolution of the screen to enlarge the
font sizes of the text on the screen. Refer to the documentation provided by your
operating system for more information.

© Copyright IBM Corp. 2005 95

 IBM Confidential

96 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Appendix D. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

© Copyright IBM Corp. 2005 97

 IBM Confidential

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating systems. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
system for which the sample programs are written. These examples have not been

98 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs. You may copy, modify, and
distribute these sample programs in any form without payment to IBM for the
purposes of developing, using, marketing, or distributing application programs
conforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color
illustrations might not appear.

Trademarks
IBM, the IBM logo, Candle, DB2®, developerWorks, eServer™, i5/OS™, iSeries,
Lotus®, OMEGAMON, OS/390®, OS/400, Passport Advantage®, pSeries®,
Rational®, Redbooks™, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli Enterprise
Console, VTAM®, WebSphere®, z/VM, and zSeries® are trademarks or registered
trademarks of International Business Machines Corporation in the United States,
other countries, or both.

Microsoft, Windows, and Windows NT® are registered trademarks of Microsoft

Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium® are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names may be trademarks or service marks
of others.

Appendix D. Notices 99
 IBM Confidential

100 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

Index
A CPU Averages workspace 14
CPU Config attribute group 26
accessibility ix, 95 customer support
actions See support
See Take Action commands customizing
agent monitoring environment 9
problem determination 84 situations 10
trace logs 75
agents, remote monitoring 1
alerts 1
attribute groups D
CPU 24 data
CPU Averages 25 collecting 11
CPU Config 26 trace logs 74
Disk 27 viewing 11
Disk I/O 28 data provider
Disk Usage Trends 29 See agent
I/O Ext 30 database agent installation problems 79
list of all 24 detecting problems, modifying situation values 10
more information 23 directory names, notation x
Network 31 Disk attribute group 27
NFS Statistics 33 disk capacity planning for historical data 47
OS Config 36 Disk I/O attribute group 28
overview 23 Disk IO Extended Rate workspace 19
Process 37 Disk IO Rate workspace 19
Process User Info 39 disk space requirements 5
RPC Statistics 41 Disk Usage Trends attribute group 29
Sockets Detail 42 Disk Usage workspace 15
Sockets Status 43
Swap Rate 44
System Statistics 45 E
User Login 46 education
VM Stats 47 see Tivoli technical training ix
attributes environment
more information 23 customizing 9
overview 23 features 1
monitoring real-time 7
real-time monitoring 7
B environment variables, notation x
books event
feedback viii mapping 61
online viii events
ordering viii investigating 8
see publications ix workspaces 8
built-in problem determination features 73

F
C features, Monitoring Agent for Linux OS 1
calculate historical data disk space 47 files
capacity planning for historical data 47 agent trace 75
Capacity Usage Information workspace 14 installation trace 75
collecting data 11 other trace log 76
commands, Take Action 57 trace logs 74
components 2 fixes, obtaining 91
configuration 5
contacting support 92
conventions G
operating system x gathering support information 73
typeface x
CPU attribute group 24
CPU Averages attribute group 25

© Copyright IBM Corp. 2005 101

 IBM Confidential

H logging (continued)
trace log files 74
historical data
calculate disk space 47
disk capacity planning 47
historical data, collecting and viewing 11 M
manuals
feedback viii
I online viii
ordering viii
I/O Ext attribute group 30 see publications ix
IBM Software Support memory requirements 5
See support messages
IBM Tivoli Enterprise Console built-in features 73
event mapping 61 modifying situation values to detect problems 10
IBM Tivoli Monitoring: Linux OS Agent Monitoring Agent for Linux OS
performance considerations 87 components 2
information centers for support 90 features 1
information, additional purposes 7
attributes 23 using 7
policies 59 Monitoring Agent for Linux OS installation problems 79
procedural 7 monitoring agents, remote 1
situations 51 monitoring servers 1
Take Action commands 57 monitoring, viewing the real-time environment 7
workspaces 13
installation 5
log file 75
problems 79 N
interface, user 2 Network attribute group 31
problem determination for Tivoli Enterprise Portal 86 Network workspace 16
Internet NFS Statistics attribute group 33
for product support 91 NFS Statistics workspace 16
investigating an event 8 notation
environment variables x
path names x
K typeface x

knowledge bases for support 90

O
L online publications
accessing ix
legal notices 97 for support 90
Linux agent installation problems 79 operating systems 5
Linux_Fragmented_File_System situation 52 operation of resource, recovering 8
Linux_High_CPU_Overload situation 52 ordering publications ix
Linux_High_CPU_System situation 52 OS Config attribute group 36
Linux_High_Packet_Collisions situation 53 other requirements 5
Linux_High_RPC_Retransmit situation 53
Linux_High_Zombies situation 53
Linux_Low_Pct_Inodes situation 53
Linux_Low_percent_space situation 53 P
Linux_Low_Space_Available situation 53 path names, for trace logs 74
Linux_Network_Status situation 53 path names, notation x
Linux_NFS_Buffer_High situation 54 performance considerations 87
Linux_NFS_Getattr_High situation 54 policies
Linux_NFS_rdlink_high situation 54 list of all 59
Linux_NFS_Read_High situation 54 more information 59
Linux_NFS_Writes_High situation 54 overview 59
Linux_Packets_Error situation 54 predefined 59
Linux_Process_High_Cpu situation 54 problem determination 73, 79
Linux_Process_stopped situation 55 agents 84
Linux_RPC_Bad_Calls situation 55 built-in features 73
Linux_System_Thrashing situation 55 describing problems 93
logging determining business impact 93
agent trace logs 75, 76 information centers for 90
built-in features 73 installation 79
installation log files 75 installation logs 75
location and configuration of logs 74 knowledge bases for 90

102 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide

IBM Confidential

problem determination (continued) situations (continued)

remote deployment 87 Linux_NFS_Buffer_High 54
situations 87, 88 Linux_NFS_Getattr_High 54
submitting problems 93 Linux_NFS_rdlink_high 54
Tivoli Enterprise Portal 86 Linux_NFS_Read_High 54
uninstallation 79 Linux_NFS_Writes_High 54
uninstallation logs 75 Linux_Packets_Error 54
problems Linux_Process_High_Cpu 54
detecting 10 Linux_Process_stopped 55
problems and workarounds 79 Linux_RPC_Bad_Calls 55
procedures 7 Linux_System_Thrashing 55
Process attribute group 37 list of all 52
Process User Info attribute group 39 more information 51
Process User Information workspace 18 overview 51
Process workspace 18 predefined 52
publications specific problem determination 87
accessing online ix values, modifying 10
feedback viii situations, using attributes 23
for support 90 Sockets Detail attribute group 42
online viii Sockets Information workspace 17
ordering viii, ix Sockets Status attribute group 43
purposes standardization 1
collecting data 11 support
customizing monitoring environment 9 about 90
investigating events 8 contacting 92
monitoring with custom situations 10 describing problems 93
problem determination 73 determining business impact of problems 93
recovering resource operation 8 gathering information for 73
viewing data 11 information centers for 90
viewing real-time monitoring environment 7 knowledge bases for 90
obtaining fixes 91
on Internet 91
Q submitting problems 93
weekly update option 91
queries, using attributes 23
Swap Rate attribute group 44
System Configuration workspace 19
System Information workspace 20
R System Statistics attribute group 45
real-time data, viewing 7
recovering the operation of a resource 8
remote deployment
problem determination 87
T
Take Action commands 8
remote monitoring agents 1
more information 57
requirements
overview 57
disk space 5
Sample_kill_Process 58
memory 5
tasks for using 7
operating system 5
Tivoli Availability Portal
other 5
how to use 1
resource, recovering operation 8
Tivoli Enterprise Portal
RPC Statistics attribute group 41
problem determination 86
RPC Statistics workspace 17
Tivoli software information center ix
Tivoli technical training ix
trace logs 74
S directories 74
Sample_kill_Process Take Action command 58 trademarks 99
situations training, Tivoli technical ix
general problem determination 88 troubleshooting 73
Linux_Fragmented_File_System 52 typeface conventions x
Linux_High_CPU_Overload 52
Linux_High_CPU_System 52
Linux_High_Packet_Collisions 53
Linux_High_RPC_Retransmit 53
U
uninstallation
Linux_High_Zombies 53
log file 75
Linux_Low_Pct_Inodes 53
problems 79
Linux_Low_percent_space 53
user interfaces options 2
Linux_Low_Space_Available 53
User Login attribute group 46
Linux_Network_Status 53

Index 103
 IBM Confidential

Users workspace 21

V
values, modifying situations 10
variables, notation for x
viewing data 11
viewing real-time monitoring environment 7
views
Capacity Usage Information workspace 14
CPU Averages workspace 14
Disk IO Extended Rate workspace 19
Disk IO Rate workspace 19
Disk Usage workspace 15
Network workspace 16
NFS Statistics workspace 16
Process User Information workspace 18
Process workspace 18
RPC Statistics workspace 17
Sockets Information workspace 17
System Configuration workspace 19
System Information workspace 20
Users workspace 21
Virtual Memory Statistics workspace 20
Virtual Memory Usage Trends workspace 15
Virtual Memory Statistics workspace 20
Virtual Memory Usage Trends workspace 15
VM Stats attribute group 47

W
weekly update support option 91
Windows agent installation problems 79
workarounds 79
agents 84
remote deployment 87
situations 87
Tivoli Enterprise Portal 86
workspaces
Capacity Usage Information 14
CPU Averages 14
Disk IO Extended Rate 19
Disk IO Rate 19
Disk Usage 15
event 8
list of all 13
more information 13
Network 16
NFS Statistics 16
overview 13
predefined 13
Process 18
Process User Information 18
RPC Statistics 17
Sockets Information 17
System Configuration 19
System Information 20
Users 21
Virtual Memory Statistics 20
Virtual Memory Usage Trends 15

104 IBM Tivoli Monitoring: Linux OS Agent: User’s Guide




IBM Confidential
Printed in USA

SC32-9447-00