IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent 6.2.2.5-TIV-ITM_UNIX-IF0007

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.2.2 Fix Pack 5

Component ID: 5724C040U

Interim Fix 0007 (6.2.2.5-TIV-ITM_UNIX-IF0007)

Date: January 31, 2014

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: IV53503
Abstract: UNIX OS Agent may send false alerts on missing processes
Additional Information: Due to an incorrect variable initialization, the UNIX OS agent may
incorrectly assign the collected metrics for running processes. When this occurs the
situation evaluation code receives garbage in the processes data rows and this can make
the situation fire if it is based on a MISSING clause condition. Symptom of this issue
is the following log entry, available also at ERROR default RAS1 setting:
(Fri Nov 29 09:35:15 2013.3659-16:get_ps_table.cpp,650,"get_ps_table") unknown process report type, default to all process data type
(Fri Nov 29 09:35:15 2013.365A-16:get_ps_table.cpp,658,"get_ps_table") Exit: 0x0

APAR: IV03411
Abstract: "PROCESS COMMAND" CONTAINS JUST FIRST 80 CHARS FOR SOME PROCESSES
Additional Information: On Solaris the Monitoring Agent for UNIX OS is not able to collect
all arguments for some processes, some processes are truncated at around 80 chars in
Process command attribute when looking in TEP.

APAR: IV19092
Abstract: Unix Os Agent can generate high CPU usage in HP when are active many situations
against processes
Additional Information: When are active many (about 100) situations monitoring the processes
attribute group, the agent can generate high CPU usage. The introduction of a configurable
delay after the request to the OS helps to avoid the peaks of the CPU even if this lenghten
the time of the data collection.

APAR: IV36900
Abstract: PERFORMANCE PROBLEM IN COLLECTING PROCESS ARGUMENTS ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent process can generate
high cpu usage when it collect processes arguments. This issue can occur when there are
processes that have a huge as file in their proc folder (proc/PID/as). In order to solve
this issue ITM code has been changed in order to use Solaris APIs to collect processes
arguments instead of directly read /proc filesystem. In order to restore the old behaviour
set the following key in the ux.ini file and reastart the Unix OS Agent (default is TRUE):
KUX_PARGS_API=FALSE

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

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

2.4 Superseded fixes
--------------------
6.2.2.5-TIV-ITM_UNIX-IF0006
6.2.2.5-TIV-ITM_UNIX-IF0005
6.2.2.5-TIV-ITM_UNIX-IF0004
6.2.2.5-TIV-ITM_UNIX-LA0003
6.2.2.5-TIV-ITM_UNIX-LA0002
6.2.2.5-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.5-TIV-ITM_UNIX-IF0006
---------------------------
APAR: IV27109
Abstract: HUGE PAGE SCAN RATE AND PAGE RECLAIMS ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS
randomly reports wrong information for some UNIXMEM attributes
like Page Scan Rate and Page Reclaims due to an internal memory
corruption.

6.2.2.5-TIV-ITM_UNIX-IF0005
---------------------------
APAR: IV14938
Abstract: KUX_VMSTAT PROCESS TAKES A REALLY HUGE TIME TO INITIALIZE
Additional Information: On Solaris the Monitoring Agent for UNIX OS
kux_vmstat process can take a very long time to initialize,
so the agents keeps running but take a very long time before
data is seen on TEP.

APAR: IV23485
Abstract: SYSTEM CALLS ATTRIBUTE IN SMP_CPU IS NOT A RATE
PER SECOND AS DESCRIBED IN THE USER'S GUIDE
Additional Information: On Solaris the Monitoring Agent for UNIX
OS reports wrong number of SystemCalls because it is not a rate
per second as described in the User's Guide, but it reports the
number of SystemCalls in last 30 seconds.

6.2.2.5-TIV-ITM_UNIX-IF0004
---------------------------
APAR: IV09263
Abstract: KUXAGENT PROCESS CRASHES ON SOLARIS 8 WHEN
AN OPERATION ON A PIPE IS INTERRUPTED BY THE OS
Additional Information: On Solaris the Monitoring Agent
for UNIX OS kuxagent process can crash when it is
reading/writing data on a pipe and the OS interrupts
this operation.

