Tivoli Monitoring for Virtual Servers Agent for Linux Kernel

Tivoli Monitoring for Virtual Servers Agent for LinuxKernel-based Virtual MachinesVersion 6.2.3

User's Guide

SC27-2892-00

��

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

This edition applies to version 6.2.3 of IBM Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-basedVirtual Machines (product number 5724-L92)) and to all subsequent releases and modifications until otherwiseindicated in new editions.

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

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

Chapter 1. Overview of the monitoringagent . . . . . . . . . . . . . . . . 1IBM Tivoli Monitoring overview. . . . . . . . 1Functions of the monitoring agent . . . . . . . 1Components of the IBM Tivoli Monitoringenvironment . . . . . . . . . . . . . . 1Agent Management Services . . . . . . . . . 2User interface options . . . . . . . . . . . 2

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

Windows systems. . . . . . . . . . . . 5UNIX or Linux systems. . . . . . . . . . 5Silent installation of language packs for agents . . 6

Configuring the monitoring agent after installation . 8Virtualization hosts . . . . . . . . . . . 8Configuration values . . . . . . . . . . 10Remote installation and configuration . . . . 13

Chapter 3. Workspaces reference . . . 15About workspaces . . . . . . . . . . . . 15More information about workspaces . . . . . . 15Predefined workspaces . . . . . . . . . . 16Agent Navigator items . . . . . . . . . . 16

Linux KVM Navigator item . . . . . . . . 16Host Navigator item . . . . . . . . . . 18Storage Pool Navigator item. . . . . . . . 19Virtual Machine Navigator item . . . . . . 20

Chapter 4. Attributes reference . . . . 23About attributes . . . . . . . . . . . . . 23More information about attributes . . . . . . . 23Attribute groups and attributes for the LinuxKernel-based Virtual Machines agent . . . . . . 23Host CPU attribute group . . . . . . . . . 24Host Memory attribute group . . . . . . . . 30Hosts attribute group . . . . . . . . . . . 34Performance Object Status attribute group . . . . 39Storage Pools attribute group . . . . . . . . 45Virtual Machines attribute group . . . . . . . 48Disk capacity planning for historical data . . . . 56

Chapter 5. Situations reference . . . . 59About situations . . . . . . . . . . . . . 59More information about situations . . . . . . . 59Predefined situations . . . . . . . . . . . 60Linux KVM Navigator item . . . . . . . . . 61

Host Navigator item . . . . . . . . . . . 61KV1_Host_CPU_Over_Commit_Info situation . . 61KV1_Host_CPU_Over_Commit_Warn situation 61KV1_Host_CPU_Over_Commit_Crit situation . . 62KV1_Host_CPU_Pct_High_Warn situation . . . 63KV1_Host_CPU_Pct_High_Crit situation. . . . 63KV1_Host_Mem_Pct_High_Warn situation . . . 64KV1_Host_Mem_Pct_High_Crit situation . . . 64

Storage Pool Navigator item. . . . . . . . . 65Virtual Machine Navigator item . . . . . . . 65

KV1_VM_CPU_Pct_High_Warn situation . . . 65KV1_VM_CPU_Pct_High_Crit situation . . . . 66KV1_VM_Mem_Pct_High_Warn situation . . . 66KV1_VM_Mem_Pct_High_Crit situation . . . . 67

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

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

Chapter 8. Troubleshooting . . . . . . 73Gathering product information for IBM SoftwareSupport . . . . . . . . . . . . . . . 73Built-in troubleshooting features . . . . . . . 73Problem classification . . . . . . . . . . . 74Trace logging . . . . . . . . . . . . . . 74

Overview of log file management . . . . . . 74Principal trace log files . . . . . . . . . 75Setting RAS trace parameters . . . . . . . 78

Problems and workarounds . . . . . . . . . 78Installation and configuration troubleshooting . . 79Remote deployment troubleshooting . . . . . 82Agent troubleshooting . . . . . . . . . . 82Workspace troubleshooting . . . . . . . . 84Situation troubleshooting . . . . . . . . . 85Take Action commands troubleshooting . . . . 89

Support information . . . . . . . . . . . 89

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

Appendix B. Documentation library . . 97Linux Kernel-based Virtual Machines agent library 97Prerequisite publications . . . . . . . . . . 97Related publications . . . . . . . . . . . 98Other sources of documentation . . . . . . . 98

Appendix C. Accessibility . . . . . . 101

© Copyright IBM Corp. 2011 iii

Navigating the interface using the keyboard . . . 101Magnifying what is displayed on the screen . . . 101

Appendix D. Notices . . . . . . . . 103

Trademarks . . . . . . . . . . . . . . 105

Index . . . . . . . . . . . . . . . 107

iv Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual Machines: User's Guide

Figures

1. Agent Configuration Data Provider . . . . 11 2. Agent Configuration Hypervisor . . . . . 12

© Copyright IBM Corp. 2011 v

vi Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual Machines: User's Guide

Tables

1. Capacity planning for historical data logged bythe Linux Kernel-based Virtual Machines agent 56

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

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

configuration . . . . . . . . . . . . 795. General problems and solutions for

uninstallation . . . . . . . . . . . . 816. Remote deployment problems and solutions 82

7. Agent problems and solutions . . . . . . 828. Workspace problems and solutions. . . . . 849. General situation problems and solutions 86

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

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

12. Take Action commands problems andsolutions . . . . . . . . . . . . . 89

© Copyright IBM Corp. 2011 vii

viii Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual Machines: User's Guide

Chapter 1. Overview of the monitoring agent

This monitoring agent provides you with the capability to monitor Linuxkernel-based virtual machines (KVM). This chapter provides a description of thefeatures, components, and interface options for the Linux Kernel-based VirtualMachines agent.

IBM Tivoli Monitoring overviewIBM Tivoli Monitoring is the base software for the Linux Kernel-based VirtualMachines agent. IBM Tivoli Monitoring provides a way to monitor the availabilityand performance of all the systems in your enterprise from one or severaldesignated workstations. It also provides useful historical data that you can use totrack trends and to troubleshoot system problems.

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

situations or custom situationsv Establish your own performance thresholdsv Trace the causes leading to an alertv Gather comprehensive data about system conditionsv Use policies to perform actions, schedule work, and automate manual tasks

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products.You can use the consolidated view of your environment as seen in the IBM TivoliEnterprise Portal to monitor and resolve performance issues throughout theenterprise.

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

Functions of the monitoring agentThe Linux Kernel-based Virtual Machines agent provides the following function:

Displays health and performance of Linux KVM host hypervisor systems andguest virtual machines

You can use this agent to visualize host capacity and virtual machineconsumption in Linux KVM systems.

Components of the IBM Tivoli Monitoring environmentAfter you install and set up the Linux Kernel-based Virtual Machines agent, youhave an environment that contains the client, server, and monitoring agentimplementation for IBM Tivoli Monitoring. This environment contains thefollowing components:v Tivoli Enterprise Portal client, which has a user interface based on Java for

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

Tivoli Enterprise Monitoring Server and enables retrieval, manipulation, and

© Copyright IBM Corp. 2011 1

analysis of data from the monitoring agents. The Tivoli Enterprise Portal Serveris the central repository for all user data.

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

v Tivoli Enterprise Monitoring Agent, Linux Kernel-based Virtual Machines agent(one or more instances of the monitoring agent). The instances communicatewith the systems or subsystems that you want to monitor. This monitoring agentcollects and distributes data to a Tivoli Enterprise Portal Server.

v IBM Tivoli Enterprise Console, which is an optional component that acts as acentral collection point for events from a variety of sources, including eventsfrom other Tivoli® software applications, Tivoli partner applications, customapplications, network management platforms, and relational database systems.You can view these events through the IBM Tivoli Enterprise Portal (using theevent viewer), and you can forward events from IBM Tivoli Monitoringsituations to the IBM Tivoli Enterprise Console component.

v IBM Tivoli Netcool/OMNIbus, which is an optional component and analternative to the IBM Tivoli Enterprise Console. The Netcool/OMNIbussoftware is a service level management (SLM) system that delivers real-time,centralized monitoring of complex networks and IT domains. The TivoliNetcool/OMNIbus components work together to collect and manage networkevent information.

Agent Management ServicesYou can use IBM Tivoli Monitoring Agent Management Services to manage theLinux Kernel-based Virtual Machines agent. These services are available in thefollowing IBM Tivoli Monitoring OS agents: Windows, Linux, and UNIX. Theservices are designed to keep the Linux Kernel-based Virtual Machines agentavailable, and to provide information about the status of the product to the IBMTivoli Enterprise Portal. IBM Tivoli Monitoring V6.2.2, Fix Pack 1 or later providessupport for Agent Management Services. For more information about AgentManagement Services, see the IBM Tivoli Monitoring Administrator's Guide, "AgentManagement Services" chapter.

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

Tivoli Enterprise Portal browser client interfaceThe browser client interface is automatically installed with the IBM TivoliEnterprise Portal Server. To start the IBM Tivoli Enterprise Portal browserclient in your Internet browser, enter the web address for a specific TivoliEnterprise Portal browser client installed on your Web server.

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

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

2 Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual Machines: User's Guide

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

Tivoli Netcool/OMNIbus event listYou can use the event list to monitor and manage alerts. An alert is createdwhen the ObjectServer receives an event, alarm, message, or data item.Each alert is made up of columns (or fields) of information that are held ina row in the ObjectServer alerts.status table. The Tivoli Netcool/OMNIbusWeb GUI is also a web-based application that processes network eventsfrom one or more data sources and presents the event data in variousgraphical formats.

Chapter 1. Overview of the monitoring agent 3

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

Before installing and configuring the agent, make sure your environment meets therequirements for the IBM Tivoli Monitoring for Virtual Servers Agent for LinuxKernel-based Virtual Machines. See the Prerequisites topic for the agent in the IBMTivoli Monitoring for Virtual Servers information center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tivoli.itmvs.doc_6.2.3/VSwelcome.htm.

To install and configure the Linux Kernel-based Virtual Machines agent, use theprocedures for installing monitoring agents in the IBM Tivoli Monitoring Installationand Setup Guide along with the agent-specific information in this chapter.

If you are performing a silent installation by using a response file, see theinformation about performing a silent installation in the IBM Tivoli MonitoringInstallation and Setup Guide.

Installing language packsTo install a language pack for the agent support files on the IBM Tivoli EnterpriseMonitoring Server, the IBM Tivoli Enterprise Monitoring Agent, and the IBM TivoliEnterprise Portal Server, first make sure that you installed the product in theEnglish language. Then, perform the following steps depending on whichoperating system and mode of installation you are using.

Windows systems1. On the language pack CD, double-click the lpinstaller.bat file to start the

installation program.2. Select the language of the installer and click OK.3. In the Introduction panel, click Next

4. Click Add/Update and click Next.5. Select the folder in which the National Language Support package

(NLSPackage) files are located.Typically the NLSPackage files are located in the nlspackage folder where theinstaller executable file is located.

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

Note: To make multiple selections, press Ctrl and select the language that youwant.

7. Select the languages that you want to install and click Next.8. Examine the installation summary page and click Next to begin installation.9. After installation completes, click Finish to exit the installer.

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

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

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


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tivoli.itmvs.doc/VSwelcome.htm



mkdir dir_name

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

cd dir_namelpinstaller.sh -c install_dir

where install_dir is where you installed IBM Tivoli Monitoring. Typically it is/opt/IBM/ITM for AIX and Linux systems.

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

(NLSPackage) files are located.Typically, the NLSPackage files are located in the nlspackage folder where theinstaller executable file is located.

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

Note: To make multiple selections, press Ctrl and select the language that youwant.

9. Select the languages that you want to install and click Next.10. Examine the installation summary page and click Next to begin installation.11. After installation completes, click Finish to exit the installer.12. Restart the IBM Tivoli Enterprise Portal, IBM Tivoli Enterprise Portal Server,

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

Silent installation of language packs for agentsYou can install the language pack by using a silent installation method:1. Copy and paste the following response file template as

ITM_Agent_LP_silent.rsp.2. Change the following parameter setting: NLS_PACKAGE_FOLDER;

PROD_SELECTION_PKGl; BASE_AGENT_FOUND_PKG_LIST;LANG_SELECTION_LIST

3. Run the command to silently install the language pack:v For Windows systems:

lpinstaller.bat -f path_to_response_file

v For UNIX or Linux systems:lpinstaller.sh -c candle_home -f path_to_response_file

where candle_home is the IBM Tivoli Monitoring base directory

Response file template:# IBM Tivoli Monitoring Agent Language Pack Silent Installation Operation##This is a sample response file for silent installation mode for the IBM Tivoli#Monitoring Common Language Pack Installer.#.#This file uses the IBM Tivoli Monitoring Common Agent Language Pack with the#install package as an example.#Note:#This response file is for the INSTALLATION of language packs only.#This file does not support UNINSTALLATION of language packs in silent mode.#-------------------------------------------------------------------------------


#-------------------------------------------------------------------------------#To successfully complete a silent installation of the the example of Common Agent#localization pack, complete the following steps:##1.Copy ITM_Agent_LP_silent.rsp to the directory where lpinstaller.bat or#lpinstaller.sh is located (IBM Tivoli Monitoring Agent Language Pack build#location).##2.Modify the response file so that it is customized correctly and completely for#your site.# Complete all steps listed below in the response file.##3.After customizing the response file, invoke the silent installation using the#following command:#For Windows:# lpinstaller.bat -f <path_to_response_file>#For UNIX and Linux:# lpinstaller.sh -c <candle_home> -f <path_to_response_file>#Note:<candle_home> is the IBM Tivoli Monitoring base directory.#--------------------------------------------------------------------------------#--------------------------------------------------------------------------------#Force silent install mode.#--------------------------------------------------------------------------------INSTALLER_UI=silent#---------------------------------------------------------------------------------#Run add and update actions.#---------------------------------------------------------------------------------CHOSEN_INSTALL_SET=ADDUPD_SET#---------------------------------------------------------------------------------#NLS Package Folder, where the NLS Packages exist.#For Windows:# Use the backslash-backslash(\\) as a file separator (for example,#C:\\zosgmv\\LCD7-3583-01\\nlspackage).#For UNIX and Linux:# Use the slash-slash (//) as a file separator (for example,#//installtivoli//lpsilenttest//nlspackage).#---------------------------------------------------------------------------------#NLS_PACKAGE_FOLDER=C:\\zosgmv\\LCD7-3583-01\\nlspackageNLS_PACKAGE_FOLDER=//tmp//LP//nlspackage#---------------------------------------------------------------------------------#List the packages to process; both variables are required.#Each variable requires that full paths are specified.#Separate multiple entries with a semicolon (;).#For Windows:# Use the backslash-backslash(\\) as a file separator.#For Unix and Linux:# Use the slash-slash (//) as a file separator.#---------------------------------------------------------------------------------#PROD_SELECTION_PKG=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkg#BASE_AGENT_FOUND_PKG_LIST=C:\\zosgmv\\LCD7-3583-01\\nlspackage\\KIP_NLS.nlspkgPROD_SELECTION_PKG=//tmp//LP//nlspackage//kex_nls.nlspkg;//tmp//LP//nlspackage//koq_nls.nlspkgBASE_AGENT_FOUND_PKG_LIST=//tmp//LP//nlspackage//kex_nls.nlspkg;//tmp//LP//nlspackage//koq_nls.nlspkg#--------------------------------------------------------------------------------#List the languages to process.#Separate multiple entries with semicolons.#--------------------------------------------------------------------------------LANG_SELECTION_LIST=pt_BR;fr;de;it;ja;ko;zh_CN;es;zh_TW

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

