IBM Tivoli Monitoring: Unix(R) OS Agent 6.2.2.2-TIV-ITM_UNIX-IF0004

Download Description

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

Component: IBM(R) Tivoli(R) Monitoring: UNIX(R) OS Agent,
Version 6.2.2

Component ID: 5724C040U

Fix: Interim Fix 0004 (6.2.2.2-TIV-ITM_UNIX-IF0004)

Date: November 30, 2010

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. 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: IZ67733
Abstract: HANDLE PROPERLY THE STATVFS64 ERROR PATH FOR THE DISK ATTRIBUTE GROUP
Additional Information: In case of an error returned by the statvfs64 system call,
the agent should not return overflow values for the attributes
belonging to the disk attribute group, but instead it should
return the default -2 or "NOT COLLECTED" value.

APAR: IZ73074
Abstract: UX AGENT CAUSING NETTL ERRORS ON HPUX FOR DOWN NETWORK INTERFACES
Additional Information: ITM Unix OS agent on HP-UX generates many errors
from ifstat process in OS NETTL.log file when it tries to collect
information about down network interfaces.

APAR: IZ76364
Abstract: OPTION TO REMOVE PRCTL CALLS FROM UNIX OS AGENT CODE
Additional Information: On Solaris the Monitoring Agent for UNIX OS
kuxagent process due to a SUN Solaris bug in prctl command,
can generate a local zone crash.
In order to workaround this Sun Solaris bug, a new parameter
has been added in order to do not use the prctl command.
It is possible to disable this command setting the
following parameter in the ux.ini file to TRUE:
KUX_PRCTL_OFF=TRUE

APAR: IZ77499
Abstract: GRANULARITY REQUIRED FOR THE UNIX OS AGENT TO WAREHOUSE
MEANINGFUL UNIX/LINUX DISK IO ATTRIBUTE FOR HP UNIX AND SOLARIS.
Additional Information: Unix OS Agent on Solaris and HP reports a lot disks
in DISK IO AttributeGroup/workspace that are not really used/available
to the machine. This can happen for machines connected to a SAN.
These disks have all values equal to 0. So a new parameter has been
added in order to filter disks that have all IO attributes equal to 0.
In order to enable this new behavior you have to set the following
variable in the ux.ini file:
KUX_SKIP_DISABLED_DISKS=TRUE

APAR: IZ77639
Abstract: WRONG CPU METRICS ON HP MACHINES
Additional Information: Unix OS Agent collets wrong CPUs Id and metrics on HP Itanium
when hyperthreading (from setboot command) is "ON" and lcpu_attr=0 (from
kctune command). In order to solve this issue set the following variable
in the ux.ini file:
KBB_HPUX_SAR=TRUE

APAR: IZ78243
Abstract: UNIX OS AGENT CRASHES ON SOLARIS WHILE IT IS COLLECTING
SOLARIS ZONES INFORMATION
Additional Information: Unix OS agent running as non-root can crash on Solaris while
it is collecting Solaris Zones information when it fails to access a file
in /proc filesystem.

APAR: IZ78623
Abstract: NEGATIVE NETWORK VALUES ON HP
Additional Information: On HP the Monitoring Agent for UNIX OS can report negative
values for some attributes (like "Input Errors") in the Network workspace.
This problem is due to an internal overflow.

APAR: IZ81260
Abstract: STAT_DAEMON PROCESS DID NOT TERMINATE WHEN OS AGENT WAS STOPPED.
Additional Information: After a restart on AIX the Monitoring Agent for UNIX OS
stat_daemon process did not stop when the OS Agent was stopped
using tha itmcmd command. When this problem happens the
stat_daemon process shows a high CPU usage and its PPID is 1.

APAR: IZ82944
Abstract: INCREASE THE OS AGENT LIMIT OF SUPPORTED DISKS
Additional Information: Monitoring Agent for Unix OS was able to monitor just
1024 disks on AIX, this limit has been increased to 4096 disks.
When the old limiti is reached this message appears in the stat_daemon
log file:
4C45EC82.01AD-1:disk_stat.cpp,1423,"is_duplicated_iostat_entry")
Error: Maximum number of disks entries exceeded!
APAR: IZ84120
Abstract: CHILD 'KUXAGENT' OF UNIX OS AGENT HANGED UP IN STARTING UP
Additional Information: On AIX child 'kuxagent' of UNIX OS Agent
hanged up in starting up sequence.
Parent 'kuxagent' was sending heartbeat to TEMS, so TEMS
recognized KUX as working fine. However, in fact, stat_daemon and
children were not started at that time.

