IBM Tivoli Monitoring: Unix (R) OS Agent 6.2.2.4-TIV-ITM_UNIX-IF0013

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the “Problems Fixed” section below.

Download Description

(C) Copyright International Business Machines Corporation 2012. All

rights reserved.

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

Component ID: 5724C040U

Fix: Interim Fix 0013 (6.2.2.4-TIV-ITM_UNIX-IF0013)

Date: 22 January 2013

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


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

2.1 APARs
---------
APAR: IZ96588
Abstract: DISK NAME IS EMPTY WHEN ITS NAME IS LONGER THAN 96 CHARS
Additional Information: the Monitoring Agent for UNIX OS is not able
to collect a disk name when its length is longer than 96 chars.

APAR: IV21269
Abstract: WRONG INFORMATION FOR ZFS FILESYSTEMS
Additional Information: On Solaris the Monitoring Agent for UNIX OS
reports wrong information for ZFS filesystems, this is due to
the fact that it uses standard statfs API to collect metrics
instead of dedicated Oracle Solaris ZFS library.

APAR: IV32051
Abstract: MISSING CIFS FILE SYSTEMS
Additional Information: On AIX the Monitoring Agent for UNIX OS is
not able to monitor CIFS file systems when KBB_SHOW_NFS=TRUE is
set.

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

2.3 Enhancements
----------------
Support for Solaris 11 Sparc.

2.4 Superseded fixes
--------------------
6.2.2.4-TIV-ITM_UNIX-IF0012
6.2.2.4-TIV-ITM_UNIX-IF0011 (not shipped)
6.2.2.4-TIV-ITM_UNIX-IF0010
6.2.2.4-TIV-ITM_UNIX-IF0009 (not shipped)
6.2.2.4-TIV-ITM_UNIX-IF0008
6.2.2.4-TIV-ITM_UNIX-IF0007
6.2.2.4-TIV-ITM_UNIX-IF0006
6.2.2.4-TIV-ITM_UNIX-IF0005
6.2.2.4-TIV-ITM_UNIX-IF0004
6.2.2.4-TIV-ITM_UNIX-IF0003
6.2.2.4-TIV-ITM_UNIX-IF0002
6.2.2.4-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.4-TIV-ITM_UNIX-IF0012
---------------------------
APAR: IV21507
Abstract: HIGH CPU USAGE BY KUXAGENT ON HP-UX WHILE COLLECTING
PROCESS INFO
Additional Information: On HP-UX the Monitoring Agent for UNIX
OS kuxagent process uses high CPU while executing UTF8
conversions for UTF8 fields introduced in ITM 6.2.1.

A possible workaround for this issue is to avoid that
conversions on HP-UX machines that use codepage 1051. This
workaround can be enabled setting in the ux.ini file
KUX_SKIP_UTF8CONV_PROCESS=TRUE

6.2.2.4-TIV-ITM_UNIX-IF0010
---------------------------
APAR: IV19092
Abstract: Unix Os Agent can generate high CPU usage when are active
many situations against processes.
Additional Information: When are active many 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.
The APAR introduce the environment variable KUX_PROCESSES_DELAY.
Its default value is 0, indicating no sleep.
If the variable is not present, the agent assumes no sleep.
Its range is 0-1000 and it is exprime the delay in milliseconds
each 100 processes.

6.2.2.4-TIV-ITM_UNIX-IF0008
---------------------------
APAR: IV07319
Abstract: KMQ AND KQI agents on Solaris displays as stopped in AMS.
Additional Information: When the Watchdog code which is part of the
OS agent is monitoring the KMQ and KQI agents on Solaris, the
status is displayed as Stopped and the Process ID=0, even though
the agents are running. The monitoring of the agents continues to
work correctly, however because Watchdog cannot determine the
correct Process ID, it will call "cinfo -r" each cycle to help
determine the status of the agent, so full benefit of IZ91032
(Minimize calls to cinfo from Watchdog) is not fully utilized.

