Tivoli Management Solution for Microsoft SQL. Release Notes. Version 1.1

Transcription

1 Tivoli Management Solution for Microsoft SQL Release Notes Version 1.1

2

3 Tivoli Management Solution for Microsoft SQL Release Notes Version 1.1

4 Tivoli Management Solution for Microsoft SQL Copyright Notice Copyright IBM Corporation 2000 All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM 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 IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. 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. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. Notices 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 valid intellectual property or other legally protectable right of Tivoli Systems or IBM, 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. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A.

5 Contents Installation and Configuration Notes.. 1 SMS Installation Unattended Installation Setting up Microsoft SQL General Product Notes How to Install the MS Loopback Adapter Product Usage Notes and Hints Product Problems and Abnormalities 11 iii

6 iv Tivoli Management Solution for Microsoft SQL: Release Notes

7 Installation and Configuration Notes Operating System and Hardware Requirements for Tivoli Management Solution for Microsoft SQL. The full or agent installation of Tivoli Management Solution for Microsoft SQL runs on Windows NT 4.0 or Windows 2000 on Intel hardware only. Tivoli Management Solution for Microsoft SQL should be installed on trusted domains. Tivoli Management Solution for Microsoft SQL is designed to run on computers that are either part of the same domain, or on computers in different domains when these domains have a full two-way trust relationship. Not all of the features of Tivoli Management Solution for Microsoft SQL will work between partially trusted domains. SMS installation and unattended installation. Tivoli Management Solution for Microsoft SQL supports SMS installations and unattended installations. Please refer to SMS Installation on page 2 and Unattended Installation on page 2. SNMP must be installed. SNMP must be installed to collect SNMP or TCP/IP statistics and to execute the SNMP_TRAP or SNMP_SET action. If SNMP is installed after Tivoli Management Solution for Microsoft SQL is installed, you will need to reinstall Tivoli Management Solution for Microsoft SQL. ODBC must be installed. ODBC must be installed for Tivoli Management Solution for Microsoft SQL to be able to collect statistics from an ODBC data source, to export data to an ODBC data source, or to execute an SQL statement. In addition, all database drivers (such as those for SQL Server and Access) must be compatible with the version of ODBC installed. Setting up Microsoft SQL for the MAIL action and for the collection of SQL statistics. In order for the MAIL action to work using Microsoft SQL, certain manual configuration steps need to be taken. These steps must be taken on every computer where the MAIL action is used. This is also required for the collection of SQL mailbox and folder statistics. Please refer to Setting up Microsoft SQL on page 3. Making changes to the Microsoft SQL Profile used by Tivoli. If you make any changes to the Microsoft SQL profile used by Tivoli Management Solution for Microsoft SQL, you will have to stop and restart the Tivoli Rule Server for these changes to take effect. This can be achieved via the Services applet in the Control Panel. Reinstalling Tivoli Management Solution for Microsoft SQL. When reinstalling Tivoli Management Solution for Microsoft SQL, you will be given a choice concerning your existing supplied rules and rule processes. The default behavior is to replace them with the latest version on the setup kit. This will cause you to lose any modifications you have made to them, but will give you any enhancements that have been made to them. During the reinstallation procedure, you can change this behavior to keep existing versions of these rules, or to keep a copy of these rules. Daily log files for rule processes. Each Tivoli Management Solution for Microsoft SQL rule process normally 1

