IBM Tivoli Monitoring: UNIX OS Agent 6.2.3.1-TIV-ITM_UNIX-IF0004

Download Description

Copyright International Business Machines Corporation 2013.
All rights reserved.

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

Component ID: 5724C040U

Interim Fix 0004 (6.2.3.1-TIV-ITM_UNIX-IF0004)

Date: May 13, 2013

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: IV36767
Abstract: NFS_STAT PROCESS CRASHES ON SOLARIS
Additional Information: On Solaris Operating Systems, the Monitoring Agent for UNIX OS nfs_stat process can
crash generating the following stacktrace:
---------------------
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:stacktrace_handler+0x58
/lib/sparcv9/libc.so.1:0xd8684
/lib/sparcv9/libc.so.1:0xcc1f8
/lib/sparcv9/libc.so.1:0xcc404
/lib/sparcv9/libc.so.1:strlen+0x50 [ Signal 11 (SEGV)]
/sys_apps_01/tivoli/ITM/agent/tmaitm6/sol286/lib/libkbb.so:RAS1_Format+0x3c
/sys_apps_01/tivoli/ITM/agent/tmaitm6/sol286/lib/libkbb.so:RAS1_Printf+0x2c
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:main+0x360
/sys_apps_01/tivoli/ITM/agent/sol296/ux/bin/nfs_stat:_start+0x17c
Fatal Error (11) Detected. Exiting
----------------------

APAR: IV11756
Abstract: UNIX OS AGENT REPORTS WRONG CPU INFO AFTER CPUS ARE DYNAMICALLY ADDED / REMOVED IN A ZONE POOL
Additional Information: On Solaris, the Monitoring Agent for UNIX OS installed in a Local Zone takes a
snapshot of which CPUs are handling the zone when it starts, but if CPUs are dynamically added or
removed from the zone pool the agent is not able to detect them and reports incorrect information
related to IDs, status and metrics

APAR: IV12744
Abstract: THE UNIXOS AGENT IS REPORTING ZERO FOR THE NUMBER OF SYSTEM PROCESSES RUNNING
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent process reports 0 for the number
of system processes running on the machine (Number of System Procs column from System attribute group).

APAR: IV13211
Abstract: SYSTEM BOARD UUID WRONG VALUE ON AIX
Additional Information: On AIX the Monitoring Agent for UNIX OS can collect a wrong "System Board UUID"
(respect to one provided by "uname -f" command), due to a bug in an internal conversion utility.

APAR: IV14938
Abstract: KUX_VMSTAT PROCESS TAKES A REALLY HUGE TIME TO INITIALIZE
Additional Information: On Solaris the Monitoring Agent for UNIX OS kux_vmstat process can take a very long time
to initialize on machines with a huge naumber of CPUs, so the agents keeps running but take a very long time
before data is seen on TEP.

APAR: IV15776
Abstract: NEGATIVE VALUES FOR NFS DISKS ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS can collect negative values for performance
information when it detects a new NFS disk for the first time. This issue seems to be due to a bug/strange
behavior in Solaris kstat API.

APAR: IV20671
Abstract: CORE FILE GENERATED WHEN AGENT STOPPED
Additional Information: When the Watchdog code which is part of the OS agent is stopped, it writes a message to the
RAS1 log indicating that a signal was captured, the signal number, and the signal name. When it writes this mesage,
it calls a basic services routine to convert the signal number to a name, which resulted in a core file being
generated. Since this occurred on agent shutdown, there is no operational problem resulting from the core file.

APAR: IV23485
Abstract: SYSTEM CALLS ATTRIBUTE IN SMP_CPU IS NOT A RATE PER SECOND AS DESCRIBED IN THE USER'S GUIDE
Additional Information: On Solaris the Monitoring Agent for UNIX OS reports wrong number of SystemCalls because it is
not a rate per second as described in the User's Guide, but it reports the number of SystemCalls in last 30 seconds.

