File Name: sp_readme_en.txt last updated on 8/16/2002 ******************************************************************** ** ** ** IBM Director Version 3.1.1 (Service Pack) ** ** ** ** Part number 09N6996 ** ** ** ** (C) Copyright IBM Corp. 1999, 2002 All Rights Reserved ** ** Licensed Materials - Property of IBM(R) ** ** ** ******************************************************************** CONTENTS -------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Installation 6.0 Web Sites and Support Telephone Numbers 7.0 Trademarks 8.0 Notices 1.0 OVERVIEW _____________ IBM Director Version 3.1.1 (Service Pack) is an upgrade release to IBM Director Version 3.1 consisting of new or updated agents, support for new hardware, and limited new functionality. The Console, Server, Agent, and Extensions are modified during the Service Pack installation. Check the web for the latest updates to this file (sp_readme_en.txt) and its translated versions. 1.1 Limitations ________________ o ServeRAID(TM) Manager console strings and online help will revert to English when the Service Pack is installed. o Translated versions of the Service Pack readme (this file) are not available for the French or Simplified Chinese languages. o Previously installed Product Engineering (PE) eFixes must be reinstalled. o (NetWare only) The stand-alone version of the ServeRAID Manager program and the version integrated into IBM Director cannot coexist. o The Fuel Gauge tasks require that you target between one and seven supported managed objects. o ServeRAID System Health will enter only the Warning (yellow) state and Normal state. RAID subsystem errors cannot change the System Health node to the Critical (red) state. o Asset ID Data is not saved if a DBCS character is used in any field. A workaround to this problem is to restart WBEM by executing the following commands after logging on to the Red Hat Linux 7.2J system. /etc/init.d/init.wbem stop /etc/init.d/init.wbem start o Software Rejuvenation does not support IBM OS/2 or Novell NetWare agents. The manual scheduling of a rejuvenation is allowed but all other Software Rejuvenation functions (including Prediction and Service Rejuvenation) will result in an error. o System Availability does not support IBM OS/2 or Novell NetWare. It does allow the task to be activated, but no report information is provided. o VMWare systems provide virtual resource information to the Resource Monitor data, which is provided to Capacity Manager, as opposed to the full physical resource capacity of the hardware. The virtual resource information is determined based on the amount of resources that are allocated for use by the host VM during system configuration. o SunCIM must be restarted when agents on Linux are not unlocking. o The Director Agent will fail to open after changing the system date. This failure occurs the next time the agent is started. A workaround for this problem is to do a refresh while holding ctrl, to force reloading of jar files from server. o ITDAgent-3.11 for Linux fails to shut down properly when shutdown is initiated within two to three minutes after startup. o Software Distribution using certain versions of Linux as an FTP Redirected Server does not work. o IBM Director Agent will no longer monitor fan speed on system types 8301, 8308, 8310, 6290, 6231, and 6849. o WMIAdapter.exe has a memory leak when IBM Director Agent v3.1 is running Windows 2000. Memory usage grows but will correct itself after the Agent browser is closed for a few minutes. o IBM Director Agent running IIS cannot display the header2.htm file. In the space where Next System, Export and Help should be (in the upper right corner of the browser window), is the message: "The page cannot be displayed." This problem can be eliminated by changing the cgi-bin/nls/en directory execute permissions to scripts only. o Server Service remains inactive after adding an RXE-100. This problem exists on the first restart after connecting the RXE-100. If the server is started manually or restarted a second time the server becomes active. o Installing both the IBM Director Agent and the IBM Director Console (in either order) on a ThinkPad A31p might not complete successfully. Users should install the agent or the console but not both on the A31p ThinkPad. o When installing Capacity Manager 3.1.1 agent and using Gigabit Ethernet in the Windows Platform, use the Monitor Activator to verify all network adapters are turned on after the initial restart. o When attempting to add a Windows 2000 client to a domain and creating an account in that domain you must have Account and Password privilege of a Domain Administrator or greater. A Windows NT 4 client connecting to a domain controller and creating an account is not supported. o The ASF interface cannot be completely navigated by keyboard input. If an error message is displayed, the user MUST have mouse control to continue. o On the IBM xSeries 345, ASF does not report an error when the new IP address for the Management Server is unreachable from the Agent. When this occurs, the previous value for the Management Server is restored and displayed. o DHCP support is not available for ASF. If the ASF NIC is enabled for DHCP, the NIC IP address, Gateway IP address, and Subnet mask fields have to be manually changed by the user. This change must be made every time a new IP address is assigned by the DHCP server. o On systems that have dual port ASF capable NICs, only one can be used for ASF and the user can not select the port to use. The first port that is found to be ASF capable is selected by IBM Director. On such systems, the user will have to use the Physical address (MAC) in identifying the physical location of the port. o Remote control cannot access a ThinkPad T30 (system types 2366, 2367) running Windows XP from IBM Director Console. o The IBM Director Agent will provide some, but not all, of the in-band alerts that were previously provided by MPA. This is because the CIM provider is not included in the service pack. o IBM IntelliStation M Pro (system types 6849, 6231, and 6229) display false voltage alerts after the installation of IBM Director Agent. A workaround is to delete umshealth.dat, which eliminates the core voltage instance from the system health list. o When one NIC in a teamed NIC configuration is unplugged a notification shows up in Hardware Status under the Networking category. There is no text associated with this error, but when the event is highlighted, the detailed text at the bottom of the window is correct. o The installation of the IBM Director Agent 3.1 Service Pack to an IBM Director Management server using Software Distribution is not supported. However, if this is attempted, the Software Distribution log will erroneously report that the install completed successfully. o Limitations of how the operating system, BIOS, and processor architecture work in conjunction with IBM Director and hyperthreading can result in the incorrect number of processors being reported or a processor might be portrayed with an incorrect speed. o The IBM Director Console Extensions and IBM Director Agent Extensions cannot be installed on a system with just the Console and Agent installed. Extension support is not functional when both have been installed. This is not a problem on a Director Management server installation which includes both Console and Agent support. o When an IBM xSeries 345 is turned off and then on, and ASF is enabled and configured on the system, the following alert is received by the Management Server. Event Type Event Text Severity Category ASF.Hardware.Drivebay Device Inserted Harmless Resolution Other event reporting channels in IBM Director (such as Hardware Status and System Health) are not affected by this issue. A firmware upgrade for the integrated systems management processor will resolve this issue. Refer to the online support Web site for your system to download this update. o If ASF is enabled and configured on an IBM xSeries 345, a minimum wait time of 30-40 seconds is required between reporting of hardware failure alerts. If more than one hardware alert occurs in a span of 30-40 seconds, only the first one is reported as an ASF alert. Other event reporting channels in IBM Director (such as Hardware Status and System Health) are not affected by this issue. o IBM Director Agent Web browser interface might be unusable after the Service Pack is installed on Windows 95, Windows 98, or Windows Millennium Edition. To fix this problem, check the %UMS_HOME%\Apache\modules directory for the file MOD_LO~.SO and if present rename it to mod_locale.so. This problem only occurs if you apply the service pack within five minutes of accessing the system through the Web browser interface. You can avoid the problem by waiting five minutes after using the Web browser before applying the service pack, or by using to find and kill, in this order, the tasks HTTPD.EXE, APACHE.EXE, and JSERV.EXE. o When uninstalling IBM Director on Windows NT the error message Setup Initialization Error is displayed. This happens when Uninstall is reporting Director Server as being uninstalled. After clicking OK to the message, the uninstall appears to continue without any problems. However, a restart results in the Director Support Service still running. Director Server is listed as a service but is not functional and the registry keys remain. To complete the uninstall wait until the first uninstall completes and run %WINDIR%\twgxserv.exe. This will perform the remaining uninstallation tasks. To complete the uninstall wait until the first uninstall completes and run %WINDIR%\twgxserv.exe. This will perform the remaining uninstallation. o The uninstall script for Linux does not delete all files. The error messages state that the directory (ex. /var/sadm) could not be removed because it was not empty, but the directory was actually removed when the post uninstall section of the rpm is invoked. The following files or directories have been noted as not being removed: /opt/tivoliwg/classes/com /opt/tivoliwg/classes /opt/tivoliwg/bin /opt/tivoliwg /opt/tivoliwg/classes/com /opt/tivoliwg/classes /opt/tivoliwg/bin /opt/tivoliwg o The uninstall of ASF does not remove all related files. Because ibmasfsrv.exe does not completely shut down, the uninstall cannot delete the file ibmasfsrv.exe, because it is locked. The file ibmasfsrv.exe can be manually deleted after a restart. o System Health does not always load information on some systems because WinMgmt requires a restart following the first restart after the installation. Without the restart, the WinMgmt event subsystem does not initialize properly which is evidenced by health information not loading. o During the Service Pack installation WinMgmt errors might be recorded in the application log and can be observed in the event viewer. These errors are a result of the installation and can be ignored. o IBM Director v3.1 Service Pack does not support unattended installation on Windows XP. A Kill utility error message might be displayed during Service Pack installation on Windows XP. However, the message can be ignored and installation will continue to completion. 1.2 Enhancements _________________ This Service Pack provides you with new hardware support and any fixes provided by level-3 support. The next release of IBM Director will include the Service Pack changes as well as an upgrade installation for systems already installed with the Service Pack. See "2.0 Change History" for fix and enhancement details. 1.3 Prerequisites __________________ This Service Pack is only for IBM Director version 3.1 systems. When you install the Service Pack on an IBM Director Agent, you must install the Service Pack on your IBM Director Consoles and IBM Director Management Server. 1.4 Additional platforms _________________________ Red Hat Linux(R) RPM, IBM OS/2(R), and Novell NetWare files are available from the IBM Support Web site. See "6.0 Web Sites and Support Telephone Numbers" for additional information. 2.0 CHANGE HISTORY ___________________ Listed are the details and history for fixes, symptoms, or both, and new enhancements since the previous release. 2.1 Director 3.1 eFixes ________________________ Apar IC32954 (23166/22964) File Transfer of files larger than 4Gb fails Apar IC32799 "ADD" button text translated incorrectly in Japanese Apar IC32736 Java exception editing/creating event filters after upgrade Defect 23840 Remote console unable to update preferences/data on server Defect 23348 Background wallpaper not disabled on Windows XP during remote control Apar IC34093 (22854) twgsysin.sys hangs with multi-processor system on Windows NT4 server (JP) Defect 23785 Server terminates discovering all systems with high/RAS enabled Defect 23755 2.2 Console hangs connecting to 2.2 Server after 3.1 console connection Defect 23991 SQL Database data files might be created in the wrong directory Defect 24035 Modify SNMP listener for UPS problem Defect 23153/16191 Director Systems Table displays wrong date Defect 24068 Customize event action error messages not translated (internal table names used) Defect 24008 Reject log on from uplevel consoles Defect 24123 IBM xSeries 440 Multiple processors have incorrect name in Windows NT Performance monitors Defect 24125 IBM xSeries 440 Multiple processors not showing correct processor utilization Defect 24126 Add event details to email sent out of SMTP Action handler Apar IC33203 (24166) Use english qualifiers when publishing event types Defect 24181 SockV5 password is read incorrectly Defect 24198 IBM xSeries 440 Multiple processor total is tracking last processor Defect 24214 IBM xSeries 440 Bus Scan NMI running IBM Director Defect 24212/17634f_1 Cim Browser: Methods help locks up Defect 24234 Console connect fails with SOCKSV5 authentication Defect 24231 Add SNMP messages not in Director 3.1 Apar IC33452 (24237) JEXP in SNMPMultiHomedCheck if bad subnet mask Apar IC32932 (23500) Director 3.1 fails to send alphanumeric page for event action Defect 24244/18503 File transfer: NW6 agnt admin folder can still be accessed Defect 24252/18814 IBM xSeries 440 Inventory times out on SuSe 8.0 Defect 24260/18980 Memory on the IBM xSeries 440 with SuSe 8.0 is incorrect Defect 24267/19120 Update fstype for ext3 on Red Hat Linux 2.1 AS Defect 24269/18803 Install: Twgmonit.exe traps after install Apar IC33594/Defect 24255 Japanese file transfer modifies the time stamp Defect 24271/19193 Twgmonit.exe traps when stopping twgipc Defect 24272/19197 Inventory: disk information wrong in inventory Apar IC33650/Defect 24263 File modified threshold alert has GMT offset wrong Defect 24280/19276 Install: twgmonit.exe traps on single processor systems Apar IY20426/Defect 24279 Keystrokes lost when using Remote Control in a WINOS2 Window Defect 24282/19339 Inventory: Processor Unknown Defect 24283 SMBIOS version check failed, > 2.1 needed Defect 24286 Add Powerware/UPS specific SNMP mapping entries Defect 24287 Change in OID for Powerware/UPS SNMP mapping entries Defect 24285 Netdrvr.ini gets extremely large Defect 24294/19533 Wrong processor speed reported from inventory in console Defect 24296/19676 IBM model type does not match known format on some BIOSs Defect 24297/19665 Inventory fails due to Java exception in TWGHwColNetbios Defect 24245/19711 Inventory: Processor family "unknown" Defect 24301/19991 Inventory: Asset ID trap for certain agents Defect 24299 Additional SNMP to event rules Defect 24303/19868 IBM xSeries 305; Inventory not collecting data in many catagories Defect 24306/19991f_1 Inventory: Unhandled JVM error causes inventory to fail Defect 24316/20946 Fixed trap in twgipc.exe Defect 24322/21349 SNMP device problems after uninstalling Intel extension on an IBM xSeries 343 Defect 24327 Fix console crash when user with no privileges tries file transfer Defect 24331 Relay Broadcast not forwarded if agent secured Defect 24333 Console Crash ThinkPad T30 Agent 2.2 Director Agent 3.1 eFixes ______________________________ Apar IC32829 (IBM xSeries Models 8668 and 8669 only) When the IBM Automatic Server Restart Service version 4.03 is installed with IBM Director 3.1, the system might unexpectedly restart after several hours of uninterrupted operation. Apar IC32839 (IBM xSeries Models 8668 or 8669 only) When IBM Director 3.1 is installed on these servers, after several hours of continuous operation, some of the hardware sensors will become unresponsive. Apar IC32846 (IBM xSeries Models 8668 or 8669 only) If the IBM Automatic Server Restart Service is installed before installing IBM Director 3.1, the following Windows Event Viewer errors are logged. Apar IC32847 (IBM xSeries Models 8668 or 8669 with one processor only) IBM Director will indicate Voltage Sensor #6 is below its threshold. Disregard this error. Apar IC32742 (IBM xSeries Model 6229 only) IBM Director 3.1 does not support hardware environmental sensors and does not report status for all available sensors. Apar IC32778 (IBM IntelliStation(R) Model 6596 only) IBM Director 3.1 does not have native hardware sensor support (for example, fan speed or temperature). Apar IC32816 (IBM Point Of Sale Models 4840 and 4835 running Windows 95, Windows 98, Windows NT 4.0, Windows 2000, and Windows XP only) When IBM Director 3.1 is installed, the system will hang during shut down. Apar IC32738 (ThinkPad(R) Models T20, T21, and T21s running Windows 98 and Windows 2000 only) After installing the Director 3.1 Agent, the diskette drive becomes inaccessible. The LM78 device interferes with the diskette drive. Uninstalling IBM Director does not remove the LM78 device drivers. Apar IC32848 The IBM Director 3.1 ServeRAID Server Extension will not create alerts if a Director Server has not discovered the system. The ServeRAID Server Extension requires an active Director Agent. To conserve resources in a stand-alone mode, the Agent does not fully activate until a Director Server discovers the Agent. If the Director Agent is used in a stand-alone configuration, the ServeRAID Server Extension will not start and will not produce alerts. Apar IC32852 When the IBM Director 3.1 ServeRAID Server Extension is run on Windows NT, Windows 2000, or Windows XP using French, Spanish, or German language support, the Extension will not create error log entries properly in the Windows Event Viewer. Apar IC32799 (Japanese only) In several windows, the "Yes" button is not translated correctly. Apar IC32736 After IBM Director Server version 3.1 is installed on a system that already has IBM Director version 2.2 or 2.21 installed, the Event Action Plan Builder fails. Specifically, if a user tries to create a simple event filter, a communication error message is displayed and the Director Console must be closed. Defect 16968 The Asset ID graphical user interface (GUI) does not display the date for Lease, Asset & Warranty. 2.3 Director Extensions 3.1 eFixes ___________________________________________ o System Availability 3.1.1 - Defect 17873 Support for SuSE 7.3 2.4 Enhancements _________________ The following enhancements are included in this Service Pack: o Support for new hardware functionality. o Alert Standard Format (ASF) There are new servers that support a vendor-supplied ASF-aware Network Interface Card (NIC). These servers support sending SNMP-style alerts for basic environmental monitoring in all power states (on, off, sleep). The SNMP listener has been updated to handle Platform Event Traps (PET) format events in IBM Director. See your hardware manual to see if the ASF hardware is present and supported on your server. The ASF hardware can be configured from the IBM Director Console or the IBM Director Agent browser. See the online helps for information regarding configuring the ASF hardware. ASF is only supported on IBM xSeries hardware and Microsoft Windows NT and Windows 2000 operating systems. NOTE: When upgrading to advanced systems management hardware (such as Remote Supervisor Adapter), the ASF functionality must be manually disabled prior to the upgrade. o ServeRAID Manager Support has been added for the following IBM xSeries hardware: - Integrated SCSI controller with RAID capabilities (LSI 1020 and LSI 1030) hereafter referred to as the integrated RAID controller - IBM ServeRAID-5i Ultra160 SCSI controller - Tape drive The IBM Director inventory collection process supports the new hardware. Inventory data is no longer specific to ServeRAID, but also includes data for integrated RAID controllers. Several tables have been renamed to reflect this change: Table Old Name Table New Name -------------- -------------- ServeRAID Disk Drives RAID Disk Drives ServeRAID Enclosures RAID Enclosures ServeRAID Logical Drives RAID Logical Drives ServeRAID Controllers RAID Controllers The ServeRAID Manager program also includes support for: - Scan for new drives - NetWare installation - special case o Hot-Spare Memory Reporting When new hardware is configured with hot-spare memory enabled, the IBM Director Agent Common Information Model (CIM) provider will report the memory as Spare. The IBM Director Server inventory system will display the spare memory, but will not indicate that it is reserved as spare. The Director Point-to-Point Memory graphical user interface (GUI) will annotate spare memory as Spare. 3.0 INSTALLATION AND SETUP INSTRUCTIONS ________________________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Important: The user or process installing IBM Director must have Administrator privileges to install this Service Pack. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NOTE: In multiuser Windows environments such as Windows NT Terminal Server Edition or Windows 2000 with Terminal Services, the system must be placed in install mode before installing this Service Pack. This can be accomplished by running the following from the command line: change user /install This Service Pack applies to the following Director component levels: o Director 3.1 o Director Agent 3.1 o Director Extensions 3.1 This Service Pack applies to the following operating systems: o Microsoft(R) Windows(R) XP Professional o Microsoft Windows Millennium Edition(R) (Me) o Microsoft Windows 2000 Professional o Microsoft Windows 2000 Server and Advanced Server o Microsoft Windows 2000 DataCenter, including Service Pack 2 o Microsoft Windows NT(R) 4.0 Server, Workstation, and Enterprise Edition o Microsoft Windows NT Terminal Server o Microsoft Windows 98 (including Second Edition) o Redhat Linux(R) 6.2, 7.1, 7.2, 7.3, and 2.1 Advanced Server o SuSe Linux 7.1, 7.2, 7.3, 8.0 o Caldera Linux 2.3.1, 3.1 o Caldera OpenUnix 8.0 o TurboLinux 6.0.5, 6.5 o SCO UnixWare 7.1.1 o IBM OS/2(R) Warp Server for eBusiness with Convenience Packages 1 and 2 o Novell NetWare 5.0 (Service Pack 1 or later), 5.1, 6.0 o VMWare ESX Server 1.5 (console VM only) This Service Pack requires 35MB for a full installation. 3.1 Primary installation _________________________ Before installing the Service Pack, you must have IBM Director 3.1 installed. You can find additional Microsoft Windows installation instructions in the \README directory: Installing_the_ServicePack_xx.htm where xx indicates the language of the translated readme file. The Service Pack is available in the following media: o Web download You can download the following files from the web site. - Linux Install Script - Linux UnInstall Script - Linux ASM RPM - Linux Framework Agent RPM - Linux RAID RPM - Linux SysAvail RPM - OS/2 Fixes ZIP - UNIX RAID Pkg - SMS Software Dist Package BFP - Linux Software Dist Package BFP - Win Software Dist Package BFP - Plus Module TAR - Director 3.11 PFTW (Package for the web) - Director 3.11 CD ISO Image See Section 6.0 WEB SITES AND SUPPORT TELEPHONE NUMBERS for URL information. Not all files on the web site are for primary installation. The Director 3.11 CD ISO Image is downloadable for burning a CD for use in the Service Pack installation. The files SMS Software Dist Package BFP, Linux Software Dist Package BFP, and Win Software Dist Package BFP are for distributing the Service Pack using the IBM Director Software Distribution function. o CD of the IBM Director 3.1 Service Pack 1, which is shipped with IBM xSeries servers. The following directories, which contain installation files are available: - File Packages - Linux - OS/2 - SCO - UM Services Plus for Tivoli - win32 3.1.1 Microsoft Windows installation ____________________________________ NOTE: Unattended install is supported. See "Section 5.0 Unattended Installation" for details. The Service Pack includes the file DA311SP.EXE. You can use this file for distributing the Service Pack to Microsoft Systems Management Server (SMS) clients. This distribution file is located in the \SERVICEPACK\DIRECTOR\FILE_PACKAGES\SMS directory. 3.1.1.1 Web-delivered Service Pack installation _______________________________________________ To install the Web-delivered Director 3.11 PFTW (Package for the web) Service Pack, use the following procedure: 1. Using Windows Explorer, view the directory that contains the downloaded file DirectorAgent311.EXE. 2. Double-click the file DirectorAgent311.EXE. The package for the web file extracts the files needed for the installation, and starts the installation. 3. Answer the prompts as they appear. 4. Click either to restart your system now or to restart later; then, click Finish. 3.1.1.2 CD Service Pack installation ____________________________________ To install using the CD, use the following procedure: 1. Using Windows Explorer, view the CD. 2. Change from the CD root directory to the \SERVICEPACK directory. 3. Double-click the file IBMSETUP.EXE. The file self-extracts the necessary files and starts the Service Pack installation. 4. Follow the prompts to complete the installation. When the installation is complete, click "Finish" to restart your system. 3.1.2 Linux installation ________________________ 3.1.2.1 Web-delivered Service Pack installation ________________________ To install all parts of the Service Pack on the Linux operating system, use the following procedure: 1. Download Linux Install Script (dir311install), Linux ASM RPM (asmlxag-3.1.1-0.i386.rpm), Linux Framework Agent RPM (ITDAgent-3.11-1.i386.rpm), Linux RAID RPM (raidlxag.rpm), Linux SysAvail RPM (SysAvailAgent-3.11-1.i386.rpm) from the Web site. 2. CD to the directory where the downloaded files were saved. If you do not need all parts of the Service Pack installed, edit the Linux Install Script (dir311install) and comment out whichever xSeries Extension tool rpm that is not wanted by adding a # as the first character of the unwanted tool rpm command line. 3. Type ./dir311install and press Enter. The installation stops the Director Agent and does not restart the Agent when the installation is complete. You must manually restart the Agent or restart your system, which will start the Agent automatically. 3.1.2.2 CD Service Pack installation ____________________________________ To install the Service Pack on the Linux operating system, use the following procedure: 1. Insert the CD into the CD-ROM drive. 2. Mount the CD by typing: mount -t iso9660 -o map=off /dev/cdrom /mnt/cdrom 3. Press Enter and then type: cd /mnt/cdrom/ServicePack/Director/Linux where mnt is the mount point of the device file created in step 2. 4. Press Enter and then type: ./dir311install 5. Press Enter. The installation stops the Director Agent and does not restart the Agent when the installation is complete. You must manually restart the Agent or restart your system, which will start the Agent automatically. 3.1.3 Caldera UnixWare installation ___________________________________ 3.1.3.1 Web-delivered Service Pack installation _______________________________________________ To install the Service Pack on UnixWare, use the following procedure: 1. Download UNIX RAID Pkg (raiduwag.pkg) from the Web site. 2. CD to the directory where the downloaded file was saved. 3. Next enter pkgadd -d raiduwag.pkg and press Enter. 3.1.3.2 CD Service Pack installation ____________________________________ To install the Service Pack on the UnixWare operating system, use the following procedure: 1. Insert the CD into the CD-ROM drive. 2. Mount the CD by typing: mount -r -F cdfs /dev/cdrom/cdromdevicefile /mnt where cdromdevicefile is the specific device file for the CD-ROM block device. Look in the /dev/cdrom directory to determine what cdromdevicefile is on your server, for example, c0b0t010. 3. Press Enter; then, type: pkgadd -d /mnt/ServicePack/director/unix/RAIDUwAg.pkg where mnt is the mount point of the device file created 4. Press Enter. 3.1.4 Novell NetWare and IBM OS/2 installation ______________________________________________ Before installing the IBM Director 3.1 Service Pack 1 on Novell NetWare you must stop the ServeRAID Director agent. Use the following steps to stop the ServeRAID Director Agent: 1. Get a list of the running Java Processes by entering on the server console: java -show 2. Find the com.ibm.sysmgt.raidmgr.DP process and its associated process ID in the list of Java processes. 3. Stop the ServeRAID agent by entering on the server console: java -kill Where is the process ID located in step 2. 3.1.4.1 Web-delivered Service Pack installation _______________________________________________ To install the Service Pack on Novel NetWare or IBM OS/2, use the following procedure: 1. Download OS/2 Fixes ZIP (os2_dir311.zip) from the Web site. 2. CD to the directory where the downloaded file was saved. 3. Next enter pkgadd -d raiduwag.pkg and press Enter. 3.1.4.2 CD Service Pack installation ____________________________________ Use the following information to install the Service Pack on IBM OS/2 or Novell NetWare. Fixes for the IBM Director Agent running on NetWare and OS/2 are installed using a self-extracting zip file. Extract the zip file into the %UMS_HOME% directory. Fixes for the IBM Director Extensions you must run the Service Pack installation program from a system running Windows NT or Windows 2000. Other Windows operating systems will not work. The distribution package provided with the Service Pack does not include the necessary files to update Server extensions. If you would like to include the Server Extensions in your software distribution you will need to create a custom package that includes the files off of the cd from: /ServicePack/Director/win32 /ServicePack/umse To install the Service Pack on the OS/2 or NetWare operating systems, use the following procedure: 1. Map a drive to the target OS/2 or NetWare system. 2. On the target system, type the following command to stop IBM Director and enable the installation: Target operating system Type ________________________________________________________ OS/2 twgipc shutdown ________________________________________________________ NetWare unload twgipc 3. On the source Windows system, type the following command at the command prompt and press Enter: d:\directory\os2netw\xsesetup.exe where d and directory are the drive and the directory where the Service Pack files are located. The os2netw directory contains the installation files for the OS/2 and NetWare installations. 4. Click OK, then click Next. 5. In the Select Platform window, click your target operating system. 6. Select the destination directory or click Next to accept the default. 7. When the installation is complete type the following command on the console of the target system and press Enter to restart IBM Director: twgipc 3.1.5 IBM Director Agent Plus Module for Tivoli Enterprise Framework ____________________________________________________________________ 3.1.5.1 Web-delivered Service Pack installation _______________________________________________ To install the Service Pack on Plus Module, use the following procedure: 1. Download Plus Module TAR (UM_Services.tar) from the Web site. 2. CD to the directory where the downloaded file was saved. 3. Next unpack the tar file. 4. Locate the README.1ST file for installation instructions. 3.1.5.2 CD Service Pack installation ____________________________________ This Service Pack includes an update to the IBM Director Agent Plus Module for Tivoli Enterprise Framework. For information on installing this update, see the README.1ST file located in the following directory: \ServicePack\director\UM SERVICES PLUS FOR TIVOLI 3.2 Uninstall ______________ The IBM Director 3.1 Service Pack 1 does not support uninstallation. The user must uninstall IBM Director 3.1 (which now includes the Service Pack) and reinstall IBM Director 3.1 to return to a IBM Director version 3.1 level. When uninstalling IBM Director Server be sure to answer NO to the pop up message saying "Would you like to delete the Director configuration data and the associated ODBC Data Source, if applicable?" This action will save your current installation configuration. 4.0 CONFIGURATION INFORMATION ______________________________ This Service Pack is only for IBM Director, version 3.1, with the configurations listed in "Section 3.0 Installation and Setup Instructions." This Service Pack is not intended for use with other versions of the product and might cause serious functionality problems or loss of data if misused. Do not install this Service Pack on versions or configurations other than those that are listed in this readme. 5.0 UNATTENDED INSTALLATION ____________________________ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Important: The user or process installing IBM Director must have Administrator privileges to install this Service Pack. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NOTE: In multiuser Windows environments such as Windows NT Terminal Server Edition or Windows 2000 with Terminal Services, the system must be placed in install mode before installing this Service Pack. This can be accomplished by running the following from the command line: change user /install The silent or unattended installation is supported (running setup -s) with the installation file included on the CD. However, you cannot customize the unattended installation. 6.0 WEB SITES AND SUPPORT TELEPHONE NUMBERS ____________________________________________ o IBM Director 3.1 plus Service Pack 1 download/publications page (http://www.pc.ibm.com/qtechinfo/MIGR-40738.html) provides access to download IBM Director 3.1 plus Service Pack 1 and to view the IBM Director 3.1 publications. o IBM Universal Manageability Discussion Forum http://www7.pc.ibm.com/~ums/ IBM forums put you in contact with other IBM users. The forums are monitored by IBM technicians. o IBM Online Assistant and e-Mail http://www.pc.ibm.com/qtechinfo/MIGR-4Z7HJX.html This Web page offers a quick resource to help solve your technical questions. Follow the instructions on this page to find additional solutions for your Systems Management tools. If you do not find an acceptable solution, or you just want to bypass looking for your own solution, you can submit an electronic question. From any page within the IBM Online Assistant, select "None of the above" and you will be directed to submit an electronic inquiry. Response times vary between 24 and 48 hours. o IBM xSeries Systems Management page http://www.ibm.com/pc/ww/eserver/xseries/systems_management/index.html This Web page presents an overview of IBM Systems Management and IBM Director. o IBM Universal Manageability page http://www.ibm.com/pc/us/pc/um/index.html This Web page links to an IBM portfolio of advanced management tools that help lower costs and increase availability throughout a product life cycle. o IBM Support page http://www.ibm.com/pc/support/ This Web page enters the IBM Support Web site for IBM hardware and Systems Management software. For Systems Management software support, click Systems management. 7.0 TRADEMARKS _______________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: the e-business logo IBM IntelliStation OS/2 ServeRAID ThinkPad xSeries Microsoft, Windows, and Windows NT 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. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds. Other company, product, and service names might be trademarks or service marks of others. 8.0 NOTICES ------------ 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 jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might 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 might make improvements and/or changes in the products and/or the programs described in this publication at any time without notice. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ============================================================================== End of Document