APAR: IV10301
Abstract: WRONG MEMORY USED WHEN USING ZFS ADAPTIVE REPLACEMENT
CACHE
Additional Information: The ZFS adaptive replacement cache (ARC)
tries to use most of a system's available memory to cache
file system data. The default is to use all of physical memory
except 1 GB. As memory pressure increases, the ARC relinquishes
memory. In this configuration the Monitoring Agent for UNIX OS
reports ARC memory as used memory, in order to address this
scenario some new attributes are needed to collect ARC information:

Net Memory Used (MB): NETMEMUSED - The number of megabytes of
physical memory used on the system not considering
memory used by ZFS Adaptive Replacement Cache.
Net Memory Available (MB): NETMEMFREE - The number of megabytes of
physical memory available on the system considering as
free memory the amount of memory used by ZFS Adaptive
Replacement Cache.
Net Memory Used (Percent): NETMEMUPCT - Percent of physical memory
used on the system considering as free memory the amount
of memory used by ZFS Adaptive Replacement Cache.
Net Memory Available (Percent): NETMEMFPCT - Percent of physical
memory available on the system not considering memory
used by ZFS Adaptive Replacement Cache.
ZFS ARC Size (MB): ARCSIZE - The number of megabytes of physical
memory used on the system by ZFS Adaptive Replacement
Cache.

Note: in order to view these new attributes in TEP you have to manually
create new queries.

APAR: IV11756
Abstract: UNIX OS AGENT REPORTS WRONG CPU INFO AFTER CPUS ARE
DYNAMICALLY ADDED/REMOVED IN A ZONE POOL
Additional Information: On Solaris, the Monitoring Agent for UNIX OS installed
in a Local Zone takes a snapshot of which CPUs are handling the zone
when it starts, but if CPUs are dynamically added or removed from the
zone pool the agent is not able to detect them and reports incorrect
information related to IDs, status and metrics.

6.2.2.5-TIV-ITM_UNIX-LA0003
---------------------------
Defect: 165471
Abstract: Avoid to use utmpx in HP and return 'Not Available'
for related values
Additional Information: On HP the Monitoring Agent for UNIX OS
kuxagent and stat_daemon processes open, using HP APIs,
utmpx file in RW mode. In order to avoid to open this file
a new configuration key has been added:

KUX_SKIP_HP_UTMPX

Default values is FALSE but it can be enabled
using the following key in the ux.ini file:

KUX_SKIP_HP_UTMPX=True

In this way the following attributes show
'Not Available':
- "User Sessions" of the "Unix All Users" Group
- "Number of User Sessions", "Up Time (Seconds)"
and "Boot Time" of the "System Attribute" Group
- "Idle Time" and "User ID" of the "User Attribute"
Group

'No one logged on':
- "Login Name", "Login Name (Unicode)" of the
"User Attribute" Group

6.2.2.5-TIV-ITM_UNIX-LA0002
---------------------------
APAR: IV07415
Abstract: PERFORMANCE PROBLEM IN COLLECTING DISKS PERFORMANCE INFO
Additional Information: On Solaris the Monitoring Agent for UNIX OS stat_daemon
and kuxdstat processes can generate high CPU usage if it monitors a
Veritas Dynamic Multipathing with thousands of disks.
In order to avoid this issue a configuration key to disable this kind of
datacollection is required. Variable KUX_DISABLE_UNIXDPERF has been added
in order to disable disk performance datacollection.
Default value is FALSE, it can be enabled setting it to TRUE in the
ux.ini file:
KUX_DISABLE_UNIXDPERF=TRUE|FALSE

6.2.2.5-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IV02284
Abstract: ITM KUXAGENT HAS PERFORMANCE PROBLEM IN RESOLVING TTY NAMES FOR
PROCESSES ON HP-UX
Additional Information: The fix uses a cache for the resolution of TTY names
related to each process. The environment variable TTY_REFRESH_TIME that
can be specified in the configuration file ux.ini allows the user to
set the refresh time in minutes for the cache.
If the environment variable is not specified, the agent uses the
default refresh time of 60 minutes. Please also note that specifying
TTY_REFRESH_TIME=0 results in the cache not being used at all.

