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

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.3.0 Fix Pack 1

Component ID: 5724C040U

Interim Fix 0002 (6.3.0.1-TIV-ITM_UNIX-IF0002)

Date: February 26, 2014

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 Copyright and trademark information
10.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: IV55187
Abstract: The UNIX OS Agent reports incorrect aggregate CPU attributes when running on HP-UX or Solaris.
Additional Information: The UNIX OS Agent reports incorrect aggregate CPU attributes when running on
HP-UX or Solaris. On the HP-UX and Solaris platforms the User CPU (Percent), System CPU (Percent),
Idle CPU (Percent), Wait I/O (Percent) and CPU Busy (Percent) attributes of the 'aggregate' CPU in
the SMP CPU attribute group are calculated as simple averages across individual CPUs' contributions.
In doing this the agent does not take into account that some CPUs could be disabled and should be
excluded not to bias the final average.

APAR: IV51670
Abstract: Incorrect values for averages on AIX aggregate CPU attributes
Additional Information: The UNIX OS agent running on AIX incorrectly calculates the averages for
aggregate CPU utilization over the last 1,5,15 and 60 minutes. These are reported by the following
attributes in the SMP_CPU group: Avg_CPU_Busy_1, Avg_CPU_Busy_5, Avg_CPU_Busy_15, Avg_CPU_Busy_60,
Avg_CPU_Sys_1, Avg_CPU_Sys_5, Avg_CPU_Sys_15, Avg_CPU_Sys_60, Avg_CPU_Usr_1, Avg_CPU_Usr_5,
Avg_CPU_Usr_15 and Avg_CPU_Usr_60. These values do not match the output of system commands like
mpstat or vmstat because they are not the mean value across individual CPUs contributions.

APAR: IV54057
Abstract: UNIX OS Agent on Solaris may crash while monitoring processes
Additional Information: In a highly dynamic environment with hundreds of running processes frequently
going down and up, the UNIX OS agent may fail to read one of the files in the /proc file system
reporting metrics for the specified process ID (PID), because that PID no longer exists. This
condition is not correctly handled and may lead to a crash because of memory left uninitialized.

APAR: IV32093
Abstract: SITUATIONS WITH UNIX PRINT QUEUE.PRINT QUEUE NAME DO NOT WORK.
Additional Information: n AIX Unix_Print_Queue.Print_Queue_Name seems to be padded with blanks, that
generates problems while evaluating situations that use this column.

APAR: IV43092
Abstract: ENTITLEMENT USED PCT ATTRIBUTE DOES NOT MATCH THE AIX PREMIUM AGENT
Additional Information: In the UNIX OS Agent System Information/AIX LPAR Information workspace, the
Entitlement Used Pct attribute of the LPAR Utilization view does not match the same attribute in
the AIX Premium agent. The problem occurs when the CPU Summary attribute group is being collected
multiple times per minute, and this causes the collection interval to be much shorter than the
interval defined for the Logical Partition attribute group. Collection over different intervals
can cause different values.

APAR: IV46733
Abstract: Unix OS Agent incorrectly calculates the used space on zfs on Solaris 10
Additional Information: Unix OS Agent incorrectly calculates the used space on zfs on Solaris 10 for
the valued quota variable.

APAR: IV51151
Abstract: DISK ATTRIBUTES ARE INCORRECT FOR ZFS FILESYSTEMS
Additional Information: The Unix OS agent doesn't read the correct size of the zfs dataset when its
quota or refquota are set up

APAR: IV53503
Abstract: UNIX OS Agent may send false alerts on missing processes
Additional Information: Due to an incorrect variable initialization, the UNIX OS agent may incorrectly
assign the collected metrics for running processes. When this occurs the situation evaluation code
receives garbage in the processes data rows and this can make the situation fire if it is based on
a MISSING clause condition. Symptom of this issue is the following log entry, available also at
ERROR default RAS1 setting:
(Fri Nov 29 09:35:15 2013.3659-16:get_ps_table.cpp,650,"get_ps_table") unknown process report type, default to all process data type
(Fri Nov 29 09:35:15 2013.365A-16:get_ps_table.cpp,658,"get_ps_table") Exit: 0x0


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

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

2.4 Superseded fixes
--------------------
6.3.0.1-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.3.0.1-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IV47625
Abstract: Wrong calculation of aggregate CPU in shared LPARs for the UNIX OS agent
Additional Information: Values reported for User CPU (Percent), System CPU (Percent),
Idle CPU (Percent) and Wait I/O (Percent) of the aggregate CPU (CPU ID=-1) in
the SMP_CPU group are incorrect when the UNIX OS agent runs in a shared LPAR.
Starting in version 6.3.0, these values are averages over a time interval that
must be in sync with the sampling interval of the running situation or historical
data collection. However, a bad isolation of the raw data taken by multiple
situations in a shared LPAR environment actually returns averages computed on
random time intervals.

