10 Monitoring Technotes you NEED to read.
Andy_M_Jenkins 100000FT92 Visits (1230)
Technotes are technical documents written by IBMers, often Technical Support personnel with direct responsibility for the subject. The technotes document timely and relevant information to help you manage your environments.
Here are 10 of the most popular Technotes for IBM Tivoli Monitoring in May 2013. I would strongly encourage at least cursory glance of these, if nothing else but to help you cement their existance.
IBM Tivoli Monitoring: ITM 6.X Product Codes. This technote provides the location to a file that contains a list of most of the product codes and their descriptors. This method suggested below may not be applicable to all customer environments.
PARMGEN Configuration for IBM Tivoli OMEGAMON XE and other Tivoli Management Services (TMS) dependent products
As a quality improvement activity, IBM has provided additional focus on verification of the following OMEGAMON XE products and components running with IBM Tivoli Monitoring Version 6.x.
The Monitoring Agent for Windows OS agent process, kntcma.exe, may show high CPU or Memory usage during Windows event log processing, while any event log is receiving a large number of events, the processing of these events for the enabled situations causes a high CPU or Memory load reading the events from the log.
A potential cross site scripting (XSS) vulnerability was found using the IBM Tivoli Enterprise Portal browser client.
How to change ITM communication protocols
Java Certificate for some Tivoli products will expire June 2013. After 9th of June, clients may get prompted to accept a valid, but expired certificate. The solution is to accept the certificate "Always" to eliminate the warning message.
Installation on UNIX/Linux uses install.sh; running this fails with a "runGSkit failure: Return error code: 99" and a "install.sh failure: Return error code: 4".
This error can occur for multiple agents even when the TEP displays the managed system in the navigator as expected. The workspace message is KFWITM217E Request error: SQL1_CreateRequest failed, rc=209.
There have been a couple cases a year where a TEMS was running with high enough CPU/Storage resource usage that the customer was concerned. In some cases, the TEMS experienced a steady storage growth and failure after seven or more days. In all recent cases, this condition has been triggered by workloads. Situations are the most common workload but SOAP calls, historical data collection and Portal Client workspaces can be involved.
Do you have some Technotes you'd like to highlight ?
Follow me on Twitter : Andy_M_Jenkins