6.2.2.4-TIV-ITM_UNIX-IF0007
---------------------------
APAR: IV00113
Abstract: IFSTAT CAN CRASH ON AIX MACHINES
Additional Information: On AIX the Monitoring Agent for UNIX OS
ifstat process crashes when encountering network interface
cards (NICs) that are not in use.
Here below the stacktrace:
**** Fatal Error (11) Detected in kuxagent or a helper binary ****
**** Stacktrace in standard logs. Enable KBB_SIG1=-dumpoff in ini for core dumps ****
+++PARALLEL TOOLS CONSORTIUM LIGHTWEIGHT COREFILE FORMAT
version 1.0
+++LCB 1.0 Tue Apr 19 15:22:11 2011 Generated by IBM AIX 5.3
#
+++ID Node 0 Process 557214 Thread 1
***FAULT "SIGSEGV - Segmentation violation"
+++STACK
strcmp : 0x00000008
strcmp__FPCcT1 : 72 # in file </usr/vacpp/include/string.h>
get_mac_addr__FPCcPc : 212 # in file <ifstat-BSD.cpp>
main : 450 # in file <ifstat-BSD.cpp>
---STACK
---ID Node 0 Process 557214 Thread 1
---LCB
Fatal Error (11) Detected. Exiting

APAR: IV08836
Abstract: IFSTAT MEMORY LEAK ON AIX MACHINES WITH MANY
DISABLED NETWORK INTERFACES
Additional Information: On AIX, the Monitoring Agent for UNIX OS
ifstat process can leak memory when it is running on a
machine with many disabled network interfaces.

6.2.2.4-TIV-ITM_UNIX-IF0006
---------------------------
APAR: IV06842
Abstract: TAKE ACTION NOT EXECUTED WITH KUX FILEINFO ATTRIBUTE
Additional Information: On UNIX the Monitoring Agent for UNIX OS
doesn't execute the TakeAction related to FILEINFO attribute
group when there are multiple situations that monitor
the same file.

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.

Defect: 163297
Abstract: KUX_SKIP_TTY keyword is not described in IV02284
Additional Information: A new 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

6.2.2.4-TIV-ITM_UNIX-IF0005
---------------------------
APAR: IZ99020
Abstract: WATCHDOG CALLS TO CINFO SOMETIMES DO NOT TERMINATE.
Additional Information: When the watchdog utility which is part of the
OS agent issues calls to the "cinfo" command sometimes the calls
do not terminate which results in extraneous "cinfo" processes
running in the background. This can occur on either the UNIX or
Linux OS agents.

The fix for this APAR is not supported on the following platforms:
li6243 - Linux Intel R2.4 (32 bit)
ls3243 - Linux S390 R2.4 (31 bit)
ls3246 - Linux S390 R2.4 (64 bit)

6.2.2.4-TIV-ITM_UNIX-IF0004
---------------------------
APAR: IZ99326
Abstract: NFS_STAT PROCESS CRASHES ON HP
Additional Information: On HP the Monitoring Agent for UNIX OS nfs_stat
process crashes with the following message in the log file:
"ERROR: nfs_stat processing terminated! (Fri Apr 1 13:53:08 2011)
ERROR: The NFS and RPC statistics will not be refreshed anymore
ERROR: Please contact IBM support to determine the cause of the
nfs_stat failure"

APAR: IV03416
Abstract: UNIX OS AGENT ON AIX TAKES MORE THAT 2 SECONDS TO COLLECT AND
PROCESS DATA
Additional Information: On AIX the Monitoring Agent for UNIX OS takes more
than 2 seconds to collect/process information. This behavior is due
to a 2 seconds sleep in the code that is going to be removed and
replaced with a configurable delay.
A new configuration key has been added to the Unix OS Agent, this
keyword can be used to set the delay interval between the two process
datacollection (getprocs64 API) used to evaluate CPU consumption of
processes.
Default values is 2000 milliseconds (2 seconds) but it can be reduced
using the following key in the ux.ini file:
KUX_GETPROCS_DELAY=<time in milliseconds>

APAR: IV03417
Abstract: MORE TRACE POINTS IN HP AGENT CODE TO DEBUG PERFORMANCE ISSUES
Additional Information: On HP the Monitoring Agent for UNIX OS doesn't
report the seconds used to collect info for each situation or
workspace refresh.
This info is very useful and it should be added in order to debug
future performance issues, AIX and Solaris code already have performance
information.

APAR: IV03687
Abstract: ALLOW USER TO OVERRIDE LOCATION FOR KCAWD.PID FILE GENERATION
Additional Information: Provide an environment variable to allow for
overriding location where kcawd.pid and .kcawd_disable_stop
files are written. These files are currently written to
$CANDLEHOME/$BINARCH/<pc>/bin directory. Customers who want
to have these files written to a different location, in order
to allow just 'Read-Only' files in the bin directory, can use
the new environment variable KCAWD_WRITE_DIR.