APAR: IV36900
Abstract: PERFORMANCE PROBLEM IN COLLECTING PROCESS ARGUMENTS ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent
process can generate high cpu usage when it collect processes arguments.
This issue can occur when there are processes that have a huge as file
in their proc folder (proc/PID/as). In order to solve this issue ITM code
has been changed in order to use Solaris APIs to collect processes arguments
instead of directly read /proc filesystem.
In order to restore the old behaviour set the following key in the ux.ini
file and reastart the Unix OS Agent (default is TRUE):
KUX_PARGS_API=FALSE

APAR: IV37297
Abstract: UNIX OS AGENT STAT_DAEMON PROCESS HANGS WHILE RECEIVING NETWORK INFO ON AIX
Additional Information: in case of failures of perfstat_netinterface API it can
happen that ifstat process doesn't send expected data to stat_daemon process
and it remains in waiting status for that data.
Below an example of stat_daemon last traces when this problem happens:
(Wed Feb 20 17:10:45 2013.0022-1:stat_daemon_ifstat.cpp,739,"refresh_ifstat_buffer") Active RAS1 Classes: EVERYT EVERYE EVERYU
(Wed Feb 20 17:10:45 2013.0023-1:stat_daemon_ifstat.cpp,739,"refresh_ifstat_buffer") Entry
(Wed Feb 20 17:10:45 2013.0024-1:stat_daemon_ifstat.cpp,741,"refresh_ifstat_buffer") ifstat_fd is 6
(Wed Feb 20 17:10:45 2013.0025-1:stat_daemon_ifstat.cpp,742,"refresh_ifstat_buffer") if_count is 0
(Wed Feb 20 17:10:45 2013.0026-1:stat_daemon_ifstat.cpp,743,"refresh_ifstat_buffer") size if_count is 4

APAR: IV43912
Abstract: PROCESSES THAT EXCEED 4096 BYTES FOR THE COMMAND STRING ARE NOT FILTERED CORRECTLY
Additional Information: The UNIX OS agent Process Filter feature allows you to apply regular
expressions for selecting the relevant portion of a long process command line. This is so
that it can fit into the "Process Command (Unicode)" attribute which is 768 characters
long and cannot be further expanded due to architectural limitations. However, this
feature is currently based on an internal 4096 byte long buffer, so applying the filter
does not work for processes whose command line is longer than 4096 characters.
Inconsistent results in the "Process Command (Unicode)" attribute may occur in such a 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.3.0, Fix Pack 1.

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html


3.1 Prerequisites for this fix
------------------------------
- IBM Tivoli Monitoring, Version 6.3.0 Fix Pack 1.


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

- 6.3.0.1-TIV-ITM_UNIX-IF0002.README - This README file
- 6.3.0.1-TIV-ITM_UNIX-IF0002.tar - Fix archive .tar format
- 6.3.0.1-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(R) environment; use the .zip file if
you are working in a Microsoft Windows(R) environment.

The fix archive file contains the following :
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_aix523_tema_if0002.tar - UNIX Agent binaries for AIX 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_aix526_tema_if0002.tar - UNIX Agent binaries for AIX 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_hp11_tema_if0002.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_hp116_tema_if0002.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_hpi116_tema_if0002.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_sol283_tema_if0002.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_sol286_tema_if0002.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_sol293_tema_if0002.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_sol296_tema_if0002.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kux_sol606_tema_if0002.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.3.0.1-TIV-ITM_UNIX-IF0002/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.3.0.1-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

- 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.3.0.1-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 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.2

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

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.0.1-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.30.01.00


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.1-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 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 Command Reference Guide.

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

On a Windows system,
if the fix was expanded to <TEMP>\6.3.0.1-TIV-ITM_UNIX-IF0002
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.0.1-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 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 updateAgent commands, see the IBM Tivoli Command Reference 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 063001002

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 063001002

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

5.4 Agent support update
------------------------
This fix (6.3.0.1-TIV-ITM_UNIX-IF0002) doesn't include changes to
the agent support files.

6.0 Additional installation information
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

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

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


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

./cinfo -i

*********** Mon Feb 11 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.30.01.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.30.01.02

.
.
.


7.0 Known problems and workarounds
==================================
It can happen that installation of this Interim Fix can fail when
there are a lot of defunct processes on the system related to kuxagent
process. When this issue occurs please stop situations related to
"Ping" attribute group, recycle the agent and them apply again the IF.


8.0 Additional product information
==================================
None.


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.



10.0 Notices
=======
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 jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

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

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.