IBM Tivoli Monitoring: UNIX (R) OS Agent 6.2.3.3-TIV-ITM_UNIX-IF0010

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.2.3 Fix Pack 3

Component ID: 5724C040U

Interim Fix 0010 (6.2.3.3-TIV-ITM_UNIX-IF0010)

Date: October 14, 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: IV65679
Abstract: Add new fields to the UNIXDISK attribute group for zfs properties and disable the use of libzfs
Additional Information: Add new fields to the UNIXDISK attribute group for the following zfs properties:
quota,
reservation,
refquota - available in zpool version 9 and higher,
refreservation - available in zpool version 9 and higher,
usedbydataset - available in zpool version 13 and higher,
usedbychildren - available in zpool version 13 and higher,
usedbysnapshots - available in zpool version 13 and higher,
usedbyrefreservation - available in zpool version 13 and higher.
Add two other fields:
1) zfs_space_used that is the space occupied by the dataset; It also contains the used space of other dataset occupying its space.
2) zfs_space_used_percent that is the percentage of zfs_space_used on the size of the disk.
The size on disk is computed with the following algorithm:
1) size = zfs pool size
2) if the quota is defined and it is less than zfs pool size, then size = quota; the quota is also checked for all the parent datasets up to the root.
3) if the refquota is defined and it is less than zfs pool size and quotas, then size = refquota.
Also add the environment variable KUX_USELIBZFS that control the use of the libzfs.so to collect the zfs metrics.
Its default value is 0, setting it to 1 the agent uses the api of libzfs.so to collect the zfs metrics; this can be useful when the command zfs is not available.

Note: The zpool version is visible with the command: zpool upgrade -v

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

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

2.4 Superseded fixes
--------------------
6.2.3.3-TIV-ITM_UNIX-IF0009
6.2.3.3-TIV-ITM_UNIX-IF0008
6.2.3.3-TIV-ITM_UNIX-IF0007
6.2.3.3-TIV-ITM_UNIX-IF0006
6.2.3.3-TIV-ITM_UNIX-IF0005
6.2.3.3-TIV-ITM_UNIX-IF0004
6.2.3.3-TIV-ITM_UNIX-IF0003
6.2.3.3-TIV-ITM_UNIX-IF0002
6.2.3.3-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.3.3-TIV-ITM_UNIX-IF0009
---------------------------
APAR: IV60096
Abstract: Socket leak when KCA_IP_DIR value changed.
Additional Information: The OS Agent communicates with the Watchdog
process (kcawd) via a directory defined by KCA_IP_DIR. The default
for this directory is $CANDLEHOME$/$BINARCH$/$PRODUCTCODE$/bin/pasipc.
If this value is overwritten and does not exist it will result in a
socket leak.

6.2.3.3-TIV-ITM_UNIX-IF0008
---------------------------
APAR: IV60533
Abstract: Defunct processes generated on AIX by the Monitoring Agent for UNIX OS
Additional Information: While collecting data for the UNIX Machine Information attribute group a temporary
subprocess is spawned on AIX but not properly cleaned up, this resulting in a defunct process left on the
system whose parent process ID is the kuxagent process ID.

6.2.3.3-TIV-ITM_UNIX-IF0007
---------------------------
APAR: IV53161
Abstract: The UNIX OS agent stops reporting Disk attributes on Solaris
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: 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: 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: IV54290
Abstract: UNIX OS Agent on Solaris does not show the not-running Solaris Zones
Additional Information: UNIX OS Agent on Solaris does not show the not-running Solaris Zones. Altough not
active, these zones can be present in the system with the following statuses: "Configured", "Incomplete",
"Installed".

APAR: IV48133
Abstract: Unix OS Agent is unable to monitor the requested file path in the Unix File Information attribute
group
Additional Information: The Unix OS agent sometimes misses detecting the correct value of the Path (Unicode)
attribute as defined in the situation predicate, so it's unable to monitor the requested full path.

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

6.2.3.3-TIV-ITM_UNIX-IF0006
---------------------------
APAR: IV51697
Abstract: Agent Management Services Watchdog not reliable message
sent at agent shutdown.
Additional Information: When the OS Agent shutsdown normally,
sometimes the critical situation UNIX_AMS_Alert_Critical is
triggered indicating "Agent Management Services watchdog not
reliable". This situation should be triggered when the Watchdog
process (kcawd) is no longer monitoring the OS agent. This should
not be triggered during a normal shutdown.

APAR: IV37438
Abstract: Watchdog process (kcawd) status displayed as "Stopped"
after rearm command issued.
Additional Information: After the rearm command is issued, the
watchdog process (kcawd) is restarted; however, the status
displayed in the Agent Management Services workspace continues
to show "Stopped", and the Process ID displays 0. The process is
actually running. This is a display-only issue and can affect
the Monitoring Agent for UNIX and Linux OS.

