README documentation for IBM Tivoli Monitoring for Version 6.2.2 Fix Pack 4 including installation-related instructions, prerequisites and corequisites, and list of fixes.
README file for: IBM Tivoli
Monitoring
Product/Component Release: 6.2.2
Update Name: Fix Pack 4
Fix ID: 6.2.2-TIV-ITM-FP0004
Publication date: 08 April 2011
Last modified date: 08
April 2011
Download location
Prerequisites and corequisites
Known issues
Known limitations
Installation information
Prior to installationAdditional Information
Installing
Performing the necessary tasks after installation
Troubleshooting installation problems from the Support site
Download IBM Tivoli Monitoring Fix Pack 4 from the following
location:
http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Tivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.2.2-TIV-ITM-FP0004&source=fc
Alternatively, access the fix from the table below.
| Product/Component Name |
Platform |
File Name |
|---|---|---|
| IBM Tivoli Monitoring Base |
Windows |
6.2.2-TIV-ITM_TMV-Windows-FP0004 |
| IBM Tivoli Monitoring Base |
UNIX |
6.2.2-TIV-ITM_TMV-Unix-FP0004 |
| IBM Tivoli Monitoring Base |
Linux |
6.2.2-TIV-ITM_TMV-Linux-FP0004 |
| IBM Tivoli Monitoring Base Agents |
All |
6.2.2-TIV-ITM_TMV-Agents-FP0004 |
| IBM Tivoli Monitoring Tools |
All |
6.2.2-TIV-ITM_TMV-Tools-FP0004 |
| IBM Tivoli Monitoring Agent Reports |
All |
6.2.2-TIV-ITM-Agent-Reports-FP0004 |
For a complete set of prerequisites, refer to the "Hardware and
software
requirements" section in the IBM Tivoli Monitoring Installation and
Setup Guide Version 6.2.2 Fix Pack 2 available at the following URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/welcome.htm
The following issues have been found in a version of this release,
either in previous releases, or in this release. The symptom and the
workaround has been listed for each issue.
The following issues are unique to this fix pack.
Symptom:
Running the "migrate-export" or "migrate-import" command generates the following unexpected messages:
products/ITM/ls3263/cq/bin/KfwServices: /products/ITM/ls3263/iw/java/jre/bin/libjsig.so: no version information available (required by /products/ITM/ls3263/cq/bin/KfwServices)
/products/ITM/ls3263/cq/bin/KfwServices: /products/ITM/ls3263/iw/java/jre/bin/libjsig.so: no version information available (required by /products/ITM/ls3263/cq/lib/libKfwORBInit.so)
Workaround:
The messages are introduced by a change in JRE 1.5 and can be ignored.
Symptom:
The Oracle Agent version 6.21 is running on a Linux or UNIX system and an IBM Tivoli Monitoring agent or component on the system is to be upgraded to IBM Tivoli Monitoring 6.2.2 FP4.
Workaround:
The Oracle agent must be stopped and a recursive link removed before the upgrade is started for any of the IBM Tivoli Monitoring agents or components. . See the Install Actions for APAR IZ43658 for more details.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ43658
Symptom:
The Oracle Agent version 6.21 is running on a Linux or UNIX system and an IBM Tivoli Monitoring agent or component is being upgraded to IBM Tivoli Monitoring 6.2.2 FP4 and the following messages are displayed during the install:
runGSkit failure: Return error code: 2.
runGSkit failure: BACKUP ERROR: error while backing up sol286/gs.
Workaround:
If the install continues successfully, the messages can be ignored.
Symptom:
The "Tivoli Enterprise Build-level listing" output shows a backlevel version for the product codes "IW" and "UI".
Workaround:
This occurs on Windows only. Validate the versions for "IW" and "UI", if applicable, using the "kincinfo" command.
The following issues affect prior IBM Tivoli Monitoring Monitoring 6.2.2 fix packs and are still applicable to this fix pack.
Symptom:
Beginning with IBM Tivoli Monitoring Version 6.2.1 Fix Pack 3 and IBM Tivoli Monitoring Version 6.2.2
Fix Pack 3, the default port number for the Warehouse Proxy Agent was changed to 63358 for IP.PIPE/IP.UDP
and 65100 for IP.SPIPE. This change was done to make sure that the Warehouse Proxy agent listening port
is at the highest addressable port so no conflict can occur with other IBM Tivoli Monitoring components
using ports. Agents that export historical data to the Warehouse Proxy agent will switch ports and may fail to
export because the new port being used on the Warehouse Proxy agent machine is not open for connection.
Workaround:
Ensure the new default port number 63358 for IP.PIPE/IP.UDP or 65100 for IP.SPIPE is open for connection.
The following Technote contains more information on this change:
http://www-01.ibm.com/support/docview.wss?uid=swg21469499
You can verify that port 63358 for IP.PIPE/IP.UDP or 65100 for IP.SPIPE was established by the Warehouse Proxy agent by following the instructions found in the following Technote below "Confirming the Warehouse Proxy Agent Listener port from the Command Line":
http://www-01.ibm.com/support/docview.wss?uid=swg21315085
Symptom:
During the installation of an agent, administrators may get a pop up warning that the certificate the software has been signed with has expired. IBM Tivoli Monitoring 6.2.2 Fix Pack 2 packaged a new certificate with the infrastructure and agents. The pop up can occur when installing agents that have not been packaged with the new certificate.
Workaround:
Accepting the certificate will allow the installation to continue.
Symptom:
When IBM Tivoli Monitoring and OMNIbus event synchronization is installed, status changes to IBM Tivoli Monitoring events originating from either IBM Tivoli Monitoring or OMNIbus result in the Severity and Summary of the events in OMNIbus being incorrect.
Workaround:
The following Technote contains more information on resolving the issue: http://www-01.ibm.com/support/docview.wss?uid=swg21428227
Symptom:
On UNIX and Linux platforms for the Warehouse Proxy Agent, when the Warehouse Proxy Agent
is stopped it may create a core file. This core file is located in the directory where the
agent was started. The core is a failure of the Java Virtual Machine (JVM) SR11 version shutdown process. This problem was introduced in SR11. The stopping of the Warehouse Proxy
agent completes correctly and no side affect from the core causes any problems other than the
space required for core file. This problem has been reported to the IBM JVM group and APAR IZ84541 has been opened. This APAR is scheduled to ship in SR13.
Workaround:
The use of the java argument: -XXallowvmshutdown:false can be used in the hd.ini file to
revert the shutdown process to the old method prior to SR11. Set the following parameter
in the hd.ini file:
KHD_JAVA_ARGS=-XXallowvmshutdown:false
Refer to JVM APAR IZ59734 available at the following URL for additional information:
http://www.ibm.com/support/docview.wss?uid=swg1IZ59734
Symptom
On a Windows 64-bit endpoint, ITM will support the coexistence of both 32-bit
and 64-bit agents. However, in order to support this coexistence, a new
bundle which is the Agent Compatibility Package (AC), has been created. This
Agent Compatibility Package contains both the 32-bit and 64-bit Agent
Framework libraries. The issue may be diagnosed by examining the ITM
Installation Log for the associated agent deployment. You will find a failure
like the following: RC_INFO: The Agent Compatibility Package in version
06220100 is required but unavailable. Affected platforms are Windows 64-bit
at V6.2.2 Fix Pack 1 or later level.
Workaround:
The AC package (which can be found in the base ITM agents CD image) will need
to be added to the depot and the agent redeployed. Refer to this Technote for information and guidelines:
http://www.ibm.com/support/docview.wss?uid=swg21427756
General information about installing the Agent Compatability component can
be found in the Installation and Setup Guide:
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp2/win_instma.htm
Symptom:
When using the Agentless Monitor for Windows, and the instance is configured
to use Windows API Connection to monitor a domain controller running Windows
Server 2003, excessive CPU on the domain controller is used. This problem can occur only when the Windows API Connection (WMI) is
configured and does not apply when the SNMP Connection is configured for the
instance.
Workaround:
Microsoft has a hotfix available for this problem which should be
installed on the domain controller:
http://support.microsoft.com/kb/933593
Refer to this Technote for information and guidelines:
http://www.ibm.com/support/docview.wss?uid=swg21430280
Symptom:
On zLinux, an upgrade of the OS Agent to the Fix Pack 2 or later level will result in the
Agent Management Services watchdog utility being turned off regardless of whether it was active or inactive
prior to the upgrade. On Intel Linux and other supported platforms, the Agent Management Services watchdog utility defaults to "enabled".
Workaround:
To enable the watchdog utility, edit the lz.ini file and comment out the line "KCA_CAP_DIR=" and uncomment the line that starts with "KCA_CAP_DIR=$CANDLEHOME$". For example:
# PAS Off
# KCA_CAP_DIR=
# PAS On
KCA_CAP_DIR=$CANDLEHOME$/$BINARCH$/$PRODUCTCODE$/bin/CAP:$CANDLEHOME$/config/CAP:/opt/IBM/CAP
Symptom:
When uninstalling a multi-instance agent from a managed system that also has
an IBM Tivoli Monitoring version 6.2.2 Fix Pack 2 or later agent installed, instances are not
uninstalled, leaving an entry in the management server. This only occurs on the Windows
64-bit platform. Other IBM Tivoli Monitoring components running on the system
continue to operate normally.
Workaround:
Remove the agent instances first and then uninstall the agent. If the agent
was already uninstalled, you can re-install the agent again, remove the
instances, and then uninstall the agent again.
Symptom:
Some versions of the Korn Shell (ksh) that are newer than the Public Domain
Korn Shell (pdksh) have changed the behavior of typeset -i. Current
versions of the IBM Tivoli Monitoring installer for all IBM Tivoli
Monitoring release families; 6.1, 6.2, 6.2.1, 6.2.2, have all been modified
to function correctly with this change. However, there are still some IBM
Tivoli Monitoring application agents in the field that are still based on a
version of the installer that has not been updated to function correctly with these newer ksh shells. Installing these older application agent
releases can potentially back-level the installer and itmcmd tools.
Workaround:
Before installing, see the Flash note #1408506 titled, "Newer ksh shell may
allow regression of ITM installation" available at the following URL for
more information on diagnosing, preventing, and (if necessary) correcting
this problem.
http://www.ibm.com/support/docview.wss?uid=swg21408506
Symptom:
IBM Tivoli Monitoring JAR files are not downloaded to the browser portal
client due to JAR version differences before and after the year 2010.
The user does not get the expected updated JARs and the update function.
Workaround:
After applying IBM Tivoli Monitoring 6.2.2 Fix Pack 4, you can validate
your portal browser client is at the correct fix pack and maintenance
level as follows:
The following limitation is unique to this fix pack.
Symptom:
Situation does not fire when using the attribute "Process Filter" from the UNIX and Linux OS agents when the regular expression begins with a parenthesis ('(') or space.
Additional information:
The UNIX and Linux OS agents previously added support for long process names, requirement 1012. This included adding a new attribute "Process Filter" to both agents to define a regular expression to filter processes based on their full command line (Process Command(Unicode) on UNIX or Command Line on Linux) and return only a portion of the command line. When creating a situation for the "Process Filter", the regular expression cannot begin with parenthesis ('(') or space or the situation will not trigger correctly.
The following limitations were documented in the README for prior IBM Tivoli Monitoring 6.2.2 fix packs and are still applicable to this fix pack.
Symptom:
Executing the tacmd login -stdin option with missing standard input may cause looping or will not prompt user for the missing inputs.
Additional information:
For tacmd login and tepslogin, if -stdin option is used, and an echo is used to pass the parameters,
then all the mandatory parameters need to be passed in the echo.
The following example is valid:
echo "-s localhost -u userid -p password" | tacmd login -stdin
The following example is not allowed:
echo "-s localhost" | tacmd login -stdin
Symptom:
In rare cases, user custom settings are can be lost after applying an IBM Tivoli Monitoring fix pack. Please refer to the Technote below to see if you might be impacted by this and instructions on how to resolve it.
Additional information:
Refer to this Technote for information and guidelines:
http://www.ibm.com/support/docview.wss?uid=swg21307768
Symptom:
When running the KinCinfo command with –x as an option, an error appears in
the OS agent log when remote deploying agents in ITM V6.2.2 Fix Pack 1 environment.
Additional information:
No corrective action needs to be taken. The error message in this log is
harmless and may be ignored. Refer to this Technote for information and guidelines::
http://www.ibm.com/support/docview.wss?uid=swg21427753
Symptom:
The GUI of an executable file launched from executecommand can not be seen in
Remote Desktop, but can be seen in VNC.
Additional information:
This command is intended for executing short CLI based actions/commands on the
remote target. It should not be used to execute long running, GUI, or
interactive executables.
Before proceeding with the installation process, please make note of these important points:
| $ITMHOME | 800 MB |
| /tmp/ | 1200 MB |
Run the pdcollect utility to gather all of the current logs and environment files. These backups can be used for reference, if needed, after the upgrade. The "tacmd pdcollect -help" command can be issued to obtain the syntax for the pdcollect utility.
If using the ITMSuper tool, run the tool to take a snapshot of the entire ITM infrastructure prior to the install of this fix pack.
Run the pdcollect utility to gather all of the current logs and environment files. These backups can be used for reference, if needed, after the upgrade. The "tacmd pdcollect -help" command can be issued to obtain the syntax for the pdcollect utility.
Run the migrate-export.bat (Windows) or migrate-export.sh (UNIX/Linux) to backup the contents of the portal server database. This snapshot will allow for recovery of the database back to the point prior to installing this fix pack maintenance.
If using the ITMSuper tool, run the tool to take a snapshot of the entire ITM infrastructure prior to the install of this fix pack.
If using the ITMSuper tool, it is recommended to run the tool after applying the fix pack to create snapshot of the entire ITM environment that can be compared to the baseline snapshot taken with ITMSuper before the installation. The baseline snapshot can be done by selecting the Topology, Connectivity, and TEMS Servers tabs and saving the session. Information about the ITMSuper tool can be found at the following URL:
http://www-01.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TM6LYou can validate your installation by running the kincinfo command on
Windows
systems or the cinfo command on Linux or UNIX systems. If you run these
commands before and after your upgrade, you can clearly see the
component
versions that have changed.
For interim fixes, only components that have been updated during this
release
have the latest listed level. If a component has not been updated, the
package
will contain the most recent GA copy. There is no need to upgrade this
component if your system is at the listed level, the install programs
should
automatically handle this for you.
Note: The kincinfo and cinfo command output examples in the sections
that
follow show all components that can be updated. If you do not have all
of these
components installed, then components not installed will not be
displayed in
the output of these commands.
Note: The "Monitoring agent for UNIX Logs" agent name has been
deprecated.
Going forward, this agent will be named "UNIX Logs."
This fix pack contains baroc files at the level documented in the list below. If you have an earlier level installed you will need to reinstall them. Refer to this Technote for information and guidelines:
http://www.ibm.com/support/docview.wss?uid=swg21382506
| IBM Tivoli Monitoring Data Warehouse Agents | ||
|---|---|---|
| Warehouse Proxy | khd.baroc | 06.21.00.00 |
| Summarization and Pruning | ksy.baroc | 06.21.00.00 |
| IBM Tivoli Monitoring 6.x for OS Agents | ||
| Windows | knt.baroc | 06.22.04.00 |
| UNIX | kux.baroc | 06.22.04.00 |
| Linux | klz.baroc | 06.22.04.00 |
| i5/OS | ka4.baroc | 06.22.02.00 |
| UNIX Log Alert | kul.baroc | 06.21.00.00 |
| IBM Tivoli Monitoring 6.x for Agentless OS Agents | ||
| Windows | kr2.baroc | 06.22.02.00 |
| AIX | kr3.baroc | 06.21.00.00 |
| Linux | kr4.baroc | 06.21.00.00 |
| HP | kr5.baroc | 06.21.00.00 |
| Solaris | kr6.baroc | 06.22.01.00 |
For additional troubleshooting help not covered in this README document, please visit the IBM Tivoli Monitoring support page at the following URL:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Monitoring_V6
This is a cumulative fix pack for IBM Tivoli Monitoring, Version 6.2.2. This fix pack supersedes all previous IBM Tivoli Monitoring versions, including GA Version 6.2.2 and above. This fix pack can be installed in just one step on top of any level of IBM Tivoli Monitoring version 6.1, 6.2, 6.2.1 or 6.2.2.
The IBM Tivoli approach for fix packs and interim fixes is to deliver regular, incremental quality improvements.The main areas of quality improvements made in this maintenance deliverable relative to the most recently shipped IBM Tivoli Monitoring maintenance (IBM Tivoli Monitoring 6.2.2 Fix Pack 3) are shown below.
The following new features have been added in IBM Tivoli Monitoring 6.2.2 Fix Pack 4.
For details on features added in previous fix packs, see the "New in this release" sections of the documentation in the IBM Tivoli Monitoring 6.2.2 Information Center which can be accessed using the following URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/welcome.htm
| Agentless OS Monitor APARs | |
|---|---|
| IZ85034 |
In IBM Tivoli Monitoring 6.2.2 FP3, when configuring an Agentless Monitor for Solaris instance, some of the parameters are not collected, the port number and community name in particular. This causes an incomplete configuration which results in no data being collected by the agent. |
| IZ90489 |
The "Percentage of Used Space" attribute in the aixPysicalVolumeTable attribute group reports a negative or incorrect percentage. The problem also occurs on the "Percentage of Used Space attribute" in the aixVolumeGroupTable attribute group. |
| Command Line Interface APARs | |
| IZ85264 |
When using any of the various forms of the "tacmd bulkimportsit" command, if there are more than about 16 to 25 situations the command fails with no output appearing on STDOUT. This problem only applies to UNIX and Linux platforms. |
| Event Synchronization APARs | |
| IZ82307 |
An event that contains spaces in the situation display item results in the creation of random files in $OMNIHOME. When the event with spaces in the display item is acknowledged, cleared or deleted, files are created in $OMNIHOME due to the way eventcmd.sh is being called from the OMNIbus external procedure. The files contain what appeared to be SUF cache entries, and are named based on the part of the situation display item that occur before the first space. |
| IZ86248 |
The event synchronization installer incorrectly attempts to create the /etc/TME/TEC/OM_TEC directory, a directory needed for Tivoli Event Console event synchronization, but not for OMNIbus event synchronization. This fix enables users on Linux or UNIX (except AIX) to run the event synchronization installer under either a root or a non-root userid. When installing under a non-root userid, the userid will need to have write access to the event synchronization install directory. Users running on AIX must install under a root userid. |
| IBM Monitoring Agent for Linux OS APARs | |
| IZ83651 |
The Monitoring Agent for Linux OS shows a wrong format for the uptime attribute. |
| IZ83731 |
In the "Historical Summarized Availability Weekly" workspace, the availability values for the "Availability(weekly)" view, are approximately one fourth of the expected values. This is due to the fact that up time is divided by a monthly time period rather than a weekly one. |
| IZ84377 |
When the IBM Tivoli Monitoring environment has some 200+ agents, the following summary workspaces fail. The exact number will vary depending on the size of the managed system names. - "Linux Systems Overview", - "Windows SYstems", - "Enterprise UNIX Systems Summary" The Portal Client displays this error message: KFWITM217E Request error: SQL1_CreateRequest failed, rc=201 SQL1_DistReqError. |
| IZ86245 |
On Red Hat Enterprise Linux Server release 5.5 (Tikanga) the Monitoring Agent for Linux OS reports wrong information in OS Vendor Information field, because it contains the gcc version. |
| IZ95043 |
Linux OS Agent support for LPAR and Steal CPU metrics. A new set of attributes and a new workspace have been added to the Linux OS Agent to support LPAR and Steal CPU metrics. LPAR support includes collecting metrics such as entitlement, capacity weight, and shared pool idle time for the LPAR. This attribute group is only supported for Linux PPC on P5 or greater with the following minimum OS versions: RHEL 5.2 and SLES 10sp2. A new attribute, Steal CPU (Percent), has been added to the CPU attribute group which represents the time spent in involuntary wait by the virtual CPU while the hypervisor is servicing another virtual processor. This attribute is only supported for Linux PPC on P5 or greater with the following minimum OS versions: RHEL 5.2 and SLES 10sp2. The following Technote contains more information on the details of the attributes and workspace added to the agent for this support: http://www-01.ibm.com/support/docview.wss?uid=swg21462114 |
| IBM Monitoring Agent for Unix Logs APARs | |
| IZ79678 |
The ITM Monitoring Agent for UNIX Logs always shows at least one format error for the /var/adm/ras/errlog file even though the file format is correct, because it considers the file header not conforming to the line format. |
| IZ87563 |
After upgrading to 6.22 FP2, on AIX systems the Unix Log Agent (Kulagent) hangs at startup time. The agent will show up as offline on the portal client. |
| IBM Monitoring Agent for Unix OS APARs | |
| IZ76819 |
Add optional support for monitoring NFS filesystems for the UNIX and Linux OS agents. IBM Tivoli Monitoring UNIX and Linux OS Agents now optionally support monitoring file systems of the network file system (NFS) type for file systems where the OS agent is not installed on the system, but that are NFS mounted from systems where the OS agent is present. Previously NFS monitoring was not consistent across the agents: - UNIX OS agent on HP-UX and Solaris explicitly excluded NFS filesystems. - UNIX OS agent on AIX the NFS filesystems were disabled by default but could be enabled through an internal (not documented) environment variable. - Linux OS agent included NFS file systems. The following environment variable is introduced to enable and disable NFS monitoring at the agent. This environment variable has a default value "true" on Linux and "false" on UNIX, which reflects the previous behavior on the Linux OS agent. KBB_SHOW_NFS=true|false The environment variable "KBB_NFS_TIMEOUT" can be configured to tune the timeout. The default value for the environment variable is 2 seconds, with an valid range of 1-30 seconds. This environment variable applies to unreachable NFS filesystems, so that the agent can give up with them after the specified number of seconds. A new attribute named "File System Status" has been added to the UNIX and Linux OS Agents "Disk" attribute group and it will report: "Up" - normal case "Down" - timeout expired "Not Available" - error condition. The following Technote also documents this new support: http://www-01.ibm.com/support/docview.wss?uid=swg21460041. |
| IZ85281 |
Errors importing discovery library adapter (DLA) book with bonded interface cards. Channel or ethernet bonding provides a method for aggregating two or more network interfaces into a single logical-bonded network interface. They can share the same IP address and MAC address although the Interface name is different. When importing the output of the "tmsdla" command into Tivoli Application Dependency Manager (TADDM), in this configuration, the following errors appear in the bulkload.log: [main] ERROR bulk.CdbConfigniaClient - ObjectId unknown: FAILURE classtype |unknown| not written to the database. Attributes required for the naming rules of this object were not set. Set attributes are: Cannot identify failing object because of grouped write operations. 2010-09-03 16:03:24,713 [main] ERROR bulk.CdbRandomAccess - group write failure followed by 2010-09-03 16:03:30,008 [main] ERROR bulk.CdbConfigniaClient - External Relationship: monitors: FAILURE. The source of the relationship had no guid. The source class type was |app.TMSAgent| objectid |x35tst02:LZ-TMSAgent| The target class type was |sys.linux.Linux| objectid |128.147.33.87-OperatingSystem| 2010-09-03 16:03:30,008 [main] ERROR bulk.CdbRandomAccess - An external relationship: monitors could not be written. Processing continuing. |
| IZ85924 |
When the Agent Management Services watchdog utility invokes the "cinfo -r" command to determine if an agent is running and "cinfo" has a problem resolving the hostname, it can report that the agent is not running when it is. This will result in the watchdog utility restarting the agent each time it checks availability. |
| IZ88088 |
On UNIX machines the Monitoring Agent for UNIX OS kuxagent process generates a defunct process every time that it executes a situation using UNIX PING attribute group. |
| IZ88737 |
In the Agent's Runtime Staus workspace, when the watchdog utility is monitoring an agent, the workspace will show various data about the process including "Total Size", "Number of Threads", and "Parent Process ID" (Unix-only). If the agent is determined not to be running, the status and Process ID get reset. However, the other runtime values do not get reset and continue to display the values that were last collected. Once the agent is restarted the values get refreshed correctly. |
| IZ89532 |
When the Agent Management Services watchdog utility which part of the OS Agent issues a command to check the status of an agent, if command times out the utility does not release the file descriptor. This can result in the maximum number of open file descriptors being exceeded for the process, which will cause the agent to not be able to retrieve data properly. This can occur on either the UNIX or Linux OS agents. |
| IZ89693 |
On Solaris the kuxagent process for the Monitoring Agent for UNIX OS takes a very long time to collect Solaris zone information because it runs the "prstat" command for each zone and the command takes about 30 seconds to collect the information. |
| IZ89717 |
On HP 11.23 Itanium systems the Monitoring Agent for UNIX OS reports an incorrect number of CPUs installed on the machine and related metrics are incorrect also. |
| IZ89747 |
IBM Tivoli Monitoring OS Agent multi-system report in 1.3 does not return all the data in Internet Explorer browser (IE) due to the default "Maximum Hotspots" of 10,000 per chart (i.e. global value is not used). |
| IZ90193 |
The Monitoring Agent for UNIX OS kuxagent process can show a high CPU usage when it does UTF-8 conversions for the process attribute group. In order to improve IBM Tivoli Monitoring OS Agent performance, a new environment variable has been added in order to disable UTF-8 conversion of the 7-bit ASCII codepages to UTF-8. In order to enable this behaviour set the following key in the ux.ini file: KUX_SKIP_UTF8CONV_PROCESS=TRUE |
| IZ91032 |
The Watchdog component of the OS Agents for UNIX and Linux makes several calls to the "cinfo" command that can be eliminated. In particular, Watchdog calls "cinfo -r" regularly to determine if an agent process is running and calls "cinfo -o" to determine the instances configured for an agent. There are conditions where some of these calls can be eliminated. |
| IZ92564 |
When creating the Discovery Library Adapter (DLA) book to import into Tivoli Application Dependency Discovery Manager (TADDM) or Tivoli Business Service Manager (TBSM), if a UNIX system has a non standard serial number, the "tmsdla" command terminates with error 12 and the following message: Starting tmsdla.sh at Tue Dec 14 14:26:36 MET 2010 Errors found. Highest severity: 12 12: Row parsing exception. java.lang.String.substring(String.java:1067) com.ibm.tivoli.monitoring.tmsdla.kux.SerialNumber.parseValue (SerialNumber.java:55) com.ibm.tivoli.monitoring.tmsdla.RowParser.parseRow(RowParser.java: 208) com.ibm.tivoli.monitoring.tmsdla.QueriesIterator.getNextValues (QueriesIterator.java:146) com.ibm.tivoli.monitoring.tmsdla.CDMSectionHandler.outputCDMSection (CDMSectionHandler.java:207) com.ibm.tivoli.monitoring.tmsdla.TMSDLATemplate.processINODESTSRow (TMSDLATemplate.java:293) com.ibm.tivoli.monitoring.tmsdla.TemplateHandler. processManagedSystems(TemplateHandler.java:164) com.ibm.tivoli.monitoring.tmsdla.TmsDla.main(TmsDla.java:246)4: query #0 failed to parse Ending tmsdla.sh at Tue Dec 14 18:14:52 MET 2010 This results in the "tmsdla" command terminating and producing an inconsistent DLA book. |
| IZ92574 |
The UNIX OS Agent can hang on Solaris when trying to collect the machine serial number. This is due to the Remote Deply API used to execute commands on Solaris. |
| IBM Monitoring Agent for Windows OS APARs | |
| IZ76559 |
In the IBM Tivoli Monitoring historical data from DataWarehouse, the "Network Interface Instance" attribute of the "Network Interface" attribute group, contains corrupted data when the Instance is in traditional Chinese. |
| IZ77114 |
When in the monitoring environment there are machines with Windows 2000 operating system, the Discovery Library Adapter (DLA) book produced by the tmsdla command contains inconsistencies and cannot be loaded into Tivoli Application Dependency Discovery Manager (TADDM). The following error is displayed at the console. Bulk Load Program running. A parsing error occurred processing the xml file. The logs may contain more information. Return code is: 7 Inside the bulkload.log file the following error record is present: Invalid relationship entry located in file: <"relationship details"> where "relationship details" is indicating the failing entry in the DLA book which can be found in the DLA book below the entry: <!-- tmsdla\knt_tmsdla.xml --> |
| IZ88921 |
When displaying logical disks in the Tivoli Enterprise Portal or in the situations created to monitor them, the Monitoring Agent for Windows OS displays every logical disk listed by Perfmon. If the disk was mapped to a drive letter it will be identified by it, otherwise a label such as "HardDiskVolume#" is used. To support customers who want to filter out the disks identified as "HardDiskVolume#", an environment variable NT_EXCLUDE_UNMAPPED_DISKS is introduced. This variable can be configured in the KNTENV configuration file and can take the values: 0 (default) = HardDiskVolume# disks are monitored, if present. 1 = HardDiskVolume# labeled disks are not be monitored. For example, the following line, if added to the KNTENV file, will filter out the disks identified by the HardDiskVolume Labels. NT_EXCLUDE_UNMAPPED_DISKS=1 Note that the "Total" line, displayed by the portal client and monitored by the IBM Tivoli Monitoring agent, is not calculated by IBM Tivoli Monitoring but by Perfmon itself and, as such, it does include all the valid disks, including the HardDiskVolume labeled ones, also when the NT_EXCLUDE_UNMAPPED_DISKS variable is set to 1. |
| IZ91167 |
The Monitoring Agent for Windows OS displays a value of 212097034 for the attribute "Copy Read Hist %" from the NTCACHE attribute group when the Microsoft perfmon tool incorrectly returns a blank for the corresponding counter, cdrhpct. The attribute will now display a value of "Unavailable" for this condition. |
| IZ91182 |
A situation written using the Registry attribute group from the Monitoring Agent for Windoww OS is not triggering when it should and the agent trace logs contain the following error message: knt64agt.cpp,453,"Retrieve_AddData") Error retrieving registry data: rc=3 |
| IBM Tivoli Enterprise Monitoring Agent APARs | |
| IZ81476 |
IBM Tivoli Monitoring agents running on i5/OS platform report invalid IBM Tivoli Monitoring version if the agent CCSID is changed after the install. The "tacmd listsystems" command shows 'XX.XX.XX.XX' in the agent version field. |
| IZ84397 |
No data is displayed in the UNIX Log Agent "Monitored Logs" workspace when the agent is running on HP-UX and tracing includes "(UNIT:kra ALL)". |
| IZ85796 |
Calculation of sub-node length used memory subtraction using an integer that could overflow on 64-bit machines and be negative. This negative value causes the sub-node length to be greater than 32 bytes and thus the sub-node name is not found for situations or historical data collection processing. |
| IZ89282 |
When TakeSample method for an agent is called for an attribute and the TakeSample method abends, then the Tivoli Enterprise Monitoring Agent (TEMA) code exception handler fails to set the next expiration time for the situation. This results in an immediate expiration of the situation and thus a high CPU condition on the agent. The trace log is flooded with the following messages during a high CPU condition: (4C8FBF16.0046-D:kraafira.cpp,877,"DriveDataCollection") TakeSample call abended for ISOp_ZLX_space_ext2_Critical <3729785806,3064988586> on KLZ.LNXDISK, stopping request. (4C8FBF16.0047-D:kraafira.cpp,892,"DriveDataCollection") Stopped request failed, status = 210102bd (4C8FBF16.0048-D:kraafira.cpp,877,"DriveDataCollection") TakeSample call abended for ISOp_ZLX_space_ext2_Critical <3729785806,3064988586> on KLZ.LNXDISK, stopping request. (4C8FBF16.0049-D:kraafira.cpp,892,"DriveDataCollection") Stopped request failed, status = 210102bd |
| IZ93258 |
Agent stops responding to Agent Service Interface (ASI) requests after about four hours, when the ASI session is terminated due to inactivity timeout. |
| IBM Tivoli Enterprise Monitoring Installation APARs | |
| IZ79755 |
User customization applied to the file glb_site.txt are lost when a new IBM Tivoli Monitoring version or a new IBM Tivoli Monitoring fix pack are installed. For example, if a user adds a new entry to the file, that entry no longer exists after an IBM Tivoli Monitoring upgrade. |
| IZ82833 |
The management console (itmcmd manage) runs slowly taking up to 30 seconds to respond to each action performed on the console. |
| IZ83646 |
Upgrade from IBM Tivoli Monitoring 6.2.2 FP1 to IBM Tivoli Monitoring 6.2.2 FP2 any base component where IBM Tivoli Monitoring 6.2.2 FP1 64-bit Windows Agent is installed causes the install to loop until the customer cancels the install. The message issued states the Agent compatibility package must be upgraded first, before the base CD can be upgraded. If OK is pressed this error continues to appear until the install is cancelled. |
| IZ84841 |
Upgrading from an Interim Fix to an Interim Fix or Provisional does not work and the following message is displayed: KDY0041E: The agent bundle XX is already updated to the highest version 062100060 found in the depot and deployed to <hostname>. however the agent in this example shows version 062100006. The "kincinfo" command returns an agent version number with the VVRRMMFF padded with an extra zero VVRRMMFF0. The code fails to account for the extra zero padding in the data returned from "kincinfo". |
| IZ85351 |
The version of Java that installs with the IBM Tivoli Monitoring installer and components contains a Category I security issue. The IBM Tivoli Monitoring supplied Java has been uplifted to 1.5 SR12 FP1 which resolves the security audit failure. |
| IZ85668 |
The uninstall.sh script does not remove config, env, or ini files. The uninstall.sh script is designed to remove individual IBM Tivoli Monitoring components or remove the entire product. When it removes a given component, it removes the code but it does not remove the configuration files associated with it. If the component is reinstalled later, these original configuration files can cause problems. |
| IZ85959 |
When uploading cat and atr files to a z/OS Tivoli Enterprise Management Server, the upload fails if the password contains '@' character. |
| IZ86195 |
When you configure the Tivoli Enterprise Portal Server using "itmcmd config -a cq", you are allowed to enter a Tivoli Data Warehouse data base name that is too long. If the data base name is too long, then the portal server does not work correctly with historical data. |
| IZ86997 |
On AIX, if there are multiple IP addresses for an aliased interface, "cinfo -r" will report incorrect results. |
| IZ87749 |
Starting in 6.2.2 Fix Pack 2, running the "cinfo -r" command results in a new message written to /var/log/message*: Mon dd hh:mm:ss host modprobe: modprobe: Can't locate module Iface This symptom occurs on older versions of RedHat Linux. However, the underlying query that causes it occurs on all versions of Linux. |
| IZ88159 |
The install.sh script fails to locate running processes when local and network host names do not match. If agents have been started with a network host name that does not match the current local `uname -n` host name, install.sh does not recognize these running processes. Local interactive installation does not warn about these processes. Local silent installation and remote installation does not attempt to stop these processes. |
| IZ88194 |
If the GSKit upgrade fails for any reason, the GSKit files are deleted from the CANDLEHOME directory. Although keeping the newer version of the GSKit in the same directory as the prior version may result in problems with already installed agents, the lack of any GSKit after a failure results in total failure of any agent to function. |
| IZ89527 |
The "kinconfg" command to start the Manage Tivoli Enterprise Monitoring Services (MTEMS) can use 100% of the CPU and almost 30 seconds of elapsed time due to the scanning of files to verify installed versions. |
| IZ89545 |
Local seeding fails when KDEB_INTERFACELIST is used to specify a network interface card (NIC) address. In a multi-NIC environment where the management server is configured to bind to a specific port using KDEB_INTERFACELIST, the seeding process is unable to communicate with the management server. |
| IZ90041 |
The "itmcmd config" command fails when a response file value contains "=", resulting in the command going into interactive mode. |
| IZ90042 |
When configuring the Tivoli Enterprise Portal Server using silent configuration, the sample silent configuration files have the variables for the JDBC driver class path and JDBC driver name reversed. |
| IZ92036 |
After the UNIX OS agent 6.2.2 Fix Pack 2 Interim Fix 4 through Interim Fix 6 is installed and "SetPerm" is run, the agent crashes whenever the "Disk Usage" workspace is selected in the Tivoli Enterprise Portal. |
| IZ93548 |
After 6.2.2 Fix Pack 3, Java related activities such as Java configuration and the "tacmd" command may fail if a CD based on 6.2.2 GA, FP1 or FP2 is installed after FP3 is installed. Java home files GetJavaHome.bat and CandleGetJavaHome.vbs become null so that Java related activities do not process properly. |
| IZ94095 |
The eWAS package which is shipped as part of the portal server needs to address security exposures identified in eWAS release 6.1.0.23 and Java SR9. The fixes are available in eWAS release 6.1.0.35 for both the Windows and UNIX platforms and includes an upgrade of Java to SR12 FP2 within eWAS. |
| IZ95737 |
Oracle Security Alert for CVE-2010-4476 describes a problem in the way that Java handles a specific numerical conversion. This problem could be exploited by a malicious user and cause an affected process to hang. The following link contains more information about the security exposure: http://www.ibm.com/developerworks/java/jdk/alerts/cve-2010-4476.html. IBM Tivoli Monitoring (ITM) software includes Java Runtime Environment (JRE) and embedded WebSphere Application Server (eWAS) packages that contain this problem. |
| IBM Tivoli Enterprise Monitoring Server APARs | |
| IZ81212 |
When a primary management HUB switches to the mirror HUB, MS_Offline events are generated for agents and/or remote management servers that were on-line but may be marked off-line at the mirror. |
| IZ81334 |
The Tivoli Enterprise Management Server can take in excess of 10 minutes to shutdown. This occurs randomly and during the product install process this can cause the install process to fail. |
| IZ81433 |
Fault Tolerant Option (FTO) stage II processing restarts every 5 seconds when a database error is encountered. The database error may be similar to the following: ...kfagroup.c,1668,"getSituation") ReadByKey for key <MY_SITUATION_NAME > failed; status <5> ...kfagroup.c,2794,"addToSitList") Failed to retrieve the definition of Situation <MY_SITUATION_NAME > for key <2010OGRP_634B5ABEAD112233 5140MY_SITUATION_NAME >; status <5> ...kfagroup.c,2076,"removeGroupTableEntry") Skipped deletion of key <2010OGRP_634B5ABEAD112233 5140MY_SITUATION_NAME > from <TGROUPI> cache because cleanup failed; status <5> ...kfaibdel.c,328,"Process") Delete failed (NotThere) for '2010OGRP_634B5ABEAD112233 5140MY_SITUATION_NAME ' ...ko4ib.cpp,6051,"IBInterface_remove_dict&") sqlS error <1136> ...kqmarm.cpp,877,"arm::doStageII") Stage-Two processing completed at <10/07/10 15:10:04>, rc = 1 Each restart opens another EIBLOG queue at the peer HUB. This can eventually lead to memory exhaustion at the peer HUB, which can, in turn, cause crashes. This problem is most likely to be seen at the HUB becoming the MIRROR, though it can happen at the HUB becoming the acting HUB. |
| IZ84839 |
If the "msg" slot is setup for any formatting such as variable or attribute substitution and the length of the data is more than 2000 bytes, the Tivoli Enterprise Management Server can crash due to storage overlay. |
| IZ86454 |
Data is no longer synchronized to the MIRROR Tivoli Enterprise Management Server. Pings may also be missed. The problem is caused by future dates in the checkpoint timestamps used by Fault Tolerant Option (FTO). The future dates get into the checkpoint timestamps from records that were synchronized. |
| IZ86487 |
After starting the MIRROR, the MIRROR appears online at the acting HUB for 6 minutes, then goes offline for a period of time, then appears online and stays online. The MIRROR is up and appears to be functioning normally during the whole time frame. This problem does not affect the true state of the environment and the MIRROR can take over as acting HUB successfully during this time period. The acting HUB does continue to synchronize data to the MIRROR. |
| IZ87817 |
Records that contain an invalid timestamp may not be properly synchronized between the MIRROR and the HUB in a Fault Tolerant Option (FTO) environment. This can result in new records missing at one of the HUBs. Updates to records with an invalid timestamp may not be reflected to the MIRROR correctly. The update may also be lost if the roles of the HUB and MIRROR are reversed. Records that should have been removed from the MIRROR may remain in place and possibly restored at the HUB where it was removed. |
| IZ87820 |
A bad timestamp can be generated resulting in various anomalies such as database records with invalid or incorrect timestamps, prevention of synchronization in Fault Tolerant Option (FTO), MIRROR appearing offline, and potentially other issues. |
| IZ88507 |
Agent status invalid in Tivoli Enterprise Portal Navigator tree after agent auto-fallback and primary RTEMS shutdown. The agent status shows it is online when it should be offline. |
| IZ88973 |
The management server can abend or garbage can be written to the trace log after specifying traces for some modules. This problem can occur after trace is added for kfaixlod, kfasphst, kfastini, kfastins, kglcmmsg, kglisiop, kglkycbt, kauctds, kdsart, kdsinos2, kdsinsql, kdsmacmd, kdspac1, kdsrqcl, kdsvws1, kraaefio, ko4mh, khdxcpub, and kshreq. |
| IZ91637 |
When a Simple Object Access Protocol (SOAP) request is run for an agent which is not currently registered, an entry is cached in SOAP for the node with an incorrect thrunode. Once the agent is registered on the hub or remote management server, the cached entry is not updated so the query will fail. |
| IZ92307 |
The management server can crash when multiple take actions are executed simultaneously due to multithreading issues. |
| IBM Tivoli Enterprise Portal Client APARs | |
| IZ75871 |
In Tivoli Enterprise Portal 6.2.2, if a link displayed in the Situation Editor Expert Advice Preview panel is opened in a new window, that window will not respond to user input or mouse clicks. The Situation Editor Expert Advice facility allows the advice text to include links to other documents. Such links may be coded to open the document in a new window or the user may choose to open the document in a new window. Either way, the new window opened for the document will not respond to user interactions. Following installation of this APAR, Tivoli Enterprise Portal browser mode users may find that keyboard input is not allowed for popup windows opened via links in the Situation Expert Advice Preview dialog. Such popups will accept input pasted from the clipboard. These popups will accept keyboard input when displayed from the Situation Expert Advice view in a workspace while a user is investigating the cause and resolution options for an active situation event. |
| IZ78022 |
While displaying summarized data in the Tivoli Enterprise Portal workspace, if the user right clicks on the data and selects "Model Situation...", the situation name entry screen may not come up, or it may come up without all of the data that it needs. Therefore the user can not model a situation using the data displayed on the screen. |
| IZ80078 |
The Administer Users dialog internally switches user group assignments if users are selected in succession while the 'Member Of' tab is not the active tab. This problem can cause various messages to be incorrectly displayed depending on the way the user definitions may be mixed. These messages may include: KFWITM457E - User cannot be saved due to a failed circular reference check and: KFWITM429W - There are no applications assigned to this User or to a Group they are a member of. |
| IZ80797 |
Physical nodes copied into custom Navigators may display duplicate entries in their Workspaces menu if multiple workspace versions exist for the node. Applications may distribute multiple versions of their product-provided workspaces that correspond to the increasing capabilities of newer agent versions. Tivoli Enterprise Portal includes only the most recent installed version when it builds the Workspaces menu for a node. This process applies to nodes in the Physical Navigator but not to copies of physical nodes in custom Navigators. |
| IZ80933 |
If a renamed situation is used in a policy, if a "Wait until is False" workflow component is selected from the Extensions tab and the renamed situation is selected from the list of situations, the old situation name will appear within the node instead of the new situation name. |
| IZ81405 |
When adding attributes in a Tivoli Enterprise Portal Plot Chart view, it only allows for a maximum of twenty attributes to be added to the view. This fix increases the default color chart to support fifty attributes. |
| IZ83418 |
When a group is assigned to a user from the Administer Users screen in the Tivoli Enterprise Portal, the views owned by the group also get assigned to the user. When the group is subsequently removed from the user, the views owned by the group should also be removed. When this problem occurs, the views owned by the group remain assigned to the user after the group is removed from the user. This happens regardless of whether or not the views owned by the group were already assigned to the user before the group was assigned to the user. |
| IZ84428 |
If you use any of the product provided queries used to select data against the Tivoli Enterprise Portal database table KFWTSIT in a workspace along with an application that has been enabled for historical collection errors can occur. If using the timespan dialog to select historical data in a workspace view and one of the other views in the workspace selects data against the KFWTSIT, the Tivoli Enterprise Portal client will try to set all the queries in the workspace views to historical if the query definition does not designate whether or not it's enabled for history. |
| IZ84756 |
The message "KFWITM495E There are no members assigned for this object group. Select Yes to delete this object group or No to assign members." can appear unexpectedly and incorrectly if a user is quickly browsing through Managed system entries without making any changes. If the user clicks "Yes", the object group will be deleted even though it is not actually empty. The message "KFWITM488W Group information has changed, do you want to save the changes?" can appear unexpectedly and incorrectly if a user is quickly browsing through Situation group entries without making any changes. If the user clicks "Yes", the group definition can be cleared or corrupted. In each of these cases, the affected group may be the one previously displayed rather than the one currently displayed. |
| IZ84840 |
In the Administer Users dialog, switching to another data tab for a User or User Group after having changed the 'Member Of' or 'Members' settings will commit the changes. Selecting another user after taking the preceding actions but before clicking 'Apply' may not display message 'KFWITM037W User information has changed, do you want to save the changes?' |
| IZ85604 |
When using the Tivoli Enterprise Portal browser client and the https protocol with the IBM Tivoli Monitoring integrated http/https server, the client will not connect when Sun Java 1.6 is used. https://<teps_host_name>:3661///cnp/client fails with an IOException with a message stating the hostname should be the name of the host where the portal server is running. |
| IZ89187 |
When running on a French Windows system using the Windows OS agent, the "System Description" column/attribute truncates the word "Systeme" after the accented character "e". It does not show the accent on the "e" character. |
| IZ89470 |
Not all eligible attributes are listed in the Tivoli Enterprise Portal Situation Action Panel "Attribute Substitution" dialog. If a version 1 attribute is used in the situation definition not all of the attributes eligible for that version of the agent appear in the Take Action panel's list for "Attribute Substitution" |
| IZ91082 |
In the Situation Editor dialog during 'Create another' processing or while selecting situations from the navigator, message 'KFWITM036W The situation you are editing was changed. Would you like to save those changes?' may be displayed even though no changes were made. If this happens while the user is creating a copy of a situation and the user clicks the 'No' button, the new situation will be created under an incorrect situation navigator node. |
| IZ92007 |
When using the "Managed System Status" workspace table view in the Tivoli Enterprise Portal client to remove and offline Tivoli Enterprise Manager Server, not all of the child nodes are removed. If you attempt to remove an offline Tivoli Enterprise Monitoring Server entry from the node list the Tivoli Enterprise Portal client will also list any managed systems that were once connected to this offline TEMS. |
| IBM Tivoli Enterprise Portal Server APARs | |
| IZ80142 |
The Discovery Library Adapter (DLA) export for Tivoli Application Dependency Discovery Manager (TADDM) upload works correctly when OS agents are in the environment. However, once an SQL agent is added, the bulkload fails to load the DLA book due to following error. "The source or target in a relationship definition were not found in the file." |
| IZ80869 |
After the sysplex agent has been changed to connect from one management server to another, the reports no longer show any data. With trace (UNIT:ctdata INPUT ERROR)(UNIT:ctsql INPUT ERROR) the report requests can be seen coming from the portal client to the portal server with a THRUNODE parameter containing the management server managed system name of the previous management server it was connected to. Because of this, the reports are routed to that specific management server, but since the sysplex agent no longer reports to that management server, no data can be returned. A query to the KFWMOBJPROPS table for the properties associated to the SYSPLEX agent shows that the THRUNODE property had been previously saved with the old management server. The THRUNODE property should not be stored with the properties of any managed object. This is a dynamic property that should be obtained at the time a request has been made. |
| IZ81878 |
Timespan icon is missing when a workspace link is followed. However, the timespan icons appear correctly when same workspace is opened by navigating to it directly using the Physical Navigator. |
| IZ83183 |
When editing an event class and the Event Integration Facility (EIF) slot customization tab is selected, the event class ITM_KR2_WINDOWS_SERVICE is missing from the list of available event classes selection window even though it is listed in the .baroc file. |
| IZ84130 |
Events show up as duplicates in the portal server client navigators and Situation Event Console, due to a change in behavior introduced in APAR IZ50716. |
| IZ84982 |
MS_Offline event in Situation Event Console (SEC) not clearing when a clear offline entry in Managed system Status is performed. The problem occurs on IBM Tivoli Monitoring 622 FP2 portal server on any OS. IBM Tivoli Monitoring 622 FP1 is not affected, the 'MS_Offline' event is removed in SEC after the clear offline. |
| IZ85001 |
After upgrade of Omegamon for IMS agent from 410 to 420, the following message popup displays on the Tivoli Entperprise Portal client when selecting Historical Data Collection for the IMS agent: "Cannot Load Product Configuration Data KFWITM217E Request error table not found". This problem occurs with any agent that renames or deletes attribute tables without deleting the associated UADVISOR situation. The portal server lists all the UADVISOR situations for a product under the assumption that there will be a corresponding attribute table for it, when there is not an exception is issued. For most agents the renaming or deleting of attribute tables is a very rare occurrence. This problem has been observed with agent builder tables as well. |
| IZ86819 |
The initial defaultTECRuleBase.xml file is packaged as part of the tepsmcsattribute.jar file. Because of this, it is not easy to determine what values are configured initially in this file. Should the customer wish to change this file using the Tivoli Enterprise Console Event Definition Generator (TEDGEN) utility or manually, they can now compare the original against the modified versions. |
| IZ89551 |
Situations show as true, when in reality are false after a remote Tivoli Enterprise Monitoring Server (RTEMS) recycle. On initial connect or reconnect to the HUB, the portal server filters out started (S) and reset (N) events. On initial connect to the HUB, this is fine because there are no existing situation models in memory. But on reconnect to the HUB, the situation model may exist in memory and may show the situation as true. The problem occurs because the portal server was filtering out those events at reconnect to the HUB as well. |
| IZ89664 |
Migrating from 6.2.2 Fix Pack 2 to 6.2.2 Fix Pack 3 the migration will appear to be successful, but the following error will display in the log: [IBM][CLI Driver][DB2/AIX64] SQL0204N "ITMUSER.KFWHISTDATA" is an undefined name. SQLSTATE=42704 ERR: -204, SQLExecDirect rc=-1: SQL_ERROR This problem can occur on any platform. |
| IZ89815 |
An error occurred when using the "tacmd histunconfiguregroups" command. As an example: tacmd histunconfiguregroups -t NT -o "Active Server Pages" -m KUIHUG001I Validating user credentials... KUIHUG099E The command failed because an unexpected error occurred. Please consult the C:\IBM\ITM\logs\HistoryConfigurationCLI_0.log The problem is caused by the invalid value passed from the command. Tivoli Enterprise Portal Server expected integer values for P*INT columns but the command passes the value of 'Off'. |
| IZ90181 |
After the IP address changes for an OS Agent and the portal client updates with "KFWITM024I Navigator update pending", using the Find tool in the portal client Navigator continues to use the old IP address instead of the new one. |
| IZ90894 |
Scaled columns in Warehouse Proxy agent ODI file (dockhd) are incorrect. The scaled columns in the files are set to PREC=2. This causes a failure in the Tivoli Enterprise Portal in display of the column correctly as it is truncated. |
| IZ95044 |
The UNIX and Linux OS agents previously added support for long process names, requirement 1012. This included adding a new attribute "Process Filter" to both agents to define a regular expression to filter processes based on their full command line (Process Command(Unicode) on UNIX or Command Line on Linux) and return only a portion of the command line. In the Historical data collection, a filter can not be saved for the OS agent if the new attribute "Process Filter" is specified. This APAR fixes this problem which completes the support of long process names in the UNIX and Linux OS agents. |
| IZ95342 |
Kfwservices process reaches 100% CPU and hangs the portal clients almost every day. After restarting the portal server, everything returns to normal operation. This occurs only as a result of a provisional fix including APAR IZ90181. |
| IZ95357 |
Improve performance for tmsdla command. |
| IBM Tivoli Universal Agent APARs | |
| IZ83558 |
Universal Agent attribute group with multiple sources that is an //INTERNAL OUTPUT redirect only processes data rows for one source. When //INTERNAL OUTPUT has multiple sources then each associated //INTERNAL INPUT attribute group needs to be flagged as MulitpleSources=TRUE. This setting is not being done, thus the result is that only one of the multiple data //SOURCES is being redirected to the associated //INTERNAL INPUT attribute groups. For example, given a metafile declared as follows: //APPL MYREDIRECT //NAME MULISOURCE E //SOURCE FILE C:/tmp/fileOne.log tail //SOURCE FILE C:/tmp/fileTwo.log tail //INTERNAL OUTPUT FileLogRecords ... //NAME Warnings E //INTERNAL INPUT FileLogRecords ... //NAME Errors E //INTERNAL INPUT FileLogRecords the results are that only the "Error" and "Warning" records from fileOne.log appear in the portal client view of 'Warnings' and 'Errors' tables; no records from fileTwo.log appear. |
| IZ85255 |
Universal Agent fails to correctly convert SNMPv2 standard traps to SNMPv1 standard traps, resulting in trap attribute 'Specific Trap' always displaying a value of '0' and numerous other trap attributes displaying value of 'Unavailable'. SNMP standard traps include Specific Trap values 1, 2, 3, 4, 5 and 6 for standard traps coldStart, warmStart, linkDown, linkUp,authFailure and egpNeighborLoss, respectively. |
| IZ86596 |
When invoking the "kumpinpt" command, the command fails with "KUMPA08E Local machine host name can not be resolved to IP address". This APAR only applies to Universal Agent running on a Solaris platform using APIS data provider. |
| IZ87367 |
When running a script that redirects STDOUT on UNIX/LINUX the resulting data rows appearing in Tivoli Enterprise Portal are erratic; sometimes a portal client refresh will show one or several of the data rows, other times no data rows appear. Regardless of how many data rows appear, ALL of the expected data rows do not appear. A Universal Agent environment variable, KUMP_STDOUT_WAIT_TIME, has been added using a unit-of-measure in seconds. This variable tells Universal Agent to wait up to this many seconds before deciding there is no more data to be read from the STDOUT pipe. The customer environment may require 'tuning' the value for KUMP_STDOUT_WAIT_TIME, for example it may need to be 1 or 2. Note that the larger the value, the longer the potential 'wait' incurred by the Universal Agent's SCRIPT data provider when processing a script. The default value for KUMP_STDOUT_WAIT_TIME is zero, which is equivalent to not setting the environment variable. |
| IZ87893 |
Universal Agent on Windows, running Japanese Codepage 943, fails to convert BACKSLASH contained in a situation's Action, due to Windows Codepage 943 not containing the Yen character for 0x5C. Therefore the conversion is incorrectly processed. For example, the situation Action -> <CMD> <![CDATA[echo NG: &{TESTLOG00.msg} >> C:\work\output.txt]]> </CMD> is translated by Universal Agent using Codepage 943 to echo NG: "some message" >> C: work output.txt which results in an invalid file path. |
| IZ88719 |
Universal Agent UTCTOLOCALTIME function does not work on UNIX and Linux platforms. On UNIX and Linux platforms, when defining an attribute to be derived per UTCTOLOCALTIME function, the resulting value appearing in the Tivoli Enterprise Portal is incorrect; it displays as a '^' character rather than as a mm/dd/yy hh:mm:ss formatted value. |
| IZ89314 |
Restart of Universal Agent alternate instance may have empty tables in the portal client view. This problem may appear on some Universal Agent alternate instances but not on other instances. The reason has to do with the presence of situations defined against the Universal Agent subnodes (applications) at issue and the timing sequence between the Universal Agent applications coming online and the initial 'sampling' request from an associated Situation. If, for a given Universal Agent subnode on an alternate instance, situations are defined AND any situation requests are received before subnode achieves 'online' state, the empty tables in the portal client will occur. The problem does not occur on the Primary Universal Agent instance. |
| IZ89636 |
The Universal Agent Reflex Action is not executed when the length of subnode name is exactly 32 characters. When this problem occurs, the following form of RAS1 message is logged; note trailing "d" is a garbage character, due to a random byte of memory that is being treated as part of the subnode data item. The trailing garbage character will vary in its value, however the effect is always the same - the subnode name is incorrect and thus the Reflex Action can not be successfully executed. kumamain.cpp,3618,"main::UA_Action") Real subnodeName <HOST_NAME:MYUAAPPLICATION_NAME00d> colinfo.offset=0 |
| IZ91917 |
Universal Agent does not support Windows automatic Private IP addressing (APIPA). Because APIPA uses IP addresses in the private Class B space, APIPA is a feature generally only useful on home or other small intranet LANs. Note that the computer can not communicate with computers on other subnets, or with computers that do not use automatic private IP addressing. Given that Automatic private IP addressing (APIPA) is enabled by default, support of APIPA could likely preempt any static IP or DHCP addressing, thereby isolating the host machine from the network enterprise and preventing Universal Agent from communicating with other IBM Tivoli Monitoring components such as the management server. This problem occurs on Windows platform only. |
| Remote Deploy APARs | |
| IZ81337 |
The "Target Managed System Name" column in the KDY.KDYDYSTS table incorrectly contains the Managed System Node (OS Agent) name. When content of the column is corrected, the display column does not always display a value. When the APAR fix is enabled, the NodeID column will not be displayed in the portal client until the Filtering for the newly added column is enabled. This is because when a new column is added to the display, the newly added columns are not enabled by default. You must manually enable the column in order for it to be displayed. To enable the display of the NodeID column, select the "Edit Properties" icon on the Deploy Detail Status Workspace. The Edit Properties Dialog will display the available column headings. To enable the NodeID Column for display in the Deploy Detailed Status Workspace, click the check box next above the NodeID name and apply the change. |
| Summarization and Pruning Agent APARs | |
| IZ84939 |
Availability shows percentage greater than 100%. The problem happens when the Summarization and Pruning agent does not have a delta row (row used to calculate delta between two sequential rows) when starting a new run and there is no partial row information or it is a start of a new vacation day or shift (and there is no partial row). |
| IZ87447 |
After upgrade to IBM Tivoli Monitoring 6.2.2, the Summarization and Pruning agent fails to aggregate because of a DB2 error: "SQLCODE: -803 when inserting into the WAREHOUSEID table". This can occur when upgrading from IBM Tivoli Monitoring 6.2.x to 6.2.2. This failure does not always occur. |
| IZ94084 |
Install of the Summarization and Pruning agent does not include the kib.atr file. This results in the failure to collect operations history log information (.LG0) for the Summarization and Pruning or Warehouse Proxy Agent in the OPLOG table. The following message is displayed in the agent log file: 4C912CF6.0000-8:khdxhist.cpp,1128,"describeColumns") Unable to Resolve Object Name from Metafile "/opt/IBM/ITM/aix536/sy/hist/OPLOG.hdr" (4C912CF6.0001-8:khdxcpub.cpp,1067,"syncHistoryData") StartSession failed for table <OPLOG>. status = 52 (4C912CF6.0002-8:kraahexp.cpp,395,"syncHistoryData") Sync history Data for table <OPLOG> failed. rc = 52 (4C912CF6.0003-8:kraahexp.cpp,119,"HistoricalExporter__Dispatch") Abort history request due to syncHistoryData error 554041355 (4C912CF6.0004-8:kraatblm.cpp,641,"checkForExpiredRequests") Sample error <2106000b%gt;, for UADVISOR_O4SRV_OPLOG <523244480,55575512> KPX.OPLOG. |
| itmpatch APARs | |
| IZ89559 |
When an Interim Fix for an agent is installed on Linux platforms, it fails to install with the following message: "Either the current platform architecture or the installed components do not meet the prerequisites of the patch." The itmpatch binary for li6263 and li6266 is also used for the lx8263, ls8263, lx8266 and ls8266 platforms. When the patch input file contains one of the following platforms lx8263, ls8263, lx8266 or ls8266 the comparison against the string li6263 and li6266 fails, which results in the failure to install the patch. |
| IZ93329 |
When the "itmpatch" command is used to install a patch for a multi-instance agent with a Windows 64-bit binary, the binary in the %CANDLE_HOME%\tmaitm6_x64 gets updated, but the multi-instance copies of k<pc>agent_<instance>.exe do not get updated. If the patch file name is <component>_wix64_<patchname>.zip, the product .EXE file directory is incorrectly set to tmaitm6 and not tmaitm6_x64. The .EXE files for the agent's instances are not located and therefore not updated. |
| Date |
Description of change |
|---|---|
| 08 April 2011 |
Original version |