IBM Tivoli Monitoring Agent Builder Interim Fix 01 6.3.0-TIV-ITM_ABLDR-IF0001

Download Description

Copyright International Business Machines Corporation 2014.
All rights reserved.

Component: IBM® Tivoli® Monitoring Agent Builder, Version 6.3.0

Component ID: 5724C04BR

Fix: 0001, 6.3.0-TIV-ITM_ABLDR-IF0001

Date: July 1, 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: IV60493
Abstract: SELINUX AUDIT LOG MESSAGES GENERATED WHEN USING IPV6 WITH
LOG AGENT
Additional information: On v6.3 and prior releases, a custom log
agent on a Security-Enhanced Linux® (SELinux) system using
IPv6 with the SELinux security policy set to "enforcing"
generates audit messages similar to the following in the
SELinux audit log /var/log/audit/audit.log:

type=AVC msg=audit(1389964628.602:213): avc: denied { write }
for pid=8121 comm="ifconfig" path="/opt/IBM/ITM/auditlogs/itm.
<hostname>_lz_audit.log" dev=dm-5 ino=4660
scontext=system_u:system_r:
ifconfig_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=file
type=AVC msg=audit(1389964628.613:214): avc: denied { write }
for pid=8126 comm="ifconfig" path="
/opt/IBM/ITM/logs/<hostname>_lz_klzagent_52d92647-01.log"
dev=dm-5
ino=5066 scontext=system_u:system_r:ifconfig_t:s0
tcontext=system_u:
object_r:usr_t:s0 tclass=file

APAR: IV58699
Abstract: MIB IS NOT LISTED AFTER PARSING IN THE SNMP EVENTS MIB
BROWSER
Additional information: When using the Management Information Base
(MIB) browser to create SNMP Event Information, the Agent
Builder does not give any warning or error if the trap uses a
name that is not properly defined according to the ASN.1/SMI
specification and is unresolved. The MIB also does not show up
in the resulting list of MIBs. For example, if an Enterprise
name starts in upper case.

This is affected by the Preference setting for MIB Parsing:
"Allow values to begin with upper case letters".

The traceKQZ.log in the .metadata\tivoli\KQZ\logs directory
of the workspace shows:
<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - Parse error at line 291, column 1

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... the parser encountered <Name> but was
expecting a token starting with a lowercase letter

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... object identifier values must start
with a lowercase letter according to the ASN.1/SMI specification

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... allowed because of -allowUppercaseValues
override

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - Parse error at line 137, column 29

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... the parser encountered <Name> but was
expecting a token starting with a lowercase letter

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... enterprise IDs must start with a
lowercase letter according to the ASN.1/SMI specification

<timestamp> - MIN - - ModalContext - ....util.ToolkitPrintStream.
System.err - ... allowed because of -allowUppercaseValues
override
. . .
--------

APAR: IV55816
Abstract: AGENT CRASH ON SOLARIS WHEN MOVING DATA TO ATTRIBUTE BUFFERS
Additional information: A custom log agent crashes on Solaris when
data in the log file matches the filter criteria and the data
is parsed into attributes that are numbers. This only occurs
when the data that is being placed into the numeric attributes
does not fall on a word boundary. A core file is created. The
core shows the process is terminated on a SIGBUS signal.

With a minimum of KBB_RAS1: ERROR (UNIT:kumpdpda ALL) (UNIT:
kumpmdba), the agent log <hostname>_<pc>_k<pc>agent_<timestamp>.log
where <pc> is the agent product code, might end with trace
entries similar to the following, when processing a log line
that triggers an event:
- - -
...
...:kumpmdba.c,142,"KUMP_MoveDataFromBufferToAttr")
Exit: 0x1
...
...
...:kumpdpda.c,92,"KUMP_DoDPdataToDCH") Getting
SourceAttrLockSEptr 100741680 local file
/ITM/Custom/config/K90_EVENT_LOG_FILE
- - -

APAR: IV54960
Abstract: SNMP AGENT CRASHES IF SNMP RESPONSE IS EMPTY
Additional information: An SNMP agent crashes when the SNMP
response received contains no varbinds, that is an empty
varbind list. For example below, the '00' indicates the
VarBindList is 0 bytes long, thus it contains no OID and
value.
This problem was found on Agent Builder v6.3 but it is not
release or platform dependent.