6.2.3.3-TIV-ITM_UNIX-IF0005
---------------------------
APAR: IV50627
Abstract: New attributes to monitor when approaching the maximum number of processes
Additional Information: 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 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: IV32093
Abstract: SITUATIONS WITH UNIX PRINT QUEUE.PRINT QUEUE NAME DO NOT WORK
Additional Information: On AIX Unix_Print_Queue.Print_Queue_Name seems to be padded with
blanks, that generates problems while evaluating situations that use this column.

6.2.3.3-TIV-ITM_UNIX-IF0004
---------------------------
APAR: IV43912
Abstract: PROCESSES THAT EXCEED 4096 BYTES FOR THE COMMAND STRING ARE NOT FILTERED CORRECTLY
Additional Information: The UNIX OS agent Process Filter feature allows you to apply regular
expressions for selecting the relevant portion of a long process command line. This is so
that it can fit into the "Process Command (Unicode)" attribute which is 768 characters
long and cannot be further expanded due to architectural limitations. However, this
feature is currently based on an internal 4096 byte long buffer, so applying the filter
does not work for processes whose command line is longer than 4096 characters.
Inconsistent results in the "Process Command (Unicode)" attribute may occur in such a case.

APAR: IV37929
Abstract: NO DATA DISPLAYED WHEN COLLECTING AIX PROCESS DATA
Additional Information: On AIX 5.3, the agent might core when collecting AIX process data.

6.2.3.3-TIV-ITM_UNIX-IF0003
---------------------------
APAR: IV35898
Abstract: HIGH CPU IN UNIX AGENT ON SOLARIS IN THE MOUNT_STAT
Additional Information: ITM Unix OS Agent on Solaris loca zones can
experiment high cpu in mount_stat process due to an hang while
collectingmountPointSpecial value for ZFS filesystems.

APAR: IV36516
Abstract: MOUNT_STAT CAN CRASH ON SOLARIS INTEL GLOBAL ZONE
Additional Information: On Solaris the Monitoring Agent for UNIX OS
mount_stat process can crash statvfs64 API gets a permission denied error:
(51149395.01A7-C:mount_stat.cpp,192,"exec_statvfs64") WARNING: statvfs64 failed for "/ams/ams/database/apc-4.0.10_9.0.10-108719/NI" with errno 13 (Permission denied)

APAR: IV36767
Abstract: NFS_STAT PROCESS CRASHES ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS nfs_stat
process can crashes generating the following stacktrace:
---------------------
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:stacktrace_handler+0x58
/lib/sparcv9/libc.so.1:0xd8684
/lib/sparcv9/libc.so.1:0xcc1f8
/lib/sparcv9/libc.so.1:0xcc404
/lib/sparcv9/libc.so.1:strlen+0x50 [ Signal 11 (SEGV)]
/sys_apps_01/tivoli/ITM/agent/tmaitm6/sol286/lib/libkbb.so:RAS1_Format+0x3c
/sys_apps_01/tivoli/ITM/agent/tmaitm6/sol286/lib/libkbb.so:RAS1_Printf+0x2c
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:main+0x360
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:_start+0x17c
Fatal Error (11) Detected. Exiting
----------------------

6.2.3.3-TIV-ITM_UNIX-IF0002
---------------------------
APAR: IV31251
Abstract: DATA NOT COLLECTED FOR WPAR
Additional Information: No data is displayed for any of the AIX WPAR workspaces.
The problem occurs when a WPAR has multiple IP addresses. The following message
appears in the aixdp_daemon log files:
(Thu Sep 20 01:08:28 2012.0015-1:aixtranslator.c,2757,"ux_CollectData") Data collection failed for attribute group 29:WPAR_Information
(Thu Sep 20 01:08:28 2012.0016-1:aixtranslator.c,2758,"ux_CollectData") Exit: 0x0
(Thu Sep 20 01:08:28 2012.0017-1:aixdp_daemon.cpp,2148,"reply_wpar_information_request") Data collection failure

APAR: IV37296
Abstract: HP SWAP BASE CALCULATION INCLUDES RESERVED AND MEMORY VALUES
Additional Information: Agent uses a formula to calculate swap space on HP-UX
systems that includes the reserve and memory values. Some customers need the
swap counter does not include memory and reserved values.

