IBM Tivoli Monitoring for Virtual Servers: VMware VI 6.2.2-TIV-ITM_VMWVI-IF0004

Downloadable files


Abstract

This is an Interim Fix for IBM Tivoli Monitoring for Virtual Servers: VMware VI 6.2.2.

Download Description

Copyright International Business Machines Corporation 2011.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Virtual Servers: VMware VI Agent,
Version 6.2.2

Component ID: 5724L92VI

Interim Fix 0004, 6.2.2-TIV-ITM_VMWVI-IF0004

Date: March 23, 2011

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
-------------
APAR: IZ96485
Abstract: NUMBER VMS AND NUMBER VMS ON INCORRECT
Additional information: If a VMware dataStore is shared across
clusters, the "Number VMs" and "Number VMs On" columns
of the Clusters workspace might be incorrect in the
Tivoli Enterprise Portal.

2.2 Defects
--------------
None.

2.3 Superseded fixes
-------------------------
6.2.2-TIV-ITM_VMWVI-IF0003
6.2.2-TIV-ITM_VMWVI-IF0002
6.2.2-TIV-ITM_VMWVI-IF0001

2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------

6.2.2-TIV-ITM_VMWVI-IF0003
--------------------------------
APAR: IZ93826
Abstract: RESTARTING PROPERTYUPDATER FAILS TO RESTORE OFFLINE
SUBNODES
Additional information: Whenever the data provider attempts to stop
and restart the property updater in response to an error
getting data from the data source, the resulting offline
subnodes might fail to come back online due to a race
condition. The last messages in the
kvm_data_provider_<instance>*.log file are:

2011-01-27 02:10:06 22 INFO: ControllableRunnable.stop: Stop requested
(PropertyUpdater)
2011-01-27 02:10:06 22 INFO: ControllableRunnable.start: Start requested
(PropertyUpdater)
2011-01-27 02:10:06 22 INFO: ControllableRunnable.start: Started
(PropertyUpdater)

The result is that the subnodes on the Tivoli Enterprise
Portal go offline and never come back online.

APAR: IZ92794
Abstract: JAVA.LANG.THREAD.STOP EXCEPTION IN PROPERTYUPDATER
Additional information: The data provider might receive
an exception similar to the following as seen in the
kvm_data_provider_<instance>.log file:
---
SEVERE: FactoryInterfaceController$3.uncaughtException: Uncaught
exception in thread 34507.
java.lang.Object
Stack trace:
java.lang.Thread.stop(Thread.java:1007)
com.ibm.tivoli.monitoring.agent.kvm.vmware.
PropertyUpdater$1.run(PropertyUpdater.java:384)
---
The result is that the subnodes on the Tivoli Enterprise
Portal beneath the "Monitored Servers" workspace have no
entries in the "Monitored Servers" view, and all the
entries listed under the VMware VI folder are greyed out,
indicating they are offline.

6.2.2-TIV-ITM_VMWVI-IF0002
--------------------------------
APAR: IZ86306
Abstract: CPU PERCENT READY INCORRECT
Additional information: The CPU Percent Ready metric is calculated
incorrectly.

Defect: 141552
Abstract: ImportAgentTEPS.sh fails to install tmsdla files
Additional Information: The kvm_tmsdla.xml support file does not
install on UNIX(R) and Linux(R) systems when using the
"itmasi.sh" command.

6.2.2-TIV-ITM_VMWVI-IF0001
--------------------------------
APAR: IZ79621
Abstract: SOME SITUATIONS DO NOT HAVE FORMULAS
Additional information: These situations added in version 6.2.2
of the agent do not work because the formulas are
missing:
KVM_Host_System_Created
KVM_Host_System_Destroyed
KVM_Virtual_Machine_Created
KVM_Virtual_Machine_Destroyed
KVM_Virtual_Machine_Relocated.

APAR: IZ79672
Abstract: SOME VMOTION EVENTS ARE DELAYED
Additional information: After a vMotion change in the VMware
environment, the processing of some VMware VI agent
situations is delayed a few minutes. The delay may be
caused by:
1) Waiting for an inventory update.
2) A time difference between the agent and vCenter
machines.

APAR: IZ81708
Abstract: USING DOMAIN NAME USERNAME CAUSES NO DATA
Additional information: When configuring the agent, if the
"Data Source User ID" under the Data Source tab is a domain
name that contains a backslash (for example,
"domain\user"), the data provider receives an exception and
no data is sent. The kvm_data_provider_<instance>_0.log
contains messages similar to:

2010-07-29 11:49:22 10 SEVERE:
FactoryInterfaceController$3.uncaughtException: Uncaught exception in
thread 1.
java.lang.Object: Illegal/unsupported escape squence near index 21
([^\\]*\\)?DomainName\Username$
^
Stack trace:
java.util.regex.Pattern.error(Pattern.java:1686)
java.util.regex.Pattern.escape(Pattern.java:2157)
java.util.regex.Pattern.atom(Pattern.java:1899)
java.util.regex.Pattern.sequence(Pattern.java:1830)
java.util.regex.Pattern.expr(Pattern.java:1723)
java.util.regex.Pattern.compile(Pattern.java:1433)
java.util.regex.Pattern.<init>(Pattern.java:1160)
java.util.regex.Pattern.compile(Pattern.java:844)
com.ibm.tivoli.monitoring.agent.kvm.vmware.PermissionManager.<init>
(PermissionManager.java:64)
com.ibm.tivoli.monitoring.agent.kvm.vmware.DataSource.start
(DataSource.java:205)
com.ibm.tivoli.monitoring.agent.kvm.itm.DataProvider.addDataSource
(DataProvider.java:265)
com.ibm.tivoli.monitoring.agent.kvm.itm.FactoryInterfaceController.
setupDataProvider(FactoryInterfaceController.java:668)
com.ibm.tivoli.monitoring.agent.kvm.itm.FactoryInterfaceController.
serviceRequests(FactoryInterfaceController.java:569)
com.ibm.tivoli.monitoring.agent.kvm.itm.FactoryInterfaceController.
main(FactoryInterfaceController.java:911)

APAR: IZ82876
Abstract: DLA FAILS WITH HOSTNAMES > 32 CHARACTERS
Additional information: When running the Tivoli Management Services
Discovery Library Adapter (DLA), the discovery of ESX
Servers with host names longer than 32 characters are
truncated. The resulting resources IDs in some
relationships might not match the ID of the resource
definition, which uses the full host name. This might cause
parsing errors in the generated Discovery Library Book.

APAR: IZ82907
Abstract: DLA FAILS WITH VERSIONS PRIOR TO 06.22.01.00
Additional information: When running the Tivoli Management Services
Discovery Library Adapter (DLA), the adapter accepts
VMware VI agent versions prior to 06.22.01, but these
previous versions are not supported. This might result
in an incomplete or invalid Discovery Library Book.

APAR: IZ83997
Abstract: VM PARTITION USED SPACE ALWAYS HAS ZERO VALUES
Additional information: The VM Partition view of the Disk workspace
always has zero values in the Used Space column.

APAR: IZ85272
Abstract: DLA FAILS IF NO OS AGENT
Additional information: The resulting file from the Tivoli
Management Services Discovery Library Adapter (DLA)
will fail to load under any of these conditions:
1) No OS agent is running on the vCenter system.
2) An OS agent is running on the vCenter system but
is connected to a different Tivoli Enterprise
Management System than the VMware agent.
3) The remote/agentless OS agent without DLA support
is running on the vCenter system.

APAR: IZ85323
Abstract: RESOURCE POOL PARENT NAME INCORRECT
Additional information: In the Resource Pools workspace, the Parent
Name column incorrectly displays the name "Resources".
It should display the cluster name.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring for Virtual Servers: VMware VI Agent User's Guide,
version 6.2.2.

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

- IBM Tivoli Monitoring for Virtual Servers: VMware VI Agent,
version 6.2.2.

Note: When the prerequisite is installed, the version number
is 06.22.01.00, instead of 06.22.00.00, because it is based on
IBM Tivoli Monitoring 6.2.2 Fixpack 1.


4.0 Image directory contents
===================
This fix image contains the following files:

- 6.2.2-TIV-ITM_VMWVI-IF0004.README - This README file
- 6.2.2-TIV-ITM_VMWVI-IF0004.tar - Fix archive .tar format
- 6.2.2-TIV-ITM_VMWVI-IF0004.zip - Fix archive .zip format.

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file if
you are working in a Windows(R) environment.