Configuring the monitoring agent after installationIn addition to the installation and configuration information in the IBM TivoliMonitoring Installation and Setup Guide, use the information in this section to installand configure the Linux Kernel-based Virtual Machines agent.

Virtualization hostsYou must take into account two aspects of your virtualization hosts when youconfigure the Linux Kernel-based Virtual Machines agent. The first aspect is howthe hosts are organized: whether you have multiple kinds of virtualized loads andwhether you want to migrate virtual machines between hosts. The second aspect ishow you want to secure communications between the Linux Kernel-based VirtualMachines agent and the hypervisors.

The Linux Kernel-based Virtual Machines agent is both multi-instance andmulticonnection.

Multi-instancemulti-instance means that you can create multiple, independent copies ofthe Linux Kernel-based Virtual Machines agent from one installation.

MulticonnectionMulticonnection means that each instance of the Linux Kernel-basedVirtual Machines agent can connect to and monitor multiple hypervisors. Itis easier to compare the characteristics of several hypervisors when theyare monitored by one agent instance.

One configuration strategy is to use a single agent instance to group together hostswith similar virtualized loads. By monitoring the supporting hosts with a singleinstance, you can more easily compare for each host the resource capacity andcurrent resource consumption by virtualization. This type of monitoring can helpyou balance your virtualized workloads by migrating virtual machines fromoverburdened hosts to hosts that can support more. Each kind of virtualizedworkload can be monitored by its own Linux Kernel-based Virtual Machines agentinstance, so you can have one instance monitoring your web applications, anothermonitoring your virtual desktops, and so on.

The Linux Kernel-based Virtual Machines agent collects its metrics by connectingremotely to each libvirt hypervisor managing your QEMU-KVM virtual machines.Libvirt can use several different remote transport protocols, as described onhttp://libvirt.org/remote.html. The Linux Kernel-based Virtual Machines agentsupports the SSH protocol, the TLS protocol, and the TCP protocol. While the SSHprotocol and the TLS protocol provide production-level security, the use of the TCPprotocol by the Linux Kernel-based Virtual Machines agent supports only anauthentication of "none" and is intended for testing. There follow instructions forimplementing the SSH protocol, the TLS protocol, and the TCP protocol in thecontext of libvirt remote connections.

SSH protocolFor the SSH agent, assume you install the Linux Kernel-based Virtual Machinesagent on Host A and you want to remotely monitor the hypervisor on Host B. Youfirst need to configure the SSH agent to allow the SSH agent to make a connectionfrom Host A to Host B without requiring you to input a password. Afterconfiguration, you can start the Linux Kernel-based Virtual Machines agent andbegin to monitor Host B. Assume you have several hosts that you want to monitor,


http://libvirt.org/remote.html

that is to say several Host Bs. For some helpful instructions on this topic, seehttp://mah.everybody.org/docs/ssh. Follow these steps:1. Log on to Host A as the ID that will run the Linux Kernel-based Virtual

Machines agent process, for example the root user ID. Have available the ID onHost B that will be making the SSH connection, often also the root user ID.

2. Generate the id_rsa and id_rsa.pub keys on Host A. The keys are saved in~/.ssh.$ ssh-keygen -t rsa

3. Copy the authorized keys from Host B, so you can add the public key for HostA to it.$ scp Id on Host B@name or IP address of Host B:~/.ssh/authorized_keys~/.ssh/authorized_keys_from_B

4. Append the public key for Host A to the end of the authorized keys for Host B.cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys_from_B

5. Copy the authorized keys back to Host B. If you are monitoring multiple hosts,repeat steps 3, 4, and 5 for each host. You may remove ~/.ssh/authorized_keys_from_B after this step.$ scp ~/.ssh/authorized_keys_from_B Id on Host B@name or IP address of HostB:~/.ssh/authorized_keys

