Tivoli IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent

Transcription

1 Tivoli IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Version User s Guide SC

2

3 Tivoli IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Version User s Guide SC

4 Note Before using this information and the product it supports, read the information in Appendix D, Notices, on page 99. First Edition (March 2006) This edition applies to version of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2005, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables v About this guide vii Who should read this guide vii What this guide contains vii Publications viii Prerequisite publications viii Related publications viii Accessing terminology online ix Accessing publications online ix Ordering publications ix Accessibility ix Tivoli technical training x Support information x Conventions used in this guide x Typeface conventions x Operating system-dependent variables and paths x Chapter 1. Overview of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent IBM Tivoli Monitoring overview Features of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent functions Components of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent User interface options Chapter 2. Requirements for the monitoring agent Chapter 3. How to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent View real-time data about VMware ESX Server..11 Investigate an event Recover the operation of a resource Customize your monitoring environment Monitor with custom situations that meet your requirements Collect and view historical data Chapter 4. Workspaces reference About workspaces More information about workspaces Predefined workspaces VMware ESX Navigator item Availability Navigator item CPU Navigator item Disk Navigator item Memory Navigator item Network Navigator item Virtual Machines Navigator item Chapter 5. Attributes reference About attributes More information about attributes Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent.23 Availability attribute group CPU Base attribute group CPU Load Average attribute group CPU VM attribute group Disk Base attribute group Disk Usage attribute group Disk VM attribute group Memory Base attribute group Memory per VM attribute group Memory VM attribute group Network Base attribute group Network VM attribute group Performance Object Status attribute group System attribute group System CPU attribute group Virtual Machines attribute group VM File System attribute group Disk capacity planning for historical data Chapter 6. Situations reference About situations More information about situations Predefined situations VMware ESX Navigator item Availability Navigator item KQV_VMware_ESX_Server_Down situation..51 CPU Navigator item KQV_VMKernel_Not_Loaded situation KQV_CPU_Phy_Utilization_High situation...52 KQV_CPU_Avg_Underutilized situation KQV_CPU_Avg_Overutilized situation Disk Navigator item KQV_Filesystem_Freespace_Low situation...53 KQV_DiskRead_Activity_High situation KQV_DiskWrite_Activity_High situation Memory Navigator item KQV_Memory_Used_COS_High situation...55 KQV_Memory_Available_Low situation Network Navigator item KQV_NetworkTX_Activity_High situation...56 KQV_NetworkRX_Activity_High situation...56 Virtual Machines Navigator item KQV_Virtual_Machine_Off situation KQV_Virtual_Machine_Stuck situation KQV_Virtual_Machine_Unknown situation...58 KQV_Virtual_Machine_Suspended situation..58 Copyright IBM Corp. 2005, 2006 iii

6 Chapter 7. Take Action commands reference About Take Action commands More information about Take Action commands..61 Predefined Take Action commands Configure SSH Windows action Start Virtual Machine action Stop Virtual Machine action Chapter 8. Policies reference About policies More information about policies Appendix A. IBM Tivoli Enterprise Console event mapping Appendix B. Problem determination.. 73 Gathering product information for IBM Software Support Built-in problem determination features Problem classification Trace logging Overview of log file management Examples of trace logging Principal trace log files Setting RAS trace parameters Problems and workarounds Installation and configuration problem determination Agent problem determination Problem determination for remote deployment 84 Workspace problem determination Situation problem determination Support information Searching knowledge bases Obtaining fixes Receiving weekly support updates Contacting IBM Software Support Informational, warning, and error messages...93 Message format IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent messages Appendix C. Accessibility Navigating the interface using the keyboard...97 Magnifying what is displayed on the screen...97 Appendix D. Notices Trademarks Index iv IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

7 Tables 1. View real-time data about VMware ESX Server Investigating an event Recover the operation of a resource Customizing your monitoring environment Monitor with custom situations Collect and view historical data Capacity planning for historical data logged by component VMware Information to gather before contacting IBM Software Support Trace log files for troubleshooting agents Problems and solutions for installation and configuration General problems and solutions for uninstallation Agent problems and solutions Remote deployment problems and solutions Workspace problems and solutions General situation problems and solutions Problems with configuring situations that you solve in the Situation Editor Problems with configuration of situations that you solve in the Workspace area Take Action commands problems and solutions Copyright IBM Corp. 2005, 2006 v

8 vi IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

9 About this guide Who should read this guide What this guide contains IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent User s Guide provides information about installing and using IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. Use the configuration chapter in this guide along with IBM Tivoli Monitoring Installation and Setup Guide to install and set up the software. Use the information in this guide along with IBM Tivoli Monitoring User s Guide to monitor VMware ESX Server. This guide is for system administrators who install and use the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent to monitor and manage VMware ESX Server resources. Readers should be familiar with the following topics: v Tivoli Enterprise Portal interface v IBM Tivoli Monitoring application software v IBM Tivoli Enterprise Console (optional) v VMware ESX Server environments This guide contains the following chapters: v Chapter 1, Overview of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, on page 1 Provides an introduction to the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. v Chapter 2, Requirements for the monitoring agent, on page 5 Provides information about the requirements for the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. v Chapter 3, How to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, on page 11 Provides a list of tasks to achieve when using a monitoring agent, a list of procedures for performing each task, and references for where to find information about the procedures. After completing installation and configuration and becoming familiar with the information in Chapter 1 of this guide, use this chapter to see how you can use a monitoring agent. v Chapter 4, Workspaces reference, on page 17 Provides an overview of workspaces, references to additional information about workspaces, and descriptions of predefined workspaces in this monitoring agent. v Chapter 5, Attributes reference, on page 23 Provides an overview of attributes, references to additional information about attributes, descriptions of the attribute groups and attributes in this monitoring agent, and disk space requirements for historical data. v Chapter 6, Situations reference, on page 49 Copyright IBM Corp. 2005, 2006 vii

10 Provides an overview of situations, references to additional information about situations, and descriptions of the predefined situations in this monitoring agent. v Chapter 7, Take Action commands reference, on page 61 Provides detailed information about the Take Action commands, references to additional information about Take Action commands, and descriptions of the Take Action commands provided in this monitoring agent. v Chapter 8, Policies reference, on page 65 Provides an overview of policies, references for detailed information about policies, and descriptions of the predefined policies included in this monitoring agent. v Appendix A, IBM Tivoli Enterprise Console event mapping, on page 67 Provides an overview of the IBM Tivoli Enterprise Console event mapping information for this monitoring agent. v Appendix B, Problem determination, on page 73 Provides information about troubleshooting the various components of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, information about log files, and information about your options for obtaining software support. v Appendix C, Accessibility, on page 97 Provides information about the accessibility features in the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. v Appendix D, Notices, on page 99 Provides IBM and Tivoli notices and trademark information as it applies to the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. Publications Prerequisite Related This section lists publications relevant to the use of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. It also describes how to access these publications online and how to order these publications. publications To use the information in this guide effectively, you must have some knowledge of IBM Tivoli Monitoring products, which you can obtain from the following documentation: v IBM Tivoli Monitoring Administrator s Guide v IBM Tivoli Monitoring Installation and Setup Guide v IBM Tivoli Monitoring Problem Determination Guide v IBM Tivoli Monitoring User s Guide v IBM Tiivoli Monitoring Readme First publications The following documents also provide useful information: v IBM Tivoli Enterprise Console Adapters Guide v IBM Tivoli Enterprise Console Event Integration Facility User s Guide v IBM Tivoli Enterprise Console Reference Manual v IBM Tivoli Enterprise Console Rule Developer s Guide viii IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

11 Accessing terminology online The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: Accessing publications online The documentation CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. Refer to the readme file on the CD for instructions on how to access the documentation. Ordering IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: Click the Tivoli product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click ITM Tivoli Monitoring to access your product library at the Tivoli software information center. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. publications You can order many Tivoli publications online at the following Web site: You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, contact your software account representative to order Tivoli publications. Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate most features of the graphical user interface. For additional information, see Appendix C, Accessibility, on page 97. About this guide ix

12 Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: Support information Support information on page 89 describes the following options for obtaining support for IBM products: v Searching knowledge bases on page 89 v Obtaining fixes on page 90 v Contacting IBM Software Support on page 91 Conventions used in this guide Typeface This guide uses several conventions for special terms and actions, and operating system-dependent commands and paths. conventions This guide uses the following typeface conventions: Bold Italic v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Words defined in text v Emphasis of words v New terms in text (except in a definition list) v Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Operating system-dependent variables and paths The direction of the slash for directory paths might vary in this documentation. No matter which type of slash you see in the documentation, use the following guidelines for a slash: v If using UNIX, use a forward slash (/). v If using Windows, use a backslash (\). x IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

13 The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX. For environment variables, use the following guidelines: v If using UNIX, use $variable. v If using Windows, use %variable%. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions. About this guide xi

14 xii IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

15 Chapter 1. Overview of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent The IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent provides you with the capability to monitor VMware ESX Server, and to perform basic actions with VMware ESX Server. This chapter provides a description of the features, components, and interface options for the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. IBM Tivoli Monitoring overview IBM Tivoli Monitoring is the base software for the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. IBM Tivoli Monitoring provides a way to monitor the availability and performance of all the systems in your enterprise from one or several designated workstations. It also provides useful historical data that you can use to track trends and to troubleshoot system problems. You can use IBM Tivoli Monitoring to do the following: v Monitor for alerts on the systems that you are managing by using predefined situations or custom situations. v Establish your own performance thresholds. v Trace the causes leading to an alert. v Gather comprehensive data about system conditions. v Use policies to perform actions, schedule work, and automate manual tasks. The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. By providing a consolidated view of your environment, the Tivoli Enterprise Portal permits you to monitor and resolve performance issues throughout the enterprise. See the IBM Tivoli Monitoring publications listed in Prerequisite publications on page viii for complete information about IBM Tivoli Monitoring and the Tivoli Enterprise Portal. Features of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent The IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent software can identify, notify you of, and correct common problems with the application that it monitors. The software includes the following features: v Monitoring v Data gathering v Event management v Operations management IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent functions IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent provides the following functions: Copyright IBM Corp. 2005,

16 Resource monitoring Collect monitoring information for memory, CPU, system, disk and network usage for the VMware ESX Server. Availability monitoring Availability information will be provided separately for the monitored VMware ESX resource. An application ping using the VMware Scripting APIs will be made to determine whether the VMware ESX server is available. The VMware Server being unavailable shall indicate either one of the following - the server is no longer reachable; the VMPerl Scripting APIs are misconfigured; the VMware ESX server has gone offline. Actions Provide actions to start and stop the virtual machines installed on the VMware ESX Server. Historical data Provide a history enablement file which gives the user the ability to generate reports for all metrics collected. Components of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent After you install and set up the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, you have an environment that contains the client, server, and monitoring agent implementation for IBM Tivoli Monitoring that contains the following components: v Tivoli Enterprise Portal client with a Java-based user interface for viewing and monitoring your enterprise. v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli Enterprise Monitoring Server and enables retrieval, manipulation, and analysis of data from the monitoring agents. The Tivoli Enterprise Portal Server is the central repository for all user data. v Tivoli Enterprise Monitoring Server, which acts as a collection and control point for alerts received from the monitoring agents, and collects their performance and availability data. The Tivoli Enterprise Monitoring Server is also a repository for historical data. v Monitoring agent, IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, installed on the systems or subsystems that you want to monitor. This monitoring agent collects and distributes data to a Tivoli Enterprise Portal Server. Note: The agent cannot be installed on the VMware ESX server. It should be installed remotely on a supported platform. For more information, refer to the Chapter 2, Requirements for the monitoring agent, on page 5 chapter. IBM Tivoli Enterprise Console is an optional component, which acts as a central collection point for events from a variety of sources, including those from other Tivoli software applications, Tivoli partner applications, custom applications, network management platforms, and relational database systems. You can view these events through the Tivoli Enterprise Portal (using the event viewer), and you can forward events from IBM Tivoli Monitoring situations to the IBM Tivoli Enterprise Console component. 2 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

17 User interface options Installation of the base software and other integrated applications provides the following interfaces that you can use to work with your resources and data: Tivoli Enterprise Portal browser client interface The browser interface is automatically installed with Tivoli Enterprise Portal. To start Tivoli Enterprise Portal in your Internet browser, enter the URL for a specific Tivoli Enterprise Portal browser client installed on your Web server. Tivoli Enterprise Portal desktop client interface The desktop interface is a Java-based graphical user interface (GUI) on a Windows or Linux workstation. IBM Tivoli Enterprise Console Event management application Manage Tivoli Enterprise Monitoring Services window The window for the Manage Tivoli Enterprise Monitoring Services utility is used for configuring the agent and starting Tivoli services not already designated to start automatically. Chapter 1. Overview of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 3

18 4 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

19 Chapter 2. Requirements for the monitoring agent This chapter contains information about the requirements for the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. In addition to the requirements described in the IBM Tivoli Monitoring Installation and Setup Guide, the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent has the following requirements: v The monitoring agent runs on these operating systems: Windows 2000 Server Windows 2000 Advanced Server Windows XP Professional Windows 2003 Server Windows 2003 Enterprise Server Red Hat 2.1 Red Hat EL Advanced Server 3.0 Red Hat EL Advanced Server 4.0 United Linux 1/ SuSe 8 for IA32 United Linux 1/ SuSe 9 for IA32 If running this agent on a Windows operating system, the User ID must have Administrator privileges. v Monitors the following versions: VMware ESX Server 2.1.2, 2.5.1, v A single computer that hosts the hub monitoring server, portal server, and a monitoring agent requires approximately 300 MB of space. A monitored computer that hosts only the monitoring agent requires approximately 30 MB of space, including the specific enablement code for the monitoring agent. More space is required for each additional monitoring agent that you deploy on the monitored computer. Because this agent is enabled for remote management, multiple instances of the VMware ESX Server can be monitored from a single agent system. After you install the IBM Tivoli Monitoring Version 6.1 and the Tivoli Enterprise Portal, you install the following software that is required for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent to operate: v IBM Tivoli Monitoring 6.1 Fix Pack 1 v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Support for Tivoli Enterprise Management Server v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Support for Tivoli Enterprise Portal Server v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Support for Tivoli Enterprise Portal This agent collects data from the following data sources: Copyright IBM Corp. 2005,

20 SNMP Acronym for Simple Network Management Protocol. The network management protocol used almost exclusively in TCP/IP networks. SNMP allows you to monitor and control network devices, and to manage configurations, statistics collection, performance, and security. For this agent, SNMP V1 is used. The agent should not be installed on the VMware ESX server. It should be installed remotely on a supported platform. Additionally, the agent requires the VmPerl Scripting APIs to be installed on the system where the agent runs. The VmPerl Scripting APIs are distributed by VMware. They may be downloaded from or installed from the VMware ESX Server CD. Install the scripting APIs prior to installing the VMware ESX agent. The installation path of the scripting APIs should be noted because it will be needed during the configuration of the VMware ESX agent. In addition to the agent configuration, an ssh client must also be installed and configured on the system where the agent runs. Install the ssh client prior to installing the VMware ESX agent. The configuration steps vary slightly depending on the platform. Example configuration steps are as follows. Windows only - Since an ssh client is not included as part of the Windows base installation, one must be acquired. There are free versions available for download. In the VMware documentation there is a reference to a free client called plink. 1. Download and install the ssh client. Take note of the installation directory path. 2. Install the VMware ESX agent. 3. Configure the VMware ESX agent. During this process you will be asked the fully qualified path where the ssh client was installed. Enter the path and include the executable file name of the client as part of the path. 4. Start the VMware ESX agent. 5. Execute the SSH_CONFIGURE_WINDOWS action available from the Take Action menu. This task will put necessary authentication keys into the registry. This is required in order for data collection to work. Linux only - Most distributions of Linux include an ssh client. This configuration procedure configures the authentication keys used between the system running the agent and the ESX server. Additional information regarding the generation of keys can be found in the man pages for the utility ssh-keygen. 1. Logon to the linux system where the VMware ESX agent will be installed. 2. Use the ssh-keygen utility to generate public and private keys with no paraphase. For example, the command ssh-keygen -t dsa -f /root/mykey generates a set of public and private keys. Press enter when prompted for a paraphase. The public key generated is stored in the file /root/mykey.pub and the private key is stored in the file /root/mykey 3. Transfer the file containing the public key to the VMware ESX server. This may be done with utilities such as ftp and scp. 4. Append the public key file to the collection of keys stored on the ESX server. The stored keys are located in the file /root/.ssh/authorized_keys 5. Add the hostname and key for the VMware ESX Server in known_hosts file. This is normally located in /root/.ssh directory. To do this - execute the command ssh vmware_server_hostname -i private_keyfile date. Enter yes 6 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

