IBM Tivoli Monitoring: Linux(R) OS Agent 6.2.2.4-TIV-ITM_LINUX-IF0005

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 0005, 6.2.2.4-TIV-ITM_LINUX-IF0005

Date: 30 April 2012

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: IV07267
Abstract: FALSE ALERTS FOR LINUX NETWORK COLLISIONS PER MINUTE
Additional Information: The Monitoring Agent for Linux OS reports
for various interfaces "Collisions per minute" > 0 but the
below systems commands at the same time show all collisions
equal zero.

2.2 Defects
-------------

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

2.4 Superseded fixes
--------------------
6.2.2.4-TIV-ITM_LINUX-IF0004
6.2.2.4-TIV-ITM_LINUX-IF0003
6.2.2.4-TIV-ITM_LINUX-IF0002
6.2.2.4-TIV-ITM_LINUX-IF0001


2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.4-TIV-ITM_LINUX-IF0004
----------------------------
APAR: IV04679
Abstract: LINUX OS AGENT DON'T DETECT FILE CHANGE AFTER 2ND CHANGE
Additional Information: Linux OS Agent don't register the hash sum
of the changed file so that the comparison is done ever
with the first change's hash sum.

APAR: IV06844
Abstract: TAKE ACTION NOT EXECUTED WITH KLZ FILEINFO ATTRIBUTE
Additional Information: Monitoring Agent for Linux OS doesn't
execute the TakeAction related to FILEINFO attribute group
when there are multiple situations that monitor the same file.

6.2.2.4-TIV-ITM_LINUX-IF0003
----------------------------
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_LINUX-IF0002
----------------------------
APAR: IV003687
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_LINUX-IF0001
---------------------------
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 causes 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.

APAR: IV02109
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 Linux or UNIX OS agent.

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


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 4

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.4-TIV-ITM_LINUX-IF0005.README - This README file
- 6.2.2.4-TIV-ITM_LINUX-IF0005.tar - Fix archive .tar format
- 6.2.2.4-TIV-ITM_LINUX-IF0005.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.4-TIV-ITM_LINUX-IF0005/klz_lpp266_tema_if0005.tar - Binaries for Linux on PowerPC®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_li6243_tema_if0005.tar - Binaries for Linux on Intel
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_li6263_tema_if0005.tar - Binaries for Linux (2.6 kernels) on Intel
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_ls3243_tema_if0005.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_ls3263_tema_if0005.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_ls3246_tema_if0005.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_ls3266_tema_if0005.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_lx8266_tema_if0005.tar - Binaries for Linux on AMD Opteron
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klz_lia266_tema_if0005.tar - Binaries for Linux on Itanium
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzlpp266.dsc - Descriptor file for Linux on Power
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzli6243.dsc - Descriptor file for Linux on Intel
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzli6263.dsc - Descriptor file for Linux on Intel
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzls3243.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzls3246.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzls3263.dsc - Descriptor file for 32-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzls3266.dsc - Descriptor file for 64-bit Linux on zSeries®
- 6.2.2.4-TIV-ITM_LINUX-IF0005/klzlx8266.dsc - Descriptor file for Linux on AMD/EM64T
- 6.2.2.4-TIV-ITM_LINUX-IF0005/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.4-TIV-ITM_LINUX-IF0005.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.4-TIV-ITM_LINUX-IF0005,
the install command would be:

> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.4-TIV-ITM_LINUX-IF0005/klz_xxxxxx_tema_if0005.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_if0005.tar

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


5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.2.4-TIV-ITM_LINUX-IF0005.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.4-TIV-ITM_LINUX-IF0005:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.4-TIV-ITM_LINUX-IF0005

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

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 062204005

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 062204005

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
------------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superceded fixes. No additional installation steps are required.


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


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
======================
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 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