APAR: IV37297
Abstract: UNIX OS AGENT STAT_DAEMON PROCESS HANGS WHILE RECEIVING NETWORK INFO ON AIX
Additional Information: in case of failures of perfstat_netinterface API it can
happen that ifstat process doesn't send expected data to stat_daemon process
and it remains in waiting status for that data.
Below an example of stat_daemon last traces when this problem happens:
(Wed Feb 20 17:10:45 2013.0022-1:stat_daemon_ifstat.cpp,739,"refresh_ifstat_buffer") Active RAS1 Classes: EVERYT EVERYE EVERYU
(Wed Feb 20 17:10:45 2013.0023-1:stat_daemon_ifstat.cpp,739,"refresh_ifstat_buffer") Entry
(Wed Feb 20 17:10:45 2013.0024-1:stat_daemon_ifstat.cpp,741,"refresh_ifstat_buffer") ifstat_fd is 6
(Wed Feb 20 17:10:45 2013.0025-1:stat_daemon_ifstat.cpp,742,"refresh_ifstat_buffer") if_count is 0
(Wed Feb 20 17:10:45 2013.0026-1:stat_daemon_ifstat.cpp,743,"refresh_ifstat_buffer") size if_count is 4

APAR: IV37298
Abstract: KUXAGENT PROCESS CAN CRASH DUE TO TIMEOUT ON PIPE COMMUNICATION
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent
can crash if it is experiencing delays in communication on pipes with other
OS Agent processes (like stat_daemon or mount_stat), generating a crash
with the following stack trace:
/opt/IBM/ITM/sol296/ux/bin/kuxagent:stacktrace_handler+0x58
/lib/sparcv9/libc.so.1:0xd8684
/lib/sparcv9/libc.so.1:0xcc1f8
/lib/sparcv9/libc.so.1:0xcc404
/lib/sparcv9/libc.so.1:0xd85fc [ Signal 14 (ALRM)]
/lib/sparcv9/libc.so.1:0xd1de4
/lib/sparcv9/libc.so.1:cond_wait+0x10
/lib/sparcv9/libc.so.1:_pthread_cond_wait+0x8
/opt/IBM/ITM/tmaitm6/sol286/lib/libkdc.so:0x36f88
/opt/IBM/ITM/tmaitm6/sol286/lib/libkdc.so:0x37520
/opt/IBM/ITM/tmaitm6/sol286/lib/libkdc.so:rpc__listen+0x330
/opt/IBM/ITM/tmaitm6/sol286/lib/libkra.so:0x2a399c
/opt/IBM/ITM/tmaitm6/sol286/lib/libkra.so:kglpsrvr+0x6a8
/opt/IBM/ITM/tmaitm6/sol286/lib/libkra.so:kramain+0x684
/opt/IBM/ITM/sol296/ux/bin/kuxagent:main+0x3a4
/opt/IBM/ITM/sol296/ux/bin/kuxagent:_start+0x17c
Fatal Error (14) Detected. Exiting

6.2.3.3-TIV-ITM_UNIX-IF0001
---------------------------
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


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

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html


3.1 Prerequisites for this fix
------------------------------
- IBM Tivoli Monitoring, Version 6.2.3 Fix Pack 3.


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

- 6.2.3.3-TIV-ITM_UNIX-IF0010.README - This README file
- 6.2.3.3-TIV-ITM_UNIX-IF0010.tar - Fix archive .tar format
- 6.2.3.3-TIV-ITM_UNIX-IF0010.zip - Fix archive .zip format

NOTE: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file if
you are working in a Microsoft Windows(R) environment.

The fix archive file contains the following :
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_aix523_tema_if0010.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_aix526_tema_if0010.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_hp11_tema_if0010.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_hp116_tema_if0010.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_hpi116_tema_if0010.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_sol283_tema_if0010.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_sol286_tema_if0010.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_sol293_tema_if0010.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_sol296_tema_if0010.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kux_sol606_tema_if0010.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.3.3-TIV-ITM_UNIX-IF0010/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.3.3-TIV-ITM_UNIX-IF0010.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.3.3-TIV-ITM_UNIX-IF0010, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.3-TIV-ITM_UNIX-IF0010/kux_xxxxxx_tema_if0010.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_if0010.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.23.03.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.3.3-TIV-ITM_UNIX-IF0010.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory. Note: On Windows, this includes
the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. To add the agent fix bundles into the remote deploy depot, use
the tacmd addBundles command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the tacmd addBundles command, see the IBM Tivoli
Monitoring Command Reference Guide.

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

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

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 062303010

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 062303010

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.3.3-TIV-ITM_UNIX-IF0010 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.2.3.3-TIV-ITM_UNIX-IF0010.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_if0010.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)

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

7. Note that the version reported by cinfo command for the TEP Browser
(TEPB) App Support component will not be updated by the itmasi tool.


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

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

ux Monitoring Agent for UNIX OS
aix523 Version: 06.23.03.10

.
.
.
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.10 201410140000 20141014 1101
UX TEPS App Support/Monitoring Agent for UNIX OS WICNS 06.23.03.10 201410140000 20141014 1101
UX TEPB App Support/Monitoring Agent for UNIX OS WIXEB 06.23.03.00 30241 20130624 1101
UX TEPD App Support/Monitoring Agent for UNIX OS WIXEW 06.23.03.19 201410140000 20141014 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.