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

Download Description

Copyright International Business Machines Corporation 2016.
All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring: Linux(R) OS Agent,
Version 6.3.0 Fix Pack 6

Component ID: 5724C04LN

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

Date: July 1, 2016

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: IV84786
Abstract: Performance impacts due to missing option for excluding unneeded filesystem types on Linux
Additional Information: The Monitoring Agent for Linux OS only provides the possibility to choose whether or not
NFS and CIFS filesystems must be monitored. Any other types cannot be excluded. In case of a large number of
filesystems of the same type that don't need to be monitored, this limitation can introduce performance issues
on the agent. In order for this APAR to be properly implemented in your environment, a new environment variable
has been added: set KLZ_EXCLUDE_FSTYPE=<comma separated list of types> in lz.ini configuration file. Example:
KLZ_EXCLUDE_FSTYPE=mvfs,ext3. The names must match exactly those shown by command "mount -l". In case of conflict
with KBB_SHOW_NFS or KBB_SHOW_CIFS settings, KLZ_EXCLUDE_FSTYPE takes priority.

APAR: IV85805
Abstract: Linux IPV6 sockets are not monitored
Additional Information: The Linux Sockets Detail and the Linux Sockets Status attribute groups in the Monitoring Agent
for Linux OS only report information about IPV4 sockets.

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

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

2.4 Superseded fixes
--------------------
6.3.0.6-TIV-ITM_LINUX-IF0001
6.3.0.6-TIV-ITM_LINUX-IF0002

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
6.3.0.6-TIV-ITM_LINUX-IF0002
----------------------------
APAR: IV79424
Abstract: Linux processes missing start and elapsed time information.
Additional Information: The Monitoring Agent for Linux OS does not provide any information about the time when
a process was started, nor for how long it has been running.

APAR: IV82704
Abstract: The Total Memory Free attribute value is not accurate.
Additional Information: The Monitoring Agent for Linux OS estimates the physical memory actually available to
the system for starting new applications without swapping by using a simple algorithm that takes into account
freeable memory contributions like memory in cache and memory in buffers. Since kernel 3.2 the same information
is directly computed by the system, in a more accurate way, and made available through the specific MemAvailable
field in the /proc/meminfo file, as well as in the new column "available" of the "free" command output.

APAR: IV78556
Abstract: Incorrect percentages of CPU time consumed by Linux processes
Additional Information: The Monitoring Agent for Linux OS may report incorrect values for the following attributes
in the Linux Process attribute group, when they exceed 100%: Process System CPU (Percent), Process User CPU (Percent),
Cumulative Process System CPU (Percent), Cumulative Process User CPU (Percent), Process Busy CPU (Percent) and
Cumulative Busy CPU (Percent). These attributes can exceed 100% on servers with multiple online processors. Also,
these attributes are not normalized to the number of online processors, thus preventing 100% to be exceeded, whereas
other CPU-related attributes in this group are normalized. 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.

6.3.0.6-TIV-ITM_LINUX-IF0001
----------------------------
APAR: IV77559
Abstract: Events from situations on custom scripts do not close automatically.
Additional Information: The data gathered executing the custom scripts in 6.30 FP5 are reported using the
KXX_Custom_Scripts_Runtime attribute groups. These groups implement 'pure event' tables. Because of this,
situations cannot receive 'clearing' events and need to be manually closed. New KXX_Custom_Scripts_Rtm_Smp
sampled tables are added by this APAR. They report the same customs scripts' output data as those reported
by the existing pure event tables.


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

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


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

- 6.3.0.6-TIV-ITM_LINUX-IF0004.README - This README file
- 6.3.0.6-TIV-ITM_LINUX-IF0004.tar - Fix archive .tar format
- 6.3.0.6-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.3.0.6-TIV-ITM_LINUX-IF0004/klz_tems_teps_tepd_if0004.tar - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_tems_teps_tepd_if0004.zip - Support files for IBM Tivoli Enterprise Monitoring Server/Tivoli Enterprise Portal Servers
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_lpp266_tema_if0004.tar - Binaries for Linux on PowerPC®
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_li6263_tema_if0004.tar - Binaries for Linux (2.6 kernels) on Intel
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_ls3263_tema_if0004.tar - Binaries for 32-bit Linux (2.6 kernels) on zSeries®
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_ls3266_tema_if0004.tar - Binaries for 64-bit Linux (2.6 kernels) on zSeries®
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klz_lx8266_tema_if0004.tar - Binaries for Linux on AMD Opteron
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klzlpp266.dsc - Descriptor file for Linux on Power
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klzli6263.dsc - Descriptor file for Linux (2.6 kernels) on Intel
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klzls3263.dsc - Descriptor file for 32-bit Linux (2.6 kernels) on zSeries®
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klzls3266.dsc - Descriptor file for 64-bit Linux (2.6 kernels) on zSeries®
- 6.3.0.6-TIV-ITM_LINUX-IF0004/klzlx8266.dsc - Descriptor file for Linux on AMD/EM64T

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.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.6-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.3.0.6-TIV-ITM_LINUX-IF0004, the install command would be:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.3.0.6-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.30.06.00


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

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

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 063006004

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.3.0.6-TIV-ITM_LINUX-IF0004) includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use one of the two following alternative methods
to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, and Tivoli Enterprise Portal Desktop.

