IBM System Storage™ DS4000 Storage Manager version 9.16 for the 32bit and 64bit Itanium II (IA64) version of Microsoft Windows Server 2003 and 23bit version of Microsoft Windows 2000 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. IMPORTANT: 1. There are not any DS4000 Storage Manager version 9.16 host software packages for the AMD-64 or EM64T servers running in native AMD-64 or EM64T code version of the Microsoft Windows Server 2003 - 64bit (X64 edition) OS. This IBM System Storage™ DS4000 Storage Manager version 9.16 host software package for Microsoft Windows Server 2003 - 32 bit (IA32) edition operating system should be used for the x64 servers running the 32 bit version of the Microsoft Windows Server 2003. Please contact IBM representatives or resellers for the availability of the System Storage™ DS4000 Storage Manager host software package for Microsoft Windows Server 2003 - x64 edition operating system in the future. Note: X64 servers referred to the servers with Intel EM64T processors or AMD AMD64 processors. There is a DS4000 Storage Manager version 9.15 host software packages for the AMD-64 or EM64T servers running in native AMD-64 or EM64T code version of the Microsoft Windows Server 2003 - 64bit (X64 edition) OS for systems connected to a DS4800 Storage Controller with firware version 06.15.xx.xx only. This DS4000 Storage Manager version 9.15 host software package is available for download at IBM's System Storage™ DS4000 Support web site. Please see web package readme file for additional details. 2. Microsoft Windows host attachment to the DS4800 requires the additional purchase of the IBM DS4800 Host Kit Option or Feature Code. The IBM DS4000 Microsoft Windows Host Kit options contain the required IBM licensing to attach an Microsoft Windows Host System to the DS4800. Please contact your IBM service representative or IBM resellers for purchasing information. This host kit is shipped as standard in the DS4800 storage subsystem models 82H, 84H and 88H. 3. The Microsoft Windows NT4 is not supported with this version of the IBM System Storage™ DS4000 Storage Manager. In addition, the only DS4000 Storage Manager host software support on Microsoft Windows XP Professional operating system is the DS4000 Storage Manager client program. 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. Last Update: 03/26/2006 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, 84A, 82H, 84H, | | | | | 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 | ------------ --------------------------------------------------- Note: - 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(dual controller) 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. 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 for Microsoft Windows 2000 and Windows Server 2003 Intel Architecture 32bit (IA32). This version 9.16 of the DS4000 Storage Manager host software is required for managing the DS4800 storage subsystems with controller firmware version 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 (dual controller) or Turbo options, the DS4400 and the DS4500 - with controller firmware version 06.12.xx.xx installed. In addition, it should also be used for managing the DS4800 with controller firmware 6.15.xx.xx and is not IO attached to a server(s) running Microsoft Windows 2003 - x64 edition. 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. Notes: 1. There are three separate IBM DS4000 Storage Manager host software version 9.16 packages for the following Microsoft Windows OSes - Windows 2000, Windows Server 2003 Intel Architecture 32bit (IA-32) and Windows Server 2003 Intel Architecture Itanium 64bit (IA-64). The WIN32, WS03_32bit and WS03_64bit directories contain the files necessary for installing the IBM DS4000 Storage Manager Version 9.16 host software in the Microsoft Windows 2000, Server 2003 32bit and Server 2003 Itanium2 64bit Operating System (OS) environments, respectively. Please select the appropriate directory for your operating system environment. The DS4000 storage subsystem controller Firmware and NVSRAM files are located in the FIRMWARE and NVSRAM CD- ROM directories. These host software and DS4000 storage subsystem firmware files are also packaged separately and are available for download from the IBM System Storage™ DS4000 Support web site - http://www.ibm.com/servers/storage/support/disk/. 2. This version of DS4000 storage manager host software does not support Microsoft Windows NT4 Operating System. In addition, the only DS4000 Storage Manager host software support on Windows XP Professional OS is the DS4000 Storage Manager client (SMClient) program from the IBM DS4000 Storage Manager host software package for the Microsoft Windows Server 2003 Intel Architecture 32bit (IA32). ATTENTION: This is not the correct DS4000 Storage Manager host software web download package version 9.16 for the AMD-64 or EM64T (X64) servers with the Microsoft Windows Server 2003 X64 edition operating system installed. The IBM System Storage™ DS4000 Storage Manager host software package for Microsoft Windows Server 2003 - 32 bit (IA32) edition operating system should be used for the X64 servers running the 32 bit version of the Microsoft Windows Server 2003. Please contact IBM representatives or resellers for the availability of the System Storage™ DS4000 Storage Manager host software package version 9.16 for Microsoft Windows Server 2003 - X64 edition operating system in the future. Note: There is a DS4000 Storage Manager version 9.15 host software packages for the AMD-64 or EM64T servers running in native AMD-64 or EM64T code version of the Microsoft Windows Server 2003 - 64bit (X64 edition) OS for systems connected to a DS4800 Storage Controller with firware version 06.15.xx.xx only. This DS4000 Storage Manager version 9.15 host software package is available for download at IBM's System Storage™ DS4000 Support web site. Please see the web package readme file for additional details. 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 IBM's Support Web Site as a downloadable Portable Document Format (PDF) file. It contains the instructions for installing the IBM DS4000 Storage Manager version 9.16 host software. In addition, the Docs directory in the DS4000 Storage Manager Version 9.16 Support for Microsoft Windows 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 05.00.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.xx.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.xx.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.12.xx.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.12.xx.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4300 Single | 05.34.xx.xx | | Controller Opt. | (for DS4300 SCU | | (1722) | only) | |------------------|--------------------------------| | DS4100 (1724) | 06.12.xx.xx | | (standard dual | (for SCU model, 06.12.16.xx | | and single | or higher) | | 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 enclosures attached, use the controller firmware version 6.15.xx.xx instead. ======================================================================= 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.35.09 release for the DS4000 controller firmware version 6.16.24.xx None New limitations with Storage Manager Installer (SMIA) package version 09.16.35.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. 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. New limitations with SMIA package version 09.15.xx.06 release for the DS4000 controller firmware version 06.12.xx.xx and 06.15.xx.xx 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.0x and DS4000 controller firmware version 06.15.xx.xx release 1. There are not any DS4000 Storage Manager host software packages for the AMD- 64 or EM64T servers running in native AMD-64 or EM64T code version of the Microsoft Windows Server 2003 - 64bit (X64 edition) OS. New limitations with SMIA package version 9.14.xx.05 and DS4000 controller firmware version 06.14.xx.xx release 1. With this release of DS4000 Storage Manager, Veritas Volume Manager (DMP) version 4.2 is supported in Microsoft Windows operating system environment. However, the Veritas Cluster Server is not supported. Please contact IBM representatives or resellers for the support of this program in the future. 2. Always click the Recovery Guru icon in the DS4800 Subsystem Management window to check for DS4800 storage subsystem problems. In certain rare error condition, the Subsystem Management window displays the subsystem with Optimal icon instead of Need Attention icon and a flashing Recovery Guru icon. New limitations with Storage Manager 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 disk resource might become offline when you execute the SMrepassist utility in the Windows Server 2003 MSCS environment. The work around is to set the big enough value (>120 seconds) for IsAlive and LooksAlive parameter of the disk resource before you execute the SMrepassist utility. This limitation is not applicable to Windows 2000 MSCS environment. 6. The RDAC driver in the DS4000 Storage Manager host software package for Windows version 9.12 or higher does not recognize the mapped logical drives from the DS4000 storage subsystem with controller firmware version 04.01.xx.xx. The work around is to upgrade the DS4000 storage subsystem controllers with firmware version 05.xx.xx.xx or later. 7. 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) 8. 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) 9. 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) 10. 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) 11. If you are unable to boot your Windows Server 2003 host in a root boot environment. It could be caused by the the controller ownership of the boot logical drive (LUN) has been changed to the alternate controller. To recover, one must manually change the Ownership/Preferred Path of the boot logical drive (LUN) to the preferred path from a different host or storage management station. For additional information about changing controller ownership of a array or logical drive, refer to the Subsystem Management Window online help. (added 2/10/2006) 12. If you disable and then re-create a flashcopy logical drive that is mapped to a Windows Server 2003 host, the operating system does not detect any changes to the base flashcopy logical drive that occurred between the time you disabled and re-created the flashcopy logical drive. This occurs on both the 32-bit and 64-bit versions of the operating system. The workaround is to reboot the Windows Server 2003 host when you finish modifying the flashcopy logical drive. (2/10/2006) 13. Occasionally, after mapping logical drives to a Windows Server 2003 host, the host can take a longer time to boot than usual. The amount of time is based on how many logical drives are mapped to the host. There is not any workaround. This is a known issue with the Plug-and-Play (PnP) Manager in the Windows Server 2003 operating system. Regardless of the long boot time, this cycle must complete. (added 2/10/2006) Limitations with Storage Manager version 9.10.xx.05 and DS4000 controller firmware version 06.10.11.xx release 1. In MSCS configurations, the MSCS service must be stopped and set to manual start after server rebooting, the clusdisk driver must have to be set to offline and, then, the server must be rebooted before uninstalling the RDAC driver in the server. If the clusdisk driver is not set to offline and the MSCS service is not set to manual start, the MS cluster service will not start after the new RDAC driver is installed because it can not bring the Quorum disk resource online. The problem is caused by the changing of the disk signatures. The work around is stated in the first sentence of this paragraph. To recover from this problem, you must: 1. Look up the old disk signatures of the disk that are defined as cluster disk resources. They could be found either in the registry under the HKLM/System/CurrentControlSet/Services/Clusdisk/Parameters/Signatures registry key or in the cluster.log file. 2. Look up the new disk signatures of the disks that are defined as cluster disk resources using the dumpcfg utility that is packaged in the Microsoft Windows resource kit. 3. Compare the new and old disk signatures. If new disk signature did not match the old signature, you have to change the new disk signature to the old disk signature values by using the dumpcfg command. The syntax of the command is dumpcfg.exe -s For example, dumpcfg.exe -s 12345678 0 2. Before updating the RDAC driver in a server that is setting up as San-boot, modifications to the Fibre Channel (FC) cabling between the Host Server HBA ports and the DS4000 storage subsystem Fibre Channel (FC) host ports or to the FC switch zoning must be performed so that the FC HBA port in the host server will see either controller A or controller B only. The server will bluescreened during the reboot after the un-installation of the RDAC driver if the HBA port can see the boot LUN on both controller A and B. (258127 - 82146) 3. 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 work around 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) 4. 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) 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. Limitations with Storage Manager version 8.4x.xx.xx (and earlier) and DS4000 controller firmware version 05.4x.xx.xx (and earlier) releases 1. You must use the Add/Remove program function in the Control Panel window to uninstall or to disable the IBM DS4000 Storage Manager RDAC device. To re-install the IBM DS4000 Storage Manager RDAC device, follow the instructions in the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux. 2. You must always uninstall IBM DS4000 Storage Manager RDAC before you uninstall the Host Bus Adapter driver. Failure to do so may result in system hung or blue-screen. 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. When alternately switching back and forth the roles of the logical drives in a remote mirrored relationship, Windows NT4, Windows 2000 and Server 2003 may cache the file(s) on the logical drive(disk) in memory and use these cached data instead of going out to the disk to get the data. This windows OS behavior may make the data look like it was not synchronized between logical drives in a remote mirrored relationship. The fix to the problem is to dismount the primary logical drive in the server before demoting it to secondary role. In Microsoft Windows environment, this is best done by shutting down the server that the primary logical drive is mapped to. Then, promote the secondary logical drive to the primary role and hot_add it to the appropriate server. If the logical drive is of "Dynamic Disk" type, there is a possible solution without requiring server to be shut down. First, in the server that has the primary logical drive, run the SMrepassist program in the DS4000 Storage Manager Util directory with the -f option to flush the cached data to disk. Then, promote the secondary logical drive and hot_add it to the appropriate server. Before promoting the logical drive to primary role in the original server, force a failure to the disk, for example, by running a chkdsk on the disk. Then, promote the logical drive to primary role in the original server and hot_add it. One may have to reactivate the disk after it is hot_added to the server. If the server environment prevents the server from being rebooted and the logical drive is of "basic disk" type, you may use the following steps 1. In the server that has the primary logical drive, run the SMrepassist program in the DS4000 Storage Manager Util directory with the -f option to flush the cached data to disk. 2. Using the DS4000 Storage Manager to remove the LUN mapping of the logical drive that had the primary role from its server (host computer). 3. Promote the secondary role LUN to the primary role and hot_add it in the appropriate server assuming that the LUN mapping is already defined for this server in the DS4000 storage subsystem. 4. Before promoting the logical drive to primary role in the original server, run Hot_add program or initiate a Scan for Hardware Changes task in the original server. This is to remove the logical drive from the available disks. In W2K, you may see Unsafe Removal of Devices messages. 5. Using the DS4000 Storage Manager to add the LUN mapping of the logical drive that will be promoted to primary role to the original server(host computer). 6. Promote the Logical Drive to Primary role and hot_add it in the original server. If you are unable to hot_add the logical drive or the data still appears to be mismatched, you must reboot the server. 5. The supplied SMrepassist utility did not utilize Microsoft Volume Shadow Services APIs to quiesce the LUNs. Appropriate steps are still need to shut down/quiesce the applications like MS Exchange and SQL Server before the FlashCopy logical drive can be made. 6. Uninstalling RDAC may cause Windows Dynamic disks to fail. After the new RDAC is installed and the server is rebooted, these disks must be reactivated and Chkdsk must be run. The work-around is to stop the applications and remove the drive letters or the mount points to these disks before uninstalling and reinstalling RDAC. 7. The current RDAC driver will coexist with Storport model driver as long as it is not the driver for the adapter that talks to the LUNs in the DS4000 storage subsystems. Note: the current release drivers for all of the Fibre Channel host bus adapters that DS4000 Storage Servers support are based on the Scsiport model. 8. 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. 9. In a direct Fibre Channel connection between the DS4000 storage server and the HBAs in the host server, the system bluescreen may occur if the DS4000 storage subsystem is powered off. The work around is to power down the server first before powering down the DS4000 storage server. 10. Only logical drives that are configured as "Basic Disks" in the Windows Disk Management folder can have FlashCopy made. The FlashCopy of a logical drive configured as "Dynamic Disk" type will always be failed by the DS4000 storage subsystem when it is added to the host server. 11. There is not an IA-64 version of the DS4000 Management Suite Java (FAStT_MSJ). Use the 32-bit version of the DS4000 Management Suite Java for the Windows Server 2003 64-bit edition. However, one should uninstall it once the diagnostic is completed. It could cause the server to bluescreen in heavy IO loads. 12. 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. 13. 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. 14. 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. 15. 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. 16. 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. 17. 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. 18. 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:. 19. 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. Furthermore, 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. 20. 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 subsystem 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. 21. 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. 22. 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 EXP 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. 23. Interoperability with tape devices is supported on separate HBA and switch zones. 24. Interoperability with IBM Enterprise Storage Server and SDD multipath device driver is supported on separate HBA and switch zones. ======================================================================== 1.3 Enhancements ----------------- DS4000 Storage Manager 9.16 (in conjunction with the DS4000 storage subsystem controller firmware 06.16.xx.xx) provides support for attachment of DS4000 EXP810 Storage Expansion Enclosures to 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 Itanium II (IA64) Windows Server 2003 and for 32bit Windows 2000 OSes 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 Microsoft Windows NT4 SP6 operating system is not supported for this release of IBM DS4000 Storage Manager version 09.1x.xx.xx. The only supported Microsoft Windows operating systems are the Windows 2000 SP4 and the IA32 and IA64 editions of Windows Server 2003 with SP1. For the 32bit Microsoft Windows 2000 or Server 2003 (X86/IA32) editions, IBM xSeries and other Intel-based servers with minimum 1024MB Memory with at least 512KB L2 Cache Pentium III 1Ghz processor(s) is recommended. For the 64bit Itanium II Microsoft Windows Server 2003 (IA64) edition, IBM xSeries and other Intel-based servers with minimum 1024MB Memory with Intel Itanium II processor(s) is recommended. (also see Dependencies section) Client Code levels at time of release are as followed --------------------------------------------------------- Important: 1. This release of IBM DS4000 Storage Manager host software supports all DS4000 storage subsystems with general released firmware versions from 05.xx.xx.xx up to 06.16.xx.xx. 2. There are three separate IBM DS4000 Storage Manager host software version 9.16 packages for the following Microsoft Windows OSes - Windows 2000, Windows Server 2003 Intel Architecture 32bit (IA-32) and Windows Server 2003 Intel Architecture Itanium II 64bit (IA-64). Please download the correct one for your operating system environment. For Microsoft Windows 2000 and Server 2003 32 bit (IA-32/32 bit) only: Starting with the DS4000 storage manager version 9.12, all of the host-software packages are included in a single 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. The version of the host software installer wizard for this release is SMIA-WS32-09.16.35.09.exe. This wizard will install the following version of the host-software packages: 1. IBM DS4000 Storage Manager Client version: 09.16.G5.08 2. IBM DS4000 Storage Manager RDAC version: 09.01.35.20 Note: This RDAC requires Windows2000-KB822831-x86-ENU.exe hot fix be installed in addition to Service Pack 4 in Microsoft Windows 2000 operating system environment) 3. IBM DS4000 Storage Manager Agent version: 09.16.35.00 4. IBM DS4000 Storage Manager Utilities version: 09.16.35.00 In addition, for DS4000 configurations with Microsoft Windows servers using Veritas Volume Manager (DMP) as multipath driver, you have to obtain the correct asl file for DS4000 storage subsystem using the following Veritas Support URL. http://seer.support.veritas.com/docs/273458.htm For Microsoft Windows Server 2003 64 bit (IA-64/64 bit edition) only: Starting with the DS4000 storage manager version 9.12, all of the host-software packages are included in a single 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. The version of the host- software installer wizard for this release is SMIA-WS64-09.16.35.09.exe. This wizard will install the following version of the host-software packages: 1. IBM DS4000 Storage Manager Client version: 09.16.G5.08 2. IBM DS4000 Storage Manager RDAC version: 09.01.35.20 3. IBM DS4000 Storage Manager Agent version: 09.16.35.00 4. IBM DS4000 Storage Manager Utilities version: 09.16.35.00 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 (DUAL CONTROLLER) 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, 06.15.xx.xx or 06.16.xx.xx controller firmware version are the DS4800 storage subsystems. Currently, there are not any controller firmware packages version 06.14.xx.xx and higher 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 CONTROLER 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 VERSON 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.1x provides full management support for IBM machine types 3552 and 3542 storage controllers that have at least firmware version 05.xx.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.14.xx.xx. The only IBM DS4000 Storage Manager version 09.1x management function supported on DS4000 storage subsystems with controller firmware version 04.xx.xx.xx up to 04.01.xx.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 (unzipped) into a user-defined directory. Then, go to this directory, locate the Windows directory to access the Storage Manager version 9.16 host software installer wizard. 2.1 Step-by-step instructions for this code update are as follows ------------------------------------------------------------------ 1. Install and update the driver for the IBM FAStT, FC-2 or FC2-133 Host Bus 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.txt file located in either the Host_Adapter directory on this installation CD or from the appropriate driver package that is downloaded from the IBM Support Web site. 2. If there is previous version 7.x, 8.x or 9.10 of the IBM DS4000 storage manager host software installed in the system, you have to uninstall it first before installing the new version of the storage manager host software. IMPORTANT: For servers with boot LUNs in the DS4000 storage subsystems (aka. SAN Boot or Root Boot), a special utility in the RDAC_UninstallUtil_for_BootFromSANConfigurations directory must be run first before unintalling the RDAC, especially in the following server configuration - W2K server with DS4000 Storage Manager 8.4 RDAC installed. Please refer to the README in the RDAC_UninstallUtil_for_BootFromSANConfigurations directory for instructions on running the utility. NOTE: This utility can also be used to recover from a failed uninstallion of the RDAC in non-SAN boot Microsoft Windows environments which resulted in a failed reboot of the Windows operating system. For instruction to unintall the DS4000 storage manager host software, please refer to the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, and Linux. If the previously installed DS4000 storage manager version is of 9.12 or later, the DS400 storage manager host software can be updated with the new code from the installer without the need of uninstalled the existing storage manager host software packages first. Just click "Yes" in the window that the installer displays, stating that there are already installed DS4000 storage manager host software in the server and whether you want to update it with the new code. 3. Install the new storage manager host software from the appropriate CD-ROM directory for your Operating Systems 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 with controller firmware version 06.10.xx.xx installed 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, 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 DS4000 drive expansion enclosure ESM code, the DS4000 storage subsystem controller firmware and NVSRAM and then the 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. ATTENTION: 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 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 Host_Adapter directory on the installation CD for the applicable drivers. Refer to the http://www.ibm.com/servers/storage/support/disk IBM System Storage™ Disk Storage Systems Technical Support web site for the latest supported host adapters, device drivers, and updated readme. ======================================================================= 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 and single controller 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. 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 subsystem 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) 12. When you configure a LUN from the DS4000 storage subsystem as a boot device, the system displays a blue screen and does not respond when it is manually or automatically set to hibernate. If you use a LUN in the DS4000 storage subsystem as a boot device for Windows Server 2003, you cannot enable the hibernation feature. To ensure that the hibernation feature is disabled, complete the following steps: a. Select Start >> Settings >> Control Panel >> Power Options. b. Select the Hibernate tab. IMPORTANT: If the Hibernate tab does not appear in this dialog, then your system does not support hibernate. No additional action is required. c. Is the Enable Hibernate Support check box selected? | Yes – Unselect the check box, select Apply, and then go to step d. | No – Go to step d. d. Select the Power Schemes tab. e. From the Turn Off Hard Disks drop-down menu, select Never. f. Select OK. 13. (Windows Server 2003) Cluster resources might fail on a host after rebooting if the "Failback immediately" option is checked in the Microsoft Cluster Server software. With this option checked, you might see failed resources or devices not associated with their preferred node. The current workaround is to make sure that the "Prevent failback" option is checked under Group Properties. This is the default option. Do not use the "Failback immediately" option. 14. (Windows 2000) In a Microsoft Cluster Server (MSCS) environment configured with VERITAS DMP, rebooting a server node owning the resources might take a long time (10 to 15 minutes). It is possible that the long server boot time might cause some Windows delayed write failures. The workaround is to move all the resources from the server node you are planning to reboot to another node before rebooting. 15. (Windows Server 2003) When in a server cluster environment, a failed disk in the storage subsystem does not show as failed in the Cluster Administrator. The host still receives I/O errors, and the disk is shown as failed in the storage management software. This is a known issue with the Windows Server 2003 operating system. Choose one of the following workarounds: • Workaround 1 – Reboot the host that owns the disk resource. The Cluster Administrator should now show the proper state of the disk resource. • Workaround 2 – Change the ownership of the disk resource to a different node in the server cluster configuration. ======================================================================= 3.0 Configuration Information ----------------------------- 3.1 Configuration Settings -------------------------- 1. For the Microsoft Windows servers in MSCS configuration, the IBM FC2-133 HBA adapter "Port Down Retry Count" BIOS parameter must be change to 70 from the default of 30. You can either use the FAStT Management Suite Java (FAStT MSJ) program or the FC2-133 HBA Fast!UTIL program to change the setting. To use the Fast!UTIL program, perform the following steps: 1. Reboot the server 2. Press when the statement "Press for Fast!UTIL " is displayed when the server scan the FC-133 adapter during boot to get invoke the Fast!UTIL program. 3. If there are multiple FC2-133 HBAs in your server, a list of the HBAs will be displayed. Select the appropriate HBA and press enter to get to the Fast!Util Options menu. Then, select the Configuration Settings menu option followed by Advanced Adapter Settings menu option to display the menu that the Port Down Retry Count parameter is displayed. Select the parameter and press enter to edit the new value. 4. Press ESC twice to get to the "Save setting" menu. Select appropriate option to save the settings and return to the Fast!UTIL Options menu. You can either select another HBA for modification or press ESC and select Reboot System when you are prompted. Alternatively, you can also use the FAStT MSJ program to modify the setting from the Microsoft Windows operating system environment. However, you must reboot the servers for the changes to become effective. In addition, the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk registry value must be increased to 120 from the default setting of 60. A utility, SMRegUpdate.reg, is provided in the SMUtil host software package to facilitate this registry change. Note: FAStT MSJ will be referred to as Qlogic SAN-Surfer in the future releases. 2. 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 Windows, change the DisableLunRebalance registry setting of the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdacdisk\Parameters] registry key from 0 to 3 in each cluster node. Then, reboot each node for the changes to take effect. 3. By default, the IBM DS4000 Storage Manager 8.3 and higher 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, create a storage partition with the host type of Windows 2000/Server 2003 non-clustered or Windows 2000/Server 2003 clustered 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. 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.14.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. 4. When you are configuring IBM machine type 1722, 1742, 1815, 3542 or 3552 storage controllers as boot devices, contact IBM support for supported configurations and instructions for configuring LUNs in IBM DS4000 storage subsystems as boot devices. 5. 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_W2K_S2003_noncluster.scr: The script will enable automatic logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003 non- cluster heterogenous host region. The default setting is to disable AVT for this heterogenous host region. This setting is one of the requirements for setting up the remote boot or SAN-boot. 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 Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT enabled) - DisableAVT_W2K_S2003_noncluster.scr: The script will disable the automatic logical drive transfer (AVT) for the Windows 2000/Server 2003 non-cluster heterogenous host region. This script will reset the Windows 2000/Server 2003 non-cluster AVT setting to the default. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non- cluster host type with the appropriate host type that needs to have AVT/ADT disabled) 6. When you are configuring IBM machine type 1722, 1724, 1742, 1815 or 3552 storage subsystems in host cluster Remote Mirror configurations, contact IBM support for supported host cluster configurations and instructions for configuring IBM storage controllers in clustered Remote Mirror configurations. ======================================================================= 3.2 Hardware status and information ----------------------------------- New installations for IBM Machine types 1722, 1724, 1742, 1815, 3552, and 3542 should be installed with the IBM DS4000 FC2-133 Host Bus Adapter and Microsoft Windows SCSIport miniport device driver version 9.0.2.60 or higher. The FC2-133 host bus adapter BIOS (IA-32) or EFI (IA-64) versions are 1.47 and 1.37, respectively. For more information on the latest support device driver and BIOS (or EFI), refer to the IBM DS4000 Support Web site. ======================================================================= 3.3 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS4000 Storage Manager Version 9.16. 1. The DS4100 (machine type 1724) storage subsystem does not support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC) drive expansion enclosures. Please contact IBM representatives or resellers for the availability of such support in the future. 2. The DS4800 (machine type 1815) storage subsystem does not support the attachment of the DS4000 EXP500 and EXP700 (FC) drive expansion enclosure. 3. 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. 4. 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. 5. The DS4100 with Single Controller option does not support the attachment of the DS4000 EXP100 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.