IBM Tivoli Monitoring: Windows (R) OS Agent 6.2.2.4-TIV-ITM_WIN-IF0004

Download Description

Copyright International Business Machines Corporation 2011.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: Windows(R) OS Agent,
Version 6.2.2 Fixpack 4

Component ID: 5724C040W

Interim Fix 0004, 6.2.2.4-TIV-ITM_WIN-IF0004

Date: December 13, 2012

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.

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

2.1 APARs
-------------
APAR: IV03507
Abstract: Windows OS Agent doesn't fill the descriprion_u with long japanese strings
Additional Information: Monitoring the Event Log when the description is in Japanese
characters and the string is greater than 377 characters, the
field description_u is empty

APAR: IV09138
Abstract: Windos OS Agent retrieves wrong number of processors
Additional Information: In a machine with 4 CPU system with 6 core each, the number of
processors is 24 but the Windows OS Agent reports 32 processors

APAR: IV14967
Abstract: Agent reports info just for 32 processors
Additional Information: The Monitoring Agent for Windows OS reports
incorrect number of CPUs in "Processor" and "Processor Overview"
workspaces due to a limitation in used Microsoft Performance
Counter (Processor). Starting from Windows 2008 R2 a new Perfmon
Counter has been introduced "Processor Information" that is able
to correctly manage CPUs with more than 4 cores and machines
with more than 64 CPUs.

APAR: IV15762
Abstract: INCOMPLETE EVENT DESCRIPTION IN WINDOWS 2008
Additional Information: Starting From Windows 2008 and Vista, and following releases,
the additional event information that could be inserted or
appended to the event description, are not displayed in the
description attribute of the Event Log attribute group,
if the base description of the event is missing.
Only the default string "N/A" is displayed in TEP when the
description is not available.

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

APAR: IZ94770
Abstract: Logical Disk Name is truncated at 64 characters
Additional Information: In case of mounted logical disk name on long directory name, the logical
disk name is truncated at 64 character (the column's dimension)

2.2 Defects
--------------
Defect: 181195
Abstract: For an event with an empty description in TEP, the XML form of the EventData
is not being displayed after setting the environment variable NT_LOG_APPEND_XML_DATA

Defect: 182828
Abstract: The enhancement is that, when processing a Windows event log the following trace record is written in the log
if trace level is selected (UNIT:KNLFUNCS ALL) :
The record indicates how many event log records are processed for each iteration.

Defect: 182907
Abstract: wrong result with multiple ip addresses on the same NIC card

Defect: 190436
Abstract: Win 2012: OS Agent failed to recognize the correct windows OS version

Defect: 193711
Abstract: Win 2012: No proper data in "Printer Overview" workspace

Defect: 193713
Abstract: Win 2012: Agent restarts unexpectedly on Win 2012

Defect: 194287
Abstract: Win 2012: OS Agent crashed on Win 2012 due to event Log

2.3 Superseded fixes
-------------------------
6.2.2.4-TIV-ITM_WIN-IF0003
6.2.2.4-TIV-ITM_WIN-IF0002
6.2.2.4-TIV-ITM_WIN-IF0001

2.4 APARS and defects included from superseded fixes
---------------------------------------------------------------
APAR: IV20934
Abstract: Windos OS Agent allows values greater than 100 for %user time
and %privileged time
Additional Information: Windows OS Agent allows values greater than 100
(so out of range 0-100) for the attribute "% User Time" and
"% Privileged Time" of the "Processor" attribute group

APAR: IV00440
Abstract: WINDOWS OS AGENT REPORTS ITM_EVENT_LOG ALERTS OUT OF ORDER
Additional Information: Monitoring Agent reads event log's portions in reverse order.
This behavior is due to a backward reading of event log and a not backward management of the events in a deque.

APAR: IZ95382
Abstract: Calls to getinstances.vbs from OS Agent never termiate
Additional Information: The watchdog script getInstances.vbs
requires CANDLE_HOME to be set when it is invoked from the Windows
OS agent. There appears to be a problem/limitation on Windows that
the environment variable is not passed to the script from the
environment after a new ITM install is done, until the machine is
rebooted. The calls to the script hang and do not terminate.

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in Chapter 2 of
the IBM Tivoli Monitoring: Monitoring Agent for Windows OS User's Guide, version 6.2.2 FP2.

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, version 6.2.2 Fix Pack 4


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

- 6.2.2.4-TIV-ITM_WIN-IF0004.README
- 6.2.2.4-TIV-ITM_WIN-IF0004.tar
- 6.2.2.4-TIV-ITM_WIN-IF0004.zip

Note: The .tar and .zip files are identical in content. If you
are working in a UNIX(R), use the .tar file. If you are working
in a Windows(R) environment, you can use either the .tar or .zip
file.

The fix archive file contains the following :
6.2.2.4-TIV-ITM_WIN-IF0004/knt_winnt_tema_if0004.cab
6.2.2.4-TIV-ITM_WIN-IF0004/knt_wix64_tema_if0004.cab
6.2.2.4-TIV-ITM_WIN-IF0004/KNTWINNT.dsc
6.2.2.4-TIV-ITM_WIN-IF0004/KNTWIX64.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

- 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. Stop the agent.

2. Transfer the appropriate archive file (6.2.2.4-TIV-ITM_WIN-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.

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

4. 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 Windows systems, if the fix was expanded to <TEMP>\6.2.2.4-TIV-ITM_WIN-IF0004,
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.2.4-TIV-ITM_WIN-IF0004\knt_winnt_tema_if0004.cab
or

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.2.4-TIV-ITM_WIN-IF0004\knt_wix64_tema_if0004.cab

5. Start the agent.

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.2.4-TIV-ITM_WIN-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 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.

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

On Windows systems,
if the fix was expanded to <TEMP>\6.2.2.4-TIV-ITM_WIN-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.2.2.4-TIV-ITM_WIN-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
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 "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Command Reference 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 NT
-n <Managed system name>
-v 062204004

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 NT
-n <Managed system name>
-v 062204004

Note:
- The component (-t) for the 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
========================

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 path 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 NT

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 NT

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

When the agent update is successful, the agent version is:
06.22.04.04.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.

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


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.