IBM Tivoli Monitoring for Virtual Servers: VMware VI 6.1.2-TIV-ITM_VMWVI-IF0005

Downloadable files


Abstract

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

Download Description

(C) Copyright International Business Machines Corporation 2009. All

rights reserved.

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

Component ID: 5724L92VI

Interim Fix 0005, 6.1.2-TIV-ITM_VMWVI-IF0005

Date: September 7, 2009

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: IZ59503
Abstract: AGENT SLOWS DOWN AFTER LOGIN/LOGOUT DUE TO STALE REQUESTS
Additional Information: In a large VMware environment, if there is a
loss of the connection from the agent to the vCenter, the
agent will logoff and log back in to the vCenter. Even if
this is successful, the agent request queue does not get
cleaned up. Over time, this can cause a slow down in the
collection of data, and it can cause the agent to stop
collecting data completely until the agent is restarted.
2.2 Defects
--------------
None.

2.3 Superseded fixes
-------------------------
6.1.2-TIV-ITM_VMWVI-IF0004
6.1.2-TIV-ITM_VMWVI-IF0003
6.1.2-TIV-ITM_VMWVI-IF0002
6.1.2-TIV-ITM_VMWVI-IF0001

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

6.1.2-TIV-ITM_VMWVI-IF0004
-------------------------------
APAR: IZ52961
Abstract: VI CLUSTERS WORKSPACE DOES NOT POPULATE ESX SERVER METRICS
Additional Information: ESX Server data for Clusters might be empty if
the data source returns a value that would result in a
divide by zero exception. The actual message in the
*kvmviclient*log file will be:
"kvmWebServices::query_clusterServer_metrics") Caught an
unknown exception when getting data for <data source>

APAR: IZ51038
Abstract: VM AGENT STARTUP ISSUE WHEN CTIRA_HOSTNAME <> HOSTNAME
Additional Information: On Linux(R), the agent does not load the
configuration file and properly start the data collector
when CTIRA_HOSTNAME is not the same as the hostname.

APAR: IZ50755
Abstract: KVM_SERVER.OVERALL_CPU_UTIL ATTRIBUTE INCORRECT
Additional Information: The attribute value is displayed for
CPU0, even in a multi-CPU environment.

6.1.2-TIV-ITM_VMWVI-IF0003
-------------------------------
APAR: IZ50291
Abstract: VMWARE VI CLIENT CRASHES WHEN UNABLE TO LOGOUT
OF DATASOURCE
Additional Information: When the kvmviclient process loses its
connection to the data source, usually the VMware
Virtual Center, the client sometimes crashes when
trying to logout before establishing a new connection.

6.1.2-TIV-ITM_VMWVI-IF0002
-------------------------------
APAR: IZ44750
Abstract: PERCENT RDY FOR VIRTUAL MACHINE CPU INCORRECT
Additional Information: The "Percent Rdy" column of the Virtual
Machine CPU workspace is incorrectly calculated.

6.1.2-TIV-ITM_VMWVI-IF0001
-------------------------------
APAR: IZ43613
Abstract: TEP VIEW NOT DISPLAYING DATA DUE TO PROBLEMS WITH CACHE
Additional Information: The caching algorithm has been improved.
In very large environments (greater than 50 VM guests
per host), the data request for VM-related workspaces,
such as the CPU workspace, can still exceed the default
timeout for displaying the data. Users can change the
timeout value for data requests,
KVM_REPORT_COLLECTION_TIMEOUT, from 20 to 10 seconds to
decrease the time allowed to wait for the data request
and fall back to the cached values. This will decrease
the time waiting for the workspace to display the data.
See section 6.4 for details on how to change the value
of KVM_REPORT_COLLECTION_TIMEOUT.

APAR: IZ43591
Abstract: TEP VIEW NOT DISPLAYING DATA DUE TO LARGE DATA REQUESTS
Additional Information: This fix makes smaller data requests
and greatly improves performance.

APAR: IZ42708
Abstract: AGENT CORE DUMPS ON LINUX WHEN RECEIVING MALFORMED DATA
Additional Information: The problem occurs when VMware API
requests receive malformed data.


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

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


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