A. Installing with the Application Support Installer (ASI)

1. Transfer the appropriate archive file (6.3.0.6-TIV-ITM_LINUX-IF0004.tar
or .zip) to the IBM Tivoli Enterprise Monitoring Servers,
Tivoli Enterprise Portal Servers, and Tivoli Enterprise Portal
Desktops.

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. Expand the archive file (klz_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 LINUX 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. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On LINUX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

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

where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java on your system might vary.

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you 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 Portal Desktop (TEPD)

Continue through the remaining GUI panels selecting the product
06.30.06.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.

7. Note that the version reported by cinfo command for the TEP Browser
(TEPB/tpw) App Support component will not be updated by the itmasi tool.

B. Exploiting the Self Describing Agent (SDA)

1. In order to exploit this method SDA needs to be enabled on the agent,
on the R-TEMS and on the HUB-TEMS. SDA is enabled by default on all
components, but the HUB-TEMS. In order to enable it on the HUB-TEMS, if
not already enabled, set KMS_SDA=Y in its environment and restart it.
This is the only possible server restart required by this method, as
opposed to the multiple restarts of each server required during the
ASI install.

2. Double check SDA status is ON through command

> tacmd listsdastatus

Hub/RTEMS State Status
<HUB_name> ON 0
<RTEMS_name> ON 0


3. Enable SDA for this Interim Fix through command

> tacmd addsdainstalloptions -t lz -v 06300604

KUICO2054I: No configuration options were found for the specified
type(s). The following options will be created:

PRODUCT VERSION
LZ 06300604

Are you sure you want to update the selected options? Type Y for yes.
Type N for no.
Y

KUIAIO150I: The selected SDA configuration options records were
successfully updated.

4. Double check required SDA install options are in place

> tacmd listsdainstalloptions

KUILIO200W: No default SDA installation settings exist.

PRODUCT VERSION
LZ 06300604

5. You need at least one agent upgraded to this Interim Fix level running
in this HUB environment. In a few moments from its startup all the needed
support files will be propagated from the agent to the servers.

6. Double check the seeding of the support files has successfully completed
(STATE=IC Installation Complete)

> tacmd listappinstallrecs

HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
<HUB_name> LZ 06300604 5655 TMS 06300604 Y IC 0
<RTEMS_name> LZ 06300604 5655 TMS 06300604 Y IC 0

7. Note that the version reported by cinfo command for the TEP Desktop
(TEPD/tpd) App Support component will not be updated by the SDA method.


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.30.06.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 May 16 03:01:21 EST 2016 ******************
User : root Group: system bin sys security cron audit lp
Host name : candle Installer Lvl:06.30.06.00
CandleHome: /data/rthan/fp1temsteps
***********************************************************
...Product inventory
.
.
.

lz Monitoring Agent for Linux OS
li6263 Version: 06.30.06.04

.
.
.
2. To verify the agent support files were updated correctly run the cinfo
command on a Unix/Linux server, or the kincinfo command on Windows server,
and check LINUX OS Support version.

Sample output of the kincinfo command on a Windows System
---------------------------------------------------------

kincinfo -t lz
********** Friday, July 1, 2016 7:02:03 PM **********
User : Administrator Group : NA
Host Name : WIN2K3SP2-32BIT Installer : Ver: 063004000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory


PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

LZ TEMS App Support/Monitoring Agent for LINUX OS WICMS 06.30.06.04 201410140000 20141014 1101
LZ TEPS App Support/Monitoring Agent for LINUX OS WICNS 06.30.06.04 201410140000 20141014 1101
LZ TEPB App Support/Monitoring Agent for LINUX OS WIXEB 06.30.06.04 30241 20130624 1101
LZ TEPD App Support/Monitoring Agent for LINUX OS WIXEW 06.30.06.04 201410140000 20141014 1101

7.0 Known problems and workarounds
==================================
1. It can happen that the installation of this Interim Fix fails while
adding the agent supports for TEMS and TEPS if using Java 1.7,
giving an error as below:

"The wizard cannot continue because of the following error: could not
load wizard specified in /wizard.inf (104)
Trace log location: C:\Users\ADMINI~1\AppData\Local\Temp\2"

When this issue occurs, please choose another version for Java (JRE)
installed on the machine for running the setup.jar file.
Java version 1.5 or 1.6 are suggested

2. The Application Support Installer may fail to stop the Tivoli Enterprise
Monitoring Server, or the Tivoli Enterprise Portal Server, within the
timeout. The agent support update process does not proceed in such a case.
To avoid this issue it is suggested to manually stop the Tivoli Enterprise
Monitoring Server and/or the Tivoli Enterprise Portal Server before starting
the Application Support Installer.




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.