IBM Support

Fixes needed on top 6.3 FP06.

Technical Blog Post


Abstract

Fixes needed on top 6.3 FP06.

Body

Fixes needed on top 6.3 FP06.

6.3 FP06 is the latest release, but do you know what other fixes on top of this may be needed in your environment?


The place to look is Fix central: https://www.ibm.com/support/fixcentral/

This will allow you to select 6.3.0.6 once you have selected IBM Monitoring (after selecting Tivoli as product group).

So the screen should look this:

image

Then you select how to view the fixes, I usually go for browse but if you know the number of the fix then it can be put in instead.

This will result in list of the fixes available, note the dates at the side, this is the release date for the fix, and they are listed by  the latest fix first, as some fixes may be superseded.

However to find out details of each fix you need to read the README's, which means selecting each one and then selecting the README to download.  

Due to this I produced this list for a customer, that gives the main fixes as of now (16 June 2016) and what apars these contain.

Obviously this list will change but this will at least give a start to knowing if there are any other fixes you require in your environment when you are upgrading to 6.3 FP06.  

I would recommend Fix Central is checked for any other fixes that may have come out since 16 June 2016.

The fixes then have to be reviewed to understand if they are need for the ITM environment being used.

Ifixes now available for 6.3 FP06 on Fix Central:

*************************************************************************************************************************************************************************

6.3.0-TIV-ITM-FP0006-IV83775

TEPS RANDOMLY CRASHES AFTER APPLYING 630 FIX PACK6.
PROBLEM DESCRIPTION:
================
TEPS randomly crashes after applying 630-FP6. The eWAS
SystemOut.log will show one of the following errors:

java.lang.NullPointerException at
com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
BCDataSource.java:541)

or:

java.sql.SQLException: Closed Resultset at
oracle.jdbc.driver.ScrollableResultSet.next(ScrollableResultSet.
java:311) at
com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
BCDataSource.java:538)

The exception occurs when trying to run a query to a JDBC data
source (such as an Oracle warehouse database). If the query
takes a long time to run, and the user switches to a different
workspace before the JDBC query finishes, the crash will occur.

***********************************************************


6.3.0-TIV-ITM-FP0006-IV77992 and  6.3.0-TIV-ITM_TMV-LP-FP0006.iso

This fix addresses a security vulnerability for remote code execution (CVE-2014-7411),
IBM Tivoli Monitoring (ITM) portal client could allow an authenticated user to increase their authority and be able to run commands they were not intended to have authority to run as administrator. This can include running commands on remote systems managed by IBM Tivoli Monitoring.

Details:
http://www-01.ibm.com/support/docview.wss?uid=swg21973559

NOTE: This has been re-released on 1 June to include a defect where once installed users had to have the premission User Administration ... View
to be able to view the TEP (got either grey screen on login or blank workspaces)

If ealier version has been installed, uninstall and install new version.


and 6.3.0-TIV-ITM_TMV-LP-FP0006.iso  for language pack (if needed).

***********************************************************

6.X.X-TIV-ITM_JRE _SUF_20160408

http://www-01.ibm.com/support/docview.wss?uid=swg24041723

If utilizing the Situation Update Forwarder (SUF) to pass updated events from OMNIbus to an ITM management server, then the following patch is provided to update the JRE installed as part of the Situation Update Forwarder. The patch updates the JRE to 6 SR16 FP20 and the patch works across SUF versions listed under

***********************************************************

 6.X.X-TIV-ITM_EWAS_ALL-8.00.11.02

http://www-01.ibm.com/support/docview.wss?uid=swg24042044

This fix upgrades the embedded WebSphere Application Server (eWAS) which is shipped as part of the IBM Tivoli Monitoring portal server, to version 8.0.0.11 plus additional Interim Fixes referred to as Interim Fix Block 2. The Interim Fixes included as part of Interim Fix Block 2 include:

    PI55780
    PI45266 - included in Interim Fix Block 1 (8.00.11.01)
    PI52103 - included in Interim Fix Block 1 (8.00.11.01)

***********************************************************

6.X.X-TIV-ITM_JRE_CANDLEHOME-20160408

http://www-01.ibm.com/support/docview.wss?uid=swg24041511

This fix updates the IBM SDK Java Technology Edition Java Runtime Environment (JRE) which is installed into the IBM Tivoli Monitoring installation directory (for example, CANDLEHOME). This is an embedded JRE which is used by various IBM Tivoli Monitoring components and agents. It is a different JRE than is used by the Tivoli Enterprise Portal Browser client or Java WebStart client.

***********************************************************

6.X.X-TIV-ITM_JRE_TEP_20160308

This fix updates the IBM® SDK, Java™ Technology Edition for the portal server to address documented security vulnerabilities.

http://www-01.ibm.com/support/docview.wss?uid=swg24041932

***********************************************************

6.X.X-TIV-ITM_IHS_ALL_8.00.11.02

http://www-01.ibm.com/support/docview.wss?uid=swg24041707

This fix upgrades the embedded IBM HTTP Server (IHS) which is shipped as part of the IBM Tivoli Monitoring portal server, to version 8.0.0.11 plus additional Interim Fixes referred to as Interim Fix Block two which includes PI54962 as well as patches included previously as part of interim fix block one: PI45596, PI42928, PI44793.. It addresses the security vulnerability as documented in the Security bulletin: http://www.ibm.com/support/docview.wss?uid=swg21976125

***********************************************************

6.3.0.6-TIV-ITM_WIN-IF0001

