IBM Tivoli Monitoring: Linux(R) OS Agent 6.2.2.2-TIV-ITM_LINUX-IF0007

Downloadable files


Abstract

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.

Download Description

Copyright International Business Machines Corporation 2011.

All rights reserved.

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

Component ID: 5724C04LN

Interim Fix 0007, 6.2.2.2-TIV-ITM_LINUX-IF0007

Date: June 10, 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: 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.


2.2 Defects
-----------
Defect: 155983
Abstract: 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. It can occur on the UNIX or Linux OS agent.

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

2.4 Superseded fixes
--------------------
6.2.2.2-TIV-ITM_LINUX-IF0006
6.2.2.2-TIV-ITM_LINUX-IF0005
6.2.2.2-TIV-ITM_LINUX-IF0004
6.2.2.2-TIV-ITM_LINUX-IF0003
6.2.2.2-TIV-ITM_LINUX-IF0002 - not shipped
6.2.2.2-TIV-ITM_LINUX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.2-TIV-ITM_LINUX-IF0006
----------------------------
APAR: IZ85924
Abstract: Watchdog contiues 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: IZ88737
Abstract: Agents' runtime status data not cleared when process stops
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: 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 runnning and calls
"cinfo -o" to determine the instances configured for an agent.
There are conditions where some of these calls can be eliminated.


6.2.2.2-TIV-ITM_LINUX-IF0005
----------------------------
Enhancement: Monitor File Systems of NFS type on Linux
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 "True" on Linux.
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 Linux Disk
group and it will report "Up" (normal case), "Down" (timeout expired)
or "Not Available" in error case.
Note that Linux Agent was hanging when an NFS disk was mounted but
not accessible.

Enhancement: 7015 Add two new attributes to Linux VM Stats table
They are Total Memory Free and Net Memory Used, obtained as
Total Memory Free = Memory Free + Memory in Buffers + Memory Cached
Net Memory Used = Memory Used - Memory in Buffers - Memory Cached

6.2.2.2-TIV-ITM_LINUX-IF0004
----------------------------
APAR: IZ83651
Abstract: WRONG FORMAT FOR THE LINUX UPTIME ATTRIBUTE
Additional Information: The ITM Monitoring Agent for Linux
OS shows a wrong format for the uptime attribute.

APAR: IZ85241
Abstract: NEGATIVE VALUES FOR "BYTES RECEIVED /SEC" AND
"BYTES TRANSMITTED /SEC"
Additional Information: On Linux the Monitoring Agent for Linux
OS shows negative values for a couple of attributes in the
Network Attribute Group. This problem is due to an internal
overflow in data manipulation.

APAR: IZ86245
Abstract: WRONG OS INFORMATION IN LINUX WORKSPACE
Additional Information: On Red Hat Enterprise Linux Server
release 5.5 (Tikanga) the Monitoring Agent for Linux
OS reports wrong information in OS Vendor Information
field, because it contains the gcc version.

Defect: 135471
Abstract: wrong I/O values in EXTIO tables.

Defect: 136744
Abstract: agent crash on SLES 11 when KBB_RAS1=ALL is set as
trace level.

6.2.2.2-TIV-ITM_LINUX-IF0003
----------------------------
APAR: IZ76377
Abstract: WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
Additional Information: The Agent Management Services watchdog utility which
is part of the OS Agent used the "cinfo -R" command to get the
status of running agents. Most of these calls originate from
the common agent package (CAP) files, such as klz_default.xml.
The "cinfo -r" call is quicker and uses less resources than
"cinfo -R". It also can reduce the risk of the RunInfo file
getting out-of-sync which can cause multiple agents to be started.
The fix also changes the checkFrequency default to 120 seconds for
the OS Agents and watchdog process.

Please see Section 8.1 under 'Additional product information' for
more information regarding this APAR fix.

APAR: IZ78695
Abstract: MULTIPLE COPIES OF OS AGENTS RUNNING
Additional Information: There are multiple kuxagent or klzagent processes
running from a single $CANDLEHOME. There can also be multiple
copies of other agents running that are being monitored by the
Agent Management Services watchdog utility of the OS Agent.