Another configuration key has been added to the Unix OS Agent,
this keyword can be used to skip TTY name conversion: KUX_SKIP_TTY.
Default values is FALSE but it can be enabled using the following
key in the ux.ini file:
KUX_SKIP_TTY=TRUE

APAR: IV02285
Abstract: ITM KUXAGENT HAS PERFORMANCE PROBLEM IN ALLOCATING MEMORY FOR
PROCESS DATA COLLECTION ON HP-UX
Additional Information: On HP-UX the Monitoring Agent for UNIX OS kuxagent
process generates high cpu usage and takes a very long time to
allocate/reallocate memory in order to store process information.

APAR: IV06922
Abstract: KUXAGENT HAS PERFORMANCE PROBLEM IN COPYING STRINGS
Additional Information: The Monitoring Agent for UNIX OS kuxagent
process generates high cpu usage when it copies a huge number
of strings that are related to process attribute group, while
using strncpy() API.

APAR: IV06977
Abstract: ITM OS AGENT OPENS UTMPX FILE IN RW MODE ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX
OS kuxagent and stat_daemon processes open, using Solaris APIs,
OS utmpx file in RW mode. In order to open this file in READ_ONLY
mode a new configuration key has been added: KUX_UTMPX_READONLY
Default values is FALSE but it can be enabled using the following
key in the ux.ini file:
KUX_UTMPX_READONLY=TRUE


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

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.2 Fix Pack 5.


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

- 6.2.2.5-TIV-ITM_UNIX-IF0007.README - This README file
- 6.2.2.5-TIV-ITM_UNIX-IF0007.tar - Fix archive .tar format
- 6.2.2.5-TIV-ITM_UNIX-IF0007.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.2.5-TIV-ITM_UNIX-IF0007/kux_tems_teps_tepd_if0007.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_tems_teps_tepd_if0007.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_aix523_tema_if0007.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_aix526_tema_if0007.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_hp11_tema_if0007.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_hp116_tema_if0007.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_hpi116_tema_if0007.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_sol283_tema_if0007.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_sol286_tema_if0007.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_sol293_tema_if0007.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_sol296_tema_if0007.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kux_sol606_tema_if0007.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.2.5-TIV-ITM_UNIX-IF0007/kuxhpi116.dsc - Descriptor file for HP-UX Itanium

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.

- It is recommended to verify the "cinfo" commands are operating
correctly on the system prior to installing the patch. See
section "7.0 Known problems and workarounds" for the workaround
for the problem titled "Remote deploy of the patch fails"

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.2.2.5-TIV-ITM_UNIX-IF0007.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 UNIX system, if the fix was expanded to
<TEMP>/6.2.2.5-TIV-ITM_UNIX-IF0007, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.5-TIV-ITM_UNIX-IF0007/kux_xxxxxx_tema_if0007.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 kux_aix523_tema_if0007.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.22.05.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.2.5-TIV-ITM_UNIX-IF0007.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.2.5-TIV-ITM_UNIX-IF0007
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.5-TIV-ITM_UNIX-IF0007

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

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 ux
-n <Managed System Name>
-v 062205007

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.

> %CANDLEHOME%\bin\tacmd updateAgent -t ux
-n <Managed System Name>
-v 062205007

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters ([xx]), not three characters ([kxx]).
- 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
------------------------
Fix 6.2.2.5-TIV-ITM_UNIX-IF0007 includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, 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 (6.2.2.5-TIV-ITM_UNIX-IF0007.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 (kux_tems_teps_tepd_if0007.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 product
06.22.05.07 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
=======================================
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 ux

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 ux

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

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


On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Mon Feb 11 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.22.05.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.22.05.07

.
.
.


7.0 Known problems and workarounds
==================================
It can happen that installation of this Interim Fix can fail when
there are a lot of defunct processes on the system related to kuxagent
process. When this issue occurs please stop situations related to
"Ping" attribute group, recycle the agent and them apply again the IF.


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.