IBM Tivoli Monitoring for Virtual Servers: VMware VI 6.2.1-TIV-ITM_VMWVI-IF0008

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the "Problems Fixed" below.

Download Description

Copyright International Business Machines Corporation 2010.

All rights reserved.

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

Component ID: 5724L92VI

Interim Fix 0008, 6.2.1-TIV-ITM_VMWVI-IF0008

Date: September 30, 2010

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: 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: 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 parent name.

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

2.3 Superseded fixes
-------------------------
6.2.1-TIV-ITM_VMWVI-IF0004
6.2.1-TIV-ITM_VMWVI-IF0005
6.2.1-TIV-ITM_VMWVI-IF0006
6.2.1-TIV-ITM_VMWVI-IF0007

2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.2.1-TIV-ITM_VMWVI-IF0007
--------------------------
APAR: IZ74621
Abstract: LOG FILE ON LINUX GROWING VERY LARGE
Additional Information: When the VMware VI agent runs on Linux(R),
the agent creates a log file with the name
$CANDLEHOME/logs/<hostname>_vm_<timestamp>.log. This
file contains stdout and stderr messages from the kvmagent
executable, as specified in the file
$CANDLEHOME/logs/vm.env. This log file increases in
size until the agent is stopped. This file can grow very
large because the data provider sends messages to stderr.

APAR: IZ74137
Abstract: ISSUES RESTARTING CUSTOM DATA PROVIDERS
Additional Information: When a multi-threaded agent using a Java(R)
provider, such as JMX/JDBC, restarts the provider,
multiple Java processes may be started. On UNIX, due to
a threading issue, an incorrect kill process statement
may also be issued. The VMware agent is a multi-threaded
agent that uses a Java provider.

6.2.1-TIV-ITM_VMWVI-IF0006
--------------------------
APAR: IZ72762
Abstract: CLUSTER ATTRIBUTE GROUP TIMING OUT
Additional Information: In large environments with many clusters,
the Cluster workspace might not show all the clusters due to a
time out in collecting the cluster data from vCenter.

APAR: IZ72765
Abstract: CRASH AROUND MULTI-THREAD USE OF HASH MAP
Additional Information: The agent might crash due to a hash map
conflict. The kvmagent_<instance>.ras file might contain entries
similar to the following:
Exception 0xC0000005 (ACCESS_VIOLATION)
Computer: HOSTNAME Windows: 5.2-SP2
Current Time: 2010/03/07, 18:26:26 Start Time: 2010/03/07, 17:27:49
Current Clock: 0x4B93EFD2 Start Clock: 0x4B93E215
Process ID: 0x00001574 Thread ID: 0x00001BA0
Program: C:\ibm\itm\TMAITM6\kvmagent_INSTANCE.exe
Origin: kvmagent_INSTANCE.exe<>0x0001:0x00025EDD
Call Stack
IP:00426EDD BP:01E8FCD4 kvmagent_INSTANCE.exe<>0x0001:0x00025EDD
IP:00411C9F BP:01E8FDA4 kvmagent_INSTANCE.exe<>0x0001:0x00010C9F
IP:0041611C BP:01E8FE30 kvmagent_INSTANCE.exe<>0x0001:0x0001511C
IP:00419698 BP:01E8FE64 kvmagent_INSTANCE.exe<>0x0001:0x00018698
IP:00441052 BP:01E8FE98 kvmagent_INSTANCE.exe<>0x0001:0x00040052
IP:004C0558 BP:01E8FEC0 kvmagent_INSTANCE.exe<>KDY::Array<long>::
init+0x40348
IP:004C109A BP:01E8FF38 kvmagent_INSTANCE.exe<>KDY::Array<long>::
init+0x40E8A
IP:004C0B3C BP:01E8FF5C kvmagent_INSTANCE.exe<>KDY::Array<long>::
init+0x4092C
IP:64545240 BP:01E8FF84 KLX.dll<>pthread_yield+0x810
IP:7C3694EF BP:01E8FFB8 MSVCR71.dll<>endthread+0xAA
IP:77E6482F BP:01E8FFEC kernel32.dll<>GetModuleHandleA+0xDF

APAR: IZ72768
Abstract: OutOfMemoryError javacore
Additional Information: In large environments, the agent data
provider might stop due to a javacore with this error:
"java/lang/OutOfMemoryError:Failed to fork OS thread".
In addition to this fix, it might be necessary to increase the
heap size for the Java(R) process. See section 6.5 for details
on increasing the heap size.

