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

Download Description

(C) Copyright International Business Machines Corporation 2010.
All rights reserved.

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

Component ID: 5724C040W

Interim Fix: 0002, (6.2.2.1-TIV-ITM_WIN-IF0002)

Date: April 19, 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.3.


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

2.1 APARs
---------
APAR: IZ68031
Abstract: WINDOWS AGENT CRASHES ON WINDOWS 2000 WHEN DNS REVERSE LOOKUP IS
DISABLED
Additional Information: When the DNS reverse lookup is disabled, kntcma.exe may
crash. The problem has been ascertained on Windows 2000, although the
code is general.
The following line will be found in the logs:

(4A8D3A81.0012-408:kntutil.cpp,1081,"CKUtil::getIPbyHost")
getaddrinfo API call failed for USAS-VM001 with error An address
incompatible with the requested protocol was used.

APAR: IZ65407
Abstract: WINDOWS OS AGENT GOES OFF-LINE WHEN COLLECTING NETWORK
PORT ATTRIBUTE DUE TO REVERSE DNS LOOK-UP TIME-OUT
Additional Information: The IBM Tivoli Monitoring Agent for Windows OS can
hang when querying network ports information, when the DNS reverse
lookup is disabled. Several errors similar to the following will be logged:

(4A7BDB8F.0000-1B90:knt67agt.cpp,243,"TakeSample") gethostbyaddr
error <11004> for IP address <xx.xx.xx.xx >
(4A7BDB94.0000-1B90:knt67agt.cpp,243,"TakeSample") gethostbyaddr
error <11004> for IP address <xx.xx.xx.xx >

The agent will appear to be offline on the TEP, and will not
report any data for any workspace.
The environment variable REVERSE_LOOKUP_ACCEPTED_FAILURES
that can be specified in the configuration file
allows the user to set the number of accepted failures in the
reverse lookup. This can reduce the hang time.

APAR: IZ63069
Abstract: WINDOWS AGENT CRASHES IN NTNETWPORT TAKESAMPLE
Additional Information: The IBM Tivoli Monitoring Agent for Windows OS crashes
when querying network ports information. The following entries are
found in the Dr Watson log drwtsn32.log:
Application exception occurred:
App: C:\IBM\ITM\TMAITM6\kntcma.exe
Exception number: c0000005 (access violation)
FAULT location:
eip=7c81bd02
ntdll!ExpInterlockedPopEntrySListFault
The agent log might show errors in the gethostbyaddr function:
(4ACB69AC.0000-8CC:knt67agt.cpp,243,"TakeSample") gethostbyaddr
error <11004> for IP address <<xx.xx.xx.xx

APAR: IZ49591
Abstract: WINDOWS ITM OS AGENT CRASH USING FILE TREND SITUATIONS.
Additional Information: When using a File Trend Situations, the
process kntcma.exe (The Windows ITM OS Agent) crashes with
exception number: c0000094 (divide by zero). This is
happening with code level: 06.21.00
If trace (unit: knt ALL) is activated, the log terminates with
the following record (49DCBD86.0019-EE0:kntftagt.cpp,736,
"establish_Trend") Entry.


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


2.3 Superseded fixes
--------------------
6.2.2.1-TIV-ITM_WIN-IF0001


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

6.2.2.1-TIV-ITM_WIN-IF0001
--------------------------
APAR: IZ62041
Abstract: WINDOWS AGENT MAY CRASH WHEN CLEANING USER'S HASH MAP
Additional Information: In systems with multiple users, the IBM Monitoring
agent for Windows OS process kntcma.exe may crash when exiting the
event log manager. The event log manager exits when the event log
situations are closed.

APAR: IZ63793
Abstract: HANG for NT Processor Information when N. of processors > 9
Additional Information: In a system with 10 or more processors, collecting
data for the "NT Processor Information" attribute group (NTPROCINFO
table) will cause a infinite loop of the IBM Tivoli Monitoring
Agent for Windows OS. You will not be able to refresh the Windows
agent information on TEP and no data for it will be displayed until
the agent restarts. The hang can happen due to the "NT Processor
Information" data collection in any of the following cases:
-If you enable historical data collection for it
-If you start a situation for the NTPROCINFO table
-If you query the above table in a TEP view.