APAR: IZ84910
Abstract: SCAN FILE NOT WORKING FOR FILE INFORMATION ATTRIBUTES GROUP
Additional Information: In a situation formula for the File Information
attribute group, with ( PATH=xxxx AND SCAN FILE=yyyy ),the Unix OS agent
does not return the list of files in PATH and the situation does not
work. On the contrary, the list is returned as expected if the
predicates are exchanged as in the following: (SCAN FILE=yyyy AND PATH=xxxx).

2.2 Defects
-----------
None.

2.3 Enhancements
----------------
Enhancement: Monitor File Systems of NFS type on UNIX
Abstract: The following environment variable is introduced to enable/disable NFS
monitoring at the agent side:
KBB_SHOW_NFS=true|false
with a default value "false" on Unix.
A timeout has been introduced, configurable through the KBB_NFS_TIMEOUT
environment variable (default is 2 seconds, allowed range 1-30 seconds).
A new attribute, named File System Status, has been added to the Unix Disk
group and it will report "Up" (normal case), "Down" (timeout expired)
or "Not Available" in error case.

2.4 Superseded fixes
--------------------
6.2.2.2-TIV-ITM_UNIX-IF0003
6.2.2.2-TIV-ITM_UNIX-IF0002 - not shipped
6.2.2.2-TIV-ITM_UNIX-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.2.2.2-TIV-ITM_UNIX-IF0003
---------------------------
APAR: IZ76377
Abstract: WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
Additional Information: The Agent Management Services watchdog utility which
is part of the OS Agent used the "cinfo -R" command to get the
status of running agents. Most of these calls originate from
the common agent package (CAP) files, such as klz_default.xml.
The "cinfo -r" call is quicker and uses less resources than
"cinfo -R". It also can reduce the risk of the RunInfo file
getting out-of-sync which can cause multiple agents to be started.
The fix also changes the checkFrequency default to 120 seconds for
the OS Agents and watchdog process.

Please see Section 8.1 under 'Additional product information' for
more information regarding this APAR fix.

APAR: IZ78695
Abstract: MULTIPLE COPIES OF OS AGENTS RUNNING
Additional Information: There are multiple kuxagent or klzagent processes
running from a single $CANDLEHOME. There can also be multiple
copies of other agents running that are being monitored by the
Agent Management Services watchdog utility of the OS Agent.

APAR: IZ81303
Abstract: ITM 622 FP2 UNIX AGENT CRASHES WHEN "AGENT MANAGEMENT SERVICES"
Additional Information: Clicking on the "Agent Management Services"
navigator item under UNIX OS in Physical view of Tivoli
Enterprise Portal causes the Unix OS Agent to crash.

Defect: 119211
Abstract: Watchdog shows Process ID 0 after itmpatch of OS Agent
Additional Information: After installing an Interim Fix for the IBM Tivoli
Monitoring Agent for UNIX OS Agent or IBM Tivoli Monitoring Agent
for Linux OS Agent, the watchdog process is started with an extra
slash in the path name. This results in a Process ID of 0 being
displayed on the Agent Management Services workspace for the Proxy
Agent Services Watchdog process (kcawd).

6.2.2.2-TIV-ITM_UNIX-IF0001
---------------------------
APAR: IZ62255
Abstract: WRONG VALUE FOR THE STATUS ATTRIBUTE OF THE SOLARIS ZONE
ATTRIBUTE GROUP
Additional Information: The Status attribute of the Solaris Zone
attribute group shows a wrong status (e.g. it shows the status
of "shutting down" instead of the actual status of "running"
reported by the OS command "zoneadm -list -cv").
The problem is due to the fact that Solaris has broken the
backward compatibility for the zone_status_t enum in the
/usr/include/sys/zone.h header file in Solaris 10 Update 7:
139555-08 (sparc) and 139556-08 (x86).

APAR: IZ68560
Abstract: ITM AGENT TAKES A VERY LONG TIME IN ORDER TO COLLECT SOLARIS
Additional Information: On Solaris the Monitoring Agent for UNIX OS
kuxagent process takes a very long time to collect physical
and virtual memory information about Local Zones from the
Global Zone.
It is possible to disable this new behavior setting the
following parameter in the ux.ini file to TRUE:
KUX_PRSTAT_OFF=TRUE

APAR: IZ76188
Abstract: PROCESS MISSING SITUATIONS FIRE WHEN AIX API GETARGS() FAILS.
Additional Information: On AIX the Monitoring Agent for UNIX OS generates
false alarms because process missing situations trigger for a
missing process but the process is actually up and running but
it appears in bracket squares in ps -ef output.

APAR: IZ78795
Abstract: ITM UNIX OS AGENT CAN CRASH ON SOLARIS MACHINES
Additional Information: kuxagent process can crash on Solaris environments
in AgentUtils::cache_string_in_map method.

Enhancement: 125159
Abstract: REQ 1012 long process names support

Enhancement: 120683
Abstract: REQ 2765.1 TCP Statistics attribute group for Unix and Linux OS


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