21 when prompted to cache the keys. The successful completion of this command shall add the entry to the known_hosts file for future connections. 6. Configure the agent on the system where the agent is installed. During the configuration you will be prompted for the location of the file that contains the private keys. Enter the fully qualified path. The IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent provides optional functionality for monitoring and managing the system-level CPU usage and file system usage on the VMware system. To collect this data, VMware requires an SSH client. On Linux, an SSH client is available as part of the standard Linux RPMs. On Windows, an SSH client is separately available from Plink at the following location: NOTICE: IBM MAKES NO REPRESENTATION OR WARRANTY REGARDING THE PERFORMANCE OR CONTINUED AVAILABILITY OF THIS OPTIONAL FUNCTIONALITY. PLINK IS SEPARATELY LICENSED CODE AS SPECIFIED IN THE LICENSE INFORMATION DOCUMENT OF THE IBM LICENSE AGREEMENT. If you desire this optional functionality, You may obtain a license for Plink under the terms of the applicable third party license agreement(s) provided or referenced at the Plink website and not the terms of any IBM agreement. Notwithstanding any of the terms in the Plink license agreement, or any other agreement you may have with IBM, the terms of the Plink license agreement(s) govern your use of the Plink code, and not the terms of any IBM agreement. Please refer to the Separately Licensed Code identified in the License Information document of the IBM license agreement. IBM makes no representations whatsoever about the Plink product, VMware, nor any web site which you may access to obtain Plink. When you access a non-ibm Web site or product, even one that may contain the IBM-logo, please understand that it is independent from IBM, and that IBM has no control over the content or products available on that Web site. In addition, a link to a non-ibm Web site or non-ibm product does not mean that IBM endorses or accepts any responsibility for the content, or the use, of such Web site or product. It is up to you to take precautions to ensure that whatever you select for your use is free of such items as viruses, worms, trojan horses and other items of a destructive nature. Notwithstanding any of the terms in the Plink license or your IBM license, or any other agreement you may have with IBM: v (a) IBM provides this information to you WITHOUT WARRANTIES OF ANY KIND; v (b) IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SEPARATELY LICENSED CODE; v (c) IBM is not liable to you, and will not defend, indemnify, or hold you harmless for any claims arising from or related to your use of Plink, the web site, or any other hyper-lined web site; and v (d) IBM is not liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages including, but not limited to, lost data, lost savings, and lost profits, business interruption, loss of programs or other data on Chapter 2. Requirements for the monitoring agent 7

22 your system with respect to your use of Plink, the web site, or any other hyper-lined web site, even if we are expressly advised of the possibility of such damages. If you obtained the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent under the IBM International Program License Agreement ( IPLA ) or IBM International Program License Agreement for Non Warranted Program ( ILAN ) and you are the original licensee of the Program, and you do not agree with the third party license agreement(s), you may return the Program in accordance with the terms of, and within the specified time frames stated in, the Money-back Guarantee section of the IPLA or ILAN. The following configuration values must be provided for the agent to operate. When configuring an agent, a panel displays that allows you to type in each value. When there is a default value, this will be pre-entered into the field. If a field represents a password, there will be 2 entry fields displayed. You must enter the same value in each field. The values you type will not be displayed. This helps maintain the security of these values. The following fields are defined for this agent: v Tab: SNMP Server v Field: Community Name v Type: password The community name used to send GET requests to the SNMP agent. v Tab: SNMP Server v Field: Host v Type: string The host name or ip address of the SNMP agent. v Tab: SNMP Server v Field: Port v Type: string The port the SNMP agent uses to receive requests (normally 161). v Tab: VMware ESX Configuration v Field: SSH keyfile location (Linux platforms only) v Type: string The fully qualified path where the SSH authentication keyfile is located. This is the key file you generated using ssh-keygen. Ensure that you have stored the corresponding public key on the VMware ESX Server. This is required for linux platforms only. v Tab: VMware ESX Configuration v Field: Fully qualified filename for the SSH Client v Type: string The fully qualified path including the executable name of the SSH Client. For example /usr/bin/ssh for Linux and c:\\program files\\plink.exe for Windows. v Tab: VMware ESX Configuration v Field: VMware Server Admin ID v Type: string The administrator user ID for the VMware ESX server that will be monitored. v Tab: VMware ESX Configuration v Field: VMware Server Admin Password v Type: password 8 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

23 The password of the administrator user ID of the VMware ESX server that will be monitored. v Tab: VMware ESX Configuration v Field: VMware Server Hostname v Type: string The hostname of the VMware server to be monitored. v Tab: VMware ESX Configuration v Field: Fully qualified path for the VmPerl Scripting APIs v Type: string The fully qualified path where the VMware VmPerl Scripting APIs are installed. The vmware-cmd file must be accessible in this path. v Tab: VMware ESX Configuration v Field: VmPerl Port v Type: numeric The port number that the VMware Scripting APIs will use to communicate with the VMware ESX server. The default is 902 and this should be used unless you configured your ESX server to use another port. When installing the agent remotely, the configuration values must be provided. An example command line would be: tacmd addsystem -t QV -n sample.node.name:nt -p SNMP.SNMP_COMMUNITY=value SNMP.SNMP_HOST=value SNMP.SNMP_PORT=value VMWARE.SSH_KEYFILE=value VMWARE.SSH_LOC=value VMWARE.VMWARE_ADMINID=value VMWARE.VMWARE_ADMINPASSWORD=value VMWARE.VMWARE_SERVERHOSTNAME=value VMWARE.VMWARE_VMPERL_DIR=value VMWARE.VMWARE_VMPERL_PORT=value Chapter 2. Requirements for the monitoring agent 9

24 10 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

25 Chapter 3. How to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent After you have installed and configured IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, and the agent is running, you can begin using this agent to monitor your resources. The following sources of information are relevant to installation and configuration: v IBM Tivoli Monitoring Installation and Setup Guide v Chapter 2, Requirements for the monitoring agent, on page 5 in this user s guide for information about installing and configuring IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent This chapter provides information about how to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent to achieve the following purposes: v View real-time data about VMware ESX Server v Investigate an event on page 12 v Recover the operation of a resource on page 12 v Customize your monitoring environment on page 13 v Monitor with custom situations that meet your requirements on page 14 v Collect and view historical data on page 15 For each of these purposes, there is a list of procedures that you perform to achieve the purpose. For the procedures, there is a cross-reference to where you can find information about performing that procedure. Information about the procedures is located in subsequent chapters of this user s guide and in the following publications: v IBM Tivoli Monitoring User s Guide v IBM Tivoli Monitoring Administrator s Guide View real-time data about VMware ESX Server After you install and configure IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, the agent begins monitoring. Table 1 contains a list of the procedures for viewing the real-time data about VMware ESX Server that the monitoring agent collects through the predefined situations. The table also contains a cross-reference to where you can find information about each procedure. Table 1. View real-time data about VMware ESX Server Procedure Where to find information View the hierarchy of your monitored resources from a system point of view (Navigator view organized by operating platform, system type, monitoring agents, and attribute groups). View the indicators of real or potential problems with the monitored resources (Navigator view). IBM Tivoli Monitoring User s Guide: Navigating through workspaces (in Monitoring: Real-time and Event-based chapter) Copyright IBM Corp. 2005,

26 Table 1. View real-time data about VMware ESX Server (continued) Procedure Where to find information View changes in the status of the resources that are being monitored (Enterprise Message Log view). View the status of the monitoring agents in the managed enterprise that you are monitoring (Monitoring Agent Status view). View the number of times an event has been opened for a situation during the past 24 hours (Opened Situations Count view). IBM Tivoli Monitoring User s Guide: Using workspaces (in Monitoring: Real-time and Event-based chapter) Chapter 4, Workspaces reference, on page 17 in this guide IBM Tivoli Monitoring User s Guide: Using workspaces (in Monitoring: Real-time and Event-based chapter) Chapter 6, Situations reference, on page 49 in this guide Manipulate the views in a workspace. IBM Tivoli Monitoring User s Guide: Using views (in Monitoring: Real-time and Event-based chapter) Chapter 4, Workspaces reference, on page 17 in this guide Investigate an event When the conditions of a situation have been met, an event indicator is displayed in the Navigator. When an event occurs, you want to obtain information about that event so you can correct the conditions and keep your enterprise running smoothly. Table 2 contains a list of the procedures for investigating an event and a cross-reference to where you can find information about each procedure. Table 2. Investigating an event Procedure Where to find information Determine which situation raised the event and identify the attributes that have values that are contributing to the alert. Review available advice. Notify other users that you have taken ownership of the problem related to an event and are working on it. IBM Tivoli Monitoring User s Guide: Opening the event workspace (in Monitoring: Real-time and Event-based chapter, Responding to Alerts section) Chapter 4, Workspaces reference, on page 17 in this guide IBM Tivoli Monitoring User s Guide: Acknowledging an event (in Monitoring: Real-time and Event-based chapter, Responding to Alerts section) Remove the event from the Navigator. IBM Tivoli Monitoring User s Guide: Closing the event workspace (in Monitoring: Real-time and Event-based chapter, Responding to Alerts section) Recover the operation of a resource When you find out that a resource is not operating as desired, you can control it manually or automatically using Take Action commands. 12 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

27 Table 3 contains a list of the procedures for recovering the operation of a resource and a cross-reference to where you can find information about each procedure. Table 3. Recover the operation of a resource Procedure Where to find information Take an action on a resource manually. IBM Tivoli Monitoring User s Guide: v Other Views (in Custom Workspaces chapter, Workspace Views section) v Take action Reflex automation (in Situations for Event-based Monitoring chapter, Event-based Monitoring Overview section) Take an action on a system condition automatically by setting up a situation to run a Take Action command. Take multiple actions on system conditions automatically using a policy. Take actions across systems, agents, or computers using a policy. Chapter 7, Take Action commands reference, on page 61 in this guide IBM Tivoli Monitoring User s Guide: Situations for Event-based Monitoring chapter v Customize a Situation v Create a Situation v Specify an action to take v Distribute the situation Chapter 7, Take Action commands reference, on page 61 in this guide IBM Tivoli Monitoring User s Guide: Policies for Automation chapter v Creating a policy v Maintaining Policies v Workflows Window Chapter 8, Policies reference, on page 65 in this guide Customize your monitoring environment You can change how your monitoring environment looks by creating new workspaces with one or more views in it. Table 4 contains a list of the procedures for customizing your monitoring environment and a cross-reference to where you can find information about each procedure. Table 4. Customizing your monitoring environment Procedure Where to find information Display data in tables or charts (views) in Tivoli Enterprise Portal. Display an overview of changes in the status of situations for your monitored resources (Message Log View). IBM Tivoli Monitoring User s Guide: v Custom Workspaces v Table and Chart Views IBM Tivoli Monitoring User s Guide: Message Log View (in Event Views: Message Log, Event Console and Graphic chapter) Chapter 3. How to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 13

28 Table 4. Customizing your monitoring environment (continued) Procedure Where to find information Specify which attributes to retrieve for a table or chart so you can retrieve only the data you want by creating custom queries. IBM Tivoli Monitoring User s Guide: Create Custom Queries (in Table and Chart Views chapter) Chapter 5, Attributes reference, on page 23 in this guide Build links from one workspace to another. IBM Tivoli Monitoring User s Guide: Identify which predefined situations started running automatically when you started the Tivoli Enterprise Management Server. v Link from a Workspace (in Custom Workspaces chapter) v Link from a Table or Chart (in Table and Chart Views chapter) IBM Tivoli Monitoring User s Guide: What the enterprise workspace shows (in Monitoring: Real-time and Event-based chapter, Using Workspaces section) Determine whether to run situations as defined, modify the values in situations, or create new situations to detect possible problems. Chapter 6, Situations reference, on page 49 in this guide Monitor with custom situations that meet your requirements in this chapter Chapter 6, Situations reference, on page 49 in this guide Monitor with custom situations that meet your requirements When your environment requires situations with values that are different from those in the existing situations, or when you need to monitor conditions not defined by the existing situations, you can create custom situations to detect problems with resources in two ways: v Create an entirely new situation v Create a situation by copying and editing a predefined situation You can specify the following information for a situation: v Name v Attribute group and attributes v Qualification to evaluate multiple rows when a situation has a multiple-row attribute group (display item) v Formula v Take Action commands v Run at startup v Sampling interval v Persistence v Manual or automatic start v Severity v Clearing conditions v Expert Advice v When a true situation closes v Available Managed Systems 14 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

29 Table 5 contains a list of the procedures for monitoring your resources with custom situations that meet your requirements and a cross-reference to where you can find information about each procedure. Table 5. Monitor with custom situations Procedure Where to find information Create an entirely new situation. IBM Tivoli Monitoring User s Guide: Create a new situation (in Situations for Event-based Monitoring chapter, Creating a Situation section) Chapter 5, Attributes reference, on page 23 in this guide Create a situation by copying and editing a predefined situation. IBM Tivoli Monitoring User s Guide: Customize a Situation (in Situations for Event-based Monitoring chapter) Chapter 6, Situations reference, on page 49 in this guide Chapter 5, Attributes reference, on page 23 in this guide Run a situation on a managed system. IBM Tivoli Monitoring User s Guide: Situations for Event-based Monitoring chapter v Associate Situations with Navigator Items v Distribute the Situation (in Customize a Situation section) v Start, Stop or Delete a Situation Collect and view historical data When you collect historical data, you specify the following configuration requirements: v Attribute groups for which to collect data v Collection interval v Roll-off interval to a data warehouse, if any v Where to store the collected data (at the agent or the Tivoli Enterprise Management Server) Table 6 on page 16 contains a list of the procedures for collecting and viewing historical data and a cross-reference to where you can find information about each procedure. Chapter 3. How to use IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 15

30 Table 6. Collect and view historical data Procedure Where to find information Configure and start collecting short-term data (24 hours). Configure and start collecting longer-term data (more than 24 hours). View historical data in the Tivoli Enterprise Portal. Create reports from historical data using third-party reporting tools. Filter out unwanted data to see specific areas of interest. IBM Tivoli Monitoring User s Guide: Historical Reporting (in Table and Chart Views chapter) IBM Tivoli Monitoring Administrator s Guide 16 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

31 Chapter 4. Workspaces reference This chapter contains an overview of workspaces, references for detailed information about workspaces, and descriptions of the predefined workspaces included in this monitoring agent. About workspaces A workspace is the working area of the Tivoli Enterprise Portal application window. At the left of the workspace is a Navigator that you use to select the workspace you want to see. As you select items in the Navigator, the workspace presents views pertinent to your selection. Each workspace has at least one view. Every workspace has a set of properties associated with it. This monitoring agent provides predefined workspaces. You cannot modify or delete the predefined workspaces, but you can create new workspaces by editing them and saving the changes with a different name. More information about workspaces For more information about creating, customizing, and working with workspaces, see IBM Tivoli Monitoring User s Guide. For a list of the predefined workspaces for this monitoring agent and a description of each workspace, refer to the Predefined workspaces section below and the information in that section for each individual workspace. Some attribute groups for this agent might not be represented in the predefined workspaces or views for this agent. For a full list of the attribute groups, see the Attributes reference section. If you are using remote management, in order to navigate to your systems in the Tivoli Enterprise Portal, navigate from the hostname of the machine where you installed the agent. When you add another vmware agent instance to a configuration that already has a vmware agent instance, the new agent instance appears dynamically in the Tivoli Enterprise Portal. Each instance s name is presented in the Tivoli Enterprise Portal when more than one instance is reporting from a specific host. To identify an instance, navigate from the hostname of the machine where you installed the agent. For example, with one instance, you will see hostname and the contained node is VMware ESX. The workspaces that display data for this application are contained in VMware ESX node. When you add an additional instance, both instances appear under hostname and an additional level that displays as the hostname:qv. In the navigator view, the instance name is only shown if there are two or more instances. Copyright IBM Corp. 2005,

32 Predefined workspaces IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent provides the following predefined workspaces, which are organized by Navigator item: v VMware ESX Navigator item VMware ESX workspace v Availability Navigator item Availability workspace v CPU Navigator item CPU workspace CPU per VM workspace v Disk Navigator item Disk workspace Disk per VM workspace v Memory Navigator item Memory workspace Memory per VM workspace v Network Navigator item Network workspace v Virtual Machines Navigator item Virtual Machines workspace VMware ESX Navigator item The remaining sections of this chapter contain descriptions of each of these predefined workspaces. The workspaces are organized by the Navigator item to which the workspaces are relevant. VMware ESX workspace This workspace displays the overall state of the VMware ESX Server. This workspace contains the following views: System Availability Navigator item Overview Displays the system overview of the VMware ESX Server. Availability Displays the availability of the VMware ESX Server. Virtual Machines Displays the state of the virtual machines installed on VMware ESX Server. Availability workspace The Availability workspace displays the overall health of the application. This agent runs the following tests on the monitored application: v VMware ESX Server Status (KQV_VMwareESX_Status.bat) v VMware ESX Server Status (KQV_VMwareESX_Status.sh) This workspace contains the following views: 18 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