APAR: IV27109
Abstract: HUGE PAGE SCAN RATE AND PAGE RECLAIMS ON SOLARI
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: IV28199
Abstract: UNIX OS AGENT OPENS AND CLOSES REPEATEDLY A SITUATION WITH FILE PATH, NAME AND LAST UPDATED
Additional Information: The Last Changed Time doesn't work in the FileInfo attribute group with the function
"Compare Time to a Time +/- delta"

APAR: IV31251
Abstract: DATA NOT COLLECTED FOR WPAR
Additional Information: No data is displayed for any of the AIX WPAR workspaces. The problem occurs when a WPAR has
multiple IP addresses. The following message appears in the aixdp_daemon log files:
(Thu Sep 20 01:08:28 2012.0015-1:aixtranslator.c,2757,"ux_CollectData") Data collection failed for attribute group 29:WPAR_Information
(Thu Sep 20 01:08:28 2012.0016-1:aixtranslator.c,2758,"ux_CollectData") Exit: 0x0
(Thu Sep 20 01:08:28 2012.0017-1:aixdp_daemon.cpp,2148,"reply_wpar_information_request") Data collection failure

APAR: IV32051
Abstract: MISSING CIFS FILE SYSTEMS
Additional Information: On AIX the Monitoring Agent for UNIX OS is not able to monitor CIFS file systems when KBB_SHOW_NFS=TRUE is set

APAR: IV35898
Abstract: HIGH CPU IN UNIX AGENT ON SOLARIS IN THE MOUNT_STAT PROCESS
Additional Information: ITM Unix OS Agent on Solaris local zones can experiment high cpu in mount_stat process due to an
hang while collecting mountPointSpecial value for ZFS filesystems.

APAR: IV36516
Abstract: MOUNT_STAT CAN CRASH ON SOLARIS INTEL GLOBAL ZONE
Additional Information: On Solaris the Monitoring Agent for UNIX OS mount_stat process can crash. statvfs64 API gets a
permission denied error:
(51149395.01A7-C:mount_stat.cpp,192,"exec_statvfs64") WARNING: statvfs64 failed for "/ams/ams/database/apc-4.0.10_9.0.10-108719/NI"
with errno 13 (Permission denied)


2.2 Defects
-----------
defect: 203977
Abstract: abnormal value for attribute "RPC Client Bad Xid Replies Limit percentage"


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

2.4 Superseded fixes
--------------------
6.2.3.1-TIV-ITM_UNIX-IF0003
6.2.3.1-TIV-ITM_UNIX-IF0002
6.2.3.1-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.3.1-TIV-ITM_UNIX-IF0003
---------------------------
APAR: IV27612
Abstract: ITM UNIX OS AGENT CRASHES WHEN ACCESSING WPAR WORKSPACE
Additional Information: When accessing the 6.2.3 FP1 Monitoring Agent
for UNIX OS workspace "AIX WPAR Summary" under "UNIX OS" -> "System
Information" on AIX 7.1 server, the UNIX agent becomes
unavailable.

APAR: IV31937
Abstract: DATA PROVIDER CORES ON ODM ERROR
Additional Information: This is a sysroute of APAR IV29791.
In the UNIX OS Agent 6.2.3 FP1, the agent might crash with the
following lines in the log file:

(5069DDA4.011B-1:dkstats.c,1787,"get_cu_adptr") Error in get_cu_adptr():
odm_get_list(): CFG_ODM_ACCESS.
(5069DDA4.011C-1:dkstats.c,1788,"get_cu_adptr") Error : CFG_ODM_ACCESS.
(5069DDA4.011D-1:stacktrace.cpp,101,"exit_with_notification") FATAL
ERROR: Fatal error (11) detected. Shutdown initiated.

APAR: IV32308
Abstract: PERFORMANCE PROBLEM IN COLLECTING PROCESS INFORMATION ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS kuxagent
process can take a very long time to collect process information due to
internal delays in pargs command.

6.2.3.1-TIV-ITM_UNIX-IF0002
---------------------------
APAR: IV18116
Abstract: UNIX OS AGENT FAILS TO RUN AFTER UPDATE TO 6.2.3 FP1 ON AIX
Additional Information: On AIX the Monitoring Agent for UNIX OS fails to
start and the following message is present in the log file:

In UX agent .log file:
**** UNIX OS Agent process aixdp_daemon terminated: <date/timestamp>
Fatal Error (1) Detected. Exiting

In <hostname>_ux_aixdp_daemon_<timestamp>-01.log

aixtranslator.c,2705,"ux_InitializeCollectors") SpmiInit error:
Spmi: Unable to malloc
aixdp_daemon.cpp,200,"main") FATAL error, Initialization failure
aixdp_daemon.cpp,228,"stop_exit")
**** UNIX OS Agent aixdp_daemon terminated ****

APAR: IV19543
Abstract: UNIX AGENT ON SOLARIS DOESN'T COLLECT INFO FOR SAMFS FILE SYSTEMS
Additional Information: On Solaris the Monitoring Agent for UNIX OS doesn't
collect
information for samfs File Systems and the following message appears in the log file:

(4F86BFE4.01D4-F:disk_space.cpp,1329,"GetHostData") Ignoring mount point: /archive; fstype: samfs.

APAR: IV21269
Abstract: WRONG INFORMATION FOR ZFS FILESYSTEMS
Additional Information: On Solaris the Monitoring Agent for UNIX OS reports wrong
information for ZFS filesystems, this is due to the fact that it
uses standard statfs API to collect metrics instead of dedicated
Oracle Solaris ZFS library.

APAR: IV21418
Abstract: UNIX OS AGENT HANGS WITH A HOURGLASS ON AIX 7.1 AND DOES NOT
RETURN ANY DATA
Additional Information: Due to a problem in "perfstat_netinterface" API of the
AIX 7.1 system that doesn't return the network statistics, the Unix OS
Agent experiments a long wait to retrieve this data (40 minutes
for each network adapter) and this appears as a hang of the agent.

APAR: IV21507
Abstract: HIGH CPU USAGE BY KUXAGENT ON HP-UX WHILE COLLECTING PROCESS INFO
Additional Information: On HP-UX the Monitoring Agent for UNIX OS kuxagent process uses
high CPU while executing UTF8 conversions for UTF8 fields
introduced in ITM 6.2.1.

A possible workaround for this issue is to avoid that
conversions on HP-UX machines that use codepage 1051. This
workaround can be enabled setting in the ux.ini file
KUX_SKIP_UTF8CONV_PROCESS=TRUE

6.2.3.1-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IV12773
Abstract: ITM AGENT RANDOMLY REPORTS CORRUPTED INFORMATION FOR "PROCESS
COMMAND (UNICODE)" AND "COMMAND (UNICODE)" ON SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS
kuxagent process randomly reports corrupted information for
"Process Command (Unicode)" and "Command (Unicode)" for some
processes. This issue is due to a memory corruption that can
occur while wrinting info in an internal buffer.

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


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

- 6.2.3.1-TIV-ITM_UNIX-IF0004.README - This README file
- 6.2.3.1-TIV-ITM_UNIX-IF0004.tar - Fix archive .tar format
- 6.2.3.1-TIV-ITM_UNIX-IF0004.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.1-TIV-ITM_UNIX-IF0004/kux_aix523_tema_if0004.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_aix526_tema_if0004.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_hp11_tema_if0004.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_hp116_tema_if0004.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_hpi116_tema_if0004.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_sol283_tema_if0004.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_sol286_tema_if0004.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_sol293_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_sol296_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kux_sol606_tema_if0004.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.3.1-TIV-ITM_UNIX-IF0004/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.1-TIV-ITM_UNIX-IF0004.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.1-TIV-ITM_UNIX-IF0004, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.1-TIV-ITM_UNIX-IF0004/kux_xxxxxx_tema_if0004.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_if0004.tar
> ./cinfo -i
ux Monitoring Agent for Unix OS
aix523 Version: 06.23.01.00


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

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

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 062301004

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 062301004

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.1-TIV-ITM_UNIX-IF0004) 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.01.04

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.01.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.01.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.23.01.04

.
.
.


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.