The new enviroment variable KCAWD_WRITE_DIR can be set in ux.ini
or lz.ini file and must be set to an existing directory with
read-write permissions. For example:
KCAWD_WRITE_DIR=$CANDLEHOME$/tmp

NOTE: This new feature is supported by UNIX and Linux OS Agents
using Watchdog.

6.2.2.4-TIV-ITM_UNIX-IF0003
---------------------------
APAR: IZ96836
Abstract: UNIX OS AGENT DOESN'T REPORT DATA ON AIX
Additional Information: On AIX the Monitoring Agent for UNIX OS kuxagent
process can take a very long time to collect process information
due to a retry mechanism implemented to workaround an AIX issue with
the getargs API.
A configuration parameter is needed in order to give the customers
the capability to set the needed delay for the getargs retry mechanism.
New variable is KUX_GETARGS_DELAY that can accept values between 0
and 1000 milliseconds. Default values is 100 milliseconds.

APAR: IZ97074
Abstract: AGENT SEEMS TO HANG WITH PROCESS ATTRIBUTES GROUP
Additional Information: When using the Process attributes group (UNIXPS table)
in a TEP view or in a situation, the agent seems to hang. As a matter of
fact processing is continuing very slowly and could complete after a long
time (e.g. half an hour).
When it happens agent is processing the isatty function, isatty() is an
external function, and ITM cannot reduce its execution time. To avoid the
huge delay (or hang), ITM has to skip its usage. For that we introduced
a new enviroment variable KBB_EXCLUDE_SLOW_ISATTY to be set in the ux.ini
file. If the variable is set to 1

KBB_EXCLUDE_SLOW_ISATTY=1

the kuxagent will check the response time of the isatty() system call.
For slow response time, the agent will skip the calls to it, and the
kuxagent will not hang any more. A trace error record will be written
in the log file when the isatty() function is excluded.

APAR: IV00112
Abstract: KUXAGENT PROCESS CAN CRASH ON SOLARIS WHEN
KUX_SKIP_UTF8CONV_PROCESS=TRUE IS SET
Additional Information: On Solaris 10 the Monitoring Agent for UNIX
OS kuxagent process can crash when KUX_SKIP_UTF8CONV_PROCESS=true
is set. It crashes with the following stacktrace:

**** Stacktrace in standard logs. Enable KBB_SIG1=-dumpoff in ini
for core dumps ****
/opt/IBM/ITM/sol296/ux/bin/kuxagent:stacktrace_handler+0x58
/lib/sparcv9/libc.so.1:0xd7498
/lib/sparcv9/libc.so.1:0xcb02c
/lib/sparcv9/libc.so.1:0xcb238
/opt/IBM/ITM/sol296/ux/bin/kuxagent:__1cSomunx_unixps_agentKTake
Sample6M_v_+0x2f04 [Signal 10 (BUS)]
/opt/IBM/ITM/tmaitm6/sol286/lib/libkra.so:__1cFctiraTDriveData
Collection6M_I_+ 0x3d00x202d2d7a6f6f6d20

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.

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: IV02781
Abstract: FILE_INFORMATION.FILE_CONTENT_CHANGED DOES NOT WORK
Additional Information: Situations which include
File_Information.File_Content_Changed attribute o not work
properly on 6.2.2 FP4 or later. These situations do not fire
although monitored files were modified actually.

APAR: IV02818
Abstract: WATCHDOG DISPLAYS PID=0 FOR AGENT ON SOLARIS GLOBAL ZONE PATH
Additional Information: When the OS agent is running on a Solaris global
zones system with a linked or mounted $CANDLEHOME, the process IDs for
the agents will display "0" in the Agent Mangement Services workpace.
The watchdog monitoring continues to work correctly.

6.2.2.4-TIV-ITM_UNIX-IF0002
---------------------------
APAR: IV00749
Abstract: Multiple copies of kcawd started due to COLUMNS environment
variable.
Additional Information: When the OS agent is started, it checks to see if
the watchdog process (kcawd) is running and if not it will start it. If the
COLUMNS environment variables is set to a low value (79 in this case) on
the system when the agent is started, this cause the status check to fail.
This will result in multiple copies of kcawd to be started, up to the retry
limit for the day.