The following link is for the Tivoli operating system 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
------------------------------
- IBM Tivoli Monitoring, Version 6.2.2 Fix Pack 2.


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

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

The fix archive file contains the following :
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_tems_teps_tepd_if0004.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_tems_teps_tepd_if0004.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_aix523_tema_if0004.tar - UNIX Agent binaries for AIX 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_aix526_tema_if0004.tar - UNIX Agent binaries for AIX 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_hp11_tema_if0004.tar - UNIX Agent binaries for HP-UX 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_hp116_tema_if0004.tar - UNIX Agent binaries for HP-UX 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_hpi116_tema_if0004.tar - UNIX Agent binaries for HP-UX Itanium.
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_sol283_tema_if0004.tar - UNIX Agent binaries for Solaris 8 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_sol286_tema_if0004.tar - UNIX Agent binaries for Solaris 8 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_sol293_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_sol296_tema_if0004.tar - UNIX Agent binaries for Solaris 9/10 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kux_sol606_tema_if0004.tar - UNIX Agent binaries for Solaris 10 Opteron 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxaix523.dsc - Descriptor file for AIX 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxaix526.dsc - Descriptor file for AIX 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxsol283.dsc - Descriptor file for Solaris 8 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxsol286.dsc - Descriptor file for Solaris 8 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxsol293.dsc - Descriptor file for Solaris 9/10 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxsol296.dsc - Descriptor file for Solaris 9/10 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxsol606.dsc - Descriptor file for Solaris 10 Opteron 64-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxhp11.dsc - Descriptor file for HP-UX 32-bit
- 6.2.2.2-TIV-ITM_UNIX-IF0004/kuxhp116.dsc - Descriptor file for HP-UX 64-bit
- 6.2.2.2-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.2.2-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.1

For example:
On a UNIX system, if the fix was expanded to
<TEMP>/6.2.2.2-TIV-ITM_UNIX-IF0004, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.2-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.22.02.04


5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.2.2.2-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 Administrator's Guide.

For example:
On UNIX systems,
if the fix was expanded to <TEMP>/6.2.2.2-TIV-ITM_UNIX-IF0004
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.2-TIV-ITM_UNIX-IF0004

On a Windows system,
if the fix was expanded to <TEMP>/6.2.2.2-TIV-ITM_UNIX-IF0004
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.2-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 "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's 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 062202004

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 062202004

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.2.2-TIV-ITM_UNIX-IF0004) 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.2.2-TIV-ITM_UNIX-IF0004.tar
or .zip) to the Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal
Desktops.

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. Expand the archive file (kux_tems_teps_tepd_if0004.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 extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.
GUI installation option
------------------------
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:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

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.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux and zLinux
operating systems requires the following files contained in
interim fix 6.2-TIV-ITM_ASI-IF0001:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".

-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java(R) is installed. The
location of Java on your system might vary.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For this fix, check or clear the
check boxes as follows:

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

Continue through the remaining GUI panels selecting the product
06.22.02.04 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 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>
-i { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-t { <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 systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, 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.22.02.04

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

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 displayed date of the build 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

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 09 03:01:19 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.22.02.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 09 03:01:21 EST 2010 ******************
User : root Group: system bin sys security cron audit lp
Host name : candleaix3 Installer Lvl:06.22.02.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

ux Monitoring Agent for UNIX OS
aix523 Version: 06.22.02.04

.
.
.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------
To validate that all components have been installed, run the
following command kincinfo -i and check UNIX OS Support Version.


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


8.0 Additional product information
==================================
8.1 IZ76377 - WATCHDOG INVOKE "cinfo -r" INSTEAD OF "cinfo -R"
--------------------------------------------------------------
The fix for this APAR makes changes to the common agent package (CAP)
file, such as $CANDLEHOME/config/CAP/klz_default.xml, which is used by
the Agent Management Services watchdog utility. In the
<availabilityStatusScript> section of this file, instead of specifying the
command "cinfo -R" it now specifies either "agentInstanceCommand.sh" or
"cinfo -r" depending on the agent.

It is recommended to not use a CAP file that still contains "cinfo -R".

If you have copied the original CAP file in $CANDLEHOME/config/CAP, such as
<pc>_default.xml file to <pc>.xml to customize settings, it is recommended
to make a copy of the latest version of this file delivered as part of this
fix and make your customizations on the newly copied file.

The Agent Builder version 6.2.2.2 Interim Fix 01
(6.2.2.2.-TIV-ITM_ABLDR-IF0001) was udpated to no longer specify "cinfo -R"
in the CAP files for single instance agents. Multi-instance agents created
by the Agent Builder did not previously specify "cinfo -R". If your agent
is a single instance agent and you will be using watchdog to monitor the
agent, it is recommended to use this version or later of the Agent Builder
to generate your agent.


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