IBM Software Group 1 IBM Tivoli Technical User's Conference


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IBM Software Group 1 IBM Tivoli Technical User's Conference

  1. 1. Chicago, IL C09 Brent Kellis IBM Tivoli Monitoring 6.1 Intro to Deployment and Troubleshooting April 24-27, 2006 ®
  2. 2. Session C09 ITM v6.1: Intro to Deployment and Troubleshooting Brent Kellis [email_address]
  3. 3. Topics <ul><li>ITM v6.1 Deployment Overview </li></ul><ul><li>ITM v6.1 Intro to Troubleshooting & Serviceability </li></ul>
  4. 4. Section 1 ITM v6.1 Deployment Introduction
  5. 5. Deployment / Installation Methods <ul><li>ITM 6.1 installation consists of the several supported methods of installing the solution. </li></ul><ul><ul><li>Local Installation </li></ul></ul><ul><ul><ul><li>Performed at the console or server (remote access or on location) </li></ul></ul></ul><ul><ul><ul><li>Installs components on one host at a time. </li></ul></ul></ul><ul><ul><li>Agent Deployment – Remote Installation (new in ITM 6.1) </li></ul></ul><ul><ul><ul><li>Uses packages or Agent Bundles that can be rolled out to the enterprise from a central location. </li></ul></ul></ul><ul><ul><li>Silent Installation </li></ul></ul><ul><ul><ul><li>Inputs installation information once through a response file instead of repeatedly through a GUI or CLI. </li></ul></ul></ul><ul><li>This presentation is not intended to be a comprehensive installation and configuration guide. </li></ul>
  6. 6. Planning Considerations <ul><li>Approach the deployment from a business objective perspective. </li></ul><ul><ul><li>What conditions impact the business that ITM can address? </li></ul></ul><ul><ul><li>How can we architect the solution to mesh into our existing business processes? </li></ul></ul><ul><ul><ul><li>How people use the solution (help desk, command center, administrators, management, etc.) </li></ul></ul></ul><ul><ul><ul><li>Logical mapping and navigation to match business applications and objectives. </li></ul></ul></ul><ul><li>Understand the technical environment in which the implementation will take place. </li></ul><ul><ul><li>Physical topology. </li></ul></ul><ul><ul><li>Applications being monitored, complexity, and required automation. </li></ul></ul><ul><ul><li>Number and types of TEP users. </li></ul></ul><ul><ul><li>Estimated event volume. </li></ul></ul><ul><ul><li>Integration with other tools and/or consoles. </li></ul></ul>
  7. 7. Planning Considerations <ul><li>There is a fair amount planning that should be done well in advance to ever spinning a CD-ROM. </li></ul><ul><li>Once the planning is complete and has been validated, the installation process should be fairly straight forward. </li></ul><ul><li>Start small with a few key objectives/milestones to work out any problems and gain confidence from your internal customers. </li></ul><ul><li>You can spend your time planning on the front-end, </li></ul><ul><li>or troubleshooting on the back-end. It’s your choice! </li></ul>
  8. 8. Typical ITM 6.1 Architecture <ul><li>Much of this has been already been reviewed in TTEC calls, Tivoli Advisor, etc. </li></ul>
  9. 9. Installation Prerequisites <ul><li>Ensure you understand and meet the pre-requisites </li></ul><ul><ul><li>Hardware </li></ul></ul><ul><ul><li>OS Versions, PTF’s, Service Packs, etc. </li></ul></ul><ul><ul><li>Required database and appropriate version. </li></ul></ul><ul><ul><li>Communication (network) protocols, ports, firewalls. </li></ul></ul><ul><li>Ensure you have the correct binaries & distribution media for the applications you plan to monitor. </li></ul><ul><li>There are special provisions made for upgrading from DM, ITM5, and OMEGAMON XE/DE. Make sure you have planned accordingly. </li></ul>
  10. 10. Local Windows Installation <ul><li>The installation is composed of an InstallShield based installer and several programs used for configuring and managing ITM services. </li></ul><ul><ul><li>Platform and Agent installs are all based on the same code </li></ul></ul><ul><ul><li>Installs GSKit and IBM JRE 1.4.2 as prerequisites. </li></ul></ul><ul><ul><ul><li>For a few TEMA’s, the JRE is not a prerequisite and not installed. </li></ul></ul></ul><ul><ul><ul><li>IBM Tivoli Monitoring provides security through the use of Global Security Toolkit (GSKit) for SSL communications. </li></ul></ul></ul><ul><li>For purposes of this session, we will assume the appropriate database has been previously installed, configured, created and running. </li></ul>
  11. 11. Local Windows Installation <ul><li>The installation “Destination Folder” does not support spaces! </li></ul><ul><li>You will need to provide an encryption key that will be used for all SSL connections. </li></ul><ul><li>During a modification of an existing install, if a user deselects anything, that item will be removed. </li></ul><ul><li>IBM Java 1.4.2 is automatically installed if any component being installed requires it. All servers require it as well as some agents. </li></ul>
  12. 12. Local Windows Installation – TEPS Data Source <ul><li>This datasource (TEPS2 for DB2 and TEPS for MSSQL) is used to store the TEP Server workspaces. </li></ul><ul><li>This dialog is being controlled by DB2DataSource.exe (for DB2) or CNPSDataSource.exe (for MSSQL). </li></ul><ul><li>During an upgrade, the existing datasource will be used. </li></ul><ul><li>If using MS SQL Server, make sure the JDBC driver has been downloaded, installed. </li></ul>
  13. 13. Local Service Configuration and Management <ul><li>Primarily done through Manage Tivoli Enterprise Monitoring Services (kinconfg.exe) – also referred to as MTEMS. </li></ul><ul><li>These programs are run either silently or graphically during in the install when the user is asked for configuration information </li></ul><ul><li>After installation, agents and servers can be managed and reconfigured if needed through the MTEMS interface. </li></ul>
  14. 14. Local UNIX Installation <ul><li>The Install is composed of a command line interface (CLI). </li></ul><ul><ul><li>Although the GUI interface is still present via Candle utilities, it is no longer recommended or supported. </li></ul></ul><ul><li>Use the same Installation Prerequisites and Planning Considerations reviewed earlier in the presentation. </li></ul><ul><li>The overall flow of the installation performed on UNIX is similar to an MS Windows installation. </li></ul><ul><ul><li>Some configuration tasks are initiated in a different order. </li></ul></ul><ul><ul><li>Install one product / component at a time. </li></ul></ul>
  15. 15. Local UNIX Installation <ul><li>User will need to provide: </li></ul><ul><ul><li>Encryption key. </li></ul></ul><ul><ul><li>UNIX platform type (usually pre-selected by installation script). </li></ul></ul><ul><ul><li>Products or components to be installed. </li></ul></ul><ul><ul><li>Tivoli Enterprise Management Server (TEMS) name. </li></ul></ul><ul><li>Some ITM 6.1 infrastructure components are currently not supported on a UNIX platform. </li></ul>
  16. 16. Local UNIX Installation – Screen Captures <ul><li>Installation interface started by executing </li></ul>
  17. 17. Local UNIX Installation & Management <ul><li>Install </li></ul><ul><ul><li> – Install products </li></ul></ul><ul><ul><li> – Uninstall products </li></ul></ul><ul><li>Config </li></ul><ul><ul><li>itmcmd config – Configure agents (including TEP/TEPS) or servers </li></ul></ul><ul><ul><li>itmcmd support – Add product support for TEMS </li></ul></ul><ul><li>Manage </li></ul><ul><ul><li>itmcmd agent – Start/stop an agent (including TEP/TEPS) </li></ul></ul><ul><ul><li>itmcmd server – Start/stop a TEMS </li></ul></ul><ul><li>itmcmd has many other variations for the UNIX platforms. </li></ul>
  18. 18. Agent Deployment – Introduction <ul><li>Agent Deployment provides the ability to deploy and/or update agents from a central location. </li></ul><ul><li>There are two types of agent deployments </li></ul><ul><ul><li>OS agent deployment using the CreateNode command. </li></ul></ul><ul><ul><li>Non-OS agent (such as the DB2 agent) deployment using the Tivoli Enterprise Portal GUI (for other non-OS agents) or the addSystem command. </li></ul></ul><ul><li>Non-OS agent deployment requires an existing OS Agent to be installed and running on the target host. </li></ul>
  19. 19. Agent Deployment – Component Overview <ul><li>ITM 6.1 OS TEMA’s </li></ul><ul><ul><li>Have been enhanced to handle agent deployment activities at the agent end. </li></ul></ul><ul><ul><li>Launches local installation and configuration commands </li></ul></ul><ul><ul><li>Sends status information to the deployment controller </li></ul></ul><ul><li>Agent Depot </li></ul><ul><ul><li>A repository of agent bundles that a Management Server can access during agent deployment. ( tacmd viewdepot or tacmd listbundles ) </li></ul></ul><ul><li>Deployment Controller </li></ul><ul><ul><li>A service on the Management Server whose role is to act as the driver for the deployment. </li></ul></ul><ul><ul><li>The Deployment Controller queries the contents of the agent depot and transfers agent bundles using Remote Procedure Calls (RPC) </li></ul></ul>
  20. 20. Agent Deployment - Process <ul><li>Agent deployment consists of carrying out a list of generic activities that need to take place in order to set up a functioning monitoring agent on a machine. </li></ul><ul><li>These activities consist of: </li></ul><ul><ul><li>determining which agents are already deployed </li></ul></ul><ul><ul><li>transferring necessary agent bundles </li></ul></ul><ul><ul><li>installing agent bundles </li></ul></ul><ul><ul><li>configuring agent instances </li></ul></ul><ul><ul><li>starting monitoring agent instances. </li></ul></ul>
  21. 21. Application Agent Deployment – TACMD CLI <ul><li>Using the tacmd command, users can </li></ul><ul><ul><li>Perform agent deployment </li></ul></ul><ul><ul><li>Perform administrative tasks on agents an </li></ul></ul><ul><ul><li>Maintain agent depot </li></ul></ul><ul><ul><li>Perform situation maintenance and basic operations </li></ul></ul><ul><li>tacmd uses the Simple Object Access Protocol (SOAP) service on TEMS. </li></ul>
  22. 22. OS Agent Deployment – TACMD CLI <ul><li>ITM 6.1 OS agents are required to accommodate the deployment process. </li></ul><ul><ul><li>The OS agent installs the required infrastructure for remote deployment and maintenance. </li></ul></ul><ul><li>Installing the initial OS agent can be done remotely, but follows a specific process using the CreateNode command after doing a tacmd login. </li></ul>
  23. 23. Agent Deployment – Add via TEP <ul><li>Agent deployment options are displayed for systems that have deployment-enabled OS agents. </li></ul>
  24. 24. Agent Deployment – Manage via TEP <ul><li>Agent administration options can be executed on agents that are “deployment-enabled” </li></ul>
  25. 25. Agent Deployment & Management – Which method to use? <ul><li>Initial Deploy </li></ul><ul><ul><li>Non-OS agent – TEP or tacmd addSystem </li></ul></ul><ul><ul><li>OS agent – tacmd createnode command </li></ul></ul><ul><li>Remove/Uninstall - TEP </li></ul><ul><li>Upgrade – TEP or tacmd updateAgent </li></ul><ul><li>Start/Stop/Restart – TEP or tacmd startAgent, stopAgent, restartAgent </li></ul><ul><li>Add/Remove Instance </li></ul><ul><ul><li>TEP or tacmd addSystem </li></ul></ul><ul><ul><li>TEP for Remove </li></ul></ul><ul><li>Reconfigure – TEP or tacmd configureSystem </li></ul>
  26. 26. Silent Installation <ul><li>This method of installation is useful for advanced users who prefer to input installation information once through a response file instead of repeatedly through a GUI or CLI. </li></ul><ul><li>Can be used for Windows and UNIX installations </li></ul><ul><li>A sample silent installation response file ( silent.txt) is provided on the product CD. </li></ul><ul><li>Complete instructions are documented in the manual as well as in silent.txt . </li></ul><ul><li>Running the silent installation </li></ul><ul><li>Setup /z&quot;/sfC: empSILENT.TXT&quot; /s /f2&quot;C: empsilent_setup.log&quot; </li></ul><ul><li>(see doc for parm definition) </li></ul>
  27. 27. Silent Installation - silent.txt
  28. 28. Section 2 ITM 6.1 Intro to Troubleshooting & Serviceability
  29. 29. Introduction <ul><li>Serviceability </li></ul><ul><ul><li>One of the goals of Serviceability is to improve customer satisfaction by making problem resolution more efficient and accurate </li></ul></ul><ul><li>Provide tools to troubleshoot and get the product deployed </li></ul><ul><li>General rule: 90 percent of occurring problems are related in misunderstanding or in the environment of the installation. Only 10 percent are actual defects… (remember the planning slide!) </li></ul>
  30. 30. Considerations <ul><li>General troubleshooting skills are essential </li></ul><ul><li>Rule out general issues </li></ul><ul><ul><li>Network issues </li></ul></ul><ul><ul><ul><li>IP/Name resolution </li></ul></ul></ul><ul><ul><ul><li>Protocols in use </li></ul></ul></ul><ul><ul><ul><li>Firewalls/port restrictions </li></ul></ul></ul><ul><ul><li>Database issues </li></ul></ul><ul><ul><ul><li>Database running </li></ul></ul></ul><ul><ul><ul><li>Database access </li></ul></ul></ul><ul><ul><ul><li>Invalid Queries </li></ul></ul></ul><ul><ul><li>User issues </li></ul></ul><ul><ul><ul><li>User ID/password </li></ul></ul></ul><ul><ul><li>Tracing and Logs </li></ul></ul><ul><ul><ul><li>TEMS, TEPS, Agents </li></ul></ul></ul>
  31. 31. Network Issues <ul><li>Name resolution </li></ul><ul><ul><li>Ping the server/agent using name and IP </li></ul></ul><ul><ul><li>If configured with fully qualified hostname ensure it can be resolved </li></ul></ul><ul><ul><ul><li>There is a 32 character Managed System name limitation </li></ul></ul></ul><ul><li>Protocols in use </li></ul><ul><ul><li>IP.PIPE, IP.SPIPE, IP.UDP & SNA </li></ul></ul><ul><ul><li>Ensure that the components use a protocol that is configured. </li></ul></ul><ul><ul><ul><li>For example: Agent configured to use IP.SPIPE make sure that the TEMS is configured with at least one protocol to be IP.SPIPE. </li></ul></ul></ul><ul><li>Firewalls </li></ul><ul><ul><li>TEPS access configured using KFW_INTERFACES, KFW_INTERFACE_name_PORT </li></ul></ul><ul><ul><li>See ITM 6.1 Installation Guide section on firewall scenarios for TEPS </li></ul></ul><ul><li>Ports </li></ul><ul><ul><li>Ensure the ports used by the product are not blocked </li></ul></ul><ul><ul><li>1918 default for TEMS </li></ul></ul><ul><ul><li>1920 default URL port to connect to TEPS </li></ul></ul><ul><ul><li>15001 default TEPS port for IOR </li></ul></ul><ul><ul><li>3601 default Warehouse proxy port (Historical collection) </li></ul></ul><ul><ul><li>1919 default UA port for primary UA </li></ul></ul><ul><li>Multiple NIC’s and Virtual Machines </li></ul>
  32. 32. Database Issues <ul><li>Ensure that the database server is running: </li></ul><ul><ul><li>TEPS (example DB2) </li></ul></ul><ul><ul><ul><li>db2 connect to teps user db2admin using <passwd> </li></ul></ul></ul><ul><ul><ul><li>db2 select * from teps.kfwdbver </li></ul></ul></ul><ul><ul><ul><li>RLSESTAMP MIGRATIONDATE FROMRLS </li></ul></ul></ul><ul><ul><ul><li>v610_kcj5293b 2005-11-29- v610_kcj5293b </li></ul></ul></ul><ul><li>Has the password been reset on the TEPS user? </li></ul><ul><ul><li>+438BC885.0000 SQLSTATE: 08001, ERR: -30082, MSG: [IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason &quot;24&quot; (&quot; USERNAME AND/OR PASSWORD INVALID &quot;). SQLSTATE=08001 </li></ul></ul>
  33. 33. Database Issues – SQL Errors <ul><li>Some views within a workspace are either unpopulated or non-existent. </li></ul><ul><ul><li>Usually implies application support has not been added for the products your are attempting to monitor. </li></ul></ul><ul><ul><li>Logs will indicate bad queries being made or SQL errors. </li></ul></ul><ul><li>Make sure you have added application support to the TEMS/TEPS for the TEMA’s you have installed. </li></ul><ul><li>Similar problems can introduced in upgraded environments (OMXE  ITM 6.1) and is frequently caused by mis-matched versions of application support. </li></ul><ul><ul><li>Ensure application support is applied uniformly to the environment after upgrading components. </li></ul></ul><ul><ul><li>Also referred to as data definition files or seed data in the documentation. </li></ul></ul>
  34. 34. User Issues – TEPS login <ul><li>Does the User ID exist as a user in the TEPS? </li></ul><ul><ul><li>Check the existence of the user in the TEPS </li></ul></ul><ul><ul><li>Can also check in the TEPS database: </li></ul></ul><ul><ul><ul><li>select id, name from teps.kfwuser </li></ul></ul></ul><ul><li>Is security enabled on the TEMS? </li></ul><ul><ul><li>If yes, then make sure that the user also exists on the TEMS </li></ul></ul><ul><li>Currently the TEMS uses native operating system for authentication </li></ul><ul><ul><li>Also uses Windows Domain Accounts </li></ul></ul><ul><li>User ID is limited to 10 characters without spaces </li></ul>
  35. 35. Trace Facilities and Logs <ul><li>Trace settings </li></ul><ul><ul><li>Default is normally ERROR </li></ul></ul><ul><ul><li>Trace levels are relatively easy to change and can be set dynamically in many cases. </li></ul></ul><ul><ul><ul><li>ini & config files </li></ul></ul></ul><ul><ul><ul><li>GUI interface for some components & TEMA’s </li></ul></ul></ul><ul><ul><ul><li>ITM Service Console </li></ul></ul></ul><ul><ul><li>Improperly set or left unchecked, some trace levels can have a severe impact on host performance. Thus, IBM currently recommends setting trace levels only under the direction of Tivoli Support. </li></ul></ul>
  36. 36. <ul><li>!438C503E.0000!========================> IBM Tivoli RAS1 Service Log <======================== </li></ul><ul><li>+438C503E.0000 System Name: REDBEARD Process ID: 752 </li></ul><ul><li>+438C503E.0000 Program Name: kfwservices User Name: SYSTEM </li></ul><ul><li>+438C503E.0000 Task Name: kfwservices System Type: WinXP;5.1-SP1 </li></ul><ul><li>+438C503E.0000 MAC1_ENV Macro: 0xC112 Start Date: 2005/11/29 </li></ul><ul><li>+438C503E.0000 Start Time: 07:57:34 CPU Count: 1 </li></ul><ul><li>+438C503E.0000 Page Size: 4K Phys Memory: 2047M </li></ul><ul><li>+438C503E.0000 Virt Memory: 2048M Page Space: 3944M </li></ul><ul><li>+438C503E.0000 Service Point: system.redbeard_cq UTC Start Time: 438c503e </li></ul><ul><li>+438C503E.0000 ITM Home: C:IBMITM ITM Process: redbeard_cq </li></ul><ul><li>+438C503E.0000 Executable Name: C:IBMITMCNPSkfwservices.exe </li></ul><ul><li>+438C503E.0000 KBB_RAS1: ERROR (UNIT:ctdatabus INPUT,ERROR) (UNIT:ctsql INPUT,ERROR) </li></ul><ul><li>+438C503E.0000 KBB_RAS1_LOG: C:IBMITMlogsREDBEARD_cq_438c503e-.log INVENTORY=C:IBMITMlogsREDBEARD_cq.inv MAXFILES=32 LIMIT=5 COUNT=5 PRESERVE=1 </li></ul><ul><li>+438C503E.0000 KBB_ENVPATH: C:IBMITMCNPSKFWENV </li></ul><ul><li>+438C503E.0000 ================================================================================ </li></ul><ul><li>(438C503E.0000-2F4:RAS1,400,&quot;CTBLD&quot;) </li></ul><ul><li>+438C503E.0000 Component: kbb </li></ul><ul><li>+438C503E.0000 Driver: d5298a/3581245.1 </li></ul><ul><li>+438C503E.0000 Timestamp: Oct 25 2005 21:05:42 </li></ul><ul><li>+438C503E.0000 Target: wv7i386 </li></ul><ul><li>(438C503E.0001-2F4:RAS1,400,&quot;CTBLD&quot;) </li></ul><ul><li>+438C503E.0001 Component: kcj </li></ul><ul><li>+438C503E.0001 Driver: kcj/CTTools/ctbld00.ctb, CTTools, TOP_dev_stage2, v610_kcj5293b/3581245.23 </li></ul>Trace Log – Sample Header TEPS Log Build level Trace setting Component (TEPS) Installation directory Env file
  37. 37. Select Log File Locations install_dir/logs/kuiras1.log KUI/UI Command line - tacmd - UNIX/Linux install_dirinkuiras1.log KUI/UI Command line - tacmd - Windows install_dir/logs/hostname_hd_timestamp-##.log KHD/HD Warehouse Proxy - Windows only install_dir/logs (varies by agent) - RAS1 - hostname_xx_component_timestamp-##.log - Operations - *.LG0 and *.LG1 Depends Tivoli Enterprise Monitoring Agents (TEMA) - UNIX/Linux install_dir maitm6logs (varies by agent) - RAS1 - hostname_xx_component_timestamp-##.log - Operations - *.LG0 and *.LG1 Depends Tivoli Enterprise Monitoring Agents (TEMA) - Windows install_dir/logs/hostname_ms_timestamp-##.log KMS/MS Tivoli Enterprise Monitoring Server (TEMS) - Windows and UNIX/Linux install_dir/logs/hostname_cq_timestamp-##.log KCQ/CQ Tivoli Enterprise Portal Server (TEPS) - Linux install_dirlogshostname_cq_timestamp-##.log KFW/FW (logs use the UNIX code of CQ) Tivoli Enterprise Portal Server (TEPS) - Windows Location Component code (three letter/two letter) Component
  38. 38. Select Log File Locations - continued Endpoint logs: $LCF_DATDIR/LCFNEW/KTM/logs/epname_tm_timestamp-xx.log KTM/TM ITM 5.x Monitoring Agent TMR logs: $DBDIR/KTM/logs     Windows - use %DBDIR% or %LCF_DATDIR%     db2prep.log - TEPS configuration log - assuming DB2 is the database.     InstallPresentation.log - TEPS seeding log.     candle_installation.log - Main installation log.     install_dir/logs   Installation logs - UNIX/Linux Warehouse_Configuration.log - Configuration of the Warehouse proxy.     TEPS_ODBC.log - Configuration of the TEPS ODBC connection.     IBM Tivoli Monitoring date PID.log - Main installation log.     install_dirInstallITM   Installation logs - Windows install_dir/logs/hostname_sy_timesta mp-xx.log KSY/SY Summarization and Pruning Agent install_dir/logs/hostname_ci_<tems pid>.log KCI/CI Seeding process - UNIX/Linux install_dir InstallITMlogsCMSSeed.log for the TEMS     install_dirCNPSlogsseedPPC.log - PPC is the component code KCI/CI Seeding process - Windows
  39. 39. Key ITM 6.1 Processes <ul><li>Windows </li></ul><ul><ul><li>TEP browser client iexplore.exe </li></ul></ul><ul><ul><li>TEP desktop clientjava.exe </li></ul></ul><ul><ul><li>TEP Server KfwServices.exe </li></ul></ul><ul><ul><li>TEMS kdsmain.exe and cms.exe </li></ul></ul><ul><ul><li>Windows Agent kntcma.exe </li></ul></ul><ul><ul><li>Universal Agent kuma610.exe </li></ul></ul><ul><ul><li>Other Agents <pc>*.exe where <pc>=product code </li></ul></ul><ul><ul><li>MTEMS kinconfg.exe </li></ul></ul><ul><li>UNIX </li></ul><ul><ul><li>TEMS kdsmain and cms </li></ul></ul><ul><ul><li>UNIX OS Agent kuxagent </li></ul></ul><ul><ul><li>UNIX log Agent kulagent </li></ul></ul>
  40. 40. Additional Sources for Information <ul><li>Tivoli Advisor, Issue 6, September 2005 </li></ul><ul><li>ITM 6 Installation and Setup Guide, GC32-9407-00 </li></ul><ul><li>IBM Redbook – Getting Started with IBM Tivoli Monitoring v6.1 on Distributed Environments, SG24-7143-00. </li></ul><ul><li>IBM Redbook - Deployment Guide Series: IBM Tivoli Monitoring 6.1, SG24-7188-00. </li></ul><ul><li>IBM Redbook - Certification Guide Series: IBM Tivoli Monitoring 6.1, SG24-7187-00. </li></ul><ul><li>IBM Tivoli Monitoring 6.1 On-Line Documentation: </li></ul><ul><li> </li></ul><ul><li>IBM Tivoli Monitoring Public Website: </li></ul><ul><li> </li></ul>
  41. 41. Questions……