IBM Tivoli Monitoring: Unix(R) OS Agent 6.2.1.2-TIV-ITM_UNIX-IF0002

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

Component ID: 5724C040U

Fix: Interim Fix 0002 (6.2.1.2-TIV-ITM_UNIX-IF0002)

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

2.2 Defects
-----------
Defect: 141438
Abstract: No data return from UX agent File Information table.

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

2.4 Superseded fixes
--------------------
6.2.1.2-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.1.2-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IZ62255
Abstract: WRONG VALUE FOR THE STATUS ATTRIBUTE OF THE SOLARIS ZONE
ATTRIBUTE GROUP
Additional Information: The Status attribute of the Solaris Zone attribute
group shows a wrong status (e.g. it shows the status of "shutting
down" instead of the actual status of "running" reported by the OS
command "zoneadm -list -cv"). The problem is due to the fact that
Solaris has broken the backward compatibility for the zone_status_t
enum in the /usr/include/sys/zone.h header file in Solaris 10
Update 7: 139555-08 (sparc) and 139556-08 (x86).

APAR: IZ63160
Abstract: THE ITM 6.2.1 TEP DOESN'T ALLOW USER TO CREATE SITUATIONS FOR
CPU UTILIZATION WITH VALUES GREATER THAN 100
Additional Information: It is not possible to create a situation with a value
"Process Cpu Utilization" (UNIXPS.CPU) greater than 100. If you try
to do it, TEP highlights the value in red as it considers it invalid.

APAR: IZ68560
Abstract: ITM AGENT TAKES A VERY LONG TIME IN ORDER TO COLLECT SOLARIS
ZONES INFORMATION
Additional Information: On Solaris the Monitoring Agent for UNIX OS
kuxagent process takes a very long time to collect physical
and virtual memory information about Local Zones from the
Global Zone.
It is possible to disable this new behavior setting the
following parameter in the ux.ini file to TRUE:
KUX_PRSTAT_OFF=TRUE

APAR: IZ78243
Abstract: UNIX OS AGENT CRASHES ON SOLARIS WHILE IT IS COLLECTING
SOLARIS ZONES INFORMATION
Additional Information: Unix OS agent running as non-root can crash on Solaris while
it is collecting Solaris Zones information when it fails to access a file
in /proc filesystem.

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 and
its stacktrace is like the following one:

pthread_yield
pthread_yield() at 0x9000000008af33c
exit(??) at 0x900000000043814
handle_SigHandler(SignalNumber = 15), line 191 in "stat_daemon.cpp"
killpg(??, ??) at 0x90000000020af34
stop_exit(), line 309 in "stat_daemon.cpp"
exit(??) at 0x900000000043634
reply_data_request(int)(sock = 13), line 448 in "stat_daemon.cpp"
process_data(int)(sock = 13), line 420 in "stat_daemon.cpp"
main(argc = 2, argv = 0x0fffffffffffee20), line 285 in "stat_daemon.cpp"


APAR: IZ82944
Abstract: INCREASE THE OS AGENT LIMIT OF SUPPORTED DISKS
Additional Information: Monitoring Agent for Unix OS was able to monitor just
1024 disks on AIX, this limit has been increased to 4096 disks.
When the old limiti is reached this message appears in the stat_daemon
log file:
4C45EC82.01AD-1:disk_stat.cpp,1423,"is_duplicated_iostat_entry")
Error: Maximum number of disks entries exceeded!

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


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

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.1 Fix Pack 2.


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

- 6.2.1.2-TIV-ITM_UNIX-IF0002.README - This README file
- 6.2.1.2-TIV-ITM_UNIX-IF0002.tar - Fix archive .tar format
- 6.2.1.2-TIV-ITM_UNIX-IF0002.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.1.2-TIV-ITM_UNIX-IF0002/kux_aix523_tema_if0002.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_aix526_tema_if0002.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_hp11_tema_if0002.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_hp116_tema_if0002.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_hpi116_tema_if0002.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_sol283_tema_if0002.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_sol286_tema_if0002.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_sol293_tema_if0002.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_sol296_tema_if0002.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_sol606_tema_if0002.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_tems_teps_tepd_if0002.tar - Support files for IBM Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Servers and Tivoli Enterprise Desktop Client
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kux_tems_teps_tepd_if0002.zip - Support files for IBM Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Servers and Tivoli Enterprise Desktop Client
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.1.2-TIV-ITM_UNIX-IF0002/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

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.2.1.2-TIV-ITM_UNIX-IF0002.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. This creates a directory
structure that contains fixes for all of the supported platforms.

3. Use the itmpatch command to install the fix for that agent platform.
For more information on the itmpatch command, see section 6.2

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.1.2-TIV-ITM_UNIX-IF0002/kux_xxxxxx_tema_if0002.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_if0002.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.21.02.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.1.2-TIV-ITM_UNIX-IF0002.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 unzip utility on Windows systems. This 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.1.2-TIV-ITM_UNIX-IF0002
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.1.2-TIV-ITM_UNIX-IF0002

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

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 login to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information on the tacmd
login and updateAgent commands, see the IBM Tivoli 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 062102002

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 062102002

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

5.4 Agent support update
------------------------
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 (on UNIX systems
6.2.1.2-TIV-ITM_UNIX-IF0002.tar and on Windows systems
6.2.1.2-TIV-ITM_UNIX-IF0002.zip) to the IBM Tivoli Enterprise Monitoring
Servers, IBM Tivoli Enterprise Portal Servers and Tivoli Enterprise
Portal Desktop.

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 (e.g
6.2.1.2-TIV-ITM_UNIX-IF0002\kux_tems_teps_tepd_if0002.tar on UNIX
systems or 6.2.1.2-TIV-ITM_UNIX-IF0002\kux_tems_teps_tepd_if0002.zip
on Windows systems) 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 unzip utility on Windows systems. This creates a
directory structure that includes a subdirectory called CD-ROM,
with the necessary updates.

4. Use the Application Support Installer(ASI) GUI to install
the application support files.
GUI installation Method
-----------------------
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.21.02.02 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 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 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.21.02.02

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

./cinfo -i

This command offers you four options on the CINFO menu shown in
the example that follows. Choose the option that meets your needs.

*********** Sun Oct 10 21:09:03 EDT 2010 *****************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.21.02.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************

-- CINFO Menu --
1) Show products installed in this CandleHome
2) Show which products are currently running
3) Show configuration settings
4) Show installed CD release versions
X) Exit CINFO
1

*********** Sun Oct 10 21:09:03 EDT 2010 *****************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.21.02.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.21.02.02

.
.
.

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.

3. To verify locally that the agent has been correctly installed
check the output "cinfo -i" command:

For example:
On UNIX systems, To validate that Unix OS has been upgraded,
run the following command and verify agent version:
./cinfo -i

*********** Wed Oct 5 17:33:35 PAKST 2011 ******************
User: root Groups: system bin sys security cron audit lp
Host name : itmaix1 Installer Lvl:06.21.02.00
CandleHome: /621FP2_UX_IF2_remote
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix526 Version: 06.21.02.02

.
.
.

7.0 Known problems and workarounds
==================================
None.



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
------------------------------------
{Be sure to include the IBM trademark statement that is included here.}

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.

{Add or remove non-IBM trademark names as appropriate. Mark the first
occurrence of IBM and special non-IBM trademark names with a '(R)'.
See http://www.ibm.com/legal/copytrade.shtml for a complete list of
non-IBM trademark names.}

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.