File Name: readme2.txt ****************************************************************** | | | IBM(R) UpdateXpress, Version 4.01 CD2 | | | | (C) Copyright International Business Machines Corporation, | | 2004, 2005. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES | | AND TRADEMARKS" in this document. | | | | Updated 27 April 2005 | | | ****************************************************************** ** Attention ** If your operating system is installed on a very large hard drive (greater than 150GBs or 65,535 cylinders), please refer to retain tip #H183962. CONTENTS --------- 1.0 Overview 1.1 About this readme file 1.2 Abbreviations and terminology 2.0 Supported servers 3.0 UpdateXpress HTML Index and Update Packages 4.0 Update versions 5.0 Known problems and limitations 6.0 Change History 6.1 UpdateXpress Version 4.01 6.2 UpdateXpress Version 3.06 7.0 National language considerations 8.0 Web sites and support 9.0 Notices and trademarks 10.0 Disclaimer 1.0 OVERVIEW ------------- This section contains information about this readme file and the other information that is on CD1. 1.1 About this readme file --------------------------- This readme file contains the latest UpdateXpress support information for the following packages that are included on CD2: o Linux firmware update packages (non-BladeCenter systems only) For information about how to use these UpdateXpress with these packages, see the help\xPress\introduction.htm page at the root of this CD, or the IBM support Web site at: http://www.pc.ibm.com/support Search on the keyword: UpdateXpress Additional UpdateXpress utilities are included on CD1 and CD3. For information about the following UpdateXpress utilities, see the readme file on the applicable CD. CD1 (Windows support) o RemoteUX for Windows o UpdateXpress bootable CD for xSeries and pSeries (x86) systems (non-BladeCenter systems only) o Windows firmware and driver packages (non-BladeCenter systems only) CD3 (BladeCenter support) o Windows firmware update packages for BladeCenter units o Windows driver update packages for BladeCenter units o Linux firmware update packages for BladeCenter units o AIX firmware update packages for BladeCenter pSeries systems o RemoteUX for Windows o RemoteUX for Linux o UpdateXpress for BladeCenter xSeries and pSeries systems 1.2 Abbreviations and terminology ---------------------------------- The following abbreviations are used in this readme file: o Administrative console The system from which RemoteUX is launched. o Target system The managed object or system that is being updated. 2.0 SUPPORTED SERVERS ----------------------- UpdateXpress CD1 is supported on the following servers: Supported server Machine type Limitations =============================== ============ =============== xSeries(R) 200 8478 xSeries 200 8479 xSeries 200 8481 xSeries 205 8480 xSeries 206 8482 xSeries 220 8646 xSeries 220 8645 xSeries 225 8647 xSeries 225 8649 xSeries 226 8648 xSeries 232 8668 xSeries 235 8671 xSeries 236 8841 xSeries 255 8685 xSeries 300 8672 xSeries 305 8673 xSeries 306 8836 eServer 325 8835 eServer 326 8848 xSeries 330 8654 xSeries 330 8674 xSeries 330 8675 xSeries 335 8676 xSeries 335 8830 xSeries 336 8837 xSeries 342 8669 xSeries 345 8670 xSeries 346 8840 xSeries 360 8686 xSeries 365 8861 xSeries 365 8862 xSeries 366 8863 xSeries 440 8687 xSeries 440-16 8687 (Firmware only) xSeries 445 8870 pSeries(R) 7081 7081 (Firmware only) pSeries 7082 7082 (Firmware only) 3.0 UPDATEXPRESS HTML INDEX AND UPDATE PACKAGES ----------------------------------------------- UpdateXpress provides update packages for firmware and device drivers. In some cases, an update does not provide an unattended installation method and an update package is not provided. The root of UpdateXpress CD2 contains an index.htm file that displays information about the updates packages that are on the CD, and provides links to these files. Each update package is a self-extracting executable file. It can be copied to a target machine by clicking the matching link from the HTML index. Once an update package is copied to the target server, it can be launched from the command line. For more information, see the index.htm file on the root of the UpdateXpress CD2. Note: The minimum requirement to view the UpdateXpress HTML index is Internet Explorer version 4.01. 4.0 UPDATE VERSIONS -------------------- 4.1 Tape drive firmware updates -------------------------------- The following tape drives are certified for use with UpdateXpress on the following servers: Server Tape drive ====== ======================================================= x200 IBM 09N4041 12/24 GB DDS/3 4 mm Internal Tape Drive x200 IBM 20L0549 10/20 GB Internal IDE Tape Drive x220 IBM 09N4042 10/20 GB NS20 Internal SCSI Tape Drive(TR5) x230 IBM 01K1320 20/40 GB DLT SCSI Internal Tape Drive x240 IBM 01K1325 20/40 GB 8mm Internal SCSI Tape Drive x250 IBM 00N8016 100/200 GB LTO Tape Drive x330 IBM 01K1325 20/40 GB 8mm Internal SCSI Tape Drive x340 IBM 01K1325 20/40 GB DLT Internal Tape Drive x350 IBM 00N7990 40/80 GB DLT Internal Tape Drive x370 IBM 00N7991 20/40 GB DDS/4 4mm Internal Tape Drive 5.0 KNOWN PROBLEMS AND LIMITATIONS ----------------------------------- This section contains information about the known problems and limitations for UpdateXpress on CD1, CD2, and CD3. 5.1 Error flashing firmware on a Remote Supervisor Adapter UpdateXpress does not support flashing a Remote Supervisor Adapter while using the Remote Supervisor Adapter remote control function. In this case, the flash will fail. 5.2 One or more updates failed message when running the hard disk drive microcode update program from UpdateXpress. The hard disk drive update program included with UpdateXpress only updates microcode on hard drives attached to a SCSI controller. If your server contains only IDE or SATA based drives and controllers, the hard disk drive update program returns a "1" indicating that the update failed. 5.3 "Installation Failed" text messages displayed when booting from the UpdateXpress CD. During the text mode portion of the UpdateXpress boot process, UpdateXpress attempts to install several SCSI device drivers. The only device drivers that are installed are those that match the hardware that is installed in your server. The device drivers for SCSI adapters that are not installed in your server display error messages. This is normal. 5.4 UpdateXpress lists the versions of the IBM ServeRAID controller as "MANY" after flashing a system. If there is more than one type of ServeRAID controller in the server or the ServeRAID controllers have different firmware levels, UpdateXpress will display the ServeRAID versions as "MANY" after flashing. This is normal. 5.5 The RemoteUX application might drop connection to the target server The network connection to the target server might be dropped while using the RemoteUX application command line utility to update an Ethernet device driver (either with the -d or -pkg option). This does not interfere with applying the update, the update results are recorded in \uxlog\ux.log file. 5.6 No automatic S3 device driver update on xSeries330 (8654) servers No device driver update is offered for S3 video adapters on xSeries330 (8654) servers. This server incorrectly reports the PCI device ID. Use the Windows manual installation using the following files: for Windows 2000 go to \SGUIDE\ADAPT\VIDEO\WIN2K\13.95.12 and for Windows NT go to \SGUIDE\ADAPT\VIDEO\WINNT\8.19.11b. 5.7 ServeRAID device driver update does not upgrade the twintail.sys The ServeRAID device driver update does not automatically upgrade the twintail.sys device driver. 5.8 Updating "ibmfe" type device drivers does not preserve settings Updating Intel Ethernet device drivers that are using the ibmfe type device driver does not preserve the adapter settings. Updating the e100b.sys device driver does not have this problem. 5.9 No remote package for Windows 2000 or Windows 2003 SCSI Adaptec device driver update The SCSI Adaptec device driver update is based on a WinBatch script. This is not available as a remote update. 5.10 Updating device drivers might cause errors to appear in event viewer Errors could be listed in the event viewer since the device drivers must be stopped during the update process. After updating the device drivers and restarting the server, these errors should disappear. In addition, ServeRAID device driver errors may appear in event viewer if the ServeRAID device driver and firmware levels do not match. 5.11 UpdateXpress only updates Ultra160 SCSI controllers that use the adpu160m.sys device driver. For servers running Windows 2000, UpdateXpress detects and updates only Ultra160 SCSI controllers that use the device driver "adpu160m.sys". Other SCSI controllers are not detected or updated in this release. In addition, the adpu160m.sys driver supports multiple chipsets and if the improper chipset has previously been selected, the SCSI update may freeze. If this occurs, the user may press CTRL+ALT+DEL to regain control of the keyboard and mouse and manually stop the update. 5.12 The xSeries300 BIOS package, 33p2589w.exe, does not generate an entry in \uxlog\ux.log. 5.13 IBM Intel based Network device driver update might return an error code of "1". When attempting to update from ibmfent.sys or ibmfent5.sys to the latest IBM Intel based network device driver, the update may return an error code of "1" (failure) although the device driver will successfully update. 5.14 The xSeries 205 and xSeries 305 BIOS package updates are supported for certain versions. The BIOS package update for the xSeries 205 is supported for level 30A or greater. The BIOS package update for the xSeries 305 is supported for level 41A or greater. Both updates are available directly from the bootable option of the UpdateXpress CD regardless of initial BIOS level. 5.15 UpdateXpress leaves ux*.tmp directories on the root of C: drive. For some device driver updates to successfully complete, UpdateXpress must leave the ux*.tmp directories on the hard disk drive. When all updates are successfully applied, these directories may be manually removed. Some device driver updates require one or more additional reboots before they are completed. 5.16 LSI device driver update sends an error code of 28, 29, or 30. These return codes specify that the following steps must be taken before the LSI device driver update is completed. Error Code 28: The version of the LSI device driver (less than 1.08.12) that is currently installed requires that you restart the server twice and log in both times. During this process the LSI device driver updates automatically. Error Code 29: The system BIOS is an earlier version that does not enable the LSI device driver update to proceed. Update the system BIOS and restart the server. The LSI device driver update completes automatically after the system BIOS is updated. Error Code 30: The system BIOS is an earlier version that does not enable the LSI device driver update to proceed. Update the system BIOS and restart the server. Additionally, the version of the LSI device driver (less than 1.08.12) that is currently installed requires you to restart and log in to the server two additional times. At the end of this process, the LSI device driver is updated. 5.17 UpdateXpress requires that the target system has the "temp" environment variable defined, and that the directory defined by "temp" exists. 5.18 When updating the Intel network card device driver with a Windows 2000 operating system, UpdateXpress also updates the ProSet utility. 5.19 Booting from the UpdateXpress CD will not work on servers with more than one IDE CD-ROM drive installed. Firmware can be updated by using the update packages or the RemoteUx application. 5.20 Running the ATI package on servers that either do not have an ATI adapter or have an unsupported ATI adapter results in an error message. You must manually accept this message to continue. 5.21 (Windows) Running the command "RemoteUX -e" or "RemoteUX -c" may not find all adapters that are in the target server. UpdateXpress displays only the information that is provided in the SMBIOS structure. Some adapters do not report their information in the SMBIOS structure, and are not displayed. 5.22 (Windows) When updating the Remote Supervisor Adapter using "RemoteUX -f" or through a package, the update returns an error code. This update might return an error code of 5 or 6. If this occurs, run the update again. This update might also return an error code of 8 indicating that the Remote Supervisor Adapter firmware does not match the current server. If this occurs, the Remote Supervisor Adapter can be updated by running UpdateXpress locally. 5.23 Video setting must set to 16 bit or higher The UpdateXpress GUI might appear distorted if the video setting color is not set to 16 bit. 5.24 "Error in config.sys line 21" displayed when booting from UpdateXpress CD. The USB CDRom device driver will display this error whenever the UpdateXpress CD is booted on a server that does not contain a USB CD-ROM. This error is harmless and can be ignored. 5.25 Driver Update Package GUI contains no default selection. If a firmware update is currently scheduled for the next system restart and a driver package is run, nothing on the GUI will be selected. Clicking next without selecting anything appears to unschedule the firmware update. However, this does not change the originally scheduled firmware update. If a selection is made on the GUI, the device driver update will work normally. 5.26 Updating the service processor device driver in an xSeries 330 (8674) or xSeries 330 (8675) server may force reboot. Your server may automatically reboot when updating the service processor device driver if all of the following conditions are met: 1. The update is being performed on an xSeries 330 (8674) or xSeries 330 (8675) server. 2. The server contains and RSA adapter. 3. The current level of the RSA device driver is v4.98 or less. In this case, UpdateXpress will complete normally and ask that you restart the server. After the server restarts, it will automatically restart again 1-2 minutes later. This second restart is forced by the service processor device driver update program. After the second restart, the service processor device driver will be updated to the current level. 5.27 UpdateXpress will not update the IBM Automatic Server Restart Service ASR or Integrated Systems Management Processor Drivers. 5.28 Active PCI device driver update returns an error code of 2. If the version of the Active PCI driver currently installed is at the same level or a later level than the version contained in the Active PCI device driver update, the update will return an error code of 2. On some servers, the update will also return a 2 if the current device driver level is 1.0.0.9 or less. If this occurs, uninstall the current driver and run the update again. 5.29 (Windows) RemoteUX -c and RemoteUX -e may report certain levels as "Unknown" On machines with older BIOS levels, RemoteUX -e and/or -c may report Diagnostics levels as "Unknown". This is a result of the Diagnostics level not appearing in the SMBIOS structure, from which RemoteUX obtains firmware information. This issue is usually resolved by updating the server to the latest BIOS level. Furthermore, RemoteUX will also report older levels of ServeRAID BIOS as "Backlevel" although ServeRAID firmware will be reported correctly. Once the ServeRAID BIOS/Firmware is updated to the latest level, RemoteUX will report both levels correctly. 5.30 (Windows) RemoteUX -c and RemoteUX -e will not report Service Processor firmware levels on xSeries 330 machines (models 8654, 8674, and 8675). 5.31 RSA II firmware update special considerations 1. Before you use UpdateXpress to update the RSA II firmware, install the RSA II device driver. 2. If the firmware currently installed on the RSA II is for a different server, you cannot use UpdateXpress to update it. 5.32 The History of Changes field on the index.htm might be empty The updates that display on the index.htm page might display partial change history information about the updates. To launch a text file that provides comprehensive information about an update, click the Readme button for the corresponding UpdateXpress package. 5.33 (Windows) The RemoteUX -f command will not update Hard Disk Drive or Tape firmware for Hard Disks or Tape Drives that are attached to an LSI SCSI controller. In this case, the Hard Disk Drive or Tape drive firmware can still be updated by booting off the UpdateXpress CD or by using the update package. 5.34 On eServer 325 and BladeCenter HS40 systems, UpdateXpress cannot detect the version of the ISMP firmware that is currently installed. As a result, the ISMP firmware displays as "Unknown" and UpdateXpress attempts to update the firmware each time you run the application. 5.35 UpdateXpress will not update the Advanced Systems Management (ASM) device driver on Windows 2003 if the version currently installed is 4.98 or less. In this case, the ASM device driver will not be listed on the UpdateXpress GUI. 5.36 Failure to extract to floppy at 99% completion There is a known issue in the extraction software that sometimes displays a popup stating that the extraction to the floppy has failed at 99%. In most cases, the xtraction was indeed successful or the user can simply try extracting again. 5.37 UpdateXpress will not update the Active PCI device driver on Windows 2003 if the version currently installed is 1.0.0.9. In this case, the device driver will be greyed out on the UpdateXpress GUI. To update this device driver, you must first uninstall it manually and then run UpdateXpress again. 5.38 (Windows) The RemoteUX -f command will not update BIOS on x225 (8649) servers. For x225 (8649) servers it is suggested that you update the BIOS prior to running the "RemoteUX -f" command. The "RemoteUX -pkg:" command allows you to send the BIOS update package, a reboot is necessary before subsequently running the "RemoteUX -f" command. 5.39 UpdateXpress does not support updating the BIOS on x445 via a package. To update the BIOS, use local or remoteUX. 5.40 UpdateXpress cannot detect the version of the RSA2 video BIOS that is currently installed. As a result, the system BIOS displays as "Unknown" and UpdateXpress attempts to update the BIOS each time you run the application. 5.41 Updating ServeRaid adapters using the ipsraidn.sys driver to version 7.00 using the UpdateXpress CD will result in a digital signature warning in Windows 2000 and Windows 2003. 5.42 BIOS level 55A or higher is required to support bootable-CD mode on the BladeCenter HS40 (8839). For BIOS levels lower than 55A firmware packages may be applied from a remote machine using RemoteUX. 5.43 Limitation when flashing back bios: For new levels of system BIOS (released on or after June, 2004): If the system is configured using the Integrated Mirroring feature for the integrated SCSI controller, upon flashing to the new system bios level, the RAID configuration will be converted to a new format. This new LSI format is unreadable by earlier levels of code. Affected bios builds are listed below. After flashing up to the levels below, if it later becomes necessary to return the system to the previous bios level, the customer must follow instructions in retain tip H182244 to recover their LSI SCSI Configuration. The following servers are affected: xSeries 445, Type 8870, any Model. Bios version 1.15 xSeries 365, Type 8861, any Model. Bios version 1.08 xSeries 345, Type 8670, any Model. Bios version 1.17 xSeries 335, Type 8676, any Model. Bios version 1.12 xSeries 235, Type 8671, any Model. Bios version 1.13 xSeries 225, Type 8647, any Model. Bios version 1.07 BladeCenter HS20, Type 8832, any Model. Bios version 1.06 5.44 If there are redundant management modules and the IP addresses are obtained through DHCP, UXBC requires the redundant management module to obtain the same IP address as the primary management module upon failover. This is only true if the existing firmware version is earlier than 57K. 5.45 If the management modules are updated, they will be restarted during the update process. 5.46 The firmware level of the management modules cannot be updated to an earlier version by using the UXBC utility. 5.47 In environments where IBM Director is being run, IBM Director might connect to the administrative port (6090) of the management module when a global scan is initiated. This might impact the ability to connect to the management module with the UXBC utility. To resolve this issue make sure that the username and password for the management module are NOT set to the manufacturer defaults. If they are, change the username and password of the management module and restart the system. A restart of the management module, will always release the administrative port. 5.48 IBM ESM configuration settings can be reset when updating from a firmware version earlier than .081 (version 1.04) to a firmware version at or later than .081. Link aggregation settings are lost during this firmware update and are reset to the default values. If link aggregation settings or port trunking are configured differently that the default settings, do not use UXBC, unless you can manually reconfigure the switch afterward. 5.49 In a small percentage of cases the UXBC utility might not be able to confirm that the firmware update for the IBM ESM completed. In this case the log file will have a warning stating that "Update completion could not be verified". In every test that was conducted where the UXBC utility was not able to verify that the flashing completed, the ESM switch had successfully been updated. However, you should manually verify that the IBM ESM is at the correct version. 5.50 Running multiple instances of the ChassisUpdate script against more than one BladeCenter chassis at a time from an administrative system can produce undesirable results and is not supported. 5.51 When copying a response file from one platform to another, such as Windows to Linux or vice-versa, it is recommended that the BladeScanner tool for the target platform be run in edit mode, and the update paths be updated accordingly. 5.52 gnome-terminal does not always clear or display the screen correctly when using the BladeScanner application. If you experience a problem use a different terminal program such as xterm. 5.53 (Linux) RemoteUX uses PowerQuest Virtual Boot Environment (PQ-VBE) to remotely update firmware on xSeries systems. PQ-VBE does not support Reiser FS, which means that the remote directory (-r) specified in RemoteUX must be a non Reiser FS, such as FAT32, or Ext2 or Ext3. This is not a limitation on JS20 blade servers, because the update process on JS20 does not use PQ-VBE. This means that the UXBC utility cannot be used to update Linux blade servers that are only using Reiser FS. 5.54 (Linux) RemoteUX requires that compat-libstdc++-7.2-2.95.3.77 module is installed on both the administrative console and the Target system when running RHEL 3.0, SLES 8 and SLES 9. If this compactability module is not installed you will get a return code of 127 in the /uxlog/ux.log file on the target system. The log entry will look similar to: Tue Jan 18 21:47:57 EST 2005, Schedule Update=RemoteUX , New=, Status=Failed, ReturnCode=127 The /uxlog/output.log file will complain about the current standard c++ libraries and will contain messages similar to the following: ./vfile: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory ./vfile: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory vdinstlx: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory 5.55 (Linux) Do not change media tray while remotely updating Linux blade servers Do not change media tray (CD and Floppy) selection while remotely updating xSeries Linux blade servers with RemoteUX. If a Linux blade server boots with the media tray selected, then the media must remain selected when remotely updating the blade server. Similarly, if the media tray was not selected at boot time it must remain unselected when remotely updating the blade server. Changing the media tray will prevent the update running and will produce error 24. The /uxlog/ux.log file will contain an error similar to: Tue Jan 18 21:39:28 EST 2005, Schedule Update=RemoteUX , New=, Status=Failed, ReturnCode=24 The /uxlog/output.log file will contain an error similar to: Processing file /tmp/vfrmbtlx/VDisk.vfd Using PQEngine to get file cluster list FileSize = 98304000 Unable to get engine cluster list for file /tmp/vfrmbtlx/VDisk.vfd. [DeleteVolumeExtentList] Destroying extent entry 0 Error: Unable to generate sector map for file '/tmp/vfrmbtlx/VDisk.vfd'. Another alternative solution is to remove the usb-storage module with the rmmod command before the update is scheduled. 5.56 (Linux) RemoteUX does not update the Broadcom firmware on the JS20. It just updates the CEC and the QLogic firmware. For this reason the UXBC utility cannot be used to update that component. 5.57 (Linux) RemoteUX requires Perl is installed on the target system. 5.58 (Linux) RemoteUX does not update the Broadcom firmware on the BladeCenter HS20 (8832) blade server, because of this the UXBC utility cannot be used to update that component. 5.59 The BladeCenter Brocade switch requires that the firmware .zip file be unzipped into a directory on the required FTP server. The path that must be entered into BladeScanner for this update is the path to the top level directory appended by release.plist. ex. path/to/brocade/4.2.1a/release.plist Refer to the README included with the Brocade firmware update for more information. 5.60 The system version for the IPMI mapping layer and Intel chipset device driver can not be discovered on a BladeCenter HS20 (8843). Therefore, after an update the selection box in the user interface remains checked. 5.61 If a management module is flashed from 57 (or higher) to a release below 57, and login profile IDs are modified or added, then these profiles will show up as read/only profiles when the management module is eventually flashed back up to 57 or higher. 5.62 The QLogic Fibre Channel daughter card firmware update is always selected by default on the JS20 bootable CD3. The is because the system level is currently reported as "Unknown". 6.0 CHANGE HISTORY -------------------- This section contains information about the UpdateXpress change history. 6.1 UpdateXpress Version 4.01 ------------------------------ UpdateXpress Version 4.01 includes the following changes: o Support for the xSeries 366 (machine type 8863) o Removed support for the xSeries 455 (machine type 8855) o Added CD3 including UpdateXpress BladeCenter Utility with support for BladeCenter Management Module and I/O Modules. o Added RemoteUX for Linux supporting BladeCenter blade servers only. o Reorganized CDs into: CD1: Windows non-blade server packages and local and remote updates CD2: Linux non-blade server packages CD3: Windows and Linux blade server packages and local and remote updates 6.2 UpdateXpress Version 3.06 ------------------------------ UpdateXpress Version 3.06 includes the following changes: o Support for the xSeries 226 (machine type 8648), the xSeries 236 (machine type 8841), the xSeries 336 (machine type 8837), the xSeries 346 (machine type 8840), the eServer 326 (machine type 8848), the BladeCenter JS20 (machine type 8842) and the BladeCenter HS20 (machine type 8843) 7.0 NATIONAL LANGUAGE CONSIDERATIONS -------------------------------------- UpdateXpress can be started, on any supported server installed with a non-English Windows 2000 operating system. The same restrictions apply as documented for the servers when you are using an English version of Windows 2000. UpdateXpress is not translated at this time. 8.0 WEB SITES AND SUPPORT -------------------------- o IBM Support Web Site http://www.pc.ibm.com/support o IBM Support Web Site with link to downloads and drivers http://www-307.ibm.com/pc/support/site.wss/ 9.0 NOTICES AND TRADEMARKS ---------------------------- INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: o the e-business logo o BladeCenter o eServer o IBM o ServerProven o xSeries o pSeries Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows 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. Other company, product, or service names may be trademarks or service marks of others. 10.0 DISCLAIMER --------------- THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.