TME 10 Reporter Release Notes

Transcription

1 TME 10 Reporter Release Notes Version 2.0 April, 1997

2

3 TME 10 Reporter (April 1997) Copyright Notice Copyright 1991, 1997 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication, or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, NetView, Tivoli Management Environment, and TME 10. Other company, product, and service names mentioned in this document are trademarks or registered trademarks of their respective manufacturers. These company, product, and service names might be denoted by a double asterisk (**) at their first occurrence in this publication. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System's or IBM's valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Patents may be pending.

4 iv Version 2.0

5 TME 10 Reporter Release Notes Components, Requirements, and Installation New Components Application Response Measurement (ARM) Reporting Tivoli Enterprise Console Reporting Tivoli/Inventory Reporting Tivoli/Sentry Reporting Known Defects in This Release Documentation Supported Environments Tivoli Management Platform Requirements Disk Space Requirements Hardware Requirements Software Requirements Installation Instructions Additional Useful Information TME 10 Reporter: Release Notes v

6 vi Version 2.0

7 1 Components, Requirements, and Installation Components, Requirements, and Installation The following Release Notes provide important information about using TME 10 Reporter, Version 2.0 on the following hardware platforms: IBM RS/6000 systems running AIX IBM RS/6000 systems running AIX 4.1.2, or later Sun SPARC systems running Solaris 1.1 Sun SPARC systems running Solaris 2.3, or later HP 9000/700 and HP 9000/800 series systems running on HP-UX 9.3, or later Please read these notes thoroughly before installing or using this software. The release notes contain important information about the following: New components Supported environments Known defects in this release Installation instructions Additional useful information TME 10 Reporter: Release Notes 1-1

8 New Components New Components Application Response Measurement (ARM) Reporting This new component allows you to store the ARM data into the TME 10 Reporter database, and display them on 15 reports. The data is collected by the TME 10 ARM Agents, put into a log file, and sent to the TME 10 Reporter manager that processes it. At the end of processing, the ARM data is available in the database for reporting. Tivoli Enterprise Console Reporting This new component allows you to display some reports on data retrieved from the T/EC relational database. In this case, TME 10 Reporter is used as a general purpose reporter, because it does not use data from its tables, but retrieves it directly from T/EC data tables. A set of 6 reports is provided. Tivoli/Inventory Reporting This new component allows you to display some reports on data retrieved from the Inventory relational database. In this case, TME 10 Reporter is used as a general purpose reporter, because it does not use data from its tables, but retrieves it directly from Inventory data tables. A set of 7 reports is provided. Tivoli/Sentry Reporting This new component allows you to display 14 reports on data retrieved from the Tivoli/Sentry application. The data is collected by the Sentry agent, stored in a log file, and sent to the TME 10 Reporter manager that processes it. At the end of processing, the Sentry data is available in the database for reporting. The reports can display data retrieved from all UNIX platforms supported by the Reporter agents and from Windows NT 3.51 and 4.0. Following is a list of the predefined reports provided with the Tivoli/Sentry component (the query files are located under /usr/lpp/perfrep/def/en_us). 1-2 Version 2.0

9 New Components All Sentry NT Monitors A complete view of 67 NT monitors gathered by the Tivoli/Sentry application, detailed by hourly, daily, and weekly trends. The query files are pr_sentry_all_nt_h.sql, pr_sentry_all_nt_d.sql, and pr_sentry_all_nt_w.sql. All Sentry UNIX Monitors A complete view of 27 UNIX monitors gathered by the Tivoli/Sentry application, detailed by hourly, daily, and weekly trends. The query files are pr_sentry_all_unix_h.sql, pr_sentry_all_unix_d.sql, and pr_sentry_all_unix_w.sql. Sentry UNIX Disk Resources Monitors A detailed view of the UNIX disk resources monitors. The query file is pr_sentry_undiskres_d.sql. Sentry UNIX System Monitors A detailed view of the UNIX system monitors. The query file is pr_sentry_unsystem_d.sql. Sentry UNIX Network Monitors A detailed view of the network monitors. The query file is pr_sentry_unnetwork_d.sql. Sentry NT Processor Monitors A detailed view of the NT processor monitors. The query file is pr_sentry_ntprocessor_d.sql. Sentry NT TCP Monitors A detailed view of the NT TCP monitors. The query file is pr_sentry_nttcp_d.sql. Sentry NT Memory Monitors A detailed view of the NT memory monitors. The query file is pr_sentry_ntmemory_d.sql. Sentry NT Server Monitors A detailed view of the NT server monitors. The query file is pr_sentry_ntserver_d.sql. Sentry NT System Monitors A detailed view of the NT system monitors. The query file is pr_sentry_ntsystem_d.sql. Components, Requirements, and Installation TME 10 Reporter: Release Notes 1-3

