IBM Tivoli Monitoring: CEC Base Agent 6.2.2.2-TIV-ITM_CEC_BASE-IF0005

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: CEC Base Agent,
Version 6.2.2.2

Component ID: 5724C04CB

Interim Fix 0005, 6.2.2.2-TIV-ITM_CEC_BASE-IF0005

Date: August 13, 2014

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.


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

2.1 APARs
---------------
APAR: IV41516
Abstract: IVM VIOS 2.2.1 AND ABOVE SHOW UNMONITORED LPARS DUE TO
LSPARTITION NOT LISTING VIOS ITSELF.
Additional information: Starting with VIOS 2.2.1, the "lspartition
-all" command in an Integrated Virtualization Manager (IVM)
environment no longer displays the VIOS itself. Since
the agent is dependent on the output of the lspartition
command, the agent does not monitor the VIOS itself.
Another side effect is that the partitions listed
might show incorrect data for the LPARs that are listed as
monitored.

This only affects the agent running on IVM VIOS 2.2.1
or above. Non-IVM systems do not have this problem.

APAR: IV43902
Abstract: KPK_RESOURCES.JAR CERTIFICATE EXPIRES JUNE 2013.
Additional information: The agent contains a kpk_resources.jar file
whose jar signing certificate expires June 9th, 2013.
After installing the application support files, this
might be seen in a number of ways. For example, on the
Tivoli Enterprise Portal, the labels or headings are still
displayed in English after the language pack is installed;
or after the expiration date, the Java Web Start client
does not launch; or using the desktop client, the internal
identifiers (for example:KPK:KPK1000) are displayed in the
navigator tree, instead of the text labels or headings.

APAR: IV56442
Abstract: CECDATAPROVIDER CORE IN SPMIEXIT WHEN STOPPING AGENT
Additional information: When stopping the agent, the cecDataProvider
process might core with this stack trace:
---
SiLock() at 0xd12ceef4
SiExit() at 0xd12ce234
SpmiExit@AF105_99() at 0xd12e0a28
cntrl_exit(0xffffffa4) at 0x1000605c
itmTranslator(0x0) at 0x1000e27c
main(0x1, 0x2ff21b40) at 0x100036b8
---

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

2.3 Enhancements
------------------
None.

2.4 Superseded fixes
---------------------
6.2.2.2-TIV-ITM_CEC_BASE-IF0004
6.2.2.2-TIV-ITM_CEC_BASE-IF0003
6.2.2.2-TIV-ITM_CEC_BASE-IF0002
6.2.2.2-TIV-ITM_CEC_BASE-IF0001

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------

6.2.2.2-TIV-ITM_CEC_BASE-IF0004
-----------------------------------
APAR: IV29809
Abstract: UNMONITORED LPARS ON IVM
Additional information: The data provider might display all
partitions as unmonitored on Integrated Virtualization
Manager (IVM) systems. All partitions are discovered
but are displayed as unmonitored. If this condition
occurs, when setting KBB_RAS1=ALL, the log file,
<hostname>__pk_cecDataProvider_<timestamp>_01.log, will
not contain the following text:

Calling open_lpar with host

Also, the data for the LPARs might be inaccurate if the
agent discovers more than 9 LPARs.

APAR: IV31439
Abstract: NO DATA ON IVM AFTER APAR IV20176
Additional information: After installing interim fix
6.2.2.2-TIV-ITM_CEC BASE-IF0003 for APAR IV20176, the
agent running on IVM will not display any data on the
Tivoli Enterprise Portal.

The <hostname>_pk_cecDataProvider_<timestamp>_01.log file
will have these messages:

---
hmcquery.c,1650,"get_STM3") RunCommand failed with rc=255
and status=0
cectranslator.c,158,"itmTranslator") Type_Model_Serial
system call request failed.
---

APAR: IV32535
Abstract: PARTITION NAME WITH / IS UNMONITORED
Additional information: If a partition has a "/" character in the
name, the LPAR will be displayed as unmonitored in the
Tivoli Enterprise Portal.
The <hostname>_cecDataProvider_<timestamp>-01.log file
will have a message a similar to this:

---
(...cecmodule.c,196,"open_lpar") TIMEL Error: Path Get Failed
for host <hostname/xxx>
---

