IBM System Storage™ DS4000 Storage Manager version 9.23 for Linux on IBM pSeries Servers (Linux on POWER - LoP). Note: The Linux on POWER (LoP) host attachment to the IBM 1722-all models (DS4300), IBM 1724-all models (DS4100), IBM 1742-all models (DS4500 and DS4400), 1814-all models (DS4200 and DS4700) and 1815-all models (DS4800) requires the additional purchase of an IBM DS4000 Linux on POWER Host Kit Option. The IBM DS4000 Linux on POWER Host Kit options contain the required IBM licensing to attach an IBM pSeries server running Linux Operating Systems to the DS4100, DS4200, DS4300, DS4400, DS4500, DS4700 or DS4800 storage subsystems. Please contact your IBM service representatives or IBM resellers for purchasing information. NOTE TO SERVICE – Reference RETAIN # N/A (C) Copyright International Business Machines Corporation 1999, 2007. 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 in section 6.0 "Trademarks and Notices” in this document. IMPORTANT: DS4000 Storage Manager version 9.19.xx.12 and later is required for DS4000 storage subsystem users in countries implementing the new Daylight Saving Time (DST) rules (which includes U.S., Canada, Bermuda). Storage Manager version 9.19.xx.12 or later release includes revised DST transition dates to comply with provision of the Energy Policy Act of 2005 extension of Daylight Saving Time (DST) by four weeks, beginning in year 2007. Please refer to section 1.3 Enhancements for more information. Refer to the IBM System Storage™ Support Web Site or CD for the IBM DS4000 Storage Manager version 9 Installation and Support Guides for AIX, HP-UX, Solaris and Linux on POWER. This guide along with the DS4000 Storage Manager program Online Help provide the installation and support information. Last Update: 05/10/2007 Please refer to corresponding Change History document for more information on new features and modifications. Products Supported ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, | | | | | 88A, 88H, 80A, 80H | |------------|-----------|--------------|------------------------| | DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, | | | | | 70T, 70S, 72T, 72S, | |------------|-----------|--------------|------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | FAStT 600 | 1722 | 6LX, 6LU, 6LJ, 60X | | | | | 60U, 60J, 60K, 60L | |------------|-----------|--------------|------------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | |----------- |-----------|--------------|------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | |----------- |-----------|--------------|------------------------| | N/A | FAStT 500 | 3552 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | N/A | FAStT 200 | 3542 | 1RX, 1RU, 2RX and 2RU | ------------ --------------------------------------------------- ATTENTION: 1. The DS4000 storage subsystem controller firmware version 05.40.xx.xx and earlier along with its associated NVSRAM files should not be loaded into DS4000 storage subsystems connected to DS4000 EXP100 drive expansion enclosures. 2. For the DS4400 and the DS4100 storage subsystems - all models (Standard /dual controller and Single Controller), the controller firmware version 06.12.xx.xx and later must be used. 3. For the DS4300 storage subsystems with Single Controller option, the controller firmware version 05.34.xx.xx and its associated NVSRAM file must be used. Do not attempt to download the controller firmware version 06.xx.xx.xx into these DS4300 storage subsystem models with single controller option. 4. For the FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models) storage subsystems, the controller firmware version 05.30.xx.xx and its associated NVSRAM file must be used. Do not attempt to download the controller firmware version 06.xx.xx.xx into these DS4000 storage subsystems. 5. For the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems connected to the DS4000 EXP810 drive expansion enclosures, the latest controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4300 with Standard (base) or Turbo options and the DS4500 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP810 drive expansion enclosure attachment. 6. For the DS4700 and the DS4800 storage subsystems connected to the DS4000 EXP100 drive expansion enclosures, the controller firmware version 06.23.xx.xx (and higher) and its associated NVSRAM file must be used. It is also recommended that the DS4700 and the DS4800 storage subsystems be upgraded to this controller firmware version even though they are not planned to have DS4000 EXP100 drive expansion enclosure attachment. Linux kernels Supported: ======================== ------------------------------------------------------------------------ | OS | Version | | | | | RDAC | |----------------------|--------------------------|----------------------| | LOP-RedHat 4 | 2.6.9-42.EL | Yes(note a) | | update 4 (RHEL4-u4)| |rdac-LINUX-09.01.B5.55| |----------------------|--------------------------|----------------------| | LoP-SLES 9 Service | 2.6.5-7.244-pseries64 | Yes(note a) | | Pack 3 (SLES9-SP3) | |rdac-LINUX-09.01.B5.55| |----------------------|--------------------------|----------------------| | LoP-SLES 10 |2.6.16.27-0.9.PTF.246308- | Yes(note a) | | |ppc64 |rdac-LINUX-09.01.B5.55| | | | | |----------------------|--------------------------|----------------------| | LoP-Redhat 3-u8 | 2.4.21-47.EL | Yes(note a) | | | |rdac-LINUX-09.00.A5.22| |----------------------|--------------------------|----------------------| Notes: a. The redundant failover/failback capability is supported by the IBM DS4000 Storage Manager Linux RDAC driver versions 9.00.A5.22 for RedHat EL 3 update 8 (2.4 kernels) and 9.01.B5.55 for SLES9 service pack 3, SLES10, and RedHat EL 4 update 4 (2.6 kernels) that are shipped with the IBM DS4000 Storage Manager version 9.23 for Linux on Power. ======================================================================== CONTENTS -------- 1.0 Overview 2.0 Installation and Setup Instructions 3.0 Configuration Information 4.0 Unattended Mode 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer ======================================================================= 1.0 Overview -------------- 1.1 Overview -------------- This IBM DS4000 Storage Manager package version 9.23 for Linux on POWER is required for managing the DS4200-all models, the DS4300-standard (dual controller) or Turbo models, the DS4500-all models, the DS4700-all models and the DS4800-all models with controller firmware version 06.23.xx.xx. In addition, it is also recommended for managing the following DS4000 storage subsystems - the DS4100-all models and the DS4400-all models with controller firmware version 06.12.1x.xx or higher installed. NOTE: DS4000 controller firmware versions 6.12.xx.xx or 06.15.2x.xx * Attachment support for EXP710 and EXP100 SATA disk drive expansion enclosures. * No attachment support for EXP810 disk drive expansion enclosure. DS4000 controller firmware version 06.16.xx.xx * Attachment support for EXP710, EXP810 and EXP420 disk drive expansion enclosures. * No attachment support for EXP100 SATA disk drive expansion enclosure. DS4000 controller firmware version 06.19.xx.xx * Attachment support for EXP710, EXP810, and EXP100 SATA disk drive expansion enclosures for DS4300 with dual controller and DS4500. DS4000 controller firmware version 06.23.xx.xx * Attachment support for EXP710, EXP810, and EXP100 SATA disk drive expansion enclosures for DS4300 with dual controller, DS4500, DS4700 and DS4800 Important: Please refer to the "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" located at http://www-1.ibm.com/servers/storage/support/disk/ for all installation and support notes pertaining to Linux on pSeries. Follow these instructions to get to the proper manual: Click the link for your DS4000 storage server. When the page opens, click the Download tab. Click the link for Current recommended Firmware and Storage Manager. The tables on the resulting page contain links to the DS4000 Storage Manager publications. In addition, the information on the IBM DS4000 Storage Manager client host software version 9.23 installation can be found in the readme.txt files included in the operating system (WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD-ROM. The "IBM DS4000 Storage Manager version 9 Installation and Support Guides for Windows 2000/Server 2003, Netware, ESX Server, and Linux" or the "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" publication is located in the \Docs directory on this CD or is available on IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. Furthermore, the Docs directory in the CD-ROM also contains other DS4000 publications that might provide helpful information. The "IBM DS4000 Storage Manager version 9.23 Linux support for pSeries" CD-ROM contains the documentation and files necessary for installing the IBM DS4000 Storage Manager Version 9.23 Client host software in Linux on pSeries(LoP) servers with Redhat RHEL3-u8 or later, SUSE SLES 9 Service Pack 3 (SLES9-SP3) or later, SUSE SLES 10, and RedHat EL 4 update 4 (RHEL4-u4) or later servers that are required to setup and manage the DS4000 storage subsystem that are connected to Linux on pSeries(LoP) servers. In addition, other host software packages are also available in the IBM System Storage™ Disk Storage Systems Technical Support web site. (see Note below for Linux on Power installations). Supported pSeries configurations and setup information can be found in the following DS4000 storage server document - IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER - which is located in the \Docs directory on this CD. Also, refer to the http://www.ibm.com/eserver/pSeries/linux IBM web site for the latest Linux for pSeries information and document updates. Please read the DS4000/FAStT EXP100 Storage Expansion Unit Release Notes before using Storage Manager version 9.xx on DS4000/FAStT storage subsystem connecting to EXP100 enclosures. IMPORTANT: This release of IBM FAStT Storage Manager host software for LoP servers supports all FAStT storage subsystems with general released firmware versions from 5.3x.xx.xx up to 06.23.xx.xx. For the latest DS4000 readme files, publications, and released code, refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site. Refer to the IBM DS4000 Support Web Site for latest DS4000 controller firmware and NVSRAM files for IBM machine types 1722, 1724, 1742, 1814, 1815, 3542 and 3552. The following table shows the first four digits of the latest controller firmware versions that are currently available for various models of the DS4000 storage subsystems. --------------------------------------------------- | DS4000 Storage | Controller firmware version | | Subsystem Model | | |------------------|--------------------------------| |------------------|--------------------------------| | DS4800 (1815) | 06.23.xx.xx | | | | |------------------|--------------------------------| | DS4700 (1814) | 06.23.xx.xx | |------------------|--------------------------------| | DS4500 (1742) | 06.23.xx.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.4x.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.23.xx.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.23.xx.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4300 Single | 05.34.xx.xx | | Controller Opt. | (for DS4300 SCU | | (SCU)(1722) | only) | |------------------|--------------------------------| | DS4200 (1814) | 06.23.xx.xx | |------------------|--------------------------------| | DS4100 (1724) | 06.12.4x.xx | | (standard dual | | | Single | | | controller Opt.)| | |------------------|--------------------------------| | FAStT500 (3552) | 05.30.xx.xx | |------------------|--------------------------------| | FAStT200 (3542) | 05.30.xx.xx | --------------------------------------------------- Note: Controller firmware 06.23.xx.xx is required for the DS4300-standard- dual controller or Turbo models, the DS4500-all models, the DS4700- all models and the DS4800-all models for attaching combinations of EXP810 and EXP100 storage expansion enclosures behind a DS4000 storage subsystem. New features introduced with controller firmware version 06.23.xx.xx or later are not available for DS4000 controllers with older firmware versions installed. The following table describes controller firmware versions required for attaching various models of DS4000 Storage Expansion Enclosures. --------------------------------------------------------------------- | Controller | EXP Storage Expansion Enclosures | | FW Version |------------------------------------------------------| | | EXP100 | EXP420 | EXP500 | EXP700 | EXP710 | EXP810 | |------------|---------|--------|--------|--------|--------|--------| |5.3x.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.40.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.41.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.42.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.0x.xx | Yes | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.1x.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.12.xx.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.14.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.15.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.16.2x.xx | No | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.8x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.9x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.19.xx.xx | Yes | No | No | No | Yes | Yes | --------------------------------------------------------------------- |6.23.xx.xx | Yes | Yes | No | No | Yes | Yes | --------------------------------------------------------------------- Note: EXP500 and EXP710/EXP100 can not be attached behind the same DS4000 storage subsystem. In addition, the EXP500 can only be intermixed with EXP700 if the fibre channel speed of the EXP700 and the DS4000 subsystem drive loop is set to 1Gbps. ======================================================================= 1.2 Limitations ---------------- The limitations are listed in the order of oldest to latest. The "*" prefix code next to the limitation number indicates this is the limitation that is added for this release. Note: The README file, that is included with the DS4000 storage manager host software version 9.23 for LOP web package, contains the most up-to-date limitations. This web package can be downloaded from the IBM System Storage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 1. The IBM DS4000 Storage Manager version 9.23 host software packages for Linux on Power are available for pSeries hosts running Redhat RHEL3 update 8, RedHat4 update 4, SLES 9 Service Pack 3, and SLES 10. 2. For the IBM DS4000 Storage Manager version 9.23 Client limitations, refer to the appropriate operating system readme files. These readme files can be found in the operating system (LoP, WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. For the latest DS4000 readme files, publications, and released code, refer to the IBM System Storage™ Disk Storage Systems Technical Support web site. http://www.ibm.com/servers/storage/support/disk 3. Refer to the "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" publication located on the http://www.ibm.com/eserver/pSeries/linux IBM web site for the latest Linux for pSeries limitations and document updates. 4. The "modprobe -r" command is not supported with this release on RHEL3-u4 when the Linux RDAC driver is installed. Use "rmmod" to remove and "modprobe" to recover the device driver stack. On pSeries servers with more then 4 processors, using the modprobe command may result in a hung server. 5. The Storage Manager Linux RDAC driver does not have the functionality to detect when a LUN is removed from the server. This includes FLASH Copy LUN's. Error messages are reported to the /var/log/messages file until missing LUN is recognized. The work around at this time is to reboot the pSeries server. 6. Universal Access Luns should not be assigned to LUN ID 0, especially with RDAC's installed. Placing an Universal Access Lun at LUN ID 0 may lead to loss of LUN recognition of next sequence LUN IDs or partial list of Virtual Luns reported with the RDAC driver. 7. SAN Boot on RHEL3 with RDAC installed, is restricted to initial root installation on Fibre Channel LUN ID 0. In addition, SAN boot is not supported for JS20 blades with RHEL3 update 5 (RHELu5) in this release due to an error in writing the partition table (BZ 16838.) 8. JS20 blades have possible intermittent problems with Fibre Channel Expansion card NVRAM corruption. (CMVC 279060) The symptoms are WWPN reverting back to default value. Please update to the 07.07.05 QLogic HBA device driver. 9. SAN Boot is not supported on IBM JS20/JS21 server blades with the initial release SLES9 kernel. The SAN Boot is only supported on JS20 server blades with SLES9 w/SP1 kernel and above. (6-3-2005) 10. The QLogic fail-over driver is currently not supported on the JS20/JS21 blade servers. 11. The following error message may be encountered under certain conditions when attempting to create a 2 TB LUN using the Create Logical drive wizard in the Subsystem Management window: "Error 4 - The operation cannot complete because of an incorrect parameter in the command sent to the controller." To avoid this error message, you must take certain steps while using the Create Logical Drive wizard to create a 2 TB LUN. Within the Specify Capacity/Name window within the create logical drive wizard, you must not manually specify the numeric value '2' in the New logical drive capacity field in tandem with the "TB" Units designator. If you do this, the Error 4 message will be issued and you will be unable to create the 2 TB LUN. Click on the up or down arrows next to the input field to select the desired capacity instead. When using the arrows, the program will display the correct maximum logical drive capacity value that can be specified for a given capacity unit (TB, GB, or MB). 12. Controller firmware 06.16.xx.xx does not support EXP100 storage expansion enclosures. Do not download it into DS4800 storage subsystems that have EXP100 enclosures attached. After the 06.16.xx.xx controller firmware is activated, the DS4000 storage subsystem will not recognize the drives in EXP100 enclosures, causing loss of data availability to the RAID arrays and logical drives that are defined in those drives. The controller firmware version 6.23.xx.xx and later must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached. 13. The storage subsystem might not recognize the drives or drive expansion enclosure correctly which results in the displaying of error messages or the inability to perform storage subsystem management operations, such as creating logical drives or arrays or initializing arrays from the storage management software. This behavior could be caused by powering up a DS4000 storage subsystem without any drive expansion enclosures attached and then connecting one or more drive expansion enclosures to the storage subsystem after it completes the boot process. The workaround is to make sure that the drive expansion enclosure(s) with at least two drives are connected to the DS4000 storage subsystem before you turn on the storage subsystem power. 14. Remove the drive(s) while the storage subsystem is online and then wait until the storage subsystem is going the boot process following a storage subsystem reboot event to reinsert the (new) drive(s) might cause the drives to be marked as failed after the storage subsystem completes the boot process. The workaround is to wait until the storage subsystem is back online before reinserting the drives. If the storage subsystem still does not recognize the drives, reconstruct the drives by using the Advanced -> Recovery -> Reconstruct menu function in the storage subsystem management window. 15. Uninstalling the storage manager host software package might leave the JAVA JRE directory behind. This problem might occur if you uninstall a copy of the SANtricity Storage Manager software that has been upgraded from a previous release. The newer installation package could not delete the JRE directory created with an older installation package. The workaround is to manually delete any directories left behind after uninstalling the software. 16. When creating remote logical drive mirrors through the SMCli script engine in the DS4000 Storage Manager client program, the following error might display during execution, stopping the remote logical drive mirror creation process: Error 173 - The operation cannot complete because the configuration number on the remote storage array is invalid. Some remote logical drive mirrors might have already been created. Rerun only the portion of the script that should be run to finish creating the rest of the remote logical drive mirrors. 17. Linux 2.6 kernels (RHEL4 and SLES9) with Emulex HBAs require device driver version 8.0.16.26 or higher. 18. Using the Linux utility to pick up newly created Universal Access LUNs (UTM LUNs) might result in two different symptoms to be seen on the Linux host. Symptom 1 When using 'hot_add' to add a UTM LUN to the system configuration for In-band management, it prevents the opening of the DS4000 'Storage Subsystem Management' window when using the Linux SMclient. Problem does not exist when accessing via the Windows SMClient. Symptom 2 When using 'hot_add' to bring UTM LUN into the system configuration of devices, it causes incorrect UTM LUN attributes to be reported by SMdevices. hot_add to pick up UTM - SMdevices program reports the incorrect UTM properties /dev/sdy (/dev/sg26) [Storage Subsystem Wingedfoot, Logical Drive , LUN 7, Logical Drive ID <600a0b80001184d60000000000000000>, Preferred Path (Controller-B): In Use] Work-around After adding the UTM LUN to the storage subsystem, reboot the Linux on Power (LoP) system to pick up the UTM LUN. This will allow the UTM device to be correctly configured and reflected by SMdevices and allow the DS4000 'Storage Subsystem Management' window to open correctly. Correctly configured UTM LUN as reported by SMdevices (/dev/sg4) [Storage Subsystem Wingedfoot, Logical Drive Access, LUN 7, Logical Drive ID <600a0b8000117ea40000000000000000>] 19. Utilizing standard Emulex installation script (lpfc-install) on SAN booted systems with RDAC installed will remove the currently used lpfc module, causing loss of access to root filesystem. Installation script uses usage count of lpfc module to determine if it is appropriate to remove the module. Installing RDAC driver will cause usage count of lpfc module to go to zero. Work-around Perform the following steps a. Boot system without RDAC driver installed. b. Update Emulex driver and reboot. c. Install RDAC driver and reboot 20. Can not increase the capacity of RAID arrays. RAID arrays with certain combinations of selected segment size and number of drives that made up the arrays will exceed the available working space in controller dacstore, causing a reconfiguration request (like expanding the capacity of the array) to be denied. These combinations are generally the largest segment size (512KB) with the number of drives in the array is 15 drives or more. There is no work-around. C324144 105008 21. Interoperability problem between the Tachyon DX2 chip in the DS4500 and the DS4300 storage subsystem controllers and the Emulex SOC 422 chip in the EXP810 expansion enclosure ESMs causing up to 5 Fibre Channel loop type errors to be posted in the DS4000 storage subsystem Major Event Log during a 24 hour period. There is a small window in the SOC 422 chip that multiple devices can be opened at one time. This ultimately leads to Fibre Channel loop errors of Fibre Channel link up/down, Drive returned CHECK CONDITION, and Timeout on drive side of controller. IBM recommends the use of the Read-Link-Status function to monitor drive loop for any problems in the drive loop/channel. There is no work-around. 22. All enclosures (including DS4000 storage subsystem with internal drive slots) on any given drive loop/channel should have complete unique ID's, especially the single digit (x1) portion of the ID, assigned to them. For example, in a maximum configured DS4500 storage subsystem, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosure id's with the same single digit such as 11, 21 and 31 should not be used on the same drive loop/channel. In addition, for enclosures with mechanical enclosure ID switch like DS4300 storage subsystems, EXP100 or EXP710 storage expansion enclosures, do not use enclosure ID value of 0. The reason is with the physical design and movement of the mechanical enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which return an incorrect enclosure ID to the storage management software. The most commonly returned enclosure ID is 0 (zero). In addition to causing the subsystem management software to report incorrect enclosure ID, this behavior also result in enclosure ID conflict error with the storage expansion enclosure or DS4000 storage subsystem intentionally set the ID to 0. The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810 storage expansion enclosures did not have mechanical ID switches. Thus, they are not susceptible to this problem. In addition, these storage subsystems and storage expansion enclosures automatically set the Enclosure IDs. IBM recommendation is not make any changes to these settings unless the automatic enclosure ID settings resulting in non- unique single digit settings for enclosures (including the storage subsystems with internal drive slots) in a given drive loop/channel. 23. If a DS4000 subsystem undergoes any operation that causes the controller to reset and go through the start-of-day boot process while you are attempting to add hardware, drives, or logical drives associated with the controller, the controller will send alert event notifications to the DS4000 subsystem Major Event Log (MEL) Log. The events indicate that the drives or the logical drives are offline or failed. The event notifications in the MEL Log are expected during the time that the controller is going through a boot process. The workaround is to wait at least 10 minutes after the controller reset is complete before moving logical drives or adding hardware. Use the DS4000 subsystem MEL to verify the time of the last controller reset event. 24. In the DS4300 and DS4500 Installation, User's and Maintenance guides, there are references that might mislead the user into thinking that IBM does not support partially-filled storage expansion enclosures or storage subsystems. IBM does support partially-filled storage expansion enclosures or storage subsystems as long as at least two drives are installed in the storage expansion or subsystem enclosures. However, IBM does not support partially-filled storage expansion enclosures or storage subsystems where the empty slots are required to keep the number of hard drives in the redundant drive loop/channel pair not exceeding the maximum of 112 drives per drive loop/channel. This is to prevent inadvertently inserting drives in those slots causing the controller of getting into the state that might result in lost of access to the storage subsystem. 25. In DS4000 storage subsystem configurations with controller firmware 6.15.2x.xx and higher installed, the performance of write intense workloads such as sequential Tape restores to DS4000 Logical drives with large I/O request sizes (e.g. 256kB) is degraded if the DS4000 logical drives are created with small segment sizes such as 8KB or 16KB. The work around is to create the DS4000 logical drives with segment size of 64KB or higher. 26. Because the MPP driver installation sets physical HBA module options during installation in /opt/mpp/modprobe.conf.mppappend. The following procedure is recommended when updating the HBA driver. a. Get the latest hba drivers supported by MPP. b. install the drivers c. execute "mppUpdate" to create a new mpp initrd image. d. reboot the system to boot with the new initrd image. See the Readme.txt file distributed with the MPP driver for more information. *27. On System p servers running RHEL4u4, an issue exists in the kernel where a panic can occur on the host system when the system is under heavy IO load. There is currently no work-a-round for this issue. RedHat is aware of the issue and has a proposed patch that will resolve the problem. Customers should contact RedHat and refer to RedHat defect number 116302 (bz32990_rh116302_cmvc360422_cmvc360556_cr117379_cr117456). *28. On System p servers running RHEL4u4 an issue exists where host system IO processes will stop making progress, pending IO completion from the kernel. This can be seen by looking at IO processes runtime where the process is outstanding for a longer time then expected. To work-a-round this issue, the SMdevices command being run when the condition is present, has shown to allow the hung IO processes to proceed. RedHat is aware of the issue and has a proposed patch that will resolve the problem. Customers should contact RedHat and refer to RedHat defect number 116303 (bz32992_rh116303_cmvc363570_cr118958). *29. When a Linux on Power system is booted on the SAN, where the boot/root volume is associated to a DS4000 Logical Volume, an issue was found were, if LILO is used to update the /etc/yaboot.conf boot loader information, while the boot/root LUN is under the control of the mpp driver, the result will be an invalid /etc/yaboot.conf file and lilo throwing exceptions during execution. To avoid this issue, do not use, LILO, YaST, or any other application to update the /etc/yaboot.conf bootloader configuration file after initial configuration. A work-a-round, is to manually edit the /etc/yaboot.conf, and perform the updates as needed to modify the bootloader configuration file in place; normally the /etc/lilo.conf file would be edited, and then lilo would be run to perform the update. Refer to the Linux documentation, manual, and info pages for a details on how to edit the file. If a kernel needs to be installed or upgrade, or if a driver is installed or upgraded, it is possible that LILO will still be run by the install scripts. In this case, if the mpp driver is still loaded, then this issue will be encountered. It is recommended that a backup copy of the /etc/yaboot.conf be kept in case of this occurring. An alternative option is to reboot the system into single path mode, without the mpp driver being loaded, before any updates are done to the kernel and/or drivers, to help to avoid this issue. If this is done, then normal applications can be used to update the boot loader configuration files. *30. Reflected Fibre Channel (FC) OPN frames occurs when intermixing the EXP810, EXP710 and EXP100s behind DS4700 or DS4800 storage subsystems. This behavior causes excessive drive side timeout, drive side link down and drive side link up events be posted in the DS4000 storage subsystem Event log (MEL.) It might also cause drives to be by-passed or failed by the controller. NEW DRIVE SIDE FC CABLING REQUIREMENT MUST BE ADHERED TO WHEN HAVING EXP100 CONNECTED TO THE DS4700 OR DS4800 STORAGE SUBSYSTEMS. Please refer to the latest version of the Installation, User's and Maintenance Guide for these storage subsystems that are posted in the IBM DS4000 Support web site for more information. http://www.ibm.com/servers/storage/support/disk/ *31. On System p servers running SLES 10, an issue exists in the kernel where a panic can occur on the host system when the storage subsystem does a failover. The following kernel PTFs are available from Novell under the SR #10325172063. http://you.novell.com/update/ppc/update/SUSE-SLES/10/PTF/014fcd0641ec128c68ddfc2ce730090f/20070315 http://you.novell.com/update/i386/update/SUSE-SLES/10/PTF/014fcd0641ec128c68ddfc2ce730090f/20070315-1 http://you.novell.com/update/x86_64/update/SUSE-SLES/10/PTF/014fcd0641ec128c68ddfc2ce730090f/20070315-2 ======================================================================= 1.3 Enhancements ----------------- The DS4000 Storage Manager version 9.23 host software for Linux on Power (LoP) operating systems in conjunction with the DS4000 storage subsystem controller firmware 06.23.xx.xx provides support for - New 4Gbps/15Krpm 300GB Fiber Channel Enhanced-Disk Drive Modules (E-DDMs) - New 750GB Serial ATA E-DDMs - The intermixing of the Fibre Channel and SATA E-DDMs within the same DS4700 storage subsystem or EXP810 drive expansion enclosure. - The intermix of EXP810/EXP710 and EXP100 enclosures behind a DS4700 and DS4800 storage subsystem. - New "Enhanced Disk Drive Predictive Fault Analysis" diagnostic feature on the DS4300, DS4500, DS4700 and DS4800 storage subsystem. The DS4000 controller will monitor the drives in the DS4000 storage subsystem and flag the drive with PFA error when one of the following conditions occurs a. 500 recoverable errors within a 24 hours period for Fibre Channel drives b. 4 medium errors within within a 24 hours period for Fibre Channel drives c. 8 medium errors within within a 24 hours period for SATA drives In addition, it also provides - Support for attaching the DS4000 EXP810 to the DS4300 Standard-Dual Controller models or Turbo models and the DS4500-All Models. - Support for the new Daylight saving time as required by the enactment of the United State's Energy Policy Act of 2005. The Daylight Saving Time (DST) will begin at 2 a.m. on the second Sunday in March and end at 2 a.m. on the first Sunday of November instead of 2 a.m. on the first Sunday of April to 2 a.m. on the last Sunday of October. For the year of 2007, DST will start on March 11, 2007 and end on November 11, 2007. DS4000 storage subsystem users in countries implementing the new DST rules (which includes U.S., Canada, Bermuda) are recommended to upgrade to Storage Manager version 9.19.xx.12 or later before March 2007. Storage Manager version 9.19.xx.12 or later release includes revised DST transition dates to comply with provision of the Energy Policy Act of 2005 extension of Daylight Saving Time (DST) by four weeks, beginning in 2007. There are no data integrity or functional problems caused by an incorrect clock setting. From the DS4000 controller firmware standpoint, this change will have no impact. The software changes are in the Java Runtime software included with the Storage Manager host software. The DS4000 controller uses an internal time clock which is GMT time based. The Storage Manager client software will make the appropriate time changes for reporting the Major Event Log entries (MEL), subsystem information or subsystem configuration changes in the time zone that the management station is installed. If no updates are made to existing DS4000 Storage Manager host software. The primary impact is that Email alerts and Major Event Log (MEL) entries will be off by 1 hour for 3 weeks in the Spring and 1 week in the Fall because they will be translated improperly by the Java Runtime Engine that is currently in use. This is a cosmetic impact only; as noted above, all times within the DS4000 controller firmware are stored in GMT time. Such values will be incorrect for the three-week period but then will be correct later when viewed from DS4000 Storage Manager client software. Additional incorrect timestamps may be seen in diagnostic reports, various subsystem component information displayed in dialog boxes, and performance monitor. In addition to updating the DS4000 Storage Manager host software, additional operating systems patches may be needed for the host server/management station that the DS4000 Storage Manager host software is installed. This will ensure that no problems occur with the implementation of the new DST rule. Please refer to the support web site for your operating systems for more information. Various impact scenarios are described below: Host System DS4000 Impact Operating Storage System Manager No Update No Update The System and DS4000 Controller time stamps are in sync until March 11, to April 1, when the times are 1 hour earlier than the time in the areas where the change is effective. Updated No Update The system and DS4000 controller time stamps will be out of sync by 1:00 hour. For example, a MEL event at 3:00 p.m. on the system will be reported as 2:00 p.m. on the DS4000 MEL logs Not Updated Updated Same as above, except the DS4000 Storage Manager will report with the correct DST time. Updated Updated Best scenario. Everything reports the correct time - Fix 114687: The disable and recreate FlashCopy logical drives can take up to 59 seconds. Changed Storage Manager client function used to handle the disableFlashcopy and recreateFlashcopy commands. This performance improvement will reduce the execution time delay to around 10 seconds (CMVC 354503). - Fix 114570: The Storage Manager SMmonitor service increments the number of Ethernet network handling threads for the DS4000 controller causing the maximum limit to be reached. The Ethernet network handling threads were not released by SMmonitor. The result is loss of SMagent connectivity to the DS4000 storage subsystem causing the storage subsystem to report "Not Responsive" error in the DS4000 Storage Manager Enterprise Management window. When the SMmonitor service is killed or the DS4000 controllers are rebooted, the number of available Ethernet network connections to the DS4000 controllers are restored resulting in normal management Ethernet connection to the storage subsystem (CMVC 355652). For more information, refer to the appropriate operating system readme files. These readme files can be found in the operating system (LoP, WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. ======================================================================= 1.4 Prerequisites ------------------ For the IBM DS4000 Storage Manager version 9.23 Client prerequisites, refer to the appropriate operating system readme files. These readme files can be found in the operating system (WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. For the Linux on pSeries prerequisites, refer to the pSeries Server document, "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" located at http://www.ibm.com/eserver/pSeries/linux IBM web site for the latest Linux for pSeries prerequisites and document updates. ======================================================================= 1.5 Dependencies ----------------- For the IBM DS4000 Storage Manager v9.23 Client dependencies, refer to the appropriate operating system readme files. These readme files can be found in the operating system (WIN32, WS03_X86_32bit, Linux, or AIX) directories on this CD or is available at the IBM DS4000 Support Web Site. For the Linux on pSeries dependencies, refer to the DS4000 storage server document, "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" located on the http://www.ibm.com/eserver/pSeries/linux IBM web site for the latest Linux for pSeries dependencies and document updates. In addition, always check the README files (especially the Dependencies section) that are packaged together with the firmware files for any required minimum firmware level requirements and the firmware download sequence for the DS4000 drive expansion enclosure ESM, the DS4000 storage server controller and the hard drive firmware. DS4000 storage subsystem controller firmware versions 6.12.16.xx or higher and EXP100 storage expansion enclosure ESM firmware version 9563 or higher are required to provide support for the new 400G SATA drive options and CRUs (P/Ns 39M4570 and 39M4575, respectively) in addition to the new 250G SATA drive CRUs (P/N 40K6837.) This new 250G SATA drive CRU is functionally equivalent to the previously-released CRUs (P/N 90P1349). The version 06.16.xx.xx of the DS4800 controller firmware is not compatible with the EXP100 SATA drive expansion enclosures. DO NOT download it into the DS4800 storage subsystems that have EXP100 drive expansion enclosures attached. After the 06.16.xx.xx controller firmware is activated, the DS4800 storage subsystem will not recognize the drives in EXP100 enclosures, causing loss of data availability to the raid arrays and logical drives that are defined in those drives. The controller firmware version 6.23.xx.xx and later must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached. Note: Controller firmware 06.16.xx.xx and later is required to support EXP810 storage expansion enclosures. Controller firmware 06.16.4x.xx and higher is required for the DS4700- all models and the DS4800-model 80A/80H. These models do not support older 06.16.xx.xx versions of controller firmware. The attachment of EXP100 enclosures is not supported for these models. Controller firmware 06.16.8x.xx and higher is required for the DS4200- all models. These models do not support older 06.16.xx.xx versions of controller firmware. The attachment of EXP100, EXP710 and EXP810 enclosures is not supported for these DS4200 models. Controller firmware version.23.xx.xx and higher is required for the attachment of EXP710, EXP810 and EXP100 behind the DS4300 with dual controller, the DS4500, the DS4700 and the DS4800 subsystems. ======================================================================= 1.6 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- Note: The IBM Storage Manager host software version 9.23 for Linux on Power (LoP) Linux OS new features and changes are described in the corresponding Change History document. Please refer to this document for more information on new features and modifications. IMPORTANT: Linux 2.6 kernels (RHEL4 and SLES9) with Emulex FC HBAs require Emulex device driver version 8.0.16.27 or higher. The IBM DS4000 Storage Manager version 9.23 Runtime, Client, Utilities and Agent host software is now available for pSeries server running Redhat RHEL3 update8 or later, RHEL4 update4 or later and SLES 9 SP3 or later. In addition, the IBM DS4000 storage subsystem Linux RDAC is now supported at this time in LoP servers with RHEL3-u6, RHEL4-u2 and SLES9 SP2 OS installed. Please contact your IBM representatives or resellers, or visit IBM web site for the availability of the DS4000 LoP Storage Manager host software support for pSeries servers with other version Linux OSes installed in the future. Note: This table for LoP servers running RHEL3 update8 or later, RHEL4 update4 or later, SLES 9 Service Pack 3 or later, and SLES 10 release. -------------------------------------------------------------------------- | Product | Version | |-----------------------------|--------------------------------------------| | SMIA | SMIA-LINUXPPC-09.23.A5.02.bin | |-----------------------------|--------------------------------------------| | SMruntime | SMruntime-LINUX-09.16.A5.04-1.ppc64.rpm | |-----------------------------|--------------------------------------------| | SMclient | SMclient-LINUX-09.23.G5.01-1.noarch.rpm | |-----------------------------|--------------------------------------------| | SMutil | SMutil-LINUX-09.23.A5.00-1.ppc64.rpm | |-----------------------------|--------------------------------------------| | SMagent | SMagent-LINUX-09.23.A5.00-1.ppc64.rpm | |-----------------------------|--------------------------------------------| |IBM Linux RDAC for RHEL3 u4 | 09.00.A5.22 | |through RHEL3 u8 | | |-----------------------------|--------------------------------------------| |IBM Linux RDAC for SLES9 SP3,| 09.01.B5.55 | |RedHat 4 update 4, and SLES10| | |-----------------------------|--------------------------------------------| |Emulex HBA driver's For Rhel3| 7.3.6 - Included on rhel3u8 release | |-----------------------------|--------------------------------------------| |Emulex Application Kit -rhel3| elxlinuxapps-2.1a29-7.3.6-1-1.tar | |-----------------------------|--------------------------------------------| |Emulex HBA driver's For | | | SLES 9 SP3 | 8.0.16.27 | |-----------------------------|--------------------------------------------| |Emulex HBA driver For RHEL4U3| 8.0.16.27 | |-----------------------------|--------------------------------------------| |Emulex HBA driver For SLES10 | 8.1.6.8-1 | |-----------------------------|--------------------------------------------| |QLA HBA driver-JS20 RHEL3u8 | 7.07.04 | |-----------------------------|--------------------------------------------| |QLA HBA driver-JS20 RHEL4U4 | 8.01.06 | | ----------------------------|--------------------------------------------| |QLA HBA driver-JS20 SLES9 SP3| 8.01.06 | -----------------------------|-------------------------------------------- |QLA HBA driver-JS20 SLES10 | 8.01.06 | -------------------------------------------------------------------------- One can also use a non-pSeries Server or a pSeries server running AIX OS as the management station. Please refer to the appropriate operating system readme file for code levels. These readme files can be found in the other operating system (WIN32, WS03_X86_32bit, Linux or AIX) directories on the DS4000 Storage Manager version 9 support for Linux on POWER Host Kit CD-ROM. IMPORTANT: Always refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released code levels. The Emulex device driver for Linux on Power can be downloaded at the following web page: http://www.emulex.com/ts/docoem/ibm/index.htm It is recommended that you use host type Linux for Linux on Power hosts connected to your storage subsystem. The failover driver recommendation is MPP/RDAC which requires that AVT be disabled. As with all NVSRAM changes from the default, anytime you download new NVSRAM you must re-enable the changes that you have made. In this case, you will have to re-run the AVT disable scripts. ========================================================================== 2.0 Installation and Setup Instructions ---------------------------------------------------- Note: The web-download Storage Manager version 9.23 host software package to support Linux on Power (LoP) servers must be first unpacked (tar - xvz) into a user-defined directory. Then, go to this directory, locate the LoP directory to access the Storage Manager version 9.23 host software installation file(s). 2.1 Readme files ------------------------ a. Determine the operating system of the management station that you will be installing this code on. b. Change to the appropriate directory on this CD (either WIN32, WS03_X86_32bit, Linux or AIX). c. Follow the instructions in that directory on how to install the IBM DS4000 Storage Manager version 9.xx Host Software. NOTE: For this release, please refer to the "IBM DS4000 Storage Manager Version 9 Installation and Support Guide for AIX, HP-UX, Solaris and Linux on POWER" located at http://www-1.ibm.com/servers/storage/support/disk/ for all installation and support notes pertaining to Linux on pSeries. Follow these instructions to get to the proper manual: Click the link for your DS4000 storage server. When the page opens, click the Download tab. Click the link for Current recommended Firmware and Storage Manager. The tables on the resulting page contain links to Storage Manager publications. 2.2 Supported Fibre Channel HBAs for Linux on POWER platforms only ------------------------------------------------------------------- IBM has tested configurations with the following Fibre Channel Host Bus Adapters with the stated adapter firmware and device driver versions: IBM Feature Code 6228, 6239, or 5716(6239-CR) IMPORTANT: See below for JS20 blades supported host bus adapters. HBA Firmware Minimum Levels for RedHat RHEL3-u8 ppc64 Linux (LoP): Driver: 7.3.6, elxlinuxapps-2.1a29-7.3.6-1-1.tar 1. FC 5716 F-code 1.91a5 2. FC 6239 F-code 1.91x4 3. FC 6228 F-code 3.93a0 4. FC 5758 F-code 2.10x8 5. FC 5759 F-code 2.10x8 HBA Firmware Minimum Levels for SLES 9-SP3 ppc64 Linux (LoP): Driver: 8.0.16.27 1. FC 5716 F-code 1.91a5 2. FC 6239 F-code 1.91x4 3. FC 6228 F-code 3.93a0 4. FC 5758 F-code 2.10x8 5. FC 5759 F-code 2.10x8 HBA Firmware Minimum Levels for RedHat RHEL4-u4 ppc64 Linux (LoP): Driver: 8.0.16.27 1. FC 5716 F-code 1.91a5 2. FC 6239 F-code 1.91x4 3. FC 6228 F-code 3.93a0 4. FC 5758 F-code 2.10x8 5. FC 5759 F-code 2.10x8 pSeries adapter code can be downloaded from: http://techsupport.services.ibm.com/server/mdownload2/download.html JS20 blades are supported with the stated adapter firmware and device driver versions as shown below: All supported Feature Codes with Firmware and driver versions listed below: HBA Firmware Minimum Levels for RHEL3u8 JS20 Linux (LoP): Firmware Version: 3.03.06 and above Driver version: 7.07.04b6 and later HBA Firmware Minimum Levels for SLES9-SP3 and RHEL4-u4 JS20 Linux (LoP): Firmware Version: 3.03.11 and above Driver version: 8.01.06 and later NOTE: JS20 blades have possible intermittent problems with Fibre Channel Expansion card NVRAM corruption. Symptoms are WWPN reverting back to default value. See Limitation section in this readme for more detail. 2.3 Helpful Hints ----------------------- 1. Please refer to the appropriate operating system readme file for specific helpful hints. These readme files can be found in the operating system (WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. 2. Running script files for specific configurations. Apply the appropriate scripts to your subsystem based on the instructions you have read in the publications or any instructions in the operating system readme file. A description of each script is shown below. - EnableAVT_Linux.script: The script will enable automatic logical drive transfer (ADT/AVT) for the Linux heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. (This script can be used for other host type if modifications are made in the script, replacing the Linux host type with the appropriate host type that needs to have AVT/ADT enabled) - DisableAVT_Linux.script: The script will disable the automatic logical drive transfer (ADT/AVT) for the Linux heterogenous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. (This script can be used for other host type if modifications are made in the script, replacing the Linux host type with the appropriate host type that needs to have AVT/ADT disabled) - EnableCntlReset.script: This script is to set the HostNVSRAMByte offset 0x1B of the LnxclVMWare host type NVSRAM region to 1 for enabling the propagation of the bus/target/LUN reset that one controller received to the other controller in a dual controller DS4K subsystem. - DisableCntlReset.script: This script is to set the HostNVSRAMByte offset 0x1B of the LnxclVMWare host type NVSRAM region to 0 for disabling the propagation of the bus/target/LUN reset that one controller received to the other controller in a dual controller DS4K subsystem. The default propagation of the bus/target/LUN reset setting for the LnxclVMWare host type is to enable it. This script should be used only when the following conditions are met. . The DS4000 storage subsystem did not have any LUNs mapped to any Linux hosts that are part of Linux cluster configuration. . The DS4000 storage subsystem did not have any LUNs mapped to any VMWare hosts. . The Linux hosts use Linux RDAC as multipath driver. . The host type of defined host ports/group is LnxclVMWare(LNXCL). Inappropriate use of this script might cause loss of access to the mapped LUNs from the VMware hosts or Linux hosts that are part of a Linux Cluster. ======================================================================= 3.0 Configuration Information ------------------------------------------ 3.1 Configuration Settings ------------------------------------- Please refer to the appropriate operating system readme file for specific configuration setting. These readme files can be found in the operating system (WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. Installation of the Emulex Application Kit, ElxLinuxApps-2.0a20-7.1.14- 1, on RHEL3 servers, automatically installs HBAnyware. HBAnyware interferes with unloading the lpfcdfc and lpfc modules. The work around for this is to either stop HBAnyware (/usr/sbin/HBAnyware stop) or uninstall the Application kit. ======================================================================= 3.2 Unsupported Configurations -------------------------------------------- Please refer to the appropriate operating system readme file for a list of unsupported configurations. These readme files can be found in the operating system WIN32, WS03_X86_32bit, Linux or AIX) directories on this CD. ======================================================================= 4.0 Unattended Mode --------------------- N/A ======================================================================= 5.0 WEB Sites and Support Phone Number ---------------------------------------- 5.1 IBM System Storage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 5.2 IBM System Storage™ Marketing Web Site: http://www.ibm.com/servers/storage/disk 5.3 If you have any questions about this update, or problem applying the update go to the following HelpCenter World Telephone Numbers URL: http://www.ibm.com/planetwide 5.4 The IBM Linux for pSeries web site: http://www.ibm.com/eserver/pSeries/linux IMPORTANT: You should download the latest version of the DS4000 Storage Manager host software, the DS4000 storage server controller firmware, the DS4000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. To be notified of important product updates, you must first register at the IBM Support and Download Web site: http://www.ibm.com/servers/storage/support/disk/ ======================================================================= 6.0 Trademarks and Notices ---------------------------- 6.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM FAStT System Storage™ the e-business logo xSeries pSeries HelpCenter Microsoft, Windows, and Windows NT are trademarks of Microsoft 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. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Other company, product, and service names may be trademarks or service marks of others. ======================================================================= 7.0 Disclaimer ---------------- 7.1 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. 7.2 Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.