IBM Tivoli Monitoring: UNIX(R) Log Agent 6.2.3.5-TIV-ITM_UXLOG-IF0001

Download Description

(C) Copyright International Business Machines Corporation 2015.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) Log Agent,
Version 6.2.3 Fix Pack 5

Component ID: 5724C04LA

Interim Fix 0001 (6.2.3.5-TIV-ITM_UXLOG-IF0001)

Date: April 23, 2015

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: IV54580
Abstract: UNIX Logs Agent stops alerting on incoming events on a monitored log
Additional Information: UNIX Logs Agent stops alerting on incoming events on a monitored log.
The UNIX Logs Agent logic to detect the presence of new events in a monitored log
is based on the lseek() system call. Under the condition that the log file is
truncated or rotated lseek may stop reporting further changes, and it is necessary
to close and reopen the file in order to restore alerts to be sent.

2.2 Defects
-----------
Defect: 202164
Abstract: Agent files to monitor log files if kul_configfile lists not existing files

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: Monitoring Agent for UNIX Logs User's Guide, version 6.2.3, Fix Pack 5.

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: Monitoring Agent for UNIX Logs, Version 6.2.3 Fix Pack 5.


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

- 6.2.3.5-TIV-ITM_UXLOG-IF0001.README - This README file
- 6.2.3.5-TIV-ITM_UXLOG-IF0001.tar - Fix archive .tar format
- 6.2.3.5-TIV-ITM_UXLOG-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.5-TIV-ITM_UXLOG-IF0001/kul_aix523_tema_if0001.tar - Binaries for 32-bit AIX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_aix526_tema_if0001.tar - Binaries for 64-bit AIX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_hp116_tema_if0001.tar - Binaries for 64-bit HP-UX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_hp11_tema_if0001.tar - Binaries for 32-bit HP-UX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_hpi116_tema_if0001.tar - Binaries for HP-UX on Itanium
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_li6243_tema_if0001.tar - Binaries for 32-bit Linux on Intel®
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_li6263_tema_if0001.tar - Binaries for 32-bit Linux 2.6 on Intel®
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_lia266_tema_if0001.tar - Binaries for Linux on Itanium
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_lpp266_tema_if0001.tar - Binaries for Linux on PowerPC®
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_ls3243_tema_if0001.tar - Binaries for 32-bit Linux on zSeries®
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_ls3246_tema_if0001.tar - Binaries for 64-bit Linux on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/klz_ls3263_tema_if0001.tar - Binaries for 32-bit Linux (2.6 kernels) on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/klz_ls3266_tema_if0001.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_lx8266_tema_if0001.tar - Binaries for Linux on AMD
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_sol283_tema_if0001.tar - Binaries for 32-bit Solaris
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_sol286_tema_if0001.tar - Binaries for 64-bit Solaris
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_sol606_tema_if0001.tar - Binaries for Solaris on AMD
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulaix513.dsc - Descriptor file for 32-bit AIX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulaix516.dsc - Descriptor file for 64-bit AIX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulhp11.dsc - Descriptor file for 32-bit HP-UX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulhp116.dsc - Descriptor file for 64-bit HP-UX
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulhpi116.dsc - Descriptor file for HP-UX on Itanium
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulli6243.dsc - Descriptor file for 32-bit Linux on Intel
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulli6263.dsc - Descriptor file for 32-bit Linux 2.6 on Intel
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kullia266.dsc - Descriptor file for Linux on Itanium
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kullpp266.dsc - Descriptor file for Linux on PowerPC
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulls3243.dsc - Descriptor file for 32-bit Linux on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulls3246.dsc - Descriptor file for 64-bit Linux on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kullx8266.dsc - Descriptor file for Linux on AMD
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulsol283.dsc - Descriptor file for 32-bit solaris
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulsol286.dsc - Descriptor file for 64-bit solaris
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/kulsol606.dsc - Descriptor file for solaris on AMD
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/klzls3263.dsc - Descriptor file for 32-bit Linux on zSeries
- 6.2.3.5-TIV-ITM_UXLOG-IF0001/klzls3266.dsc - Descriptor file for 64-bit Linux on zSeries


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
(6.2.3.5-TIV-ITM_UXLOG-IF0001.tar or .zip) to a temporary directory
on the system that contains the agent code to be updated.
For the purpose of this README, the symbol <TEMP> represents
the fully qualified path to this directory.
Note: On Windows, 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. 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.5-TIV-ITM_UXLOG-IF0001, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.5-TIV-ITM_UXLOG-IF0001/kul_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 kul_li6243_tema_if0001.tar.
> ./cinfo -i
Monitoring Agent for Unix Log
li6243 Version: 06.23.05.00


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

On a Windows system,
if the fix was expanded to <TEMP>\6.2.3.5-TIV-ITM_UXLOG-IF0001:
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.3.5-TIV-ITM_UXLOG-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 "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring 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 ul
-n <Managed System Name>
-v 062305001

On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t ul
-n <Managed System Name>
-v 062305001

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


5.4 Agent support update
----------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superseded fixes. No additional installation steps are required.


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 ul

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 ul

When the agent update is successful, the agent version should now be:
06.23.05.01

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



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

./cinfo -i

*********** Mon April 30 04:02:21 EDT 2011 ******************
User: root Groups: sys root other bin adm daemon mail lp users
Host name : mybox_dev Installer Lvl:06.23.05.00
CandleHome: /data/rthan/ITM623FP5
******************************************************
...Product inventory

ax IBM Tivoli Monitoring Shared Libraries
hp116 Version: 06.23.05.00

jr Tivoli Enterprise-supplied JRE
hp11 Version: 05.05.00.00

ui Tivoli Enterprise Services User Interface
hp116 Version: 06.23.05.00

ul Monitoring Agent for Unix Log
hp116 Version: 06.23.05.01



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

8.0 Additional product information
==================================
This Limited Availability/Interim fix is being provided for the IBM Tivoli Monitoring,
Unix Log agent at Version 6.2.3.5. This LA/IF fix is provided as a temporary solution
until the official maintenance release is made generally available.
When performing any code maintenance it is critical that you validate that the
APAR(s)from your LA/IF fix are contained in the maintenance package you are about
to deploy to avoid any code regressions.

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.