IBM Tivoli Monitoring: Unix(R) OS Agent 6.3.0.7-TIV-ITM_UNIX-IF0002

Download Description

Copyright International Business Machines Corporation 2018.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
       Version 6.3.0 Fix Pack 7

Component ID: 5724C040U

Interim Fix 0002 (6.3.0.6-TIV-ITM_UNIX-IF0002)

Date: July 20, 2018 - Updated

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

Change History:
---------------
2018-07-20  Updated Interim Fix to include APAR IJ07771.

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: IJ02490
  Abstract:  Scripting feature does not allow .ref location to be changed.
  Additional Information:   The scripting feature automatically generates a
     .ref file which contains information for the script to run.  Currently
     the OS Agent defaults the location for this file to the
     $CANDLEHOME/tmp/osfcp directory.   This APAR add the capability to set the
     location where the .ref file gets generated.

     In order for this APAR to be properly implemented in your environment, a
     new environment variables has been added: KUX_FCP_REF_FILE_PATH.  To specify
     a different location for the .ref file, set value to a valid path that
     has read-write authority, for example:
        KUX_FCP_REF_FILE_PATH=/opt/writelocation

     The default if the environment variable is not set, is to continue to use
     the location $CANDLEHOME/tmp/osfcp.

   APAR: IJ01986
   Abstract: High CPU caused by running "sneep" command
   Additional Information:  On Solaris, when the agent collects the serial number attribute,
     it will first try to call "eeprom" command.  If this is not successful or if
     KUX_SKIP_SUN_EEPROM environment variable is set, it will try to call the "sneep"
     command to collect the data.

     On some systms, the "sneep" command can cause high CPU.  This APAR will
     add a new environment variable that will skip calling the "sneep" command.

     In order for this APAR to be properly implemented in your environment, a new
     environment variables has been added: KUX_SKIP_SUN_SNEEP.  The variable should
     be set to "true" to have the agent not call the "sneep" command.
        KUX_SKIP_SUN_SNEEP=true

     The default if the environment variable is not set, is to continue to call "sneep"
     if the "eeprom" command is not successful or is skipped.
 
  APAR: IJ03901
  Abstract:  AIXNETADPT data sometimes returns extra rows
  Additional Information:  When monitoring the AIX Network Adapters (AIXNETADPT)
      attribute group, sometimes extra rows are returned containing invalid data.
      This can cause real time data to show invalid data on portal as well as
      historical data collection table to be corrupted or unusable.

  APAR: IJ02261
  Abstract:  Allow Watchdog cpuThresold to be greater than 100.
  Additional Information: Allow the CPU Threshold which can be set for Watchdog
      to be greater than 100.   On a multi-CPU system, the CPU percentage can
      be greater than 100, however Watchdog allows a maximum of 100 percent to
      be set.

      A new environment variable has been added and when set to true will allow the
      cpuThreshold value to be greater than 100 in the Watchdog CAP file (e.g. kca.xml)
      KCA_CPUTHRESHOLD_GREATER_100=true  

  APAR: IJ05086
  Abstract:  Problem Description: On Solaris, the agent stops collecting data relying
      on stat_daemon
  Additional Information: On Solaris, the stat_daemon is reported as having terminated
      with a timeout message even though the stat_daemon process remains running and
      the stat_daemon RAS1 log continues to be updated indicating it is still
      collecting data. When this issue occurs, the main agent process - kuxagent -
      indicates that the stat_daemon processing has been terminated, and attributes
      relying on this data collector will no longer be gathered.

  APAR: IV96264
  Abstract:  On AIX, memory percentage can sometimes be a negative value.
  Additional Information:   On AIX, the Monitoring Agent for UNIX OS values for
     "Percent on Computational Memory", "Percent Computiatonal Memory, and
     Percent Available File Cache can sometimes be a negative value.
 
  APAR: IV96304
  Abstract:  On AIX, situation using ProcessFilter for a MISSING process triggered when running.
  Additional Information:  On AIX, the Monitoring Agent for UNIX OS a situation for a *MISSING
    process is triggered when it is running.   This occurs when using the ProcessFilter_U
    attribute group along with the *MISSING, for example:
      *IF *VALUE Process.ProcessFilter_U *EQ '.*java .*(appserver01).*' *AND
      *MISSING Process.Process_Command_U *EQ ('appserver01')

    The agent does not have the correct process arguments when a process is newly started. This
    is a timing issue and results in a situation with for a MISSING process to be triggered when
    the process is actually running.

    Along with this update, the *MISSING Process situations should be updated to have Situation
    Persistence "Consecutive true samples" set to 2 (or higher).
 
  APAR: IV96512
  Abstract:  String attributes in AIX LPAR attribute group not converted to UTF-8
  Additional Information:  The following attributes in the AIX LPAR attribute group are defined
    as UTF-8 strings, but are not converted to UTF-8:
    Shared Mode, Capped Mode, SMT Mode, Machine ID, Last Machine ID, LPAR Name, Uptime, Hostname

  APAR: IV97081
  Abstract:  On Solaris, the value for the for the Space Used Percent does not align with
    the "df" command.
  Additional Information:   On Solaris with ZFS, the Space Used Percent does not
    align with the "df" command output.  The value is calculated using the ZFS metrics
    which uses the USED value from "zfs get" command, which includes reservations allocated
    for children dataset as used by the parent.  

    This APAR fix, when a new environment variable is set, will calculate the Space Used
    Percent to include only the spaced used by the dataset and not include the space
    allocated for the child datasets. This will allow the value to more closely align with
    the "df" command output.

    In order for this APAR to be properly implemented in your environment, a new environment
    variable, KUX_SPACE_USED_PCT_FS, must be set to TRUE.  When this variable to set to TRUE
    the Space Used Percent attribute will be calculated using just the space used by the
    dataset (without taking into accout the quota for the children).
                                   
    For example, set in the $CANDLEHOME/ux.ini file:               
      KUX_SPACE_USED_PCT_FS=TRUE

    If this variable is not set or not set to TRUE then the value for the attribute will be
    calculated as previously done.

  APAR: IV98517
  Abstract:  Agent log file filled with "Error Converting process command" messages
  Additional Information:  The Monitoring Agent for UNIX OS agent RAS1 log file
    (<hostname>_ux_kuxagent_<nnnnnn>-0<n>.log) is filled with the message:
     (592D6494.0004-13:kux03agt.cpp,742,"TakeSample") Error converting ;
     no conversion occurred. Length '0', commandArgs: ''

  APAR: IJ07771
  Abstract: Remove extra processutils trace messages
  Additional Information:  APAR fix IV96304 inadvertantly added extra tracing
     which should not be on by default.  As a result extra tracing is written to
     the agent RAS1 log file.

     The messages do not cause a problem, as the RAAS1 log files will
     wrap, however other important messages could be missed by the
     extraneous messages.

     Example of the trace messages:
     (5B47A38B.0013-4:processutils.cpp,291,"getArguments")
     <0x110B328C0,0x8000>
     +5B47A38B.0013     00000000   2F757372 2F736269  6E2F736E
     6D706420   /usr/sbin/snmpd.
     +5B47A38B.0013     00000010   00000000 00000000  00000000
     00000000   ................
     +5B47A38B.0013     **************  00000020 - 00008000: Same as
     above  **************

  2.2 Defects
  -----------
  None.
 
  2.3 Enhancements
  ----------------
  None.

  2.4 Superseded fixes
  --------------------
  6.3.0.6-TIV-ITM_UNIX-IF0001

  2.5 APARS and defects included from superseded fixes
  ----------------------------------------------------
  6.3.0.6-TIV-ITM_UNIX-IF0001
  ---------------------------
  APAR: IV91153
  Abstract: On Solaris, the value for the zone name for active zones can
     contain extra (garbage) characters.
  Additional Information: This has been seen on Intel Solaris systems,
     independent of the Monitoring Agent for UNIX OS version, version
     of the operating system, or zfs configuration.

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

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.ht…

  3.1 Prerequisites for this fix
  ------------------------------
  - IBM Tivoli Monitoring, Version 6.3.0 Fix Pack 7.

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

