====================================================================== Readme file for IBM Systems Director BladeCenter and System x Management Version 6.1.2 Manager Feature Software Installable: com.ibm.director.systemx_bc_6.1.2.zip IBM Corp. 21 November 2009 ====================================================================== CONTENTS 1.0 Overview 2.0 Prerequisites and co-requisites 3.0 Installation Information 3.1 Prior to installation 3.2 Install 3.3 Perform the necessary tasks after installation 3.4 Special instructions 4.0 Uninstalling 5.0 List of changes included 5.1 Authorized Program Analysis Reports (APARs) 5.1.1 APARs incorporated into 6.1.1 5.1.2 APARs incorporated into 6.1.1.1 5.1,3 APARs incorporated into 6.1.1.2 5.1.4 APARs incorporated into 6.1.1.3 5.1.5 APARs incorporated into 6.1.2 5.2 Product Enhancements 5.3 Troubleshooting and known issues 6.0 Copyright and trademark information 1.0 Overview This is a maintenance update for IBM Systems Director Server BladeCenter Management. See section 5 for a list of items patched or updated. 2.0 Prerequisites and co-requisites None. 3.0 Installation information 3.1 Prior to installation If you downloaded from ibm.com, you must import the update before you can install it using update manager. If you downloaded the files using update manager, the update has already been imported. To import the update from the command line, use the following command: smcli importupd -r To import the update from the IBM Systems Director Web interface, perform these steps: 1. In navigation area, expand Release Management and click Updates. The Update Summary page displays. 2. In the Common Tasks section, click Import updates. The Import Updates page is displayed. 3. Type the directory of the update files on the management server in the Path field. All updates in the specified directory will be copied to the update library. You cannot select specific updates from this directory. 4. Click OK. The scheduler is displayed. Choose to run the task now or schedule it to run in the future. 3.2 Install To install the update from the command line, use the following command: smcli installupd [-n | -N ] -u com.ibm.director.systemx_bc_6.1.2 To install the update from the IBM Systems Director Web interface, perform these steps: 1. In navigation area, expand Release Management and click Updates. The Update Summary page displays. 2. In the Common Tasks section, click Install updates. The Install Wizard is displayed. 3. Follow the steps in the Install Wizard to install the update. 3.3 Perform the necessary tasks after install Restart the management server or managed systems on which the update has been applied. 3.4 Troubleshooting the installation For information about troubleshooting problems you encounter during installation, see the IBM Systems Director information center on the Web at: http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/director_6.1/fqm0_main.html 4.0 Uninstalling Update Manager does not support uninstallation of com.ibm.director.systemx_bc_6.1.2. Contact IBM Systems support if you need to uninstall this update: www.ibm.com/systems/support/ 5.0 List of changes included 5.1 Authorized Program Analysis Reports (APARs) Below is a list of APARs incorporated into IBM Systems Director versions 6.1.1, 6.1.1.1, 6.1.1.2, 6.1.1.3 and 6.1.2. IBM Systems Director updates and patches are cumulative with respect to the APARs they contain. For example, 6.1.2 contains not only the patches listed under that section but all other APARs listed that were originally resolved in previous 6.1.x.x patches and updates. 5.1.1 APARs incorporated into 6.1.1 The following APARs are incorporated into IBM Systems Director 6.1.1 IC53525 IBM Systems Director Server does not recognize French Keyboard layout during remote session. Certain keys such as $, &, @, |, }, ?, do not work. IC55593 IBM Systems Director may crash with a JAVA out of memory error as a result of collecting inventory against Bladecenter Chassis. IC56191 Critical Memory Alert in Advance Management Module (AMM) shows as “Minor” in the IBM Systems Director Server’s event log. IC56622 When an RSA or BMC is not connected to a network or does not have its own IP address, IBM Systems Director Server could not discover that card via in-band communication as a physical platform. IC57794 Critical Voltage Alert in Advance Management Module (AMM) shows as “Minor” in the IBM Systems Director Server’s event log. IC57842 Systems with LSI’s 10K, 10I, 10M and 8480 controllers report degraded array alert as Warning not Critical in Health Status. IC59135 (Infocenter Update) URL of Infocenter for IBM Systems Director was incorrectly documented in DVD and Infocenter. IC59418 Integrated version of MPCLI when launched via IBM Systems Director Server against a service processor card, fails to connect when password for that service processor contains special characters such as $. IC59459 IBM Systems Director Server runs very slowly and times out on many tasks after adding domain accounts to the local groups such as SMADMIN, SMUSER and SMMGR. IC59821 Light Inventory on Bladecenter Chassis runs full collection, with each request taking at least 30 seconds to complete, causing collection to back up. This results in slow performance, high CPU and memory growth, leading to Server crash (with Active Energy Manager installed only). Secondly, When Advanced Management Modules (AMM) have been discovered in IBM Systems Director Server, their event logs may repeatedly get full by multiple login attempts made by the IBM Systems Director Server. IC59866 On the Discovery Summary page, the numbers in the legends do not match the size of the corresponding slice of the pie chart. The pie chart on the Discovery Summary page will not update while the page is open, but the legend numbers do change as new systems are discovered. IC59869 GUI for right clicking on a problem system in Health Summary screen causes the right-click menu to show up below the area of the screen at 1280x800 resolution making it impossible to navigate to the menu items. IC59919 The IP Default Gateway in now collected as part of inventory. This allows for creation of dynamic groups based on this property. IC59963 (Infocenter Update) Troubleshooting topic added: "Remote command line prompt on a Windows 2003 Common-Agent managed system does not have working scroll bars", which describes how Enhanced Security Configuration for Internet Explorer can affect scroll bar on Windows Remote Command prompt function when launched via IBM Systems Director. IC59966 Inventory collection was failing when collected on large number of object via single task. IC60112 (Infocenter Update) Added a step in the topic "Preparing firewalls and proxies for IBM Systems Director". IC60165 IBM Systems Director incorrectly reports x64 bit system as x86 (32 bit) in the inventory. IC60205 (Infocenter Update) Added a Troubleshooting topic indicating Storage Configuration Manager’s (SCM) support statement on Regional Language Support for Operating System. IC60338 IBM Systems Director does not install “twguser.ini” file with Common Agent Services (CAS) agent. Hence users can not collect location information in the inventory for a given system. IC60340 During installation of IBM Systems Director Server, when asked to configure database, if user tries to connect to a non-default instance of MS SQL database, the installation will fail due to an inability to connect to given database instance name. IC60395 Double Byte Character Systems (DBCS) running Common Agent Services (CAS) agents would not collect inventory initiated by Systems Director 6.1. IC60476 Auto Discovery uses the wrong SNMP community name when verifying connection with the user’s SNMP objects, causing request to time out. This behavior makes the Request Access task slow since it is queued behind those queries. IC60511 Updates from UpdateXpress System Packs (UXSP) do not always show up in the install update page. IC60552 SMSTATUS incorrectly reports Server in “error” state which users may interpret as “Server down” when it is not. IC60573 Request Access fails for a non-root user account that has root privileges. IC60583 Certain Inventory mappings such as SystemAssetSettings, CacheMemory and UserContact which existed in 5.20.x versions are needed in the IBM Systems Director 6.1 release. This will allow users to edit twguser.ini file to collect inventory from additional resources. IC60630 Exporting inventory table data with more than 1000 entries fails in IBM Systems Director Server 6.1. IC60633 Event Filter sub-tree shows inconsistent information about event types. It displays repeated numeric and other data instead of correct types. IC60721 Collecting inventory from the CAS agent local to the IBM Systems Director management server and then restarting the IBM Systems Director server can cause the agent state be become "Unknown" and it remains in that state. IC60727 Users may not be able to refresh inventory of an individual system. IBM Systems Director needed users to close the inventory page and re-open to refresh it. IC60748 (Infocenter Update) Section added to the "Creating a monitor view" topice to show support for enabling Disk Monitors with steps on how to do it. IC60851 When requesting access with an invalid password to an AIX agentless system using SMCLI, IBM Systems Director may return an “Access Completed” message right after it reports “Request Access Failed”. The message misleads users who may interpret this as access being granted after the attempted failed due to an invalid password. IC60885 (Infocenter Update) New topic added: "Enabling collection of SNMP-based inventory by way of management modules" that provides information on how to configure Advanced Management Module (AMM) for SNMP V1 and V3 settings to enable collection of SNMP based inventory in Systems Director. PK80904 Common Agent Services (CAS) agents could not be installed using Agent Installation Wizard under Release Management on the IBM Systems Director console. Agent installation task may complete successfully without any errors, but users will not see the IBM Systems Director’s folder being created by the installation program. PK82871 When running SMSTOP, IBM Systems Director Server does not always stop targeted services and may receive an error as "SEVERE Error while stopping 'com.ibm.usmi.kernel.USMIKernel_1.0.0'" PK83676 IBM Systems Director Server crashes with a NULL Pointer Exception in “TCMServiceAccessPoint”. 5.1.2 APARs incorporated into 6.1.1.1 The following APARs are incorporated into IBM Systems Director 6.1.1.1 IC59693 IBM Systems Director Inventory information for network components displays each DNS Interface, IP Interface and LAN connection twice. The data is accurate but is displayed twice. IC59856 IBM Systems Director could not surface RAID Rebuilt notifications from LSI's Mega RAID adapters such as 10i, 10k, 10m and 8480. IC61434 After running Inventory collection from an IBM Systems Director 6.1.1 server on local or remote Agentless, Platform Agent, or Common Agent systems the Operating System object may show as Unknown. 5.1.3 APARs incorporated into 6.1.1.2 The following APARs are incorporated into IBM Systems Director 6.1.1.2 IC61526 When IBM Systems Director management server is installed in an Active Directory or LDAP environment, logging in to the console as a member of the domain takes a long time to complete and the execution of console tasks is very slow. In this setting, logging in as a local user also results in degraded performance. IC60731 Infocenter Update) Clarified instructions to configure both a client and server for SSL communication. IC61717 Afer applying the IBM Systems Director 6.1.1 update the Director server may not start properly. 5.1.4 APARs incorporated into 6.1.1.3 The following APARs are incorporated into IBM Systems Director 6.1.1.3 IC62083 From a 6.1.1, 6.1.1.1, or 6.1.1.2 IBM Systems Director management server, if you discover a blade as an agentless OS MEP, request access successfully and run an inventory collection on this OS MEP, the inventory collection hangs and the blade will go offline, from the AMM perspective, with a COMM error. 5.1.5 APARs incorporated into 6.1.2 The following APARs are incorporated into IBM Systems Director 6.1.2 IC59906 Verify connection can cause CIM server to crash on Linux or Windows systems with the MegaRaid card oSystems Management Application Programming Interfaceinstalled on the x3250. IC59978 MSSQL Warning Message resolved by extending the database column width to remove the potential for data loss. IC60089 (Infocenter update) Added step to "Importing agent packages" topic to restart the IBM Systems Director service. IC60310 Asset ID shows HP Proliant systems as IBM Proliant. IC60334 (Infocenter update) Added a limitation statement to the Troubleshooting section: "Cannot change IP address or host name of management server" to document that the management server's hostname and IP address cannot be changed after installing IBM Systems Director 6.1.0 or later updates. IC60444 Error connecting to MSSQL on a non default port. IC60555 Updates failed due to lack of required space. Will now log a message in the install task job log where and how much space is needed for the update. IC60581 (Infocenter update) Updated Troubleshooting topic: "Clones of Linux machines are not discovered or are merged", which describes generating unique secure shell (ssh) fingerprints required for cloned systems. IC60666 For environments with disconnected networks where, in addition to IBM Systems Director, customers also have a stand-alone or shared Agent Manager located remote of the IBM Systems Director Server, we resolved an issue that allowed the discovery of Common Agent systems. Prior to this fix, Agent Manager discovery would allow the discovery of agent systems on networks that are not accessible to the IBM Systems Director Server. IC60715 Improved response time on request access tasks. IC60926 Made the Update Manager HTTP proxy settings persistent. IC61015 (Infocenter update) "The IBM System x and IBM BladeCenter platform configuration file" topic was updated to specify that the xbc_platforms.cfg is case sensitive when customizing the IBM System x and IBM BladeCenter platform configuration. IC61020 (Infocenter update) Corrected Director 6.1 "Supported operating systems" documentation regarding which RHEL 5 releases are supported. IC61107 Corrected the time range displayed when setting the time range while building an automation plan. IC61170 Resource Monitor recordings stop permaturely. IC61222 Location inventory information is overlaid with subsequent inventory requests to different agents. IC61265 Autorename of the server mep to display the hostname does not work. IC61303 Application error of twgucd32.dll encountered running smcli genenvet command on non-English Windows system. IC61370 Added a popup when requesting the discovery of an endpoint that was already discovered. IC61461 IBM Systems Director Server encounters a java exception in TWGEventManagerServiceNode$EventProcessor.processEvent when processing an event action. IC61649 6.1 Director server shows duplicate IP addresses for Brocade and Cisco switches when using a Multi-Switch Interconnect Module in a BladeCenter. IC61782 Configuring SLP port usage using the slp.properties file does not work. IC61804 (Infocenter update) Corrected information on the registry location for restricting command execution in the "Restricting anonymous command execution on Windows" topic. IC61825 Resolved inventory collection from Linux systems that contain non-default text in the /etc/issue file. This fix allows users to customise the contents of this file and still properly collect inventory. IC62018 (Infocenter update) Updated uninstall procedures in the "Uninstalling IBM Systems Director" topic. IC62018 (Infocenter update) Added information on list of all items that can be removed after an uninstall of the IBM Systems Director agent depending on what other software is installed. IC62156 Allow autorename of Server MEP display name to be the same as the OS MEP display name. IC62180 (Infocenter update) Updated the "Supported database applications topic" to specify that Oracle Cluster configuration is not currently supported. IC62331 Launch in Context (LiC) fails when the logon userid contains a Dollar Sign ($). IC62382 (Infocenter update) Corrected "Preparing to install IBM Systems Director Server on Linux for System x and x86-based systems" topic to remove references to rpms that did not apply to a Linux installation. IC62392 (Infocenter) Limitation statement added to "Troubleshooting and support" that explains that for IBM Systems Director 6.1.1 Platform Agents installed on systems with an IMM (Integrated Management Processor), the IPMI (Intelligent Platform Management Interface) driver is needed to manage the IMM. The only IPMI drivers supported with the IMM are the IPMI drivers distributed with the Operating System. IC62398 (Infocenter update) Corrected link to MPCLI in the "Unattended installation" and "InstallShield wizard installation" topics. IC62435 Execution of 'smcli lsmeps' command is terminating prematurely without producing the complete list of MEPs. IC62662 (Infocenter update) Update the "Configure Systems Management Application Programming Interface (API)" topic. IC62703 Opening the logging page of a task in the task manager results in a blank screen with ATKCOR031E, an UNKNOWN ERROR message. IC62835 Correct the Discovery Manager screen status on the number of systems with access to the Director Server when the number of systems that have been discovered exceeds the default maximum number of rows for the Navigate Resources screen. IC62859 Corrected an issue with the 6.1.1.2 and 6.1.1.3 releases of IBM Systems Director where passwords containing the "#" symbol and ther special characters would not be accepted by the Director Server. IC62863 (Infocenter update) Documented that alerts for issues with the LSI 1030 controller are only sent as Director CIM events even though subscriptions exist for other handlers such as TEC and SNMP. IC62889 Server start up times could be exceptionally long (multiple hours) in environments with large numbers of endpoints. This fix resolves the problem and can reduce times in larger environments to under one hour. IC62893 IBM Systems Director 6.1.1.2 Server preferences don't persist after a server restart. IC62900 (Infocenter update) Added information for why full access status for discovered endpoints may not be reported. IC62919 Issuing smstatus -r may return alternating active/inactive status when the IBM Systems Director Server status was constant. IC62959 Creating Advanced Discovery profiles which importing a file of ip addresses results in a profile that cannot be reopened. IC62967 (Infocenter update) Updated the "Compiling a MIB file" topic to clarify that the MIB files must be resident on the IBM Systems Director server system for compilation. IC62968 An event action of Send an SNMP trap fails if target cannot be pinged. IC63119 (Infocenter update) Clarified that agent versioning reflects the patch level of the agent which may not be the same as the name of the package. IC63244 Corrected an out of memory condition when IBM Systems Director 6.1 manages a large number of legacy agents. IC63404 The IBM Systems Director 6.1.1 Platform Agent reports incorrect BMC firmware in the 6.1.1.1 IBM Systems Director Server database under software inventory. IC63405 Disk Drive Operational Condition: Failed appears in the list of Hardware Predictive Failure Alert events in error. IC63439 Inventory collection may fail for SuSE Linux Systems Director Server or SuSE Linux Agentless and Common Agent endpoints. IC63446 The IBM Systems Director 6.1.1 CAS Agent BIOS information is not available in inventory. IC63453 System name should not be filterable in an Inventory view containing more than 1000 lines of inventory data. IC63541 Diagnostics and RSA firmware level are not visible in inventory. IC63576 smcli commands with arguments containing a single quote do not work. IC63584 Using the changePassword.cmd to change the database password results in an inability to start IBM Systems Director. IC63690 Corrected a NullPointer Exception after IBM Systems Director Server Start, which was a timing issue. IC63715 No BIOS/Firmware levels were shown after inventory collection from an agentless system. IC63791 When executing smsave on a Windows server, database backup error messages are now reflected in the completion status. PK90444 (InfoCenter update) Provided meaningful corresponding information for message IDs such as "DNZZMS451E: Component=VMAPI RC=420 RSN=8". 5.2 Product enhancements The following list provides information about new features and enhancements in IBM Systems Director 6.1.2. featureID Description --------- ------------------- 135049 Adding IPMICmdLine support for blade 137402 Adding hardware log support for IMM 136862 Adding profile based power operation support 137275 Adding new BladeCenter group for FCoE Device 136370 Adding standard profile for lightpath support 137866 Adding profile profile based bluelight support 137103 Adding new chassis switch inventory support 139387 Adding BladeCenter E support 133562 Adding LDAP client configuration for IMM and RSA 133563 Adding LDAP client configuration for AMM 133614 Adding NTP client configuration for AMM, RSA and IMM 134813 Adding network configuration support for IMM 136276 Adding power operation configuration for RSA and IMM 136277 Adding power operation configuration for AMM 137786 Adding new switch configuration support 135829 Adding support for virtual center 4x and hyper-v 5.3 Troubleshooting and Known Issues For information about troubleshooting problems you encounter with installation or other update activities, see the IBM Systems Director information center on the Web at: http://publib.boulder.ibm.com/infocenter/systems/topic/director.tbs_6.1/fqm0_r_tbs_solving_problems.html 6.0 Copyright and trademark information www.ibm.com/legal/copytrade.shtml Notices INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Other company, product, or service names may be trademarks or service marks of others. THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: * the Excluded Components are provided on an "AS IS" basis * IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * IBM will not be liable to you or indemnify you for any claims related to the Excluded Components * IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.