File Name: README.txt Electronic Service Agent for Netfinity version 1.1.2 README.txt CONTENTS ________ 1.0 Overview 1.1 Changes made to the Electronic Service Agent version 1.1.2 README 2.0 Limitations 3.0 Prerequisites 4.0 Migrating from IBM Remote Connect to Electronic Service Agent 5.0 Increasing Capacity Manager's Data Storage Capacity 5.1 Introduction 5.2 How Do I Increase Capacity Manager's Data Storage Capacity? 5.3 Why Do I Need to Increase Capacity Manager's Data Storage Capacity? 5.3.1 Reporting System Performance Data After Noon (1200) Each Day 5.3.2 When Your Central Management Server(CMS) and Managed Systems Reside in Different Time Zones 5.3.3 An Additional Note about Time Zones 6.0 README Updates and Contacting Customer Support 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview ________________ Electronic Service Agent for Netfinity version 1.1.2 is a program that operates on IBM Netfinity servers, and is designed to be installed as an extension to your Netfinity Director Central Management Server. Electronic Service Agent monitors your networked servers for hardware errors and also has an integrated performance monitor function that automatically collects system utilization information. Electronic Service Agent also performs hardware and software inventories, and reports inventory changes to IBM. All information sent to IBM is stored in a secure IBM database and used for improved problem determination. Electronic Service Agent version 1.1.2 also provides generic support for IBM's Electronic Systems Management Services for Netfinity Extended Service Levels. Electronic Systems Management Services for Netfinity currently provides two Extended Service Levels. These are the Premiere and Premiere Plus Extended Service Levels. 1.1 Changes Made to the Electronic Service Agent -------------------------------------------- Version 1.1.2 README. -------------------- Additional information has been added to the Electronic Service Agent version 1.1.1 README in order to produce this README for Electronic Service Agent version 1.1.2 as follows: 1.1.1 Previously using Electronic Service Agent version 1.1.1 a user with administrative privileges had to be logged on to the Central Management Server (CMS) in order for the modem connection for Electronic Service to function properly. This is no longer the case. Using Electronic Service Agent version 1.1.2 it is not necessary for any user to be logged on to the Central Management Server. 1.1.2 Section 2.6 contains some amended information about socksifying your Electronic Service Agent Central Management Server. 1.1.3 Section 3.1 contains some additional upgrade information. 1.1.4 Section 5.0, "Increasing Capacity Manager's Data Storage Capacity" has been added. 2.0 Limitations _______________ 2.1 Due to differing capabilities of the Advanced Systems Management Adapters in various Netfinity models, Electronic Service Agent will not report the following events from Netfinity 5000, 5500, 5500 M10, 5500 M20, or 7000: - Netfinity System Events.Critical.Temperature - Netfinity System Events.Critical.Voltage - Netfinity System Events.Critical.Voltage Regulator Module Failure - Netfinity System Events.Critical.Power Failure - Netfinity System Events.Critical.Hard Disk Drive The Netfinity Advanced Systems Management Processor and Adapter must be updated to the latest level on each managed server. To obtain the latest level of device driver: 1.0 Visit website: http:www.pc.ibm.com/support on the Internet Ensure that your web browser is capable of displaying frames. 2.0 Select "Servers." 3.0 Select the machine type of your managed server from the drop down list. 4.0 Select "Downloadable files" from the left hand navigation frame. 5.0 Select "Advanced Systems Management" from the Category drop down list. 6.0 Download and follow the directions for all Advanced Systems Management firmware and device driver updates. 2.2 If you enable one or more systems for PMR Tracking or Performance Management then subsequently disable either PMR Tracking or Performance Management, then inventory collection will automatically be disabled. You must then explicitly enable inventory collection if you require it. 2.3 If you have clicked Send in the Inventory or Performance Manager page or clicked Test Modem Connection in the Dialer page, then you must wait until the tasks have completed before interacting with the Electronic Service Agent user interface. These tasks may take several minutes to complete. The user interface may display "Ready" even though the modem may still be in use. We recommend that you physically view the modem (using the Dial-Up Networking Monitor screen)and wait until it is in a state of rest before using the interface again. If Electronic Service Agent appears to hang during any of the tasks mentioned above, then you may have to shutdown then restart the Netfinity Director Management Console. Lastly, you should note that when collecting and sending inventory or performance data using the Inventory or Performance Manager pages respectively, targeting more than four systems at one time may cause heavy network traffic. 2.4 If you are viewing inventory data for a managed system or group of managed systems using Netfinity Director's Query Browser window and then you change the Extended Service Level enablement of this managed system or group of managed systems, note that the inventory data displayed in the Query Browser window will not be automatically updated. To view updated inventory data, you must close the Netfinity Director Query browser window and then reopen it by relaunching the inventory task targeted at the managed system or group of managed systems for which you want to view refreshed inventory data. 2.5 If the Netfinity Director Central Management Server is stopped and restarted, Performance Monitors will stop functioning. Changing Extended Service Levels may also have unpredictable effects. If you stop a Netfinity Director Central Management Server, that is managing systems enabled for the Premier Plus Extended Service Level, and then restart the Netfinity Director Central Management Server, you must restart Performance Monitors. To restart Performance Monitors: 1.0 Restart Netfinity Director to launch the Netfinity Director Management Console. 2.0 Drag and drop the Resource Monitors task from the Tasks pane onto the Electronic Service Eligible Systems group in the Groups pane of the Netfinity Director Management Console. 3.0 The Resources Window appears. Close this window. 2.6 If you want to socksify your Electronic Service Agent Central Management Server (CMS) after you have installed Electronic Service Agent, then you must make a modification to your Socks.cnf file. Locate and open your Socks.cnf file, then type the following line at the TOP of the file: EXCLUDE MODULE DIALERSERVICE 3.0 Prerequisites __________________ 3.1 Electronic Service Agent versions 1.0 and 1.0.1 are NOT upgradeable to Electronic Service Agent version 1.1.2. If you have previously installed either version 1.0 or 1.0.1, then you should use the uninstalling procedure detailed in Chapter 3, "Obtaining and installing Electronic Service Agent for Netfinity" of your Electronic Service Agent for Netfinity User's Guide to properly remove all version 1.0 or 1.0.1 files from your Netfinity Director Central Management Server. Electronic Service Agent versions 1.1 and 1.1.1 can be upgraded to version 1.1.2. There is no need to uninstall either version 1.1 or 1.1.1 prior to installing Electronic Service Agent version 1.1.2. 3.2 Electronic Service Agent version 1.1.2 supports the following operating systems: 3.2.1 Netfinity Director Central Management Server - Windows NT 4.0 Server with Service Pack 4 or higher - Windows NT 4.0 Enterprise with Service Pack 4 or higher - Windows 2000 Server, Windows 2000 Advanced Server 3.2.2 Managed systems - OS/2 3.00, OS/2 3.00 Connect, OS/2 Warp Server, OS/2 Warp Server SMP, OS/2 Warp Merlin 4.0, OS/2 Aurora 4.5 - Windows NT 4.0 Server with Service Pack 4 or higher - Windows NT 4.0 Workstation with Service Pack 4 or higher - Windows NT 4.0 Enterprise with Service Pack 4 or higher - Novell Netware 4.10 Server, 4.11 Server, 4.2 Server, 5.0 Server, 5.1 Server - Windows 2000 Professional - Windows 2000 Server - Windows 2000 Advanced Server 3.2.3 Netfinity Director Management Console - Windows NT 4.0 Server with Service Pack 4 or higher - Windows NT 4.0 Workstation with Service Pack 4 or higher - Windows NT 4.0 Enterprise with Service Pack 4 or higher - Windows 95 Release 2 - Windows 98, Windows 98 Second Edition - Windows 2000 Professional - Windows 2000 Server - Windows 2000 Advanced Server 3.3 Ensure that you have selected the Remote Access Service (RAS) option when installing your Windows NT ® operating system. You can add the Remote Access Service from the Network Properties resource on your server console. For further information refer to your Windows NT Administrator's Guide. NOTE: The modem listed on com 1 in the Remote Access Setup screen is the default modem for your Netfinity Director Central Management Server. 3.4 Ensure that you have completed the configuration of the dialer and contact and location information before activating the Electronic Service Agent task in targeted mode. It is particularly important that you configure the location details of your Netfinity Director Central Management Server and managed systems accurately. If you record your Netfinity Director Central Management Server location details incorrectly then IBM's service delivery will be delayed. Similarly, if you record your managed systems' location details incorrectly, then IBM service representatives will not be dispatched to the correct site location after a hardware problem has been reported. 4.0 Migrating from IBM Remote Connect to Electronic _______________________________________________ Service Agent ______________ 4.1 Electronic Service Agent is a functional replacement for IBM Remote Connect Manager providing greater ease of installation, higher reliability, and improved manageability of IBM Netfinity(tm) Servers. 4.1.1 The primary software architectural difference between IBM Remote Connect and Electronic Service Agent is between the underlying systems management products and is detailed as follows: - IBM Remote Connect leverages Netfinity Manager. - Electronic Service Agent leverages Netfinity Director and UM Server Extensions. 4.1.2 The primary hardware architectural difference between IBM Remote Connect and Electronic Service Agent is: - IBM Remote Connect Manager installs on a generic workstation running Netfinity Manager. - Electronic Service Agent installs on a supported server running Netfinity Director Central Management Server and UM Server Extensions. To view the current list of supported servers visit website: http://www.ibm.com/pc/qtechinfo/MIGR-4L4QVC.html As with the IBM Remote Connect Manager workstation, the Electronic Service Agent Central Management Server must be dedicated to the task of Netfinity systems management. 4.2 The first step to migrate from IBM Remote Connect to Electronic Service Agent is to decommission IBM Remote Connect. Uninstall Netfinity Manager Services on each server managed by IBM Remote Connect. For further details refer to the Netfinity Manager user documentation. The IBM Remote Connect Manager workstation may then be put to another use; for example the workstation could be used as an auxiliary Netfinity Director console. 4.3 Install Netfinity Director Agent version 2.12 on each of the supported servers formerly managed by Netfinity Manager and IBM Remote Connect. Refer to the Netfinity Director documentation for Netfinity Director version 2.12 installation details. Nefinity Manager Services must be uninstalled on the managed servers prior to installing Netfinity Director Agent. Nefinity Manager Remote Control and Netfinity Director Remote Control are incompatible. Netfinity Director will not allow Remote Control to be installed if Netfinity Manager Remote Control is detected. 4.4 Install UM Server Extensions version 2.12 on each of the supported servers on which Netfinity Director Agent was installed in step 4.3 above. Refer to the UM Server Extensions documentation for UM Server Extensions version 2.12 installation details. 4.5 Install Netfinity Director Server 2.12 on a supported server dedicated to Netfinity Director systems management. Refer to the Netfinity Director version 2.12 user documentation for installation details. Do not install Netfinity Director Central Management Server on a server with other applications. The Central Management Server is the point of service for managing servers running applications. Microsoft® RAS must be installed, and NOS Service Packs reapplied, prior to installing Netfinity Director Server on the Central Management Server. Refer to the Electronic Service Agent Prerequisites in section 3.0 above. The default Windows NT® Server RAS configuration must be changed to allow dial-out connections. 4.6 Install UM Server Extensions version 2.12 on the Netfinity Director Central Management Server. Refer to the UM Server Extensions version 2.12 user documentation for installation details. 4.7 Using Netfinty Director, perform a Systems Discovery and Inventory Collection on the managed supported servers. Refer to the Netfinity Director version 2.12 on-line help for further details. 4.8 Download and install Electronic Service Agent on the Netfinity Director Central Management Server. Refer to the Electronic Service Agent User Guide for this procedure. 4.9 Ensure that you have installed Netfinity Director version 2.12, Electronic Service Agent version 1.1.2 and UM Server extensions ONLY on IBM supported servers. If you install Netfinity Director version 2.12, Electronic Service Agent version 1.1.2 or UM Server extensions on a NON-IBM supported server then the server will not have an electronic call generation capability. Refer to Chapter 1, "Introducing Electronic Service Agent for Netfinty" of your Electronic Service Agent for Netfinity Version 1.1 user's guide for an exhaustive list of supported managed systems. Refer to your Netfintiy Director version 2.12 documentation for a list of supported Central Management Servers (CMS). 5.0 Increasing Capacity Manager's Data Storage Capacity ___________________________________________________ 5.1 Introduction ------------ The process of system performance data collection, including performance data storage capacity is managed by Capacity Manager. Capacity Manager is one of a suite of software extensions (Universal Manageability Server Extensions) that you will have installed on your Central Management Server (CMS)and each of your managed systems prior to installing Electronic Service Agent. There are a number of instances where it may be necessary for you to alter Capacity Manager's configuration details such as increasing Capacity Manager's data storage capacity. The reasons for increasing Capacity Manager's data storage capacity are discussed in 5.3.1, and 5.3.2 below Capacity Manager's configuration details are stored and editable in a file named Cmagent.ini. The Cmagent.ini file is located as follows: Ibm/Director/bin/Cmagent.ini 5.2 How Do I Increase Capacity Manager's Data Storage ------------------------------------------------- Capacity? --------- To increase Capacity Manager's storage time capacity 1. Locate and open your Capacity Manager configuration file Cmagent.ini. 2. Locate the [Shift] section of the configuration text file and the following line of text: RealTimeSize = 2160 Where 2160 denotes 36 hours x 60 samples of performance data (performance data is sampled every minute). 3. Increase the 2160 minutes, to increase the storage time capacity. For example: RealTimeSize = 3600, will increase the storage capacity time to 60 hours (i.e. 60 hours x 60 samples of performance data). 5.3 Why Do I Need to Increase Capacity Manager's Data ------------------------------------------------- Storage Capacity? ----------------- When Capacity Manager is first installed, it is configured to store performance data sampled every minute for a time period of 36 hours. There are instances where you may require Capacity Manager to store data that has been sampled for a period of time in excess of 36 hours. Such instances occur when: - you have configured Electronic Service Agent's Scheduler to send system performance data reports to IBM after noon (1200) each day. - your Central Management Server (CMS) and managed systems reside in two different time zones. 5.3.1 Reporting System Performance Data After Noon --------------------------------------------- (1200) Each Day --------------- In the scenarios tabulated below, Electronic Service Agent is scheduled to report performance data to IBM on a Tuesday at 0700, 1200 and 1700. In each case Electronic Service Agent reports data collected every minute from the previous day for a duration of 24 hours between 2400 and 2400. ELECTRONIC SERVICE 0700 Tuesday 1200 Tuesday 1700 Tuesday AGENT'S SCHEDULER TIME (7 hours (12 hours (17 hours after data after data after data collection collection collection period) period) period) REPORTING PERIOD 2400 Sunday 2400 Sunday 2400 Sunday to to to 2400 Monday 2400 Monday 2400 Monday TOTAL STORAGE 7 + 24 hrs 12 + 24 hrs 17 + 24 hrs TIME REQUIRED = 31 hours = 36 hours = 41 hours FOR COLLECTED PERFORMANCE DATA The data above illustrates that when Electronic Service Agent's scheduler is set for a time after noon (1200), then Capacity Manager must store performance data that has been collected every minute for a time period in excess of 36 hours. If Capacity Manager's data storage capacity remains configured at 36 hours, then Capacity Manager will statistically reanalyse the performance data collected and present the data as if it were collected at a sampling rate of 5 minutes as opposed to 1 minute, thus reducing the amount of data stored. However, to avoid this statistical reanalysis you can increase Capacity Manager's data storage capacity by following step 5.2 above. 5.3.2 When Your Central Management Server (CMS) ----------------------------------------- and Managed Systems Reside In Different Time -------------------------------------------- Zones ----- Consider the following scenario: 1. Your managed systems reside in a time zone that is 12 hours ahead of the time zone in which your Central Management Server resides. 2. Electronic Service Agent's (installed on your Central Management Server) scheduler is configured to report performance data to IBM at 0100 on a Wednesday. Your Central Management Server dictates and sets the date of the 24 hour block of data that is reported to IBM. In this scenario the 24 hour block of data that is reported to IBM is that block of data that has been collected between 2400 on Monday and 2400 on Tuesday. The times between which the 24 hour block of data is collected i.e. 2400 and 2400 is dictated by the time zone in which your managed systems reside. Hence, in this example data that has been collected between Monday 2400 and Tuesday 2400 in the time zone of your managed systems, will be reported to IBM at 1300 on Wednesday, in the time zone of your managed systems, given that your managed systems reside in a time zone that is 12 hours ahead of that of your Central Management Server. In addition to the 24 hours of data (Monday 2400 to Tuesday 2400) that is reported to IBM, an additional 13 hours of performance data (Tuesday 2400 to Wednesday 1300) has now been collected and must be stored by Capacity Manager. This equates to 37 hours (24 + 13) of data storage and therefore exceeds Capacity Manager's initial configuration of 36 hours of data storage time. You can increase Capacity Manager's data storage capacity by following step 5.2 above. 5.3.3 An Additional Note About Time Zones ----------------------------------- You may find that the performance data report sent to IBM daily does not consist of performance data collected over a full 24 hour period because some data is not included in the report. The mechanics of this are discussed in the scenario below. 1. Your Central Management Server resides in a time zone that is 5 hours ahead of the time zone in which your managed systems reside. 2. Electronic Service Agent's (installed on your Central Management Server) scheduler is configured to report performance data to IBM at 0100 on a Wednesday. Your Central Management Server dictates and sets the date of the 24 hour block of data that is to be reported to IBM. In this scenario the 24 hour block of data that is to be reported to IBM is that block of data which has been collected between 2400 on Monday and 2400 on Tuesday. The times between which the 24 hour block of data is collected i.e. 2400 and 2400, is dictated by the time zone in which your managed systems reside. Hence, in theory, in this example, data that has been collected between Monday 2400 and Tuesday 2400 in the time zone of your managed systems, will be reported to IBM. However, since the time zone of your managed systems is 5 hours behind that of your Central Management Server, data is actually scheduled to be reported at 2000 on Tuesday in the time zone of your managed systems. This is 4 hours earlier than the end of the 24 hour block of data collection and means that the 24 hour block of data scheduled to be reported in actual fact consists of only 20 hours of data No data has been collected between Tuesday 2000 and Tuesday 2400 due to the fact that 2400 has not arrived in the time zone of your managed systems. 6.0 README Updates and Contacting Customer Support ____________________________________________________ 6.1 This README document may be periodically updated. You can obtain the latest version of the Electronic Service Agent for Netfinity version 1.1.2 README from the following World Wide Web site: http://www.pc.ibm.com/qtechinfo/MIGR-4L4QVC.html 6.2 Should you encounter problems or have technical questions regarding the Electronic Service Agent for Netfinity product, you should call your nearest IBM support center. You can obtain support center contact details that are appropriate for your country/region from the following web site: http://publib.boulder.ibm.com/pubs/html/as400/ v4r4/ic2924/info/rzajitbl.htm If you are a resident in the United States, support can be reached by calling 1-800-IBM-SERV (1-800-426-7378). When calling IBM quote brand name The Electronic Service Agent for Netfinity and request hardware support. You should have your machine type and serial number when calling. Your machine type is identified by a four digit number. You will be asked for this four digit number and your serial number by IBM support staff. 7.0 Trademarks and Notices ___________________________ 7.1 The following terms are trademarks of the International Business Machines Corporation in the United States, or other countries, or both: IBM Netfinity Electronic Service Agent 7.2 Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. 7.3 Novell and Netware are registered trademarks of the Novell Corporation. 7.4 Other company, product, and service names may be trademarks or service marks of others. 8.0 Disclaimer _______________ 8.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 8.2 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 Corporation. 8.3 You agree to pay any communications charges associated with accessing Electronic Service Agent for Netfinity unless we specify otherwise. (C) COPYRIGHT IBM CORPORATION 2000, 2001. ALL RIGHTS RESERVED.