IBM Tivoli Monitoring: Unix(R) OS Agent 6.3.0.2-TIV-ITM_UNIX-IF0006

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.3.0 Fix Pack 2

Component ID: 5724C040U

Interim Fix 0006 (6.3.0.2-TIV-ITM_UNIX-IF0006)

Date: May 26, 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: IV53199
Abstract: UNIX OS Agent CPU Pct attribute in the Process attribute group not
in synch with AIX topas and nmon tools
Additional Information: The UNIX OS Agent is aligned to the command
ps -p <PID> -o pcu
when reporting CPU utilization of processes in the CPU Pct attribute
of the Process attribute group. This value is normalized to the number
of online logical processors and may be largely different from what
the topas and nmon tools display on AIX. Topas normalizes processes'
CPU utilization to the LPAR entitlement, if in a shared capped or
dedicated configuration, or to the actual current physical processors'
consumption, if in a shared uncapped configuration. Nmon does not apply
any normalization, so values can exceed 100%.

APAR: IV54057
Abstract: UNIX OS Agent on Solaris may crash while monitoring processes
Additional Information: In a highly dynamic environment with hundreds of
running processes frequently going down and up, the UNIX OS agent may
fail to read one of the files in the /proc file system reporting
metrics for the specified process ID (PID), because that PID no longer
exists. This condition is not correctly handled and may lead to a crash
because of memory left uninitialized.

APAR: IV60455
Abstract: ADD THE FIELD "FULLY QUALIFIED FILE NAME" FIELD TO FILE INFO
Additional Information: Monitoring Agent for Unix OS File Information
attribute group does not have a unique field to specify both path
and file name.

APAR: IV47363
Abstract: SITUATION UADVISOR_OMUNX_SP2OS MUST BE DISABLED BY DEFAULT.
Additional Information: UADVISOR_OMUNX_SP2OS is a default situation that gets
distributed to every UNIX OS agent that connects to a monitoring server.
It was thought to populate a virtual table at the monitoring server
(OMUNX.SP2OS) for optimizing the support of older IBM Super Computers
(named SP2). No workspaces are based on queries to this table, nor
there are other dependencies on it. The attributes are duplicates of the
UNIX OS System table. Since the situation is defined as an autostarted
situation with a three minute interval, it runs on every UNIX OS agent
producing unneeded overhead.

APAR: IV51670
Abstract: INCORRECT VALUES FOR AGGREGATE CPU AVG_CPU* ATTRIBUTES
Additional Information: The UNIX OS agent running on AIX incorrectly
calculates the averages for aggregate CPU utilization over the last
1,5,15 and 60 minutes. These are reported by the following attributes
in the SMP_CPU group: Avg_CPU_Busy_1, Avg_CPU_Busy_5, Avg_CPU_Busy_15,
Avg_CPU_Busy_60, Avg_CPU_Sys_1, Avg_CPU_Sys_5, Avg_CPU_Sys_15,
Avg_CPU_Sys_60, Avg_CPU_Usr_1, Avg_CPU_Usr_5, Avg_CPU_Usr_15 and
Avg_CPU_Usr_60. These values do not match the output of system
commands like mpstat or vmstat because they are not the mean value
across individual CPUs contributions.

APAR: IV53161
Abstract: THE UNIX OS AGENT ON SOLARIS STOPS REPORTING DISK ATTRIBUTES
Additional Information: After the UNIX OS agent has been running for some
time, most of the attributes in the Disk group may evaluate to
Not Collected. When this happens all of the disks are affected and only
a recycle of the agent can restore normal functionality. This issue is
due to a lack of recovery logic when one of the system calls that allow
inter-process communications between kuxagent and mount_stat daemons
gets interrupted by a signal. When this occurs kuxagent assumes
mount_stat is no longer reachable and stops collecting disk metrics.