6. Add the following command to the ~/.bash_profile of the current ID on HostA. Ensure you use the single back quotation mark (`), located under the tilde(~) on US keyboards, rather than the single quotation mark (').$ eval `ssh-agent`

7. Add the identity to Host A. You are asked for the passphrase you used whenthe ID was created. If you receive the message "Could not open a connection toyour authentication agent.", run the exec ssh-agent bash command (you canreplace bash with the shell you are using) and then run the ssh-add commandagain.$ ssh-add ~/.ssh/id_rsa

8. Test that the SSH agent can make a connection from Host A to Host B withoutentering the SSH password. If you are monitoring multiple hosts, test this foreach host.$ ssh Id on Host B@name or IP address of Host B

When you have finished the configuration, check your work by using the virshcommand by entering virsh -c qemu+ssh://Id on Host B@name or IP address ofHost B:port/system. You can omit the :port section of the command if you havenot changed the default SSH port. If the virsh command succeeds, the LinuxKernel-based Virtual Machines agent can connect.

Note: You must rerun the ssh-add command and supply the passphrase each timeyou restart Host A before you restart the Linux Kernel-based VirtualMachines agent on Host A. If you use SSH keychains, you can avoid havingto reenter the passphrase. A discussion of SSH keychains is beyond thescope of this guide, but information is available on the Internet.

TLS protocolFor the TLS protocol, assume you install the Linux Kernel-based Virtual Machinesagent on Host A and you want to remotely monitor the hypervisor on Host B.Follow these steps:1. Log in to Host B and confirm you have installed the gnutls and gnutls-utils

packages.


http://mah.everybody.org/docs/ssh

2. Edit /etc/libvirt/libvirtd.conf to make sure that listen_tls is enabled andthe tls_port is 16514 (the default).

3. Go to libvirt.org/remote.html and follow the instructions for setting up acertificate authority between Host A and Host B. Pay special attention to thesections of Setting up a Certificate Authority (CA), Issuing server certificates,and Issuing client certificates.

4. Restart the libvirt daemon on Host B in listening mode by running it with--listen flag or by editing /etc/sysconfig/libvirtd and uncommenting theLIBVIRTD_ARGS="--listen" line.

When you have finished the configuration, check your work using the virshcommand by entering virsh -c qemu+tls://name or IP address of HostB:port/system. You can omit the :port section of the command if you have notchanged the default TLS port. If the virsh command succeeds, the LinuxKernel-based Virtual Machines agent can connect.

TCP protocolOnly use the TCP protocol for testing. For TCP, assume you install the LinuxKernel-based Virtual Machines agent on Host A and you want to remotely monitorthe hypervisor on Host B. Follow these steps:1. Log in to Host B.2. Edit /etc/libvirt/libvirtd.conf to make sure that listen_tcp is enabled and

tcp_port is 16509 (the default).3. Edit /etc/libvirt/libvirtd.conf to set auth_tcp to "none". This instructs TCP

not to perform any authentication.4. Restart the libvirt daemon on Host B in listening mode by running it with

--listen flag or by editing /etc/sysconfig/libvirtd and uncommenting theLIBVIRTD_ARGS="--listen" line.

When you have finished the configuration, check your work using the virshcommand by entering virsh -c qemu+tcp://name or IP address of HostB:port/system. You can omit the :port section of the command if you have notchanged the default TCP port. If the virsh command succeeds, the LinuxKernel-based Virtual Machines agent can connect.

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

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

Data Provider (DATA_PROVIDER)This section provides the logging characteristics that the data provideruses.

The configuration elements defined in this group are always present in theconfiguration of the agent.

This group defines information that applies to the entire agent.


Maximum Number Of Data Provider Log Files(KV1_LOG_FILE_MAX_COUNT)

This number is the number of log files that is created before rollingover.

The type is numeric.

This value is required.

Default: 10

Maximum Size in KB of Each Data Provider Log(KV1_LOG_FILE_MAX_SIZE)

This value is the maximum size in KB that a log file reaches beforemoving to the next log file.



Default: 5190

Level of Detail in Data Provider Log. (KV1_LOG_LEVEL)This value controls how many log messages the agent writes andat what level of detail.

The type is one of the following values: "Off", "Severe", "Warning","Info", "Fine", "Finer", "Finest", "All".


Default: INFO

Figure 1. Agent Configuration Data Provider


Hypervisor (HYPERVISOR)This section provides the connection information for each hypervisor beingmonitored.

The configuration elements defined in this group are always present in theconfiguration of the agent.

Use the information in this group to create additional subnodes.

Hypervisor ID (Hypervisor ID)A unique identifier for this hypervisor.

The type is string.


Default: None

Host (HOST_ADDRESS)The host name or IP address of the KVM hypervisor.

The type is string.


Default: None

User (USERNAME)A user name on the KVM hypervisor that has sufficient privilegesto collect monitoring data. The user name is only needed for SSHtransport.

The type is string.

This value is optional.

Figure 2. Agent Configuration Hypervisor


Default: None

Remote Transport (PROTOCOL)This value controls which protocol the local libvirt uses to connectto remote libvirts.

The type is one of the following values: "SSH", "TLS", "TCP(Unencrypted – not recommended for production use)".


Default: ssh

Port (PORT)The port used by the transport protocol to make the libvirtconnection. The port is only needed if the standard ports havebeen changed (22 for SSH, 16514 for TLS, 16509 for TCP).


This value is optional.

Default: None

Connection Instance Type (CONNECTION_MODE)This value controls whether the local libvirt connects to theprivileged system driver or the per-user unprivileged sessiondriver.

The type is one of the following values:v system

Note: If you are unsure, this answer is probably correct.v session


Default: system

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

See the tacmd describeSystemType section in the IBM Tivoli Monitoring CommandReference for information about displaying the configuration options that areavailable to use with the configureSystem or addSystem commands.

You can install the monitoring agent remotely from the IBM Tivoli EnterprisePortal or from the command line. To install from the portal, see the IBM TivoliMonitoring Installation and Setup Guide.

If using the command line, the following command is an example of remoteconfiguration:tacmd addsystem -t v1 -n Primary:sample.node.name:LZ-p DATA_PROVIDER.KV1_LOG_FILE_MAX_COUNT=10DATA_PROVIDER.KV1_LOG_FILE_MAX_SIZE=5190DATA_PROVIDER.KV1_LOG_LEVEL=INFOINSTANCE=instanceNameHYPERVISOR:UniqueDataSourceID.HOST_ADDRESS=hostAddressOrNameHYPERVISOR:UniqueDataSourceID.USERNAME=user


HYPERVISOR:UniqueDataSourceID.PROTOCOL=(ssh|tls|tcp)HYPERVISOR:UniqueDataSourceID.PORT=portHYPERVISOR:UniqueDataSourceID.CONNECTION_MODE=system


Chapter 3. Workspaces reference

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

About workspacesA workspace is the working area of the IBM Tivoli Enterprise Portal applicationwindow. Use the Navigator tree that is displayed at the left of the workspace toselect the workspace you want to see. As part of the application window, the rightside of the status bar shows the IBM Tivoli Enterprise Portal Server name and portnumber to which the displayed information applies and the ID of the current user.

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

The workspaces in the Navigator are displayed in a Physical view that shows yourenterprise as a physical mapping or a dynamically populated logical view that isagent-specific. You can also create a Logical view. The Physical view is the defaultview.

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

The Linux Kernel-based Virtual Machines agent provides various defaultworkspaces. These workspaces are displayed in the Navigator tree under thefollowing nodes and subnodes for this monitoring agent:

Linux KVM (V1 node)Corresponds to a Linux kernel-based virtual machine instance and containsagent instance-level workspaces.

When multiple instances of the monitoring agent are defined on a system, thetop-level node becomes Linux KVM. The Linux KVM workspace is undefined atthis node. A subnode for each instance is created called Instance::V1. A workspacethat is called Instance:Hostname:V1 is associated with the instance node. Thisworkspace is comparable to the Linux KVM workspace.

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

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


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

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

Predefined workspaces

The Linux Kernel-based Virtual Machines agent provides the following predefinedworkspaces, which are organized by Navigator item.

Agent-level navigator itemsv Linux KVM Navigator item

– Host CPU Comparison workspace– Host Memory Allocation Comparison workspace– Host Memory Use Comparison workspace

v Host Navigator item– Host Detail workspace– Host Overview workspace– Host Relations workspace

v Storage Pool Navigator item– Storage Pool Detail workspace– Storage Pool Overview workspace

v Virtual Machine Navigator item– Virtual Machine Detail workspace– Virtual Machine Overview workspace

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

Linux KVM Navigator itemLinux KVM workspaces

These workspaces show the most heavily used hosts and the least heavilyused hosts based on a variety of resources. The hosts are compared inabsolute measurements and in percentage measurements.

This navigator item contains the following workspaces:

Host CPU ComparisonThis workspace shows the most heavily used hosts and the leastheavily used hosts in terms of CPU use.

Host Memory Allocation ComparisonThis workspace shows the most heavily used hosts and the leastheavily used hosts in terms of memory allocation.

Host Memory Use ComparisonThis workspace shows the most heavily used hosts and the leastheavily used hosts in terms of memory use.


Host CPU Comparison workspaceThis workspace shows the most heavily used hosts and the least heavilyused hosts in terms of CPU use. The hosts are compared in absolutemeasurements and in percentage measurements. The absolutemeasurements use CPU GHz to enable comparison between differentmachine types. All the CPU measurements can be seen by expanding thetable view holding all the detailed data.

This workspace contains the following views:

Top VM CPU GHz By HostThis view shows the most heavily used hosts based on the absolutemeasurement of CPU CHz consumed by the virtual machines oneach host.

Top Unaccounted CPU GHz By HostThis view shows the least heavily used hosts based on the absolutemeasurement of CPU CHz unaccounted for by the virtualmachines consumption on each host.

Top VM Consumed CPU Percent By HostThis view shows the most heavily used hosts based on thepercentage of the CPU consumed by the virtual machines from thenumber of CPUs on each host.

Top Unaccounted CPU Percent By HostThis view shows the least heavily used hosts based on thepercentage of the CPU that remains unaccounted for aftersubtracting the CPU consumed by the virtual machines on eachhost.

Hosts This view shows all the CPU measurements for each host. The linkat the beginning of each row takes you to the Host Detailworkspace for the selected host.

Host Memory Allocation Comparison workspaceThis workspace shows the most heavily used hosts and the least heavilyused hosts in terms of memory allocation. The hosts are compared inabsolute measurements and in percentage measurements. The absolutemeasurements use GB of memory. All the memory measurements can beseen by expanding the table view holding all the detailed data.


Top Allocated Memory By HostThis view shows the most heavily used hosts based on the absolutemeasurement of GB of memory allocated to the virtual machineson each host.

Top Unallocated Memory By HostThis view shows the least heavily used hosts based on the absolutemeasurement of GB of memory allocated to the virtual machineson each host.

Top Allocated Memory Percent By HostThis view shows the most heavily used hosts based on thepercentage of the GB of memory allocated to the virtual machinesfrom the GB of memory on each host.

Top Unallocated Memory Percent By HostThis view shows the least heavily used hosts based on the

Chapter 3. Workspaces reference 17

percentage of the memory that remains unallocated aftersubtracting the memory allocated to the virtual machines on eachhost.

Hosts This view shows all the memory measurements for each host. Thelink at the beginning of each row takes you to the Host Detailworkspace for the selected host.

Host Memory Use Comparison workspaceThis workspace shows the most heavily used hosts and the least heavilyused hosts in terms of memory use. The hosts are compared in absolutemeasurements and in percentage measurements. The absolutemeasurements use GB of memory. All the memory measurements can beseen by expanding the table view holding all the detailed data.


Top Used Memory By HostThis view shows the most heavily used hosts based on the absolutemeasurement of GB of memory used by the virtual machines oneach host.

Top Unused Memory By HostThis view shows the least heavily used hosts based on the absolutemeasurement of GB of memory used by the virtual machines oneach host.

Top Used Memory Percent By HostThis view shows the most heavily used hosts based on thepercentage of the GB of memory used by the virtual machinesfrom the GB of memory on each host.

Top Unused Memory Percent By HostThis view shows the least heavily used hosts based on thepercentage of the memory that remains unused after subtractingthe memory used by the virtual machines on each host.

Hosts This view shows all the memory measurements for each host. Thelink at the beginning of each row takes you to the Host Detailworkspace for the selected host.

Host Navigator itemHost workspaces

These workspaces show all the hosts being monitored by an agentinstance, as well as detailed information about individual hosts and thedata center resources related to a host.


Host OverviewThis workspace shows all the hosts being monitored by an agentinstance.

Host DetailThis workspace shows detailed information about one host,including trend graphs of CPU and memory use, as well asdefining characteristics, and CPU and memory metrics.

Host RelationsThis workspace shows the data center resources that are related toone host.


Host Detail workspaceThis view shows a trend graph of CPU capacity allocated and consumedby the virtual machines on the host.


CPU Allocated and ConsumedThis view shows a trend graph of CPU capacity allocated andconsumed by the virtual machines on the host.

Memory Allocated and ConsumedThis view shows a trend graph of memory allocated to and usedby the virtual machines on the host.

Host DefinitionThis view shows the defining characteristics of the host.

Host CPUThis view shows the CPU metrics of the host.

Host MemoryThis view shows the memory metrics of the host.

Host Overview workspaceThis workspace shows all the hosts being monitored by an agent instance.Each view shows a different set of metrics about every host. Every row hasa link that takes you to the Host Detail workspace for the selected host.


Host CPU MetricsThis view shows the CPU metrics of every host being monitoredby an agent instance.

Host Memory MetricsThis view shows the memory metrics of every host beingmonitored by an agent instance.

Host DefinitionsThis view shows the defining characteristics of every host beingmonitored by an agent instance.

Host Relations workspaceThis workspace shows the data center resources that are related to onehost.


Virtual MachinesThis view shows the virtual machines on the host.

Storage PoolsThis view shows the storage pools on the host.

Storage Pool Navigator itemStorage Pool workspaces

These workspaces show an overview of the most heavily used and leastheavily used storage pools monitored by an agent instance, as well asdetailed information about individual storage pools.



Storage Pool OverviewThis workspace shows an overview of the most heavily used andleast heavily used storage pools monitored by an agent instance.

Storage Pool DetailThis workspace shows detailed information about one storagepool, including trend graphs of percent storage used and GB ofstorage available, as well as defining characteristics of the storagepool.

Storage Pool Detail workspaceThis workspace shows detailed information about one storage pool,including trend graphs of percent storage used and GB of storageavailable, as well as defining characteristics of the storage pool.


Percent UsedThis view shows a trend graph of percent used of the storage pool.

Storage Available (GB)This view shows a trend graph of the GB of storage available onthe storage pool.

Storage Pool DetailThis view shows the detail metrics of the storage pool.

Storage Pool Overview workspaceThis workspace shows an overview of the most heavily used and leastheavily used storage pools monitored by an agent instance.


Percent UsedThis view shows the most heavily used storage pools based onpercent used.

Storage Available (GB)This view shows the least heavily used storage pools based on GBof storage available.

Storage PoolsThis view shows the detail metrics of every storage pool monitoredby an agent instance.

Virtual Machine Navigator itemVirtual Machine workspaces

These workspaces show an overview of the virtual machines monitored byan agent instance, including the virtual machines consuming the most CPUand the most memory, as well as detailed information about individualvirtual machines.


Virtual Machine OverviewThis workspace shows an overview of the virtual machinesmonitored by an agent instance, including the virtual machinesconsuming the most CPU and the most memory.

Virtual Machine DetailThis workspace shows detailed information about one virtualmachine, including trend graphs of CPU and memory use.


Virtual Machine Detail workspaceThis workspace shows detailed information about one virtual machine,including trend graphs of CPU and memory use.


CPUs ConsumedThis view shows a trend graph of amount of CPUs consumed bythe virtual machine.

CPU PercentThis view shows a trend graph of amount of CPUs consumed as apercent of the number of CPUs allocated to the virtual machine.

Memory UsedThis view shows a trend graph of the GB of memory used by thevirtual machine.

Memory PercentThis view shows a trend graph of amount of memory used as apercent of the memory allocated to the virtual machine.

Virtual Machine DetailThis view shows the detail metrics of the virtual machine.

Virtual Machine Overview workspaceThis workspace shows an overview of the virtual machines monitored byan agent instance, including the virtual machines consuming the most CPUand the most memory.


Top VM CPUs ConsumedThis view shows the virtual machines consuming the most CPU.

Top VM Memory Used (GB)This view shows the virtual machines consuming the mostmemory.

Virtual MachinesThis view shows the detail metrics of every virtual machinemonitored by an agent instance.


Chapter 4. Attributes reference

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

About attributesAttributes are the application properties that are being measured and reported bythe Linux Kernel-based Virtual Machines agent.

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

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

v SituationsYou use attributes to create situations that monitor the state of your operatingsystem, database, or application. A situation describes a condition you want totest. When you start a situation, the Tivoli Enterprise Portal compares the valuesyou have assigned to the situation attributes with the values collected by theLinux Kernel-based Virtual Machines agent and registers an event if thecondition is met. You are alerted to events by indicator icons that are displayedin the Navigator.

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

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

Attribute groups and attributes for the Linux Kernel-based VirtualMachines agent

This monitoring agent contains the following attribute groups. The table namedepends on the maximum table name limits of the target database being used forthe Tivoli Data Warehouse. If the maximum name is 30 characters, then anywarehouse table name longer than 30 characters is shortened to 30 characters.v Attribute group name: Host CPU

– Table name: KV1HOSTCG– Warehouse table name: KV1_HOST_CPU or KV1HOSTCG

v Attribute group name: Host Memory– Table name: KV1HOSTMG– Warehouse table name: KV1_HOST_MEMORY or KV1HOSTMG


v Attribute group name: Hosts– Table name: KV1HOSTAG– Warehouse table name: KV1_HOSTS or KV1HOSTAG

v Attribute group name: Performance Object Status– Table name: KV1POBJST– Warehouse table name: KV1_PERFORMANCE_OBJECT_STATUS or

KV1POBJSTv Attribute group name: Storage Pools

– Table name: KV1STGPLAG– Warehouse table name: KV1_STORAGE_POOLS or KV1STGPLAG

v Attribute group name: Virtual Machines– Table name: KV1VMACHAG– Warehouse table name: KV1_VIRTUAL_MACHINES or KV1VMACHAG

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

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

Attribute descriptionsDescription, type, and Warehouse name (if applicable) for each attribute inthe attribute group

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

Host CPU attribute group

The Host CPU attribute group contains information about host CPU capacity andvirtual machine CPU consumption.

Historical groupThis attribute group is eligible for use with Tivoli Data Warehouse.

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

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.

Type

String

Warehouse nameNODE

Timestamp attribute


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

Type

String

Warehouse nameTIMESTAMP

Host Name attribute - This attribute is a key attribute.

DescriptionThe name of the host.

Type

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

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

Warehouse nameHOST_NAME

Number of CPUs attribute

DescriptionThe number of CPUs in the host.

Type

DEFAULT with enumerated values. The strings are displayed inthe Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v Unavailable (-1)


Warehouse nameNUMBER_OF_CPUS or CPU_COUNT

Number of CPU GHz attribute

DescriptionThe number of CPU GHz in the host.

Type



Warehouse nameNUMBER_OF_CPU_GHZ or GHZ_COUNT

VM CPUs Consumed attribute

Chapter 4. Attributes reference 25

DescriptionThe number of CPUs consumed by the Virtual Machines.

Type



Warehouse nameVM_CPUS_CONSUMED or CPU_CNSMD

VM CPU GHz Consumed attribute

DescriptionThe number of CPU GHz consumed by the Virtual Machines.

Type



Warehouse nameVM_CPU_GHZ_CONSUMED or GHZ_CNSMD

CPUs Unaccounted For attribute

DescriptionThe number of CPU unaccounted for; includes system overheadand idle capacity.

Type



Warehouse nameCPUS_UNACCOUNTED_FOR or CPU_UNACCT

CPU GHz Unaccounted For attribute

DescriptionThe number of CPU GHz unaccounted for; includes systemoverhead and idle capacity.

Type




Warehouse nameCPU_GHZ_UNACCOUNTED_FOR or GHZ_UNACCT

CPUs Consumed Per VM attribute

DescriptionThe number of CPUs consumed by the average virtual machine.

Type



Warehouse nameCPUS_CONSUMED_PER_VM or CPU_PER_VM

CPU GHz Consumed Per VM attribute

DescriptionThe number of CPU GHz consumed by the average virtualmachine.

Type



Warehouse nameCPU_GHZ_CONSUMED_PER_VM or GHZ_PER_VM

Number of Active VMs attribute

DescriptionThe number of active virtual machines.

Type



Warehouse nameNUMBER_OF_ACTIVE_VMS or ACTV_COUNT

CPU Percent Consumed by VMs attribute

DescriptionThe very approximate percent consumed based on CPU capacity


for the host and the consumption by the VMs. Does not take intoaccount hypervisor overhead or non-virtual machine processes.

Type



Warehouse nameCPU_PERCENT_CONSUMED or CNSMD_P

CPU Percent Unaccounted attribute

DescriptionThe very approximate percent available based on CPU capacity forthe host. Does not take into account hypervisor overhead ornon-virtual machine processes.

Type



Warehouse nameCPU_PERCENT_UNACCOUNTED or UNACCT_P

VM CPU Fit Estimate attribute

DescriptionThe very approximate number of virtual machines that fit in theunaccounted CPU capacity.

Type



Warehouse nameVM_CPU_FIT_ESTIMATE or CPU_FIT

Virtual CPUs Allocated attribute

DescriptionThe number of CPUs allocated to active Virtual Machines.

Type

DEFAULT with enumerated values. The strings are displayed inthe Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:


v Unavailable (-1)


Warehouse nameVIRTUAL_CPUS_ALLOCATED or CPU_ALLO

Over Under Allocated CPU attribute

DescriptionThe amount of CPUs allocated to active virtual machines over orunder the amount available of CPUs. Negative values indicate overallocation.

Type



Warehouse nameOVER_UNDER_ALLOCATED_CPU or OV_UN_CPU

Over Under Allocated CPU GHz attribute

DescriptionThe amount of CPU GHz allocated to active virtual machines overor under the amount available of CPU GHz. Negative valuesindicate over allocation.

Type



Warehouse nameOVER_UNDER_ALLOCATED_CPU_GHZ or OV_UN_GHZ

Percent CPU Allocated to VMs attribute

DescriptionThe percent of CPU that is allocated to virutal machines.

Type



Warehouse namePERCENT_CPU_ALLOCATED or C_ALLO_P


Host Memory attribute group

The Host Memory attribute group contains information about host memorycapacity and virtual machine memory consumption.


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



Type

String

Warehouse nameNODE

Timestamp attribute


Type

String




Type




Memory Size attribute

DescriptionThe size of main memory in the host in GB

Type



v Unavailable (-1)


Warehouse nameMEMORY_SIZE or MEMRY_SIZE

VM Memory Allocated attribute

DescriptionThe sum of the amounts of memory promised to each virtualmachine in GB

Type



Warehouse nameVM_MEMORY_ALLOCATED or MEMRY_ALLO

VM Memory Used attribute

DescriptionThe sum of the amounts of memory used by each virtual machinein GB

Type



Warehouse nameVM_MEMORY_USED or MEMRY_USED

Over Under Allocated attribute

DescriptionThe amount of memory allocated to virtual machines over orunder the amount available in GB; negative values indicate overallocation.

Type



Warehouse nameOVER_UNDER_ALLOCATED or OV_UN_ALLO


Over Under Used attribute

DescriptionThe amount of memory used by the virtual machines over orunder the amount available in GB; negative values indicate overuse.

Type



Warehouse nameOVER_UNDER_USED or OV_UN_USED

Percent Memory Allocated attribute

DescriptionThe percent of memory that is allocated to virtual machines

Type



Warehouse namePERCENT_MEMORY_ALLOCATED or M_ALLO_P

Percent Memory Used attribute

DescriptionThe percent of memory that is used by virtual machines

Type



Warehouse namePERCENT_MEMORY_USED or M_USED_P

Percent Memory Unallocated attribute

DescriptionThe percent of memory that is unallocated to virtual machines

Type



v Unavailable (-1)


Warehouse namePERCENT_MEMORY_UNALLOCATED or M_UNALLO_P

Percent Memory Unused attribute

DescriptionThe percent of memory that is unused by virtual machines

Type



Warehouse namePERCENT_MEMORY_UNUSED or M_UNUSED_P


DescriptionThe number of active virtual machines

Type




Memory Allocated Per VM attribute

DescriptionThe memory allocated to an average virtual machine

Type



Warehouse nameMEMORY_ALLOCATED_PER_VM or ALC_PER_VM

Memory Used Per VM attribute

DescriptionThe memory used by the average virtual machine


Type



Warehouse nameMEMORY_USED_PER_VM or USD_PER_VM

VM Memory Allocated Fit Estimate attribute

DescriptionThe very approximate number of virtual machines that fit in theunallocated memory, based on the average memory allocated pervirtual machine.

Type



Warehouse nameVM_MEMORY_ALLOCATED_FIT_ESTIMATE or M_ALLO_FIT

VM Memory Used Fit Estimate attribute

DescriptionThe very approximate number of virtual machines that fit in theunused memory, based on the average memory used per virtualmachine.

Type



Warehouse nameVM_MEMORY_USED_FIT_ESTIMATE or M_USED_FIT

Hosts attribute group

The host attribute group contains information about the host: name and address,hypervisor URI and protocol, number and configuration of CPUs, size of memory,and number of virtual machines.



Attribute descriptionsThe following list contains information about each attribute in the Hosts attributegroup:



Type

String

Warehouse nameNODE

Timestamp attribute


Type

String




Type




IP Address attribute

DescriptionThe IP address used to create the Hypervisor URI.

Type



Warehouse nameIP_ADDRESS or IP_ADDR

Hypervisor URI attribute


DescriptionThe URI used for the connection to the hypervisor.

Type



Warehouse nameHYPERVISOR_URI or HYPER_URI

Protocol attribute

DescriptionThe communications protocol used by the connection to thehypervisor.

Type



Warehouse namePROTOCOL

CPU Model attribute

DescriptionThe model of the CPUs in the host.

Type



Warehouse nameCPU_MODEL

Number of CPUs attribute

DescriptionThe number of CPUs in the host.

Type




Warehouse nameNUMBER_OF_CPUS or CPU_COUNT

CPU Frequency (GHz) attribute

DescriptionThe frequency of the CPUs in the host in GHz.

Type



Warehouse nameCPU_FREQUENCY or CPU_FREQ

Number of CPU GHz attribute

DescriptionThe number of CPU GHz in the host.

Type



Warehouse nameNUMBER_OF_CPU_GHZ or GHZ_COUNT

Number of Nodes attribute

DescriptionThe number of NUMA cells in the host; 1 means uniform memoryaccess.

Type



Warehouse nameNUMBER_OF_NODES or NODE_COUNT

Sockets Per Node attribute

DescriptionThe number of CPU sockets per node in the host.


Type



Warehouse nameSOCKETS_PER_NODE or SKTS_PER

Cores Per Socket attribute

DescriptionThe number of cores per socket in this host.

Type



Warehouse nameCORES_PER_SOCKET or CORES_PER

Threads Per Core attribute

DescriptionThe number of threads per core in the host.

Type



Warehouse nameTHREADS_PER_CORE or THRDS_PER

Memory Size (GB) attribute

DescriptionThe size of main memory in the host in GB.

Type




Warehouse nameMEMORY_SIZE or MEMRY_SIZE

Number of VMs attribute

DescriptionThe number of defined virtual machines in the host.

Type



Warehouse nameNUMBER_OF_VMS or VM_COUNT


DescriptionThe number of active virtual machines in the host.

Type




Performance Object Status attribute group

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


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




Type

String

Warehouse nameNODE

Timestamp attribute


Type

String


Query Name attribute - This attribute is a key attribute.

DescriptionThe name of the attribute group.

Type

String

Warehouse nameQUERY_NAME or ATTRGRP

Object Name attribute

DescriptionThe name of the performance object.

Type

String

Warehouse nameOBJECT_NAME or OBJNAME

Object Type attribute

DescriptionThe type of the performance object.

Type

Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v WMI (0)v PERFMON (1)v WMI ASSOCIATION GROUP (2)v JMX (3)v SNMP (4)v SHELL COMMAND (5)v JOINED GROUPS (6)v CIMOM (7)v CUSTOM (8)


v ROLLUP DATA (9)v WMI REMOTE DATA (10)v LOG FILE (11)v JDBC (12)v CONFIG DISCOVERY (13)v NT EVENT LOG (14)v FILTER (15)v SNMP EVENT (16)v PING (17)v DIRECTOR DATA (18)v DIRECTOR EVENT (19)v SSH REMOTE SHELL COMMAND (20)


Warehouse nameOBJECT_TYPE or OBJTYPE

Object Status attribute

DescriptionThe status of the performance object.

Type

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


Warehouse nameOBJECT_STATUS or OBJSTTS

Error Code attribute

DescriptionThe error code associated with the query

Type

Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v NO ERROR (0)v GENERAL ERROR (1)v OBJECT NOT FOUND (2)v COUNTER NOT FOUND (3)v NAMESPACE ERROR (4)v OBJECT CURRENTLY UNAVAILABLE (5)v COM LIBRARY INIT FAILURE (6)v SECURITY INIT FAILURE (7)


v PROXY SECURITY FAILURE (9)v NO INSTANCES RETURNED (10)v ASSOCIATOR QUERY FAILED (11)v REFERENCE QUERY FAILED (12)v NO RESPONSE RECEIVED (13)v CANNOT FIND JOINED QUERY (14)v CANNOT FIND JOIN ATTRIBUTE IN QUERY 1 RESULTS (15)v CANNOT FIND JOIN ATTRIBUTE IN QUERY 2 RESULTS (16)v QUERY 1 NOT A SINGLETON (17)v QUERY 2 NOT A SINGLETON (18)v NO INSTANCES RETURNED IN QUERY 1 (19)v NO INSTANCES RETURNED IN QUERY 2 (20)v CANNOT FIND ROLLUP QUERY (21)v CANNOT FIND ROLLUP ATTRIBUTE (22)v FILE OFFLINE (23)v NO HOSTNAME (24)v MISSING LIBRARY (25)v ATTRIBUTE COUNT MISMATCH (26)v ATTRIBUTE NAME MISMATCH (27)v COMMON DATA PROVIDER NOT STARTED (28)v CALLBACK REGISTRATION ERROR (29)v MDL LOAD ERROR (30)v AUTHENTICATION FAILED (31)v CANNOT RESOLVE HOST NAME (32)v SUBNODE UNAVAILABLE (33)v SUBNODE NOT FOUND IN CONFIG (34)v ATTRIBUTE ERROR (35)v CLASSPATH ERROR (36)v CONNECTION FAILURE (37)v FILTER SYNTAX ERROR (38)v FILE NAME MISSING (39)v SQL QUERY ERROR (40)v SQL FILTER QUERY ERROR (41)v SQL DB QUERY ERROR (42)v SQL DB FILTER QUERY ERROR (43)v PORT OPEN FAILED (44)v ACCESS DENIED (45)v TIMEOUT (46)v NOT IMPLEMENTED (47)v REQUESTED A BAD VALUE (48)v RESPONSE TOO BIG (49)v GENERAL RESPONSE ERROR (50)v SCRIPT NONZERO RETURN (51)v SCRIPT NOT FOUND (52)v SCRIPT LAUNCH ERROR (53)


v CONF FILE DOES NOT EXIST (54)v CONF FILE ACCESS DENIED (55)v INVALID CONF FILE (56)v EIF INITIALIZATION FAILED (57)v CANNOT OPEN FORMAT FILE (58)v FORMAT FILE SYNTAX ERROR (59)v REMOTE HOST UNAVAILABLE (60)v EVENT LOG DOES NOT EXIST (61)v PING FILE DOES NOT EXIST (62)v NO PING DEVICE FILES (63)v PING DEVICE LIST FILE MISSING (64)v SNMP MISSING PASSWORD (65)


Warehouse nameERROR_CODE or ERRCODE

Last Collection Start attribute

DescriptionThe most recent time a data collection of this group started

Type

Timestamp with enumerated values. The strings are displayed inthe Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v NOT COLLECTED (0691231190000000)


Warehouse nameLAST_COLLECTION_START or COLSTRT

Last Collection Finished attribute

DescriptionThe most recent time a data collection of this group finished

Type

Timestamp with enumerated values. The strings are displayed inthe Tivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v NOT COLLECTED (0691231190000000)


Warehouse nameLAST_COLLECTION_FINISHED or COLFINI

Last Collection Duration attribute

DescriptionThe duration of the most recently completed data collection of thisgroup in seconds


Type

Real number (32-bit counter) with 2 decimal places of precision

Warehouse nameLAST_COLLECTION_DURATION or COLDURA

Average Collection Duration attribute

DescriptionThe average duration of all data collections of this group inseconds

Type

Real number (32-bit counter) with 2 decimal places of precisionwith enumerated values. The strings are displayed in the TivoliEnterprise Portal. The warehouse and queries return the valuesshown in parentheses. The following values are defined:v NO DATA (-100)


Warehouse nameAVERAGE_COLLECTION_DURATION or COLAVGD

Refresh Interval attribute

DescriptionThe interval at which this group is refreshed in seconds

Type

Integer (32-bit counter)

Warehouse nameREFRESH_INTERVAL or REFRINT

Number of Collections attribute

DescriptionThe number of times this group has been collected since agent start

Type


Warehouse nameNUMBER_OF_COLLECTIONS or NUMCOLL

Cache Hits attribute

DescriptionThe number of times an external data request for this group wassatisfied from the cache

Type


Warehouse nameCACHE_HITS or CACHEHT

Cache Misses attribute


DescriptionThe number of times an external data request for this group wasnot available in the cache

Type


Warehouse nameCACHE_MISSES or CACHEMS

Cache Hit Percent attribute

DescriptionThe percentage of external data requests for this group that weresatisfied from the cache

Type

Real number (32-bit counter) with 2 decimal places of precision

Warehouse nameCACHE_HIT_PERCENT or CACHPCT

Intervals Skipped attribute

DescriptionThe number of times a background data collection for this groupwas skipped because the previous collection was still runningwhen the next one was due to start

Type


Warehouse nameINTERVALS_SKIPPED or INTSKIP

Storage Pools attribute group

The Storage Pool attribute group contains information about storage pools,including storage pool name, containing host name, UUID, state, type, capacity,used, available, and percent used.


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



Type

String

Warehouse nameNODE

Timestamp attribute



Type

String




Type




Storage Pool Name attribute - This attribute is a key attribute.

DescriptionThe name of the storage pool.

Type



Warehouse nameSTORAGE_POOL_NAME or STGPL_NAME

Storage Pool UUID attribute

DescriptionThe UUID of the storage pool.

Type



Warehouse nameSTORAGE_POOL_UUID or STGPL_UUID

Storage Pool State attribute


DescriptionThe run state of the storage pool.

Type

String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v Unavailable (unavailable)v Initializing (VIR_STORAGE_POOL_BUILDING)v Degraded (VIR_STORAGE_POOL_DEGRADED)v Inactive (VIR_STORAGE_POOL_INACTIVE)v Running (VIR_STORAGE_POOL_RUNNING)


Warehouse nameSTORAGE_POOL_STATE or STGPL_STAT

Storage Pool Type attribute

DescriptionThe type of the storage pool, which is one of 'dir', 'fs', 'netfs', 'disk','iscsi', or 'logical'.

Type



Warehouse nameSTORAGE_POOL_TYPE or STGPL_TYPE

Storage Pool Capacity (GB) attribute

DescriptionThe storage capacity of the storage pool in GB.

Type



Warehouse nameSTORAGE_POOL_CAPACITY or STG_CAPCTY

Storage Pool Used (GB) attribute

DescriptionThe amount of storage used from the storage pool in GB.

Type




Warehouse nameSTORAGE_POOL_USED or STG_USED

Storage Pool Available (GB) attribute

DescriptionThe amount of storage available in the storage pool in GB.

Type



Warehouse nameSTORAGE_POOL_AVAILABLE or STG_AVAIL

Percent Used (%) attribute

DescriptionThe amount of storage used from the storage pool as a percent ofthe total capacity.

Type



Warehouse namePERCENT_USED or PCT_USED

Virtual Machines attribute group

The Virtual Machine attribute group contains information about virtual machines,including virtual machine name, containing host name, UUID, state, number ofCPUs, CPU time, memory used, life-cycle control, and CPU requirements.


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




Type

String

Warehouse nameNODE

Timestamp attribute


Type

String




Type




Virtual Machine Name attribute - This attribute is a key attribute.

DescriptionThe name of the virtual machine.

Type



Warehouse nameVIRTUAL_MACHINE_NAME or VM_NAME

Virtual Machine UUID attribute

DescriptionThe UUID of the virtual machine.

Type




Warehouse nameVIRTUAL_MACHINE_UUID or VM_UUID

Virtual Machine State attribute

DescriptionThe running state of the virtual machine.

Type

String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v Unavailable (unavailable)v Blocked (VIR_DOMAIN_BLOCKED)v Crashed (VIR_DOMAIN_CRASHED)v No State (VIR_DOMAIN_NOSTATE)v Paused (VIR_DOMAIN_PAUSED)v Running (VIR_DOMAIN_RUNNING)v Shutting Down (VIR_DOMAIN_SHUTDOWN)v Shut Off (VIR_DOMAIN_SHUTOFF)


Warehouse nameVIRTUAL_MACHINE_STATE or VM_STATE

Virtualization Type attribute

DescriptionThe type of virtualization used by this virtual machine. 'hvm'means full virtualization, which is used by KVM; 'linux' meanspara virtualization, which is used by XEN.

Type



Warehouse nameVIRTUALIZATION_TYPE or VIRT_TYPE

Number Of Virtual CPUs attribute

DescriptionThe number of virtual CPUs in the virtual machine.

Type




Warehouse nameNUMBER_OF_VIRTUAL_CPUS or VCPU_COUNT

Sample Timestamp attribute

DescriptionThe date and time UTC of the most recent CPU measurement.

Type

String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v Unavailable (0000-00-00 00:00:00)


Warehouse nameSAMPLE_TIMESTAMP or SAMP_TS

Sample Time Delta (sec) attribute

DescriptionThe time duration of the most recent measurement period inseconds.

Type



Warehouse nameSAMPLE_TIME_DELTA or SAMP_DELTA

Total CPU Time (sec) attribute

DescriptionThe CPU time used in seconds.

Type



Warehouse nameCPU_TIME


CPU Time Delta (sec) attribute

DescriptionThe CPU time used during the most recent measurement period inseconds.

Type



Warehouse nameCPU_TIME_DELTA or CPU_DELTA

CPUs Consumed attribute

DescriptionThe equivalent number of real CPUs consumed by this virtualmachine.

Type



Warehouse nameCPUS_CONSUMED or CPU_CNSMD

CPU Percent attribute

DescriptionThe composite CPU percent of this virtual machine across allvirtual CPUs.

Type



Warehouse nameCPU_PERCENT or CPU_PCT

Memory Allocated (GB) attribute

DescriptionThe maximum memory allocated and available for the virtualmachine in GB.

Type




Warehouse nameMEMORY_ALLOCATED or MEMRY_ALLO

Memory Used (GB) attribute

DescriptionThe memory used by the virtual machine in GB.

Type



Warehouse nameMEMORY_USED or MEMRY_USED

Memory Percent attribute

DescriptionThe percent of allocated memory that has been used by this virtualmachine.

Type



Warehouse nameMEMORY_PERCENT or MEMRY_PCT

Action On PowerOff attribute

DescriptionThe action to take when the virtual machine requests a power-off.

Type



Warehouse nameACTION_ON_POWEROFF or ACTN_PWROF


Action On Reboot attribute

DescriptionThe action to take when the virtual machine requests a restart.

Type



Warehouse nameACTION_ON_REBOOT or ACTN_RBOOT

Action On Crash attribute

DescriptionThe action to take when the virtual machine crashes.

Type



Warehouse nameACTION_ON_CRASH or ACTN_CRASH

CPU Match attribute

DescriptionHow strictly the virtual CPU provided to the virtual machine mustmatch these requirements.

Type

String with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:v Unavailable (unavailable)v Minimum (minimum)v Exact (exact)v Strict (strict)


Warehouse nameCPU_MATCH

CPU Model attribute

DescriptionThe CPU model requested for the virtual machine.

Type




Warehouse nameCPU_MODEL

Number of Sockets attribute

DescriptionThe requested number of CPU sockets for the virtual machine.

Type



Warehouse nameNUMBER_OF_SOCKETS or SKTS_COUNT

Cores Per Socket attribute

DescriptionThe requested number of cores per socket for the virtual machine.

Type



Warehouse nameCORES_PER_SOCKET or CORES_PER

Threads Per Core attribute

DescriptionThe requested number of threads per core for the virtual machine.

Type



Warehouse nameTHREADS_PER_CORE or THRDS_PER


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

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

attribute group is configured to be written to the warehouse. The table namelisted here corresponds to the table name in “Attribute groups and attributes forthe Linux Kernel-based Virtual Machines agent” on page 23

v Attribute group is the name of the attribute group used to create the table in thewarehouse database if it is short enough to fit in the table naming constraints ofthe database being used for the warehouse. The attribute group name listed herecorresponds to the Warehouse table name in “Attribute groups and attributes forthe Linux Kernel-based Virtual Machines agent” on page 23.

v Bytes per row (agent) is an estimate of the record length for each row or instancewritten to the agent disk for historical data collection. This estimate can be usedfor agent disk space planning purposes.

v Database bytes per row (warehouse) is an estimate of the record length for detailedrecords written to the warehouse database, if the attribute group is configured tobe written to the warehouse. Detailed records are records that have beenuploaded from the agent for long-term historical data collection. This estimatecan be used for warehouse disk space planning purposes.

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

In addition to the information in the tables, you must know the number of rows ofdata that you plan to collect. An attribute group can have single or multiple rowsof data depending on the application environment that is being monitored. Forexample, if your attribute group is monitoring each processor in your computerand you have a dual processor computer, the number of rows is two.

The following table contains capacity planning information for the data logged byIBM Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based VirtualMachines.

Table 1. Capacity planning for historical data logged by the Linux Kernel-based Virtual Machines agent

Table Attribute group

Bytes perrow(agent)

Databasebytes perrow(warehouse)

Aggregatebytes perrow(warehouse)

KV1HOSTAG KV1_HOSTS 810 845 1336

KV1HOSTCG KV1_HOST_CPU 459 568 1389

KV1HOSTMG KV1_HOST_MEMORY 443 558 1301

KV1POBJST KV1_PERFORMANCE_OBJECT_STATUS 352 399 664

KV1STGPLAG KV1_STORAGE_POOLS 730 767 1008


Table 1. Capacity planning for historical data logged by the Linux Kernel-based Virtual Machines agent (continued)

Table Attribute group

Bytes perrow(agent)

Databasebytes perrow(warehouse)

Aggregatebytes perrow(warehouse)

KV1VMACHAG KV1_VIRTUAL_MACHINES 906 989 1606

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


Chapter 5. Situations reference

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

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

The monitoring agents that you use to monitor your system environment include aset of predefined situations that you can use as-is. You can also create newsituations to meet your requirements. Predefined situations contain attributes thatcheck for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can beginusing the Linux Kernel-based Virtual Machines agent. You can change theconditions or values being monitored by a predefined situation to the conditions orvalues best suited to your enterprise.

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

FormulaFormula describing condition being tested.

DistributionList of managed systems (operating systems, subsystems, or applications)to which the situation can be distributed. All the Linux Kernel-basedVirtual Machines agent managed systems are assigned by default.

Expert adviceComments and instructions to be read in the event workspace.

ActionCommand to be sent to the system.

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

More information about situationsThe Tivoli Enterprise Portal User's Guide contains more information about predefinedand custom situations and how to use them to respond to alerts.

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


Predefined situationsThis monitoring agent contains the following predefined situations, which areorganized by Navigator item.

Agent level Navigator itemsv Linux KVM

– Not applicablev Host

– KV1_Host_CPU_Over_Commit_Info– KV1_Host_CPU_Over_Commit_Warn– KV1_Host_CPU_Over_Commit_Crit– KV1_Host_CPU_Pct_High_Warn– KV1_Host_CPU_Pct_High_Crit– KV1_Host_Mem_Pct_High_Warn– KV1_Host_Mem_Pct_High_Crit

v Storage Pool– Not applicable

v Virtual Machine– KV1_VM_CPU_Pct_High_Warn– KV1_VM_CPU_Pct_High_Crit– KV1_VM_Mem_Pct_High_Warn– KV1_VM_Mem_Pct_High_Crit

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

DescriptionInformation about the conditions that the situation tests.

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

DistributionWhether the situation is automatically distributed to instances of the agentor is available for manual distribution.

Run at startupWhether the situation starts monitoring when the agent starts.

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

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

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


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

Linux KVM Navigator itemNo predefined situations are included for this Navigator item.

Host Navigator item

KV1_Host_CPU_Over_Commit_Info situation

DescriptionThe CPU of your host is over committed.

The situation is evaluated for each distinct value of the HOST_NAME attribute.

Formula*IF *VALUE KV1_HOST_CPU.Percent_CPU_Allocated *GE 100 *AND *VALUEKV1_HOST_CPU.Percent_CPU_Allocated *LT 125

See “Attribute groups and attributes for the Linux Kernel-based Virtual Machinesagent” on page 23 for descriptions of the attributes in this formula.

DistributionThis situation is available for distribution.

Run at startupNo

Sampling interval15 minutes

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

SeverityInformational

Clearing conditionsThe situation clears when the condition becomes false.

KV1_Host_CPU_Over_Commit_Warn situation

DescriptionThe CPU of your host is moderately over committed.


Formula*IF *VALUE KV1_HOST_CPU.Percent_CPU_Allocated *GE 125 *AND *VALUEKV1_HOST_CPU.Percent_CPU_Allocated *LT 150

Chapter 5. Situations reference 61



Run at startupNo



SeverityWarning


KV1_Host_CPU_Over_Commit_Crit situation

DescriptionThe CPU of your host is highly over committed.


Formula*IF *VALUE KV1_HOST_CPU.Percent_CPU_Allocated *GE 150



Run at startupNo



SeverityCritical



KV1_Host_CPU_Pct_High_Warn situation

DescriptionYour host has chronically low available CPU capacity.


Formula*IF *VALUE KV1_HOST_CPU.CPU_Percent_Consumed *GE 85 *UNTIL ( *SITKV1_Host_CPU_Pct_High_Crit )



Run at startupNo



SeverityWarning


KV1_Host_CPU_Pct_High_Crit situation

DescriptionYour host has persistently low available CPU capacity.


Formula*IF *VALUE KV1_HOST_CPU.CPU_Percent_Consumed *GE 85



Run at startupNo




SeverityCritical


KV1_Host_Mem_Pct_High_Warn situation

DescriptionThe memory utilization of the host is persistently high.


Formula*IF *VALUE KV1_HOST_MEMORY.Percent_Memory_Used *GE 95 *UNTIL ( *SITKV1_Host_Mem_Pct_High_Crit )



Run at startupNo



SeverityWarning


KV1_Host_Mem_Pct_High_Crit situation

DescriptionThe memory utilization of the host is chronically high.


Formula*IF *VALUE KV1_HOST_MEMORY.Percent_Memory_Used *GE 95




Run at startupNo



SeverityCritical


Storage Pool Navigator itemNo predefined situations are included for this Navigator item.

Virtual Machine Navigator item

KV1_VM_CPU_Pct_High_Warn situation

DescriptionThe CPU utilization of the virtual machine is persistently high.


Formula*IF *VALUE KV1_VIRTUAL_MACHINES.CPU_Percent *GE 95 *UNTIL ( *SITKV1_VM_CPU_Pct_High_Crit )



Run at startupNo



SeverityWarning



KV1_VM_CPU_Pct_High_Crit situation

DescriptionThe CPU utilization of the virtual machine is chronically high.


Formula*IF *VALUE KV1_VIRTUAL_MACHINES.CPU_Percent *GE 95



Run at startupNo



SeverityCritical


KV1_VM_Mem_Pct_High_Warn situation

DescriptionThe memory utilization of the VM is persistently high.


Formula*IF *VALUE KV1_VIRTUAL_MACHINES.Memory_Percent *GE 95 *UNTIL ( *SITKV1_VM_Mem_Pct_High_Crit )



Run at startupNo




SeverityWarning


KV1_VM_Mem_Pct_High_Crit situation

DescriptionThe memory utilization of the VM is chronically high.


Formula*IF *VALUE KV1_VIRTUAL_MACHINES.Memory_Percent *GE 95



Run at startupNo



SeverityCritical



Chapter 6. Take Action commands reference

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

About Take Action commandsTake Action commands can be run from the portal client or included in a situationor a policy.

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

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

A basic Take Action command shows the return code of the operation in a messagebox that is displayed after the action is completed or in a log file. After you closethis window, no further information is available for this action.

More information about Take Action commandsFor more information about working with Take Action commands, see the IBMTivoli Enterprise Portal User's Guide.

Predefined Take Action commandsThe Linux Kernel-based Virtual Machines agent does not provide predefined TakeAction commands.


Chapter 7. Policies reference

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

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

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

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

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

Predefined policiesThe Linux Kernel-based Virtual Machines agent does not provide predefinedpolicies.


Chapter 8. Troubleshooting

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

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in the Prerequisites topic for the agent in theinformation center.

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

Table 2. Information to gather before contacting IBM Software Support

Information type Description

Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectoryon the host computer. See “Trace logging” on page 74 for lists of all trace log files andtheir locations. See the Tivoli Enterprise Portal User's Guide for general information aboutthe IBM Tivoli Monitoring environment.

Linux Kernel-basedVirtual Machineinformation

Version number and patch level

Operating system Operating system version number and patch level

Messages Messages and other information displayed on the screen

Version numbers forIBM Tivoli Monitoring

Version number of the following members of the monitoring environment:v IBM Tivoli Monitoring. Also provide the patch level, if available.v IBM Tivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual

Machines

Screen captures Screen captures of incorrect output, if any

You can use the pdcollect tool to collect the most commonly used information froma system. This tool gathers log files, configuration information, versioninformation, and other data. See the "pdcollect tool" section in the "Tools" chapterof the IBM Tivoli Monitoring Troubleshooting Guide for more information about usingthis tool.

See http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general) for information about working with IBM SoftwareSupport.

Built-in troubleshooting featuresThe primary troubleshooting feature in the Linux Kernel-based Virtual Machinesagent is logging. Logging refers to the text messages and trace data that isgenerated by the Linux Kernel-based Virtual Machines agent. Messages and tracedata are sent to a file.


http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

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

Problem classificationThe following types of problems might occur with the Linux Kernel-based VirtualMachines agent:v Installation and configurationv General usage and operationv Display of monitoring datav Take Action commands

This chapter provides symptom descriptions and detailed workarounds for theseproblems, and describes the logging capabilities of the monitoring agent. See theIBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.

Trace loggingTrace logs capture information about the operating environment when componentsoftware fails to operate as designed. The principal log type is the RAS (Reliability,Availability, and Serviceability) trace log. These logs are in the English languageonly. The RAS trace log mechanism is available for all components of IBM TivoliMonitoring. Most logs are located in a logs subdirectory on the host computer. Seethe following sections to learn how to configure and use trace logging:v “Principal trace log files” on page 75v “Examples: using trace logs” on page 77v “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 aproblem to its source or to determine why an error occurred. All components inthe IBM Tivoli Monitoring environment have a default tracing level. The tracinglevel can be changed on a per-component level to adjust the type of traceinformation collected, the degree of trace detail, the number of trace logs to bekept, and the amount of disk space used for tracing.

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

Linux and UNIX systemshostname_productcode_HEXtimestamp-nn.log

where:

hostnameHost name of the computer where the monitoring component is running.


productcodeTwo-character product code. For IBM Tivoli Monitoring for Virtual ServersAgent for Linux Kernel-based Virtual Machines, the product code is v1.

programName of the program being run.

HEXtimestampHexadecimal time stamp representing the time at which the programstarted.

nn Rolling log suffix.

Principal trace log files

Table 3 contains locations, file names, and descriptions of trace logs that can helpdetermine the source of problems with agents.

Table 3. Trace log files for troubleshooting agents

System where logis located File name and path Description

On the TivoliEnterpriseMonitoring Server

v Windows: The file in theinstall_dir\InstallITM path

v Linux: The candle_installation.log filein the install_dir/logs path

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


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

Provides details about the configuration of datawarehousing for historical reporting.


The name of the RAS log file is as follows:

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

v Linux: install_dir/logs/hostname_ms_timestamp-nn.log

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

Traces activity on the monitoring server.

On the TivoliEnterprise PortalServer

The name of the RAS log file is as follows:

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

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

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

Traces activity on the portal server.

On the TivoliEnterprise PortalServer

The teps_odbc.log file is located in thefollowing path:

v Windows: install_dir\InstallITM

v Linux: install_dir/logs

When you enable historical reporting, this log filetraces the status of the warehouse proxy agent.

Chapter 8. Troubleshooting 75

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

System where logis located File name and path Description

On the computerthat hosts themonitoring agent

The RAS1 log files are as follows:

v Linux:hostname_BegiN_SHORT_PRODUCT_CODE_LOWER_EnD_HEXtimestamp-nn.log in theinstall_dir/logs directory

These logs are in the following directories:


On Linux systems, the followingadditional logs are provided:

– hostname_v1_timestamp.log

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

Traces activity of the monitoring agent.


The agent operations log files are as follows:

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

instance_hostname_V1.LG1 is the backup ofthe previous log.

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


Shows whether the agent could connect to themonitoring server. Shows which situations arestarted and stopped, and shows other eventswhile the agent is running. A new version of thisfile is generated every time the agent is restarted.

IBM Tivoli Monitoring generates one backupcopy of the *.LG0 file with the tag .LG1. View the.LG1 tag to learn the following details regardingthe previous monitoring session:v Status of connectivity with the monitoring

serverv Situations that were runningv The success or failure status of Take Action

commands


The Take Action command log files are asfollows:

v

v1_data_provider_actions_instance_n.log

The logs are in the following directories:


Traces activity each time a Take Action commandruns. For example, when a hypotheticalstart_command Take Action command runs, IBMTivoli Monitoring generates a start_command.logfile.

Definitions of variables:

timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), asfollows: yyyymmdd hhmm

HEXtimestamp is a hexadecimal representation of the time at which the process was started.

install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir canrepresent a path on the computer that hosts 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. But, the first isalways retained because it includes configuration parameters.

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

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


Examples: using trace logsIBM Software Support applies specialized knowledge to analyze trace logs todetermine the source of problems. You can open trace logs in a text editor to learnsome basic facts about your IBM Tivoli Monitoring environment. The followingexamples are from the IBM Tivoli Enterprise Monitoring Server log.

Example oneThis excerpt shows the typical log for a failed connection between amonitoring agent and a monitoring server with the host name server1a:

(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect tobroker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unableto find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

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

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

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

to form a unique name (SERVER5B:V1) for this instance of the LinuxKernel-based Virtual Machines agent. By using this unique name, youcan distinguish multiple monitoring products that might be running onSERVER5B.

v The log shows when the agent started (ON-LINE) and later stopped(OFF-LINE) in the environment.

v For the sake of brevity, an ellipsis (...) represents the series of trace logentries that were generated while the agent was running.

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

v The ON-LINE and OFF-LINE log entries are always available in thetrace log. All trace levels that are described in “Setting RAS traceparameters” on page 78 provide these entries.

On Windows systems, you can use the following alternate method to view tracelogs:1. In the Windows Start menu, click Program Files > IBM Tivoli Monitoring >

Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli EnterpriseMonitoring Services window is displayed.

2. Right-click a component and click Advanced > View Trace Log in the menu.For example, if you want to view the trace log of the Linux Kernel-basedVirtual Machines agent, right-click the name of that agent in the window. Youcan also use the viewer to access remote logs.

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


Setting RAS trace parameters

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

Background InformationThe Linux Kernel-based Virtual Machines agent uses RAS1 tracing and generatesthe logs described in Table 3 on page 75. The default RAS1 trace level is ERROR.

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

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

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

Use collector trace logs as an additional source of troubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting cangenerate a large amount of trace logging. Use these settings onlytemporarily while you are troubleshooting problems. Otherwise, the logs canoccupy excessive amounts of hard disk space.

Problems and workaroundsThe following sections provide symptoms and workarounds for problems thatmight occur with the Linux Kernel-based Virtual Machines agent:v “Installation and configuration troubleshooting” on page 79v “Remote deployment troubleshooting” on page 82v “Agent troubleshooting” on page 82v “Workspace troubleshooting” on page 84v “Situation troubleshooting” on page 85v “Take Action commands troubleshooting” on page 89

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in the Prerequisites topic for the agent in theinformation center.

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


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

Table 4. Problems and solutions for installation and configuration

Problem Solution

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

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

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

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

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

If a message similar to "Unable to find running CMS onCT_CMSLIST" is displayed in the log file, the agent cannotconnect to the monitoring server. Confirm the followingpoints:

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

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

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

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


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

Problem Solution

Installation on RHEL Linux 64-bit systems usesinstall.sh. Running this script fails with a "runGSkitfailure: Return error code: 99".

GSkit is called by install.sh and fails when runGSkitcalls verifyInstall. Review the InstallDirectory/logs/candle_installation.log file and look for references torunGSkit.

For example, output similar to the following might bepresent:

runGSkit: ----- Running command:/opt/IBM/ITM/li6243/gs/bin/private_verifyinstall

/opt/IBM/ITM/li6243/gs/bin/gsk7ver:error while loading shared libraries:

libstdc++.so.5:cannot open shared object file:

No such file or directoryError: Verify FailedExpected Details of gskit in /opt/IBM/ITM/li6243/gsrunGSkit: return code from command is 99runGSkit: ----- End of running command -----runGSkit: error Return error code: 99runGSkit: error GSKit check failure, script:

/opt/IBM/ITM/li6243/gs/bin/private_verifyinstallrunGSkit: error li6243 - GSK check error,

verifyInstall test failed

In the previous example, the 32-bit version of thelibstdc++.so.5 file is not present. This file comes fromthe package compat-libstdc++-33-3.2.3-XX.i686.rpm, whichis not installed on 64-bit RHEL systems by default. Whenthis package is installed, the problem no longer occurs.

After installation, the KVM agent instance fails to start.The following message appears in the agent log:

(4CF55620.003F-1:kbbssge.c,52,"BSS1_GetEnv")KBB_SIG1="-asyncoff -syncoff -dumpoff"(4CF55620.0040-1:signalmanager.cpp,170,"startManagerThread") Error starting signalmanager thread. Return code = 11; Resourcetemporarily unavailable. Use the returncode and message to investigate the failure. Agentis terminating.

The probable cause of the problem is the public domainKorn shell, pdksh. Uninstall the pdksh shell and install theksh rpm that is included on the Linux installation media.


Table 5. General problems and solutions for uninstallation

Problem Solution

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

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

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

a. Use Manage Tivoli Enterprise Monitoring Services.

b. Select Tivoli Enterprise Monitoring Server.

c. Right-click and select Advanced.

d. Select Remove TEMS application support.

e. Select the agent to remove its application support.

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

v Uninstall a single monitoring agent for a specific database.

-OR-

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

3. Uninstall IBM Tivoli Monitoring.

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

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

1. Click the Enterprise icon in the Navigator tree.

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

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

To uninstall the monitoring agent, use the procedure described in the IBM TivoliMonitoring Installation and Setup Guide.

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

If the agent supports multiple instances, IBM Tivoli Monitoring automaticallycreates a name for each monitoring component by concatenating the subsystemname, host name, and product code separated by colons(subsystem_name:hostname:KV1).Note: When you monitor a multinode system, such as a database, IBM TivoliMonitoring adds a subsystem name to the concatenated name, typically adatabase instance name.

The length of the name that IBM Tivoli Monitoring generates is limited to 32characters. Truncation can result in multiple components having the same32-character name. If this problem happens, shorten the hostname portion of thename as follows:

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

v On UNIX and Linux: itm_home/config/product_code.ini andproduct_code.config. For example, the file names for the MonitoringAgent for UNIX OS is ux.ini and ux.config.

2. Find the line that begins with CTIRA_HOSTNAME=.

3. Type a new name for host name that is a unique, shorter name for the hostcomputer. The final concatenated name including the subsystem name, newhost name, and KV1, cannot be longer than 32 characters.Note: You must ensure that the resulting name is unique with respect to anyexisting monitoring component that was previously registered with the IBMTivoli Enterprise Monitoring Server.

4. Save the file.

5. Restart the agent.


Table 5. General problems and solutions for uninstallation (continued)

Problem Solution

The software inventory tag forthe agent on UNIX and Linuxsystems is not removed duringuninstallation of the agent.

After uninstalling the agent, manually remove the file named full name ofagent.cmptag from the $CANDLEHOME/properties/version/ directory.

Remote deployment troubleshootingTable 6 lists problems that might occur with remote deployment. This sectionprovides information about troubleshooting remote deployment of the monitoringagent. See the IBM Tivoli Monitoring Troubleshooting Guide for generaltroubleshooting information.

This section describes problems and solutions for remote deployment and removalof agent software using Agent Remote Deploy process.

Table 6. Remote deployment problems and solutions

Problem Solution

While you are using the remote deployment featureto install the Linux Kernel-based Virtual Machinesagent, an empty command window is displayed onthe target computer. This problem occurs when thetarget of remote deployment is a Windowscomputer. (See the IBM Tivoli Monitoring Installationand Setup Guide for more information about theremote deployment feature.)

Do not close or modify this window. It is part of theinstallation process and is dismissed automatically.

The removal of a monitoring agent fails when youuse the remote removal process in the IBM TivoliEnterprise Portal desktop or browser.

This problem might occur when you attempt the remoteremoval process immediately after you have restarted theIBM Tivoli Enterprise Monitoring Server. You must allowtime for the monitoring agent to refresh its connection withthe IBM Tivoli Enterprise Monitoring Server before you beginthe remote removal process.

Agent troubleshootingThis section lists problems that might occur with agents.

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

Table 7. Agent problems and solutions

Problem Solution

Log data accumulates toorapidly.

Check the RAS trace option settings, which are described in “Setting RAS traceparameters” on page 78. The trace options settings that you can set on theKBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.

If you want to receive multipletrace logs for separate calls orstarts of the same Take Actioncommand, leaving this setting onpermanently fills the availabledisk space.

Do not leave this setting on permanently. By doing so, you create a new log filefor each call or start of the Take Action command and all of them are left on theagent system.


Table 7. Agent problems and solutions (continued)

Problem Solution

When using the itmcmd agentcommands to start or stop thismonitoring agent, you receivethe following error message:

KCIIN0201E Specified productis not configured.

Include the command option -o to specify the instance to start or stop. Theinstance name must match the name used for configuring the agent. Forexample:

./itmcmd agent -o SNMP start v1

For information about using the itmcmd commands, see the IBM TivoliMonitoring Command Reference.

A configured and runninginstance of the monitoring agentis not displayed in the IBMTivoli Enterprise Portal, butother instances of the monitoringagent on the same system aredisplayed in the portal.

Tivoli Monitoring products use Remote Procedure Call (RPC) to define andcontrol product behavior. RPC is the mechanism that a client process uses tomake a subroutine call (such as GetTimeOfDay or ShutdownServer) to a serverprocess somewhere in the network. Tivoli processes can be configured to useTCP/UDP, TCP/IP, SNA, and SSL as the protocol (or delivery mechanism) forRPCs that you want.

IP.PIPE is the name given to Tivoli TCP/IP protocol for RPCs. The RPCs aresocket-based operations that use TCP/IP ports to form socket addresses. IP.PIPEimplements virtual sockets and multiplexes all virtual socket traffic across asingle physical TCP/IP port (visible from the netstat command).

A Tivoli process derives the physical port for IP.PIPE communications based onthe configured, well-known port for the hub Tivoli Enterprise Monitoring Server.(This well-known port or BASE_PORT is configured by using the 'PORT:'keyword on the KDC_FAMILIES / KDE_TRANSPORT environment variable anddefaults to '1918'.)

The physical port allocation method is defined as (BASE_PORT + 4096*N), whereN=0 for a Tivoli Enterprise Monitoring Server process and N={1, 2, ..., 15} foranother type of monitoring server process. Two architectural limits result as aconsequence of the physical port allocation method:

v No more than one Tivoli Enterprise Monitoring Server reporting to a specificTivoli Enterprise Monitoring Server hub can be active on a system image.

v No more than 15 IP.PIPE processes can be active on a single system image.

A single system image can support any number of Tivoli Enterprise MonitoringServer processes (address spaces) if each Tivoli Enterprise Monitoring Server onthat image reports to a different hub. By definition, there is one Tivoli EnterpriseMonitoring Server hub per monitoring enterprise, so this architecture limit hasbeen simplified to one Tivoli Enterprise Monitoring Server per system image.

No more than 15 IP.PIPE processes or address spaces can be active on a singlesystem image. With the first limit expressed above, this second limitation refersspecifically to Tivoli Enterprise Monitoring Agent processes: no more than 15agents per system image.

This limitation can be circumvented (at current maintenance levels, IBM® TivoliMonitoring V6.1, Fix Pack 4 and later) if the Tivoli Enterprise Monitoring Agentprocess is configured to use the EPHEMERAL IP.PIPE process. (This process isIP.PIPE configured with the 'EPHEMERAL:Y' keyword in the KDC_FAMILIES /KDE_TRANSPORT environment variable). There is no limitation to the numberof ephemeral IP.PIPE connections per system image. If ephemeral endpoints areused, the Warehouse Proxy Agent is accessible from the IBM Tivoli EnterpriseMonitoring Server associated with the agents using ephemeral connections eitherby running the Warehouse Proxy Agent on the same computer or by using theFirewall Gateway feature. (The Firewall Gateway feature relays the WarehouseProxy Agent connection from the Tivoli Enterprise Monitoring Server computerto the Warehouse Proxy Agent computer if the Warehouse Proxy Agent cannotcoexist on the same computer.)


Workspace troubleshootingTable 8 shows problems that might occur with workspaces. This chapter providesagent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information.

Table 8. Workspace problems and solutions

Problem Solution

The process application components areavailable, but the Availability status showsPROCESS_DATA_NOT_ AVAILABLE.

This problem occurs because the PerfProc performance object isdisabled. When this condition exists, IBM Tivoli Monitoringcannot collect performance data for this process. Perform thefollowing steps to confirm that this problem exists and resolve it:

1. In the Windows Start menu, click Run.

2. Type perfmon.exe in the Open field of the Run window. ThePerformance window is displayed.

3. Click the plus sign (+) in the toolbar located above the rightpane. The Add Counters window is displayed.

4. Look for Process in the Performance object menu.

5. Perform one of the following actions:

v If you see Process in the menu, the PerfProc performanceobject is enabled and the problem is coming from adifferent source. You might need to contact IBM SoftwareSupport.

v If you do not see Process in the menu, use the Microsoftutility from the following website to enable the PerfProcperformance object:

http://blogs.technet.com/mscom/archive/2008/12/18/the-mystery-of-the-missing-process-performance-counter-in-perfmon.aspx

The Process performance object becomes visible in thePerformance object menu of the Add Counters windows,and IBM Tivoli Monitoring is able to detect Availabilitydata.

6. Restart the monitoring agent.

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute name.

At the bottom of each view, you see thefollowing Historical workspace KFWITM220Eerror: Request failed during execution.

Ensure that you configure all groups that supply data to theview. In the Historical Configuration view, ensure that datacollection is started for all groups that supply data to the view.





Table 8. Workspace problems and solutions (continued)

Problem Solution

You start collection of historical data but the datacannot be seen.

Use the following managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See the IBM Tivoli Monitoring Administrator's Guide forinformation about managing this feature including how to setthe interval at which data is collected. By setting a morefrequent interval for data collection, you reduce the load onthe system incurred every time data is uploaded.

v You use the Summarization and Pruning agent to collectspecific amounts and types of historical data. Historical data isnot displayed until the Summarization and Pruningmonitoring agent begins collecting the data. By default, thisagent begins collection at 2 a.m. daily. At that point, data isvisible in the workspace view. See the IBM Tivoli MonitoringAdministrator's Guide to learn how to modify the defaultcollection settings.

Historical data collection is unavailable becauseof incorrect queries in the IBM Tivoli EnterprisePortal.

The Sort By, Group By, and First/Last functions column are notcompatible with the historical data collection feature. Use ofthese advanced functions makes a query ineligible for historicaldata collection.

Even if data collection has been started, you cannot use the timespan feature if the query for the chart or table includes columnfunctions or advanced query options (Sort By, Group By, First /Last).

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

See the IBM Tivoli Monitoring Administrator's Guide or the IBMTivoli Enterprise Portal online help for information about theHistorical Data Collection function.

When you use a long process name in thesituation, the process name is truncated.

Truncation of process or service names for situations in theAvailability table in the portal display is the expected behavior.100 bytes is the maximum name length.

Regular (non-historical) monitoring data fails tobe displayed.

Check the formation of the queries you use to gather data. Forexample, look for invalid SQL statements.

No row of data for 64-bit applications isdisplayed in the workspaces when themonitoring agent is running on a 64-bit operatingsystem.

The Tivoli Enterprise Portal shows data only for 32-bitapplications. No solution is available for this problem at thistime.

Navigator items and workspace titles are labeledwith internal names such as Kxx:KXX0000 insteadof the correct names (such as Disk), where XXand xx represent the two-character agent code.

Ensure that application support has been added on themonitoring server, portal server, and portal client.

For more information about installing application support, see"Installing and enabling application support" in the IBM TivoliMonitoring Installation and Setup Guide.

Situation troubleshootingThis section provides information about both general situation problems andproblems with the configuration of situations. See the IBM Tivoli MonitoringTroubleshooting Guide for more information about troubleshooting for situations.


General situation problemsTable 9 lists general problems that might occur with situations.

Table 9. General situation problems and solutions

Problem Solution

Monitoring activity requires too muchdisk space.

Check the RAS trace logging settings that are described in “Setting RAStrace parameters” on page 78. For example, trace logs grow rapidly whenyou apply the ALL logging option.

Monitoring activity requires too manysystem resources.

“Disk capacity planning for historical data” on page 56 describes theperformance impact of specific attribute groups. If possible, decrease youruse of the attribute groups that require greater system resources.

A formula that uses mathematicaloperators appears to be incorrect. Forexample, if you were monitoring aLinux system, the formula thatcalculates when Free Memory fallsunder 10 percent of Total Memory doesnot work: LT#’Linux_VM_Stats.Total_Memory’ / 10

This formula is incorrect because situation predicates support only logicaloperators. Your formulas cannot have mathematical operators.Note: The Situation Editor provides alternatives to math operators.Regarding the example, you can select the % Memory Free attribute andavoid the need for math operators.

You want to change the appearance ofsituations when they are displayed inthe navigation tree.

1. Right-click an item in the navigation tree.

2. Click Situations in the menu. The Situation Editor window isdisplayed.

3. Select the situation that you want to modify.

4. Use the State menu in the lower right of the window to set the statusand appearance of the Situation when it triggers.Note: The State setting is not related to severity settings in IBM TivoliEnterprise Console.

When a situation is triggered in theEvent Log attribute group, it remains inthe Situation Event Console as long asthe event ID entry is present in theEvent Log workspace. When this eventID entry is removed from the Event Logworkspace on the Tivoli EnterprisePortal, the situation is also cleared evenif the actual problem that caused theevent is not resolved, and the event IDentry is also present in the WindowsEvent Viewer.

A timeout occurs on the cache of events for the NT Event Log group.Increase the cache time of Event Log collection to meet your requirementsby adding the following variable and timeout value to the KXXENV file forthe agent: CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600

This variable determines how long events from the NT Event Log arekept.

For a situation that uses the 'MISSING'operator and is distributed to a remoteagentless monitoring subnode, when thesituation becomes true, you see noindication in the IBM Tivoli EnterprisePortal or in the Situation Event Console.

The MISSING predicate is currently not supported on subnodes. If asituation with a MISSING predicate is distributed to a subnode, the IRAcannot tell which subnode or node the event is occurring on. It inserts thesystem name as the origin node for the event and returns. When theevent reaches the Tivoli Enterprise Portal Server, the origin node does notmatch the system name of the subnode where the situation is associated,so the event is dropped.


Table 9. General situation problems and solutions (continued)

Problem Solution

When a situation is triggered in theEvent Log attribute group, it remains inthe Situation Event Console as long asthe event ID entry is present in theEvent Log workspace. When this eventID entry is removed from the Event Logworkspace on the Tivoli EnterprisePortal, the situation is also cleared evenif the actual problem that caused theevent is not resolved, and the event IDentry is also present in the WindowsEvent Viewer

There is a timeout on the cache of events for the NT Event Log group.Increase the cache time of Event Log collection to meet your requirementsby adding the following variable and timeout value to the KXXENV filefor the agent: CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600 Thisvariable determines how long events from the NT Event Log are kept.

If the Expert Advice for a situationcontains a hyperlink to an externalwebsite (for example, a MicrosoftTechNet website) and you click thehyperlink, the website opens in anexternal window. However, the externalwindow stops responding.

The external window responds after you close the Preview window andSituation Editor window.

Problems with configuration of situationsTable 10 lists problems that might occur with configuring situations.

This section provides information for troubleshooting for agents. Be sure to consultthe IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshootinginformation.

Table 10. Problems with configuring situations that you solve in the Situation Editor

Problem Solution

Note: To get started with the solutions in this section, perform these steps:1. Start the IBM Tivoli Enterprise Portal.2. Click Edit > Situation Editor.3. In the navigation tree, choose the agent whose situation you want to modify.4. Choose the situation in the list. The Situation Editor view is displayed.

The situation for a specific agent isnot visible in the IBM TivoliEnterprise Portal.

Open the Situation Editor. Access the All managed servers view. If the situationis absent, confirm that the monitoring server has been seeded for the agent. Ifnot, seed the server, as described in the IBM Tivoli Monitoring Installation andSetup Guide.

The monitoring interval is toolong.

Access the Situation Editor view for the situation that you want to modify.Check the Sampling interval area in the Formula tab. Adjust the time intervalas required.

The situation did not activate atstartup.

Manually recycle the situation as follows:

1. Right-click the situation and select Stop Situation.

2. Right-click the situation and select Start Situation.

Note: You can permanently avoid this problem by selecting the Run at Startupcheck box of the Situation Editor view for a specific situation.

The situation is not displayed. Click the Action tab and check whether the situation has an automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event or theupdate in the graphical user interface.


Table 10. Problems with configuring situations that you solve in the Situation Editor (continued)

Problem Solution

An Alert event did not occur eventhough the predicate was properlyspecified.

Check the logs, reports, and workspaces.

A situation fires on an unexpectedmanaged object.

Confirm that you distributed and started the situation on the correct managedsystem.

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for the situation.

The situation does not fire. This problem can be caused when incorrect predicates are present in theformula that defines the situation. For example, the managed object shows astate that normally triggers a monitoring event, but the situation is not truebecause the wrong attribute is specified in the formula.

In the Formula tab, analyze predicates as follows:

1. Click the fx icon in the upper-right corner of the Formula area. The Showformula window is displayed.

a. Confirm the following details in the Formula area at the top of thewindow:v The attributes that you intend to monitor are specified in the formula.v The situations that you intend to monitor are specified in the formula.v The logical operators in the formula match your monitoring goal.v The numeric values in the formula match your monitoring goal.

b. (Optional) Select the Show detailed formula check box in the lower leftof the window to see the original names of attributes in the applicationor operating system that you are monitoring.

c. Click OK to dismiss the Show formula window.

2. (Optional) In the Formula area of the Formula tab, temporarily assignnumeric values that immediately trigger a monitoring event. The triggeringof the event confirms that other predicates in the formula are valid.Note: After you complete this test, you must restore the numeric values tovalid levels so that you do not generate excessive monitoring data based onyour temporary settings.

See the IBM Tivoli Monitoring Troubleshooting Guide for additional informationabout situations that do not fire.

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

Problem Solution

Situation events are not displayedin the Events Console view of theworkspace.

Associate the situation with a Navigator item.Note: The situation does not need to be displayed in the workspace. It issufficient that the situation is associated with any Navigator item.

You do not have access to asituation.

Note: You must have administrator privileges to perform these steps.

1. Click Edit > Administer Users to access the Administer Users window.

2. In the Users area, select the user whose privileges you want to modify.

3. In the Permissions tab, Applications tab, and Navigator Views tab, selectthe permissions or privileges that correspond to the user role.

4. Click OK.

A managed system seems to beoffline.

1. Select Physical View and click the Enterprise Level of the navigator tree.

2. Click View > Workspace > Managed System Status to see a list ofmanaged systems and their status.

3. If a system is offline, check network connectivity and the status of thespecific system or application.


Take Action commands troubleshootingTable 12 lists general problems that might occur with Take Action commands.When each Take Action command runs it generates the log file listed in Table 3 onpage 75. This chapter provides agent-specific troubleshooting information.

See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Table 12. Take Action commands problems and solutions

Problem Solution

Take Action commands often require severalminutes to complete.

Allow several minutes. If you do not see a message advising youof completion, try to run the command manually.

Situations fail to trigger Take Action commands. Attempt to manually run the Take Action command in the IBMTivoli Enterprise Portal. If the Take Action command works, lookfor configuration problems in the situation. See “Situationtroubleshooting” on page 85. If the Take Action command fails,see IBM Tivoli Monitoring Troubleshooting Guide for generalinformation about troubleshooting Take Action commands.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineThe following sites contain troubleshooting information:v Go to the IBM Software Support site at http://www.ibm.com/support/

entry/portal/software and follow the instructions.v Go to the IBM Tivoli Distributed Monitoring and Application

Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home. Feel free to contribute to this wiki.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to http://www.ibm.com/software/support/isa.


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


http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home


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

Appendix A. IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli EnterpriseConsole. For a description of the event slots for each event class, see the lists inthis appendix. For more information about mapping attribute groups to eventclasses, see the IBM Tivoli Monitoring Administrator's Guide.

Generic event mapping provides useful event class and attribute information forsituations that do not have specific event mapping defined. BAROC files are foundon the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB(that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console eventsynchronization provides a collection of ready-to-use rule sets that you can deploywith minimal configuration. Be sure to install IBM Tivoli Enterprise Console eventsynchronization to access the correct Sentry.baroc, which is automatically includedduring base configuration of IBM Tivoli Enterprise Console rules if you indicatethat you want to use an existing rule base. See the IBM Tivoli Monitoring Installationand Setup Guide for details.

The Tivoli Enterprise Console Event Definition Generator (TEDGEN) tool providesan alternate method for generating a new XML file for EIF Slot Customization. See"Updating the XML used by the MCS Attribute Service" in the IBM TivoliMonitoring Version 6.2.2 Fix Pack 2 Administrator's Guide for information about theTEDGEN tool.

Each of the event classes is a child of KV1_Base and is defined in the kv1.baroc(version 6.2.3) file. The KV1_Base event class can be used for generic rulesprocessing for any event from the IBM Tivoli Monitoring for Virtual Servers Agentfor Linux Kernel-based Virtual Machines.

For events generated by situations in the Host CPU attribute group, TivoliEnterprise Console events are sent using the ITM_KV1_HOST CPU class. This classcontains the following slots:v node: STRINGv timestamp: STRINGv host_name: STRINGv host_name_enum: STRINGv number_of_cpus: INTEGERv number_of_cpus_enum: STRINGv number_of_cpu_ghz: REALv number_of_cpu_ghz_enum: STRINGv vm_cpus_consumed: REALv vm_cpus_consumed_enum: STRINGv vm_cpu_ghz_consumed: REALv vm_cpu_ghz_consumed_enum: STRINGv cpus_unaccounted_for: REALv cpus_unaccounted_for_enum: STRINGv cpu_ghz_unaccounted_for: REALv cpu_ghz_unaccounted_for_enum: STRING


v cpus_consumed_per_vm: REALv cpus_consumed_per_vm_enum: STRINGv cpu_ghz_consumed_per_vm: REALv cpu_ghz_consumed_per_vm_enum: STRINGv number_of_active_vms: INTEGERv number_of_active_vms_enum: STRINGv cpu_percent_consumed: REALv cpu_percent_consumed_enum: STRINGv cpu_percent_unaccounted: REALv cpu_percent_unaccounted_enum: STRINGv vm_cpu_fit_estimate: REALv vm_cpu_fit_estimate_enum: STRINGv virtual_cpus_allocated: INTEGERv virtual_cpus_allocated_enum: STRINGv over_under_allocated_cpu: INTEGERv over_under_allocated_cpu_enum: STRINGv over_under_allocated_cpu_ghz: REALv over_under_allocated_cpu_ghz_enum: STRINGv percent_cpu_allocated: REALv percent_cpu_allocated_enum: STRING

For events generated by situations in the Host Memory attribute group, TivoliEnterprise Console events are sent using the ITM_KV1_HOST MEMORY class. Thisclass contains the following slots:v node: STRINGv timestamp: STRINGv host_name: STRINGv host_name_enum: STRINGv memory_size: REALv memory_size_enum: STRINGv vm_memory_allocated: REALv vm_memory_allocated_enum: STRINGv vm_memory_used: REALv vm_memory_used_enum: STRINGv over_under_allocated: REALv over_under_allocated_enum: STRINGv over_under_used: REALv over_under_used_enum: STRINGv percent_memory_allocated: REALv percent_memory_allocated_enum: STRINGv percent_memory_used: REALv percent_memory_used_enum: STRINGv percent_memory_unallocated: REALv percent_memory_unallocated_enum: STRINGv percent_memory_unused: REALv percent_memory_unused_enum: STRING


v number_of_active_vms: INTEGERv number_of_active_vms_enum: STRINGv memory_allocated_per_vm: REALv memory_allocated_per_vm_enum: STRINGv memory_used_per_vm: REALv memory_used_per_vm_enum: STRINGv vm_memory_allocated_fit_estimate: REALv vm_memory_allocated_fit_estimate_enum: STRINGv vm_memory_used_fit_estimate: REALv vm_memory_used_fit_estimate_enum: STRING

For events generated by situations in the Hosts attribute group, Tivoli EnterpriseConsole events are sent using the ITM_KV1_HOSTS class. This class contains thefollowing slots:v node: STRINGv timestamp: STRINGv host_name: STRINGv host_name_enum: STRINGv ip_address: STRINGv ip_address_enum: STRINGv hypervisor_uri: STRINGv hypervisor_uri_enum: STRINGv protocol: STRINGv protocol_enum: STRINGv cpu_model: STRINGv cpu_model_enum: STRINGv number_of_cpus: INTEGERv number_of_cpus_enum: STRINGv cpu_frequency: REALv cpu_frequency_enum: STRINGv number_of_cpu_ghz: REALv number_of_cpu_ghz_enum: STRINGv number_of_nodes: INTEGERv number_of_nodes_enum: STRINGv sockets_per_node: INTEGERv sockets_per_node_enum: STRINGv cores_per_socket: INTEGERv cores_per_socket_enum: STRINGv threads_per_core: INTEGERv threads_per_core_enum: STRINGv memory_size: REALv memory_size_enum: STRINGv number_of_vms: INTEGERv number_of_vms_enum: STRINGv number_of_active_vms: INTEGERv number_of_active_vms_enum: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 93

For events generated by situations in the Performance Object Status attributegroup, Tivoli Enterprise Console events are sent using theITM_KV1_PERFORMANCE OBJECT STATUS class. This class contains thefollowing slots:v node: STRINGv timestamp: STRINGv query_name: STRINGv object_name: STRINGv object_type: INTEGERv object_type_enum: STRINGv object_status: INTEGERv object_status_enum: STRINGv error_code: INTEGERv error_code_enum: STRINGv last_collection_start: STRINGv last_collection_start_enum: STRINGv last_collection_finished: STRINGv last_collection_finished_enum: STRINGv last_collection_duration: REALv average_collection_duration: REALv average_collection_duration_enum: STRINGv refresh_interval: INTEGERv number_of_collections: INTEGERv cache_hits: INTEGERv cache_misses: INTEGERv cache_hit_percent: REALv intervals_skipped: INTEGER

For events generated by situations in the Storage Pools attribute group, TivoliEnterprise Console events are sent using the ITM_KV1_STORAGE POOLS class.This class contains the following slots:v node: STRINGv timestamp: STRINGv host_name: STRINGv host_name_enum: STRINGv storage_pool_name: STRINGv storage_pool_name_enum: STRINGv storage_pool_uuid: STRINGv storage_pool_uuid_enum: STRINGv storage_pool_state: STRINGv storage_pool_state_enum: STRINGv storage_pool_type: STRINGv storage_pool_type_enum: STRINGv storage_pool_capacity: REALv storage_pool_capacity_enum: STRINGv storage_pool_used: REAL


v storage_pool_used_enum: STRINGv storage_pool_available: REALv storage_pool_available_enum: STRINGv percent_used: REALv percent_used_enum: STRING

For events generated by situations in the Virtual Machines attribute group, TivoliEnterprise Console events are sent using the ITM_KV1_VIRTUAL MACHINESclass. This class contains the following slots:v node: STRINGv timestamp: STRINGv host_name: STRINGv host_name_enum: STRINGv virtual_machine_name: STRINGv virtual_machine_name_enum: STRINGv virtual_machine_uuid: STRINGv virtual_machine_uuid_enum: STRINGv virtual_machine_state: STRINGv virtual_machine_state_enum: STRINGv virtualization_type: STRINGv virtualization_type_enum: STRINGv number_of_virtual_cpus: INTEGERv number_of_virtual_cpus_enum: STRINGv sample_timestamp: STRINGv sample_timestamp_enum: STRINGv sample_time_delta: REALv sample_time_delta_enum: STRINGv cpu_time: REALv cpu_time_enum: STRINGv cpu_time_delta: REALv cpu_time_delta_enum: STRINGv cpus_consumed: REALv cpus_consumed_enum: STRINGv cpu_percent: REALv cpu_percent_enum: STRINGv memory_allocated: REALv memory_allocated_enum: STRINGv memory_used: REALv memory_used_enum: STRINGv memory_percent: REALv memory_percent_enum: STRINGv action_on_poweroff: STRINGv action_on_poweroff_enum: STRINGv action_on_reboot: STRINGv action_on_reboot_enum: STRINGv action_on_crash: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 95

v action_on_crash_enum: STRINGv cpu_match: STRINGv cpu_match_enum: STRINGv cpu_model: STRINGv cpu_model_enum: STRINGv number_of_sockets: INTEGERv number_of_sockets_enum: STRINGv cores_per_socket: INTEGERv cores_per_socket_enum: STRINGv threads_per_core: INTEGERv threads_per_core_enum: STRING


Appendix B. Documentation library

This appendix contains information about the publications related to the IBMTivoli Monitoring for Virtual Servers Agent for Linux Kernel-based VirtualMachines. These publications are listed in the following categories:v Linux Kernel-based Virtual Machines agent libraryv Prerequisite publicationsv Related publications

See the IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Managerproducts: Documentation Guide, SC23-8816, for information about accessing andusing publications. You can find the Documentation Guide in the followinginformation centers:v IBM Tivoli Monitoring and OMEGAMON® XEv IBM Tivoli Composite Application Manager

To open the Documentation Guide in the information center, select Using thepublications in the Contents pane.

To find a list of new and changed publications, click What's new on the Welcomepage of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. Tofind publications from the previous version of a product, click Previous versionsunder the name of the product in the Contents pane.

Linux Kernel-based Virtual Machines agent libraryOne document is specific to the Linux Kernel-based Virtual Machines agent: IBMTivoli Monitoring for Virtual Servers Agent for Linux Kernel-based Virtual MachinesUser's Guide. This publication provides agent-specific information for configuring,using, and troubleshooting the Linux Kernel-based Virtual Machines agent

Use the configuration chapter in this guide with the IBM Tivoli MonitoringInstallation and Setup Guide to set up the software.

Use the information in this guide with the Tivoli Enterprise Portal User's Guide tomonitor Linux Kernel-based Virtual Machine resources.

Prerequisite publicationsTo use the information in this publication effectively, you must have someprerequisite knowledge, which you can obtain from the following IBM TivoliMonitoring publications:v Exploring IBM Tivoli Monitoring

v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Agent Builder User’s Guide

v IBM Tivoli Monitoring Command Reference

v IBM Tivoli Monitoring: Configuring Tivoli Enterprise Monitoring Server on z/OS

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring Troubleshooting Guide


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp

v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring

v IBM Tivoli Monitoring: Upgrading from V5.1.2

v IBM Tivoli Monitoring: i5/OS® Agent User's Guide

v IBM Tivoli Monitoring: Linux OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX Log OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX OS Agent User's Guide

v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v IBM Tivoli Monitoring Universal Agent User's Guide

v IBM Tivoli Monitoring Universal Agent API and Command Programming ReferenceGuide

v Tivoli Enterprise Portal User's Guide

Related publicationsThe following documents also provide useful information:v IBM Tivoli Enterprise Console Adapters Guide

v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide

v IBM Tivoli Enterprise Console Reference Manual

v IBM Tivoli Enterprise Console Rule Builder’s Guide

Other sources of documentationYou can also obtain technical documentation about monitoring products from thefollowing sources:v Tivoli Integrated Service Management Library

http://www-01.ibm.com/software/brandcatalog/ismlibrary/The Integrated Service Management Library is an online catalog that containsintegration documentation as well as other downloadable product extensions.

v Redbook publicationshttp://www.redbooks.ibm.com/IBM Redbooks®, Redpapers, and Redbooks Technotes provide information aboutproducts from platform and solution perspectives.

v TechnotesTechnotes provide the latest information about known product limitations andworkarounds. You can find Technotes through the IBM Software Supportwebsite at http://www.ibm.com/support/entry/portal/software.

v Tivoli wikis on the IBM developerWorks websiteTivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the home for interactive wikis that offer best practices andscenarios for using Tivoli products. The wikis contain white papers contributedby IBM employees, and content created by customers and business partners.


http://www-01.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/


http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki at

http://www-10.lotus.com/ldd/tivmonitorwiki.nsf provides information aboutIBM Tivoli Monitoring and related distributed products, including IBM TivoliComposite Application Management products.

– Tivoli System z Monitoring and Application Management Wiki athttp://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about the OMEGAMON XE products, TivoliNetView for z/OS, Tivoli Monitoring Agent for z/TPF, and other System zmonitoring and application management products.

Appendix B. Documentation library 99


http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Appendix C. Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in this product enable users to do the following:v Use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the followingfeatures to aid accessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Navigating the interface using the keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. See the documentation provided by youroperating system for more information.

Magnifying what is displayed on the screenYou can enlarge information in the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. See the documentation provided by youroperating system for more information.


Appendix D. Notices

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

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

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to


IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Sun Microsystems, Inc. in the United States,other countries, or both.

Appendix D. Notices 105

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.


Index

Aaccessibility 101Action On Crash attribute 54Action On PowerOff attribute 53Action On Reboot attribute 54agent

trace logs 75Agent Management Services 2agents

troubleshooting 82attribute groups

Host CPU 24Host Memory 30Hosts 34list of all 23more information 23overview 23Performance Object Status 39Storage Pools 45Virtual Machines 48

attributesAction On Crash 54Action On PowerOff 53Action On Reboot 54Average Collection Duration 44Cache Hit Percent 45Cache Hits 44Cache Misses 44Cores Per Socket 38, 55CPU Frequency (GHz) 37CPU GHz Consumed Per VM 27CPU GHz Unaccounted For 26CPU Match 54CPU Model 36, 54CPU Percent 52CPU Percent Consumed by VMs 27CPU Percent Unaccounted 28CPU Time Delta (sec) 52CPUs Consumed 52CPUs Consumed Per VM 27CPUs Unaccounted For 26Error Code 41Host CPU 24Host Memory 30Host Name 25, 30, 35, 46, 49Hosts 35Hypervisor URI 35Intervals Skipped 45IP Address 35Last Collection Duration 43Last Collection Finished 43Last Collection Start 43Memory Allocated (GB) 52Memory Allocated Per VM 33Memory Percent 53Memory Size 30Memory Size (GB) 38Memory Used (GB) 53Memory Used Per VM 33more information 23Node 24, 30, 35, 39, 45, 49

attributes (continued)Number of Active VMs 27, 33, 39Number of Collections 44Number of CPU GHz 25, 37Number of CPUs 25, 36Number of Nodes 37Number of Sockets 55Number Of Virtual CPUs 50Number of VMs 39Object Name 40Object Status 41Object Type 40Over Under Allocated 31Over Under Allocated CPU 29Over Under Allocated CPU GHz 29Over Under Used 32overview 23Percent CPU Allocated to VMs 29Percent Memory Allocated 32Percent Memory Unallocated 32Percent Memory Unused 33Percent Memory Used 32Percent Used (%) 48Performance Object Status 39Protocol 36Query Name 40Refresh Interval 44Sample Time Delta (sec) 51Sample Timestamp 51Sockets Per Node 37Storage Pool Available (GB) 48Storage Pool Capacity (GB) 47Storage Pool Name 46Storage Pool State 46Storage Pool Type 47Storage Pool Used (GB) 47Storage Pool UUID 46Storage Pools 45Threads Per Core 38, 55Timestamp 24, 30, 35, 40, 45, 49Total CPU Time (sec) 51Virtual CPUs Allocated 28Virtual Machine Name 49Virtual Machine State 50Virtual Machine UUID 49Virtual Machines 48Virtualization Type 50VM CPU Fit Estimate 28VM CPU GHz Consumed 26VM CPUs Consumed 25VM Memory Allocated 31VM Memory Allocated Fit Estimate 34VM Memory Used 31VM Memory Used Fit Estimate 34

Average Collection Duration attribute 44

Bbuilt-in troubleshooting features 73


CCache Hit Percent attribute 45Cache Hits attribute 44Cache Misses attribute 44calculate historical data disk space 56capacity planning

Linux Kernel-based Virtual Machines agent 56capacity planning for historical data 56commands

tacmd addSystem 13commands, Take Action 69components 1configuration 5

after installation 8fields 10remote 13values 10

configuring the monitoring agent 8Cores Per Socket attribute 38, 55CPU Frequency (GHz) attribute 37CPU GHz Consumed Per VM attribute 27CPU GHz Unaccounted For attribute 26CPU Match attribute 54CPU Model attribute 36, 54CPU Percent attribute 52CPU Percent Consumed by VMs attribute 27CPU Percent Unaccounted attribute 28CPU Time Delta (sec) attribute 52CPUs Consumed attribute 52CPUs Consumed Per VM attribute 27CPUs Unaccounted For attribute 26

Ddata

trace logs 74data logged

Linux Kernel-based Virtual Machines agent 56data provider logs

See agentdeveloperWorks website 98disk capacity planning

See capacity planningdisk capacity planning for historical data 56documentation

See publications

Eenvironment

functions 1Error Code attribute 41event

mapping 91

Ffiles

agent trace 75installation trace 75other trace log 75trace logs 74

functions, Linux Kernel-based Virtual Machines agent 1

Ggathering support information 73

Hhistorical data

calculate disk space 56capacity planning

Linux Kernel-based Virtual Machines agent 56disk capacity planning 56

Hostsituations 60, 61workspaces

descriptions 18list 16

Host CPU attribute group 24Host CPU Comparison workspace 17Host Detail workspace 19Host Memory Allocation Comparison workspace 17Host Memory attribute group 30Host Memory Use Comparison workspace 18Host Name attribute 25, 30, 35, 46, 49Host Overview workspace 19Host Relations workspace 19Host workspace 18Hosts attribute group 34Hypervisor URI attribute 35

IIBM Software Support

See supportIBM Support Assistant 89IBM Tivoli Distributed Monitoring and Application

Management Wiki 89IBM Tivoli Enterprise Console

event mapping 91information

troubleshooting 73information, additional

attributes 23policies 71situations 59Take Action commands 69workspaces 15

installationlog file 75problems 79remote 13silent 5

installing language packs 5Integrated Service Management Library documentation 98interface, user 2Intervals Skipped attribute 45IP Address attribute 35ISA 89

KKV1_Host_CPU_Over_Commit_Crit situation 62KV1_Host_CPU_Over_Commit_Info situation 61KV1_Host_CPU_Over_Commit_Warn situation 61KV1_Host_CPU_Pct_High_Crit situation 63KV1_Host_CPU_Pct_High_Warn situation 63KV1_Host_Mem_Pct_High_Crit situation 64


KV1_Host_Mem_Pct_High_Warn situation 64KV1_VM_CPU_Pct_High_Crit situation 66KV1_VM_CPU_Pct_High_Warn situation 65KV1_VM_Mem_Pct_High_Crit situation 67KV1_VM_Mem_Pct_High_Warn situation 66

Llanguage packs

installing 5silent 6UNIX, Linux 5Windows 5

Last Collection Duration attribute 43Last Collection Finished attribute 43Last Collection Start attribute 43library, Linux Kernel-based Virtual Machines agent 97Linux Kernel-based Virtual Machine

workspaceslist 16

Linux Kernel-based Virtual Machines agentcomponents 1functions 1performance considerations 86

Linux KVMsituations 60, 61workspaces

descriptions 16Linux KVM workspace 16logged data

Linux Kernel-based Virtual Machines agent 56logging

agent trace logs 75built-in features 73installation log files 75trace log files 74

MMemory Allocated (GB) attribute 52Memory Allocated Per VM attribute 33Memory Percent attribute 53Memory Size (GB) attribute 38Memory Size attribute 30Memory Used (GB) attribute 53Memory Used Per VM attribute 33messages

built-in features 73

NNode attribute 24, 30, 35, 39, 45, 49Number of Active VMs attribute 27, 33, 39Number of Collections attribute 44Number of CPU GHz attribute 25, 37Number of CPUs attribute 25, 36Number of Nodes attribute 37Number of Sockets attribute 55Number Of Virtual CPUs attribute 50Number of VMs attribute 39

OObject Name attribute 40Object Status attribute 41

Object Type attribute 40Over Under Allocated attribute 31Over Under Allocated CPU attribute 29Over Under Allocated CPU GHz attribute 29Over Under Used attribute 32

PPercent CPU Allocated to VMs attribute 29Percent Memory Allocated attribute 32Percent Memory Unallocated attribute 32Percent Memory Unused attribute 33Percent Memory Used attribute 32Percent Used (%) attribute 48performance considerations 86Performance Object Status attribute group 39policies

more information 71overview 71

problems and workarounds 78Protocol attribute 36publications

developerWorks website 98Integrated Service Management Library 98Linux Kernel-based Virtual Machines agent 97prerequisite 97Redbooks 98related 98Technotes 98types 97wikis 98

purposestroubleshooting 73

Qqueries, using attributes 23Query Name attribute 40

RRedbooks 98Refresh Interval attribute 44remote

installation and configuration 13remote deployment

troubleshooting 82

SSample Time Delta (sec) attribute 51Sample Timestamp attribute 51silent installation 5situations

general troubleshooting 86, 87KV1_Host_CPU_Over_Commit_Crit 62KV1_Host_CPU_Over_Commit_Info 61KV1_Host_CPU_Over_Commit_Warn 61KV1_Host_CPU_Pct_High_Crit 63KV1_Host_CPU_Pct_High_Warn 63KV1_Host_Mem_Pct_High_Crit 64KV1_Host_Mem_Pct_High_Warn 64KV1_VM_CPU_Pct_High_Crit 66KV1_VM_CPU_Pct_High_Warn 65KV1_VM_Mem_Pct_High_Crit 67

Index 109

situations (continued)KV1_VM_Mem_Pct_High_Warn 66list of all 60more information 59overview 59predefined 60

situations, using attributes 23Sockets Per Node attribute 37Software Support 89Storage Pool

situations 60, 65workspaces


Storage Pool Available (GB) attribute 48Storage Pool Capacity (GB) attribute 47Storage Pool Detail workspace 20Storage Pool Name attribute 46Storage Pool Overview workspace 20Storage Pool State attribute 46Storage Pool Type attribute 47Storage Pool Used (GB) attribute 47Storage Pool UUID attribute 46Storage Pool workspace 19Storage Pools attribute group 45support

gathering information for 73support assistant 89

Ttacmd addSystem command 13Take Action commands

more information 69overview 69troubleshooting 89

Technotes 98Threads Per Core attribute 38, 55Timestamp attribute 24, 30, 35, 40, 45, 49Total CPU Time (sec) attribute 51trace logs 74troubleshooting 73, 78

agents 82built-in features 73installation 79installation logs 75remote deployment 82situations 85, 87Take Action commands 89uninstallation 79uninstallation logs 75workspaces 84

Uuninstallation

log file 75problems 79

user interfaces options 2

Vviews

Host CPU Comparison workspace 17Host Detail workspace 19Host Memory Allocation Comparison workspace 17

views (continued)Host Memory Use Comparison workspace 18Host Overview workspace 19Host Relations workspace 19Host workspace 18Linux KVM workspace 16Storage Pool Detail workspace 20Storage Pool Overview workspace 20Storage Pool workspace 19Virtual Machine Detail workspace 21Virtual Machine Overview workspace 21Virtual Machine workspace 20

Virtual CPUs Allocated attribute 28Virtual Machine

situations 60, 65workspaces


Virtual Machine Detail workspace 21Virtual Machine Name attribute 49Virtual Machine Overview workspace 21Virtual Machine State attribute 50Virtual Machine UUID attribute 49Virtual Machine workspace 20Virtual Machines attribute group 48Virtualization Type attribute 50VM CPU Fit Estimate attribute 28VM CPU GHz Consumed attribute 26VM CPUs Consumed attribute 25VM Memory Allocated attribute 31VM Memory Allocated Fit Estimate attribute 34VM Memory Used attribute 31VM Memory Used Fit Estimate attribute 34

Wwikis 98workarounds 78

agents 82remote deployment 82situations 85Take Action commands 89workspaces 84

workspacesHost 18Host CPU Comparison 17Host Detail 19Host Memory Allocation Comparison 17Host Memory Use Comparison 18Host Overview 19Host Relations 19Linux KVM 16list of all 15, 16more information 15overview 15predefined 15, 16Storage Pool 19Storage Pool Detail 20Storage Pool Overview 20troubleshooting 84Virtual Machine 20Virtual Machine Detail 21Virtual Machine Overview 21


��

Printed in USA

SC27-2892-00

Tivoli Monitoring for Virtual Servers Agent for Linux Kernel

Documents

Transcript of Tivoli Monitoring for Virtual Servers Agent for Linux Kernel