The fix archive file contains the following files:
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_li6263_tema_if0004.tar
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_lx8266_tema_if0004.tar
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_lx3266_tema_if0004.tar
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_winnt_tema_if0004.cab
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_wix64_tema_if0004.cab
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvmli6263.dsc
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvmlx8266.dsc
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvmlx3266.dsc
- 6.2.2-TIV-ITM_VMWVI-IF0004/KVMWINNT.dsc
- 6.2.2-TIV-ITM_VMWVI-IF0004/KVMWIX64.dsc
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_tems_teps_tepd_if0004.tar
- 6.2.2-TIV-ITM_VMWVI-IF0004/kvm_tems_teps_tepd_if0004.zip
- 6.2.2-TIV-ITM_VMWVI-IF0004/vm_dd.properties
- 6.2.2-TIV-ITM_VMWVI-IF0004/vm_dd_062201004.xml


5.0 Installation instructions
==================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (6.2.2-TIV-ITM_VMWVI-IF0004.tar
or .zip) to a temporary directory on the system that contains the
agent code to be updated. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this
directory. Note: On Windows systems, this path includes the drive
letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for the operating
system of that agent. For more information on the "itmpatch"
command, see section 6.2.

On UNIX systems, if the fix was expanded to
<TEMP>/6.2.2-TIV-ITM_VMWVI-IF0004, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2-TIV-ITM_VMWVI-IF0004/kvm_xxxxxx_tema_if0004.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the "./cinfo -i" command.

In the following example, the file is
kvm_li6263_tema_if0004.tar.
> ./cinfo -i
Monitoring Agent for VMware VI
li6263 Version: 06.22.01.00

On Windows systems, if the fix was expanded to
<TEMP>\6.2.2-TIV-ITM_VMWVI-IF0004, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.2-TIV-ITM_VMWVI-IF0004\kvm_xxxxx_tema_if0004.cab

where:
- xxxxx corresponds to the value in the first column returned
by the "kincinfo -i" command.

In the following example, the file is
kvm_winnt_tema_if0004.cab.
> kincinfo -i
VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.00 Build: 201008161706

5.3 Remote agent update
------------------------------
1. Transfer the appropriate archive file (6.2.2-TIV-ITM_VMWVI-IF0004.tar
or .zip) to a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this
directory. Note: On Windows systems, this path includes the drive
letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.

3. To add the agent fix bundles into the remote deploy depot, use the
"tacmd addBundles" command found in $CANDLEHOME/bin on UNIX systems
or in %CANDLE_HOME%\bin on Windows systems. For more information
on the "tacmd addBundles" command, see the IBM Tivoli Monitoring
Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.2-TIV-ITM_VMWVI-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2-TIV-ITM_VMWVI-IF0004

On Windows systems,
if the fix was expanded to <TEMP>\6.2.2-TIV-ITM_VMWVI-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2-TIV-ITM_VMWVI-IF0004

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
may require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t vm
-n <Managed system name>
-v 062201004

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t vm
-n <Managed system name>
-v 062201004

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (vm), not three characters (kvm).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for an "tacmd updateAgent" command is always an
OS agent.

