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

Component: IBM(R) Tivoli(R) Monitoring: Linux(R) OS Agent,
	   Version 6.2.1   
           
Component ID: 5724C04LN

Interim Fix: 0002, 6.2.1.0-TIV-ITM_LINUX-IF0002

Date: December 7, 2009           

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. 


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs 
-------------
None.                                   

2.2 Defects
-----------
Defect: 110855
Abstract: OS Version Information attribute display incorrect value
Additional Information: In "System Configuration" workspace, "OS version"
            information Attribute reports wrong data on VMware ESX Server 4.0

2.3 Enhancements 
----------------
None.
      
2.4 Superseded fixes:
---------------------
6.2.1.0-TIV-ITM_LINUX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
APAR: IZ37670
Abstract: ITM LINUX OS AGENT CRASHES
Additional Information: The Monitoring Agent for Linux OS crashes if 
           there is a blank line at the end of the file /proc/net/dev. 
  
APAR: IZ49762   
Abstract: ITM IDML BOOK CONTAINS INVALID MAPPING - LINUX OS AGENT
Additional Information: In a private IP network, running tmsdla 
            you get messages like: "No default template found";
            the resulting idml book is invalid, therefore, when loading
            the book to TADDM using loadidml, you get the following
            errors:
            2008-11-11 06:50:32,326   main   ERROR bulk.CdbRandomAccess
             - Invalid relationship entry located in file:
               <cdm:installedOn source="xxxxx" target="yyyyy"/>
            2008-11-11 06:50:32,326   main   ERROR bulk.CdbRandomAccess
             - The source or target in a relationship defintion were
               not found in the file.
            where xxxxx is the source address, and yyyyy is the target
            address.
            NOTE: see additional product information is section 8.1 below.

APAR: IZ50736 
Abstract: TOTAL_ERROR_PERCENT RETURN VALUES BIGGER THAT 100
Additional Information:  From time to time, attribute
            Total_Error_Percent (column FIOERRPCT, caption Error Percent)
            within attribute group Linux_Network, returns wrong
            values, even much higher than 100, causing the related
            situation to fire.

APAR: IZ58740 
Abstract: LINUX AGENT HIGH CPU UTILIZATION FOR THE PROCESS ATTRIBUTE GROUP                                          
Additional Information: The Monitoring Agent for Linux OS klzagent    
            process spikes in CPU when handling request for the KLZPROC      
            attribute group when interacting with a third-party              
            authentication software.  The fix uses a cache for the           
            resolution of UID/GID in usernames/groupnames.  The              
            environment variable UID_USERNAME_REFRESH_TIME that can be       
            specified in the configuration file lz.ini allows the user       
            to set the refresh time in  minutes for the cache.  If the       
            environment variable is not specified, the agent uses the        
            default refresh time of 60 minutes.  Please also note that       
            specifying UID_USERNAME_REFRESH_TIME=0 results in the cache      
            not being used at all.        

Defect: 87492
Abstract: Situation for the missing file does not trigger as expected.

Defect: 99792
Abstract: When using remote deploy to upgrade the Log Alert Agent for
            UNIX on platform ls3263, the silent install is interrupted by
            a user prompt from the installer and aborts.  The deploy command
            proceeds to timeout since it did not get a successful result
            from the install.
		  
Defect 105837
Abstract: agents Agent xml files, e.g. klz_tdmdla, in wrong directory.

3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in Chapter 2 of 
the IBM Tivoli Monitoring: Monitoring Agent for Linux OS User's Guide, version 6.2.1.

The following link is for the Tivoli platform 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
  --------------------------------
  The prerequisite level for this fix is as follows:
 
  - IBM Tivoli Monitoring, Version 6.2.1

4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.1.0-TIV-ITM_LINUX-IF0002.README  - This README file
- 6.2.1.0-TIV-ITM_LINUX-IF0002.tar     - Fix archive .tar format
- 6.2.1.0-TIV-ITM_LINUX-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 Windows(R) environment. 