33 Availability Displays the state of each component in the application. An application-specific operation is performed to determine whether VMware ESX Server is running correctly. This is displayed using the descriptive name of the function tested and the results of the operation (PASSED or FAILED). When the state of the component is FAILED (for a test) it will be highlighted with a red background. Data Collection Status Displays the status of the tables that represent performance metrics for this application. This view allows the user to verify that data is being collected for each of the tables. If data is not being collected, it will provide an error status. This may indicate that there are no instances to be returned, or it may indicated a problem to be corrected. CPU Navigator item CPU Disk Navigator item workspace Provides CPU information about the VMware ESX Server. This workspace contains the following views: CPU Utilization per Physical CPU Displays the CPU Utilization for each physical CPU. CPU Load Average - Five Minute Average Displays the load average for the CPUs over five minute intervals. CPU Load Averages Displays the load average for the CPUs over one minute, five minute and fifteen minute intervals. CPU per VM workspace Provides CPU information per virtual machine on the VMWare ESX Server. Disk This workspace contains the following views: CPU Shares per VM Displays the CPU shares per VM for the VMware ESX Server. CPU Utilization Rate Displays the percent rate of CPU utilization per VM for the VMware ESX Server. workspace Provides disk information about the VMware ESX Server machine. This workspace contains the following views: Filesystem Overview Displays an overview of the filesystems mounted on the VMware ESX Server. VMFS Filesystem Overview Displays an overview of the files in the VMFS filesystem. Filesystem Percent Used Displays the percent of blocks used by each filesystem mounted on the VMware ESX Server. Chapter 4. Workspaces reference 19

34 Disk per VM workspace Provides disk information per virtual machine on the VMWare ESX Server. This workspace contains the following views: Share of Disk Bandwidth Allocated per VM Displays the relative disk bandwith allocated to each VM on the VMware ESX Server. Disk Memory Navigator item Network Navigator item Activity Displays the disk activity per VM on the VMware ESX Server. Disk Utilization Rate Displays the disk utilization per VM on the VMware ESX Server. Disk Adapters in Use per VM Displays the disk adapters in use per VM on the VMware ESX Server. Memory workspace Provides memory information for the VMware ESX Server machine and the Virtual Machines. This workspace contains the following views: Free Memory Available Displays the free memory available on the VMware ESX Server. Memory Used by Console OS Displays the memory used by the console OS (COS) on the VMware ESX Server. Total Memory Statistics Total Memory Statistics Displays in KB the total and available memory for the VMware ESX server. Memory per VM workspace Provides memory information for the virtual machines installed on the VMware ESX Server. This workspace contains the following views: Memory Usage per VM Displays the memory used per VM in KB for each VM installed on the VMware ESX Server. Memory Configured per VM Displays the memory configured in MB for each VM installed on the VMware ESX Server. Memory Shares per VM Displays the relative memory allocated to each VM installed on the VMware ESX Server. Network workspace Provides network information about the VMware ESX Server machine. This workspace contains the following views: 20 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

35 Virtual Machines Navigator item Network Activity Displays the network activity per VM for the VMware ESX Server. Network Usage Rate per Adapter Displays the network utilization per adapter for the VMware ESX Server. Network Adapters in Use per VM Displays the network adapters in use per VM for the VMware ESX Server. Virtual Machines workspace Provides an overview of the virtual machines installed on the VMware ESX Server machine. This workspace contains the following views: Virtual Machine Overview Displays the metrics related to the virtual machines on the VMware ESX Server. It displays the state of the virtual machines as well as the state of the guest operating system installed on the virtual machine. A value of unknown in the VM Guest State column along with a value of off in the VM State column indicates that the VM is down and the guest OS is in shutdown state. Also, a value of unknown in the VM Guest State and a value of on in the VM State column signifies that no guest OS has been installed on the virtual machine.. Memory Configured per VM Displays the memory configured for the virtual machines installed on the VMware ESX Server. Chapter 4. Workspaces reference 21

36 22 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

37 Chapter 5. Attributes reference This chapter contains an overview of attributes, references for detailed information about attributes, and descriptions of the attributes for each attribute group included in this monitoring agent. About attributes Attributes are the application properties being measured and reported by IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. Attributes are organized into groups according to their purpose. The attributes in a group can be used in the following two ways: v Chart or table views v Attributes are displayed in chart and table views. The chart and table views use queries to specify which attribute values to request from a monitoring agent. You use the Query editor to create a new query, modify an existing query, or apply filters and set styles to define the content and appearance of a view based on an existing query. Situations You use attributes to create situations that monitor the state of your operating system, database, or application. A situation describes a condition you want to test. When you start a situation, the Tivoli Enterprise Portal compares the values you have assigned to the situation attributes with the values collected by IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent and registers an event if the condition is met. You are alerted to events by indicator icons that are displayed in the Navigator. More information about attributes For more information about using attributes and attribute groups, see IBM Tivoli Monitoring User s Guide. For a list of the attributes groups, a list of the attributes in each attribute group, and descriptions of the attributes for this monitoring agent, refer to the Attribute groups and attributes section in this chapter. Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent This monitoring agent contains the following attribute groups: v Availability v CPU Base v CPU Load Average v CPU VM v Disk Base v Disk Usage v Disk VM v Memory Base Copyright IBM Corp. 2005,

38 v Memory per VM v Memory VM v Network Base v Network VM v Performance Object Status v System v System CPU v Virtual Machines v VM File System Availability attribute group Historical Attribute The remaining sections of this chapter contain descriptions of these attribute groups, which are listed alphabetically. The following information is provided for each attribute group: Attributes List of attributes that belong to the attribute group Historical group Whether the attribute group is a historical type that you can roll off to a data warehouse Attribute descriptions and type for each attribute in the attribute group Contains the availability data for the application. The table provides a common format for representation of application availability. This includes the relevant information for three aspects of an application. These are processes, services (Windows only) and functionality tests. This agent runs the following tests on the monitored application: v VMware ESX Server Status (KQV_VMwareESX_Status.bat) v VMware ESX Server Status (KQV_VMwareESX_Status.sh) If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Availability attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type Time 24 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

39 Application Component attribute - This attribute is a key attribute. The descriptive name of a part of the application. Type String Name attribute The name of the process, service or functional test. This will match the executable name of the process, the service short name or the name of the process used to test the application. Type String Status attribute The status of the application component. v For processes this is UP, DOWN WARNING or PROCESS_DATA_NOT_AVAILABLE. PROCESS_DATA_NOT_AVAILABLE will be displayed for a process when the matching process is running but the resource use information cannot be collected for that process. v For services this is UP, DOWN or UNKNOWN. UNKNOWN will be displayed when the service is not installed. v For functionality tests this is PASSED or FAILED Type String Full Name attribute Type Type attribute The full name of the process including the path. String Identifies the type of the application component. Components are processes, services or functionality tests. Type Integer (Gauge) Virtual Size attribute The virtual size (in MB) of the process. Type Integer (Gauge) Page Faults Per Sec attribute The rate of page faults for the process measured in faults per second. This will only contain valid data for processes. Type Integer (Gauge) Working Set Size attribute Chapter 5. Attributes reference 25

40 The working set size of the process in MB. This will only contain valid data for processes. Type Integer (Gauge) Thread Count attribute The number of threads currently allocated by this process. This will only contain valid data for processes. Type Integer (Gauge) PID attribute The process id associated with the process. This will only contain valid data for processes. Type Integer (Gauge) Percent Privileged Time attribute The percentage of the available CPU time that is being used by this process for privileged operation. Type Integer (Gauge) Percent User Mode Time attribute The percentage of the available CPU time that is being used by this process for user mode operation. Type Integer (Gauge) Percent Processor Time attribute The percentage of the elapsed time that this process used the processor to execute instructions. Type Integer (Gauge) Command Line attribute The program name and any arguments specified on the command line when the process was started. This has the value N/A if this is a Service or Functionality test. Type String Functionality Test Status attribute The return code of the functionality test. When the monitored application is running correctly SUCCESS is displayed, NOT_RUNNING when it is not running correctly or N/A when the row does not represent a functionality test. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: N/A (1), SUCCESS (0), GENERAL_ERROR (2), WARNING (3), NOT_RUNNING (4), 26 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

41 DEPENDENT_NOT_RUNNING (6), ALREADY_RUNNING (6), PREREQ_NOT_RUNNING (7), TIMED_OUT (8), DESNT_EXIST (9) or UNKNOWN (10). Any other values will display the numeric value in the Tivoli Enterprise Portal. Functionality Test Message attribute The text message that corresponds to the Functionality Test Status. This is only valid for functionality tests. Type CPU Base attribute group Historical Attribute String Contains metrics for CPU utilization for the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is not stored in the warehouse. group This attribute group is not part of the default historical group. descriptions The following list contains information about each attribute in the CPU Base attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String CPU VMID attribute - This attribute is a key attribute. The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) CPU Share attribute Amount of relative CPU share allocated to this virtual machine by the vmkernel. Type Integer (Counter) CPU Utilization Rate attribute The CPU utilization in seconds per VM time interval. A VM time interval does not match real-world time intervals. This CPU Chapter 5. Attributes reference 27

42 Type utilization will not match monitors running inside the VM because of processes in the VM and the CPU used by other VMs. CPU Load Average attribute group Historical Attribute This contains metrics for the CPU load average over one, five and fifteen minutes intervals for the VMware ESX Server. These are calculated by dividing the numbers reported in the /proc/vmware/sched/cpu-load vcpus row by the number of physical cpus. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the CPU Load Average attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Load Avg One Min attribute The CPU load average for the VMware ESX Server calculated over a one minute interval. Type Floating point Load Avg Five Min attribute The CPU load average for the VMware ESX Server calculated over a five minute interval. Type Floating point Load Avg Fifteen Min attribute The CPU load average for the the VMware ESX Server calculated over a fifteen minute interval. Type Floating point 28 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

43 CPU VM attribute group Historical Attribute This attribute group contains metrics for the CPU utilization of the virtual machines on the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the CPU VM attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String VM Index attribute The snmp index number for this virtual machine. Type Integer (Counter) VM Name attribute The display name for this virtual machine. Type String VM Config File attribute - This attribute is a key attribute. Fully qualified configuration file name for this virtual machine. Type String VM OS attribute Operating system running on this virtual machine. Type String VM Memory attribute Memory configured for this virtual machine in MB. Type Integer (Counter) VM State attribute Virtual machine state. Chapter 5. Attributes reference 29

44 Type String VM VMID attribute The ID assigned to a running virtual machine by the vmkernel. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: NONE (-1) Any other values will display the numeric value in the Tivoli Enterprise Portal. VM Guest State attribute Guest operating system state. A value of unknown and a value of off for VM State indicates that the guest OS is shut down, whereas unknown and a value of on for the VM State indicates that the VM does not have a guest OS installed. Type String CPU VMID attribute - This attribute is a key attribute. The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) CPU Share attribute Amount of relative CPU share allocated to this virtual machine by the vmkernel. Type Integer (Counter) CPU Utilization Rate attribute The CPU utilization in seconds per VM time interval. A VM time interval does not match real-world time intervals. This CPU utilization will not match monitors running inside the VM because of processes in the VM and the CPU used by other VMs. Type Disk Base attribute group Historical Attribute Contains metrics for Disk adapter and target information. If the warehouse default setting is enabled, data for this attribute group is not stored in the warehouse. group This attribute group is not part of the default historical group. descriptions The following list contains information about each attribute in the Disk Base attribute group: Node attribute - This attribute is a key attribute. 30 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

45 The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String HBA index attribute Index for Host Bus Adapter table. Type Integer (Counter) HBA name attribute - This attribute is a key attribute. String describing the disk. Format: devicename#:target:lun Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) Disk Shares attribute Amount of relative disk bandwidth allocated to this virtual machine by the vmkernel. Type Integer (Counter) Number of Reads attribute Number of reads from this disk since the disk module was loaded. Type Integer (Counter) KB Read per Sec attribute Rate of change in kilobytes per second read from this disk. Type Integer (rate of change between successive values) Number of Writes attribute Number of writes to this disk since the disk module was loaded. Type Integer (Counter) KB Write per Sec attribute Rate of change in kilobytes per second written to this disk. Type Integer (rate of change between successive values) Chapter 5. Attributes reference 31

46 Disk Usage attribute group Historical Attribute This attribute group contains metrics for the filesystem usage on the VMware ESX Server. This corresponds to the vdf command provided on the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Disk Usage attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Filesystem attribute - This attribute is a key attribute. This is the name of the filesystem mounted on the VMware ESX Server. Type String Total Blocks attribute This is the number of 1K-blocks associated with the filesystem in kilobytes. Type Integer (Counter) Blocks Used attribute This is the number of 1K-blocks used by the filesystem. Type Integer (Counter) Blocks Available attribute This is the number of 1K-blocks available to the filesystem. Type Integer (Counter) Percent Used attribute This is the percent used by the filesystem. Type Integer (Counter) 32 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

47 Mount Point attribute This is the location where the filesystem is mounted. Type String Disk VM attribute group Historical Attribute This attribute group contains metrics related to the disk usage by different virtual machines. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Disk VM attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String VM Index attribute The snmp index number for this virtual machine. Type Integer (Counter) VM Name attribute The display name for this virtual machine. Type String VM Config File attribute - This attribute is a key attribute. Fully qualified configuration file name for this virtual machine. Type String VM OS attribute Operating system running on this virtual machine. Type String VM Memory attribute Chapter 5. Attributes reference 33

48 Memory configured for this virtual machine in MB. Type Integer (Counter) VM State attribute Virtual machine state. Type String VM VMID attribute The ID assigned to a running virtual machine by the vmkernel. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: NONE (-1) Any other values will display the numeric value in the Tivoli Enterprise Portal. VM Guest State attribute Guest operating system state. A value of unknown and a value of off for VM State indicates that the guest OS is shut down, whereas unknown and a value of on for the VM State indicates that the VM does not have a guest OS installed. Type String HBA index attribute Index for Host Bus Adapter table. Type Integer (Counter) HBA name attribute - This attribute is a key attribute. String describing the disk. Format: devicename#:target:lun Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) Disk Shares attribute Amount of relative disk bandwidth allocated to this virtual machine by the vmkernel. Type Integer (Counter) Number of Reads attribute Number of reads from this disk since the disk module was loaded. 34 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

49 Type Integer (Counter) KB Read per Sec attribute Rate of change in kilobytes per second read from this disk. Type Integer (rate of change between successive values) Number of Writes attribute Number of writes to this disk since the disk module was loaded. Type Integer (Counter) KB Write per Sec attribute Rate of change in kilobytes per second written to this disk. Type Integer (rate of change between successive values) Memory Base attribute group Historical Attribute Contains metrics for memory utilization for the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Memory Base attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Total Memory attribute Total physical memory present on the VMware ESX server (KB). Type Integer (Counter) ConsoleOS Memory attribute Amount of physical memory used by the console OS (COS) in KB. Type Integer (Counter) Memory Available attribute Chapter 5. Attributes reference 35

50 Amount of physical memory free kilobytes. Type Integer (Counter) Pct Mem Used by COS attribute Percent of memory used by the console OS (COS) Type Integer (Calculated) Pct Mem Not Used by COS attribute Percent of memory not being used by the console OS (COS) Type Integer (Calculated) Pct Total Free Memory attribute Percent of memory free Type Integer (Calculated) Memory per VM attribute group Historical Attribute Contains metrics for memory utilization per virtual machine for the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is not stored in the warehouse. group This attribute group is not part of the default historical group. descriptions The following list contains information about each attribute in the Memory per VM attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) Memory Shares attribute 36 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

51 Amount of relative memory shares allocated to this virtual machine by the vmkernel. Type Integer (Counter) Memory Configured attribute Memory configured for this virtual machine (MB). Type Integer (Counter) Memory Utilized attribute Memory VM attribute group Historical Attribute The amount of memory utilized by the virtual machine (KB). Type Integer (Counter) Contains metrics for memory utilization of the virtual machines and their state. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Memory VM attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String VM Index attribute The snmp index number for this virtual machine. Type Integer (Counter) VM Name attribute The display name for this virtual machine. Type String VM Config File attribute - This attribute is a key attribute. Fully qualified configuration file name for this virtual machine. Chapter 5. Attributes reference 37