Technote "Multiple copies of OS Agents running"
(http://www-01.ibm.com/support/docview.wss?uid=swg21445312) contains
the list of additional interim fixes related to this APAR as well as
updated CAP files for other IBM Tivoli Monitoring agents that can be
downloaded.

APAR: IZ78723
Abstract: "FILE READ FAILED" MESSAGES FILLING UP LOG
Additional Information: There are multiple "Error: file read failed" messages
in the OS Agent log file every 30 seconds which can fills up the log
file.

Defect: 119211
Abstract: Watchdog shows Process ID 0 after itmpatch of OS Agent
Additional Information: After installing an Interim Fix for the IBM Tivoli
Monitoring Agent for UNIX OS Agent or IBM Tivoli Monitoring Agent
for Linux OS Agent, the watchdog process is started with an extra
slash in the path name. This results in a Process ID of 0 being
displayed on the Agent Management Services workspace for the Proxy
Agent Services Watchdog process (kcawd).

6.2.2.2-TIV-ITM_LINUX-IF0001
---------------------------
APAR: IZ72224
Abstract: The Pattern Match (i.e. grep) and Ping Attribute groups incorrectly
take user input from the query/situation Filter and then pass the input
to popen(). A malicious user may craft a payload to do whatever they want
on the target system.

APAR: IZ74848
Abstract: Linux OS Agent takes hours to start and connect to TEMS
Additional Information: When starting the agent, it appears to start correctly,
however it can take several hours for the agent to actually
connect to the management server and display data.

APAR: IZ77964
Abstract: WRONG VALUE FOR "TRANSFERS PER SECOND" AND "BLOCKS WRITTEN/READ SECOND"
FOR THE LINUX AGENT
Additional Information: On multi-logical CPUs machine running Linux
with a 2.6 kernel, the ITM Linux OS Agent values for the attributes
"Transfers Per Second", "Block Written Per Second", and "Block
Reads Per Second" are erroneously calculated by a factor equal to the
number of logical CPUs.

APAR: IZ75298
Abstract: Add support of Process Group Leader ID attribute to the OS Agent for Linux.
Additional Information: In both Linux and Unix, process groups are used to manage
multiple related tasks. The Linux Process Group ID is used to identify
the leader of the process group. The customer needs to alert on the condition
when a process group leader is missing and the children are still running.

Enhancement: 125159
Abstract: REQ 1012 UNIX/Linux long process names support

Enhancement: 120683
Abstract: REQ 2765.1 TCP Statistics attribute group for Unix and Linux OS

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in Chapter 2 of
the IBM Tivoli Monitoring: Monitoring Agent for Linux OS 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
--------------------------------
The prerequisite level for this fix is as follows:

- IBM Tivoli Monitoring, version 6.2.2 Fix Pack 2

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.2-TIV-ITM_LINUX-IF0007.README - This README file
- 6.2.2.2-TIV-ITM_LINUX-IF0007.tar - Fix archive .tar format
- 6.2.2.2-TIV-ITM_LINUX-IF0007.zip - Fix archive .zip format

Note: The .tar and .zip files are identical in content. If you
are working in a UNIX(R), use the .tar file. If you are working
in a Windows(R) environment, you can use either the .tar or .zip
file.


The fix archive file contains the following files:
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_tems_teps_tepd_if0007.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_tems_teps_tepd_if0007.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_lpp266_tema_if0007.tar - Binaries for Linux on PowerPC®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_li6243_tema_if0007.tar - Binaries for Linux on Intel
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_li6263_tema_if0007.tar - Binaries for Linux (2.6 kernels) on Intel
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_ls3243_tema_if0007.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_ls3263_tema_if0007.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_ls3246_tema_if0007.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_ls3266_tema_if0007.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_lx8266_tema_if0007.tar - Binaries for Linux on AMD Opteron
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klz_lia266_tema_if0007.tar - Binaries for Linux on Itanium
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzlpp266.dsc - Descriptor file for Linux on Power
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzli6243.dsc - Descriptor file for Linux on Intel
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzli6263.dsc - Descriptor file for Linux on Intel
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzls3243.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzls3246.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzls3263.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzls3266.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzlx8266.dsc - Descriptor file for Linux on AMD/EM64T
- 6.2.2.2-TIV-ITM_LINUX-IF0007/klzlia266.dsc - Descriptor file for Linux on 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/Linux systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX/Linux systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
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 (6.2.2.2-TIV-ITM_LINUX-IF0007.tar
or .zip) 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. Note: On Windows systems, this path includes the drive
letter.

2. Expand the archive file using the "tar" command on UNIX/Linux 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 the operating
system of that agent. For more information on the "itmpatch"
command, see section 6.2.

On UNIX/Linux systems, if the fix was expanded to <TEMP>/6.2.2.2-TIV-ITM_LINUX-IF0007,
the install command would be:

> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.2-TIV-ITM_LINUX-IF0007/klz_xxxxxx_tema_if0007.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the <CANDLEHOME>/bin/cinfo -i" command.

In the following example, the file would be klz_li6263_tema_if0007.tar

> <CANDLEHOME>/bin/cinfo -i
lz Monitoring Agent for Linux OS
li6263 Version: 06.22.02.07


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

2. Expand the archive file using the "tar" command on UNIX/Linux 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/Linux
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.

On UNIX/Linux systems,
if the fix was expanded to <TEMP>/6.2.2.2-TIV-ITM_LINUX-IF0007:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.2-TIV-ITM_LINUX-IF0007

On a Windows system,
if the fix was expanded to <TEMP>\6.2.2.2-TIV-ITM_LINUX-IF0007:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.2-TIV-ITM_LINUX-IF0007

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

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX/Linux 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 lz
-n <Managed system name>
-v 062202007

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.

> %CANDLE_HOME%\bin\tacmd updateAgent -t lz
-n <Managed system name>
-v 062202007

Note:
- The component (-t) for the updateAgent command is specified as
two characters (lz), not three characters (klz).

- 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.2-TIV-ITM_LINUX-IF0005 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.2-TIV-ITM_LINUX-IF0007.tar
or .zip) to the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli
Enterprise Portal Servers or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the "tar" command on UNIX/Linux 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 (klz_tems_teps_tepd_if0007.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX/Linux 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/Linux systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

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

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0001:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".

On UNIX/Linux systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".

-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java(R) is installed. The
location of Java on your system might vary.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For the 6.2.2.2-TIV-ITM_LINUX-IF0007,
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 Monitoring
Agent for Linux OS 06.22.02.07 support to complete the installation.

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


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

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/Linux systems:
- 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 systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, 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 log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX/Linux 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 lz

On Windows systems, 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 lz

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

When the agent update is successful, the agent version is:
06.22.02.07.

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/Linux 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 displayed date of the build 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:

$CANDLEHOME/bin/cinfo -i


On Windows Systems:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

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


7.0 Known problems and workarounds
=========================
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
======================
8.1 IZ76377 - WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
--------------------------------------------------------------
The fix for this APAR makes changes to the common agent package (CAP)
file, such as $CANDLEHOME/config/CAP/klz_default.xml, which is used by
the Agent Management Services watchdog utility. In the
<availabilityStatusScript> section of this file, instead of specifying the
command "cinfo -R" it now specifies either "agentInstanceCommand.sh" or
"cinfo -r" depending on the agent.

It is recommended to not use a CAP file that still contains "cinfo -R".

If you have copied the original CAP file in $CANDLEHOME/config/CAP, such as
<pc>_default.xml file to <pc>.xml to customize settings, it is recommended
to make a copy of the latest version of this file delivered as part of this
fix and make your customizations on the newly copied file.

The Agent Builder version 6.2.2.2 Interim Fix 01
(6.2.2.2.-TIV-ITM_ABLDR-IF0001) was updated to no longer specify "cinfo -R"
in the CAP files for single instance agents. Multi-instance agents created
by the Agent Builder did not previously specify "cinfo -R". If your agent
is a single instance agent and you will be using watchdog to monitor the
agent, it is recommended to use this version or later of the Agent Builder
to generate your agent.

Technote "Multiple copies of OS Agents running"
(http://www-01.ibm.com/support/docview.wss?uid=swg21445312) contains the list
additional interim fixes related to this APAR as well as updated CAP files
for other IBM Tivoli Monitoring agents that can be downloaded.

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 are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
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

The prerequisite level for this fix is as follows:

- IBM Tivoli Monitoring, version 6.2.2 Fix Pack 2 (6.2.2-TIV-ITM-FP0002)

URL LANGUAGE SIZE(Bytes)
6.2.2-TIV-ITM-FP0002 English 999999

Installation Instructions

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 package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.2.2-TIV-ITM_LINUX-IF0007 10 Jun 2011 English 999999999 FC

Product Alias/Synonym

ITM Linux Agent

Problems (APARS) fixed
IZ72224, IZ74848, IZ75298, IZ76377, IZ77964, IZ78695, IZ78723, IZ83651, IZ85241, IZ86245, IZ85924, IZ88737, IZ89532, IZ91032, IV00749, IV00769, IV00799

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Components
ITM Agent Linux V6

Software version:

6.2.2.2

Operating system(s):

Linux

Reference #:

4030231

Modified date:

2013-05-13

Translate my page

Machine Translation

Content navigation