IBM System Storage™ DS4000 Storage Manager version 9.19 for VMware ESX Server 2.5.3 and 3.0 Note: VMware ESX Server 2.0 is supported by the DS4000 Storage Manager version 8.x only. In addition, VMware ESX Server 2.1 is supported by the DS4000 Storage Manager version 9.1 only. VMware ESX Server 2.1 is not supported with DS4000 storage subsystems having version 06.12.xx.xx and higher controller firmware. VMWare ESX Server host attachment to the DS4000 storage subsystems requires the additional purchase of the IBM DS4000 VMWare Host Kit Option or Feature Code. The IBM VMWare Host Kit Option contains the required IBM licensing to attach a VMWare ESX Server host to the DS4000 storage subsystems. Please contact your IBM service representatives or IBM resellers for purchasing information. NOTE TO SERVICE – Reference RETAIN # N/A (C) Copyright International Business Machines Corporation 1999, 2006. 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: There are not any IBM System Storage™ DS4000 Storage Manager host software packages for the VMWare ESX server operating system environments. To manage the DS4000 storage subsystems that are IO attached to your VMware ESX Server hosts, you must install the DS4000 Storage Manager client software (SMclient) on a Windows or Linux management workstation. (This can be the same workstation that you use for the browser-based VMware Management Interface.) The SMclient program is included in the IBM System Storage™ DS4000 Storage Manager version 9.19 for the 32 and 64 bit version of Linux operating systems or the IBM System Storage™ DS4000 Storage Manager version 9.19 for Microsoft Windows operating systems host software packages. Refer to the IBM System Storage™ Support Web Site or IBM System Storage™ DS4000 Storage Manager host software package for the VMWare ESX server CD for the installation and support guide. In addition, the Docs directory in the IBM System Storage™ DS4000 Storage Manager host software package for the VMWare ESX server CD also contains others DS4000 publications that might provide helpful information. For other related publications refer to Related Publications in the installation and support guide. Last Update: 10/31/2006 Products Supported ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, | | | | | 88A, 88H, 80A, 80H | |------------|-----------|--------------|------------------------| | DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, | | | | | 70T, 70S, 72T, 72S | |------------|-----------|--------------|------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | FAStT 600 | 1722 | 6LX, 6LU, 6LJ, 60X | | | | | 60U, 60J, 60K, and 60L | |------------|-----------|--------------|------------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | |----------- |-----------|--------------|------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | ----------- ---------------------------------------------------- IBM System Storage DS4000 Manager version 9.1x for VMware does not support the FAStT500 and FAStT200 machine types 3552 and 2542) with ESX Server 2.1 or ESX Server 2.5 or higher. Please refer to the latest storage inter operability matrix and ServerProven matrix at the following web sites: http://www-1.ibm.com/servers/storage/disk/ds4000/interop-matrix.html http://www.pc.ibm.com/us/compat/nos/matrix.shtml CONTENTS -------- 1.0 Overview 2.0 Limitations 3.0 Enhancements 4.0 Helpful Configuration Information 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer ======================================================================== 1.0 Overview ------------------ 1.1 Overview ------------------- There are not any IBM System Storage™ DS4000 Storage Manager host software packages for the VMWare ESX server operating system environment. To manage the DS4000 storage subsystems that are IO attached to your VMware ESX Server hosts, you must install the DS4000 Storage Manager client software (SMclient) on a Windows or Linux management workstation and manage the DS4000 storage subsystem via out-of-band management method. (This can be the same workstation that you use for the browser- based VMware Management Interface.) The SMclient program is included in the IBM System Storage™ DS4000 Storage Manager version 9.19 for the 32 and 64 bit version of Linux operating systems or the IBM System Storage™ DS4000 Storage Manager version 9.19 for Microsoft Windows operating systems host software packages. The usage permission of the SMclient program in the IBM System Storage™ DS4000 Storage Manager version 9.19 host software packages for Windows and Linux does not give the user the entitlement to the Windows or Linux host IO privileges. In those DS4000 storage subsystems that require the Windows and Linux host entitlement kits/ options, these kits/options must be purchased before these servers can be IO attached to the DS4000 storage subsystems. The IBM Storage Manager host software version 9.19 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. Refer to the IBM System Storage™ Support Web Site or IBM System Storage™ DS4000 Storage Manager host software package for the VMWare ESX server CD (in the Docs directory) for the installation and support guide. In addition, the Docs directory in the CD-ROM also contains others DS4000 publications that might provide helpful information. Also, please refer to the readme file(s) that are included in the IBM System Storage™ DS4000 Storage Manager version 9.19 host software package(s) for Windows and Linux for the latest information on usage and installation. ======================================================================= 1.1 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 9330. 2. DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X WHEN THE CONTROLLER FIRMWARE IS AT 06.1X.XX.XX. TO DETERMINE THE FIRMWARE LEVEL OF AN EXP100 ESM, IDENTIFY THE PRODUCT LABEL LOCATED AT THE REAR OF THE EXP100 ENCLOSURE. ONLY LABELS ON WHICH THE FIELD REPLACEABLE UNIT (FRU) PART NUMBER READS 25R0156 POSITIVELY INDICATE THAT AN ESM MODULE IS RUNNING FIRMWARE VERSION 955X OR HIGHER. IF THERE IS NO LABEL OR THE PART NUMBER ON THE LABEL DOES NOT READ 25R0156, THE ESM MAY STILL HAVE THE FIRMWARE VERSION 955X OR HIGHER IF IT HAD BEEN PREVIOUSLY UPGRADED. IF NECESSARY, CONTACT YOUR IBM REPRESENTATIVE, SUPPORT, OR RESELLERS FOR ASSISTANCE. IN ADDITION, IT IS NOT POSSIBLE TO UPGRADE THE ESM FIRMWARE FROM VERSION 953X TO VERSION 956X OR LATER DIRECTLY. THE 953X ESM MUST BE UPGRADED TO VERSION 9554 FIRST BEFORE IT CAN BE UPGRADED TO VERSION 956X. 3. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED BY THE 06.12.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 - ALL MODELS, THE DS4300 WITH STANDARD (BASE) OR TURBO OPTIONS, THE DS4400 AND THE DS4500. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM. 4. The only DS4000 storage subsystems that are supported by the 06.14.xx.xx or higher (06.14.xx.xx, 06.15.xx.xx, 06.16.xx.xx, or 06.19.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 DS4000 storage 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. IN-BAND MANAGEMENT IS NOT SUPPORTED WITH VMWARE ESX SERVER. THERE ARE NOT ANY HOST SOFTWARE PACKAGES FOR THE VMWARE ESX SERVER OPERATING SYSTEMS ENVIRONMENT. THE STORAGE MANAGER 9.19 CLIENT PROGRAM MUST BE INSTALLED IN OUT-OF-BAND MANAGEMENT CONFIGURATIONS, PREFERABLY ON THE SAME SYSTEM THAT IS USED TO MANAGE THE ESX SERVER 2.5 OR HIGHER. THE DS4000 STORAGE MANAGER 9.19 CLIENT PROGRAMS FOR THE FOLLOWING OPERATING SYSTEMS - MICROSOFT WINDOWS 2000 AND WINDOWS SERVER 2003 AND LINUX THAT ARE INCLUDED IN THE CD. PLEASE REFER TO THE FOLLOWING DIRECTORIES IN THE CD FOR THE DS4000 STORAGE MANAGER 9.19 CLIENT PROGRAM THAT IS APPROPRIATE FOR THE OPERATING SYSTEM IN THE COMPUTER THAT IS USED TO MANAGE THE DS4000 STORAGE SERVER - WIN32 (WINDOWS 2000), WS03_32BIT AND WS03_64BIT (WINDOWS SERVER 2003 IA32 AND IA64, RESPECTIVELY) AND LINUX (REDHAT 3 or 4 AND SUSE SLES 8 or 9.) 9. THE DS4000 STORAGE SERVER WITH CONTROLLER FIRMWARE VERSION 05.41.1X.XX MUST BE UPGRADED TO CONTROLLER FIRMWARE VERSION 05.41.5X.XX FIRST BEFORE IT CAN BE UPGRADED TO CONTROLLER FIRMWARE VERSION 06.1X.XX.XX OR LATER. OTHERWISE, THE ERROR 231-FIRMWARE INCOMPATIBLE WILL BE DISPLAYED. 10. DS4000 storage subsystem controller firmware versions 6.12.16.xx or higher and EXP100 storage expansion enclosure ESM firmware version 9563 or higher are required to provide support for the new 400G SATA drive options and CRUs (P/Ns 39M4570 and 39M4575, respectively) in addition to the new 250G SATA drive CRUs (P/N 40K6837.) This new 250G SATA drive CRU is functionally equivalent to the previously-released CRUs (P/N 90P1349). 11. 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. 12. Controller firmware 06.16.xx.xx is required to support EXP810 storage expansion enclosures. 13. Controller firmware 06.16.4x.xx and higher is required for the DS4700-all models and the DS4800-model 80A/80H. These models do not support older 06.16.xx.xx versions of controller firmware. The attachment of EXP100 enclosures is not supported for these models. 14. Controller firmware 06.19.xx.xx is required for the DS4300- standard-dual controller or Turbo models and the DS4500-all models, for attaching the EXP810 storage expansion enclosures. The IBM DS4000 Storage Manager version 09.1x.xx.xx provides full management support for IBM machine types 1722 (DS4300 Standard or Turbo), 1724 (DS4100 Standard), 1742 (DS4400), 1742-900 (DS4500) storage controllers that have at least firmware version 06.10.02.xx, and 1815 storage controllers that have at least firmware version 06.14.xx.xx. In addition, the DS4000 Storage Manager version 09.1x.xx.xx also provides management capabilities to IBM Machine type 1722-6LU/X/J (DS4300) and 1724-1SC (DS4100) storage controllers that have at least firmware version 05.34.xx.xx and 05.42.xx.xx, respectively. ======================================================================= 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. All of the limitations should be reviewed before proceeding. New limitations with Storage Manager Installer (SMIA) package version 09.19.xx.06 release. 1. Can not increase the capacity of RAID arrays. RAID arrays with certain combinations of selected segment size and number of drives that made up the arrays will exceed the available working space in controller dacstore, causing a reconfiguration request (like expanding the capacity of the array) to be denied. These combinations are generally the largest segment size (512KB) with the number of drives in the array is 15 drives or more. There is no work-around. C324144 105008 2. Interoperability problem between the Tachyon DX2 chip in the DS4500 and the DS4300 storage subsystem controllers and the Emulex SOC 422 chip in the EXP810 expansion enclosure ESMs causing up to 5 Fibre Channel loop type errors to be posted in the DS4000 storage subsystem Major Event Log during a 24 hour period. There is a small window in the SOC 422 chip that multiple devices can be opened at one time. This ultimately leads to Fibre Channel loop errors of Fibre Channel link up/down, Drive returned CHECK CONDITION, and Timeout on drive side of controller. IBM recommends the use of the Read-Link-Status function to monitor drive loop for any problems in the drive loop/channel. There is no work-around. 3. The single digit of the Enclosure IDs for all enclosures (including the DS4000 storage subsystem with internal drive slots) in a given redundant drive loop/channel pair must be unique. For example, with four enclosures attached to the DS4300, the correct enclosure ID settings should be x1, x2, x3, and x4 (where x can be any digit that can be set). Examples of incorrect settings would be 11, 21, 31, and 41 or 12, 22, 32, and 62. These examples are incorrect because the x1 digits are the same in all enclosure IDs (either 1 or 2). If you do not set the single digit of the enclosure IDs to be unique among enclosures in a redundant drive loop/channel pair, then drive loop/channel errors might be randomly posted in the DS4000 subsystem Major Event Log (MEL), especially in the cases where the DS4300 storage substems are connected to EXP810s and EXP100s. In addition, enclosure IDs with same single digits in a redundant drive loop/channel pair will cause the DS4000 subsystem controller to assign a soft AL_PA address to devices in the redundant drive loop/channel pair. The problem with soft AL_PA addressing is that AL_PA address assignment can change between LIPs. This possibility increases the difficulty of troubleshooting drive loop problems because it is difficult to ascertain whether the same device with a different address or a different device might be causing a problem. 4. If a DS4000 subsystem undergoes any operation that causes the controller to reset and go through the start-of-day boot process while you are attempting to add hardware, drives, or logical drives associated with the controller, the controller will send alert event notifications to the DS4000 subsystem Major Event Log (MEL) Log. The events indicate that the drives or the logical drives are offline or failed. The event notifications in the MEL Log are expected during the time that the controller is going through a boot process. The workaround is to wait at least 10 minutes after the controller reset is complete before moving logical drives or adding hardware. Use the DS4000 subsystem MEL to verify the time of the last controller reset event. 5. In the DS4300 and DS4500 Installation, User's and Maintenance guides, there are references that might mislead the user into thinking that IBM does not support partially-filled storage expansion enclosures or storage subsystems. IBM does support partially-filled storage expansion enclosures or storage subsystems as long as at least two drives are installed in the storage expansion or subsystem enclosures. However, IBM does not support partially-filled storage expansion enclosures or storage subsystems where the empty slots are required to keep the number of hard drives in the redundant drive loop/channel pair not exceeding the maximum of 112 drives per drive loop/channel. This is to prevent inadvertently inserting drives in those slots causing the controller of getting into the state that might result in lost of access to the storage subsystem. 6. In DS4000 storage subsystem configurations with controller firmware 6.15.2x.xx and higher installed, the performance of write intense workloads such as sequential Tape restores to DS4000 Logical drives with large I/O request sizes (e.g. 256kB) is degraded if the DS4000 logical drives are created with small segment sizes such as 8KB or 16KB. The work around is to create the DS4000 logical drives with segment size of 64KB or higher. 7. Microsoft MSCS or Vmotion clustering is not supported in the ESX Server 3.0. 8. Microsoft MSCS or Vmotion clustering is supported on ESX Server 2.5.3 for all DS4000 storage subsystems that are certified for the VMWare ESX 2.5.3 operating environment, with the exception of the DS4700 and the DS4200 storage subsystems. 9. ESX Server 2.5.3 does not support 4Gbps Fibre Channel host bus adapters. The work-around is to upgrade to ESX Server 3.0, which supports 4Gbps Fibre Channel host bus adapters. Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.62 release None Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.44 release for the DS4000 controller firmware version 6.12.27.xx and 6.16.8x.xx None Limitations with Storage Manager Installer (SMIA) package version 09.16.xx.08 release for the DS4000 controller firmware version 6.16.xx.xx 1. Controller firmware 06.16.xx.xx does not support EXP100 storage expansion enclosures. Do not download it into DS4000 storage subsystems that have EXP100 enclosures attached. After the 06.16.xx.xx controller firmware is activated, the DS4000 storage subsystem will not recognize the drives in EXP100 enclosures, causing loss of data availability to the RAID arrays and logical drives that are defined in those drives. The controller firmware version 6.15.xx.xx and earlier must be installed in the DS4000 storage subsystems that have EXP100 SATA drive expansion enclosure attached instead. 2. The storage subsystem might not recognize the drives or drive expansion enclosure correctly which results in the displaying of error messages or the inability to perform storage subsystem management operations, such as creating logical drives or arrays or initializing arrays from the storage management software. This behavior could be caused by powering up a DS4000 storage subsystem without any drive expansion enclosures attached and then connecting one or more drive expansion enclosures to the storage subsystem after it completes boot process. The workaround is to make sure that the drive expansion enclosure(s) with at least two drives are connected to the DS4000 storage subsystem before you turn on the storage subsystem power. 3. Remove the drive(s) while the storage subsystem is online and then wait until the storage subsystem is going the boot process following a storage subsystem reboot event to reinsert the (new) drive(s) might cause the drives to be marked as failed after the storage subsystem completes the boot process. The workaround is to wait until the storage subsystem is back online before reinserting the drives. If the storage subsystem still does not recognize the drives, reconstruct the drives by using the Advanced -> Recovery -> Reconstruct menu function in the storage subsystem management window. 4. Uninstalling the storage manager host software package might leave the JAVA JRE directory behind. This problem might occur if you uninstall a copy of the SANtricity Storage Manager software that has been upgraded from a previous release. The newer installation package could not delete the JRE directory created with an older installation package. The workaround is to manually delete any directories left behind after uninstalling the software. 5. When creating remote logical drive mirrors through the SMCli script engine in the DS4000 Storage Manager client program, the following error might display during execution, stopping the remote logical drive mirror creation process: Error 173 - The operation cannot complete because the configuration number on the remote storage array is invalid. Some remote logical drive mirrors might have already been created. Rerun only the portion of the script that should be run to finish creating the rest of the remote logical drive mirrors. 6. A JavaScript error might cause the Glossary pop-up window to stay open when the help contents on the storage management software GUI are closed and reopened. Workaround None. This is a SUN JAVA defect. Limitations with SMIA package version 09.15.xx.06 release for DS4000 controller firmware version 06.12.xx.xx and 06.15.xx.xx release 1. The following error message may be encountered under certain conditions when attempting to create a 2 TB LUN using the Create Logical drive wizard in the Subsystem Management window: "Error 4 - The operation cannot complete because of an incorrect parameter in the command sent to the controller." To avoid this error message, you must take certain steps while using the Create Logical Drive wizard to create a 2 TB LUN. Within the Specify Capacity/Name window within the create logical drive wizard, you must not manually specify the numeric value '2' in the New logical drive capacity field in tandem with the "TB" Units designator. If you do this, the Error 4 message will be issued and you will be unable to create the 2 TB LUN. Click on the up or down arrows next to the input field to select the desire capacity instead. When using the arrows, the program will display the correct maximum logical drive capacity value that can be specified for a given capacity unit (TB, GB, or MB). Limitations with SMIA package version 9.15.xx.xx and DS4000 controller firmware version 06.15.xx.xx release None Limitations with SMIA package version 9.14.xx.05 and DS4000 controller firmware version 06.14.19.xx release 1. When using ESX Server prior to version 2.5.2 with the DS4100 and DS4800, the failover policy must be manually changed to MRU from Fixed. This issue is resolved with ESX 2.5.2 build 16390 and later. 2. When using ESX Server with the DS4100 and DS4800 the LUNs must be initially assigned to the A Controller (lowest numbered HBA). Once the LUNs are formatted, the path can be changed to the B Controller. This should be corrected with the version 3.0 release of ESX Server. Limitations with SMIA package version 9.12.xx.08 and DS4000 controller firmware version 06.12.03.xx release 1. Do not cut and paste the information in the DS4000 Storage Manager online help into the DS4000 Storage Manager script command window or into the text file that will be used as input for the SMcli script engine. Extra space may be inserted in the required parameter names which will cause error(s) during the script command execution. (267873) 2. In the configuration that have both SATA-technology drives (EXP100) and Fibre-Channel technology drives (EXP700/EXP710/DS4100) behind the same DS4000 storage server, 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 server 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 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 logical drives 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) Limitations with Storage Manager version 9.10.xx.05 and DS4000 controller firmware version 06.10.11.xx release 1. Do not update the DS4000 storage server 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 newer. If the EXP700 ESM firmware is earlier than the 9326 versions, the EXP700 enclosure and the installed drives may not be displayed in the DS4000 subsystem management window after the controller firmware is upgraded to 06.1x.xx.xx version. The workaround is to update the EXP700 ESM firmware to the version 9326 or newer first before upgrading the controller firmware to version 06.1x.xx.xx. (260160 - pr 82841) 2. When connecting the EXP100 drive expansion enclosures, one must set the single digit (X1) of the enclosure ID to unique values. This is to prevent the possibility that one of the drives in the EXP100 enclosures be assigned the same ALPA as the DS4000 controller blade under certain DS4000 storage subsystem reboot scenarios. (261188) Limitations with version 9.10.xx.02 release 1. The DS4000 Copy Service RVM is not supported at this time for the DS4100 and the DS4300 storage server 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 managed by the preferred owner/controller. There is no work-around. If the drive is currently managed by a non- preferred owner/controller, one can change the currently managed non-preferred owner/controller into currently managed preferred owner/controller. 3. Concurrent firmware download (downloading firmware/NVSRAM to the DS4000 storage server 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.10.xx.xx version. ALL IOs must be stopped during the version 06.10.xx.xx controller firmware upgrade from a 05.xx.xx version. 4. Do not pull or inserting 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. When instructing 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. 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. There is no work-around. 6. Staged firmware and NVSRAM download function is not available on the DS4000 700 (machine type 1742) models with firmware 06.1x.00.00 in conjunction with IBM Storage Manager 09.1x.xx.xx." 7. Auto LUN/Array Transfer is not supported. If a controller fails over arrays to the alternate controller and the failed controller is replaced and brought back online, the arrays do not automatically transfer to the preferred controller. This must be done manually by redistributing arrays. 8. When using VMFS volumes with virtual disk (.vmdk/.dsk) files, the Flashcopy and the VolumeCopy logical drives can only be read on a different ESX server than the ESX server which has the source logical drives that the Flashcopy or the Volumecopy logical drives are made from. If using the System/LUN (Raw) disk configuration the Flashcopy and the VolumeCopy logical drives can be used on the same ESX server which has the source logical drives. Limitations with Storage Manager version 8.4x.xx.xx (and earlier) and DS4000 controller firmware version 05.4x.xx.xx (and earlier) releases 1. There is currently not support for the Fibre Channel adapters in the VMWare ESX servers directly connecting to the DS4000 storage server host ports. The Fibre Channel switch must be in between the Fibre Channel Host Bus Adapter ports and the DS4000 storage server host ports. 2. In-band management is not supported with VMware ESX Server 2.5. The Storage Manager 9.1x client program must be installed in out-of-band management configurations, preferably on the same system that is used to manage the ESX Server. 3. LUN sharing across multiple ESX servers is only supported when configuring VMotion enabled hosts or Microsoft Cluster nodes. LUNs mapped to multiple ESX Servers must have the access mode changed to Shared. LUNS can be mapped to a Host Group for the ESX servers and will be available to all members of the Host Group. For additional information on Windows Clustering with ESX Server, please reference the ESX 2.5 Installation guide at http://www.vmware.com/support/pubs/. For additional information on VMotion please reference the VirtualCenter Administration guide at http://www.vmware.com/support/pubs/. 4. Dynamic Volume Expansion is not supported for VMFS formatted LUNS. 5. ESX Server versions 2.5 or higher supports the boot from san (root boot or SAN-boot) option with DS4000 storage. Booting ESX Server versions 2.1.X or earlier from DS4000 storage server logical drive (aka. Root-boot or SAN-boot) is not supported. 6. ESX Server 2.5 does not have the capability of running IBM DS4000 Management Suite Java (FAStT-MSJ) for Fibre Channel path diagnostics. 7. When using two HBAs in one VMware server, LUN numbers must be the same for each HBA attached to DS4000 Storage Server. 8. Please contact IBM Support, IBM resellers and IBM Representatives for the availability of DS4000 Copy Service features support for DS4000 Storage Server having LUNs mapped to an ESX 2.5 server. 9. The IBM DS4000 Storage Server hardware and software is designed to have redundant paths from the host system to ensure the availability of storage. However, it is possible to connect a single host adapter from the host system to one of the controller minihubs and then connect this minihub to the minihub of the other controller. This configuration will create a FC-AL loop between the host adapter and the two IBM DS4000 Storage Server controllers and no redundant path to the host system. When you connect the two minihubs together, always connect the "IN" port of one minihub to the "OUT" port of the other minihub or vice versa. Do not connect the "IN" port of one to the "IN" port of the other minihub or the "OUT" port of one minihub to the "OUT" port of the other minihub. 10. Dynamically changing the cache read ahead multiplier setting via the storage manager client may result in an error message indicating the operation has failed. Despite the error message, the request to change the cache read ahead multiplier will remain queued to the controllers and will eventually complete when I/O activity to the storage subsystem has subsided. In order to avoid the error message and any delays in the cache read ahead multiplier value changing, it is recommended to change the cache read ahead multiplier when the subsystem is in a quiesced state. 11. This following behavior applies for the direct Fibre Channel connection setup between the DS4300 storage server 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 server. 12. 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. 13. The DS4000 storage server 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 server configured with Fibre Channel drives. Slower response times of SATA disk drives compared to Fibre Channel disk drives cause higher I/O retries from the DS4000 storage server controllers, resulting in a greater number of informational events logged. In addition, the number of information events reported in the DS4000 storage server event log will also grow in proportion to the increase in I/Os to the Logical Drives. In all cases, the DS4000 storage server controller will always successfully service the timeout I/O on the subsequent retries. 14. Single controller DS4000 storage server models are not support at this time. Please contact your IBM representatives or resellers for availability of such supports in the future. 15. When saving the DS4000 storage server Major Event Log entries, it may take up to several minutes to save all entries in the event log depending on the DS4000 management workstation resources. However, the DS4000 Storage Manager client GUI will show the completion of the event log saving almost instantly. The work around is to check the file size of the file that the event log entries are saved periodically; if the file size does not change, the event log saving is completed. 16. Do not perform other storage management tasks, such as creating or deleting logical drives, reconstructing arrays, and so on, while downloading the DS4000 storage server controller firmware, NVSRAM or ESM or drive 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 server that you plan to update. 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. The DS4100 storage subsystems (machine type 1724) can not be connected to EXP700/EXP710 (FC) drive expansion enclosures. Please contact your IBM representatives for such support in the future. ======================================================================= 3.0 Enhancements ------------------------------ The DS4000 Storage Manager version 9.19 host software for VMware ESX operating systems in conjunction with the DS4000 storage subsystem controller firmware 06.19.xx.xx provides support for - Support for attaching the DS4000 EXP810 to the DS4300 Standard-Dual Controller models or Turbo models and the DS4500-All Models. 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. ======================================================================= 3.0 Helpful Configuration Tips ------------------------------ 1. Storage Management software should not be installed on the ESX server or within the Virtual Machines. ESX Server has its own built-in failover mechanism and path management is handled through the ESX Server Storage Manager GUI. 2. VMware Tools should be installed on all virtual machines using DS4000 logical drives. 3. The ESX Server Advanced options for SCSI device reset should be configured as follows: Disk.UseDeviceReset=0 (disabled for DS4000 logical drives) Disk.UseLunReset=1 (enabled for DS4000 logical drives) Disk.ResetOnFailover=0 This option should be enabled (changed to 1) when using System/LUN (Raw) disk mappings or when using Microsoft cluster nodes across multiple ESX servers as the Virtual Machine configuration file is edited to use the scsi target address (vmhbaX.X.X.X) instead of the VMFS volume label Disk.RetryUnitAttention=1 4. When using a "bootfromsan" configuration with volume mappings from multiple Controllers you must enable persistent bindings to ensure that the Controller containing the Boot LUN is the lowest numbered SCSI target address (vmhba0:0). If persistent bindings are not set the boot lun can be re-ordered to a higher numbered target address causing the server to not boot. To set persistent bindings run the command "/usr/sbin/pbind.pl -A" while the Controller containing the boot LUN is vmhba0:0. 5. ESX 2.1, 2.5, 2.5.1 or 2.5.2 server customers we recommend the use of "LNXCL" as the host type to disable AVT. This reduces path thrashing behavior in the VM kernel during failover. In certain conditions this change can cause the vmkernel to hang on boot up due to a known issue with LUN discovery in ESX Server. Prior to implementing this change, please reference the IBM RedBook: "Implementing VMware ESX Server 2.1 with IBM System Storage DS4000 ", available from the IBM support web-site. The LUN discovery issue is to be corrected with the ESX Server 2.5 or later release. 6. MRU (Most Recently Used) is the supported failover policy when AVT is disabled. Preferred Path can be configured using the DS4000 Storage Manager client and then using the Rescan SAN option within the Storage Management MUI. 7. LUNS should be assigned to the ESX Server starting with LUN number 0. 8. The Access LUN should not be mapped to the ESX server host. 9. The VMware ESX Server 2.1 and higher FC HBA driver includes failover support. You will need to have two HBAs in the server to enable failover. Using a single HBA is supported; but, you will not have path failover support. VMware ESX Server 2.5 or later does not have the capability to utilize FAStT Management Suite Java (FAStT MSJ) program for multi-path I/O configuration. Instead, use the VMware ESX server 2.5 instructions in the ESX Server 2.x Administration Guide to set up IO path fail-over support and to redistribute the LUNs between the FC HBAs. 10. Always use the VMware ESX Server driver for the FC HBA. Please refer to VMware documentation on how to install and configure these FC HBA drivers. 11. Unique partition labels should be used if multiple targets (multiple DS4000 ) are installed to insure proper labeling of logical volumes when the server is rebooted. 12. With ESX Server 2.1 or higher it is no longer necessary to reboot when creating or deleting LUNS. Use the Rescan SAN function within the Storage Management MUI to automatically recognize changes on the Storage Subsystem. 13. Please refer to the ESX Server 2.5 Administrator guides and README for more info on how to setup storage in a SAN environment. 14. 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. 15. 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 server serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 16. 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 Servers DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 Storage Servers DS4300 (IBM machine type 1722) and DS4100 (IBM machine type 1724) have two ports per controller. The DS4000 storage Server FAStT200 (IBM machine type 3542) has only one port per controller. The DS4800 storage Server (IBM machine type 1815) has four ports per controller. 17. All enclosures (including DS4000 storage subsystem with internal drive slots) on any given drive loop/channel should have complete unique ID's, especially the single digit (x1) portion of the ID, assigned to them. For example, in a maximum configured DS4500 storage subsystem, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosure id's with the same single digit such as 11, 21 and 31 should not be used on the same drive loop/channel. In addition, for enclosures with mechanical enclosure ID switch like DS4300 storage subsystems, EXP100 or EXP710 storage expansion enclosures, do not use enclosure ID value of 0. The reason is with the physical design and movement of the mechanical enclosure ID switch, it is possible to leave the switch in a “dead zone” between ID numbers, which return an incorrect enclosure ID to the storage management software. The most commonly returned enclosure ID is 0 (zero). In addition to causing the subsystem management software to report incorrect enclosure ID, this behavior also result in enclosure ID conflict error with the storage expansion enclosure or DS4000 storage subsystem intentionally set the ID to 0. The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810 storage expansion enclosures did not have mechanical ID switches. Thus, they are not susceptible to this problem. In addition, these storage subsystems and storage expansion enclosures automatically set the Enclosure IDs. IBM recommendation is not make any changes to these settings unless the automatic enclosure ID settings resulting in non- unique single digit settings for enclosures (including the storage subsystems with internal drive slots) in a given drive loop/channel. 18. The DS4500 and DS4300 storage subsystem have new 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 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 and DS4300 Installation, Users. and Maintenance Guide for more information. =========================================================================== 4.0 WEB Sites and Support Phone Number -------------------------------------- 4.1 IBM System Storage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 4.2 IBM System Storage™ Marketing Web Site: http://www.ibm.com/servers/storage/disk 4.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 server controller firmware, the DS4000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. To be notified of important product updates, you must first register at the IBM Support and Download Web site: 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. ======================================================================= 5.0 Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DS4000 System Storage™ the e-business logo xSeries pSeries HelpCenter Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United states, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds. ESX Server is a registered trademark of VMware Corporation. Other company, product, and service names may be trademarks or service marks of others. ======================================================================= 6.0 Disclaimer --------------- THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 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. Refer to the appropriate Storage Manager Client package for the Operating system that you plan to use for management of the DS4000 Storage Subsystem. Server is a registered trademark of VMware Corporation. Other company, product, and service names may be trademarks or service marks of others. ======================================================================= 6.0 Disclaimer --------------- THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 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. Refer to the appropriate Storage Manager Client package for the Operating system that you plan to use for management of the DS4000 Storage Subsystem.