IBM Tivoli Monitoring: Unix(R) OS Agent 6.2.2.3-TIV-ITM_UNIX-IF0004

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

rights reserved.

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

Component ID: 5724C040U

Fix: IF 0004 (6.2.2.3-TIV-ITM_UNIX-IF0004)

Date: 29 November 2011

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: IZ89532
Abstract: Watchdog not closing file descriptors in timeout conditions
Additional Information: When the watchdog utility which is part of the
OS agent issues a command to check the status of an agent, if
there is a timeout condition with the command, when the command
finishes the utility does not release the file descriptor. This
can result in the maximum number of open file descriptors being
exceeded for the process, which will cause the agent to not be
able to retrieve data properly. This can occur on either the Unix
or Linux OS agents.

APAR: IZ91032
Abstract: Minimize calls to cinfo from watchdog
Additional Information: The Watchdog component of the OS Agents for
Unix and Linux makes several calls to the "cinfo" command that
can be eliminated. In particular, Watchdog calls "cinfo -r"
regularly to determine if an agent process is running and calls
"cinfo -o" to determine the instances configured for an agent.
There are conditions where some of these calls can be eliminated.

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.

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)

APAR: IV02109
Abstract: "AGENT STARTED SUCCESSFULLY" MESSAGE WRITTEN UNNECESSARILY.
Additional Information: The message "Monitoring Agent for Linux OS Operational
Event: Agent started successfully" message sometimes is written to
KLZ:LG0 every two minutes. The message is written during the
availability checking for the agent when the agent is running and
can be ignored.

APAR: IV02818
Abstract: WATCHDOG DISPLAYS PID=0 FOR AGENT ON SOLARIS GLOBAL ZONE
WHEN CANDLEHOME LINKED OR MOUNTED.
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.

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


2.2 Defects
-----------
Defect: 154305
Abstract: Incorrect Watchdog version displayed in Agent's Management workspace.


can be ignored. It can occur on the UNIX or Linux OS agent.

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

2.4 Superseded fixes
--------------------
6.2.2.3-TIV-ITM_UNIX-LA0003
6.2.2.3-TIV-ITM_UNIX-IF0002
6.2.2.3-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.3-TIV-ITM_UNIX-LA0003
---------------------------
APAR: IZ89693
Abstract: PERFORMANCE PROBLEM IN COLLECTING SOLARIS ZONE INFO
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent
process takes a very long time to collect Solaris Zone info because
it runs prstat command for each zone and OS command takes about 30
seconds to collect info.

APAR: IZ90193
Abstract: AVOIDING UTF-8 CONVERTION FOR 7-BIT ASCII CODEPAGES
Additional Information: The Monitoring Agent for UNIX OS kuxagent process
can show a high CPU usage when it does UTF-8 conversions for
process attribute group.
In order to improve ITM OS Agent performance a new variable has
been added that will disable the conversion of the 7-bit ASCII
codepages to UTF-8.
In order to enable this behaviour set the following key in the ux.ini
file:
KUX_SKIP_UTF8CONV_PROCESS=TRUE
Default value is FALSE:
KUX_SKIP_UTF8CONV_PROCESS=FALSE

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 has been added in order to give 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 value is 100 milliseconds:
KUX_GETARGS_DELAY=100

APAR: IZ97074
Abstract: AGENT SEEMS TO HANG WITH PROCESS ATTRIBUTES GROUP
Additional Information: When using the Process attributes group
(UNIXPS table) in a portal client view or in a situation,
the agent seems to hang. Processing is continuing very slowly
and could complete after a long time (e.g. half an hour).
The stack for the kuxagent process shows a thread similar to:

26558: /Tivoli62/sol286/ux/bin/kuxagent
----------------- lwp# 1 / thread# 38 ----------------
ffffffff7b9a59a0 ioctl (15, 5401, ffffffff709fecbc)
ffffffff7b94922c isatty (15, 2, ffffffff709fee50, ffffff
0000000100123fdc __1cQfind_major_minor6FrknDstdMbasic_s
00000001001236dc __1cLtty_to_name6FrnMps_raw_table_kl2pc
000000010011dc80 __1cRsave_process_data6FpnIps_table_ii_
0000000100120964 __1cSget_entire_process6FpnIps_table__i
000000010012003c __1cMget_ps_table6FpnIps_table__i_ (100
0000000100053370 __1cSomunx_unixps_agentKTakeSample6M_v_

Showing that the agent is processing the isatty function,
and that this system function is taking excessive time to execute.

APAR: IV00112
Abstract: KUXAGENT PROCESS CAN CRASH ON SOLARIS
Additional Information: On Solaris 10 the Monitoring Agent
for UNIX OS kuxagent process can crash when
KUX_SKIP_UTF8CONV_PROCESS=true is set.

6.2.2.3-TIV-ITM_UNIX-IF0002
---------------------------
APAR: IZ92574
Abstract: ITM UNIX OS AGENT CAN HANG WHILE EXECUTING KDY RUNCOMMAND METHOD
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent
process can hang when it tries to execute deploy API runCommand,
in order to get values from eeprom OS command

APAR: IZ92800
Abstract: SELECTING DISK USAGE WORKSPACE CAUSES AGENT CRASH
Additional Information: After the 6.22.02.04-06 Unix OS agent (ux) agent
is installed and SetPerm is run, the agent crashes whenever the
Disk Usage workspace is selected in the TEP or when a situation
uses Unix Disk attribute group.

6.2.2.3-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IZ88737
Abstract: Runtime status data not cleared when process stops running.
Additional Information: In the Agent's Runtime Staus workspace, when the
watchdog utility is monitoring an agent, the workspace will show
various data about the process including "Total Size", "Number
of Threads", and "Parent Process ID" (Unix-only). If the agent
is determined not to be running, the status and Process ID
get reset. However, the other runtime values do not get reset
and continue to display the values that were last collected.
Once the agent is restarted the values get refreshed correctly.

APAR: IZ88088
Abstract: defunt processes using UNIX PING
Additional Information: On UNIX machines the Monitoring Agent for UNIX OS
kuxagent process generates a defunct process every time that it
executes a situation using UNIX PING attribute group.

APAR: IZ85924
Abstract: WATCHDOG CONTINUES TO RESTART OS AGENT
Additional Information: When the Agent Management Services watchdog utility
invokes the "cinfo -r" command to determine if an agent is running
and "cinfo" has a problem resolving the hostname, it can report
that the agent is not running when it is. This will result in the
watchdog utility restarting the agent each time it checks
availability.

APAR: IZ85281
Abstract: ERRORS IMPORTING DLA BOOK WITH BONDED INTERFACE CARDS
Additional Information: Channel, or ethernet bonding provides a method for
aggregating two or more network interfaces into a single logical-bonded
network interface. They can share the same ip address and MAC address
although the Interface name are different. When importing the output
of the tmsdla command into TADDM, in this configuration, the following
errors appear in the bulkload.log :

[main] ERROR bulk.CdbConfigniaClient - ObjectId unknown: FAILURE
classtype |unknown| not written to the database.
Attributes required for the naming rules of this object were not set.
Set attributes are:
Cannot identify failing object because of grouped write operations.
2010-09-03 16:03:24,713 [main] ERROR bulk.CdbRandomAccess - group write failure

followed by

2010-09-03 16:03:30,008 [main] ERROR bulk.CdbConfigniaClient -
External Relationship: monitors: FAILURE. The source of the relationship had no guid.
The source class type was |app.TMSAgent| objectid |x35tst02:LZ-TMSAgent|
The target class type was |sys.linux.Linux| objectid |128.147.33.87-OperatingSystem|
2010-09-03 16:03:30,008 [main] ERROR bulk.CdbRandomAccess - An external relationship:
monitors could not be written. Processing continuing.

APAR: IZ84910
Abstract: SCAN FILE NOT WORKING FOR FILE INFORMATION ATTRIBUTES GROUP
Additional Information: In a situation formula for the File Information attribute
group, with ( PATH=xxxx AND SCAN FILE=yyyy ), the Unix OS agent does not
return the list of files in PATH and the situation does not work.
On the contrary, the list is returned as expected if the predicates
are exchanged as in the following: (SCAN FILE=yyyy AND PATH=xxxx).

APAR: IZ84377
Abstract: Missing data in summary workspaces when ITM has more than 200 Agents.
Additional Information: When the ITM environment has some 200+ agents, the
following summary workspaces fail.
The exact number will vary depending on the size of the managed system names.
- "Linux Systems Overview",
- "Windows SYstems",
- "Enterprise UNIX Systems Summary"

The Portal Client displays this error message: KFWITM217E
Request error: SQL1_CreateRequest failed, rc=201 + SQL1_DistReqError


APAR: IZ84120
Abstract: CHILD 'KUXAGENT' OF UNIX OS AGENT HANGED UP IN STARTING UP
Additional Information: On AIX child 'kuxagent' of UNIX OS Agent hanged up in
starting up sequence. Parent 'kuxagent' was sending heartbeat to TEMS,
so TEMS recognized KUX as working fine. However, in fact, stat_daemon
and children were not started at that time.

APAR: IZ82944
Abstract: INCREASE THE OS AGENT LIMIT OF SUPPORTED DISKS
Additional Information: Agent is not able to monitor more than 1024 disks.

APAR: IZ81260
Abstract: STAT_DAEMON PROCESS DID NOT TERMINATE WHEN OS AGENT WAS STOPPED
Additional Information: After a restart on AIX the Monitoring Agent for UNIX OS
stat_daemon process did not stop when the OS Agent was stopped using
tha itmcmd command. When this problem happens the stat_daemon process
shows a high CPU usage, its PPID is 1.

Enhancement: Monitor File Systems of NFS type on UNIX
Abstract: The following environment variable is introduced to enable/disable NFS
monitoring at the agent side:
KBB_SHOW_NFS=true|false
with a default value "false" on Unix.
A timeout has been introduced, configurable through the KBB_NFS_TIMEOUT
environment variable (default is 2 seconds, allowed range 1-30 seconds).
A new attribute, named File System Status, has been added to the Unix Disk
group and it will report "Up" (normal case), "Down" (timeout expired)
or "Not Available" in error case.


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


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

- 6.2.2.3-TIV-ITM_UNIX-IF0004.README - This README file
- 6.2.2.3-TIV-ITM_UNIX-IF0004.tar - Fix archive .tar format
- 6.2.2.3-TIV-ITM_UNIX-IF0004.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.3-TIV-ITM_UNIX-IF0004/kux_tems_teps_tepd_if0004.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_tems_teps_tepd_if0004.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_aix523_tema_if0004.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_aix526_tema_if0004.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_hp11_tema_if0004.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_hp116_tema_if0004.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_hpi116_tema_if0004.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_sol283_tema_if0004.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_sol286_tema_if0004.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_sol293_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_sol296_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kux_sol606_tema_if0004.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.2.3-TIV-ITM_UNIX-IF0004/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.3-TIV-ITM_UNIX-IF0004.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.3-TIV-ITM_UNIX-IF0004, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.3-TIV-ITM_UNIX-IF0004/kux_xxxxxx_tema_if0004.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_if0004.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.22.03.00


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

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

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 062203004

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 062203004

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters ([xx]), not three characters ([kxx]).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5.4 Agent support update
------------------------
Fix 6.2.2.3-TIV-ITM_UNIX-IF0002 included changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or
Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.2.3-TIV-ITM_UNIX-IF0004.tar
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.

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

3. Expand the archive file (kux_tems_teps_tepd_if0004.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX systems or an extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.
GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

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

where <JAVAHOME> is the fully-qualified path (do not include bin
directory in JAVAHOME path) 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 Desktop Client (TEPD)

Continue through the remaining GUI panels selecting the product
06.22.03.04 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
Browser was running when the update was installed, it must be
restarted.

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

6.1 Installation instructions for agent baroc file
--------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the 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.03.04

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

2. To verify the agent support files were updated correctly, use the
kincinfo command on Windows systems or the cinfo command on Linux
or UNIX systems. The sample output below shows the versions of
the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, or Tivoli Enterprise Portal Desktop systems after this
fix has been successfully applied.

Note:
- The date of the build displayed might not be accurate. This is a
known problem.


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

./cinfo -i

*********** Mon Feb 09 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.22.03.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.
ux Monitoring Agent for UNIX OS
aix523 Version: 06.22.03.04
.
.
.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------
To validate that all components have been installed, run the
following command kincinfo -i and check UNIX OS Support Version.


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 03, 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
==================================
None.


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

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

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

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

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

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

Trademarks and Service Marks
----------------------------
IBM, the IBM logo, and ibm.com(R) are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (R or TM), these symbols
indicate U.S. registered or common law trademarks owned by IBM
at the time this information was published. Such trademarks may
also be registered or common law trademarks in other countries.
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.

Prerequisites

IBM Tivoli Monitoring, Version 6.2.2 Fix Pack 3.

URL LANGUAGE SIZE(Bytes)
6.2.2-TIV-ITM-FP0003 English 999999999

Installation Instructions

Please refer to the full README contained in the Download 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.3-TIV-ITM_UNIX-IF0004 30 Nov 2011 English 999999999 FC

Product Alias/Synonym

Unix OS Agent

Problems (APARS) fixed
IV00112, IZ81260, IZ82944, IZ84120, IZ84377, IZ84910, IZ85281, IZ85924, IZ88088, IZ88737, IZ89693, IZ90193, IZ92574, IZ92800, IZ96836, IZ97074, IZ89532, IZ91032, IZ96602, IZ99020, IV02109, IV02818, IV00749, IV00769, IV00799

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

Operating system(s):

AIX, HP-UX, Solaris

Reference #:

4031498

Modified date:

2013-10-25

Translate my page

Machine Translation

Content navigation