52 Type String VM OS attribute Operating system running on this virtual machine. Type String VM Memory attribute Memory configured for this virtual machine in MB. Type Integer (Counter) VM State attribute Virtual machine state. Type String VM VMID attribute The ID assigned to a running virtual machine by the vmkernel. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: NONE (-1) Any other values will display the numeric value in the Tivoli Enterprise Portal. VM Guest State attribute Guest operating system state. A value of unknown and a value of off for VM State indicates that the guest OS is shut down, whereas unknown and a value of on for the VM State indicates that the VM does not have a guest OS installed. Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) Memory Shares attribute Amount of relative memory shares allocated to this virtual machine by the vmkernel. Type Integer (Counter) Memory Configured attribute Memory configured for this virtual machine (MB). Type Integer (Counter) Memory Utilized attribute 38 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

53 The amount of memory utilized by the virtual machine (KB). Type Integer (Counter) Network Base attribute group Historical Attribute Contains metrics for network adapter statistics. If the warehouse default setting is enabled, data for this attribute group is not stored in the warehouse. group This attribute group is not part of the default historical group. descriptions The following list contains information about each attribute in the Network Base attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Network Name attribute - This attribute is a key attribute. String describing the network adapter. Format: vmnic Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) MAC Address attribute MAC address of the virtual machine s virtual NIC. Type String Number of Pkts Transmitted attribute Number of packets transmitted on this NIC since the network module was loaded. Type Integer (Counter) KB Transmitted Rate attribute Chapter 5. Attributes reference 39

54 Rate of network traffic in kilobytes per second sent from this NIC. Type Integer (rate of change between successive values) Number of Pkts Received attribute Number of packets received on this NIC since the network module was loaded. Type Integer (Counter) KB Received Rate attribute Network VM attribute group Historical Attribute Rate of network traffic in kilobytes per second received on this NIC. Type Integer (rate of change between successive values) Contains metrics describing the network usage statistics by the virtual machines. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Network VM attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String VM Index attribute The snmp index number for this virtual machine. Type Integer (Counter) VM Name attribute The display name for this virtual machine. Type String VM Config File attribute - This attribute is a key attribute. 40 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

55 Fully qualified configuration file name for this virtual machine. Type String VM OS attribute Operating system running on this virtual machine. Type String VM Memory attribute Memory configured for this virtual machine in MB. Type Integer (Counter) VM State attribute Virtual machine state. Type String VM VMID attribute The ID assigned to a running virtual machine by the vmkernel. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: NONE (-1) Any other values will display the numeric value in the Tivoli Enterprise Portal. VM Guest State attribute Guest operating system state. A value of unknown and a value of off for VM State indicates that the guest OS is shut down, whereas unknown and a value of on for the VM State indicates that the VM does not have a guest OS installed. Type String Network Name attribute - This attribute is a key attribute. String describing the network adapter. Format: vmnic Type String VMID attribute The ID allocated to a running virtual machine by the vmkernel. This corresponds to the VM ID in the virtual machine table. A VMID of 127 generally represents the service console. Type Integer (Counter) MAC Address attribute MAC address of the virtual machine s virtual NIC. Type String Chapter 5. Attributes reference 41

56 Number of Pkts Transmitted attribute Number of packets transmitted on this NIC since the network module was loaded. Type Integer (Counter) KB Transmitted Rate attribute Rate of network traffic in kilobytes per second sent from this NIC. Type Integer (rate of change between successive values) Number of Pkts Received attribute Number of packets received on this NIC since the network module was loaded. Type Integer (Counter) KB Received Rate attribute Rate of network traffic in kilobytes per second received on this NIC. Type Integer (rate of change between successive values) Performance Object Status attribute group Historical Attribute Contains the status of the performance objects collected for this application. When data cannot be collected for a table the application may be degraded, the corresponding part of the application may not be installed, configured or running, or the monitoring for the application may be impaired. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the Performance Object Status attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type Time Query Name attribute The name of the attribute group. 42 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

57 Type String Object Name attribute The name of the performance object. Type String Object Type attribute The type of the performance object. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: WMI(0), PERFMON(1), WMI_ASSOCIATION_GROUP(2), SNMP(4), SHELL COMMAND(5) or JOINED GROUPS(6) Any other values will display the numeric value in the Tivoli Enterprise Portal. Object Status attribute The status of the performance object. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: ACTIVE (0) or INACTIVE (1). Any other values will display the numeric value in the Tivoli Enterprise Portal. Error Code attribute The error code associated with the status. When the group is ACTIVE this will be NO ERROR. Other values allow you to verify the operation of the agent. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: When the group is ACTIVE this will be NO ERROR (0). Other values allow you to verify the operation of the agent. They are: GENERAL ERROR (1), OBJECT NOT FOUND (2), COUNTER NOT FOUND (3), NAMESPACE ERROR (4), OBJECT CURRENTLY UNAVAILABLE (5), COM LIBRARY INIT FAILURE (6), SECURITY INIT FAILURE (7), PROXY SECURITY FAILURE (9), NO INSTANCES RETURNED (10) ASSOCIATOR QUERY FAILED (11), REFERENCE QUERY FAILED (12), NO RESPONSE RECEIVED(13), CANNOT FIND JOINED QUERY(14), CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULT(15), CANNOT FIND JOIN ATTRIBUTE IN QUERY 2 RESULT(16), QUERY 1 NOT A SINGLETON(17), QUERY 2 NOT A SINGLETON(18), NO INSTANCES RETURNED IN QUERY 1(19), NO INSTANCES RETURNED IN QUERY 2(20), CANNOT_FIND_ROLLUP_QUERY(21), CANNOT_FIND_ROLLUP_ATTRIBUTE(22). Any other values will display the numeric value in the Tivoli Enterprise Portal. Chapter 5. Attributes reference 43

58 System attribute group Historical Attribute Contains system level metrics for the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the System attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Product Name attribute The VMware product name. Type String Product Version attribute The VMware product version. Type String Product OID attribute The version specific OID for the product in the VMware SNMP MIB. Type String Product Build attribute The build number of the VMware product. Type String Kernel Loaded attribute Indicates if the vmkernal is loaded. Type String Number of CPUs attribute Number of logical CPUs on the system. This represents the number 44 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

59 System CPU attribute group Historical Attribute of logical CPUs seen on the VMware ESX Server, this may differ from the number of physical CPUs present if hyperthreading is on. Type Integer (Counter) This attribute group contains metrics for the CPU utilization of the VMware ESX Server If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the System CPU attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute The local time at the agent when the data was collected. Type String Physical CPU attribute This is the percent of cpu utilized per physical cpu on the VMware ESX Server. Type Integer (Counter) Virtual Machines attribute group Historical Attribute Contains metrics that provide an overview of the virtual machines that have been configured on the VMware ESX server. If the warehouse default setting is enabled, data for this attribute group is not stored in the warehouse. group This attribute group is not part of the default historical group. descriptions The following list contains information about each attribute in the Virtual Machines attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Chapter 5. Attributes reference 45

60 Timestamp attribute The local time at the agent when the data was collected. Type String VM Index attribute The snmp index number for this virtual machine. Type Integer (Counter) VM Name attribute The display name for this virtual machine. Type String VM Config File attribute - This attribute is a key attribute. Fully qualified configuration file name for this virtual machine. Type String VM OS attribute Operating system running on this virtual machine. Type String VM Memory attribute Memory configured for this virtual machine in MB. Type Integer (Counter) VM State attribute Virtual machine state. Type String VM VMID attribute The ID assigned to a running virtual machine by the vmkernel. Type Integer with enumerated values. The strings are displayed in the Tivoli Enterprise Portal, the warehouse and queries will return the numbers. The defined values are: NONE (-1) Any other values will display the numeric value in the Tivoli Enterprise Portal. VM Guest State attribute Guest operating system state. A value of unknown and a value of off for VM State indicates that the guest OS is shut down, whereas unknown and a value of on for the VM State indicates that the VM does not have a guest OS installed. Type String 46 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

61 VM File System attribute group Historical Attribute This attribute group contains details of the virtual machine filesystem - /vmfs. It lists all the virtual disks and swap files configured on the VMware ESX Server. If the warehouse default setting is enabled, data for this attribute group is stored in the warehouse. group This attribute group is part of the default historical group. descriptions The following list contains information about each attribute in the VM File System attribute group: Node attribute - This attribute is a key attribute. The managed system name of the agent. Type String Timestamp attribute Type Size attribute The local time at the agent when the data was collected. String This is the size of the file in kilobytes. Type Integer (Counter) Name attribute - This attribute is a key attribute. This is the name of the file. Type String Disk capacity planning for historical data Disk capacity planning for a monitoring agent is a prediction of the amount of disk space to be consumed for each attribute group whose historical data is being collected. Required disk storage is an important factor to consider when you are defining data collection rules and your strategy for historical data collection. The tables in this appendix provide the following information required to calculate disk space for the IBM Tivoli Monitoring, V6.1 component software: v Table is the table name as it would appear in the warehouse database, if the attribute group is configured to be written to the warehouse. v Attribute group is the name of the attribute group as it will appear in the warehouse configuration panel. v Bytes per instance (agent) is an estimate of the record length for each row or instance written to the agent disk for historical data collection. This estimate can be used for agent disk space planning purposes. Chapter 5. Attributes reference 47

62 v Database bytes per instance (warehouse) is an estimate of the record length for detailed records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Detailed records are those that have been uploaded from the agent for long-term historical data collection. This estimate can be used for warehouse disk space planning purposes. v Aggregate bytes per instance (warehouse) is an estimate of the record length for aggregate records written to the warehouse database, if the attribute group is configured to be written to the warehouse. Aggregate records are created by the Summarization agent for attribute groups that have been configured for summarization. This estimate can be used for warehouse disk space planning purposes. In addition to the information in the tables, you must know the number of instances of data that you plan to collect. An attribute group can have single or multiple instances of data depending on the application environment that is being monitored. For example, if your attribute group is monitoring each processor in your computer and you have a dual processor computer, the number of instances is 2. The following table contains capacity planning information for the data logged by the resource models defined by the VMware component software. Table 7. Capacity planning for historical data logged by component VMware Table Attribute group Bytes per instance (agent) Database bytes per instance (warehouse) Aggregate bytes per instance (warehouse) KQVAVAIL KQV_AVAILABILITY KQVCPUBASE KQV_CPU_BASE KQVCPULAVG KQV_CPU_LOAD_AVERAGE KQVCPUVM KQV_CPU_VM KQVDSKBASE KQV_DISK_BASE KQVDSKUSG KQV_DISK_USAGE KQVDISKVM KQV_DISK_VM KQVMEMBASE KQV_MEMORY_BASE KQVMEMTBL KQV_MEMORY_PER_VM KQVMEMVM KQV_MEMORY_VM KQVNETBASE KQV_NETWORK_BASE KQVNETVM KQV_NETWORK_VM KQVPOBJST KQV_PERFORMANCE_OBJECT_STATUS KQVSYSTEM KQV_SYSTEM KQVCPUSYS KQV_SYSTEM_CPU KQVVM KQV_VIRTUAL_MACHINES KQVVMFS KQV_VM_FILE_SYSTEM For more information about historical data collection, see the IBM Tivoli Monitoring Administrator s Guide. 48 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

63 Chapter 6. Situations reference This chapter contains an overview of situations, references for detailed information about situations, and descriptions of the predefined situations included in this monitoring agent. About situations A situation is a logical expression involving one or more system conditions. Situations are used to monitor the condition of systems in your network. You can manage situations from Tivoli Enterprise Portal by using the Situation editor. The monitoring agents that you use to monitor your system environment are delivered with a set of predefined situations that you can use as-is or you can create new situations to meet your requirements. Predefined situations contain attributes that check for system conditions common to many enterprises. Using predefined situations can improve the speed with which you can begin using the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. You can examine and, if necessary, change the conditions or values being monitored by a predefined situation to those best suited to your enterprise. You can display predefined situations and create your own situations using the Situation editor. The left frame of the Situation editor initially lists the situations associated with the Navigator item that you selected. When you click a situation name or create a new situation, the right frame opens with the following tabs: Condition Condition being tested Distribution List of managed systems (operating systems, subsystems, or applications) to which the situation can be distributed. All of the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent managed systems are assigned by default. Expert Action advice Comments and instructions to be read in the event workspace Command to be sent to the system More information about situations IBM Tivoli Monitoring User s Guide contains more information about predefined and custom situations and how to use them to respond to alerts. For a list of the predefined situations for this monitoring agent and a description of each situation, refer to the Predefined situations section below and the information in that section for each individual situation. Copyright IBM Corp. 2005,

64 Predefined situations This monitoring agent contains the following predefined situations, which are organized by Navigator item: v VMware ESX v v v v v Not applicable Availability KQV_VMware_ESX_Server_Down CPU KQV_VMKernel_Not_Loaded KQV_CPU_Phy_Utilization_High KQV_CPU_Avg_Underutilized KQV_CPU_Avg_Overutilized Disk KQV_Filesystem_Freespace_Low KQV_DiskRead_Activity_High KQV_DiskWrite_Activity_High Memory KQV_Memory_Used_COS_High KQV_Memory_Available_Low Network KQV_NetworkTX_Activity_High KQV_NetworkRX_Activity_High v Virtual Machines KQV_Virtual_Machine_Off KQV_Virtual_Machine_Stuck KQV_Virtual_Machine_Unknown KQV_Virtual_Machine_Suspended The remaining sections of this chapter contain descriptions of each of these situations. The situations are organized by Navigator item. The following information is provided about each situation: Information about the conditions that the situation tests Formula Syntax that contains one or more logical expressions describing the conditions for the situation to monitor Run at startup Whether the situation starts monitoring as soon as it is saved, when the managed system to which it is distributed comes online, and when the hub Tivoli Enterprise Management Server has been restarted, or whether the situation needs to be started manually from the Situation editor Sampling interval Number of seconds that elapses between one sample of data that the monitoring agent collects for the server and the next sample Situation persistence Whether the conditions specified in the situation evaluate to true for the 50 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

65 VMware ESX Navigator item Availability Navigator item defined number of occurrences in a row before the situation is raised. The default of 1 means no persistence checking takes place. Severity Severity of the event: Warning, Informational, or Critical Clearing conditions Controls when a true situation closes: after a period of time, when another situation is true, or whichever occurs first if both are selected. There are no predefined situations for this Navigator item. KQV_VMware_ESX_Server_Down situation The Status of the VMware ESX Server is unreachable. Formula *IF ( ( *SCAN KQV_AVAILABILITY.Name *EQ KQV_VMwareESX_Status.bat *AND *VALUE KQV_AVAILABILITY.Status *EQ FAILED ) *OR ( *SCAN KQV_AVAILABILITY.Name *EQ KQV_VMwareESX_Status.sh *AND *VALUE KQV_AVAILABILITY.Status *EQ FAILED ) ) See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical CPU Navigator item Clearing conditions The situation clears when the condition becomes false. KQV_VMKernel_Not_Loaded situation The vmkernel is not loaded Formula *IF *SCAN KQV_SYSTEM.Kernel_Loaded *EQ no Chapter 6. Situations reference 51

66 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_CPU_Phy_Utilization_High situation The CPU utilization is very high. Formula *IF *VALUE KQV_SYSTEM_CPU.Physical_CPU *GT 95 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_CPU_Avg_Underutilized situation The CPU utilization is low. Formula *IF *VALUE KQV_CPU_LOAD_AVERAGE.Load_Avg_Five_Min *LT 0.5 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. 52 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

67 Run at startup Yes Sampling interval 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Warning Clearing conditions The situation clears when the condition becomes false. KQV_CPU_Avg_Overutilized situation The CPU is overloaded. Formula *IF *VALUE KQV_CPU_LOAD_AVERAGE.Load_Avg_Five_Min *GT 1.0 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Disk Navigator item Clearing conditions The situation clears when the condition becomes false. KQV_Filesystem_Freespace_Low situation The filesystem is almost full. Formula *IF *VALUE KQV_DISK_USAGE.Percent_Used *GT 90 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Chapter 6. Situations reference 53

68 Run at startup Yes Sampling interval 30 minutes Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_DiskRead_Activity_High situation The disk read activity is high. Formula *IF *VALUE KQV_DISK_VM.KB_Read_per_Sec *GT 5000 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_DiskWrite_Activity_High situation The disk write activity is high. Formula *IF *VALUE KQV_DISK_VM.KB_Write_per_Sec *GT 5000 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes 54 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

69 Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Memory Navigator item Clearing conditions The situation clears when the condition becomes false. KQV_Memory_Used_COS_High situation Amount of available free memory for the console OS (COS) is low. Formula *IF *VALUE KQV_MEMORY_BASE.Pct_Mem_Used_by_COS *GT 90 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_Memory_Available_Low situation Amount of available free memory for the VMware sever is low. Formula *IF *VALUE KQV_MEMORY_BASE.Pct_Total_Free_Memory *LT 10 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Chapter 6. Situations reference 55

