File Name: dir412_readme.txt **************************************************************** | | | IBM(R) Director Version 4.12 Update | | | | (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. | | | | Updated 16 March 2004. | **************************************************************** CONTENTS 1.0 About this readme file 1.1 Compatibility with previous versions of IBM Director 1.2 Supported operating systems 1.2.1 Changes to previously supported operating systems 1.2.2 New supported operating systems 1.3 New database support 1.4 New partitioning support 1.5 About the "IBM Director Version 4.12" CD 1.6 Packages included in this update 1.6.1 Packages for Microsoft Windows 1.6.1.1 IBM Director for Windows 1.6.1.2 IBM Director for Windows patches 1.6.1.3 Notes about Microsoft Installer software patch (MSP) files 1.6.2 Packages for Linux 1.6.2.1 IBM Director for Linux 1.6.2.2 IBM Director for Linux patches 2.0 Change history 3.0 Installation 3.1 Installation on Windows 3.1.1 Installing an IBM Director 4.12 Update on Windows 3.1.2 Installing IBM Director Agent, Version 4.12, on Windows 3.2 Installation on Linux 3.2.1 Installing IBM Director Agent, IBM Director Console, or IBM Director Server, Version 4.12, on Linux 3.2.2 Installing IBM Director Agent and IBM Director Console patch, Version 4.12, on Linux 4.0 Issues resolved by this update 5.0 Known problems and workarounds 5.1 General 5.2 BladeCenter products and BladeCenter Assistant 5.3 Web-based Access 5.4 xSeries 450 and 455 servers 5.4.1 General 5.4.2 Management Processor Assistant 5.5 Operating-system specific problems 5.5.1 Windows 5.5.2 Linux 5.5.3 VMware ESX Server 5.5.4 Other operating systems 6.0 Serial over LAN support in the BladeCenter Assistant task 6.1 Serial over LAN configuration 6.2 Serial over LAN status 7.0 Corrections to the documents 7.1 Installation and Configuration Guide (dir411_install.pdf) 7.2 Systems Management Guide (dir411_sysmgt.pdf) 6.8 Support Web sites 9.0 Notices 1.0 ABOUT THIS README FILE --------------------------- This readme file provides information about IBM Director Version 4.12. IBM Director Version 4.12 is an update release to IBM Director Version 4.11. This readme file is provided as an addition to the following files: o (IBM Director 4.1) readme4.1.txt o (IBM Director 4.11) dir411_readme.txt Make sure that you read all of these files. They are included in this release. These readme files are provided in English only. In addition to these readme files, the following publications are available from the IBM Support Web site: o "IBM Director 4.11 Installation and Configuration Guide" o "IBM Director 4.11 Systems Management Guide" o "IBM Director 4.1 Events Reference" o "IBM Director 4.1 Upward Integration Modules Installation Guide" The guides are in Portable Document Format (PDF) and require Adobe Acrobat Reader to view them. 1.1 Compatibility with previous versions of IBM Director --------------------------------------------------------- When installing this update, consider the following compatibility statements: o IBM Director Server, Version 4.12, supports connections to IBM Director Console, Version 4.12 only. o IBM Director Console, Version 4.12, supports connections to IBM Director Server, Version 4.12 only. o IBM Director Agent, Version 4.12, is supported by IBM Director Server, Version 4.12 only. o IBM Director Server, Version 4.12, supports the following versions of IBM Director Agent: o IBM Director Agent, Version 3.1 o IBM Director Agent, Version 3.1.1 o IBM Director Agent, Version 4.1 o IBM Director Agent, Version 4.10.2 o IBM Director Agent, Version 4.11 If you upgrade your management server, you must upgrade all of your management consoles. Different versions of IBM Director Console and IBM Director Server do not communicate with one another. 1.2 Supported operating systems -------------------------------- IBM Director adds operating-system support as new operating systems become available. For the most recent list of operating systems on which IBM Director can be installed, see the IBM Director Hardware and Software Compatibility document. This PDF file is updated every 6 to 8 weeks. You can download it from http://www.ibm.com/servers/eserver/xseries/systems_management/ sys_migration/ibmdiragent.html. See the "IBM Director 4.11 Installation and Configuration Guide" (dir411_install.pdf) for information and installation instructions for previously provided operating-system support. 1.2.1 Changes to previously supported operating systems -------------------------------------------------------- For IBM Director Server, IBM Director Console, and IBM Director Agent, Version 4.12, support for SUSE LINUX Enterprise Server 8 (32-bit) now requires Service Pack 3. The service pack is required to meet GLIBC (GNU C library) dependencies. 1.2.2 New supported operating systems -------------------------------------- The IBM Director Version 4.12 Update provides new operating- system support for IBM Director Agent: o SUSE LINUX Enterprise Server 8 for Intel(R) Itanium2 Processor Family (Service Pack 3 required) o SUSE LINUX Enterprise Server 8 for AMD64 (Service Pack 3 required) o SUSE LINUX Enterprise Server 8 for IBM iSeries(TM) and pSeries(R) servers (Service Pack 3 required) Note: This operating system is supported on the IBM eServer(TM) BladeCenter(TM) JS20 only. o Microsoft(R) Windows(R) Server 2003, Enterprise Edition for 64-Bit Itanium-based systems o Windows Server 2003, Datacenter Edition for 64-Bit Itanium- based systems o VMware ESX Server, Version 1.5.2, with the following guest operating systems: o Windows Server 2003 Standard and Enterprise Editions (VMware ESX 1.5.2 Patch 3 required) o Windows 2000 (Professional, Server, and Advanced Server Editions) o Windows NT(R) Workstation and Enterprise Server Editions (Service Pack 4 or later required) o Red Hat(R) Linux, Versions 7.1 and 7.2 o Red Hat Enterprise Linux AS, Version 2.1, formerly Red Hat Linux Advanced Server, Version 2.1 (VMware ESX 1.5.2 Patch 3 required) o SUSE LINUX, Version 7.3 o VMware ESX Server, Version 2.0, with the following guest operating systems: o Windows Server 2003 (Standard, Web, and Enterprise Editions) o Windows 2000 Professional, Server, and Advanced Server Editions (Service Pack 3 or later required) o Windows NT Workstation and Enterprise Server Editions (Service Pack 6a or later required) o Red Hat Linux, Version 7.3 o Red Hat Enterprise Linux AS, Version 2.1 (formerly Red Hat Linux Advanced Server, Version 2.1) o SUSE LINUX Enterprise Server, Version 8.0 1.3 New database support ------------------------- IBM Director now supports IBM DB2(R) Universal Database(TM) 8.1 (Fix Pack 2). 1.4 New partitioning support ----------------------------- IBM Director 4.12 supports Scalable Systems Manager 4.12. Additionally, IBM Director 4.12 contains static partitioning changes that apply to users of Scalable Systems Manager 4.12. These changes are explained in the readme file for Scalable Systems Manager 4.12. Furthermore, xSeries 455 servers can be discovered as physical- platform managed objects. After this type of managed object is unlocked, IBM Director interrogates the NVRAM of the service processor in the server, which could result in the automatic creation of a scalable system and a scalable partition that contain its corresponding scalable nodes. IBM Director 4.12 incorrectly identifies scalable systems that are created for xSeries 455 servers with the manageable scalable system icon. You cannot configure or manage these view-only scalable systems with Scalable Systems Manager 4.12. For more information about view-only scalable systems, see the information about scalable systems in the "Scalable Systems Manager 4.11 Installation and User's Guide." 1.5 About the "IBM Director Version 4.12" CD --------------------------------------------- The "IBM Director 4.12" CD contains the following installations: o Installing IBM Director Version 4.12 to systems running Windows o Updating IBM Director, Version 3.1, 3.1.1, 4.1, or 4.10.2 for Windows to Version 4.12 o Installing IBM Director Version 4.12 to systems running Linux o Updating IBM Director Server or IBM Director Console Version 4.1, 4.10.2, or 4.11 for Linux to Version 4.12 o Updating IBM Director Agent Version 3.1, 3.1.1, 4.1, 4.10.2, or 4.11 for Linux to Version 4.12 Notes: 1. (Windows only) You cannot use the "IBM Director 4.12" CD to update an existing IBM Director Version 4.11 installation. Instead, use the IBM Director for Windows patch. Download the patch from the IBM Systems Management: xSeries, BladeCenter and e325 page at: http://www.ibm.com/pc/ww/eserver/xseries/systems_management/ index.html 2. (Linux only) If you have a system on which IBM Director Agent and IBM Director Console are installed, you cannot use the "IBM Director 4.12" CD to update an existing IBM Director Version 4.11 installation. Instead, use the IBM Director for Linux patch. Download the patch from the IBM Systems Management: xSeries, BladeCenter and e325 page at: http://www.ibm.com/pc/ww/eserver/xseries/systems_management/ index.html 1.6 Packages contained in this update -------------------------------------- This update contains packages for IBM Director components running on Microsoft Windows or Linux. 1.6.1 Packages for Microsoft Windows ------------------------------------- The IBM Director, Version 4.12, Update provides packages for: o Installing IBM Director Version 4.12 to systems running Windows o Updating IBM Director, Version 3.1, 3.1.1, 4.1, 4.10.2, or 4.11, for Windows to Version 4.12 1.6.1.1 IBM Director for Windows --------------------------------- Use the following packages to install components of IBM Director, Version 4.12, for Windows: o IBM Director Agent for Windows Use this package (IBMDirectorAgentWindows4.12.zip) to: o Install IBM Director Agent, Version 4.12, for Windows o Upgrade an existing IBM Director Agent, Version 3.1, 3.1.1, 4.1, or 4.10.2 for Windows to Version 4.12. Note: You cannot use this package to update an existing IBM Director Agent, Version 4.11. Instead, use the IBM Director Agent for Windows patch. The following files are in this package: o IBMDirectorAgent4.12.exe o diragent_windows.xml o diragent.rsp o IBM Director Console for Windows Use this package (IBMDirectorConsoleWindows4.12.zip) to: o Install IBM Director Console, Version 4.12, for Windows o Upgrade an existing IBM Director Console, Version 3.1, 3.1.1, 4.10, or 4.10.2 for Windows to Version 4.12. Note: You cannot use this package to update an existing IBM Director Console, Version 4.11. Instead, use the IBM Director Console for Windows patch. The files in this package are: o IBMDirectorConsole4.12.exe o dircon.rsp o IBM Director Server for Windows Use this package (IBMDirectorServerWindows4.12.zip) to: o Install IBM Director Server, Version 4.12, for Windows o Upgrade an existing IBM Director Server, Version 3.1, 3.1.1, 4.10, or 4.10.2 for Windows to Version 4.12. Note: You cannot use this package to update an existing IBM Director Server, Version 4.11. Instead, use the IBM Director Server for Windows patch. The file in this package is IBMDirectorServer4.12.exe. o IBM Director Agent for Windows Server 2003 for 64-Bit Itanium- based systems Use this package (IBMDirectorAgent64Windows4.12.zip) to install IBM Director Agent, Version 4.12, for Windows Server 2003 for 64-Bit Itanium-based Systems. The following files are in this package: o IBMDirectorAgent4.12.exe o diragent.rsp 1.6.1.2 IBM Director for Windows patches ----------------------------------------- Use the following packages to update components of IBM Director, Version 4.11, for Windows to Version 4.12: o IBM Director Agent for Windows patch Use this package (IBMDirectorAgentWindowsPatch4.12.zip) to update IBM Director Agent, Version 4.11, for Windows to Version 4.12. The following files are in this package: o IBMDirectorAgentPatch4.12.exe o diragentpatch_windows.xml o IBMDirectorAgentPatch4.12.msp o IBM Director Console for Windows patch Use this package (IBMDirectorConsoleWindowsPatch4.12.zip) to update IBM Director Console, Version 4.11, for Windows to Version 4.12. The following files are in this package: o IBMDirectorConsolePatch4.12.exe o IBMDirectorConsolePatch4.12.msp o IBM Director Server for Windows patch Use this package (IBMDirectorServerWindowsPatch4.12.zip) to update IBM Director Server, Version 4.11, for Windows to Version 4.12. The following files are in this package: o IBMDirectorServerPatch4.12.exe o IBMDirectorServerPatch4.12.msp 1.6.1.3 Notes about Microsoft Installer software patch (MSP) files ------------------------------------------------------------- The IBM Director Version 4.12 Update provides Microsoft Installer software patch (MSP) files for each patch. The MSP files are provided for customers who prefer to use Microsoft Windows Installer and understand how to use MSP files. These files are not used in conjunction with the executable file. 1.6.2 Packages for Linux ------------------------- The IBM Director, Version 4.12, Update provides packages for: o Installing IBM Director Version 4.12 to systems running Linux o Updating IBM Director Server or IBM Director Console Version 4.1, 4.10.2, or 4.11 for Linux to Version 4.12 o Updating IBM Director Agent Version 3.1, 3.1.1, 4.1, 4.10.2, or 4.11 for Linux to Version 4.12 1.6.2.1 IBM Director for Linux ------------------------------- Use the following packages to install components of IBM Director, Version 4.12, for Linux: o IBM Director Agent for Linux Use this package (IBMDirectorAgentLinux4.12-1.tar.gz) to install IBM Director Agent, Version 4.12, for Linux. The following files are in this package: o IBMDirectorAgent4.12-1.sh o diragent_linux.xml o diragentpatch_linux.xml o dirinstall.alt o IBM Director Agent for Linux (64-Bit Itanium-based servers) Use this package (IBMDirectorAgent64Linux4.12-1.tar.gz) to install IBM Director Agent, Version 4.12, for Linux (64-Bit Itanium-based servers). The following files are in this package o IBMDirectorAgent4.12-1.sh o dirinstall.alt o IBM Director Console for Linux Use this package (IBMDirectorConsoleLinux4.12-1.tar.gz) to install IBM Director Console, Version 4.12, for Linux. The following files are in this package: o IBMDirectorConsole4.12-1.sh o dirinstall.alt o IBM Director Server for Linux Use this package (IBMDirectorServerLinux4.12-1.tar.gz) to install IBM Director Server, Version 4.12, for Linux. The following files are in this package: o IBMDirectorServer4.12-1.sh o dirinstall.alt 1.6.2.2 IBM Director for Linux patches --------------------------------------- For systems that have only one component of IBM Director installed (IBM Director Console, IBM Director Server, or IBM Director Agent), use the packages listed in Section 1.4.2.1, "IBM Director for Linux" to update the installed component from Version 3.1, 3.1.1, 4.1, 4.10.2, or 4.11 to Version 4.12. If you have a system on which IBM Director Agent and IBM Director Console are installed, you must use the following package: o IBM Director Agent and IBM Director Console for Linux patch Use this package (IBMDirectorAgentConsoleLinux4.12-1.tar.gz) to update IBM Director Agent, Version 4.1, 4.10.2, or 4.11, for Linux and IBM Director Console, Version 4.1, 4.10.2, or 4.11, for Linux to Version 4.12. You must use this package on any system on which both IBM Director Agent and IBM Director Console are installed. The following files are in this package: o IBMDirectorAgentConsolePatch4.12-1.sh. o dirpatch 2.0 CHANGE HISTORY ------------------- 27Feb2004 - Resolves APARs. See Section 4.0, "Issues resolved by this update." - Provides additional operating-system support. See Section 1.2, "Supported operating systems." - Provides a subset of IBM Director features and functionality for 64-bit operating systems, VMware ESX Server, and the IBM eServer BladeCenter JS20. 3.0 INSTALLATION ----------------- The packages provided in this update are self-extracting executable files. Select the applicable packages for your updates and execute each package to install the update. You can use the provided XML files with Director Update Assistant to install your update packages. For more information about Director Update Assistant, see the "IBM Director 4.11 Systems Management Guide." Note: If you are updating an installation of IBM Director Agent, Version 3.1 or 3.1.1, to Version 4.12 and that installation includes one or more of the IBM Director Server Plus Pack extensions, you must now install the IBM Director Server Plus Pack, Version 4.1, for those extensions. IBM Director Server Plus Pack includes the following extensions: Active PCI Manager, Capacity Manager, Rack Manager, Software Rejuvenation, and System Availability. If you are updating IBM Director Agent, Version 4.11 to Version 4.12 by using the 4.12 patch, the Server Plus Pack extensions previously installed using the IBM Director Server Plus Pack, Version 4.1, will not be effected. 3.1 Installation on Windows ---------------------------- Note: The MSP files are provided for customers who prefer to use Windows Installer and understand how to use MSP files. 3.1.1 Installing an IBM Director 4.12 update on Windows -------------------------------------------------------- Complete the following steps to install an IBM Director update on a system running Windows: 1. Select the applicable package for your update. 2. From a command prompt, type one of the following commands and press Enter: Note: These commands are case-sensitive. ----------------------------------------------------------- For an unattended installation: /v"/qb" ----------------------------------------------------------- For a silent installation: /S /v"/qn" ----------------------------------------------------------- where is the executable file provided in the update or patch you selected. 3.1.2 Installing IBM Director Agent, Version 4.12, on Windows -------------------------------------------------------------- Complete the following steps to install IBM Director Agent, Version 4.12, on a system running Windows: 1. If you do not want to customize the default installation options, go to step 4. 2. If you want to customize the default installation options, open the diragent.rsp file in an ASCII text editor. 3. Modify and save the diragent.rsp file. This file follows the Windows INI file format and is fully commented. 4. From the command prompt, type one of the following commands and press Enter: --------------------------------------------------------------- - For an unattended installation: IBMDirectorAgent4.12.exe -a unattended rsp="" --------------------------------------------------------------- - For a silent installation: IBMDirectorAgent4.12.exe -s -a silent rsp="" --------------------------------------------------------------- - where rsp is an optional parameter that you can use to specify a customized response file and is the path and name of the customized response file that you created in step 3. 3.1.3 Installing IBM Director Console, Version 4.12, on Windows ---------------------------------------------------------------- Complete the following steps to install IBM Director Console, Version 4.12, on a system running Windows: 1. If you do not want to customize the default installation options, go to step 4. 2. If you want to customize the default installation options, open the dircon.rsp file in an ASCII text editor. 3. Modify and save the dircon.rsp file. This file follows the Windows INI file format and is fully commented. 4. From the command prompt, type one of the following commands and press Enter.: --------------------------------------------------------------- - For an unattended installation: IBMDirectorConsole4.12.exe -a unattended rsp=" [-x | -r ] where: o is the executable file provided in the update or patch you selected. o -x is an optional parameter that you can use to extract the executable file contents without installing the patch or update and is the directory destination for the executable-file contents. o -r is an optional parameter that you can use to specify the name of a customized dirinstall file and is the name of the edited dirinstall.alt file. 3.2.2 Installing IBM Director Agent and IBM Director Console patch, Version 4.12, on Linux ------------------------------------------------------------- Complete the following steps to update a system running Linux and both IBM Director Agent and IBM Director Console: 1. If you do not want to customize the default installation options, go to step 4. 2. If you want to customize the default installation options, open the dirpatch file in an ASCII text editor. 3. Modify and save the file. This file is fully commented. 4. From a command prompt, type the following command and press Enter: [-x | -r ] where: o is the executable file provided in the update or patch you selected. o -x is an optional parameter that you can use to extract the executable file contents without installing the patch or update and is the directory destination for the executable-file contents. o -r is an optional parameter you can use to specify the name of a customized dirpatch file and is the name of the edited dirpatch file. 4.0 ISSUES RESOLVED BY THIS UPDATE ----------------------------------- The IBM Director Version 4.12 Update resolves the following Authorized Program Analysis Reports (APARs): o IC37353: IBM Director Server fails to maintain a Remote Control session for a consistent time span. o IC37505: (xSeries(R) server models 235 and 360 only) IBM Director does not receive power-supply alerts from the Hardware Status task or from the local system. o IC37536: IBM Director Agent Version 4.1 can cause the NetVista(TM) 8319-52U system fan to run more frequently and at a high speed resulting in a noticeably louder system. o IC37788: Software Distribution limits the length of commands to 254 characters. o IC37899: (Non-English systems only) Modified alert bindings do not take effect. o IC37995: The IBM Director Inventory task reports write-back disk caching as write-through. o IC38010: The BladeCenter Deployment wizard does not work with the QLogic Fibre Channel Switch Module firmware level 1.4.0.49 or earlier. o IC38120: If IBM Director Agent is restarted, an event action plan that monitors its Windows event log might not be triggered. o IC38212: Upgrading IBM Director Server in a domain environment in which IBM Director Server Version 3.1 or 3.1.1 was previously installed leads to a 1378 error during the upgrade installation. o IC38238: IBM Director Server fails when User Administration is started from IBM Director Console in a domain environment in which IBM Director Version 3.1 or 3.1.1 native users exist. o IC38267: IBM Director does not receive test alerts from the Advanced Systems Management Web Based Configuration Tool program. The Remote Supervisor Adapter and Remote Supervisor Adapter II come with the Advanced Systems Management Web Based Configuration Tool program. After using this program to configure the Remote Supervisor Adapter, you can use the program to send a test alert to another system that has either IBM Director Agent or IBM Director Server installed on it. However, a previous version of the program did not successfully send the test alerts. Make sure that you use the latest version of this program. o IC38268: When using Web-based Access is used to log in to IBM Director Agent on a managed system, IBM Director Web Server throws a "Servlet not found" exception. The exception prevents the login window from opening. The IBM Director Web Server log provides the following information: javax.servlet.ServletException - Exception processing JAR at resource path /WEB-INF/lib/cimsrv.jar, the Tomcat module cannot open up the jar file that contains the servlet classes. o IC38304: IBM Director Server might produce Java(R) exceptions when its services are shut down and started manually. o IC38313: Deleting a system from IBM Director Console occasionally causes the management console to freeze. o IC38435: IBM Director Console fails when processing or viewing custom inventory collection queries is initiated. o IC38654: IBM Director Agent sends old queued Windows event log events to IBM Director Server. o IC39079: IBM Director Server fails with an OutOfMemory error when monitoring certain SNMP devices. o IC39218: Depending on the level of BIOS firmware, hardware platforms that have a certain super I/O chip installed might fail with a Windows bluescreen after installing IBM Director Server or IBM Director Agent. The device driver lm78nt.sys might be implicated in the failure o IC39236: Management Processor Assistant produces a NULL pointer exception. o IC39292: IBM Director Agent installed on ThinkCentre(TM) computers causes false fan alerts. IBM Director does not support fan alerts on these systems; IBM Director, Version 4.12, does not generate these false alerts. o IC39403: The domain administrator or domain users cannot log into Web-based Access unless they are the default domain administrator. o IC39521: When upgrading IBM Director Server, Version 3.1.1, to Version 4.11, the management server fails to start due to SNMP MIB files compiled under IBM Director Version 3.1.1. o (Japanese only) The System Availability task, a part of the Server Plus Pack, is updated in this release of IBM Director. This update corrects the previously observed problem of inaccurate planned and unplanned outage information reported for managed systems. 5.0 KNOWN PROBLEMS AND WORKAROUNDS ----------------------------------- The IBM Director Version 4.12 Update has the following known problems and workarounds. 5.1 General ------------ o (Scalable Systems Manager only) You must uninstall Scalable Systems Manager Version 4.11 before updating to IBM Director Version 4.12. Otherwise, after the IBM Director Version 4.12 update, you will not be able to uninstall Scalable Systems Manager Version 4.11. For compatibility information between IBM Director and Scalable Systems Manager versions, see the readme file that accompanies the version of Scalable Systems Manager that you plan to use. o When an IBM Director Server installation that includes the Management Processor Assistant is stopped (net stop twgipc), 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 the IBM ASM Service Processor Device Driver Version 5.24b on servers that support this level. The following servers currently support this level: o IBM eServer xSeries 220 (8646) o IBM eServer xSeries 225 (8647) o IBM eServer xSeries 345 (8670) o IBM eServer xSeries 255 (8670) o IBM eServer xSeries 445 (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 In the Event Action Plan Builder, if you select to customize the log file name for the "Log to Textual Log File" action, you can specify the file name but not the path. The log file is created in the log directory on the server running IBM Director Server (the management server). o If you apply an Asset ID profile to a system that you have already applied a profile to, the task progress indicator shows a conflict error, but the new profile is applied. o To enable secure socket layers (SSL) on a system running IBM Director Server or IBM Director Console, edit the properties file; then, restart the system. For more information, see the "IBM Director 4.11 Installation and Configuration Guide." o (xSeries 445, machine type 8870 only) Events generated by an RXE-100 enclosure that is attached to an xSeries 445 server installed with a Remote Supervisor Adapter II might be displayed in IBM Director Console as associated with the xSeries 445 system managed object and not the RXE-100 enclosure managed object. Update the xSeries 445 server firmware to level 1.01 or later to display RXE-100 enclosure events with the RXE-100 enclosure managed object in IBM Director Console. o (xSeries 365 only) Use the Remote Supervisor Adapter II firmware Version 1.02 to correct currently known Remote Supervisor Adapter II problems on this server. 5.2 BladeCenter products and BladeCenter Assistant --------------------------------------------------- o In the BladeCenter Management subtask of BladeCenter Assistant, to view light path diagnostics for a blade server you must select the chassis as well as the blade server. o The Serial over LAN subtasks of BladeCenter Assistant do not have online help. For help information about these subtasks, see Section 6.0, "Serial over LAN support in the BladeCenter Assistant task." o After deploying a BladeCenter Deployment wizard profile, if you remove and replace the same blade server in the same slot of a BladeCenter chassis, IBM Director schedules a Remote Deployment Manager Scan task for the existing blade server. Cancel the pending task. o (IBM eServer BladeCenter JS20 only) You cannot set the keyboard /video/mouse (KVM) assignment for BladeCenter JS20. However, the KVM assignment task in BladeCenter Assistant lists the BladeCenter JS20 as a selection. Although the task appears to be completed without error, no KVM assignment is made, and no hardware failure occurs. o (IBM eServer BladeCenter HS40 only) In the BladeCenter Management subtask of BladeCenter Assistant, if you click "VRM" to view the voltage regulator module (VRM) information, two rows of information are reported. Ignore the second VRM row with a value of 0.0; that VRM does not exist. This error does not generate an event or cause any functional problems. 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 If you open a previously saved profile with the BladeCenter Deployment wizard, the "Configure the IP Settings" window might open differently than when you created and saved the profile. In the "Configure the IP Settings" window, if you select the check box to assign an IP address range to all three types of modules that might be present on the chassis, the wizard removes Management Modules, Network Switch Modules, and Storage Switch Modules tabs. The wizard shows the assigned IP address range for the three groups of modules. If you restart the BladeCenter Deployment wizard and select "Load existing profile" in the "Welcome to the BladeCenter Deployment wizard" window, the "Configure the IP Settings" window shows the individual tabs for Management Modules, Network Switch Modules, and Storage Switch Modules, and the "Use same IP pool for all management and switch modules" check box is cleared. The IP address range that you saved in the profile is displayed on each of the three tabs. o You can create a task to automatically rename chassis and blade objects in IBM Director using custom naming conventions. Complete the following steps to configure and use the auto-renaming feature: 1. To configure a naming convention template for either BladeCenter chassis managed objects or physical platform managed objects, using a text editor, open the applicable template file: --------------------------------------------------------- For BladeCenter chassis managed objects: director\data\BCChassisNamingConvention.properties --------------------------------------------------------- For physical platform managed objects: director\data\PhysicalPlatformNamingConvention.properties --------------------------------------------------------- 2. Edit and save the text file. The file contains the initial default templates and definitions of the variables that you can use. For example, one of the variables that you can use with physical platform objects is %CHASSIS_SLOT%. When you auto-rename a set of physical platform objects, %CHASSIS_SLOT% is replaced with the actual slot number of the object. 3. In IBM Director Console, select one or more chassis or physical platform objects. 4. Right-click the chassis or physical platform objects that you want to rename; then, click "Auto-rename". The objects are renamed. If you made an error in the syntax when editing the BCChassisNamingConvention.properties or PhysicalPlatformNamingConvention.properties file, the error is displayed in the new object name in IBM Director Console. To correct the error, edit the applicable properties file and apply the Auto-rename task to the object or objects again. If a value does not exist for a variable that you used in a template, the task shows a space for that variable in the new object name in IBM Director Console. To correct the error, edit the applicable properties file and apply the Auto-rename task to the object or objects again. 5.3 Web-based Access --------------------- o (Windows only) The default Guest user account on Windows systems cannot log on to a managed system using Web-based Access. Edit the local Guest account to add user privileges on the local system, or use any other account with user privileges on the local system to log on to a managed system using Web-based Access. o When Web-based Access is used from a system that does not have Java installed, a message is displayed that the Java Virtual Machine (JVM) is required to view a managed system. Install a JVM from Sun Microsystems. o (Internet Explorer on Windows Server 2003 only) Exporting data from a task in Web-based Access can fail when the Internet Explorer Enhanced Security Configuration is enabled. Turn off the Internet Explorer Enhanced Security Configuration to export data from a task. See the Microsoft documentation for further information about Internet Explorer Enhanced Security Configuration. o (Windows only) You can view and configure multiple network adapters in the same system using the Network Configuration panel of Web-based Access. Use the DNS Suffix Search Order page to set the DNS suffix search order for the system and not for individual network adapters. Editing the DNS Suffix Search Order values changes the DNS suffix search order for all network adapters in the system. o (Windows only) You can view and configure settings for multiple network adapters in a single system using the Network Configuration panel of Web-based Access. To avoid losing network configuration changes for multiple network adapters in the same system, click "Apply" after changing the configuration for a network adapter before switching to view or change the configuration for a second network adapter. If you change the IP address, you might lose the network connection after applying the changes, and you must reconnect to the system to continue using Web-based Access. 5.4 xSeries 450 and 455 servers -------------------------------- 5.4.1 General -------------- o (xSeries 455 only) False microprocessor (CPU) and ambient temperature alerts might be received if the server is discovered shortly after the Remote Supervisor Adapter is restarted. Also, incorrect thresholds for these temperatures might be displayed during the same interval. o (xSeries 450 and 455 servers only) IBM Director can monitor hardware status only through a physical platform managed object that represents the server. Hardware status is not available through the standard managed system object. For more information about managed systems and physical platform managed objects, see the "IBM Director 4.11 Systems Management Guide." o (Single-node xSeries 450 only) Rack Manager does not support hardware-status alerts. o (xSeries 450 only) IBM Director Server cannot discover or automatically manage the service processor in this system. You first must manually create a management processor object representing the service processor in IBM Director Console. For more information, see the "IBM Director 4.11 Installation and Configuration Guide." 5.4.2 Management Processor Assistant ------------------------------------- o (xSeries 450 only) Management Processor Assistant cannot retrieve and display the processor board and memory board vital product data (VPD). o (xSeries 450 only) Management Processor Assistant might not display the vital product data (VPD) of some dual inline memory modules (DIMMs). o (xSeries 450 and 455 servers only) In the Server management subtask of Management Processor Assistant, when you select "Server status" for these server models, the information that is displayed in the "BIOS Firmware VPD Image file" column contains invalid characters (small squares). 5.5 Operating-systems specific problems ---------------------------------------- 5.5.1 Windows -------------- o When uninstalling IBM Director Agent, if either of the following errors occur, see the "IBM Director 4.11 Installation and Configuration Guide," p. 185, Table 15, "Uninstallation problems" and complete the steps in the Suggested action column in the row that begins "Error message 1306 is displayed during an installation.": o A window displays the following error: "Apache.ede has generated errors and will be closed by Windows. You will need to restart the program." o Error message 1306 is displayed. o After you use the Network Configuration task to change the IP address and the computer name of the managed system, the IP address changes immediately, but the computer name changes only after the system is restarted. A pop-up window opens that states "You must shut down and restart your computer." If you click "Yes," the managed system does not restart, and the managed system is left with the new IP address and the old computer name. o If you cancel installing either IBM Director Server or IBM Director Agent during the installation, files that were created during the canceled installation can cause a subsequent installation to fail. If a subsequent installation reports errors during the installation process, restart the system; then, delete the installation folder before restarting the installation process. o If you install IBM Director Server onto a Windows system that is a member of a domain, the following conditions apply: o If the IBM Director Service account has local Administrator privileges, you cannot add global domain groups to the created DirAdmin and DirSuper groups. Windows accounts with only local Administrator privileges cannot access the contents of a global domain group. To avoid this, install IBM Director Server using an account with Domain Administrator privileges. o If the IBM Director Service account has Domain Administrator privileges, add the IBM Director Service account to the local Administrator group. o If you want to log in to IBM Director Server using a local user account, the local account must include the computer name in the user name. IBM Director Server prepends the Domain name to a user account that is not fully qualified. For example, the name of the local account "userid" must include the computer name "computer" and be of the form "computer\userid". If the local account named "userid" attempts to log in to IBM Director Server, IBM Director Server looks for the account "domain\userid," which might not exist. o (Windows XP only) Mass configuration for the Network Configuration task might not work for IBM Director Agent running on Windows XP. 5.5.2 Linux ------------ o At a local command prompt, typing the following command causes a stackpoint error: cfgdb You can configure the database by accessing the system either remotely using Telnet or locally by typing the following command at the local command prompt and using the interface: startx o Shortly after IBM Director Server or IBM Director Agent is started, it enters an error state, and the daemon.stderr file reports the following error: Exception in thread "main" Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Server or IBM Director Agent. o Exporting a software distribution package to Stored Procedure Builder (SPB) format sets the permissions to strict levels. To export the SPB file to a system running Windows, you must type the following command at the local command prompt: chmod 644 filename.spb o (eServer 325 only) Although the ServeRAID(TM) Linux package (RAIDLxAgent-4.11-1.i386.rpm) can be installed on this server, this model does not support the package. o (Netfinity(R) 5100 or xSeries 230, machine type 8658 only) You might experience slow file transfer when using the File Transfer, Remote Control, or Software Distribution task with managed systems running Linux. Complete the following steps to disable session support in IBM Director Agent on the managed system: 1. Edit the following file: /opt/IBM/director/classes/extensions/TCPIP.NETEXT 2. Uncomment the following line: net.session.classname=com.tivoli.twg.netipc.TWGTCPSocketImplFactory 3. Restart IBM Director Agent. 5.5.3 VMware ESX Server ------------------------ o ServeRAID Manager is not supported on VMware or any guest operating systems. Make sure you do not install the ServeRAID Manager, even by accident, in VMware installations or their guest operating systems. o Installing IBM Director Agent with the ServeRAID Manager component on a guest operating system is not supported. o (VMware ESX Server Version 2.0.1 and earlier) Guest operating systems might report incorrect information to IBM Director Agent when the Inventory task is used. Incorrect information might include the amount of memory or number of microprocessors (CPUs) that do not match their virtual configuration. This is a VMware limitation. o (16-way xSeries 445 with Remote Supervisor Adapter II-EXA option only) 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.5.4 Other operating systems ------------------------------ o (64-bit operating systems only) Interprocess Communication (IPC) data encryption is not available for IBM Director Agent. o (UNIX(R) only) Shortly after IBM Director Agent is started, it enters an error state and the daemon.stderr file reports the following error: Exception in thread "main" Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Server or IBM Director Agent. 6.0 SERIAL OVER LAN SUPPORT IN THE BLADECENTER ASSISTANT TASK -------------------------------------------------------------- You can use the BladeCenter Assistant tasks to view and configure Serial over LAN settings for a BladeCenter chassis and its blade servers. Support for Serial over LAN configuration is available for the following switches only: o IBM BladeCenter 4-Port Gb Ethernet Switch Module o Nortel Network Layer 2-7 GbE Switch Module for IBM eServer BladeCenter 6.1 Serial over LAN configuration ---------------------------------- Use the Serial over LAN configuration task to view and configure the following settings: o Serial over LAN enablement o The IP address range o Serial over LAN packet handling for all blade servers in the BladeCenter chassis The columns provide the following information: o Chassis Shows the name of the chassis containing the target blade server. o Enabled Select the Enabled check box to enable Serial over LAN for the chassis and any blade servers in the chassis. Clear the check box to disable Serial over LAN for the chassis and any blade servers in the chassis. o VLAN ID Shows the virtual LAN ID for the internal management network. o BSMP IP address Shows the first IP address range used for the blade servers in the chassis. Click the field and type an IP address. The range of the last byte of the IP address can be from 1 to 254 minus the number of blade servers in the chassis. For example, if there are 14 blade servers in the chassis, the last byte of the address must be less than or equal to 241. o Transport parameters Shows transport parameters for Serial over LAN packets. These values are: o Accumulate timeout Shows the time, in milliseconds, that the blade server management processor waits before transmitting a partial Serial over LAN packet. The default value is 5 milliseconds. The range is from 5 to 1275 milliseconds in increments of 5. Click the field and type a value in the range from 5 to 1275 to change the accumulated timeout value. Numbers that are no even multiples of 5 are rounded to the next lowest multiple of 5. o Send threshold Shows the size, in bytes, of a complete Serial over LAN packet. The default value is 250 bytes. The range is from 1 to 251 bytes. Click the field and type a value in the range of 1 to 251 to change the Serial over LAN packet size. o Retry count Shows the number of times a blade server resends a Serial over LAN packet without acknowledgment from the intended recipient before the server stops resending that Serial over LAN packet. The default value is 3 retries. The range is from 0 to 7 retries. Click the field and type a number from 0 to 7 to change the retry count. o Retry interval Shows the time, in milliseconds, after the blade server sends a Serial over LAN packet before it retries sending that packet. The default value is 200 milliseconds. The range is from 10 to 2550 milliseconds in increments of 10. Click the field and type a number between 10 and 2550 to change the retry interval. A number that is not an even multiple of 10 is rounded down to the next highest multiple of 10. o Escape sequence Shows the key sequence that you can use to exit the Serial over LAN console and return to the command-line interface console. The default key combination is Esc + (. Click the field and type a key combination to change the escape-key combination. o Reset sequence Shows the key sequence that you can use in the Serial over LAN console to reset the blade server. The default key sequence is Esc R Esc r Esc R. Click the field and type a key sequence to change the reset-key sequence. 6.2 Serial over LAN status --------------------------- Use the Serial over LAN Status task to view and configure settings for individual blade servers in a BladeCenter chassis. The columns provide the following information: o Chassis Shows the name of the chassis containing the target blade server. o Blade ID Shows the ID number of the blade server. o Enabled Select the Enabled check box to enable Serial over LAN for that blade server. If the Enabled check box on the "Serial over LAN configuration" pane is cleared, when you select the Enabled check box on the "Serial over LAN status" pane for a blade server, a warning message is displayed stating that Serial over LAN is disabled for the chassis and its blade servers. o Session Shows the status of the Serial over LAN session to the blade server. The values are: o Not Ready: The blade server does not have an open Serial over LAN session. o Ready: The blade server has an open but inactive Serial over LAN session. o Active: The blade server has an active Serial over LAN session that is redirecting serial data. o BSMP IP address Shows the blade server IP address. 7.0 CORRECTIONS TO THE DOCUMENTS --------------------------------- The following corrections are for the IBM Director Version 4.11 documents. 7.1 Installation and Configuration Guide (dir411_install.pdf) -------------------------------------------------------------- o (Chapter 14. Solving IBM Director problems, on page 187) In "Table 16. IBM Director Server problems," the suggested action in the following entry is incomplete. ____________________________________________________________ Symptom: (Linux only) Shortly after starting IBM Director Server, it enters an error state and the daemon.stderr file reports the following error: Exception in thread "main" Suggested action: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file. ____________________________________________________________ The complete suggested action is as follows: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Server. o (Chapter 14. Solving IBM Director problems, on page 191) In "Table 18. IBM Director Agent problems," the suggested action in the following entry is incomplete. ____________________________________________________________ Symptom: (UNIX and Linux only) Shortly after starting IBM Director Agent, it enters an error state and the daemon.stderr file reports the following error: Exception in thread "main" Suggested action: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file. ____________________________________________________________ The complete suggested action is: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Agent. 7.2 Systems Management Guide (dir411_sysmgt.pdf) ------------------------------------------------- o (Chapter 3. Working with managed systems using IBM Director Console tasks, on page 38) In "Table 1. Operating-system support for IBM Director Console tasks," the VMware ESX Server column should state: o ServeRAID Manager is not supported o System Availability is supported o (Chapter 7. Solving IBM Director problems, on page 225) In "Table 19. IBM Director Server problems," the suggested action in the following entry is incomplete. ____________________________________________________________ Symptom: (Linux only) Shortly after starting IBM Director Server, it enters an error state and the daemon.stderr file reports the following error: Exception in thread "main" Suggested action: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file. ____________________________________________________________ The complete suggested action is as follows: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Server. o (Chapter 7. Solving IBM Director problems, on page 229) In "Table 21. IBM Director Agent problems," the suggested action in the following entry is incomplete. ____________________________________________________________ Symptom: (UNIX and Linux only) Shortly after starting IBM Director Agent, it enters an error state and the daemon.stderr file reports the following error: Exception in thread "main" Suggested action: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file. ____________________________________________________________ The complete suggested action is as follows: Make sure that "localhost" is an alias for the loopback address 127.0.0.1 in the /etc/hosts file; then, restart IBM Director Agent. 8.0 SUPPORT WEB SITES ---------------------- The following Web pages provide resources for understanding, using, and troubleshooting IBM Director and systems-management tools: 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. o IBM Systems Management: xSeries, BladeCenter and e325 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. Click "IBM Director 4.1" for the latest information and documents. o IBM Director Agent page http://www.ibm.com/servers/eserver/xseries/systems_management/ sys_migration/ibmdiragent.html This Web page includes the compatibility documents for IBM Director 4.1. It lists all the supported operating systems and is updated every 6 to 8 weeks. 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 ServerProven(R) page http://www.ibm.com/pc/us/compat/index.html This Web page provides information about IBM hardware compatibility with IBM Director 4.1. 9.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. The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: BladeCenter DB2 the e-business logo eServer IBM iSeries Netfinity NetVista pSeries ServeRAID ServerProven ThinkCentre Universal Database xSeries Microsoft, Windows, Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel is a trademark of Intel Corporation in the United States, other countries, or both. 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. Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.