APAR: IV00769
Abstract: Watchdog displays pid=0 for agent when CANDLEHOME path is on
a mounted of linked filesystem.
Additional Information: The Agent Management Services watchdog utility
is not able to correctly identify the process ID for an agent when
the filesystem on which CANDLEHOME resides is mounted or symbolically
linked. It is necessary for Watchdog to validate the process ID
correctly in order for the fix for APAR IZ91032 (minimize calls to
cinfo) to be used. This can occur on the Linux or Unix OS
agents.

APAR: IV00799
Abstract: Watchdog restarting agent can result in multiple start commands
Additional Information: When the Agent Management Services watchdog
utility goes to restart an agent it has determined is down, if the start
command does not complete within the timeout parameter, it will
immediately try to start agent up to three retries in a row. This can
lead to multiple start commands running at the same time and result in
multiple copies of the agent getting started.

Defect: 155983
Abstract: "Monitoring Agent for Linux OS Operational Event: Agent started
successfully" message written to KLZ:LG0 every two minutes.

6.2.2.4-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IZ91446
Abstract: AGENT IS NOT ABLE TO CORRECTLY MANAGE A CONFIGURATION
VARIABLE WHEN IT HAS BLACK CHARS AFTER ITS VALUE.
Additional Information: Agent is not able to correctly manage a
configuration variable when it has black chars after its
value. This problem has been found for variable
KBB_SHOW_NETWORKMOUNTS.

APAR: IZ96602
Abstract: AGENT CRASHES ON SOLARIS WHEN IT TAKES A LONG TIME TO COLLECT
SOME PROCESS INFO
Additional Information: On Solaris the Monitoring Agent for UNIX OS
stat_daemon process sometimes takes a very long time to collect
some System Attributes like:
- Processes Idle
- Processes Runnable
- Processes Running
- Processes Sleeping
- Processes Stopped
- Processes Threads
- Processes Threads
- Processes Zombie
When this issue occurs the agent itself suppose that it is
hanging and execute a controlled shutdown.

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.

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
------------------------------
- IBM Tivoli Monitoring, Version 6.2.2 Fix Pack 4.


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

- 6.2.2.4-TIV-ITM_UNIX-IF0013.README - This README file
- 6.2.2.4-TIV-ITM_UNIX-IF0013.tar - Fix archive .tar format
- 6.2.2.4-TIV-ITM_UNIX-IF0013.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 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.4-TIV-ITM_UNIX-IF0013/kux_aix523_tema_if0013.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_aix526_tema_if0013.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_hp11_tema_if0013.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_hp116_tema_if0013.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_hpi116_tema_if0013.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_sol283_tema_if0013.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_sol286_tema_if0013.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_sol293_tema_if0013.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_sol296_tema_if0013.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kux_sol606_tema_if0013.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.2.4-TIV-ITM_UNIX-IF0013/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.4-TIV-ITM_UNIX-IF0013.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.1

For example:
On a UNIX system, if the fix was expanded to
<TEMP>/6.2.2.4-TIV-ITM_UNIX-IF0013, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.4-TIV-ITM_UNIX-IF0013/kux_xxxxxx_tema_if0013.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_if0013.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.22.04.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.2.4-TIV-ITM_UNIX-IF0013.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 Administrator's Guide.

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

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

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's 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 062204013

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 062204013

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.2.2.4-TIV-ITM_UNIX-IF0013) does not include changes to
the agent support files.

6.0 Additional installation information
=======================================