APAR: IZ72770
Abstract: DOUBLE FREE CAUSES AGENT TO CRASH
Additional Information: The agent might crash due to a double
free coding error. The kvmagent_<instance>.ras file might
contain entries similar to the following:
Exception 0xC0000005 (ACCESS_VIOLATION)
Computer: HOSTNAME Windows: 5.2-SP2
Current Time: 2010/03/04, 12:18:11 Start Time: 2010/03/04, 10:27:46
Current Clock: 0x4B8FEB53 Start Clock: 0x4B8FD172
Process ID: 0x00001978 Thread ID: 0x00001A1C
Program: C:\ibm\itm\TMAITM6\kvmagent_HOSTNAME-agent.exe
Origin: MSVCR71.dll<>strcmp+0x53
Call Stack
IP:7C362DB3 BP:01F8FCD4 MSVCR71.dll<>strcmp+0x53
IP:00411C02 BP:01F8FDA4 kvmagent_HOSTNAME-agent.exe<>0x0001:0x00010C02
IP:0041603C BP:01F8FE30 kvmagent_HOSTNAME-agent.exe<>0x0001:0x0001503C
IP:004195B8 BP:01F8FE64 kvmagent_HOSTNAME-agent.exe<>0x0001:0x000185B8
IP:00440D32 BP:01F8FE98 kvmagent_HOSTNAME-agent.exe<>0x0001:0x0003FD32
IP:004BCC28 BP:01F8FEC0 kvmagent_HOSTNAME-agent.exe<>KDY::Array<long>::
init+0x3D418
IP:004BD76A BP:01F8FF38 kvmagent_HOSTNAME-agent.exe<>KDY::Array<long>::
init+0x3DF5A
IP:004BD20C BP:01F8FF5C kvmagent_HOSTNAME-agent.exe<>KDY::Array<long>::
init+0x3D9FC
IP:64545240 BP:01F8FF84 KLX.dll<>pthread_yield+0x810
IP:7C3694EF BP:01F8FFB8 MSVCR71.dll<>endthread+0xAA
IP:77E6482F BP:01F8FFEC kernel32.dll<>GetModuleHandleA+0xDF

APAR: IZ72801
Abstract: CPU AND MEMORY UTILIZATION OVERFLOW
Additional Information: Due to an overflow in the calculation, the
CPU and Memory Utilization metrics displayed in the Cluster
workspace might show negative values, instead of the correct values.

6.2.1-TIV-ITM_VMWVI-IF0005
--------------------------
APAR: IZ67821
Abstract: TEP NOT DISPLAYING DATA IN LARGE VMWARE ENVIRONMENTS
WHILE RUNNING SITUATIONS AND HISTORICAL DATA COLLECTION.
Additional Information: In large VMware environments, if the VMware
agent is configured to run situations and historical data
collection, requests from the Tivoli Enetrprise Portal might time
out before the agent responds with data. The result is most or all
of the views in a workspace will be blank. This occurs after the
Tivoli Enterprise Portal shows data for the first 5 to 15 minutes
after starting the agent. The agent cache is now used, in
addition to the data provider cache. See section 6.4 for details on
how to tune the agent cache environment variables.

APAR: IZ68602
Abstract: STOPPING THE AGENT DOES NOT STOP THE DATA PROVIDER
Additional Information: On Windows(R), stopping the VMware VI agent
stops the kvmagent_<instance>.exe but might not stop its child
process, java kvm_data_provider.jar. This might inhibit the
ability to restart the agent.

APAR: IZ68626
Abstract: ITM 6.2.1 VI VMWARE AGENT FAILS TO COLLECT VM MEMORY DATA
Additional Information: The data provider might report errors
collecting data for the VM Memory attribute group, resulting
in incomplete data in Tivoli Enterprise Portal workspaces views.
In the kvm_data_provider*.log file, these errors might be logged:
2009-12-17 11:21:38 22 SEVERE: ThreadRunner$1.run: Exception
execeuting thread: java.lang.NullPointerException
at com.ibm.tivoli.monitoring.agent.kvm.itm.attributegroup
.VMMemoryAttributeGroup$1.run (VMMemoryAttributeGroup.java:89)
at com.ibm.tivoli.monitoring.agent.kvm.util.ThreadRunner$1
.run(ThreadRunner.java:144)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadPool$RunnableWrapper.run(ThreadPool.java:41)
at java.lang.Thread.run(Thread.java:801)