10 New Components To be processed by TME 10 Reporter, the log file created by the Tivoli/Sentry application must comply with the following: The message style of the log file must be Local format 1. The log file path must be /tmp/filenamesentry.log (for UNIX) or \temp\filenamesentry.log (for Windows NT), where filename is the name you want to assign to the log file. Ensure that the name of the Sentry profile to generate the log file does not contain a vertical bar ( ). For more information about Sentry profiles, see the Tivoli/Sentry User's Guide. To ensure that the Sentry data can be displayed with TME 10 Reporter, the data collected at each Sentry agent must be processed and sent to the TME 10 Reporter manager. To do so, create a task by running the prinstall script (provided with TME 10 Reporter under /usr/lpp/perfrep/bin) at the workstation where the TME 10 Desktop is installed. The script creates: A policy region named Reporter Region A task library named Reporter Library A task named SendSentryLogToReporter You can execute the task manually or by scheduling a job. To execute the task manually: 1. From the TME 10 Desktop, double-click on the Reporter Region icon. 2. On the Policy Region: Reporter Region window, double-click on the Reporter Library icon. 3. On the Task Library: Reporter Library window, click with the right mouse button on the SendSentryLogToReporter icon and select Execute Task. 4. On the Execute Task window, from the Available Task Endpoints list, select the workstations where to execute the task and click on the left arrow button. The selected workstations are moved to the Selected Task Endpoints list. 1-4 Version 2.0

11 Known Defects In the Execution Parameters list, ensure that the value specified as Timeout is adequate to the time needed to process the Sentry log file. Click on the Execute push button. 5. On the SendSentryLogToReporter window, specify the address, login, and password of the TME 10 Reporter manager respectively in the Reporter Host Address, Reporter Host Login, and Reporter Host Password fields. Specify the directory where to store the log file at destination in the Reporter Host Directory field. 6. Click on the Set & Execute push button. Each log file is sent at destination after being renamed as node.sentry.dyymmdd, where node is the name of the node where the data was collected and yymmdd is the date on which the data was collected. To execute a task by scheduling a job, see the TME 10 Framework User's Guide for more information. Components, Requirements, and Installation Known Defects in This Release This section describes known defects in this release of TME 10 Reporter. Where applicable and known, suggested work-arounds are identified. The defects are listed by category. For each defect a tracking number is assigned. Note that this may not be a complete list of defects. Documentation 1. In the Installation and Admnistration manual, on page 4-14, change the information contained in Setting Up Tivoli Enterprise Console, to read as follows: The Tivoli Enterprise Console (T/EC) component generates reports that read data directly from the T/EC database. Hence, to work with the T/EC component, Reporter must be installed on the T/EC database. The T/EC database must reside on the TME 10 Reporter: Release Notes 1-5

12 Known Defects Reporter manager or be accessible from the manager via the database client. To ensure that the database management system works correctly with Reporter, follow the instructions given in Setting Up the Database Management System on page 3-4 replacing the environment variables with the values appropriate to the T/EC database. For T/EC 2.6, use the following values: SYBASE=$BINDIR/TME/TEC/sybase DSQUERY=TEC PATH=$PATH:$SYBASE/bin For T/EC 3.1, use the same database environment variables that you set when you installed T/EC 3.1 (depending on the Oracle or Sybase database you are using). If you are using Sybase, after customizing the database perform the following steps to grant database authority to the Reporter default user PERFREP. For T/EC 2.6, enter: isql -Usa -P 1> use tec 1> grant select on tec_t_evt_rep to PERFREP 1> grant select on tec_t_severity to PERFREP For T/EC 3.1, enter: isql -Usa -P 1> use tec 1> grant select on tec.tec_t_evt_rep to PERFREP 1> grant select on tec.tec_t_severity to PERFREP Note that when you installed T/EC 3.1, the default value used for the database name and table prefix was tec. If you changed these defaults, be sure to use the correct value when you grant database authority to the user PERFREP (for Sybase). Additionally, be sure to edit the report query files and change 1-6 Version 2.0

