IBM Tivoli Monitoring: CEC Base Agent 6.2.2.1-TIV-ITM_CEC_BASE-IF0004

Download Description

Copyright International Business Machines Corporation 2011.
All rights reserved.

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

Component ID: 5724C04CB

Interim Fix 0004, 6.2.2.1-TIV-ITM_CEC_BASE-IF0004

Date: October 3, 2011

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.


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

2.1 APARs
---------------
APAR: IV08103
Abstract: 6.2.2.1-TIV-ITM_CEC_BASE-IF0003 cores on VIOS 2.2.0.0 or
2.2.0.11 FP24 SP1
Additional information: After installing Interim Fix
6.2.2.1-TIV-ITM_CEC_BASE-IF0003 on the VIOS (Virtual I/O
Server) V2.2.0.0 or V2.2.0.11 FP24 SP1, the cecDataProvider
process might core with the following stack:

Segmentation fault in strncpy.strncpy at 0x100102a4 ($t2)
0x100102a4 (strncpy+0xe4) 8d240001 lbzu r9,0x1(r4)
(dbx) where
strncpy.strncpy() at 0x100102a4
getSecondaryHMC()
unnamed block in getHMCaddressV6()
getHMCaddressV6()
gather_hmc_info(arg = (nil))

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

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

2.4 Superseded fixes
---------------------
6.2.2.1-TIV-ITM_CEC_BASE-IF0003
6.2.2.1-TIV-ITM_CEC_BASE-IF0002
6.2.2.1-TIV-ITM_CEC_BASE-IF0001

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

6.2.2.1-TIV-ITM_CEC_BASE-IF0003
-----------------------------------
APAR: IV02388
Abstract: SOME OF THE MACHINE IDS ARE IN LOWER CASE, CAUSING PROBLEM
FROM TCR MERGE
Additional information: When running the Tivoli Cognos Reporting (TCR)
reports, some dimensions of the Central Electronics Complex
(CEC) table do not match properly because some machine ids
are in upper case and some in lower case. This causes a
problem with TCR merge.

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: IV03965
Abstract: HMC FAILOVER DOES NOT WORK ON VIOS 2.2.0.12 FP24 SP2
Additional information: VIOS 2.2.0.12 FP24 SP2 requires APAR IV01286
in order to configure the agents with the cfgsvc command.
The cfgsvc command will now have a new parameter,
"second_managing_system", to define optionally a secondary
Hardware Management Console (HMC) host name to be used by the
agent to fail over to the secondary HMC.

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.

6.2.2.1-TIV-ITM_CEC_BASE-IF0002
-----------------------------------
APAR: IZ99289
Abstract: CEC AGENT DOESN'T DISPLAY DATA IF RUN AS NON-ROOT AND
STARTED FROM TEPS.
Additional information: If the agent is installed with a non-root
user ID, then the agent does not return data when remotely
started from the Tivoli Enterprise Portal.

APAR: IZ96832
Abstract: 1) INCLUDE ONLY THE SHARED LPARS IN THE SHARED POOL
CALCULATION
2) HANDLE THE DIFFERENCE BETWEEN PHYS POOL AND VIRT SHARED
POOLS
Additional information: The calculation of "CPU Shared Pools" attribute
includes both shared LPARs and non-shared LPARS. Also, the
"Maximum Pool Capacity" attribute is incorrectly calculated
on IBM System p5 hardware.

6.2.2.1-TIV-ITM_CEC_BASE-IF0001
-----------------------------------
APAR: IZ87110
Abstract: SYSTEM DIRECTOR LINK DISABLED
Additional information: The System Director link from the CEC
Resource Inventory view is sometimes disabled.

APAR: IZ86443
Abstract: CEC AGENT DISPLAYS DIFFERENT AVAILABLE CPU UNITS IN POOL
VALUE FROM TOPAS
Additional information: The agent displays a different value for
the "Available CPU Units in Pool" attribute value than the
topas command shows for APP values. This occurs with the
topas command from the latest bos.perf.tools fileset (for
example, 6.1.4.5).

APAR: IZ76024
Abstract: DATA PROVIDER FAILS TO CONNECT TO AGENT SOCKET
WITH ERRNO=78 WHEN XPG_SUS_ENV=ON
Additional information: When the environment variable XPG_SUS_ENV=ON,
the data provider does not connect to the agent, and the
Tivoli Enterprise Portal does not display any data for this
agent.
The <hostname>_px_aixDataProvider-61_<timestamp>.log file
contains the following messages:
---
clientsocket.cpp,124,"ClientSocket::open")
Unable to connect to TCP socket for port 62115, errno=78 - retrying....
clientsocket.cpp,133,"ClientSocket::open")
Unable to connect to TCP socket, errno=78 - retry count exceeded.
---
The problem occurs because setting XPG_SUS_ENV=ON forces
the tcp kernel to use a higher backlog than the agent
specifies when calling listen() with a backlog of 0. When
the data provider calls connect(), it fails because the
agent listen() call does not have enough queue depth to
accept the connection.


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.

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
--------------------------------
The prerequisite level for this fix is as follows:

IBM Tivoli Monitoring: CEC Base Agent, Version 6.2.2 Interim
Feature 1.

The above release is available from Passport Advantage. For details,
see the Support Wiki:

https://www.ibm.com/developerworks/wikis/display/tivolimonitoring/System+P+Agents


4.0 Image directory contents
===================
This fix image contains the following files:
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004.README - This README file
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004.tar - Fix archive .tar format
- 6.2.2.1-TIV-ITM_CEC_BASE-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 files:
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004/kpkaix523.dsc
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004/kpk_aix523_tema_if0004.tar
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004/pk_dd.properties
- 6.2.2.1-TIV-ITM_CEC_BASE-IF0004/pk_dd_062201004.xml


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.1-TIV-ITM_CEC_BASE-IF0004.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 of 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.1-TIV-ITM_CEC_BASE-IF0004, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.2.1-TIV-ITM_CEC_BASE-IF0004/kpk_aix523_tema_if0004.tar

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.2.1-TIV-ITM_CEC_BASE-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 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.1-TIV-ITM_CEC_BASE-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.1-TIV-ITM_CEC_BASE-IF0004

On Windows systems,
if the fix was expanded to <TEMP>\6.2.2.1-TIV-ITM_CEC_BASE-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.2.2.1-TIV-ITM_CEC_BASE-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.

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 062201004

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 062201004

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 an "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
========================

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


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


8.0 Additional product information
======================
None.


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 are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
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.

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.