APAR: IZ68736
Abstract: ERROR COLLECTING CLUSTER SERVER ATTRIBUTE GROUP
Additional Information: The following exception might be logged
in the kvm_data_provider*.log file and might result
in inconsistent data for the Cluster Server
attribute group:
2009-12-10 16:15:49 12 SEVERE: ThreadRunner$1.run: Exception
execeuting thread:
java.lang.ArrayIndexOutOfBoundsException
at java.util.ArrayList.add(ArrayList.java:378)
at com.ibm.tivoli.monitoring.agent.kvm.itm.attributegroup
.ClusteredServersAttributeGroup$1$1$1.run
(ClusteredServersAttributeGroup.java:166)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadRunner$1.run(ThreadRunner.java:144)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadPool$RunnableWrapper.run(ThreadPool.java:41)
at java.lang.Thread.run(Thread.java:801)
or
2009-12-15 23:39:07 15692 SEVERE: ThreadRunner$1.run: Exception
execeuting thread: java.lang.IllegalArgumentException: timeout
value is negative
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:231)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadRunner$CountingSemaphore.blockUntil
(ThreadRunner.java:96)
at com.ibm.tivoli.monitoring.agent.kvm.util.ThreadRunner
.executeAllSynchronous(ThreadRunner.java:127)
at com.ibm.tivoli.monitoring.agent.kvm.itm.attributegroup
.ClustersAttributeGroup.getClusterRow
(ClustersAttributeGroup.java:80)
at com.ibm.tivoli.monitoring.agent.kvm.itm.attributegroup
.ClustersAttributeGroup.access$000
(ClustersAttributeGroup.java:38)
at com.ibm.tivoli.monitoring.agent.kvm.itm.attributegroup
.ClustersAttributeGroup$2$1.run
(ClustersAttributeGroup.java:244)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadRunner$1.run(ThreadRunner.java:144)
at com.ibm.tivoli.monitoring.agent.kvm.util
.ThreadPool$RunnableWrapper.run(ThreadPool.java:41)
at java.lang.Thread.run(Thread.java:801)

APAR: IZ68737
Abstract: ConcurrentModificationException During Data Collection
Additional Information: During agent data collection, the following
exception might be logged in the kvm_data_provider*.log file and
might result in a loss of data:
2009-12-15 23:38:27 10 SEVERE: FactoryInterfaceController
.serviceRequests: Received an uncaught exception while servicing
request 2634. Continuing.
java.util.ConcurrentModificationException
Stack trace:
java.util.AbstractList$Itr.checkForComodification
(AbstractList.java:464)
java.util.AbstractList$Itr.next(AbstractList.java:435)
com.ibm.tivoli.monitoring.agent.kvm.itm
.FactoryInterfaceController.processCollectDataRequest
(FactoryInterfaceController.java:789)
com.ibm.tivoli.monitoring.agent.kvm.itm
.FactoryInterfaceController.serviceRequests
(FactoryInterfaceController.java:538)
com.ibm.tivoli.monitoring.agent.kvm.itm
.FactoryInterfaceController.main
(FactoryInterfaceController.java:840)

APAR: IZ70912
Abstract: No Data Due To VirtualMachineMetaInventoryItem
NullPointerException
Additional Information: During agent inventory data collection,
no data is displayed in the Tivoli Enterprise Portal for
the VMware VI agent, and the following exception might
be logged in the kvm_data_provider*.log file:
2010-02-23 17:27:50 11 SEVERE: MetaInventoryItem.
processDataProperty:
Caught an exception while processing property
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
metainventory.item.VirtualMachineMetaInventoryItem$19@f7d3a442
for value com.vmware.vim.ArrayOfVirtualDevice@4bf830f0 and
(VirtualMachine) xxx : null
java.lang.NullPointerException
Stack trace:
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
metainventory.item.VirtualMachineMetaInventoryItem$19.
processValue(VirtualMachineMetaInventoryItem.java:227)
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
metainventory.item.VirtualMachineMetaInventoryItem$19.
processValue(VirtualMachineMetaInventoryItem.java:197)
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
metainventory.item.MetaInventoryItem.processDataProperty
(MetaInventoryItem.java:302)
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
Inventory.processInventoryUpdates(Inventory.java:490)
com.ibm.tivoli.monitoring.agent.kvm.vmware.inventory.
Inventory.run(Inventory.java:287)
com.ibm.tivoli.monitoring.agent.kvm.util.
ControllableRunnable$RunnableWrapper.run
(ControllableRunnable.java:27)
java.lang.Thread.run(Thread.java:810)

6.2.1-TIV-ITM_VMWVI-IF0004
--------------------------
APAR: IZ64926
Abstract: NO DATA COLLECTED FOR VCENTER 2.5.0 BASE OR UPDATE 1
Additional Information: The VMware VI Agent v6.2.1 cannot collect
data from VMware vCenter v2.5.0 base (build 64192) or
update 1 (build 84767). No data shows on the
Tivoli Enterprise Portal, and the kvm_data_provider_*.log
file shows warning messages, such as:
WARNING: Inventory.run: Caught an exception while
collecting inventory updates.
Note: Vmware recommends upgrading vCenter to v2.5.0
Update 5 or vCenter 4.0. This problem does not occur
at those levels.