13 Known Defects the table prefix in the SELECT statement, when reporting (for Sybase and Oracle). If you have not installed T/EC 3.1 yet, it is recommended that you do not change those default. After installation, you do not need to activate the T/EC component or start data gathering, because reports are generated automatically and data is collected directly from the T/EC database. Following is a list of the predefined reports provided with the T/EC component (the query files are located in the /usr/lpp/perfrep/def/en_us directory): T/EC General Summary A complete and detailed view of the T/EC main table. The query file is pr_tec_gen.sql. T/EC General Summary with Parameters A filtered view from the T/EC main table. You are prompted to enter values for the query parameters Hostname, Class, and Source. The query file is pr_tec_parm.sql. T/EC Summary by Event Timestamp A filtered view from the T/EC main table. You are prompted to enter values for the query parameters From date and To date. The query file is pr_tec_date.sql. T/EC Summary by Event Severity A filtered view from the T/EC main table. You are prompted to enter a value for the query parameter Severity. The query file is pr_tec_sev.sql. T/EC Open Events by Event Severity A filtered view from the T/EC main table. You are prompted to enter a value for the query parameter Severity. The query file is pr_tec_open.sql. Components, Requirements, and Installation TME 10 Reporter: Release Notes 1-7

14 Known Defects T/EC Closed Events by Event Severity A filtered view from the T/EC main table. You are prompted to enter a value for the query parameter Severity. The query file is pr_tec_closed.sql. TME 10 Reporter supports both T/EC 2.6 and 3.1, but at installation time T/EC 3.1 is set by default. To generate reports on T/EC 2.6, you must rename the query files provided under /usr/lpp/perfrep/def/en_us. For each query file, an equivalent file with the extention tec26 is given. For example, the query file pr_tec_gen.sql has an equivalent pr_tec_gen.sql.tec26, which is needed only with T/EC 2.6. To rename the query files, from an AIX command line, in the /usr/lpp/perfrep/def/en_us directory, enter: mv filename filename.tec31 mv filename.tec26 filename where filename is the name of the query file you are renaming. 2. In the Installation and Admnistration manual, on page 4-15, change the information contained in Setting Up Tivoli/Inventory, to read as follows: After customizing the database, perform the following steps to grant database authority to the Reporter default user PERFREP (this is needed only if you are using Sybase). 1-8 Version 2.0

15 Enter: Known Defects isql -Usa -P 1> use inventory 1> grant select on tivoli.inventorydata to PERFREP 1> grant select on tivoli.processor_view to PERFREP 1> grant select on tivoli.memory_view to PERFREP 1> grant select on tivoli.computer_view to PERFREP 1> grant select on tivoli.installed_software_view to PERFREP 1> grant select on tivoli.basenode_view to PERFREP 1> grant select on tivoli.managednode_view to PERFREP Components, Requirements, and Installation After installation, you do not need to activate the Tivoli/Inventory component or start data gathering, because reports are generated automatically and data is collected directly from the Tivoli/Inventory database. TME 10 Reporter supports both Tivoli/Inventory 3.0 and 3.1, but at installation time Tivoli/Inventory 3.1 is set by default. To generate reports on Tivoli/Inventory 3.0, you must rename the query files provided under /usr/lpp/perfrep/def/en_us. For each query file, an equivalent file with the extention inv30 is given. For example, the query file pr_inv_data.sql has an equivalent pr_inv_data.sql.inv30, which is needed only with Tivoli/Inventory 3.0. To rename the query files, from an AIX command line, in the /usr/lpp/perfrep/def/en_us directory, enter: mv filename filename.inv31 mv filename.inv3 filename where filename is the name of the query file you are renaming. TME 10 Reporter: Release Notes 1-9

16 Supported Environments Supported Environments This section describes the hardware and software requirements for TME 10 Reporter on the systems mentioned above. For details on additional platform support, contact Tivoli at TIVOLI-8 or your customer support representative. Tivoli Management Platform Requirements This version of TME 10 Reporter requires version 3.1 (or later) of the Tivoli Management Platform (TMP). If you have a previous version and require an upgrade, you should follow the TMP installation instructions provided in the release notes of the TMP. If you have additional questions, please contact Tivoli at TIVOLI-8 or your customer support representative. If you have comments or suggestions, please send to USIB2HPD@VNET.IBM.com. Disk Space Requirements The following amount of disk space is required on the manager: 1-10 Version 2.0

