IBM Systems IBM Director Release Notes Version 5.20 Update 1 +---- Note ------------------------------------------------------------+ Before using this information and the product it supports, read the information in Appendix C, "Notices". +----------------------------------------------------------------------+ This edition applies to version 5.20 Update 1 of IBM Director for i5/OS (program number 5722-DR1), IBM Director for AIX and Linux on POWER (program number 5765-DR1), IBM Director for AIX (program number 44E7846), IBM Director for Linux on POWER (program number 44E7847), IBM Director for Linux on System z (program number 5648-DR1), and IBM Director on x86 (program numbers 5765-DIR, 44E7845, 44E7841, 42D8237, and 42D8238) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2007. All rights reserved. US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. About this release 1.1 New in version 5.20.1 1.2 Product fix history 1.2.1 Applying a SAN profile to a blade server that replaces a previously-attached blade server might fail. 1.3 Accessibility Chapter 2. Installation and upgrade information 2.1 Installation notes 2.2 Upgrade notes 2.3 Version compatibility of IBM Director version 5.20.1 components Chapter 3. Known limitations, problems, and workarounds 3.1 Limitations 3.1.1 When upgrading a SLES 9 agent, IBM Director Console shows the agent status as offline. 3.1.2 When installing IBM Director Console on a system running AIX 5.3, a superfluous warning message displays. 3.1.3 Update Manager cannot perform a compliance check for hard disk drives on Level-0 managed systems. 3.1.4 ServeRAID Manager does not work if IBM Director is installed on a different drive than the operating system 3.1.5 Hardware with support limitations 3.1.6 Accessibility 3.1.7 LSI is not supported for Red Hat Enterprise Linux version 5.0 3.1.8 Advanced Management Module 2.7 3.1.9 Requesting access to a Hardware Management Console does not succeed 3.1.10 Cannot unlock non-root user on a System x server running Red Hat Linux 64 bit 3.1.11 Event viewer for IBM Director ServeRAID Manager extension might not display all events 3.1.12 IBM Director for Linux on System z does not support SNMP access 3.1.13 BladeCenter Configuration Manager fails to configure SNMPv3 on the management module 3.1.14 Configure SNMP Agent window displays only SNMPv1 data 3.1.15 (Windows 2000 only) Processor usage by winmgmt.exe or wmicimsv.exe rises to 99%. 3.1.16 QLogic provider package and Adaptec ServeRAID Manager Level-1 or Level-2 package 3.1.17 Generating a report in SQL using Capacity Manager 3.1.18 Installing Web-based Access after installing IBM Director version 5.20 or later causes errors 3.1.19 The Hardware Status task might incorrectly report the failing drive number for IBM BladeCenter blade servers. 3.1.20 The setkvm command does not work when used with the -owner option. 3.1.21 Fibre Channel adapters connected to System z 3.1.22 IBM IntelliStation Z Pro, model 9228 does not support the processor temperature event when the processor gets hot. 3.1.23 The Event Action Plan Builder task is available only for users with task access permissions for all event action plans 3.1.24 Alert and inventory data not supported on some operating systems 3.1.25 Managed systems running slpd and Linux are incorrectly discovered as Level-1 managed systems after IBM Director Core Services is uninstalled. 3.1.26 The Inventory Query Browser displays IBM Director Agent as IBM Director Core Services. 3.1.27 Level-0 and Level-1 managed systems running Windows 2003, display incorrectly as Windows XP in IBM Director Console. 3.1.28 Inventory is not collected simultaneously for CECs and LPARs that are managed by the same HMC 3.1.29 Firmware inventory is not collected for Level-1 or Level-2 managed system running RHEL5 3.1.30 The Remote Session task is not supported for managed systems running Linux on POWER on IBM System p 570 with POWER6 processors 3.1.31 IC46865: (Windows systems only) Using the reboot option in the Custom Package Editor with custom packages in categories can cause Software Distribution jobs to fail. 3.1.32 The Software Distribution task does not support manually moving packages on file distribution servers 3.1.33 Limited error recovery when using Software Distribution 3.1.34 Deploying a package using Software Distribution fails 3.1.35 Performing a health check on a device that does not have drivers installed. 3.1.36 Cannot update firmware for Broadcom on Linux on POWER 3.1.37 Health Check unsupported on devices. 3.1.38 Displaying the details of an update in Update Manager 3.1.39 Displaying the details for an UpdateXpress System Pack in Update Manager 3.1.40 IBM Director does not support a dual HMC configuration consisting of HMC Version 7 and another HMC of a previous version. 3.1.41 Shutdown and Power Off task restarts Level-1 managed system running Linux on POWER 3.2 Problems 3.2.1 A Level-1 managed system running VMware 3.0.1 is discovered as a Level-0 managed system. 3.2.2 Duplicate events are sent after port offline for Brocade switch when the provider is configured to more than one 3.2.3 If Hyper-Threading is enabled, the Resource Monitors task displays two CPU Monitor resources even if only one CPU exists. 3.2.4 After successful update to an out-of-band IBM BladeCenter component, the firmware does not become active. 3.2.5 Complete IBM Director installation using screen readers that do not support Java applications 3.3 Workarounds 3.3.1 Some events are not generated and inventory is not correct for Level-1 managed systems running VMware 3.0 3.3.2 Viewing inventory tables for Level-1 and Level-2 managed systems running on AIX 3.3.3 Using keyboard functions to navigate with high contrast with large fonts enabled 3.3.4 Using keyboard functions to access IBM Director Help topics 3.3.5 Using screen reader or keyboard functions to access ServeRAID Manager Help topics 3.3.6 Using Update Manager to acquire partially superseded updates 3.3.7 Health check of the QLogic/McDATA 4Gb/2Gb Fibre Channel Switch Module Firmware version 5.5.0.22 3.3.8 Cannot run IBM Director command-line programs and utilities from a Windows terminal services session 3.3.9 Misleading error messages DNZZVS262E and DNZZSM336E when displaying Operating System Templates 3.3.10 Cannot update Linux distribution-certified device drivers 3.3.11 Using Konqueror to download update packages 3.3.12 Logging on or requesting access to a SUSE Linux Enterprise Server 10 system running IBM Director Agent 3.3.13 Timeout with FSP power management on SUSE Linux Enterprise Server 10 and AIX 3.3.14 Unable to perform Health Check on target system 3.3.15 Using Health Check on Adaptec 8i, 8k, and 8k-l controllers. 3.3.16 Managed system does not send events 3.3.17 The fwupdate command does not update Advanced Management Module firmware. Chapter 4. Documentation updates Appendix A. Related information Appendix B. Getting help and support B.1 Before you call B.2 Using the hardware documentation B.3 Getting information from the World Wide Web B.4 Software service and support Appendix C. Notices Appendix D. Trademarks Chapter 1. About this release This document contains the release notes for IBM(R) Director Version 5.20 Update 1. See the IBM Director Web site for possible updates to these release notes and other documents at www.ibm.com/systems/management/director/. 1.1 New in version 5.20.1 IBM Director 5.20.1 provides a number of new features and enhancements. There are additional supported systems for installation and management. In addition, some functions have changed in this version and some features have been discontinued. Support for new hardware For complete hardware support information, see the IBM Director Hardware and Software Support Guide. IBM Director Agent Version 5.20.1 can be installed on the following new IBM systems and products. * IBM System p(TM) 570 with POWER6(TM) processors * IBM BladeCenter(R) HT Chassis * IBM System Storage(TM) DS3400 IBM Director Version 5.20.1 provides support for the following additional switches: * Cisco 4 Gb 10 port Fibre Channel Switch Module, Part Number 39Y9284 * Cisco 4 Gb 20 port Fibre Channel Switch Module, Part Number 39Y9280 * Nortel 10 Gb Ethernet Switch Module, Part Number 39Y9267 * QLogic 10-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number 43W6724 * QLogic 20-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number 43W6725 * QLogic 4 Gb Intelligent Pass-thru Module for IBM BladeCenter, Part Number 43W6723 * QLogic InfiniBand Ethernet Bridge Module, Part Number 39Y9207 * QLogic InfiniBand Fibre Channel Bridge Module, Part Number 39Y9211 IBM Director Version 5.20.1 provides inventory awareness for the following additional devices: * Switch Legacy Interface Module (SLIM) * Concurrent keyboard/video/mouse (cKVM) feature card IBM Director support for new operating systems IBM Director version 5.20.1 can be installed on additional operating system versions as indicated in the following table. For complete operating system support information, see the IBM Director Hardware and Software Support Guide. Table 1. New operating systems supported by IBM Director Version 5.20 Update 1 +---------------------------------+----+----+----+----+ | Operating system | IB | IB | IB | IB | | | M | M | M | M | | | Di | Di | Di | Di | | | re | re | re | re | | | ct | ct | ct | ct | | | or | or | or | or | | | Co | Se | Ag | Co | | | ns | rv | en | re | | | ol | er | t | Se | | | e | | | rv | | | | | | ic | | | | | | es | +-----------------------------------------------------+ | New operating systems supported on System x(TM) | | systems and IBM and third-party x86-based systems: | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux(R) AS, | | | | X | | ES, and WS, version 5.0 | | | | | +---------------------------------+----+----+----+----+ | SUSE Linux Enterprise Server 9 | X | X | X | X | | for x86 (supports Service Pack | | | | | | 3, Update 1 and earlier) | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS, | | | X | | | version 4.0, for Intel(R) | | | | | | Itanium(R) (supports Update 5 | | | | | | and earlier) | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS and | X | X | X | X | | ES, version 4.0, for AMD64 and | | | | | | EM64T (supports Update 5 and | | | | | | earlier) | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux WS, | | | X | X | | version 4.0, for AMD64 and | | | | | | EM64T (supports Update 5 and | | | | | | earlier) | | | | | +---------------------------------+----+----+----+----+ | SUSE Linux Enterprise Server 9 | X | X | X | X | | for AMD64 and EM64T (supports | | | | | | Service Pack 3 Update 1 and | | | | | | earlier) | | | | | +---------------------------------+----+----+----+----+ | Microsoft(R) Virtual Server | X | X | X | X | | 2005 (Release 2 required; SP1 | | | | | | supported) | | | | | +-----------------------------------------------------+ | New operating systems supported on System i(TM) and | | System p products: | +---------------------------------+----+----+----+----+ | AIX 5L(TM), Version 5.2 | | | X | | | (supports TL06 or later) | | | | | | Note: Level-0 support includes | | | | | | only Discovery, Remote Session | | | | | | and a limited subset of the | | | | | | Software Distribution task. | | | | | +---------------------------------+----+----+----+----+ | AIX 5L, Version 5.3 (supports | X | X | X | | | TL03 or later) | | | | | | Note: Level-0 support includes | | | | | | only Discovery, Remote Session | | | | | | and a limited subset of the | | | | | | Software Distribution task. | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS, | X | X | X | X | | versions 4.3, 4.4, and 4.5, for | | | | | | IBM POWER(TM) | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS, | | | | X | | version 5.0, for IBM POWER | | | | | +---------------------------------+----+----+----+----+ | SUSE Linux Enterprise Server 9 | X | X | X | X | | for IBM POWER (Service Pack 3 | | | | | | required) | | | | | +-----------------------------------------------------+ | New operating systems supported on System z(TM) | | systems: | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS, | X | X | X | X | | version 4.0, for IBM System z | | | | | | (supports Update 5 and earlier) | | | | | +---------------------------------+----+----+----+----+ | Red Hat Enterprise Linux AS, | | | | X | | version 5.0, for IBM System z | | | | | +---------------------------------+----+----+----+----+ | SUSE Linux Enterprise Server 9 | X | X | X | X | | for IBM System z (supports | | | | | | Service Pack 3 and earlier) | | | | | +---------------------------------+----+----+----+----+ Updated database support IBM Director Server supports the following newer versions of external databases: * Apache Derby V10.2 (embedded with IBM Director Server 5.10 Update 1) * IBM DB2(R) Universal Database * version 9.1 with Fix Pack 2 * version 8.2 with Fix Pack 7 * version 8.1 with Fix Pack 14 For complete information about database support in IBM Director 5.20 Update 1, see the "Supported database applications" topic in the information center. In addition, new versions of the Oracle Java(TM) Database Connectivity (JDBC) drivers are supported. For additional information, see the "Preparing the Oracle Server database" topic in the information center. Additional changes in version 5.20.1 Added Rack Manager support for BladeCenter T chassis, machine type 8730 Added support for the Asset ID(TM) task on Level-2 managed systems running AIX(R) Additional operating system supported for IBM Director UIM for HP OpenView IBM Director UIM for HP OpenView now supports Level-2 managed systems running AIX. IBM Director-based events and information can be received by a management server running HP OpenView. Improvements to the Hardware Management Console extension for IBM Director Version 5.20.1 of Hardware Management Console extension for IBM Director is updated to start the web based HMC version 7 console alternatively to the earlier version of the HMC console. Depending on the version of the Hardware Management Console managed object, the Hardware Management Console task in IBM Director will start either the web based HMC version 7 console or the earlier version of the HMC console. Documentation updates The online help files for IBM Director Version 5.20 Update 1 are not changed from Version 5.20. For IBM Director Version 5.20 Update 1, documentation updates are available in the IBM Director Information Center at publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/diricinfo_5.20/fqm0_main.html. The IBM Director Information Center includes updates to both the printed and online documentation. 1.2 Product fix history This section describes the limitations and problems resolved by IBM Director 5.20.1. Authorized Program Analysis Reports The following Authorized Program Analysis Reports (APARs) were resolved in IBM Director 5.20.1: IC50899 IBM Director Server incorrectly generates IBM Director Agent Offline events and reports status of managed systems as offline when the systems are online and IBM Director Agent is running. IC51267 IBM Director Server shuts down unexpectedly when attempting to access Remote Supervisor Adapters with older firmware. IC51643 IBM Director Agent generates hardware status events for a NIC that is disabled in the operating system. IC51662 The CIM listener locks up after a request to shut down. IC51841 The CIM listener locks up after a request to shut down. IC51715 Requesting access to a BladeCenter chassis might generate a JVM exception and shut down IBM Director Server. IC51804 The cimserver service has high processor usage after a Remote Supervisor Adapter II is disconnected. IC52008 An unattended upgrade installation of IBM Director Agent 5.20 requires user input when performed on a managed system that has IBM Director Web Based Access installed. IC52141 Installing IBM Director 5.20 on a system that has an LSI 1064 RAID controller running Linux will cause the LSI RAID array to immediately go to the degraded state. IC52157 When running IBM Director Agent on a managed system that has an LSI 1064 RAID controller, if the LSI RAID array goes to a degraded state no event is sent to the system events log. IC52461 SNMP events are not correlated with IBM Native Managed Objects. IC52463 IBM Director Server trap mapping using variable filters specified via slot index does not work. IC52568 Performing inventory on a managed system that has both IBM Director Agent 5.20 installed and an LSI 1064 RAID controller running Linux will cause the LSI RAID array to immediately go to the degraded state. IC52606 When the Nmap utility is used with the TCP connect scan option (nmap -sT), the scan causes the Secure Sockets Layer (SSL) listener to close, resulting in a loss of SSL communications between IBM Director Server and IBM Director Console. This occurs only for management servers running Linux. The default SYN scan option for Nmap does not cause this problem. For IBM Director Version 5.20, restart IBM Director Server when this problem occurs. 1.2.1 Applying a SAN profile to a blade server that replaces a previously-attached blade server might fail. When replacing a blade server that is attached to a host, the existing blade server must be detached from the host before removing the blade server and replacing it with a new blade server. If the old blade server is not first detached, applying a storage area network (SAN) configuration profile to the new blade server will fail. To detach the old blade server, issue the following command before removing it: dircli chnshost -D -n host_name where host_name is the name of the attached host. Then, you can remove the old blade server, insert a replacement blade server, and apply the SAN configuration profile. 1.3 Accessibility IBM Director has been validated for accessibility and meets the U.S. Section 508 requirements and W3C Web Content Accessibility Guidelines (WCAG) when installed on the following operating systems: * Linux * Windows(R) 2000 * Windows Server 2003 * Windows XP * z/VM(R) When IBM Director is installed on AIX, i5/OS(R), and Linux on POWER, it is compliant with accessibility requirements when you use the remote command line. For Linux on POWER, the graphical user interface was also tested for accessibility and meets accessibility requirements. However, neither platform includes supporting assistive technology tools. As a result, tests with such tools were not performed on these platforms. Related information "Accessibility features for IBM Director" in the IBM Director Information Center Chapter 2. Installation and upgrade information This section provides information about installing and upgrading to IBM Director Version 5.20 Update 1. For detailed information about installing and upgrading, see the IBM Director Information Center. From the IBM Director Information Center you also can access the IBM Director Planning, Installation and Configuration Guide and the IBM Director Express Planning, Installation and Configuration Guide. These documents also are available on the IBM Director on x86 CD. 2.1 Installation notes After preparing your system, use the applicable installation procedure for the operating system on which you plan to install IBM Director. General notes * IBM Director components that are upgraded to Version 5.20 Update 1 will have the version number 5.20.1. * IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. * If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. * If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers running i5/OS, IBM Director Server uses the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. * On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. * On management servers running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. * To use IBM Director Console to access IBM Director Server on a system that is running i5/OS, IBM Director Console must be installed on a separate non-i5/OS server. * Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component. Upgrading Hardware Management Console extension (Windows only) If the Hardware Management Console extension is installed for 5.10 Update 3 or earlier, you must uninstall the Hardware Management Console extension before updating to IBM Director version 5.20.1. The IBM Director on x86, Version 5.20 Update 1 CD does not include installation packages for Red Hat Enterprise Linux version 5, SUSE Linux Enterprise Server 9, or VMware ESX 2.5.x For Version 5.20 Update 1, you can download the installation packages for IBM Director components on these operating systems for System x platforms from the IBM Director Web site at www.ibm.com/systems/management/director/downloads.html OpenSSH not included on the IBM Director on x86, Version 5.20 Update 1 CD The IBM Director on x86, Version 5.20 Update 1 CD does not include OpenSSH for Windows. If a Level-1 managed system does not have a Secure Shell (SSH) package installed, IBM Director Server cannot provide secure command shell to the managed system. To have a secure command shell, using, for example, IBM Director Remote Session, you can install OpenSSH on the managed system. You can download OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ . To deploy a Level-1 IBM Director Core Services update that includes the OpenSSH package to a Windows managed system, start IBM Update Assistant and create a software package using the dir5.20.1_coreservices-toc_windows.xml file that is located on the IBM Director on x86, Version 5.20 Update 1 CD. When prompted, import the OpenSSH download into the Update Assistant package. Use Software Distribution to distribute the package to the managed system. Installing an IBM Director component on a System z platform running Red Hat Enterprise Linux AS, version 5.0, for IBM System z To install an IBM Director component on a System z platform that is running Red Hat Enterprise Linux AS, version 5.0, you must use the Red Hat Enterprise Linux AS, version 4.0 RPM files. Installing an IBM Director component on a System z platform running SUSE Linux Enterprise Server 10 To install an IBM Director component on a System z platform that is running SUSE Linux Enterprise Server 10, you must use the SUSE Linux Enterprise Server 9 RPM files. Accesibility note (Windows only) When installing an IBM Director component using a screen reader, the screen reader might not process the IBM Director Setup Window correctly. Also, if high contrast colors are enabled, the Setup Window might not display these colors appropriately. To start the installation wizard when these accessibility features are enabled, perform the following steps: 1. Close the IBM Director Setup Window. 2. Open Windows Explorer. 3. Navigate to the director/dir_component/windows/i386 directory on the IBM Director on x86, V5.20 CD, where dir_component is the component that you want to install. 4. Run the ibmsetup.exe program. 5. Continue with the installation. Hardware requirements for IBM Director Server IBM Director Software Distribution might require a large amount of virtual memory. There must be enough swap space on the management server to contain another Java Virtual Machine, which might require up to 800 MB. Management server * (Windows only) When you install IBM Director Server, the InstallShield wizard automatically installs IBM Director Console and IBM Director Agent. During the installation process, you can install the optional IBM Director features. You also can change security settings. Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Server installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Server without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart regardless of whether the IBM Director Server installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must change to the directory containing the ibmsetup.exe file and run the installation program using the following command: ibmsetup.exe admin. This command updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so. * (Linux only) z/VM Center extension components must be installed in the IBM Director default installation directory (/opt/ibm/director/). For Linux systems on which you want to run z/VM Center components, do not change the installation prefix by RPM relocation when installing the IBM Director component or the z/VM Center component. * In order for Update Manager to receive updates, IBM Director Server must be able to access the following Internet addresses: * 207.25.252.197 on port 443 (eccgw01.boulder.ibm.com) * 129.42.160.51 on port 443 (eccgw02.rochester.ibm.com) Configure your firewall to allow IBM Director Server to access to these addresses and ports in order to receive updates. Managed systems * Installing ServeRAID(TM) Manager Agent on a Level-2 managed systems: You must install the ServeRAID Manager Level-1 Agent on a managed system before installing the ServeRAID Manager Level-2 Agent. * (Windows only) If a Level-1 managed system does not have an Secure Shell (SSH) package installed, IBM Director Server cannot provide secure communication to the managed system. To secure communication, you can install OpenSSH on the managed system. You can download OpenSSH from www.sourceforge.net/projects/sshwindows/. * IBM Director 5.20.1 support for Intel Itanium systems is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20.1 for Intel Itanium systems. IBM Director Agent for Intel Itanium systems is available as a Web-download only. Download the dir5.10.3_agent_windows64.zip or dir5.10.3_agent_linux64.zip file as needed, from the IBM Director Web site at www.ibm.com/systems/management/director/downloads.html. Installing vendor-supplied switch hardware abstraction plug-ins Management support for some switches is provided through the installation of vendor-supplied switch hardware abstraction plug-ins. Use the following steps to obtain and install these plug-ins. 1. Navigate to the IBM Director Partners in management Web page at www.ibm.com/systems/management/director/partners/. 2. Under Partner extensions, click the name of the vendor for the switch you want to manage. The link will take you to a page on the vendor's Web site. 3. Follow the instructions provided by the vendor for downloading and installing the extension on the management server. 4. Optional: If you use a remote management console, you will need to copy the .jar file for the extension from the management server to the management console. a. Shut down IBM Director Console on the remote management console. b. Identify the .jar file in the install_root\classes directory on the management server that was installed with the vendor-supplied switch hardware abstraction plug-in, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Typically, this .jar file will use a variant of the vendor name, such as cisco4.jar. c. Copy the .jar file from the management server to the install_root\classes directory on the management console, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). d. Start IBM Director Console on the remote management console. Related information "Installing IBM Director using the Express installation" in the IBM Director Information Center "Installing IBM Director using the Standard installation" in the IBM Director Information Center 2.2 Upgrade notes The following general rules apply to the version compatibility of IBM Director components: * You cannot upgrade IBM Director components on Linux on System z directly from a version prior to 5.20 to version 5.20.1. You can either uninstall your current version and then install 5.20.1, or you can first upgrade to version 5.20 and then update to version 5.20.1. * IBM Director Server and IBM Director Console must be at the same version level, even when installed on different systems. * Components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be at the same version level. * The version of IBM Director Server must always be greater than or equal to the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. * If you upgrade to a new version of IBM Director Server, you must also upgrade all instances of IBM Director Console to the same version. * If you upgrade to a new version of IBM Director Agent or IBM Director Core Services on any managed system, you must upgrade both IBM Director Server and all instances of IBM Director Console to a version that is the same or later than the agent version. * You can upgrade to a new version of IBM Director Server without necessarily upgrading all instances of IBM Director Agent or IBM Director Core Services. You can upgrade to IBM Director Version 5.20 Update 1 from the following versions of IBM Director: * 4.10 * 4.10.2 * 4.11 * 4.12 * 4.20 * 4.20.2 * 4.21 * 4.22 * 5.10 * 5.10 Update 1 * 5.10 Update 2 * 5.10 Update 3 * 5.20 Important: Some operating systems or hardware that were supported for older versions of IBM Director are not supported in later versions. To successfully upgrade, your existing IBM Director component must be running on an operating system and hardware configuration that is supported by the version of IBM Director to which you are upgrading. Related information "Upgrading and updating IBM Director" in the IBM Director Information Center 2.3 Version compatibility of IBM Director version 5.20.1 components Some IBM Director 5.20.1 components can work with IBM Director components from previous versions of the software. As with previous versions of IBM Director, the following rules apply to the version compatibility of IBM Director version 5.20.1 components: * The versions of IBM Director Server and IBM Director Console must be the same, even when they are installed on different systems. * Versions of components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be the same. * The version of IBM Director Server must always be the same or later than the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. See Table 2 for a complete listing of compatible IBM Director component versions for each IBM Director Version 5.20.1 component. Table 2. Compatibility of IBM Director Version 5.20.1 components with other component versions +-------------+-------------+-------------+-------------+-------------+ | IBM | Compatible | Compatible | Compatible | Compatible | | Director | versions of | versions of | versions of | versions of | | Version | IBM | IBM | IBM | IBM | | 5.20.1 | Director | Director | Director | Director | | | Server | Console | Agent | Core | | | | | | Services | +-------------+-------------+-------------+-------------+-------------+ | IBM | N/A | 5.20.1 | 5.20.1, | 5.20.1, | | Director | | | 5.20, | 5.20, | | Server | | | 5.10.3, | 5.10.3, | | 5.20.1 | | | 5.10.2, | 5.10.2, | | | | | 5.10.1, | 5.10.1, | | | | | 5.10, 4.22, | 5.10 | | | | | 4.21, | | | | | | 4.20.2, | | | | | | 4.20, 4.12, | | | | | | 4.11, | | | | | | 4.10.2, | | | | | | 4.10 | | +-------------+-------------+-------------+-------------+-------------+ | IBM | 5.20.1 | N/A | 5.20.1, | 5.20.1, | | Director | | | 5.20, | 5.20, | | Console | | | 5.10.3, | 5.10.3, | | 5.20.1 | | | 5.10.2, | 5.10.2, | | | | | 5.10.1, | 5.10.1, | | | | | 5.10, 4.22, | 5.10 | | | | | 4.21, | | | | | | 4.20.2, | | | | | | 4.20, 4.12, | | | | | | 4.11, | | | | | | 4.10.2, | | | | | | 4.10 | | +-------------+-------------+-------------+-------------+-------------+ | IBM | 5.20.1 and | 5.20.1 and | N/A | N/A | | Director | later | later | | | | Agent | | | | | | 5.20.1 | | | | | +-------------+-------------+-------------+-------------+-------------+ | IBM | 5.20.1 and | 5.20.1 and | N/A | N/A | | Director | later | later | | | | Core | | | | | | Services | | | | | | 5.20.1 | | | | | +-------------+-------------+-------------+-------------+-------------+ IBM Director version 5.20.1 is compatible with the following versions of IBM Director extensions: Table 3. Compatibility of IBM Director extensions with IBM Director version 5.20.1 +----------------------------------+----------------------------------+ | Extension | Compatible versions | +----------------------------------+----------------------------------+ | Capacity Manager | 5.20 | +----------------------------------+----------------------------------+ | Electronic Service Agent(TM) | System x DE V5.0, System x DE | | | Linux V5.0 | +----------------------------------+----------------------------------+ | External Application Launch | 5.20 | | Wizard | | +----------------------------------+----------------------------------+ | Hardware Management Console | 5.20.1 | +----------------------------------+----------------------------------+ | PowerExecutive(TM) | 2.00.1, 2.00 | +----------------------------------+----------------------------------+ | Remote Deployment Manager | 4.30.1, 4.30 | +----------------------------------+----------------------------------+ | ServeRAID Manager | 5.20 | +----------------------------------+----------------------------------+ | IBM Server Storage Provisioning | 5.20.1 | | Tool | | +----------------------------------+----------------------------------+ | Software Distribution Premium | 5.20 | | Edition | | +----------------------------------+----------------------------------+ | System Availability | 5.20 | +----------------------------------+----------------------------------+ | IBM Virtualization Manager | 1.1 | +----------------------------------+----------------------------------+ | z/VM Center | 5.20.1 | +----------------------------------+----------------------------------+ Chapter 3. Known limitations, problems, and workarounds This section provides information about known limitations, problems, and workarounds when using IBM Director Version 5.20 Update 1. 3.1 Limitations IBM DirectorVersion 5.20 Update 1 has the limitations described in this section. 3.1.1 When upgrading a SLES 9 agent, IBM Director Console shows the agent status as offline. When upgrading the agent on a managed system running SLES 9 from IBM Director version 5.10.2 or earlier to IBM Director version 5.20 or later, the IBM Director Console shows the agent status as offline. Delete the agent and then rediscover the agent. 3.1.2 When installing IBM Director Console on a system running AIX 5.3, a superfluous warning message displays. When installing IBM Director Console on a system running AIX 5.3, the following superfluous warning message is displayed and can be safely ignored. WARNING: File /opt/ibm/director/classes/com/tivioli/twg/softwaredist/TWGFtp.properties is also owned by fileset IBM.Director.Agent.IBMDirA 3.1.3 Update Manager cannot perform a compliance check for hard disk drives on Level-0 managed systems. The following appears in the compliance report when you attempt to perform a compliance check for hard disk drives on Level-0 managed systems, even if hard disk drives are present and inventory has been run. Systems requiring update: This update does not apply to any of the targeted systems. Ensure the update is appropriate for the systems and inventory has been run 3.1.4 ServeRAID Manager does not work if IBM Director is installed on a different drive than the operating system This problem affects IBM Director Server, IBM Director Agent, and IBM Director Core Services installations on Windows with the ServeRAID Manager extension installed. Affected versions of the ServeRAID Manager extension include V8.15 through V8.40. The ServeRAID Manager extension for IBM Director is always installed on the same logical or physical drive as IBM Director. If this drive is not the same as the drive on which the operating system is installed, the ServeRAID Manager task will not be started. Instead, attempting to start the ServeRAID Manager task will generate the following error message: Task Not Supported If you will be installing the ServeRAID Manager extension on a Windows operating system, you must install IBM Director Server, IBM Director Agent, or IBM Director Core Services on the same drive as the operating system. 3.1.5 Hardware with support limitations The degree of support that IBM Director Agent provides on IBM systems and products can vary. Support Most IBM products are supported. All features and functions that are available in the current version of IBM Director are supported on these products, if applicable. For example, if a system does not have a ServeRAID option installed, then ServeRAID Manager is not supported on that system. Support with limitation Occasionally, IBM Director supports an IBM product, but one or more features or functions might not work as intended. Non-IBM-Hardware-Level support For some systems and products, IBM Director provides basic system-management capabilities. IBM Director Agent provides this level of support on non-IBM Intel-based or AMD-based systems with SMBIOS 2.1 or later that meet the Intel Wired for Management (WfM) 2.0 specification. These functions and features include Asset ID, CIM Browser, Discovery, File Transfer, Inventory (Software), Power Management, Process Management, Remote Control, Remote Session, Resource Monitors, SNMP events for SNMP Agent, SNMP Browser, and Software Distribution. IBM Director Agent provides support with limitations of Non-IBM-Hardware-Level support for the following products. IBM BladeCenter products HS21 blade server, machine type 8853 (Only Non-IBM-Hardware-Level support is provided.) Netfinity(R) servers Netfinity 7000 (Only Non-IBM-Hardware-Level support is provided.) IBM SurePOS(TM) point-of-sale systems * SurePOS 4694 (Only Non-IBM-Hardware-Level support is provided.) * SurePOS 500 / 600 - 4840 (Only Non-IBM-Hardware-Level support is provided.) * SurePOS 700 - 4800 (Only Non-IBM-Hardware-Level support is provided.) IBM System x3nnn servers x3105, machine types 4347 and 4348 (Environmental-sensor monitoring and hardware events are not supported.) IBM System Storage Network Attached Storage products IBM NAS 100 - 5190 NAS Model R12 (Alert Standard Format {ASF} is not supported.) IBM System x(R) servers * 100 (Only Non-IBM-Hardware-Level support is provided.) * 205 (ASF and fan monitoring are not supported.) * 206, 206m (ASF is not supported on AMD64 or EM64T operating systems.) * 225 (ASF and fan monitoring are not supported.) * 232 (Alert on LAN is not supported.) * 305 (ASF is not supported.) * 306, 306m (ASF is not supported on AMD64 or EM64T operating systems.) * 342 (Alert on LAN is not supported.) * 343 (Only Non-IBM-Hardware-Level support is provided.) 3.1.6 Accessibility Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products successfully. Some of these accessibility features, however, have limitations or might require additional steps. Using keyboard accessibility during a Remote session (Linux only) The sticky keys feature cannot be used to highlight text within the IBM Director Remote Control and Remote Session tasks. Using sticky keys to access Help in the ServeRAID Manager task (Linux only) If you use the sticky keys keyboard accessibility feature to select the Help menu option in the ServeRAID Manager task (Alt -> H) in IBM Director, the Help menu will not open. To open the Help menu, press Alt -> Alt -> H. Using sticky keys to open IBM Director menus Windows To open the IBM Director menus, press Alt three times. Alternatively, you can press F10. Linux To open the IBM Director menus, press Alt once. Note: When you use the Alt sticky keys feature in IBM Director, the menu opens. This does not interfere with sticky keys combinations for Linux. To access a sticky keys combination for Linux that uses Alt as the first key, press Alt followed by the next key in the sequence. GNOME desktop IBM Director 5.20 Update 1 and earlier does not support the GNOME desktop. Using K Desktop Environment key combinations If you are using the K Desktop Environment (KDE), the following KDE key combinations conflict with key combinations that are used in IBM Director: * Ctrl+Tab * Ctrl+Shift+Tab To resolve the conflict, change the default keyboard combinations in the KDE desktop settings. Displaying the Group Contents pane when using a screen reader When you use a screen reader with IBM Director Console, make sure that the Tree view is selected in the Group Contents pane. Otherwise, all objects in the pane might not be identified. Using keyboard functions to navigate in a tree If you use the keyboard features to navigate in a window that contains objects in a tree, the keyboard focus might not be immediately visible when you tab to the tree. To see the keyboard focus when you tab to the tree, press the space bar or downward arrow. Windows MouseKeys feature does not perform as expected on the Help index alphabet links. When using the MouseKeys to access the letters in the Help index, the focus does not move to the correct location in the Help file initially. The focus moves to the line of letters at the top of the help window. To move to the location of the letter in the help file, press the letter again. Changes to font size do not display If you change the font size in the Accessibility Preferences window, you might have to close and reopen any task windows that are displayed for the changes to take effect. Note: (Update Manager task only) To force the font-size changes to take effect in Update Manager, open and close the Update Manager task three times; or, modify an Update Manager Profile, save the changes, and then close and reopen the task. (Systems running Red Hat Enterprise Linux with the GNOME or KDE desktop environment) A new window does not automatically become the active window If you perform an action that causes a new window to display, the new window might not (by default) become the active window, even though it is the top-most window. This limitation is caused by a known problem in the Java Runtime Environment. Workarounds include clicking on the new window to make it active, or using the keyboard shortcut (Alt+Tab) to go to the new window. Cannot use the keyboard to resize columns in IBM Director You cannot use the keyboard to resize or reorder columns in IBM Director. 3.1.7 LSI is not supported for Red Hat Enterprise Linux version 5.0 For 5.20 Update 1 only, LSI controllers are not supported on Level-1 managed systems running Red Hat Enterprise Linux version 5.0. 3.1.8 Advanced Management Module 2.7 IBM Director Version 5.20 Update 1 provides limited support for the IBM BladeCenter Advanced Management Module 2.7. This support includes forced password changes and discovery of systems that are using a configurable network port. 3.1.9 Requesting access to a Hardware Management Console does not succeed Requesting access to a Hardware Management Console with a version earlier than V6R1.1 can return the following error message: The action on the target system failed. This limitation is resolved in Hardware Management Console V6R1.1. 3.1.10 Cannot unlock non-root user on a System x server running Red Hat Linux 64 bit (System x server running Red Hat Linux [64 bit] only) If you use a non-root user to log into IBM Director Console and you make seven log-in attempts using the incorrect password, the user account that you use is locked. When you use the faillog or the pam_tally command to view the log-in status, the incorrect information is displayed and the user account cannot be unlocked. 3.1.11 Event viewer for IBM Director ServeRAID Manager extension might not display all events The Event viewer for IBM Director ServeRAID Manager extension might not display all events. Some of the events that do not display consistently are synchronization, copy-back, migration, and rebuilding events. 3.1.12 IBM Director for Linux on System z does not support SNMP access SNMP access is not supported by IBM Director Agent or IBM Director Core Services for Linux on System z platforms. On these managed systems, IBM Director-specific information cannot be obtained through a Net-SNMP master agent. 3.1.13 BladeCenter Configuration Manager fails to configure SNMPv3 on the management module If you change a user's password or enable SNMPv3 authentication for that user, the management module may restart unexpectedly, causing a BladeCenter Configuration Manager profile to fail. This limitation occurs when the user's SNMPv3 trap IP address is set to the default of 0.0.0.0. To prevent the BladeCenter Configuration Manager profile from failing, change the SNMPv3 trap IP address before changing the user's password or enabling SNMPv3 for that user. 3.1.14 Configure SNMP Agent window displays only SNMPv1 data (Linux only) IBM Director Version 5.20 Update 1 supports SNMP versions 1, 2, and 3, however, when viewing or configuring managed system by using the Configure SNMP Agent window, only SNMPv1 trap information is displayed. To configure a trap destination to use SNMP versions 2 or 3 for a managed system, use the SNMP tool provided by your operating system. 3.1.15 (Windows 2000 only) Processor usage by winmgmt.exe or wmicimsv.exe rises to 99%. The processor usage by winmgmt.exe or wmicimsv.exe might rise to 99% on systems that are running Windows 2000 and have IBM Director Server, IBM Director Agent, or IBM Director Core Services installed. This limitation might cause the system to become unresponsive, which will affect IBM Director activity such as inventory and events. If the system becomes unresponsive or processor usage for winmgmt.exe or wmicimsv.exe rises to 99%, restart the system. 3.1.16 QLogic provider package and Adaptec ServeRAID Manager Level-1 or Level-2 package If you install the QLogic provider package or the Adaptec ServeRAID Manager Level-1 or Level-2 package for IBM Director Version 5.20 Update 1 to a system that is currently managed using IBM Director, subscriptions to CIM indications will occur on the next presence check. By default, presence check occurs every 15 minutes. The Fibre Channel and RAID-related CIM indications will not display in the IBM Director Event log or the hardware status until the next presence check. You can use IBM Director Console to manually run a presence check on these systems by right-clicking a managed system, and selecting Presence Check. 3.1.17 Generating a report in SQL using Capacity Manager The ability to generate a report in Structured Query Language (SQL) format is available on the Windows platform only. Only Microsoft SQL Server 2000 and Microsoft SQL Server Desktop Engine 2000 (MSDE 2000) are supported. The database to which Capacity Manager exports information is independent of the database used by IBM Director. As a result, information is not shared between the two. Make sure the Open DataBase Connectivity (ODBC) default database uses the Capacity Manager database, which is named cmdb. 3.1.18 Installing Web-based Access after installing IBM Director version 5.20 or later causes errors Do not install Web-based Access 5.10 on a system that has IBM Director 5.20 installed. Web-based Access will install without error, but will overwrite required 5.20 installation files, which will cause errors when you run IBM Director. 3.1.19 The Hardware Status task might incorrectly report the failing drive number for IBM BladeCenter blade servers. This limitation occurs because the LSI Logic Serial Attached SCSI (SAS) 1064 controller installed on some hardware does not report the slot information on IBM BladeCenter blade servers. Verify the failing drive number using the LSI BIOS utility, which will report the actual degraded or missing drive number. 3.1.20 The setkvm command does not work when used with the -owner option. When you attempt to set the owner of a keyboard, video, and mouse (KVM) to a System p blade server using the Management Processor Command-Line Interface command setkvm -owner n (where n is the number of the blade server to assume ownership), the command indicates a successful completion, but the KVM ownership is not changed. 3.1.21 Fibre Channel adapters connected to System z When multiple I/O ports on a System z platform are defined for a single Fibre Channel adapter, the inventory in IBM Director for the system displays only the active adapter. 3.1.22 IBM IntelliStation Z Pro, model 9228 does not support the processor temperature event when the processor gets hot. The processor environmental control (temperature) is controlled by the processor. This is a limitation of the IBM IntelliStation(R) Z Pro hardware. Do not design event action plans that rely on the MPA > Environmental > Temperature event for the IBM IntelliStation Z Pro. 3.1.23 The Event Action Plan Builder task is available only for users with task access permissions for all event action plans If a user is granted task access to the Event Action Plan Builder task but does not have task access for all event action plans, the user will not be able to access the Event Action Plan Builder task. If a user has permissions for only some (but not all) event action plans, the user can only use the Event Action Plan Wizard to modify those event action plans. 3.1.24 Alert and inventory data not supported on some operating systems IBM Director Agent running on VMware 2.5.x, VMware 3.0.x, and Red Hat Enterprise Linux version 3 does not support alerts from QLogic FibreChannel 4GB host bus adapters or firmware levels for these adapters in the default inventory collection, Firmware table. IBM Director Agent running on VMware 2.5.x, VMware 3.0.x, SUSE Linux Enterprise Server 10, and Red Hat Enterprise Linux version 3 does not support alerts for physical hard drive, logical drive, RAID controller, or RAID array on the following systems: * HS21 blade server * LS21 blade server * LS41 blade server * HS20 blade server, machine type 7981 * x3250 server * x3200 server Also, these systems do not support physical drive and controller firmware levels in the default inventory collection, Firmware table. 3.1.25 Managed systems running slpd and Linux are incorrectly discovered as Level-1 managed systems after IBM Director Core Services is uninstalled. When IBM Director Core Services is uninstalled, managed systems that use the SLP daemon (slpd) are not unregistered. These managed systems include many servers running SUSE Linux Enterprise Server; in SUSE Linux Enterprise Server, slpd runs in the default configuration. Managed systems that use slpd are incorrectly discovered as Level-1 managed systems until the SLP registration expires, which typically occurs about 18 hours after IBM Director Core Services is uninstalled. 3.1.26 The Inventory Query Browser displays IBM Director Agent as IBM Director Core Services. When Level 2: IBM Director Agent is installed, the Inventory Query Browser displays IBM Director Core Services. 3.1.27 Level-0 and Level-1 managed systems running Windows 2003, display incorrectly as Windows XP in IBM Director Console. Level-0 and Level-1 managed systems that are running Windows 2003, display as Windows XP in IBM Director Console. To display the correct operating system information, request access to the managed system. After you have successfully accessed the managed system, the correct operating system information is displayed. 3.1.28 Inventory is not collected simultaneously for CECs and LPARs that are managed by the same HMC If you select multiple CECs and LPARs that are managed by the same Hardware Management Console (HMC) and then attempt to collect inventory for the selected CECs and LPARs, inventory collection might not succeed for one or more of the CECs or LPARs. This problem affects HMC versions 5 and 6. This problem occurs only if at least one CEC and at least one LPAR that are managed by the same HMC are both selected for inventory collection. To avoid this problem, collect inventory for CECs only, and then collect inventory for LPARs only. 3.1.29 Firmware inventory is not collected for Level-1 or Level-2 managed system running RHEL5 A limitation in the lsmcode command prevents information about firmware inventory from being obtained for RedHat Linux 5 managed systems running IBM Director Agent or IBM Director Core Services for Linux on POWER. Without this information, Update Manager cannot update the firmware. 3.1.30 The Remote Session task is not supported for managed systems running Linux on POWER on IBM System p 570 with POWER6 processors The Remote Session task is not supported for managed systems running Linux on POWER on IBM System p 570 with POWER6 processors. 3.1.31 IC46865: (Windows systems only) Using the reboot option in the Custom Package Editor with custom packages in categories can cause Software Distribution jobs to fail. If you create a custom package for Windows using the Software Distribution task and you want to make that package part of a category, do not use the Restart Computer option in the Custom Package Editor. This option will cause the Software Distribution job to fail. Instead, use the reboot option in the Category Editor. 3.1.32 The Software Distribution task does not support manually moving packages on file distribution servers If you manually add or remove software distribution packages on a file distribution server, the changes might not be reflected in the File Distribution Servers Manager window. Additionally, the packages that were manually added or removed might not be available to the Software Distribution task. Always use the File Distribution Servers Manager window to make changes to software distribution packages on file distribution servers. 3.1.33 Limited error recovery when using Software Distribution When using the Software Distribution task, the following procedures might not display errors to indicate that the package that you are distributing failed to install: * If the file system does not have enough space, the package cannot be copied to a Level-0 managed system, and the Software Distribution task fails without displaying an error message. * (Linux and AIX systems only) If you distribute IBM Director Agent to a target system that is missing a prerequisite RPM file, the Software Distribution task might complete without actually installing the IBM Director Agent. 3.1.34 Deploying a package using Software Distribution fails When software distribution deploys a package to Level-0 or Level-1 managed systems, the package content is copied to the managed system and run remotely. After the execution of the package, the return code is retrieved and logged in the debug_rpd.log file, which is located in the IBM Director Server log directory on the management server. A return code of 0 indicates a successful deployment. Some packages might return a code of 0 even though the execution failed. If the deployment is completed without error, but the deployed application is not available on the target system, open the debug_rpd.log file for additional information. 3.1.35 Performing a health check on a device that does not have drivers installed. IBM Director cannot be used to perform a health check for a device on a managed system if there are no drivers already installed for the device. To enable deployment and health checking of these devices, you must install drivers for the devices. 3.1.36 Cannot update firmware for Broadcom on Linux on POWER A limitation in the lsmcode command prevents Update Manager from obtaining information about the Broadcom firmware on Linux on POWER. Without this information, the firmware cannot be updated. 3.1.37 Health Check unsupported on devices. Update Manager supports deployment for the specified software on the following devices, however, it does not support health checking: * Intel Chipset device driver * MSI Chipset device driver * OSA device driver Update Manager does not support deployment or health checking for the specified software on the following devices: * AMD PowerNow device driver * Broadcom for IBM BladeCenter JS21 * cKVM firmware * Emulex 4Gb expansion card * Emulex/QLogic Fibre Channel/iSCSI device driver * Emulex/QLogic Host Bus Adapter firmware * IBM 10 GB Ethernet device driver * IBM 10 GB Ethernet network interface card * Intel IDE MegaRAID device driver * LSI MegaRAID firmware * LSI SAS 2-Port daughter card * Netxen 10Gb Ethernet daughter card * QLogic 4Gb Fibre Channel daughter card * QLogic SLIM daughter cards * Remote Supervisor Adapter II video BIOS * SAS Switch and its associated non-RAID Storage Controllers 3.1.38 Displaying the details of an update in Update Manager When you attempt to view the details of an update in Update Manager, the Details menu might not respond initially. The Update Manager task contains tables that display updates. If you right-click an update and select Details, in some instances, the first time the menu option is selected, the details panel will not display Select the Details option a second time to display the Details panel. 3.1.39 Displaying the details for an UpdateXpress System Pack in Update Manager When you display the details for an UpdateXpress System Pack in Update Manager, all information might not be available. An Update Manager profile can be created to download an UpdateXpress System Pack. After the System Pack is downloaded, you can select Bundle Details from the Open Profile window to open a panel that displays the details about the UpdateXpress System Pack. The Applicable Operating Systems field on this panel displays numbers rather than the operating systems. Also the XML descriptor field associated with the UpdateXpress System Pack incorrectly displays as a empty field. 3.1.40 IBM Director does not support a dual HMC configuration consisting of HMC Version 7 and another HMC of a previous version. The configuration of two hardware management consoles managing the same hardware is supported only when either both HMCs are HMC Version 7 or both HMCs are Version 5 or Version 6. If one HMC is Version 7 and the other HMC is Version 5 or Version 6, some management functions might not be available in IBM Director. When upgrading from HMC Version 5 or Version 6 to HMC Version 7, use the following recommendations: * If possible, first upgrade hardware that is managed by a single HMC. * When upgrading dual HMC configurations, upgrade both HMCs at the same time. * If both HMCs in a dual configuration cannot be upgraded at the same time, then split the HMCs to upgrade the HMC that can be upgraded first. After the second HMC is upgraded to Version 7, you can recombine them. 3.1.41 Shutdown and Power Off task restarts Level-1 managed system running Linux on POWER On managed systems running IBM Director Core Services for Linux on POWER, the Power Management task "Shutdown and Power Off" restarts the managed system instead of shutting down and powering off the managed system. 3.2 Problems IBM Director Version 5.20 Update 1 has the following known problems: 3.2.1 A Level-1 managed system running VMware 3.0.1 is discovered as a Level-0 managed system. After installing IBM Director Core Services on a managed system running VMware 3.0.1, the managed system appears in IBM Director Console as an agentless managed system. This problem could occur in one of two circumstances: * The managed system is rebooted after installing IBM Director Core Services but before adding and unlocking the managed system in IBM Director Console. * OpenPegasus is restarted on the managed system after installing IBM Director Core Services but before adding and unlocking the managed system in IBM Director Console. This problem occurs because the version of OpenPegasus that is included with VMware 3.0.1 has a built-in SLP service agent. When OpenPegasus starts, it takes control of port 427, removing the registration for the IBM Director Core Services service agent. To resolve this problem after the managed system is rebooted or after OpenPegasus is restarted, issue the following command to start tier1slpinst again: /etc/init.d/tier1slpinst restart 3.2.2 Duplicate events are sent after port offline for Brocade switch when the provider is configured to more than one When the SMI-S provider for a Brocade switch is configured to more than one, if a port goes offline then duplicate events are sent to all switches attached to the storage device. This happens because the SMI-S provider has knowledge of the end storage device, but when a connection is broken the provider does not know which switch it was attached to. 3.2.3 If Hyper-Threading is enabled, the Resource Monitors task displays two CPU Monitor resources even if only one CPU exists. On some managed Windows systems with Hyper-Threading capability, resource attributes for two microprocessors (or CPUs) are displayed when you run the Resource Monitors task on a managed system and view the CPU Monitors resources, despite the fact that the system contains only one microprocessor. This problem occurs if Hyper-Threading is enabled for the microprocessor. The Resource Monitor task draws data from the operating system, and the operating system interprets a single Hyper-Threaded microprocessor as two logical microprocessors. 3.2.4 After successful update to an out-of-band IBM BladeCenter component, the firmware does not become active. When an update to an out-of-band IBM BladeCenter component successfully completes, the firmware does not become active until the applicable hardware component is restarted or reset. IBM Director does not support restarting or resetting these BladeCenter components. To activate the firmware, log in to the management module by using the Web interface or a Telnet interface and restart or reset the component as needed. Note: When you update the firmware for a management module, the management module is automatically reset after its two firmware files are downloaded. 3.2.5 Complete IBM Director installation using screen readers that do not support Java applications When using a non-Java screen reader during IBM Director installation, the reader will probably not be able to read the content of the Database Configuration window, because it is a Java-based interface. To finish the installation with a non-Java screen reader: 1. Using your screen reader, find the window whose title bar reads "IBM Director database configuration", and press Enter. 2. The screen reader indicates that the next window is the Apache configuration window. Press Enter again. 3. Finish the installation as directed. 4. After installation is complete and you obtain a Java screen reader, you can access and change the database configuration settings by entering the following command in the command prompt window: cfgdb 3.3 Workarounds This section addresses problems you might encounter when using IBM Director Version 5.20 Update 1. For troubleshooting information about additional issues not listed here, see the Troubleshooting section of the IBM Director Information Center at publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/diricinfo_5.20/fqm0_r_tbs_solving_problems.html. 3.3.1 Some events are not generated and inventory is not correct for Level-1 managed systems running VMware 3.0 After installing IBM Director Core Services (versions 5.20 and 5.20 Update 1) on a Level-1 managed system running VMware 3.0, sensor events and Predictive Failure Analysis(R) events are not generated, and inventory is not correct for the managed system. After installing IBM Director Core Services, shut down and restart the managed system. Inventory and events should work as expected after the managed system is restarted. 3.3.2 Viewing inventory tables for Level-1 and Level-2 managed systems running on AIX Some inventory tables for Level-1 and Level-2 managed systems running on AIX might be empty even though the information should be available. To fix this problem, run the following two commands in the given order to stop and restart cimserver: /opt/ibm/icc/cimom/bin/stopcim /opt/ibm/icc/cimom/bin/startcim 3.3.3 Using keyboard functions to navigate with high contrast with large fonts enabled (Windows only) When you install IBM Director by using the keyboard functions to navigate and High contrast color and Large or Extra Large font settings are enabled, you cannot move the keyboard focus to the scroll bars in the installation windows. Also, some components and text do not display in the windows that are displayed during installation. To access the scroll bars using the keyboard, use the Windows MouseKeys feature. You can use the MouseKeys feature to move the mouse pointer by using the arrow keys on the keyboard. 3.3.4 Using keyboard functions to access IBM Director Help topics The keyboard shortcut that is used to select a Help link in IBM Director Console does not work. If you use keyboard functions to access IBM Director Help topics, use the help topics in the IBM Director Information Center. The help topics are fully-accessible from the IBM Director Information Center. 3.3.5 Using screen reader or keyboard functions to access ServeRAID Manager Help topics If you use a screen reader or keyboard functions to access ServeRAID Manager Help topics, use the help topics in the IBM Director Information Center. The help topics are fully-accessible from the IBM Director Information Center. 3.3.6 Using Update Manager to acquire partially superseded updates When you create individual update profiles in Update Manager, you can select one or more systems as criteria for obtaining updates to include in the profile. If multiple systems are selected in the same profile, a download request might not return all of the matching updates that are available from IBM. Updates that are partially superseded might not be returned. To ensure that all updates are returned, specify only one system as criteria for each profile. All updates that match the profile criteria are returned on a download request. 3.3.7 Health check of the QLogic/McDATA 4Gb/2Gb Fibre Channel Switch Module Firmware version 5.5.0.22 If you perform a health check of the QLogic/McDATA 4Gb/2Gb Fibre Channel Switch Module Firmware version 5.5.0.22 against either the mcdt_fw_bcsw_5.5.1.10_anyos_noarch update or the mcdt_bcsw_5.5.1.10_anyos_noarch update, the health report will falsely indicate that this switch is compliant even though it is not. This issue is caused because the version specified by the switch provider is incorrect. To deploy this update to the switch using IBM Director Software Distribution, you must disable Smart Updates. 3.3.8 Cannot run IBM Director command-line programs and utilities from a Windows terminal services session Some command-line programs and utilities, including dircmd, dircli, genevent, raswatch, and MPCLI, cannot be run from a Windows terminal services session. To run these utilities from a Windows terminal services session, use the mstsc /console command to start the Windows terminal services session. 3.3.9 Misleading error messages DNZZVS262E and DNZZSM336E when displaying Operating System Templates If your access credentials for a z/VM system are incorrect and you attempt to display Operating System Templates in the Virtual Server Deployment window, a misleading combination of error messages, DNZZVS262E and DNZZSM336E, is displayed. To resolve the error, open the z/VM profile for this z/VM system and make sure that it contains the correct user ID and password. This error might occur, for example, after the password has expired or has been changed on the z/VM system. 3.3.10 Cannot update Linux distribution-certified device drivers By default, IBM Director cannot deploy IBM device-driver updates for Linux to systems that are using the Linux distribution-certified device drivers. To enable deployment and health checking of these systems, you must modify the XML file that is included with the IBM update. To modify the XML file and enable updates to the Linux device drivers on a managed system, complete the following steps: 1. Downloaded the update that you want to use and add it to a profile. 2. Double click on the profile to view the profile details. 3. Make note of the ID for the update. 4. Edit the XML file for the update: a. Navigate to the install_root\data\UpdateLib\ directory, where install_root is the root directory of your IBM Director installation. b. Open the id_name.xml file, where id_name is the ID for the update. c. For the UnattendedInstallCommandLine entry, change the --force-if-overridden value to --force. d. Save the XML file with the changes. 5. From IBM Director Console, right-click on the profile and select Create a Software Distribution Package. After the package is imported, you can send it to the necessary endpoints and it will install the IBM device driver. Note: Any modifications that you make in the data\UpdateLib directory will be overwritten if new updates are downloaded for that profile. The updates that have been imported into software distribution will not be overwritten. 3.3.11 Using Konqueror to download update packages (Linux only) If you use Konqueror to download updates, make sure to configure the Konqueror download directory to the fully qualified path to your updates directory, otherwise the download might fail. You also can copy and paste the URL to the update into a different browser such as Firefox. 3.3.12 Logging on or requesting access to a SUSE Linux Enterprise Server 10 system running IBM Director Agent IBM Director uses the Pluggable Authentication Module (PAM) architecture to authenticate user credentials. This architecture is used by IBM Director Server when IBM Director Console is used to log on to the management server. It also is used by IBM Director Agent during request access. The PAM configuration for IBM Director is defined in the /etc/pam.d/ibmdir configuration file. This configuration requires that the following two PAM modules be installed as part of the operating system: * pam_unix.so * pam_tally.so Typically, these modules are available as part of the operating system. On SUSE Linux Enterprise Server 10, however, these modules might not be installed by default. If these modules are not installed, users are unable to log on to IBM Director Server using IBM Director Console. In addition, users are unable to request access to a managed system. If log-on or request access is failing and pam_unix.so or pam_tally.so are not present in the /lib/security directory, install the pam-modules-32bit-10.2.2 RPM on the system. After installation, the required modules should be available. 3.3.13 Timeout with FSP power management on SUSE Linux Enterprise Server 10 and AIX The FSPProxyServerExt package on SUSE Linux Enterprise Server 10 and AIX performs power management of your Integrated Virtualization Manager (IVM) managed Flexible Service Processor (FSP). If you are using this package, you must update the csm.hc_utils package to the PTF2 version or later. Version 1.6.2.x of the csm.hc_utils package includes PTF2. If this package is not updated, repeated timeouts might occur during the performance of power management functions on the FSP from the SUSE Linux Enterprise Server 10 system. The csm.hc_utils update package can be downloaded from http://www14.software.ibm.com/webapp/set2/sas/f/csm/download/home.html. 3.3.14 Unable to perform Health Check on target system If an update in the Update Manager task cannot perform a health check, you can still import the contents of a profile containing that update into Software Distribution by right-clicking the profile and selecting Create a Software Distribution Topic. Then, you can send that update to a target system by using Software Distribution. 3.3.15 Using Health Check on Adaptec 8i, 8k, and 8k-l controllers. To use Update Manager to perform a health check on Adaptec 8i, 8k, and 8k-l controllers, the controllers must first be added to the inventory. For Level-1 and Level-2 managed systems, you must install the appropriate Adaptec provider and restart the endpoint. Note: The restart is required for all managed systems that you update. For Level-0 managed systems, you must install a filter driver before the adapter can be queried or updated. To install the filter driver, manually send a driver or firmware update package for the controller to the managed system and then restart that system. 3.3.16 Managed system does not send events This problem only affects managed systems running VMware ESX 3.0. Problem Managed systems running VMware ESX 3.0 do not send in-band events to IBM Director Server. Investigation The OpenIPMI drivers are not enabled by the VMware ESX 3.0 operating system, causing these managed systems not to send in-band events to IBM Director. Use the following procedure to enable the OpenIPMI drivers on VMware ESX 3.0. This problem is fixed by ESX Server 3.0.0 patch ESX-8005537. Obtain download and installation instructions for this patch from the following Web site: kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=8005537. 3.3.17 The fwupdate command does not update Advanced Management Module firmware. The format of the Advanced Management Module firmware update file has changed. The CNETCMUS.pkt file is not a true PKT format file, but instead is a tar file containing two PKT format files (CNETBRUS.pkt and CNETMNUS.pkt). Extract these two files from the CNETCMUS.pkt file and then use the fwupdate command to update the Advanced Management Module firmware. Chapter 4. Documentation updates The online help files for IBM Director Version 5.20 Update 1 are not changed from Version 5.20. For IBM Director Version 5.20 Update 1, documentation updates are available in the IBM Director Information Center at publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/diricinfo_5.20/fqm0_main.html. The IBM Director Information Center includes updates to both the printed and online documentation. Users of translated information should consider these facts: * The IBM Director Information Center updates for IBM Director Version 5.20 Update 1 are in English only and have not been translated into other languages. * The English documentation has been approved by technical reviewers and is updated more frequently than the translated documentation; when discrepancies occur between translated documentation and the English documentation, you should rely on the English documentation. This section provides information about corrections to the IBM Director help files and IBM Director Information Center topics. Appendix A. Related information Besides this documentation, there is additional information related to IBM Director. IBM Director resources on the World Wide Web The following Web pages provide resources for understanding, using, and troubleshooting IBM Director and other system-management tools. IBM Director information center publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/diricinfo_5.20/fqm0_main.html This information center is updated periodically. It contains the most current documentation on a wide range of topics. IBM Director extension information centers These information centers are updated periodically. They contain the most current documentation on a wide range of topics. * Capacity Manager: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/capman_5.20/fqn0_main.html * External Application Launch Wizard: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/ealwiz_5.20/frj0_main.html * Hardware Management Console (HMC): publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/hmc_5.20/frk0_main.html * ServeRAID Manager: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/serveraid_5.20/fqy0_main.html * Software Distribution Premium Edition: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/swdistpe_5.20/frl0_main.html * System Availability: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/sysavail_5.20/fqq0_main.html * z/VM Center: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/zvmcenter_5.20/zvm0_main.html IBM Director Web site on ibm.com(R) www.ibm.com/systems/management/director/ The IBM Director Web site on ibm.com has links to downloads and documentation for all currently supported versions of IBM Director. Information on this site includes: * Downloads and documentation for the following IBM Director releases: * IBM Director 5.20 Update 1 (5.20.1) * IBM Director 5.20 * IBM Director 5.10 Update 3 (5.10.3) * IBM Director 5.10 Update 2 (5.10.2) * IBM Director 5.10 Update 1 (5.10.1) * IBM Director 5.10 * IBM Director 4.22 * IBM Director 4.22 Upward Integration Modules (UIMs) * IBM Director 4.21 * IBM Director 4.20 * IBM Director Hardware and Software Support Guide document, which lists supported IBM systems and all supported operating systems. It is updated every 6 to 8 weeks. * Printable documentation for IBM Director is available in Portable Document Format (PDF) in several languages. IBM Director Software Developers Kit information center publib.boulder.ibm.com/infocenter/dirinfo/toolkit/index.jsp The IBM Director Software Developers Kit (SDK) information center provides information about the IBM Director SDK, which is a set of tools and documentation to help extend the capabilities of IBM Director by using the APIs and CLIs, creating tasks, and launching tools from the IBM Director user interface. IBM Systems Software information center www.ibm.com/servers/library/infocenter/ This Web page provides information about IBM Director, External Application Launch Wizard, IBM Virtualization Manager, and other topics. IBM ServerProven(R) page www.ibm.com/servers/eserver/serverproven/compat/us/ This Web page provides information about the hardware compatibility of IBM System x, BladeCenter, and IntelliStation with IBM Director. IBM Servers www.ibm.com/servers/ This Web page on ibm.com links to information, downloads, and IBM Director extensions, such as Remote Deployment Manager, Capacity Manager, Systems Availability and Software Distribution (Premium Edition), for the following IBM products: * IBM BladeCenter * IBM System i * IBM System p * IBM System x * IBM System z IBM forums www.ibm.com/developerworks/forums/dw_esforums.jsp This Web page on ibm.com links to several forums, available as Web pages or using Rich Site Summary (RSS) feeds, in which users can discuss technology issues relating to IBM servers. Three of these forums are of particular interest to IBM Director users: System x IBM Director forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759&cat=53 A forum for discussing any IBM Director topics. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. System x Server forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=740&cat=53 A forum for discussing System x server topics, including questions related to drivers, firmware, operating systems, clustering, and storage. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. IBM Director SDK forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=849&cat=53 A forum for discussing the use of the IBM Director Software Developers Kit (SDK) to extend the functionality of IBM Director to meet your specific needs. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. IBM Redbooks(R) publications www.ibm.com/redbooks/ You can download the following documents from the IBM Redbooks Web page. You can also search this Web page for documents that focus on specific IBM hardware; such documents often contain systems-management material. Notes: 1. Be sure to note the date of publication and to determine the level of IBM Director software to which the Redbooks publication refers. 2. You need Adobe(R) Acrobat(R) Reader to view or print these PDF files. You can download a copy from the Adobe Web site at www.adobe.com/products/acrobat/readstep.html. * Creating a Report of the Tables in the IBM Director 4.1 Database (TIPS0185) * Implementing IBM Director 5.20 (SG24-6188) * Integrating IBM Director with Enterprise Management Solutions (SG24-5388) * Managing IBM TotalStorage(R) NAS with IBM Director (SG24-6830) * Managing Linux Guests Using IBM Director and z/VM Center (SG24-6830) * Monitoring Redundant Uninterruptible Power Supplies Using IBM Director (REDP-3827) * Using the IBM Director cimsubscribe Utility (REDP-4123-00) * Virtualization on the IBM System x3950 Server (SG24-7190-00) * iSeries(TM) Systems Management Handbook (REDP-4070) Remote Supervisor Adapter The following Web pages provide resources for understanding and using Remote Supervisor Adapters with IBM Director: Remote Supervisor Adapter overview www.ibm.com/support/docview.wss?uid=psg1MIGR-4UKSML This Web page contains links to the Remote Supervisor Adapter User's Guide and the Remote Supervisor Adapter Installation Guide. Remote Supervisor Adapter II overview www.ibm.com/support/docview.wss?uid=psg1MIGR-50116 This Web page contains information about the Remote Supervisor Adapter II. Other documents For planning purposes, the Planning and Installation Guide - IBM BladeCenter (Type 8677) might be of interest. Appendix B. Getting help and support If you need help, service, or technical assistance or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. This section contains information about where to go for additional information about IBM and IBM products, and whom to call for service, if it is necessary. B.1 Before you call Before you call, make sure that you have taken these steps to try to solve the problem yourself: * Check all cables to make sure that they are connected. * Check the power switches to make sure that the system is turned on. * Use the troubleshooting information in your system documentation and the diagnostic tools that are included with your system. You can find information about diagnostic tools for BladeCenter and System x systems in the Problem Determination Service Guide on the IBM System x Documentation CD. You can find information about diagnostic tools for IntelliStation in the IntelliStation Hardware Maintenance Manual at the IBM Support Web site. * Go to the IBM Support Web site at www.ibm.com/support/us to check for technical information, hints, tips, and new device drivers or to submit a request for information. You can solve many problems without outside assistance by following the troubleshooting procedures that IBM provides in the online help or in the publications that are provided with your system and software. The information that is included with your system also describes the diagnostic tests that you can perform. Most BladeCenter, System x, and IntelliStation systems, operating systems, and programs includes information that contains troubleshooting procedures and explanations of error messages and error codes. If you suspect a software problem, see the information for the operating system or program. B.2 Using the hardware documentation Information about your IBM BladeCenter, System x, or IntelliStation system and any preinstalled software is available in the documentation that is included with your system. That documentation includes printed books, online books, readme files, and help files. See the troubleshooting information in your system documentation for instructions for using the diagnostic programs. The troubleshooting information or the diagnostic programs might tell you that you need additional or updated device drivers or other software. IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. To access these pages, go to www.ibm.com/support/us and follow the instructions. Also, you can order publications through the IBM Publications Ordering System at www.ibm.com/planetwide/. B.3 Getting information from the World Wide Web On the World Wide Web, the IBM Web site has up-to-date information about IBM BladeCenter, System i, System p, System x, System z, and IntelliStation products, services, and support. Use the following Web addresses for the applicable product information. +-----------------+---------------------------------------------------+ | IBM product | Web address | +-----------------+---------------------------------------------------+ | BladeCenter | www.ibm.com/servers/eserver/support/bladecenter/ | | products | | +-----------------+---------------------------------------------------+ | IntelliStation | www.ibm.com/servers/intellistation/pro/already.ht | | workstations | ml | +-----------------+---------------------------------------------------+ | System i | www.ibm.com/servers/eserver/support/iseries/ | | systems | | +-----------------+---------------------------------------------------+ | System p | www.ibm.com/servers/eserver/support/unixservers/ | | servers | | +-----------------+---------------------------------------------------+ | System x | www.ibm.com/servers/eserver/support/xseries/index | | servers | .html | +-----------------+---------------------------------------------------+ | System z | www.ibm.com/servers/eserver/support/zseries/ | | mainframes | | +-----------------+---------------------------------------------------+ You can find service information for your IBM products, including supported options, at www.ibm.com/support/us. Also, you can find information about IBM Director in the IBM Systems forum at www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759&cat=53. B.4 Software service and support IBM provides a wide range of support products for IBM Director software. For installations on IBM BladeCenter products If you install and use IBM Director Server on BladeCenter products, you can purchase the Implementation Services ServicePac(R) for BladeCenter and xSeries for service and support of IBM Director Server. For installations on System i technology Through IBM Software Maintenance (SWMA), you can get assistance with usage, configuration, and software problems with System i technology. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. For installations on System p servers Through IBM Software Maintenance (SWMA), for a fee, you can get telephone or electronic assistance with usage, configuration, and software problems with System p servers. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. Note: When ordering or downloading only IBM Director Server, SWMA is optional and must be ordered specifically. For installations on System x servers and IntelliStation workstations Through IBM Support Line, for a fee, you can get telephone assistance with usage, configuration, and software problems. You also can purchase Enhanced Technical Support (ETS), which is a proactive support option to Support Line for System x servers. Through IBM Software Maintenance (SWMA), for a fee, you can get telephone or electronic assistance with usage, configuration, and software problems with System x servers. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. If you install and use IBM Director Server on System x servers, you can purchase the Implementation Services ServicePac for BladeCenter and xSeries for service and support of IBM Director Server. For installations on System z mainframes Through IBM Service and Subscription (S&S), for a fee, you can get telephone or electronic assistance for software problems with System z mainframes. Fixes and updates are part of the warranty of this product and are included in your license for this product. For installations on non-IBM hardware If you want to install and run IBM Director Server on non-IBM hardware, you must purchase a license for IBM Director Server. However, this license does not entitle you to service and support of IBM Director Server. You can purchase service and support separately from Support Line. You also can purchase Enhanced Technical Support (ETS), which is a proactive support option to Support Line for non-IBM x86 systems. For information about which products are supported by Support Line in your country or region, go to www.ibm.com/services/us/its/pdf/remotesupportxseries.pdf. For more information about Support Line and other IBM services, go to www.ibm.com/services/us/index.wss, or go to www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). Appendix C. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: 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 states 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. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation MW9A/050 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. Appendix D. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: * AIX * AIX 5L * Alert on LAN(TM) * Asset ID * BladeCenter * DB2 * DB2 Universal Database(TM) * DirMaint(TM) * Electronic Service Agent * Enterprise Storage Server(R) * eServer(TM) * FlashCopy(R) * HiperSockets(TM) * i5/OS * IBM * ibm.com * IntelliStation * iSeries * Lotus Notes(R) * Multiprise(R) * Netfinity * NetServer(TM) * NetView(R) * OS/400(R) * PC 300(R) * POWER * Predictive Failure Analysis * pSeries(R) * RACF(R) * Redbooks * S/390(R) * ServeRAID * ServerProven * ServicePac * SurePOS * System i * System p * System p5(TM) * System Storage * System z * System x * System z9(TM) * Tivoli(R) * Tivoli Enterprise Console(R) * Tivoli Management Environment(R) * TotalStorage * Virtualization Engine(TM) * Wake on LAN(R) * xSeries * z/VM * zSeries(R) Intel , Itanium, and Pentium(R) are trademarks 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. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT(R) are trademarks of Microsoft Corporation in the United States, other countries, or both. Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. SET is a registered trademark of SET Secure Electronic Transaction LLC in the United States and other countries. UNIX(R) 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.