IBM Tivoli Monitoring: Linux(R) OS Agent 6.2.3.5-TIV-ITM_LINUX-IF0004

Download Description

Copyright International Business Machines Corporation 2018.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: Linux(R) OS Agent,
       Version 6.2.3 Fix Pack 5

Component ID: 5724C04LN

Interim Fix 0004 (6.2.3.5-TIV-ITM_LINUX-IF0004)

Date: September 30, 2018

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: IV80542
  Abstract: Monitoring Agent for Linux OS core dumps while monitoring disks.
  Additional Information:  he Monitoring Agent for Linux OS can randomly crash
    during Disk attribute group data collection. This is due to a memory
    corruption caused by a timing condition between two agent internal threads.
    This condition may occur when one or more filesystems do not respond within
    the 2 seconds default timeout for the statfs64 system call.
    
  2.2 Defects
  -----------
  None.
 
  2.3 Enhancements
  ----------------
  None.

  2.4 Superseded fixes
  --------------------
  6.2.3.5-TIV-ITM_LINUX-IF0003
  ----------------------------
  APAR: IV73936
  Abstract: Incorrect processors' CPU percentages in the Linux CPU attribute group.
  Additional Information:  The Monitoring Agent for Linux OS may temporarily incorrectly
     report 0% or 100% for all of the CPU percent attributes in the Linux CPU attribute
     group, like User CPU (Percent), System CPU (Percent) or Busy CPU (Percent). This is
     the effect of a failure in waiting for the expected time between two consecutive
     samples. This behavior is not permanent and normal values are restored within few minutes.

  6.2.3.5-TIV-ITM_LINUX-IF0002
  ----------------------------
  APAR: IJ01157
  Abstract: Extra device names listed for Disk IO attribute grouop.
  Additional Information:  The Monitoring Agent for Linux OS agent sometimes
    shows extra values for the Device Name for the Linux Disk IO attribute
    group. The agent reads the /proc/diskstats file to get the
    device names. If on a subsequent read of the file, there are
    fewer device names listed, the names are still returned as
     current values, even if they no longer exist in the file.

  6.2.3.5-TIV-ITM_LINUX-IF0001
  ----------------------------
  APAR: IV71612
  Abstract: Monitoring Agent for Linux OS randomly crashes during Disk data collection.
  Additional Information: Due to a lack of synchronization with the internal thread that collects data for the
    "Disk Usage Trends" attribute group it may happen that the agent crashes while responding to a query or a
    situation on the "Linux Disk" attribute group, as the two groups share the same filesystems' cache.
    The event is rare because the "Disk Usage Trends" thread runs only once per hour by default.  
    
  APAR: IV78033
  Abstract: Monitoring Agent for Linux OS randomly goes in hang during Disk data collection.
  Additional Information: Due to a lack of synchronization with the internal thread that collects data for the
    "Disk Usage Trends" attribute group it may happen that the agent goes in hang while responding to a query
    or a situation on the "Linux Disk" attribute group, as the two groups share the same object. The event is
    rare because the "Disk Usage Trends" thread runs only once per hour by default.

  APAR: IV56917
  Abstract: Monitoring Agent for Linux OS does not have a system to disable the monitor on cifs file system.
  Additional Information: Monitoring Agent for Linux OS does not have a system to disable the monitor on cifs
    file system in Linux Disk attribute group. In order for this APAR to be properly implemented in your
    environment, a new environment variable has been added. See the "Install Actions" section of the APAR
    conclusion for more details.

  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: Linux OS Agent 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, 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_LINUX-IF0004.README  - This README file
- 6.2.3.5-TIV-ITM_LINUX-IF0004.tar     - Fix archive .tar format
- 6.2.3.5-TIV-ITM_LINUX-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 Linux(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_LINUX-IF0004/klz_lpp266_tema_if0004.tar    - Binaries for Linux on PowerPC®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_li6243_tema_if0004.tar    - Binaries for Linux on Intel
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_li6263_tema_if0004.tar    - Binaries for Linux (2.6 kernels) on Intel
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_ls3243_tema_if0004.tar    - Binaries for 32-bit Linux on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_ls3263_tema_if0004.tar    - Binaries for 32-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_ls3246_tema_if0004.tar    - Binaries for 64-bit Linux  on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_ls3266_tema_if0004.tar    - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_lx8266_tema_if0004.tar    - Binaries for Linux on AMD Opteron
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klz_lia266_tema_if0004.tar    - Binaries for Linux on Itanium
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzlpp266.dsc                 - Descriptor file for Linux on Power
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzli6243.dsc                 - Descriptor file for Linux on Intel
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzli6263.dsc                 - Descriptor file for Linux (2.6 kernels) on Intel
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzls3243.dsc                 - Descriptor file for 32-bit Linux on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzls3246.dsc                 - Descriptor file for 64-bit Linux on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzls3263.dsc                 - Descriptor file for 32-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzls3266.dsc                 - Descriptor file for 64-bit Linux (2.6 kernels) on zSeries®
- 6.2.3.5-TIV-ITM_LINUX-IF0004/klzlx8266.dsc                 - Descriptor file for Linux on AMD/EM64T
- 6.2.3.5-TIV-ITM_LINUX-IF0004/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 Linux systems and 'C:\IBM\ITM'
    on Windows systems.

    Before installing this fix on Linux 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.5-TIV-ITM_LINUX-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 Linux 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 Linux system, if the fix was expanded to
     <TEMP>/6.2.3.5-TIV-ITM_LINUX-IF0004, the install command would be:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>/6.2.3.5-TIV-ITM_LINUX-IF0004/klz_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 klz_li6263_tema_if0004.tar
       > ./cinfo -i
       lz      Monitoring Agent for Linux OS
                 li6263  Version: 06.23.05.00

  5.3 Remote agent update
  ------------------------
  1. Transfer the appropriate archive file
     (e.g. 6.2.3.5-TIV-ITM_LINUX-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 Linux 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 Linux
     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 Linux systems,
     if the fix was expanded to <TEMP>/6.2.3.5-TIV-ITM_LINUX-IF0004
     > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.3.5-TIV-ITM_LINUX-IF0004

     On a Windows system,
     if the fix was expanded to <TEMP>\6.2.3.5-TIV-ITM_LINUX-IF0004
     > %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.3.5-TIV-ITM_LINUX-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 Linux 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 062305004

     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 lz
                                          -n <Managed System Name>
                                          -v 062305004

     Note:
     - The component (-t) for the "tacmd updateAgent" command is
       specified as two characters (lz), not three characters (klz).
     - 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.5-TIV-ITM_LINUX-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 Linux 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 Linux 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

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

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

     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 : candle      Installer Lvl:06.23.05.00
      CandleHome: /data/rthan/fp1temsteps
      ***********************************************************
      ...Product inventory
       .
       .
       .

      lz      Monitoring Agent for Linux OS
               li6263  Version: 06.23.05.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 klzagent
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.