APAR: IV55187
Abstract: The UNIX OS Agent reports incorrect aggregate CPU attributes when
running on HP-UX or Solaris.
Additional Information: The UNIX OS Agent reports incorrect aggregate CPU
attributes when running on HP-UX or Solaris. On the HP-UX and Solaris
platforms the User CPU (Percent), System CPU (Percent),
Idle CPU (Percent), Wait I/O (Percent) and CPU Busy (Percent)
attributes of the 'aggregate' CPU in the SMP CPU attribute group are
calculated as simple averages across individual CPUs' contributions.
In doing this the agent does not take into account that some CPUs could
be disabled and should be excluded not to bias the final average.

APAR: IV55868
Abstract: VOLUME GROUPS SHOW "UNKNOWN" AND "NOT COLLECTED"
Additional Information: In the Volume Group Details and Logical Volume Group
views of the Disk Usage--AIX Storage workspace, the Name and State
columns might show "unknown" values and the other columns might show
"Not Collected" values.

APAR: IV57730
Abstract: NON UTF-8 CHARACTERS IN UTF-8 ATTRIBUTES OF THE TOP PROCESSES
Additional Information: Process Command, Base Command and User Name
attributes in the Monitoring Agent for UNIX OS Agent Top CPU
Processes and Top Memory Processes attribute groups are defined
as UTF-8 strings but non UTF-8 characters may be left in case of
an error occurred during UTF-8 conversion.
As one of the consequences the Warehouse Proxy Agent treats them as
UTF-8 strings, but since non-UTF-8 characters are found an error like
the following may result:
"A value in the attribute Process_Command after UTF8 conversion has a
length (1560) greater than the column size (1536)".

APAR: IV60498
Abstract: EMPTY UNICODE ATTRIBUTES IF UTF-8 CONVERSION FAILS
Additional Information: The Monitoring Agent for UNIX OS does not apply
truncation in case the conversion from the native string to UTF-8
encoding fails due to a buffer overflow. As a result the unicode
attribute is filled with blanks.

Prerequisites
-------------
APAR: IV46707
Abstract: Situations defined against "File Pattern" attributes do not
trigger alerts if no "Match Option" value is specified.
Additional Information: Defining a situation without specifying a
"Match Option" will never trigger as the situation does not gather
attribute data.

APAR: IV47410
Abstract: Useless information provided by "Processes/Threads in Run Queue".
Additional Information: The Monitoring Agent for UNIX OS has a metric called
"Processes/Threads in Run Queue" that provides the number of processes
that can be run waiting for execution by the CPU. This attribute is
useless if the number of active CPUs is not taken into consideration,
so a new attribute is needed to provide this information.

APAR: IV50627
Abstract: New attributes to monitor when approaching the maximum number of
processes
Additional Information: New attributes to monitor when approaching the
maximum number of processes. All UNIX operating systems define
configurable parameters to limit the maximum number of processes
that can run on the system.
The UNIX OS agent should be capable to report such a value, as well
as the percentage of currently running processes with respect to this
limit, as it is an important indicator that the system is approaching
its maximum capacity.

APAR: IV52450
Abstract: UNIX OS Agent does not manage the value "Shutting Down" for the
Solaris_Zones.Status attribute
Additional Information: UNIX OS Agent does not manage the value "Shutting Down"
for the Solaris_Zones.Status attribute.

APAR: IV52558
Abstract: Make sure the UNIX OS agent kills its children during the shutdown
phase
Additional Information: During the shutdown phase, the UNIX OS agent sends
termination signals to its children processes to stop them. The process
IDs (PIDs) of the child processes stat_daemon, mount_stat (and on AIX
aixdp_daemon) are saved in memory when they are spawned from the parent
kuxagent process during the startup phase. In a rare scenario, if a
child process has died and the system has reused the same PID for
another process, a signal 15 or 9 may be sent to what it believes is a
child process of kuxagent during shutdown. For reliability, additional
checks should be performed before sending out any termination signals,
and for serviceability the PID values that are being killed need to be
printed to the agent log file.

