IBM Tivoli Monitoring: UNIX OS Agent 6.2.3.2-TIV-ITM_UNIX-IF0001

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the “Problems Fixed” section below

Download Description

Copyright International Business Machines Corporation 2012.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.2.3 Fix Pack 2

Component ID: 5724C040U

Interim Fix: IF 0001 (6.2.3.2-TIV-ITM_UNIX-IF0001)

Date: November 30, 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 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: IV25043
Abstract: "TOTAL CPU PERCENT" IS QUITE ALWAYS 0
Additional Information: The Monitoring Agent for UNIX OS
reports quite always 0 for "Total CPU Percent" due to a
bug in some internal calculations.

APAR: IV25235
Abstract: WRONG UNIXPS.COMMAND FOR SOME SHORT PROCESSES
Additional Information: The Monitoring Agent for UNIX OS reports
wrong information for some processes with short names for field
UNIXPS.Command. In fact agent returns the process command truncated
with '.../' for some short pathnames like ".../ksh" instead
of "/bin/ksh"

APAR: IV27109
Abstract: HUGE PAGE SCAN RATE AND PAGE RECLAIMS ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS
randomly reports wrong information for some UNIXMEM attributes
like Page Scan Rate and Page Reclaims due to an internal memory
corruption.

APAR: IV27994
Abstract: UNIX AGENT PROCESS FILTER LOGIC NEEDS ADDED DIAGNOSTIC TRACING
Additional Information: Diagnosing an issue with Process Filter (Unicode)
required debug version of kuxagent.
That tracing should be included in kuxagent code in all
platforms where process filter is implemented.

APAR: IV28538
Abstract: PERFORMANCE PROBLEM IN COLLECTING PROCESS INFORMATION
Additional Information: Sometimes it happens that UNIX OS kuxagent
process takes a very high CPU usage while collecting Process
information, this cab be due to "Terminal Device" collection.

In order to workaround this problem, skipping collection of this
info, an environmental variable has been introduced in ITM 6.2.2
FixPack 6 (KUX_SKIP_TTY); currently by default this behavior is
disabled, but it should be enabled by default.

2.2 Defects
-----------
Defect: 189242
Abstract: Network.MAC_Address on Solaris Intel 10 can be empty

Defect: 191277
Abstract: Machine_Information.System_Board_UUID on SunOS can be wrong
if serial number starts with 0

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

2.4 Superseded fixes
--------------------
None.

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
None.


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

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


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

- 6.2.3.2-TIV-ITM_UNIX-IF0001.README - This README file
- 6.2.3.2-TIV-ITM_UNIX-IF0001.tar - Fix archive .tar format
- 6.2.3.2-TIV-ITM_UNIX-IF0001.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.2.3.2-TIV-ITM_UNIX-IF0001/kux_aix523_tema_if0001.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_aix526_tema_if0001.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_hp11_tema_if0001.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_hp116_tema_if0001.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_hpi116_tema_if0001.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_sol283_tema_if0001.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_sol286_tema_if0001.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_sol293_tema_if0001.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_sol296_tema_if0001.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kux_sol606_tema_if0001.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.3.2-TIV-ITM_UNIX-IF0001/kuxhpi116.dsc - Descriptor file for HP-UX Itanium

Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.

5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

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

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.

- It is recommended to verify the "cinfo" commands are operating
correctly on the system prior to installing the patch. See
section "7.0 Known problems and workarounds" for the workaround
for the problem titled "Remote deploy of the patch fails"

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.2.3.2-TIV-ITM_UNIX-IF0001.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.2.3.2-TIV-ITM_UNIX-IF0001, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.2-TIV-ITM_UNIX-IF0001/kux_xxxxxx_tema_if0001.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_if0001.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.23.02.00


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

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

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 062302001

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 062302001

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.2.3.2-TIV-ITM_UNIX-IF0001) 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.23.02.01

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

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

*********** Mon Feb 11 03:01:19 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.23.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

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

ux Monitoring Agent for UNIX OS
aix523 Version: 06.23.02.01

.
.
.


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.

Prerequisites

IBM Tivoli Monitoring: Windows (R) Unix Agent 6.2.3 FP2

Installation Instructions

Please refer to the 6.2.3.2-TIV-ITM_UNIX-IF0001.README contained in the Description section above for general installation instructions.

Download package

Fix Central

Fix Central is a new way to acquire fixes. In the future it will be the only option for downloading fixes, but for now we are including it as an additional download option. The two main differences from the current download options will be the FTP option will be replaced by HTTP and that you will need to use an IBM registered ID. The reason for this, is we can use Fix Central to notify you if there is a problem with the fix. Privacy is maintained.

To download the files using Fix Central use the following link:

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.3.2-TIV-ITM_UNIX-IF0001 30 Nov 2012 English 1 FC

Problems (APARS) fixed
IV25043 IV25235 IV27109 IV27994 IV28538

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Components
ITM Agent UNIX V6

Software version:

6.2.3.2

Operating system(s):

AIX, HP-UX, Solaris

Reference #:

4033956

Modified date:

2012-11-30

Translate my page

Machine Translation

Content navigation