With tracing set to a minimum of KBB_RAS1 = ERROR (UNIT:snmp
ALL),entries similar to the following are seen at the end of
the agent log <hostname>_<pc>_k<pc>agent_<timestamp>-0n.log
where <pc> is the agent product code:
. . .
<timestamp>:snmp_print.c,1165,"snmp_log_message")
================ Begin Response Dump Info ===============
+<timestamp> 30 1c 02 02 00 00 04 06 70 75 62 6c 69 63 a2 0e
0....... public..
+<timestamp> 02 02 00 02 02 02 00 00 02 02 00 00 30 00
........ ....0. !!
+<timestamp>
+<timestamp> version: SNMPv1
+<timestamp> community: public
+<timestamp> PDUtype: GetResponse ('a2'h)
+<timestamp> request: 2
+<timestamp> error-status: noError (0)
+<timestamp> error-index: 0
+<timestamp>
+<timestamp> ===================== End Dump Info
=====================
. . .
. . .
<timestamp>:snmpqueryclass.cpp,1555,"handle_snmp_response_async")
Processing OID
<timestamp>:snmphelp.c,439,"snmpGetVarBind") Entry
<timestamp>:snmphelp.c,468,"snmpGetVarBind") Exit: 0x0
<timestamp>:snmphelp.c,249,"snmpGetOID") Entry
----------------------------------------------------------------

APAR: IV50345
Abstract: DISPLAY NON-ASCII CHARACTER PROPERLY FOR SNMP TRAPS IN
HISTORICAL VIEWS USING SNMP DISPLAY HINT.
Additional information: Using a DisplayHint of 255a, an agent
builder agent displays the data properly in the Realtime
data in the portal but the historical data does not
display properly.

For example, with the RealTime data "verifichèrò", where è
and ò are the non-ASCII character, it is shown correctly.
However in the historical data, the hex data is shown.

APAR: IV49650
Abstract: FULL AGENT TEST FAILS DUE TO MISSING SUBNODE CONFIGURATION
Additional information: An Agent Builder agent that has subnode
specific configuration fails to collect data in full agent
test, due to missing configuration information at the subnode
level. Using full agent test to test an agent which defines
more than one subnode type, and more than one of the subnode
types defines the same configuration property at the subnode
level (not at the agent level), then the configuration
property which is defined for both subnodes, is only created
in the first subnode instance, not in the agent or other
subnode instance. Therefore only the one subnode with all
the configuration properties defined, returns data and can be
tested successfully.

The <Subnode>_Performance_Object_Status shows an Error_Code
which varies based on how the missing configuration information
is used.

For example: The <hostname>_<pc>.cfg file in
%temp%\KQZ_....\tmaitm6 contains

FULL_CONFIG INSTANCE= [ SECTION=TestSection [ { SNMP_PORT=161 }
{
SNMP_VERSION=snmpV1 } {
SNMP_COMMUNITY=\{AES256:keyfile: .... } ]
SECTION=INT:TestSubnodeInstance [ { K14_INTERFACEDATA=k }
{ SNMP_HOST=rock.ibm.com } ]
SECTION=SyD:TestSubnodeInstance [ { K14_SYSTEMDATAVALUE=e } ]]

The configuration property SNMP_HOST is only defined in the
INT:TestSubnodeInstance sub-section which is the one subnode
that works. SNMP_HOST is not defined at the agent level or
in the SyD:TestSubnodeInstance.

This problem occurs on Agent Builder v6.3 and is platform
independent.

APAR: IV49322
Abstract: AGENT BUILDER UNABLE TO BROWSE AND PROCESS SOAP REQUEST
FROM ORCHESTRA WEB SERVICE AND TOMCAT APPLICATION SERVER
Additional information: Agent Builder v6.3 does not process SOAP
requests properly from Orchestra Web Service. It is unable to
show data from Browser/Testing for this type of SOAP request.

APAR: IV48801
Abstract: SECURE SHELL AGENT FAILS TO START DUE TO LIBSSH2
INITIALIZATION ERROR WITH GSKIT V8.
Additional information: A secure shell agent created with Agent
Builder v6.3, fails to start, due to libssh2 initialization
error with GSKIT v8. The agent fails to start and might
generate a core file.

This only occurs when you are using an authentication method
without a password, that is, public key without a password.
Password authentication works and public key with password
works.

With a minimum of KBB_RAS1: ERROR, the agent log
<hostname>_<pc>_k<pc>agent_<timestamp>.log where <pc> is the
agent product code, ends with trace entries similar to the
following:

<timestamp>:sshconnector.cpp,339,"SshConnector") Preparing to
load shared library libk95ssh-gsk8.so
. . .
<timestamp>:sshlibinterface.cpp,96,"Ssh_Interface_load") Entry
<timestamp>:sshlibinterface.cpp,487,"Ssh_Interface_load")
Warning: Unable to find a dynamic library entry point for
libssh2_set_exit_status
<timestamp>:sshlibinterface.cpp,535,"Ssh_Interface_load") Exit:
0x0
<timestamp>:kbbssge.c,52,"BSS1_GetEnv")
ICCRTE_DIR="/opt/IBM/ITM/lx8266/gs"
<timestamp>2-1:libgsk7icc.c,1105,"icc_encryption_init") Failed
to properly initialize GSKit's ICC (rc = 4.2)
<timestamp>:session.c,536,"libssh2_session_init_ex")
libssh2_session_init() failed to initialize cryptography engine
rc=-2.
<end of log>

