File Name: dir4.20_readme.txt **************************************************************** | | | IBM(R) Director 4.20 | | | | (C) Copyright International Business Machines Corporation | | 1999, 2004. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under | | "NOTICES" in this document. | | | | This readme file is provided only in English. You can | | obtain the latest version of the readme file from the IBM | | Support Web site. | | | | Updated 11 July 2004. | **************************************************************** CONTENTS -------- 1.0 About this readme 2.0 Installing, upgrading, and uninstalling 2.1 Installing IBM Director 4.20 2.2 Upgrading to IBM Director 4.20 3.0 New functions and support 4.0 Authorized Program Analysis Reports (APARs) resolved by this release 5.0 Known problems and workarounds 5.1 General 5.2 Operating-system specific problems 5.2.1 Linux (general) 5.2.2 Red Hat Linux 5.2.3 VMware ESX Server 5.2.4 Windows Server 2003 5.3 System-specific problems 5.4 BladeCenter products 5.5 IBM Director tasks 5.5.1 Configure Alert Standard Format 5.5.2 Management Processor Assistant (MPA) 5.5.3 Network Configuration 5.5.4 Resource Monitors 5.5.5 ServeRAID Manager 5.5.6 System Availability 5.5.7 Web-based Access 6.0 Support Web sites 7.0 Notices 7.1 Trademarks and service marks 1.0 ABOUT THIS README ---------------------- IBM Director 4.20 is an upgrade release to the following versions of IBM Director: o IBM Director 3.1 o IBM Director 3.1.1 o IBM Director 4.1 o IBM Director 4.10.2 o IBM Director 4.11 o IBM Director 4.12 The following documents have been updated and are available on the "IBM Director 4.20" CD: o "IBM Director 4.20 Installation and Configuration Guide" o "IBM Director 4.20 Systems Management Guide" For additional information about known problems in IBM Director and their solutions or workarounds, see "Solving IBM Director problems" in either of the preceding documents. The following documents are available from the IBM Support Web site: o "IBM Director 4.1 Events Reference" o "IBM Director 4.20 Upward Integration Modules Installation Guide" The documentation is in Portable Document Format (PDF). You need Adobe Acrobat Reader or Xpdf to view it. Check the IBM Support Web site regularly for updated IBM Director documentation and readme files. 2.0 INSTALLING, UPGRADING, AND UNINSTALLING -------------------------------------------- The "IBM Director 4.20 Installation and Configuration Guide" contains instructions for the following tasks: o Installing IBM Director 4.20 o Upgrading to IBM Director 4.20 o Uninstalling IBM Director 4.20 The "IBM Director 4.20 Installation and Configuration Guide" is located in the docs directory on the "IBM Director 4.20" CD. The document is in PDF format. To view it, you must use Adobe Acrobat Reader or Xpdf. 2.1 Installing IBM Director 4.20 -------------------------------- o When you install IBM Director Agent on Linux(R), the following error message might be generated: Could not detect DirAgent supported Linux distribution However, the installation of IBM Director Agent is completed successfully. This error message occurs when another application has modified the /etc/issue file on the system where you are installing IBM Director Agent. 2.2 Upgrading to IBM Director 4.20 ----------------------------------- o Upgrading from IBM Director 4.0 for BladeCenter(TM) products to IBM Director 4.20 is NOT supported. However, you can export the following IBM Director 4.0 data and import it after installing IBM Director 4.20: o Event action plans o Thresholds o Dynamic group definitions o BladeCenter Deployment wizard profiles Instructions are available from the IBM Director Support Web site at http://www.ibm.com/pc/support. Search on "01r0545". 3.0 NEW FUNCTIONS AND SUPPORT ------------------------------ IBM Director 4.20 contains the following new functions and features: o Additional operating systems supported, including the following: o AIX(R) 5L, version 5.2 o IBM i5/OS(TM) Version 5 Release 3 o Novell NetWare 6.5 o Red Hat(R) Enterprise Linux 3.0 (AS, ES, and WS) o Red Hat Enterprise Linux AS, version 3.0, for AMD64, IBM PowerPC(R), and Intel(R) Itanium o VMware ESX Server, version 2.1 (Console and guest operating systems) o BladeCenter Deployment wizard: Support for additional switch modules o Power management using Secure Remote Management for xSeries(R) 206 and 306 servers running Microsoft(R) Windows(R) o Remote Session task: Support for Secure Shell (SSH) o Resource Monitor task: CIM resources supported on Linux o ServeRAID(TM) Manager enhancements o Support for new IBM systems and hardware, including the Intelligent Platform Management Interface (IPMI) baseboard management controller o SNMP version 3 support o System Health Monitoring for certain xSeries servers running Linux 4.0 APARS RESOLVED BY THIS RELEASE ----------------------------------- IBM Director 4.20 resolves the following APARs: o IC17252: On an xSeries 345 server running IBM Director 4.11, unnecessary alerts are generated for power supply 2. o IC36546: On an xSeries 445 server running a German-language version of Microsoft Windows and IBM Director 4.11, a pop-up message is displayed when the server is powered off. This pop-up message also might be displayed when the server is restarted. o IC37317: When IBM Director 4.12 is installed on an xSeries 220 server, a temperature threshold error occurs. o IC37679: Using IBM Director 4.1, you cannot use the Network Configuration task to change the computer name of the managed system. o IC38909: When you add an "Update the Status of the 'event' System" action to an event action plan, you cannot export the event action plan to HTML. o IC39009: After you click "Associations" --> "Resource Monitors" and open the "All Available Thresholds" window for a group, individual thresholds for systems not in the group are displayed. o IC39010: The uninstallation of IBM Director hangs when IBM Director and HP Insight Manager are installed on the same server. o IC39099: The operating-system information that is displayed by the Inventory task and Web-based Access is not consistent. o IC39100: After upgrading to IBM Director 4.1 on a system running Windows, the version number of the system management bus (SMBus) device driver is incorrectly displayed. o IC39292: IBM Director Agent 4.12 running on a ThinkCentre(TM) system sends frequent and unnecessary temperature alerts. o IC39455: After the management server is restarted, IBM Director Server might not receive Windows NT(R) events from managed systems. o IC39475: IBM Director Agent 4.12 running on a ThinkCentre system sends frequent and unnecessary temperature alerts. o IC39527: A defect in the redundant network interface card (NIC) monitoring provider generated a runtime error. o IC39776: Separate managed objects are not created for each SNMP device when multiple SNMP devices have the same non-routable IP address. o IC39778: When IBM Director 4.11 and Tivoli(R) Endpoint are installed on the same system, some events are not displayed in the IBM Director event log. o IC39786: An empty stack Java(TM) exception is generated. o IC39938: When there are many groups on a domain controller, Web-based Access is slow to start. o IC40082: After upgrading to IBM Director 4.11, the File Transfer task takes a long time to complete when using a 256 KBps satellite link. o IC40180: After upgrading to IBM Director 4.12, systems on which IBM Director Agent 3.1 or 3.11 is installed cannot be controlled remotely. o IC40154: An error is displayed when the start and stop times of a repeating scheduled job are identical. o IC40856: When IBM Director 4.12 is installed on an xSeries 345 server, a bluescreen error might occur. o IC40890: When IBM Director Agent 4.12 is running on an xSeries 450 server, Windows NT event log events are not sent to IBM Director Server. o IC40931: You cannot modify the encryption settings for IBM Director Agent running on Windows. o IC41003: Hardware status warnings are not generated when a hard disk drive enters the defunct state. This problem occurs only on xSeries 345 servers running Windows Server 2003 Enterprise Edition with Italian regional settings. 5.0 KNOWN PROBLEMS AND WORKAROUNDS ----------------------------------- IBM Director 4.20 has the following known problems and workarounds. 5.1 General ------------ o Presence check does not work on physical platform managed objects. o When an IBM Director Server installation that includes Management Processor Assistant (MPA) Agent is stopped, a pop-up window might be displayed stating that the following error occurred: twgagent.exe - application error This problem does not affect IBM Director Server; it can be restarted and it will function normally. To correct this problem, obtain and install the IBM ASM Service Processor Device Driver Version 5.24b. The following servers currently support this level: o IBM eServer(TM) xSeries 220, machine type 8646 o IBM eServer xSeries 225, machine type 8647 o IBM eServer xSeries 345, machine type 8670 o IBM eServer xSeries 255, machine type 8670 o IBM eServer xSeries 445, machine type 8870 At this time, there is no correction available for servers that support only the IBM ASM Service Processor Device Driver Version 2.21b. o (IBM Storage Area Network Utility installed) If you installed either IBM Director or the IBM Storage Area Network Utility in a non-default directory, the IBM Storage Area Network Utility might not start. You can successfully start the IBM SAN Utility from the Windows Start menu or from a command prompt. o Do not use the ServeRAID Health event filter in an event action plan; use the ServeRAID Controller event filter or any of its suboptions instead. The ServeRAID health filter is deprecated and will be removed in a forthcoming release. In the "Event Filter Builder" window, on the Event Type page, these event filter types are displayed in the following locations: o CIM | |__ Director Agent Events | |___ ServeRAID Health o Storage | |__ ServeRAID Controller 5.2 Operating-system specific problems ---------------------------------------- This section contains information about problems that are specific to the following operating systems: o Linux (general) o Red Hat Linux o VMware ESX Server 5.2.1 Linux (general) ---------------------- o (Netfinity(R) 5100 or xSeries 230, machine type 8658 server only) You might experience slow file transfer when running the following tasks on managed systems running Linux: o File Transfer o Remote Control o Software Distribution You can disable IBM Director Agent session support to remedy this problem. Complete the following steps to disable session support for the instance of IBM Director Agent installed on the managed system running Linux: 1. Open the following file in an ASCII text editor: /opt/IBM/director/classes/extensions/TCPIP.NETEXT 2. Uncomment the following line: net.session.classname=com.tivoli.twg.netipc.TWGTCPSocketImplFactory 3. Save the modified file. 4. Stop and restart IBM Director Agent. o The "Import Groups" window might be displayed incorrectly the first time that it opens. Expand the window so that it can be clearly seen. o You might not be able to use the system clipboard to copy information into IBM Director windows or entry fields. This is a known limitation of KDE and Java Development Kit (JDK) 1.3.1. o (Managed systems running Linux) The following events are not delivered to IBM Director Server: o IBMPSG_RedundantNetworkAdapterEvent o IBMPSG_RedundantNetworkAdapterSwitchoverEvent o IBMPSG_RedundantNetworkAdapterSwitchbackEvent o IBMPSG_RedundantNetworkAdapterFailedEvent o IBMPSG_RedundantNetworkAdapterOfflineEvent o IBMPSG_RedundantNetworkAdapterOnlineEvent o IBMPSG_ChassisEvent o IBMPSG_LANLeashEvent 5.2.2 Red Hat Linux -------------------- o If you install the IBM SMbus or LM78 device driver, a warning message similar to the following might be recorded in the Bootmsg.log file: depmod: *** Unresolved symbols in /lib/modules/2.4.7-10smp/kernel/drivers/char/.o where is either ibmsmb or ibmlm78. This warning message is generated if the Red Hat Linux kernel was compiled with versioned symbols enabled. Ignore this message; the device driver loaded and will operate properly. o (Red Hat Enterprise Linux AS, version 2.1 or 3.0) System Availability might report an unplanned outage when the managed system is restarted. To avoid this, after installing System Availability, be sure to stop and restart IBM Director Agent before you restart the managed system. 5.2.3 VMware ESX Server ------------------------ o (VMware ESX Server 2.0.1 and earlier) When the Inventory task is run against IBM Director Agent installed on a guest operating system, incorrect information about the amount of memory or number of microprocessors (CPUs) might be displayed. This is a VMware limitation. o (16-way xSeries 445 server, with the Remote Supervisor Adapter II-EXA option) The Remote Supervisor Adapter II-EXA located in the secondary server might display the following server state for the 16-way configuration: "Booting OS or in unsupported OS" This server state occurs even though the secondary server has successfully loaded the device driver for the Remote Supervisor Adapter II-EXA and it can be seen by the Remote Supervisor Adapter II-EXA in the primary server. 5.2.4 Windows Server 2003 -------------------------- o After IBM Director Server is installed, incorrect information about the SMBus device drivers might be displayed in the "Device Manager" window. The SMBus device drivers might be displayed as NOT digitally signed. This is an error; the device drivers are digitally signed by Microsoft. 5.3 System-specific problems ----------------------------- o (xSeries 230 server only) You cannot use the Asset ID task to view System GUID on managed systems running Windows or Linux. On systems running Windows, the System GUID is displayed as an empty string. On systems running Linux, the System GUID is displayed as a string of zeros. o (xSeries 232, 255, 235, 342, 345, 335, 360, and 440 servers only) If no power is running through an installed power supply, whether it is plugged in or in a failing state, the following alert is generated: Power supply device identified as PowerSupply reports critical state with possible loss of redundancy. where is the power supply number. o (xSeries 255 server only) When MPA Agent is installed, the Hardware Status task does not correctly report temperature sensor information. o (xSeries 445, machine type 8870 server only) If an RXE-100 enclosure is attached to an xSeries 445 server with a Remote Supervisor Adapter II installed, events generated by the RXE-100 might be incorrectly displayed in IBM Director Console. They might be displayed as associated with the xSeries 445 server rather than the RXE-100. To make sure that the events are correctly associated with the RXE-100, update the xSeries 445 server firmware to level 1.01 or later. o (Single-node xSeries 450 server only) Rack Manager does not support hardware-status alerts. o (xSeries 455 server only) If IBM Director Server discovers the server shortly after the Remote Supervisor Adapter is restarted, false microprocessor (CPU) and ambient temperature alerts might be generated. Also, incorrect thresholds for these temperatures might be displayed during the same interval. o (eServer 325 server) You cannot change the host name for the IPMI baseboard management controller. By default, the IP address is displayed as the host name. o (ThinkCentre A51, A51P, MP51, and S51 running Windows) When you run the Resource Monitors task on the managed system and view the CPU Monitors resources, resource attributes for two microprocessors (CPUs) are displayed, despite the fact that the system contains only one microprocessor. This occurs if hyperthreading is enabled for the microprocessor. The Resource Monitor task draws data from the operating system, and the operating system interprets a single hyperthreaded microprocessor as two logical microprocessors. 5.4 BladeCenter products ------------------------- o After you remove or insert a blade server, IBM Director might take several minutes to register the changes to the BladeCenter chassis. This can affect the speed with which IBM Director applies chassis detect-and-deploy policies, runs event action plans, updates the chassis association, and writes to the event log. If, after you insert or remove a blade server and wait several minutes, the BladeCenter chassis and blade servers are not properly represented in IBM Director Console, perform a BladeCenter chassis discovery operation. o If the BladeCenter chassis discovery process does not create an SNMP managed object for a BladeCenter switch module, or if an existing SNMP managed object displays the switch module as offline when it is online, make sure that the SNMP community name in the SNMP agent of the switch module is set to "public" and matches the community name in the SNMP managed object in IBM Director Console. IBM Director expects the community name of the SNMP managed object of the switch module to be set to "public." If the community name of the switch module is not set to "public," the BladeCenter chassis discovery will not detect that switch module and will not create an SNMP managed object for that switch module. Also, the community name in the SNMP agent that is installed on the switch module must match the community name in the SNMP managed object in IBM Director Console. Complete the following steps if you must use an SNMP community name other than "public" with a switch module: 1. Set the community name in the SNMP agent that is installed on the switch module to "public." 2. Run the BladeCenter chassis discovery. IBM Director creates an SNMP managed object for the switch module and displays its status as Online. 3. Set the community name in the SNMP agent that is installed on the switch module to the new value. IBM Director Console displays the status of the switch module as Offline. 4. Change the community name in the SNMP managed object to the new value. The status of the switch module is displayed as Online. o (eServer BladeCenter HS40, machine type 8839 server) If firmware level 1.17 is installed, IBM Director generates a hardware status warning for the 12v voltage. To remedy this problem, complete the following steps: 1. Upgrade the firmware installed on the managed system to level 1.18. 2. Stop and restart IBM Director Server. o (IBM eServer BladeCenter JS20 server only) You cannot use the BladeCenter task to set the keyboard/video/mouse (KVM) assignment. However, the KVM assignment task in BladeCenter Assistant lists the BladeCenter JS20 server. If you run the KVM assignment task against the BladeCenter JS20 server, the task appears to be completed without error, although no KVM assignment is made. o When you run the BladeCenter Management subtask against a chassis that contains an Intel Gigabit Ethernet Expansion Card for IBM eServer BladeCenter, the component vital product data incorrectly returns a value for height and width. o (BladeCenter unit with an IBM eServer PCI I/O Expansion Unit installed) If the management module firmware is either level 59D or 59F, when the Inventory task is run against the BladeCenter chassis, the PCI I/O Expansion Unit is incorrectly identified as an IBM eServer BladeCenter SCSI Storage Expansion Unit. Install firmware level 64A or later to resolve this problem. 5.5 IBM Director tasks ----------------------- This section contains information about problems that are specific to certain IBM Director tasks. 5.5.1 Configure Alert Standard Format -------------------------------------- o When you run the Configure ASF task against a managed system, you do not need to select the "Enable ASF Hardware" check box in order to use Secure Remote Management. However, if the "Enable All Platform Event Traps" check box is not displayed, select or clear the "Enable ASF Hardware" check box to enable or disable Platform Event Trap (PET) alerts. 5.5.2 Management Processor Assistant (MPA) ------------------------------------------- o You cannot use the MPA task against a managed system running SCO UnixWare and IBM Director Agent 3.1. 5.5.3 Network Configuration ---------------------------- o If you run the Network Configuration task against a managed system and change a static IP address to an IP address generated by a DHCP server, the gateway address is not modified automatically. You must manually set the gateway address to DHCP on the managed system. 5.5.4 Resource Monitors ------------------------ o When you run the Resource Monitors task on a non-English-language system, the Windows performance monitors are displayed in English only. 5.5.5 ServeRAID Manager ------------------------ o The stand-alone version of ServeRAID Manager and the IBM Director version of ServeRAID Manager cannot be installed on the same managed system. o (Managed system running NetWare) If you use the ServeRAID Manager task to configure logical drives on an IBM ServeRAID-7T controller, the logical drives are created in the blocked state. To solve this problem, restart either IBM Director Agent or the system running NetWare. o (Managed system with an IBM ServeRAID-6M or ServeRAID-4Mx controller installed) If the managed system is running one of the following operating systems, the level of ServeRAID Manager will not be synchronized with the levels of the ServeRAID BIOS, firmware, and device driver: o Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium o SUSE LINUX Enterprise Server 8 for Itanium Processor Family o Windows Server 2003 (for Itanium systems) 5.5.6 System Availability -------------------------- o (Japanese, Korean, Simplified Chinese, and Traditional Chinese only) The System Availability task does not work with managed systems running IBM Director Agent 3.1 or 3.1.1. 5.5.7 Web-based Access ----------------------- o You can use the Network Configuration page to view and configure multiple network adapters in the same system. Consider the following points: o You must click "Apply" after you change the settings for a network adapter. If you do not click "Apply" and then switch to view another network adapter, the changes will be lost. o If you change the IP address, you might lose the network connection after applying the changes. If this occurs, you must reconnect to the system to continue using Web-based Access. o To set the DNS suffix search order for the system, use the DNS Suffix Search Order page. If you edit the DNS suffix search order values, the DNS suffix search order is changed for all network adapters in the system. o (Terminal Services installed) The operating system must be in Install mode before you can successfully install the Java Foundation Class/Swing library (JFC/Swing). 6.0 SUPPORT WEB SITES ---------------------- The following Web pages provide resources for understanding, using, and troubleshooting IBM Director and systems-management tools: o IBM Director 4.20 http://www.ibm.com/pc/support/site.wss/ document.do?lndocid=MIGR-55606 You can download the following IBM Director 4.20 code and information from this Web page: o CD image o Documentation o IBM LM78 and SMBus device drivers for Linux o Readme files o Extensible Markup Language (XML) files for use with the Software Distribution task Check this Web page regularly for updated readme files and documentation. o IBM Director Agent page http://www.ibm.com/servers/eserver/xseries/systems_management/ sys_migration/ibmdiragent.html You can download the IBM Director Hardware and Software Compatibility document from this Web page. This document lists supported eServer and xSeries systems, as well as all supported operating systems. It is updated every 6 to 8 weeks. o IBM eServer Information Center http://www.ibm.com/servers/library/infocenter This Web page provides information about the IBM Virtualization Engine(TM) and IBM Director Multiplatform. o IBM ServerProven page http://www.ibm.com/pc/us/compat/index.html The ServerProven(R) Web page provides information about xSeries, BladeCenter, and IntelliStation(R) hardware compatibility with IBM Director. o IBM Support page http://www.ibm.com/pc/support/ This is the IBM Support Web site for IBM hardware and systems- management software. For systems-management software support, click "Systems management". o IBM Systems Management Software: Download/Electronic Support page http://www.ibm.com/pc/us/eserver/xseries/systems_management/ dwnl.html Use this Web page to download IBM systems-management software, including IBM Director. Check this Web page regularly for new IBM Director releases and updates. 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. It also contains links to Web pages for IBM Director extensions including Remote Deployment Manager, Scalable Systems Manager, Server Plus Pack, and Software Distribution (Premium Edition). 7.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 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. 7.1 Trademarks and service marks --------------------------------- The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: AIX BladeCenter eServer i5/OS IBM IntelliStation Virtualization Engine Netfinity PowerPC ServeRAID ServerProven ThinkCentre Tivoli xSeries Intel is a trademark of Intel Corporation in the United States, other countries, or both. Java is a trademark of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 1999, 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. End