- 6.1.2-TIV-ITM_VMWVI-IF0005.README - This README file
- 6.1.2-TIV-ITM_VMWVI-IF0005.tar - Fix archive .tar format
- 6.1.2-TIV-ITM_VMWVI-IF0005.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.1.2-TIV-ITM_VMWVI-IF0005/kvm_li6243_tema_if0005.tar
- 6.1.2-TIV-ITM_VMWVI-IF0005/kvm_lx8263_tema_if0005.tar
- 6.1.2-TIV-ITM_VMWVI-IF0005/kvm_winnt_tema_if0005.cab
- 6.1.2-TIV-ITM_VMWVI-IF0005/kvmli6243.dsc
- 6.1.2-TIV-ITM_VMWVI-IF0005/kvmlx8263.dsc
- 6.1.2-TIV-ITM_VMWVI-IF0005/KVMWINNT.dsc


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

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (6.1.2-TIV-ITM_VMWVI-IF0005.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, this includes the drive letter.

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

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

On UNIX systems, if the fix was expanded to
<TEMP>/6.1.2-TIV-ITM_VMWVI-IF0005, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.1.2-TIV-ITM_VMWVI-IF0005/kvm_xxxxxx_tema_if0005.tar

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

In the following example, the file would be
kvm_li6243_tema_if0005.tar.
> ./cinfo -i
Monitoring Agent for VMware VI
li6243 Version: 06.10.02.00

On a Windows system, if the fix was expanded to
<TEMP>\6.1.2-TIV-ITM_VMWVI-IF0005, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.1.2-TIV-ITM_VMWVI-IF0005\kvm_winnt_tema_if0005.cab

5.3 Remote agent update
------------------------------
1. Transfer the appropriate archive file (6.1.2-TIV-ITM_VMWVI-IF0005.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, this includes the drive letter.

2. Expand the archive file using the tar command on UNIX systems or
an unzip 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 Commands reference
of the IBM Tivoli Monitoring Administrator's Guide.

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

On a Windows system,
if the fix was expanded to <TEMP>/6.1.2-TIV-ITM_VMWVI-IF0005:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.1.2-TIV-ITM_VMWVI-IF0005

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 login 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 updateAgent commands, see Appendix A. Commands
reference of 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 061002005

On a Windows system:
> %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 061002005

Note:
- The component (-t) for the updateAgent command is specified as
two characters (vm), not three characters (kvm).
- The node (-n) for the updateAgent command is the managed system
name of the operating system (OS) agent to be updated. The
target node for an 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 superceded 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, this must include the drive letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, this must include the drive letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the tacmd to view
the agent's current version. You are required to login 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 a Windows system, 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.10.02.05

6.4 Changing KVM_REPORT_COLLECTION_TIMEOUT
------------------------------------------
To change the KVM_REPORT_COLLECTION_TIMEOUT value for the agent
(as described in Additional Information for APAR IZ43613 in section
2.4):

On Windows systems:

- Edit the <CANDLEHOME>\TMAITM6\KVMENV_<instance> file and
change:

KVM_REPORT_COLLECTION_TIMEOUT=20

to

KVM_REPORT_COLLECTION_TIMEOUT=10

- Restart the IBM Tivoli Monitoring for Virtual Servers: VMware
VI Agent.

On Linux systems:

- Edit the <CANDLEHOME>\config\vm.ini file and
change:

KVM_REPORT_COLLECTION_TIMEOUT=20

to

KVM_REPORT_COLLECTION_TIMEOUT=10

- Restart the IBM Tivoli Monitoring for Virtual Servers: VMware
VI 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(R) are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (R or TM), these symbols
indicate U.S. registered or common law trademarks owned by IBM
at the time this information was published. Such trademarks may
also be registered or common law trademarks in other countries.
A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at
http://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.

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.1.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 DD?
6.1.2-TIV-ITM_VMWVI-IF0005.README 9/10/2009 English 19702 FTP DD
6.1.2-TIV-ITM_VMWVI-IF0005.zip 9/10/2009 English 2765646 FTP DD
6.1.2-TIV-ITM_VMWVI-IF0005.tar 9/10/2009 English 6359040 FTP DD

Product Alias/Synonym

VMware agent

Problems (APARS) fixed
IZ59503, IZ52961, IZ51038, IZ50755, IZ50291, IZ44750, IZ43613, IZ43591, IZ42708

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring for Virtual Environments
ITM Agent for VMWare VI V6

Software version:

6.1.2

Operating system(s):

Linux, Windows

Software edition:

All Editions

Reference #:

4024302

Modified date:

2009-09-10

Translate my page

Machine Translation

Content navigation