APAR: IV46785
Abstract: COLLECT DATA IN TEST MODE FAILS FOR A MULTI-INSTANCE
AGENT WITH CONFIG ON UNIX
Additional information: Using the Agent Builder test or full agent
test function, "collect data" for a multi-instance agent
which requires configuration information fails on AIX and
Linux platforms. It fails because the configuration
variables are blank. The specific error depends on what the
configuration information is needed for.
The configuration file (.cfg) is not found because the .cfg
file is referenced as <hostname>_<pc>_$INSTANCE$.cfg where
<pc> is the agent product code and $INSTANCE$ is not resolved.
The cfg file is created as <hostname>_<pc>.cfg without the
instance name portion.
This problem does not exist in the run-time environment.

APAR: IV43445
Abstract: AGENT BUILDER AIX BINARY LOG TRUNCATES DESCRIPTION FIELD
AT SPACE FOR ERRPT
Additional information: An agent which monitors "Logged data" for
"AIX Binary Log" truncates the "Description" attribute at the
first space of the Description field, if one exists. This
behavior is triggered by editing the Description attribute
in the builder.

APAR: IV43014
Abstract: PAGE TITLE VALUE DISPLAYS WRONG CHARACTER WHEN CHARSET IS
UTF8 AND HTML TITLE IS NOT ENGLISH
Additional information: Non-English characters in the HTML Head
Title are not displayed in the correct character set.

APAR: IV42752
Abstract: AGENT IS NOT INSTALLED CORRECTLY IF SPACE IN INSTALL
DIRECTORY
Additional information: When an Agent Builder agent is extracted
into a directory with a space, it appears to install
successfully but it is not installed properly.

For example, "my k06" directory:
C:\my k06\>installIraAgent.bat c:\IBM\ITM
Installing agent into c:\IBM\ITM
Installing K06 .....
Install of K06 Agent successful.

kincinfo -i returns "NOVALUE" for the agent:
C:\IBM\ITM\BIN>kincinfo -i
************ Friday, August 23, 2013 1:19:31 PM *************
User : user Group : NA
Host Name : DDRZ Installer : Ver: 062301000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
...
NOVALUE NOVALUE
WINNT Version: 0N.OV.AL.UE Build: NOVALUE
...

This problem occurs on Windows® platforms only with Agent
Builder v6.3 and earlier.

APAR: IV42343
Abstract: UNABLE TO ADD MULTIPLE LOG FILES TO BE MONITORED
Additional information: When creating an Agent Builder agent to
monitor more than one log file, the additional files are not
added to the list of monitored files. On the Advanced Data
Sources Properties page, File Information tab, clicking the
Add button to specify additional files, the file appears to
be added. When returning to the Advanced Data Sources
Properties page, File Information tab, the additional files
are no longer listed. Only the first file in the list remains.

When the agent is generated and installed, only the initial
file is monitored.

APAR: IV41218
Abstract: AGENT TEST FAILS TO START DUE TO MISSING MFC71U.DLL
Additional information: On some Microsoft Windows systems, the
Agent Builder test function fails to start the agent because
the MFC71U.dll is missing in the system path and from the
%TEMP%\KQZ_<timestamp>\tmaitm6 directory.

The "Start agent" button results in the pop-up:
kxxagent.exe - System Error: "The program can't start
because MFC71U.DLL is missing from your computer. Try
re-installing the program to fix this problem."

This problem occurs on Agent Builder v6.3 and 6.2.3.1 on
Windows systems. This can occur, for example, when the IBM
Tivoli Monitoring infrastructure is not installed on the
system.

2.2 Defects
--------------

Defect: 210358
Abstract: HTTP provider fails with NullPointerException when host
not found.