8 SMS Installation Unattended Installation creates two log files in Tivoli Management Solution for Microsoft SQL s \logs folder - one for action errors and one for miscellaneous rule output. These files are kept open while the rule process is executing. You may force the creation of daily log files by creating a value entry named DailyLogFiles in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Heroix\TEMS\Config This registry value should have a DWORD value containing the number of days to maintain these log files. If it exists, Tivoli Management Solution for Microsoft SQL will close the previous days log files at midnight, and new log files will be created for the new day. Also, log files older than the specified number of days will be deleted. If this registry value does not exist, the single pair of log files will be created and kept open for each rule process. Microsoft SQL required for batch reports and graphs. If you want to send reports and graphs created in batch to one or more recipients in an , you must configure Tivoli Management Solution for Microsoft SQL to use Microsoft SQL for . Tivoli Management Solution for Microsoft SQL supports SMS installation. To install Tivoli Management Solution for Microsoft SQL using SMS refer to the following instructions. 1. Perform a local installation on a single machine, configuring Tivoli Management Solution for Microsoft SQL as desired. 2. Tivoli Management Solution for Microsoft SQL will create the files it requires for a SMS installation and place them in the windows directory - typically C:\winnt or C:\winnt Copy all the Tivoli Management Solution for Microsoft SQL installation files from the distribution media to a working directory accessible by the SMS site server. 4. Copy the file named RoboMonsetup.iss from the Tivoli Management Solution for Microsoft SQL directory of the local installation into this working directory and rename it to setup.iss. 5. Import the.pdf file RoboMon.PDF into SMS Administrator. 6. Set the.pdf file s source directory to the working directory containing the Tivoli Management Solution for Microsoft SQL installation files. 7. Create a job to install the package on remote workstations and servers. Please consult your SMS documentation for additional details. To perform an unattended installation on additional computers after performing a regular installation on one computer, do the following: 1. Perform a local installation on a single machine, configuring Tivoli Management Solution for Microsoft SQL as desired. 2. Copy all the Tivoli Management Solution for Microsoft SQL installation files from the distribution media to a working directory on each additional computer. 3. Copy the file named RoboMonsetup.iss from the Tivoli Management Solution for Microsoft SQL directory of the local installation into this working directory and rename it to setup.iss. 2 Tivoli Management Solution for Microsoft SQL: Release Notes

9 Setting up Microsoft SQL 4. Select all files in the working directory, and remove the read-only attribute. 5. Execute smssetup.bat on each additional computer to perform the unattended installation. In order for the MAIL action to work using Microsoft SQL, or to be able to collect the Microsoft SQL mailbox and folder statistics (used by the Microsoft SQL rules), the following manual configuration steps need to be taken. These steps must be taken on every computer where the MAIL action is used or where these statistics are collected. 1. Install Microsoft SQL client. 2. Using Microsoft SQL Administrator, create a Tivoli mailbox. 3. Using User Manager, create a domain level account with administrator privilege named Tivoli. 4. Log off and Log back on under the new Tivoli account. 5. Create a Microsoft SQL profile for Tivoli Management Solution for Microsoft SQL to use. This is typically done using the Mail applet from within the Control Panel or by clicking on the Inbox icon. Consult your Microsoft documentation for details. 6. Log off from the Tivoli account. 7. During the Tivoli Management Solution for Microsoft SQL installation, or in Tivoli Configuration Manager, configure Tivoli Management Solution for Microsoft SQL to use this account. Enter the domain name, the account name (Tivoli) and the password. 8. Also during the Tivoli Management Solution for Microsoft SQL installation, or in Tivoli Configuration Manager, enter the Microsoft SQL profile name in the Profile Name field. Typically this is MS SQL Settings. Installation and Configuration Notes 3

10 4 Tivoli Management Solution for Microsoft SQL: Release Notes

11 General Product Notes Converting Tivoli Management Solution for Microsoft SQL databases to SQL Server Tivoli Management Solution for Microsoft SQL event and performance databases are initially installed as Jet databases. If you are consolidating events and performance data from many computers, your databases may become too large for a Jet database. In this case, you may want to convert one or both of these databases to SQL Server. See a more detailed discussion here. You may convert your event database to SQL Server 6.5 as follows: 1. Create a database using SQL Server Enterprise Manager. 2. From SQL Server Enterprise Manager, highlight the newly created database and run the RoboMon_EventDatabase_CreateTables.SQL script to create the tables. This script is located in Tivoli Management Solution for Microsoft SQL s \config directory. 3. Update the ODBC System DSN RoboMon Event Database to point to your newly created SQL Server database. You may convert your event database to SQL Server 7 as follows: 1. Create a database using SQL Server Enterprise Manager. 2. From SQL Server Enterprise Manager, highlight the newly created database and run the RoboMon_SQL7_EventDB_CreateTables.SQL script to create the tables. This script is located in Tivoli Management Solution for Microsoft SQL s \config directory. 3. Update the ODBC System DSN RoboMon Event Database to point to your newly created SQL Server database. You may convert your performance database to SQL Server 6.5 or SQL Server 7 as follows: 1. Create a database using SQL Server Enterprise Manager. 2. From SQL Server Enterprise Manager, highlight the newly created database and run the RoboMon_PerformanceDatabase_CreateTables.SQL script to create the tables. This script is located in Tivoli Management Solution for Microsoft SQL s \config directory. 3. Update the ODBC System DSN RoboMon Performance Database to point to your newly created SQL Server database. Compacting the databases Tivoli Management Solution for Microsoft SQL can automatically compact your event database and performance database using the utility program, RoboMon_compact.exe (if they are Jet databases). The Admin rule, Compact_Databases, does this automatically every night. RoboMon_compact is executed from a command line, and can take the following switches: /E Compactthe eventdatabase /P Compact the performance database /A Compact the event database and the performance database /V Verbose mode Security for Tivoli Management Solution for Microsoft SQL files Tivoli Management Solution for Microsoft SQL rules can be written to 5

