IBM Tivoli Monitoring: Windows (R) OS Agent 6.2.3.2-TIV-ITM_WIN-IF0002

Download Description

Copyright International Business Machines Corporation 2013.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: Windows(R) OS Agent,
Version 6.2.3 Fix Pack 2

Component ID: 5724C040W

Interim Fix 0002 (6.2.3.2-TIV-ITM_WIN-IF0002)

Date: August 26, 2013

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 Copyright and trademark information
10.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: IV36542
Abstract: AVG % PROCESSOR TIME > 100 IN PROCESS ATTRIBUTES
Additional Information: In the Process attributes group, the "Avg % Processor Time"
is showing as greater than 100 % . This attribute is averaged on
the number of processors, therefore it should not exceed 100.
However, sometimes the ITM agent is receiving inconsistent values
from the monitored platform.
In addition to that, the number of processors is wrongly calculated
when hyperthreading is enabled. And the calculation of the average
is incorrect.
A similar problem for the average also exists for the attribute
"High Process Average Utilization" in the "Processor Summary"
attribute group.

APAR: IV32008
Abstract: Windows OS Agent crashes during the collection of the Logical Disk info.
Additional Information: Windows OS Agent crashes during the collection of the
Logical Disk info due to a memory corruption.

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

2.3 Enhancements
----------------
None.

2.4 Superseded fixes
--------------------
6.2.3.2-TIV-ITM_WIN-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
APAR: IV27944
Abstract: LARGE AMOUNT OF MEMORY CONSUMED BY ITM WINDOWS OS AGENT
KNTCMA.EXE PROCESS
Additional Information: In Windoms 2008, ITM Windows OS agent
uses excessive memory when running situations that evaluate against
the "Event Log" attribute group (KNT.NTEVTLOG).
Large amounts of memory can be consumed quickly, or memory
use may grow over time indicating a memory leak against the
kntcma.exe process. The memory leak becomes evident when
many events are being received by the system.
The problem is associated to event XML information appended to the
"description" attribute of Event Log attribute group. By displaying
the list of events in the TEP user iterface,
extra data is appended with an XML tag such as <EventData>
<Data> or <UserData> or similar ones.

APAR: IV29794
Abstract: XML TAGS INCLUDED IN THE EVENT DESCRIPTION
Additional Information: In Windows 2008, When displaying the
"description" attribute of the Event Log attribute group for the
ITM Windows agent, extra data is appended with an XML tag such as
<EventData> <Data> or <UserData> or similar ones.
The problem is associated to the wrong default value for the
NT_LOG_APPEND_XML_DATA environment variable.
This variable is used to specify if the event description in XML
format should be appended to the plane description of the event or not.
If the parameter is not specified, the default should be equivalent to 0
(do not append the xml information). On the contrary the default is
set to 1 (append the xml information to the event description).

defect: 190436
Abstract: OS Agent failed to recognize the correct windows OS

defect: 193711
Abstract: Windows OS Agent doesn't show the proper information in
"Printer Overview" workspace for a Fax Printer.

defect: 193713
Abstract: Windows OS Agent do crash on Windows 2012 reading the
Network configuration.

defect: 194287
Abstract: Windows OS Agent do crash on Windows 2012 due to the
event Log manager.


3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Windows OS Agent User's Guide, version 6.2.3, Fix Pack 2.

Please refer to the IBM Software Product Compatability 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
------------------------------
- IBM Tivoli Monitoring, Version 6.2.3 Fix Pack 2.


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

- 6.2.3.2-TIV-ITM_WIN-IF0002.README - This README file
- 6.2.3.2-TIV-ITM_WIN-IF0002.tar - Fix archive .tar format
- 6.2.3.2-TIV-ITM_WIN-IF0002.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 Microsoft Windows(R) environment.

The fix archive file contains the following:
6.2.3.2-TIV-ITM_WIN-IF0002/knt_winnt_tema_IF0002.cab
6.2.3.2-TIV-ITM_WIN-IF0002/knt_wix64_tema_IF0002.cab
6.2.3.2-TIV-ITM_WIN-IF0002/KNTWINNT.dsc
6.2.3.2-TIV-ITM_WIN-IF0002/KNTWIX64.dsc

Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.

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
(e.g. 6.2.3.2-TIV-ITM_WIN-IF0002.tar) 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.

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 that agent platform.
For more information on the itmpatch command, see section 6.2

For example:
On a Windows system, if the fix was expanded to
<TEMP>\6.2.3.2-TIV-ITM_WIN-IF0002, the install command would be,
depending if you are installing a 32 bit agent or a 64 bit agent:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.3.2-TIV-ITM_WIN-IF0002\knt_winnt_tema_IF0002.cab
or

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.3.2-TIV-ITM_WIN-IF0002\knt_wix64_tema_IF0002.cab

Note: if the itmpatch command gets this error:
"The application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log for more detail."
it's necessary install the "visualstudio redistribution package" before to run
run the itmpatch command.
For a 32bit architecture, the name of this package is vcredist_x86.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=5582
For a 64bit architecture, the name of this package is vcredist_x64.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=2092


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.3.2-TIV-ITM_WIN-IF0002.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 extract utility on Windows systems. This step 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 Command Reference Guide.

For example:
On UNIX systems,
if the fix was expanded to <TEMP>/6.2.3.2-TIV-ITM_WIN-IF0002
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.3.2-TIV-ITM_WIN-IF0002

On a Windows system,
if the fix was expanded to <TEMP>\6.2.3.2-TIV-ITM_WIN-IF0002
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.3.2-TIV-ITM_WIN-IF0002

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
might 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 updateAgent commands, see the IBM Tivoli Command Reference Guide.

For example:
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 NT
-n <Managed System Name>
-v 062302002

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 NT
-n <Managed System Name>
-v 062302002

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (NT), not three characters (KNT).
- 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 the "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
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

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:
<CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
<TEMP> points to the temporary directory where the fix is located.

- 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 command
to view the agent's current version after the agent is restarted.
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 NT

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 NT

When the agent update is successful, the agent version should now be:
06.23.02.02

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

You can also use the GUI (Manage Tivoli Enterprise Monitoring Services) to
verify the agent is successfully updated.

For the agent on a Windows system, the version number is 06.23.02.02.


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.