1 / 36

Finnish/Swedish TUG ITM 6.1 Universal Agent and Log Management

Finnish/Swedish TUG ITM 6.1 Universal Agent and Log Management. 28th November 2006 Mike Hau Tivoli EMEA GRT. Agenda. The Universal Agent Logs How to manage? Where are they?. The Universal Agent. A highly customisable agent Used when no out-of-the-box solutions available

alexa
Download Presentation

Finnish/Swedish TUG ITM 6.1 Universal Agent and Log Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Finnish/Swedish TUG ITM 6.1 Universal Agent and Log Management 28th November 2006 Mike Hau Tivoli EMEA GRT

  2. Agenda • The Universal Agent • Logs • How to manage? • Where are they?

  3. The Universal Agent ... • A highly customisable agent • Used when no out-of-the-box solutions available • The “Swiss Army Knife” of ITM 6.1

  4. How it fits into the ITM 6.1 environment Data Sources TEP Data Sources Data Providers ( DP‘s ) Data Providers ( DP‘s ) TEPS ITM 6.1 Universal Agent ITM 6.1 Universal Agent TEMS ITM 6.1 Standard Agents ( OS, DB’s, applications ), also called IRA’s ( Intelligent Remote Agents )

  5. What is it good for? Use the UA to: • Monitor data that is not supported with other agents. • Monitor only data of interest (through metafile applications) • Respond quickly to changing monitoring and management scenarios. • Provide control of attributes and surfacing of data. • Create an easily expandable solution.

  6. TEMS Hub or remote TEP UA Universal agent - IRA (Intelligent Remote Agent) Data provider (DP) to collect data and issue system commands DP Metafile Data definition file Data source Components, Architecture and Data Flow in Detail

  7. Data Providers • Serve as the data interfaces for the UA, the “ears” of the UA • Receive data from client programs, files, databases etc. and pass it on to the UA IRA. • Data providers run as threads inside the IBM Tivoli Universal Agent process, but useful to view them as autonomous entities Each Data Provider: • May support multiple applications which are defined through metafiles. • Can monitor multiple sources and extract only data that is part of the applications.

  8. The Data Providers ( DP’s ) Universal Agent FILE SOCK API POST HTTP SNMP ODBC SCRP File Collects information from sequential files Socket Provides support for resource connected through TCP/IP or UDP API Provides a set of API calls that can be used from applications, batch files, scripts, or console commands Post Accepts console commands HTTP Monitors Web sites SNMP Includes SNMP components and trap support ODBC Integrates data from ODBC data sources SCRP Script DP integrates data from custom scripts

  9. The File DP • Reads the contents of files on the machine where the UA is installed or networked files via NFS. • Tails files for event type data or complete contents for persistent information • Dynamic file name support for log files with numbers and dates in the name • Support of multiple records, i.e. one logical records built from multiple files

  10. The Socket DP • The UA does not need to reside on the monitored host. Programs can open up a socket connection to the UA across the IP network. • Can have multiple applications and also multiple sources for a single application. • Some programming is required. Any language which supports the socket interface ( Compiler languages, i.e. C/C++, or script languages, i.e. PERL )

  11. The API DP • Allows communication with the UA from C/C++ programs providing an API ( Application Programming Interface ) • Can also be accessed from any script language which can access the product provided API-executables. i.e. VBS or PERL • Built in socket handler

  12. The Post DP • A convenient way to send ad hoc notifications such as messages, alerts, and status. • Uses sockets to send data to a predefined set of attributes. • Best used with the KUMPSEND program which provides a command line interface to the Post Data Provider.Example:kumpsend msg=”text” [cat=category] [dp=dp_hostname][port=dp_listening_port] [ack=Y|N]

  13. The HTTP DP • Allows you to monitor the availability and response time of selected URLs. • Supports HTTPS and proxies • Can control the sampling interval • Averages over a 15 minute period • does not use a metafile for data definition, it uses a file with HTTP information instead

  14. The SNMP DP • Provides the functionality of an SNMP manager to ITM 6.1, including network discovery, trap monitoring, and MIB data collection • Some MDL-converted standard MIBs as well as some product provided MDLs come along with the product. • Customer specific MIBs need to be converted into data definition metafiles. This can be done using a compiler, the process is to file a PMR with Tivoli support • For only receiving traps you don’t need a compiled MIB, but you can configure these traps to be converted into more meaningful expressions using a TRAPCNFG file

  15. The ODBC DP • Allows you to collect data from ODBC-compliant databases using SQL select statements • Supports Stored Procedures - if the DSN (Data Source Name) supports it • Only available on Windows • Can use remote DB’s via ODBC • Can generate Metafiles according to the DB structure • Maps tables and columns in the ODBC data source into attribute groups and attributes in the associated Metafile.

  16. The Script DP • Sends the output of scripts to the UA • Can run the scripts as required • Any script which sends the output to STDOUT or STDERR can be used • Data are processed like any other data from any UA DP

  17. The ASFS DP (9th) • Consolidation of DPs • API • Socket • File • Script • Default DP when UA installed • Has <hostname>ASFSdp as its DP name

  18. Port Requirements – Data Providers • The Universal Agent can be configured to do communications over a variety of ports. Typical ports used by the Universal Agent: • Port 161 Standard SNMP port (used when running SNMP UA) • Port 1919 Data Clearing House port • Port 7500 Socket Data Provider listening port • Port 7575 Post Data Provider listening port • Port 7600 API Data Provider listening port • Port 7700-7710 Console ports (one for each DP that's activated at startup) • These ports can be changed in the app. config files

  19. Logfile Management

  20. Logfiles: How to change tracing • 4 ways to change tracing level • Service Console (Browser based) • All Components • MTEMS • All Components • Managed System • All Components • SPUFI • TEMS • TEP • TEP Only

  21. Service Console – Browser option • Requires port 1920 open to target • Requires local Administrator/Root credentials • Provides dynamic changing of tracing level • Available for all components (TEMS, TEPS, S&P, WP & Agents)

  22. Open http://<hostname>:1920 • Enter Administrator/Root username & Password

  23. Example opening screen of Service Console

  24. Service Console – sub commands Bss1 – Basic System Services • List and change current environment settings • usage : bss1 (command) … (command) • Options : dir, evaluate, config, info, setenv, getenv, listenv • bss1 listenv • bss1 (listenv) (info) • Type ‘?’ for full list of commands • Changes lost on Agent restarted

  25. Service Console – sub commands Ras1 – Reliability, Availability, Serviceability • modifies ras1 filters and display settings • usage : ras1 (command) … (command) • Options : units, ctbld, set, list & log • ras1 (list) • ras1 (list) (log) • Type ‘?’ for full list of commands • Changes lost on Agent restarted

  26. Listing current trace settings

  27. Listing RAS1 units

  28. Manage Tivoli Monitoring Services (MTEMS)

  29. Managed System (Unix / Linux) • Edit <productcode>.ini file directly on the ManagedSystem. • <install_dir>/config/<pc>.ini • Eg : ux.ini, or.ini, ms.ini • Requires Agent restart • <productcode>.config written using .ini

  30. Managed System (Windows) • Edit <productcode>ENV file directly on the Managed System • <install_dir>\TMAITM6\<PC>ENV • Eg : KNTENV, KORENV, KSYENV • Requires Agent restart

  31. SPUFI - to set Dynamic tracing • SPUFI – SQL Parser Using File Input • Tool to issue SQL1 to any TEMS (REMOTE or HUB) • SQL from either CLI or file • <install_dir>\cms\kdstsns.exe on Windows • <install_dir>/<interp>ms/bin/kdstsns on Unix • Can be used to set dynamic traces as well as perform other TEMS diagnostics, e.g. determine current global memory allocation, number of “users” with open SQL queries, etc…

  32. Tivoli Enterprise Portal (TEP) Client • kcjras1.log, kcj.log & kcjerror.log for Desktop Client • <install_dir>\cnp\logs • plugin142.trace for Browser Client • C:\Documents and Settings\Administrator\Application Data\IBM\Java\Deployment\log\plugin142.trace • Important: The TEP client has dynamic logging. Restarting the processes before collecting the logs will rewrite the log.

  33. Tivoli Enterprise Portal (TEP) - RAS1 (Desktop and Browser)

  34. Logfile Management • All logs are cyclic • Default size 5Mb each • 3 or 5 logs per session • All log sizes and number customisable • MTEMS • Manual editing of the ‘<PC>ENV’ or ‘<PC>.ini’ file

  35. Log locations • Agents • Unix/Linux located at <install_dir>/logs • Windows located at <install_dir>\TMAITM6\logs • TEMS & TEPS • <install_dir>/logs • TEP Browser • c:\Documents and Settings\Administrator\Application Data\IBM\Java\Deployment\log\Plugin142.trace • TEP Desktop • <install_dir>/cnp/logs

  36. Questions

More Related