APAR: IZ65466
Abstract: THE VIRTUAL MACHINE CPU PERCENT READY METRIC ALWAYS
REPORTS A VALUE OF ZERO.
Additional Information: In the CPU workspace of the VMware VI agent
v6.2.1, the Percent Ready column of the Virtual Machine
CPU view always displays a value of zero due to an
incorrect calculation of the interval. It was using
milliseconds instead of seconds.

APAR: IZ65773
Abstract: VM_CPU DATA COLLECTION IS SLOW
Additional Information: Data collection for the VM_CPU attribute
group is too slow to update the CPU workspace before
the VMware ESX servers with more that 70 VMs per
server time out. The data collection for this
attribute group was single-threaded. This interim
fix changes the data collection for this attribute
group to multi-threaded.

APAR: IZ66178
Abstract: VIRTUALAPP OBJECT CAUSES VMWARE DISCOVERY TO FAIL
Additional Information: Only the top level nodes (VMware VI Agent,
Monitored Servers, and Events) are displayed in
the Tivoli Enterprise Portal Naviagation tree.
No monitored servers are discovered and no ESX Server
subnodes are displayed in the Navigation tree.
This can occur when a VirtualApp managed object type,
which extends ResourcePool, is returned by the vCenter
API. The kvm_data_provider_*.log contains entries
similar to:
2009-11-23 13:11:05 13 SEVERE:
MetaInventory.getMetaByTypeString: Unknown type string:
VirtualApp
2009-11-23 13:11:05 13 WARNING: Inventory.run: Accessed
a null reference while collecting inventory updates.
2009-11-23 13:11:05 13 WARNING:
Inventory.handleException: Encountered an error but
connection still seems valid.


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.1.

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.1.

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.

Note: When the base prerequisite is installed, the version number
is 06.21.00.03, instead of 06.21.00.00, due to an internal
installation requirement.


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

- 6.2.1-TIV-ITM_VMWVI-IF0008.README - This README file
- 6.2.1-TIV-ITM_VMWVI-IF0008.tar - Fix archive .tar format
- 6.2.1-TIV-ITM_VMWVI-IF0008.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.1-TIV-ITM_VMWVI-IF0008/kvm_li6263_tema_if0008.tar
- 6.2.1-TIV-ITM_VMWVI-IF0008/kvm_lx8266_tema_if0008.tar
- 6.2.1-TIV-ITM_VMWVI-IF0008/kvm_winnt_tema_if0008.cab
- 6.2.1-TIV-ITM_VMWVI-IF0008/kvmli6263.dsc
- 6.2.1-TIV-ITM_VMWVI-IF0008/kvmlx8266.dsc
- 6.2.1-TIV-ITM_VMWVI-IF0008/KVMWINNT.dsc
- 6.2.1-TIV-ITM_VMWVI-IF0008/vm_dd.properties
- 6.2.1-TIV-ITM_VMWVI-IF0008/vm_dd_062100008.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.1-TIV-ITM_VMWVI-IF0008.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.1-TIV-ITM_VMWVI-IF0008, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.1-TIV-ITM_VMWVI-IF0008/kvm_xxxxxx_tema_if0008.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_if0008.tar.
> ./cinfo -i
Monitoring Agent for VMware VI
li6263 Version: 06.21.00.03

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.1-TIV-ITM_VMWVI-IF0008\kvm_winnt_tema_if0008.cab

5.3 Remote agent update
------------------------------
1. Transfer the appropriate archive file (6.2.1-TIV-ITM_VMWVI-IF0008.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.1-TIV-ITM_VMWVI-IF0008:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.1-TIV-ITM_VMWVI-IF0008

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

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 062100008

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 062100008

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
------------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superceded fixes. No additional installation steps are required.


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.21.00.08.

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(R) 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 a Linux system:

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.1

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)?
What is DD?
6.2.1-TIV-ITM_VMWVI-IF0008 9/30/2010 English 10226386 FC DD

Product Alias/Synonym

VMware agent

Problems (APARS) fixed
IZ64926, IZ65466 , IZ65773 , IZ66178, IZ67821, IZ68602 , IZ68626, IZ68736 , IZ68737 , IZ70912, IZ72762, IZ72765, IZ72768, IZ72770, IZ72801, IZ74137, IZ74621, IZ83997, IZ85323

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.1

Operating system(s):

Linux, Windows

Reference #:

4028098

Modified date:

2010-09-30

Translate my page

Machine Translation

Content navigation