APAR: IZ64352
Abstract: BAD RESPONSE TIME FOR NT PROCESSOR INFORMATION IN MULTIPROCESSOR
MACHINES
Additional Information: Several minutes delay is experienced in multiprocessor
machines when querying the NT Processor Information attribute group.
The number of minutes is depending on the number of processors. For
instance, a 16 processors machines will show almost 5 minutes delay.
During that period, any other query to the same agent will be put in
wait. The delay can happen when a query is executed on the NT
Processor Information attribute group in any of the following cases:
-If you enable historical data collection for it
-If you start a situation for the NTPROCINFO table
-If you query the above table in a TEP view.

APAR: IZ64862
Abstract: OPTIONALLY DISABLE JOB OBJECT AND JOB OBJECT DETAILS PERFORMANCE
COUNTERS DATA COLLECTION
Additional Information: Data retrieval from the Windows Performance
Counters "Job Objects" and "Job Objects Details" can result in
an unexpected high CPU usage for the IBM Tivoli Monitoring Agent
for Windows OS kntcma.exe process.
The problem occurs when other applications running on the system
create several objects under the \BaseNamedObjects namespace,
because these will be queried by the Microsoft Performance
Libraries. Under this condition, any perfmon API client, like the
Windows OS Agent, may experience high CPU.
To avoid affecting Microsoft Performance Libraries, these
applications would need to create the objects under their own
private namespace. Additional information can be found at
the following links.

http://msdn.microsoft.com/en-us/library/ms684161(VS.85).aspx
http://msdn.microsoft.com/en-us/library/ms682419(VS.85).aspx
http://msdn.microsoft.com/en-us/library/ms684295(VS.85).aspx

This problem is with non-ITM code. Further details on the problem's
root cause and affected platforms can be found at the following link:
http://support.microsoft.com/default.aspx?scid=kb;en-US;2008368

Since this problem cannot be avoided, because it is with non-ITM
code, the purpose of this APAR is to provide an additional option
to disable data collection for Job Object and Job Object Details in
case this problem occurs. The APAR has been extended to exclude any
counter the agent relies on.

The environment variable NT_EXCLUDE_PERF_OBJS needs to be defined
to exclude Performance Counters data collection. The list of
Performance Counters that can be excluded is the following:
Paging File, Processor, LogicalDisk, Memory, Objects,
PhysicalDisk, Process, System, RAS Port, RAS Total,
Network Interface, Network Segment, UDP, TCP, IP, ICMP, HTTP,
HTTP Content Index, Active Server Pages, Gopher Service,
FTP Server, Internet Information Services Global, MSMQ IS,
MSMQ Service, MSMQ Queue, UDPv4, Cache, MSMQ Sessions,
MSMQ Session, Job Object, Job Object Details, FTP Service,
Web Service, Content Index, Content Index Filter, NNTP Commands,
NNTP Server, SMTP Server, DHCP Server, DNS, Indexing Service,
Print Queue, Http Indexing Service, Web Service,
Indexing Service Filter, Thread, Server Work Queues,
IPv4, TCPv4, Redirector.
The list of counters should use a comma as a separator.
For instance,
NT_EXCLUDE_PERF_OBJS=Job Object,Job Object Details,Processor
Note that the following counters must be specified together in
order for the exclusion to function:
- Network Interface,TCPv4,TCP,UDPv4,UDP,IPv4,IP,ICMP

Furthermore, when the agent start, it verifies whether there are
counters that might lead to high CPU, considering a very long
execution time to get the counter value as an indication of high
CPU. The agent log file will report traces similar the following:

"Counter:'xxx' is taking long (>yy sec). This is a possible source
of high CPU usage
Consider to disable it by means of the NT_EXCLUDE_PERF_OBJS
variable"

Enhancement: 2789 (119830)
Abstract: Can't warehouse MAC address or FQDN
Additional Information: You can now start Historical Data Collection on the
NT IP Address attribute group. The table definition was changed from
"not warehousable " to "warehousable".


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.2 FP1.

3.1 Prerequisites for this fix:
-------------------------------
IBM Tivoli Monitoring, Version 6.2.2 FP1
The fix for the APAR IZ73759 must also be installed if you are using this
Interim Fix for a 64 bit ITM OS Agent on a 64-bit architecture.
For a 32 bit Agent on a 64-bit architecture, the fix for the
APAR IZ73759 is not necessary.


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