12 perform actions on the local computer or on a remote computer. For security reasons, to prevent certain users from writing or starting rules, you should install Tivoli Management Solution for Microsoft SQL on an NTFS file system. Then, you can restrict access to rule files and executable files. For example you can require administrator privileges for key files such as the Tivoli Enterprise Manager (RoboMon_Emgr.exe), the Tivoli Enterprise Service (RoboMon_esrv.exe) and the Tivoli Rule Service (RoboMon_rulsrv.exe). You can also restrict access to all the files on key subdirectories such as the rules and processes subdirectories under the Tivoli Management Solution for Microsoft SQL main directory. Tivoli Management Solution for Microsoft SQL s use of TCP/IP Tivoli Management Solution for Microsoft SQL makes use of the TCP/IP network services. A network adapter and the TCP/IP network protocol must be installed. Note: If you do not have a network adapter you must install the MS Loopback Adapter. For more information on installing the MS Loopback adapter, see How to Install the MS Loopback Adapter on page 7. Computer name and TCP/IP host name Tivoli Management Solution for Microsoft SQL expects the computer name and the TCP/IP host name for each computer it is running on to be identical. Note: If the names are not identical, Tivoli Management Solution for Microsoft SQL will not run correctly. Both names can be set through the Network applet available from within the Control Panel. The computer name can be set via the Network applet s main screen. The TCP/IP host name can be set from the TCP/IP protocol s DNS configuration screen. Windows NT automatically configures the computer name and the TCP/IP name to be the identical unless the computer name contains a character that is illegal under the DNS standard. In this case, the invalid character is replaced by the closest legal character. Sometimes the TCP/IP host name can be changed to include the illegal character (depending on how strict the DNS server is). Sometimes the computer name must be changed. Note: The underscore character ( _ ) is illegal in DNS and will be substituted with a dash ( - ) character. Ensure that the computer name and the TCP/IP host names are identical on all computers that have an underscore in their computer name. Tivoli Management Solution for Microsoft SQL services Tivoli Management Solution for Microsoft SQL installs several services: TCP/IP Service, Rule Service, Event Service, Remote Event Service, and Enterprise Manager Service. A service is a program that can start up automatically when the system is booted, and can run without a user being logged on. All Tivoli Management Solution for Microsoft SQL services are configured for automatic startup and should normally be running. They may be accessed directly through the Services applet in the Control Panel. Under normal conditions, it is not necessary to do this. TCP/IP port numbers used by Tivoli Management Solution for Microsoft SQL Tivoli Management Solution for Microsoft SQL reserves the TCP/IP port numbers for its exclusive use. If you are using a firewall, you 6 Tivoli Management Solution for Microsoft SQL: Release Notes

13 will need to allow access to these port numbers through the firewall. Ports are used by the TCP/IP Service and the Rule Service. Port numbers beginning with 5625 are used by rule processes and are assigned in ascending order. Lastly, ports are used by the Enterprise Service, the Event Service and the Remote Event Service, respectively. Adding columns or tables to the performance database If you have added rules to archive data to new columns or new tables in the performance database, you should modify the empty version of this database (named PerformanceEmpty.mdb ) in Tivoli Management Solution for Microsoft SQL s \config directory. Then run the database compaction program that will convert and compact your performance database with the following command: RoboMon_compact/P Uninstalling Tivoli Management Solution for Microsoft SQL To uninstall Tivoli Management Solution for Microsoft SQL, open the Control Panel and click on the Add/Remove programs icon. Select Tivoli Management Solution for Microsoft SQL and click on the Add/Remove button. Uninstall will remove all files in the Tivoli Management Solution for Microsoft SQL directories. How to Install the MS Loopback Adapter First check if the TCP/IP protocol is installed: 1. Open up the Control Panel. 2. Open up the Network applet. Installed network software will be listed in alphabetical order. If no network software or hardware has been installed, a message indicating this will appear. Install your network components at this time. Make sure to install TCP/IP. See below for additional instruction on installing the various components of TCP/IP. 3. Scroll down to the T range and look for TCP/IP Protocol. If the name is displayed, then the TCP/IP Protocol has been installed. If the TCP/IP protocol is not installed you must install it: 1. Open up the Control Panel. 2. Open up the Network applet. 3. Press the Add Software button. 4. Select TCP/IP Protocol and related components. Press the Continue button. 5. Step through the TCP/IP configuration options. Now Install the MS Loopback Adapter: 1. Open up the Control Panel. 2. Open up the Network applet. 3. Press the Add Adapter button. 4. Select MS Loopback adapter from the Network Adapter card list and press the Continue button. 5. Choose the default frame type and press Continue. 6. You will be prompted for an IP address. Since you are not connected to a network, it can be anything. Enter and press OK. General Product Notes 7

