Technical Blog Post
Abstract
ITM Nuggets: Time to plan that upgrade to ITM 6.3 Fix Pack 6... (Live links for download, APAR information and part numbers / codes)
Body
2016 Q1 is nearly at an end, which means its a good time to plan that upgrade you have been putting off in 2015!!
ITM 6.3 Fix Pack 6 was released in December and this fix pack not only increases stability, but it also has a range of must have fixes! I strongly recommend at least start the planning of the upgrade to the latest fix pack. Its already making a real difference in several customers environments.
|
The Fix Pack:
Here is all of the info you need to download, review and plan the upgrade/install
LIVE and direct download links Part numbers for fix central, Full APAR and package listings
NOTE: This is also a fresh installable fix pack, as Jens Helbig explains here: http://ow.ly/ZcLMs
All of the links in the below tables are LIVE. They will take you directly to the download location of the package
you require, or the IBM official technote for one of the APARs included in this fix pack (if you wish to know
more about the APAR)
What Each Package Contains
Here are the direct download links for all packages in Fix Pack 6
File Name | Contents of each Package |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Windows operating systems | |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support in English for base agents for 32-bit Windows operating systems | |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for UNIX operating systems | |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Env. Linux operating systems | |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 32-bit Env. Linux operating systems | |
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for Linux on System z operating systems | |
Operating system agents (IBM i, Linux, UNIX, Windows) and Agentless OS agents (AIX, HP-UX, Linux, Solaris, Windows) | |
Tivoli Monitoring event synchronization component, Tivoli Enterprise Console® Event Definition Generator (TEDGEN) utility, and audit record DTDs | |
Operating system agent reports and reports installer | |
Performance Analyzer domains and BIRT reports | |
Language pack for Tivoli Monitoring server components, warehouse agents, OS agents, agentless OS agents, Tivoli Performance Analyzer agent for all operating systems and languages |
List of APARs and Fixes included in the fix pack
Link to full README: Click here
IBM Tivoli Enterprise Monitoring Server APARs | |
Display Item with value of -1 displays in Tivoli Enterprise Portal client as 4294967295. In the case of a situation definition that includes a Display Item, where said Display Item is a 4 byte integer type containing a negative value, the Display Item value will be incorrect in the Situation Event Console and the portal client Message Log; it will also be incorrect in the message recorded in the Tivoli Enterprise Monitoring server Operation (MSG2) log. This incorrect Display Item value only manifests on some operating system platforms, notably on Linux 64 bit platform. | |
The permission settings of scripts, or files, downloaded by UNIX or Linux Agents from the Centralized Configuration Server prohibits the User, Group or Other from doing anything other than reading, or in the case of User reading and writing to the file (-rw-r--r--) regardless of the file permissions specified on the server. | |
Tivoli hub monitoring server may fail to reopen situation. This problem may only occur if hub monitoring server environment variable KDS_SITLOGSIZE is declared as KDS_SITLOGSIZE=32767, which is the maximum size supported for Situation Status History table (TSITSTSH). | |
Situation never closes if an OFFLINE MSN is removed while the Situation is in Open state. A rare scenario was discovered that can result in a Situation with a stale Open event. If while a Situation is open the user stops the Agent for managed system node on which Situation was opened (moving Agent to offline status) and the user also then performs a 'Clear Offline Entry', thereby removing the managed system node, the existing Open event for the Situation will never be closed. This leaves this Open event in a staled/orphaned state. | |
When a remote monitoring server is shutdown, for each Situation running at remote monitoring server a 'stop' event is being sent to HUB monitoring server. This is inefficient since regardless of how many Situations are running at remote monitoring server they will all be stopped because the remote monitoring server is shutting down. | |
If there is a slow network link between remote monitoring server and HUB monitoring server the aggregate of data transfer time over the network plus processing time for the collection of individual 'stop' events is exacerbated and in turn results in a protracted time lapse before remote monitoring server completes shutdown. | |
When a remote monitoring server is shutdown, for each Situation running at remote monitoring server a 'stop' event is being sent to HUB monitoring server. This is inefficient since regardless of how many Situations are running at remote monitoring server they will all be stopped because the remote monitoring server is shutting down. | |
The monitoring server or agent can consume large amounts of CPU in KGE component during startup. The KGE component uses the getpwnam() function provided by the operating system to acquire a list of all root users during startup. The function is inefficient and uses a large amount of CPU to accomplish its function. | |
The node list or node status table can become out of sync between the HUB and standby Tivoli Enterprise Monitoring Server. This can occur under several circumstances. | |
Given a situation with extensive formula that produces large amount of literal text or large filter plan, the situation will fail to start and appear via Tivoli Enterprise Portal in 'Problem' status. This failure is due to error during attempt to allocate memory for situation's data structures. | |
The KO49045 buffer exceeded message can sometimes be issued when it should not. The result is the event is lost and the situation is stopped at the agent that sent in the event data. | |
Situation with embedded situation(s) may incorrectly be raised/opened. The assumption users make is that different criteria can be split across multiple situations which are then combined within a containing situation and that events opened by this containing situation will have satisfied all of the criteria defined within the contained (embedded) situations. | |
Given a situation that contains UNTIL and Display Items, for example 'Sit_A is TRUE UNTIL Sit_B is TRUE' where Sit_A and Sit_B each have a DisplayItem declared, but Display Item for Sit_A is from different attribute group than Sit_B's Display Item. | |
Update Situation Update Forwarder JRE to 1.6 SR16 FP5. | |
Using the updateframework command to update the Tivoli Enterprise Management Agent framework does not update the kax component for architecture li6263. After the update, the kax component remains at the prior level. | |
The Tivoli Monitoring KDE_TRANSPORT environment variable 'POOL:' keyword does not permit configuration of socket port pools on the LOOPBACK device. | |
IBM Tivoli Enterprise Portal Client APARs | |
If the column to the left or the right of the "Opened" column is moved, this changes the index of both the "Opened" and the column that is moved. This causes the "Age" column to stop updating as it relies on the date/time data in the "Opened" column for it's calculation. Changing the "Opened" column causes the incorrect date and time data to be retrieved. | |
The KRV application workspace view timespan button disables. In the CBTI BKUPEND workspace event view, the historical time span dialog does not re-enable after selecting and setting historical query options. | |
When using the launch feature in the tivoli portal client, the launch definition can contain variables that being with an anpersand. The variables should be properly resolved to the proper display name when the definition is launched. | |
IBM Tivoli Enterprise Portal Server APARs | |
Users are unable to log in to the portal client. The portal server log shows many messages similar to the following: | |
Omegamon Z/os agent 1 byte unsigned integers not supported in IBM Tivoli Monitoring data provider. The 1 byte integer value used by several of the Omegamon agents are not being formatted correctly in the data provider. | |
On the Self-Monitoring Topology, last heartbeat times for agents connected to a remote Tivoli Enterprise Monitoring Server are incorrect. | |
With the Tivoli Enterprise Portal Client history collection configuration window open, Portal client showed KFWITM217E error if the database connection was disconnected and restored. | |
The tepsRestore script can run very slow, for example taking more than 6 hours to complete. | |
Add new functionality to allow administrators to restrict which users have the permission to perform the "clear offline entry" function that deletes offline managed systems from the physical navigator. | |
Users are not locked out after exceeding the number of invalid login attempts defined in KFW_AUTHORIZATION_MAX_INVALID_LOGIN. | |
Empty Managed System List is not manipulated correctly by Tivoli Enterprise Portal Client. Empty Managed System List is supported by Tivoli Enterprise Portal Client and tacmd command starting ITM Tivoli Monitoring 6.3 Fix Pack 2 . However, Empty Managed System List is not creatable from Tivoli Enterprise Portal Client. | |
When creating a new Tivoli Enterprise Portal user that uses LDAP to determine the distinguished name (DN), if the DN contains any single quote marks, the newly created user does not contain the correct DN. The new user cannot log in. If the portal server is restarted, the DN will be from the defaultWIMITMBasedRealm. This only occurs if the portal server is using Microsoft SQL Server as the database. | |
Added support so the Owner column shows up in the event payload from the IBM Tivoli Monitoring data provider. | |
Add support for TLS 1.2 encryption protocol to the CORBA IIOP interface. | |
Remove insecure ciphers from portal server interface. | |
Some attributes incorrectly scaled in the JAZZ/sm UI (DASH). The problem was orginally reported by the KI5 agent. The Jazz/sm widgets use the valueMax field for calulation of the scale value for integer display. The IBM Tivoli Monitoring data provider was changed to allow for proper formatting on the UI side. | |
Remote Deploy APARs | |
Specifying incomplete or incorrect command line arguments for the command line command setagentconnection will result in a segmentation fault or a silent failure returning no results. | |
When the TEMA Framework constructs a message for output to the Probe Status Log (LG0, LG1, ...) the message is constructed in a buffer whose total length is less than the message for display. As a result, when the message is written to the buffer, the message overwrites stack storage outside of the buffer space, eventually resulting in the Agent's abnormal termination. | |
Parameters specified by the user for the command line command setagentconnection are not correctly parsed which may result in the command parameters not taking effect for the target agent. Fox example, specifying a parameter of PROTOCOL1=IP.PIPE for the command setagentconnection does not result in change in the target system's configuration. The configuration of the target system remains the same as before the command is issued. | |
The component responsible for parsing the user's command parameters does not detect the presence of a Secondary Server when there are multiple protocols defined for that Secondary Server. The resulting configuration file produced by this component does not include the Keywords IPPIPE_Host and FTO_IPPIPE_Host and their values. | |
Basic Services APARs | |
Setting Tivoli monitoring server environment variable MSG_MODE to a value other than MSG2, e.g. AVA or KMS, may produce large volumes of RAS1 messages written to Tivoli monitoring server trace log file. | |
The Tivoli Monitoring AIX Portal Server fails with Remote Procedure Call (RPC) communication errors when started on or after Sept 6, 2015. This defect is specific to AIX. The RPC errors (1C010008) occurs due to the latent effects of APAR IV76801. On AIX, a program fault does not occur, but the arithmatic result is not unique in the UUID generation process. Activity mismanagement results as a consequence of these non-unique UUIDs, and this results in RPC call failures. The external manifestation of these RPC call failures are Tivoli Enterprise Portal display failures. |
Let's connect!
To follow my social updates on IBM software, please feel free to connect with me by clicking on the images below:
Find all my other blogs here:
LINK
Subscribe and follow us for all the latest information directly on your social feeds:
|
|
|
Check out all our other posts and updates: | |
Academy Blogs: | h |
Academy Videos: | http://ow.ly/PIKFz |
Academy Google+: | http://ow.ly/Dj3nn |
Academy Twitter Handle: | http://ow.ly/Dj35c |
hshsh
UID
ibm11082811