- 6.2.2.1-TIV-ITM_WIN-IF0002.README
- 6.2.2.1-TIV-ITM_WIN-IF0002.tar
- 6.2.2.1-TIV-ITM_WIN-IF0002.zip

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

The fix archive file contains the following :
6.2.2.1-TIV-ITM_WIN-IF0002/knt_tems_teps_tepd_IF0002.tar
6.2.2.1-TIV-ITM_WIN-IF0002/knt_tems_teps_tepd_IF0002.zip
6.2.2.1-TIV-ITM_WIN-IF0002/knt_winnt_tema_IF0002.cab
6.2.2.1-TIV-ITM_WIN-IF0002/knt_wix64_tema_if0002.cab
6.2.2.1-TIV-ITM_WIN-IF0002/KNTWINNT.dsc
6.2.2.1-TIV-ITM_WIN-IF0002/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

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.2.2.1-TIV-ITM_WIN-IF0002.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 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.2.1-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.2.1-TIV-ITM_WIN-IF0002\knt_winnt_tema_IF0002.cab

or

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.2.1-TIV-ITM_WIN-IF0002\knt_wix64_tema_if0002.cab


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

On a Windows system,
if the fix was expanded to <TEMP>/6.2.2.1-TIV-ITM_WIN-IF0002:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.2.2.1-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
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 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 NT
-n <Managed system name>
-v 062201002

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 062201002

Note:
- The component (-t) for the updateAgent command is specified as
two characters (NT), not three characters (KNT).
- 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
------------------------
The Agent support update is not required by the new apars in this fix,
but it was required by 6.2.2.1-TIV-ITM_WIN-IF0001.
If you have already installed such fix you do not need
to install the Agent support update.
This fix includes agent support updates for Tivoli Enterprise Portal
Server. It does not have agent support updates for Tivoli Enterprise
Monitoring Server and Tivoli Enterprise Portal Desktops.
Use the following steps to update the Tivoli Enterprise Portal Server.

1. Transfer the appropriate archive file
(6.2.2.1-TIV-ITM_WIN-IF0002.tar or 6.2.2.1-TIV-ITM_WIN-IF0002.zip)
to the IBM Tivoli Enterprise Portal Servers.

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. Expand the archive file (knt_tems_teps_tepd_IF0002.tar or.zip)
that contains the updates for Tivoli Enterprise Portal Server,
using the tar command on UNIX systems or an unzip utility on
Windows systems. This creates a directory structure that includes
a subdirectory called CD-ROM, with the necessary updates.

For example:

On a Windows system:
unzip
c:\temp\6.2.2.1-TIV-ITM_WIN-IF0002\knt_tems_teps_tepd_IF0002.zip

On a UNIX System:
tar -xvf
/tmp/6.2.2.1-TIV-ITM_WIN-IF0002/knt_tems_teps_tepd_IF0002.tar

4. Start the Application Support Installer GUI to install the fix.
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:
> $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar

On a Windows system:
> <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar

where <"C:\Program Files\IBM\Java142"> is the default drive
and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
on your system may vary.

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.

On a Windows system
c:\temp\6.2.2.1-TIV-ITM_WIN-IF0002\CD-ROM

On a UNIX system:
/tmp/6.2.2.1-TIV-ITM_WIN-IF0002/CD-ROM

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you would
like to add application support to. For this fix, the check boxes
should be as follows:

checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
unchecked - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the
Windows 06.22.01.02 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 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 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

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

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


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 date of the build displayed 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

*********** Fri Apr 10 12:23:53 EST 2010 ******************
User : root Group: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.22.01.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Tivoli Enterprise Portal Server update:

nt Monitoring Agent for Windows OS
tps Version: 06.22.01.02
.
.
.


On a Windows System:
--------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

*********** Friday, Apr 10, 2010 3:19:52 PM **********
User : Administrator Group : NA
Host Name : mywinbox Installer: Ver: 062201000
CandleHome: C:\IBM\ITM
Installitm: C:\IBM\ITM\InstallITM
*********************************************************************
.
.
.
Tivoli Enterprise Portal Server update:

NT Windows OS Support
WINNT Version: 06.22.01.02 Build: 2010040900

.
.
.


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

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.