IBM System Storage™ DS4000 Storage Manager version 9.16 for the 32bit and 64bit version of Linux operating systems Note: Linux host attachment to the DS4800, DS4300 and DS4100 requires the additional purchase of the IBM DS4800/DS4300/DS4100 Host Kit Option or Feature Code. The IBM Linux Host Kit Option contains the required IBM licensing to attach a Linux Host System to the DS4800, DS4300 or DS4100. Please contact your IBM service representatives or IBM resellers for purchasing information. IMPORTANT: This IS NOT the correct DS4000 Storage Manager version 9.16 host software package FOR LINUX ON IBM pSERIES SERVERS. Please refer to the DS4000 Storage Manager version 9.16 Linux on Power host software package for the host software package for IBM pSeries server that is running Linux operating system. NOTE TO SERVICE – Reference RETAIN # N/A (C) Copyright International Business Machines Corporation 1999, 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 in "Notices and trademarks” in this document. Microsoft Windows Notepad might not view this readme properly, if you must view this on a Windows system use Wordpad instead to view this readme. Refer to the IBM System Storage™ Support Web Site or CD for the IBM DS4000 Storage Manager version 9 Installation and Support Guides for Windows 2000/Server 2003, Netware, ESX Server, and Linux. This guide along with the DS4000 Storage Manager program Online Help provide the installation and support information. This guide also provides information on other DS4000 related publications. Last Update: 02/13/2006 Products Supported ================== ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4800 | N/A | 1815 | 82H, 82A, 84H, 84A, 88A| | | | | 88H | |------------|-----------|--------------|------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | FAStT 600 | 1722 | 6LX, 6LU, 6LJ, 60X | | | | | 60U, 60J, 60K, and 60L | |------------|-----------|--------------|------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | |----------- |-----------|--------------|------------------------| | N/A | FAStT 500 | 3552 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | N/A | FAStT 200 | 3542 | 1RX, 1RU, 2RX and 2RU | ------------ --------------------------------------------------- ATTENTION: - 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. - For the DS4300 with Standard(base) or Turbo options, the DS4400 and the DS4500 storage subsystems connected to the DS4000 EXP100 drive expansion enclosures, the latest controller firmware version 06.12.xx.xx and its associated NVSRAM file must be used. In addition, the DS4100 storage server - all models (Standard/dual-controller and Single Controller) are now supporting the controller firmware version 06.12.xx.xx. - 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.1x.xx.xx into these DS4300 storage subsystem models with single controller option. - 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.1x.xx.xx into these DS4000 storage subsystems. Linux kernels Supported: ======================== ----------------------------------------------------------------- | RedHat 3 IA-32 | 2.4.21-37.EL UP SMP | | | | |--------------------------------|--------------------------------| | RedHat 3 IA-64 | 2.4.21-37.EL UP SMP | | | | |--------------------------------|--------------------------------| | RedHat 3 AMD-64/EM64T | 2.4.21-37.EL UP SMP | | (x86 and x86_64 versions) | | |--------------------------------|--------------------------------| | RedHat 4 IA-32 update 1 | 2.6.9-22.EL UP SMP | | | | |--------------------------------|--------------------------------| | RedHat 4 IA-64 update 1 | 2.6.9-22.EL UP SMP | | | | |--------------------------------|--------------------------------| | RedHat 4 AMD-64/EM64T update 1 | 2.6.9-22.EL UP SMP | | (x86 and x86_64 versions) | | |--------------------------------|--------------------------------| | SuSe SLES 8 | 2.4.21-295 UP SMP | | 32-bit | | |--------------------------------|--------------------------------| | SuSe SLES 8 | 2.4.21-295 UP SMP | | IA-64 | | |--------------------------------|--------------------------------| | SuSe SLES 8 | 2.4.21-295 UP SMP | | AMD-64 (x86 version only) | | |--------------------------------|--------------------------------| | SuSe SLES 9 SP2 | 2.6.5-7.191 UP SMP | | 32-bit | 2.6.5-7.201 UP SMP | |--------------------------------|--------------------------------| | SuSe SLES 9 SP2 | 2.6.5-7.191 UP SMP | | IA-64 | 2.6.5-7.201 UP SMP | |--------------------------------|--------------------------------| | SuSe SLES 9 AMD-64/EM64T SP2 | 2.6.5-7.191 UP SMP | | (x86 and x86_64 versions) | 2.6.5-7.201 UP SMP | ----------------------------------------------------------------- Earlier or later versions of the vendor kernels or generic kernels might not been tested with this DS4000 Storage Manager version 9.16 and might not be supported with this release. IN ADDITION, REDHAT ADVANCE SERVER 2.1 KERNELS ARE NOT SUPPORTED WITH THIS RELEASE (VERSION 9.16) OF THE DS4000 STORAGE MANAGER HOST SOFTWARE FOR LINUX OPERATING SYSTEM. PLEASE CONTACT IBM FOR THE AVAILABILITY OF SUCH SUPPORT IN THE FUTURE. Note: The only SLES 8 OS kernels that are supported are of x86(IA-32) and IA-64 versions. Hardware Platform Supported =========================== ---------------------------------------------------------- | Hardware Platform | IA-32 | IA-64 | EM64T | AMD64 | | supported | | | | | |--------------------------|-------|-------|-------|-------| | RHEL 3 and 4 | Y/na | na/Y | Y/Y | Y/Y | | RDAC Multipath Driver | Y/na | na/Y | Y/Y | Y/Y | | Qlogic Multipath Driver| Y/na | na/Y | Y/Y | Y/Y | |--------------------------|-------|-------|-------|-------| | SLES 8 | Y/na | na/Y | Y/N | Y/N | | RDAC Multipath Driver | Y/na | na/Y | Y/N | Y/N | | Qlogic Multipath Driver| Y/na | na/Y | Y/N | Y/N | |--------------------------|-------|-------|-------|-------| | SLES 9 | Y/na | na/Y | Y/Y | Y/Y | | RDAC Multipath Driver | Y/na | na/Y | Y/Y | Y/Y | | Qlogic Multipath Driver| Y/na | na/Y | Y/Y | Y/Y | ---------------------------------------------------------- Legend: - 32 bit OS version/64 bit OS version (either IA-64 or X86_64 version) - Y=supported, N=not supported, n/a=not applicable ======================================================================= 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 is the latest release of the IBM DS4000 Storage Manager host software for Linux Operating System environments. This version of the DS4000 Storage Manager host software is required for managing the DS4800 storage subsystems with controller firmware version 06.15.xx.xx or 06.16.xx.xx. It is also required for managing the following DS4000 storage subsystems - the DS4100 with standard (dual controller) or single-controller option, the DS4300 with standard (base) or Turbo options, the DS4400 and the DS4500 - with controller firmware version 06.12.xx.xx installed. NOTE: The DS4800 controller firmware version 06.16.xx.xx is required to support EXP810 drive expansion enclosures. Whereas the DS4800 controller firmware version 06.15.20.xx is required to support EXP100 SATA drive expansion enclosures. The IBM Storage Manager host software version 9.16 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. The Linux and Linux_IA64 web packages contain the files that are necessary for installing the IBM DS4000 Storage Manager version 9.16 Host Software for the Intel Architecture 32bit (IA-32) and the Intel Architecture 64bit (IA-64) Linux operating systems, respectively. The same host software in the Linux web package should also be used for the AMD64 and EM64T servers running either x86 (32 bit IA32) or x86_64 (64 bit) versions of the Linux operating system kernel. The DS4000 storage subsystem controller Firmware and NVSRAM files are located in the FIRMWARE and NVSRAM CD-ROM directories. These host software packages and the DS4000 storage subsystem firmware files are also available for download from the IBM System Storage™ DS4000 Support web site - http://www.ibm.com/servers/storage/support/disk/ Note: This is not the correct DS4000 Storage Manager version 9.16 host software package for Linux on IBM pSeries servers. Please refer to the "DS4000 Storage Manager version 9.16 Linux on Power host software package" for the DS4000 storage manager host software package for IBM pSeries server that is running Linux operating system. The IBM System Storage DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux is also available on the IBM System Storage™ Disk Storage Systems Technical Support web site as a downloadable Portable Document Format (PDF) file. It contains the instructions for installing the IBM DS4000 Storage Manager host software for Linux. In addition, the Docs directory in the DS4000 Storage Manager Version 9.16 Support for Linux CD-ROM also contains others DS4000 publications that provide helpful information. The latest versions of these files are available on IBM System Storage™ DS4000 Support web site as PDF files. IMPORTANT: This release of IBM DS4000 Storage Manager host software supports all DS4000 storage subsystems with general released firmware versions from 04.01.xx.xx up to 06.16.xx.xx. Refer to the IBM DS4000 Support Web Site for latest DS4000 controller firmware and NVSRAM files for IBM machine types 1722, 1724, 1742, 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. --------------------------------------------------- | | Controller firmware version | |------------------|--------------------------------| | DS4000 | | | storage subsystem| | | Model | | |------------------|--------------------------------| | DS4800 (1815) | 06.15.xx.xx and 6.16.xx.xx | | | (See note below) | |------------------|--------------------------------| | DS4500 (1742) | 06.12.1x.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.1x.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.12.1x.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.12.1x.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4300 Single | 05.34.xx.xx | | Controller Opt. | (for DS4300 SCU | | (1722) | only) | |------------------|--------------------------------| | DS4100 (1724) | 06.12.1x.xx | | (standard dual | | | controller Opt.)| | | | | |------------------|--------------------------------| | FAStT500 (3552) | 05.30.xx.xx | |------------------|--------------------------------| | FAStT200 (3542) | 05.30.xx.xx | --------------------------------------------------- Note: Controller firmware 06.16.xx.xx does not support EXP100 storage expansion enclosures. Do not download it into DS4000 storage subsystems that have EXP100 enclosures attached. For the DS4800 storage subsystems with EXP100 SATA drive expansion enclosures attached, use the controller firmware version 6.15.xx.xx instead. Note: New features that are introduced with the controller firmware version 06.16.xx.xx or later will not be available for any DS4000 storage subsystem controllers without the controller firmware version 06.16.xx.xx installed. Similarly, new features that are introduced with the controller firmware version 06.12.xx.xx or later will not be available for any DS4000 storage subsystem controllers without the controller firmware version 06.12.xx.xx installed. ======================================================================= 1.2 Limitations --------------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by the DS4000 storage subsystem controller firmware and Storage Manager host software releases to indicate which controller firmware and Storage Manager host software release that they were first seen and documented. New limitations with Storage Manager Installer (SMIA) package version 09.16.xx.08 release for the DS4000 controller firmware version 6.16.24.xx 1. Controller firmware 06.16.xx.xx does not support EXP100 storage expansion enclosures. Do not download it into DS4000 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.15.xx.xx and earlier must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 2. 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 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. 3. 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. 4. 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. 5. 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. 6. A JavaScript error might cause the Glossary pop-up window to stay open when the help contents on the storage management software GUI are closed and reopened. Workaround None. This is a SUN JAVA defect. 7. Sometimes when there are two Linux hosts connecting to the same storage subsystem, they are displayed in the Enterprise Management Window as a single node, showing the IP addresses of both Linux hosts rather than displaying them as separate host nodes. As a single node, it is not possible to remove just one of the hosts. The workaround is If the host has a static IP address, then modify the /etc/hosts file to map the host name to the host address. For more information, refer to http://bugs.sun.com/bugdatabase/ view_bug.do?bug_id=4665037. 8. Root Boot fails when QLogic HBA port 1, instead of port 0, is connected to a target during the installation of the operating system. With this hardware setup, the operating system gives you the option to load the Master Boot Record to /dev/sdb. The QLogic HBA driver skips the scan of /dev/sda/. If you accept this option and install the operating system on /dev/sdb, root boot will fail after the operating system is installed. This action occurs because the host will try to scan for the operating system at /dev/sda when it is actually loaded on /dev/sdb instead. The workaround is if QLogic HBA port 1, instead of port 0, is connected to a target when performing a root boot installion the operating system, make sure that the Configure Advanced Boot Loader option box is checked on the Boot Loader Configuration window. Edit the settings in the Change Drive Order window by prioritizing /dev/sdb as the boot device instead of /dev/sda. 9. After you select a file on the firmware download or NVSRAM download dialog, double clicking on “..” in the dialog no longer moves the directory back one level. The workaround is do not select a firmware file until you are finished navigating through your directory structure. 10. (Linux 2.4 Kernel) In Linux, the SCSI device discovery operation scans all contiguous LUNs and stops scanning after a break in the numbers. For example, if LUNs 0, 1, 2, 3, and 7 are being used, 0 through 3 will be scanned and 7 will be skipped. This scenario will cause several problems: • Hosts will not have access to any logical drives associated with skipped LUNs. • SMagent will be stopped at boot time if it does not detect an access logical drive (LUN 31) in the block of contiguous LUNs. • SMdevices will not be able to report on logical drives associated with any skipped LUNs. The workaround is to run hot_add to force the operating system to discover the skipped LUNs. NOTE: The hot_add utility is included with the SANtricity Storage Manager RDAC package for Linux. New limitations with SMIA package version 09.15.xx.06 release for DS4000 controller firmware version 06.12.xx.xx and 06.15.xx.xx release 1. 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 desire 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). New limitations with SMIA package version 9.15.xx.xx and DS4000 controller firmware version 06.15.xx.xx release 1. The Red Hat Enterprise Linux 4 operating system cannot load the HBA driver after the kernel is upgraded to a later version. When the Red Hat Enterprise Linux 4 operating system is initially installed, the installation creates a symbolic link to the kernel source tree. When a kernel is upgraded to a later version, the operating system does not create the symbolic link, which prevents the HBA driver from loading. The workaround is to create symbolic links similar to the following: ln -s /usr/src/kernels/2.6.9-5.EL-ia64/ build ln -s build/ source (added 2/10/2006) New limitations with SMIA package version 9.14.xx.05 and DS4000 controller firmware version 06.14.xx.xx release None New limitations with SMIA package version 9.12.xx.08 and DS4000 controller firmware version 06.12.03.xx release 1. Do not cut and paste the information in the DS4000 Storage Manager online help into the DS4000 Storage Manager script command window or into the text file that will be used as input for the SMcli script engine. Extra space may be inserted in the required parameter names which will cause error(s) during the script command execution. (267873) 2. In the configuration that have both SATA-technology drives (EXP100) and Fibre-Channel technology drives (EXP700/EXP710/DS4100) behind the same DS4000 storage subsystem, do not download drives firmware to both SATA-technology drives and Fibre-Channel(FC) technology drives at the same time. Download the drive firmware to drives of a single drive technology (either SATA or FC) at a time. 3. Currently, IBM does not support Gold key Premium Feature as a chargeable upgrade. The Gold key Premium Feature is enable or disable depending on the DS4000 storage subsystem models. 4. The Asynchronous Remote Mirroring utility, asyncRVMUtil, is not supported. This utility is used to automatically synchronize the logical drives in the Remote Mirroring pairs. Please contact IBM representatives or resellers for the support of this utility in the future. 5. The SMclient, SMUtil and SMAgent programs are installed into the /opt/IBM_FAStT directory instead of the /opt/IBM_DS4000 directory. This defect is fixed in the Storage Manager version 9,15 and later releases. 6. Do not add drive expansion enclosure(s) to the DS4000 storage subsystem drive loops/channels during the ESM firmware download. The ESM firmware download process might fail due to a disconnected FC loop. Either add the drive expansion enclosure(s) before initiating the ESM firmware download or wait until the ESM firmware download is completed before adding additional drive expansion enclosures to the drive loop/channel. (added 2/10/2006) 7. Small Form-factor Pluggable (SFP) hardware that is removed and then reinserted within 10 seconds might not be recognized by the controller. Device polling is done at 10-second intervals. Any device that is removed and replaced within the 10-second window will not be recognized. After removing SFP hardware, ALWAYS wait at least 20 seconds before replacing or reinserting it. (added 2/10/2006) 8. When connected through the DS4000 Storage Manager Agent and mapped volumes using Storage Partitioning on an in-band managed storage subsystem, the following error message might appear after a successful volume-to-LUN mapping operation: Error 62 - The operation cannot complete because the logical unit number (LUN) is already in use. Please enter another LUN. Verify that the volume-to-LUN mapping was created correctly. If it was, this error is erroneous and can be ignored. (added 2/10/2006) 9. After you disable a premium feature, the Disable Premium Feature dialog might go blank and no longer show any other enabled premium features to select. The workaround is to close and then re-open the dialog. (added 2/10/2006) 10. When Linux hosts that are configured with QLogic HBA drivers attempt to allocate DMA-capable memory by way of the kernel’s pci_alloc_consistent( ) function, the allocation sometimes fails. There is no workaround. (added 2/10/2006) 11. Linux hosts that are configured with SteelEye® LifeKeeper® cluster version 4.4.3 might lock up due to Error No Memory (ENOMEM) problems. The error messages, located in the /var/log/messages file are displayed as follows: ENOMEM in journal_alloc_journal_head, retrying The workaround is to use only one resource (two LUNs). (added 2/10/2006) New limitations with Storage Manager version 9.10.xx.05 and DS4000 controller firmware version 06.10.11.xx release 1. Do not update the DS4000 storage subsystem controller firmware to version 06.1x.xx.xx from versions 05.4x.xx.xx or earlier if the EXP700 ESM firmware of the attached exp700 was not at 9326 or higher. If the EXP700 ESM firmware is earlier than the 9326 versions, the EXP700 enclosure and the installed drives may not be displayed in the DS4000 subsystem management window after the controller firmware is upgraded to 06.1x.xx.xx version. The workaround is to update the EXP700 ESM firmware to the version 9326 or higher first, before upgrading the controller firmware to version 06.1x.xx.xx. (260160 - 82841) 2. When connecting the EXP100 drive expansion enclosures, one must set the single digit (X1) of the enclosure ID to unique values. This is to prevent the possibility that one of the drives in the EXP100 enclosures be assigned the same ALPA as the DS4000 controller blade under certain DS4000 storage subsystem reboot scenarios. (261188) 3. There are not DS4000 Storage Manager version 9.12 Linux host software packages for AMD-64 or EM64T servers running Linux OS kernels written in native AMD-64 or EM64T code. Please contact IBM resellers or representatives for availability of such support in the future. This limitation was fixed in the DS4000 Storage Manager host software for Linux version 9.15 and later release. 4. In Redhat EL 3.0 Update 3 environment, when there are memory intensive applications running, RHEL 3.0 kernel may not process the memory request from the running device driver processes like network driver or Linux RDAC driver. In certain case, this denial of memory request to the RDAC driver cause it to loop in the memory request routine indefinitely. In that case, the /var/log/messages will be full with the messages like the ones shown below kernel: 493 [RAIDarray.mpp] Cmnd failed-retry 0:0:0 the same path vSCp SN 13633729 TOLO pcmnd SN HOCOTOLO or kernel: 494 [RAIDarray.mpp] Cmnd-failed try alt ctrl 0 vcmnd SN 13799399 TOLO pcmnd SN H1COTOLO The recovery procedure is to reboot the server. (261523) 5. Do not hot swap an HBA in a Linux host while I/O activity is present. If the data path on the to-be-hot swapped HBA is active, place the controller attached to the HBA into service mode to transfer volume ownership to the other controller. Then perform the hot swap of the HBA after the data path is inactive. New limitations with Storage Manager version 9.10.xx.02 and DS4000 controller firmware version 06.10.06.xx release 1. The DS4000 Copy Service RVM is not supported at this time for the DS4100 and the DS4300 storage subsystem with Standard or Single Controller options. (Note: With the release of the controller firmware version 06.12.16.00 or higher, the DS4100 with standard option is now supported Copy Service Remote Mirroring and VolumeCopy premium features.) 2. In the Storage Manager version 9 client Subsystem Management window, the preferred owner of a defined logical drive can not be changed if the logical drive is not managed by the preferred owner/controller. The Storage Manager client will grey-out (not allowing one to select) the controller that is currently managing the logical drive in the selection list of the new preferred owner/controller. One is allowed to only select the controller that is not managing the logical to be the new preferred owner. There is no work-around. 3. Concurrent firmware download (downloading firmware/NVSRAM to the DS4000 storage subsystem controllers with IOs to the host servers) is not supported when upgrading the controller firmware from a 05.xx.xx.xx version to a 06.1x.xx.xx version. ALL IOs must be stopped during the version 06.1x.xx.xx controller firmware upgrade from a 05.xx.xx.xx version. 4. Do not pull or insert drives during the drive firmware download. In addition, ALL IOs must also be stopped during the drive firmware download. Otherwise, drives may be shown as missing, unavailable or failed. 5. Controller diagnostics will not run in a DS4000 storage subsystem with single controller. 6. When instructed to remove and reinsert or to replace a hard drive, wait at least 70 seconds before inserting either the removed existing drive or the new drive into the drive slot. Then, wait up to 3 minutes for the drive to be spun up, recognized by the DS4000 storage subsystem and displayed in the Subsystem Management window before repeating the process for another hard drive. There is no work-around. Similarly, wait at least 70 seconds before reinserting either the removed existing ESM module or the new ESM module into the empty ESM slot in the EXP drive expansion enclosure. Then, wait up to 3 minutes for the ESM CRU to be recognized by the DS4000 storage subsystem and displayed in the Subsystem Management window before repeating the process for another ESM. There is no work-around. 7. Staged firmware and NVSRAM download function is not available on the DS4400 (machine type 1742) models with firmware 06.1x.00.00 in conjunction with IBM Storage Manager 09.1x.xx.xx." 8. The transmission of the User Datagram Protocol (UDP) broadcast message that starts auto discovery may be blocked because of a configuration issue. The storage management software uses UDP at the broadcast IP address 255.255.255.255. The system must be configured to allow broadcast messages for auto discovery to work. The work-around is to manually add storage arrays via their IP address or host name or add the following command to enable the broadcast address on that Ethernet port and allow normal auto discovery to proceed. For example, route add -host 255.255.255.255 eth0 9. The DS4000 Storage Manager client crashes on Linux, AMD-based, 64-bit server because support for the “no execute” bit is enabled by default. To fix the problem, one need to disable support for the "no execute" bit in the operating system by editing the /etc/grub.conf file (if you are using GRUB to boot), and add the following parameter to the end of the kernel line: noexec=off For example, in Red Hat Enterprise Linux AS, you would add noexec=off to the end of the kernel line in the grub.conf file as shown here: kernel /boot/vmlinuz-2.4.21-15.ELsmp ro root=LABEL=/ hdc=ide-scsi noexec=off After adding this information, reboot the server. 10. QLogic Multipath failover driver will not work while the controllers are in service mode because QLogic Multipath failover driver relies on Automatic Logical Drive/Volume Transfer (ADT/AVT) to move the logical drives to the controller that receives the I/O requests. When a controller is in service mode, the controller is not capable of successfully completing the I/O requests. Since the path to that controller is not "broken," QLogic Multipath failover driver has no knowledge to fail over to the alternate controller. The I/O request gets retried repeatedly until the I/O timeout period has been reached and the request times out. IBM recommends the use of Linux RDAC as the DS4000 storage subsystem multipath driver in Linux OS environment. Limitations with Storage Manager version 8.4x.xx.xx (and earlier) and DS4000 controller firmware version 05.4x.xx.xx (and earlier) releases 1. In the DS4000 Storage Manager 9.12 Client, Storage Partitioning must be enabled with the host type of 'linux' selected and the UTM must be removed from the 'Linux' storage partition when the IBM FC HBA failover Linux device driver is used as multipathing (failover/ failback) driver. Otherwise the correct drive information is not presented to the Linux operating system. Note: When using the Linux RDAC as the multipathing driver, the "LNXCL" host type must be used and there is not a requirement that the UTM(Access LUN) must be removed from the LNXCL Storage Partitioning partition. 2. When updating Firmware or NVSRAM with high disk activity a controller may become unresponsive during the update. IBM recommends that disk I/O be stopped during these code updates. 3. When creating a Remote Mirror of a base logical drive, in the case where a FlashCopy of the base logical drive has already been created, the following restriction applies. If the Remote Mirror relationship is created while the base logical drive is receiving I/O, the FlashCopy logical drive will be failed. The work around is to quiesce I/O to the base logical drive while you are creating the remote mirror relationship. Alternatively, if the Remote Mirror relationship is created before creating the FlashCopy logical drive, the FlashCopy logical drive will not be failed. 4. This following behavior applies for the direct Fibre Channel connection setup between the DS4300 storage subsystem host ports and the server HBA ports only. If all DS4300 host ports are occupied, the DS4300 event log may show "host-side data rate negotiation failed" error when the server is booted up, this is normal error that were generated during the host rate negotiation routine inside the DS4300 storage subsystem. 5. When managing the DS4000 storage subsystems with firmware version 05.3x.xx.xx, the Help window of the Subsystem Management window may not be displayed correctly the topics that are listed as result of executing a full text search. 6. The DS4000 storage subsystem when configured with the DS4000 EXP100 SATA Drive Expansion Unit is currently reporting a higher frequency of informational events such as Destination Driver Events (DDEs) and Fibre Channel link up/down events ... in the DS4000 Controller event log compared to the DS4000 storage subsystem configured with Fibre Channel drives. Slower response times of SATA disk drives compared to Fibre Channel disk drives cause higher I/O retries from the DS4000 storage server controllers, resulting in a greater number of informational events logged. In addition, the number of information events reported in the DS4000 storage subsystem event log will also grow in proportion to the increase in I/Os to the Logical Drives. In all cases, the DS4000 storage subsystem controller will always successfully service the timeout I/O on the subsequent retries. 7. When migrating array(s) from a dual controller DS4000 storage subsystem to a single controller DS4000 storage subsystem, you must first set the preferred owner of the to-be-migrated array(s) to be controller A before inserting it into the drive slots of a single controller DS4000 storage subsystem. Otherwise, the array(s) will not be added to the single controller DS4000 storage subsystem correctly which might cause problems. 8. When managing a single controller DS4000 storage subsystem model, do not use the menu option - Configuration->Automatic... - in the Subsystem Management window to create LUNs. You might not be able to access or manage LUNs that are created this way. 9. After you replace a controller with a new controller in the single controller models of DS4000 storage subsystems, the premium features become unauthorized and are out of compliance. Any premium features not supported by the firmware of the new controller are unavailable. The work-around is to upgrade the firmware in the new controller to the same level as the removed controller and re-enable the premium features using the key files that you were provided when the premium feature was originally enabled. 10. When migrating drive Customer Replaceable Units (CRUs) from multiple DS4000 storage subsystems into a single destination DS4000 storage servers, all of the drive CRUs from the same DS4000 storage subsystem should be moved as a ‘set’ into the new destination DS4000 storage server. Before moving the next ‘set’ of drive CRUs, ensure that all of the drive CRUs for a single ‘set’ have been moved to the destination DS4000 storage subsystem. If drive CRUs are not moved as a ‘set’ to the destination DS4000 storage subsystems, the newly relocated array may not appear in the Subsystem Management window. 11. Enclosure IDs may be listed incorrectly in the Subsystem Management window, even if the Enclosure ID switch settings appear to be correct. This is because of the physical design and movement of the Enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which will return an incorrect Enclosure ID (this value is 0 in most cases) to the storage management software. When setting the Enclosure ID, ensure that the switch has actuated completely and has settled where the value is clearly visible in the viewing window. 12. To download controller firmware, you must select the drive where the firmware is located. If the drive you select does not respond, the File Selection dialog box will revert to the A: drive and display an error message that drive A: is not ready if there are no media in drive A:. 13. You must suspend all I/O while ESM firmware downloads if you select multiple enclosures for downloading ESM firmware. If you select only one enclosure for download at a time, you can download ESM firmware with I/Os. However, IBM recommends that you suspend all I/O activity to perform firmware upgrades. 14. If the EXP100 ESM firmware version is 953x or earlier, no IOs are allowed during the duration that the EXP100 ESMs are being updated with new firmware, including clustering reservation checking IOs. 15. When saving the DS4000 storage subsystem event log entries, it may take up to several minutes to save all entries in the event log depending on the DS4000 management workstation resources. However, the DS4000 Storage Manager client GUI will show the completion of the event log saving almost instantly. The work around is to check the file size of the file that the event log entries are saved periodically; if the file size does not change, the event log saving is completed. 16. Do not perform other storage management tasks, such as creating or deleting logical drives, reconstructing arrays, and so on, while downloading the DS4000 storage subsystem controller firmware and DS4000 EXP100 ESM firmware. It is recommended that you close all storage management sessions (other than the session that you use to upgrade the firmware) to the DS4000 storage subsystem that you plan to update. 17. Inter-operability with tape devices is supported on separate HBA and switch zones. ======================================================================= 1.3 Enhancements --------------------------- The DS4000 Storage Manager 9.16 for Linux operating systems (in conjunction with the DS4000 storage subsystem controller firmware 06.16.xx.xx) provides support for attachment of DS4000 EXP810 Storage Expansion Enclosures to the DS4800 Storage Subsystems. It also supports automatic ESM firmware synchronization feature of the new EXP810 storage expansion enclosure. When you install a new ESM into an existing EXP810 enclosure that is attached to a DS4000 storage subsystem that supports automatic ESM firmware synchronization, this feature resolves firmware mismatch conditions by automatically synchronizing the firmware in the new ESM with the firmware in the existing ESM. Please refer to the New Features section of the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux for additional information about the IBM DS4000 Storage Manager version 9 enhancements. ======================================================================= 1.4 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- Note: The IBM Storage Manager host software version 9.16 for 32bit (IA32) and 64bit (IA64 and x86_64) 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. IBM xSeries and other Intel-based 32 bit servers with minimum 1024MB Memory with 512 KB L2 Cache Pentium II 450Mhz processor minimum or any AMD64 or EM64T processor architecture servers with a minimum of 512MB Memory. The servers must have the appropriate version of x86 or x86_64 versions of Linux OS installed. (also see Dependencies section) Code levels at time of release are as follows ------------------------------------------------------------------ IMPORTANT: There are two separate IBM DS4000 Storage Manager host software version 9.16 packages for the 32bit X86 and 64bit x86_64 and the 64bit IA64 Linux operating system environments. Please download the correct one for your operating system environment. Starting with the DS4000 storage manager version 9.16, all of the host software packages (SMruntime, SMclient, SMutil and SMagent) are included in a single DS4000 Storage Manager host software installer wizard. During the execution of the wizard, the user will have a choice to install all or only certain software packages depending the need for a given server. Note: The Linux RDAC package is not part of this installer wizard. It must be installed separately, if needed. For Linux servers without the graphics adapter, individual host software installation packages are provided in the DS4000 Storage Manager Version 9.16 Support for Linux OSes CD under the directory named "/Linux/Individual packages" or "/Linux_IA64/Individual packages". These individual host software installation packages can also be downloaded at the IBM System Storage™ Disk Storage Systems Technical Support web site. - For 32bit Intel architecture (IA-32) servers OR AMD64 and EM64T processor architecture servers having either the x86(IA-32) OR x86_64(64 bit AMD64 and EM64T) versions of Linux OS installed. Note: There is not support for x86_64 version of SuSe SLES 8 Linux OS. The version of the host software installer wizard for this release is SMIA-LINUX-09.16.A5.08.bin. IMPORTANT: The DS4000 Storage Manager host software installer wizard requires the installation of a graphics adapter in the Linux server for it to run. The packages will be installed in the /opt/IBM_DS4000 directory. This installer wizard will install the following version of the host- software packages SMruntime: 09.16.A5.00-1 SMclient: 09.16.G5.08-1 SMutil: 09.16.A5.00-1 SMagent: 09.16.A5.00-1 Note: The SMagent package can be installed when the Linux RDAC is configured as multipath (Failover/Failback) driver. It should not be installed if the IBM FC HBA Linux failover device driver is used as multipath driver. The DS4000 Storage Manger version 9 supports both Linux RDAC and the IBM FC HBA Linux failover device driver as the multipath failover/failback driver for the DS4000 storage subsystem logical drives. When using Linux RDAC driver as the multipath failover/failback driver, the non-failover version of the Linux FC HBA device driver must be installed instead of the failover version. The minimum DS4000 controller firmware version that the Linux RDAC driver supported was 05.4x.xx.xx. You must select one of the two options and refer to the README that are part of the Linux RDAC and the IBM FC HBA Linux failover device driver packages for installation instructions. The latest version of these drivers are as follows: - IBM FC HBA Linux failover device driver: 7.05.00 (for 2.4 kernel) 8.00.02 (for 2.6 kernel) - IBM DS4000 storage subsystem Linux RDAC: 09.00.A5.13 (for 2.4 kernel only) rdac-LINUX-09.00.A5.13-source.tar.gz 09.01.B5.21 (for 2.6 kernel only) rdac-LINUX-09.01.B5.21-source.tar.gz - For Intel architecture 64bit version (IA-64) servers ONLY. These host software packages are not for the AMD64 or EM64T servers that have the native AMD64 or EM64T code version (x86_64) of Linux OS kernel installed. The version of the host software installer wizard for this release is SMIA-LINUX64-09.16.A5.08.bin. IMPORTANT: The DS4000 Storage Manager host software installer wizard requires the installation of a graphics adapter in the Linux server for it to run. The packages will be installed in the /opt/IBM_DS4000 directory. This installer wizard will install the following version of the host- software packages SMruntime: 09.16.A5.00-1 SMclient: 09.16.G5.08-1 SMutil: 09.16.A5.00-1 SMagent: 09.16.A5.00-1 Note: The SMagent package can be installed when the Linux RDAC is configured as multipath (Failover/Failback) driver. It should not be installed if the IBM FC HBA Linux failover device driver is used as multipath driver. The DS4000 Storage Manger version 9 supports both Linux RDAC and the IBM FC HBA Linux failover device driver as the multipath failover failback driver for the DS4000 storage subsystem logical drives. When using Linux RDAC driver as the multipath failover/failback, the non-failover version of the Linux FC HBA device driver must be installed instead of the failover version. The minimum DS4000 controller firmware version that the Linux RDAC driver supported was 05.4x.xx.xx. You must select one of the two options and refer to the README that are part of the Linux RDAC and the IBM FC HBA Linux failover device driver packages for installation instructions. The latest version of these drivers are as follows: - IBM FC HBA Linux failover device driver: 7.05.00 (for 2.4 kernel) 8.00.02 (for 2.6 kernel) - IBM DS4000 storage subsystem Linux RDAC: 09.00.A5.13 (for 2.4 kernel only) rdac-LINUX-09.00.A5.13-source.tar.gz 09.01.B5.21 (for 2.6 kernel only) rdac-LINUX-09.01.B5.21-source.tar.gz 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. ======================================================================= 1.5 Dependencies -------------------------- ATTENTION: 1. DS4000 storage subsystem CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP700 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 9326 OR HIGHER. IF THE EXP700 ESM FIRMWARE IS EARLIER THAN THE 9326 VERSIONS, THE EXP700 ENCLOSURE AND THE INSTALLED DRIVES MAY NOT BE DISPLAYED IN THE DS4000 SUBSYSTEM MANAGEMENT WINDOW AFTER THE CONTROLLER FIRMWARE IS UPGRADED. THE CURRENT RELEASE ESM FIRMWARE VERSION FOR THE EXP700 ESM IS 9327. 2. DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X WHEN THE CONTROLLER FIRMWARE IS AT 06.1X.XX.XX. TO DETERMINE THE FIRMWARE LEVEL OF AN EXP100 ESM, IDENTIFY THE PRODUCT LABEL LOCATED AT THE REAR OF THE EXP100 ENCLOSURE. ONLY LABELS ON WHICH THE FIELD REPLACEABLE UNIT (FRU) PART NUMBER READS 25R0156 POSITIVELY INDICATE THAT AN ESM MODULE IS RUNNING FIRMWARE VERSION 955X OR HIGHER. IF THERE IS NO LABEL OR THE PART NUMBER ON THE LABEL DOES NOT READ 25R0156, THE ESM MAY STILL HAVE THE FIRMWARE VERSION 955X OR HIGHER IF IT HAD BEEN PREVIOUSLY UPGRADED. IF NECESSARY, CONTACT YOUR IBM REPRESENTATIVE, SUPPORT, OR RESELLERS FOR ASSISTANCE. IN ADDITION, IT IS NOT POSSIBLE TO UPGRADE THE ESM FIRMWARE FROM VERSION 953X TO VERSION 956X OR LATER DIRECTLY. THE 953X ESM MUST BE UPGRADED TO VERSION 9554 FIRST BEFORE IT CAN BE UPGRADED TO VERSION 956X. 3. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED BY THE 06.12.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 - ALL MODELS, THE DS4300 WITH STANDARD (BASE) OR TURBO OPTIONS, THE DS4400 AND THE DS4500. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM. 4. The only DS4000 storage subsystems that are supported by the 06.14.xx.xx or 06.15.xx.xx controller firmware version are the DS4800 storage subsystems. Currently, there are not any controller firmware packages version 06.14.xx.xx or 06.15.xx.xx for other DS4000 storage subsystems besides the DS4800 subsystems. Do not download this controller firmware on any other DS4000 storage subsystems. 5. 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 subsystem controller and the hard drive firmware. 6. If the managed DS4000 storage subsystem had the FC/SATA intermix premium feature enable, do not upgrade the controller firmware from version 06.10.xx.xx to version 06.12.xx.xx until a FC/SATA intermix premium feature key file is generated and available. Once the controller firmware is upgraded to version 06.12.xx.xx, the FC/SATA intermix premium feature will be shown as out-of-compliance and the FC/SATA intermix premium feature key file is required to re-enable the feature. When the FC/SATA intermix premium feature is in out-of- compliance state, LUNs management functions like creations, deletions and modifications will not be operational. Please refer to the FC/SATA intermix premium feature activation card that was shipped with the FC/SATA intermix premium feature kit for instructions to generate the required premium key file. 7. The DS4800 storage subsystems do not support the attachment of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700 Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be attached to the DS4800 storage subsystems. 8. THE DS4000 STORAGE SERVER WITH CONTROLLER FIRMWARE VERSION 05.41.1X.XX MUST BE UPGRADED TO CONTROLLER FIRMWARE VERSION 05.41.5X.XX FIRST BEFORE IT CAN BE UPGRADED TO CONTROLLER FIRMWARE VERSION 06.1X.XX.XX OR LATER. OTHERWISE, THE ERROR 231-FIRMWARE INCOMPATIBLE WILL BE DISPLAYED. 9. This 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.15.xx.xx and earlier must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 10. Controller firmware 06.16.xx.xx is required to support EXP810 storage expansion enclosures. IBM DS4000 Storage Manager version 09.16.xx.xx provides full management support for IBM machine types 3552 and 3542 storage controllers that have at least firmware version 04.01.xx.xx, IBM Machine type 1742 storage controllers that have at least firmware version 05.00.04.xx, IBM Machine type 1742-900 and Machine type 1722 storage controllers that have at least firmware version 05.3x.xx.xx, IBM Machine type 1724 storage controllers that have at least firmware version 05.42.xx.xx or IBM Machine type 1815 storage controllers that have at least firmware version 06.15.xx.xx. The only IBM DS4000 Storage Manager version 09.16.xx.xx management function supported on DS4000 storage subsystems with controller firmware version 04.xx.xx.xx up to 04.00.02.xx is controller firmware and NVSRAM download. ======================================================================= 2.0 Installation and Setup Instructions ---------------------------------------------------- Note: The web-download Storage Manager version 9.16 host software package must be first unpacked (tar -xvz) into a user-defined directory. Then, go to this directory, locate the Linux or Linux_IA64 directory to access the Storage Manager version 9.16 host software installation file(s). 2.1 Step-by-step instructions for this code update are as follows ----------------------------------------------------------------------------------------- NOTE: (for installation in Redhat EL AS 3.0 environment only) Some packages of JRE 1.3.1 may not contain all of the files necessary for the IBM DS4000 Storage Manager host software to run correctly on RedHat Enterprise Linux, version 3.0. If you are missing these files, the client and agent software will not run on that system, and an error message similar to the following example may display: /opt/SM8/jre/bin/i386/native_threads/java: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory To determine if the required compatibility library is installed, type the following at a terminal window command prompt: "rpm -q compat-libstdc++" The system will respond that the library package is not installed, or display the current version of the package. Verify that the current compatibility library matches the following package version: "compat-libstdc++-7.3.2.96.122" If the library is installed, proceed with the code installation procedure listed below. If not, you can download the library from RedHat Support web site. 1. Install and update the driver for the IBM DS4000 Host Adapter. a. Install the hardware by using the instructions that come with the adapter. b. Install the IBM DS4000 Host Adapter driver by using the instructions provided in the readme file located in the HostAdapter directory on the installation CD or downloaded with the device driver source package from the IBM support web site. c. If one chooses Linux RDAC as multipath failover/failback driver, install the IBM DS4000 Linux RDAC driver by using the instructions provided in the readme file located in the LinuxRDAC directory on the installation CD or downloaded with the device driver source package from the IBM support website. 2. If there is previous version 7.x, 8.x or 9.1x of the IBM DS4000 Storage Manager host software (ie. SMRuntime, SMClient, RDAC, SMUtil and SMAgent packages) installed in the server, you have to uninstall it first before installing the new version of the storage manager host software. 3. Install the new Storage Manager host software version from the CD-ROM directory or from the host software package that you downloaded from the IBM Support Web site. Refer to the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux for detailed installation instructions. 4. If the managed DS4000 storage subsystem had the FC/SATA intermix premium feature enable, do not continue with the next step until a FC/SATA intermix premium feature key file is generated and available. Once the controller firmware is upgraded to version 06.12.xx.xx from version 06.10.xx.xx, the FC/SATA intermix premium feature will be shown as out- of-compliance and the FC/SATA intermix premium feature key file is required to re-enable the feature. When the FC/SATA intermix premium feature is in out-of-compliance state, LUNs management functions like creations, deletions and modifications will not be operational. Please refer to the FC/SATA intermix premium feature activation card that was shipped with the FC/SATA intermix premium feature kit for instructions to generate the required premium key file. 5. Upgrade the DS4000 storage subsystem firmware in the following order - the drive expansion enclosure ESM code, controller firmware and NVSRAM, and then hard drive firmware code. Refer to the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux or the online help in the Subsystem Management window for detailed instructions. CAUTION: 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. 6. (if applicable) Re-enable the FC/SATA intermix premium feature using the premium key file. Refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the the latest DS4000 Storage Manager host software, the DS4000 controllers firmware, the drive expansion enclosure ESM firmware and the hard disk drive code. ======================================================================= 2.2 Refer to the HostAdapter or LinuxRDAC directory in the installation CD for the applicable drivers or refer to the IBM Support Web Site for the latest supported host adapters, device drivers, and updated readme. At this time, the supported drivers are as follows: 1. IBM DS4000 FAStT, FC-2 and FC2-133 Host Bus Adapter device driver version 7.05.00-fo (failover version) and 7.05.00 (non-failover version) for Linux 2.4 kernel (RHEL 3 and SLES 8) 2. IBM DS4000 FAStT, FC-2 and FC2-133 Host Bus Adapter device driver version 8.00.02 (failover and non-failover) for Linux 2.6 kernel (SLES 9) 3. Qlogic Sansurfer HBA 2.0.30 build 62 4. IBM DS4000 storage subsystem Linux RDAC version 09.00.A5.09 (for Linux 2.4 kernels)or 09.01.B5.21 (for Linux2.6 kernels) ======================================================================= 2.3 Helpful Hints ----------------------- 1. The DS4500 storage subsystem has a new recommended drive-side cabling instruction. The instructions are documented in the IBM System Storage DS4500 Storage Subsystem Fibre Channel Cabling Guide (GC26-7813-00 or IBM P/N 39M6031.) Please follow the cabling instructions in this publication to cable the new DS4500 setup. If you have an existing DS4500 setup with four drive side minuhub installed that was cabled according to the previously recommended cabling instructions, please schedule down time as soon as possible to make changes to the drive side FC cabling. Refer to the IBM System Storage DS4500 Storage Subsystem Fibre Channel Cabling Guide for more information. 2. If you are unable to see the maximum number of drives during Automatic Configuration, you should be able to use Manual Configuration to select individual drives and select the maximum number of drives allowed. 3. Depending on the storage subsystem that you have purchased, you may have to purchase the DS4000 storage partitioning premium feature option or an option to upgrade the number of supported partitions in a storage subsystem. Please see IBM Marketing representatives or IBM resellers for more information. - IBM DS4100 storage subsystem (machine type 1724): The standard configuration does not have the DS4000 storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. - IBM DS4300 storage subsystem (machine type 1722): The standard configuration does not have the DS4000 storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. The IBM DS4300 Turbo option comes with 8 partition storage partitioning premium option installed. An upgrade to 64 partitions can be purchased for the IBM DS4300 Turbo option. - IBM FAStT200 (machine type 3542: The standard configuration has 16 partition storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM FAStT500 and DS4400 storage subsystems (machine type 3552 and 1742 - models 1RU and 1RX, respectively): The standard configuration has 64 partition storage partitioning premium option installed. No additional storage partitioning premium feature options can be purchased for these storage subsystems. - IBM DS4500 storage subsystem (machine type 1742 - models 90X and 90U): The standard configuration has 16 partition storage partitioning premium option installed. An upgrade from 16 to 64 partition storage partitioning premium feature option can be purchased. - IBM DS4800 storage subsystem (machine type 1815): Depending on the ordering channels, the 1815 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the subsystem is ordered with less than 64 partitions, an upgrade from 8 to 16, 8 to 64 or 16 to 64 partition storage partitioning premium feature option can be purchased. 4. Do not delete the Access LUN or Access Volume if you want to manage the DS4000 storage subsystem in-band (host-agent managed). The Access LUN is required by the SMClient to communicate with the storage controllers when using the in-band management method. 5. The DS4000 controller host ports or the Fibre Channel HBA ports can not be connected to a Cisco FC switch ports with "trunking" enable. You might encounter failover and failback problems if you do not change the Cisco FC switch port to "non-trunking" using the following procedure: a. Launch the Cicso FC switch Device Manager GUI. b. Select one or more ports by a single click. c. Right click the port(s) and select Configure, a new window pops up d. Select the "Trunk Config" tab from this window, a new window opens e. In this window under Admin, select the "non-trunk" radio button, it is set to auto by default. f. Refresh the entire fabric. 6. When making serial connections to the DS4000 storage controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the DS4000 storage subsystem serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 7. Fabric topology zoning requirement. To avoid possible problem at the host level, it is best practice that all Fibre Channel (FC) Switches must be zoned such that a single FC host bus adapter can only access one controller per storage array. In addition, this zoning requirement also ensures the maximum number of host connections can be seen and log into the controller FC host port. This is because if a FC HBA port is seen by both controller A and B host ports, it will be counted as two host connections to the storage subsystem - one for controller A port and one for controller B port. Note: The DS4000 storage subsystems DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 storage subsystems DS4300 (IBM machine type 1722) and DS4100 (IBM machine type 1724) have two ports per controller. The DS4000 storage Server FAStT200 (IBM machine type 3542) has only one port per controller. The DS4800 storage subsystem (IBM machine type 1815) has four ports per controller. 8. All drive enclosures on any given loop should have complete unique ID's assigned to them. For example, in a maximum configured DS4500 storage server, 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. Enclosures id's 00 ~ 09 should not be used and enclosure id's with the same single digit such as 11 and 21 should not be used on the same drive loop. 9. The ideal configuration for SATA drives is one drive in each EXP per array, one logical drive per array and one OS disk partition per logical drive. This configuration minimizes the random head movements that increase stress on the SATA drives. As the number of drive locations to which the heads have to move increases, application performance and drive reliability may be impacted. If more logical drives are configured, but not all of them used simultaneously, some of the randomness can be avoided. SATA drives are best used for long sequential reads and writes. 10. IBM recommends at least one hot spare per EXP100 drive expansion enclosure. A total of 15 hot-spares can be defined per DS4000 storage subsystem configuration. 11. Starting with the DS4000 Storage Manager (SM) host software version 9.12 or later, the Storage Manager client script window looks for the files with the file type of ".script" as the possible script command files. In the previous versions of the DS4000 Storage Manager host software, the script window looks for the file type ".scr" instead. (i.e. enableAVT.script for SM 9.12 or later vs. enableAVT.scr for pre-SM 9.12) ======================================================================= 3.0 Configuration Information ---------------------------------------- 3.1 Configuration Settings ------------------------------------ 1. When using the Linux RDAC as the failover/failback driver, the host type should be set to LNXCL instead of Linux. If Linux RDAC is not used, the host type of Linux must be used instead. 2. By default, the IBM DS4000 Storage Manager 9.1x firmware does not automatically map logical drives when the IBM DS4000 storage partitioning premium feature is enabled. This means that the logical drives after being created are not automatically presented to the host systems. a. For a new installation, after creating new arrays and logical drives, if your host OS type is any of the supported version of Linux OS's, create a partition with the host type of Linux and map the logical drives to this partition. b. If you are upgrading the NVSRAM with Storage Partitions, you may have to change the default host type to match the host system OS like Linux or LNXCL. After upgrading the NVSRAM, the default host type is reset to Windows 2000/Server 2003 non-clustered for DS4000 storage subsystem with controller firmware version 06.15.xx.xx or later. For DS4000 storage server with controller firmware version 06.12.xx.xx or earlier, it is reset to Windows non-clustered (SP5 or higher), instead. Refer to the IBM DS4000 Storage Manager online help to learn more about creating storage partitions and changing host types. 3. When you are configuring IBM machine type 1722, 1724, 1742, 3542, 1815 or 3552 storage controllers as boot devices, contact IBM support for supported configurations and instructions for configuring IBM storage controllers as boot devices. 4. 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. - SameWWN.scr: Setup RAID controllers to have the same World Wide Names. The World Wide Names (node) will be the same for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - DifferentWWN.scr: Setup RAID controllers to have different World Wide Names. The World Wide Names (node) will be different for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - EnableDriveMigration.scr: The Enable drive migration script scans the drives for configurations when they are added to a storage system and will also attempt to use configurations found on the newly added drives. The NVSRAM default will enable drive migration. - DisableDriveMigration.scr: The disable drive migration script allows the addition of disk drives while the system is running. In addition, it identifies the drives as unused capacity regardless of past drive configuration. The NVSRAM default will enable drive migration. - EnableAVT_Linux.scr: The script will enable automatic logical drive transfer (ADT) 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.scr: The script will disable the automatic logical drive transfer (ADT) 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) 5. When you are configuring IBM machine type 1722, 1724, 1742, 1815 or 3552 storage subsystems in clustered Remote Mirror configurations, contact IBM support for supported cluster configurations and instructions for configuring IBM storage controllers in clustered Remote Mirror configurations. 6. When using the Linux RDAC as the multipathing driver, the "LNXCL" host type must be used instead of the linux host type and there is not a requirement that the UTM(Access LUN) must be removed from the LNXCL Storage Partitioning partition. 7. If a host in a cluster server configuration lost a physical path to a DS4000 storage subsystem controller, the logical drives that are mapped to the cluster group will periodically failover and then failback between cluster nodes until the failed path is restored. This behavior is the result of the automatic logical drive failback feature of the RDAC multipath driver. The cluster node with a failed path to a DS4000 controller will issue a failover command of all logical drives that were mapped to the cluster group to the controller that it can access. After a programmed interval, the nodes that did not have failed path will issue failback command for the logical drives because they can access the logical drives both controllers, resulting in the cluster node with the failed path not be able to access certain logical drives. This cluster node will then issue a failover command for all logical drives, repeating the logical drives failover-failback cycle. The workaround is to disable this automatic failback feature. For Linux cluster (SteelEye) environments, perform the following steps: a. Open the /etc/mpp.conf file, and change the DisableLunRebalance parameter to 3. Save the changes. b. From a shell prompt, type the following command, and press Enter: mppUpdate c. Reboot the computer for the changes to take effect. d. Repeat this procedure on any system in the cluster configuration that has the Linux RDAC driver installed. ======================================================================= 3.2 Hardware status and information -------------------------------------------------- New installations for IBM Machine types 1722, 1742, 1815 and 1724 should be installed with the IBM DS4000 and FC-2/FC2-133 Host Adapter. The device driver version should be 7.05.00 or 08.00.02 for FAStT and FC-2/FC2-133 Host Adapters depending on the whether the Linux kernel version is of 2.4 or 2.6, respectively. For more information, refer to the IBM System Storage™ Disk Storage Systems Technical Support web site. ======================================================================= 3.3 Unsupported configurations -------------------------------------------- The configurations that are currently not being supported with IBM DS4000 Storage Manager Version 9.16 are listed below: 1. The DS4100 (machine type 1724) storage subsystem does not support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC) drive expansion enclosure. Please contact IBM representatives or resellers for the availability of such support in the future. 2. The DS4100 with Single Controller option does not support the attachment of the DS4000 EXP100 drive expansion enclosures. 3. The DS4800 storage subsystem (machine type 1815 - all models) does not support the attachment of the FAStT EXP500, DS4000 EXP700 drive expansion enclosures. 4. The DS4800 storage subsystem (machine type 1815 - all models) with controller firmware 6.15.xx.xx installed does not support the attachment of the DS4000 EXP810 (FC) drive expansion enclosures. 5. The DS4800 storage subsystem (machine type 1815 - all models) with controller firmware 6.16.xx.xx installed does not support the attachment of the DS4000 EXP100 (SATA) drive expansion enclosures. 6. The DS4300 storage subsystem with Single Controller option does not support the controller firmware version 06.1x.xx.xx. The correct firmware version for these DS4300 storage subsystem models is 05.34.xx.xx. 7. Fibre Channel loop environments with the IBM Fibre Channel Hub, machine type 3523 and 3534, in conjunction with the IBM Fibre Channel Switch, machine types 2109-S16, 2109-F16 or 2109-S8. In this configuration, the hub is connected between the switch and the IBM Fibre Channel RAID Controllers. 8. The IBM Fibre Channel hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1815, 3542 and 3552. 9. A configuration in which a server with only one FC host bus adapter connects directly to any DS4000 storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC host bus adapter connects to both controller ports of any DS4000 storage subsystem with dual controllers via Fibre Channel (FC) switch (SAN-attached configuration.) ======================================================================= 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 You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426- 7378). IMPORTANT: You should download the latest version of the DS4000 Storage Manager host software, the DS4000 storage subsystem 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: www-1.ibm.com/servers/storage/disk/ Perform the following steps to register at the IBM Support and Download Web site: 1. Click on My Support in the Additional Support box in the right side of the DS4000 Support web page. 2. The Sign In window displays. Either enter your IBM ID and Password in the sign in area to sign in and proceed to step 6 or, if you are not currently registered with the site, click Register Now. 3. The My IBM Registration window Step 1 of 2 opens. Enter the appropriate information and click Continue to get to the second My IBM Registration window. 4. In the My IBM Registration window Step 2 of 2, enter the appropriate information and click Submit to register. 5. The My IBM Registration windows opens with the following message, “Thank you for registering with ibm.com. Continue to explore ibm.com as a registered user.” Click Edit Profile in the My IBM box on the right side of the window. 6. The My Support window opens. Click Add Products to add products to your profile. 7. Use the pull-down menus to choose the appropriate DS4000 storage server and expansion enclosures that you want to add to your profile. To add the product to your profile, select the appropriate box or boxes next to the product names and click Add Product. 8. Once the product or products are added to your profile, click Subscribe to Email folder tab 9. Select Storage in the pull down menu. Select Please send these documents by weekly email and select Downloads and drivers and Flashes to receive important information about product updates. Click Updates. 10. Click Sign Out to log out of My Support. ======================================================================= 6.0 Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM System Storage the e-business logo xSeries, pSeries HelpCenter UNIX is a registered of The Open Group in the United States and other countries. Microsoft, Windows, and Windows NT are of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. QLogic and SANsurfer are trademarks of QLogic Corporation. Other company, product, or 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.