6.2.2.2-TIV-ITM_CEC_BASE-IF0003
-----------------------------------
APAR: IV20176
Abstract: NO UNIQUE MACHINE IDENTIFIER FOR REMOTE CECS CAUSES
REPORTS TO FAIL
Additional information: When running Tivoli Common Reporting for the
following three reports:
---
LPAR Physical CPU Utilization Details
LPAR Physical Memory Utilization Details
LPAR Workload Trend and Forecast
---
the prompt page asks the user to choose a Central
Electronics Complex (CEC) and displays a list of
Logical Partitions (LPARs) for the users to select. If
the agent is monitoring the CEC from a remote LPAR, the
list shows LPARs from multiple CECs, not just the
LPARs on the chosen CEC. This occurs because the
machine ID attribute contains the ID of the CEC on which
the agent LPAR is running. However, the CEC ID of the
remote CEC cannot be determined due to a limitation in
the AIX Performance Tools.
Note: This APAR also requires interim fix
6.2.2.2-TIV-ITM_SYSP_RPT-IF0002 or above for the
reports.

Defect: 183500 (179111)
Abstract: Memory Leak in Take Action Code
Additional Information: Take Action can leak a small amount of
memory in the kpkagent process when the task name is
converted from UTF-8 to the local code page. This causes
memory to be allocated which is never freed.

Defect: 184783
Abstract: Add FSM support to key.pl
Additional Information: Add the ability to configure Secure Shell
(SSH) communication with the IBM Flex System Manager (FSM)
through the key.pl configuration script.

Defect: 185279
Abstract: Add FSM support to CEC agent
Additional Information: Add agent support for the IBM Flex
System Manager (FSM).

Defect: 185264
Abstract: Add support for IPV6 addresses in MANAGING_SYSTEM
cfgsvc parm
Additional Information: The agent will now allow ssh communication
with the Hardware Management Console (HMC) or the IBM
Flex System Manager (FSM) via an IPV6 address, if an
IPV6 address was configured using the cfgsvc command
for MANAGING_SYSTEM attribute.
Note: IPV4 addressing is required for the monitored
LPARs. This enhancement only addresses the communication
between the CEC agent and the HMC or FSM.

6.2.2.2-TIV-ITM_CEC_BASE-IF0002
-----------------------------------
APAR: IV15773
Abstract: CPU UNITS CONSUMED EXCEEDS MAXIMUM POOL CAPACITY
Additional information: If a monitored LPAR becomes unmonitored,
the CPU Units Consumed metric might be incorrect because
it is still using the physical CPU consumption value of
the now unmonitored LPAR.

APAR: IV15774
Abstract: CORE DUMP AT CP_WAITFORREQUEST
Additional information: The aixDataProvider-61 process might core
with the following stack trace:
---
malloc_y 69C
malloc_y 6D4
malloc_co 2C
malloc D4
strdup@AF 20
cp_WaitFo 388
itmTransl 5C8
main 3B4
__start 6C
---

APAR: IV15962
Abstract: SOMETIMES CEC AGENT SHOWS WRONG APP VALUE.
Additional information: The Available CPU Units in Pool metric might
be incorrect if one or more of the monitored LPARs goes
down.


6.2.2.2-TIV-ITM_CEC_BASE-IF0001
-----------------------------------
APAR: IV03108
Abstract: CEC UTILIZATION VIEW SHOWS DETAILS OF AN INACTIVE PARTITION.
Additional information: Statistics of an LPAR are displayed in the CEC
Utilization workspace, even after the LPAR is inactive.

APAR: IV03156
Abstract: CEC AGENT SHOWS DUPLICATE LPARS IN CEC LPAR METRICS VIEW.
Additional information: The CEC LPAR workspace sometimes shows
duplicate data for the same LPAR. This might happen when
the agent runs for days with multiple LPARs that do not
have hostnames. It might also occur when removing an LPAR
and adding another LPAR with the same hostname and IP
address.

APAR: IV04336
Abstract: CEC AGENT IS NOT DELETING REMOVED LPARS FROM THE CEC AGENT
LPAR METRICS VIEW
Additional information: If an LPAR is removed after the agent has
discovered it, then the LPAR remains in the LPAR metrics
workspace view.

APAR: IV06231
Abstract: TOTAL MONITORED CPU IS INCORRECT
Additional information: The "Total Monitored CPU" attribute value in the
Monitored CPU Resources view is not equal to the sum of all
the values for the "Entitlement" attribute values in the
Monitored Partitions view.

APAR: IV06628
Abstract: MONITORED LPARS BECOME UNMONITORED IF WE RUN CEC AGENT FOR A
LONG TIME.
Additional information: Due to a limited number of RSi handlers, an LPAR
might become unmonitored if the LPAR is rebooted nearly 1000
times before the agent is restarted.

APAR: IV07007
Abstract: PK AGENT TO SHOW PROPER ENTC VALUE FOR ALL CATEGORIES OF
MONITORED LPARS
Additional information: The "CPU Entitlement Used Pct" (entc) attribute
is incorrect for dedicated LPARs.