- 6.3.0.7-TIV-ITM_UNIX-IF0002.README  - This README file
- 6.3.0.7-TIV-ITM_UNIX-IF0002.tar     - Fix archive .tar format
- 6.3.0.7-TIV-ITM_UNIX-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 Microsoft Windows(R) environment.

The fix archive file contains the following :
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_aix523_tema_if0002.tar    - UNIX Agent binaries for AIX 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_aix526_tema_if0002.tar    - UNIX Agent binaries for AIX 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_hp11_tema_if0002.tar      - UNIX Agent binaries for HP-UX 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_hp116_tema_if0002.tar     - UNIX Agent binaries for HP-UX 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_hpi116_tema_if0002.tar    - UNIX Agent binaries for HP-UX Itanium.
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_sol283_tema_if0002.tar    - UNIX Agent binaries for Solaris 8 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_sol286_tema_if0002.tar    - UNIX Agent binaries for Solaris 8 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_sol293_tema_if0002.tar    - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_sol296_tema_if0002.tar    - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kux_sol606_tema_if0002.tar    - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxaix523.dsc                 - Descriptor file for AIX 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxaix526.dsc                 - Descriptor file for AIX 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxsol283.dsc                 - Descriptor file for Solaris 8 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxsol286.dsc                 - Descriptor file for Solaris 8 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxsol293.dsc                 - Descriptor file for Solaris 9/10 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxsol296.dsc                 - Descriptor file for Solaris 9/10 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxsol606.dsc                 - Descriptor file for Solaris 10 Opteron 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxhp11.dsc                   - Descriptor file for HP-UX 32-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/kuxhp116.dsc                  - Descriptor file for HP-UX 64-bit
- 6.3.0.7-TIV-ITM_UNIX-IF0002/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.3.0.7-TIV-ITM_UNIX-IF0002.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.3.0.7-TIV-ITM_UNIX-IF0002, the install command would be:

     > itmpatch -h <CANDLEHOME>
                -i <TEMP>/6.3.0.7-TIV-ITM_UNIX-IF0002/kux_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 kux_aix523_tema_if0002.tar
       > ./cinfo -i
       ux      Monitoring Agent for Unix OS
                   aix523  Version: 06.30.07.00

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

     On a Windows system,
     if the fix was expanded to <TEMP>\6.3.0.7-TIV-ITM_UNIX-IF0002
     > %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.0.7-TIV-ITM_UNIX-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 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 063007002

     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 063007002

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

     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

      *********** Mon Feb 6 03:01:21 EST 2017 ******************
      User      : root         Group: system bin sys security cron audit lp
      Host name : host1        Installer Lvl:06.30.07.00
      CandleHome: /data/rthan/fp1temsteps
      ***********************************************************
      ...Product inventory
       .
       .
       .

      ux      Monitoring Agent for UNIX OS
               aix523  Version: 06.30.07.02

       .
       .
       .

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

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.