Defect: 207939
Abstract: Java CPCI - deadlock due to bad lock usage in some
versions of Java® runtime.
Additional information: Classloading and resource loading are
grabbing locks in wrong order and causing a dead lock.

2.3 Superseded fixes
-------------------------
None.

2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------
None.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring Agent Builder User's Guide, version 6.3.0.

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

IBM Tivoli Monitoring V6.3.0 Agent builder, which is available
from PassPort Advantage under the following eAssembly:

* IBM Tivoli Monitoring V6.3.0 Agent Builder, English,
Multiplatform (CIGM4EN)
* IBM Tivoli Monitoring V6.3.0 Agent Multiplatform Multilingual
eAssembly (CRLF3ML).


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

- 6.3.0-TIV-ITM_ABLDR-IF0001.README - This README file
- 6.3.0-TIV-ITM_ABLDR-IF0001.tar - Fix archive .tar format
- 6.3.0-TIV-ITM_ABLDR-IF0001.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® environment; use the .zip file
if you are working in a Windows environment.

The fix archive file contains the following files:
- plugins/com.ibm.tivoli.monitoring.agentkit_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.AgentGenerator_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.AgentGenerator.runtime_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.agentkit.provider.jmx_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.agentkit.provider.log_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.agentkit.provider.snmp_6.3.0.v201406241513.jar
- plugins/com.ibm.tivoli.monitoring.agentkit.native_6.3.0.v201302201339/os/win32/x86/mfc71u.dll

Notes:
1. The com.ibm.tivoli.monitoring.agentkit.native_6.3.0.v201302201339
directory is merged with the existing directory.

2.The plugins contained in this fix are not removed when the
builder is uninstalled. They must be manually removed.

5.0 Installation instructions
==================
This fix applies to an Agent Builder, version 6.3.0 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.

- Stop the builder, if it is currently running.

5.2 Agent Builder update
--------------------------
1. Transfer the appropriate archive file 6.3.0-TIV-ITM_ABLDR-IF0001.tar
or .zip to the directory where the Agent Builder to be updated is
installed. The default installation location on Windows systems is
"C:\Program Files\IBM\ITM\AgentBuilder" and on UNIX systems, it is
"/opt/IBM/ITM/AgentBuilder".

2. Expand the archive file in to the Agent Builder installation
location using the tar command on UNIX systems or an extract
utility on Windows systems, such that it expands directly to the
builder installation directory. This installs the fix in the
plugins directory.

The plugins directory now contains the new jar files listed in
section 4.0 "Image directory contents".

3. If the builder was running when the update was installed, you may
restart the builder.

4. Use the Generate Agent Wizard to regenerate your agents and then
re-install the agent.

5.3 Agent support update
------------------------------
There are no Agent Builder changes which affect agent support files
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.


6.0 Additional installation information
========================

6.1 Verifying the update
----------------------------
1. In the builder, select Help->About IBM Tivoli Monitoring Agent
Builder and select the "Installation Details" button. Select the
Plug-ins tab. Click on the Version column header to sort in
descending order. The top entries are:

1. Plug-in Name: IBM Tivoli Monitoring Agent Builder
Version: 6.3.0.201406241513
2. Plug-in Name: IBM Tivoli Monitoring Agent Generator
Version: 6.3.0.v
3. Plug-in Name: IBM Tivoli Monitoring Agent Generator Runtime
Version: 6.3.0.v201406241513
4. Plug-in Name: JMX Data Provider
Version: 6.3.0.v201406241513
5. Plug-in Name: JMX Data Provider
Version: 6.3.0.v201406241513
6. Plug-in Name: SNMO Data Provider
Version: 6.3.0.v201406241513

2. To verify Agent Builder was updated correctly, the header of
most newly generated text based agent files contain a few similar
lines with a timestamp of "201406241513":

. . .
<!-- IBM Tivoli Monitoring Agent Generator 6.3.0 v201406241513-->
<!-- IBM Tivoli Monitoring Agent Generator Runtime 6.3.0 v201406241513-->
. . .

3. To verify the agent you are running contains the updates from the
fix, see the following lines in the agent log
<hostname>_<productCode>_<instance>_k<productCode>agent_<timestamp>.log:
located in $CANDLEHOME/logs on UNIX systems and
%CANDLE_HOME%\tmaitm6<_x64>\logs on Windows systems.

<timestamp> Component: ira
<timestamp> Driver: 201406241513/...
<Timestamp> Timestamp: Jun 24 2014 15:35:33

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 states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
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.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.