17 Table 1. Disk Space Required on the Manager Node Item Manager programs Log file copies: Process accounting log pacct All other logs (total) Database space by component: Accounting Configuration Error analysis NetView Performance Systems Monitor Supported Environments Disk Space Required 15MB + 5MB for documentation MB per agent node MB per agent node Components, Requirements, and Installation TME 10 Reporter: Release Notes 1-11

18 Supported Environments The following amount of disk space is required on the agent nodes: Table 2. Disk Space Required on Agent Nodes Item Agent programs Log files (file name in parentheses): Disk accounting log (dtmp) Process accounting log (pacct) Printer accounting log (qacct) Login/logout accounting log (wtmp) Configuration log (conf) Error analysis log (errpt) NetView log (netview) Disk performance log (disk) Performance log (perf) Systems Monitor log (sysmon) Disk Space Required 1.0MB on AIX 1.5MB on HP 2.5MB on Solaris MB on Solaris 2.x Space for 7 days data, in KB: Hardware Requirements The following hardware (or equivalent) is required. Manager: Any processor that can run AIX or later, or AIX 3.2.5, with: 1/4-inch or 8mm tape drive, or a CD-ROM drive (required for installation) TCP/IP connection A color display supporting X-Window System MB memory 1-12 Version 2.0

19 Supported Environments 0,6MB disk space per agent for temporary files. If process accounting data is collected, 6MB additional disk space per agent is required. If Systems Monitor data is collected, 2MB additional disk space per agent is required. 1MB disk space per agent for the database. If process accounting data is collected, 2.5MB additional disk space per agent is required. Agents: Any processor that can run one of these operating systems, or later releases: AIX AIX HP-UX 9.3 Solaris 1.1 Solaris 2.3 with: 10MB memory TCP/IP communication adapter Note: The specified memory is required to run only the TME 10 Reporter. To run other applications, you may need additional memory. Components, Requirements, and Installation Software Requirements The following software (or later releases) is required. The products program numbers are shown in parentheses. Manager: AIX for RS/6000 ( ) with X11vsm ( ) or AIX for RS/6000 ( ) with: X11vsm Accounting Services Software Error Logging and Dump Service Aids AIX 3.2 to 4.1 Compatibility Links IBM DATABASE 2 AIX/ TME 10 Reporter: Release Notes 1-13

20 Supported Environments or IBM DATABASE 2 AIX/ or ORACLE with SQL*Plus 3.1 or SYBASE SQL Server Optionally, DynaText 2.03 Note: On DATABASE , PTF U must be applied. Agents: AIX for RS/6000 ( ) or AIX for RS/6000 ( ) with: Accounting Services Software Error Logging and Dump Service Aids AIX 3.2 to 4.1 Compatibility Links or HP-UX 9.3 or Solaris 1.1 or Solaris 2.3 (or later) Optional software: Hewlett Packard OpenView Network Node Manager 3.1 NetView for AIX 3.1 ( ) NetView for AIX 4.1 ( ) NetView/ ( ) Systems Monitor for AIX 2.1 ( ) Systems Monitor/ ( ) Systems Monitor for HP-UX 1.1 ( ) Systems Monitor for Sun Solaris 1.1 ( ) SystemView NetView for Sun Solaris 2.1 ( ) Tivoli/Inventory 3.0 Tivoli Enterprise Console 2.6 TME 10 ARM Agents Note: On Systems Monitor 2.1, PTF U must be applied Version 2.0

21 Installation Instructions Installation Instructions To install the TME 10 Reporter components refer to the installation instructions given in the TME 10 Reporter Installation and Administration manual. Components, Requirements, and Installation TME 10 Reporter: Release Notes 1-15

22 1-16 Version 2.0

23 2 Additional Useful Information For information about TME 10 Reporter, refer to the following manuals: TME 10 Reporter Installation and Administration TME 10 Reporter Log Collector Guide and Reference TME 10 Reporter Messages Guide TME 10 Reporter Reporting Dialog Guide TME 10 Reporter User s Reference Additional Useful Information TME 10 Reporter: Release Notes 2-1

24 2-2 Version 2.0

25

26 GI