APAR: IV53168
Abstract: Space_Available_Percent attribute cannot be used in Take Action
commands executed on the monitoring server.
Additional Information: When a situation in the Disk attribute group triggers
and the Space_Available_Percent attribute is not defined in the
situation predicate, the value of Space_Available_Percent is blank when
used in a Take Action command on the monitoring server.

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.

APAR: IV54290
Abstract: UNIX OS Agent on Solaris does not show the non-running Solaris Zones
Additional Information: UNIX OS Agent on Solaris does not show the non-running
Solaris Zones. Although not active, these zones can be present in the
system with the following statuses: "Configured", "Incomplete", "Installed".


2.2 Defects
-----------
Defect: 208949
Abstract: Minor leaks - and defunct processes - in AIX code

Prerequisites
-------------
Defect: 209068
Abstract: on_demand/REPORT situation not deleted from global list

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

2.4 Superseded fixes
--------------------
6.3.0.2-TIV-ITM_UNIX-IF0005
6.3.0.2-TIV-ITM_UNIX-IF0004
6.3.0.2-TIV-ITM_UNIX-IF0003
6.3.0.2-TIV-ITM_UNIX-IF0002
6.3.0.2-TIV-ITM_UNIX-IF0001

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

APAR: IV59293
Abstract: Monitoring Agent for UNIX OS fills the file log <hostname>_ux_<timestamp>.log with the
message: "/etc/resolv.conf does not exist."
Additional Information: In the data collection of the Network attribute group is present the
field Domain. This field on AIX is collected parsing the result of the command
"/usr/sbin/namerslv -s". If the file /etc/resolv.conf does not exist, this command send to
stderr the message "/etc/resolv.conf does not exist." each 30 seconds filling the log
<hostname>_ux_<timestamp>.log.
Moreover, for the same cause, the log <host>_ux_ifstat_<timestamp>-<n>.log contains a series
of message "Unable to find domain".

APAR: IV47168
Abstract: Unix OS Agent on AIX fills up the <HOSTNAME>_UX_<TIMESTAMP>.LOG file
Additional Information: Unix OS Agent on AIX fills up the <HOSTNAME>_UX_<TIMESTAMP>.LOG file due
to an expected error message of the entstat command. The error message has the format:
entstat: 0909-003 Unable to connect to device <device>, errno = 19

APAR: IV54974
Abstract: UNIX OS Agent File Information attribute group sends to TEMS more
lines than necessary
Additional Information: UNIX OS Agent File Information attribute group send
the entire contents of the directory to TEMS in a situation with a single
file and a time field compared with LocalTime.

APAR: IV52071
Abstract: UNIX FILE INFORMATION DOESN'T SEND INFO FOR MULTIPLE FILES IN A
SITUATION
Additional Information: The UNIX OS Agent File Information attribute is
unable to monitor a list of files with the Missing operator in a situation.

APAR: IV48133
Abstract: UNIX FILE INFORMATION UNABLE TO MONITOR THE REQUESTED FILE PATH
Additional Information:The Unix OS agent sometimes misses to
detect the correct value of the Path (Unicode) attribute, as
defined in the situation predicate, so it's unable to monitor
the requested full path to monitor.

APAR: IV52312
Abstract: The UNIX OS agent reports 'Unknown' for the Machine Serial Number on Solaris
Additional Information: On the Solaris platform the UNIX OS agent exploits command 'eeprom nvramrc',
that optionally reports the Chassis Serial Number, to fill the Machine Serial Number attribute
in the Machine Information attribute group. This command may report other hardware specific data
stored in the machine eeprom and the parsing code is not robust enough to handle all the cases.
When it misses to retrieve the Chassis Serial Number, "Unknown" is returned for this attribute.

APAR: IV51151
Abstract: Disk attributes are incorrect for ZFS filesystems
Additional Information: The Unix OS agent doesn't read the correct size of the zfs dataset when its
quota or refquota are set up

