Documente Academic
Documente Profesional
Documente Cultură
Steve Strutt
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Introduction
This IBM Redpaper outlines how it is possible to integrate management and reporting in IBM Tivoli Storage Manager (TSM) environments into an enterprise-wide IT monitoring and management solution. It shows how IBM Tivoli Storage Manager Operational Reporting can be used to simplify the monitoring and reporting on the status of a Tivoli Storage Manager environment and how this information can be displayed centrally on an enterprise event management console. IBM Tivoli Storage Manager Operational Reporting provides a significant step forward in monitoring and reporting on the current state of one or more TSM servers. Summary reports and automatic notification of issues simplify administration and reduce the time required to manage TSM environments by enabling a management-by-exception approach to be adopted. In environments where enterprise monitoring and event consoles are used, these Operational Reporting status events can be used to simplify the management of TSM environments and integrate them into the wider picture of management of the whole IT infrastructure. Accompanying configuration files are provided to implement the features described in this paper. These can be downloaded from the following URL:
ftp://www.redbooks.ibm.com/redbooks/REDP3850/
Select Additional materials and open the directory that corresponds with the Redpaper form number, REDP3850.
ibm.com/redbooks
TSM W e b a d m in
Launch w eb a d m in
E v e n t C o n s o le
Laun ch w eb r e p o rt
T SM O R W e b s e rv e r
TSM O R C o n s o le
E v e n ts
T S M O R S e rv e r T S M S erver H a rdw a re
TSM Operational Reporting intelligently monitors the results of TSM operations, schedules, and status. It can then alert exception conditions to the event console. The alert thresholds can also be set to meaningful values for specific user environments, such as the known minimum number of scratch tapes to complete the overnight backup schedules. As a result, the number of events that must be forwarded from a TSM server to monitor its activities can 2
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
be reduced significantly because Operational Reporting can more precisely summarize the results. TSM is an extremely verbose product and an out-of-the-box implementation of TSM results in many messages being sent to the event console. With Operational Reporting monitoring schedule results and server status, the number of TSM messages forwarded to the event console can be restricted to those critical events that indicate severe problems and those issues that must be dealt with immediately With the 5.2.2 release of TSM for Windows, Operational Reporting provides an event log that can be exploited to forward status events to an IBM Tivoli Enterprise Console (TEC) or other SNMP Event Managers. This paper shows how this event log can be used to forward TSM Operational Reporting status events on to TEC using a TEC logfile adapter and how the Web versions of the reports can be launched and viewed from TEC. This approach to central monitoring of TSM servers could also be implemented for SNMP-based event management solutions that provide adapters to read log files.
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
TEC Server
Write Message
TSM_Monitor_Warning version "1.0" timestamp "06/13/2003 08:59:04" file "SSTRUTTServer1MonHourlyMonitor20030613 085904.htm" type "1" typename "Monitor" computer "SSTRUTT" instance "Server1" serverurl "http://SSTRUTT:1580" report "Hourly Monitor" begin "2003-06-13 07:33" end "200306-13 08:33" status "1" statusname "Needs attention" "message There are not enough scratch volumes available. condition 0 < 5 recommendation Check in some scratch tapes."
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Enter the fully qualified host name of the computer where the Tivoli Enterprise Console resides on the Server Configuration panel, as shown in Figure 4.
Enter the port name used by Tivoli Enterprise Console to receive events in the Server Port panel. This is usually 5529 for a TEC installed on a Windows server, but it should be the value used in your environment. This is shown in Figure 5 on page 6.
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
When this is complete, the logfile adapter is installed. However, it must be configured to forward events from Operational Reporting to TEC.
This file is created when Operational Reporting is configured to create TEC events, and all subsequent events are written into this file. The writing of events to this file is enabled in the Operational Reporting properties panels. To enable this process launch the (Windows) TSM Management Console and select the Tivoli Storage Manager menu item in the left-hand pane, as shown in Figure 6 on page 7. Right click the menu item to configure Operational Reporting.
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Writing to the TEC log file is enabled on the Summary Information tab of the Properties panel. Check the Create a Tivoli Enterprise Console (TEC) log file box and click OK, as shown in Figure 7.
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Two files are required, tecad_win.fmt and tecad_win.cds, for the logfile adapter to recognize the Operational Reporting events and format them correctly as TEC events. The format of the messages that the adapter looks for is defined in the .fmt file. The sample configuration files provided as additional materials to this Redpaper include .fmt and .cds files. The four Operational Reporting events can be found at the end of the sample .fmt file. The .cds file is generated from the .fmt file and read by the logfile adapter. A pre-generated .cds file is provided. The tecad_win.cds file should be copied to the c:\tecwin\etc directory. The logfile adapter uses the locale of the Windows Server. The sample .cds and .fmt files assume a locale of English. If this is the case, the sample tecad_win.fmt file should be copied to the c:\tecwin\etc\c directory. If the locale is set differently and monitoring of the Windows Event log is needed in addition to the tecinfo.txt file, the four Operational Reporting message format statements in the sample fmt file should be copied to the correct locale version of the tecad_win.fmt file and a new .cds file generated. The logfile adapter installs as a Windows service. It should be stopped and restarted after updating the configuration files, as in Example 2.
Example 2 Commands to stop and restart TEC Logfile Adapter net stop TECWinAdapter net start TECWinAdapter
messages and to automatically close preceding success or issue events if the status of a report or monitor changes. This leaves just one success event or a small number of issue events for each report or monitor on the TEC view, which significantly reduces the number of events that must be monitored. As a result, (1) the TEC event views show only that information that is both current and relevant, and (2) the views are automatically updated with the latest status information. This simplifies management when multiple TSM servers are monitored because the number of events to be reviewed is relatively small. Rules files are loaded in the same fashion as outlined for class files, with the rules file being imported instead of a class file. After the class and rules files have been loaded and the TEC server stopped and restarted, it should display the Operational Reporting events in the all events view.
Event Groups have been used to separate out events into the different storage management disciplines. These include the SAN fabric that TSM is potentially dependant on, along with the storage hardware device status for tape libraries and disks. An Event Group has been
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
created for Operational Reporting events. This group makes locating these events easier and enables you to see the status of multiple TSM servers at a glance from this event view. Figure 9 shows the Operational Reporting TEC Event View with events showing the status of multiple monitors and reports for two TSM servers, DUBLIN and Azure. The TSM server name can be seen in the Hostname field in the top pane of the window.
10
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
11
Summary
TSM Operational Reporting provides the ability to significantly reduce the administrative effort to manage a TSM environment by summarizing the results of operations and alerting users to specific out-of-line situations. When integrated with centralized event management, it enables IT administrators to manage their whole environment by exception and only get involved when the situation warrants it. It also simplifies the management of multiple TSM servers by bringing all status reports of all servers to a single point and presenting it on one screen. Exploiting the custom button feature of TEC and TSMs Web-based administration enables a TEC event management console to become a central focal point for a storage administration console. This focal point is a place where all relevant management interfaces can be launched and products can be administered to address any identified issues.
12
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Comments welcome
Your comments are important to us. Send us your comments in one of the following ways (be sure to include the document number, ): Use the online review redbook found at:
http://www.ibm.com/redbooks
Mail your comments to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 U.S.A.
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
13
14
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
15
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
Eserver Eserver Redbooks (logo) Eserver ibm.com z/OS IBM Redbooks Tivoli Enterprise Tivoli Enterprise Console Tivoli TME
The following terms are trademarks of other companies: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
16
Integrating IBM Tivoli Storage Manager Operational Reporting with Event Management