© 2009 IBM Corporation © 2010 IBM Corporation Maintaining Your ITM Environment Tips to Help Scott Wallace - [email protected]

© 2009 IBM Corporation

© 2010 IBM Corporation

Maintaining Your ITM Environment

Tips to Help

Scott Wallace - [email protected]

2© 2010 IBM Corporation

Agenda

■ Overview■ Self monitoring■ Collecting logs/configuration data (pdcollect)

■ Converting timestamps in RAS1 logs■ Online Resources


Overview

■ Goal of this session is to provide you some tips to servicing your ITM environment.

■ The IT environment is distributed across your business so the Tivoli monitoring of your resources is also distributed across the environment.

■ Reality is that you will encounter challenges in the environment – network issues, database issues, unexpected changes and others.

■ These challenges can impact your ITM environment and require that you take steps to service ITM.


Self Monitoring – Workspaces

■ Several ITM components provide self monitoring workspaces to help manage those resources

– TEMS / TEPS– Warehouse Proxy and Summarization/Pruning Agents– Agentless Agents


TEMS – Self Monitoring Topology


Warehouse Proxy Agent


Summarization and Pruning Agent


Warehouse Agents – Situations

■ Pre-defined situations– Automatically started– Warehouse Proxy

• KHD_DB_Connectivity• KHD_Error_Fatal • KHD_Error_Critical

– Summarization & Pruning• KSY_Summarization_Failures • KSY_DB_Connectivity_Fail • KSY_TEPS_Connectivity_Fail • KSY_Pruning_Failures

■ Agent User's Guides contain details on the attributes and attribute groups


Agentless Monitoring Health

■ Each remote monitor has self-monitoring attribute tables that can be used to monitor the collection process:

■ Subset of Performance Object Status attributes:

– Last collection start/finish times– Number of collections– Intervals skipped (most useful)

■ It is recommended that an Operating System agent be co-deployed to the Agentless Monitoring Server to watch CPU, Memory, and Network utilization of the monitors


Self Monitoring – Agent Management Services

■ Agent Management Services monitors the availability of agents and automatically takes action if the agent is not responsive.

■ It also provides workspaces with views for a set of base agents including the OS agents, Warehouse agents, Universal Agent and Agentless agents.


Collecting logs/configuration data - pdcollect

■ ITM provides a common tool to collect problem determination data (pdcollect).

■ Provides a comprehensive and consistent interface for collecting logs/data for IBM Support

■ Provided for many ITM platforms including Linux, UNIX, Windows and z/OS

■ Allows you to collect a snapshot of the TEPS database

■ Allows you to collect logs/data locally or remotely


ITM 6.2.1 FP03 – enhancements to pdcollect

Allows customer to name the archive file (recommendation is to have the PMR number as the file name)

Introduces ability to snapshot the TEPS database. Updated for data/log currency with product updates Invoked from tacmd to make it consistent with all other ITM commands.

Technote: http://www.ibm.com/support/docview.wss?uid=swg21446655


Sample pdcollect commands

tacmd pdcollect -d /opt/pmrs -o nohist -a pmr12345.499.000_pdcollect_tems Specify a local directory for the archive with the -d

Do not use the CANDLEHOME for this location Specify the archive name with the -a Specify options with the -o

tacmd pdcollect -s agent1 -u root -d /usr/local/tmp -c /opt/IBM/ITM -o nohist -a pmr12345.000.000_pdcollect_agent

Remote collection requires a login ID on the target system Specify location of ITM with -c

Pre-FP03 defaults to /opt/ibm/itm on UNIX/Linux tacmd pdcollect -d /opt/pmrs -o nohist nologs -a pmr12345.499.000_teps_database -m

Export the TEPS database with the -m Note that these commands are using the updated pdcollect with ITM 6.2.1 FP03


Timestamps in the RAS1 Logs

■ RAS1 logs serve the purpose of providing detailed information on what the ITM processes are doing.

■ They contain a wealth of information especially with the correct trace level set

■ There is a hex timestamp at the begging of each line

■ So how do you convert this timestamp from hex to one you can use?– Use the TMS Log Viewer– Get a script from your favorite Support person

You Support

Please send me that cool

script.

Sure – are you aware of ras1log?


Converting timestamps - ras1log

■ ras1log– Located in Installdir/bin directory on Linux/UNIX/Windows– Converts timestamp and redirects input log file to stdout

■ ras1log <filename>– Defaults to UTC– Use the “-l” flag to change to local time of the system where it is run


Some Gotchas With These Tools

■ Agent Management Services (watchdog) – Multiple copies of OS agent running

• IZ76377 – watchdog using “cinfo -R” instead of “cinfo -r”• IZ78695 – multiple copies of OS agent running• http://www.ibm.com/support/docview.wss?uid=swg21445312

– See technote for fix versions– Multiple copies of cscript running on Windows

• http://www.ibm.com/support/docview.wss?uid=swg21429650

■ Issues with pdcollect– ITM 6.2.1 not collecting logs

• IZ42589 – does not collect logs• Fixed in ITM 6.2.1 FP01• http://www.ibm.com/support/docview.wss?uid=swg21368486


Online Resources

■ IBM Support Portal– https://www.ibm.com/support/entry/myportal

■ IBM Education Assistant for ITM– http://www.ibm.com/support/docview.wss?rs=2366&uid=swg21393195

■ Tivoli Media Gallery– https://www.ibm.com/developerworks/wikis/display/tivolimediagallery/Home

■ Tivoli Monitoring Wiki on developerWorks– https://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

■ IBM Fix Central– http://www.ibm.com/support/fixcentral/


ITM Support Portal

■ Provides you access to a wealth of information for your ITM environment!


Wrap Up

Are you aware of these features?

Do you use these features to improve your ITM experience?

What can we do to enhance these features for you?

Documents

© 2009 IBM Corporation © 2010 IBM Corporation Maintaining Your ITM Environment Tips to Help Scott Wallace - [email protected]