IBM System Storage DS Storage Manager version 11.20.x5.10 for Microsoft Windows Server 2012, Microsoft Windows Server 2008 SP2 - X64 (64bit), Windows Server 2008 R2 SP2 with HyperV Clustering edition, Windows Server 2008 SP2 - x86 (32bit), Windows Server 2003 SP2 - X64 (AMD64/EM64T) and Windows Server 2003 SP2 - x86 (32bit) edition operating system environments. (Please see Important note #3 below) Attention: With controller firmware 7.86.32.00 and later, the DSM is supported on Windows 64bit ONLY. Please do not upgrade any storage subsystem to controller firmware to 7.86.32.00 or later if that storage subsystem has 32bit Windows hosts attached. A problem causing recursive reboots exists while using 7.36.08 and 7.36.12 firmware on IBM System Storage DS4000 or DS5000 systems. This problem is fixed in 7.36.14.xx and above firmware. All subsystems currently using 7.36.08 and 7.36.12 firmware MUST run a file system check tool (DbFix) before and after the firmware upgrade to 7.36.14.xx or higher. Instructions for obtaining and using DbFix are contained in the 7.36.14.xx or higher firmware package. Carefully read the firmware readme and the DbFix instructions before upgrading to firmware 7.36.14.xx or higher. For subsystems with firmware level 7.36.08 or 7.36.12, configuration changes should be avoided until a firmware upgrade to 7.36.14.xx or higher has been completed successfully. Subsystems not currently using 7.36.08 or 7.36.12 do not need to run DbFix prior to upgrading to 7.36.14.xx or higher. DbFix may be run after upgrading to 7.36.14.xx or higher, but it is not required. DbFix is only applicable to subsystems using 7.36.xx.xx or greater firmware. If problems are experienced using DbFix or the resulting message received is "Check Failed", DO NOT upgrade your firmware and contact IBM support before taking any further actions. (C) Copyright International Business Machines Corporation 1999, 2015. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in section 6.0 "Trademarks and Notices" in this document. Last Update: 08/28/2015 Please refer to corresponding Change History document for more information on new features and modifications. IMPORTANT: 1. This storage manager software package contains non-IBM code (Open Source code.) Please review and agree to the Non-IBM Licenses and Notices terms stated in the DS_Storage_Manager_Non_IBM_Licenses_and_Notices_v3.pdf file before use. 2. Microsoft Windows host attachment to the DS5300, DS5100, DS5020, DS4800, DS4700, DS4300, DS4200, DS4100, DCS3700, DS3950, and DS3500 requires the additional purchase of the IBM Ds3000/DS4000/DS5000 Microsoft Windows operating system Host Kit Option or Feature Code. The IBM DS3000, DS4000 and DS5000 Microsoft Windows Host Kit options contain the required IBM licensing to attach an Microsoft Windows Host System to the DS5300, DS5100, DS5020, DS4800, DS4700, DS4300, DS4200 DS4100, DS3950, DCS3700, and DS3500. Please contact your IBM service representative or IBM reseller for purchasing information. This host kit is shipped as standard in the DS4200 storage subsystem models 7VH, DS4700 storage subsystem models 70H, 70T, 72H 72T, the DS4800 storage subsystem models 80H, 82H, 84H and 88H, the DS5020 storage subsystem model 20A, and the DS3950 models 94H and 98H. Windows and Linux host kits are included with DCS3700 and DS3500. VMWare Host kit is also included with the DS3500. 3. There are two separate IBM DS Storage Manager host software version 11.20 packages for various CPU-platform versions of Microsoft Windows operating systems. The supported cpu-platforms are as followed: - 32-bit IA32 (intl386 or x86) - 64-bit (AMD64 or EM64T) x64 Please select the correct Storage Manager host software installer package for the CPU-platform of your Linux operating system (OS). Note: Starting with the Storage Manager host software version 10.8x, there is not any Storage Manager host software for the 64-bit Itanium 64 (IA64) edition of Microsoft Windows operating systems. 4. The Microsoft Windows NT4, Microsoft Windows 2000 and the Itanium2 64bit (IA- 64) editions of the Microsoft Windows 2003 and 2008 are not supported with this version of the IBM System Storage DS Storage Manager. In addition, the only DS4000/DS5000 Storage Manager host software support on Microsoft Windows XP Professional,Microsoft Windows Vista (English only), and Windows 7 operating systems is the DS Storage Manager client program. 5. Review section 3.2 "Hardware status and information" for the list of recommended fibre channel host bus adapters and their driver versions. Refer to the IBM System Storage Support Web Site or CD for the IBM System Storage DS Storage Manager Version 11 Installation and Host Support Guide. This guide along with the DS Storage Manager program Online Help provide the installation and support information. 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 release of the IBM DS Storage Manager 11.20 for Microsoft Windows Server 2012 R2, Windows Server 2012, Microsoft Windows Server 2008 SP2, Microsoft Windows Server 2003 SP2, and Windows Server 2008 SP2 R2 with HyperV Clustering operating system environments. This version of the DS Storage Manager host software is required for managing the DCS3700-all models, the DCS3860-all models and the DS3500- all models with controller firmware version 08.20.xx.xx. In addition, it is also recommended for managing IBM DS storage subsystems with controller firmware version 06.5x.xx.xx or higher installed. The IBM Storage Manager host software version 11.20 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 separate IBM DS Storage Manager host software version 11.20 packages for the following Microsoft Windows Server 2003-x86, Windows Server 2008-x86; Windows Server 2008-x64, Windows Server 2003-X64 64bit (AMD64 and EM64T) and Windows Server 2012. The WS03_WS08_X86_32bit, WS03_WS08_X64 CD and WS2012 directories contain the files necessary for installing the IBM DS Storage Manager Version 11.20 host software in the Windows Server 2003 - x86, Windows Server 2008 - x86, Windows Server 2003 x64 and Windows Server 2008 x64 64bit (AMD64 and EM64T) , 2008 R2 and Windows Server 2012 Operating System (OS) environments, respectively. Please select the appropriate directory for your operating system environment. The host software and storage subsystem firmware files are packaged separately and are available for download from the IBM System Storage Disk Storage Systems Technical Support web site: http://www.ibm.com/systems/support/storage/disk 2. This version of DS Storage Manager host software does not support Microsoft Windows NT4, Microsoft Windows 2000 and the Itanium2 64bit (IA- 64) editions of the Microsoft Windows 2003 and 2008 Operating System. In addition, the only DS Storage Manager host software support on Windows XP Professional OS, Windows Vista and Windows 7 is the DS Storage Manager client (SMClient) program from the IBM DS Storage Manager host software package for Microsoft Windows Server 2008- x86 (32bit); Windows 8 (English only) is the DS Storage Manager client (SMClient) program from the IBM DS Storage Manager host software package for Microsoft Windows Server 2012. The IBM System Storage DS Storage Manager Version 11.20 Installation and Host Support Guide 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 DS Storage Manager version 11.20 host software. Not all versions of Microsoft Windows operating systems are IO-attach support for each of the DS3950/DS4000/DS5000 storage subsystem model. Windows Operating Systems Supported ------------------------------------ -------------------------------------------------------------------------- | DS4000 |Windows Server 2003/2008| 2003/2008 | 2012 | | Storage Subsystem | 32bit | 64bit - X64 | 64bit - IA64 | | |-------------------|--------|---------------|--------------|--------------| | DS5300 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS5100 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS5020 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4800 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4700 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4500 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4400 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4300 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4200 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS4100 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS3950 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DCS3700 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DCS3860 | Yes | Yes | No | Yes | |-------------------|--------|---------------|--------------|--------------| | DS3500 | Yes | Yes | No | Yes | --------------------------------------------------------------------------- Note: Only the DS4300 with Standard (base) or Turbo options are supported for I/O attach with this release of DS Storage Manager Host Software for Windows. Products Supported ----------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |----------- |-----------|--------------|-------------------------| | DS5300 | N/A | 1818 | 53A | |----------- |-----------|--------------|-------------------------| | DS5100 | N/A | 1818 | 51A | |----------- |-----------|--------------|-------------------------| | DS5020 | N/A | 1814 | 20A | |----------- |-----------|--------------|-------------------------| | DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, | | | | | 88A, 88H, 80A, 80H | |----------- |-----------|--------------|-------------------------| | DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, | | | | | 70T, 70S, 72T, 72S, | |----------- |-----------|--------------|-------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |----------- |-----------|--------------|-------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |----------- |-----------|--------------|-------------------------| | DS4300 | FAStT 600 | 1722 | 60X, 60U, 60J, 60K | | | | | 60L | |----------- |-----------|--------------|-------------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | |----------- |-----------|--------------|-------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | |----------- |-----------|--------------|-------------------------| | DS3950 | N/A | 1814 | 94H, 98H | |------------|-----------|--------------|-------------------------| | DCS3700 | N/A | 1818 | 80C, 90C | |----------- |-----------|--------------|-------------------------| | DCS3860 | N/A | 1818 | 86C, 96C | |----------- |-----------|--------------|-------------------------| | DS3500 | N/A | 1746 | C2A, A2S, A2D, C4A, | | | | | A4S, A4D | |----------- |-----------|--------------|-------------------------| | DS3200 | N/A | 1726 | 21X, 22X, 22T, HC2, HC6 | |----------- |-----------|--------------|-------------------------| | DS3300 | N/A | 1726 | 31X, 32X, 32T, HC3, HC7 | |----------- |-----------|--------------|-------------------------| | DS3400 | N/A | 1726 | 41X, 42X, 42T, HC4, HC8 | ----------------------------------------------------------------- ATTENTION: 1. For the DS4400 and the DS4100 storage subsystems - all models (Standard /dual controller and Single Controller), the controller firmware version 06.12.xx.xx and later must be used. 2. The DS4300 with Single Controller option(M/T 1722-6LU,6LX,and 6LJ), FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models) storage subsystems can no longer be managed by DS Storage Manager version 10.50.xx.23 and higher. 3. For the DS3x00 storage subsystems, please refer to the readme files that are posted in the IBM DS3000 System Storage support web site for the latest information about their usage, limitations or configurations. http://www.ibm.com/systems/support/storage/disk ======================================================================= 1.2 Limitations ---------------- IMPORTANT: The listed limitations are cumulative. However, they are listed by the DS4000/DS5000 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 version 11.20 release (controller firmware 08.20.xx.xx) 1. During an update of the DSM on Windows, the driver stacks are torn down and rebuilt. The presence of host I/O during the upgrade can extend the time needed to tear down and rebuild the stacks, thereby extending the time to complete the upgrade operation beyond the time allowed by the Windows system API. This results in a timeout and failure of the DSM to complete the update operation. To avoid the issue, halt host I/O during the Storage Manager upgrade process. To recover from the issue, if the upgrade process fails, reboot the host and verify that the correct DSM version is installed. If the correct version is not installed, re-execute the appropriate upgrade process. No new limitations with Storage Manager version 10.86.x5.43 release (controller firmware 07.86.xx.xx) No new limitations with Storage Manager version 10.86.xx05.0035 release (controller firmware 07.86.xx.xx) New limitations with Storage Manager version 10.86.xx05.0028 release (controller firmware 07.86.xx.xx) 1. JAWs is only able to read out the title of the Window on which the initial focus is, it is not reading out any content inside that Window.(LSIP200327858) 2. When using OLH with JAWS screen reader, will have difficulty on navigating through the content in the Index Tab under Help content window due to incorrect and duplicate reading of the text. Please use the search/find tab in the OLH. (LSIP200331090) 3. When using the accessibility software JAWS 11 or 13, may hear the screen reading of a background window, even if the dialog is not in focus. Please use the INSERT+B key to get the reading reinitiated for the dialog in focus.(LSIP200329868) 4. Will not be able to find Tray tab on storage array profile dialog launch. User needs to navigate to Hardware tab to find Tray tab.(LSIP200332950) 5. Will not be able to perform multiple array upgrades having different firmware versions. Please choose to upgrade arrays having different firmware versions separately.(LSIP200335962) 6. May hit IO error if all the paths are lost due delayed uevent, Please always make sure to run 'multipath -v0' command to rediscover the returning path. This will prevent the host from encountering an IO error due to the host losing all paths should the alternate path fails. (LSIP200347725) 7. Volume copy pair itself would get removed, if user attempts to create a shadow copy of a source volume of a volume copy pair using VSS provider. There is no data loss as shadow copy creation is only allowed after 100% copy for volume copy is completed. User needs to manually re-establish the volume copy relation. This would result in re-copy of data from source volume to destination volume. (LSIP200352122) 8. There may be some confusion when the data is compared between summary tab and storage array profile. There is no actual functionality issue. The way the contents are labelled is not consistent.(LSIP200354832) New limitations with Storage Manager version 10.84.xx.30 release (controller firmware 07.84.xx.xx). 1. On a more than 30 drive disk pool with T10-PI enabled, the reconstruction progress indicator never moves because a finish notification is not sent to Storage Manager. When seeing this issue, just putting the replacement drive in the storage subsystem will allow the reconstruction to resume. (LSIP200298553) No new limitations with Storage Manager version 10.83.xx.23 release (controller firmware 07.83.xx.xx). New limitations with Storage Manager version 10.83.xx.18 release (controller firmware 07.83.xx.xx). 1. A non-T10PI logical drive can not be "volumecopied" to a logical drive with T10 PI functionality enabled. A non-T10 PI logical drive can only be volumeCopied to a non-T10 PI logical drive.(LSIP200263988) 2. Initiating dynamic logical drive expansion (DVE) on logical drives that are part of an asynchronous enhanced remote mirroring (ERM) without write order consistency will result in an error that is misleading because the controller is sending incorrect return code. DVE can only perform on logical drives having asynchronous ERM with write order consistency or synchronous ERM relationship.(LSIP200287980) 3. Cache settings can not be updated on thin logical drives. They can only be updated on the repository drives that are associated with these thin logical drives.(LSIP200288041) 4. Wait at least two minutes after canceling a logical drive creation in the disk pool before deleting any logical drives just created in the disk pool from the cancelled logical drive creation process. (LSIP200294588) 5. T10PI errors were incorrectly reported in the MEL log for T10PI- enabled logical drives that are participated in an enhanced remote mirroring relationship during the logical drive initializations.(LSIP200296754) 6. Having more than 20 SSD drives in a storage subsystem will result in SSD premium feature "Out-of-Compliance" error. One has to remove the extra SSD drives to bring the total number of SSDs in the storage subsystem to 20 or less.(LSIP200165276) 7. Pressing shift + F10 does not display the shortcut or context menu for the active object in the Storage Manger host software windows. The work-around is to use right-click on the mouse or the Windows key on the keyboard. (LSIP200244269) 8. Storage Manager subsystem management window performance might be slow due to Java runtime memory leak. The work around is to close the Storage Manager client program after the management tasks are completed. (LISP200198341) New limitations with Storage Manager version 10.77.xx.28 release (controller firmware 07.77.xx.xx). 1. Only one EXP5060 drive slot with a 3 TB SATA drive inserted can have the ATA translator firmware updated at any one time if the inserted 3 TB drive has "Incompatible" status. Simultaneously updating ATA translator firmware on multiple 3 TB drives having an "Incompatible" status might result in an "interrupted" firmware download state that requires the power- cycling of the subsystem to clear it. This limitation is reduced with the Storage Manager version 10.83 and later. The timeout was increased to accommodate simultaneously updating ATA translator firmware on up to five 3 TB SATA drives having an "Incompatible". 2. The 3 TB NL SAS drive can only be used to create non-T10PI arrays and logical drives. However, in certain conditions, where there are not any available hot-spare drives for T10PI enabled arrays, it will be used by the controller as a hot-spare for a failed drive in these T10PI enabled arrays. The controller will operate properly in this scenario and there are no adverse affects to the system while the 3 TB NL SAS drive is being used as the hot spare in a T10PI enabled array. This limitation is removed with controller firmware version 7.83.xx.xx and later. Please upgrade the controller firmware version 7.83.xx.xx and later if there is need to create a T10 PI-enabled arrays using 3TB NL SAS drives. New limitations with Storage Manager version 10.77.xx.16 release (controller firmware 07.77.xx.xx). 1. When you switch between the Search tab and the TOC tab, the topic that was open in the Search tab is still open in the TOC tab. Any search terms that were highlighted in the Search tab are still highlighted in the TOC tab. This always happens when you switch between the Search tab and the TOC tab. Workaround: Select another topic in the TOC to remove all search term highlighting from all the topics. 2. Support tab in the AMW kept open for longer duration will result in display of unevenly spaced horizontal marks. If the storage Manager is kept open for long durations a few grey lines may be seen on the Support Tab after restoring the AMW. Re-launching the AMW eliminates this problem. 3. The storage subsystem configuration script contains the logical drive creation commands with incorrect T10PI parameter. The workaround is to manually edit the file to change instances of dataAssurance parameters to T10PI. 4. The DS3500 subsysem does not support External Key Management at this time. Please contact IBM resellers or Representatives for such support in the future. New limitations with Storage Manager version 10.70.xx.25 release (controller firmware 07.70.xx.xx). 1. Kernel Panic reported on Linux SLES10 SP3 during controller failover. Probability of this issue happening in the field is low. Workaround: Avoid placing controllers online/offline frequently. Novell was informed about this issue. Opened Novell Bugzilla NVBZ589196. 2. CHECK CONDITION b/4e/0 returned during ESM download on DS5000 The interposer running LP1160 firmware is reporting an Overlapped Command (0B/4E/00) for a Read Command containing an OXID that was very recently used for a previous read command on the same loop to the same ALPA. In almost all cases, this command will be re-driven successfully by the controller. Impact should be negligible. Workaround: Can be avoided by halting Volume I/O prior to downloading ESM firmware. 3. If a host sees RAID volumes from the same RAID module that are discovered through different interface protocols (fibre/SAS/iSCSI) failovers will not occur properly and hosts IOs will error out. If the user does not map volumes to a host that can be seen through different host interfaces this problem will not occur. Workaround: Place controller online and reboot the server to see all volumes again. 4. Linux guest OS reported I/O error during Controller Firmware Upgrade on ESX4.1 with Qlogic HBA. The user will see I/O errors during controller activation from the guest OS due to mapped devices becoming inaccessible and offline. Workaround: This issue occurs on various Linux guest OSes, so to avoid the issue the user should perform an offline (no I/O to controllers) controller firmware upgrade. 5. I/O Error on Linux RH 4.8 after rebooting controller on DS3500 iSCSI. The devices will be disconnected from the host until the iSCSI sessions are re-established. workaround: Restart the iSCSI service. Configure the iSCSI service to start automatically on boot. 6. CFW Upgrade on 4.1 w/SLES 11 fails with IO error on SLES 11 Guest partition. This issue occurred if there is filesystem volume in SLES11 VM. User will see I/O errors and Filesystem volumes in SLES11 VMs will be changed to read-only mode. Workaround: User can perform controller FW upgrade with either no I/O running on SLES11 VM or no Filesystem created in SLES11 VMs. 7. "gnome-main-menu" crashes unexpectedly while install HSW on Suse 10. The crashes appear to happen randomly with other applications as well. After the crash the menu reloads automatically. Dismiss the prompt and the host will reload the application. This problem appears to be a vendor issue. 8. I/O errors on RHEL 4.8 guests on VMware 4.1 during controller reset. VMware has suggested VMware 4.1 P01 may resolve this issue. No support was issued for RHEL 4.8 guests under VMware 4.1 over SAS. Workaround: Use RHEL 5.5. 9. VMWare guest OS not accessible on iSCSI DS3524 (VMware SR 1544798051, VMware PR 582256). VMware has suggested VMware 4.1 P01 may resolve this issue. Workaround: Use Fibre Channel or SAS connectivity. 10. When DMMP is running in a BladeCenter SAS environment, I/O errors occur during failover and controller firmware operations. Support for Device Mapper and SLES 11.1 SAS has been restricted and will not be published. Workaround: Install RDAC. 11. SLES11.1ppc SAN boot fails on PS700 with 10 Gb Qlogic ethernet to DS3512. After configuration and install of Linux on a LUN using software iSCSI, the JS blade will not boot into the OS. Workaround: Use local boot, SAS or Fibre Channel. 12. ‘No response messages from Device Mapper devices with volumes on non-preferred path. Any I/O operations against volumes mapped to failed devices will timeout or hang. Workaround: This problem requires the host to be rebooted in order to restart I/O successfully. Update SLES11.1 to maintenance update 20101008 containing kernel version 2.6.32.23-0.3.1. Note that this kernel version has not been fully certified by LSI and should only be used if this issue is encountered. Bugzilla #650593 contains issue details and fix provided by Novell. 13. LifeKeeper 7.2.0 recovery kits require multiple host ports to use SCSI reservations. Workaround: Use two single port SAS HBAs. In this case each port will be represented as a host, and LifeKeeper will identify both separately. Another way to avoid the issue is to use MPP as the failover driver. 14. Unexpected "jexec" messages during mpp installation/un-installation on SLES 11.1. Workaround: None - https://bugzilla.novell.com/show_bug.cgi?id=651156 15. I/O write errors on mounted LifeKeeper volumes before node resources transfers to another node. recovery: I/O can be restarted as soon as node resources are transferred to another node in the cluster. Workaround: None. 16. Solaris 10u8 guest OS disks become inaccessible on ESX35u5 during sysReboot on array controller. This can be avoided by not using raw device mappings and instead using virtual disks. If raw device mappings are required, they must be used with virtual compatibility mode selected when adding the disks to the guest OS. Workaround: None. 17. Solaris 10u8 guest OSes reported I/O error during Controller Firmware Upgrade on ESX35U5 with Qlogic HBA. Permanent restriction. Workaround: Perform upgrade with no I/O. 18. Solaris guest OS reported I/O error during Controller reset on ESX35U5. The only recovery method is to rebooting the failed VM host. Permanent restriction. Please refer to the file LegacyStorageManagerLimitations-Windows.chg in the Storage Manager host software download package or in the !Readme CD directory for information on the legacy limitations that might still be applicable for your environment. ======================================================================== 1.3 Enhancements ----------------- The DS Storage Manager version 11.20 host software in conjunction with controller firmware version 8.20.xx.xx and higher provide the following new functions: - A media scan with redundancy check is enabled by default when a volume is created. - The storage capacity reserved for configuration information (and other system data) on each drive in a volume group or a disk pool is increased from 500 MB to 5.5 GB. - The storage management software now supports the DCS3700 and DCS3860 storage systems with Gen2 controllers. - Adds the ability to update drive firmware while the storage array is operating and online. All selected drives are updated while the volumes stay online and the storage array responds normally to read and write requests. - 4-K sector drives are supported through 512 emulation. - When a disk pool is being created, configuration candidates that offer tray loss protection or drawer loss protection are now identified and listed first. Tray loss protection and drawer loss protection ensure accessibility to your data if a total loss of communication occurs with a single drive tray or drawer. Your storage array must have six trays or drawers to be capable of this protection. Also, this implementation is focused on initial configuration; the tray loss protection or drawer loss protection is not maintained when additional drives are added to the disk pool. - If a drive is in an unresponsive state, the firmware automatically cycles power to the drive in an attempt to correct the problem. (The individual drive is powered off, then powered on.) If the drive does not recover, the drive is failed. If the drive does recover, reconstruction completes quickly because only the changed data needs to be reconstructed instead of the entire drive. - If failure of a drive is predicted, the data on that drive is automatically copied from the drive and the drive is powered down. If the affected drive is in a volume group, a hot spare must be available for automatic data copying. Data is not copied if the drive failure is not predicted. Also, if you manually fail a drive, you can copy the data from the drive to enable faster drive reconstruction. - The iSCSI statistics report now includes data pertaining to DCBX. This data is available only on the DCS3700 controller or the DCS3860 controller with specific iSCSI host interface cards. The report is accessible by selecting Monitor > Heatlh > iSCSI Statistics from the SANtricity Storage Manager Array Management Window. - Offloaded Data Transfers (ODX) provides a way to transfer data without using buffered read and buffered write operations and does not require direct host involvement with the data transfer operation. You can turn ODX on or off through the CLI. ODX is available only on the Windows Server 2012 operating system. For more information, please view the IBM System Storage DS Storage Manager Version 11.2 Installation and Host Support Guide and the IBM System Storage DS Storage Manager Version 11 Copy Services User's Guide. IMPORTANT: Do not use Storage Manager host software version 10.77.x5.xx and earlier to manage storage subsystems with 3 TB NL SAS and SATA drive option installed. ======================================================================= 1.4 Level Recommendation and Prerequisites for the update ----------------------------------------------------------- Note: 1. The IBM Storage Manager host software version 11.20 for Microsoft Windows operating systems, 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. 2. IBM recommends upgrading to Storage Manager version 10.83.x5.18 or later because it does not include the IBM Support Monitor Profiler code. This code has a security vulnerability that might allow unwanted XSS and SQL injections. If upgrading to Storage Manager version 10.83.x5.18 or later is not possible, one should remove the IBM Support Monitor Profiler code from the management station immediately. The instruction to uninstall IBM Support Monitor Profiler can be found in the IBM System Storage DS Storage Manager Version 11.20 Installation and Host Support Guide. Microsoft Windows NT4 SP6, Windows 2000 SP4 operating systems and the Itanium2 64bit (IA-64) editions of the Microsoft Windows 2003 and 2008 are not supported for this release of IBM DS Storage Manager version 11.20. The only supported Microsoft operating systems are the x86 and x64 editions of Windows Server 2003 with SP2, the x86 and x64 editions of Windows Server 2008, Windows Server 2012, Windows Server 2012 R2, Windows Vista (English only) 32bit, Windows 7 (English only) and Windows 8 (English only). For the 32bit Windows Vista, Server 2003 (X86), or Server 2008 (x86) 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 X64 64bit (AMD64 and EM64T) Microsoft Windows Server 2003, Microsoft Windows Server 2008 edition, Microsoft Windows Server 2012 and Microsoft Windows Server 2012 R2, IBM xSeries and other servers with minimum 2048MB Memory with Intel EM64T or AMD AMD64 processor(s) is recommended. (also see Dependencies section) Client Code levels at time of release are as follows --------------------------------------------------------- Important: 1. This release of IBM DS Storage Manager host software Client supports managing all DS3000/DS4000/DS5000/DCS storage subsystems with general released firmware versions from 06.5x.xx.xx up to 08.20.xx.xx. 2. There are two separate IBM DS Storage Manager host software version 11.20 packages for the following Microsoft Windows OSes - Windows 7, Windows 8, Windows Vista (English only) 32bit, Windows Server 2003 Intel Architecture (x86) and Windows Server 2008 (x86); Windows Server 2003 (x64); Windows Server 2008 (x64) and Windows Server 2008 R2 and Windows Server 2012. Please download the correct one for your operating system environment. 3. Beginning with storage manager version 10.75.xx.xx, the Microsoft Windows multipath driver - MPIO/DSM - is provided in a separate installer package. Operating Systems support Packs: - Windows Server 2012 - Windows Server 2008: SP2, R2, R2 SP1 - Windows Server 2003: SP2, R1, R2 - Windows Vista - Windows 8 (English only) - Windows 7 ============================================================================= Attention: Staring with the IBM DS storage manager version 11.20, the host software wizard incorporates both x64 and x86 into the same file. It implements logic to detect which version needs to be installed. Starting with Storage Manager version 10.77, the multipath driver DSM MPIO (or MPIO DSM) will not be part of the SMIA installer. It is packaged in a separate installer. You must run this installer to install the multipath driver DSM MPIO in the servers that are IO attached to the DS storage subsystems. From controller firmware 7.83.xx.xx, please use the correct DSM MPIO driver for your OS. Note: The MPIO/DSM multipath driver is supported with controller firmware version 06.12.xx.xx or higher. For Window Server 2003, Windows Server 2008 and Windows Server 2012, install the latest STORport driver with the MPIO/DSM multipath driver. In addition, the MPIO/DSM version 01.03.0305.0608 and later supports ALUA failover method when an appropriate ALUA host type, W2KALUA, is selected for the defined MS Windows host and the installed version of the controller firmware is of 7.83.xx.xx and later. DSM MPIO (or MPIO DSM) version support list ------------------------------------------- ------------------------------------------------------------------------------------------------ | |Windows Server |Windows Server |Windows Server |Windows Server |Windows Server | | CFW |2003 32ibit |2008 32bit |2008 R2 |2012 |2012 R2 | |---------------|---------------|----------------|---------------|---------------|---------------| | 07.83.xx.xx |01.03.0305.0608| 01.03.0305.0608|01.03.0305.0608|01.03.1305.0715| not supported | |---------------|---------------|----------------|---------------|---------------|---------------| | 07.84.xx.xx |01.03.0305.0608| 01.03.0305.0608|01.03.0305.0608|01.03.1305.0715|02.01.1305.1010| |---------------|---------------|----------------|---------------|---------------|---------------| | 07.86.xx.xx |not supported |not supported |01.03.0305.0750|01.03.1305.0750|02.01.1305.1010| |---------------|---------------|----------------|---------------|---------------|---------------| | 08.20.xx.xx |not supported |not supported |02.01.0305.1010|02.01.1305.1010|02.01.1305.1010| ------------------------------------------------------------------------------------------------ Starting with the IBM DS 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-11.20.0305.0002.exe. This wizard will install the following host-software packages: 1. IBM DS Storage Manager Client. 2. IBM DS Storage Manager Agent. 3. IBM DS Storage Manager Utilities. 4. IBM DS Storage Manager ESM. Refer to the http://www.ibm.com/systems/support/storage/disk IBM System Storage Disk Storage Systems Technical Support web site for the latest released code levels. ======================================================================= 1.5 Dependencies ----------------- ATTENTION: 1. The DS5020, DS3950, EXP5000, EXP810, EXP520, and EXP395 FC-SAS drives must have the FC-SAS interposer firmware version 2264 or later installed. Some drives with FC-SAS interposer firmware version earlier than version 2264 may report incorrect inquiry information during Start of Day. This causes the controller firmware to make the drive uncertified (incompatible), which in turn, causes the drive to no longer be accessible for I/Os. This condition will also cause the associated array to go offline. Since the array is no longer accessible, the controller firmware may not recover the cache for all LUNs under this array. This behavior may result in data not being written. If you believe that you have encountered this issue, please call IBM Support for assistance with the recovery actions. The FC-SAS interposer firmware version 2264 and later is available in the ESM/HDD firmware package version 1.78 or later. 2. The 3 TB SATA drive option for EXP5060 expansion enclosure requires ATA firmware version LW1613 and higher. The drive will be shown as "Incompatible" if it is installed in an EXP5060 drive slot with ATA translator firmware version older than LW1613. Please refer to the latest EXP5060 Installation, Users and Maintenance Guide for more information on working with the 3 TB SATA drive option. 3. The Storage Manager host software version 10.83.x5.18 or higher is required for managing storage subsystems with 3 TB NL FC-SAS drives. Storage manager version 10.83.x5.18 or higher in conjunction with controller firmware version 7.83.xx.xx and later allow the creation of T10PI-enabled arrays using 3 TB NL FC-SAS drives. 4. CURRENTLY, THE ONLY IBM DS 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 IBM DS STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM. 5. The only IBM DS storage subsystems that are supported by the 06.14.xx.xx or higher (06.14.xx.xx, 06.15.xx.xx, 06.16.xx.xx, 06.19.xx.xx or 6.23.xx.xx) controller firmware version are the DS4200 (06.16.88.xx or higher), DS4300 Standard-dual controller or Turbo models (06.19.xx.xx or higher), and the DS4500 (06.19.xx.xx or higher), DS4700 (06.16.4x.xx or higher) and DS4800 (06.14.xx.xx or higher) storage subsystems. Currently, there are not any controller firmware packages version 06.14.xx.xx and higher for other IBM DS storage subsystems. Do not download this controller firmware on any other IBM DS storage subsystems. 6. 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 IBM DS storage subsystem drive expansion enclosure ESM, the controller and the hard drive firmware. 7. 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. 8. The DS4700 and 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 DS4700 and DS4800 storage subsystems. 9. The version 06.16.xx.xx of the DS4700 or 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. IBM recommends installing the controller firmware version 6.23.xx.xx and higher in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 10. When using STORport miniport version of the Fibre Channel host bus adapter device driver, Windows Server 2003 service pack 1 must be installed along with the Microsoft Windows Server 2003 STORport hot- fix KB916048 - An updated Storport storage driver (version 5.2.3790.2723) is available for Windows Server 2003. The Windows Server 2003 service pack 1 and the STORport hot-fix 916048 are available for download at the Microsoft support web site. 11. The latest version of Microsoft Windows SCSIport and the STORport FC HBA device drivers do not support the BUSCHANGE=0 parameter. It requires the DS4000 storage subsystem controller firmware to be compatible with the MS Plug and Play driver. Not all versions of the DS4000 storage subsystem controller firmware are compatible with the Microsoft Plug and Play driver. Currently, only the controller firmware versions that are listed in the table below for each of the DS4000 subsystems, which support the SCSIport device drivers with BUSCHANGE parameter set to Microsoft required default value of 2, are compatible with the MS Plug-and-Play driver. ------------------------------------------ | DS4000 | Controller Firmware | | Storage Subsystem | Version Required | ------------------------------------------- | DS4700 | 06.16.8x.xx or later| | DS4800 | 06.15.2x.xx | | | 06.16.8x.xx or later| | DS4500 | 06.12.27.xx or later| | DS4400 | 06.12.27.xx or later| | DS4300 | 06.12.27.xx or later| | DS4200 | 06.16.88.xx or later| | DS4100 | 06.12.27.xx or later| ------------------------------------------ Do not use STORport miniport device driver or FAStT/DS4000 FC HBA SCSIport device driver version 9.1.2.11 and higher in the Microsoft Windows servers that have IO access to the DS4000 storage subsystems with controller firmware that are not listed in the controller firmware table above. Please check with your IBM reseller, IBM representative, or the DS4000 interoperability matrix for information on future DS4000 storage subsystems support of this device driver without BUSCHANGE=0 parameter. IBM DS Storage Manager version 11.20 host software requires the DS3000 /DS4000/DS5000 storage subsystem controller firmware be at version 06.xx.xx.xx or higher. The IBM IBM DS Storage Manager v9.60 supports storage subsystems with controller firmware version 04.xx.xx.xx up to 05.2x.xx.xx. The IBM DS Storage Manager v10.36 supports storage subsystems with controller firmware version 05.3x.xx.xx to 07.36.xx.xx. The IBM DS Storage Manager v10.70 supports storage subsystems with controller firmware version 05.4x.xx.xx to 07.70.xx.xx. ======================================================================= 2.0 Installation and Setup Instructions ----------------------------------------- Note: The web-download Storage Manager version 11.20 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 11.20 host software installer wizard. 2.1 Step-by-step instructions for this code update are as follows ------------------------------------------------------------------ 1. Install and update the device driver for the IBM FAStT, FC-2, FC2-133 single port or dual port, FC 4Gbps PCIx single port or dual port, Qlogic 4Gb/8Gb FC PCIe for IBM System X Fibre Channel Host Bus Adapters or the IBM-supported Host Bus Adapters for your environment. a. Install the hardware by using the instructions that come with the adapter. b. Review section 3.2 in this readme file for the minimum recommended device driver version for your Fibre Channel Host Bus Adapters. c. Install the IBM DS3000/4000/5000 Host Adapter device 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 IBM DS 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. For instruction to uninstall the IBM DS Storage Manager host software, please refer to the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide, the IBM System Storage DS Storage Manager Version 10.8 Installation and Host Support Guide or the IBM System Storage DS Storage Manager Version 11.20 Installation and Host Support Guide. If the previously installed DS3000/4000/5000 storage manager version is of 10 or later, the IBM DS storage manager host software can be updated with the new code from the installer without the need of uninstalling the existing storage manager host software packages first. Just click "Yes" in the window that the installer displays, stating that there are already installed IBM DS 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 System Storage DS Storage Manager Version 11.20 Installation and Host Support Guide for detailed installation instructions. Note: The Storage Manager installer might take up to 5 minutes to display the end user license for machine code (EULA) depending on the Operating System versions. 4. Install the Windows MPIO DSM multipath driver. Starting with the Storage Manger version 10.75.xx release, the Microsoft multipath driver MPIO DSM was packaged separately from the SMIA installer bundle that includes the SMClient, SMUtil and SMAgent. You must use this package to install the Microsoft multipath driver MPIO DSM on servers that are IO attached to the DS3500/DS3000/4000/5000 subsystems. To install, execute the package .exe file and click through the installer wizard. Note: To enable Asymmetric Logical Unit Access (ALUA) failover method with storage subsystems having controller firmware version 7.83.xx.x and later installed, the host type, W2KALUA (host region 21), must be selected for the defined host ports. 5. Upgrade the DS3000/DS4000/DS5000 storage subsystem firmware in the following order - 1. Controller firmware and NVSRAM 2. ESM firmware 3. Drive firmware Refer to the IBM System Storage DS Storage Manager Version 11 Installation and Host Support Guide 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 DS3000/DS4000/DS5000 drive expansion enclosure ESM, the DS3000/DS4000/DS5000 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/systems/support/storage/disk IBM System Storage Disk Storage Systems Technical Support web site for the the latest DS Storage Manager host software, the DS3000/DS4000/DS5000 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/systems/support/storage/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 and DS4300 storage subsystem have updated recommended drive-side cabling instructions. The DS4500 instructions are documented in the IBM System Storage DS4500 Installation, Users, and Maintenance Guide (GC27- 2051-00 or IBM P/N 42D3302). The DS4300 instructions are documented in the IBM System Storage DS4300 Installation, Users, and Maintenance Guide (GC26-7722-02 or IBM P/N 42D3300). Please follow the cabling instructions in these publication to cable the new DS4500 and DS4300 setup. If you have an existing DS4500 setup with four drive side minihub 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 and DS4300 Installation, Users, and Maintenance 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 IBM DS 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 DS4200 storage subsystem (machine type 1814): Depending on the ordering channels, the DS420 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage partitions. If the DS4200 storage subsystem is ordered with less than 64 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - 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 DS4700 storage subsystem (machine type 1814): Depending on the ordering channels, the DS4700-model 70 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16, 32, 64 or 128 storage partitions. Similarly, the DS4700-model 72 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16, 32, 64 or 128 storage partitions. If the DS4700 storage subsystem is ordered with less than 128 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. - IBM DS4800 storage subsystem (machine type 1815): Depending on the ordering channels, the DS4800 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16, 32, 64, 128, 256 or 512 storage partitions. If the subsystem is ordered with less than 512 partitions, an upgrade from 8 to 16, 8 to 32, 8 to 64, 16 to 32, 16 to 64, 32 to 64, 32 to 128, 64 to 128, 64 to 256, 128 to 256, 128 to 512, or 256 to 512 partition storage partitioning premium feature option can be purchased. - IBM DS5300 and DS5100 storage subsystem (machine type 1818): the DS5300 and DS5100 storage subsystem is shipped with a user selected 8, 16, 32, 64, 128, 256 or 512 storage partitions. If the subsystem is ordered with less than 512 partitions, various storage partition feature upgrade options can be purchased to increase the maximum number of supported storage partitions. 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 IBM DS storage subsystem 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 Cisco 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 IBM DS storage subsystem controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the IBM DS storage subsystem serial ports unless instructed by IBM Support. Incorrect use of the serial port might result in loss of configuration and/or loss of data. 7. All enclosures (including IBM DS storage subsystem with internal drive slots) on any given drive loop/channel should have complete unique ID's, especially the single digit (x1) portion of the ID, assigned to them. For example, in a maximum configured DS4500 storage subsystem, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosure id's with the same single digit such as 11, 21 and 31 should not be used on the same drive loop/channel. In addition, for enclosures with mechanical enclosure ID switch like DS4300 storage subsystems, EXP100 or EXP710 storage expansion enclosures, do not use enclosure ID value of 0. The reason is with the physical design and movement of the mechanical enclosure ID switch, it is possible to leave the switch in a “dead zone between ID numbers, which return an incorrect enclosure ID to the storage management software. The most commonly returned enclosure ID is 0 (zero). In addition to causing the subsystem management software to report incorrect enclosure ID, this behavior also result in enclosure ID conflict error with the storage expansion enclosure or IBM DS storage subsystem intentionally set the ID to 0. The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810 storage expansion enclosures did not have mechanical ID switches. Thus, they are not susceptible to this problem. In addition, these storage subsystems and storage expansion enclosures automatically set the Enclosure IDs. IBM recommendation is not make any changes to these settings unless the automatic enclosure ID settings resulting in non- unique single digit settings for enclosures (including the storage subsystems with internal drive slots) in a given drive loop/channel. 8. 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. 9. IBM recommends at least one hot spare per EXPxxxx drive expansion enclosure. A total of 15 hot-spares can be defined per IBM DS storage subsystem configuration. 10. Starting with the IBM DS 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 IBM DS 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) 11. When you configure a LUN from the IBM DS 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 IBM DS 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. 12. (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. 13. (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. 14. (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 DS4000 FC2, FC2-133 single or dual port and FC 4Gbps single or dual port FC HBA adapter "Port Down Retry Count" BIOS parameter must be change to 70 from the default of 30. You can either use the Qlogic SANsurfer (aka. FAStT Management Suite Java (FAStT MSJ)) program or the FC HBA Fast!UTIL program to change the setting in 32bit or X64 64bit servers. To invoke 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 Qlogic SANsurfer program to modify the setting from the Microsoft Windows operating system environment. This is also the recommended method to change NVSRAM setting in Intel Itanium II 64bit (IA64) servers. 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. The QLogic SANsurfer program can be downloaded from the Qlogic support web site. 2. (Not applicable for configurations with IBM DS storage subsystem having controller version 7.83.xx.xx and later installed) If a host in a cluster server configuration lost a physical path to a IBM DS 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 IBM DS 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 IBM DS Storage Manager 8.3 and higher firmware does not automatically map logical drives when the IBM IBM DS 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 IBM DS storage subsystem with controller firmware version 06.14.xx.xx or later. For IBM DS storage subsystem 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 IBM DS Storage Manager online help to learn more about creating storage partitions and changing host types. 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.script: 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.script: 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. - EnableAVT_W2K_S2003_noncluster.script: (Do not use this script when the installed storage subsystem controller firmware version is of 7.83.xx.xx and later) 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.script: 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) 5. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 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 ----------------------------------- Up to date interoperability information can be found at: http://www-03.ibm.com/systems/support/storage/config/ssic/ ======================================================================= 3.3 Unsupported configurations ------------------------------ The following lists configurations that are currently not being supported with IBM DS Storage Manager Version 11.20. 1. The IBM EXP395 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS3950. EXP810 drive enclosures are also supported in the DS3950 with the purchase of a premium feature key. 2. The IBM EXP520 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5020. EXP810 drive enclosures are also supported in the DS5020 with the purchase of a premium feature key. 3. The IBM EXP5000 Expansion Enclosure is not supported attached to any other IBM DS Storage Subsystems except the DS5100 and DS5300. 4. The DS4100 (machine type 1724-all models) storage subsystem does not support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC) drive expansion enclosure. 5. The DS4800 storage subsystem (machine type 1815-all models) does not support the attachment of the FAStT EXP500 and DS4000 EXP700 drive expansion enclosures. 6. The DS4200 (machine type 1814 - models 7VA/H) does not support the attachment of the DS4000 EXP100 (SATA), EXP710 (FC) and EXP810 (SATA and FC) drive expansion enclosures. In addition, it does not support Fibre Channel disk drive options. 7. The IBM DS4000 EXP420 Expansion Enclosure is not supported attached to any other IBM DS4000 Storage Subsystems except the DS4200. 8. The DS4100 with Single Controller option does not support the attachment of the DS4000 storage expansion enclosures. 9. The DS5100 and DS5300 storage subsystems do not support the attachment of the DS4000 EXP100, EXP700, EXP710 drive expansion enclosures. The EXP810 is only supported through an RPQ process. 10. The DS5000 EXP5000 drive expansion enclosure is supported attached to the DS5100 and DS5300 only. 11. The DS4700 and 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 DS4700 and DS4800 storage subsystems. 12. The DS4300 storage subsystem with Single Controller option does not support the controller firmware version 06.xx.xx.xx. The correct firmware version for these DS4300 storage subsystem models is 05.34.xx.xx. 13. 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. 14. The IBM Fibre Channel hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1814, 1815, 3542 and 3552. 15. A configuration in which a server with only one FC/SAS/iSCSI host bus adapter connects directly to any IBM DS storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC/SAS/iSCSI host bus adapter connects to both controller ports of any IBM DS storage subsystem with dual controllers via FC/SAS/Ethernet 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/systems/support/storage/disk 5.2 IBM System Storage Marketing Web Site: http://www.ibm.com/systems/storage 5.3 IBM System Storage Interoperation Center (SSIC) web site: http://www.ibm.com/systems/support/storage/ssic/ 5.4 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 DS Storage Manager host software, the DS4000/DS5000 storage subsystem controller firmware, the DS4000/DS5000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. For more information about how to register for support notifications, see the following IBM Support Web page: ftp.software.ibm.com/systems/support/tools/mynotifications/overview.pdf You can also check the Stay Informed section of the IBM Disk Support Web site, at the following address: www.ibm.com/systems/support/storage/disk ======================================================================= 6.0 Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DS3000 DS3500 DCS3700 DCS3860 DS4000 DS5000 FAStT 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.