IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI-IF0003

Download Description

Copyright International Business Machines Corporation 2015.
All rights reserved.


Component: IBM(R) Tivoli(R) Monitoring for Virtual Environments:
VMware VI Agent,Version 7.2.0 Fix Pack 2.

Component ID: 5724L92VI

Interim Fix: 0003, 7.2.0.2-TIV-ITM_VMWVI-IF0003

Date: February 4, 2015

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: IV65302
Abstract: : Inconsistency in the snapshot count.
Additional Information:
The snapshot count that is provided by the agent
and the vCenter or the ESX Server does not match.
If all the snapshots from the particular VM have
been removed, the agent does not reflect the
changes in the snapshot count.
To resolve this problem, recycle the agent.

APAR: IV68477
Abstract: : Snapshot size incorrectly captured.
Additional Information:
The snapshot size given by the powershell cmdlets
and the agent does not match.
Impact of this fix will reflect in the snapshot size
related metrics of the Virtual Machines and Datastores
attribute groups.

APAR: IV68498
Abstract: : The summarized tables for the KVM Datastores
attribute group display the value of zero for the
Percent Overcommitted metric.
Additional Information:
Inappropriate warehouse scaling was applied for the
Percent Overcommitted metric in the KVM Datastores
attribute group. As a result, valid data values were
also being ignored for the summarization.

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

2.3 Enhancements
------------
Virtual Machine :
A new metric has been added in the Virtual Machines attribute
group to obtain the overall datastore utilization in percentage
for the particular virtual machine.

Clusters :
The Percent Datastore Usage attribute has been added to obtain the
overall datastore usage in percentage for a specific cluster.

Clustered Datastores:
Enhancements have been made to provide overall status of the datastore,
instead of cluster.


2.4 Superseded fixes
---------------------
7.2.0.2-TIV-ITM_VMWVI-IF0002
7.2.0.2-TIV-ITM_VMWVI-IF0001

2.5 APARs and defects included from superseded fixes
----------------------------------------------------
APAR: IV52535
Abstract: Historical data is missing for KVM_VM_DATASTORE_UTILIZATION.
Additional Information:
Inconsistency in the Historical data collection for the attribute
group KVM_VM_DATASTORE_UTILIZATION.All the virtual machines listed
under the column Virtual_Machine are not considered for summarization.
This is the issue with the design consideration followed to define
primary keys for attribute group KVM_VM_DATASTORE_UTILIZATION.

APAR: IV55838
Abstract: VMWARE VI AGENT WORKSPACE HANGS AND STOPS SHOWING DATA.
Additional Information:
VMware VI Agent remains online. Subnodes representing ESX
servers remain online. But updates to the set of ESX servers,
situation status and TEP displays stop.

APAR: IV53276
Abstract: AGENT INSTANCE IS NOT RESPONDING TO THE REQUEST.
Additional Information:
If multiple data sources are configured for a single agent
instance and some of the data sources (either vCenter or
ESX Server) are not responding to connection request then agent
hangs on the non-responsive data source. Further, it is unable
to discover any other configured data sources and no response
is received for the data sources.

APAR: IV58575
Abstract: Unable to get data for Datastores attribute group.
Additional Information:
The agent was not able to collect the data for the data stores because the
null check was missed in the Datastores attribute group. Therefore, no data
displayed on Tivoli Enterprise Portal.

Defect: 210166
Abstract: Inappropriate value for HBA speed
Additional Information:
A defect in the VMware vSphere API documentation states that the unit for the
HBA speed is bits per second. However, the unit for the HBA speed is Gigabits.

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 7.2.0 fix pack 2.

Please refer to the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.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 7.2.0 fix pack 2.

Note: When the prerequisite is installed, the version number
is 07.20.02.00


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

- 7.2.0.2-TIV-ITM_VMWVI-IF0003.README - This README file
- 7.2.0.2-TIV-ITM_VMWVI-IF0003.tar - Fix archive .tar format
- 7.2.0.2-TIV-ITM_VMWVI-IF0003.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 environment; use the .zip file if
you are working in a Windows environment.

The fix archive file contains the following files:
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_li6263_tema_IF0003.tar
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_lx8266_tema_IF0003.tar
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_ls3266_tema_IF0003.tar
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_tems_teps_tepd_IF0003.tar
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_tems_teps_tepd_IF0003.zip
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_winnt_tema_IF0003.cab
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_wix64_tema_IF0003.cab
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvmli6263.dsc
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvmlx8266.dsc
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/kvmls3266.dsc
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/KVMWINNT.dsc
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/KVMWIX64.dsc
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/vm_dd.properties
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/vm_dd_072002003.xml
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/vm_dd_072002002.xml
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/vm_dd_072002001.xml
- 7.2.0.2-TIV-ITM_VMWVI-IF0003/vm_dd_072002000.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

- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------------
1. Transfer the appropriate archive file
(7.2.0.2-TIV-ITM_VMWVI-IF0003.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 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>/7.2.0.2-TIV-ITM_VMWVI-IF0003, the install command is
(navigate to $CANDLEHOME/bin):

./itmpatch -h <$CANDLEHOME/>
-i <TEMP>/7.2.0.2-TIV-ITM_VMWVI-IF0003/kvm_xxxxxx_tema_IF0003.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_IF0003.tar
> ./cinfo -i
Monitoring Agent for VMWare agent
li6263 Version: 07.20.02.03

On a Windows system, if the fix was expanded to
<TEMP>\7.2.0.2-TIV-ITM_VMWVI-IF0003, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.2.0.2-TIV-ITM_VMWVI-IF0003\kvm_xxxxx_tema_IF0003.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_IF0003.cab.
> kincinfo -i
VM Monitoring Agent for VMware VI
WINNT Version: 07.20.02.03 Build: 201501150000

5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(7.2.0.2-TIV-ITM_VMWVI-IF0003.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 the IBM Tivoli
Monitoring Administrator's Guide.

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

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

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 072002003

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
-v 072002003
> %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 072002003
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 also provides agent support upgrade through the ITM SDA feature.
This fix 7.2.0.2-TIV-ITM_VMWVI-IF0003 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
(7.2.0.2-TIV-ITM_VMWVI-IF0003.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_IF0003.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)
checked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the VMware VI
07.20.02.03 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 the 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 that the agent was updated correctly, use the tacmd
command to view the current version of the agent 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 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 be:
07.20.02.03


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

********** Monday, January 15, 2015 3:23:40 PM ***********
User : Administrator Group : NA
Host Name : HOSTNAME Installer : Ver: 072002003
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
.
.
.
VM Monitoring Agent for VMware VI
WINNT Version: 07.20.02.03 Build: 201501150000

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


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


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.


10.0 Notices
=======
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 jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

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

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

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.