IBM Tivoli Monitoring: UNIX OS Agent: User.s Guidewepnet.com.br/docs/main_unix.pdf · SMP CPU attributes ... iv IBM Tivoli Monitoring: UNIX OS Agent: User’s Guide. Tables 1

Tivoli® Monitoring: UNIX OS AgentVersion 6.2.2 Fix Pack 2 (Revised May 2010)

User’s Guide

SC32-9446-03

��

Tivoli® Monitoring: UNIX OS AgentVersion 6.2.2 Fix Pack 2 (Revised May 2010)

User’s Guide

SC32-9446-03

��

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

This edition applies to version 6.2.2 Fix Pack 2 of IBM Tivoli Monitoring: UNIX OS Agent (product number5724-C04) and to all subsequent releases and modifications until otherwise indicated in new editions.

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

Contents

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

Chapter 1. Overview of the MonitoringAgent for UNIX OS . . . . . . . . . . 1IBM Tivoli Monitoring overview. . . . . . . . 1Features of the Monitoring Agent for UNIX OS . . . 1New in this release . . . . . . . . . . . . 2Monitoring Agent for UNIX OS components. . . . 2User interface options . . . . . . . . . . . 3

Chapter 2. Requirements for themonitoring agent . . . . . . . . . . . 5Securing your IBM Tivoli Monitoring installation . . 7Enabling the Monitoring Agent for UNIX OS to runas a non-Administrator user . . . . . . . . . 8

Limitations of starting the agent as anon-Administrator user . . . . . . . . . . 8Setting necessary permissions . . . . . . . 10

Setting up the Monitoring Agent for UNIX OS in acluster environment . . . . . . . . . . . 11Using Agent Management Services . . . . . . 11

Chapter 3. Workspaces reference . . . 13About workspaces . . . . . . . . . . . . 13More information about workspaces . . . . . . 13Predefined workspaces . . . . . . . . . . 13

Agent Management Services workspace . . . . 14Agents' Management Log workspace . . . . . 15Disk Usage workspace. . . . . . . . . . 16File Information workspace . . . . . . . . 17Historical Summarized Availability workspace. . 17Historical Summarized Availability Dailyworkspace . . . . . . . . . . . . . . 17Historical Summarized Availability Hourlyworkspace . . . . . . . . . . . . . . 18Historical Summarized Availability Weeklyworkspace . . . . . . . . . . . . . . 18Historical Summarized Capacity workspace . . 18Historical Summarized Capacity Daily workspace 19Historical Summarized Capacity Hourlyworkspace . . . . . . . . . . . . . . 19Historical Summarized Capacity Weeklyworkspace . . . . . . . . . . . . . . 20Historical Summarized Performance workspace 21Historical Summarized Performance Dailyworkspace . . . . . . . . . . . . . . 21Historical Summarized Performance Hourlyworkspace . . . . . . . . . . . . . . 22Historical Summarized Performance Weeklyworkspace . . . . . . . . . . . . . . 23Network workspace . . . . . . . . . . 23NFS Activity workspace . . . . . . . . . 24Process workspace . . . . . . . . . . . 25System Information workspace . . . . . . . 26

RPC Performance workspace . . . . . . . 27UNIX workspaces . . . . . . . . . . . 28Users workspace . . . . . . . . . . . 29

Chapter 4. Attributes reference . . . . 31About attributes . . . . . . . . . . . . . 31More information about attributes . . . . . . . 31Attribute groups and attributes . . . . . . . . 31Agent Availability Management Status attributes . . 33Agent Active Runtime Status attributes . . . . . 34Alerts Table attributes . . . . . . . . . . . 35All Users attributes . . . . . . . . . . . . 37Configuration Information attributes . . . . . . 37Disk attributes . . . . . . . . . . . . . 39Disk Performance attributes . . . . . . . . . 43File Comparison Group attributes . . . . . . . 45File Information attributes . . . . . . . . . 46File Pattern attributes . . . . . . . . . . . 49Group attributes . . . . . . . . . . . . . 49IP Address attributes . . . . . . . . . . . 50Machine Information attributes . . . . . . . . 50Memory attributes . . . . . . . . . . . . 51Network attributes . . . . . . . . . . . . 56NFS / RPC Statistics attributes . . . . . . . . 63Ping attributes . . . . . . . . . . . . . 71Print Queue attributes . . . . . . . . . . . 72Process attributes . . . . . . . . . . . . 73SMP CPU attributes . . . . . . . . . . . 83Solaris Zones attributes . . . . . . . . . . 87SP2 System attributes . . . . . . . . . . . 89System attributes . . . . . . . . . . . . 97User attributes . . . . . . . . . . . . . 105Disk capacity planning for historical data . . . . 106

Chapter 5. Situations reference. . . . 109About situations . . . . . . . . . . . . 109More information about situations . . . . . . 110Predefined situations . . . . . . . . . . . 110

Agent Management Services situation . . . . 111Disk Usage situations. . . . . . . . . . 111File Information situation . . . . . . . . 112Network situations . . . . . . . . . . 113NFS Activity situation . . . . . . . . . 113Process situations . . . . . . . . . . . 113System Information situations . . . . . . . 114

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

AMS Recycle Agent Instance . . . . . . . 118AMS Reset Agent Daily Restart Count . . . . 118AMS Start Agent action . . . . . . . . . 119AMS Start Agent Instance action . . . . . . 119

© Copyright IBM Corp. 2005, 2010 iii

AMS Stop Agent action . . . . . . . . . 120AMS Start Management action . . . . . . 120AMS Stop Management action . . . . . . 121Sample_kill_Process action . . . . . . . . 121

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

UNIX_CPU_Busy policy . . . . . . . . . 123UNIX_Disk_Space_Full policy . . . . . . . 124UNIX_Virtual_Memory_High policy. . . . . 124

Appendix A. Upgrading for warehousesummarization . . . . . . . . . . . 125Tables in the warehouse . . . . . . . . . . 125Effects on summarized attributes . . . . . . . 125Upgrading your warehouse with limited userpermissions . . . . . . . . . . . . . . 126Types of table changes . . . . . . . . . . 127Table summary . . . . . . . . . . . . . 128Upgrading your warehouse for primary key andtablespace changes . . . . . . . . . . . 128

Affected attribute groups and supporting scripts 129Procedures . . . . . . . . . . . . . 130

Appendix B. Attributes . . . . . . . 135Overview. . . . . . . . . . . . . . . 135Tivoli Enterprise Portal reports and attributes . . 135Cross referencing historical reports and attributes 136

Appendix C. Situations . . . . . . . 137

Appendix D. IBM Tivoli EnterpriseConsole event mapping . . . . . . . 143

Appendix E. Historical data . . . . . 173UNIXCPU historical table . . . . . . . . . 173UNIXDISK historical table . . . . . . . . . 174UNIXDPERF historical table . . . . . . . . 174UNIXFILE historical table . . . . . . . . . 175UNIXNET historical table . . . . . . . . . 175UNIXNFS historical table . . . . . . . . . 176UNIXPS historical table . . . . . . . . . . 178UNIXOS historical table . . . . . . . . . . 179UNIXUSER historical table . . . . . . . . . 182

Appendix F. Monitoring Agent forUNIX data collection . . . . . . . . 183

Appendix G. Troubleshooting . . . . 203Gathering product information for IBM SoftwareSupport . . . . . . . . . . . . . . . 203Built-in troubleshooting features . . . . . . . 203Problem classification. . . . . . . . . . . 204Trace logging . . . . . . . . . . . . . 204

Overview of log file management . . . . . 204Examples of trace logging . . . . . . . . 205Principal trace log files . . . . . . . . . 205Setting RAS trace parameters . . . . . . . 208

Problems and workarounds . . . . . . . . 209Installation and configuration troubleshooting 210Agent troubleshooting . . . . . . . . . 214Tivoli Enterprise Portal troubleshooting . . . 218Troubleshooting for remote deployment . . . 219Workspace troubleshooting . . . . . . . . 219Situation troubleshooting . . . . . . . . 220Take Action command troubleshooting . . . . 224Troubleshooting for UNIX . . . . . . . . 224

Support information . . . . . . . . . . . 225Accessing terminology online . . . . . . . . 225Accessing publications online . . . . . . . . 225Ordering publications . . . . . . . . . . 225Tivoli technical training . . . . . . . . . . 226Tivoli user groups . . . . . . . . . . . . 226

Appendix H. Discovery LibraryAdapter for the monitoring agent . . . 227About the DLA. . . . . . . . . . . . . 227More information about DLAs. . . . . . . . 227UNIX data model class types represented in CDM 227

UNIX class . . . . . . . . . . . . . 227ComputerSystem class . . . . . . . . . 228IpInterface class . . . . . . . . . . . 229IpV4Address class . . . . . . . . . . . 229IpV6Address class . . . . . . . . . . . 229Fqdn class . . . . . . . . . . . . . 230TMSAgent class . . . . . . . . . . . 230

Appendix I. Tivoli Common Reportingfor the monitoring agent . . . . . . 231Utilization Details for Single Resource report . . . 233Utilization Details for Multiple Resources report 237Utilization Heat Chart for Single Resource report 240Top Resources Utilization report . . . . . . . 243Enterprise Resource List report . . . . . . . 246

Appendix J. Documentation library 247IBM Tivoli Monitoring library . . . . . . . . 247

Documentation for the base agents . . . . . 248Related publications . . . . . . . . . . . 249Other sources of documentation . . . . . . . 249

Appendix K. Accessibility . . . . . . 251Navigating the interface using the keyboard . . . 251Magnifying what is displayed on the screen . . . 251

Notices . . . . . . . . . . . . . . 253Trademarks . . . . . . . . . . . . . . 255

Index . . . . . . . . . . . . . . . 257

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

Tables

1. System requirements for the Monitoring Agentfor UNIX OS . . . . . . . . . . . . 5

2. Capacity planning for historical data loggedby component . . . . . . . . . . . 107

3. Time periods and suffixes for summary tablesand views. . . . . . . . . . . . . 126

4. Additional columns to report summarizationinformation . . . . . . . . . . . . 126

5. Primary key and warehouse changes for theMonitoring Agent for UNIX OS . . . . . 128

6. Scripts for affected attribute groups andsummary tables for the Monitoring Agent forUNIX OS . . . . . . . . . . . . . 129

7. UNIX situations. . . . . . . . . . . 1378. Overview of Distributed Monitoring migrated

situations . . . . . . . . . . . . . 1439. Overview of attribute groups to event classes

and slots . . . . . . . . . . . . . 14610. UNIXCPU table column heads and the

corresponding SMP CPU attributes . . . . 17311. UNIXDISK table column heads and the

corresponding Disk Information attributes . . 17412. UNIXDPERF table column heads and the

corresponding Disk Performance attributes . 17413. UNIXFILE table column heads and the

corresponding File Information attributes . . 17514. UNIXNET table column heads and the

corresponding Network attributes. . . . . 17515. UNIXNSF table column heads and the

corresponding NFS and RPC Statisticsattributes . . . . . . . . . . . . . 176

16. UNIXPS table column heads and thecorresponding Process attributes . . . . . 178

17. UNIXOS table column heads and thecorresponding System attributes . . . . . 180

18. UNIXUSER table column heads and thecorresponding User attributes . . . . . . 182

19. Mechanisms used to gather attributes 18320. Information to gather before contacting IBM

Software Support . . . . . . . . . . 20321. Trace log files for troubleshooting agents 20622. Problems and solutions for installation and

configuration. . . . . . . . . . . . 21123. General problems and solutions for

uninstallation . . . . . . . . . . . 21324. Agent problems and solutions . . . . . . 21525. Tivoli Enterprise Portal problems and

solutions . . . . . . . . . . . . . 21926. Remote deployment problems and solutions 21927. Workspace problems and solutions . . . . 21928. Specific situation problems and solutions 22029. Problems with configuring situations that you

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

you solve in the Workspace area . . . . . 22331. Problems with configuration of situations that

you solve in the Manage Tivoli EnterpriseMonitoring Services window . . . . . . 223

32. Take Action commands problems andsolutions . . . . . . . . . . . . . 224

33. Paging and memory issues for a systemadministrator to consider . . . . . . . 224

© Copyright IBM Corp. 2005, 2010 v

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

Chapter 1. Overview of the Monitoring Agent for UNIX OS

The Monitoring Agent for UNIX OS provides you with the capability to monitorand perform basic actions on AIX®, Solaris, and HP-UX operating systems. Thischapter provides a description of the features, components, and interface optionsfor the Monitoring Agent for UNIX OS.

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

You can use IBM Tivoli Monitoring to 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. Byproviding a consolidated view of your environment, the Tivoli Enterprise Portalpermits you to monitor and resolve performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in Appendix J, “Documentationlibrary,” on page 247 for complete information about IBM Tivoli Monitoring andthe Tivoli Enterprise Portal.

Features of the Monitoring Agent for UNIX OSThe Monitoring Agent for UNIX OS offers a central point of management for yourUNIX® server environment. This monitoring agent provides a way to monitor theavailability and performance of all the systems in your enterprise from one orseveral designated workstations. This monitoring agent also provides usefulhistorical data that you can use to track trends and to troubleshoot systemproblems. Information is standardized across all systems (AIX, HP-UX, andSolaris).

The Monitoring Agent for UNIX OS lets you easily collect and analyzeserver-specific information, such as the following:v Operating system and CPU performancev UNIX disk information and performance analysisv Process status analysisv Network performance

The Monitoring Agent for UNIX OS provides the following benefits:

© Copyright IBM Corp. 2005, 2010 1

v Simplifies application and system management by managing applications,platforms, and resources across your system.

v Increases profits by providing you with real-time access to reliable,up-to-the-minute data that allows you to make faster, better informed operatingdecisions.

v Scales and ports to a wide variety of UNIX platforms.v Enhances system performance because you can integrate, monitor, and manage

your environment, networks, console, and mission-critical applications. Forexample, the Monitoring Agent for UNIX OS can alert you when a condition inyour environment meet or exceed the thresholds you set. These alerts notifyyour system administrator to limit and control system traffic. You can view datagathered by the Monitoring Agent for UNIX OS in reports and charts thatinform you of the status of your managed UNIX systems.

v Enhances efficiency by monitoring diverse platforms and networks. Dependingon the configuration of this monitoring agent, you can collect and monitor dataacross platforms. The Monitoring Agent for UNIX OS gathers and filters statusinformation at the managed system rather than at the Hub, eliminatingunnecessary data transmission and sending only data that is relevant to changesin status conditions.

New in this releaseFor version 6.2.2 Fix Pack 2 of the Monitoring Agent for UNIX OS, the followingenhancements have been made:v OS agent availability is now visible from the Agents' Management Log

workspace.v New Take Action commands:

– AMS Recycle Agent Instance– AMS Reset Agent Daily Restart Count

Monitoring Agent for UNIX OS componentsAfter you install the Monitoring Agent for UNIX OS (product code "kux" or "ux")as directed in the IBM Tivoli Monitoring Installation and Setup Guide, you have anenvironment with a client, server, and monitoring agent implementation for IBMTivoli Monitoring that contains the following components:v Tivoli Enterprise Portal client with a Java-based user interface for viewing and

monitoring your enterprise.v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli

Enterprise Monitoring Server and enables retrieval, manipulation, and analysisof data from the monitoring agents.

v Tivoli Enterprise Monitoring Server, which acts as a collection and control pointfor alerts received from the monitoring agents, and collects their performanceand availability data.

v Monitoring Agent for UNIX OS, which collects and distributes data to a TivoliEnterprise Monitoring Server. This component also embeds the AgentManagement Services function.

v Operating system agents and application agents installed on the systems orsubsystems you want to monitor. These agents collect and distribute data to theTivoli Enterprise Monitoring Server.

v Tivoli Data Warehouse for storing historical data collected from agents in yourenvironment. The data warehouse is located on a DB2®, Oracle, or Microsoft®

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

SQL database. To collect information to store in this database, you must installthe Warehouse Proxy agent. To perform aggregation and pruning functions onthe data, install the Warehouse Summarization and Pruning agent.

v Tivoli Enterprise Console event synchronization component for synchronizingthe status of situation events that are forwarded to the event server. When thestatus of an event is updated because of IBM® Tivoli Enterprise Console® rulesor operator actions, the update is sent to the monitoring server, and the updatedstatus is reflected in both the Situation Event Console and the Tivoli EnterpriseConsole event viewer. For more information, see the IBM Tivoli MonitoringInstallation and Setup Guide.

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

Tivoli Enterprise Portal browser client interfaceThe browser interface is automatically installed with Tivoli EnterprisePortal. To start Tivoli Enterprise Portal in your Internet browser, enter theURL for a specific Tivoli Enterprise Portal browser client installed on yourWeb server.

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

IBM Tivoli Enterprise ConsoleEvent management application

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

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


Chapter 2. Requirements for the monitoring agent

This chapter contains information about the requirements for the Monitoring Agentfor UNIX OS.

In addition to the requirements described in the IBM Tivoli Monitoring Installationand Setup Guide, the Monitoring Agent for UNIX OS has the requirements listed inTable 1.

Table 1. System requirements for the Monitoring Agent for UNIX OS

Operating system UNIX

Operating system versions v AIX V5.2, 5.3 (32-bit and 64-bit)

v AIX V6.1 (64-bit)3

v HP-UX 11i v1 PA-RISC (32-bit)1

v HP-UX 11i v2 PA-RISC (64-bit)

v HP-UX 11i v3 PA-RISC (64-bit)

v HP-UX 11i v2 Integrity (64-bit)

v HP-UX 11i v3 Integrity (64-bit)

v Solaris V8 on SPARC 32-bit (requires Solaris patches108434-17, 111721-04, and 109147-07)


v Solaris V9 on SPARC 32-bit (requires Solaris patches111711-11 and 111722-04)


v Solaris V10 on SPARC (32-bit and 64-bit)2

v Solaris V10 on x86-64 (64-bit)2

Memory v 55 MB RAM for the Monitoring Agent for UNIX OS

Disk space The Monitoring Agent for UNIX OS needs 250 MB of diskspace in the file system where it is to be installed throughthe local install method. It needs 184 MB of disk space inthe /tmp file system and 294 MB of disk space in the filesystem where the agent is to be installed through thetacmd createNode command. It needs 380MB of diskspace when it is updated using the command tacmdupdateAgent.

Historical data space varies, depending on the tablescollected. Refer to general installation guidelines for diskspace requirements in the IBM Tivoli MonitoringInstallation and Setup Guide and the section in this guide,“Disk capacity planning for historical data” on page 106.

Disk space requirements can be as high as 1 GB for logfiles, remote deploys and historical data.


Table 1. System requirements for the Monitoring Agent for UNIX OS (continued)

Operating system UNIX

Other requirements v IBM Tivoli Monitoring v6.2.2 agents require at least av6.2.2 hub monitoring server and portal server. IBMTivoli Monitoring v6.2.1 hub monitoring servers andportal servers do not support v6.2.2 monitoring agents.IBM Tivoli Monitoring v6.2.1 monitoring agents workwith both v6.2.1 and v6.2.2 environments.

v A POSIX-compliant threads package must be installedon the monitored machine.

v Ethernet or token ring LAN capability.

v Native X-term monitor for UNIX or HummingbirdExceed X-windows emulators for PCs only.

v For AIX: A compatible version of libperfstat. Forexample, AIX 5.2 requires libperfstat V5.2. Upgrade tothe latest version of libperfstat for the latest memoryfixes.

v Most AIX versions require version 8 of the AIX XLC/C++ runtime. For AIX 5.3. you might need version9. To determine the current level, run the following AIXcommand:

lslpp -l | grep -i xlc

v The monitoring agent must have the permissionsnecessary to perform requested actions. For example, ifthe user ID you used to log onto the system to installthe monitoring agent (locally or remotely) does nothave the permission to perform a particular actionbeing monitored by the monitoring agent (such asrunning a particular command), the monitoring agentwill be unable to perform the requested action.

v Solaris versions require the latest version of SUNWlibC(libC.so.5).

v Veritas VxFS (type 32) is a supported file system for theAIX platform.

Notes:

1. As a prerequisite for the Monitoring Agent for UNIX on HP-UX 11i v1, you shouldhave the minimum patch set:

v PHCO_35743 (PHCO_24400) 'libc cumulative patch'

v PHCO_31923 (PHCO_24402) 'libc cumulative header file patch'

v PHCO_32544 (PHCO_23251) 'libc manpage cumulative patch'

The patches referenced in parenthesis are a minimum level, and the ones on the left ofthe parenthesis are the latest versions.

2. For Solaris 10, the minimum software group required to run this monitoring agent isthe 'End User' group.

3. However, AIX 6.1 running inside Workload Partitions (WPARs) is not supported.

Note: For the most current information about the operating systems that aresupported, see the following URL:http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

When you get to that site, click Tivoli platform and database supportmatrix link at the bottom of the window.


Silent installation: If you are performing a silent installation using aresponse file, see the IBM Tivoli Monitoring Installation and Setup Guide,"Performing a silent installation of IBM Tivoli Monitoring."

Securing your IBM Tivoli Monitoring installationImportant: Run the secureMain utility on any installation, especially thoseinstallations that include the UNIX OS Agent, to prevent privilege escalation.

If you install or upgrade IBM Tivoli Monitoring on a UNIX computer, the filepermissions for many files and directories are set to a very low level, 777. Use thesecureMain utility to change these permissions.

Note: You do not need to be logged in as a root user to run this utility, but youare prompted for the root password when it is required.

The secureMain utility has the following syntax:secureMain [-h install_dir] [-g common_group] [-t type_code [-t type_code]] lock

secureMain [-h install_dir] lock|unlock

where:

-h install_dirThe directory path for the IBM Tivoli Monitoring installation. If thisparameter is not supplied, then the script attempts to determine theinstallation directory.

-g common_groupThe group ID common to all of the user IDs that are used to runcomponents in this installation. The user ID that is used to perform theinstallation must also be a member of the group ID specified. The onlyexception is that the root ID is not required to be a member of the groupID specified.

-t type_codeThe component code belonging to an installed component. You can specifymultiple -t options to create a list of component codes to be processed.

lock Tightens the directory tree permissions. The permissions are set to 750.

If certain products or components that require access by multiple user IDsare installed, a basic permission model of 755 is used. Some specific filesand directories remain at 777 permissions.

unlockLoosens the directory tree permissions.

Note that the unlock parameter does not restore permissions to exactlywhat they were before secureMain lock was run. The unlock parametersets most files and directories back to 777 permissions but not all files anddirectories. Permissions on the common directories shared by applications,and on the server components (monitoring server, portal server, and portalclient) are set to 777. Permissions on most application-specific directoriesare not reset.

For more information, see the IBM Tivoli Monitoring Installation and Setup Guide.

Chapter 2. Requirements for the monitoring agent 7

Enabling the Monitoring Agent for UNIX OS to run as anon-Administrator user

The Monitoring Agent for UNIX OS is capable of running with non-Administratoruser privileges, with some limitations, by changing some agent file permissionsand assuring that the desired running user ID has write access to the necessarydirectories listed below.

The Monitoring Agent for UNIX OS needs to run with Administrator privileges toassure proper remote deploy, and collection of some attributes on the Solarisplatform. To ensure Administrator privileges, the IBM Tivoli Monitoringinstallation sets the owner to Administrator and the Set User-ID bit on the primaryagent binary, kuxagent, to ensure the agent starts up as the Administrator userregardless of which user ID starts the agent.

If you want to start the Monitoring Agent for UNIX OS with permissions ofanother user ID, it is sufficient to remove the Set User-ID (SUID) bits off of thekuxagent binaries to enable running the agent as non-Administrator. The SUIDpermission is set on the user ID and optionally on the group ID, depending on thetarget platform.

The Monitoring Agent for UNIX OS is comprised of the following binaries in thedirectory ITMHOME/platform/ux/bin:v kuxagent (HPUX - User and Group SUID, Solaris - User SUID)v nfs_statv ifstatv stat_daemon (AIX - User-ID SUID)v kux_vmstatv kuxdstat (Installed on Solaris and HPUX only)

There are also the following Agent Management Services binaries to the list:v kcawd (which is in same bin directory as the Monitoring Agent for UNIX OS)v Scripts associated with the Agent Management Services watchdog (also in the

bin directory):– rearmWatchdog.sh– disarmWatchdog.sh– startWatchdog.sh– statusWatchdog.sh– stopWatchdog.sh– agentInstanceCommand.sh

v libkca.a - on AIX systems in the ${interp}/ux/lib directoryv libkca.so - on Solaris systems in the ${interp}/ux/lib directoryv libkca.sl - On HP-UX systems in the ${interp}/ux/lib directory

Limitations of starting the agent as a non-Administrator userOn installation of any other agent by a non-Administrator user, the permissions onthe agent are reset to run the agent with root requirements. You must manuallyreset the permissions as described above.

Remote Deploy:


Remote deploy might not complete or work at all on certain agents that requireAdministrator privileges to install the desired application. Local installation of theagents is recommended or configuring the agent manually post-installation.

Take Actions:

The agent cannot start any actions that require privileged permissions that the userID does not have.

Solaris:

While running as a non-Administrator user, the agent is not able to access/proc/pid/status, and therefore is not able to report the following 9 attributes:v User CPU Time (UNIXPS.USERTIME)v System CPU Time (UNIXPS.SYSTEMTIM)v Total CPU Time (UNIXPS.TOTALTIME)v Thread Count (UNIXPS.THREADCNT)v Child User CPU Time (UNIXPS.CHILDUTIME)v Child System CPU Time (UNIXPS.CHILDSTIME)v Total Child CPU Time (UNIXPS.CHILDTIME)v Wait CPU Time (UNIXPS.WAITCPUTIM)v Terminal (UNIXPS.USERTTY)

Agent Management Services:

Data reported in the Agent Active Runtime Status attribute group, for example thePID, the command line, the CPU, and the memory, might also be affected whenthe non-Administrator user is monitoring agents running as a differentnon-Administrator user.

The watchdog cannot stop or start any agent that it does not have privileges tostop or start. If the OS agent is running as a user other than Administrator but youwould still like to use it to stop and start other agents, the sudo facility on UNIXand Linux provides one way of supporting this capability. In the example thatfollows, the OS agent user is a member of a group called 'itm'. Also, it is assumedthat Agent Management Services will not be prompted for a password to performthese operations and that the target agents' user IDs are 'user1' and 'user2':# sudoers file.## This file MUST be edited with the 'visudo' command as root.# Failure to use 'visudo' may result in syntax or file permission errors# that prevent sudo from running.## See the sudoers man page for the details on how to write a sudoers file.#

# Host alias specification

# User alias specification

# Cmnd alias specification

Cmnd_Alias AMSAGENTSTART = /opt/PAS/ITMTEST/bin/itmcmd agent -[po] [[\:alnum\:]_]*start [[\:alnum\:]][[\:alnum\:]],/opt/PAS/ITMTEST/bin/itmcmd agent start[[\:alnum\:]][[\:alnum\:]]


Cmnd_Alias AMSAGENTSTOP = /opt/PAS/ITMTEST/bin/itmcmd agent -[po] [[\:alnum\:]_]*stop [[\:alnum\:]][[\:alnum\:]],/opt/PAS/ITMTEST/bin/itmcmd agent stop[[\:alnum\:]][[\:alnum\:]]

Cmnd_Alias ITMAMSCMD = AMSAGENTSTART,AMSAGENTSTOP

# Defaults specification

# Runas alias specification

Runas_Alias ITMAGENTIDS = user1,user2

# Same thing without a password%itmusers ALL=( ITMAGENTIDS ) NOPASSWD: ITMAMSCMD

This is just one possible example. The sudo facility has many advanced capabilitiesincluding the ability to audit and to alert administrators of usage of the sudocommand by unauthorized users. See your operating system's sudo man pages formore information.

In the agentInstanceCommand.sh script, replace calls to 'su' with calls to 'sudo'. Forexample:if [ -z "$USR" ]; then$START_CMDelse# su - $USR -c "$START_CMD"

sudo -u $USR $START_CMDfi...if [ -z "$USR" ]; then$STOP_CMDelse

# su - $USR -c "$STOP_CMD"sudo -u $USR $STOP_CMDfi

Ensure that the user1 and user2 users also have write permission to any files towhich an application agent needs to write.

Setting necessary permissionsChanging the permissions requires running systems commands locally on thetarget system:cd ITMHOME/platform/ux/bin/

chmod ug-s ./kuxagent

Note: Do not remove the SUID option from the stat_daemon binary on the AIXplatform.

The agent must also be able to write to the following directories:v ITMHOME/platform/ux/hist/v ITMHOME/platform/ux/itlm/v ITMHOME/platform/ux/bin/v ITMHOME/logs/

Read from the following:v ITMHOME/platform/ux/bin/

v /opt/IBM/ITM/tmaitm6/links/platform/libs/, which is a symbolic link intoITMHOME/tmaitm6/platform/libs


If you plan to run the agent as a non-Administrator user, install the agent as thatnon-Administrator user to set all permissions correctly, or change the owner/groupso the desired target agent runs correctly. Be sure to take into account any otheruser IDs other installed agents require.

Setting up the Monitoring Agent for UNIX OS in a cluster environmentThe IBM Tivoli Monitoring Installation and Setup Guide contains an overview ofclustering. The information provided here is specifically for installing and settingup the Monitoring Agent for UNIX OS in an HACMP™ clustered environment.

The Monitoring Agent for UNIX OS is set up and works as it does in anon-clustered environment. There is a unique cluster configuration prompt for theMonitoring Agent for UNIX OS:Are you installing this product into a clustered environment (Default is: NO):

You should accept the default (NO).

Note: The NO or YES response is case-sensitive.

The shared disks attributes are displayed in all cluster nodes workspace views thatuse the disk-related queries. However, the disk metrics are zero for the nodes thatare not controlling the shared disk because they do not have access to the shareddisk. The highly available IP addresses are not displayed in the network table sincethe highly available IP address is bound to an alias interface. Alias interface IPaddresses are reported in the IP Address attribute group. The relevant statistics forthose IP addresses are reported in the base Interface name in the Network attributegroup since all aliases share one set of statistics for a particular network interface.The base interface can usually be found by removing the colon and number at theend of the aliased interface (for example, Alias = en0:3 Base: en0).

Using Agent Management ServicesThere are two watchdog monitors that run as part of the Monitoring Agent forUNIX. One monitor runs as part of the OS Monitoring Agent process, which isreferred to as the Agent Watchdog. The other watchdog monitor runs as a separateprocess named 'kcawd'. The kcawd process is also called the Agent ManagementServices Watchdog. This watchdog monitor watches the OS Agent as long as itsAvailability Status is showing 'Running' in the Agent's Runtime Status view of theAgent Management Services workspace. No setup or configuration is required.

The Agent Watchdog monitors agent processes other than the OS Agent. By usingthe communication facility of the OS Agent, the monitor can respond to TivoliEnterprise Portal Desktop queries and Take Action commands that are performedagainst these other agent processes. This data is displayed in the AgentManagement Services workspace. In the Tivoli Enterprise Portal Desktop, theAgent Management Services workspace lists the agents that can be monitored bythis watchdog that is running as part of the OS Agent. One of the agents listed inthe workspace is the Agent Management Services Watchdog. Its purpose is tomonitor the OS Agent's availability.

The Agent Management Services Watchdog monitor is responsible for watchingjust the OS Monitoring Agent and restarting it if it goes down. It is enabled bydefault and does not need to be configured. It is started automatically when theMonitoring Agent for UNIX is started. This watchdog does not have acommunication facility, so it cannot report information to the Tivoli Enterprise


Portal or respond to Take Action commands. It is not an agent in itself, but aseparate process that always monitors the OS Monitoring Agent.

You can temporarily disable the Agent Management Services Watchdog by usingthe InstallDir/bin/itmcmd execute ux disarmWatchdog.sh command. Thiscommand disables the Watchdog process for the OS Monitoring Agent and allAgent Management Services managed agents. If there is local administrative workto be performed, and you do not want the auto-restart of the agents to interferewith it, run the InstallDir/bin/itmcmd execute ux disarmWatchdog.sh commandbefore proceeding. When the work is complete, recycle the OS Monitoring Agent toreenable Agent Management Services, or use the InstallDir/bin/itmcmd execute uxrearmWatchdog.sh command.

If you use the itmcmd interface to stop or start an Agent Management Servicesmanaged agent, its watchdog will be disabled if stopping the agent and enabled ifstarting the agent.


Chapter 3. Workspaces reference

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

About workspacesA workspace is the working area of the Tivoli Enterprise Portal applicationwindow. At the left of the workspace is a Navigator that you use to select theworkspace you want to see.

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

This monitoring agent provides predefined workspaces. You cannot modify thepredefined workspaces, but you can create new workspaces by editing them andsaving the changes with a different name.

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

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

Predefined workspacesThe Monitoring Agent for UNIX OS provides the following predefined workspaces,which are organized by Navigator item:

The following list shows how the IBM Tivoli Monitoring: UNIX OS Agentworkspaces are organized.v UNIX OS

– UNIX– UNIX Details– Enterprise UNIX System Summary– Agent Management Services workspace– Agents' Management Log workspace

v Disk Usage– Disk Usage Details– Disk Utilization for Mount Point

v File Information– All Files

v Networkv NFS Activity


v Process– All Processes– Top CPU-Memory %-VSize Details– Solaris Zone Processes

v RPC Performancev System Information

– Solaris System CPU Workload Summary– System Details– Solaris Zones

v Users– User Processes

This agent also includes the following historical workspaces:v Historical Summarized Availabilityv Historical Summarized Availability Dailyv Historical Summarized Availability Hourlyv Historical Summarized Availability Weeklyv Historical Summarized Capacityv Historical Summarized Capacity Dailyv Historical Summarized Capacity Hourlyv Historical Summarized Capacity Weeklyv Historical Summarized Performancev Historical Summarized Performance Dailyv Historical Summarized Performance Hourlyv Historical Summarized Performance Weekly

Some predefined workspaces are not available from the Navigator tree item, butare accessed by selecting the link indicator next to a row of data in a view.Left-clicking a link indicator selects the default workspace associated with thatlink. Right-clicking a link indicator displays all linked workspaces that can beselected. Examples of the workspaces for this monitoring agent include thefollowing:v Application for Process - which includes the Application for Process ID table

view and the Take Action view.v Child Processes - which includes the Child Processes for Process ID table view

and Take Action view.v Command for Process - which includes the Command for Process ID table view

and Take Action view.v Processes for Group Leader - which includes the Processes for Group Leader ID

table view and Take Action view.v Process Resource - which includes the Resource Usage for Process ID table view

and Take Action view. This workspace has a superseded version that displaysqueries with signed 32-bit maximum value (2,147,483,647) and a version with thesame name (minus ‘superseded’) with queries that support values up to signed64-bit max (9,223,372,036,854,775,807).

Agent Management Services workspaceThe Agent Management Services workspace contains views of data collected by theAgent Management Services component of the Monitoring Agent for UNIX.


This workspace includes an Agents' Management Status view, an Agents' RuntimeStatus view, an Agents' Alerts view, and an Agents' Management Definitions view.

Alerts that are seen in the Alerts view in the default workspace are cached for 24hours, by default. The time can be overridden by changing the environmentvariable KCA_CACHE_LIMIT found in the ux.ini file. The variable is specified inhours. This functionality is not available to previous versions of the agents.

Agents' Management Log workspaceThe Agents' Management Log workspace contains a list of monitoring agent logentries filtered on the Agent Management Services component. Use this workspaceto see the operations being executed by Agent Management Services and to keepan audit trail of these operations.

Log messages generated by the physical watchdog are displayed in the Agents'Management Log workspace view. By using these log messages, you can track OSAgent restarts and availability. The limitations of this function are that the physicalwatchdog must be running.

The workspace includes the following operation messages:v Agent added to system - CAP file found.v Agent CAP file initialization completed.v Agent daily restart count reset.v Agent exceeded policy defined CPU threshold.v Agent exceeded policy defined memory threshold.v Agent exceeded restart tries.v Agent initial start.v Agent Management Services watchdog not reliable.v Agent manual start failed.v Agent manual stop failed.v Agent not configured.v Agent not found.v Agent now managed.v Agent now unmanaged.v Agent recycle command received.v Agent removed from system - CAP file removed.v Agent restart disabled - disarm mode activev Agent restart failed.v Agent start command received.v Agent started successfully.v Agent stop command received.v Agent stopped abnormally.v Agent stopped successfully.v Disarm completed successfully.v Rearm completed successfully.

This workspace includes an Agents' Management Log view.

Chapter 3. Workspaces reference 15

Disk Usage workspaceThe Disk Usage workspace is comprised of four views and provides an at-a-glancesnapshot of your disk condition. This workspace has a superseded version thatdisplays queries with signed 32-bit maximum value (2,147,483,647) and a versionwith the same name (minus ‘superseded’) with queries that support values up tosigned 64-bit max (9,223,372,036,854,775,807). The views for this workspace are:

Space Used % - Top TenThis chart provides information on the top ten subdirectories using harddrive space.

Inodes Used % - Top TenThis chart presents a diagrammatic view of the percent of inodes used bythe top ten drive space components.

Disk UtilizationThe Disk Utilization report helps you solve disk-related problems quicklyby providing information on devices with excessive I/O activity and/orlong service times. New data includes average disk queue length andaverage number of processes waiting for service.

Note: By viewing monitored disk input/output (I/O) data collected by theUNIX agents, you can perform the following tasks:v Improve the performance of your UNIX system by quickly and

accurately pinpointing how your system transfers data from diskto memory

v Increase your efficiency by keeping you constantly informed ofhow the disk performs

You monitor the performance of disks in your system to make surethey operate smoothly. Disk performance has a major impact on theoverall functioning of your UNIX system. If disk performance ispoor, it affects jobs that require a large amount of disk I/O, virtualmemory functioning, and the time required to run a program.

Use this report to identify disk performance problems caused byslow rates of data transfer from disk to memory, or high disk usage.

Disk Busy %This graph shows monitored disk input/output (I/O) data collected by theUNIX OS Agents. With this information you can perform the followingtasks:v Improve the performance of your UNIX system by quickly and

accurately pinpointing how your system transfers data from disk tomemory

v Increase your efficiency by keeping you constantly informed of how thedisk performs

The Disk Utilization for Mount Point workspace and the Disk Usage Detailsworkspace can be accessed by right-clicking the Disk Usage navigator item. TheDisk Utilization for Mount Point workspace includes the Disk Utilization forMount Point table view and Take Action view. The Disk Usage Details workspaceincludes the Disk Utilization, Disk Performance, and Disk Inode Views. Both ofthese workspaces have a superseded version that displays queries with signed


32-bit maximum value (2,147,483,647) and a version with the same name (minus‘superseded’) with queries that support values up to signed 64-bit max(9,223,372,036,854,775,807).

File Information workspaceThe File Information workspace is comprised of two views. The views for thisworkspace are:

File Size - Top Ten chartThis graph allows you to quickly see at a glance the files that areconsuming the largest amount of disk space.

File Size - Top Ten tableThis table allows you to quickly see at a glance the files that areconsuming the largest amount of disk space.

The All Files workspace can be accessed by right-clicking on the File Informationnavigator item. The All Files workspace includes the File Size - Top Ten view andthe All Files view.

The Specific File Information workspace can be accessed by right-clicking the linkon either the File Information workspace or the All Files workspace. The SpecificFile Information workspace includes the File Information and Take Actions views.

Historical Summarized Availability workspaceThe Historical Summarized Availability workspace shows the average availabilityof managed resources over the number of months that you specify in the TimeSpan dialog. This workspace consists of the following two graphical views:v Availability by O/S Type (average over months), which shows the percentage of

aggregate time that managed resources were available, grouped by operatingsystem

v Availability by Server (average over months), which shows the percentage ofaggregate time that each server was available

Historical Summarized Availability Daily workspaceThe Historical Summarized Availability Daily workspace shows the availability ofthe server and the system summary for a server by day. This workspace consists ofthe following two graphical views:v Availability (daily), which shows the total percentage of aggregate time that a

server was available, summarized by dayv System Summary (daily), which shows system data such as the following,

summarized by day:– Internet Protocol (IP) address of a monitored system, expressed in dotted

decimal format– Average sum of the System CPU and User CPU attributes expressed as a

percentage– Maximum amount of virtual memory, in kilobytes, that the system was using– Maximum percentage of virtual memory that was used– Average number of processes that were running on a processor– Operating system type and version


Historical Summarized Availability Hourly workspaceThe Historical Summarized Availability Hourly workspace shows the availabilityof the server and the system summary for a server by hour. This workspaceconsists of the following two graphical views:v Availability (hourly), which shows the total percentage of aggregate time that a

server was available, summarized by hourv System Summary (hourly), which shows system data such as the following,

summarized by hour:– Internet Protocol (IP) address of a monitored system, expressed in dotted



Historical Summarized Availability Weekly workspaceThe Historical Summarized Availability Weekly workspace shows the availabilityof the server and the system summary for a server by week. This workspaceconsists of the following two graphical views:v Availability (weekly), which shows the total percentage of aggregate time that a

server was available, summarized by weekv System Summary (weekly), which shows system data such as the following,

summarized by week:– Internet Protocol (IP) address of a monitored system, expressed in dotted



Historical Summarized Capacity workspaceThe Historical Summarized Capacity workspace shows the percentage of systemresources used for the time span that you specify in the Time Span dialog. Thisworkspace consists of the following four graphical views:v Network Capacity (average over months), which shows the following ratio

regarding the time span that you specify in the Time Span dialog: Total numberof times that a frame transmitted by the network interface collided withanother frame to the total number of frames received and transmitted

Note: The Frames_Received and Frames_Transmitted attributes really refer topackets, not frames.

v Processor Utilization (average over months), which shows the averagepercentage of idle CPU time during the sampling period

v Memory Utilization (average over months), which shows the average andmaximum percentages of virtual memory used, ordered by the maximumpercentage of virtual memory used, during the specified time period


v Disk Utilization (average over months), which shows the maximum percentageof space used (expressed as a percentage of the sum of used and available space)on all the system's logical disks during the specified time period. This valueshows the percentage of disk space that is available to non-superusers.

Historical Summarized Capacity Daily workspaceThe Historical Summarized Capacity Daily workspace shows the percentage ofsystem resources used daily. This workspace consists of the following fourgraphical views:v Network Capacity (daily), which shows the following information for each

network instance, summarized by day:– Percentage of total times that a frame transmitted by the network interface

collided with another frame– Number of frames received since the network interface was configured– Total number of eight-bit packets transmitted per second by an interface since

boot timev Processor Utilization (daily), which shows the following information,

summarized by day:– Average percentage of idle CPU time during the sampling period– Percentage of processors' CPU time devoted to running UNIX system kernel

code– Percentage of processors' CPU time devoted to user processes, including time

spent executing user program and library functions but not executing systemcalls

– Wait I/O CPU time during the sampling period, which indicates howeffectively the system or a processor is using disks

v Memory Utilization (daily), which shows the average and maximum percentageof virtual memory used, ordered by the maximum percentage of virtual memoryused, summarized by day

v Disk Utilization (daily), which shows space used on all the system's logicaldisks, including the following details, summarized by day:– Name of the physical disk partition where the file system is mounted (the

physical location of the disk)– Mount point, the path name of the directory to which a file system was

mounted and thus the virtual name for the directory– Total size of a file system, expressed in KB– Maximum amount of disk space used on a file system, expressed in kilobytes– Maximum space used on the file system, expressed as a percentage of the

sum of used and available space– Minimum available space– Maximum percentage of inode space that was allocated to files

Historical Summarized Capacity Hourly workspaceThe Historical Summarized Capacity Hourly workspace shows the percentage ofsystem resources used, summarized by hour. This workspace consists of thefollowing four graphical views:v Network Capacity (hourly), which shows the following information for each

network instance, summarized by hour:– Percentage of total times that a frame transmitted by the network interface

collided with another frame


– Number of frames received since the network interface was configured– Total number of eight-bit packets transmitted per second by an interface since

boot timev Processor Utilization (hourly), which shows the following information for each

processor in the server, summarized by hour:– CPU ID– Average percentage of idle CPU time during the sampling period– Average percentage of system or per processor CPU time devoted to running

UNIX system kernel code– Average percentage of system or per processor CPU time devoted to user

processes, including time spent executing user program and library functionsbut not executing system calls

– Average wait I/O CPU time during the sampling period, which indicateshow effectively the system or a processor is using disks

– Average number of processes that were waiting to be run or were running ona processor

– Average number of processes that were idle, or in sleep state, or in a stoppedstate

– Average number of zombie processesv Memory Utilization (hourly), which shows the average and maximum

percentage of virtual memory used, ordered by the maximum percentage ofvirtual memory used, summarized by hour

v Disk Utilization (hourly), which shows space used on all the system's logicaldisks, including the following details, summarized by hour:– Name of the physical disk partition where the file system is mounted (the

physical location of the disk)– Mount point, the path name of the directory to which a file system is


sum of used and available space– Minimum available space– Maximum number and maximum percentage of inode space that was

allocated to files– Minimum number of inodes that was available on your file system, which can

help you take corrective action such as freeing unneeded space or deletingtemporary files

Historical Summarized Capacity Weekly workspaceThe Historical Summarized Capacity Weekly workspace shows the percentage ofsystem resources used, summarized by week. This workspace consists of thefollowing four graphical views:v Network Capacity (weekly), which shows the total number of times that a frame

transmitted by the network interface collided with another frame, summarizedby week

v Processor Utilization (weekly), which shows the average percentage of idle CPUtime, summarized by week


v Memory Utilization (weekly), which shows the average and maximumpercentage of virtual memory used, ordered by the maximum percentage ofvirtual memory used, summarized by week

v Disk Utilization (weekly), which shows space used on all the system's logicaldisks, including the following details, summarized by week:– Name of the physical disk partition where the file system was mounted (the

physical location of the disk)– Mount point, the path name of the directory to which a file system was


sum of used and available space– Minimum available space– Maximum percentage of inode space that was allocated to files

Historical Summarized Performance workspaceThe Historical Summarized Performance workspace shows the averageperformance of system resources for the time span that you specify in the TimeSpan dialog. This workspace consists of the following five graphical views:v Network Interface Performance (average over months), which shows (calculated

per second) the total number of frames received plus frames transmitted for allnetwork interfaces since the network interface was configured, during the timespan that you specify in the Time Span dialog

v Load Average (average over months), which shows the average of the averagenumber of processes in the UNIX kernel run queue during a 15-minute interval,during the specified time period

v Processor Performance (average over months), which shows the averagepercentage of time that the CPU was not processing instructions, during thespecified time period

v Memory Performance (average over months), which shows the average rate ofpage in and page out for the system during the specified time period

v Disk Performance (average over months), which shows the maximum percentagethat the disk was busy during the specified time period

Historical Summarized Performance Daily workspaceThe Historical Summarized Performance Daily workspace shows the averageperformance of system resources, summarized by day. This workspace consists ofthe following five graphical views:v Network Interface Performance (daily), which shows the following information

for each network interface, summarized by day:– Total number of frames received– Total number of frames transmitted– Total input errors– Total output errors– Total number of times during the sampling period that a frame transmitted

by the network interface collided with another frame


v Load Average (daily), which shows the average of the average number ofprocesses in the UNIX kernel run queue during a 15-minute interval and theaverage percentage of time that the CPU was not processing instructions,summarized by day

v Processor Performance (daily), which shows the following information,summarized by day:– Average percentage of idle CPU time during the sampling period– Average percentage of processors' CPU time devoted to running UNIX system

kernel code– Average percentage of processors' CPU time devoted to user processes,

including time spent executing user program and library functions but notexecuting system calls

– Average wait I/O CPU time during the sampling period, which indicates howeffectively the system or a processor is using disks

v Memory Performance (daily), which shows the average rate of page in and pageout for the system, summarized by day

v Disk Performance (daily), which shows the following information, summarizedby day:– Name of the disk– Maximum percentage of time a disk was busy transferring data, which can

indicate whether a process is I/O bound– Average number of disk requests outstanding during the sampling period– Average amount of disk time used in milliseconds over the sampling period– Average time waiting for disk access, expressed in milliseconds– Maximum number of total kilobytes per second written to and read from all

local disks during a specified sampling period

Historical Summarized Performance Hourly workspaceThe Historical Summarized Performance Hourly workspace shows the averageperformance of system resources, summarized by hour. This workspace consists ofthe following five graphical views:v Network Interface Performance (hourly), which shows the following information

for each network interface, summarized by hour:– Total number of frames received– Total number of frames transmitted– Total input errors– Total output errors– Total number of times during the sampling period that a frame transmitted

by the network interface collided with another framev Load Average (hourly), which shows the average of the average number of

processes in the UNIX kernel run queue during a 15-minute interval and theaverage percentage of time that the CPU was not processing instructions,summarized by hour

v Processor Performance (hourly), which shows the following information for eachprocessor, summarized by hour:– Average percentage of idle CPU time during the sampling period– Average percentage of processors' CPU time devoted to running UNIX system

kernel code


– Average percentage of processors' CPU time devoted to user processes,including time spent executing user program and library functions but notexecuting system calls

– Average wait I/O CPU time during the sampling period, which indicates howeffectively the system or a processor is using disks

– Average numbers of processes that were waiting to be run or were runningon a processor

– Average numbers of processes that were idle, or in sleep state, or in a stoppedstate

– Average number of zombie processesv Memory Performance (hourly), which shows the average rate of page in and

page out rates for the system, summarized by hourv Disk Performance (hourly), which shows the following information, summarized

by hour:– Name of the disk– Maximum percentage of time a disk was busy transferring data, which can

indicate whether a process is I/O bound– Average number of disk requests outstanding during the sampling period– Average amount of disk time used in milliseconds over the sampling period– Average time waiting for disk access, expressed in milliseconds– Maximum number of total kilobytes per second written to and read from all

local disks during a specified sampling period

Historical Summarized Performance Weekly workspaceThe Historical Summarized Performance Weekly workspace shows the averageperformance of system resources, summarized by week. This workspace consists ofthe following five graphical views:v Network Interface Performance (weekly), which shows (calculated per second)

the total number of frames received plus frames transmitted for all networkinterfaces since the network interface was configured, summarized by week

v Load Average (weekly), which shows the average of the average number ofprocesses in the UNIX kernel run queue during a 15-minute interval,summarized by week

v Processor Performance (weekly), which shows the average percentage of timethat the CPU was not processing instructions, summarized by week

v Memory Performance (weekly), which shows the average rate of page in andpage out for the system, summarized by week

v Disk Performance (weekly), which shows the maximum percentage that the diskwas busy, summarized by week

Network workspaceThe Network workspace is comprised of four views. This workspace has asuperseded version that displays queries with signed 32-bit maximum value(2,147,483,647) and a version with the same name (minus ‘superseded’) withqueries that support values up to signed 64-bit max (9,223,372,036,854,775,807). Theviews for this workspace are:

Errors and collisionsThe bar chart displays network input errors, output errors, and collisionsallowing you a quick glance at potentially severe network problems.


Packet TransfersThe Packet Transfers chart displays graphically the frames received andframes transmitted on each network card.

The Received Count (Frames) and Transmitted Count (Frames) show theraw frame counts for the interface. Frames and packets are not necessarilythe same thing.

System administrators might define the interface so that multiple framesare sent or received in a packet. The network report and the networkattributes display frame counts.

Network Information reportThe Network Info report contains monitored data that helps you see youroverall network performance, and supplies you with information aboutnetwork interfaces on your monitored UNIX systems.

Using this real-time network information, you can perform the followingtasks:v Fine-tune your network by allowing you to pinpoint bottlenecks in

network traffic so your system administrator can reroute jobs to avoidthem

v Increase system productivity by providing you with the information thatlets you determine how network resources can be used more efficiently

The UNIX Network report contains numerical attributes that report thechanging interface workload throughout each workday. This informationallows your system administrator to see the ebb and flow of networktraffic.

The UNIX Network report helps you perform the following tasks:v See how much data your network interfaces transmit and receivev Identify network interfacesv Determine whether the interfaces are operationalv View the amount of data traffic that flows through interfacesv Justify rerouting network data traffic, if necessaryv Measure errors in frame transmission and collisions

IP AddressesThe view displays IP Address information.

NFS Activity workspaceThis workspace is comprised of four views. The views for this workspace are:

NFS Server StatisticsThe NFS Server Statistics chart graphically displays the activity for thefollowing attributes:v NFS Server Callsv NFS Server Calls Rejectedv NFS Server Null Callsv NFS Server lookups

NFS Client StatisticsThe NFS Client Statistics chart graphically displays the activity for thefollowing attributes:v NFS Client Calls


v NFS Client Calls Rejectedv NFS Client Null Callsv NFS Client lookups

NFS Server Activity reportNFS Server Activity attributes report on NFS calls to the managed system.The agent reports these calls only when the managed system is an NFSserver.

NFS Client Activity reportNFS Client Activity attributes report on calls from the managed system toNFS servers.

NFS RPC Statistics group is a single-instance attribute group. You can mix theseattributes with those of any other single-instance group.

Process workspaceThe Process workspace is comprised of four views. The views for this workspaceare:

Top CPU Time % ProcessesThis chart displays CPU Percent for the processes utilizing the highestCPU time.

Memory % - Top TenThis chart displays graphically the Memory Percent attribute for the topten processes utilizing memory.

Top CPU Time % ProcessesThe Top CPU Time Processes report provides detailed information aboutthe top CPU processes currently running. You can view this information inthe detail report columns.

The Top CPU Time Processes report help you perform the following tasks:v Solve process problems quickly by giving you information you need to

pinpoint problem processes and their owners.v Improve system performance by providing you with real-time

information on which users and what processes are using the system.

Note: When monitoring process information, pay special attention to thefollowing attribute values.v Large values in the CPU Utilization column indicate a

CPU-intensive process. These values result in a lower processpriority. Small values indicate an I/O intensive process. Thesevalues result in a higher process priority.

v A value greater than 100 indicates a process is consuming a largeamount of the CPU. If this value is high, check the ExecutionState column to see if the process is running, and the Timecolumn to see how long the process has been running.

The CPU Utilization value is computer-dependent and also variesaccording to the version of the UNIX operating system running.

Virtual Size - Top TenThe Virtual Size - Top Ten graph provides information about virtualmemory process usage by the top ten processes.


The All Processes, the Solaris Zone Processes, and the Top CPU-Memory %-VSizeDetails workspaces can be accessed by right-clicking the Process navigator item.The All Processes workspace includes the Top CPU Time, Memory %, Processes,and Virtual Size views. The Solaris Zone Processes workspace includes the TopCPU Time in zone, Top Virtual Size in zone, and Top Memory % used in zoneviews. The Top CPU-Memory %-VSize Details workspace includes the Top CPUTime, Top Virtual Size, Top Memory % Used, and Take Action views.

The following workspaces are linked workspaces available for all the workspacesin the Process navigator item. They can be accessed by selecting the link indicatornext to a row of data in a view. Left-clicking a link indicator selects the defaultworkspace associated with that link. Right-clicking a link indicator displays alllinked workspaces that can be selected.v Application for Processv Child Processesv Command for Processv Process Resourcev Processes for Group Leader

System Information workspaceThis workspace is comprised of five views. The views for this workspace are:

Virtual Memory AvailabilityThis chart displays the following attributes:v Virtual Memory Percent Usedv Virtual Memory Percent Available

Memory shortages can cause system performance problems. If systemperformance is poor, excessive page-outs and swapping activity canindicate memory problems. By viewing the monitored virtual memory datacollected by IBM Tivoli Monitoring for UNIX on a remote system, you canperform the following tasks:v Determine whether performance degradation is caused by a lack of

virtual memory.v View monitored data collected from remote systems either as a report or

a chart.

Page Fault StatisticsThis chart displays page fault attributes to provide an at-a-glance view ofproblems with virtual memory faults. The attributes displayed are:v Page Faultsv Page Scan Ratev Page Reclaimsv Pages Paged Inv Pages Paged Outv Page Insv Page Outs

Total Real and Virtual MemoryThe Total Real and Virtual Memory chart graphically displays vitalinformation about system memory. The attributes displayed are:v Total Real Memoryv Free Memory


v Total Virtual Memory

The chart gives you operating system and memory information on yourUNIX systems. By viewing the monitored system data collected by IBMTivoli Monitoring: UNIX OS Agent on remote systems, you can performthe following tasks:v Improve system performance by helping you identify the configuration

of your systems and check their current activity levelsv View monitored data collected from remote systems either as a report or

as a chart.

CPU %The CPU % pie chart helps you improve system CPU performance, andyou can use it to identify and monitor system CPU activity. The CPU %chart displays percentages of processor activity taking place on eachmonitored UNIX system. Use this report to perform the following tasks:v Improve system CPU performance by helping you identify managed

systems that consume large amounts of CPU timev Increase system throughput by identifying user demands on CPUs,

allowing you to allocate these demands among several CPUs on yoursystem

v Identify managed systems with I/O bottlenecks caused by waits forCPU time

v Identify managed systems with CPU bottlenecks caused by high CPUutilization

Use the CPU % chart to check for problems, such as:v Managed systems with high CPU utilizationv Imbalances between user and system CPU demandsv Long CPU waits caused by I/O bottlenecks

Note: There is a limit of up to 9 CPU per page. You can either modify theworkspace or select a second page.

Load AveragesThe Load Average chart gives you load average information on your UNIXsystems. Load average refers to the average number of processes in theUNIX kernel run queue during an interval. By viewing the monitoredsystem data collected by IBM Tivoli Monitoring: UNIX OS Agent onremote systems, you can improve system performance by helping youidentify the configuration of your systems and check their current activitylevels.

The Solaris System CPU Workload workspace, the Solaris Zones workspace, andthe System Details workspace can be accessed by right-clicking on the SystemInformation navigator item. The Solaris System CPU Workload workspace includesthe Solaris System CPU Workload table chart, the Solaris System CPU WorkloadStatistics bar chart, and the Take Action view. The Solaris Zones workspaceincludes the Solaris Zones and Take Action views. The System Details workspaceincludes System CPU, System Virtual Memory, Systems, System Load Average,System Workload, and System Cache and Buffers views.

RPC Performance workspaceThe RPC Performance workspace is comprised of four views. The views for thisworkspace are:


RPC Server StatisticsThis chart graphically displays the following attributes:v RPC Client Calls Rejected by Serverv RPC Server Times RPC Packet Unavailablev RPC Server Packets Too Shortv RPC Server Packets with Malformed Header

RPC Client StatisticsThis chart graphically displays the following attributes:v RPC Client Calls Rejected by Serverv RPC Client Calls Retransmittedv RPC Client Replies Not Matching Callsv RPC Client Calls Timed Out

RPC Server Performance reportThis table contains statistics attributes that refer to Remote Procedure Call(RPC) Server call rates and errors. The RPC Server attributes report onRPC calls made to the managed system.

RPC Client Performance reportThis table contains statistics attributes that refer to Remote Procedure Call(RPC) Client call rates and errors. The RPC Client attributes report on callsmade by the managed system to RPC Servers.

UNIX workspacesThree UNIX workspaces are available at the top level of the system tree. You canaccess these workspaces by right-clicking the UNIX navigator tree item. Use theseworkspaces to obtain a quick at-a-glance view of your UNIX systems. The threeworkspaces are:v UNIXv UNIX Detailv Enterprise UNIX System Summary

UNIX workspaceThe UNIX workspace is comprised of the following views:

Top CPU Time (bar chart)

Memory % - Top Ten (bar chart)

Disk Space Used % - Top Ten (bar chart)

Virtual Size - Top Ten (bar chart)

Virtual Memory Availability (bar chart)

UNIX Detail workspaceThe UNIX Detail workspace is comprised of the following views:

Top CPU Time - Processes (table)

Top Virtual Size (table)

Top Memory % (table)


Top Space Used % (table)

System Virtual Memory (table)

Enterprise UNIX System Summary workspaceThis workspace requires that the hub and remote Tivoli Enterprise MonitoringServers are seeded with the IBM Tivoli Monitoring: UNIX OS Agent seed data.This workspace displays a summary of all UNIX systems on-line with thefollowing views:

UNIX System Summary Table

UNIX System Memory Summary Table

Memory Usage Summary (bar chart)

Load Average Summary (bar chart)

CPU % Summary (bar chart)

Users workspaceThe Users workspace is comprised of two views. The views for this workspace are:

Users ReportThe Users Report attributes refer to user characteristics such as idle time,user name, location, and login time. By viewing the monitored user datacollected by IBM Tivoli Monitoring: UNIX OS Agent on remote systems,you can perform the following tasks:v Troubleshoot problems and solve them quickly using reliable, real-time

information about users and the programs they use.v Use this information to pinpoint problem processes, and the user(s)

responsible for them. Your system administrator can then eliminate theprocess, contact the user responsible for the problem, and take correctiveaction.

You can use this report to obtain information on individual users and theprocesses they use, and check for problems caused by user activity.

Take ActionUse the Take Action view to perform a selected action on select systemdestinations.

The User Processes workspace can be accessed by right-clicking this workspace.This workspace includes the Processes for Users ID and Take Action views.



Chapter 4. Attributes reference

This chapter contains information about the following topics:v Overview of attributesv References for detailed information about attributesv Descriptions of the attributes for each attribute group included in this

monitoring agentv Disk space requirements for historical data

About attributesAttributes are the application properties that are measured and reported by theMonitoring Agent for UNIX OS, such as the amount of memory usage and themessage ID.

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

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

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

Some of the attributes in this chapter are listed twice, with the second attributehaving a "(Unicode)" designation after the attribute name. These Unicode attributeswere created to provide access to globalized data.

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

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

Attribute groups and attributesAn attribute is a characteristic of a managed object (node). For example, DiskName is an attribute for a disk, which is a managed object.

Use IBM Tivoli Monitoring: UNIX OS Agent attributes to build situations thatmonitor the performance of your UNIX network managed systems. When the


values of the selected attributes in a situation exceed their threshold settings, theagent posts an alert to the Tivoli Enterprise Portal console notifying you of aproblem.

Note: Some of the attributes have the enumerations, Value Exceeds Maximum andValue Exceeds Minimum. The Tivoli Enterprise Monitoring Server allowsonly signed integers, so the maximum is 2147483647 and the minimum is-2147483648. If the agent has a value bigger or smaller than these, it iscapped with these enumerations.

Workspaces and attributesThe IBM Tivoli Monitoring: UNIX OS Agent workspaces provide real-timeinformation on many of the attributes. Each column in a table view corresponds toan attribute. And each data series in a chart corresponds to an attribute.

Groups of attributesEach attribute belongs to an attribute group. The attribute group includesattributes that are related. Each attribute item stores data for a particular propertyof an attribute group.

The following are the attribute groups for IBM Tivoli Monitoring: UNIX OS Agent.The groups are collected in attribute tables that are designated in brackets [ ] afterthe group name.v Agent Availability Management Status [KUXPASMGMT]v Agent Active Runtime Status [KUXPASSTAT]v Alerts Table [KUXPASALRT]v All Users Group [UNIXALLUSR]v Configuration Information [KUXPASCAP]v Disk Information [UNIXDISK]v Disk Performance [UNIXDPERF]v File Comparison Group [UNIXFILCMP]v File Information [FILEINFO]v File Pattern [UNIXFILPAT]v Group [UNIXGROUP]v IP Address [UNIXIPADDR]v Computer Information [UNIXMACHINE]v Memory [UNIXMEM]v Network [UNIXNET]v NFS/RPC Statistics [UNIXNFS]v Ping Group [UNIXPING]v Print Queue [UNXPRINTQ]v Process [UNIXPS]v SMP_CPU [UNIXCPU]v Solaris Zones [UNIXSOLZON]v System group [UNIXOS]v User [UNIXUSER]


IBM Tivoli Monitoring provides other attribute groups that are available to allmonitoring agents, for example Universal Time and Local Time. The attributes inthese common attribute groups are documented in the Tivoli Enterprise PortalHelp.

Platforms supportedAttributes display information on all of the platforms below unless notedotherwise in the attribute usage information.v AIXv HP-UXv Solaris

Assignment of valuesNot all UNIX systems display all UNIX attributes. For example, AIX systems donot display the CPU ID on which the process is running. If your system does notdisplay a value for a certain attribute, you see Not_Available in fields relating tothat attribute. A value of -1, or Not_Available, means that this information is notcurrently being collected for the UNIX platform on which your system is running.For example, HP-UX and Solaris systems do not display Busy Percent information.

A value of -2, or Not_Collected, is an indication that an error occurred.

A value of either 9,223,372,036,854,775,807, or Value_Exceeds_Maximum, and-9,223,372,036,854,775,808, or Value_Exceeds_Minimum, indicates that the value istoo large and the Tivoli Enterprise Monitoring Server cannot handle the valuewithout wrapping it. These values are then capped at either9,223,372,036,854,775,807 or -9,223,372,036,854,775,808.

Agent Availability Management Status attributesUse Agent Availability Management Status attributes to view the currentmanagement status of an agent relative to Agent Management Services.

Agent Management Status The watched agent management status. The followingvalues are valid: Unmanaged (0), Managed (1), Watchdog (2). A value of 'Managed'means that the agent is under the management of Agent Management Services. Avalue of 'Unmanaged' means it is known, but that the agent is not under themanagement of Agent Management Services.

Agent Name The watched agent name.

Agent Type The watched agent type. The following values are valid: Unknown (0),ITM_Unix (1), Console (2), Windows_Service (3), Discover_ITM (4), Discover_Bin(5), Linux_Service (6), ITM_Windows (7).

Agent Version The version, release, and modification information for the agent.

Build Number The build number information for the agent.

Manager Type The enum defining the manager type. The following values arevalid: Unknown (0), Not_Managed (1), Agent_Management Services (2), Watchdog(3), External (4). A value of 'Agent Management Services' means that AgentManagement Services is responsible. A value of 'NotManaged' means that theagent is not under availability monitoring by any application. A value of

Chapter 4. Attributes reference 33

'Externally' means that some other application besides Agent Management Servicesis responsible for availability monitoring of the agent, for example Tivoli SystemAutomation or Windows service control manager.

Operating System The operating system identification. The following values arevalid: Unknown (0), Windows (1), Linux (2), UNIX (3).

Server Name The origin node of the collecting agent.

Service Name The Windows or Linux service name of the agent.

Timestamp The date and time the Tivoli Enterprise Monitoring Server samples thedata. This information is displayed in the standard 16-character date/time format(CYYMMDDHHMMSSmmm), where:

C Century (0 for 20th, 1 for 21st)YY YearMM MonthDD DayHH HourMM MinuteSS Secondmmm Millisecond

Use simple text strings as described above. For example, 1101009130500000expresses October 9, 2010, 1:05:00 pm.

Agent Active Runtime Status attributesUse the Agent Active Runtime Status attributes to view the current availabilitystatus of an agent: Running, Not present, Unknown, Stopped, Manually Stopped.You can view the frequency at which the agent's availability and runtimeproperties are queried and also the agent's Daily Restart Count.

Agent Availability Status The watched agent availability status. The followingvalues are valid: Unknown (0), Not_found (1), Stopped (2), Start_Pending (3),Running (4), Manually_Stopped (5), Stop_Pending (6), Not_configured (7). Foragents that have an Availability Status of 'Running', use the attribute group to seeruntime properties of the agent such as its Process ID and Thread Count.

Agent Host Name The host name of the agent.


Agent Type The watched agent type. The following values are valid: Unknown (0),ITM_Unix (1), Console (2), Win_Service (3), Discover_ITM (4), Discover_Bin (5),Linux_Service (6), ITM_Windows (7).

Check Frequency The frequency to check status in seconds.

Command Line The command line.

Daily Restart Count The restarts within a period of a day.


Instance Name The instance name of the running managed IBM Tivoli Monitoringagent.

IP Address The IP address of the agent.

Last Health Check The last health check timestamp.

Number of Threads The thread count.


Page Faults Per Second The page faults per second.

Parent Process ID The parent process identification.

Process ID The process ID.

Process Name The process name.

Process System CPU (Percent) The system CPU.

Process User CPU (Percent) The user CPU time.

Resident Size The size of the resident process.





Total Size (Pages) The total memory size in pages.

User Name The user name of the running managed agent.

Alerts Table attributesUse the Alerts Table attributes to view exceptional Critical, Warning, orInformational alerts sent by Agent Management Services. You can view these for 24hours or until the OS agent is recycled. These events have to do with the operationof Agent Management Services or conditions affecting its ability to manage agents.The following alerts are included:


v Availability policy removedv Agent abnormally stoppedv Agent restart failedv Agent exceeded restart countv Agent not found.v Agent overutilizing memoryv Agent overutilizing CPUv Managed agent removed from systemv Unmanaged agent removed from systemv Agent start failedv Agent status check script failed


Agent Status The agent status. The following values are valid: Unknown (0),Not_found (1), Stopped (2), Start_Pending (3), Running (4), Manually_Stopped (5),Stop_Pending (6), Not_configured (7).


Alert Details The alert message details.

Alert Message The alert message. The following values are valid:Availability_policy_removed (1), Managed_agent_removed_from_system (2),Unmanaged_agent_removed_from_system (3), Agent_abnormally_stopped (4),Agent_exceeded_restart_count (5), Agent_restart_failed (6),Agent_overutilizing_memory (7), Agent_overutilizing_CPU (8),Agent_manual_stop_failed (9), Agent_Management_Services_watchdog_not_reliable(11).


Process ID The process ID.

Process Name The process name.






All Users attributesThe All Users attributes refer to user characteristics such as user ID and usersessions.

Duplicate User Name True if the user name is listed more than once in/etc/passwd. True if no password is assigned to the user. The following values arevalid: Not Collected, Not Available, False and True.

Name The full name of a user.

No Password True if no password is assigned to the user. The following values arevalid: Unknown, False, Not Collected, and True.

System Name The managed system name. The form should be hostname:agent_code.

Examples include spark:KUX or deux.raleigh.ibm.com:KUX.

In workspace queries, this attribute should be set equal to the value $NODE$ inorder to populate the workspace with data. This attribute is generally not includedin situations, unless there is a need to customize the situation for a specificmanaged system.

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

User ID The numeric ID the system assigned to a user. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

User Sessions The number of login sessions this user currently has established.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Configuration Information attributesUse Configuration Information attributes to monitor agent configuration such asMemory Threshold and Operating System.

Agent Name The sub agent name.

Agent Path The fully qualified path to the agent.


Check Frequency The frequency to check status in seconds.

Configuration Script The agent configuration script.


% CPU Threshold The amount of CPU the agent process is allowed to consumebefore Agent Management Services restarts it.

Dependencies Any agents, monitored by Agent Management Services, that mustbe started before the target agent can be started.

Kernel Release The version of Linux kernel that a particular CAP file stanzaapplies to, if that level of granularity is needed.

Manager Type The enum defining the manager type. The following values arevalid: Unknown (0), Not_Managed (1), Agent_Management Services (2), Watchdog(3), External (4).

Maximum Daily Restarts The maximum number of restarts allowed. The clockbegins at midnight.

Memory Threshold The amount of working set memory the agent process isallowed to consume before Agent Management Services restarts it.

Memory Unit The maximum memory allowed units. The following values arevalid: Bytes (0), KB (1), MB (2), GB (3).

Operating System The operating system that a particular CAP file stanza appliesto. The following values are valid: Unknown (0), Windows (1), Linux (2), andUNIX (3).

Operating System Name The operating system name that a particular CAP filestanza applies to, if that level of granularity is required.

Operating System Version The operating system version that a particular CAP filestanza applies to, if that level of granularity is required.

PAS_ID The internal ID assigned to an agent by Agent Management Services.

Policy File Timestamp The date and time of CAP file.

Process Name The process name of the managed agent.


Service Name The Windows or Linux service name of an agent.

Startup Script The agent startup script.

Status Script The agent status script.

Stop Script The agent stop script.


C Century (0 for 20th, 1 for 21st)YY YearMM MonthDD Day


HH HourMM MinuteSS Secondmmm Millisecond


Disk attributesThe Disk attributes refer to disk characteristics such as inode size, inodes used,mount point, and space available. Entries for the Disk Information table(UNIXDISK) reports file systems of the following types:v AIX systems

– JFS - Journaled File System– JFS2 - Enhanced Journaled File System– Veritas VxFS

v Solaris systems– ufs - UNIX File System– tmpfs - Temp File System– vxfs - Veritas File System– bfs -Boot File System– lofs - loopback File System– zfs - Zettabyte File System

v HPUX systems– All File Systems except NFS

Inodes Available Percent The percentage of inode space currently not in use. Note:the value -1 indicates Not Available and -2 indicates Not Collected.

Inodes Free The number of inodes currently available on your file system. Use thisattribute to avoid a pending crisis. Corrective action might include freeing upunneeded space or deleting temporary files. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 9223372036854775807 indicatesValue_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

Inodes Free (Superseded) The number of inodes currently available on your filesystem. Use this attribute to avoid a pending crisis. Corrective action might includefreeing up unneeded space or deleting temporary files. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Example: Disk inode space is usually a high number, so the percentage of inodespace to disk space must also be a high number. If the value for Inodes Free is lessthan 100, this is a critical condition. Notify your system administrator immediately.If the value for Inodes Percent is above 30%, delay taking corrective action.

Inodes Used The number of inodes currently allocated to files on the file system.Note: the value -1 indicates Not Available, -2 indicates Not Collected,9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.


Inodes Used (Superseded) The number of inodes currently allocated to files on thefile system. This value equals the Inode Size value minus the Inodes Free value.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Inodes Used Percent The percentage of inode space currently allocated to files.Valid entries are whole numbers up to 100, such as 85 for 85%. Note: the value -1indicates Not Available and -2 indicates Not Collected.

Mount Point The path name of the directory to which a file system is mounted.This is the virtual name for the directory. Valid entries are up to 32 letters ornumbers representing a directory path.

Mount Point (Unicode) The path name of the directory to which a file system ismounted. This is the virtual name for the directory.

Name The name of the physical disk partition where the file system is mounted.This is the physical location of the disk. Valid entries are up to 32 letters ornumbers.

Name (Unicode) The name of the physical disk partition where the file system ismounted. This is the physical location of the disk.

Size (KBytes) The total size of a file system, expressed in kilobytes with 64 bitprecision. Note: the value -1 indicates Not Available, -2 indicates Not Collected,9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.

Size (KBytes) (Superseded) The total size of a file system, expressed in kilobytes.For example, 1000000 represents one gigabyte. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Size (GigaBytes) The total size of a file system, expressed in gigabytes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 9223372036854775807indicates Value_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

Size (GB) (Superseded) The total size of a file system, expressed in gigabytes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Size (MegaBytes) The total size of a file system, expressed in megabytes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 9223372036854775807indicates Value_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

Size (MB) (Superseded) The total size of a file system, expressed in megabytes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Space Available (KBytes) The amount of unused space currently available tonon-superusers on a file system, expressed in kilobytes. For example, 40000


represents 40 megabytes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.

Space Available (KB) (Superseded) The amount of unused space currentlyavailable to non-superusers on a file system, expressed in kilobytes. For example,40000 represents 40 megabytes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

This disk space does not include any space which is reserved for supersuser. A lowvalue in this column, relative to the disk size, alerts you to critical disk spaceconditions.

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

Space Available (GigaBytes) The amount of disk space currently available tonon-superusers on a file system, expressed in gigabytes. Note: the value -1indicates Not Available, -2 indicates Not Collected, 9,223,372,036,854,775,807indicates Value_Exceeds_Maximum, and -9,223,372,036,854,775,808 indicatesValue_Exceeds_Minimum.

Space Available (GigaBytes) (Superseded) The amount of disk space currentlyavailable to non-superusers on a file system, expressed in gigabytes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Space Available (MegaBytes) The amount of disk space currently available tonon-superusers on a file system, expressed in megabytes. Note: the value -1indicates Not Available, -2 indicates Not Collected, 9223372036854775807 indicatesValue_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

Space Available (MegaBytes) (Superseded) The amount of disk space currentlyavailable to non-superusers on a file system, expressed in megabytes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Space Available Percent The percentage of space available. Valid entries are wholenumbers up to 100, such as 10 for 10%. Note: the value -1 indicates Not Availableand -2 indicates Not Collected.

Space Used (KBytes) The amount of disk space currently in use on a file system,expressed in kilobytes. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.

Space Used (KB) (Superseded) The amount of disk space currently in use on a filesystem, expressed in kilobytes. Valid entries For example, 5000 represents fivemegabytes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Space Used (GigaBytes) The amount of disk space currently in use on a filesystem, expressed in gigabytes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 9223372036854775807 indicates Value_Exceeds_Maximum,and -9223372036854775808 indicates Value_Exceeds_Minimum.

Space Used (GigaBytes) (Superseded) The amount of disk space currently in useon a file system, expressed in gigabytes. Note: the value -1 indicates Not Available,-2 indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Space Used (MegaBytes) The amount of disk space currently in use on a filesystem, expressed in megabytes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 9223372036854775807 indicates Value_Exceeds_Maximum,and -9223372036854775808 indicates Value_Exceeds_Minimum.

Space Used (MegaBytes) (Superseded) The amount of disk space currently in useon a file system, expressed in megabytes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Space Used Percent The space currently used on the file system, expressed as apercentage of the sum of used and available space. The Space Used Percent reflectsthe percentage of disk space which is available to non-superusers. A high value inthis column alerts you to critical disk space conditions. Valid entries are wholenumbers up to 100, such as 80 for 80%. Note: the value -1 indicates Not Availableand -2 indicates Not Collected.




Timestamp The date and time the agent collects information as set on themonitored system. The timestamp for SCAN and STR functions is in theCYYMMDDHHMMSSmmm format (as in 1020315064501000 for 03/15/02 06:45:01)where:

C = Century (0=20th)

YY = Year

MM = Month of the Year (01-12)

DD = Day of the Month (01-31)

HH = Hour, in 24-hour time (00-23)

MM = Minute

SS = Second

mmm = Millisecond


Total Inodes The number of inodes allocated on a file system. Note: the value -1indicates Not Available, -2 indicates Not Collected, 9223372036854775807 indicatesValue_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

Total Inodes (Superseded) The number of inodes allocated on a file system. Forexample, a value of 163817 indicates that the number of inodes allocated is 163,817.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

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

Disk Performance attributesThe Disk Performance attributes refer to disk operations such as data transfer rates,average waiting times, and percentage busy.

% Disk Read Time The percentage of elapsed time that the disk drive was busyservicing read requests over the previous 30-second interval. Note: the value -1indicates Not Available and -2 indicates Not Collected. HP-UX systems and AIXsystems do not measure this attribute and a value of -1 will be reported.

Avg Disk Bytes Xfer The number of bytes per disk transfer averaged over theprevious 30-second interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Average Service Time Average amount of disk time used in milliseconds over thesampling period. For example, in terms of a bank teller queue, it is the time spentat the teller's window. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. AIX systems do not measure this, therefore, forthese systems, it is reported with a value of -1.

Average Queue Average number of disk requests outstanding during the samplingperiod. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. AIX systems do not measure this, therefore, for thesesystems, it is reported with a value of -1.

Average Wait Average time waiting for disk access expressed in milliseconds. Forexample, in terms of a bank teller queue, it is the time from when you first join thequeue until you advance to the teller window to be serviced. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.AIX systems do not measure this, therefore, for these systems, it is reported with avalue of -1.

Busy Percent The percentage of time a disk has been busy transferring data. Validentries are whole numbers up to 100, such as 35 for 35%. The Busy Percent valuelets you check whether a process is I/O bound. Values greater than 30% usuallyindicate excessive paging out to disk, or that a process is I/O bound. If the Busy


Percent value is high (greater than 30%) and CPU utilization is also high (greaterthan 80%), your system is probably overloaded and experiencing degradation ofperformance. Note: the value -1 indicates Not Available and -2 indicates NotCollected.

Disk Name The name of the physical disk which might be partitioned. Validentries are up to 32 letters or numbers.

Disk Name (Unicode) The name of the physical disk which might be partitioned.

Disk Read Bytes per Sec The number of bytes per second transferred from thedisk during read operations over the previous 30-second interval. HP-UX systemsdo not measure this attribute and a value of -1 will be reported. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Disk Reads per Sec The number of read operations on the disk per secondaveraged over the previous 30-second interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.HP-UX systems and AIX systems do not measure this attribute and a value of -1will be reported.

Disk Write Bytes per Sec The number of bytes per second transferred to the diskduring write operations over the previous 30-second interval. HP-UX systems donot measure this attribute and a value of -1 will be reported. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Disk Writes per Sec The number of write operations on the disk per secondaveraged over the previous 30-second interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.HP-UX systems and AIX systems do not measure this attribute and a value of -1will be reported.

Percent Disk Write Time The percentage of elapsed time that the disk drive wasbusy servicing write requests over the previous 30-second interval. Note: the value-1 indicates Not Available and -2 indicates Not Collected. HP-UX systems and AIXsystems do not measure this attribute and a value of -1 will be reported.







YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Transfer Rate The number of data transfers per second during a monitoringinterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Transferred Bytes (KBytes) The total number of kilobytes that have beentransferred during the recording interval. The Transferred Bytes count is oneindicator of how fast your disk is moving data. It does not account for variables,such as disk format and efficiency of space usage, that also affect the speed of datatransfer. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

File Comparison Group attributesThe File Comparison Group attributes refer to file characteristics such as filecompare result and file name.

File Compare Option Options that affect how the comparison is performed. Thefollowing values are valid: Plain, Ignore Whitespace, Ignore Case, Ignore CaseWhitespace, Binary Not Available, and Not Collected.

File Compare Result The result of the file comparison between File_Name_1 andFile_Name_2. The following values are valid: Same, Different, Not Available, andNot Collected.

File Name 1 Fully-qualified file name of one of the files to be compared.

File Name 2 Fully-qualified file name of the other of the files to be compared.






File Information attributesThe File Information attributes refer to file and directory characteristics such asname, size, owner, access rights, and links. File Information is a multiple-instanceattribute group.

Note: This attribute group is not historically collected.

Access This attribute defines a four-digit octal number representing the accessrights for a file. You specify access rights using a four-digit number representingthe permissions associated with a file. Each digit is the decimal equivalent of abinary three-bit string. Note: the value -1 indicates Not Available and -2 indicatesNot Collected. Valid entries are Numeric strings in the range 0000 to 7777, fromleft to right, the digits have the following meaning:

1st Digit

Determines whether, on execution, the file takes on the ID of the user orgroup that owns the file. This permission assignment applies to users thatneither own the file they are trying to run, nor belong to the group thatowns the file.

2nd Digit Determines the access permissions of the user that owns the file.

3rd Digit Determines the access permissions of the group that owns the file.

4th Digit Determines the access permissions for other users.

From right to left, the bits for the first digit have the following meanings:

1st bitThe meaning if this bit depends on the type of UNIX operating system youare monitoring.

2nd bit

If the value of this bit is 1, the system runs the file with the group ID ofthe group that owns the file. If the value of this bit is 0, the system runsthe file with the group ID of the user that ran the file. If the file is adirectory and this bit is 1, all files created in that directory inherit thegroup ID of that directory.

Checksum The value of the checksum.

Checksum Algorithm Only used in situations in conjunction with the Checksum.Note: the -1 value indicates Not_Available, and the -2 value indicatesNot_Collected.

File The name of a file or directory. If the file is a symbolic link, the link name isshown in the Link Name attribute. Valid entries: simple text string, alphanumericwith a maximum length 256 characters.

File Content Changed A numeric indicator that the content of a file has changed.It is equivalent to noting a change in checksum between two samples. Thefollowing values are valid: No, Yes, and Not Available.

File Size (Bytes) The size, in bytes, of a file. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 9223372036854775807 indicatesValue_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum.

File Size (Bytes) (Superseded) The size, in bytes, of a file. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.


File Size (MB) The size, in megabytes, of a file. Since the attribute does not havedecimal precision, previously any file with a size less than "1" would be displayedas "0". As of IBM Tivoli Monitoring v6.1 Fix Pack 5, the size of the file is roundedup to the nearest whole number. For example, 1.2 would display as 2, and 0.1would display as 1. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.

File Size (MB) (Superseded) The size, in megabytes, of a file. Since the attributedoes not have decimal precision, previously any file with a size less than "1"would be displayed as "0". As of IBM Tivoli Monitoring v6.1 Fix Pack 5, the size ofthe file is rounded up to the nearest whole number. For example, 1.2 woulddisplay as 2, and 0.1 would display as 1. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

File (Unicode) The name of a file or directory. If the file is a symbolic link, the linkname is shown in the Link Name attribute.

Group The name of the logical group to which a file owner belongs. Valid entries:simple text string, alphanumeric with a maximum length 16 characters

Group (Unicode) The name of the logical group to which a file owner belongs.

Last Accessed Time The date and time of the last file access. Valid entries are inthe CYYMMDDHHMMSSmmm format, where:


YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Last Attr Chg Time The time when the file attributes were last modified.

Last Changed Time The date and time of the last change to a file. Valid entries arein the format CYYMMDDHHMMSSmmm, where:


YY = Year




MM = Minute

SS = Second

mmm = Millisecond


Links The number of links to a file. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Link Name The name of the file for which this file is a symbolic link. If this fieldis blank, the file is not a link. Note that V120 agents do not place data in this field.Valid entries are simple text string, alphanumeric with a maximum length 256characters.

Link Name (Unicode) The name of the file for which this file is a symbolic link. Ifthis field is blank, the file is not a link. Note that V120 agents do not place data inthis field.

Mode The string representation of the file mode.

Owner The name of the file owner. Valid entries are simple text string,alphanumeric with a maximum length 16 characters.

Owner (Unicode) The name of the file owner. Valid entries are simple text string,with a maximum length 768 bytes.

Path The full path containing a particular file or directory. Valid entries are a textstring representing the full path of the file, alphanumeric with a maximum length256 characters.

Path (Unicode) The full path containing a particular file or directory.






YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Type The type of file. The following values are valid:

Dir = Directory


DirLink = Directory Link

File = File

FileLink = File Link

Sock = Socket

Link = Link

Spec = Special

Unknown = Unknown

The maximum length is 12 characters.

File Pattern attributesThe File Pattern attributes refer to file and match characteristics such as matchcount and match pattern.

File Name Fully qualified file name which will be searched for lines matching apattern.

Match Count The number of matches for the specified pattern in the specified file.Note: the -1 value indicates Not_Available, and the -2 value indicatesNot_Collected.

Match Option Options that affect how the search is performed. The followingvalues are valid: Normal, Ignore Case, Inverse Search, Match Whole Words, NotAvailable, and Not Collected.

Match Pattern The grep regular expression used to search for matching lines inFile_Name.





Group attributesThe Group attributes refer to group characteristics.

Duplicated Group Name True if the group name is listed more than once in/etc/group. The following values are valid: False and True.

Group ID The ID of this group. Note: the value -1 indicates Not Available, thevalue -2 indicates Not Collected, the value 2147483647 indicatesValue_Exceeds_Maximum, and the value Value_Exceeds_Minimum=-2147483648.

Group Name The name of the group.






IP Address attributesThe IP Address attributes refer to IP address characteristics.

DNS Name The Domain Name Server (DNS) entry associated with the IP networkaddress. Note: No_DNS_Entry is a valid value.

IP Address An IP address associated with the network interface.

IP Version An indicator as to whether the IP address is version 4 or version 6. Thefollowing values are valid: Not Available (-1), Not Collected (-2), IPv4 (4) and IPv6(6).

Network Interface Name The name of the network interface.





Machine Information attributesThe Machine Information attribute group contains various items required by otherTivoli products. They include system hardware information.

Hardware Manufacturer The manufacturer of the hardware on which the agent isrunning.

Hardware Model The specific hardware model underlying the monitoredoperating system.

Machine Serial Number The serial number of the computer.

Name The host name for the computer.

Number of Physical Processors The number of physical processors on thecomputer. This number excludes secondary processor contexts, but might include


virtual processors in some virtual environments. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processor Megahertz The detected processor speed for the targeted operatingsystem. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

System Board UUID The Universally Unique Identifier burned in to the systemboard. The following value is valid: Unknown (UNKNOWN).





Virtual Machine Identifier The unique serial number or name of this operatingsystem instance. It usually corresponds to a name identifying a virtual machine,but it can also identify an nPar or vPar on HP-UX, or the default OS.

Memory attributesThe Memory attributes refer to memory characteristics.

The use of the term megabyte refers to 2^20 bytes. This is equivalent to the SI unit,megabyte.

Available Real Memory (MB) The amount of physical memory, in megabytes,currently available on the system. The amount of real memory available to userprograms and the system. It is not unusual for the amount of available memory tobe low, because the system uses available real memory for caching of systeminformation. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Note: This is the amount of physical RAM available for program allocation. Thisvalue is derived from the number of free pages available in real memory.

Available Swap Space (MB) The number of megabytes of secondary storageavailable to host virtual memory. Any part of memory available for additionalpaging (pseudo-swap) that is free is also included. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Note: This value represents the amount of paging space the system has availableto assign programs memory.


Available Virtual Storage (MB) The total number of megabytes available forpaging that is not currently being used. This includes primary memory andsecondary storage. This includes primary memory and secondary storage. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Note: The amount of memory available to the system for allocation. It is notunusual for this value to be small on some operating systems because thesystem uses real memory as a caching space.

Average Page Ins\1 Minute The average rate of page ins over the last 1 minute.Displays N/C (not collected) if agent has been up for less than 1 minute. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Average Page Ins\5 Minutes The average rate of page ins over the last 5 minutes.Displays N/C (not collected) if agent has been up for less than 5 minutes. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Ins\15 Minutes The average rate of page ins over the last 15minutes. Displays N/C (not collected) if agent has been up for less than 15minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Ins\60 Minutes The average rate of page ins over the last 60minutes. Displays N/C (not collected) if agent has been up for less than 60minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Outs\1 Minute The average rate of page outs over the last 1minute. Displays N/C (not collected) if agent has been up for less than 1 minute.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Outs\5 Minutes The average rate of page outs over the last 5minutes. Displays N/C (not collected) if agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Outs\15 Minutes The average rate of page outs over the last 15minutes. Displays N/C (not collected) if agent has been up for less than 15minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Outs\60 Minutes The average rate of page outs over the last 60minutes. Displays N/C (not collected) if agent has been up for less than 60


minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Scans\1 Minute The average rate of page scans over the last 1minute. Displays N/C (not collected) if agent has been up for less than 1 minute.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Scans\5 Minutes The average rate of page scans over the last 5minutes. Displays N/C (not collected) if agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Scans\15 Minutes The average rate of page scans over the last 15minutes. Displays N/C (not collected) if agent has been up for less than 15minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Average Page Scans\60 Minutes The average rate of page scans over the last 60minutes. Displays N/C (not collected) if agent has been up for less than 60minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Faults Per Second Page faults per second averaged over the previous30-second interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page In Rate (KB per Second) The number of kilobytes that the virtual memorymanager pages in per second averaged over the previous 30-second interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page-In Requests Per Second The number of requests per second of page-inrequests averaged over the previous 30-second interval. A page-in request mayinclude multiple pages and gives an indication of the I/O rate on the paging file.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Out Rate (KB per Second) The number of kilobytes that the virtual memorymanager pages out per second averaged over the previous 30-second interval.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page-Out Requests Per Second The number of requests per second of page-outrequests averaged over the previous 30-second interval. A page-out request mayinclude multiple pages and gives an indication of the I/O rate on the paging file.


Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Reclaims Per Second The number of times per second that the systemremoved a page from the queue and used that page for another process, averagedover the previous 30-second interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Page Scan Rate (KB Per Second) The number of kilobytes in pages that the virtualmemory manager scans per second averaged over the previous 30-second interval.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Scan Rate Per Second The number of pages examined per second over theprevious 30-second interval. Virtual memory manager uses a clock-algorithm toimplement a pseudo least recently used (lsu), page replacement scheme. Pages areaged by examination by the clock. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Pages Paged-In Per Second The number of pages per second that were paged-infrom disk to system memory averaged over the previous 30-second interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Pages Paged-Out Per Second The number of pages per second paged-out fromsystem memory to disk averaged over the previous 30-second interval. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Percent Real Memory Available Percent of real memory available. Calculated bythe agent using the formula: (Avail_Real_Mem_MB / Total_Real_Mem_MB ) * 100.Note: the value -1 indicates Not Available and -2 indicates Not Collected.

Percent Real Memory Used Percent of real memory used. Calculated by the agentusing the formula: (100 - Avail_Real_Mem_Pct). Note: the value -1 indicates NotAvailable, and -2 indicates Not Collected.

Percent Swap Space Available Percent of swap space available. Calculated by theagent using the formula: (Avail_Swap_Space_MB / Total_Swap_Space_MB ) * 100.Note: the value -1 indicates Not Available, and -2 indicates Not Collected.

Percent Swap Space UsedThe percent of swap space used. Calculated by the agentusing the formula: (100 - Avail_Swap_Space_Pct). Note: the value -1 indicates NotAvailable and -2 indicates Not Collected.

Percent Virtual Storage Available Percent of virtual storage available. Calculatedby the agent using the formula: 100 - Virtual_Storage_Pct_Used. Note: the value -1indicates Not Available and -2 indicates Not Collected.


Percent Virtual Storage Used Percent of virtual memory used. Calculated by theagent using the formula: (Used_Virtual_Storage_MB / Total_Virtual_Storage_MB ) *100. Note: the value -1 indicates Not Available and -2 indicates Not Collected.





Total Real Memory (MB) The total number of megabytes of physical memory on amonitored system. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Note: The total physical RAM installed and active in the system. Some systemshave the capability to disable portions of RAM; the disabled memory is notreported. On virtual machines, the memory reported is that which isallocated to the virtual machine and activated by the operating system.

Total Swap Space (MB) The total number of megabytes of secondary storagededicated to hosting virtual memory. Any part of memory available for the systemto use for additional paging (pseudo-swap) is also included. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Note: The total amount of executable pages possible for paging including physicalRAM plus secondary paging space, in megabytes. All of the physical RAMmight not be available for paging, therefore, total swap space might notequal total virtual storage. Total swap space does not include file cache onAIX systems.

Total Virtual Storage (MB) The total number of megabytes of storage available forhosting virtual memory. This includes primary memory and secondary backingstore. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Note: Total virtual storage is the total physical RAM allocated to the system plusthe total secondary paging space. Total virtual storage combines the totalreal RAM plus the total secondary storage.

Used Real Memory (MB) The amount of physical memory, in megabytes, currentlyused on the system. The amount of real memory in use by user programs and thesystem. It is not unusual for the amount of in use memory to be very high,because the system uses available real memory for caching of system information.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Note: Used Real Memory is derived from subtracting Available Real Memory fromTotal Real Memory. Used Real Memory includes the following:v Executable Pages stored in real memoryv System Pages stored in real memoryv Application Heap Pages stored in real memoryv Shared Memory Pages stored in real memoryv MMAP pages stored in real memoryv File Cache pagesv Memory that is outside of Page Space, usually used by the kernel

Used Swap Space (MB) The number of megabytes of secondary storage currentlyhosting virtual memory. Any part of memory used for additional paging(pseudo-swap) is also included. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Note: The total amount of pages being used by the system in real memory andsecondary paging space. This memory includes any physical memory beingused as pseudo-swap and reserved memory. Reserved memory includesallocations that have been allocated, but not accessed and therefore notassigned to physical memory or secondary paging spaces. Used swap spaceconsists of the following:v Executable Pages stored in real memory and on secondary paging spacev System Pages stored in real memory and secondary paging spacev Application Heap Pages stored in real memory and secondary paging

spacev Shared Memory Pages stored in real memory and secondary paging spacev MMAP pages stored in real memory and secondary paging space

Used Virtual Storage (MB) The number of megabytes of virtual memory currentlyin use by the system. This includes primary memory and secondary backing store.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Note: All the secondary paging space plus all the real RAM used for any purpose.This could include all memory included in used real memory and thatallocated on the disk.

Network attributesThe Network attributes refer to network characteristics such as received count, sentcount, network interface name, and interface status.

Avg Input Packet Rate 1 Minute The average number of packets received on allnetwork interfaces over last 1 minute. Displays N/C (not collected) if the agent hasbeen up for less than 1 minute. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Input Packet Rate 5 Minutes The average number of packets received on allnetwork interfaces over last 5 minutes. Displays N/C (not collected) if the agenthas been up for less than 5 minutes. Note: the value -1 indicates Not Available, -2


indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Input Packet Rate 15 Minutes The average number of packets received on allnetwork interfaces over last 15 minutes. Displays N/C (not collected) if the agenthas been up for less than 15 minutes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Input Packet Rate 60 Minutes The average number of packets received on allnetwork interfaces over last 60 minutes. Displays N/C (not collected) if the agenthas been up for less than 60 minutes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Input Errors Rate 1 Minute The average number of packets with errorsreceived on all network interfaces over last 1 minute. Displays N/C (not collected)if the agent has been up for less than 1 minute. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Input Errors Rate 5 Minutes The average number of packets with errorsreceived on all network interfaces over last 5 minutes. Displays N/C (not collected)if the agent has been up for less than 5 minutes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Input Errors Rate 15 Minutes The average number of packets with errorsreceived on all network interfaces over last 15 minutes. Displays N/C (notcollected) if the agent has been up for less than 15 minutes. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Input Errors Rate 60 Minutes The average number of packets with errorsreceived on all network interfaces over last 60 minutes. Displays N/C (notcollected) if the agent has been up for less than 60 minutes. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Output Packets Rate 1 Minute The average number of packets transmitted onall network interfaces over last 1 minute. Displays N/C (not collected) if the agenthas been up for less than 1 minute. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Output Packets Rate 5 Minutes The average number of packets transmittedon all network interfaces over last 5 minutes. Displays N/C (not collected) if theagent has been up for less than 5 minutes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.




Avg Output Errors Rate 1 Minute The average number of packets transmissionerrors on all network interfaces over last 1 minute. Displays N/C (not collected) ifthe agent has been up for less than 1 minute. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Output Errors Rate 5 Minutes The average number of packets transmissionerrors on all network interfaces over last 5 minutes. Displays N/C (not collected) ifthe agent has been up for less than 5 minutes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Output Errors Rate 15 Minutes The average number of packets transmissionerrors on all network interfaces over last 15 minutes. Displays N/C (not collected)if the agent has been up for less than 15 minutes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg Output Errors Rate 60 Minutes The average number of packets transmissionerrors on all network interfaces over last 60 minutes. Displays N/C (not collected)if the agent has been up for less than 60 minutes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Collisions The number of times during the monitoring interval that a packettransmitted by the network interface collided with another packet. This occurswhen another interface on the same local network transmits a packet at nearly thesame time. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine if a network interface hasan unacceptable number of packet collisions. Packet collisions cause the interface toretransmit the packet. With this increased traffic, the likelihood of future collisionsincreases. This can result in a steady increase of network traffic to critical levels.

Collisions Rate Avg 1 Minute The average number of collisions on all networkinterfaces over last 1 minute. Displays N/C (not collected) if the agent has been upfor less than 1 minute. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Collisions Rate Avg 5 Minutes The average number of collisions on all networkinterfaces over last 5 minutes. Displays N/C (not collected) if the agent has beenup for less than 5 minutes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Collisions Rate Avg 15 Minutes The average number of collisions on all networkinterfaces over last 15 minutes. Displays N/C (not collected) if the agent has been


up for less than 15 minutes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Collisions Rate Avg 60 Minutes The average number of collisions on all networkinterfaces over last 60 minutes. Displays N/C (not collected) if the agent has beenup for less than 60 minutes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Hostname IPv4 DNS Name The Domain Name Server (DNS) entry associatedwith the first IP address of the network interface. The following values are valid:Sum_of_all_interface_metrics and Not_Resolvable.

Input Errors The number of packets with errors received by the interface duringthe monitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Input Packet Errors Percent Portion of packets received over the previous30-second interval with errors. Note: the value -1 indicates Not Available and -2indicates Not Collected.

Interface DNS Name The Domain Name Server (DNS) entry associated with thefirst IP address of the network interface. The following values are valid: Sum ofall interface metrics and Not_Resolvable. Valid entries are alphanumeric stringswith a maximum 32 characters.

Example:

www.company.com indicates that the DNS resolves the name www.company.comto mean the IP address for the interface.

Interface IP Address The Internet Protocol (IP) address of the network interface. Agateway system has more than one interface, each with a separate address. Validentries: Internet protocol addresses in the form a.b.c.d. where a, b, c, and d areintegers in the range 0 to 255.

Example 197.128.55.55 indicates the network interface uses the IP address197.128.55.55. Multiple addresses assigned to a single network interface are not alldisplayed from Tivoli Enterprise Portal.

Interface Status This attribute indicates if a network interface is currentlyavailable. Valid entries for each Network interface:

UP Indicates the interface is in service

DOWN Indicates the interface is not in service

Up NotRunning

Indicates the interface is in service but not running

These values are case-sensitive.

Example UP means an interface is in service.


Mac Address The Machine Access Control (MAC) address of the NetworkInterface Card.

Maximum Transmission Unit The maximum packet size (in bytes) for thespecified network interface. This is a fixed value. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the minimum, maximum or average packet sizeused by a network interface. This information can help you determine the sizeused by a network interface.

This information can help you determine the data transfer capabilities of variousnetwork interfaces, and alleviate bottlenecks by re-routing traffic from devices thatare displayed to be overloaded, to other network interfaces that might be able tohandle additional data traffic.

Network Interface Name Identifies the network interface adapter. Aggregate is avalid value. Valid entries are simple text string, alphanumeric 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 of 0-7.

Example On an AIX system, typical network adapters are represented as follows:

en = Ethernet

lo = Loopback

tr = Token Ring

sl = SLIP

Other operating systems might refer to the adapter type in a different manner. Forexample, on SunOS, ethernet adapters are typically represented by le.

On HP-UX, you might see ethernet represented as lan.

The possible combinations based on hardware, operating systems and installationoptions are virtually impossible to list. Ask your local System Administrator forassistance in determining the specific adapter types installed on your system.

Output Errors The number of packet transmission errors by the network interfaceduring the monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Output Packet Errors Percent Portion of packets sent over the previous 30-secondinterval with errors. Note: the value -1 indicates Not Available and -2 indicates NotCollected.

Packet Collisions Percent Portion of packets sent over the previous 30-secondinterval with collisions. Note: the value -1 indicates Not Available and -2 indicatesNot Collected.


Example If a low number of packets are being received, data traffic might need tobe re-routed.

Packets Received The number of packets received by the interface during themonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Packets Transmitted The number of packets transmitted by the interface duringthe sampling period. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Received Megabytes Second The number of megabytes received per secondaveraged over the previous 30-second interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Received Megabytes (Total) The number of megabytes received on the interface(total). Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Example Host names vary from system to system. Check with your systemadministrator for a list of all host names on your system.





YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Total Packets Received The number of packets received since the networkinterface was initialized. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.


Total Packets Received (superseded) The number of packets received since thenetwork interface was initialized. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Total Packets Transmitted The number of packets transmitted since the networkinterface was initialized. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum.

Total Packets Transmitted (superseded) The number of packets transmitted sincethe network interface was initialized. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Example A high value might indicate an overloaded interface. A low value mightindicate a device that is not being used much, which can carry an additional load,if required.

Transmitted Megabytes Second The number of megabytes sent per secondaveraged over the previous 30-second interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Transmitted Megabytes (Total) The number of megabytes transmitted on theinterface (total). Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Type The type of network interface card. The following values are valid:

Ethernet X.25 IEEE 802.5Token-Ring

PPP

Other Localtalk SLIP Not Available

Unknown Multi-protocol OverFrame Relay

CharacterAsynchronousProtocol

ATM Classical IPInterface

Infiniband HDH Arpanet ISO 802.6 MAN Hyperchannel

SMDS SONET 802.2 LLC Frame Relay

Federation Switch SP Switch Virtual Interface DS3/T3

ULTRA ISO 8802/3 andEthernet

ISO HDLC Protocol HIPPI

Frame Relay LAPF 100-Based VG TokenRing

IEEE 802.4 Token-Bus MODEM

Fibre ChannelInterface

100-Based VGEthernet

PTP Serial IEEE 802.3 Network

Proprietary Virtual IBM Channel toChannelAdapter

HSSI T1/E1

Fiber DistributedData Interface

CharacterSynchronous Protocol

ISDN XNS

ATM ProprietaryMultiplexing

100 Base-T V.35


SDLC X.25 LAPB Not Collected Software Loopback

NFS / RPC Statistics attributesThe NFS / RPC Statistics group attributes refer to Network File System andRemote Procedure Call call rates and errors. These attributes fall into foursubgroups:v NFS Client attributes report on calls from the managed system to NFS servers.v NFS Server attributes report on NFS calls to the managed system. The agent

reports these calls only when the managed system is an NFS server.v RPC Client attributes report on calls from the managed system to RPC servers.v RPC Server attributes report on PRC calls to the managed system. The agent

reports these calls only when the managed system is an RPC server.

NFS Client Calls The number of calls made to a server during a monitoringinterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to show the amount of NFS traffic. Ifthe value is high, it might mean a client is flooded with call requests.

NFS Client Calls Rejected The number of calls rejected by a server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute in conjunction with the NFSClient Calls attribute to determine the proportion of calls rejected by the NFSserver.

NFS Client File Creates The number of File Creates calls made to a server duringthe monitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute with other Call-typeattributes for analyzing NFS traffic and correcting problems on your network.

NFS Client File System Statistics Calls The number of file statistics calls madewithin the monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Get Attribute Calls The number of calls made to determine what typeof file is being called. For example, a text file or an executable file. Note: the value-1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute with other Call-type attributes for analyzing NFS traffic andcorrecting problems on your network.

NFS Client Link Calls The number of hard link reports made by a server during apre-defined time interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute with other Call-typeattributes for analyzing NFS traffic and correcting problems on your network.


NFS Client Lookups The number of Lookups requests made by an NFS serverduring the monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute to determine thenumber of Make Directory requests handled by an NFS server during themonitoring interval.

NFS Client Make Directory Calls The number of calls made to a server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute with other Call-typeattributes for analyzing NFS traffic and correcting problems on your network.

NFS Client Null Calls The number of calls generated for checking connectivity toa server. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute with other Call-type attributes foranalyzing NFS traffic and correcting problems on your network.

NFS Client Read Calls The number of Read Directory calls read by a serverduring a monitored interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to determine how many callrequests to read a file were received by an NFS server over a period of time.

NFS Client Read Directory Calls The number of Read Directory calls made to aserver during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Read Link Calls The number of calls received by an NFS server toread a linked file during the monitoring interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine how many link-call requests an NFS server receivedover a period of time.

NFS Client Rejected Call Percentage The percentage of NFS calls rejected by aserver during a monitoring interval. Valid entry is an integer in the range 0 to 100.Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use thisattribute to monitor unacceptable rates of NFS call rejection and to determinewhether the server or a particular client is causing network problems. If the serveris experiencing problems, all calls are rejected. If a client is experiencing problems,it alone has its calls rejected. The rejection percentage might increase dramaticallyafter reaching a critical threshold, since rejections require re-transmission.

NFS Client Remove Directory Calls The number of Remove Directory calls madeto a server during a monitoring interval. Note: the value -1 indicates Not Available,-2 indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.


NFS Client Remove File Calls The number of Remove File calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Rename File Calls The number of Rename File calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Root Calls The number of NFS calls made to the server by the rootduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute to determine thenumber of calls made by the root (Super-User) account versus calls made by allusers.

NFS Client Set Attribute Calls The number of NFS calls made to set the attributesof a file during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Symbolic Link Calls The number of Symbolic Link calls made to aserver during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Write Cache Calls The number of Write Cache calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Client Writes The number of Writes calls made to a server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to determine how manywrite requests an NFS server received over a pre-specified period of time.

NFS Server Calls The number of Server Calls made from an NFS server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to show the amount of NFStraffic. If the value is high, it might mean a server is flooded with call requests.

NFS Server Calls Rejected The number of calls rejected by a server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates Not


Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute in conjunction with the NFSServer Calls attribute to determine the proportion of calls rejected by the NFSserver.

NFS Server File Creates The number of File Creates calls made to a server duringthe monitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute with other Call-typeattributes for analyzing NFS traffic and correcting problems on your network.

NFS Server File System Statistics Calls The number of file statistics calls madewithin the monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Get Attribute Calls The number of calls made to determine what typeof file is being called during a monitoring interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

NFS Server Get Attr Percent The portion of calls made over the previous30-second interval to determine what type of file is being called. Note: the value -1indicates Not Available and -2 indicates Not Collected.

NFS Server Link Calls The number of hard link reports made by a server during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute with other Call-typeattributes for analyzing NFS traffic and correcting problems on your network.

NFS Server Lookups The number of Lookups requests made by an NFS serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute to determine thenumber of Lookups requests handled by an NFS server during the monitoringinterval.

NFS Server Make Directory Calls The number of Make Directory calls made to aserver during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Null Calls The number of calls generated for checking connectivity toa server. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute with other Call-type attributes foranalyzing NFS traffic and correcting problems on your network.

NFS Server Read Calls The number of Read Directory calls read by a serverduring a monitored interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648


indicates Value_Exceeds_Minimum. Use this attribute to determine how many callrequests to read a file were received by an NFS server over a period of time.

NFS Server Read Directory Calls The number of Read Directory calls made to aserver during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Read Link Calls The number of calls received by an NFS server toread a linked file during the monitoring interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine how many link-call requests an NFS server receivedover a period of time.

NFS Server Read Link Percent The portion of lookup requests made by an NFSserver over the previous 30-second interval that read a linked file. Note: the value-1 indicates Not Available and -2 indicates Not Collected.

NFS Server Read Percent The portion of client calls made to a server over theprevious 30-second interval that were reads. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected.

NFS Server Rejected Call Percentage The percentage of NFS calls rejected by aserver during a monitoring interval. Valid entry is an integer in the range 0 to 100.Note: the value -1 indicates Not Available and -2 indicates Not Collected. Use thisattribute to monitor unacceptable rates of NFS call rejection and to determinewhether the server or a particular client is causing network problems. If the serveris experiencing problems, all calls are rejected. If a client is experiencing problems,it alone has its calls rejected. The rejection percentage might increase dramaticallyafter reaching a critical threshold, since rejections require re-transmission.

NFS Server Remove Directory Calls The number of Remove Directory calls madeto a server during a monitoring interval. Note: the value -1 indicates Not Available,-2 indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Remove File Calls The number of Remove File calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Rename File Calls The number of Rename File calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.


NFS Server Root Calls The number of NFS calls made to server root during amonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to determine the number ofcalls made by the root (Super-User) account versus calls made by all users.

NFS Server Set Attribute Calls The number of NFS calls made to set the attributesof a file during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Symbolic Link Calls The number of Symbolic Link calls made to aserver during a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Write Cache Calls The number of Write Cache calls made to a serverduring a monitoring interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute with otherCall-type attributes for analyzing NFS traffic and correcting problems on yournetwork.

NFS Server Write Percent The portion of client calls made to a server over theprevious 30-second interval that were writes. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected.

NFS Server Writes The number of Writes made to a server during a monitoringinterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine how many write requestsan NFS server received over a pre-specified period of time.

NFS Version The version of NFS from which metrics were obtained, or Aggregateif metrics from more than one version are included. Only Aggregate for the NFSattributes is supported. Note: the value -1 indicates Not Available, -2 indicates NotCollected, and 0 indicates Aggregate. Other values are v1, v2, v3, and v4.

RPC Client Bad Xid Replies Percent The portion of RPC server calls over theprevious 30-second interval that did not match the call. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

RPC Client Bad Xid Replies Limited Percent The portion of rejected RPC servercalls over the previous 30-second interval that did not match the call. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected.

RPC Client Calls The number of RPC client calls per second averaged over theprevious 30-second interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.


RPC Client Calls Rejected by Server The number of calls made by a client to aserver that the server rejected, during a monitoring interval. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute in conjunction with the Calls attribute to determine theproportion of calls rejected by the RPC server. If the value is high, it might meanthere is excessive noise on the network, which causes bad datagrams to occur, or aserver might be flooded with call requests.

RPC Client Calls Rejected by Server Percent The portion of calls made by a clientto a server over the previous 30-second interval that the server rejected. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected.

RPC Client Calls Rejected Percent The portion of RPC client calls over theprevious 30-second interval that were rejected by the server. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

RPC Client Calls Retransmitted The number of RPC packets retransmitted to anRPC server during a monitoring interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine if a large number of calls are being retransmitted. Ifso, your server might be overworked or there might be a network problem.

RPC Client Calls Retransmitted Limit Percent The portion of timed-out RPCclient calls over the previous 30-second interval that were retransmitted. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected.

RPC Client Calls Retransmitted Percent The portion of RPC packets over theprevious 30-second interval retransmitted to an RPC server. Note: the value -1indicates Not Available and -2 indicates Not Collected.

RPC Client Calls Timed Out The number of times an RPC call from the managedsystem timed out before the RPC server replied. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine if the server is failing to acknowledge callsreceived. If the server is overworked, you might need to re-route network traffic.

RPC Client Calls Timed Out Percent The portion of RPC client calls over theprevious 30-second interval that timed out. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected.

RPC Client Replies Not Matching Calls The number of times the managedsystem received replies from an RPC server that did not match calls. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine if a reply or acknowledgment from the servermatches a request made by a client. A failure to match the request might meanthere is noise on the network.

RPC Client Times Authentication Refreshed The number of times the managedsystem had to resend the authentication information for an RPC call during themonitoring interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648


indicates Value_Exceeds_Minimum. Use this attribute to count the number of timesan authorization is refreshed. This attribute helps you verify client authorizationfor making a request by periodically requesting an electronic handshake from theclient.

RPC Client Times Call Wait On Busy The number of times the initial bind for anRPC call from the managed system had to wait because of a busy server. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to show the amount of NFS traffic. When a client sends a callrequest to a server, it gives the server a certain amount of time to respond beforere-sending the call. The amount of time varies from system to system. If the TimesCall Wait On Busy value is high, it might indicate that the server is overworked.You might want to re-route call requests to another server.

RPC Server Calls The number of RPC server calls per second averaged over theprevious 30-second interval. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

RPC Server Calls Rejected The number of RPC calls from the managed systemthat were rejected by a server during a monitoring interval. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine if the server is rejecting a large number of calls. Ifonly a few calls are being rejected, it might be a client-specific problem. If manycalls are being rejected, it might be a problem with your server.

RPC Server Calls Rejected Percent The portion of RPC server calls over theprevious 30-second interval that were rejected by the server. Note: the value -1indicates Not Available and -2 indicates Not Collected.

RPC Server Dup Checks The number of RPC server calls per second servicedfrom the duplicate request cache averaged over the previous 30-second interval.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

RPC Server Dup Reqs The number of duplicate RPC server calls per secondaveraged over the previous 30-second interval. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

RPC Server Dup Reqs Percent The portion of RPC server calls over the previous30-second interval that were duplicate requests. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected.

RPC Server Packets Too Short The number of incomplete RPC packets that weretoo short in length received by a server during a monitoring interval. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine if the server is having problems processing packetdata. If the packet size does not match the size stated in the packet header, theremight be noise on the system.


RPC Server Packets with Malformed Header The number of RPC packets thathad malformed headers and were received by the server during a monitoringinterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine if there is noise on thesystem. The server cannot validate a packet or where it came from if, due to amalformed header, it cannot acknowledge the sender. This decreases the efficiencyof the network. Try checking server connections. Another cause might includeextraneous network noise.

RPC Server Times RPC Packet Unavailable The number of times a serverattempted to receive a packet when none was available, during a monitoringinterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.






YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Ping attributesThe Ping attributes refer to target characteristics such as target host and pingresult. Historical information is available for the Ping table for users interested intrending server response times. However, to enable history collection for thisattribute group, a list of monitored (pinged) servers must be specified. The list isspecified through an environment variable - "KUX_PINGHOSTLIST" in the ux.inifile in the IBM Tivoli Monitoring config directory. For example:KUX_PINGHOSTLIST='/opt/IBM/ITM/config/kuxpinghosts'

sample content of kuxpinghosts:## hosts pinged for availability from this agent


#server1.domain.comserver2server4

Once the kuxpinghosts file has been created on the monitored system and theparm entry has been made in the ux.ini file, you can create a table to display theUNIX Ping attributes. The returned rows would be for each of the hosts specifiedin the kuxpinghosts file on the monitored system.

You can also create a situation using the UNIX Ping attributes. If the situation doesnot contain a value in the Target Host attribute field, then the systems identified inthe kuxpinghosts file is pinged. If the situation contains a host name or ip addressin the Target Host attribute field in the situation, then this Target Host nameoverrides the use of the kuxpinghosts file (and the hosts specified therein).

To create this situation, in the situation editor complete the following steps:v Create the situation.v Set the System Node to $NODE$.v Set the Target_Host or leave it blank to use a ping hosts file.v Select Advanced and the select Display Item.v Set the Display Item to Target_Host.

This creates a situation that generates an event and report the target host's IP inthe situation. It is especially useful if you set up multiple Ping queries.

Ping Result Result from pinging the host. The following values are valid:Successful, Unsuccessful, and Not Collected and Not Available.

Server Response Time Ping Operation response time in milliseconds. Thefollowing values are valid: a numerical value in milliseconds, Not Collected andNot Available.




Target Host Host name or IP address of the host to be pinged.


Print Queue attributesThe Print Queue attributes refer to print queue characteristics.

Device Name The name of a device associated with this queue.


Print Queue Depth The number of jobs in the print queue. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Print Queue Name The name of the print queue.

Print Queue Job Size The number of kilobytes in the print queue, includingcopies. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum

Print Queue Status The status of the print queue.




Timestamp The date and time the agent collects information as set on themonitored system. The date and time of the last file access. Valid entries are in theformat CYYMMDDHHMMSSmmm, where:


YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Process attributesThe Process Attributes Group refers to process operations such as commandexecuted, CPU utilization, real memory usage, and execution state.

Note: Do not collect history from this attribute group due to the volume ofinformation that might be sent to the Tivoli Data Warehouse.

Special information about the Flag field (Solaris only)The Flag field of the UNIX Process report contains hexadecimal and additive flags.These flags are available for historical purposes only, and contain no informationregarding the current status of your monitored process. These fields are notrelevant on Solaris systems. For additional information about the Flag field, see theman pages for your operating system.

Base Command The command that initiated a process.


Child System CPU Time The time spent in system and user mode by the child ofthis process. Valid entry is a numeric time string with a format ofDDDdHH:MM:SS where:

DDD = Days to a maximum of 999

HH = Hours

MM = Minute

SS = Second

Example To express 45 days, 1 hour, 5 minutes, and 30 seconds, enter 045d01:05:30.Note: Not Available indicates a value of 0.

Use this attribute to determine which processes have children consuming a largeamount of CPU time and take corrective action.

Child User CPU Time The time spent in user mode by the child of this process.Valid entry is a numeric time string with a format of DDDdHH:MM:SS where:


HH = Hours

MM = Minute

SS = Second


Command The command that initiated a process. Valid entry is a simple textstring, alphanumeric with a maximum 32 characters. Use this attribute todetermine which command initiated a process.

Command (Unicode) The command that initiated a process. Use this attribute todetermine which command initiated a process.

Example An example of a command that initiates a process would be run.

Context Switch The number of CPU context switches for this process. A contextswitch occurred when a process voluntarily giving up the processor before its timeslice was completed. This usually occurs while the process waits for a resource.Note: the value -1 indicates Not Available, -2 indicates Not Collected,9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum. Use this attribute tomonitor for context switches. Excessive context switches might indicate too manywaits for resources. Available on Solaris and AIX only.

Context Switch (Superseded) The number of CPU context switches for thisprocess. A context switch occurred when a process voluntarily giving up theprocessor before its time slice was completed. This usually occurs while theprocess waits for a resource. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to monitor for contextswitches. Excessive context switches might indicate too many waits for resources.Available on Solaris and AIX only.


Count of Processes The count of processes with the same name. On systems withAIX WPARs or Solaris Zones where all processes from the containers are visible,the process count includes all processes from all virtual containers and the count isnot respective to each WPAR or Zone. Note: the value -1 indicates Not Available,the value -2 indicates Not Collected, and the value 2147483647 indicatesValue_Exceeds_Maximum.

CPU ID The ID of the processor on which the process is running. Note: the value-1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the processor on which a process is running.Available on Solaris and HP-UX only.

CPU Pct The percentage of CPU used by this process. This value may exceed 100percent if more than one processor is installed. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected. Use this attribute to determine whichprocesses are using the most CPU time. High CPU percent might indicate arunaway or long running process.

For example, enter 50 to represent 50.00%, or 50.34 to represent 50.34%.

CPU Time The time the CPU has been utilized. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

CPU Utilization The numerical value indicating the relative CPU intensity of aprocess. The CPU Utilization attribute represents the number of times a processuses the CPU over a period of 20 system clock ticks. The system decays this valueafter each 20 clock-tick period by dividing the number by 2. The system uses CPUUtilization to determine process priority. Large values indicate a CPU intensiveprocess and result in lower process priority. Small values indicate an I/O intensiveprocess and result in a more favorable priority. Valid entry is a numeric value inthe range 0 to 999. Note: the value -1 indicates Not Available and -2 indicates NotCollected. Use this attribute to check process if you suspect it is using the CPU somuch that the CPU is not available to anything else. This can cause networkresponse time to be sluggish.

Example A high value indicates a CPU-intensive process. A low value indicates anI/O-intensive process.

Effective Group ID The effective GROUP ID. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the effective group ID for this process. Available onall platforms.

Effective Group Name The effective group name of the process.

Effective User ID The effective USER ID. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the effective user ID for this process. Available onall platforms

Effective User Name The effective user name of the process.


Elapsed Time The elapsed time for the process. Note: the value -0 indicates NotAvailable. Valid entry is a numeric time string with a format of DDDdHH:MM:SSwhere:


HH = Hours

MM = Minute

SS = Second

Use this attribute to determine how long this process has been running.

Example To express 45 days, 1 hour, 5 minutes, and 30 seconds, enter 045d01:05:30

Entry Address The virtual memory address of a process. This address correspondsto the segment number of the process stack. Valid entry is a hexadecimal string.Check with you local System Administrator for information on how to use thisattribute. Note: On 64-bit systems, only the low-order part of the address is used.

Example The virtual memory address of a process varies from process to process.

Event Waited On The memory address of an event (if any) on which a process iswaiting. A process must have this information before it can run. Valid entry is asimple text string or hexadecimal value depending on the operating system with amaximum string length of 8. This information is specific to your particularnetwork.

Example On AIX, the word EVENT is an example of what is displayed for thisattribute.

Execution State The execution state of a process. For valid entries, use one of thefollowing codes to indicate an execution state:

0 = Non-existent

A = Active

I = Intermediate

O = Running

R = Runable

S = Sleeping

T = Stopped

W = Waiting

X =Growing

Z = Zombie

Use this process to determine the state of a particular process. If a process iswaiting, there might be an excessive amount of network traffic, or a process mightbe taking a long time to complete. Further investigation might be needed. Checkwith your local system administrator to determine what corrective action to take.

Flag The hexadecimal value associated with a process. Valid entry is a hexadecimalvalue with a maximum string length of 8. The meaning of a flag depends on thetype of UNIX system you are monitoring. The Flag field of the UNIX Process


report contains hexadecimal and additive flags. These flags are available forhistorical purposes only, and contain no information regarding the current status ofyour monitored process. These fields are not relevant on Solaris systems. Foradditional information about the Flag field, please refer to the man pages for youroperating system.

Group Name The group name of the process owner.

Heap Size The size of the heap for this process expressed in bytes. Note: the value-1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the heap size for a process. Excessive heap sizemight indicate a memory leak. Available on Solaris only.

Involuntary Context Switch The number of involuntary context switches for theprocess. An involuntary context switch occurs when a higher priority process ranor because the current process exceeded its time slice. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 9223372036854775807 indicatesValue_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum. Use this attribute to monitor for involuntary contextswitches. Excessive involuntary context switches might indicate function problemsin a process. Available on Solaris and AIX only.

Involuntary Context Switch (Superseded) The number of involuntary contextswitches for the process. An involuntary context switch occurs when a higherpriority process ran or because the current process exceeded its time slice. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to monitor for involuntary contextswitches. Excessive involuntary context switches might indicate function problemsin a process. Available on Solaris and AIX only.

Major Fault The number of major faults requested by this process. A major faultrequires disk access. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 9223372036854775807 indicates Value_Exceeds_Maximum, and-9223372036854775808 indicates Value_Exceeds_Minimum. Use this attribute tomonitor for major faults. Excessive major faults might indicate memory shortage.

Major Fault (Superseded) The number of major faults requested by this process. Amajor fault requires disk access. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute to monitor formajor faults. Excessive major faults might indicate memory shortage.

Mem Pct The percentage of system memory used by this process. Valid entry is anumeric value in the range 0 to 100.00 to two decimal places. Note: the value -1indicates Not Available and -2 indicates Not Collected. Use this attribute tomonitor memory usage by a process. Processes with high memory percent leads tomemory shortage and cause system performance problems.

Example Enter 50 to represent 50.00%, or 50.34 to represent 50.34%.

Minor Fault The number of page reclaims for the process. Note: the value -1indicates Not Available, -2 indicates Not Collected, 9223372036854775807 indicates


Value_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum. Use this attribute to determine the number of minorfaults occurred in any processes.

Minor Fault (Superseded) The number of page reclaims for the process. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the number of minor faults occurred in anyprocesses.

Nice Value The requested execution priority of a process, in relation to otherprocesses. The higher the nice value, the lower the priority of the command. Thenice value, plus the minimum user process priority level equals the priority of theprocess. The range of nice values varies among UNIX systems. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.The range of nice values varies among UNIX systems. Check with your localsystem administrator for information concerning the range of nice values for yoursystem.

Parent Process ID The unique numerical identifier of a process. The process thatinvoked the forked system call is the parent process, and the newly created processis the child process. Every process has one parent process, but a process can haveseveral children. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to determine the PPID forthis process.

Priority The current execution priority value. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.The priority equals the nice value of the process plus the minimum priority valueassigned to all user processes. The higher the priority value, the lower the priorityof the command.

Example A value of 245 indicates the process is scheduled to be the 245th processran. This is usually considered to be a low scheduling priority.

Process Command A command string including the arguments up to 100characters in length. Valid entry is a simple text sting with a maximum 100characters. Use this attribute to determine which command initiated this process.

Process Command (Unicode) A command string including the arguments up to768 bytes in length. Use this attribute to determine which command initiated thisprocess.

Process Group Leader ID The process group leader PID. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the process group leader ID for this process.Available on all platforms

Process ID The numerical process ID assigned to a process. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicates


Value_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the process ID for this process. Process ID valuesvary from system to system.

Read/Write The number of characters read and write by this process. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 9223372036854775807indicates Value_Exceeds_Maximum, and -9223372036854775808 indicatesValue_Exceeds_Minimum. Use this attribute to determine the number of read andwrite completed by this process.

Read/Write (Superseded) The number of characters read and write by this process.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine the number of read andwrite completed by this process.

Real Group ID The real group ID for this process. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the real group id for this process. Not available onHP-UX.

Scheduling Class The scheduling class for this process. Valid entry is a simple textsting with a maximum 8 characters. Use this attribute to determine the schedulingclass of this process. Not available on AIX and HP-UX.

Session ID The real session ID for this process. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Size (KBytes) The resident set size of the process, in kilobytes. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine which processes are using too much memory.Excessive resident set size might lead to memory shortage and cause systemperformance problems.

Stack Size The size of the stack for this process. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine which processes are using too much stack size.

Start Time The time when the process was started. Note: the value -0 indicates NotAvailable. Valid entries are in the format CYYMMDDHHMMSSmmm, where:


YY = Year




MM = Minute

SS = Second

mmm = Millisecond


Example A value of 0951009130500000 indicates the agent collected the data onOctober 9, 1995 at 1:05 p.m.

System CPU Time The system time spent executing this process. Note: the value -0indicates Not Available. Valid entry is a numeric time string with a format ofDDDdHH:MM:SS where:


HH = Hours

MM = Minute

SS = Second

Use this attribute to monitor the system CPU time spent by any processes.Excessive system CPU time might indicate a runaway or long running process.





Terminal Device The name of the terminal device that started a process. Validentry is a simple text string with a maximum 8 characters. Terminal names varyfrom system to system. Check with your local system administrator for a completelist of all terminals in your system.

Thread Count The total number of threads for the process. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the number of threads in this process forinformation only. Not available on HP-UX.

Time The total amount of CPU time that a process has consumed. Should thisvalue become large, it might indicate a runaway or long-running process. Validentry is a numeric time string with a format of MMMMM:SS where:

MMMMM = Minute

SS = Second

Example To express 1 hour, 5 minutes, and 30 seconds, enter 00065:30

Use this attribute to identify runaway or long-running processes.




YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Total Child CPU Time The sum of the child CPU time (user + system) spentexecuting the process. Valid entry is a numeric time string with a format ofDDDdHH:MM:SS where:


HH = Hours

MM = Minute

SS = Second


Total CPU Percent The percentage of CPU used since the process was started. Thisvalue might exceed 100 percent if more than one processor is installed. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected. Use this attributeto identify which processes are using the most CPU time. Excessive total CPUpercent might indicate a runaway or long running process.

Example Enter 50 to represent 50.00%, or 50.34 to represent 50.34%

Total CPU Time The total CPU time (user + system) spent on the process. Note:the value -0 indicates Not Available. Valid entry is a numeric time string with aformat of DDDdHH:MM:SS where:


HH = Hours

MM = Minute

SS = Second


Use this attribute to identify which processes are using the most CPU time.Excessive CPU time might indicate a runaway or a long running process.

Type The type of UNIX operating system residing on a monitored host.

User CPU Time The user CPU time spent executing the process. Note: the value -0indicates Not Available. Valid entry is a numeric time string with a format ofDDDdHH:MM:SS where:



HH = Hours

MM = Minute

SS = Second


Use this attribute to identify which processes are using the most CPU time.Excessive CPU time might indicate a runaway or a long running process.

User ID The numerical user ID of the owner of a process. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to identify the owner of a process.

Example The numeric identification number varies from system to system and userto user. An example of a user ID could be 48765.

User Name The login name of the user based on UID. Valid entry is a simple textsting with a maximum 32 characters. Use this attribute to identify the owner of aprocess.

User Name (Unicode) The login name of the user based on UID. Use this attributeto identify the owner of a process.

Virtual Size The size of the virtual memory used by this process, in kilobytes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine the size of the virtualmemory used by a process. Excessive virtual memory size might indicate amemory leak.

Wait CPU Time The time spent waiting for the CPU. Valid entry is a numeric timestring with a format of DDDdHH:MM:SS where:


HH = Hours

MM = Minute

SS = Second


Use this attribute to determine the time spent waiting for CPU. Excessive wait forCPU time might indicate a system problem. Available on Solaris only.

Wait Lock Time The time spent waiting for locks to release. Valid entry is anumeric time string with a format of DDDdHH:MM:SS where:


HH = Hours


MM = Minute

SS = Second


Use this attribute to determine the time spent waiting for a lock. Excessive wait forlock time might indicate a resource concurrence problem. Available on Solaris only.

Zone ID (Solaris) The ID of the Solaris zone. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Zone Name (Solaris) The name of the Solaris zone. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

SMP CPU attributesThe SMP CPU Group attributes refer to multi-processor characteristics such ascross-calls, thread migrations, and system calls.

Avg CPU Busy 1 The average CPU busy time over the last one minute. DisplaysN/C (not collected) if the agent has been up for less than one minute. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg CPU Busy 5 The average CPU busy time over the last 5 minutes. DisplaysN/C (not collected) if the agent has been up for less than 5 minutes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.



Avg CPU System 1 The average system CPU time over the last 1 minute. DisplaysN/C (not collected) if the agent has been up for less than 1 minute. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg CPU System 5 The average system CPU time over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.




Avg CPU User 1 The average user CPU time over the last 1 minute. Displays N/C(not collected) if the agent has been up for less than 1 minute. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Avg CPU User 5 The average user CPU time over the last 5 minutes. DisplaysN/C (not collected) if the agent has been up for less than 5 minutes. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.



Context Switches CPU context switches rate per second during the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use to determine system workload or per processorworkload of the SMP system. Available on Solaris only.

CPU Busy (Percent) The sum of the System CPU and User CPU attributes inpercent. Valid entries in the range 0 to 100. Note: the value -1 indicates NotAvailable and -2 indicates Not Collected. Use to determine system workload or perprocessor workload of the SMP system.

CPU ID The processor ID. Use this attribute to determine the processor ID. In anSMP system with more than one processor, the CPU report shows CPU ID as“aggregate” on the first row. This means the data row return aggregated CPUstatistics.

CPU Status The current status of the processor. Valid entries include 0 = off-lineand 1 = on-line. Note: the value -1 indicates Not Available and -2 indicates NotCollected.

CPU Time The time the CPU has been utilized. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.


CPU Usage The sum of the percent user and percent system time of the CPUaveraged over the sampling period. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Cross Calls Inter-processor cross-calls rate per second during the sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum. Use this attribute to determine the inter-processor crossreference call rate of the system or per processor of the SMP system. Available onSolaris only.

Idle CPU (Percent) Percentage of idle CPU time during the sampling period. Thefollowing values are valid: numeric values in the range 0 to 100. Note: the value -1indicates Not Available and -2 indicates Not Collected. Use this attribute todetermine how efficiently the entire system or each processor of the SMP system isoperating. The Idle CPU value must be low if the system load is heavy, and high ifthe system load is light. If the system load is heavy and the Idle CPU value ishigh, an I/O problem might exist. If the Idle CPU value is small, or zero, and theUser percentage is larger (greater than 30%), the system might be compute-boundor in a loop. Available on all platforms.

Interrupts Interrupts rate per second over the sampling interval. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the devices interrupts rate of the system or of eachprocessor of the SMP system. Available on Solaris only.

Interrupts As Threads Interrupts as thread (not counting interrupts) rate persecond during the sampling period. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum. Use this attribute to determine therate of interrupts as threads (below block) of the system or of each processor of theSMP system. Available on Solaris only.

Involuntary Context Switches Involuntary context switches rate per second duringthe sampling period. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Major Faults Major faults rate per second during the sampling period. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the rate of page faults that need disk access of thesystem or of each processor of the SMP system. Available on Solaris only.

Minor Faults Minor faults rate per second during the sampling period. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the rate of page faults where the pages faulted islocated in memory, usually on the inactive list for the entire system or for eachprocessor of the SMP system. This is available on Solaris only.

Spins On Mutexes Spins on mutexes (locks not acquired on try) rate per secondduring the sampling period. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648


indicates Value_Exceeds_Minimum. Use this attribute to determine the spins onmutexes rate of the system or of each processor of the SMP system. Available onSolaris only.

Spins On RW Locks Spins on read/write locks (locks not acquired on first try)rate per second during the sampling period. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the spins on read write locks rate of the system orof each processor of the SMP system. Available on Solaris only.

System Calls System calls rate per second during the sampling period. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to determine the system calls rate of the system or of eachprocessor of the SMP system. Available on Solaris only.

System CPU (Percent) Percent of system CPU time during the sampling period.The following values are valid: numeric values in the range 0 to 100. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected. Use this attributeto determine the percentage of system or per processor CPU time devoted toexecuting UNIX system kernel code. System CPU time includes time spentexecuting system calls and performing administrative functions. Available on allplatforms.




Thread Migrations Thread migrations to another processor rate per second duringthe sampling period. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum. Use this attribute to determine the rate ofthread migrations to another processor of the system or of each processor of theSMP system. Available on Solaris only.



YY = Year




MM = Minute

SS = Second


mmm = Millisecond

User CPU (Percent) Percent of user CPU time during the sampling period. Thefollowing values are valid: numeric values in the range 0 to 100. Note: the value -1indicates Not Available and -2 indicates Not Collected. Use this attribute todetermine the percentage of system or per processor CPU time devoted to userprocesses. User CPU time includes time spent executing both user program andlibrary functions. It does not include CPU time spent executing system calls. Theratio between user and system CPU time varies, depending on the kinds ofprograms executing. If user CPU is extremely high and adversely affecting systemperformance, you might want to determine which user programs are preventingthe CPU from functioning at its normal speed. Available on all platforms.

Wait I/O Percent of wait I/O CPU time during the sampling period. The followingvalues are valid: numeric values in the range 0 to 100. Note: the value -1 indicatesNot Available and -2 indicates Not Collected. Use Wait I/O to indicate howeffectively the system or a processor is using disks. Available on all platform.

Solaris Zones attributesThe Solaris Zones attributes refer to zone characteristics such as init process ID,path, and zone ID.

CPU Share PCT The percent of the processor set available to this zone. Note: thevalue -1 indicates Not Available and the value -2 indicates Not Collected.

CPU Shares The weight used by the fair share scheduler to control CPU usage.Note: the value -1 indicates Not Available, -2 indicates Not Collected, and2147483647 indicates Value_Exceeds_Maximum.

Init Process ID The process ID of the init process for this zone. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Name The name of a zone. Valid entry is a simple text string, alphanumeric with amaximum length 192 characters. Note: the value -1 indicates Not Available and -2indicates Not Collected.

Path The path to the root directory of the zone.

Physical Memory The physical memory in kilobytes used by all processes in thezone. Note: the value -1 indicates Not Available, -2 indicates Not Collected, and2147483647 indicates Value_Exceeds_Maximum.

Pool ID The numeric pool ID this zone is bound to. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Scheduler The scheduler used by the zone. The following values are valid:Fair_Share_Scheduler, Time_Share, Interactive, Fixed_Priority, System, andReal_Time.

Status The status of a zone. Note: the value -1 indicates Not Available and -2indicates Not Collected. The following values are valid:


v Uninitializedv Readyv Bootingv Runningv Shutting Downv Emptyv Downv Dyingv Deadv Initialized






YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Total CPUs The number of CPUs that are in the processor set. Note: the value -1indicates Not Available, -2 indicates Not Collected, and 2147483647 indicatesValue_Exceeds_Maximum.

Virtual Memory The virtual memory in kilobytes used by all processes in thezone. Note: the value -1 indicates Not Available, -2 indicates Not Collected, and2147483647 indicates Value_Exceeds_Maximum.

Zone CPU Usage The CPU usage of all processes in the zone. Note: the value -1indicates Not Available and the value -2 indicates Not Collected.

Zone ID The full name of a user. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.


SP2 System attributesSP2 System is a virtual attribute group that aggregates data at the Tivoli EnterpriseMonitoring Server for the attribute groups of all your instances of the MonitoringAgent for UNIX OS. Any workspace or situation that queries against this attributegroup are fulfilled at the Tivoli Enterprise Monitoring Server. This attribute groupis useful for monitoring a large number of systems to reduce query time andnetwork load. SP2 System attributes refer to system characteristics such as theamount of available virtual memory, idle CPU percentage, the number ofnon-block device reads, and load averages.

Note: This attribute group is not historically collected.

Active Virtual Memory (KBytes) The amount of real memory and secondarystorage, in kilobytes, currently in use by the system for paging, system users, andcaching. On HP-UX and Solaris, this value does not include in-use real memory.This is a deprecated attribute. New queries should utilize the UNIX Memoryattributes for clearer definitions. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Page Ins 1 Minute The average rate of page ins over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Ins 5 Minute The average rate of page ins over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Ins 15 Minutes The average rate of page ins over the last 15 minutes.Displays N/C (not collected) if the agent has been up for less than 15 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Avg Page Outs 1 Minute The average rate of page outs over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Outs 5 Minutes The average rate of page outs over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.




Avg Page Scans 1 Minute The average rate of page scans over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Scans 5 Minutes The average rate of page scans over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Scans 15 Minutes The average rate of page scans over the last 15minutes. Displays N/C (not collected) if the agent has been up for less than 15minutes. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Avg Processes RunQueue 60 Minutes The average number of processes in the runqueue over the last 60 minutes. Displays N/C (not collected) if the agent has beenup for less than 60 minutes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Block Reads The number of physical block reads over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Block Writes The number of physical block writes (synchronous+ asynchronous)over a specified sampling period. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Boot Time The system boot time on the monitored system. Valid entries are in theformat CYYMMDDHHMMSSmmm, where:



YY = Year




MM = Minute

SS = Second

mmm = Millisecond

CPU Busy (Percent) The sum of the System and User CPU attributes in percent.The following values are valid: numeric values in the range 0 to 100. Note: thevalue -1 indicates Not Available, and -2 indicates Not Collected.

CPU Context Switches Number of CPU context switches over the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Device Interrupts The number of non-clock device interrupts over the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Execs Executed The number of execs executed over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Forks Executed The number of forks executed over the sampling interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Free Virtual Memory (KBytes) The amount of unused real memory and secondarystorage in kilobytes, currently free for the system to use for paging. On HP-UX andSolaris, this value does not include unused real memory. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Idle CPU (Percent) The percentage of time the CPU is not processing instructions.The following values are valid: numeric values in the range 0 to 100. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected.

IPv6_Address The IPv6 address corresponding to the system host name. Thisattribute only supports IPv6 addresses. The following values are valid:Not_Collected and Not_Available among others.

Load Average 1 Min The average number of processes in the run queue of theUNIX kernel during the last minute. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Load Average 15 Min The average number of processes in the UNIX kernel runqueue during the last 15 minutes. Note: the value -1 indicates Not Available, -2



Load Average 5 Min The average number of processes in the UNIX kernel runqueue during the last 5 minutes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Logical Block Reads Number of logical block reads of system buffers during thesampling interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Logical Block Writes Number of logical block writes of system buffers during thesampling interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Net Address The Internet Protocol (IP) address of a monitored system, expressedin dotted decimal format. Valid entry is a simple text string, alphanumeric. Thefollowing values are valid: Not_Collected and Not_Available among others. Thisattribute only supports IPv4 addresses.

NonBlock Reads Number of physical block reads (synchronous + asynchronous)during the sampling interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

NonBlock Writes The number of raw I/O writes over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Number of System Procs The number of processes running on the system,including both system and user processes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Number of Users Sessions The number of interactive user sessions running. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Faults (Per Sec) The average rate of page faults per second. Note: the value-1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Page Ins (Per Sec) The average rate per second of page-in requests over a specifiedsampling period. A page-in request might include multiple pages and gives anindication of the I/O rate on the paging file. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.


Page Ins Rate The number of kilobytes that the virtual memory manager pages inper second. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Outs (Per Sec) The average rate per second of page-out requests over aspecified sampling period. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Out Rate The number of kilobytes that the virtual memory manager pagesout per second. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Reclaims (Per Sec) The number of times during the monitoring interval thatthe system removed a page from the queue and used that page for anotherprocess. This is the average rate per second. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Page Scan Rate (Per Sec) The average rate per second of pages examined over thesampling interval. Virtual memory manager uses a clock-algorithm to implement apseudo “least recently used (lsu), page replacement scheme. Pages are aged byexamination by the clock. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Scanning The number of kilobytes that the virtual memory manager pagesscans per second. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Pages Paged In (Per Sec) The average rate per second of pages that were paged-infrom disk to system memory during the monitoring interval. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Pages Paged Out (Per Sec) The average rate per second of pages paged-out fromsystem memory to disk during the monitoring interval. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Idle Number of processes currently in idle state. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Runnable Number of processes waiting to be run. (For AIX and HP-UX,this includes both the processes able to be run as well as the running processes.)For AIX, they are the processes in the SACTIVE state: active. For HP-UX, they arethe processes in the PS_RUN state: running or waiting for CPU. For Solaris theyare the processes in the R (SRUN) state: able to be run, but not currently running.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Processes Running Number of processes currently running on a processor(available for Solaris only). For Solaris, it is the number of processes in the O(SONPROC) state: running. This attribute is not available for AIX and HP-UXbecause, on these systems, this information is collected as part of the ProcessesRunnable attribute. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Processes Sleeping Number of processes currently in sleep state. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Stopped Number of processes currently in the stopped state. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Threads in Run Queue The total number of processes that can be run(or threads in AIX 4 1 and above) waiting for execution by the CPU. This numberdoes not include processes waiting for I/O or some external event, or processes ina sleeping state. The following values are valid: numeric values in the range 0 to999. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Processes Threads Waiting The number of processes (or threads in AIX 4 1 andabove) waiting for page operations. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Processes Zombie Number of zombie processes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Swap Space Free Amount of swap space (in MB) available. Swap space is usuallya disk partition on which page-outs are written. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

System Calls Number of system calls made during the sampling interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

System CPU (Percent) The percentage of CPU time devoted to executing UNIXsystem kernel code. The following values are valid: numeric values expressed as apercentage in the range 1 to 100. Note: the value -1 indicates Not Available and -2indicates Not Collected.





System Read The number of read and readv system calls during the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

System Write Number of write and writev system calls over the sampling interval.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.



YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Total Real Memory (KBytes) The total number of kilobytes of physical memory(primary paging memory) on the monitored system. This is a deprecated attribute.New queries should utilize the UNIX Memory attributes for clearer definitions.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Total Virtual Memory (KBytes) The Virtual memory is the total amount memorythat is available virtually. The total amount memory that is displayed (virtual) tobe available is nothing but the real memory and the part of the disk (paging space)that is available for usage as memory. This is a deprecated attribute. New queriesshould utilize the UNIX Memory table attributes for more clear definitions. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Type The type of UNIX operating system residing on a monitored host. Forexample, you might see AIX, HPUX, SunOS or OSF1 displayed on your system.The following values are valid:

AIX The IBM AIX operating system

HPUX The Hewlett Packard HP-UX operating system

SunOS Sun Microsystems Solaris I or II operating system

v Maximum length 8 characters


Up Time (Seconds) The number of seconds that a monitored system has beenrunning continuously. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

UpTime The system up time of the monitored system. Valid entries in the formatDDDdHH:MM:SS, where:

DDD = Days

HH = Hours

MM = Minutes

SS = Seconds

User CPU (Percent) The percentage of processor time devoted to user processes.The following values are valid: numeric values expressed as a percentage in therange 0 to 100. Note: the value -1 indicates Not Available and -2 indicates NotCollected.

Version The version number of a UNIX operating system on the network. Validentry is a simple text string, alphanumeric with a maximum length of 16characters.

Virtual Memory Percent Available Percent of virtual memory available. This iscalculated by the agent using the formula:

100 - Percent_Virtual_Memory_Used.

The following values are valid: numeric values in the range 0 to100.0 to onedecimal place. Note: the value -1 indicates Not Available, and -2 indicates NotCollected.

Virtual Memory Percent Used Percent of virtual memory used. This calculated bythe agent using the formula:

Active_Virtual_Memory / Total_Virtual_Memory * 100.

The following values are valid: numeric values in the range 0 to 100.0 to onedecimal place. Note: the value -1 indicates Not Available, and -2 indicates NotCollected.

Wait I/O (Percent) The percentage of time the CPU spends waiting for I/Ooperations. The following values are valid: numeric values in the range 0 to 100.Note: the value -1 indicates Not Available, and -2 indicates Not Collected.




System attributesSystem attributes refer to system characteristics such as the amount of availablevirtual memory, idle CPU percentage, the number of non-block device reads, andload averages.

Active Virtual Memory (KBytes) The amount of real memory and secondarystorage, in kilobytes, currently in use by the system for paging, system uses andcaching. On HP-UX and Solaris, this value does not include in-use real memory.This is a deprecated attribute. New queries should utilize the UNIX Memoryattributes for clearer definitions. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Avg Page Ins 1 Minute The average rate of page ins over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Ins 5 Minute The average rate of page ins over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.



Avg Page Outs 1 Minute The average rate of page outs over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.





Avg Page Scans 1 Minute The average rate of page scans over the last 1 minute.Displays N/C (not collected) if the agent has been up for less than 1 minute. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Avg Page Scans 5 Minutes The average rate of page scans over the last 5 minutes.Displays N/C (not collected) if the agent has been up for less than 5 minutes.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.



Avg Processes RunQueue 60 Minutes The average number of processes in the runqueue over the last 60 minutes. Displays N/C (not collected) if the agent has beenup for less than 60 minutes. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Block Reads The number of physical block reads over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Block Writes The number of physical block writes (synchronous+ asynchronous)over a specified sampling period. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Boot Time The system boot time on the monitored system. Valid entries are in theformat CYYMMDDHHMMSSmmm, where:


YY = Year





MM = Minute

SS = Second

mmm = Millisecond

CPU Busy (Percent) The sum of the System and User CPU attributes in percent.The following values are valid: numeric values in the range 0 to 100. Note: thevalue -1 indicates Not Available, and -2 indicates Not Collected.

CPU Context Switches Number of CPU context switches over the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Device Interrupts The number of non-clock device interrupts over the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Execs Executed The number of execs executed over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Forks Executed The number of forks executed over the sampling interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Free Virtual Memory (KBytes) The amount of unused real memory and secondarystorage in kilobytes, currently free for the system to use for paging. On HP-UX andSolaris, this value does not include unused real memory. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Idle CPU (Percent) The percentage of time the CPU is not processing instructions.The following values are valid: numeric values in the range 0 to 100. Note: thevalue -1 indicates Not Available and -2 indicates Not Collected.

IPv6_Address The IPv6 address corresponding to the system host name. Thisattribute only supports IPv6 addresses. The following values are valid:Not_Collected and Not_Available among others.

Load Average 1 Min The average number of processes in the run queue of theUNIX kernel during the last 1 minute. Note: the value -1 indicates Not Available,-2 indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Load Average 15 Min The average number of processes in the UNIX kernel runqueue during the last 15 minutes. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Load Average 5 Min The average number of processes in the UNIX kernel runqueue during the last 5 minutes. Note: the value -1 indicates Not Available, -2



Logical Block Reads Number of logical block reads of system buffers during thesampling interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Logical Block Writes Number of logical block writes of system buffers during thesampling interval. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Net Address The Internet Protocol (IP) address of a monitored system, expressedin dotted decimal format. Valid entry is a simple text string, alphanumeric. Thefollowing values are valid: Not_Collected and Not_Available among others. Thisattribute only supports IPv4 addresses.

NonBlock Reads Number of physical block reads (synchronous + asynchronous)during the sampling interval. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

NonBlock Writes The number of raw I/O writes over a specified sampling period.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Number of System Procs The number of processes running on the system,including both system and user processes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Number of Users Sessions The number of interactive user sessions running. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Page Faults (Per Sec) The average rate of page faults per second. Note: the value-1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Page Ins (Per Sec) The average rate per second of page-in requests over a specifiedsampling period. A page-in request might include multiple pages and gives anindication of the I/O rate on the paging file. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Page Ins Rate The number of kilobytes that the virtual memory manager pages inper second. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.


Page Outs (Per Sec) The average rate per second of page-out requests over aspecified sampling period. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Out Rate The number of kilobytes that the virtual memory manager pagesout per second. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Reclaims (Per Sec) The number of times during the monitoring interval thatthe system removed a page from the queue and used that page for anotherprocess. This is the average rate per second. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Page Scan Rate (Per Sec) The average rate per second of pages examined over thesampling interval. Virtual memory manager uses a clock-algorithm to implement apseudo “least recently used (lsu), page replacement scheme. Pages are aged byexamination by the clock. Note: the value -1 indicates Not Available, -2 indicatesNot Collected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Page Scanning The number of kilobytes that the virtual memory manager pagesscans per second. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Pages Paged In (Per Sec) The average rate per second of pages that were paged-infrom disk to system memory during the monitoring interval. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Pages Paged Out (Per Sec) The average rate per second of pages paged-out fromsystem memory to disk during the monitoring interval. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Idle Number of processes currently in idle state. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Runnable Number of processes waiting to be run. (For AIX and HP-UX,this includes both the processes able to be run as well as the running processes.)For AIX, they are the processes in the SACTIVE state: active. For HP-UX, they arethe processes in the PS_RUN state: running or waiting for CPU. For Solaris theyare the processes in the R (SRUN) state: able to be run, but not currently running.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Processes Running Number of processes currently running on a processor(available for Solaris only). For Solaris, it is the number of processes in the O(SONPROC) state: running. This attribute is not available for AIX and HP-UXbecause, on these systems, this information is collected as part of the Processes


Runnable attribute. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

Processes Sleeping Number of processes currently in sleep state. Note: the value -1indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Stopped Number of processes currently in the stopped state. Note: thevalue -1 indicates Not Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Processes Threads in Run Queue The total number of processes that can be run(or threads in AIX 4 1 and above) waiting for execution by the CPU. This numberdoes not include processes waiting for I/O or some external event, or processes ina sleeping state. The following values are valid: numeric values in the range 0 to999. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Processes Threads Waiting The number of processes (or threads in AIX 4 1 andabove) waiting for page operations. Note: the value -1 indicates Not Available, -2indicates Not Collected, 2147483647 indicates Value_Exceeds_Maximum, and-2147483648 indicates Value_Exceeds_Minimum.

Processes Zombie Number of zombie processes. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Swap Space Free Amount of swap space (in MB) available. Swap space is usuallya disk partition on which page-outs are written. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

System Calls Number of system calls made during the sampling interval. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

System CPU (Percent) The percentage of CPU time devoted to executing UNIXsystem kernel code. The following values are valid: numeric values expressed as apercentage in the range 1 to 100. Note: the value -1 indicates Not Available and -2indicates Not Collected.





System Read The number of read and readv system calls during the samplinginterval. Note: the value -1 indicates Not Available, -2 indicates Not Collected,2147483647 indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

System Write Number of write and writev system calls over the sampling interval.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.



YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Total Real Memory (KBytes) The total number of kilobytes of physical memory(primary paging memory) on the monitored system. This is a deprecated attribute.New queries should utilize the UNIX Memory attributes for clearer definitions.Note: the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Total Virtual Memory (KBytes) The Virtual memory is the total amount memorythat is available virtually. The total amount memory that is displayed (virtual) tobe available is nothing but the real memory and the part of the disk (paging space)that is available for usage as memory. This is a deprecated attribute. New queriesshould utilize the UNIX Memory table attributes for more clear definitions. Note:the value -1 indicates Not Available, -2 indicates Not Collected, 2147483647indicates Value_Exceeds_Maximum, and -2147483648 indicatesValue_Exceeds_Minimum.

Type The type of UNIX operating system residing on a monitored host. Forexample, you might see AIX, HPUX, SunOS or OSF1 displayed on your system.The following values are valid:

AIX The IBM AIX operating system

HPUX The Hewlett Packard HP-UX operating system

SunOS Sun Microsystems Solaris I or II operating system

v Maximum length 8 characters


Up Time (Seconds) The number of seconds that a monitored system has beenrunning continuously. Note: the value -1 indicates Not Available, -2 indicates NotCollected, 2147483647 indicates Value_Exceeds_Maximum, and -2147483648indicates Value_Exceeds_Minimum.

UpTime The system up time of the monitored system. Valid entries in the formatDDDdHH:MM:SS, where:

DDD = Days

HH = Hours

MM = Minutes

SS = Seconds

User CPU (Percent) The percentage of processor time devoted to user processes.The following values are valid: numeric values expressed as a percentage in therange 0 to 100. Note: the value -1 indicates Not Available and -2 indicates NotCollected.

Version The version number of a UNIX operating system on the network. Validentry is a simple text string, alphanumeric with a maximum length of 16characters.

Virtual Memory Percent Available Percent of virtual memory available. This iscalculated by the agent using the formula:

100 - Percent_Virtual_Memory_Used.

The following values are valid: numeric values in the range 0 to100.0 to onedecimal place. Note: the value -1 indicates Not Available, and -2 indicates NotCollected.

Virtual Memory Percent Used Percent of virtual memory used. This calculated bythe agent using the formula:

Active_Virtual_Memory / Total_Virtual_Memory * 100.

The following values are valid: numeric values in the range 0 to 100.0 to onedecimal place. Note: the value -1 indicates Not Available, and -2 indicates NotCollected.

Wait I/O (Percent) The percentage of time the CPU spends waiting for I/Ooperations. The following values are valid: numeric values in the range 0 to 100.Note: the value -1 indicates Not Available, and -2 indicates Not Collected.




User attributesThe User Attributes refer to user characteristics such as idle time, user name,location, and login time.

Idle Time The number of minutes that have passed since a user last entered acommand. Use this attribute to check idle time. Note: the value -1 indicates NotAvailable, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.

Location Information provided by the user about their location. Valid entry is asimple text string, alphanumeric with a maximum length 16 characters. Thisinformation varies from location to location, and might not be available for allusers or for all UNIX operating systems. Check with your local SystemAdministrator for additional information concerning this attribute.

Login Name The login name of a user. Valid entry is a simple text string,alphanumeric with a maximum length 16 characters. Use this attribute to includeor exclude specific user login names in the situation.

Login Name (Unicode) The login name of a user. Use this attribute to include orexclude specific user login names in the situation.

Login Time The date and time a user logged in. Valid entries are in the formatCYYMMDDHHMMSSmmm, where:


YY = Year




MM = Minute

SS = Second

mmm = Millisecond

Example To express November 6, 1998, 1:05 p.m., enter 0981106130500000.

Name The full name of a user. Valid entry is a simple text string, alphanumericwith a maximum length 32 characters.

Name (Unicode) The full name of a user.




Terminal The identity of a logged-in device. Valid entry is a simple text string,alphanumeric with a maximum length 8 characters.


Example A value of w14921 could be the name of a device. This could indicate alocation, such as Wood Lake. Your location might already have a namingconvention for network devices. Check with your local system administrator foradditional information.



YY = Year




MM = Minute

SS = Second

mmm = Millisecond

User ID The numeric ID the system assigned to a user. Note: the value -1 indicatesNot Available, -2 indicates Not Collected, 2147483647 indicatesValue_Exceeds_Maximum, and -2147483648 indicates Value_Exceeds_Minimum.Use this attribute to include or exclude a particular user in the situation. Thisattribute is supported on all platforms. On AIX, you need a patch from IBM inorder to get the user ID.

The numeric identification number varies from system to system and user to user.An example of a user ID could be 48765.

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

Expected number of instances is a guideline that can be different for each attributegroup, because it is the number of instances of data that the agent will return for agiven attribute group, and depends on the application environment that is beingmonitored. For example, if your attribute group is monitoring each processor onyour computer and you have a dual processor computer, the number of instancesis 2.

Calculate expected disk space consumption by multiplying the number of bytesper instance by the expected number of instances, and then multiplying thatproduct by the number of samples. Table 2 on page 107 provides the followinginformation required to calculate disk space for the Monitoring Agent for UNIXOS:v Bytes per instance (agent) is an estimate of the record length for each row or

instance written to the agent disk for historical data collection. This estimate canbe used for agent disk space planning purposes.


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

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

v Number of rows stored in warehouse per historical collection query is an estimate ofthe number of rows that are stored in the Tivoli Data Warehouse per query.

The IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can beused to estimate the amount of disk space used at the agent and in the warehousedatabase for historical data collection of an attribute group.

Table 2. Capacity planning for historical data logged by component

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

UNIXDISK Disk 1212 1285 2166

UNIXDPERF Disk_Performance 328 299 843

FILEINFO File_Information 4212 4260 4508

KUXPASSTAT KCA_UX_Agent_Active_Runtime_Status 1410 1435 1472

KUXPASMGMT KCA_UX_Agent_Availability_Management_\Status

538 542 579

KUXPASALRT KCA_UX_Alerts_Table 512 516 553

KUXPASCAP KCA_UX_Configuration_Information 3090 3132 3169

UNIXMACHIN Machine_Information 536 540 577

UNIXNFS N_F_S_and_R_P_C_Statistics 520 449 3138

UNIXNET Network 524 605 2022

UNIXPS Process 2288 2264 3003

UNIXCPU SMP_CPU 364 264 1471

UNIXSOLZON Solaris_Zones 550 583 800

UNIXOS System 844 846 3670

UNIXIPADDR UNIX_IP_Address 574 578 615

UNIXALLUSR Unix_All_Users 188 189 265

UNIXFILCMP Unix_File_Comparison 1652 1660 1697

UNIXFILPAT Unix_File_Pattern 1652 1660 1697

UNIXGROUP Unix_Group 164 163 200

UNIXMEM Unix_Memory 256 361 1874

UNIXPING Unix_Ping 884 899 987

UNXPRINTQ Unix_Print_Queue 316 309 424

UNIXUSER User 312 310 386


Note: FILEINFO cannot be historically collected.

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


Chapter 5. Situations reference

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

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

The IBM Tivoli Monitoring agents that you use to monitor your systemenvironment are delivered with a set of predefined situations that you can use as-isor you can create new situations to meet your requirements. Predefined situationscontain attributes that check for system conditions common to many enterprises.

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

Note: The predefined situations provided with this monitoring agent are notread-only. Do not edit these situations and save over them. Software updateswill 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 theSituation editor. The left frame of the Situation editor initially lists the situationsassociated with the Navigator item that you selected. When you click a situationname or create a new situation, the right frame opens with the following tabs:

FormulaCondition being tested

DistributionList of managed systems (operating systems, subsystems, or applications)to which the situation can be distributed.

Expert AdviceComments and instructions to be read in the event workspace

ActionCommand to be sent to the system

Until Duration of the situation

The Monitoring Agent for UNIX OS predefined situations describe systemconditions on your UNIX networked systems that you want to monitor at yoursite. Use these situations to being monitoring any UNIX managed object quickly, oras models for customizing your own situations. In some cases, the values that areassigned to the predefined situations are examples only and should be modified toreflect the conditions of your distributed system. Each predefined situation isassigned to a predefined template, and an alert status for the situation is defined.


More information about situationsThe IBM Tivoli Monitoring User's Guide contains more information about predefinedand custom situations and how to use them to respond to alerts.

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

For additional information about the situations for this monitoring agent, seeAppendix C, “Situations,” on page 137.

Predefined situationsThis monitoring agent contains the following predefined situations, which areorganized by the Navigator item that the situations are associated with.v Agent Management Services situations

– UMX_AMS_Alert_Criticalv Disk Usage situations

– UNIX_Disk_Availability– UNIX_CMD_Disk_Inodes_Critical– UNIX_CMD_Disk_Inodes_Critical_2– UNIX_CMD_Disk_Space_Warning– UNIX_Filemount_Critical– UNIX_HD_Config_Critical– UNIX_HD_Config_Critical_2– UNIX_scratch_tmp_Disk_Full

v File Information situation– UNIX_User_File_Exists

v Network situations– UNIX_Network_Collsns_Critical– UNIX_Network_Collsns_Warning– UNIX_Network_Errors– UNIX_Network_Interface_Busy– UNIX_Network_Interface_Idle

v NFS Activity situation– UNIX_NFS_RPC_Rejects

v Process situations– UNIX_CMD_Process_Critical– UNIX_CMD_Runaway_Process– UNIX_CPU_Critical– UNIX_CPU_Warning– UNIX_Process_Memory_Critical– UNIX_Process_Memory_Leak– UNIX_Process_Memory_Warning– UNIX_Process_MISSING_inetd

v System Information situations– UNIX_Active_Virtual_Memory


– UNIX_CPU_Busy_Critical– UNIX_CPU_Busy_Warning– UNIX_HD_Excessive_IO_Wait– UNIX_System_Busy_Critical– UNIX_System_Busy_Warning– UNIX_System_Capacity_Critical– UNIX_System_Paging_Critical– UNIX_System_Virtual_Memory_Warning– UNIX_User_CPU_Critical

The remaining sections of this chapter contain descriptions of each of thesepredefined situations. The situations are organized by the Navigator item that thesituations are associated with.

Agent Management Services situation

UNIX_AMS_Alert_Critical situationDetermines if one of the following conditions is true:v A managed agent has exceeded its restart count for the day as configured in the

'maxRestarts' field of its Common Agent Package file.v A managed agent is overutilizing the available CPU resources as configured in

the 'cpuThreshold' field of its Common Agent Package file.v A managed agent is overutilizing the available system memory resources as

configured in the 'memoryThreshold' field of its Common Agent Package file.v An attempt at auto-restarting a managed agent failed.v An attempt at starting a stopped or manually stopped managed agent failed.v The Agent Management Services watchdog is no longer reliable. If either

watchdog stops monitoring, you will receive this message.

The formula for this situation is as follows:Alert Message=='Agent exceeded restart count' ORAlert Message=='Agent overutilizing CPU' ORAlert Message=='Agent overutilizing memory' ORAlert Message=='Agent restart failed' ORAlert Message=='Agent manual stop failed' ORAlert Message =='Agent Management Services watchdog no longer reliable'

Disk Usage situations

UNIX_Disk_Availability situationDetermines under-utilized hard disk space.

The formula for this situation is as follows:IF Disk.Mount_Point EQ /user AND Disk.Space_Used_Percent LT 25

UNIX_CMD_Disk_Inodes_Critical situationSuperseded by UNIX_CMD_Disk_Inodes_Critical_2. Monitors the /tmp and /varfree inodes for critical space.

The formula for this situation is as follows:IF Disk.Mount_Point EQ /tmp OR Disk.Mount_Point EQ /var) AND Disk.Inodes_FreeLT 20000 ACTION echo UNIX_CMD_Disk_Inodes_Critical &Disk.System_Name Low freeinodes on /tmp and /var

Chapter 5. Situations reference 111

UNIX_CMD_Disk_Inodes_Critical_2 situationMonitors the /tmp and /var free inodes for critical space.

The formula for this situation is as follows:IF Disk.Mount_Point_U EQ /tmp OR Disk.Mount_Point_U EQ /var)AND Disk.Inodes_Free_64LT 20000 ACTION echo UNIX_CMD_Disk_Inodes_Critical_2&Disk.System_Name Low free inodes on /tmp and /var

UNIX_CMD_Disk_Space_Warning situationMonitors any mounted file system with space usage greater than 90 percent.

The formula for this situation is as follows:IF Disk.Space_Used_Percent GE 90 ACTION echo UNIX_CMD_Disk_Space_Warning&Disk.System_Name Filemount: &Disk.Mount_Point Space_Used: &Disk.Space_Used_Percent

UNIX_Filemount_Critical situationChecks for the existence of a specific mount point on a specific system.

The formula for this situation is as follows:IF Disk.System_Name EQ Redwood AND Disk.Mount_Point EQ /usr

UNIX_HD_Config_Critical situationSuperseded by UNIX_HD_Config_Critical_2. Monitors hard disk space or freeinodes that are going critical.

The formula for this situation is as follows:IF Disk.Inodes_Free LT 100 OR Disk.Space_Used_Percent GT 90

UNIX_HD_Config_Critical_2 situationMonitors hard disk space or free inodes that are going critical.

The formula for this situation is as follows:IF Disk.Inodes_Free_64 LT 100 OR Disk.Space_Used_Percent GT 90

UNIX_scratch_tmp_Disk_Full situationMonitors file mount /scratch or /tmp with space usage greater than 90 percent.

The formula for this situation is as follows:IF Disk.Space_Used_Percent GT 90 AND (SCAN Disk.Mount_Point EQ /scratch ORDisk.Mount_Point *EQ /tmp)

File Information situation

UNIX_User_File_Exists situationMonitors for the existence of a specific user file.

The formula for this situation is as follows:IF File_Information.Path EQ /a/path2/search AND File_Information.File EQthe File_2find


Network situations

UNIX_Network_Collsns_Critical situationIndicates a large number of network collisions.

The formula for this situation is as follows:IF Network.Collisions GT 15

UNIX_Network_Collsns_Warning situationIndicates a small number of network collisions.

The formula for this situation is as follows:IF Network.Collisions GT 2

UNIX_Network_Errors situationMonitors whether the received or transmitted error limit has been exceeded.

The formula for this situation is as follows:IF Network.Interface_Status EQ UP AND (Network.Output_Errors GT 10OR Network.Input_Errors *GT 10)

UNIX_Network_Interface_Busy situationMonitors whether the frames transmitted or received has exceeded the limit.

The formula for this situation is as follows:IF Network.Network_Interface_Name NE Lo0 AND Network.Interface_Status EQUP AND (Network.Frames_Received GT 1000 OR Network.Frames_Transmitted GT1000)

UNIX_Network_Interface_Idle situationMonitors whether the frames transmitted or received is less than the limit.

The formula for this situation is as follows:IF Network.Network_Interface_Name *NE Lo0 AND Network.Interface_Status EQUP AND (Network.Frames_Received LT 100 OR Network.Frames_Transmitted LT 100)

NFS Activity situation

UNIX_NFS_RPC_Rejects situationMonitors for rejected NFS RPC calls.

The formula for this situation is as follows:IF N_F_S_and_R_P_C_Statistics.NFS_Server_Calls_Rejected GT 2OR N_F_S_and_R_P_C_Statistics.NFS_Client_Calls_Rejected GT 2

Process situations

UNIX_CMD_Process_Critical situationMonitors for the existence of a process.

The formula for this situation is as follows:IF Process.Command EQ FOO


UNIX_CMD_Runaway_Process situationReports processes with high CPU utilization.

The formula for this situation is as follows:IF Process.CPU_Utilization GT 95 AND Process.User_ID NE 0 AND(Process.Execution_State EQ R OR Process.Execution_State EQ A)ACTION echo UNIX_CMD_Runaway_Process &Process.System_NameProcessid: &Process.Process_ID Command: &Process.Command

UNIX_CPU_Critical situationMonitors for processes with CPU utilization that is greater than or equal to 85percent.

The formula for this situation is as follows:IF Process.CPU_Utilization GE 85 AND Process.Command NE kproc AND Process.CommandNE swapper

UNIX_CPU_Warning situationMonitors processes with CPU utilization that is greater than or equal to 70 percentand less than 85 percent.

The formula for this situation is as follows:IF Process.CPU_Utilization *GE 70 AND Process.CPU_Utilization LT 85

UNIX_Process_Memory_Critical situationReports process with high memory usage that have reached a critical state.

The formula for this situation is as follows:IF Process.Mem_Pct GT 8000

UNIX_Process_Memory_Leak situationReports process with high virtual memory usage.

The formula for this situation is as follows:IF Process.Virtual_Size GT 9999999

UNIX_Process_Memory_Warning situationReports processes with high memory usage before they become critical.

The formula for this situation is as follows:IF Process.Mem_Pct GT 5000 AND Process.Mem_Pct LT 8000

UNIX_Process_MISSING_inetd situationMonitors whether the inetd Internet services daemon is up and running.

The formula for this situation is as follows:IF MISSING Process.Command EQ ('inetd')

System Information situations

UNIX_Active_Virtual_Memory situationMonitors whether active virtual memory is approaching total virtual memory.

The formula for this situation is as follows:IF System.Active_Virtual_Memory GE nnnn


UNIX_CPU_Busy_Critical situationMonitors whether the CPU workload is high (greater than 90 percent).

The formula for this situation is as follows:IF SMP_CPU.CPU_Busy GT 90

UNIX_CPU_Busy_Warning situationMonitors whether the CPU workload is greater than 70 percent and less than orequal to 90 percent.

The formula for this situation is as follows:IF SMP_CPU.CPU_Busy GT 70 AND SMP_CPU.CPU_Busy LE 90

UNIX_HD_Excessive_IO_Wait situationMonitors a typical I/O bound processor (NSF).

The formula for this situation is as follows:IF System.Wait_I/O GT 20

UNIX_System_Busy_Critical situationMonitors for a critical state of I/O wait, low free memory, and CPU idle.

The formula for this situation is as follows:IF System.Wait_I/O GT 25 AND System.Free_Memory LT 1 AND System.Idle_CPUGT 10 AND System.Load_Average_1_Min GT 2

UNIX_System_Busy_Warning situationMonitors for system CPU, idle, I/O wait, and load average for busy state.

The formula for this situation is as follows:IF System.System_CPU GT 50 AND System.Idle_CPU GT 0 AND System.Wait_I/O GT0 AND System.Load_Average_5_Min GT 1

UNIX_System_Capacity_Critical situationMonitors system capacity using a process number and CPU usage.

The formula for this situation is as follows:IF System_Proc_Number GE 250 AND System.System_CPU GT 80

UNIX_System_Paging_Critical situationMonitors if the virtual memory manager is working too hard to find free pages.

The formula for this situation is as follows:IF System.Page_Scan_Rate GT 500

UNIX_User_CPU_Critical situationMonitors if user CPU usage is system dominant and impacts users.

The formula for this situation is as follows:IF System.User_CPU GE 0 AND System.User_CPU LT 70 AND System.System_CPU GT40

UNIX_System_Virtual_Memory_Warning situationMonitors if the available virtual memory is running low.

The formula for this situation is as follows:


IF System.Virtual_Memory_Percent_Used GT 90


Chapter 6. Take Action commands reference

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

About Take Action commandsTake Action commands can be run from the desktop or included in a situation or apolicy.

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

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

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

Predefined Take Action commandsThis monitoring agent contains the following Take Action commands:v AMS Recycle Agent Instancev AMS Reset Agent Daily Restart Countv AMS Start Agentv AMS Start Agent Instancev AMS Stop Agentv AMS Start Managementv AMS Stop Managementv Sample_kill_Process

The remaining section of this chapter contains a description of the Take Actioncommand. The following information is provided about Take Action commands:

DescriptionWhich actions the command performs on the system to which it is sent

ArgumentsList of arguments, if any, for the Take Action with a short description anddefault value for each one


Destination systemsWhere the command is to be run: on the Managed System (monitoringagent) where the agent resides or on the Managing System (TivoliEnterprise Monitoring Server) to which it is connected

Usage notesAdditional relevant notes for using the Take Actions

AMS Recycle Agent Instance

DescriptionUse this action to stop and start any agent with a single request. This recycle doesnot increase the restart count of an agent.

ArgumentsAgent Name

The name of the agent as it is displayed in the Agents' Runtime StatusView's Agent Name column.

Process NameThe name of the agent's process as it is displayed in the Agents' RuntimeStatus View's Process Name column.

Instance NameIf it exists, the name of an agent instance as it is displayed in the Agents'Runtime Status View's Instance Name column.

Process IDThe process ID of the agent process as it appears in the Agents' RuntimeStatus View's Process ID column.

Destination systemsManaged system

Usage notesNot available to previous versions of the OS agents. To use this action against theOS agent, the Agent Management Services watchdog must be running.

AMS Reset Agent Daily Restart Count

DescriptionUse this action to reset the daily restart count of an agent to 0.

ArgumentsAgent Name


Process NameThe name of the agent's process as it is displayed in the Agents' RuntimeStatus View's Process Name column.

Instance NameIf it exists, the name of an agent instance as it is displayed in the Agents'Runtime Status View's Instance Name column.



Usage notesNot available to previous versions of the OS agents. To use this action against theOS agent, the Agent Management Services watchdog must be running.

AMS Start Agent action

DescriptionUse this action to start an agent that is under the management of AgentManagement Services. The action includes an optional input field for resetting theDaily Restart Count back to 0. This action is helpful when an agent has exceededits maxRestartCount for the day.

ArgumentsAgent Name


Daily Restart CountValue indicating whether to reset the daily restart count. The value 1indicates True, and the value 0 (default) indicates False.

Process NameThe name of the process representing the agent instance as it is displayedin the Agents' Runtime Status View's Process Name column.


Usage notesYou cannot target the Monitoring Agent for UNIX OS with this action. Only theother agents being managed by Agent Management Services running on theMonitoring Agent for UNIX OS can be targeted with this action.

AMS Start Agent Instance action

DescriptionUse this action to start a monitoring agent instance of type ITM Windows or ITMUNIX that is under the management of Agent Management Services. The actionincludes an optional input field for resetting the Daily Restart Count back to 0.This action is helpful when an agent instance has exceeded its maxRestartCountfor the day.

ArgumentsAgent Name


Daily Restart CountValue indicating whether to reset the daily restart count. The value 1indicates True, and the value 0 (default) indicates False.

Process NameThe name of the process representing the agent instance as it is displayedin the Agents' Runtime Status View's Process Name column.

Chapter 6. Take Action commands reference 119

Instance NameThe name of the monitoring agent instance as it is displayed in the Agents'Runtime Status View's Instance Name column.



AMS Stop Agent action

DescriptionUse this action to stop an agent that is under the management of AgentManagement Services. The action will put a running instance of an agent into the'Manually Stopped' state, meaning that Agent Management Services will notperform any auto-restarts. To prompt Agent Management Services to commenceauto-restarting, use the AMS Start Agent command or the AMS Start AgentInstance command to manually put the agent back into a Running state.

ArgumentsProcess ID

By default, this argument is populated with the Process ID of the particularagent instance selected from the Tivoli Enterprise Portal. To stop allinstances of an agent, such as by using the tacmd executeaction AMS StopAgent command, leave this argument blank.



AMS Start Management action

DescriptionUse this action to put an agent under the management of Agent ManagementServices. This management provides the auto-restart capability.


Usage notesYou now can target the Monitoring Agent for UNIX OS with this command.Starting management of the OS Agent restarts the physical watchdog and rearmsAgent Management Services. Watch of managed agents resumes. There is nochange to non-OS agent management operations.


AMS Stop Management action

DescriptionUse this action to remove an agent from management by Agent ManagementServices. The action will cause the Agent Management Services watchdog to stopperforming health checks and auto restarts.


Usage notesYou now can target the Monitoring Agent for UNIX OS with this command.However, stopping management stops the physical watchdog and disarms AgentManagement Services, which also stops watching and restarting of any managedagents. While the OS Agent is unmanaged, the Start Manage action will not beallowed against any other non-OS agent. The UNIX_AMS_Alert_Critical situationis activated if this take action is run on the OS agent.

Sample_kill_Process action

DescriptionKills the process named in the parameter supplied and enables you to issue ad-hoccommands from the Tivoli Enterprise Portal that the Monitoring Agent for UNIXOS will run on your behalf.

ArgumentsProcess ID

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


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

Chapter 6. Take Action commands reference 121


Chapter 7. Policies reference

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

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

A policy is a set of automated system processes that can perform actions, schedulework for users, or automate manual tasks. You use the Workflow Editor to designpolicies. You control the order in which the policy runs a series of automated steps,which are also called activities. Policies are connected to create a workflow. Afteran activity is completed, Tivoli Enterprise Portal receives return code feedback andadvanced automation logic responds with subsequent activities prescribed by thefeedback.

Note: The predefined policies provided with this monitoring agent are notread-only. Do not edit these policies and save over them. Software updateswill 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 policiesFor more information about working with policies, see the IBM Tivoli MonitoringUser's Guide.

For information about using the Workflow Editor, see the IBM Tivoli MonitoringAdministrator'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 sectionfor each individual policy.

Predefined policiesThis monitoring agent contains the following predefined policies:v UNIX_CPU_Busyv UNIX_Disk_Space_Fullv UNIX_Virtual_Memory_High

The remaining sections of this chapter contain descriptions of these policies, whichare listed alphabetically.

UNIX_CPU_Busy policyWhen the Runaway_Process and CPU_Critical situations are both true, you canchoose to send a message or to terminate the runaway process (after confirmationfrom an administrator, if possible).v If the termination fails, the administrator is informed, and the policy completes.


v If the termination succeeds, the policy waits and re-evaluates the CPU_Criticalsituation.

v If the CPU_Critical situation is still true, the administrator is informed.

UNIX_Disk_Space_Full policyWhen the Disk_Space_Warning and the scratch-tmp_Disk_Full situations are bothtrue, you can choose to perform the following actions:v Compress all files that reside at mount point /scratch or /tmp.v Remove all files which reside at mount point /scratch or /tmp.v After a timeout with no user choice, echo a message.

UNIX_Virtual_Memory_High policyWhen the Virtual_Memory_Warning and the Process Memory Leak situations areboth true, the process identified in the Process Memory Leak event is terminated.v If the termination fails, the administrator is informed, and the policy completes.v If the termination succeeds, the policy waits and reevaluates the

Virtual_Memory_Warning situation.v If the Virtual_Memory_Warning situation is still true, the administrator is

informed.


Appendix A. Upgrading for warehouse summarization

The Monitoring Agent for UNIX OS made changes to the warehouse collection andsummarization characteristics for some agent attribute groups. These changescorrect and improve the way warehouse data is summarized, producing moremeaningful historical reports. This appendix explains those changes and theimplications to your warehouse collection and reporting.

Note: This upgrade is only available from IBM Tivoli Monitoring v6.1.0 to v6.2.1,and is not available for upgrading from IBM Tivoli Monitoring v6.2 tov6.2.1.

Warehouse summarization is controlled on a per-table basis. How the rows in eachtable are summarized is determined by a set of attributes in each table that aredesignated as primary keys. There is always one primary key representing themonitored resource, and data is minimally summarized based on this value. For allagents, this primary key is represented internally by the column name,ORIGINNODE; however, the external attribute name varies with each monitoringagent.

One or more additional primary keys are provided for each attribute group tofurther refine the level of summarization for that attribute group. For example, inan OS agent disk attribute group, a primary key might be specified for the logicaldisk name that allows historical information to be reported for each logical disk ina computer.

Tables in the warehouseFor a monitoring agent, there are two main types of warehouse tables:v Raw tables:

These tables contain the raw information reported by a monitoring agent andwritten to the warehouse by the Warehouse Proxy agent. Raw tables are namedfor the attribute group that they represent, for example,N_F_S_and_R_P_C_Statistics.

v Summary tables:These tables contain summarized information based on the raw tables andwritten to the warehouse by the Summarization and Pruning agent.Summarization provides aggregation results over various reporting intervals, forexample, hours, days, and so on. Summary table names are based on the rawtable name with an appended suffix, for example,N_F_S_and_R_P_C_Statistics_H, N_F_S_and_R_P_C_Statistics_D, and so on.

Effects on summarized attributesWhen tables are summarized in the warehouse, the summary tables and summaryviews are created to include additional columns to report summarizationinformation. Table 3 on page 126 contains a list of the time periods and the suffixesfor the summary tables and views.


Table 3. Time periods and suffixes for summary tables and views

Data collection time period Summary table suffixes Summary view suffixes

Hourly _H _HV

Daily _D _DV

Weekly _W _WV

Monthly _M _MV

Quarterly _Q _QV

Yearly _Y _YV

Table 4 shows the expansion to summary columns of some of the most commonlyused attribute types.

Table 4. Additional columns to report summarization information

Attribute name Aggregation type Additional summarizationcolumns

MyGauge GAUGE MIN_MyGaugeMAX_MyGaugeSUM_MyGaugeAVG_MyGauge

MyCounter COUNTER TOT_MyCounterHI_MyCounterLO_MyCounterLAT_MyCounter

MyProperty PROPERTY LAT_Property

These additional columns are provided only for attributes that are not primarykeys. In the cases when an existing attribute is changed to be a primary key, theSummarization and Pruning agent no longer creates summarization values for theattributes, but the previously created column names remain in the table with anyvalues already provided for those columns. These columns cannot be deleted fromthe warehouse database, but as new data is collected, these columns will notcontain values. Similarly, when the primary key for an existing attribute has itsdesignation removed, that attribute has new summarization columns automaticallyadded. As new data is collected, it is used to populate these new column values,but any existing summarization records do not have values for these new columns.

The overall effect of these primary key changes is that summarization informationis changing. If these changes result in the old summarization records no longermaking sense, you can delete them. As a part of warehouse upgrade, summaryviews are dropped. The views will be recreated by the Summarization and Pruningagent the next time it runs. Dropping and recreating the views ensure that theyreflect the current table structure.

Upgrading your warehouse with limited user permissionsThe IBM Tivoli Monitoring warehouse agents (Warehouse Proxy andSummarization and Pruning agents) can dynamically adjust warehouse tabledefinitions based on attribute group and attribute information being loaded intothe warehouse. These types of table changes must be done for this monitoringagent for one or both of the following conditions:


v The monitoring agent has added new attributes to an existing attribute groupand that attribute group is included in the warehouse.

v The monitoring agent has added a new attribute group and that attribute groupis included in the warehouse.

For the warehouse agents to automatically modify the warehouse table definitions,they must have permission to alter warehouse tables. You might not have grantedthese agents these permissions, choosing instead to manually define the raw tablesand summary tables needed for the monitoring agents. Or, you might have grantedthese permissions initially, and then revoked them after the tables were created.

You have two options to effect the required warehouse table changes during theupgrade process:v Grant the warehouse agents temporary permission to alter tables

If using this option, grant the permissions, start historical collection for all thedesired tables, allow the Warehouse Proxy agent to add the new data to the rawtables, and allow the Summarization and Pruning agent to summarize data forall affected tables. Then, remove the permission to alter tables

v Make the warehouse table updates manuallyIf using this option, you must determine the table structures for the raw andsummary tables. If you manually created the tables in the earlier warehousedefinition, you already have a methodology and tools to assist you in this effort.You can use a similar technique to update and add new tables for thiswarehouse migration.For a method of obtaining raw table schema, refer to the IBM Redbook,TivoliManagement Services Warehouse and Reporting, January 2007, SG24-7290. Thechapter that explains warehouse tuning includes a section on creating data tablesmanually.

Types of table changesThe following types of table changes affect warehouse summarization:

Case 1 - New attribute added to an attribute group and defined as a primarykey.Case 2 - Existing attribute defined as a primary key or had primary keydesignation removed.Case 3 - Moving some tables from 4K tablespaces to 8K tablespaces when usingDB2 as the warehouse database.

Case 1 and Case 2 are primary key changes. In both cases, new summarizationrecords will not match existing summarized data:v A new attribute was added to an attribute group and that attribute was defined

as a primary key:New summarization records will provide more accurate summarization orgreater granularity than previous records. Existing summarization records arestill available but contain less granular detail if default values are not assignedfor the new primary keys.

v An existing attribute was defined as a primary key or the primary keydesignation was removed:If a new key was added, then the new summarization records will provide moreaccurate summarization or greater granularity than previous records. If a keywas removed, then the new summarization records will provide less granularity

Appendix A. Upgrading for warehouse summarization 127

than previous records, but with the intent of providing more meaningfulsummarization. Existing summarization records are still available.

Case 3 requires that you move some tables from 4K tablespaces to 8K tablespaceswhen using DB2 as the warehouse database to avoid errors during summarizationand pruning processing.

Table summaryTable 5 provides information to help you determine the effects of primary key andwarehouse changes for this monitoring agent. The table shows each attributegroup, the current primary keys (in addition to ORIGINNODE) for the attributegroup, primary keys that were removed, and whether this table is being includedin warehouse reporting.

Table 5. Primary key and warehouse changes for the Monitoring Agent for UNIX OS

Attribute group Current primary keys Removed primary keys Warehoused

Disk_Performance Disk_Name_U Yes

Disk Name_U Yes

File_Information File_U Path_U No

Machine_Information Yes

N_F_S_and_R_P_C_Statistics NFS_Version Yes

Network Network_Interface_Name Yes

Process Process_ID Yes

SMP_CPU CPU_ID Yes

Solaris_Zones Path Zone_ID Name Yes

System SP2System Yes

UNIX_IP_Address IP_AddressNetwork_Interface_Name

Yes

UNIX_All_Users User_ID Name Yes

UNIX_File_Comparison No

UNIX_File_Pattern No

UNIX_Group Group_ID Group_Name Yes

UNIX_Memory Yes

UNIX_Ping Target_Host Yes

UNIX_Print_Queue Device_Name Print_Queue_Name Yes

User Login_Name_U Yes

Upgrading your warehouse for primary key and tablespace changesUpgrading your warehouse includes making the following types of changes:v Case 1 - New attribute is added and is designated as a primary key

– New attribute and a default value must be added to the raw table and thesummarization tables.If the attribute group name is not too large for the underlying database, thetable name corresponds to the attribute group name. If the attribute groupname is too long, a short name is used. The mapping of attribute groupnames to table names is stored in the WAREHOUSEID table.


– Case-1 scripts that perform the following actions are provided to assist in thischange:- Alter existing raw tables- Alter existing summary tables- Drop existing summary views

– These changes must be done before the monitoring agent is started andbegins exporting data to the Warehouse Proxy agent.

v Case-2 - Existing attributes are changed to either add or remove primary keydesignation.– Existing data is of limited value and should be deleted.– Case-2_Truncate scripts that perform the following actions are provided to

assist in this change:- Remove all records from existing summary tables, preserving existing table

definitions- Delete the raw data marker allowing raw data to be resummarized

– Case-2_Drop scripts that perform the following actions are provided to assistin this change:- Drop existing summary views- Drop existing summary tables- Delete the raw data marker allowing raw data to be resummarized

– These changes are optional, but result in more accurate summarizedinformation.

v Case 3 - Move tables from 4K tablespace to 8K tablespace for selected agents– Special processing for selected agents, to move tables from a 4K tablespace to

an 8K tablespace.– Individual scripts are provided for each summary table to be changed.

Affected attribute groups and supporting scriptsTable 6 shows the attribute groups and summary tables affected for this monitoringagent, the names of the SQL scripts provided to assist in the upgrade process, thetypes of warehouse databases for which the scripts must be run, and the types ofchanges (cases) to which the scripts apply.

Table 6. Scripts for affected attribute groups and summary tables for the Monitoring Agent for UNIX OS

Attribute group orsummary table

File DB2 Oracle MSSQLServer

Case 1 Case 2 Case 3

N_F_S_and_R_P_C_Statistics_D

kux_61migr_N_F_S_and_R_P_C_Statistics_D.sql

X X X

N_F_S_and_R_P_C_Statistics_H

kux_61migr_N_F_S_and_R_P_C_Statistics_H.sql

X X X

N_F_S_and_R_P_C_Statistics_M

kux_61migr_N_F_S_and_R_P_C_Statistics_M.sql

X X X

N_F_S_and_R_P_C_Statistics_Q

kux_61migr_N_F_S_and_R_P_C_Statistics_Q.sql

X X X

N_F_S_and_R_P_C_Statistics_W

kux_61migr_N_F_S_and_R_P_C_Statistics_W.sql

X X X

N_F_S_and_R_P_C_Statistics_Y

kux_61migr_N_F_S_and_R_P_C_Statistics_Y.sql

X X X


Table 6. Scripts for affected attribute groups and summary tables for the Monitoring Agent for UNIX OS (continued)

Attribute group orsummary table

File DB2 Oracle MSSQLServer

Case 1 Case 2 Case 3

N_F_S_and_R_P_C_Statistics

kux_61migr_UNIX_OS_Agent_Case-1.sql

X X X X

System_D kux_61migr_System_D.sql X X

System_H kux_61migr_System_H.sql X X

System_M kux_61migr_System_M.sql X X

System_Q kux_61migr_System_Q.sql X X

System_W kux_61migr_System_W.sql X X

System_Y kux_61migr_System_Y.sql X X

Note: The raw table System does not need to be modified even though the corresponding summary tables aremodified.

The following types of warehouse objects are affected by these scripts. Review thescripts before running them:v Case-1.sql

These scripts affect raw tables, summary tables, and summary views.v Case-2_Drop.sql

These scripts affect the summary tables, summary views, and the Summarizationand Pruning agent WAREHOUSEMARKER table.

v Case-2_Truncate.sqlThese scripts affect the summary tables and the Summarization and Pruningagent WAREHOUSEMARKER table.

ProceduresThe warehouse can be hosted on any of three databases: DB2, Oracle, or MicrosoftSQL Server. There are different sets of script files for each type of database. Thesescripts are provided as part of the monitoring agent Tivoli Enterprise Portal Serversupport file installation. After installing the Tivoli Enterprise Portal Server supportfiles for the monitoring agent, the files are located on the Tivoli Enterprise PortalServer computer in install_dir/CNPS/SQLLIB/WAREHOUSE. There is a subdirectoryfor each type of database: DB2 for DB2, Oracle for Oracle, and SQLServer forMicrosoft SQL Server.

The scripts provide commands for all affected tables and views. If you do not havesummarization enabled for some periods, for example, quarterly or yearly, you willnot have the corresponding summary tables (_Q, _Y) and summary views (_QV,_YV) in your warehouse database. If you run the scripts that are provided, thedatabase reports errors for these missing objects. The scripts continue to run theremaining commands. Similarly, if you rerun the scripts, all commands areattempted. If the objects do not exist, or the command cannot be run (especially forthe ALTER commands), the scripts continue processing the remaining commands.

DB2 warehouse database procedure1. Stop all running Warehouse Proxy agent instances and the Summarization and

Pruning agent.2. Back up your warehouse database.


3. Copy the scripts from the Tivoli Enterprise Portal Server in one of the followingdirectories to a temporary directory on the system where the warehousedatabase is located:v Windows:

install dir\CNPS\SQLLIB\WAREHOUSE\DB2

v UNIX and Linux®:install dir/arch/cq/sqllib/WAREHOUSE/DB2

4. On the system where the warehouse database is located, change to thedirectory where you placed the script files in Step 3. Then, connect to thewarehouse database through the DB2 command line with a user ID that has theauthorization to alter and load tables and drop views. Run commands based onthe following example to connect, set the schema, and save the script to anoutput file:db2 connect to WAREHOUS user ITMUSER using ITMPASSdb2 set current schema="ITMUSER"db2 -tv -z log/script.sql.log -f script.sql

These parameters are used in the example:v WAREHOUS is the database name.v ITMUSER is the user name used by the Warehouse Proxy agent.v ITMPASS is the password used by the Warehouse Proxy agent.v script.sql is the name of the script file. See Table 6 on page 129 for the script

file names.v script.sql.log is the name of the output file.

Notes: You might receive error messages such the following from DB2:v SQL0204N "schema name.table name" is an undefined name.

SQLSTATE=42704

This message indicates that the table named table name does not existand cannot be altered or dropped. This happens if you do not havewarehousing or summarization enabled for the given table. Forexample if you only have hourly and daily summarization enabled,you see this message for the weekly, monthly, quarterly, and yearlysummarization tables because these tables do not exist.

v SQL3304N The table does not exist.

This message indicates that the table does not exist and cannot beloaded. This happens if you do not have warehousing orsummarization enabled for the given table. For example if you onlyhave hourly and daily summarization enabled, you see this messagefor the weekly, monthly, quarterly, and yearly summarization tablesbecause these tables do not exist.

Oracle warehouse database procedure1. Stop all running Warehouse Proxy agent instances and the Summarization and

Pruning agent.2. Back up your warehouse database.3. Copy the scripts from The Tivoli Enterprise Portal Server in one of the

following directories to a temporary directory on the system where thewarehouse database is located:v Windows

install dir\CNPS\SQLLIB\WAREHOUSE\Oracle

v UNIX and Linux


install dir/arch/cq/sqllib/WAREHOUSE/Oracle

4. On the system where the warehouse database is located, change to thedirectory where you placed the script files in Step 3. Then, connect to thewarehouse database through the Oracle command line with the same user thatthe Warehouse Proxy agent uses to connect to the warehouse, and run thescript. To run the script, the user ID must have authorization to alter tables anddrop views, or to drop tables when using Case 2 Drop, or truncate tables whenusing Case 2 Truncate. The output is saved to a file named script name.log.Run the following command:sqlplus ITMUSER/ITMPASS@WAREHOUS @script.sql

These parameters are used in the example:v WAREHOUS is the connect identifier.v ITMUSER is the user name used by the Warehouse Proxy agent.v ITMPASS is the password used by the Warehouse Proxy agent.v script.sql is the name of this script file. See Table 6 on page 129 for the

script file names.

Note: You might receive error messages such as the following from Oracle:ORA-00942: table or view does not exist

This message indicates that the table does not exist and cannot bealtered, dropped, or truncated. This happens if you do not havewarehousing or summarization enabled for the given table. For exampleif you only have hourly and daily summarization enabled, you see thismessage for the weekly, monthly, quarterly, and yearly summarizationtables because these tables do not exist.

MS SQL warehouse database procedure1. Stop all running Warehouse Proxy agent instances and the Summarization and

Pruning agent.2. Back up your warehouse database.3. Copy the scripts from the Tivoli Enterprise Portal Server in the one of the

following directories to a temporary directory on the system where thewarehouse database is located:v Windows:

install dir\CNPS\SQLLIB\WAREHOUSE\SQLServer

v UNIX and Linux:install dir/arch/cq/sqllib/WAREHOUSE/SQLServer

4. On the system where the warehouse database is located, change to thedirectory where you placed the script files in Step 3. Then, connect to thewarehouse database through the SQL Server command line with the same userthat the Warehouse Proxy agent uses to connect to the warehouse, and run thescript. To run the script, the user ID must have authorization to alter tables anddrop views, or to drop tables when using Case 2 Drop, or truncate tables whenusing Case 2 Truncate. The output is saved to a file named script name.log.Run the following command:osql -I -S SQLHOST[\SQLINST] -U ITMUSER -P ITMPASS -d WAREHOUS

-m-1 -n -o log/script.sql.log -i script.sql

These parameters are used in the example:v WAREHOUS is the database name.v ITMUSER is the user name used by the Warehouse Proxy agent.


v ITMPASS is the password used by the Warehouse Proxy agent.v script.sql is the name of this script file.v SQLHOST is the SQL server name.v SQLINST is the optional SQL instance name.

Note: You might receive error messages from the SQL Server such as thefollowing: Msg 4902, Level 16, State 1, Server ENTERPRISE, Line 1Cannot find the object "table name" because it does not exist oryou do not have permissions.

This message indicates that the table named table name does not exist andcannot be dropped or truncated. This happens if you do not havewarehousing or summarization enabled for the given table. For exampleif you only have hourly and daily summarization enabled, you see thismessage for the weekly, monthly, quarterly, and yearly summarizationtables because these tables do not exist.



Appendix B. Attributes

This appendix contains additional information about the Monitoring Agent forUNIX OS attributes. An attribute is a characteristic of a managed object (node). Forexample, Disk Name is an attribute for a disk, which is a managed object.

OverviewAn attribute is a characteristic of a managed object (node). For example, DiskName is an attribute for a disk, which is a managed object.

You can use the Monitoring Agent for UNIX OS attributes to build situations thatmonitor the performance of your UNIX network managed resources. When thevalues of the selected attributes in a situation exceed their threshold settings, theMonitoring Agent for UNIX OS systems posts an alert, notifying you of a problem.

The Monitoring Agent for UNIX OS provides the following types of attributes:

single-instanceSingle-instance attributes are attributes that gather only one set of data. Forexample, the local time attributes are single-instance attributes becausethere is only one set of values for local time at any one time.

multiple-instancemultiple-instance attributes are attributes that can gather multiple sets ofdata. For example, the Avg_Queue attribute is a multiple-instance attributebecause it can return one set of data for each queue that exists on thesystem.

You cannot use attributes from more than one multiple-instance attributegroup in the same situation. Examples of multiple-instance attribute groupsare Disk_Performance, System, and User.

Tivoli Enterprise Portal reports and attributesThe Monitoring Agent for UNIX OS reports provide real-time information on manyof the attributes by using the reports. Each column in a report corresponds to anattribute. These reports are available to you at any time, independent of whetheryou are using the Monitoring Agent for UNIX OS to monitor situations.

Assignment of valuesNot all UNIX systems display all UNIX attributes. For example, AIX systems donot display the CPU ID on which the process is running. If your system does notdisplay a value for a certain attribute, you see Not_Available in fields relating tothat attribute. A value of -1, or Not_Available, means that this information is notcurrently being collected for the UNIX platform on which your system is running.For example, HP-UX and Solaris systems do not display Busy Percent information.

A value of -2, or Not_Collected, is an indication that an error occurred.

A value of either 2147483648, or Value_Exceeds_Maximum, and -2147483648, orValue_Exceeds_Minimum, indicates that the value is too large and the Tivoli


Enterprise Monitoring Server cannot handle the value without wrapping it. Thesevalues are then capped at either 2147483648 or -2147483648.

Cross referencing historical reports and attributesHistorical reports use a column header that identifies the attributes using anshorter character name. The historical column header is identified in capital letterssurrounded by brackets [ ] under the attribute name. The historical data tables areidentified in the same manner after the attribute group name.

Here is an example of an attribute:

Space_Used_PercentIs the attribute name

[PCTSPCUSED]Is the historical column header.

Here is an example of an attribute group:

File_Information Group [UNIXFILE]Is the name of the attribute group and the name of the historical table.


Appendix C. Situations

Table 7 provides the name, activated-at-startup setting, description, situation logic,and comparison value for each situation.

Table 7. UNIX situations

NameActivate atstartup Description, logic, and values

UNIX_Active_Virtual_Memory No Checks if Active Virtual Memory approaches TotalVirtual Memory

*IF *VALUE System.Active_Virtual_Memory *GE nnnn

UNIX_CMD_Disk_Inodes_Critical No Monitors the /tmp and /var free inodes for criticalspace.

*IF (*VALUE Disk.Mount_Point *EQ /tmp *OR*VALUE Disk.Mount_Point *EQ /var) *AND *SUMDisk.Inodes_Free *LT 20000

*ACTION echo UNIX_CMD_Disk_Inodes_Critical

&Disk.System_Name Low free inodes on /tmp and/var

UNIX_CMD_Disk_Inodes_Critical_2 No Monitors the /tmp and /var free inodes for criticalspace.

*IF (*VALUE Disk.Mount_Point *EQ /tmp *OR*VALUE Disk.Mount_Point *EQ /var) *AND *SUMDisk.Inodes_Free *LT 20000

*ACTION echo UNIX_CMD_Disk_Inodes_Critical

&Disk.System_Name Low free inodes on /tmp and/var

UNIX_CMD_Disk_Space_Warning No Any Filemount with space usage GT 90%

*IF *VALUE Disk.Space_Used_Percent *GE 90

*ACTION

echo UNIX_CMD_Disk_Space_Warning

&Disk.System_Name Filemount:

&Disk.Mount_Point

Space_Used: &Disk.Space_Used_Percent

UNIX_CMD_Process_Critical No Checks for existence of process

*IF *VALUE Process.Command *EQ FOO


Table 7. UNIX situations (continued)


UNIX_CMD_Runaway_Process Yes Report High CPU processes

*IF *VALUE Process.CPU_Utilization *GT 95

*AND *VALUE Process.User_ID *NE 0

*AND (*VALUE Process.Execution_State *EQ R

*OR *VALUE Process.Execution_State *EQ A)

*ACTION echo UNIX_CMD_Runaway_Process

&Process.System_Name

Processid: &Process.Process_ID

Command: &Process.Command

UNIX_CPU_Critical No Process CPU utilization greater than or equal to 85%

*IF *VALUE Process.CPU_Utilization *GE 85

*AND *VALUE Process.Command *NE kproc

*AND *Process.Command *NE swapper

UNIX_CPU_Warning Yes Process CPU greater than or equal to 70% and lessthan 85%

*IF *VALUE Process.CPU_Utilization *GE 70

*AND *VALUE Process.CPU_Utilization *LT 85

UNIX_CPU-Busy_Critical No Monitors if the CPU workload is high (> 90%).

*IF *VALUE SMP_CPU.CPU_Busy *GT 90

UNIX_CPU_Busy_Warning No Monitors if the CPU workload is greater than 70% andless than or equal to 90%

*IF *VALUE SMP_CPU.CPU_Busy

*GT 70 *AND *VALUE SMP_CPU.CPU_Busy *LE 90

UNIX_Disk_Availability No Determines under utilized HD space

*IF *SCAN Disk.Mount_Point *EQ /user

*AND *VALUE Disk.Space_Used_Percent *LT 25

UNIX_Filemount_Critical No Checks for existence of specific mount point on aspecific system

*IF *SCAN Disk.System_Name *EQ Redwood

*AND

*SCAN Disk.Mount_Point *EQ /usr

UNIX_HD_Config_Critical No Hard disk space OR Inodes free going critical

*IF *VALUE Disk.Inodes_Free *LT 100

*OR *VALUE Disk.Space_Used_Percent *GT 90




UNIX_HD_Config_Critical_2 No Hard disk space OR Inodes free going critical

*IF *VALUE Disk.Inodes_Free *LT 100

*OR *VALUE Disk.Space_Used_Percent *GT 90

UNIX_HD_Excessive_IO_Wait Yes Note typical I/O bound processor (NSF)

*IF *VALUE System.Wait_I/O *GT 20

UNIX_Network_Collsns_Critical No Large number of network interface collisions

*IF *VALUE Network.Collisions *GT 15

UNIX_Network_Collsns_Warning No Small number of network interface collisions

*IF *VALUE Network.Collisions *GT 2

UNIX_Network_Errors No Received or transmitted error limit exceeded

*IF *VALUE Network.Interface_Status *EQ UP

*AND (*VALUE Network.Output_Errors *GT 10

*OR *VALUE Network.Input_Errors *GT 10)

UNIX_Network_Interface_Busy No Packets transmitted or received has exceeded the limit

*IF *VALUE Network.Network_Interface_Name *NELo0

*AND *VALUE Network.Interface_Status *EQ UP

*AND (*VALUE Network.Frames_Received *GT 1000

*OR *VALUE Network.Frames_Transmitted *GT 1000)Note: Frames_Received and Frames_Transmitted referto packets.

UNIX_Network_Interface_Idle No Packets transmitted or received less than limit

*IF *VALUE Network.Network_Interface_Name *NELo0

*AND *VALUE Network.Interface_Status *EQ UP

*AND (*VALUE Network.Frames_Received *LT 100*OR *VALUE Network.Frames_Transmitted *LT 100)Note: Frames_Received and Frames_Transmitted referto packets.

UNIX_NFS_RPC_Rejects No Checks for rejected NFS/RPC calls.

*IF *VALUEN_F_S_and_R_P_C_Statistics.NFS_Server_Calls_Rejected *GT 2 *OR *VALUEN_F_S_and_R_P_C_Statistics.NFS_Client_Calls_Rejected *GT 2

UNIX_Process_Memory_Critical No Reports high memory usage processes.

*IF *VALUE Process.Mem_Pct *GT 8000

UNIX_Process Memory_Warning No Reports high memory usage processes.

*IF *VALUE Process.Mem_Pct *GT 5000 *AND *VALUEProcess.Mem_Pct *LT 8000

Appendix C. Situations 139



UNIX_Process_Memory_Leak No Report high virtual memory usage processes

*IF *VALUE Process.Virtual_Size *GT 9999999

UNIX_Process_MISSING_inetd No Test if the Internet Services Daemon, inetd, is uprunning

*IF *MISSING Process.Command *EQ ('*inetd*')

UNIX_scratch_tmp_Disk_Full No Report filemount scratch or tmp with space usage GT90%

*IF *VALUE Disk.Space_Used_Percent *GT 90 *AND(*SCAN Disk.Mount_Point *EQ /scratch *OR *SCANDisk.Mount_Point *EQ /tmp)

UNIX_System_Busy_Critical No Check for critical state of I/O Wait, Low Free Mem,CPU Idle

*IF *VALUE System.Wait_I/O *GT 25

*AND *VALUE System.Free_Memory *LT 1

*AND *VALUE System.Idle_CPU *GT 10

*AND *VALUE System.Load_Average_1_Min *GT 2

UNIX_System_Busy_Warning Yes Checks for System CPU, Idle, I/O Wait, and Load Avg.for Busy State.

*IF *VALUE System.System_CPU *GT 50

*AND *VALUE System.Idle_CPU *GT 0

*AND *VALUE System.Wait_I/O *GT 0

*AND *VALUE System.Load_Average_5_Min *GT 1

UNIX_System_Capacity_Critical No Monitors system capacity w/process number and CPUUtil

*IF *VALUE System_Proc_Number *GE 250 *AND*VALUE System.System_CPU *GT 80

UNIX_System_Paging_Critical No Monitors if the VMM is working too hard to find freepages.

*IF *VALUE System.Page_Scan_Rate *GT 500

UNIX_System_Virtual_Memory_Warning No Monitors if the available virtual memory is runninglow.

*IF *VALUE System.Virtual_Memory_Percent_Used*GT 90

UNIX_User_CPU_Critical No Monitors if user CPU usage is system dominant andimpacts users

*IF *VALUE System.User_CPU *GE 0

*AND *VALUE System.User_CPU *LT 70

*AND *VALUE System.System_CPU *GT 40




UNIX_User_File_Exists No Notes that a specific user file was found

*IF *VALUE File_Information.Path *EQ/a/path2/search

*AND

*VALUE File_Information.File *EQ the File_2find

Appendix C. Situations 141


Appendix D. IBM Tivoli Enterprise Console event mapping

Specific event mapping is provided for those monitoring agents that supportDistributed Monitoring migration. The specific event mapping creates DistributedMonitoring events for Distributed Monitoring migrated situations. For a list ofthese situations and their related event classes, see Table 8.

Generic event mapping provides useful event class and attribute information forsituations that do not have specific event mapping defined. Each event classcorresponds to an attribute group in the monitoring agent. For a description of theevent slots for each event class, see Table 9 on page 146. For more informationabout mapping attribute groups to event classes, see the IBM Tivoli MonitoringAdministrator's Guide.

BAROC files are found on the Tivoli Enterprise Monitoring Server in theinstallation directory in TECLIB (that is, install_dir/cms/TECLIB for Windowssystems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). Forinformation on the current version of the BAROC file, see the IBM Tivoli MonitoringInstallation and Setup Guide. IBM Tivoli Enterprise Console event synchronizationprovides a collection of ready-to-use rule sets that you can deploy with minimalconfiguration. Be sure to install IBM Tivoli Enterprise Console eventsynchronization to access the correct Sentry.baroc, which is automatically includedduring base configuration of IBM Tivoli Enterprise Console rules if you indicatethat you want to use an existing rulebase. See the IBM Tivoli Monitoring Installationand Setup Guide for details.

Table 8. Overview of Distributed Monitoring migrated situations

Situation IBM Tivoli Enterprise Console event class

UX_USInodes* Sentry2_0_inodesSentry2_0_inodesused

UX_USIUsPct* Sentry2_0_inodesusedpct

UX_USDkUPct* Sentry2_0_diskusedpct

UX_USDskAva* Sentry2_0_diskavail

UX_USDskUsd* Sentry2_0_diskused

UX_USDIORtK* Sentry2_0_diskioratek

UX_USPDskRt* Sentry2_0_peakdiskrate

UX_USPkDkXf* Sentry2_0_peakdiskxfer

UX_USSpcUtl* Sentry2_0_spaceutil

UX_USSpcUtK* Sentry2_0_spaceutilkb

UX_USReqWt* Sentry2_0_reqwait

UX_USReqTm* Sentry2_0_reqtime

UX_USRPCTmO* Sentry2_0_rpctmout

UX_USBadNFS* Sentry2_0_badnfs

UX_USBadRPC* Sentry2_0_badrpc

UX_USNtInEr* Sentry2_0_netinerr

UX_USNtInEX* Sentry2_0_netinerrx

UX_USNetIn* Sentry2_0_netinerr


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


UX_USNetInX* Sentry2_0_netinx

UX_USNetCol* Sentry2_0_netcoll

UX_USNetCoX* Sentry2_0_netcollx

UX_USNtCPct* Sentry2_0_netcollpct

UX_USNCPctX* Sentry2_0_netcollpctx

UX_USNetOEr* Sentry2_0_netouterr

UX_USNetOEX* Sentry2_0_netouterrx

UX_USNetOut* Sentry2_0_netouterr

UX_USNetOX* Sentry2_0_netoutx

UX_USNtCIRt* Sentry2_0_netcollirate

UX_USNtIERt* Sentry2_0_netinerrate

UX_USNtOERt* Sentry2_0_netouterrate

UX_USNetIRt* Sentry2_0_netinrate

UX_USNetORt* Sentry2_0_netoutrate

UX_USSwpAva* Sentry2_0_swapavail

UX_USTProcs* Sentry2_0_totalprocs

UX_USCPUIdl* Sentry2_0_cpuidle

UX_USCPUSys* Sentry2_0_cpusys

UX_USCPUUsr* Sentry2_0_cpuusr

UX_USCPUSpu* Sentry2_0_cpuspu

UX_USZombie* Sentry2_0_zombies

UX_USLdAv15* Sentry2_0_loadavgfifteenm

UX_USLdAv5* Sentry2_0_loadavgonem

UX_USLdAv1* Sentry2_0_loadavgonem

UX_USPgScnR* Sentry2_0_pagescanrate

UX_USPgIns* Sentry2_0_pageins

UX_USPgOuts* Sentry2_0_pageouts

UX_USPgScan* Sentry2_0_pagescans

UX_USPgInRt* Sentry2_0_pageinrate

UX_USPgORt* Sentry2_0_pageoutrate

UX_USPgScRt* Sentry2_0_pagescanrate

UX_USRnQJbs* Sentry2_0_runqjobs

UX_USACPUBu* Sentry2_0_avgcpubusy

UX_USACPUSy* Sentry2_0_avgcpusys

UX_USACPUUs* Sentry2_0_avgcpuusr

UX_USFilPrm* Sentry2_0_fileperm

UX_USULginT* Sentry2_0_ulogintot

UX_UDskAva* universal_diskavail

UX_UDskUsd* universal_diskused

UX_UDskUPct* universal_diskusedpct


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


UX_UIndsFre* universal_diskusedpct

UX_UINdsUsd* universal_diskusedpct

UX_ULoadAvg* universal_loadavg

UX_UPageOut* universal_pageouts

UX_USwapAva* universal_swapavail

To determine what event class is sent when a given situation is triggered, look atthe first referenced attribute group in the situation predicate. The event class that isassociated with that attribute group is the one that is sent. This is true for bothpre-packaged situations and user-defined situations. See the table below forattribute group to event classes and slots mapping information.

For example, if the situation is monitoring the User Sessions attribute from theUNIX All Users Group attribute group, the event class that is sent once thesituation is triggered is ITM_Unix_All_Users.

Note: There are cases where these mappings generate events that are too large forthe Tivoli Enterprise Console. In these cases, the event class names and theevent slot names are the same, but some of the event slots are omitted.

Each of the event classes is a child of KUX_Base. The KUX_Base event class can beused for generic rules processing for any event from the Monitoring Agent forUNIX OS.

Appendix D. IBM Tivoli Enterprise Console event mapping 145

Table 9. Overview of attribute groups to event classes and slots

Attribute group event classes and slots

System ITM_System event class with these slots:

v system_name: STRING

v timestamp: STRING

v type: STRING

v version: STRING

v total_real_memory: INTEGER

v total_real_memory_enum: STRING

v total_virtual_memory: INTEGER

v total_virtual_memory_enum: STRING

v up_time: INTEGER

v up_time_enum: STRING

v users_session_number: INTEGER

v system_procs_number: INTEGER

v net_address: STRING

v net_address_enum: STRING

v user_cpu: INTEGER

v user_cpu_enum: STRING

v users_session_number_enum: STRING

v system_cpu: INTEGER

v system_cpu_enum: STRING

v system_procs_number_enum: STRING

v idle_cpu: INTEGER

v idle_cpu_enum: STRING

v wait_io: INTEGER

v wait_io_enum: STRING

v processes_in_run_queue: INTEGER

v processes_in_run_queue_enum: STRING

v processes_waiting: INTEGER

v processes_waiting_enum: STRING

v page_faults: INTEGER

v page_faults_enum: STRING

v page_reclaims: INTEGER

v page_reclaims_enum: STRING

v pages_paged_in: INTEGER

v pages_paged_in_enum: STRING

v pages_paged_out: INTEGER

v pages_paged_out_enum: STRING

v page_ins: INTEGER

v page_ins_enum: STRING

v page_outs: INTEGER

v page_outs_enum: STRING

v free_memory: INTEGER

v free_memory_enum: STRING


Table 9. Overview of attribute groups to event classes and slots (continued)


System (Cont.) v active_virtual_memory: INTEGER

v active_virtual_memory_enum: STRING

v cpu_context_switches: INTEGER

v cpu_context_switches_enum: STRING

v system_calls: INTEGER

v system_calls_enum: STRING

v forks_executed: INTEGER

v forks_executed_enum: STRING

v execs_executed: INTEGER

v execs_executed_enum: STRING

v block_reads: INTEGER

v block_reads_enum: STRING

v block_writes: INTEGER

v block_writes_enum: STRING

v logical_block_reads: INTEGER

v logical_block_reads_enum: STRING

v logical_block_writes: INTEGER

v logical_block_writes_enum: STRING

v nonblock_reads: INTEGER

v nonblock_reads_enum: STRING

v nonblock_writes: INTEGER

v nonblock_writes_enum: STRING

v receive_interrupts: INTEGER

v receive_interrupts_enum: STRING

v transmit_interrupts: INTEGER

v transmit_interrupts_enum: STRING

v modem_interrupts: INTEGER

v modem_interrupts_enum: STRING

v active_internet_connections: INTEGER

v active_internet_connections_enum:STRING

v active_sockets: INTEGER

v active_sockets_enum: STRING

v load_average_1_min: REAL

v load_average_1_min_enum: STRING





v dummy-memory_free: INTEGER

v dummy-memory_free_enum: STRING

v memory_used: INTEGER

v memory_used_enum: STRING

v page_scan_rate: INTEGER

v page_scan_rate_enum: STRING




System (Cont.) v virtual_memory_percent_used: REAL

v virtual_memory_percent_used_enum:STRING

v virtual_memory_percent_available: REAL

v virtual_memory_percent_available_enum:STRING

v cpu_busy: INTEGER

v cpu_busy_enum: STRING

v system_read: INTEGER

v system_read_enum: STRING

v system_write: INTEGER

v system_write_enum: STRING

v system_threads: INTEGER

v system_threads_enum: STRING

v processes_runnable: INTEGER

v processes_runnable_enum: STRING

v processes_running: INTEGER

v processes_running_enum: STRING

v processes_sleeping: INTEGER

v processes_sleeping_enum: STRING

v processes_idle: INTEGER

v processes_idle_enum: STRING

v processes_zombie: INTEGER

v processes_zombie_enum: STRING

v processes_stopped: INTEGER

v processes_stopped_enum: STRING

v threads_in_run_queue: INTEGER

v threads_in_run_queue_enum: STRING

v threads_waiting: INTEGER

v threads_waiting_enum: STRING

v boot_time: STRING

v pending_io_waits: INTEGER

v pending_io_waits_enum: STRING

v start_io: INTEGER

v start_io_enum: STRING

v device_interrupts: INTEGER

v device_interrupts_enum: STRING

v uptime: STRING

v parameter: STRING

v omunx_value: STRING

v swap_space_free: INTEGER

v swap_space_free_enum: STRING

v page_ins_rate: INTEGER

v page_ins_rate_enum: STRING




System (Cont.) v page_out_rate: INTEGER

v page_out_rate_enum: STRING

v page_scanning: INTEGER

v page_scanning_enum: STRING

v avg_pageins_1: INTEGER

v avg_pageins_1_enum: STRING







v avg_pageout_1: INTEGER

v avg_pageout_1_enum: STRING







v avg_pagescan_1: INTEGER

v avg_pagescan_1_enum: STRING







v avg_proccesses_runqueue_60: INTEGER

v avg_proccesses_runqueue_60_enum:STRING

v ipv6_address: STRING

v ipv6_address_enum: STRING

v zone_id: INTEGER

v zone_id_enum: STRING

v zone_name: STRING

v zone_name_enum: STRING




Disk ITM_Disk event class with these slots:


v timestamp: STRING

v name: STRING

v mount_point: STRING

v size: INTEGER

v size_enum: STRING

v space_used: INTEGER

v space_used_enum: STRING

v space_available: INTEGER

v space_available_enum: STRING

v inode_size: INTEGER

v inode_size_enum: STRING

v inodes_used: INTEGER

v inodes_used_enum: STRING

v inodes_free: INTEGER

v inodes_free_enum: STRING

v space_used_percent: INTEGER

v space_used_percent_enum: STRING

v inodes_used_percent: INTEGER

v inodes_used_percent_enum: STRING

v fs_type: STRING

v space_available_percent: INTEGER

v space_available_percent_enum: STRING

v name_u: STRING

v mount_point_u: STRING

v size_mb: INTEGER

v size_mb_enum: STRING

v size_gb: INTEGER

v size_gb_enum: STRING

v space_used_mb: INTEGER

v space_used_mb_enum: STRING

v space_used_gb: INTEGER

v space_used_gb_enum: STRING

v space_available_mb: INTEGER

v space_available_mb_enum: STRING

v space_available_gb: INTEGER

v space_available_gb_enum: STRING

v inodes_available_percent: INTEGER

v inodes_available_percent_enum: STRING




Disk (Continued) v size_64: REAL

v size_64_enum: STRING

v space_used_64: REAL

v space_used_64_enum: STRING

v space_available_64: REAL

v space_available_64_enum: STRING

v inode_size_64: REAL

v inode_size_64_enum: STRING

v inodes_used_64: REAL

v inodes_used_64_enum: STRING

v inodes_free_64: REAL

v inodes_free_64_enum: STRING

v size_mb_decimal: REAL

v size_mb_decimal_enum: STRING

v size_gb_decimal: REAL

v size_gb_decimal_enum: STRING

v space_used_mb_decimal: REAL

v space_used_mb_decimal_enum: STRING

v space_used_gb_decimal: REAL

v space_used_gb_decimal_enum: STRING

v space_available_mb_decimal: REAL

v space_available_mb_decimal_enum:STRING

v space_available_gb_decimal: REAL

v space_available_gb_decimal_enum:STRING




Disk_Performance ITM_Disk_Performance event class withthese slots:


v timestamp: STRING

v disk_name: STRING

v transfer_rate: INTEGER

v transfer_rate_enum: STRING

v transferred_bytes: INTEGER

v transferred_bytes_enum: STRING

v busy_percent: INTEGER

v busy_percent_enum: STRING

v avg_queue: INTEGER

v avg_queue_enum: STRING

v avg_wait: INTEGER

v avg_wait_enum: STRING

v avg_serv: INTEGER

v avg_serv_enum: STRING

v disk_name_u: STRING

v percent_disk_read_time: INTEGER

v percent_disk_read_time_enum: STRING

v percent_disk_write_time: INTEGER

v percent_disk_write_time_enum: STRING

v disk_reads_sec: INTEGER

v disk_reads_sec_enum: STRING

v disk_writes_sec: INTEGER

v disk_writes_sec_enum: STRING

v disk_read_bytes_sec: INTEGER

v disk_read_bytes_sec_enum: STRING

v disk_write_bytes_sec: INTEGER

v disk_write_bytes_sec_enum: STRING

v avg_disk_bytes_xfer: INTEGER

v avg_disk_bytes_xfer_enum: STRING




Network ITM_Network event class with these slots:


v timestamp: STRING

v network_interface_name: STRING

v network_interface_name_enum: STRING

v interface_ip_address: STRING

v interface_dns_name: STRING

v interface_dns_name_enum: STRING

v interface_status: STRING

v interface_status_enum: STRING

v transmission_unit_maximum: INTEGER

v transmission_unit_maximum_enum:STRING

v received_count: INTEGER

v received_count_enum: STRING

v transmitted_count: INTEGER

v transmitted_count_enum: STRING

v frames_received: INTEGER

v frames_received_enum: STRING

v frames_transmitted: INTEGER

v frames_transmitted_enum: STRING

v input_errors: INTEGER

v input_errors_enum: STRING

v output_errors: INTEGER

v output_errors_enum: STRING

v collisions: INTEGER

v collisions_enum: STRING

v subunit_driver: INTEGER

v subunit_driver_enum: STRING

v avg_coll_rate_1: INTEGER

v avg_coll_rate_1_enum: STRING







v avg_in_rate_1: INTEGER

v avg_in_rate_1_enum: STRING










Network (continued) v avg_inerr_rate_1: INTEGER

v avg_inerr_rate_1_enum: STRING

v avg_inerr_rate_5: INTEGER






v avg_out_rate_1: INTEGER

v avg_out_rate_1_enum: STRING







v avg_outerr_rate_1: INTEGER

v avg_outerr_rate_1_enum: STRING







v received_mb: REAL

v received_mb_enum: STRING

v transmitted_mb: REAL

v transmitted_mb_enum: STRING

v received_mb_total: REAL

v received_mb_total_enum: STRING

v transmitted_mb_total: REAL

v transmitted_mb_total_enum: STRING

v ipv4_dns_name: STRING

v ipv4_dns_name_enum: STRING

v type: INTEGER

v type_enum: STRING

v input_packet_errors_percent: INTEGER

v input_packet_errors_percent_enum:STRING

v output_packet_errors_percent: INTEGER

v output_packet_errors_percent_enum:STRING

v packet_collisions_percent: INTEGER

v packet_collisions_percent_enum: STRING




Network (continued) v mac_address: STRING

v mac_address_enum: STRING

v received_count_64: REAL

v received_count_64_enum: STRING

v transmitted_count_64: REAL

v transmitted_count_64_enum: STRING

User ITM_User event class with these slots:


v timestamp: STRING

v login_name: STRING

v name: STRING

v terminal: STRING

v idle_time: INTEGER

v idle_time_enum: STRING

v login_time: STRING

v location: STRING

v user_id: INTEGER

v user_id_enum: STRING

v process_id: INTEGER

v login_name_u: STRING

v name_u: STRING




Process ITM_Process event class with these slots:


v timestamp: STRING

v process_id: INTEGER

v process_id_enum: STRING

v flag: STRING

v execution_state: STRING

v execution_state_enum: STRING

v user_id: INTEGER


v parent_process_id: INTEGER

v parent_process_id_enum: STRING

v cpu_utilization: INTEGER

v cpu_utilization_enum: STRING

v priority: INTEGER

v priority_enum: STRING

v nice_value: INTEGER

v nice_value_enum: STRING

v entry_address: STRING

v size: INTEGER

v size_enum: STRING

v event_waited_on: STRING

v terminal_device: STRING

v time: STRING

v command: STRING

v process_command: STRING

v reptype: STRING

v real_group_id: INTEGER

v real_group_id_enum: STRING

v effective_user_id: INTEGER

v effective_user_id_enum: STRING

v effective_group_id: INTEGER

v effective_group_id_enum: STRING

v process_group_leader_id: INTEGER

v process_group_leader_id_enum: STRING

v session_id: INTEGER

v session_id_enum: STRING

v scheduling_class: STRING

v cpu_id: INTEGER

v cpu_id_enum: STRING

v user_name: STRING

v starttime: STRING

v elapsed_time: STRING

v virtual_size: INTEGER

v virtual_size_enum: STRING




Process (continued) v mem_pct: REAL

v mem_pct_enum: STRING

v cpu_pct: REAL

v cpu_pct_enum: STRING

v total_cpu_percent: REAL

v total_cpu_percent_enum: STRING

v sample_cpu_pct: REAL

v sample_cpu_pct_enum: STRING

v heap_size: INTEGER

v heap_size_enum: STRING

v stack_size: INTEGER

v stack_size_enum: STRING

v major_fault: INTEGER

v major_fault_enum: STRING

v minor_fault: INTEGER

v minor_fault_enum: STRING

v context_switch: INTEGER

v context_switch_enum: STRING

v involuntary_context_switch: INTEGER

v involuntary_context_switch_enum:STRING

v user_cpu_time: STRING

v system_cpu_time: STRING

v total_cpu_time: STRING

v thread_count: INTEGER

v thread_count_enum: STRING




Process (Cont.) v child_user_cpu_time: STRING

v child_user_cpu_time_enum: STRING

v child_system_cpu_time: STRING

v child_system_cpu_time_enum: STRING

v total_child_cpu_time: STRING

v total_child_cpu_time_enum: STRING

v wait_cpu_time: STRING

v wait_cpu_time_enum: STRING

v wait_lock_time: STRING

v wait_lock_time_enum: STRING

v read_per_write: INTEGER

v read_per_write_enum: STRING

v cpu_time: INTEGER

v cpu_time_enum: STRING

v parameter: STRING


v command_u: STRING

v process_command_u: STRING

v user_name_u: STRING

v group_name: STRING

v effective_user_name: STRING

v effective_group_name: STRING

v base_command: STRING

v type: STRING

v zone_id: INTEGER


v zone_name: STRING

v zone_name_enum: STRING

v process_count: INTEGER

v process_count_enum: STRING

v major_fault_64: REAL

v major_fault_64_enum: STRING

v minor_fault_64: REAL

v minor_fault_64_enum: STRING

v context_switch_64: REAL

v context_switch_64_enum: STRING

v involuntary_context_switch_64: REAL

v involuntary_context_switch_64_enum:STRING

v read_per_write_64: REAL

v read_per_write_64_enum: STRING




File_Information ITM_File_Information event class with theseslots:


v timestamp: STRING

v path: STRING

v file: STRING

v size: INTEGER

v size_enum: STRING

v owner: STRING

v group: STRING

v last_changed_time: STRING

v last_accessed_time: STRING

v links: INTEGER

v links_enum: STRING

v access: INTEGER

v access_enum: STRING

v type: STRING

v type_enum: STRING

v link_name: STRING

v path_u: STRING

v file_u: STRING

v owner_u: STRING

v group_u: STRING

v link_name_u: STRING

v size_mb: INTEGER

v size_mb_enum: STRING

v mode: STRING

v last_attr_chg_time: STRING

v checksum: STRING

v checksum_algorithm: INTEGER

v checksum_algorithm_enum: STRING

v file_content_changed: INTEGER

v file_content_changed_enum: STRING

v size_64: REAL

v size_64_enum: STRING

v size_mb_64: REAL

v size_mb_64_enum: STRING




N_F_S_and_R_P_C_Statistics ITM_N_F_S_and_R_P_C_Statistics eventclass with these slots:


v timestamp: STRING

v rpc_server_calls_rejected: INTEGER

v rpc_server_calls_rejected_enum: STRING

v rpc_server_times_rpc_packet_unavailable:INTEGER

v rpc_server_times_rpc_packet_unavailable_enum: STRING

v rpc_server_packets_too_short: INTEGER

v rpc_server_packets_too_short_enum:STRING

v rpc_server_packets_with_malformed_header: INTEGER

v rpc_server_packets_with_malformed_header_enum: STRING

v rpc_client_calls_rejected_by_server:INTEGER

v rpc_client_calls_rejected_by_server_enum:STRING

v rpc_client_calls_retransmitted: INTEGER

v rpc_client_calls_retransmitted_enum:STRING

v rpc_client_replies_not_matching_calls:INTEGER

v rpc_client_replies_not_matching_calls_enum: STRING

v rpc_client_calls_timed_out: INTEGER

v rpc_client_calls_timed_out_enum: STRING

v rpc_client_times_call_wait_on_busy:INTEGER

v rpc_client_times_call_wait_on_busy_enum:STRING

v rpc_client_times_authentication_refreshed:INTEGER

v rpc_client_times_authentication_refreshed_enum: STRING

v nfs_server_calls: INTEGER

v nfs_server_calls_enum: STRING

v nfs_server_calls_rejected: INTEGER

v nfs_server_calls_rejected_enum: STRING

v nfs_server_rejected_call_percentage:INTEGER

v nfs_server_rejected_call_percentage_enum:STRING




N_F_S_and_R_P_C_Statistics (Continued) v nfs_server_null_calls: INTEGER

v nfs_server_null_calls_enum: STRING

v nfs_server_get_attribute_calls: INTEGER

v nfs_server_get_attribute_calls_enum:STRING

v nfs_server_set_attribute_calls: INTEGER

v nfs_server_set_attribute_calls_enum:STRING

v nfs_server_root_calls: INTEGER

v nfs_server_root_calls_enum: STRING

v nfs_server_lookups: INTEGER

v nfs_server_lookups_enum: STRING

v nfs_server_read_link_calls: INTEGER

v nfs_server_read_link_calls_enum: STRING

v nfs_server_read_calls: INTEGER

v nfs_server_read_calls_enum: STRING

v nfs_server_write_cache_calls: INTEGER

v nfs_server_write_cache_calls_enum:STRING

v nfs_server_writes: INTEGER

v nfs_server_writes_enum: STRING

v nfs_server_file_creates: INTEGER

v nfs_server_file_creates_enum: STRING

v nfs_server_remove_file_calls: INTEGER

v nfs_server_remove_file_calls_enum:STRING

v nfs_server_rename_file_calls: INTEGER

v nfs_server_rename_file_calls_enum:STRING

v nfs_server_link_calls: INTEGER

v nfs_server_link_calls_enum: STRING

v nfs_server_symbolic_link_calls: INTEGER

v nfs_server_symbolic_link_calls_enum:STRING

v nfs_server_make_directory_calls:INTEGER

v nfs_server_make_directory_calls_enum:STRING

v nfs_server_remove_directory_calls:INTEGER

v nfs_server_remove_directory_calls_enum:STRING




N_F_S_and_R_P_C_Statistics (Continued) v nfs_server_read_directory_calls: INTEGER

v nfs_server_read_directory_calls_enum:STRING

v nfs_server_file_system_statistics_calls:INTEGER

v nfs_server_file_system_statistics_calls_enum: STRING

v nfs_client_calls: INTEGER

v nfs_client_calls_enum: STRING

v nfs_client_calls_rejected: INTEGER

v nfs_client_calls_rejected_enum: STRING

v nfs_client_rejected_call_percentage:INTEGER

v nfs_client_null_calls: INTEGER

v nfs_client_get_attribute_calls: INTEGER

v nfs_client_set_attribute_calls: INTEGER

v nfs_client_root_calls: INTEGER

v nfs_client_lookups: INTEGER

v nfs_client_read_link_calls: INTEGER

v nfs_client_read_calls: INTEGER

v nfs_client_write_cache_calls: INTEGER

v nfs_client_writes: INTEGER

v nfs_client_file_creates: INTEGER

v nfs_client_remove_file_calls: INTEGER

v nfs_client_rename_file_calls: INTEGER

v nfs_client_link_calls: INTEGER

v nfs_client_symbolic_link_calls: INTEGER

v nfs_client_make_directory_calls: INTEGER

v nfs_client_remove_directory_calls:INTEGER

v nfs_client_read_directory_calls: INTEGER

v nfs_client_file_system_statistics_calls:INTEGER

v parameter: STRING


v nfs_version: INTEGER

v nfs_version_enum: STRING

v rpc_server_calls: INTEGER

v rpc_server_calls_enum: STRING

v rpc_server_dup_checks: INTEGER

v rpc_server_dup_checks_enum: STRING

v rpc_server_dup_reqs: INTEGER

v rpc_server_dup_reqs_enum: STRING




N_F_S_and_R_P_C_Statistics (Continued) v rpc_client_calls: INTEGER

v rpc_client_calls_enum: STRING

v rpc_server_dup_reqs_percent: INTEGER

v rpc_server_dup_reqs_percent_enum:STRING

v rpc_server_calls_rejected_percent:INTEGER

v rpc_server_calls_rejected_percent_enum: STRING

v rpc_client_calls_retransmitted_percent:INTEGER

v rpc_client_calls_retransmitted_percent_enum: STRING

v rpc_client_calls_retransmitted_limit_percent: INTEGER

v rpc_client_calls_retransmitted_limit_percent_enum: STRING;

v rpc_client_calls_timed_out_percent:INTEGER

v rpc_client_calls_timed_out_percent_enum:STRING

v rpc_client_bad_xid_replies_percent:INTEGER

v rpc_client_bad_xid_replies_percent_enum:STRING;

v rpc_client_bad_xid_replies_limit_percent:INTEGER

v rpc_client_bad_xid_replies_limit_percent_enum: STRING

v

rpc_client_calls_rejected_by_server_percent:INTEGER

v rpc_client_calls_rejected_by_server_percent_enum: STRING

v nfs_server_get_attr_percent: INTEGER

v nfs_server_get_attr_percent_enum:STRING

v nfs_server_write_percent: INTEGER

v nfs_server_write_percent_enum: STRING

v nfs_server_read_percent: INTEGER

v nfs_server_read_percent_enum: STRING

v nfs_server_read_link_percent: INTEGER

v nfs_server_read_link_percent_enum:STRING




SMP_CPU ITM_SMP_CPU event class with these slots:


v timestamp: STRING

v cpu_id: INTEGER

v cpu_id_enum: STRING

v user_cpu: INTEGER

v user_cpu_enum: STRING

v system_cpu: INTEGER

v system_cpu_enum: STRING

v idle_cpu: INTEGER

v idle_cpu_enum: STRING

v wait_io: INTEGER

v wait_io_enum: STRING

v cpu_busy: INTEGER

v cpu_busy_enum: STRING

v minor_faults: INTEGER

v minor_faults_enum: STRING

v major_faults: INTEGER

v major_faults_enum: STRING

v cross_calls: INTEGER

v cross_calls_enum: STRING

v interrupts: INTEGER

v interrupts_enum: STRING

v interrupts_as_threads: INTEGER

v interrupts_as_threads_enum: STRING

v context_switches: INTEGER

v context_switches_enum: STRING

v involuntary_context_switches: INTEGER

v involuntary_context_switches_enum:STRING

v thread_migrations: INTEGER

v thread_migrations_enum: STRING

v spins_on_mutexes: INTEGER

v spins_on_mutexes_enum: STRING

v spins_on_rw_locks: INTEGER

v spins_on_rw_locks_enum: STRING

v system_calls: INTEGER

v system_calls_enum: STRING

v cpu_status: INTEGER

v cpu_status_enum: STRING

v parameter: STRING


v cpu_usage: INTEGER

v cpu_usage_enum: STRING




SMP_CPU (continued) v cpu_time: INTEGER

v cpu_time_enum: STRING

v avg_cpu_busy_1: INTEGER

v avg_cpu_busy_1_enum: STRING







v avg_cpu_sys_1: INTEGER

v avg_cpu_sys_1_enum: STRING







v avg_cpu_usr_1: INTEGER

v avg_cpu_usr_1_enum: STRING







Print_Queue ITM_Unix_Print_Queue event class withthese slots:


v timestamp: STRING

v print_queue_name: STRING

v device_name: STRING

v print_queue_status: STRING

v print_queue_depth: INTEGER

v print_queue_depth_enum: STRING

v print_queue_job_size: INTEGER

v print_queue_job_size_enum: STRING




Group ITM_Unix_Group event class with theseslots:


v timestamp: STRING

v group_name: STRING

v group_id: INTEGER

v group_id_enum: STRING

v group_duplicated: INTEGER

v group_duplicated_enum: STRING




Memory ITM_Unix_Memory event class with theseslots:


v timestamp: STRING

v total_virtual_storage_mb: INTEGER

v total_virtual_storage_mb_enum: STRING

v used_virtual_storage_mb: INTEGER

v used_virtual_storage_mb_enum: STRING

v avail_virtual_storage_mb: INTEGER

v avail_virtual_storage_mb_enum: STRING

v virtual_storage_pct_used: REAL

v virtual_storage_pct_used_enum: STRING

v virtual_storage_pct_avail: REAL

v virtual_storage_pct_avail_enum: STRING

v total_swap_space_mb: INTEGER

v total_swap_space_mb_enum: STRING

v used_swap_space_mb: INTEGER

v used_swap_space_mb_enum: STRING

v avail_swap_space_mb: INTEGER

v avail_swap_space_mb_enum: STRING

v used_swap_space_pct: REAL

v used_swap_space_pct_enum: STRING

v avail_swap_space_pct: REAL

v avail_swap_space_pct_enum: STRING

v total_real_mem_mb: INTEGER

v total_real_mem_mb_enum: STRING

v used_real_mem_mb: INTEGER

v used_real_mem_mb_enum: STRING

v avail_real_mem_mb: INTEGER

v avail_real_mem_mb_enum: STRING

v used_real_mem_pct: REAL

v used_real_mem_pct_enum: STRING

v avail_real_mem_pct: REAL

v avail_real_mem_pct_enum: STRING

v page_faults: INTEGER

v page_faults_enum: STRING

v page_reclaims: INTEGER

v page_reclaims_enum: STRING

v page_ins: INTEGER

v page_ins_enum: STRING

v page_outs: INTEGER

v page_outs_enum: STRING

v page_in_reqs: INTEGER

v page_in_reqs_enum: STRING




Memory (continued) v page_out_reqs: INTEGER

v page_out_reqs_enum: STRING

v page_in_kb_s: INTEGER

v page_in_kb_s_enum: STRING

v page_out_kb_s: INTEGER

v page_out_kb_s_enum: STRING

v page_in_1min: INTEGER

v page_in_1min_enum: STRING







v page_out_1min: INTEGER

v page_out_1min_enum: STRING







v page_scan: INTEGER

v page_scan_enum: STRING

v page_scan_kb: INTEGER

v page_scan_kb_enum: STRING

v page_scan_1min: INTEGER

v page_scan_1min_enum: STRING







File_Pattern ITM_Unix_File_Pattern event class withthese slots:


v timestamp: STRING

v file_name: STRING

v match_pattern: STRING

v match_option: INTEGER

v match_option_enum: STRING

v match_count: INTEGER

v match_count_enum: STRING




File_Comparison ITM_Unix_File_Comparison event class withthese slots:


v timestamp: STRING

v file_name_1: STRING

v file_name_2: STRING

v file_compare_option: INTEGER

v file_compare_option_enum: STRING

v file_compare_result: INTEGER

v file_compare_result_enum: STRING

Ping ITM_Unix_Ping event class with these slots:


v timestamp: STRING

v target_host: STRING

v ping_result: INTEGER

v ping_result_enum: STRING

v response_time: REAL

v response_time_enum: STRING

All_Users ITM_Unix_All_Users event class with theseslots:


v timestamp: STRING

v name: STRING

v user_id: INTEGER


v password_null: INTEGER

v password_null_enum: STRING

v user_duplicated: INTEGER

v user_duplicated_enum: STRING

v user_sessions: INTEGER

v user_sessions_enum: STRING




Solaris_Zones ITM_Solaris_Zones event class with theseslots:


v timestamp: STRING

v name: STRING

v name_enum: STRING

v zone_id: INTEGER


v omunx_status: INTEGER

v omunx_status_enum: STRING

v path: STRING

v pool_id: INTEGER

v pool_id_enum: STRING

v init_pid: INTEGER

v init_pid_enum: STRING

v zone_cpu_usage: REAL

v zone_cpu_usage_enum: STRING

v physical_memory: INTEGER

v physical_memory_enum: STRING

v virtual_memory: INTEGER

v virtual_memory_enum: STRING

v total_cpus: INTEGER

v total_cpus_enum: STRING

v scheduler: STRING

v scheduler_enum: STRING

v cpu_shares: INTEGER

v cpu_shares_enum: STRING

v cpu_share_pct: REAL

v cpu_share_pct_enum: STRING




Machine_Information ITM_Machine_Information event class withthese slots:


v timestamp: STRING

v omunx_hostname: STRING

v omunx_hostname_enum: STRING

v hardware_manufacturer: STRING

v hardware_manufacturer_enum: STRING

v hardware_model: STRING

v hardware_model_enum: STRING

v number_of_physical_processors: INTEGER

v number_of_physical_processors_enum:STRING

v processor_megahertz: INTEGER

v processor_megahertz_enum: STRING

v machine_serial: STRING

v machine_serial_enum: STRING

v system_board_uuid: STRING

v system_board_uuid_enum: STRING

v virtual_machine_identifier: STRING

v virtual_machine_identifier_enum: STRING

IP_Address ITM_IP_Address event class with these slots:


v timestamp: STRING

v network_interface_name: STRING

v ip_address: STRING

v dns_name: STRING

v dns_name_enum: STRING

v ip_version: INTEGER

v ip_version_enum: STRING



Appendix E. Historical data

Historical reports use a column header that uses a shorter character name thatidentifies the attributes. The tables in this appendix identify the historical table, theMonitoring Agent for UNIX OS attribute group associated with the table, thehistorical table column head (in capital letters), and the associated attribute name.Use the information in this appendix in conjunction with the information inAppendix B, “Attributes,” on page 135 to identify attribute definitions for thehistorical data tables.

UNIXCPU historical tableThe UNIXCPU historical table corresponds to the SMP CPU attributes.

Table 10 lists the historical table column heads alphabetically and thecorresponding SMP CPU attributes.

Table 10. UNIXCPU table column heads and the corresponding SMP CPU attributes

Historical table column head Attribute name

CPUBUSY CPU_Busy

CPUID CPU_ID

CPUSTAT CPU_Status

CSW Context_Switches

ICSW Involuntary_Context_Switches

IDLECPU Idle_CPU

INTRRUPT Interrupts

INTRTHRD Interrups_As_Threads

MAJF Major_Faults

MINF Minor_Faults

ORIGINNODE System_Name

SMTX Spins_On_Mutexes

SRWLOCKS Spins_On_RW_Locks

SYSCALL System_Calls

SYSCPU System_CPU

THRDMIGR Thread_Migrations

TIMESTAMP Timestamp

USRCPU User_CPU

WAITIO Wait_I/O

XCALLS Cross_Calls

ZATTRIB Parameter

Column seen in historical data collection tables butcurrently not collecting validated data.


Table 10. UNIXCPU table column heads and the corresponding SMP CPUattributes (continued)


ZVALUE Value


UNIXDISK historical tableThe UNIXDISK historical table corresponds to the Disk Information attributes.

Table 11 lists the historical table column heads alphabetically and thecorresponding Disk group attributes.

Table 11. UNIXDISK table column heads and the corresponding Disk Information attributes


DSKNAME Name

DSKSIZE Size

FSTYPE FS_Type


INODEFREE Inodes_Free

INODESIZE Inode_Size

INODEUSED Inodes_Used

MOUNTPT Mount_Point


PCTINDUSED Inodes_Used_Percent

PCTSPCAV Space_Available_Percent


PCTSPCUSED Space_Used_Percent

SPCAVAIL Space_Available

SPCUSED Space_Used

TIMESTAMP Timestamp

UNIXDPERF historical tableThe UNIXDPERF historical table corresponds to the Disk Performance attributes.

Table 12 lists the historical table column heads alphabetically and thecorresponding Disk Performance attributes.

Table 12. UNIXDPERF table column heads and the corresponding Disk Performanceattributes


AVGSERV Avg_Serv


Table 12. UNIXDPERF table column heads and the corresponding Disk Performanceattributes (continued)


DSKAVQUE Avg_Queue

DSKAVWAIT Avg_Wait

DSKBUSY Busy_Percent

DSKBYTESIZ Transferred_Bytes

DSKNAME Disk_Name

DSKXFERRAT Transfer_Rate


TIMESTAMP Timestamp

UNIXFILE historical tableThe UNIXFILE historical table corresponds to the File Information attributes.

Table 13 lists the historical table column heads alphabetically and thecorresponding File Information attributes.

Table 13. UNIXFILE table column heads and the corresponding File Information attributes


ACCESS Access

ACCESSEDTM Last_Accessed_Time

CHANGEDTM Last_Changed_Time

FILE File

GROUP Group

LINKNAME Link_Name

LINKS Links


OWNER Owner

PATH Path

SIZE Size

TIMESTAMP Timestamp

TYPE Type

UNIXNET historical tableThe UNIXNET historical table corresponds to the Network attributes.

Table 14 lists the historical table column heads alphabetically and thecorresponding Network attributes.

Table 14. UNIXNET table column heads and the corresponding Network attributes


FCOLLSNS Collisions

FDNSNAME Interface_DNS_Name

Appendix E. Historical data 175

Table 14. UNIXNET table column heads and the corresponding Networkattributes (continued)


FIBYTES Received_Count

FIERRORS Input_Errors

FIFRAMES Frames_Received

FIPADDR Interface_IP_Address

FMTU Transmission_Unit_Maximum

FNAME Network_Interface_Name

FOBYTES Transmitted_Count

FOERRORS Output_Errors

FOFRAMES Frames_Transmitted

FSTATUS Interface_Status

FUNIT Subunit_Driver


TIMESTAMP Timestamp

Note: Frames_Received and Frames_Transmitted refer to packets.

UNIXNFS historical tableThe UNIXNFS historical table corresponds to the NFS and RPC Statistics attributes.

Table 15 lists the historical table column heads alphabetically and thecorresponding NFS and RPC Statistics attributes.

Table 15. UNIXNSF table column heads and the corresponding NFS and RPC Statisticsattributes


ZTITLE Attribute_Title

Column seen in historical data collection tables but currentlynot collecting validated data.

ZVALUE Attribute_Value

Column seen in historical data collection tables but currentlynot collecting validated data.

NCCALLS NFS_Client_Calls

NCBAD NFS_Client_Calls_Rejected

NCCREATE NFS_Client_File_Creates

NCFSSTAT NFS_Client_File_System_Statistics_Calls

NCGETATT NFS_Client_Get_Attribute_Calls

NCLINK NFS_Client_Link_Calls

NCLOOKUP NFS_Client_Lookups

NCMKDIR NFS_Client_Make_Directory_Calls

NCNULL NFS_Client_Null_Calls

NCREAD NFS_Client_Read_Calls


Table 15. UNIXNSF table column heads and the corresponding NFS and RPC Statisticsattributes (continued)


NCRDDIR NFS_Client_Read_Directory_Calls

NCRDLINK NFS_Client_Read_Link_Calls

NCPERC NFS_Client_Rejected_Calls_Percentage

NCRMDIR NFS_Client_Remove_Directory_Calls

NCREMOVE NFS_Client_Remove_File_Calls

NCRENAME NFS_Client_Rename_File_Calls

NCROOT NFS_Client_root_Calls

NCSETATT NFS_Client_Set_Attribute_Calls

NCSYMLNK NFS_Client_Symbolic_Link_Calls

NCWRCACH NFS_Client_Write_Cache_Calls

NCWRITE NFS_Client_Writes

NSCALLS NFS_Server_Calls

NSBAD NFS_Server_Calls_Rejected

NSCREATE NFS_Server_File_Creates

NSFSSTAT NFS_Server_File_System_Statistics_Calls

NSGETATT NFS_Server_Get_Attribute_Calls

NSLINK NFS_Server_Link_Calls

NSLOOKUP NFS_Server_Lookups

NSMKDIR NFS_Server_Make_Directory_Calls

NSNULL NFS_Server_Null_Calls

NSREAD NFS_Server_Read_Calls

NSRDDIR NFS_Server_Read_Directory_Calls

NSRDLINK NFS_Server_Read_Link_Calls

NSPERC NFS_Server_Rejected_Calls_Percentage

NSRMDIR NFS_Server_Remove_Directory_Calls

NSREMOVE NFS_Server_Remove_File_Calls

NSRENAME NFS_Server_Rename_File_Calls

NSROOT NFS_Server_root_Calls

NSSETATT NFS_Server_Set_Attribute_Calls

NSSYMLNK NFS_Server_Symbolic_Link_Calls

NSWRCACH NFS_Server_Write_Cache_Calls

NSWRITE NFS_Server_Writes

RCBAD RPC_Client_Calls_Rejected_by_Server

RCRETRAN RPC_Client_Calls_Retransmitted

RCTIMOUT RPC_Client_Calls_Timed_Out

RCBADXID RPC_Client_Replies_Not_Matching_Calls

RCAREF RPC_Client_Times_Authentication_Refreshed

RCWAIT RPC_Client_Times_Call_Wait_On_Busy

RSBAD RPC_Server_Calls_Rejected


Table 15. UNIXNSF table column heads and the corresponding NFS and RPC Statisticsattributes (continued)


RSBADLEN RPC_Server_Packets_Too_Short

RSBADHDR RPC_Server_Packets_with_Malformed_Header

RSNULL RPC_Server_Times_RPC_Packet_Unavailable


TIMESTAMP Timestamp

UNIXPS historical tableThe UNIXPS historical table corresponds with the Process attributes.

Table 16 lists the historical table column heads alphabetically and thecorresponding Process attributes.

Table 16. UNIXPS table column heads and the corresponding Process attributes


ADDR Entry_Address

CHILDTIME Total_Child_CPU_Time

CHILDSTIME Child_System_CPU_Time

CHILDUTIME Child_User_CPU_Time

CMD Command

COMMAND Process_Command

CONTSWITCH Context_Switch

CPU CPU_Utilization

CPUID CPU_ID

CPUPERCENT CPU_Pct

CPUTIME CPU_Time


EGID Effective_Group_ID

ELAPTIME Elapsed_Time

EUID Effective_User_ID

EVENT Event_Waited_On

EXECSTATE Execution_State

FLAG Flag

GID Real_Group_ID

HEAP Heap_Size

INVCONTSWT Involuntary_Context_Switches

MAJORFAULT Major_Fault

MEMPERCENT Mem_Pct

MINORFAULT Minor_Fault

NICE Nice_Value


Table 16. UNIXPS table column heads and the corresponding Processattributes (continued)



PID Process_ID

PGID Process_Group_Leader_ID

PPID Parent_Process_ID

PRIORITY Priority

READWRITE Read/Write

REPTYPE Reptype

Column seen in historical data collection tables. IBMinternal use only.

SAMPCPUTCT Sample_CPU_Pct


SCHEDCLASS Scheduling_Class

SESSIONID Session_ID

SIZE Size

STACK Stack_Size

STARTTIME StartTime

SYSTEMTIM System_CPU_Time

THREADCNT Thread_Count

TIME Time

TIMESTAMP Timestamp

TOTCPUPERC Total_CPU_Percent

TOTALTIME Total_CPU_Time

TTY Terminal_Device

UID User_ID

USERNAME User_Name

USERTIME User_CPU_Time

VSIZE Virtual_Size

WAITCPUTIM Wait_CPU_Time

WAITLTIME Wait_Lock_Time

ZATTRIB Parameter


ZVALUE Value


UNIXOS historical tableThe UNIXOS historical table corresponds to the System attributes.


Table 17 lists the historical table column heads alphabetically and thecorresponding System attributes.

Table 17. UNIXOS table column heads and the corresponding System attributes


BOOTTIME Boot_Time

BREAD Block_Reads

BWRITE Block_Writes

CPUBUSY CPU_Busy

DEVINT Device_Interrupts

LREAD Logical_Block_Reads

LWRITE Logical_Block_Writes

MEMFREE DUMMY-Memory_Free


MEMUSED Memory_Used


MDMINT Modem_Interrupts


NETADDR Net_Address

NETCONNECT Active_Internet_Connections


NETLOAD1 Load_Average_1_Min



NETSOCKET Active_Sockets


NOSYSPROCS System_Procs_Number

NOUSRSESS Users_Session_Number

NSYSTHRD System_Threads



PENDIOWT Pending_IO_Waits


PHREAD NonBlock_Reads

PHWRITE NonBlock_Writes

PIDLE Processes_Idle


Table 17. UNIXOS table column heads and the corresponding System attributes (continued)


PRUNABLE Processes_Runnable

PRUNNING Processes_Running

PSLEEPING Processes_Sleeping

PSTOPPED Processes_Stopped

PSWITCH CPU_Context_Switches

PZOMBIE Processes_Zombie

RCVINT Receive_Interrupts


STARTIO Start_IO


SYSCALL System_Calls

SYSEXEC Execs_Executed

SYSFORK Forks_Executed

SYSREAD System_Read

SYSWRITE System_Write

SYSTEMTYPE Type

SYSUPTIME Up_Time

SYSTEMVERS Version

TIMESTAMP Timestamp

THRDRUNQ Threads_in_Run_Queue


THRDWAIT Threads_Waiting


TOTREALMEM Total_Real_Memory

TOTVIRTMEM Total_Virtual_Memory

UNIXIDLCPU Idle_CPU

UNIXSYSCPU System_CPU

UNIXUSRCPU User_CPU

UNIXWAITIO Wait_I/O

UPTIME UpTime

VMFREEMEM Free_Memory

VMFREEPRC Virtual_Memory_Percent_Available

VMFREESWAP Active_Virtual_Memory

VMINPGWAIT Processes_Waiting

VMINRUNQ Processes_in_Run_Queue

VMPGFAULTS Page_Faults


Table 17. UNIXOS table column heads and the corresponding System attributes (continued)


VMPGIN Pages_Paged_In

VMPGOUT Pages_Paged_Out

VMPGRCLM Page_Reclaims

VMPGSIN Page_Ins

VMPGSOUT Page_Outs

VMSCAN Page_Scan_Rate

VMUSEDPRC Virtual_Memory_Percent_Used

XMTINT Transmit_Interrupts


ZATTRIB Parameter


ZVALUE Value


UNIXUSER historical tableThe UNIXUSER historical table corresponds to the User group attributes.

Table 18 lists the historical table column heads alphabetically and thecorresponding User attributes.

Table 18. UNIXUSER table column heads and the corresponding User attributes



PID Process_ID


TIMESTAMP Timestamp

UID User_ID

USERIDLE Idle_Time

USERLOGIN Login_Name

USERNAME Name

USERSITE Location

USERTTY Terminal

USERWHEN Login_Time


Appendix F. Monitoring Agent for UNIX data collection

In general, the Monitoring Agent for UNIX gathers data when requested to satisfya workspace refresh, situation sampling of attributes, or historical data collection.All attributes in the attribute groups that make up a workspace or situation aregathered at that time. The default refresh/sampling intervals were chosen suchthat the agent will not put a significant load on the system as it gathers the data.

The following table shows each UNIX attribute group:

Table 19. Mechanisms used to gather attributes

Attribute group AttributeCollectionmethods AIX HPUX Solaris

UNIXOS /SP2OS

SYSTEMTYPE API uname() uname() uname()

SYSTEMVERS API uname() uname() uname()

TOTREALMEM API perfstat_memory_total

pstat_getdynamic

sysconf

TOTVIRTMEM API perfstat_memory_total

pstat_getdynamic+/usr/sbin/swapinfo

swapctl+sysconf

SYSUPTIME API time()-boottime() time()-boottime() time()-boottime()

NOUSRSESS API getutxent getutxent getutxent

NOSYSPROCS API getprocs64 pstat_getproc /proc/

NETADDR API gethostname()+getaddrinfo

gethostname()+getaddrinfo


UNIXUSRCPU API 5.2 perfstat_cpu 5.3/usr/bin/mpstat

get_sysinfo kstat

UNIXSYSCPU API 5.2 perfstat_cpu 5.3/usr/bin/mpstat

get_sysinfo kstat

UNIXIDLCPU API 5.2 perfstat_cpu 5.3/usr/bin/mpstat

get_sysinfo kstat

UNIXWAITIO API 5.2 perfstat_cpu 5.3/usr/bin/mpstat

get_sysinfo kstat

VMINRUNQ API perfstat_cpu_total

pstat_getdynamic

kstat

VMINPGWAIT API perfstat_cpu_total

pstat_getdynamic

kstat

VMPGFAULTS API perfstat_memory_total

pstat_getvminfo

kstat

VMPGRCLM API perfstat_memory_total

pstat_getvminfo

kstat


Table 19. Mechanisms used to gather attributes (continued)


VMPGIN API perfstat_memory_total

pstat_getvminfo

kstat

VMPGOUT API perfstat_memory_total

pstat_getvminfo

kstat

VMPGSIN API perfstat_memory_total

pstat_getvminfo

kstat

VMPGSOUT API perfstat_memory_total

pstat_getvminfo

kstat

VMFREEMEM API perfstat_memory_total

pstat_getdynamic

sysconf

VMFREESWAP API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

PSWITCH API perfstat_cpu_total

get_sysinfo kstat

SYSCALL API perfstat_cpu_total

get_sysinfo kstat

SYSFORK API perfstat_cpu_total

get_sysinfo kstat

SYSEXEC API perfstat_cpu_total

get_sysinfo kstat

BREAD API perfstat_cpu_total

get_sysinfo kstat

BWRITE API perfstat_cpu_total

get_sysinfo kstat

LREAD API perfstat_cpu_total

get_sysinfo kstat

LWRITE API perfstat_cpu_total

get_sysinfo kstat

PHREAD API perfstat_cpu_total

get_sysinfo kstat

PHWRITE API perfstat_cpu_total

get_sysinfo kstat

RCVINT API perfstat_cpu_total

get_sysinfo kstat

XMTINT API perfstat_cpu_total

get_sysinfo kstat

MDMINT API perfstat_cpu_total

get_sysinfo kstat

NETLOAD1 API perfstat_cpu_total

pstat_getdynamic

getloadavg





pstat_getdynamic

getloadavg


pstat_getdynamic

getloadavg

MEMFREE API perfstat_memory_total

pstat_getdynamic

sysconf

MEMUSED API perfstat_memory_total

pstat_getdynamic

swapctl

VMSCAN API perfstat_memory_total

pstat_getvminfo

kstat

VMUSEDPRC API perfstat_memory_total


sysconf+swapctl

VMFREEPRC API perfstat_memory_total


sysconf+swapctl

CPUBUSY API perfstat_cpu_total

get_sysinfo kstat

SYSREAD API perfstat_cpu_total

get_sysinfo kstat

SYSWRITE API perfstat_cpu_total

get_sysinfo kstat

PRUNABLE API getprocs64 get_sysinfo kstat

PRUNNING API N/A /proc ioctl() pstat_getproc

PSLEEPING API /proc ioctl() get_sysinfo pstat_getproc

PIDLE API /proc ioctl() get_sysinfo pstat_getproc

PZOMBIE API /proc ioctl() get_sysinfo pstat_getproc

PSTOPPED API /proc ioctl() get_sysinfo pstat_getproc

BOOTTIME API getutxid getutxid getutxid

DEVINT API perfstat_cpu_total

pstat_getvminfo

kstat

UPTIME API time()-boottime() time()-boottime() time()-boottime()

SWAPFREE API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

PGINRATE API perfstat_memory_total

pstat_getvminfo

kstat

PGOUTRATE API perfstat_memory_total

pstat_getvminfo

kstat

Appendix F. Monitoring Agent for UNIX data collection 185



PGSCANRATE API perfstat_memory_total

pstat_getvminfo

kstat

AVPGINS1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

AVPGOUT1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

AVPGSCAN1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

AVPRRUNQ60 API perfstat_memory_total

pstat_getvminfo

kstat

NETADDR6 API gethostname()+getaddrinfo



ZID API N/A N/A zone_list

ZONE API N/A N/A zone_getattr

UNIXDISK DSKNAME API statvfs statvfs statvfs64

MOUNTPT API statvfs statvfs statvfs64




DSKSIZE API statvfs statvfs statvfs64

SPCUSED API statvfs statvfs statvfs64

SPCAVAIL API statvfs statvfs statvfs64

INODESIZE API statvfs statvfs statvfs64

INODEUSED API statvfs statvfs statvfs64

INODEFREE API statvfs statvfs statvfs64

PCTSPCUSED API statvfs statvfs statvfs64

PCTINDUSED API statvfs statvfs statvfs64

FSTYPE API statvfs statvfs statvfs64

PCTSPCAV API statvfs statvfs statvfs64

UDSKNAME API statvfs statvfs statvfs64

UMOUNTPT API statvfs statvfs statvfs64

DSKSIZEMB API statvfs statvfs statvfs64

DSKSIZEGB API statvfs statvfs statvfs64

SPUSEDMB API statvfs statvfs statvfs64

SPUSEDGB API statvfs statvfs statvfs64

SPAVMB API statvfs statvfs statvfs64

SPAVGB API statvfs statvfs statvfs64

PCTINDAVAL API statvfs statvfs statvfs64

UNIXDPERF DSKNAME API /bin/iostat pstat_getdisk kstat

MOUNTPT API /bin/iostat pstat_getdisk kstat

DSKXFERRAT API /bin/iostat pstat_getdisk kstat

DSKBYTESIZ API /bin/iostat pstat_getdisk kstat

DSKBUSY API /bin/iostat pstat_getdisk kstat

DSKAVQUE API /bin/iostat pstat_getdisk kstat

DSKAVWAIT API /bin/iostat pstat_getdisk kstat

AVGSERV API /bin/iostat pstat_getdisk kstat

UDSKNAME API /bin/iostat pstat_getdisk kstat

PCTDSKRD API /bin/iostat pstat_getdisk kstat

PCTDSKWR API /bin/iostat pstat_getdisk kstat

DSKRDSEC API /bin/iostat pstat_getdisk kstat

DSKWRSEC API /bin/iostat pstat_getdisk kstat

DSKRDBYSEC API /bin/iostat pstat_getdisk kstat

DSKWRBYSEC API /bin/iostat pstat_getdisk kstat

DSKAVXFR API /bin/iostat pstat_getdisk kstat

UNIXNET FNAME API perfstat_netinterface

DLPI SOCK_DGRAM ioctl

FIPADDR API perfstat_netinterface

SOCK_DGRAM ioctl

SOCK_DGRAM ioctl

FDNSNAME API gethostbyaddr gethostbyaddr gethostbyaddr




FDSTATUS API perfstat_netinterface

SOCK_DGRAM ioctl

SOCK_DGRAM ioctl

FMTU API perfstat_netinterface

DLPI SOCK_DGRAM ioctl

FIBYTES API perfstat_netinterface

DLPI kstat

FOBYTES API perfstat_netinterface

DLPI kstat

FIFRAMES API perfstat_netinterface

DLPI kstat

FOFRAMES API perfstat_netinterface

DLPI kstat

FIERRORS API perfstat_netinterface

DLPI kstat

FOERRORS API perfstat_netinterface

DLPI kstat

FCOLLSNS API perfstat_netinterface

DLPI kstat

FUNIT API perfstat_netinterface

DLPI SOCK_DGRAMioctl

AVCOL1 API perfstat_netinterface

DLPI kstat


DLPI kstat


DLPI kstat


DLPI kstat

AVGINS1 API perfstat_netinterface

DLPI kstat


DLPI kstat


DLPI kstat


DLPI kstat

AVGINERR1 API perfstat_netinterface

DLPI kstat


DLPI kstat


DLPI kstat


DLPI kstat

AVGOUT1 API perfstat_netinterface

DLPI kstat





DLPI kstat


DLPI kstat


DLPI kstat

INMB API perfstat_netinterface

DLPI kstat

OUTMB API perfstat_netinterface

DLPI kstat

INMBTTL API perfstat_netinterface

DLPI kstat

OUTMBTTL API perfstat_netinterface

DLPI kstat

FDNSNAME4 API gethostbyaddr gethostbyaddr gethostbyaddr

IFTYPE API perfstat_netinterface

DLPI kstat

PKTINERRPT API perfstat_netinterface

DLPI kstat

PKTOTERRPT API perfstat_netinterface

DLPI kstat

PKTCOLPCT API perfstat_netinterface

DLPI kstat

MAC_Address API /bin/netstat-in

DLPI - DL_PHYS_ADDR_REQ

/sbin/ifconfig -a

UNIXUSER USERLOGIN API getutxent getutxent getutxent

USERNAME API getpwnam_r getpwnam_r getpwnam_r

USERTTY API getutxent getutxent getutxent

USERIDLE API stat(tty) stat(tty) stat(tty)

USERWHEN API gmtime_r gmtime_r gmtime_r

USERSITE API getutxent getutxent getutxent

UID API getpwuid_r getpwuid_r getpwuid_r

UUSERLOGIN API getutxent getutxent getutxent

UUSERNAME API getpwnam_r getpwnam_r getpwnam_r

UNIXPS PID API getprocs64 pstat_getproc /proc/%s/psinfo

FLAG API getprocs64 pstat_getproc /proc/%s/psinfo

EXECSTATE API getprocs64 pstat_getproc /proc/%s/psinfo

UID API getprocs64 pstat_getproc /proc/%s/psinfo

PPID API getprocs64 pstat_getproc /proc/%s/psinfo

CPU API getprocs64 pstat_getproc /proc/%s/psinfo

PRIORITY API getprocs64 pstat_getproc /proc/%s/psinfo

NICE API getprocs64 pstat_getproc /proc/%s/psinfo

ADDR API getprocs64 pstat_getproc /proc/%s/psinfo




SIZE API getprocs64 pstat_getproc /proc/%s/psinfo

EVENT API getprocs64 pstat_getproc /proc/%s/psinfo

TTY API getprocs64 pstat_getproc /proc/%s/psinfo

TIME API getprocs64 pstat_getproc /proc/%s/psinfo

CMD API getprocs64 pstat_getproc /proc/%s/psinfo

COMMAND API getprocs64 pstat_getproc /proc/%s/psinfo

REPTYPE API getprocs64 pstat_getproc /proc/%s/psinfo

GID API getprocs64 pstat_getproc /proc/%s/psinfo

EUID API getprocs64 pstat_getproc /proc/%s/psinfo

EGID API getprocs64 pstat_getproc /proc/%s/psinfo

PGID API getprocs64 pstat_getproc /proc/%s/psinfo

SESSIONID API getprocs64 pstat_getproc /proc/%s/psinfo

SCHEDCLASS API getprocs64 pstat_getproc /proc/%s/psinfo

CPUID API getprocs64 pstat_getproc /proc/%s/psinfo

USERNAME API getprocs64 pstat_getproc /proc/%s/psinfo

STARTTIME API getprocs64 pstat_getproc /proc/%s/psinfo

ELAPTIME API getprocs64 pstat_getproc /proc/%s/psinfo

VSIZE API getprocs64 pstat_getproc /proc/%s/psinfo

MEMPERCENT API getprocs64 pstat_getproc /proc/%s/psinfo

CPUPERCENT API getprocs64 pstat_getproc /proc/%s/psinfo

TOTCPUPERC API getprocs64 pstat_getproc /proc/%s/psinfo

SAMPCPUPCT API getprocs64 pstat_getproc /proc/%s/psinfo

HEAP API getprocs64 pstat_getproc /proc/%s/psinfo

STACK API getprocs64 pstat_getproc /proc/%s/psinfo

MAJORFAULT API getprocs64 pstat_getproc /proc/%s/usage

MINORFAULT API getprocs64 pstat_getproc /proc/%s/usage

CONTSWITCH API getprocs64 pstat_getproc /proc/%s/usage

INVCONTSWT API getprocs64 pstat_getproc /proc/%s/usage

USERTIME API getprocs64 pstat_getproc /proc/%s/status

SYSTEMTIM API getprocs64 pstat_getproc /proc/%s/status

TOTALTIME API getprocs64 pstat_getproc /proc/%s/status

THREADCNT API getprocs64 pstat_getproc /proc/%s/status

CHILDUTIME API getprocs64 pstat_getproc /proc/%s/status

CHILDSTIME API getprocs64 pstat_getproc /proc/%s/status

CHILDTIME API getprocs64 pstat_getproc /proc/%s/status

WAITCPUTIM API getprocs64 pstat_getproc /proc/%s/usage

WAITLKTIME API getprocs64 pstat_getproc /proc/%s/usage

READWRITE API getprocs64 pstat_getproc /proc/%s/psinfo

CPUTIME API getprocs64 pstat_getproc /proc/%s/psinfo




UCMD API getprocs64 pstat_getproc /proc/%s/psinfo

UCOMMAND API getprocs64 pstat_getproc /proc/%s/psinfo

UUSERNAME API getprocs64 pstat_getproc /proc/%s/psinfo

GRPN API getprocs64 pstat_getproc /proc/%s/psinfo

EUSERN API getprocs64 pstat_getproc /proc/%s/psinfo

EGRPN API getprocs64 pstat_getproc /proc/%s/psinfo

BCMD API getprocs64 pstat_getproc /proc/%s/psinfo

SYSTEMTYPE API uname uname uname

ZONEID API N/A N/A /proc/%s/psinfo

ZONENAME API N/A N/A getzonenamebyid

FILEINFO PATH API FromSituation/Query |"/"

FromSituation/Query |"/"

FromSituation/Query |"/"

FILE API FromSituation/Query

FromSituation/Query

FromSituation/Query

SIZE API stat() stat() stat()

OWNER API stat() stat() stat()

GROUP API stat() stat() stat()

CHANGEDTM API stat() stat() stat()

ACCESSEDTM API stat() stat() stat()

LINKS API stat() stat() stat()

ACCESS API stat() stat() stat()

TYPE API stat() stat() stat()

LINKNAME API stat() stat() stat()

UPATH API stat() stat() stat()

UFILE API stat() stat() stat()

UOWNER API stat() stat() stat()

UGROUP API stat() stat() stat()

ULINKNAME API stat() stat() stat()

SIZEMB API stat() stat() stat()

MODE API stat() stat() stat()

ACCESSTM API stat() stat() stat()

CHECKSUM API ICC library ICC library ICC library

HASHALGO API FromSituation/Query

FromSituation/Query

FromSituation/Query

MODRESULT API ICC library ICC library ICC library

UNIXNFS RSBAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RSNULL API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RSBADLEN API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RSBADHDR API /usr/etc/nfsstat /usr/bin/nfsstat kstat




RCBAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RCRETRAN API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RCBADXID API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RCTIMOUT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RCWAIT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

RCAREF API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSCALLS API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSBAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSPERC API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSNULL API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSGETATT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSSETATT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSROOT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSLOOKUP API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSRDLINK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSREAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSWRCACH API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSWRITE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSCREATE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSREMOVE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSRENAME API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSLINK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSSYMLNK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSMKDIR API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSRMDIR API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSRDDIR API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NSFSSTAT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCCALLS API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCBAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCPERC API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCNULL API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCGETATT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCSETATT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCROOT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCLOOKUP API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCRDLINK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCREAD API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCWRCACH API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCWRITE API /usr/etc/nfsstat /usr/bin/nfsstat kstat




NCCREATE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCREMOVE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCRENAME API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCLINK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCSYMLNK API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCMKDIR API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCRMDIR API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NCFSSTAT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

ZATTRIB API /usr/etc/nfsstat /usr/bin/nfsstat kstat

ZVALUE API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NFSVER API /usr/etc/nfsstat /usr/bin/nfsstat kstat

SRPCALLS API /usr/etc/nfsstat /usr/bin/nfsstat kstat

SRPDUPCHKS API /usr/etc/nfsstat /usr/bin/nfsstat kstat

SRPDUPREQP API /usr/etc/nfsstat /usr/bin/nfsstat kstat

SRPREJPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPRETRPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPRETLPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPTIMOUT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPBADREP API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPBADREPL API /usr/etc/nfsstat /usr/bin/nfsstat kstat

CRPREJSPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NFSATRPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NFSWRPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NFSRDPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

NFSRDLKPCT API /usr/etc/nfsstat /usr/bin/nfsstat kstat

UNIXCPU CPUID API 5.2: perfstast_cpu5.3: mpstat

mpctl kstat

USRCPU API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

SYSCPU API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

IDLECPU API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

WAITIO API 5.2: perfstast_cpu5.3: mpstat

get_sysinfo kstat

CPUBUSY API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

MINF API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

MAJF API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat




XCALLS API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

INTRRUPT API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

INTRTHRD API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

CSW API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

ICSW API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

THRDMIGR API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

SMTX API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

SRWLOCKS API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

SYSCALL API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

CPUSTAT API 5.2: perfstast_cpu5.3: mpstat

get_sysinfo

kstat

CPUUSAGE API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

CPUUVS API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat

AVCPUBIZ1 API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

AVCPUSYS1 API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

AVCPUUSR1 API 5.2: perfstast_cpu5.3: mpstat

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat





pstat_getvminfo

kstat

UNXPRINTQ PRT API /bin/enq N/A N/A

DEVICENM API /bin/enq N/A N/A

PRNTQSTATE API /bin/enq N/A N/A

PRNTQDEPTH API /bin/enq N/A N/A

PRINTQSIZE API /bin/enq N/A N/A

UNIXGROUP GRPNAME API getgrent getgrent getgrent

GRPID API getgrent getgrent getgrent

GRPDUP API getgrent getgrent getgrent

UNIXMEM VMTOT API perfstat_memory_total


swapctl+sysconf

USEDVM API perfstat_memory_total


swapctl+sysconf

AVAILVM API perfstat_memory_total


swapctl+sysconf

USEDVMPCT API perfstat_memory_total


swapctl+sysconf

AVALVMPCT API perfstat_memory_total


swapctl+sysconf

SWAPTOT API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

SWAPUSED API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

SWAPAVAIL API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

SWUSDP API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

SWAVAP API perfstat_memory_total

/usr/sbin/swapinfo

swapctl

MEMTOT API perfstat_memory_total

pstat_getdynamic

sysconf




MEMUSED API perfstat_memory_total

pstat_getdynamic

sysconf

MEMAVAIL API perfstat_memory_total

pstat_getdynamic

sysconf

RMUSDP API perfstat_memory_total

pstat_getdynamic

sysconf

RMAVAP API perfstat_memory_total

pstat_getdynamic

sysconf

VMPGFAULT API perfstat_memory_total

pstat_getvminfo

kstat

VMPGRCLM API perfstat_memory_total

pstat_getvminfo

kstat

VMPGIN API perfstat_memory_total

pstat_getvminfo

kstat

VMPGOUT API perfstat_memory_total

pstat_getvminfo

kstat

VMPGINREQ API perfstat_memory_total

pstat_getvminfo

kstat

VMPGOUTREQ API perfstat_memory_total

pstat_getvminfo

kstat

VMPGINKBS API perfstat_memory_total

pstat_getvminfo

kstat

VMPGOUTKBS API perfstat_memory_total

pstat_getvminfo

kstat

VMPGIN1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat




VMPGOUT1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

VMSCAN API perfstat_memory_total

pstat_getvminfo

kstat

VMSCANKB API perfstat_memory_total

pstat_getvminfo

kstat

VMSCAN1 API perfstat_memory_total

pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat


pstat_getvminfo

kstat

UNIXFILPAT FILENAME API FromSituation/Query

FromSituation/Query

FromSituation/Query

MATCHPAT API FromSituation/Query

FromSituation/Query

FromSituation/Query

MATCHOPT API FromSituation/Query

FromSituation/Query

FromSituation/Query

MATCHCNT API /usr/bin/grep /usr/bin/grep /usr/bin/grep

UNIXFILCMP FILENAME1 API FromSituation/Query

FromSituation/Query

FromSituation/Query

FILENAME2 API FromSituation/Query

FromSituation/Query

FromSituation/Query

COMPOPT API FromSituation/Query

FromSituation/Query

FromSituation/Query

COMPRESULT API /usr/bin/diff |/usr/bin/cmp

/usr/bin/diff |/usr/bin/cmp

/usr/bin/diff |/usr/bin/cmp

UNIXPING

PINGHOST API /usr/sbin/ping /usr/sbin/ping /usr/sbin/ping

PINGRESULT API /usr/sbin/ping /usr/sbin/ping /usr/sbin/ping




HOSTRESP API /usr/sbin/ping /usr/sbin/ping /usr/sbin/ping

UNIXALLUSR

ORIGINNODE API getpwent getpwent getpwent

TIMESTAMP API getpwent getpwent getpwent

USERNAME API getpwent getpwent getpwent

UID API getpwent getpwent getpwent

PWNULL API getpwent getpwent getpwent

USERDUP API getpwent getpwent getpwent

USERSES API getutxent getutxent getutxent

UNIXSOLZON

ZONENAME API N/A N/A zone_getattr

ZID API N/A N/A zone_list

ZSTATUS API N/A N/A zone_getattr

ZPATH API N/A N/A zone_getattr

POOLID API N/A N/A zone_getattr

IPID API N/A N/A zone_getattr

ZCPU API N/A N/A /proc

ZRSS API N/A N/A /proc

ZVMS API N/A N/A /proc

ZCPUS API N/A N/A pconf_info

SCHED API N/A N/A pconf_info

CPUSHARES API N/A N/A prctl

SHAREPCT API N/A N/A prctl

UNIXMACHIN

HOSTNAME API gethostname() gethostname() gethostname()

VENDOR API set to "IBM" set to"Hewlett-Packard"

SI_HW_PROVIDER

MODEL API getaddr() _CS_MACHINE_MODEL

SI_PLATFORM

PHYSPROC API perfstat_cpu pstat_getdynamic

_SC_NPROCESSORS_CONF

PMHZ API perfstat_cpu_total

_SC_CLK_TCK kstat()

MACSERIAL API uname -uM confstr(_CS_MACHINE_SERIAL)

/usr/sbin/eepromnvramrc|/opt/SUNWsneep/bin/sneep*

UUID API uname -f confstr(_CS_MACHINE_IDENT)

gethostid()




VMID API sysconfig(SYS_GETLPAR_INFO)

confstr(_CS_PARTITION_IDENT)

getzonenamebyid(),getzoneid()

UNIXIPADDR

INTFNAME API SIOCGIFCONF SIOCGIFCONF/SIOCGLIFCONF

SIOCGLIFCONF

IPADDRESS API SIOCGIFCONF SIOCGIFCONF/SIOCGLIFCONF

SIOCGLIFCONF

DNSNAME API getaddrinfo getaddrinfo getaddrinfo

IP_Version API socket(SOCK_DGRAM)

socket(SOCK_DGRAM)

socket(SOCK_DGRAM)

KUXPASALRT PASAGTNAME API Proxy AgentServices API

Proxy AgentServices API


STATUS API Proxy AgentServices API



AGENTTYPE API Proxy AgentServices API



DETAILS API Proxy AgentServices API



MESSAGE API Proxy AgentServices API



OSTYPE API Proxy AgentServices API



PID API getprocs64 API pstat_getproc API Read from /proc;PID is thesubdirectory name

PROCNAME API getprocs64 API pstat_getproc API Read from/proc/PID/psinfo

TIMESTAMP API Current time Current time Current time

KUXPASCAP PASAGTNAME API Proxy AgentServices API



AGENTPATH API Proxy AgentServices API






CHECKFREQ API Proxy AgentServices API



CFGSCRIP API Proxy AgentServices API



CPUTHRES API Proxy AgentServices API



DEPENDS API Proxy AgentServices API






KRNLRLS API Proxy AgentServices API



MGTYPE API Proxy AgentServices API



MAXREST API Proxy AgentServices API



MEMTHRES API Proxy AgentServices API



MEMUNIT API Proxy AgentServices API






OSNAME API Proxy AgentServices API



OSVER API Proxy AgentServices API



PASID API Proxy AgentServices API



CAPTS API stat() API structurestat.st_mtime

stat() API structurestat.st_mtime

stat() API structurestat.st_mtime

PROCNAME API Proxy AgentServices API



SERVNAME API Proxy AgentServices API



STRSCRIP API Proxy AgentServices API



STATSCRIP API Proxy AgentServices API



STOPSCRIP API Proxy AgentServices API




KUXPASMGMT MGMTSTAT API Proxy AgentServices API



PASAGTNAME API Proxy AgentServices API






VERSION API Proxy AgentServices API



BUILDNUM API Proxy AgentServices API



MGTYPE API Proxy AgentServices API









SERVNAME API Proxy AgentServices API




KUXPASSTAT STATUS API Proxy AgentServices API



AGENTHOST API Proxy AgentServices API



PASAGTNAME API Proxy AgentServices API






CHECKFREQ API Proxy AgentServices API



COMMAND API getargs() API pstat() API proc_arg_psinfo()API

RESTARTS API Proxy AgentServices API



INSTNAME API Results of cinfo -rand cinfo -o

Results of cinfo -rand cinfo -o

Results of cinfo -rand cinfo -o

IPADDR API getaddrinfo getaddrinfo getaddrinfo

CHECKTS API Proxy AgentServices API



THRCNT API getprocs64() API pstat_getproc()API

proc_arg_psinfo()API




PGFAULT API getprocs64() API pstat_getproc()API


PPID API getprocs64() API pstat_getproc()API


PID API getprocs64() API pstat_getproc()API

Read from /proc;PID is thesubdirectory name

PROCNAME API getprocs64() API pstat_getproc()API

Read from/proc/PID/psinfo

CPUPCT API getprocs64() API pstat_getproc()API


USRPCT API getprocs64() API pstat_getproc()API


RSSIZE API getprocs64() API pstat_getproc()API



MEMSIZE API getprocs64() API pstat_getproc()API





USERNAME API getprocs64() APIandidToUserName()API

pstat_getproc()API andidToUserName()API

proc_arg_psinfo()API andidToUserName()API


Appendix G. Troubleshooting

This appendix explains how to troubleshoot the IBM Tivoli Monitoring: UNIX OSAgent. Troubleshooting, or problem determination, is the process of determiningwhy a certain product is malfunctioning.

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

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

Gathering product information for IBM Software SupportBefore contacting IBM Software Support about a problem you are experiencingwith this product, gather the following information that relates to the problem:

Table 20. Information to gather before contacting IBM Software Support

Information type Description

Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectoryon the host computer. See “Trace logging” on page 204 for lists of all trace log files andtheir locations. See the IBM Tivoli Monitoring User's Guide for general information aboutthe IBM Tivoli Monitoring environment.

UNIX information v Version number and patch levelv 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 forIBM Tivoli Monitoring

Version number of the following members of the monitoring environment:v IBM Tivoli Monitoring. Also provide the patch level, if available.v IBM Tivoli Monitoring: UNIX OS Agent

Screen captures Screen captures of incorrect output, if any.

(UNIX only) Core dumpfiles

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

Built-in troubleshooting featuresThe primary troubleshooting feature in the IBM Tivoli Monitoring: UNIX OS Agentis logging. Logging refers to the text messages and trace data generated by the IBMTivoli Monitoring: UNIX OS Agent. Messages and trace data are sent to a file.

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


Problem classificationThe following types of problems might occur with the IBM Tivoli Monitoring:UNIX OS Agent:v Installation and configurationv General usage and operationv Display of monitoring datav Take Action commands

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

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

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

The default configuration for trace logging, such as whether trace logging isenabled or disabled and trace level, depends on the source of the trace logging.Trace logging is always enabled.

Typically, IBM Software Support applies specialized knowledge to analyze tracelogs to determine the source of problems. However, you can open trace logs in atext editor such as vi to learn some basic facts about your IBM Tivoli Monitoringenvironment as described in “Examples: using trace logs” on page 207.

Overview of log file managementTable 21 on page 206 provides the names, locations, and descriptions of RAS1 logfiles. 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 computer on which the monitoring component

is running.v product is the two-character product code. For Monitoring Agent for UNIX OS,

the product code is ux.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 logrolling.

Examples of trace loggingFor example, if a UNIX monitoring agent is running on computer "server01", theRAS log file for the Monitoring Agent for UNIX OS might be named as follows:server01_ux_kuxagent_437fc59-01.log

For long-running programs, the nn suffix is used to maintain a short history of logfiles for that startup of the program. For example, the kuxagent program mighthave a series of log files as follows:server01_ux_kuxagent_437fc59-01.logserver01_ux_kuxagent_437fc59-02.logserver01_ux_kuxagent_437fc59-03.log

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

Each time a program is started, a new timestamp is assigned to maintain a shortprogram history. For example, if the Monitoring Agent for UNIX OS is startedtwice, it might have log files as follows:server01_ux_kuxagent_437fc59-01.logserver01_ux_kuxagent_437fc59-02.logserver01_ux_kuxagent_437fc59-03.log

server01_ux_kuxagent_537fc59-01.logserver01_ux_kuxagent_537fc59-02.logserver01_ux_kuxagent_537fc59-03.log

Each program that is started has its own log file. For example, the MonitoringAgent for UNIX OS would have agent logs in this format:server01_ux_kuxagent_437fc59-01.log

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

where ifstat is the program name.

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

Principal trace log files

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

Appendix G. Troubleshooting 205

Table 21. Trace log files for troubleshooting agents

System where logis located

File name and path Description

On the computerthat hosts themonitoring agent

See “Definitions ofvariables” on page207 fordescriptions of thevariables in thefile names incolumn two.

The RAS1 log files are namedhostname_ux_program_timestamp-nn.log and arelocated in the install_dir/logs path.Note: File names for RAS1 logs include ahexadecimal timestamp.

Also on UNIX, a log with a decimal timestamp isprovided: hostname_ux_timestamp.log andhostname_ux_timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn is theprocess ID number.

Traces activity of the monitoring agent.Note: Other logs, such as logs for UNIXcollector processes and Take Actioncommands (if available), have a similarsyntax and are located in this directorypath.

The *.LG0 file is located in the install_dir/logspath.

A new version of this file is generatedevery time the agent is restarted. IBM TivoliMonitoring generates one backup copy ofthe *.LG0 file with the tag .LG1. View .LG0to learn the following details regarding thecurrent 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 TivoliEnterpriseMonitoring Server

See “Definitions ofvariables” on page207 fordescriptions of thevariables in thefile names incolumn two.

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

On Windows: The file in the install_dir\InstallITM path.

Provides details about products that areinstalled.Note: Trace logging is enabled by default.A configuration step is not required toenable this tracing.

The Warehouse_Configuration.log file is locatedin the following path on Windows:install_dir\InstallITM.

Provides details about the configuration ofdata warehousing for historical reporting.

The RAS1 log file is namedhostname_ms_timestamp-nn.log and is located inthe following path:

v On Windows: install_dir\logs

v On UNIX: install_dir/logs

Note: File names for RAS1 logs include ahexadecimal timestamp

Also on UNIX, a log with a decimal timestamp isprovided: hostname_ms_timestamp.log andhostname_ms_timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn is theprocess ID number.

Traces activity on the monitoring server.


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

System where logis located

File name and path Description

On the TivoliEnterprise PortalServer

See “Definitions ofvariables” fordescriptions of thevariables in thefile names incolumn two.

The RAS1 log file is namedhostname_cq_timestamp-nn.log and is located inthe following path:

v On Windows: install_dir\logs

v On UNIX: install_dir/logs

Note: File names for RAS1 logs include ahexadecimal timestamp

Also on UNIX, a log with a decimal timestamp isprovided: hostname_cq_timestamp.log andhostname_cq_timestamp.pidnnnnn in theinstall_dir/logs path, where nnnnn is the process IDnumber.

Traces activity on the portal server.

The TEPS_ODBC.log file is located in the followingpath on Windows: install_dir\InstallITM.

When you enable historical reporting, thislog file traces the status of the warehouseproxy agent.

Definitions of variables for RAS1 logs:v hostname is the host name of the computer 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 UNIX OS, the product code is ux.v program is the name of the program being run.v timestamp is an eight-character hexadecimal timestamp representing the time at which the program started.v nn is a rolling log suffix. See “Examples of trace logging” on page 205 for details of log rolling.

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

Examples: using trace logsTypically IBM Software Support applies specialized knowledge to analyze tracelogs to determine the source of problems. However, you can open trace logs in atext editor such as vi to learn some basic facts about your IBM Tivoli Monitoringenvironment. You can use the ls -ltr command to list the log files in theinstall_dir/logs directories, sorted by time they were last updated.

Example oneThis excerpt shows the typical log for a failed connection between amonitoring agent and a monitoring server with the host name server1a:

(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE

(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect tobroker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK

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

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

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

Key points regarding the preceding excerpt:


v The monitoring server appends the KUX product code to the servername to form a unique name (SERVER5B:KUX) for this instance ofMonitoring Agent for UNIX OS. This unique name enables you todistinguish multiple monitoring products that might be running onSERVER5B.

v The log shows when the agent started (ON-LINE) and later stopped(OFF-LINE) in the environment.

v For the sake of brevity an ellipsis (...) represents the series of trace logentries that were generated while the agent was running.

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

v The ON-LINE and OFF-LINE log entries are always available in thetrace log. All trace levels that are described in “Setting RAS traceparameters” provide these entries.

Setting RAS trace parameters

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

Background InformationMonitoring Agent for UNIX OS uses RAS1 tracing and generates the logsdescribed in Table 21 on page 206. The default RAS1 trace level is ERROR.

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

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

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

After you finishMonitor the size of the logs directory. Default behavior can generate a total of 45 to60 MB for each agent that is running on a computer. For example, each databaseinstance that you monitor 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 toprevent logging activity from occupying too much disk space.

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

Consider using collector trace logs (described in Table 21 on page 206) as anadditional source of troubleshooting information.


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

ProcedureSpecify RAS1 trace options in the install_dir/config/ux.ini file. You canmanually edit the configuration file to set trace logging:1. Open the trace options file: /install_dir/config/ux.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 Tracingoption:export KBB_RAS1='ERROR (UNIT:kux ALL) (UNIT:kra ALL)'

3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation oflog 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 arediscarded. Default value is 9.

– LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Defaultvalue is 5.

v IBM Software Support might guide you to modify the following parameters:– COUNT: the number of log files to keep in the rolling cycle of one

program startup. Default 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 ofthe log file directory, log file name, and the inventory control filedirectory and name. Do not modify these values or log information canbe lost.

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

Problems and workaroundsThe following sections provide symptoms and workarounds for problems thatmight occur with Monitoring Agent for UNIX OS:v “Installation and configuration troubleshooting” on page 210v “Agent troubleshooting” on page 214v “Tivoli Enterprise Portal troubleshooting” on page 218v “Workspace troubleshooting” on page 219v “Troubleshooting for remote deployment” on page 219v “Situation troubleshooting” on page 220v “Take Action command troubleshooting” on page 224v “Troubleshooting for UNIX” on page 224

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


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

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

Agent upgrade and restart using non-rootThe monitoring agent can run using a non-root user ID on UNIX and Linuxsystems. This can be done by running the itmcmd agent start command whilelogged in as a non-root user, and this can be done remotely by deploying the agentusing the Run As option on the GUI or using the _UNIX_STARTUP_.Usernameoption on the tacmd addSystem command line. If the agent is running using anon-root user ID, and then the agent is upgraded, restarted remotely, restarted as aresult of a system reboot, or the itmcmd agent start is run using the root user ID,then the monitoring agent subsequently runs as the root user. To confirm the userID that the monitoring agent is using, run the following command:itm_install/bin/cinfo -r

If the agent is using root, and that is not the desired user ID, then use thefollowing steps to restart the agent:1. Log in as root.2. Run the itmcmd agent stop command.3. Log in (or 'su') to the user ID that you want the agent to run as.4. Run the itmcmd agent start command.

If the agent was running as root because of a system reboot, then edit the startupfile using the following steps so that the appropriate user ID is used the next timethe system is rebooted:1. Look at install_dir/registry/AutoStart, and get NUM.2. Edit the autostart for your operating system:

The location of the startup file is platform dependent as follows:v AIX: /etc/rc.itmNUMv HP-UX: /sbin/init.d/ITMAgentsNUMv Linux: /etc/init.d/ITMAgentsNUMv Solaris: /etc/init.d/ITMAgentsNUM

3. Add entries for your operating system using the following command:/usr/bin/su - instancename-c "install_dir/bin/itmcmd agent-h install_dir-o instancenamestart product_code"

Where:

instancenameName of the instance

install_dirName of the directory

product_code2-character product code for the agent, for example, ux for theMonitoring Agent for UNIX OS


Examples:

v For AIX, add entries with the following format:su - USER -c " /opt/IBM/ITM/bin/itmcmd agent-o INSTANCE start ux”

Where:

USER Name of the user

INSTANCEName of the instance

v For Linux, HP_UX, and Solaris, add entries with the following format:/bin/su - USER -c " /opt/IBM/ITM/bin/itmcmd agent-o INSTANCE start ux >/dev/null 2>&1"

Where:

USER Name of the user

INSTANCEName of the instance

4. Repeat Steps 1 through 3 for all occurrences of stop.5. Save the file.

Table 22. Problems and solutions for installation and configuration

Problem Solution

Installation fails on HPUX11. Thelog for the monitoring agent showsthe message listed in the next rowof this table.

You must install the PHSS_30966 patch on the HPUX system. See the Web sitelisted in the next row of this table for details.

When a patch is missing on HPUX11, the following message is generated:

/usr/lib/pa20_64/dld.sl: Unsatisfied code symbol 'dladdr' in load module \'/opt/IBM/ITM/tmaitm6/hp116/lib/libkbb.sl'

The following Web site provides details about the required patch for HPUX11:

http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_30966&admit=-1335382922+112672773755 \6+28353475

When you upgrade to IBM TivoliMonitoring, you might need toapply fixpacks to Candle, Version350, agents.

Fixpacks for Candle, Version 350, are delivered as each monitoring agent isupgraded to IBM Tivoli Monitoring.Note: The IBM Tivoli Monitoring download image or CD provides applicationfixpacks for the monitoring agents that are installed from that CD (forexample, the agents for operating systems such as Windows, Linux, UNIX, andi5/OS®). The upgrade software for other agents is located on the downloadimage or CDs for that specific monitoring agent, such as the agents fordatabase applications.

If you do not upgrade the monitoring agent to IBM Tivoli Monitoring, theagent continues to work. However, you must upgrade to have all thefunctionality that IBM Tivoli Monitoring offers.

Presentation files and customizedOMEGAMON® screens for Candlemonitoring agents need to beupgraded to a new Linux onz/Series system.

The upgrade from version 350 to IBM Tivoli Monitoring handles export of thepresentation files and the customized OMEGAMON screens.


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

Problem Solution

The product fails to do amonitoring activity that requiresread, write, or execute permissions.For example, the product might failto run a Take Action command orread a log.

The monitoring agent must have the permissions necessary to performrequested actions. For example, if the user ID you used to log onto the systemto install the monitoring agent (locally or remotely) does not have thepermission to perform a monitoring operation (such as running a command),the monitoring agent is not able perform the operation.

While installing the agent from aCD, the following message isdisplayed and you are not able tocontinue the installation:

install.sh warning: unarchiveof "/cdrom/unix/cienv1.tar" mayhave failed

This error is caused by low disk space. Although the install.sh scriptindicates that it is ready to install the agent software, the script considers thesize of all tar files, not the size of all the files that are contained within the tarfile.Run the df -k command to check whether the file systems have enoughspace to install agents.

The Monitoring Agent for UNIXOS repeatedly restarts.

You can collect data to analyze this problem as follows:

1. Access the install_dir/config/ux.ini file, which is described in “SettingRAS trace parameters” on page 208.

2. Add the following line: KBB_SIG1=trace –dumpoff

Agents in the monitoringenvironment use differentcommunication protocols. Forexample, some agents havesecurity enabled and others do not.

Configure both the monitoring server and the Warehouse proxy server toaccept multiple protocols, as described in the IBM Tivoli Monitoring Installationand Setup Guide.

Creating a firewall partition file:The partition file enables an agentto connect to the monitoring serverthrough a firewall.

How it works: When the agents start, they search KDCPARTITION.TXT for thefollowing matches:

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.

The Monitoring Agent for UNIXOS is started and running but notdisplaying data in the TivoliEnterprise Portal.

Check the following issues:

1. Check the Monitoring Agent for UNIX OS log files to see whether there areconnection problems.

2. If there are no connection problems, check whether the agent hasterminated. (Search for the word "terminated" in the log.)

3. If the agent is not terminated, confirm that you have added applicationsupport for the Monitoring Agent for UNIX in the Tivoli EnterpriseMonitoring Server, as described in the IBM Tivoli Monitoring Installation andSetup Guide.

You successfully migrate anOMEGAMON monitoring agent toIBM Tivoli Monitoring, Version6.1.0. However, when youconfigure historical data collection,you see an error message thatincludes, Attribute name may beinvalid, or attribute file notinstalled for warehouse agent.

Install the agent's application support files on the Tivoli Enterprise MonitoringServer, using the following steps:

1. Open the Manage Tivoli Enterprise Monitoring Services 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 the IBM Tivoli Monitoring Installation and Setup Guide for moreinformation on adding application support.

Ensure that the agent's application support files are pushed to the system thathouses the Warehouse Proxy Agent. The Warehouse Proxy must be able toaccess the short attribute names for tables and columns. That way, if the longerversions of these names exceed the limits of the Warehouse database, theshorter names can be substituted.


Table 23. General problems and solutions for uninstallation

Problem Solution

The way to remove inactivemanaged systems (systems whosestatus is OFFLINE) from theEnterprise navigation tree in theportal is not obvious.

When you want to remove a managed system from the navigation tree,complete the following steps:

1. Click Enterprise in the navigation tree.

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

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

Unique names for monitoring componentsIf you have multiple instances of a monitoring agent, you must decide how toname the monitoring agents. This name is intended to uniquely identify thatmonitoring agent. The agent's default name is composed of three qualifiers:v Optional instance namev Computer network host namev Agent product node type

An agent name truncation problem can occur when the network domain name isincluded in the network host name portion of the agent name. For example,instead of just the host name myhost1 being used, the resulting host name mightbe myhost1.acme.north.prod.com. Inclusion of the network domain name causesthe agent name in the example above to expand toSERVER1:myhost1.acme.north.prod.com:KXX. This resulting name is 39 characterslong. It is truncated to 32 characters resulting in the nameSERVER1:myhost1.acme.north.prod.

The agent name truncation is only a problem if there is more than one monitoringagent on the same system. In this case, the agent name truncation can result incollisions between agent products attempting to register using the same truncatedname value. When truncated agent names collide on the same system, this can leadto Tivoli Enterprise Monitoring Server problems with corrupted EIB tables. Theagent name collision in the Tivoli Enterprise Monitoring Server might cause aregistered name to be associated with the wrong product.

In general, create names that are short but meaningful within your environment.Use the following guidelines:v Each name must be unique. One name cannot match another monitoring agent

name exactly.v Each name must begin with an alpha character.v Do not use blanks or special characters, including $, #, and @.v Each name must be between 2 and 32 characters in length.v Monitoring agent naming is case-sensitive on all operating systems.

Create the names by completing the following steps:1. Open the configuration file for the monitoring agent, which is located in the

following path:v On Windows: &install_dir;\tmaitm6\Kproduct_codeCMA.INI. For example,

the product code for the Monitoring Agent for Windows OS is NT and thefile name is KNTCMA.INI.

v On UNIX and Linux: install_dir/tmaitm6/product_code.ini andproduct_code.config. For example, the file names for the Monitoring Agentfor UNIX OS is ux.ini and ux.config.


2. Find the line the begins with CTIRA_HOSTNAME=.3. Type a new name for host name that is a unique, shorter name for the host

computer. The final concatenated name including the subsystem name, newhost name, and UX, cannot be longer than 32 characters.

Note: You must ensure that the resulting name is unique with respect to anyexisting monitoring component that was previously registered with theTivoli 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.

If you do not find the files mentioned in the preceding steps, perform thefollowing workarounds:1. Change CTIRA_HOSTNAME environment variable in the configuration file of

the monitoring agent.v Find the KUXENV file in the same path mentioned in the preceding row.v For z/OS® agents, find the RKANPAR library.v For i5/OS agents, find the QAUTOTMP/KMSPARM library in member

KBBENV.2. 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 and

to config/product_code.config files.v On z/OS: Add the variable to the RKANPAR library, member

Kproduct_codeENV.v On i5/OS: Add the variable to the QAUTOTMP/KMSPARM library in

member KBBENV.3. Some monitoring agents (for example, the monitoring agent for MQ Series) do

not reference the CTIRA_HOSTNAME environment variable to generatecomponent names. Check the documentation for the monitoring agent that youare using for information on name generation. If necessary, contact IBMSoftware Support.

Agent troubleshootingThis section lists problems that might occur with agents.

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


Table 24. Agent problems and solutions

Problem Solution

A configured and runninginstance of the monitoring agentis not displayed in the TivoliEnterprise Portal, but otherinstances of the monitoring agenton the same system do appear inthe portal.

Tivoli Monitoring products use Remote Procedure Call (RPC) to define andcontrol product behavior. RPC is the mechanism that allows a client process tomake a subroutine call (such as GetTimeOfDay or ShutdownServer) to a serverprocess somewhere in the network. Tivoli processes can be configured to useTCP/UDP, TCP/IP, SNA, and SSL as the desired protocol (or deliverymechanism) for RPCs.

"IP.PIPE" is the name given to Tivoli TCP/IP protocol for RPCs. The RPCs aresocket-based operations that use TCP/IP ports to form socket addresses. IP.PIPEimplements virtual sockets and multiplexes all virtual socket traffic across asingle physical TCP/IP port (visible from the netstat command).

A Tivoli process derives the physical port for IP.PIPE communications based onthe configured, well-known port for the HUB Tivoli Enterprise MonitoringServer. (This well-known port or BASE_PORT is configured using the 'PORT:'keyword on the KDC_FAMILIES / KDE_TRANSPORT environment variable anddefaults to '1918'.)

The physical port allocation method is defined as (BASE_PORT + 4096*N) whereN=0 for a Tivoli Enterprise Monitoring Server process and N={1, 2, ..., 15} for anon-Tivoli Enterprise Monitoring Server. Two architectural limits result as aconsequence of the physical port allocation method:

v No more than one Tivoli Enterprise Monitoring Server reporting to a specificTivoli Enterprise Monitoring Server HUB can be active on a system image.

v No more that 15 IP.PIPE processes can be active on a single system image.

A single system image can support any number of Tivoli Enterprise MonitoringServer processes (address spaces) provided that each Tivoli EnterpriseMonitoring Server on that image reports to a different HUB. By definition, thereis one Tivoli Enterprise Monitoring Server HUB per monitoring Enterprise, sothis architecture limit has been simplified to one Tivoli Enterprise MonitoringServer per system image.

No more that 15 IP.PIPE processes or address spaces can be active on a singlesystem image. With the first limit expressed above, this second limitation refersspecifically to Tivoli Enterprise Monitoring Agent processes: no more that 15agents per system image.

This limitation can be circumvented (at current maintenance levels, IBM TivoliMonitoring V6.1 Fix Pack 4 and later) if the Tivoli Enterprise Monitoring Agentprocess is configured to use EPHEMERAL IP.PIPE. (This is IP.PIPE configuredwith the 'EPHEMERAL:Y' keyword in the KDC_FAMILIES / KDE_TRANSPORTenvironment variable). There is no limitation to the number of ephemeral IP.PIPEconnections per system image. If ephemeral endpoints are used, the WarehouseProxy Agent is accessible from the Tivoli Enterprise Monitoring Server associatedwith the agents using ephemeral connections either by running the WarehouseProxy Agent on the same computer or by using the Firewall Gateway feature.(The Firewall Gateway feature relays the Warehouse Proxy Agent connectionfrom the Tivoli Enterprise Monitoring Server computer to the Warehouse ProxyAgent computer if the Warehouse Proxy Agent cannot coexist on the samecomputer.)

When you edit the configurationfor an existing monitoring agent,the values displayed are notcorrect.

The original configuration settings might include non-ASCII characters. Thesevalues were stored incorrectly and result in the incorrect display. Enter newvalues using only ASCII characters.


Table 24. Agent problems and solutions (continued)

Problem Solution

The Monitoring Agent for UNIXOS starts and displays in theTivoli Enterprise Portal, butitmcmd/CandleAgent indicatesthat the agent has failed to startand is not running.

Check the config/ux.ini file for any blank lines. Delete them and restart theagent.

Attributes do not allownon-ASCII input in the situationeditor.

None. Any attribute that does not include "(Unicode)" might support only ASCIIcharacters. For example "Attribute (Unicode)" will support unicode but"Attribute" without "(Unicode)" might only support ASCII characters.

Changes made to theconfiguration of monitoring donot take effect.

Restart the monitoring agent so that your changes take effect.

(For Monitoring Agent for UNIXOS agents running on AIX only)When you use Logical Partitions(LPARs) on AIX 5.3 LPARs, theMonitoring Agent for UNIX OSfails to automatically detect somedynamic changes.

Restart the Monitoring Agent for UNIX OS so that it can detect the changes. Forexample, if the allocated memory for an LPAR changed, restart the agent.

You have installed the productmanually, using an approachother than the one documentedin the IBM Tivoli MonitoringInstallation and Setup Guide. Youneed to confirm whether youhave run the SetPerm command.

When you use the installation approach that is documented in the IBM TivoliMonitoring Installation and Setup Guide, the SetPerm command is runautomatically to set required permissions for the processes that IBM TivoliMonitoring runs. When you do not use this approach the executables for themonitoring agent do not have the required privileges.

Run the SetPerm command (which is located under install_dir/bin/ directory).The following example shows lists of agent binaries before and after they havethe required privileges.

The monitoring agent support has the existing permissions:

-rwxrwx--- 1 itmuser itmusers 32243 Sep 09 13:30 ifstat-rwxrwx--- 1 itmuser itmusers 41045 Sep 09 13:30 kux_vmstat-rwxrwx--- 1 itmuser itmusers 507562 Sep 09 13:30 kuxagent-rwxrwx--- 1 itmuser itmusers 5772 Sep 09 13:30 kuxdstat-rwxrwx--- 1 itmuser itmusers 42514 Sep 09 13:30 nfs_stat-rwxr-sr-x 1 itmuser system 128211 Sep 09 13:30 stat_daemon

The permissions for the Solaris2 monitoring agent are as follows:

UID r-s r-x r-x kuxagent uid(0) gid(3)

The user has the following permissions:

real user id(0) effective user id(0)real group id(1) effective group id(1)

If you have not run the SetPerm command, the following permissions are set:

rwx rwx r-x uid(35008) gid(1111) kuxagentrwx rwx r-x uid(35008) gid(1111) stat_daemonrwx rwx r-x uid(35008) gid(1111) ifstatrwx rwx r-x uid(35008) gid(1111) nfs_statrwx rwx r-x uid(35008) gid(1111) kuxagent

Note: If the log file has SUID, that means that you have run the SetPerm command.



Problem Solution

Solaris agent is terminatingunexpectedly.

Obtain the agent log file and verify whether it contains any of the followinginformation in the log file:

bad_scan in server rpcbad_scan could be caused by nfsstate command output mismatch or NFS notactive on this system***** nfs_stat terminating ****read 0 expected 248nsf-sd *** data collection terminated ***

If the log file has this type of information, see “Support information” on page225.

The agent is installed andrunning normally. Afterrebooting the computer, whereTivoli Enterprise MonitoringServer was running, the agent isnot online.

This problem can occur when the root user account is used to install and startthe agent. Verify whether you have used the root user account to install theagent.To change the user account from root to some other user account, seeEnabling the Monitoring Agent for UNIX OS to run as a non-Administrator user.

You want to have multipleinstances of the same MonitoringAgent for UNIX OS running onthe same system but talking todifferent Tivoli EnterpriseMonitoring Server.

If you plan to install and run the Monitoring Agent for UNIX OS and MonitoringAgent for Linux OS agent on one computer, they can use the same networkinterface because they run as different processes.

However, if you want to have two UNIX or two Linux agents on the samecomputer or want to run two instances of each agent, install two-networkadapters. Each instance is configured for the host-specific address so they can berecognized in the configuration settings.

The Monitoring Agent for UNIXOS fails and the log file has thefollowing message:

KUXDSTAT: Contact CustomerSupport disk performancetable exceeded.

This message is not related to the failure, so you can ignore it. If the agent isfailing, search for a different cause. Further analyze the log to know whether theagent has terminated.

When you restart the system thathosts the Tivoli EnterpriseMonitoring Server, theMonitoring Agent for UNIX OSdoes not start automatically.However, when you useCandleAgent start, the agent isstarts and continues running.

If the agent does not connect to the Tivoli Enterprise Monitoring Serverautomatically, it means that you used the root user account to install and startthe Monitoring Agent for UNIX OS. Most of the time, using the root accountdoes not cause a problem, but the result is unpredictable.

Check the IBM Tivoli Monitoring root account to install and start the agent. Tochange the user account from root to another user account, see Enabling theMonitoring Agent for UNIX OS to run as a non-Administrator user.



Problem Solution

The Monitoring Agent for UNIXOS (specifically the kuxagentprocess) uses a large amount ofsystem resources.

In most cases, the problem occurs during the backup. Any one of the followingscenarios can cause this problem.

The agent is running during the backupAfter 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 wasrebooted and the agent has been installed by the root user account.

The agent is running during the backupDuring the backup, some of the service might be interrupted or not beavailable or locked for some amount of time. While the backup processis going on, the Monitoring Agent for UNIX OS, which is runningparallel, might wait for resources to be freed by the backup process.When the backup is completed and you are viewing the agent, highCPU 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. Stopthe 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 froman init process script when you restart the system.

The computer that hosts the Tivoli Enterprise Monitoring Server wasrebooted and the agent has been installed by the root user account.Verify whether the Monitoring Agent for UNIX OS log file has thefollowing information:

Unable to find running Tivoli Enterprise Monitoring Server on CMSLIST

You have two monitoring agentswith the same name due totruncation.

Each name must be between 2 and 32 characters in length. Each agent namemust be unique on the Tivoli Enterprise Monitoring Server. If the host name plusdomain name length is greater than 32 characters multiple agents will conflictresulting in odd behavior (such as the agents appearing and disappearing fromthe Tivoli Enterprise Portal). Setting a unique host name resolves this issue. See“Unique names for monitoring components” on page 213 for more information.

Unicode filenames not properlybeing displayed in the FileInformation Viewer.

Due to incompatibilities in reading information from different language codepages, any file that has non-ascii text will not be properly displayed in the FileInformation viewer.

Unicode process names notproperly being displayed inProcess workspace.

Due to incompatibilities in reading information from different language codepages, any process that has non-ascii text will not be properly displayed in theProcess Workspace.

On AIX systems, theProcess.Base_Command attributereturns different data thanexpected.

The data should represent the name of the actual program being run. This is acurrent limitation on this platform.

Tivoli Enterprise Portal troubleshootingTable 25 on page 219 lists problems that might occur with the Tivoli EnterprisePortal. This appendix provides agent-specific troubleshooting information. See theIBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.


Table 25. Tivoli Enterprise Portal problems and solutions

Problem Solution

Historical data collection isunavailable because ofincorrect queries in the TivoliEnterprise Portal.

The column, Sort By, Group By, and First/Last functions are not compatible withthe historical data collection feature. Use of these advanced functions will make aquery ineligible for historical data collection.

Even if data collection has been started, you cannot use the time span feature if thequery for the chart or table includes any column functions or advanced queryoptions (Sort By, Group By, First / Last).

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

See the IBM Tivoli Monitoring Administrator's Guide the Tivoli Enterprise Portalonline Help for information on the Historical Data Collection function.

When you use a long processname in the situation, theprocess name is truncated.

Truncation of process names in the portal display is the expected behavior. 64 bytesis the maximum name length.

Troubleshooting for remote deploymentTable 26 lists problems that might occur with remote deployment. This appendixprovides agent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information.

This section describes problems and solutions for remote deployment and removalof agent software Agent Remote Deploy:

Table 26. Remote deployment problems and solutions

Problem Solution

The removal of a monitoring agent fails when youuse the remote removal process in the TivoliEnterprise Portal desktop or browser.

This problem might happen when you attempt the remoteremoval process immediately after you have restarted theTivoli Enterprise Monitoring Server. You must allow time forthe monitoring agent to refresh its connection with the TivoliEnterprise Monitoring Server before you begin the remoteremoval process.

Remote deploy fails. Ensure that the OS agent is running as root.

Problems deploying agents through remotedeployment.

If the user cannot deploy an agent without receiving an error,the deployed agent might require root permissions. Ensurethat the deploying agent (UNIX agent binary - kuxagent) hasroot permissions by either starting it as root or assigningSETUID root permissions to the deploying agent.

Workspace troubleshootingTable 27 shows problems that might occur with workspaces. This appendixprovides agent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information.

Table 27. Workspace problems and solutions

Problem Solution

You see the following message: KFWITM083WDefault link is disabled for the selectedobject; please verify link and link anchordefinitions.

You see this message because some links do not have defaultworkspaces. Right-click the link to access a list of workspaces toselect.


Table 27. Workspace problems and solutions (continued)

Problem Solution

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute's name.

A link to 'Process Resource' leads to a supersededworkspace.

Use the provided workspace as a template for creating a customworkspace using the "Resource (621)" query. Then you candirectly access the new workspace and see all the availableprocesses on the system. You can create links to the workspaceand also create links from the workspace pointing to otherworkspaces.

At the bottom of each view, you see thefollowing Historical workspace KFWITM220Eerror: Request failed during execution.

Ensure that you configure all groups that supply data to theview. In the Historical Configuration view, ensure that datacollection is started for all groups that supply data to the view.

You start collection of historical data but the datacannot be seen.

Managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See Chapter 2, “Requirements for the monitoring agent,” onpage 5 for information on managing this feature includinghow to set the interval at which data is collected. By setting amore frequent interval for data collection you reduce the loadon the system incurred every time data is uploaded.

v You use the Summarization and Pruning monitoring agent tocollect specific amounts and types of historical data. Be awarethat historical data is not displayed until the Summarizationand Pruning monitoring agent begins collecting the data. Bydefault, this agent begins collection at 2 AM daily. At thatpoint, data is visible in the workspace view. See the IBM TivoliMonitoring Administrator's Guide to learn how to modify thedefault collection settings.

Situation troubleshootingThis section provides information about both general situation problems andproblems with the configuration of situations. See the IBM Tivoli MonitoringTroubleshooting Guide for more information about troubleshooting for situations.

Specific situation problemsTable 28 lists problems that might occur with specific situations.

Table 28. Specific situation problems and solutions

Problem Solution

You want to change the appearance ofsituations when they are displayed in aWorkspace view.

1. Right-click an item in the Navigation tree.

2. Select Situations in the pop-up menu. The Situation Editor window isdisplayed.

3. Select the situation that you want to modify.

4. Use the Status pull-down menu in the lower right of the window toset the status and appearance of the Situation when it triggers.Note: This status setting is not related to severity settings in IBMTivoli Enterprise Console.


Table 28. Specific situation problems and solutions (continued)

Problem Solution

Situations are triggered in the TivoliEnterprise Monitoring Server, but eventsfor the situation are not sent to theTivoli Enterprise Console server. TheTivoli Enterprise Monitoring Server isproperly configured for eventforwarding, and events for many othersituations are sent to the event server.

This condition can occur when a situation is only monitoring the status ofother situations. The event forwarding function requires an attributegroup reference in the situation in order to determine the correct eventclass to use in the event. When the situation only monitors othersituations, no attribute groups are defined and the event class cannot bedetermined. Because the event class cannot be determined, no event issent.

This is a limitation of the Tivoli Enterprise Monitoring Server eventforwarding function. Situations that only monitor other situations do notsend events to the event server.

Monitoring activity requires too muchdisk space.

Check the RAS trace logging settings that are described in “Setting RAStrace parameters” on page 208. For example, trace logs grow rapidlywhen you apply the ALL logging option.

A formula that uses mathematicaloperators is displayed to be incorrect.For example, if you were monitoringLinux, a formula that calculates whenFree Memory falls under 10 percent ofTotal Memory does not work: LT#'Linux_VM_Stats.Total_Memory' / 10

This formula is incorrect because situation predicates support only logicaloperators. Your formulas cannot have mathematical operators.Note: The Situation Editor provides alternatives to math operators.Regarding the example, you can select % Memory Free attribute andavoid the need for math operators.

If you are running a Version 350Monitoring Agent for UNIX OS and youchoose to alter the views to include aVersion 610 UNICODE attribute, beaware that data for this attribute is notdisplayed and you see a blank columnin this view.

To enable Unicode and other features, upgrade the monitoring agent toIBM Tivoli Monitoring, Version 6.1.0.

The Size attribute in the FileInformation group of Monitoring Agentfor UNIX OS provides file size metricsin bytes, and the resulting integers areso long that they are difficult to read.

Use the option to log size metrics in megabytes (MB). Future releases ofthis monitoring agent can provide the option to capture this metric inother units, such as KB.

You see the 'Unable to get attributename' error in the Tivoli EnterpriseMonitoring Server log after creating asituation.

Install the agent's application support files on the Tivoli EnterpriseMonitoring Server, using the following steps:

1. Open the Manage Tivoli Enterprise Monitoring Services window.

2. Right-click the name of the monitoring server.

3. Select Advanced > Add TEMS Application Support in the pop-upmenu. Add application support if any for any agent that is missingfrom the list. See the IBM Tivoli Monitoring Installation and Setup Guidefor more information on adding application support.

Events received at the Tivoli EnterpriseConsole server from IBM TivoliMonitoring do not have values for allevent attributes (slots) even though thevalues are visible in workspace views.

The problem is due to a limitation in the IBM Tivoli Monitoring interfacecode that generates Tivoli Enterprise Console events from situations. Thesituation results are provided in a chain of buffers of 3000 bytes each. Theinterface code currently extracts event information from only the firstbuffer. When situations or agent table data expands into a second buffer,this additional data is not examined, and it is not included in events sentto the Tivoli Enterprise Console server.


Table 28. Specific situation problems and solutions (continued)

Problem Solution

Tivoli Enterprise Console events fromIBM Tivoli Monitoring 6.2 for IBMTivoli Monitoring 5.x migratedsituations receive parsing errors in theTivoli Enterprise Console server.

Complete the following two steps:

1. Ensure that you have the IBM Tivoli Monitoring 6.2 Event Syncinstalled on your Tivoli Enterprise Console server.

2. Obtain updated baroc files from IBM Tivoli Monitoring 6.2 for themonitoring agent's events. Updated baroc files are on the TivoliEnterprise Monitoring Server in the CANDLEHOME/CMS/TECLIB/itm5migrdirectory.

You are receiving Tivoli BusinessSystems Management events that cannotbe associated due to application_oid andapplication_class not being set.

The problem is due to IBM Tivoli Monitoring 6.2 sending TivoliEnterprise Console events for IBM Tivoli Monitoring 5.x migratedsituations. These events are not able to set the cited slot values. Replacethe agent_name_forward_tbsm_event_cb.sh script on the Tivoli EnterpriseConsole server with the version of this file from the Tivoli EnterpriseMonitoring Server in the CANDLEHOME/CMS/TECLIB/itm5migr directory.

Problems with configuration of situationsTable 29 lists problems that might occur with situations.

This section provides information for troubleshooting for agents. Be sure to consultthe IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshootinginformation.

Table 29. Problems with configuring situations that you solve in the Situation Editor

Problem Solution

Note: To get started with the solutions in this section, perform these steps:1. Launch the Tivoli Enterprise Portal.2. Click Edit > Situation Editor.3. In the tree view, choose the agent whose situation you want to modify.4. Choose the situation in the list. The Situation Editor view is displayed.

The situation for a specific agent isnot visible in the Tivoli EnterprisePortal.

Open the Situation Editor. Access the All managed servers view. If the situationis absent, confirm that application support for Monitoring Agent for UNIX OShas been added to the monitoring server. If not, add application support to theserver, as described in the IBM Tivoli Monitoring Installation and Setup Guide.

The monitoring interval is toolong.

Access the Situation Editor view for the situation that you want to modify.Check the Sampling interval area in the Formula tab. Adjust the time intervalas needed.

The situation did not activate atstartup.

Manually recycle the situation as follows:

1. Right-click the situation and choose Stop Situation.

2. Right-click the situation and choose Start Situation.

Note: You can permanently avoid this problem by placing a check mark in theRun at Startup option of the Situation Editor view for a specific situation.

The situation is not displayed. Click the Action tab and check whether the situation has an automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event or theupdate in the graphical user interface.

An Alert event has not occurredeven though the predicate has beenproperly specified.

Check the logs, reports, and workspaces.

A situation fires on an unexpectedmanaged object.

Confirm that you have distributed and started the situation on the correctmanaged system.


Table 29. Problems with configuring situations that you solve in the Situation Editor (continued)

Problem Solution

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for the situation.

The situation does not fire.

Incorrect predicates are present inthe formula that defines thesituation. For example, themanaged object shows a state thatnormally triggers a monitoringevent, but the situation is not truebecause the wrong attribute isspecified in the formula.

In the Formula tab, analyze predicates as follows:

1. Click the fx icon in the upper-right corner of the Formula area. The Showformula window is displayed.

a. Confirm the following details in the Formula area at the top of thewindow:v The attributes that you intend to monitor are specified in the formula.v The situations that you intend to monitor are specified in the formula.v The logical operators in the formula match your monitoring goal.v The numerical values in the formula match your monitoring goal.

b. (Optional) Click the Show detailed formula check box in the lower leftof the window to see the original names of attributes in the applicationor operating system that you are monitoring.

c. Click OK to dismiss the Show formula window.

2. (Optional) In the Formula area of the Formula tab, temporarily assignnumerical values that will immediately trigger a monitoring event. Thetriggering of the event confirms that other predicates in the formula arevalid.Note: After you complete this test, you must restore the numerical valuesto valid levels so that you do not generate excessive monitoring data basedon your temporary settings.

Table 30. Problems with configuration of situations that you solve in the Workspace area

Problem Solution

Situation events are not displayedin the Events Console view of theworkspace.

Associate the situation with a workspace.Note: The situation does not need to be displayed in the workspace. It issufficient that the situation be associated with any workspace.

You do not have access to asituation.

Note: You must have administrator privileges to perform these steps.

1. Select Edit > Administer Users to access the Administer Users window.

2. In the Users area, select the user whose privileges you want to modify.

3. In the Permissions tab, Applications tab, and Navigator Views tab, selectthe permissions or privileges that correspond to the user's role.

4. Click OK.

A managed system seems to beoffline.

1. Select Physical View and highlight the Enterprise Level of the navigatortree.

2. Select View > Workspace > Managed System Status to see a list ofmanaged systems and their status.

3. If a system is offline, check network connectivity and status of the specificsystem or application.

Table 31. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Serviceswindow

Problem Solution

After an attempt to restart theagents in the Tivoli EnterprisePortal, the agents are still notrunning.

For UNIX, NetWare, or Windows, log on to the applicable system and performthe appropriate queries.


Table 31. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Serviceswindow (continued)

Problem Solution

The Tivoli Enterprise MonitoringServer is not running.

Check the system status and check the appropriate IBM Tivoli Monitoring logs.

The managed objects you createdare firing on incorrect managedsystems.

Check the managed system distribution on both the situation and the managedobject settings sheets.

Take Action command troubleshootingTable 32 lists general problems that might occur with Take Action commands.When each Take Action command runs it generates the log file listed in Table 21 onpage 206. This appendix provides agent-specific troubleshooting information. Seethe IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Table 32. Take Action commands problems and solutions

Problem Solution

Take Action commands might require severalminutes to complete.

Allow several minutes. If you do not see a pop-up messageadvising you of completion, try to run the command manually.If you are unable to perform the Take Action commandmanually, see IBM Tivoli Monitoring Troubleshooting Guide forgeneral information on troubleshooting the Take Actioncommand.

Troubleshooting for UNIXTable 33 lists problems that might occur on the system or application that you aremonitoring. See the IBM Tivoli Monitoring Troubleshooting Guide for generaltroubleshooting information.

Table 33. Paging and memory issues for a system administrator to consider

Problem Solution

Paging space allotted needs to beincreased.

A system needs to have about two times its total memory size. However,paging space depends on the programs that are running. If the site hasmany small programs that run to completion quickly, then only one timesthe total memory size might be required. If the site runs large programsthat run for hours or days at a time, then more paging space is required.

Paging space allocation needs to bemore accurate on a UNIX system.

You can test the allocation of paging space by creating a situation thatmonitors Active Virtual Memory. Active Virtual Memory closely matcheshow much paging space is being used. When the system uses all thepaging space, the operating system terminates processes that ask formore.

To create a situation that monitors active virtual memory:

1. Use the UNIX detail view to obtain the Total Virtual Memory, and tocompute 90% and 95% of the Total Virtual Memory.

2. When the Active Virtual Memory is equal to 90%, of the Total VirtualMemory this is a Yellow light condition. When the Active VirtualMemory is equal to 95% of the Total Virtual Memory this is a Redlight condition.

In response to this test, the local system administrator can increase thepercentages or lower them, as appropriate.


Table 33. Paging and memory issues for a system administrator to consider (continued)

Problem Solution

The Free Memory value seems toosmall.

The System Report, Free Memory column displays how much freememory is available at the current time. This number is normally small.However, you must take action if this number is zero and remains zerofor a long period of time. On AIX systems a small number means that theoperating system is doing an efficient job at managing the memory of thesystem. If this number is very large, the system is not busy and has moreRAM than required.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and follow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to http://www.ibm.com/software/support/isa.

Accessing terminology onlineThe IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:

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

Accessing publications onlineIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Documentation CentralWeb site at http://www.ibm.com/tivoli/documentation.

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File &rarrow; Print window that allows Adobe Reader to printletter-sized pages on your local paper.

Ordering publicationsYou can order many Tivoli publications online at http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968


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


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

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

http://www.ibm.com/tivoli/documentation

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss


In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.2. Select your country from the list and click Go.3. Click About this site in the main panel to see an information page that

includes the telephone number of your local representative.

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation Web site at http://www.ibm.com/software/tivoli/education.

Tivoli user groupsTivoli user groups are independent, user-run membership organizations thatprovide Tivoli users with information to assist them in the implementation ofTivoli Software solutions. Through these groups, members can share informationand learn from the knowledge and experience of other Tivoli users. Tivoli usergroups include the following members and groups:v 23,000+ membersv 144+ groups

Access the link for the Tivoli Users Group at www.tivoli-ug.org.



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

www.tivoli-ug.org

Appendix H. Discovery Library Adapter for the monitoringagent

This chapter contains information about the Discovery Library Adapter (DLA) forthe Monitoring Agent for UNIX.

About the DLAThe Tivoli Management Services DLA discovers resources and relationships andcreates a Discovery Library Book file. The Book follows the Discovery LibraryIdML schema version 2.9.2 and is used to populate the Configuration ManagementDatabase (CMDB) and Tivoli Business System Management products. The TivoliManagement Services DLA discovers UNIX resources. For all UNIX systems thatare active and online at the Tivoli Enterprise Portal Server, information is includedin the discovery book for those resources. The Tivoli Management Services DLAdiscovers active resources. It is run on demand and can be run periodically todiscover resources that were not active during previous discoveries.

The DLA discovers UNIX components.

More information about DLAsThe following sources contain additional information about using the DLAprogram with all monitoring agents:v The IBM Tivoli Monitoring Administrator's Guide contains information about using

the Tivoli Management Services Discovery Library Adapter.v For information about using a DLA with Tivoli Application Dependency

Discovery Manager (TADDM), see the information center athttp://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.1/cmdb_welcome.html

UNIX data model class types represented in CDMThis section contains information about how the various source application dataobjects map to classes in the Common Data Model (CDM) for the MonitoringAgent for UNIX.

The following information is provided for each class where appropriate:

RelationshipsCDM relationships (hierarchical) between currently identified modelobjects

CDM attributes, agent attributes, descriptions, and examplesCDM and agent attributes that are required to create an instance of aresource, descriptions of the attributes, and examples of the attributes

UNIX classThe following information describes the UNIX class.

CDM class namesys.aix.Aix or sys.sun.Solaris or sys.hpux.HpUx


http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.1/cmdb_welcome.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/com.ibm.taddm.doc_7.1/cmdb_welcome.html

Relationships

v installedOnv runsOn

CDM attributes, agent attributes, descriptions, and examples

v CDM attribute: ManagedSystemNameAgent attribute: noneDescription: Managed System Name

v CDM attribute: OSVersionAgent attribute: SYSTEMVERS/UNIXOSDescription: OS Version

v CDM attribute: NameAgent attribute: SYSTEMTYPE/UNIXOSDescription: OS Type

v CDM attribute: FQDNAgent attribute: DNSNAME/UNIXIPADDRDescription: Fully Qualified Domain Name

ComputerSystem classThe following information describes the ComputerSystem class.

CDM class namesys.ComputerSystem



v CDM attribute: NameAgent attribute: noneDescription: Fully Qualified Host Name

v CDM attribute: SignatureAgent attribute: IPADDRESS/UNIXIPADDR andMACADDRESS/UNIXNETDescription: Lowest IP Address ( MAC Address )

v CDM attribute: PrimaryMACAddressAgent attribute: MACADDRESS/UNIXNETDescription: MAC Address of the network interface with the lowestIP Address (alpha order)

v CDM attribute: TypeAgent attribute: noneDescription: "ComputerSystem"

v CDM attribute: FqdnAgent attribute: DNSNAME/UNIXIPADDRDescription: Fully Qualified Domain Name

v CDM attribute: SystemBoardUUIDAgent attribute: UUID/UNIXMACHINDescription: System Board UUID

v CDM attribute: SerialNumberAgent attribute: MACSERIAL/UNIXMACHINDescription: Serial Number

v CDM attribute: ModelAgent attribute: MODEL/UNIXMACHIN


Description: Modelv CDM attribute: Manufacturer

Agent attribute: VENDOR/UNIXMACHINDescription: Manufacturer

v CDM attribute: VMIDAgent attribute: VMID/UNIXMACHINDescription: Partition ID

v CDM attribute: LabelAgent attribute: noneDescription: Fully Qualified Host Name

IpInterface classThe following information describes the IpInterface class.

CDM class namenet.IpInterface

Relationships

v contains

CDM attributes, agent attributes, descriptions, and examplesnone

IpV4Address classThe following information describes the IpV4Address class.

CDM class namenet.IpV4Address

Relationships

v bindsTo


v CDM attribute: DotNotationAgent attribute: IPADDRESS/UNIXIPADDRDescription: IP Address of the network interface

v CDM attribute: LabelDescription: IP Address of the network interface

IpV6Address classThe following information describes the IpV6Address class.

CDM class namenet.IpV6Address

Relationships

v bindsTo


v CDM attribute: StringNotationAgent attribute: IPADDRESS/LNXIPADDRDescription: IP Address of the network interface

v CDM attribute: LabelDescription: IP Address of the network interface

Appendix H. Discovery Library Adapter for the monitoring agent 229

Fqdn classThe following information describes the Fqdn class.

CDM class namenet.Fqdn


v CDM attribute: FqdnAgent attribute: IPADDRESS/LNXIPADDRDescription: Fully Qualified Domain Name for the network interface

TMSAgent classThe following information describes the TMSAgent class.

CDM class nameapp.TMSAgent

Relationships

v installedOnv monitors



v CDM attribute: ManagedObjectNameDescription: "p@" Managed System Name

v CDM attribute: SoftwareVersionDescription: OS Agent ITM version

v CDM attribute: ProductCodeDescription: OS Agent Product Code (UX)

v CDM attribute: AffinityDescription: OS Agent affinity

v CDM attribute: LabelDescription: Managed System Name "- UNIX OS"


Appendix I. Tivoli Common Reporting for the monitoringagent

This chapter contains descriptions of the reports that are currently available withthe Monitoring Agents for Windows OS, Linux OS, and UNIX OS.

See the following additional information about using reports with this monitoringagent:v The IBM Tivoli Monitoring Administrator's Guide, V6.2.2 or later contains

information about prerequisites and importing and running the reports.

Complete documentation for the Tivoli Common Reporting tool is located athttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/tcr_welcome.html

You must have the following prerequisite actions completed to use this function:v IBM Tivoli Monitoring v6.2.2 must be installed with the OS agents up and

running.v The Summarization and Pruning agent must be started with or without shifts

enabled.v Historical collection must be turned on and collection started.v Summarized tables and views must be created and populated in the Tivoli Data

Warehouse.

The following paragraphs describe the reports. In particular, they contain therequired views for each one. If these views are not present, the report might notwork. To ensure that the required views are present, run the following queryagainst the Tivoli Data Warehouse:DB2: select distinct "VIEWNAME" from SYSCAT.VIEWS where"VIEWNAME" like '%V'Oracle: select distinct "VIEW_NAME" from USER_VIEWS where"VIEW_NAME" like '%V'MS SQL Server: select distinct "NAME" from SYS.VIEWS where"NAME" like '%V'

The following databases are supported: DB2, Oracle, and SQL Server.

The following reports are available:v Utilization Details for Single Resource

The report shows CPU, memory, disk, network utilization and top 10 CPUutilizing processes for a system during the selected time period in a line chart.Statistical process information is shown in all line charts (including average,upper and lower control limits). A linear trending feature is also provided and itis based on the selected forecast period.

v Utilization Details for Multiple ResourcesThis report shows CPU, memory, disk and network utilization for multiplesystems during the selected time period in an overlaid line chart. A lineartrending feature is also provided, and it is based on the selected forecast period.

v Utilization Heat Chart for Single Resource


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/welcome.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/welcome.htm

This report helps identify patterns of utilization of a particular system over aperiod of time. The first column shows dates during the selected time periodand the other columns represent hours during the day. The chart can be used forshowing a heat chart for CPU, Memory and Disk or all three in the same report.The dates have hyperlinks that you can use to drill down to Utilization Detailsfor Single Resource. A linear trending feature is also provided, which is based onthe selected forecast period.

v Top Resources UtilizationThis report shows top resources by CPU, Disk and Memory utilization. Thestacked bars show average CPU used and free (in percent) for each system overthe selected report period. If the number of systems is less than 20, then a bar isshown in each row. For example, there are 20 rows in the table with charts foreach system. If the number of systems is more than 20, then there is a bar charton top with the top 20 systems, and the rest of the data is in the table. This isdone to eliminate overcrowding of the bars in the chart.

v Enterprise Resources ListThis report lists all the Windows, Linux and UNIX resources in the environment.By clicking on a resource name, you can drill through to see the utilizationdetails for that resource over a period of time.

These reports use the following attribute groups:v Windows agent:

– Logical_Disk– Memory– Process– Server– System

v Linux agent:

– CPU– Disk– Network– Process– VM_Stats

v UNIX agent:

– Disk– Network– Process– System– Memory

The remaining sections in this chapter contain descriptions of the reports. For eachreport, the following information is included:v Namev Descriptionv Purposev Parametersv Tables or views usedv Outputv Usage


One of the parameters, summarization type, has the following maximum forecastperiods:v Hourly: 60 hours in the futurev Daily: 60 days in the futurev Weekly: 1 year in the futurev Monthly: 5 years in the futurev Quarterly: no limitv Yearly: no limit

Utilization Details for Single Resource report

Name Utilization Details for Single Resource

Description The report shows resources utilization for a selected server: CPU utilization, Disk utilization,Memory utilization, Network utilization. Each metric is shown on a separate chart where datafor the server is overlaid. For disk utilization, only this average value for all logical disks isshown. For network utilization, total value for all network interfaces is shown.

The time frame for report data can be determined in the standard way by using the Durationand Include shift periods parameters.

The server can be selected from a list of available servers by using the OS Type and Serversparameters.

The forecasts can also be shown for the given period. If set, all the charts show data that endsat that date, and missing samples are determined based on linear trend computed overhistorical data.

The report also shows the top 10 CPU utilizing processes for the selected server.

Purpose Helps identify system performance of a system or server over a period of time. Shows dailypatterns for utilization.

Appendix I. Tivoli Common Reporting for the monitoring agent 233

Parameters OS TypeDetermines the type of agent to work on, and is selected from the drop-down list with thefollowing items:v Linuxv UNIXv Windows

Date RangeDetermines the range of data shown on a report. Provide the value as two border dates(from or to) or selected from the drop-down list with the following options:v Allv Date Range (below)v Todayv Yesterdayv Last 7 daysv Last 30 daysv Last 90 daysv Last 355 daysv Current weekv Current monthv Current Year to Datev Last weekv Last monthv Last Year

Summarization TypeDetermined by Summarization and Pruning and is selected from the drop-down list withthe following items:v Daily (Default)v Hourlyv Weeklyv Monthlyv Quarterlyv Yearly

ServersThe server or system names for the selected OS Type are displayed in a drop-down listsorted alphabetically. You can see up to 30 system names. For more than 30 names, typethe name to see the filtered list.

Include shift periodsA drop-down list that you can use to select the shift periods to be included. ThePeak/Off-Peak Hours period terms refer to definitions contained in Summarization andPruning. The list contains the following options:v All Shifts (Default)v Peak Hours Onlyv Off - Peak Hours Only

Include vacation periodsA drop-down list that you can use to include or exclude vacation days. The Vacationperiod terms refer to definitions contained in Summarization and Pruning. The listcontains the following options:v All Days (Default)v Work daysv Vacation days

Forecast PeriodSpecifies the forecast period.

Show DataSpecifies if the chart data source should be displayed in a table or not.


Tables or viewsused

CPU Utilization:

Windows agent: NT_System_HV, NT_System_DV, NT_System_WV, NT_System_MV,NT_System_QV, NT_System_YV

Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV, KLZ_CPU_QV,KLZ_CPU_YV

UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV, System_YV

Disk Utilization:

Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV, NT_Logical_Disk_WV,NT_Logical_Disk_MV, NT_Logical_Disk_QV, NT_Logical_Disk_YV

Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV, KLZ_Disk_QV,KLZ_Disk_YVV

UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV

Memory Utilization:

Windows agent: NT_Memory_64_HV, NT_Memory_64_DV, NT_Memory_64_WV,NT_Memory_64_MV, NT_Memory_64_QV, NT_Memory_64_YV

Linux agent: KLZ_VM_Stats_HV, KLZ_VM_Stats_DV, KLZ_VM_Stats_WV, KLZ_VM_Stats_MV,KLZ_VM_Stats_QV, KLZ_VM_Stats_YV

UNIX agent: Unix_Memory_HV, Unix_Memory_DV, Unix_Memory_WV, Unix_Memory_MV,Unix_Memory_QV, Unix_Memory_YV

Network Utilization:

Windows agent: NT_Server_HV, NT_Server_DV, NT_Server_WV, NT_Server_MV,NT_Server_QV, NT_Server_YV

Linux agent: KLZ_Network_HV, KLZ_Network_DV, KLZ_Network_WV, KLZ_Network_MV,KLZ_Network_QV, KLZ_Network_YV

UNIX agent: Network_HV, NetworkDV, Network_WV, Network_MV,Network_QV,Network_YV

Processes:

Windows agent: NT_Process_64_HV, NT_Process_64_DV, NT_Process_64_WV,NT_Process_64_MV, NT_Process_64_QV, NT_Process_64_YV

Linux agent: KLZ_Process_HV, KLZ_Process_DV, KLZ_Process_WV, KLZ_Process_MV,KLZ_Process_QV, KLZ_Process_YV

UNIX agent: Process_HV, Process_DV, Process_WV, Process_MV, Process_QV, Process_YV


Output A heat chart. The first column shows dates during the selected time period and the othercolumns represent 24 hours during the day starting with 0. The last column shows averagevalue for that day. The report can be generated for CPU, Disk or Memory Utilization. Thetimestamp is a hyperlink that you can use to drill through to a details report for CPU, disk,memory, network usage, top 10 processes for that particular system on the selected day. Thethresholds for the colors can be specified in the parameters. When hovering your cursor over anicon or bar, the value shows up in a tooltip. The heat chart can be represented in icons or barsby clicking on the Bar or Icon hyperlinks.

Usage The IT administrator or manager responsible for meeting service levels based on serverperformance needs to receive periodic reports showing which servers are at risk of violatingService Level Agreements (SLAs). Reports indicate which systems are overutilized orunderutilized relative to a collection of systems. The report can be run hourly, daily, weekly,monthly, quarterly, and yearly.

The following table includes information about the historical collectionconfiguration:

TypeAttributeGroup Table Summarization

H D W M Q Y

Linux Linux CPU KLZ_CPU X X X X X X

Linux Disk KLZ_Disk X X X X X X

Linux VMStats

KLZ_VM_Stats X X X X X X

LinuxNetwork

KLZ_Network X X X X X X

LinuxProcess

KLZ_Process X X X X X X

UNIX System System X X X X X X

Disk Disk X X X X X X

UNIXMemory

UNIX_Memory X X X X X X

Network Network X X X X X X

Process Process X X X X X X

Windows System NT_System X X X X X X

LogicalDisk

NT_Logical_Disk X X X X X X

Memory NT_Memory_64 X X X X X X

Server NT_Server X X X X X X

Process NT_Process_64 X X X X X X


Utilization Details for Multiple Resources report

Name Utilization Details for Multiple Resources

Description The report shows resources utilization for selected servers: CPU utilization, Diskutilization, Memory utilization, Network utilization. Each metric is shown on aseparate line chart where data for all servers is overlaid. For disk utilization, onlyaverage value for all logical disks is shown. For network utilization, total value forall network interfaces is shown.

The time frame for report data can be determined in standard way by using theDuration and Include shift periods parameters.

The servers can be selected from a list of available servers using the OS Type andServers parameters.

The forecasts can also be shown for the given period. If set, all the charts show datathat ends at that date, and missing samples are determined based on linear trendcomputed over historical data.

Purpose Helps identify and compare system performance problems related to over-utilizationof key system resources. Helps identify which systems are performing poorly due tolow physical memory, causing excessive paging, performing poorly due to CPUintensive tasks, or performing poorly due to other factors such as poor loadbalancing of applications across available systems.


Parameters OS TypeDetermines the type of agent to work on and can be selected from thedrop-down list with the following items:v Linuxv UNIXv Windows

Date RangeDetermines the range of data shown on a report. Provide the value as twoborder dates (from and to) or selected from the drop-down list with thefollowing options:v Allv Date Range (below)v Todayv Yesterdayv Last 7 daysv Last 30 daysv Last 90 daysv Last 355 daysv Current weekv Current monthv Current Year to Datev Last weekv Last monthv Last Year

Summarization TypeDetermined by Summarization and Pruning and should be selected from thedrop-down list with the following items:v Daily (Default)v Hourlyv Weeklyv Monthlyv Quarterlyv Yearly

ServersThe server or system names for the selected OS Type are displayed in adrop-down list sorted alphabetically. You are able to see up to 30 systemnames. For more than 30 names, type the name to filter the list.

Include shift periodsA drop-down list that you can use to select the shift periods to be included.The Peak/Off-Peak Hours period terms refer to definitions contained inSummarization and Pruning. The list contains the following options:v All Shifts (Default)v Peak Hours Onlyv Off - Peak Hours Only

Include vacation periodsA drop-down list that you can use to include or exclude vacation days. TheVacation period terms refer to definitions contained in Summarization andPruning. The list contains the following options:v All Days (Default)v Work daysv Vacation days

Forecast PeriodSpecifies the forecast period.

Show DataSpecifies if the chart data source should be displayed in a table or not.


Tables or views used CPU Utilization:

Windows agent: NT_System_HV, NT_System_DV, NT_System_WV, NT_System_MV,NT_System_QV, NT_System_YV

Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV,KLZ_CPU_QV, KLZ_CPU_YV

UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV,System_YV

Disk Utilization:

Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV, NT_Logical_Disk_WV,NT_Logical_Disk_MV, NT_Logical_Disk_QV, NT_Logical_Disk_YV

Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV,KLZ_Disk_QV, KLZ_Disk_YV

UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV

Memory Utilization:

Windows agent: NT_Memory_64_HV, NT_Memory_64_DV, NT_Memory_64_WV,NT_Memory_64_MV, NT_Memory_64_QV, NT_Memory_64_YV

Linux agent: KLZ_VM_Stats_HV, KLZ_VM_Stats_DV, KLZ_VM_Stats_WV,KLZ_VM_Stats_MV, KLZ_VM_Stats_QV, KLZ_VM_Stats_YV

UNIX agent: Unix_Memory_HV, Unix_Memory_DV, Unix_Memory_WV,Unix_Memory_MV, Unix_Memory_QV, Unix_Memory_YV

Network Utilization:

Windows agent: NT_Server_HV, NT_Server_DV, NT_Server_WV, NT_Server_MV,NT_Server_QV, NT_Server_YV

Linux agent: KLZ_Network_HV, KLZ_Network_DV, KLZ_Network_WV,KLZ_Network_MV, KLZ_Network_QV, KLZ_Network_YV

UNIX agent: Network_HV, NetworkDV, Network_WV, Network_MV,Network_QV,Network_YV

Output Three overlaid line charts for selected systems, with each line representing thedifferent systems. If the selected summarization is not enabled for collection, itdefaults to daily or hourly summarization based on the number of days.

Usage The IT administrator or manager responsible for meeting service levels based onserver performance needs to receive periodic reports showing which servers are atrisk of violating Service Level Agreements (SLAs). Reports indicate which systemsare overutilized or underutilized relative to a collection of systems. The report can berun hourly, daily, weekly, monthly, quarterly, and yearly.




H D W M Q Y



Linux VMStats


LinuxNetwork

KLZ_Network X X X X X X



UNIXMemory


Network Network X X X X X X


Logical Disk NT_Logical_Disk X X X X X X


Server NT_Server X X X X X X

Utilization Heat Chart for Single Resource report

Name Utilization Heat Chart for Single Resource

Description The report shows resources utilization for a selected server: CPU utilization, Diskutilization, Memory utilization, Network utilization. Each metric is shown on aseparate heat chart where data for all servers is overlaid. For disk utilization, onlyaverage value for all logical disks is shown. For network utilization, total value forall network interfaces is shown.

The time frame for report data can be determined in standard way by using theDuration and Include shift periods parameters.

The servers can be selected from a list of available servers using the OS Type andServers parameters.

Purpose Helps identify system performance of a system or server over a period of time.Shows daily patterns for utilization.


Parameters OS TypeDetermines the type of agent to work on and should be selected from thedrop-down list with the following items:v Linuxv UNIXv Windows



ServersThe server or system names for the selected OS Type is displayed in adrop-down list sorted alphabetically. You can see up to 30 system names. Formore than 30 names, type the name to filter the list.



Upper Limit for Good StatusSpecifies the upper limit for good status.

Upper Limit for Fair StatusSpecifies the upper limit for fair status.

Upper Limit for Warning StatusSpecifies the upper limit for warning status.

Upper Limit for Bad Status and Lower Limit for Critical StatusSpecifies the upper limit for bad status and the lower limit for critical status.


Tables or views used CPU Utilization:

Windows agent: NT_System_HV

Linux agent: KLZ_CPU_HV

UNIX agent: System_HV

Disk Utilization:

Windows agent: NT_Logical_Disk_HV

Linux agent: KLZ_Disk_HV

UNIX agent: Disk_HV

Memory Utilization:

Windows agent: NT_Memory_64_HV

Linux agent: KLZ_VM_Stats_HV

UNIX agent: Unix_Memory_HV

Output A heat chart. The first column shows dates during the selected time period and theother columns represent 24 hours during the day starting with 0. The last columnshows average value for that day. The report can be generated for CPU, Disk orMemory Utilization. The timestamp is a hyperlink that you can use to drill throughto a details report for CPU, disk, memory, network usage, top 10 processes for thatparticular system on the selected day. The thresholds for the colors can be specifiedin the parameters. When hovering your cursor over an icon or bar, the value showsup in a tooltip. The heat chart can be represented in icons or bars by clicking on theBar or Icon hyperlinks.




H D W M Q Y

Linux LinuxCPU

KLZ_CPU X

LinuxDisk

KLZ_Disk X

Linux VMStats

KLZ_VM_Stats X

UNIX System System X

Disk Disk X

UNIXMemory

UNIX_Memory X



Windows System NT_System X

LogicalDisk

NT_Logical_Disk X

Memory NT_Memory_64 X

Top Resources Utilization report

Name Top Resources Utilization

Description The report shows top resources by CPU, Disk and Memory utilization. The stackedbars show average CPU used and free (in percent) for each system over the selectedreport period. If the number of systems is less than 20, then a bar is shown in eachrow. For example, there are 20 rows in the table with charts for each system. If thenumber of systems is more than 20, then a bar chart is on top with the top 20systems and the rest of the data is in the table. This is done to eliminateover-crowding of the bars in the chart.

Purpose CPU utilization: Helps identify which systems are most overloaded and which havethe least load based on the percentage of CPU utilization. Identifies which systemsare over-utilized and which are under-utilized.

Disk utilization: Helps identify which systems are experiencing heavy disk activity.Additionally, shows systems running low on disk space. This allows for planning theaddition of hard drives or balancing of applications or data across available harddisk resources.

Memory utilization: Helps identify growth in memory utilization which can lead toapplication and server outages. This allows for planning the increasing of pagingspace or the addition of physical memory.


Parameters OS TypeDetermines the type of agent to work on and should be selected from thedrop-down list with the following items:v Linuxv UNIXv Windows



ServersThe server or system names for the selected OS Type is displayed in adrop-down list sorted alphabetically. You can see up to 30 system names. Formore than 30 names, type the name to filter the list.




Tables or views used CPU utilization

v Windows agent: NT_System_HV, NT_System_DV, NT_System_WV,NT_System_MV, NT_System_QV, NT_System_YV

v Linux agent: KLZ_CPU_HV, KLZ_CPU_DV, KLZ_CPU_WV, KLZ_CPU_MV,KLZ_CPU_QV, KLZ_CPU_YV

v UNIX agent: System_HV, System_DV, System_WV, System_MV, System_QV,System_YV

Disk utilization

v Windows agent: NT_Logical_Disk_HV, NT_Logical_Disk_DV,NT_Logical_Disk_WV, NT_Logical_Disk_MV, NT_Logical_Disk_QV,NT_Logical_Disk_YV

v Linux agent: KLZ_Disk_HV, KLZ_Disk_DV, KLZ_Disk_WV, KLZ_Disk_MV,KLZ_Disk_QV, KLZ_Disk_YV

v UNIX agent: Disk_HV, Disk_DV, Disk_WV, Disk_MV, Disk_QV, Disk_YV

Memory utilization

v Windows agent: NT_Memory_64_HV, NT_Memory_64_DV, NT_Memory_64_WV,NT_Memory_64_MV, NT_Memory_64_QV, NT_Memory_64_YV

v Linux agent: KLZ_VM_Stats_HV, KLZ_VM_Stats_DV, KLZ_VM_Stats_WV,KLZ_VM_Stats_MV, KLZ_VM_Stats_QV, KLZ_VM_Stats_YV

v UNIX agent: Unix_Memory_HV, Unix_Memory_DV, Unix_Memory_WV,Unix_Memory_MV, Unix_Memory_QV, Unix_Memory_YV

Output A table is displayed with each row displaying a stacked bar representing one of thefollowing for each system over the selected report period.

v average CPU used and free (in percent)

v average Disk space used and free (in GB and in percent)

v average Memory used and free (in percent)

If the number of systems is less than 20, then a bar is shown in each row. Forexample, there are 20 rows in the table with charts for each system. If the number ofsystems is more than 20, then a bar chart is on top with the top 20 systems and therest of the data is in the table. This is done to eliminate over-crowding of the bars inthe chart. The charts are interactive. By clicking on a bar you can drill through to adetails report showing CPU, Disk, or Memory Utilization for the selected resourceover time in a line chart. The same hyperlink is provided in the Server Name columnin the table. If no data is available for the selected parameters, an appropriatemessage is displayed. The table columns can be sorted dynamically.

For CPU Utilization: By clicking on the Avg % CPU Used column heading the table issorted with the servers using the most CPU on top, and on clicking on the Avg %CPU Free column heading the table is sorted with the servers with the least CPUused on top, thereby having the capability of showing top or bottom resources byCPU utilization in the same report.

For Disk Utilization: By clicking the Avg % Disk Used or Avg 30 Disk Space Used inGB column headings the table is sorted with the servers using the most Disk on top,and on clicking on the Avg % Disk Free or Avg Disk Space Free in GB columnheading the table is sorted with the servers with the least Disk used on top, therebyhaving the capability of showing top or bottom resources by Disk utilization in thesame report.

For Memory Utilization: By clicking the Avg % Memory Used column heading thetable is sorted with the servers using the most Memory on top, and on clicking onthe Avg % Memory Free column heading the table is sorted with the servers with theleast memory used on top, thereby having the capability of showing top or bottomresources by memory utilization in the same report.





H D W M Q Y



Linux VMStats




UNIXMemory



LogicalDisk

NT_Logical_Disk X X X X X X


Enterprise Resource List report

Name Enterprise Resource List

Description This report lists all the Windows, Linux and UNIX resources in the environment. Onclicking on a resource name you can drill through to see the utilization details forthat resource over a period of time.

Purpose This report you can use to see the list of OS Agents in the enterprise during aparticular time.

Parameters None

Tables or views used Windows agent: NT_System

Linux agent: KLZ_CPU

UNIX agent: System

Output Three tables showing resource names for Windows, Linux and UNIX. The footer ofthe tables contains the total number of resources for that OS type. Each resourcename is a hyperlink and you can use to drill down to the ITM: Resource Utilizationfor Single Server Overlaid Comparison report.



Appendix J. Documentation library

This appendix contains information about the publications related to IBM TivoliMonitoring and to the commonly shared components of Tivoli ManagementServices. These publications are listed in the following categories:v IBM Tivoli Monitoring libraryv Related publications

See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide,SC23-8816, for information about accessing and using the publications. You canfind the Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON XEInformation Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.To open the Documentation Guide in the information center, select Using thepublications in the Contents pane.

To find a list of new and changed publications, click What's new on the Welcomepage of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. Tofind publications from the previous version of a product, click Previous versionsunder the name of the product in the Contents pane.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring andabout the commonly shared components of Tivoli Management Services:v Quick Start Guide, GI11-8058

Introduces the components of IBM Tivoli Monitoring.v Installation and Setup Guide, GC32-9407

Provides instructions for installing and configuring IBM Tivoli Monitoringcomponents on Windows, Linux, and UNIX systems.

v Program Directory for IBM Tivoli Management Services on z/OS, GI11-4105Gives instructions for the SMP/E installation of the Tivoli Management Servicescomponents on z/OS.

v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC32-9463Gives detailed instructions for using the Configuration Tool to configure TivoliEnterprise Monitoring Server on z/OS systems. Includes scenarios for usingbatch mode to replicate monitoring environments across the z/OS enterprise.Also provides instructions for setting up security and for adding applicationsupport to a Tivoli Enterprise Monitoring Server on z/OS.

v Administrator's Guide, SC32-9408Describes the support tasks and functions required for the Tivoli EnterprisePortal Server and clients, including Tivoli Enterprise Portal user administration.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/

v High-Availability Guide for Distributed Systems, SC23-9768Gives instructions for several methods of ensuring the availability of the IBMTivoli Monitoring components.

v Tivoli Enterprise Portal online helpProvides context-sensitive reference information about all features andcustomization options of the Tivoli Enterprise Portal. Also gives instructions forusing and administering the Tivoli Enterprise Portal.

v Tivoli Enterprise Portal User's Guide, SC32-9409Complements the Tivoli Enterprise Portal online help. The guide provideshands-on lessons and detailed instructions for all Tivoli Enterprise Portalfeatures.

v Command Reference, SC32-6045Provides detailed syntax and parameter information, as well as examples, for thecommands you can use in IBM Tivoli Monitoring.

v Troubleshooting Guide, GC32-9458Provides information to help you troubleshoot problems with the software.

v Messages, SC23-7969Lists and explains messages generated by all IBM Tivoli Monitoring componentsand by z/OS-based Tivoli Management Services components (such as TivoliEnterprise Monitoring Server on z/OS and TMS:Engine).

v IBM Tivoli Universal Agent User's Guide, SC32-9459Introduces you to the IBM Tivoli Universal Agent, an agent of IBM TivoliMonitoring. The IBM Tivoli Universal Agent enables you to use the monitoringand automation capabilities of IBM Tivoli Monitoring to monitor any type ofdata you collect.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide,SC32-9461Explains the procedures for implementing the IBM Tivoli Universal Agent APIsand provides descriptions, syntax, and return status codes for the API calls andcommand-line interface commands.

v Agent Builder User's Guide, SC32-1921Explains how to use the Agent Builder for creating monitoring agents and theirinstallation packages, and for adding functions to existing agents.

Documentation for the base agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of basemonitoring agents as part of the product. If you purchased a monitoring agentproduct (for example, an OMEGAMON XE product) that includes the commonlyshared components of Tivoli Management Services, you did not receive the baseagents.

The following publications provide information about using the base agents.v Operating system agents:

– Windows OS Agent User's Guide, SC32-9445– UNIX OS Agent User's Guide, SC32-9446– Linux OS Agent User's Guide, SC32-9447– i5/OS Agent User's Guide, SC32-9448– UNIX Log Agent User's Guide, SC32-9471


v Agentless operating system monitors:– Agentless Monitoring for Windows Operating Systems User's Guide, SC23-9765– Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761– Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763– Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764– Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762

v Warehouse agents:– Warehouse Summarization and Pruning Agent User's Guide, SC23-9767– Warehouse Proxy Agent User's Guide, SC23-9766

v System P agents:– AIX Premium Agent User's Guide, SA23-2237– CEC Base Agent User's Guide, SC23-5239– HMC Base Agent User's Guide, SA23-2239– VIOS Premium Agent User's Guide, SA23-2238

v Other base agents:– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide,

SC32-9490

Related publicationsYou can find useful information about related products in the IBM TivoliMonitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

Other sources of documentationYou can also obtain technical documentation about IBM Tivoli Monitoring andrelated products from the following sources:v IBM Tivoli Open Process Automation Library (OPAL)

http://www.ibm.com/software/tivoli/opalOPAL is an online catalog that contains integration documentation and otherdownloadable product extensions.

v Redbookshttp://www.redbooks.ibm.com/IBM Redbooks® and Redpapers include information about products fromplatform and solution perspectives.

v TechnotesTechnotes provide the latest information about known product limitations andworkarounds. You can find Technotes through the IBM Software Support Website at http://www.ibm.com/software/support.

v Tivoli wikis on the IBM developerWorks® Web siteTivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the home for interactive wikis that offer best practices andscenarios for using Tivoli products. The wikis contain white papers contributedby IBM employees, and content created by customers and business partners.

Appendix J. Documentation library 249



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

http://www.redbooks.ibm.com/


http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki at

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home provides information about IBM Tivoli Monitoring and relateddistributed products, including IBM Tivoli Composite ApplicationManagement products.

– Tivoli System z® Monitoring and Application Management Wiki athttp://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about the OMEGAMON XE products, NetView®

for z/OS, Tivoli Monitoring Agent for z/TPF, and other System z monitoringand application management products.


http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Appendix K. Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in this product enable users to do the following:v Use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the followingfeatures to aid accessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Navigating the interface using the keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. Refer to the documentation provided byyour operating system for more information.

Magnifying what is displayed on the screenYou can enlarge information on the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. Refer to the documentation provided by youroperating system for more information.



Notices

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

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

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. 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 applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Java™ and all Java-based trademarks and logos are trademarks orregistered trademarks of Sun Microsystems, Inc. in the United States,other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT®, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 255


Index

Aaccessibility 251actions

See Take Action commandsagent

trace logs 205troubleshooting 214

agent installation problems 210AMS Recycle Agent Instance action 118AMS Reset Agent Daily Restart Count action 118AMS Start Agent action 119AMS Start Agent Instance action 119AMS Start Management action 120AMS Stop Agent action 120AMS Stop Management action 121attribute

cross-reference 136multiple-instance definition 135single-instance definition 135

attribute groupsDisk Information

UNIXDISK historical table 174Disk Performance

UNIXDPERF historical table 174File Information

UNIXFILE historical table 175more information 31Network

UNIXNET historical table 175NFS and RPC Statistics

UNIXNFS historical table 176overview 31Process

UNIXPS historical table 178SMP CPU

UNIXCPU historical table 173System

UNIXOS historical table 179User

UNIXUSER historical table 182attributes

more information 31overview 31

Bbooks

see publications 225built-in troubleshooting features 203

Ccalculate historical data disk space 106capacity planning for historical data 106cluster environment 11code, product 2commands, Take Action 117components 2

Ddata

trace logs 204data collection 183data provider

See agentdatabase agent installation problems 210developerWorks Web site 249disk capacity planning for historical data 106Disk Information attribute group

UNIXDISK historical table 174Disk Performance attribute group

UNIXDPERF historical table 174disk space requirements 5documentation

See publications

Eeducation

see Tivoli technical training 226environment

features 1event

mapping 143

Ffeatures, Monitoring Agent for UNIX OS 1File Information attribute group

UNIXFILE historical table 175files

agent trace 205installation trace 205other trace log 206trace logs 204

Ggathering support information 203

Hhistorical data

calculate disk space 106disk capacity planning 106

historical reportsattributes 136column header 136cross reference 136

historical tablesUNIXCPU 173UNIXDISK 174UNIXDPERF 174UNIXFILE 175UNIXNET 175UNIXNFS 176UNIXOS 179UNIXPS 178


historical tables (continued)UNIXUSER 182

IIBM Software Support

See supportIBM Support Assistant 225IBM Tivoli Enterprise Console

event mapping 143optional product 3

IBM Tivoli Monitoring for UNIXbenefits of 1definition of 1types of information collected by 1

information, additionalattributes 31policies 123situations 110Take Action commands 117workspaces 13

installationlog file 205problems 210

installation requirements 5interface, user 3

troubleshooting for Tivoli Enterprise Portal 218ISA 225

Llibraries

IBM Tivoli Monitoring 247limited user permissions, upgrading your warehouse

with 126logging

agent trace logs 205, 206built-in features 203installation log files 205location and configuration of logs 204trace log files 204

Mmanuals

see publications 225memory requirements 5messages

built-in features 203Monitoring Agent for UNIX OS

components 2features 1

Monitoring Agent for UNIX OS installation problems 210multiple-instance attributes

definition 135

NNetwork attribute group

UNIXNET historical table 175NFS and RPC Statistics attribute group

UNIXNFS historical table 176non-administrator user 8non-root user 8

Oonline publications

accessing 225OPAL documentation 249operating systems 5ordering publications 225other requirements 6

Ppath names, for trace logs 204permissions, upgrading your warehouse with limited

user 126policies

list of all 123more information 123overview 123predefined 123UNIX_CPU_Busy 123UNIX_Disk_Space_Full 124UNIX_Virtual_Memory_High 124

problems and workarounds 209problems with monitoring UNIX 224Process attribute group

UNIXPS historical table 178product code 2product-provided situations

UNIX_System_Busy_Warning 140publications

accessing online 225developerWorks Web site 249OPAL 249ordering 225Redbooks 249related 249Technotes 249types 247wikis 249

purposestroubleshooting 203

Qqueries, using attributes 31

RRedbooks 249remote deployment

troubleshooting 219requirements

disk space 5memory 5operating system 5other 6

requirements, installation 5

SSample_kill_Process Take Action command 121security 7single-instance attributes

definition 135situations

general troubleshooting 222


situations (continued)list of all 110more information 110overview 109predefined 110specific troubleshooting 220UMX_AMS_Alert_Critical 111UNIX_Active_Virtual_Memory 114, 137UNIX_CMD_Disk_Inodes_Critical 111, 137UNIX_CMD_Disk_Inodes_Critical_2 112UNIX_CMD_Disk_Space_Warning 112, 137UNIX_CMD_Process_Critical 113, 137UNIX_CMD_Runaway_Process 114, 138UNIX_CPU_Busy_Critical 115UNIX_CPU_Busy_Warning 115, 138UNIX_CPU_Critical 114, 138UNIX_CPU_Warning 114, 138UNIX_CPU-Busy_Critical 138UNIX_Disk_Availability 111, 138UNIX_Filemount_Critical 112, 138UNIX_HD_Config_Critical 112, 138, 139UNIX_HD_Config_Critical_2 112UNIX_HD_Excessive_IO_Wait 115, 139UNIX_Network_Collsns_Critical 113, 139UNIX_Network_Collsns_Warning 113, 139UNIX_Network_Errors 113, 139UNIX_Network_Interface_Busy 113, 139UNIX_Network_Interface_Idle 113, 139UNIX_NFS_RPC_Rejects 113, 139UNIX_Process Memory_Warning 139UNIX_Process_Memory_Critical 114, 139UNIX_Process_Memory_Leak 114UNIX_Process_Memory_Warning 114UNIX_Process_MISSING_inetd 114UNIX_scratch_tmp_Disk_Full 112UNIX_System_Busy_Critical 115, 140UNIX_System_Busy_Warning 115UNIX_System_Capacity_Critical 115, 140UNIX_System_Paging_Critical 115, 140UNIX_System_Virtual_Memory_Warning 115, 140UNIX_User_CPU_Critical 115, 140UNIX_User_File_Exists 112, 141

situations, using attributes 31SMP CPU attribute group

UNIXCPU historical table 173Software Support 225support

gathering information for 203support assistant 225System attribute group

UNIXOS historical table 179

TTake Action commands

AMS Recycle Agent Instance 118AMS Reset Agent Daily Restart Count 118AMS Start Agent 119AMS Start Agent Instance 119AMS Start Management 120AMS Stop Agent 120AMS Stop Management 121more information 117overview 117Sample_kill_Process 121troubleshooting 224

target applicationproblems 224

Technotes 249Terminal 182Tivoli Data Warehouse 2Tivoli Enterprise Console

See IBM Tivoli Enterprise ConsoleTivoli Enterprise Monitoring Server 2Tivoli Enterprise Portal

component 2troubleshooting 218

Tivoli Information Center 225Tivoli technical training 226Tivoli user groups 226trace logs 204

directories 204training, Tivoli technical 226transport command 224troubleshooting 203, 209

agents 214built-in features 203installation 210installation logs 205remote deployment 219situations 220, 222Take Action commands 224Tivoli Enterprise Portal 218uninstallation 210uninstallation logs 205workspaces 219

UUMX_AMS_Alert_Critical situation 111uninstallation

log file 205problems 210

UNIX problems 224UNIX_Active_Virtual_Memory situation 114UNIX_CMD_Disk_Inodes_Critical situation 111UNIX_CMD_Disk_Inodes_Critical_2 situation 112UNIX_CMD_Disk_Space_Warning situation 112UNIX_CMD_Process_Critical situation 113UNIX_CMD_Runaway_Process situation 114UNIX_CPU_Busy policy 123UNIX_CPU_Busy_Critical 138UNIX_CPU_Busy_Critical situation 115UNIX_CPU_Busy_Warning 138UNIX_CPU_Busy_Warning situation 115UNIX_CPU_Critical situation 114UNIX_CPU_Warning situation 114UNIX_Disk_Availability situation 111UNIX_Disk_Space_Full policy 124UNIX_Filemount_Critical situation 112UNIX_HD_Config_Critical situation 112UNIX_HD_Config_Critical_2 situation 112UNIX_HD_Excessive_IO_Wait situation 115UNIX_Network_Collsns_Critical situation 113UNIX_Network_Collsns_Warning situation 113UNIX_Network_Errors situation 113UNIX_Network_Interface_Busy situation 113UNIX_Network_Interface_Idle situation 113UNIX_NFS_RPC_Rejects 139UNIX_NFS_RPC_Rejects situation 113UNIX_Process Memory_Warning 139UNIX_Process_Memory_Critical 139UNIX_Process_Memory_Critical situation 114

Index 259

UNIX_Process_Memory_Leak situation 114UNIX_Process_Memory_Warning situation 114UNIX_Process_MISSING_inetd situation 114UNIX_scratch_tmp_Disk_Full situation 112UNIX_System_Busy_Critical situation 115UNIX_System_Busy_Warning situation 115UNIX_System_Capacity_Critical situation 115UNIX_System_Paging_Critical 140UNIX_System_Paging_Critical situation 115UNIX_System_Virtual_Memory_Warning 140UNIX_System_Virtual_Memory_Warning situation 115UNIX_User_CPU_Critical situation 115UNIX_User_File_Exists situation 112UNIX_Virtual_Memory_High policy 124UNIXCPU historical table 173UNIXDISK historical table 174UNIXDPERF historical table 174UNIXFILE historical table 175UNIXNET historical table 175UNIXNFS historical table 176UNIXOS historical table 179UNIXPS historical table 178UNIXUSER historical table 182upgrading for warehouse summarization 125upgrading your warehouse with limited user

permissions 126User attribute group

UNIXUSER historical table 182user groups, Tivoli 226user interfaces options 3user permissions, upgrading your warehouse with

limited 126

WWarehouse Proxy agent 2warehouse summarization

upgrading foroverview 125

Warehouse Summarization and Pruning agent 2warehouse summarization upgrading

affected attribute groups and supporting scripts 129DB2 warehouse database procedure 130effects on summarized attributes 125MS SQL warehouse database procedure 132Oracle warehouse database procedure 131procedures for running scripts 130table summary 128tables in the warehouse 125types of table changes 127upgrading your warehouse 128

wikis 249Windows agent installation problems 210workarounds 209

agents 214remote deployment 219situations 220Take Action commands 224Tivoli Enterprise Portal 218workspaces 219

workspaceslist of all 13more information 13overview 13predefined 13troubleshooting 219


��

Printed in USA

SC32-9446-03

Documents

IBM Tivoli Monitoring: UNIX OS Agent: User.s Guidewepnet.com.br/docs/main_unix.pdf · SMP CPU attributes ... iv IBM Tivoli Monitoring: UNIX OS Agent: User’s Guide. Tables 1