The fix archive file contains the following files:
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_tems_teps_tepd_if0002.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers 
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_tems_teps_tepd_if0002.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers 
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_lpp266_tema_if0002.tar    - Binaries for Linux on PowerPC®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_li6242_tema_if0002.tar    - Binaries for Linux on Intel®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_li6243_tema_if0002.tar    - Binaries for Linux on Intel
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_li6263_tema_if0002.tar    - Binaries for Linux (2.6 kernels) on Intel
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_ls3243_tema_if0002.tar    - Binaries for 32-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_ls3263_tema_if0002.tar    - Binaries for 32-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_ls3246_tema_if0002.tar    - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_ls3266_tema_if0002.tar    - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_lx8266_tema_if0002.tar    - Binaries for Linux on AMD Opteron
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klz_lia266_tema_if0002.tar    - Binaries for Linux on Itanium
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzlpp266.dsc                 - Descriptor file for Linux on Power
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzli6242.dsc                 - Descriptor file for Linux on Intel
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzli6243.dsc                 - Descriptor file for Linux on Intel
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzli6263.dsc                 - Descriptor file for Linux on Intel
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzls3243.dsc                 - Descriptor file for 32-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzls3246.dsc                 - Descriptor file for 64-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzls3263.dsc                 - Descriptor file for 32-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzls3266.dsc                 - Descriptor file for 64-bit Linux on zSeries®
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzlx8266.dsc                 - Descriptor file for Linux on AMD/EM64T
- 6.2.1.0-TIV-ITM_LINUX-IF0002/klzlia266.dsc                 - Descriptor file for Linux on 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.

  5.2 Local agent update
  --------------------------
  1. Transfer the appropriate archive file (6.2.1.0-TIV-ITM_LINUX-IF0002tar
     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 unzip utility on Windows systems. This creates a directory 
     structure that contains fixes for all of the supported platforms.
     
  3. Use the itmpatch command to install the fix for the operating 
     system of that agent. For more information on the itmpatch command,
     see section [6.2].      
     
     On UNIX systems, if the fix was expanded to <TEMP>/6.2.1.0-TIV-ITM_LINUX-IF0002, 
     the install command would be:
     
     > itmpatch -h <CANDLEHOME> 
                -i <TEMP>/6.2.1.0-TIV-ITM_LINUX-IF0002/[klz_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 klz_li6263_tema_if0002.tar
       > ./cinfo -i
       lz      Monitoring Agent for Linux OS
                 li6263  Version: 06.21.00.00


  5.3 Remote agent update
  ----------------------------
  1. Transfer the appropriate archive file (6.2.1.0-TIV-ITM_LINUX-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.

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

     On a Windows system, 
     if the fix was expanded to <TEMP>\6.2.1.0-TIV-ITM_LINUX-IF0002:
     > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.1.0-TIV-ITM_LINUX-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.

     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 lz
                                         -n <Managed system name>
                                         -v 06210000

     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 lz
                                           -n <Managed system name>    
                                           -v 06210002
                              
     Note:
     - The component (-t) for the updateAgent command is specified as 
       two characters (lz), not three characters (klz).
     - 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
  ------------------------------
  
  This fix (6.2.1.0-TIV-ITM_LINUX-IF0002) includes changes to the agent
  support files which need to be installed. 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 (6.2.1.0-TIV-ITM_LINUX-IF0002.tar
     or .zip) to the IBM Tivoli Enterprise Portal Servers.
     
  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. Expand the archive file (klz_tems_teps_tepd_if0002.tar or .zip)
     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. Start the Application Support Installer GUI to install the fix.  
     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:
     > $CANDLEHOME/JRE/<platform>/bin/java -jar setup.jar   
           
     On a Windows system:
        > <"C:\Program Files\IBM\Java142">\jre\bin\java -jar setup.jar 
        
        where <"C:\Program Files\IBM\Java142"> is the default drive
        and location of IBM Java 1.4.2. The location of IBM Java 1.4.2
        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 would
     like to add application support to.  For this fix, the check boxes
     should be as follows:

     checked   - Tivoli Enterprise Monitoring Server (TEMS)
     checked   - Tivoli Enterprise Portal Server (TEPS)
     unchecked - Tivoli Enterprise Desktop Client (TEPD)

     Continue through the remaining GUI panels selecting the product
     06.21.00.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 superceded 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, 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 lz

     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 lz 

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

     When the agent update is successful, the agent version is: 
     [06.21.00.01].
    
  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 date of the build displayed 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
     
  
     On a Windows System:
     ---------------------
     To validate that all components have been installed, run the
     following command:
    
     For example:
     > %CANDLE_HOME%\InstallITM\kincinfo -i

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

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


8.0 Additional product information
======================

8.1 IZ49762   ITM IDML BOOK CONTAINS INVALID MAPPING - LINUX OS AGENT
==========================
  This APAR is addressing the case that Linux OS agents are in a private 
network. It installs an updated version of the klz_tmsdla.xml file in the TEPS directory structure.
If you also have UNIX or Windows agents, you must also install the corresponding maintenance vehicle 
with the updated file for these environments (APARS IZ50834, IZ50835).
 

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
------------------------------------
{Add or Remove as appropriate. The first occurrence of these require '(R)'.
 See http://www.ibm.com/legal/copytrade.shtml for a complete list.}

IBM, the IBM logo, and ibm.com(R) are trademarks or registered 
trademarks of International Business Machines Corporation in the 
United States, other countries, or both. If these and other IBM 
trademarked terms are marked on their first occurrence in this 
information with a trademark symbol (R or TM), these symbols 
indicate U.S. registered or common law trademarks owned by IBM 
at the time this information was published. Such trademarks may 
also be registered or common law trademarks in other countries. 
A current list of IBM trademarks is available on the Web at 
"Copyright and trademark information" at 
http://www.ibm.com/legal/copytrade.shtml.

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.