5.4 Agent support update
------------------------------
This fix 6.2.2-TIV-ITM_VMWVI-IF0004 include changes to the agent
support files which need to be installed. Use the following steps to
update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, or Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.2-TIV-ITM_VMWVI-IF0004.tar
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Expand the archive file (kvm_tems_teps_tepd_if0004.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX systems or an extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0001:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".

-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java(R) is installed. The
location of Java on your system might vary.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
unchecked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the VMware VI
06.22.01.04 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
Browser was running when the update was installed, it must be
restarted.


6.0 Additional installation information
========================

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch.


For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this must include the
drive letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows systems, this must include the drive
letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems -t VM

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t VM

Note:
- The component (-t) for the "tacmd listSystems" command is
specified as two characters (VM), not three characters (KVM).

When the agent update is successful, the agent version is now:
06.22.01.04.

2. To verify the agent support files were updated correctly, use the
"kincinfo" command on Windows systems or the "cinfo" command on
Linux or UNIX systems. The sample output below shows the versions
of the Tivoli Enterprise Portal Server, Tivoli Enterprise
Monitoring Server, or Tivoli Enterprise Portal Desktop systems
after this fix has been successfully applied.

Note: The displayed date of the build might not be accurate. This
is a known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

************* Tuesday, March 8, 2011 7:56:03 AM *************
User : Administrator Group : NA
Host Name : HOSTNAME Installer : Ver: 062202000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
.
.
.
VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.04 Build: 201103230000

VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.04 Build: 201103230000

VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.04 Build: 201103230000

VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.00 Build: 201008161706

VM Monitoring Agent for VMware VI
WINNT Version: 06.22.01.00 Build: 201008161706

6.4 Tuning the Agent Cache Environment Variables
------------------------------------------------
Users may control some aspects of the agent data caching to improve
performance by changing certain environment variables. The
environment variables are in these files:

On Windows systems: %CANDLE_HOME%\TMAITM6\KVMENV_<instance>
On Linux systems : $CANDLEHOME/config/vm_<instance>.config

where <instance> is the same of the instance that was created
during configuration.

The recommendation for large VMware environments, such as those
with a vCenter running over 100 VMware ESX Servers or over 1000
VMs, is to change these defaults values:

CDP_DP_CACHE_TTL=60
CDP_DP_REFRESH_INTERVAL=60
CDP_DP_IMPATIENT_COLLECTOR_TIMEOUT=5
CDP_DISCOVERY_ATTRIBUTE_GROUP_UPDATE_INTERVAL=60

to:

CDP_DP_CACHE_TTL=120
CDP_DP_REFRESH_INTERVAL=120
CDP_DP_IMPATIENT_COLLECTOR_TIMEOUT=1
CDP_DISCOVERY_ATTRIBUTE_GROUP_UPDATE_INTERVAL=120

The environment variable descriptions are:

CDP_DP_CACHE_TTL: Data collected for an attribute group is
cached for this number of seconds. Multiple requests for the
same data in this time interval receive a cached copy of the
data.

CDP_DP_REFRESH_INTERVAL: The interval in seconds at which
attribute groups are updated in the background.

CDP_DP_IMPATIENT_COLLECTOR_TIMEOUT: The number of seconds to
wait for a data collection to happen before timing out and
returning cached data, even if the cached data is stale (older
than CDP_DP_CACHE_TTL seconds). If this variable is not set,
the agent waits as long as the data collection takes, which at
times can make the Tivoli Enterprise Portal time out and give
up on it.

CDP_DISCOVERY_ATTRIBUTE_GROUP_UPDATE_INTERVAL: The interval
in seconds at which the discovery attribute group is updated.

6.5 Increasing the Java heap size
---------------------------------
The default heap size for the Java data provider is 256 megabytes.
In very large VMware environments, it might be necessary to
increase the heap size. If the Java data provider stops due to a
javacore, and creates a file named
javacore.<date>.<time>.<number>.txt in the CANDLEHOME\tmaitm6
directory, which contains the string "java/lang/OutOfMemoryError",
then increase the heap size for the Java data provider.

The heap size value "-Xmx512m" is recommended for environments with
more than 100 ESX hosts and more than 1000 VMs. For environments
with more than 150 hosts and more than 2000 VMs, the value
"-Xmx1024m" is recommended.

To increase the heap size for the Java data provider, do the
following:

On Windows systems:

1) Edit the file: %CANDLE_HOME%\TMAITM6\kvm_data_provider.bat

2) Add the following line before the line that starts with
'SET KVM_JVM_ARGS="$KVM_CUSTOM_JVM_ARGS...':

SET KVM_CUSTOM_JVM_ARGS=-Xmx512m

3) Restart the agent.

On Linux systems:

1) Edit the file: $CANDLEHOME/<platform>/vm/bin/kvm_data_provider.sh

2) Add the following line before the line that starts with
'KVM_JVM_ARGS="$KVM_CUSTOM_JVM_ARGS...':

KVM_CUSTOM_JVM_ARGS=-Xmx512m

3) Restart the agent.


7.0 Known problems and workarounds
=========================
None.


8.0 Additional product information
======================
None.


9.0 Notices
=======

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

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

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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

Trademarks and service marks
------------------------------------

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International 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 and trademark information" at
www.ibm.com/legal/copytrade.shtml.

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

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

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

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

Prerequisites

IBM Tivoli Monitoring for Virtual Servers: VMware VI Agent, version 6.2.2

Installation Instructions

Please refer to the full README contained in the Download Description section above for general installation instructions.

Download package

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.2-TIV-ITM_VMWVI-IF0004 4/21/2011 English 44941573 FC

Problems (APARS) fixed
IZ79621, IZ79672, IZ81708, IZ82876, IZ82907, IZ83997, IZ85272, IZ85323, IZ86306, IZ92794, IZ93826, IZ96485

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Monitoring for Virtual Environments
ITM Agent for VMWare VI V6

Software version:

6.2.2

Operating system(s):

Linux, Windows

Reference #:

4029773

Modified date:

2011-04-27

Translate my page

Machine Translation

Content navigation