70 Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Warning Network Navigator item Clearing conditions The situation clears when the condition becomes false. KQV_NetworkTX_Activity_High situation The network transmit activity is high. Formula *IF *VALUE KQV_NETWORK_VM.KB_Transmitted_Rate *GT 5000 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_NetworkRX_Activity_High situation The network receive activity is high. Formula *IF *VALUE KQV_NETWORK_VM.KB_Received_Rate *GT 5000 See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes 56 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

71 Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. Virtual Machines Navigator item KQV_Virtual_Machine_Off situation The virtual machine is powered off. Formula *IF *SCAN KQV_VIRTUAL_MACHINES.VM_State *EQ off See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Warning Clearing conditions The situation clears when the condition becomes false. KQV_Virtual_Machine_Stuck situation The virtual machine is in a stuck state. Formula *IF *SCAN KQV_VIRTUAL_MACHINES.VM_State *EQ stuck See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Chapter 6. Situations reference 57

72 Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_Virtual_Machine_Unknown situation The virtual machine is in an unknown state. Formula *IF *SCAN KQV_VIRTUAL_MACHINES.VM_State *EQ unknown See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Critical Clearing conditions The situation clears when the condition becomes false. KQV_Virtual_Machine_Suspended situation The virtual machine is in a suspended state. Formula *IF *SCAN KQV_VIRTUAL_MACHINES.VM_State *EQ suspended See Attribute groups and attributes for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent on page 23 for descriptions of the attributes in this formula. Run at startup Yes Sampling interval 1 minute 58 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

73 Situation persistence The number of times the conditions of the situation must occur for the situation to be true is 1. Severity Warning Clearing conditions The situation clears when the condition becomes false. Chapter 6. Situations reference 59

74 60 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

75 Chapter 7. Take Action commands reference This chapter contains an overview of Take Action commands, references for detailed information about Take Action commands, and descriptions of the Take Action commands included in this monitoring agent, if any. About Take Action commands Take Action commands can be run from the desktop or included in a situation or a policy. When included in a situation, the command runs when the situation becomes true. A Take Action command in a situation is also referred to as reflex automation. When you enable a Take Action command in a situation, you automate a response to system conditions. For example, you can use a Take Action command to send a command to restart a process on the managed system or to send a text message to a cell phone. Advanced automation uses policies to perform actions, schedule work, and automate manual tasks. A policy comprises a series of automated steps called activities that are connected to create a workflow. After an activity is completed, Tivoli Enterprise Portal receives return code feedback, and advanced automation logic responds with subsequent activities prescribed by the feedback. A basic Take Action command displays the return code of the operation in a message box that is displayed after the action completes. After you close this window, no further information is available for this action. More information about Take Action commands For more information about working with Take Action commands, see IBM Tivoli Monitoring User s Guide. For a list of the Take Action commands for this monitoring agent and a description of each command, refer to the Predefined Take Action commands section below and the information in that section for each individual command. Predefined Take Action commands This monitoring agent contains the following Take Action commands: v Configure SSH Windows v Start Virtual Machine v Stop Virtual Machine The remaining sections of this chapter contain descriptions of these Take Action commands, which are listed alphabetically. The following information is provided about each Take Action command: Which actions the command performs on the system to which is it sent Copyright IBM Corp. 2005,

76 Arguments List of parameters, if any, for the Take Action command with a short description and default value for each one Return Configure SSH Windows action codes Information that the Take Action command returns The task tests if the client provided during the agent configuration is compatible for data collection and configures the ssh-client to start the data collection process for the VMware ESX Agent. Return codes Return Code: 0 Return Code Type: OK Platforms: windows Message ID: KQV9001I Message: The SSH Client is working and is compatible. Return Code: 2 Return Code Type: GENERAL_ERROR Platforms: windows Message ID: KQV9002E Message: The SSH Client you are trying to use could not be configured to collect data. Return Code: 2 Return Code Type: GENERAL_ERROR Platforms: linux Message ID: KQV9004E Message: This task is supported on Windows platform only. Start Virtual Machine action Start a specific virtual machine. The name of the virtual machine can be provided either by typing it in or by navigating to the Virtual Machines workspace and selecting the virtual machine to be started from the Virtual Machine Overview view. Arguments v Name: KQV_Virtual_Machines.VM_Config_File v : This is the name of the configuration file of the virtual machine to be started. v Default: Return codes Return Code: 0 Return Code Type: OK Platforms: windows, linux 62 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

77 Stop Virtual Machine action Message ID: KQV0001I Message: The virtual machine was successfully started. Return Code: 2 Return Code Type: GENERAL_ERROR Platforms: windows, linux Message ID: KQV0003E Message: Could not perform the requested start action. Return Code: 6 Return Code Type: ALREADY_RUNNING Platforms: windows, linux Message ID: KQV0002I Message: The virtual machine is already started. Stop a specific Virtual Machine.The name of the virtual machine can be provided either by typing it in or by navigating to the Virtual Machines workspace and selecting the virtual machine to be started from the Virtual Machine Overview view. Arguments v Name: KQV_Virtual_Machines.VM_Config_File v : This is the name of the configuration file of the virtual machine to be stopped. v Default: Return codes Return Code: 0 Return Code Type: OK Platforms: windows, linux Message ID: KQV0004I Message: The virtual machine was successfully stopped. Return Code: 2 Return Code Type: GENERAL_ERROR Platforms: windows, linux Message ID: KQV0006E Message: Could not perform the requested stop action. Return Code: 4 Return Code Type: NOT_RUNNING Platforms: windows, linux Message ID: KQV0005I Message: The virtual machine is already stopped. Chapter 7. Take Action commands reference 63

78 64 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

79 Chapter 8. Policies reference This chapter contains an overview of policies, references for detailed information about policies, and descriptions of the predefined policies included in this monitoring agent, if any. About policies Policies are an advanced automation technique for implementing more complex workflow strategies than you can create through simple automation. A policy is a set of automated system processes that can perform actions, schedule work for users, or automate manual tasks. You use the Workflow Editor to design policies. You control the order in which the policy executes a series of automated steps, which are also called activities. Policies are connected to create a workflow. After an activity is completed, Tivoli Enterprise Portal receives return code feedback and advanced automation logic responds with subsequent activities prescribed by the feedback. More information about policies This agent does not provide predefined policies. For more information about working with policies, see the IBM Tivoli Monitoring User s Guide. For information about using the Workflow Editor, see the IBM Tivoli Monitoring Administrator s Guide or the Tivoli Enterprise Portal online help. Copyright IBM Corp. 2005,

80 66 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