14 7. Choose the defaults for any other configuration screen that might be shown. Windows NT will create the bindings and suggest you reboot. 8. Press the Restart Now button. This will reboot your computer. 8 Tivoli Management Solution for Microsoft SQL: Release Notes

15 Product Usage Notes and Hints Maximum number of Tivoli Management Solution for Microsoft SQL rule processes. There is a maximum of fifty (50) rule processes per computer. Use of dotted decimal address as a computer name. A dotted decimal address may be specified in place of a computer name. A dotted decimal address may also be specified after a computer name. In both cases, Tivoli Management Solution for Microsoft SQL will use the dotted decimal address instead of the computer name. See the following examples: ABCDEF In both these cases, Tivoli Management Solution for Microsoft SQL will use the address instead of the computer name ABCDEF. This feature can be helpful if your network has DNS configuration problems. Forcing RPC connections to use TCP/IP. When a Tivoli Management Solution for Microsoft SQL service on a remote computer performs a task on behalf of a user interface component, an RPC connection is made to perform the task. If the computer is specified using a dotted decimal address, TCP/IP is used to establish the connection. Otherwise, a named pipe is used. You can force Tivoli Management Solution for Microsoft SQL to always use TCP/IP when establishing an RPC connection by creating a registry value entry named TcpIpForRpc in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Heroix\TEMS\Config The data type should be DWORD, and the value should 1. If this value entry does not exist, or if it exists with a value of 0, Tivoli Management Solution for Microsoft SQL will use the default mechanism (either a named pipe or TCP/IP) to establish an RPC connection. Execution of multiple one-shot rules. When a rule file contains multiple one-shot rules, they each execute completely, in sequence. The collection for the first rule is performed, the rule is executed and any actions are performed. Then the second rule s collection is performed, it is executed, and so forth. Variable usage in asynchronous rules. When an asynchronous rule is executed, the memory for any variables used in the rule is freed. This means that the value of a variable set in an asynchronous rule will not be available to other rules. To make the value available to other rules, you will have to write the variable to a file. This behavior is unique to asynchronous rules. Defining timeout value for IP_REACHABLE. By default, Tivoli Management Solution for Microsoft SQL uses a timeout value of five seconds when determining the value of the IP_REACHABLE statistic. If the computer is not reachable in this length of time, it is considered unreachable and the value of IP_REACHABLE is set to zero (0). You can modify this timeout value by creating a registry value entry named IPTimeToReach in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Heroix\TEMS\Config 9

16 The data type should be DWORD, and the value should be the timeout value (in seconds) to use to determine if a computer is reachable. If this value entry does not exist, a timeout value of five (5) seconds is used. The IP_REACHABLE statistic is used in the WindowsNT-2000Server rule, Unreachable_Computers. Defining community name and timeout value for DHCP statistics. By default, Tivoli Management Solution for Microsoft SQL uses a community name of public and a timeout value of three (3) seconds when collecting DHCP statistics. You can modify this behavior by creating registry value entries named DHCPCommunity and DHCPTimeout in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Heroix\TEMS\Config The data type for DHCPCommunity should be String, and the data type for DHCPTimeout should be DWORD. The value of DHCPTimeout should be the timeout value in seconds. 10 Tivoli Management Solution for Microsoft SQL: Release Notes