6.1 Installation instructions for agent baroc file
--------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using itmpatch command
-----------------------------------------------------
The itmpatch command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-t { <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.04.13

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

ux Monitoring Agent for UNIX OS
aix523 Version: 06.22.04.13

.
.
.

7.0 Known problems and workarounds
==================================
Abstract: The installation of this Interim Fix can fail when there
are a lot of defunct processes on the system related to kuxagent.
Workaround: When this issue occurs stop situations related to "Ping"
attribute group, recycle the agent and install the Interim Fix again.

Abstract: If the ITM home directory is defined as a linked directory,
such as /opt/IBM/ITM -> /opt/IBM/ITMbase and agents are running with
CANDLEHOME=/opt/IBM/ITM when upgrading to Fix Pack 04, the installer
on Linux and Solaris will restart any running agents using CANDLEHOME
set to the linked directory, such as CANDLEHOME=/opt/IBM/ITMbase.
Workaround: If this occurs, any local commands, such as "itmpatch" or
"itmcmd agent" should be done using the CANDLEHOME the OS agent was
restarted with. An agent started with a different CANDLEHOME
setting than the OS agent can result in the Process ID set to '0'.
The underlying monitoring will continue to work correctly.

Abstract: Process Name is displayed as "<agent name>.orig".
Problem: When upgrading to Fix Pack 4, if agents are running during
the install, they will normally be stopped before the code has been
upgraded and then restarted after the code has been updated. If the
agents do not stop for the install, the binaries in use will be copied
to the same name with ".orig" appended. For example "kulagent.orig".
When this occurs the agent is still running the previous version of code.
If Watchdog begins monitoring at this point, the Process Name in the
Agents' Runtime Status view will be shown as "kulagent.orig" instead
of "kulagent" and the Process ID will be "0".
Workaround: The agent with the ".orig" should be restarted so it will
be running the latest code. To correct the "<process name>.orig" in the
Agents' Runtime Status, you can do either of the following:
- Stop the OS agent, remove the $CANDLEHOME/config/CAP/pas.dat file
and restart the agent.
- Remove the CAP file for the agent temporarily. For example,
move $CANDLEHOME/config/CAP/kul_default.xml to kul_default.xml.bkp.
After a minute, Watchdog will dynamically remove management of the agent.
Once that occurs, copy the file back and Watchdog will discover the file
and the Process Name should be corrected.

Abstract: A second copy of kcawd process can get started after the
rearmWatchdog.sh script is run on UNIX or Linux.
Problem: If $CANDLEHOME resides on a symbolically linked or mounted
filesystem, if the script is run with the following format it can
result in a second copy of the kcawd process getting started.
$CANDLEHOME/bin/itmcmd execute ux rearmWatchdog.sh
Workaround: When running the rearmWatchdog.sh command, fully qualify the
path to the script. The setting for $CANDLEHOME should match the value
used to start the agent. For example:
$CANDLEHOME/bin/itmcmd execute ux $CANDLEHOME/<BIN_ARCH>/ux/bin/rearmWatchdog.sh

Abstract: Two kcawd processes displayed in Agent Management Services
workspace.
Problem: In the Agent Management Services workspace, the Watchdog
process (kcawd) is displayed twice, once with a correct value for
the Process ID and once with a Process ID of 0.
Workaround: Check the pas.dat file in the $CANDLEHOME/config/CAP
directory. If there are two entries for kcawd in the file,
then stop the OS Agent, delete the pas.dat file, and restart the agent.

8.0 Additional product information
==================================
This Interim Fix is being provided for the IBM
Tivoli Monitoring, Unix OS agent at Version 6.2.2.4
This Interim Fix is provided as a temporary solution until
the official maintenance release is made generally available.
When performing any code maintenance it is critical that you
validate that the APAR(s)from your IF are contained in
the maintenance package you are about to deploy to avoid
any code regressions.


9.0 Notices
===========
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Trademarks and Service Marks
----------------------------
IBM, the IBM logo, and ibm.com(R) are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (R or TM), these symbols
indicate U.S. registered or common law trademarks owned by IBM
at the time this information was published. Such trademarks may
also be registered or common law trademarks in other countries.
A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at
http://www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

Installation Instructions

Please refer to the 6.2.2.4-TIV-ITM_UNIX-IF0013.README contained in the Description section above for general installation instructions.

Download package

Fix Central

Fix Central is a new way to acquire fixes. In the future it will be the only option for downloading fixes, but for now we are including it as an additional download option. The two main differences from the current download options will be the FTP option will be replaced by HTTP and that you will need to use an IBM registered ID. The reason for this, is we can use Fix Central to notify you if there is a problem with the fix. Privacy is maintained.

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.2.4-TIV-ITM_UNIX-IF0013 22 Jan 2013 English 158817963 FC

Product Alias/Synonym

ITM UNIX agent

Problems (APARS) fixed
IZ96588 , IV21269 , IV32051

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Components
ITM Agent UNIX V6

Software version:

6.2.2.4

Operating system(s):

AIX, HP-UX, Solaris

Reference #:

4034230

Modified date:

2013-10-07

Translate my page

Machine Translation

Content navigation