2.1 APARs
---------
APAR: IV78199
Abstract: Windows OS Agent crashes when Wathdog alerts older than 24
hours.
Additional Information: The Monitoring Agent for Windows OS terminates
when the Agent Management Services workspace is selected and the
Agents' Alerts view has one or more alerts listed that are more than
24 hours old. The problem occurs when the code tries to delete the
alerts older than KCA_CACHE_LIMIT (default is 24 hours). The crash
does not happen every time.

APAR: IV69861
Abstract: On some Windows systems, the Monitoring Agent for Windows OS
cannot be stopped due to the executable kcasc.exe hanging periodically.
Additional Information: On some Windows systems, the Monitoring Agent for
Windows OS cannot be stopped due to the executable kcasc.exe hanging
periodically. This executable is called when Watchdog is being disarmed
which needs to occur before the OS Agent can be stopped. This was seen
on a Citrix server.

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


***********************************************************
6.3.0.6-TIV-ITM_UNIX-IF0001


2.1 APARs
---------
APAR: IV81845
Abstract: Monitoring Agent for UNIX OS becomes unresponsive on AIX
Additional Information: Monitoring Agent for UNIX OS becomes unresponsive on AIX due to an incomplete
response of the AIX api perfstat_netinterface.

APAR: IV81209
Abstract: The attribute UNIXDISK.Mount_Point_U cannot be used in plot chart legend label
Additional Information: The attribute Mount Point (Unicode) in the Disk attribute group of the
Monitoring Agent for UNIX OS cannot be chosen as a legend label in Tivoli Enterprise Portal plot chart
views, due to an internal illegal definition.

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

APAR: IV75662
Abstract: The attribute UNIXDISK.Mount_Point_U is not defined as primary key.
Additional Information: The attribute Mount_Point_U of the group UNIXDISK is not defined as primary key. This
prevents its use with performance analyzer as it needs 2 primary keys.

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

***********************************************************

6.3.0.6-TIV-ITM_LINUX-IF0001


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

APAR: IV78033
Abstract: Monitoring Agent for Linux OS randomly hangs during Disk data collection
Additional Information: Due to a lack of synchronization with the internal thread that collects data for the
"Disk Usage Trends" attribute group it may happen that the agent hangs while responding to a query or a
situation on the "Linux Disk" attribute group, as the two groups share the same object. The event is rare
because the "Disk Usage Trends" thread runs only once per hour by default.

APAR: IV80542
Abstract: Monitoring Agent for Linux OS core dumps while monitoring disks.
Additional Information: The Monitoring Agent for Linux OS can randomly crash during Disk attribute group data
collection. This is due to a memory corruption caused by a timing condition between two agent internal threads.
This condition may occur when one or more filesystems do not respond within the 2 seconds default timeout for
the statfs64 system call.

APAR: IV83672
Abstract: Spurious row returned for a custom script with empty output.
Additional Information: he Monitoring Agent for Linux OS returns an empty data row in the Custom Scripts Runtime
Sampled attribute group even if the configured custom script does not produce any output rows. This is not
consistent with the equivalent pure event attribute group, Custom Scripts Runtime, that returns no rows in
such a case. Also, situations based on the number of expected rows may trigger improperly.

2.2 Defects
-----------
Defect: 216163
Abstract: small mem leak after installing 623FP5 IF0001
Addition Information: After installing the 623fp5 IF0001 for linux agents, a small memory leak can be observed
if there are the following conditions on the agents:
- more that 200 situations running
- the KLZ_DISK_SAMPLE_HRS var set to 5

***********************************************************
6.3.0.6-TIV-ITM_LINUX-IF0002

 2.1 APARs
  ---------
  APAR: IV79424
  Abstract: Linux processes missing start and elapsed time information.
  Additional Information: The Monitoring Agent for Linux OS does not provide any information about the time when
    a process was started, nor for how long it has been running.
    
  APAR: IV82704
  Abstract: The Total Memory Free attribute value is not accurate.
  Additional Information: The Monitoring Agent for Linux OS estimates the physical memory actually available to
    the system for starting new applications without swapping by using a simple algorithm that takes into account
    freeable memory contributions like memory in cache and memory in buffers. Since kernel 3.2 the same information
    is directly computed by the system, in a more accurate way, and made available through the specific MemAvailable
    field in the /proc/meminfo file, as well as in the new column "available" of the "free" command output.

  APAR: IV78556
  Abstract: Incorrect percentages of CPU time consumed by Linux processes
  Additional Information: The Monitoring Agent for Linux OS may report incorrect values for the following attributes
    in the Linux Process attribute group, when they exceed 100%: Process System CPU (Percent), Process User CPU (Percent),
    Cumulative Process System CPU (Percent), Cumulative Process User CPU (Percent), Process Busy CPU (Percent) and
    Cumulative Busy CPU (Percent). These attributes can exceed 100% on servers with multiple online processors. Also,
    these attributes are not normalized to the number of online processors, thus preventing 100% to be exceeded, whereas
    other CPU-related attributes in this group are normalized. In order for this APAR to be properly implemented in your
    environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for
    more details.  
 
  2.2 Defects
  -----------
  None.
 
  2.3 Enhancements
  ----------------
  None.

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

*********************************************************************************************************************************************************************************

Tutorials Point

Subscribe and follow us for all the latest information directly on your social feeds:

image

image

image

  

Check out all our other posts and updates:
Academy Blogs:  http://ow.ly/Otue0
Academy Videos:  http://ow.ly/PIKFz
Academy Google+:  http://ow.ly/Dj3nn
Academy Twitter Handle:  http://ow.ly/Dj35c

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"SSZ8F3","label":"IBM Tivoli Monitoring V6"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":""}]

UID

ibm11083309