APAR: IV09487
Abstract: RSIOPEN CALL IN CECDATAPROVIDER CAUSES CORE
Additional information: In IBM Tivoli Monitoring: CEC Base Agent,
Version 6.2.2 Interim Feature 2, the cecDataProvider
process might core dump. This does not occur in earlier
releases. The core entry at the end of the "errpt -a"
output would be similar to:
--
PROGRAM NAME
cecDataProvider
STACK EXECUTION DISABLED
0
COME FROM ADDRESS REGISTER
RSiOpen 7FC
PROCESSOR ID
hw_fru_id: 5
hw_cpu_id: 19
ADDITIONAL INFORMATION
RSiOpen 4A4
RSiOpen 7FC
Unable to generate symptom string.
--

APAR: IV09500
Abstract: DATA PROVIDER CORE DUMP ON VIOS WHEN CONFIGURING WITH NO
HMC USER NAME.
Additional information: The cecDataProvider process might core dump
under the following conditions:
- The CEC Base agent is on VIOS 2.2.1 or above.
- When running the "cfgsvc" command to configure the agent,
the managing_system parameter does not include an HMC userid
(that is, only the HMC hostname is provided).
- Starting the agent after the above configuration.
The core entry at the end of the "errpt -a" output would
be similar to:
--
COME FROM ADDRESS REGISTER
strncpy 14
PROCESSOR ID
hw_fru_id: 0
hw_cpu_id: 2
ADDITIONAL INFORMATION
strncpy BC
getHMCadd 3EC
--
And the trace back is:
---------------------------
(dbx) where
strncpy() at 0x1001267c
getHMCaddressV6() at 0x1001f09c
gather_hmc_info(0x0) at 0x10025564
---------------------------



3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: CEC Base Agent User's Guide, version 6.2.2.1,
which is the User's Guide for version 6.2.2 Interim Feature 1 and
Interim Feature 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.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:

IBM Tivoli Monitoring: CEC Premium Agent, Version 6.2.2 Interim
Feature 2, which is available from PassPort Advantage under the
following eAssembly:

IBM Tivoli Monitoring Agents for System p V6.2.2 Interim Feature 2
AIX English (CI1MREN)
IBM Tivoli Monitoring Agents for System p V6.2.2 Interim Feature 2,
Agent Support Files Multiplatform English (CI1MQEN).

For details, see the Troubleshooting Wiki:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/System%20P%20Agents

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.

If running Tivoli Common Reporting, interim fix
6.2.2.2-TIV-ITM_SYSP_RPT-IF0003 or above is required.


4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005.README - This README file
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005.tar - Fix archive .tar format
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005.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.2.2-TIV-ITM_CEC_BASE-IF0005/kpkaix523.dsc
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005/kpk_aix523_tema_if0005.tar
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005/pk_dd.properties
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005/pk_dd_062202005.xml
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005/kpk_tems_teps_tepd_if0005.tar
- 6.2.2.2-TIV-ITM_CEC_BASE-IF0005/kpk_tems_teps_tepd_if0005.zip


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

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(6.2.2.2-TIV-ITM_CEC_BASE-IF0005.tar or .zip) to a temporary
directory on the system that contains the agent code to be
updated. For the purpose of this README, the symbol <TEMP>
represents the fully qualified path to this directory. Note: On
Windows systems, this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for the operating
system for 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.2.2-TIV-ITM_CEC_BASE-IF0005, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.2-TIV-ITM_CEC_BASE-IF0005/kpk_aix523_tema_if0005.tar

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(6.2.2.2-TIV-ITM_CEC_BASE-IF0005.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 systems,
this path 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.

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

On Windows systems,
if the fix was expanded to <TEMP>\6.2.2.2-TIV-ITM_CEC_BASE-IF0005:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.2-TIV-ITM_CEC_BASE-IF0005

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.

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 pk
-n <Managed system name>
-v 062202005

On Windows systems:
> %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 PK
-n <Managed system name>
-v 062202005

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (PK), not three characters (KPK).
- 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_CEC_BASE-IF0005 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_CEC_BASE-IF0005.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 (kpk_tems_teps_tepd_if0005.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.

Note: For IBM Tivoli Monitoring Version 6.2.3 or above, one
of the following additional steps must be performed.

1. Acquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-tiv-itm_asi-if0002 at

http://www.ibm.com/support/docview.wss?uid=swg24034924

for download and installation instructions.

-- OR --

2. Specify the '-j javahome' parameter with the path to
a Java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.

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 CEC Base
06.22.02.05 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
-----------------------------------------------------
This fix includes changes to the agent baroc files that must be
reinstalled. Refer to IBM Tivoli Monitoring Installation and Setup
Guide under "Installing monitoring agent baroc files on the event
server" in "Installing the IBM Tivoli Enterprise Console Event
Synchronization" section for more information.

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 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 log in 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 PK

On Windows systems, 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 PK

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

When the agent update is successful, the agent version is:
6.22.02.05.


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

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.