APAR: IV47625
Abstract: Wrong calculation of aggregate CPU in shared LPARs for the UNIX OS agent.
Additional Information: Values reported for User CPU (Percent),System CPU (Percent),Idle CPU (Percent)
and Wait I/O (Percent) of the aggregate CPU (CPU ID=-1) in the SMP_CPU group are incorrect when the
UNIC OS agent runs in a shared LPAR. Starting in version 6.3.0, these values are averages over a
time interval that must be in sync with the sampling interval of the running situation or historical
data collection. However, a bad isolation of the raw data taken by multiple situations in a shared
LPAR environment actually returns averages computed on random time intervals.

APAR: IV46733
Abstract: Unix OS Agent incorrectly calculates the used space on zfs in wrong way on Solaris 10
Additional Information: Unix OS Agent incorrectly calculates the used space on zfs in wrong way
on Solaris 10 for the valued quota variable.

Defect: 208422
Abstract: Wrong entry for File Information query in the agent log file

Defect: 208425
Abstract: Wrong entries for File attribute in the agent log file

Feature: 208178
Abstract: Reduce Unix OS Agent memory consumption while monitoring
processes.

Defect: 208197
Abstract: duplicated info in AIX Networks Adapters workspace
on machines with multiples adapters.

Defect: 208357
Abstract: Agent can crash when a MISSING situation on UNIXPS table is distributed as first
situation.


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


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

- 6.3.0.2-TIV-ITM_UNIX-IF0006.README - This README file
- 6.3.0.2-TIV-ITM_UNIX-IF0006.tar - Fix archive .tar format
- 6.3.0.2-TIV-ITM_UNIX-IF0006.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.3.0.2-TIV-ITM_UNIX-IF0006/kux_tems_teps_tepd_if0006.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_tems_teps_tepd_if0006.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_aix523_tema_if0006.tar - UNIX Agent binaries for AIX 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_aix526_tema_if0006.tar - UNIX Agent binaries for AIX 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_hp11_tema_if0006.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_hp116_tema_if0006.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_hpi116_tema_if0006.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_sol283_tema_if0006.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_sol286_tema_if0006.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_sol293_tema_if0006.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_sol296_tema_if0006.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kux_sol606_tema_if0006.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.3.0.2-TIV-ITM_UNIX-IF0006/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.3.0.2-TIV-ITM_UNIX-IF0006.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.3.0.2-TIV-ITM_UNIX-IF0006, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.0.2-TIV-ITM_UNIX-IF0006/kux_xxxxxx_tema_if0006.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_if0006.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.30.02.00


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

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

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 063002006

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 063002006

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
------------------------
This fix (6.3.0.2-TIV-ITM_UNIX-IF0006) 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,
and Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.3.0.2-TIV-ITM_UNIX-IF0006.tar
or .zip) to the IBM Tivoli Enterprise Portal Servers,
Tivoli Enterprise Portal Servers, and 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_if0006.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. 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:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java on your system might 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.

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 Portal Desktop (TEPD)

Continue through the remaining GUI panels selecting the product
06.30.02.06 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.30.02.06

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.30.02.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.30.02.06

.
.
.

2. To verify the agent support files were updated correctly run the cinfo
command on a Unix/Linux server, or the kincinfo command on Windows server,
and check UNIX OS Support version.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------

kincinfo -t ux
********** Friday, February 28, 2014 7:02:03 PM **********
User : Administrator Group : NA
Host Name : WIN2K3SP2-32BIT Installer : Ver: 062303000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory


PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

UX TEMS App Support/Monitoring Agent for UNIX OS WICMS 06.23.03.08 201402280000 20140228 1101
UX TEPS App Support/Monitoring Agent for UNIX OS WICNS 06.23.03.08 201402280000 20140228 1101
UX TEPB App Support/Monitoring Agent for UNIX OS WIXEB 06.23.03.00 30241 20130628 1101
UX TEPD App Support/Monitoring Agent for UNIX OS WIXEW 06.23.03.08 201402280000 20140228 1101


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.