81 Appendix A. IBM Tivoli Enterprise Console event mapping Each event class corresponds to an attribute group in the IBM Tivoli Enterprise Console. For a description of the event slots for each event class, see the list below. For more information about mapping attribute groups to event classes, see the IBM Tivoli Monitoring Administrator s Guide. Generic event mapping provides useful event class and attribute information for situations that do not have specific event mapping defined. BAROC files are found on the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB (that is, install_dir/cms/teclib for Windows systems and install_dir/tables/ TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console event synchronization provides a collection of ready-to-use rule sets that you can deploy with minimal configuration. Be sure to install IBM Tivoli Enterprise Console event synchronization to access the correct Sentry.baroc, which is automatically included during base configuration of IBM Tivoli Enterprise Console rules if you indicate that you want to use an existing rulebase. See the IBM Tivoli Monitoring Installation and Setup Guide for details. Each of the event classes is a child of KQV_Base. The KQV_Base event class can be used for generic rules processing for any event from the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. For events generated by situations on the AVAILABILITY attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_AVAILABILITY class. This class contains the following slots: v node: STRING v timestamp: STRING v application_component: STRING v name: STRING v kqv_status: STRING v kqv_status_enum: STRING v full_name: STRING v type: INTEGER v virtual_size: INTEGER v page_faults_per_sec: INTEGER v working_set_size: INTEGER v thread_count: INTEGER v pid: INTEGER v percent_privileged_time: INTEGER v percent_user_mode_time: INTEGER v percent_processor_time: INTEGER v command_line: STRING v functionality_test_status: INTEGER v functionality_test_status_enum: STRING v functionality_test_message: STRING Copyright IBM Corp. 2005,

82 For events generated by situations on the CPU_BASE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_CPU_BASE class. This class contains the following slots: v node: STRING v timestamp: STRING v cpu_vmid: INTEGER v cpu_share: INTEGER v cpu_utilization_rate: INTEGER For events generated by situations on the CPU_LOAD_AVERAGE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_CPU_LOAD_AVERAGE class. This class contains the following slots: v node: STRING v timestamp: STRING v load_avg_one_min: INTEGER v load_avg_five_min: INTEGER v load_avg_fifteen_min: INTEGER For events generated by situations on the CPU_VM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_CPU_VM class. This class contains the following slots: v node: STRING v timestamp: STRING v vm_index: INTEGER v vm_name: STRING v vm_config_file: STRING v vm_os: STRING v vm_memory: INTEGER v vm_state: STRING v vm_vmid: INTEGER v vm_vmid_enum: STRING v vm_guest_state: STRING v cpu_vmid: INTEGER v cpu_share: INTEGER v cpu_utilization_rate: INTEGER For events generated by situations on the DISK_BASE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_DISK_BASE class. This class contains the following slots: v node: STRING v timestamp: STRING v hba_index: INTEGER v hba_name: STRING v vmid: INTEGER v disk_shares: INTEGER v number_of_reads: INTEGER v kb_read_per_sec: INTEGER v number_of_writes: INTEGER 68 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

83 v kb_write_per_sec: INTEGER For events generated by situations on the DISK_USAGE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_DISK_USAGE class. This class contains the following slots: v node: STRING v timestamp: STRING v filesystem: STRING v total_blocks: INTEGER v blocks_used: INTEGER v blocks_available: INTEGER v percent_used: INTEGER v mount_point: STRING For events generated by situations on the DISK_VM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_DISK_VM class. This class contains the following slots: v node: STRING v timestamp: STRING v vm_index: INTEGER v vm_name: STRING v vm_config_file: STRING v vm_os: STRING v vm_memory: INTEGER v vm_state: STRING v vm_vmid: INTEGER v vm_vmid_enum: STRING v vm_guest_state: STRING v hba_index: INTEGER v hba_name: STRING v vmid: INTEGER v disk_shares: INTEGER v number_of_reads: INTEGER v kb_read_per_sec: INTEGER v number_of_writes: INTEGER v kb_write_per_sec: INTEGER For events generated by situations on the MEMORY_BASE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_MEMORY_BASE class. This class contains the following slots: v node: STRING v timestamp: STRING v total_memory: INTEGER v consoleos_memory: INTEGER v memory_available: INTEGER v pct_mem_used_by_cos: INTEGER v pct_mem_not_used_by_cos: INTEGER Appendix A. IBM Tivoli Enterprise Console event mapping 69

84 v pct_total_free_memory: INTEGER For events generated by situations on the MEMORY_PER_VM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_MEMORY_PER_VM class. This class contains the following slots: v node: STRING v timestamp: STRING v vmid: INTEGER v memory_shares: INTEGER v memory_configured: INTEGER v memory_utilized: INTEGER For events generated by situations on the MEMORY_VM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_MEMORY_VM class. This class contains the following slots: v node: STRING v timestamp: STRING v vm_index: INTEGER v vm_name: STRING v vm_config_file: STRING v vm_os: STRING v vm_memory: INTEGER v vm_state: STRING v vm_vmid: INTEGER v vm_vmid_enum: STRING v vm_guest_state: STRING v vmid: INTEGER v memory_shares: INTEGER v memory_configured: INTEGER v memory_utilized: INTEGER For events generated by situations on the NETWORK_BASE attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_NETWORK_BASE class. This class contains the following slots: v node: STRING v timestamp: STRING v network_name: STRING v vmid: INTEGER v mac_address: STRING v number_of_pkts_transmitted: INTEGER v kb_transmitted_rate: INTEGER v number_of_pkts_received: INTEGER v kb_received_rate: INTEGER For events generated by situations on the NETWORK_VM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_NETWORK_VM class. This class contains the following slots: v node: STRING 70 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

85 v timestamp: STRING v vm_index: INTEGER v vm_name: STRING v vm_config_file: STRING v vm_os: STRING v vm_memory: INTEGER v vm_state: STRING v vm_vmid: INTEGER v vm_vmid_enum: STRING v vm_guest_state: STRING v network_name: STRING v vmid: INTEGER v mac_address: STRING v number_of_pkts_transmitted: INTEGER v kb_transmitted_rate: INTEGER v number_of_pkts_received: INTEGER v kb_received_rate: INTEGER For events generated by situations on the PERFORMANCE_OBJECT_STATUS attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_PERFORMANCE_OBJECT_STATUS class. This class contains the following slots: v node: STRING v timestamp: STRING v query_name: STRING v object_name: STRING v object_type: INTEGER v object_type_enum: STRING v object_status: INTEGER v object_status_enum: STRING v error_code: INTEGER v error_code_enum: STRING For events generated by situations on the SYSTEM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_SYSTEM class. This class contains the following slots: v node: STRING v timestamp: STRING v product_name: STRING v product_version: STRING v product_oid: STRING v product_build: STRING v kernel_loaded: STRING v number_of_cpus: INTEGER Appendix A. IBM Tivoli Enterprise Console event mapping 71

86 For events generated by situations on the SYSTEM_CPU attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_SYSTEM_CPU class. This class contains the following slots: v node: STRING v timestamp: STRING v physical_cpu: INTEGER For events generated by situations on the VIRTUAL_MACHINES attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_VIRTUAL_MACHINES class. This class contains the following slots: v node: STRING v timestamp: STRING v vm_index: INTEGER v vm_name: STRING v vm_config_file: STRING v vm_os: STRING v vm_memory: INTEGER v vm_state: STRING v vm_vmid: INTEGER v vm_vmid_enum: STRING v vm_guest_state: STRING For events generated by situations on the VM_FILE_SYSTEM attribute group, Tivoli Enterprise Console events will be sent using the ITM_KQV_VM_FILE_SYSTEM class. This class contains the following slots: v node: STRING v timestamp: STRING v size: INTEGER v name: STRING 72 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

87 Appendix B. Problem determination This appendix explains how to troubleshoot the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. Troubleshooting, or problem determination, is the process of determining why a certain product is malfunctioning. Note: You can resolve some problems by ensuring that your system matches the system requirements listed in Chapter 2, Requirements for the monitoring agent, on page 5. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Also see Support information on page 89 for other problem-solving options. Gathering product information for IBM Software Support Before contacting IBM Software Support about a problem you are experiencing with this product, gather the following information that relates to the problem: Table 8. Information to gather before contacting IBM Software Support Information type Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectory on the host computer. See Trace logging on page 74 for lists of all trace log files and their locations. See the IBM Tivoli Monitoring User s Guide for general information about the IBM Tivoli Monitoring environment. VMware ESX Server information v Version number and patch level Operating system Operating system version number and patch level Messages Messages and other information displayed on the screen Version numbers for IBM Tivoli Monitoring Version number of the following members of the monitoring environment: v IBM Tivoli Monitoring. Also provide the patch level, if available. v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent Screen captures Screen captures of incorrect output, if any. (UNIX only) Core dump files If the system stops on UNIX systems, collect the core dump file from install_dir/bin directory, where install_dir is the directory oath where you installed the monitoring agent. Upload files for review to the following FTP site: ftp.emea.ibm.com. Log in as anonymous and place your files in the directory that corresponds to the IBM Tivoli Monitoring component that you use. See Contacting IBM Software Support on page 91 for more information about working with IBM Software Support. Built-in problem determination features The primary troubleshooting feature in the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent is logging. Logging refers to the text messages and trace data generated by the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. Messages and trace data are sent to a file. Trace data captures transient information about the current operating environment when a component or application fails to operate as designed. IBM Software Copyright IBM Corp. 2005,

88 Support personnel use the captured trace information to determine the source of an error or unexpected condition. See Trace logging for more information. Problem classification The following types of problems might occur with the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: v Installation and configuration v General usage and operation v Display of monitoring data v Take Action commands Trace logging This appendix provides symptom descriptions and detailed workarounds for these problems, as well as describing the logging capabilities of the monitoring agent. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Trace logs capture information about the operating environment when component software fails to operate as intended. The principal log type is the RAS (Reliability, Availability, and Serviceability) trace log. These logs are in the English language only. The RAS trace log mechanism is available for all components of IBM Tivoli Monitoring. Most logs are located in a logs subdirectory on the host computer. See the following sections to learn how to configure and use trace logging: v Principal trace log files on page 75 v Examples: using trace logs on page 77 v Setting RAS trace parameters on page 78 Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as "RAS1". IBM Software Support uses the information captured by trace logging to trace a problem to its source or to determine why an error occurred. The default configuration for trace logging, such as whether trace logging is enabled or disabled and trace level, depends on the source of the trace logging. Trace logging is always enabled. Overview of log file management Table 9 on page 76 provides the names, locations, and descriptions of RAS1 log files. The log file names adhere to the following naming convention: hostname_productcode_program_timestamp-nn.log where: v hostname is the host name of the machine on which the monitoring component is running. v productcode is the two-character product code. For IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, the product code is qv. 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. 74 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

89 v nn is a rolling log suffix. See Examples of trace logging for details of log rolling. Examples of trace logging For example, if a VMware ESX Server monitoring agent is running on computer server01, the RAS log file for the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent might be named as follows: server01_qv_kqvagent_437fc59-01.log For long-running programs, the nn suffix is used to maintain a short history of log files for that startup of the program. For example, the kqvagent program might have a series of log files as follows: server01_qv_kqvagent_437fc59-01.log server01_qv_kqvagent_437fc59-02.log server01_qv_kqvagent_437fc59-03.log As the program runs, the first log (nn=01) is preserved because it contains program startup information. The remaining logs roll." In other words, when the set of numbered logs reach a maximum size, the remaining logs are overwritten in sequence. Each time a program is started, a new timestamp is assigned to maintain a short program history. For example, if the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent is started twice, it might have log files as follows: server01_qv_kqvagent_437fc59-01.log server01_qv_kqvagent_437fc59-02.log server01_qv_kqvagent_437fc59-03.log server01_qv_kqvagent_537fc59-01.log server01_qv_kqvagent_537fc59-02.log server01_qv_kqvagent_537fc59-03.log Each program that is started has its own log file. For example, the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent would have agent logs in this format: server01_qv_kqvagent_437fc59-01.log Other logs, such as logs for Take Action command logs, have a similar syntax as in the following example: host_productcode_takeactioncommand.log Only one log file is produced per Take Action command. Note: When you communicate with IBM Software Support, you must capture and send the RAS1 log that matches any problem occurrence that you report. Principal trace log files Table 9 on page 76 contains locations, file names, and descriptions of trace logs that can help determine the source of problems with agents. Appendix B. Problem determination 75

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

91 Table 9. Trace log files for troubleshooting agents (continued) System where log is located On the computer that hosts the monitoring agent File name and path The RAS1 log files are named hostname_qv_kqvagent_timestamp-nn.log and are located in the install_dir\tmaitm6\ logs path. Note: File names for RAS1 logs include a hexadecimal time stamp. The *.LG0 file is located in the install_dir\tmaitm6\logs path. The host_productcode_takeactioncommand.log file (where takeactioncommand is the name of the Take Action command) is located in the install_dir\tmaitm6\logs path. Traces activity of the monitoring agent. Shows whether agent was able to connect to the monitoring server. Shows which situations are started and stopped, and shows other events while the agent is running. A new version of this file is generated every time the agent is restarted. IBM Tivoli Monitoring generates one backup copy of the *.LG0 file with the tag.lg1. View.LG1 to learn the following details regarding the previous monitoring session: v Status of connectivity with the monitoring server. v Situations that were running. v The success or failure status of Take Action commands. Traces activity each time a Take Action command runs. For example, when a hypothetical start_command Take Action command runs, IBM Tivoli Monitoring would generate a start_command.log file. Definitions of variables: timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows: yyyymmdd hhmm HEXtimestamp is a hexadecimal representation of the time at which the process was started. install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can represent a path on the computer that host the monitoring system, the monitoring agent, or the portal. instance refers to the name of the database instance that you are monitoring. hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs. nn represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first is always retained, since it includes configuration parameters. productcode specifies the product codes, for example, um for Universal Agent or nt for Windows. See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the complete set of trace logs that are maintained on the monitoring server. Examples: using trace logs Typically IBM Software Support applies specialized knowledge to analyze trace logs to determine the source of problems. However, you can open trace logs in a text editor to learn some basic facts about your IBM Tivoli Monitoring environment. The following examples are from the Tivoli Enterprise Monitoring Server log. Example one This excerpt shows the typical log for a failed connection between a monitoring agent and a monitoring server with the host name server1a: (Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006, "location server unavailable", ncs/kdc1_stc_server_unavailable (Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to Appendix B. Problem determination 77

92 broker at ip.pipe:: status=0, "success", ncs/kdc1_stc_ok (Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable to find running CMS on CT_CMSLIST <IP.PIPE:#server1a> Example two The following excerpts from the trace log for the monitoring server show the status of an agent, identified here as Remote node. The name of the computer where the agent is running is SERVER5B: (42C039F A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:KQV is ON-LINE.... (42C3079B A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:KQV is OFF-LINE. Key points regarding the preceding excerpt: v The monitoring server appends the KQV product code to the server name to form a unique name (SERVER5B:KQV) for this instance of IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent. This unique name enables you to distinguish multiple monitoring products that might be running on SERVER5B. v The log shows when the agent started (ON-LINE) and later stopped (OFF-LINE) in the environment. v For the sake of brevity an ellipsis (...) represents the series of trace log entries that were generated while the agent was running. v Between the ON-LINE and OFF-LINE log entries, the agent was communicating with the monitoring server. v The ON-LINE and OFF-LINE log entries are always available in the trace log. All trace levels that are described in Setting RAS trace parameters provide these entries. On Windows, you can use the following alternate method to view trace logs: 1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed. 2. Right-click a component and select Advanced > View Trace Log in the pop-up menu. For example, if you want to view the trace log of the VMware ESX Server agent, right-click on the name of the that agent in the window. You can also use the viewer to access remote logs. Note: The viewer converts time stamps in the logs to a format that is easier to read. Setting RAS trace parameters Objective Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules. Background Information The IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent uses RAS1 tracing and generates the logs described in Table 9 on page 76. The default RAS1 trace level is ERROR. Before you begin See Overview of log file management on page 74 to ensure that you understand log rolling and can reference the correct log files when you manage log file generation. 78 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

93 After you finish Monitor the size of the logs directory. Default behavior can generate a total of 45 to 60 MB for each agent that is running on a computer. For example, each database instance that you monitor could generate 45 to 60 MB of log data. See the "Procedure" section to learn how to adjust file size and numbers of log files to prevent logging activity from occupying too much disk space. Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files which are pruned automatically, other log types can grow indefinitely, for example, the logs in Table 9 on page 76 that include a process ID number (PID). Consider using collector trace logs as an additional source of problem determination information. Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space. Procedure Specify RAS1 trace options in the install_dir\tmaitm6\kqvenv file on Windows or the install_dir/config/kqv.ini file on UNIX systems. Use the graphical user interface to set trace options: 1. Open the Manage Tivoli Enterprise Monitoring Services window. 2. Right-click the icon of the monitoring agent whose logging you want to modify. 3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed. 4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string. The selections are as follows: v General error tracing. KBB_RAS1=ERROR v Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL) Note: As this example shows, you can set multiple RAS tracing options in a single statement. 5. Modify the value for 'Maximum Log Size Per File (MB)" to change the log file size (changes LIMIT value). 6. Modify the value for 'Maximum Number of Log Files Per Session" to change the number of log files per startup of a program (changes COUNT value). 7. Modify the value for 'Maximum Number of Log Files Total" to change the number of log files for all startups of a program (changes MAXFILES value). 8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you diagnose communications and connectivity problems between the monitoring agent and the monitoring server. Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space. 9. Click OK. You see a message reporting a restart of the monitoring agent so that your changes take effect. Appendix B. Problem determination 79

94 Problems and workarounds Alternate method to edit trace logging parameters: 1. Open the trace options file: install_dir\tmaitm6\kqvenv 2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. For example, if you want detailed trace logging, set the Maximum Tracing option:kbb_ras1=error (UNIT:kqz ALL) (UNIT:kra ALL) 3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files: v MAXFILES: the total number of files that are to be kept for all startups of a given program. Once this value is exceeded, the oldest log files are discarded. Default value is 9. v LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5. v IBM Software Support might guide you to modify the following parameters: COUNT: the number of log files to keep in the rolling cycle of one program startup. Default is 3. PRESERVE: the number of files that are not to be reused in the rolling cycle of one program startup. Default value is 1. Note: The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost. 4. Restart the monitoring agent so that your changes take effect. The following sections provide symptoms and workarounds for problems that might occur with the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: v Installation and configuration problem determination on page 80 v Agent problem determination on page 83 v Workspace problem determination on page 84 v Problem determination for remote deployment on page 84 v Situation problem determination on page 86 Note: You can resolve some problems by ensuring that your system matches the system requirements listed in Chapter 2, Requirements for the monitoring agent, on page 5. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Installation and configuration problem determination This section provides tables that show solutions for installation, configuration, and uninstallation problems. 80 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

95 Table 10. Problems and solutions for installation and configuration Problem (UNIX only) During a command-line installation, you choose to install a component that is already installed, and you see the following warning: WARNING - you are about to install the SAME version of "component_name" where component_name is the name of the component that you are attempting to install. Note: This problem affects UNIX command-line installations. If you monitor only Windows environments, you would see this problem if you choose to install a product component (for example, a monitoring server) on UNIX. A problem can arise when you install and configure a new monitoring agent to a computer where other agents are running as described in this example: v Agents are running on computer and communicating with a Tivoli Enterprise Monitoring Server, called TEMS1. v You install a new agent on the same computer and you want this agent to communicate with a different monitoring server, called TEMS2. v When you configure the new agent to communicate with TEMS2, all the existing agents are re-configured to communicate with TEMS2. Solution You must exit and restart the installation process. You cannot return to the list where you selected components to install. When you run the installer again, do not attempt to install any component that is already installed. You must reconfigure the previously existing agents to restore their communication connection with TEMS1. For example, you can right-click the row for a specific agent in the Manage Tivoli Enterprise Monitoring Services, and select Reconfigure. See the IBM Tivoli Monitoring Installation and Setup Guide for more information on reconfiguration. Diagnosing problems with product browse settings. When you have problems with browse settings, perform the following steps: A message similar to Unable to find running CMS on CT_CMSLIST in the log file is displayed. 1. Click on Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services is displayed. 2. Right-click the Windows agent and select Browse Settings. A text window is displayed. 3. Click Save As and save the information in the text file. If requested, you can forward this file to IBM Software Support for analysis. If a message similar to Unable to find running CMS on CT_CMSLIST is displayed in the Log file, the agent is not able to connect to the monitoring server. Confirm the following points: v Do multiple network interface cards (NICs) exist on the system? v If multiple NICs exist on the system, find out which one is configured for the monitoring server. Ensure that you specify the correct host name and port settings for communication in the IBM Tivoli Monitoring environment. Appendix B. Problem determination 81

96 Table 10. Problems and solutions for installation and configuration (continued) Problem Solution The system is experiencing high CPU usage. Agent process: View the memory usage of the KQVCMA process. If CPU usage seems to be excessive, recycle the monitoring agent. For the virtual server vmware agent, you must install the VMware Perl API (downloadable from the VMware website) that the agent uses to determine if the server the VMware ESX server is up or down. On Linux, while there is an install.sh, two libraries are not placed where the vmware-cmd can use them, and the API will not work out of the box. Network Cards: The network card configurations can decrease the performance of a system. Each of the stream of packets that a network card receives (assuming it is a broadcast or destined for the under-performing system) must generate a CPU interrupt and transfer the data through the I/O bus. If the network card in question is a bus-mastering card, work can be off-loaded and a data transfer between memory and the network card can continue without using CPU processing power. Bus-mastering cards are generally 32-bit and are based on PCI or EISA bus architectures. To correct the problem, copy the libraries to an appropriate place like /usr/lib. Table 11. General problems and solutions for uninstallation Problem On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire environment. Systems are inactive, show a status of OFFLINE and a dimmed appearance, and the way to remove inactive managed systems from the Enterprise navigation tree in the portal is not obvious. After the remote removal from the Tivoli Enterprise Portal of a running instance, the instance s name is still listed in the Start List. Solution Be sure that you follow the general uninstallation process described in theibm Tivoli Monitoring Installation and Setup Guide: 1. Uninstall monitoring agents first, as in the following examples: v Uninstall a single monitoring agent for a specific database. -OR- v Uninstall all instances of a monitoring product, such as IBM Tivoli Monitoring for Databases. 2. Uninstall IBM Tivoli Monitoring. When you want to remove a managed system from the navigation tree, right-click the appropriate workspace from which you want to remove the item, and select Remove managed system. The managed system will not reappear until it is reconnected. Bring up the configure list to remove the instance name from the Start list. Unique names for monitoring components IBM Tivoli Monitoring might not be able to generate a unique name for monitoring components due to the truncation of names that the product automatically generates. 82 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

97 If the agent supports multi-instances, IBM Tivoli Monitoring automatically creates a name for each monitoring component by concatenating the subsystem name, host name, and product code separated by colons (subsystem_name:hostname:kqv). Note: When you monitor a multinode system, such as a database, IBM Tivoli Monitoring adds a subsystem name to the concatenated name, typically a database instance name. The length of the name that IBM Tivoli Monitoring generates is limited to 32 characters. Truncation can result in multiple components having the same 32-character name. If this problem happens, shorten the hostname portion of the name as follows: 1. Open the configuration file for the monitoring agent, which is located in the following path: v On Windows: install_dir\tmaitm6\kproduct_codecma.ini. For example, the product code for the Monitoring Agent for Windows OS is NT. The file name for is KNTCMA.INI. v On UNIX and Linux: itm_home/config/product_code.ini and product_code.config. For example, the file names for the Monitoring Agent for UNIX OS is ux.ini and ux.config. 2. Find the line the begins with CTIRA_HOSTNAME=. 3. Type a new name for host name that is a unique, shorter name for the host computer. The final concatenated name including the subsystem name, new host name, and KQV, cannot be longer than 32 characters. Note: You must ensure that the resulting name is unique with respect to any existing monitoring component that was previously registered with the Tivoli Enterprise Monitoring Server. 4. Save the file. 5. Restart the agent. Agent problem determination This section lists problems that might occur with agents. Table 12. Agent problems and solutions Problem Log data accumulates too rapidly. When using the F1 key or selecting Help --> Contents and Index, you receive a message in your Microsoft Internet Explorer browser which states, It seems javascript is disabled in your browser, please enable it and reload again, or click here to view without javascript. If you select here, the Tivoli Enterprise Portal V6.1 Help is displayed, but the agent help is not. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Solution Check the RAS trace option settings, which are described in Setting RAS trace parameters on page 78. The trace options settings that you can set on the KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data. Ensure that the local site is added to the browser s trusted site and then enable the javascript. Appendix B. Problem determination 83

98 Table 12. Agent problems and solutions (continued) Problem If you want to receive multiple trace logs for separate invocations of the same Take Action command, leaving this setting on permanently fills the available disk space. Solution Do not leave this setting permanently. By doing so, you create a new log file for each invocation of the take action and ALL of them will be left on the agent system. Problem determination for remote deployment Table 13 lists problems that might occur with remote deployment. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. This section describes problems and solutions for remote deployment and removal of agent software Agent Remote Deploy: Table 13. Remote deployment problems and solutions Problem While you are using the remote deployment feature to install IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent, an empty command window is displayed on the target computer. This problem occurs when the target of remote deployment is a Windows computer. (See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the remote deployment feature.) The removal of a monitoring agent fails when you use the remote removal process in the Tivoli Enterprise Portal desktop or browser. Solution Do not close or modify this window. It is part of the installation process and will be dismissed automatically. This problem might happen when you attempt the remote removal process immediately after you have restarted the Tivoli Enterprise Monitoring Server. You must allow time for the monitoring agent to refresh its connection with the Tivoli Enterprise Monitoring Server before you begin the remote removal process. Workspace problem determination Table 14 on page 85 shows problems that might occur with workspaces. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. 84 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

99 Table 14. Workspace problems and solutions Problem The process application components are available, but the Availability status shows PROCESS_DATA_NOT_ AVAILABLE. You see the following message: KFWIT083W Default link is disabled for the selected object; please verify link and link anchor definitions. The name of the attribute does not display in a bar chart or graph view. At the bottom of each view, you see the following Historical workspace KFWITM220E error: Request failed during execution. Solution This problem occurs because the PerfProc performance object is disabled. When this condition exists, IBM Tivoli Monitoring cannot collect performance data for this process. Do the following to confirm that this problem exists and resolve it: 1. Choose Run in the Windows Start menu. 2. Type perfmon.exe in the Open field of the Run window. The Performance window is displayed. 3. Click the plus sign (+) in the tool bar located above the right pane. The Add Counters window is displayed. 4. Look for Process in the Performance object pull-down menu. 5. Perform one of the following actions: v If you see Process in the pull-down menu, the PerfProc performance object is enabled and the problem is coming from a different source. You might need to contact IBM Software Support. v If you do not see Process in the pull-down menu, use the Microsoft utility from the following Web site to enable the PerfProc performance object: reskit/tools/existing /exctrlst-o.asp The Process performance object becomes visible in the Performance object pull-down menu of the Add Counters windows, and IBM Tivoli Monitoring is able to detect Availability data. 6. Restart the monitoring agent You see this message because some links do not have default workspaces. Right-click the link to access a list of workspaces to select. When a chart or graph view that includes the attribute is scaled to a small size, a blank space is displayed instead of a truncated name. To see the name of the attribute, expand the view of the chart until there is sufficient space to display all characters of the attribute s name. Ensure that you configure all groups that supply data to the view. In the Historical Configuration view, ensure that data collection is started for all groups that supply data to the view. Appendix B. Problem determination 85

100 Table 14. Workspace problems and solutions (continued) Problem You start collection of historical data but the data cannot be seen. Historical data collection is unavailable because of incorrect queries in the Tivoli Enterprise Portal. Solution Managing options for historical data collection: v Basic historical data collection populates the Warehouse with raw data. This type of data collection is turned off by default. See the IBM Tivoli Monitoring Administrator s Guide for information on managing this feature including how to set the interval at which data is collected. By setting a more frequent interval for data collection you reduce the load on the system incurred every time data is uploaded. v You use the Summarization and Pruning monitoring agent to collect specific amounts and types of historical data. Be aware that historical data is not displayed until the Summarization and Pruning monitoring agent begins collecting the data. By default, this agent begins collection at 2 AM daily. At that point, data is visible in the workspace view. See the IBM Tivoli Monitoring Administrator s Guide to learn how to modify the default collection settings. The column, Sort By, Group By, and First/Last functions are not compatible with the historical data collection feature. Use of these advanced functions will make a query ineligible for historical data collection. Even if data collection has been started, you cannot use the time span feature if the query for the chart or table includes any column functions or advanced query options (Sort By, Group By, First / Last). To ensure support of historical data collection, do not use the Sort By, Group By, or First/Last functions in your queries. When you use a long process name in the situation, the process name is truncated. Regular (non-historical) monitoring data fails to be displayed. See the IBM Tivoli Monitoring Administrator s Guide the Tivoli Enterprise Portal online Help for information on the Historical Data Collection function. Truncation of process or service names for situations in the Availability table in the portal display is the expected behavior. 100 bytes is the maximum name length. Check the formation of the queries you use to gather capture data. For example, look for invalid SQL statements. Situation problem determination This section provides information about both general situation problems and problems with the configuration of situations. See the IBM Tivoli Monitoring Problem Determination Guide for more information about problem determination for situations. General situation problems Table 15 lists problems that might occur with rightasksituations. Table 15. General situation problems and solutions Problem Monitoring activity requires too much disk space. Solution Check the RAS trace logging settings that are described in Setting RAS trace parameters on page 78. For example, trace logs grow rapidly when you apply the ALL logging option. 86 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

101 Table 15. General situation problems and solutions (continued) Problem Monitoring activity requires too many system resources. A formula that uses mathematical operators appears to be incorrect. For example, if you were monitoring Linux, a formula that calculates when Free Memory falls under 10 percent of Total Memory does not work: LT # Linux_VM_Stats.Total_Memory / 10 IBM Tivoli Monitoring is configured to provide data to the optional product IBM Tivoli Enterprise Console. However, a either a predefined situation that has been edited or a user created situation displays the severity UNKNOWN in IBM Tivoli Enterprise Console. You want to change the appearance of situations when they are displayed in the Navigation tree. Solution Disk capacity planning for historical data on page 47 describes the performance impact of specific attribute groups. If possible, decrease your use of the attribute groups that require greater system resources. This formula is incorrect because situation predicates support only logical operators. Your formulas cannot have mathematical operators. Note: The Situation Editor provides alternatives to math operators. Regarding the example, you can select % Memory Free attribute and avoid the need for math operators. For a situation to have the correct severity in IBM Tivoli Enterprise Console for those situations that are not mapped, you need to ensure that an entry exists in the tecserver.txt file for the situation and that SEVERITY is specified. See the "Configuring Tivoli Enterprise Console Integration" chapter in the IBM Tivoli Monitoring Administrator s Guide for more information. 1. Right-click an item in the Navigation tree. 2. Select Situations in the pop-up menu. The Situation Editor window is displayed. 3. Select the situation that you want to modify. 4. Use the Status pull-down menu in the lower right of the window to set the status and appearance of the Situation when it triggers. Note: This status setting is not related to severity settings in IBM Tivoli Enterprise Console. Problems with configuration of situations Table 16 lists problems that might occur with situations. This section provides information for problem determination for agents. Be sure to consult the IBM Tivoli Monitoring Problem Determination Guide for more general problem determination information. Table 16. Problems with configuring situations that you solve in the Situation Editor Problem Solution Note: To get started with the solutions in this section, perform these steps: 1. Launch the Tivoli Enterprise Portal. 2. Click Edit > Situation Editor. 3. In the tree view, choose the agent whose situation you want to modify. 4. Choose the situation in the list. The Situation Editor view is displayed. The situation for a specific agent is not visible in the Tivoli Enterprise Portal. The monitoring interval is too long. Open the Situation Editor. Access the All managed servers view. If the situation is absent, confirm that the monitoring server has been seeded for the agent. If not, seed the server, as described in the IBM Tivoli Monitoring Installation and Setup Guide. Access the Situation Editor view for the situation that you want to modify. Check the Sampling interval area in the Formula tab. Adjust the time interval as needed. Appendix B. Problem determination 87

102 Table 16. Problems with configuring situations that you solve in the Situation Editor (continued) Problem The situation did not activate at startup. Solution Manually recycle the situation as follows: 1. Right-click the situation and choose Stop Situation. 2. Right-click the situation and choose Start Situation. Note: You can permanently avoid this problem by placing a check mark in the Run at Startup option of the Situation Editor view for a specific situation. The situation is not displayed. Click the Action tab and check whether the situation has an automated corrective action. This action can occur directly or through a policy. The situation might be resolving so quickly that you do not see the event or the update in the graphical user interface. An Alert event has not occurred Check the logs, reports, and workspaces. even though the predicate has been properly specified. A situation fires on an unexpected managed object. The product did not distribute the situation to a managed system. The situation does not fire. Incorrect predicates are present in the formula that defines the situation. For example, the managed object shows a state that normally triggers a monitoring event, but the situation is not true because the wrong attribute is specified in the formula. Confirm that you have distributed and started the situation on the correct managed system. Click the Distribution tab and check the distribution settings for the situation. In the Formula tab, analyze predicates as follows: 1. Click the fx icon in the upper-right corner of the Formula area. The Show formula window is displayed. a. Confirm the following details in the Formula area at the top of the window: v The attributes that you intend to monitor are specified in the formula. v The situations that you intend to monitor are specified in the formula. v The logical operators in the formula match your monitoring goal. v The numerical values in the formula match your monitoring goal. b. (Optional) Click the Show detailed formula check box in the lower left of the window to see the original names of attributes in the application or operating system that you are monitoring. c. Click OK to dismiss the Show formula window. 2. (Optional) In the Formula area of the Formula tab, temporarily assign numerical values that will immediately trigger a monitoring event. The triggering of the event confirms that other predicates in the formula are valid. Note: After you complete this test, you must restore the numerical values to valid levels so that you do not generate excessive monitoring data based on your temporary settings. Table 17. Problems with configuration of situations that you solve in the Workspace area Problem Situation events are not displayed in the Events Console view of the workspace. You do not have access to a situation. Solution Associate the situation with a workspace. Note: The situation does not need to be displayed in the workspace. It is sufficient that the situation be associated with any workspace. Note: You must have administrator privileges to perform these steps. 1. Select Edit > Administer Users to access the Administer Users window. 2. In the Users area, select the user whose privileges you want to modify. 3. In the Permissions tab, Applications tab, and Navigator Views tab, select the permissions or privileges that correspond to the user s role. 4. Click OK. 88 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

103 Table 17. Problems with configuration of situations that you solve in the Workspace area (continued) Problem A managed system seems to be offline. Solution 1. Select Physical View and highlight the Enterprise Level of the navigator tree. 2. Select View > Workspace > Managed System Status to see a list of managed systems and their status. 3. If a system is offline, check network connectivity and status of the specific system or application. Take Action commands problem determination Table 18 lists general problems that might occur with Take Action commands. When each Take Action command runs it generates the log file listed in Table 9 on page 76. This appendix provides agent-specific problem determination information. See the IBM Tivoli Monitoring Problem Determination Guide for general problem determination information. Table 18. Take Action commands problems and solutions Problem Take Action commands often require several minutes to complete. Solution Allow several minutes. If you do not see a pop-up message advising you of completion, try to run the command manually. Situations fail to trigger Take Action commands. Attempt to manually run the Take Action command in the Tivoli Enterprise Portal. If the Take Action command works, look for configuration problems in the situation. See Situation problem determination on page 86. If the Take Action command fails, see IBM Tivoli Monitoring Problem Determination Guide for general information on troubleshooting Take Action commands. Support information If you have a problem with your IBM software, you have the following options for obtaining support for software products: v Searching knowledge bases v Obtaining fixes on page 90 v Receiving weekly support updates on page 90 v Contacting IBM Software Support on page 91 Searching knowledge bases You can search the available knowledge bases to determine whether your problem was already encountered and is already documented. Searching the information center Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper. The documentation CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Appendix B. Problem determination 89

104 Obtaining Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click M to access all of the IBM Tivoli Monitoring product manuals. Searching the Internet If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. The IBM Software Support Web site provides the latest information about known product limitations and workarounds in the form of technotes for your product. You can view this information at the following Web site: To search for information on IBM products through the Internet (for example, on Google), be sure to consider the following types of documentation: v IBM technotes v IBM downloads v IBM Redbooks v IBM developerworks v Forums and newsgroups fixes A product fix might be available to resolve your problem. To determine what fixes are available for your IBM software product, follow these steps: 1. Go to the Software support Web site at support. 2. Click the Download tab. 3. Select the operating system in the Operating system menu. 4. Type search terms in the Enter search terms field. 5. As appropriate, use other search options to further define your search. 6. Click Search. 7. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are available, see the IBM Software Support Handbook at handbook.html. Receiving weekly support updates To receive weekly notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at support. 2. Click My account in the upper right corner of the page. 90 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

105 3. Click Subscribe to IBM e-news. (If you have already subscribed and want to modify your subscription preferences, click Modify subscriptions and follow the instructions on screen.) 4. Follow the instructions on screen to provide the following data: v Your personal contact information. v Your areas of interest. v The types of subscriptions and regional versions that you want to receive. 5. Review the subscription confirmation to confirm your settings. Contacting IBM Software Support IBM Software Support provides assistance with product defects. Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have: v For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows, or UNIX operating systems), enroll in Passport Advantage in one of the following ways: Online Go to the Passport Advantage Web site at services/passport.nsf/ WebDocs/Passport_Advantage_Home and click How to Enroll. By phone For the phone number to call in your country, go to the IBM Software Support Web site at contacts.html and click the name of your geographic region. v For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at login. v For customers with IBMLink, CATIA, Linux, OS/390, iseries, pseries, zseries, and other support agreements, go to the IBM Support Line Web site at v For IBM eserver software products (including, but not limited to, DB2 and WebSphere products that run in zseries, pseries, and iseries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eserver software products, go to the IBM Technical Support Advantage Web site If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at and click the name of your geographic region for phone numbers of people who provide support for your location. To contact IBM Software support, follow these steps: 1. Determining the business impact on page Describing problems and gathering information on page 92 Appendix B. Problem determination 91

106 3. Submitting problems Determining the business impact When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria: Severity 1 The problem has a critical business impact. You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Severity 2 The problem has a significant business impact. The program is usable, but it is severely limited. Severity 3 The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unavailable. Severity 4 The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented. Describing problems and gathering information When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions: v What software versions were you running when the problem occurred? v Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. v Can you re-create the problem? If so, what steps were performed to re-create the problem? v Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, and so on. v Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem. See Gathering product information for IBM Software Support on page 73 for further tips for gathering information for IBM Software Support. Submitting problems You can submit your problem to IBM Software Support in one of two ways: Online Click Submit and track problems on the IBM Software Support site athttp:// Type your information into the appropriate problem submission form. By phone For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook at guides/contacts.html and click the name of your geographic region. If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, 92 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

107 IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution. Informational, warning, and error messages Message This appendix introduces message logging and explains how to gather information from those logs. Message logging refers to the text and numeric messages created by the software. These messages relay information about how the system or application is performing and can alert you to exceptional conditions when they occur. Messages are sent to an output destination, such as a file, database, or console screen. If you receive a warning or error message, you can do one of the following: v Follow the instructions listed in the Detail window of the message if this information is included there. v Consult the message details listed in this appendix to see what action you can take to correct the problem. v Consult the message log for message ID and text, time and date of the message, as well as other data you can use to diagnose the problem. format IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent messages have the following format: Message ID and text Explanation Operator Response The message ID has the following format: CCC####severity where: CCC Prefix that indicates the component to which the message applies. The component is one of the following: KQV General IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent messages #### Number of the message severity Severity of the message. There are three levels of severity: I Informational messages provide feedback about something that happened in the product or system that might be important. These messages can provide guidance when you are requesting a specific action from the product. W Warning messages call your attention to an exception condition. The condition might not be an error but can cause problems if not resolved. Appendix B. Problem determination 93

108 KQV0001I KQV0006E E Error messages indicate that an action cannot be completed because of a user or system error. These messages require user response. The Text of the message provides a general statement regarding the problem or condition that occurred. The Explanation provides additional information about the message and what might have caused the condition. The Operator Response provides actions to take in response to the condition, particularly for error messages (messages with the E suffix). Note: Many message texts and explanations contain variables, such as the specific name of a server or application. Those variables are represented in this appendix as symbols, such as &1. Actual messages contain values for these variables. This appendix includes the messages for the following software: v IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent messages KQV0001I The virtual machine was successfully started. Explanation: The virtual machine was successfully started. Operator response: None. KQV0002I The virtual machine is already started. Explanation: The virtual machine is already started. Operator response: None. KQV0003E Could not perform the requested start action. Explanation: The task could not be executed as requested. Operator response: Check if the Scripting APIs are installed correctly and there is network connection between the agent and the ESX Server. KQV0004I The virtual machine was successfully stopped. Explanation: The virtual machine was successfully stopped. Operator response: None. KQV0005I The virtual machine is already stopped. Explanation: The virtual machine is already stopped. Operator response: None. KQV0006E Could not perform the requested stop action. Explanation: The task could not be executed as requested. Operator response: Check if the Scripting APIs are installed correctly and there is network connection between the Agent and the ESX Server. 94 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

109 KQV3001I KQV9004E KQV3001I The VMware ESX Server is up and reachable. Explanation: The VMware ESX Server is reachable. Operator response: None. KQV3002I The VMware ESX Server is not reachable. Explanation: The VMware ESX Server is not reachable. Operator response: Check if there is network connectivity between the VMware ESX server and the agent; check if the Password/Username supplied is correct; check if the scripting APIs are configured correctly. KQV3003E An error occurred while checking the VMware ESX Server status. Explanation: An error occurred while checking the VMware ESX Server status. Operator response: Check if the VmPerl Scripting APIs are installed and configured correctly. KQV9001I The SSH Client is working and is compatible. Explanation: The SSH Client is working and is compatible to collect data for our agent. Operator response: None KQV9002E The SSH Client you are trying to use could not be configured to collect data. Explanation: The SSH Client is either not compatible or you are experiencing network problems. Operator response: Try another ssh client at the command line of the form SSH_CLIENT -ssh -pw password. KQV9003E An error occurred while configuring the SSH Client for data collection. Explanation: An error occurred while configuring the SSH Client for data collection. Operator response: Check if the SSH Client path is correct, there is network connectivity or the client is compatible. KQV9004E This task is supported on Windows platform only. Explanation: The configure SSH task is supported on windows platforms only. Operator response: If you are trying to configure the agent for data collection using SSH, please refer to the user s guide for setting up SSH on Linux platforms. Appendix B. Problem determination 95

110 96 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

111 Appendix C. Accessibility Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to use software products successfully. The major accessibility features in this product enable users to do the following: v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what is displayed on the screen. Consult the product documentation of the assistive technology for details on using those technologies with this product. v Operate specific or equivalent features using only the keyboard. v Magnify what is displayed on the screen. In addition, the product documentation was modified to include the following features to aid accessibility: v All documentation is available in both HTML and convertible PDF formats to give the maximum opportunity for users to apply screen-reader software. v All images in the documentation are provided with alternative text so that users with vision impairments can understand the contents of the images. Navigating the interface using the keyboard Standard shortcut and accelerator keys are used by the product and are documented by the operating system. Refer to the documentation provided by your operating system for more information. Magnifying what is displayed on the screen You can enlarge information on the product windows using facilities provided by the operating systems on which the product is run. For example, in a Microsoft Windows environment, you can lower the resolution of the screen to enlarge the font sizes of the text on the screen. Refer to the documentation provided by your operating system for more information. Copyright IBM Corp. 2005,

112 98 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

113 Appendix D. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent provides optional functionality for monitoring and managing the system-level CPU usage and file system usage on the VMware system. To collect this data, VMware requires an SSH client. On Linux, an SSH client is available as part of the standard Linux RPMs. On Windows, an SSH client is separately available from Plink at the following location: NOTICE: IBM MAKES NO REPRESENTATION OR WARRANTY REGARDING THE PERFORMANCE OR CONTINUED AVAILABILITY OF THIS OPTIONAL FUNCTIONALITY. PLINK IS SEPARATELY LICENSED CODE AS SPECIFIED IN THE LICENSE INFORMATION DOCUMENT OF THE IBM LICENSE AGREEMENT. If you desire this optional functionality, You may obtain a license for Plink under the terms of the applicable third party license agreement(s) provided or referenced at the Plink website and not the terms of any IBM agreement. Notwithstanding any of the terms in the Plink license agreement, or any other agreement you may have with IBM, the terms of the Plink license agreement(s) govern your use of the Plink code, and not the terms of any IBM agreement. Please refer to the Separately Licensed Code identified in the License Information document of the IBM license agreement. IBM makes no representations whatsoever about the Plink product, VMware, nor any web site which you may access to obtain Plink. When you access a non-ibm Web site or product, even one that may contain the IBM-logo, please understand that it is independent from IBM, and that IBM has no control over the content or products available on that Web site. In addition, a link to a non-ibm Web site or non-ibm product does not mean that IBM endorses or accepts any responsibility for the content, or the use, of such Web site or product. It is up to you to take precautions to ensure that whatever you select for your use is free of such items as viruses, worms, trojan horses and other items of a destructive nature. Copyright IBM Corp. 2005,

114 Notwithstanding any of the terms in the Plink license or your IBM license, or any other agreement you may have with IBM: v (a) IBM provides this information to you WITHOUT WARRANTIES OF ANY KIND; v (b) IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SEPARATELY LICENSED CODE; v (c) IBM is not liable to you, and will not defend, indemnify, or hold you harmless for any claims arising from or related to your use of Plink, the web site, or any other hyper-lined web site; and v (d) IBM is not liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages including, but not limited to, lost data, lost savings, and lost profits, business interruption, loss of programs or other data on your system with respect to your use of Plink, the web site, or any other hyper-lined web site, even if we are expressly advised of the possibility of such damages. If you obtained the IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent under the IBM International Program License Agreement ( IPLA ) or IBM International Program License Agreement for Non Warranted Program ( ILAN ) and you are the original licensee of the Program, and you do not agree with the third party license agreement(s), you may return the Program in accordance with the terms of, and within the specified time frames stated in, the Money-back Guarantee section of the IPLA or ILAN. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. 100 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

115 Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating systems. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating system for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. If you are viewing this information in softcopy form, the photographs and color illustrations might not appear. Trademarks DB2, developerworks, eserver, IBM, IBMLink, the IBM logo, iseries, Lotus, OS/390, Passport Advantage, pseries, Rational, Redbooks, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli Enterprise Console, WebSphere, and zseries are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Appendix D. Notices 101

116 Microsoft, and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. 102 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

117 Index A accessibility ix, 97 actions See Take Action commands agent trace logs 75 agents problem determination 83 Application Component attribute 25 attribute groups Availability 24 CPU Base 27 CPU Load Average 28 CPU VM 29 Disk Base 30 Disk Usage 32 Disk VM 33 list of all 23 Memory Base 35 Memory per VM 36 Memory VM 37 more information 23 Network Base 39 Network VM 40 overview 23 Performance Object Status 42 System 44 System CPU 45 Virtual Machines 45 VM File System 47 attributes Application Component 25 Availability 24 Blocks Available 32 Blocks Used 32 Command Line 26 ConsoleOS Memory 35 CPU Base 27 CPU Load Average 28 CPU Share 27, 30 CPU Utilization Rate 27, 30 CPU VM 29 CPU VMID 27, 30 Disk Base 30 Disk Shares 31, 34 Disk Usage 32 Disk VM 33 Error Code 43 Filesystem 32 Full Name 25 Functionality Test Message 27 Functionality Test Status 26 HBA index 31, 34 HBA name 31, 34 KB Read per Sec 31, 35 KB Received Rate 40, 42 KB Transmitted Rate 39, 42 KB Write per Sec 31, 35 Kernel Loaded 44 Load Avg Fifteen Min 28 Load Avg Five Min 28 attributes (continued) Load Avg One Min 28 MAC Address 39, 41 Memory Available 35 Memory Base 35 Memory Configured 37, 38 Memory per VM 36 Memory Shares 36, 38 Memory Utilized 37, 38 Memory VM 37 more information 23 Mount Point 33 Name 25, 47 Network Base 39 Network Name 39, 41 Network VM 40 Node 24, 27, 28, 29, 30, 32, 33, 35, 36, 37, 39, 40, 42, 44, 45, 47 Number of CPUs 44 Number of Pkts Received 40, 42 Number of Pkts Transmitted 39, 42 Number of Reads 31, 34 Number of Writes 31, 35 Object Name 43 Object Status 43 Object Type 43 overview 23 Page Faults Per Sec 25 Pct Mem Not Used by COS 36 Pct Mem Used by COS 36 Pct Total Free Memory 36 Percent Privileged Time 26 Percent Processor Time 26 Percent Used 32 Percent User Mode Time 26 Performance Object Status 42 Physical CPU 45 PID 26 Product Build 44 Product Name 44 Product OID 44 Product Version 44 Query Name 42 Size 47 Status 25 System 44 System CPU 45 Thread Count 26 Timestamp 24, 27, 28, 29, 31, 32, 33, 35, 36, 37, 39, 40, 42, 44, 45, 46, 47 Total Blocks 32 Total Memory 35 Type 25 Virtual Machines 45 Virtual Size 25 VM Config File 29, 33, 37, 40, 46 VM File System 47 VM Guest State 30, 34, 38, 41, 46 VM Index 29, 33, 37, 40, 46 VM Memory 29, 33, 38, 41, 46 VM Name 29, 33, 37, 40, 46 Copyright IBM Corp. 2005,

118 attributes (continued) VM OS 29, 33, 38, 41, 46 VM State 29, 34, 38, 41, 46 VM VMID 30, 34, 38, 41, 46 VMID 31, 34, 36, 38, 39, 41 Working Set Size 25 Availability situations 50, 51 workspaces descriptions 18 list 18 Availability attribute group 24 Availability workspace 18 B Blocks Available attribute 32 Blocks Used attribute 32 books feedback viii online viii ordering viii see publications ix built-in problem determination features 73 C calculate historical data disk space 47 capacity planning VMware 48 capacity planning for historical data 47 collecting data 15 Command Line attribute 26 commands, Take Action 61 components 2 configuration 5 Configure SSH Windows action 62 ConsoleOS Memory attribute 35 contacting support 91 conventions operating system x typeface x CPU situations 50, 51 workspaces descriptions 19 list 18 CPU Base attribute group 27 CPU Load Average attribute group 28 CPU per VM workspace 19 CPU Share attribute 27, 30 CPU Utilization Rate attribute 27, 30 CPU VM attribute group 29 CPU VMID attribute 27, 30 CPU workspace 19 customer support See support customizing monitoring environment 13 situations 14 D data collecting 15 trace logs 74 data (continued) viewing 15 data logged VMware 48 data provider logs See agent detecting problems, modifying situation values 14 directory names, notation x Disk situations 50, 53 workspaces descriptions 19 list 18 Disk Base attribute group 30 disk capacity planning See capacity planning disk capacity planning for historical data 47 Disk per VM workspace 20 Disk Shares attribute 31, 34 Disk Usage attribute group 32 Disk VM attribute group 33 Disk workspace 19 E education see Tivoli technical training x environment customizing 13 features 1 functions 1 monitoring real-time 11 real-time monitoring 11 environment variables, notation x Error Code attribute 43 event mapping 67 events investigating 12 workspaces 12 F features, IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 1 files agent trace 75 installation trace 75 other trace log 76 trace logs 74 Filesystem attribute 32 fixes, obtaining 90 Full Name attribute 25 Functionality Test Message attribute 27 Functionality Test Status attribute 26 functions, IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 1 G gathering support information IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

119 H HBA index attribute 31, 34 HBA name attribute 31, 34 historical data calculate disk space 47 capacity planning VMware 48 disk capacity planning 47 historical data, collecting and viewing 15 I IBM Software Support See support IBM Tivoli Enterprise Console event mapping 67 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent components 2 features 1 functions 1 performance considerations 86 purposes 11 using 11 information problem determination 73 information centers for support 89 information, additional attributes 23 policies 65 procedural 11 situations 49 Take Action commands 61 workspaces 17 installation log file 75 more information 11 problems 80 interface, user 3 Internet for product support 90 investigating an event 12 K KB Read per Sec attribute 31, 35 KB Received Rate attribute 40, 42 KB Transmitted Rate attribute 39, 42 KB Write per Sec attribute 31, 35 Kernel Loaded attribute 44 knowledge bases for support 89 KQV_CPU_Avg_Overutilized situation 53 KQV_CPU_Avg_Underutilized situation 52 KQV_CPU_Phy_Utilization_High situation 52 KQV_DiskRead_Activity_High situation 54 KQV_DiskWrite_Activity_High situation 54 KQV_Filesystem_Freespace_Low situation 53 KQV_Memory_Available_Low situation 55 KQV_Memory_Used_COS_High situation 55 KQV_NetworkRX_Activity_High situation 56 KQV_NetworkTX_Activity_High situation 56 KQV_Virtual_Machine_Off situation 57 KQV_Virtual_Machine_Stuck situation 57 KQV_Virtual_Machine_Suspended situation 58 KQV_Virtual_Machine_Unknown situation 58 KQV_VMKernel_Not_Loaded situation 51 KQV_VMware_ESX_Server_Down situation 51 L legal notices 99 list of messages 94 Load Avg Fifteen Min attribute 28 Load Avg Five Min attribute 28 Load Avg One Min attribute 28 logged data VMware 48 logging agent trace logs 75, 76 built-in features 73 installation log files 75 trace log files 74 M MAC Address attribute 39, 41 manuals feedback viii online viii ordering viii see publications ix Memory situations 50, 55 workspaces descriptions 20 list 18 Memory Available attribute 35 Memory Base attribute group 35 Memory Configured attribute 37, 38 Memory per VM attribute group 36 Memory per VM workspace 20 Memory Shares attribute 36, 38 Memory Utilized attribute 37, 38 Memory VM attribute group 37 Memory workspace 20 messages built-in features 73 for IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent 94 format 93 overview 93 syntax 93 modifying situation values to detect problems 14 monitoring, viewing the real-time environment 11 Mount Point attribute 33 N Name attribute 25, 47 Network situations 50, 56 workspaces descriptions 20 list 18 Network Base attribute group 39 Network Name attribute 39, 41 Network VM attribute group 40 Network workspace 20 Node attribute 24, 27, 28, 29, 30, 32, 33, 35, 36, 37, 39, 40, 42, 44, 45, 47 notation environment variables x path names x typeface x Number of CPUs attribute 44 Index 105

120 Number of Pkts Received attribute 40, 42 Number of Pkts Transmitted attribute 39, 42 Number of Reads attribute 31, 34 Number of Writes attribute 31, 35 O Object Name attribute 43 Object Status attribute 43 Object Type attribute 43 online publications accessing ix for support 89 operation of resource, recovering 12 ordering publications ix P Page Faults Per Sec attribute 25 path names, notation x Pct Mem Not Used by COS attribute 36 Pct Mem Used by COS attribute 36 Pct Total Free Memory attribute 36 Percent Privileged Time attribute 26 Percent Processor Time attribute 26 Percent Used attribute 32 Percent User Mode Time attribute 26 performance considerations 86 Performance Object Status attribute group 42 Physical CPU attribute 45 PID attribute 26 policies more information 65 overview 65 problem determination 73, 80 agents 83 built-in features 73 describing problems 92 determining business impact 92 information centers for 89 installation 80 installation logs 75 knowledge bases for 89 messages 93 remote deployment 84 situations 86, 87 submitting problems 92 Take Action commands 89 uninstallation 80 uninstallation logs 75 workspaces 84 problems detecting 14 problems and workarounds 80 procedures 11 Product Build attribute 44 Product Name attribute 44 Product OID attribute 44 Product Version attribute 44 publications accessing online ix feedback viii for support 89 online viii ordering viii, ix purposes collecting data 15 customizing monitoring environment 13 investigating events 12 monitoring with custom situations 14 problem determination 73 recovering resource operation 12 viewing data 15 viewing real-time monitoring environment 11 Q queries, using attributes 23 Query Name attribute 42 R real-time data, viewing 11 recovering the operation of a resource 12 remote deployment problem determination 84 requirements 5 resource, recovering operation 12 S situations general problem determination 86, 87 KQV_CPU_Avg_Overutilized 53 KQV_CPU_Avg_Underutilized 52 KQV_CPU_Phy_Utilization_High 52 KQV_DiskRead_Activity_High 54 KQV_DiskWrite_Activity_High 54 KQV_Filesystem_Freespace_Low 53 KQV_Memory_Available_Low 55 KQV_Memory_Used_COS_High 55 KQV_NetworkRX_Activity_High 56 KQV_NetworkTX_Activity_High 56 KQV_Virtual_Machine_Off 57 KQV_Virtual_Machine_Stuck 57 KQV_Virtual_Machine_Suspended 58 KQV_Virtual_Machine_Unknown 58 KQV_VMKernel_Not_Loaded 51 KQV_VMware_ESX_Server_Down 51 list of all 50 more information 49 overview 49 predefined 50 values, modifying 14 situations, using attributes 23 Size attribute 47 Start Virtual Machine action 62 Status attribute 25 Stop Virtual Machine action 63 support about 89 contacting 91 describing problems 92 determining business impact of problems 92 gathering information for 73 information centers for 89 knowledge bases for 89 list of messages 94 messages 93 obtaining fixes 90 on Internet IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

121 support (continued) submitting problems 92 weekly update option 90 syntax messages 93 System attribute group 44 System CPU attribute group 45 T Take Action commands 12 Configure SSH Windows 62 list of all 61 more information 61 overview 61 predefined 61 problem determination 89 Start Virtual Machine 62 Stop Virtual Machine 63 Thread Count attribute 26 Timestamp attribute 24, 27, 28, 29, 31, 32, 33, 35, 36, 37, 39, 40, 42, 44, 45, 46, 47 Tivoli software information center ix Tivoli technical training x Total Blocks attribute 32 Total Memory attribute 35 trace logs 74 trademarks 101 training, Tivoli technical x troubleshooting 73 Type attribute 25 typeface conventions x U uninstallation log file 75 problems 80 user interfaces options 3 V values, modifying situations 14 variables, notation for x viewing data 15 viewing real-time monitoring environment 11 views Availability workspace 18 CPU per VM workspace 19 CPU workspace 19 Disk per VM workspace 20 Disk workspace 19 Memory per VM workspace 20 Memory workspace 20 Network workspace 20 Virtual Machines workspace 21 VMware ESX workspace 18 Virtual Machines situations 50, 57 workspaces descriptions 21 list 18 Virtual Machines attribute group 45 Virtual Machines workspace 21 Virtual Size attribute 25 VM Config File attribute 29, 33, 37, 40, 46 VM File System attribute group 47 VM Guest State attribute 30, 34, 38, 41, 46 VM Index attribute 29, 33, 37, 40, 46 VM Memory attribute 29, 33, 38, 41, 46 VM Name attribute 29, 33, 37, 40, 46 VM OS attribute 29, 33, 38, 41, 46 VM State attribute 29, 34, 38, 41, 46 VM VMID attribute 30, 34, 38, 41, 46 VMID attribute 31, 34, 36, 38, 39, 41 VMware ESX situations 50, 51 workspaces descriptions 18 list 18 VMware ESX workspace 18 W weekly update support option 90 workarounds 80 agents 83 remote deployment 84 situations 86 Take Action commands 89 workspaces 84 Working Set Size attribute 25 workspaces _EnDNAVIGATOR_ITEM_EnD 18, 19, 20, 21 Availability 18 CPU 19 CPU per VM 19 Disk 19 Disk per VM 20 event 12 list of all 18 Memory 20 Memory per VM 20 more information 17 Network 20 overview 17 predefined 18 problem determination 84 Virtual Machines 21 VMware ESX 18 Index 107

122 108 IBM Tivoli Monitoring for Virtual Servers: VMware ESX Agent: User s Guide

123

124 Printed in USA SC