This README file contains the latest information about installing IBM TotalStorage™ DS4000 Storage Manager version 9.15 for VMware ESX Server 2.5.2. Note: VMware ESX Server 2.0 is supported by the DS4000 Storage Manager version 8.x only. In addtion, 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. Important: There are not any IBM TotalStorage™ DS4000 Storage Manager host software package for the VMWare ESX server operating systems 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. (This can be the same workstation that you use for the browser-based VMware Management Interface.) The SMclient program is included in the IBM TotalStorage™ DS4000 Storage Manager version 9.15 for the 32 and 64 bit version of Linux operating system or the IBM TotalStorage™ DS4000 Storage Manager version 9.15 for Microsoft Windows Server 2003 host software packages. Refer to the IBM TotalStorage™ Support Web Site or CD 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. For other related publications refer to Related Publications in the installation and support guide. Last Update: 12/01/2005 Products Supported ---------------------------------------------------------------- | New Model | Old Model | Machine Type | Model | |------------|-----------|--------------|------------------------| | DS4800 | N/A | 1815 | 82A, 84A, 82H, 84H | |------------|-----------|--------------|------------------------| | DS4500 | FAStT 900 | 1742 | 90X, 90U | |------------|-----------|--------------|------------------------| | DS4400 | FAStT 700 | 1742 | 1RX, 1RU | |------------|-----------|--------------|------------------------| | DS4300 | FAStT 600 | 1722 | 6LX, 6LU, 6LJ, 60X | | | | | 60U, 60J, 60K, and 60L | |------------|-----------|--------------|------------------------| | DS4100 | FAStT 100 | 1724 | 100, 1SC | ----------- ---------------------------------------------------- IBM TotalStorage 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 Change History 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 Change History - 12/1/2005 Support the DS4100, DS4300, DS4400, DS4500 and DS4800 controller firmware versions that 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). Note: The drive enclosure EXP100 ESM must also be updated to version 9563 or later. The DS4100 storage subsystem with standard option is now supported the DS4000 Copy Services Remote Mirroring and VolumeCopy premium features. - Fix defect C291078 (90136/89954) - when managing DS4000 controllers with firmware version 06.10.xx.xx or 06.12.xx.xx installed, highlighting the selected drive firmware update package will result in no drives being listed as compatible in the select drives for firmware updating window. - Fix defect C290432 (91773) SM9_R3 MIB Naming violation causing compilation failure - Fix defect 87085 (~86641) Unable to see free capacity node of a migrated logical drive/array - Fix 87313 (~87099) RVM Repository Volume Cache States are missing from Array - Add 87941 (~85376) Support Diagnostic Data Capture (DDC) functions in the DS4000 controller firmware - Fix defect 88007 (~87397) (C273843) RVM logical drive status is inconsistent. The storage subsystem profile and RVM logical drive properties status can indicate "Not Available" when GUI fly-over status indicates optimal, mirror synchronized. Some RVM volumes update the status correctly over time while others don't appear to change from the "Not Available" state. - Fix defect 89457 Create FlashCopy wizard Subsystem Management online help incorrect in some circumstances - Fix defect 93883 Not Printing out Stack Trace in Diagnostic Data Capture - 6/28/2005 Support the DS4800 storage subsystems with controller firmware version 06.15.11.xx. With this version of firmware, the DS4800 controllers utilize all of the available data cache memory installed in each controller blade for I/O caching. Previously with controller firmware version 06.14.xx.xx, the DS4800 controllers used only the first 1G bytes of the installed data cache memory per controller for I/O caching. - 5/18/2005 Support the DS4800 storage subsystem with controller firmware version 06.14.xx.xx Support ESX Server 2.5.1 - 3/18/2005 Support for the DS4000 Storage Manager 9.12 with the DS4000 controller firmware version 06.12.xx.xx or higher. Support the DS4100 storage servers with standard option in the 06.xx.xx.xx controller firmware code thread. Support the FC/SATA intermix premium feature via the permium feature key file. - 2/8/2005 Support the controller firmware version 06.10.xx.xx or higher for the DS4300 storage servers with standard option. Support for the attachment of EXP710 drive enclosures to the DS4300 storage servers with standard option - 11/24/2004 Support for DS4000 Storage Manager 9.1 with DS4000 controller firmware version 06.10.11.xx - 08/20/2004 Support for DS4000 Storage Manager 9.1 with DS4000 controller firmware version 06.10.06.xx - 06/18/2004 Support for the DS4100 Storage Server - 08/27/2003 This is the first support release of the IBM TotalStorage™ DS4000 Storage Manager version 8.4 in VMware ESX Server 2.0. ======================================================================= 1.5 Dependencies -------------------------- ATTENTION: 1. DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP700 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 9326 OR HIGHER. IF THE EXP700 ESM FIRMWARE IS EARLIER THAN THE 9326 VERSIONS, THE EXP700 ENCLOSURE AND THE INSTALLED DRIVES MAY NOT BE DISPLAYED IN THE DS4000 SUBSYSTEM MANAGEMENT WINDOW AFTER THE CONTROLLER FIRMWARE IS UPGRADED. THE CURRENT RELEASE ESM FIRMWARE VERSION FOR THE EXP700 ESM IS 9327. 2. DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE VERSION 06.1X.XX.XX REQUIRES THAT THE FIRMWARE VERSION OF AN ATTACHED EXP100 ENVIRONMENTAL SERVICE MODULE (ESM) BE AT VERSION 955X OR HIGHER. IT IS NOT POSSIBLE TO UPGRADE EXP100 ESM FIRMWARE VERSIONS THROUGH 953X TO VERSION 955X WHEN THE CONTROLLER FIRMWARE IS AT 06.1X.XX.XX. TO DETERMINE THE FIRMWARE LEVEL OF AN EXP100 ESM, IDENTIFY THE PRODUCT LABEL LOCATED AT THE REAR OF THE EXP100 ENCLOSURE. ONLY LABELS ON WHICH THE FIELD REPLACEABLE UNIT (FRU) PART NUMBER READS 25R0156 POSITIVELY INDICATE THAT AN ESM MODULE IS RUNNING FIRMWARE VERSION 955X OR HIGHER. IF THERE IS NO LABEL OR THE PART NUMBER ON THE LABEL DOES NOT READ 25R0156, THE ESM MAY STILL HAVE THE FIRMWARE VERSION 955X OR HIGHER IF IT HAD BEEN PREVIOUSLY UPGRADED. IF NECESSARY, CONTACT YOUR IBM REPRESENTATIVE, SUPPORT, OR RESELLERS FOR ASSISTANCE. IN ADDITION, IT IS NOT POSSIBLE TO UPGRADE THE ESM FIRMWARE FROM VERSION 953X TO VERSION 956X OR LATER DIRECTLY. THE 953X ESM MUST BE UPGRADED TO VERSION 9554 FIRST BEFORE IT CAN BE UPGRADED TO VERSION 956X. 3. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED BY THE 06.12.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 - ALL MODELS, THE DS4300 WITH STANDARD (BASE) OR TURBO OPTIONS, THE DS4400 AND THE DS4500. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM. 4. The only DS4000 storage subsystems that are supported by the 06.14.xx.xx or 06.15.xx.xx controller firmware version are the DS4800 storage subsystems. Currently, there are not any controller firmware packages version 06.14.xx.xx or 06.15.xx.xx for other DS4000 storage subsystems besides the DS4800 subsystems. Do not download this controller firmware on any other DS4000 storage subsystems. 5. Always check the README files (especially the Dependencies section) that are packaged together with the firmware files for any required minimum firmware level requirements and the firmware download sequence for the DS4000 drive expansion enclosure ESM, the DS4000 storage subsystem controller and the hard drive firmware. 6. If the managed DS4000 storage subsystem had the FC/SATA intermix premium feature enable, do not upgrade the controller firmware from version 06.10.xx.xx to version 06.12.xx.xx until a FC/SATA intermix premium feature key file is generated and available. Once the controller firmware is upgraded to version 06.12.xx.xx, the FC/SATA intermix premium feature will be shown as out-of-compliance and the FC/SATA intermix premium feature key file is required to re-enable the feature. When the FC/SATA intermix premium feature is in out-of- compliance state, LUNs management functions like creations, deletions and modifications will not be operational. Please refer to the FC/SATA intermix premium feature activation card that was shipped with the FC/SATA intermix premium feature kit for instructions to generate the required premium key file. 7. The DS4800 storage subsystems do not support the attachment of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700 Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be attached to the DS4800 storage subsystems. 8. 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.15 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.15 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.15 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 CONTROLER FIRMWARE VERSION 05.41.1X.XX MUST BE UPGRADED TO CONTROLLER FIRMWARE VERSION 05.41.5X.XX FIRST BEFORE IT CAN BE UPGRADED TO CONTROLLER FIRMWARE VERSON 06.1X.XX.XX OR LATER. OTHERWISE, THE ERROR 231-FIRMWARE INCOMPATIBLE WILL BE DISPLAYED. 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. ======================================================================= 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 version 09.15.xx.06 release for DS4000 controller firmware version 06.12.xx.xx and 06.15.xx.xx release 1. The following error message may be encountered under certain conditions when attempting to create a 2 TB LUN using the Create Logical drive wizard in the Subsystem Management window: "Error 4 - The operation cannot complete because of an incorrect parameter in the command sent to the controller." To avoid this error message, you must take certain steps while using the Create Logical Drive wizard to create a 2 TB LUN. Within the Specify Capacity/Name window within the create logical drive wizard, you must not manually specify the numeric value '2' in the New logical drive capacity field in tandem with the "TB" Units designator. If you do this, the Error 4 message will be issued and you will be unable to create the 2 TB LUN. Click on the up or down arrows next to the input field to select the desire capacity instead. When using the arrows, the program will display the correct maximum logical drive capacity value that can be specified for a given capacity unit (TB, GB, or MB). New limitations with Storage Manager version 9.15.xx.xx and DS4000 controller firmware version 06.15.xx.xx release None New limitations with Storage Manager version 9.14.xx.05 and DS4000 controller firmware version 06.14.19.xx release 1. When using ESX Server with the DS4100 and DS4800 the failover policy must be manually changed to MRU from Fixed. This should be corrected with the release 3.0 of ESX Server. 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. New limitations with Storage Manager version 9.12.xx.08 and DS4000 controller firmware version 06.12.03.xx release 1. Do not cut and paste the information in the DS4000 Storage Manager online help into the DS4000 Storage Manager script command window or into the text file that will be used as input for the SMcli script engine. Extra space may be inserted in the required parameter names which will cause error(s) during the script command execution. (267873) 2. In the configuration that have both SATA-technology drives (EXP100) and Fibre-Channel technology drives (EXP700/EXP710/DS4100) behind the same DS4000 storage 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. 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. 8. When using two HBAs in one VMware server, LUN numbers must be the same for each HBA attached to DS4000 Storage Server. 9. 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. 10. 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. 11. 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. 12. 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. 13. 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. 14. 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. 15. 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. 16. 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. 17. 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. 18. 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. 19. 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.15 for VMWare operating systems supports the new version of controller firmware for the DS4100, DS4300, DS4400, DS4500 and DS4800 storage subsystem models to support the new 400G SATA hard drive option/CRU and the new 250G SATA drive CRU. 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. 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 or 2.5.1 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 TotalStorage 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. The ESX Server advanced option: "Disk.RetryUnitAttention" must be set to 1" for use with DS4000 Storage. 14. Please refer to the ESX Server 2.5 Administrator guides and README for more info on how to setup storage in a SAN environment. 15. 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. 16. 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. 17. 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. 18. All drive enclosures on any given loop should have complete unique ID's assigned to them. For example, in a maximum configured DS4500 storage server, enclosures on one redundant drive loop should be assigned with id's 10-17 and enclosures on the second drive loop should be assigned with id's 20-27. Enclosures id's 00 ~ 09 should not be used and enclosure id's with the same single digit such as 11 and 21 should not be used on the same drive loop. 19. The DS4500 storage subsystem has a new recommended drive-side cabling instruction. The instructions are documented in the IBM TotalStorage DS4500 Storage Subsystem Fibre Channel Cabling Guide (GC26-7813-00 or IBM P/N 39M6031.) Please follow the cabling instructions in this publication to cable the new DS4500 setup. If you have an existing DS4500 setup with four drive side minuhub installed that was cabled according to the previously recommended cabling instructions, please schedule down time as soon as possible to make changes to the drive side FC cabling. Refer to the IBM TotalStorage DS4500 Storage Subsystem Fibre Channel Cabling Guide for more information. =========================================================================== 4.0 WEB Sites and Support Phone Number -------------------------------------- 4.1 IBM TotalStorage™ Disk Storage Systems Technical Support web site: http://www.ibm.com/servers/storage/support/disk/ 4.2 IBM TotalStorage™ Marketing Web Site: http://www.ibm.com/servers/storage/disk 4.3 If you have any questions about this update, or problem applying the update go to the following HelpCenter World Telephone Numbers URL: http://www.ibm.com/planetwide 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 ToTalStorage™ 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.