17 Product Problems and Abnormalities Tivoli Management Solution for Microsoft SQL rate statistics. Rate statistics may occasionally exceed 100%. This anomaly only occurs when a rule is run on a very short interval. It is caused by an inherent inaccuracy in the Windows NT timing mechanisms. The effect becomes insignificant with intervals over 30 seconds. An error in certain versions of Windows NT. On some machines a dialog box reading There is no disk in the drive. Please insert a disk into drive X: will occasionally appear. Tivoli Management Solution for Microsoft SQL does not continue until the dialog box is dismissed. This is due to an error with certain versions of NT. There are two methods to work around this: 1. Place a disk in drive X. 2. Log on using a similarly privileged account other than Administrator. The dialog box will only be displayed when the current or last user logged on using the Administrator s account. A problem with DISK_READ_PCT and DISK_WRITE_PCT. The value of the statistics, DISK_READ_PCT and DISK_WRITE_PCT, are often zero, even when there has been disk activity. These statistics are collected from the Windows NT performance database, and match the values of the counters, Disk Reads/sec and Disk Writes/sec. The problem is in the values of these counters. A problem with EVT_DATE and EVT_TIME. The statistics, EVT_DATE and EVT_TIME, may be incorrect in some time zones. This is due to a problem in localtime, a system function used to collect these statistics. Access violations from the Tivoli Statistics Builder. The Tivoli Statistics Builder uses the Microsoft function, RegQueryValueEx, with the predefined HKEY_PERFORMANCE_DATA key to collect Windows NT performance objects and counters. Under some circumstances this function may cause an access violation in the Tivoli Enterprise Manager Service. The problem is caused when a Microsoft DLL used to get data for a specific performance object, known as a performance monitor extension, is corrupted. The first thing you should do if you experience this problem is to restart the Tivoli Enterprise Manager service from the Services applet of Control Panel. You should then be able to continue using the Tivoli Statistics Builder normally. The permanent solution to this problem involves determining which DLL is causing the problem, and renaming it. We have seen this problem in SQLCTR60.DLL, which is referenced by the value entry Library in the following registry entry: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ MSSQLServer \ Performance Renaming SQLCTR60.DLL to XSQLCTR60.DLL avoids the problem. However, this also disables the collection of performance information in all SQL Server performance objects. A detailed explanation of this problem and its solution is found in Microsoft Technet article Q

18 IIS 4.0 causes problems in the Tivoli Statistics Builder and Rule Designer. A problem with Microsoft Internet Information Server (IIS) version 4.0 may prevent the Tivoli Statistics Builder from seeing performance monitor objects provided by IIS. This problem may also cause the Tivoli Rule Designer to produce errors when creating certain actions, and when saving a rule. This problem is documented in Technet article Q192224, and a fix described in this article is available. Installation log used to diagnose installation problems. A file named TivoliInstallLog.txt is created in the Tivoli Management Solution for Microsoft SQL installation directory by the installation. If you experience any errors or problems during installation, the contents of this file can help diagnose the cause of the problems. Microsoft SQL mail action problem. A problem in Microsoft SQL may cause Tivoli Management Solution for Microsoft SQL mail action to fail when Tivoli Management Solution for Microsoft SQL is configured to use Microsoft SQL for the mail action. The action error log file, located in Tivoli Management Solution for Microsoft SQL \logs directory will contain the error Unknown MAPI error. This problem is documented in TechNet article Q179116, and is fixed in Microsoft SQL version 5.5, Service Pack 1. If you experience this problem, do one of the following: 1. Install Microsoft SQL version 5.5, Service Pack Configure Tivoli Management Solution for Microsoft SQL to use SMTP, rather than Microsoft SQL, for the mail action. After making one of these changes, you will need to restart the rule process or processes before the mail action will begin working. Error loading a DLL during an upgrade installation. During an upgrade installation, we have sometimes seen an error loading MSJTER40.DLL. You should be able to dismiss this error and continue with the installation without problems. CPU usage statistics on Windows 2000 computers. On Windows 2000 computers, the value of the CPU usage statistics (CPU_BUSY_PCT, CPU_DPC_PCT, CPU_INTERRUPT_PCT, CPU_PRIVILEGED_PCT, and CPU_USER_PCT) will return zeros. The total CPU usage can be calculated from the sum of the processor statistics (PROCESSOR_BUSY_PCT, PROCESSOR_PCT_DPC_TIME, PROCESSOR_INTERRUPT_PCT, PROCESSOR_PRIVILEGED_PCT, and PROCESSOR_USER_PCT) across all processors. 12 Tivoli Management Solution for Microsoft SQL: Release Notes

19

20 Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.