IBM System Storage™ DS4000 storage subsystem controller firmware version 06.60.34.00 for the DS4800-all models, DS4700-all models, DS4500-all models, DS4300-all dual controller models, and DS4200-all models storage subsystems only. IMPORTANT: DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM MODEL. Please contact your IBM representatives, Resellers or the DS4000 SSIC Inter-operability matrix for the support of this controller firmware thread on other DS4000 storage subsystems. This firmware version supports the intermix of the EXP810, EXP710 and the EXP100 storage expansion enclosures behind the IBM DS4000 TotalStorage™ DS4300, DS4500, DS4700 and DS4800 storage subsystems. The IBM DS Storage Manager host software version 10.60.x5.17 or higher is required to manage DS4000 storage subsystems with controller firmware version 6.60.34.00 installed. ATTENTION: EXP700 expansion enclosures will be supported with firmware levels 06.60.08.xx, 6.60.17.xx, 6.60.22.xx, and 6.60.34.xx on all DS4300 and DS4500 machine types (all models except DS4300 SCU). (C) Copyright International Business Machines Corporation 1999, 2010. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before commencing with any firmware upgrade procedure, use the Storage Manager client to perform a Collect All Support Data capture. Save this support data capture on a system other than the one that is being upgraded. Note: Before using this information and the product it supports, read the general information in section 6.0 "Trademarks and Notices" in this document. Refer to the IBM System Storage™ Support Web Site or CD for the IBM System Storage DS Storage Manager Version 10 Installation and Host Support Guide. This guide along with the DS Storage Manager program Online Help provide the installation and support information. For other related publications, refer to Related Publications in the Installation, User's and Maintenance guide of your DS4000 storage subsystem or storage expansion enclosures. Last Update: 11/16/2010 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 | |------------|-----------|--------------|-----------------------| | DS4300 | FAStT 600 | 1722 | 60X, 60U, 60J, 60K, | | Standard/ | Standard/ | | 60L | | Base | Base | | (Base or Turbo | | or Turbo | or Turbo | | option) | |------------|-----------|--------------|-----------------------| | DS4200 | N/A | 1814 | 7VA, 7VH | ------------ -------------------------------------------------- Notes: 1. The DS4000 storage subsystem controller firmware version 06.60.34.00 with its associated NVSRAM file ARE NOT AVAILABLE for the following DS4000 storage subsystems - DS4100 with Standard (base) or Single controller option (M/T 1724-all models), DS4300 with Single Controller option (M/T 1722 - models 6LX and 6LU), DS4400 (M/T 1742 - models 1RX and 1RU), FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models). The following table shows the first four digits of the latest 6.60.xx.xx controller firmware versions that are currently available for various models of the DS4000 storage subsystems. --------------------------------------------------- | DS4000 Storage | Controller firmware version | | Subsystem Model | | |------------------|--------------------------------| |------------------|--------------------------------| | DS4800 (1815) | 06.60.34.xx | | | | |------------------|--------------------------------| | DS4700 (1814) | 06.60.34.xx | |------------------|--------------------------------| | DS4500 (1742) | 06.60.34.xx | |------------------|--------------------------------| | DS4400 (1742) | 06.12.56.xx | |------------------|--------------------------------| | DS4300 Turbo | 06.60.34.xx | | Option (1722) | | |------------------|--------------------------------| | DS4300 | 06.60.34.xx | | Standard Option | | | (1722) | | |------------------|--------------------------------| | DS4300 Single | 05.34.10.xx | | Controller Opt. | (for DS4300 SCU | | (SCU)(1722) | only) | |------------------|--------------------------------| | DS4200 (1814) | 06.60.34.xx | |------------------|--------------------------------| | DS4100 (1724) | 06.12.56.xx | | (standard dual | | | Single | | | controller Opt.)| | |------------------|--------------------------------| | FAStT500 (3552) | 05.30.25.xx | |------------------|--------------------------------| | FAStT200 (3542) | 05.30.25.xx | --------------------------------------------------- 2. For the DS4300 storage subsystems with Single Controller option, the controller firmware version 05.34.xx.xx and its associated NVSRAM file must be used. DO NOT ATTEMPT TO DOWNLOAD the controller firmware version 06.xx.xx.xx into these DS4300 storage subsystem with single controller option models. 3. For the FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models)storage subsystems, the controller firmware version 05.30.xx.xx and its associated NVSRAM file must be used. DO NOT ATTEMPT TO DOWNLOAD the controller firmware version 06.xx.xx.xx into these DS4000 storage subsystems. ======================================================================= CONTENTS -------- 1.0 Overview 2.0 Installation and Setup Instructions 3.0 Configuration Information 4.0 Unattended Mode 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer ======================================================================= 1.0 Overview -------------- The IBM System Storage™ DS4000 storage subsystem controller firmware version 06.60.34.00 release includes the storage subsystem controller firmware and NVSRAM files for the DS4800-all models, DS4700-all models, DS4500-all models, DS4300-all dual controller models, and DS4200-all models storage subsystems only. This firmware supports the attachment of the DS4000 EXP810 storage expansion enclosures to the IBM DS4000 TotalStorage™ DS4300, DS4500, DS4700, and DS4800 storage subsystems. It is also required to support the intermix of the EXP810, EXP700/710 and the EXP100 storage expansion enclosures behind the IBM System Storage™ DS4000 storage subsystems. The IBM DS Storage Manager host software version 10.60.x5.17 or higher is required to manage DS4000 storage subsystems with controller firmware version 6.60.34.00 installed. ATTENTION: DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS4000 STORAGE SUBSYSTEM MODEL. The IBM IBM System Storage DS Storage Manager Version 10 Installation and Host SUpport Guide is available on IBM's Support Web Site as a down-loadable Portable Document Format (PDF) file. In addition, the DS4000 FC/SATA intermix premium features and the DS4000 Copy Services premium features; FlashCopy, VolumeCopy, and Enhanced Remote Mirroring are separately purchased options. The DS4000 Storage partitioning premium feature is standard on all IBM DS4000 storage subsystems with the exception of the IBM DS4100 (machine type 1724 with Standard or Single Controller options) and the DS4300 (machine type 1722 with Standard or Single Controller options) storage subsystems. Please contact IBM Marketing representatives or IBM resellers if you want to purchase the IBM DS4000 Storage partitioning premium feature option for it. See section 3.3 "Helpful Hints" for more information. The DS4000 Storage Controller firmware 06.60.34.00 release is available ONLY for the IBM machine types 1815-models 80A, 80H, 82A, 82H, 84A, 84H, 88A, and 88H(DS4800) and 1814-models 70A, 70H, 72A, 72H, 70T, 70S, 72T, and 72S(DS4700) and 1742-models 90X and 90U(DS4500) and 1722-models 60X, 60U, 60J, 60K and 60L (DS4300 dual- controller)and 1814-models 7VA and 7VH(DS4200). The DS4000 Storage subsystem controller firmware 06.60.34.xx release is not available for all models of the following IBM machine types - 1742-models 1RU and 1RX, 1724, 3542, or 3552. IBM DS Storage Manager version 10.36.x5.13 host software requires the DS4000 storage subsystem controller firmware be at version 05.30.XX.XX or higher. The only IBM DS4000 Storage Manager supported on DS4000 storage subsystems with controller firmware version 04.xx.xx.xx up to 05.2x.xx.xx is version 09.60.xx.xx. Refer to the IBM Support Web Site for the latest Firmware and NVSRAM files and DS4000 Storage Manager host software for the IBM DS4000 Storage Subsystems. http://www.ibm.com/systems/support/storage/disk 1.1 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. Note: For limitations in certain operating system environment, refer to the readme file that is included in the DS4000 Storage Manager host software package for that operating system environment. The condition when LUNs within a Raid array have split ownership between the two controllers could possibly see false positives on synthesized PFA has been corrected by CR151915. The stagnant I/O will be discarded. In order to utilize the stagnant I/O functionality, configure arrays so that all LUNs in an array are owned by one controller. Limitations with version 06.60.34.00 release None Limitations with version 06.60.22.00 release. 1. Collect All Support Data may on occasion be incomplete. Some files may be missing. Workaround is to recollect the data. 2. Unexpected Timeouts on EXP810 Expansion Drawers Problem or Restriction - When you power up a storage subsystem that contains EXP810 expansion drawers, the loop initialization protocols (LIPs) do not complete, with the result that the expansion drawers time out and are not included in the storage subsystem. Workaround - This problem is usually caused by having too many EXP810 expansion drawers attached to one drive port on the controller module. There should be no more than four EXP810 expansion drawers attached to one port. If more than four EXP810 expansion drawers are in the storage subsystem, connect four to one port, and the remaining expansion drawers to the second port on the same channel. Support Information - CR 154265. 3. Empty Support Bundle File Generated Problem or Restriction - Following a controller failure, a support bundle file is automatically generated, but the file is empty (file size = 0 Kb). Workaround - The support files can be manually collected and compressed by going to the following directories: a. In Windows, go to \client\data\monitor\tmpxxxxx (where is the directory specified at installation, and tmpxxxxx is the temporary directory in which the files are stored). b.In a Unix-based operating system, go to /var/opt/SM/monitor/tmpxxxxx (where tmpxxxxx is the temporary directory where the files are stored). To ensure that the automatic generation feature remains enabled, the Persistent Monitor should be restarted. To restart the Persistent Monitor, follow the appropriate procedure below: In Windows a Go to Windows Services >> Storage Array Event Monitor. b Double-click on the Persistent Monitor entry. c Click Stop. d Click Start. e Click OK and exit the Windows Services window. In a UNIX-based operating system, use the command line interface to enter the following sequence of commands: SMmonitor stop SMmonitor start Support Information - CR 154448. 4. Disable autoSupportConfig Command Does Not Work Operating System - AIX Problem or Restriction Using the CLI command disable autoSupportConfig does not work. Workaround - This feature is not supported in 10.50. Support Information - CR 153601. 5. Logical Drive Creation Using the Script Editor Fails Syntax Verification Operating System - Windows 2003 Problem or Restriction - When using the script editor to create a logical drive, entering a logical drive capacity of two digits (for example, 20Gb) results in a failure of the “verify syntax,” and the logical drive is not created. Workaround - The syntax requires a space between the digits and the unit of measure for example, (20 Gb). Insert the space and the command should work. Support Information - CR 152600. Limitations with version 06.60.17.00 release. None Limitations with version 06.60.08.00 release. none Limitations with version 06.60.02.xx release. 1. RHEL5 on System p (Linux on Power) is not supported with this release. 2. Using In-Band Management with RHEL5 is not supported with this release. Out-of-Band Management must be used. 3. Linux on Power support of JS20 blades with QLogic fail-over driver is not supported at this time. (BZ 23360) 4. SAN Boot on RHEL3 is restricted to initial root installation on Fibre Channel LUN ID 0. 5. SAN Boot is not supported on IBM JS20 server blades with the initial release SLES 9 kernel. 6. SAN Boot is only supported on JS20 server blades with SLES9 w/SP1 and above kernel. (6-3-2005) 7. Storage Management software should not be installed on the ESX Server. 8. Async RVM will only work at communication speeds of 10Mbytes or higher. Limitations with version 06.23.05.00 release. 1. EXP500 and EXP700 storage expansion enclosures are not supported by this version of the controller firmware (6.23.xx). EXP700 storage expansion enclosures can be upgraded to an EXP710s using the DS4000 EXP700 Models 1RU-1RX Switched-ESM Option Upgrade Kit before they are recognized by the controller firmware version 6.23.xx. ATTENTION: DO NOT DOWNLOAD this controller firmware version INTO THE DS4500 STORAGE SUBSYSTEMS WITH EXP500S AND EXP700S OR DS4300 WITH EXP700S EXPANSION ENCLOSURES ATTACHED. AFTER THE CONTROLLER FIRMWARE VERSION 06.23.XX.XX IS ACTIVATED, THE DS4500 AND DS4300 STORAGE SUBSYSTEMS WILL NOT RECOGNIZE THE DRIVES IN EXP700 AND EXP500 (FOR DS4500 ONLY) ENCLOSURES, CAUSING LOSS OF DATA AVAILABILITY TO THE RAID ARRAYS AND LOGICAL DRIVES THAT ARE DEFINED IN THOSE DRIVES. Please note section 1.4 "Dependencies" for EXP700 supported controller firmware levels. 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 (MEL) 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 storage subsystem, 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 subsystems 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. DS4400, FAStT200 and FAStT500 subsystems, which are currently withdrawn from market, will not be supported by the controller firmware version 6.23.xx.xx code thread. 5. During array and logical drive creation using SATA drive, it is common to see Destination Drive Event reported in the MEL against the drives being used in the array and logical drive. These events are not indicative of a real problem but are the result of a limitation in SATA technology at the present time. So, when creating arrays and logical drives using SATA drive, the Destination Drive Events being reported against the drives being used in the creation of the array and logical drive can be ignored. 6. MEL Check Condition type b/88/1 is a vendor specific event that is associated with SATA E-DDM drives. This event is the result of some other error. If these events are present in the MEL, you should also look for the presents of other drive error or check conditions to identify the source of problem. 7. If you are adding an EXP810 and attaching it to a EXP710 on the same redundant drive loop channel, after upgrading ESM firmware to a EXP810 that is attached to a EXP710 on the same redundant drive loop channel, you may get a the following message in Recovery Guru. "Drive Enclosures Not Cabled Correctly" This is the result of a failed message between the EXP710 and EXP810 switched ESMs. The message informs another switched ESM that it is attached to another switched ESM. The controllers also use this message to determine if storage expansion enclosures with switched ESMs are clustered correctly, and what causes the Recovery Guru message. The workaround is as follows: a. Verify through DS4000 Storage Manager Client that there is no lose of path redundancy to any of you storage expansion enclosures. b. Use the MEL to identify which storage expansion enclosures (i.e.EXP710, EXP810) is reporting the incorrect cabling, as well as which loop/channel (A side or B side). When this occurs, you will find a MEL Event 2835 for each affected enclosure. Enclosure and loop/channel identification are part of the event information. c. For each MEL event, for the Fibre Channel connection between the enclosure (i.e. 810, 710) identified in the MEL event and the next enclosure or controller (i.e. EXP810, EXP710, DS4800, DS4700, DS4200), unplug the cable from the SFP on one side and plug it back in. d. Repeat until all connections between the enclosures mentioned in the "Drive enclosures not cabled correctly" MEL have been unplugged and plugged back in. Note that a connection between a enclosure and the adjacent enclosure/controller only needs to be unplugged/inserted once at one end. 8. With the release of 6.23.xx.xx controller firmware, when deleting a volume that is part of a Remote Volume Mirror relationship, the following steps are required before volume deletion: a. Disable Media Scan on the DS4000 Storage subsystem you are deleting the volume from. b. Break remote mirror relationship associated with the logical drive or drives Once all volume deletion have been completed, re-enable Media Scan. Failure to perform these step may result in a controller reboot. 9. When deleting volumes that are part of a array made up of SATA drives, in some rare instances you may get an error message stating that the volume deletion has failed. However, if you check further in the Storage Manage GUI you will find that the volume was deleted. 10.SAN Volume Controller (SVC) customer are now allow to download ESM firmware with concurrent I/O to the disk subsystem at controller firmware levels of 6.23.05.xx or higher, with the following restrictions. 1) The ESM Firmware upgrade must be done on one disk expansion enclosure at a time. 2) A 10 minute delay from when one enclosure is upgraded to the start of the upgrade of another enclosure is required. Confirm via the Storage Manager Application's "Recovery Guru" that the DS4000 status is in an optimal state before upgrading the next enclosure. If it is not, then do not continue ESM firmware upgrades until the problem is resolved. 11.Customer with IBM branded Hitachi FC drives should verify that these drives are at drive firmware FQ8, or later, before doing a controller firmware or ESM firmware download. It has been observed by IBM Support that customer's with older versions of the Hitachi FC drive firmware have experienced failure of these Hitachi drives during controller firmware and ESM firmware downloads. Upgrading the drive firmware to FQ8 will prevent this problem. Hitachi FC Product IDs supported in DS4000 Storage Subsystems: HUS103009FLF21 JFQ8 (9G/10Krpm/2Gbps) HUS103018FLF21 JFQ8 (18G/10Krpm/2Gbps) HUS103036FLF21 JFQ8 (36G/10Krpm/2Gbps) HUS103073FLF21 JFQ8 (73G/10Krpm/2Gbps) HUS103030FLF21 JFQ8 (300G/10Krpm/2Gbps) HUS103014FLF21 JFQ8 (146G/10Krpm/2Gbps) To identify these drives you must view the Storage Subsystem Profile in the Storage Manager Client. Any drive NOT AT FQ8 should be upgraded to the FQ8 firmware level before attempting controller or ESM firmware upgrades. 12.IMPORTANT: EXP710 ESM FIRMWARE 9661 REQUIRES A MIMINUM DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE LEVEL OF 06.12.40.00 OR HIGHER BEFORE UPGRADING EXP710 ESM TO THIS LEVEL. 1.2 Enhancements ----------------- The DS4000 Storage Manager version 9.60.xx.xx host software in conjunction with controller firmware version 6.60.xx.xx provides supports for - VDS/VSS Use new ability to recreate multiple snapshots. This is associated with enhancement Recreate Multiple snapshots(see below). The SMI-S providers will updated to use the new commands for recreating multiple snapshots. - Recreate multiple snapshots. SYMbol addition of a re-create snapshot command that will accept a list of snapshots as input. This command will be used by VSS and SMI-S providers to reduce the time needed to re-create several snapshots at one time. In addition, it also provides - Support for the new Daylight saving time as required by the enactment of the United State's Energy Policy Act of 2005. The Daylight Saving Time (DST) will begin at 2 a.m. on the second Sunday in March and end at 2 a.m. on the first Sunday of November instead of 2 a.m. on the first Sunday of April to 2 a.m. on the last Sunday of October. For the year of 2007, DST will start on March 11, 2007 and end on November 11, 2007. DS4000 storage subsystem users in countries implementing the new DST rules (which includes U.S., Canada, Bermuda) are recommended to upgrade to Storage Manager version 9.19.xx.12 or later before March 2007. Storage Manager version 9.19.xx.12 or later release includes revised DST transition dates to comply with provision of the Energy Policy Act of 2005 extension of Daylight Saving Time (DST) by four weeks, beginning in 2007. There are no data integrity or functional problems caused by an incorrect clock setting. From the DS4000 controller firmware standpoint, this change will have no impact. The software changes are in the Java Runtime software included with the Storage Manager host software. The DS4000 controller uses an internal time clock which is GMT time based. The Storage Manager client software will make the appropriate time changes for reporting the Major Event Log entries (MEL), subsystem information or subsystem configuration changes in the time zone that the management station is installed. If no updates are made to existing DS4000 Storage Manager host software. The primary impact is that Email alerts and Major Event Log (MEL) entries will be off by 1 hour for 3 weeks in the Spring and 1 week in the Fall because they will be translated improperly by the Java Runtime Engine that is currently in use. This is a cosmetic impact only; as noted above, all times within the DS4000 controller firmware are stored in GMT time. Such values will be incorrect for the three-week period but then will be correct later when viewed from DS4000 Storage Manager client software. Additional incorrect timestamps may be seen in diagnostic reports, various subsystem component information displayed in dialog boxes, and performance monitor. In addition to updating the DS4000 Storage Manager host software, additional operating systems patches may be needed for the host server/management station that the DS4000 Storage Manager host software is installed. This will ensure that no problems occur with the implementation of the new DST rule. Please refer to the support web site for your operating systems for more information. Various impact scenarios are described below: Host System DS4000 Impact Operating Storage System Manager No Update No Update The System and DS4000 Controller time stamps are in sync until March 11, to April 1, when the times are 1 hour earlier than the time in the areas where the change is effective. Updated No Update The system and DS4000 controller time stamps will be out of sync by 1:00 hour. For example, a MEL event at 3:00 p.m. on the system will be reported as 2:00 p.m. on the DS4000 MEL logs Not Updated Updated Same as above, except the DS4000 Storage Manager will report with the correct DST time. Updated Updated Best scenario. Everything reports the correct time Please refer to the New Features section of the IBM DS4000 Storage Manager version 9 Installation and Support Guide for Windows 2000/Server 2003, NetWare, ESX Server, and Linux for additional information about the IBM DS4000 Storage Manager version 9 enhancements. 1.3 Prerequisites ------------------ The DS4000 controller firmware version 06.60.34.xx and NVSRAM file that are packaged with this README file can ONLY be loaded in the following DS4000 storage subsystems: - DS4200 storage subsystems with or without DS4000 EXP420 storage expansion enclosures attached. - DS4300 storage subsystems with or without DS4000 EXP810 and/or DS4000 EXP700/710 and/or EXP100 storage expansion enclosures attached. - DS4500 storage subsystems with DS4000 EXP810 and/or DS4000 EXP700/710 and/or EXP100 storage expansion enclosures attached. - DS4700 storage subsystems with DS4000 EXP100 and/or DS4000 EXP810 and/or EXP710 storage expansion enclosures attached. - DS4800 storage subsystems with DS4000 EXP810 and/or DS4000 EXP710 and/or EXP100 storage expansion enclosures attached. Note: Controller firmware version 06.60.34.xx does not support EXP500 storage expansion enclosures. The following table shows the controller firmware versions required for attaching the various models of the DS4000 Storage Expansion Enclosures. ------------------------------------------------------------------- | Controller | EXP Storage Expansion Enclosures | | FW Version |------------------------------------------------------| | | EXP100 | EXP420 | EXP500 | EXP700 | EXP710 | EXP810 | |------------|---------|--------|--------|--------|--------|--------| |5.3x.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.40.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.41.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |5.42.xx.xx | Yes | No | No | No | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.00.xx.xx | No | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.10.xx.xx | No | No | Yes | Yes | No | No | |------------|---------|--------|--------|--------|--------|--------| |6.12.xx.xx | Yes | No | Yes | Yes | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.14.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.15.xx.xx | Yes | No | No | No | Yes | No | |------------|---------|--------|--------|--------|--------|--------| |6.16.2x.xx | No | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.8x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.16.9x.xx | No | Yes | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.19.xx.xx | Yes | No | No | No | Yes | Yes | |------------|---------|--------|--------|--------|--------|--------| |6.23.xx.xx | Yes | Yes | No | No | Yes | Yes | |-------------------------------------------------------------------| |6.60.xx.xx | Yes | Yes | No | Yes | Yes | Yes | ------------------------------------------------------------------- The IBM DS4000 Storage Manager host software version 10.60.x5.17 or higher is required to manage DS4000 storage subsystems with controller firmware version 6.60.34.xx installed. IMPORTANT: DO NOT DOWNLOAD this controller firmware on any other DS4000 storage subsystem configuration that are not listed above. In addition to lost of access to the data in the storage subsystem that resides in the non-supported storage expansion enclosures, the procedure to recover the DS4000 storage subsystem that was inadvertently loaded with this firmware file will require downtime to the DS4000 storage subsystem. Also see next section - Dependencies. 1.4 Dependencies ----------------- The information in this section is pertinent to the controller firmware version 6.60.xx.xx release only. For the dependency requirements of previously released controller firmware versions, please consult the Dependencies section in the readme file that was packaged with each of those controller firmware releases. ATTENTION: 1. Beginning in 2009, EXP700 expansion enclosures will be supported with firmware levels 06.60.08.xx, 6.60.17.xx, 6.60.22.xx, and 6.60.34.xx on all DS4300 and DS4500 machine types (all models except DS4300 SCU). Supported ESM Firmware levels for intermix support: EXP 700 ESM = 9330 EXP 100 ESM = 9566 EXP 710 ESM = 9681 EXP 810 ESM = 98C1 EXP 810 ESM = 98C5 with 6.60.22.xx (and higher) 2. 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 storage/drive expansion enclosure ESM, the DS4000 storage subsystem controller and the hard drive firmware. Certain versions of the controller firmware might require the storage expansion enclosures ESM be at certain version for the upgrade to be successful. In the same vein, a particular version of ESM firmware might require certain version of controller firmware to be installed first before it can be download to the ESM. 3. The only DS4000 storage subsystems that are supported by the controller firmware version 06.60.34.xx are the DS4200-all models, DS4300 (dual-controller Standard/Base and Turbo models only), the DS4500-all models, the DS4700-all models and the DS4800-all models Currently, there are not any controller firmware packages version 06.60.34.xx for other DS4000 storage subsystems. Do not download this controller firmware on any other DS4000 storage subsystems. 4. The minimum EXP710, EXP100 and the EXP810 ESM firmware versions must be at or greater then 9663, 9566 and 98A3, respectively. 5. The Fibre Channel drives in the DS4000 configuration must be loaded with the appropriate minimum drive firmware version as defined in the hard drive and ESM firmware package version 1.59 or greater found at the IBM support web site. 6. Customer with IBM branded Hitachi FC drives should verify that these drives are at drive firmware FQ8, or later, before doing a controller firmware or ESM firmware download. It has been observed by IBM Support that customer's with older versions of the Hitachi FC drive firmware have experienced failure of these Hitachi drives during controller firmware and ESM firmware downloads. Upgrading the drive firmware to FQ8 will prevent this problem. Hitachi FC Product IDs supported in DS4000 Storage Subsystems: HUS103009FLF21 JFQ8 (9G/10Krpm/2Gbps) HUS103018FLF21 JFQ8 (18G/10Krpm/2Gbps) HUS103036FLF21 JFQ8 (36G/10Krpm/2Gbps) HUS103073FLF21 JFQ8 (73G/10Krpm/2Gbps) HUS103030FLF21 JFQ8 (300G/10Krpm/2Gbps) HUS103014FLF21 JFQ8 (146G/10Krpm/2Gbps) To identify these drives you must view the Storage Subsystem Profile in the Storage Manager Client. Any drive NOT AT FQ8 should be upgraded to the FQ8 firmware level before attempting controller or ESM firmware upgrades. 7. IMPORTANT: EXP710 ESM FIRMWARE 9661 REQUIRES A MIMINUM DS4000 STORAGE SUBSYSTEM CONTROLLER FIRMWARE LEVEL OF 06.12.40.00 OR HIGHER BEFORE UPGRADING EXP710 ESM TO THIS LEVEL. 1.5 Level Recommendation for the update ----------------------------------------- Note: For controller firmware version 6.60.xx.xx code thread, the DS4300 dual-controller standard/base model share the same firmware and NVSRAM files an the DS4300 dual-controller Turbo model. 1. Storage Controller Firmware versions: a. DS4200: FW_DS4200_06603400 b. DS4300 dual-controller: FW_DS4300-dualControllers_06603400 c. DS4500: FW_DS4500_06603400 d. DS4700: FW_DS4700_06603400 e. DS4800: FW_DS4800_06603400 Note: The same firmware file can be used for upgrading the controller firmware through the SMClient GUI or through the controller serial port. Do not attempt to download the firmware through serial port without the presence of IBM Support personnel. A botched controller firmware download via the serial port can cause a controller to become nonfunctional. 2. Storage Controller NVSRAM versions: a. DS4200: N1814D420R960V06.dlp b. DS4300 dual-controller: N1722F60R960V0BF.dlp Use this level of NVSRAM for: * DS4300 installed without drive expansion enclosures. * DS4300 configured with only Fibre Channel drive expansion enclosures attached. * DS4300 with the FC/SATA intermix premium feature. Feature which enables intermix support of EXP700/EXP710. * DS4300 with EXP710/EXP810 drive expansion enclosures (either Fibre Channel or SATA drives installed in EXP810) and EXP100 SATA drive expansion enclosures. c. DS4300 dual-controller: N1722F60R960V0BS.dlp Use this level of NVSRAM for: * DS4300 installed with SATA ONLY disks installed in EXP100 or EXP810 expansion disk drive enclosures. d. DS4500: N1742F900R960V06.dlp e. DS4700: N1814D470R960V06.dlp f. DS4800: N1815D480R960V06.dlp ATTENTION: THERE IS NO SAFETY MECHANISM TO PREVENT THE UNINTENTIONAL LOADING OF THIS NVSRAM FILE. 1. DO NOT LOAD NVSRAM FILE (N1722F60R960V0AS.dlp) ONTO DS4300 WITH FIBRE CHANNEL DRIVES INSTALLED IN INTERNAL CHASSIS. THIS IMPROPER ACTION WILL RESULT IN: * LOST CONFIGURATION FOR NEWLY INSTALLED DRIVES OR FOR DRIVES THAT MAY HAVE BEEN PREVIOUSLY CONFIGURED. * DEGRADATION OF DEFINED RAID ARRAY OR LOSS OF ACCESS TO DATA. 2. DO NOT LOAD NVSRAM FILE (N1722F60R960V0AS.dlp) ONTO DS4300 WITHOUT ANY DRIVE EXPANSION ENCLOSURES ATTACHED THIS IMPROPER ACTION WILL RESULT IN: * DS4300 NOT COMPLETING BOOT PROCESS WHICH INITIATES THE ACTIVATION OF NEW NVSRAM SETTINGS * LOSS OF STORAGE MANAGEMENT ACCESS TO DS4300. 3. DO NOT USE THIS NVSRAM FILE (N1722F60R960V0AS.dlp) WITH DS4300 WHICH HAS FC/SATA INTERMIX PREMIUM FEATURE ENABLED. Note: The DS4000 storage subsystems shipped from the factory may have NVSRAM versions installed with a different first character prefix. Both manufacturing NVSRAM version and the "N" prefixed NVSRAM version are the same. You do not need to update your DS4000 storage subsystem with the "N" prefixed NVSRAM version as stated above. For example, the N1815D480R923V08 and M1815D480R923V08 (or C1815D480R960V03 or D1815D480R960V03 or ...) versions are the same. Both versions share the same "1815D480R960V03" string value. Refer to the following IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released code levels. http://www.ibm.com/systems/support/storage/disk ======================================================================= 2.0 Installation and Setup Instructions ----------------------------------------- Note: Before commencing with any firmware upgrade procedure, use the Storage Manager client to perform a Collect All Support Data capture. Save this support data capture on a system other than the one that is being upgraded. The sequence for updating your DS4000 Storage Subsystem firmware may be different depending on whether you are updating an existing configuration, installing a new configuration, or adding drive expansion enclosures. ATTENTION: If you have not already done so, please check the Dependencies section for ANY MINIMUM FIRMWARE REQUIREMENTS for the DS4000 storage server controllers, the drive expansion enclosure ESMs and the hard drives in the DS4000 configurations. The order in which you will need to upgrade firmware levels can differ based on prerequisites or limitations specified in these readme files. If no prerequisites, or limitations, are specified, the upgrade order refered in section 2.1 Installation For and Existing Configuration should be observed. If drive firmware upgrades are required, down time will need to be scheduled. The drive firmware upgrades require that there are no Host I/Os sent to the DS4000 controllers during the download. Note: For additional setup instructions, Refer to the Installation, User's and Maintenance guide of your DS4000 storage subsystem or storage expansion enclosures. 2.1 Installation For an Existing Configuration ------------------------------------------------- ATTENTION: If you have not already done so, please check the Dependencies section for ANY MINIMUM FIRMWARE REQUIREMENTS for the DS4000 storage server controllers, the drive expansion enclosure ESMs and the hard drives in the DS4000 configurations. The order in which you will need to upgrade firmware levels can differ based on prerequisites or limitations specified in these readme files. If no prerequisites, or limitations, are specified, the upgrade order refered in section should be observed. 1. Upgrade the storage manager client program to the latest storage manager 10.60.x5.17 version that is available from the DS4000 system storage support web site. Older versions of the storage manager client program will show that the new firmware file is not compatible with the to-be- upgraded DS4000 subsystem, even when the existing version of the controller firmware installed in the DS4000 subsystem is of 6.60.xx.xx code thread. http://www.ibm.com/systems/support/storage/disk 2. Make any hard disk drive and/or drive expansion enclosure ESM firmware updates as required BEFORE proceeding to upgrade the DS4000 controller with the firmware and NVSRAM files packaged with this README file. FAILURE to observe the minimum firmware requirement might cause your DS4000 storage subsystem to be OUT-OF-SERVICE. Check the IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released hard drive firmware if you have not already upgraded drive firmware to the latest supported version. (See 1.4 Dependencies) To download hard disk drive firmware, do the following: a. Schedule down time because the drive firmware upgrades require that there are no HOST I/Os to be sent to the DS4000 controllers. b. Open the Subsystem Management window. c. Click Advanced => Maintenance => Download => Drive Firmware. Follow the online instructions. Note: with controller firmware version 06.1x.xx.xx or later, multiple drives from up to four different drive types can be updated at the same time. 3. Update the firmware of the ESMs in the attached drive expansion enclosures to latest levels before the upgrading the controller firmware. (See 1.4 Dependencies) To download drive expansion ESM firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Environmental(ESM) Card Firmware. Follow the online instructions. Note: If the existing controller firmware in the DS4000 storage server is of version 05.30.xx.xx or higher, the drive expansion enclosure ESM firmware can be updated online with no downtime if both ESMs in each of the drive expansion enclosures are functional and one (and ONLY one) drive expansion enclosure is selected in the ESM firmware download window for ESM firmware updating at a time. Note: SAN Volume Controller (SVC) customer are now allow to download ESM firmware with concurrent I/O to the disk subsystem at controller firmware levels of 6.23.05.xx or higher, with the following restrictions. 1) The ESM Firmware upgrade must be done on one disk expansion enclosure at a time. 2) A 10 minute delay from when one enclosure is upgraded to the start of the upgrade of another enclosure is required. Confirm via the Storage Manager Application's "Recovery Guru" that the DS4000 status is in an optimal state before upgrading the next enclosure. If it is not, then do not continue ESM firmware upgrades until the problem is resolved. Note: Reference IBM System Storage™ Disk Storage Systems Technical Support web site for the current ESM firmware versions for the drive expansion enclosures. 4. Important: Install the Controller firmware update and Controller NVSRAM update at the same time using the option check box in the controller firmware download window. DO NOT proceed any further if you have any EXP500 storage/drive expansion enclosures attached to the DS4300 or the DS4500 storage subsystem that you are planning to upgrade the controller firmware. This version of controller firmware is not compatible with the EXP500 drive expansion enclosures. After the 06.60.34.xx controller firmware is activated, the DS4300 or DS4500 storage subsystem will not recognize the drives in EXP500 drive expansion enclosures, causing loss of data availability to the raid arrays and logical drives that are defined in those drives. Please refer to the 1.4 "Dependencies" section for supported levels of controller firmware with EXP700 Enclosures. To download controller firmware and NVSRAM, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller Firmware Follow the online instructions. NOTE: It is recommended to download NVRAM with the controller firmware. In the controller firmware download windows check the box "download NVSRAM" and follow the online instructions. Attention: If there are any modifications to the default NVSRAM settings, these modifications must be reapplied after loading the new NVSRAM file in this package. c. Reapply and modifications to the NVSRAM. Both controllers will be rebooted to activate the new NVSRAM settings To download controller NVSRAM separately, do the following: Attention: If there are any modifications to the default NVSRAM settings, these modifications must be reapplied after loading the new NVSRAM file in this package. a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller => Controller NVSRAM. Follow the online instructions. c. Reapply and modifications to the NVSRAM. Both controllers will be rebooted to activate the new NVSRAM settings 2.2 Installation For a New Configuration ------------------------------------------- 1. Upgrade the storage manager client program to the latest storage manager 10.60.x5.17 version that is available from the DS4000 system storage support web site. Older versions of the storage manager client program will show that the new firmware file is not compatible with the to-be- upgraded DS4000 subsystem, even when the existing version of the controller firmware installed in the DS4000 subsystem is of 6.60.xx.xx code thread. http://www.ibm.com/systems/support/storage/disk 2. You must install the Controller firmware update prior to downloading the Controller NVSRAM update. To download controller firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller Firmware. Follow the online instructions. To download controller NVSRAM, do the following: Attention: If there are any modifications to the default NVSRAM settings, these modifications must be reapplied after loading the new NVSRAM file in this package. a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Controller => Controller NVSRAM. Follow the online instructions. c. Reapply and modifications to the NVSRAM. Both controllers will be rebooted to activate the new NVSRAM settings 3. Check the IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released hard drive firmware if you have not already upgraded drive firmware to the latest supported version. (See 1.4 Dependencies) To download hard disk drive firmware, do the following: a. Schedule down time because the drive firmware upgrades require that there are no HOST I/Os to be sent to the DS4000 controllers. b. Open the Subsystem Management window. c. Click Advanced => Maintenance => Download => Drive Firmware. Follow the online instructions. Note: with controller firmware version 06.1x.xx.xx or later, multiple drives from up to four different drive types can be updated at the same time. 4. Update the firmware of the ESMs in the attached drive expansion enclosures to latest levels before the upgrading the controller firmware. (See 1.4 Dependencies) To download drive expansion ESM firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Environmental(ESM) Card Firmware. Follow the online instructions. Note: If the existing controller firmware in the DS4000 storage server is of version 05.30.xx.xx or higher, the drive expansion enclosure ESM firmware can be updated online with no downtime if both ESMs in each of the drive expansion enclosures are functional and one (and ONLY one) drive expansion enclosure is selected in the ESM firmware download window for ESM firmware updating at a time. Note: Reference IBM System Storage™ Disk Storage Systems Technical Support web site for the current ESM firmware versions for the drive expansion enclosures. 2.3 Installing additional Drive Expansion Enclosure --------------------------------------------------------- ATTENTION: You must complete instruction in section 2.1 or 2.2 before you start this section. This section is intended as a guide to installing and setting up disk expansion enclosures after upgrading controller firmware to 06.60.34.xx. The DS4300 and DS4500 subsystems at firmware levels prior to 06.19.xx.xx and DS4800 subsystems at firmware levels prior to 06.16.xx.xx, WILL NOT configure the EXP810 disk drive expansion enclosure. The DS4700 subsystem at firmware levels prior to 06.23.xx.xx and DS4800 firmware levels at 06.16.xx.xx WILL NOT configure the EXP100 disk drive expansion enclosure. 1. Instruction for adding you drive expansion enclosures is covered in the following Document. Installation and Migration Guide - IBM TotalStorage DS4000 hard drive and Storage Expansion Enclosure Please follow the instruction located in the chapter titled "Adding or migrating drive expansion enclosures". 2. Once you have successfully added your drive expansion enclosures you will need to update the firmware of the hard drives and the ESMs in the attached drive expansion enclosures. Check the IBM System Storage™ Disk Storage Systems Technical Support web site for the latest released hard drive and ESM firmware. (See 1.4 Dependencies) To download hard disk drive firmware, do the following: a. Schedule down time because the drive firmware upgrades require that there are no HOST I/Os to be sent to the DS4000 controllers. b. Open the Subsystem Management window. c. Click Advanced => Maintenance => Download => Drive Firmware. Follow the online instructions. Note: with controller firmware version 06.1x.xx.xx or later, multiple drives from up to four different drive types can be updated at the same time. To download drive expansion ESM firmware, do the following: a. Open the Subsystem Management window. b. Click Advanced => Maintenance => Download => Environmental(ESM) Card Firmware. Follow the online instructions. Note: If the existing controller firmware in the DS4000 storage server is of version 05.30.xx.xx or higher, the drive expansion enclosure ESM firmware can be updated online with no downtime if both ESMs in each of the drive expansion enclosures are functional and one (and ONLY one) drive expansion enclosure is selected in the ESM firmware download window for ESM firmware updating at a time. Note: Reference IBM System Storage™ Disk Storage Systems Technical Support web site for the latest hard disk drive and ESM firmware versions. ======================================================================= 3.0 Configuration Information ----------------------------- 3.1 Configuration Settings -------------------------- 1. By default, the IBM DS4000 Storage Manager 10.xx does not automatically map logical drives if storage partitioning feature is enabled. This means that the logical drives are not automatically presented to host systems. For a new installation, after creating new arrays and logical drives; a. If your host type is not Windows NT, create a partition with your host type and map the logical drives to this partition. b. If your host type is Windows NT, you can map your logical drives to the "Default Host Group" or create a partition with a NT host type. When upgrading from previous versions of IBM DS4000 Storage Manager to version 10.xx.xx.xx a. If upgrading with no partitions created and you have an operating system other than Windows NT, you will need to create a partition with your host type and map the logical drives from the "Default Host Group" to this partition. b. If upgrading with Storage Partitions and an operating system other than Windows NT is accessing the default host group, you will need to change the default host type. After upgrading the NVSRAM, the default host type is reset to Windows 2000/Server 2003 non-clustered for DS4000 storage server with controller firmware version 06.14.xx.xx or later. For DS4000 storage server with controller firmware version 06.12.xx.xx or earlier, it is reset to Windows non- clustered (SP5 or higher), instead. Refer to the IBM DS4000 Storage Manager online help to learn more about creating storage partitions and changing host types. 2. When you are configuring IBM machine type 1742 or 1722 storage subsystems as boot devices, contact IBM support for supported configurations and instructions for configuring LUNs in the IBM storage subsystems as boot devices. 3. Running script files for specific configurations. Apply the appropriate scripts to your subsystem based on the instructions you have read in the publications or any instructions in the operating system readme file. A description of each script is shown below. - SameWWN.scr: Setup RAID controllers to have the same World Wide Names. The World Wide Names (node) will be the same for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - DifferentWWN.scr: Setup RAID controllers to have different World Wide Names. The World Wide Names (node) will be different for each controller pair. The NVSRAM default sets the RAID controllers to have the same World Wide Names. - EnableDriveMigration.scr: The Enable drive migration script scans the drives for configurations when they are added to a storage system and will also attempt to use configurations found on the newly added drives. The NVSRAM default will enable drive migration. - DisableDriveMigration.scr: The disable drive migration script allows the addition of disk drives while the system is running. In addition, it identifies the drives as unused capacity regardless of past drive configuration. The NVSRAM default will enable drive migration. - EnableAVT_W2K_S2003_noncluster.scr: The script will enable automatic logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003 non- cluster heterogeneous host region. The default setting is to disable AVT for this heterogeneous host region. This setting is one of the requirements for setting up the remote boot or SAN-boot. Do not use this script unless it is specifically mentioned in the applicable instructions. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT enabled) - DisableAVT_W2K_S2003_noncluster.scr: The script will disable the automatic logical drive transfer (AVT) for the Windows 2000/Server 2003 non-cluster heterogenous host region. This script will reset the Windows 2000/Server 2003 non-cluster AVT setting to the default. (This script can be used for other host type if modifications are made in the script, replacing the Windows 2000/Server 2003 non-cluster host type with the appropriate host type that needs to have AVT/ADT disabled) - EnableAVT_Linux.scr: The script will enable automatic logical drive transfer (AVT) for the Linux heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Linux.scr: The script will disable the automatic logical drive transfer (AVT) for the Linux heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - EnableAVT_Netware.script: The script will enable automatic logical drive transfer (AVT) for the NetWare Failover heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - DisableAVT_Netware.script: The script will disable the automatic logical drive transfer (AVT) for the NetWare Failover heterogeneous host region. Do not use this script unless it is specifically mentioned in the applicable instructions. - disable_ignoreAVT8192_HPUX.script: This script will disable the DS4000 storage subsystem ignoring of AVT requests for the HP-UX server specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request for the LBA 8192 reads was implemented to prevent a possible occurrence of an AVT storm caused by the HP-UX server probing in the wrong order of available paths to the volume(s) when it detect server to LUN path failure. Use this script only when you do not have defined LVM mirrored volumes using the mapped logical drives from the DS4000 storage subsystems. Please contact IBM support for additional information, if required. - enable_ignoreAVT8192_HPUX.script: This script will enable the DS4000 storage subsystem ignoring of AVT requests for the HP-UX server specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request for the LBA 8192 reads was implemented to prevent a possible occurrence of an AVT storm caused by the HP-UX server probing in the wrong order of available paths to the volume(s) when it detect server to LUN path failure. Use this script only when you do have defined LVM mirrored volumes using the mapped logical drives from the DS4000 storage subsystems. Please contact IBM support for additional information, if required. 3.2 Unsupported configurations ------------------------------ The configurations that are currently not being supported with controller firmware version 06.60.34.xx in conjunction with DS4000 Storage Manager version 10.60 are listed below: 1. Any DS4400, DS4300- with Single Controller option, DS4100, FAStT500 and FAStT200 storage subsystems configurations are not supported with this version of controller firmware. 2. DS4500 storage subsystems configurations with EXP500 and/or EXP700 storage expansion enclosures at 06.23.05.xx or 06.60.02.00. Refer to the 1.4 Dependencies section for controller firmware levels that will support EXP700. 3. The DS4300 storage subsystems configurations with EXP700 storage expansion enclosure at 06.23.05.xx or 06.60.02.xx. Refer to the 1.4 Dependencies section for controller firmware levels that will support EXP700. 4. 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-S08. In this configuration, the hub is connected between the switch and the IBM Fibre Channel RAID Controllers. 5. The IBM Fibre Channel Hub, machine type 3523, connected to IBM machine type 1722, 1724, 1742, 1815, 1814, 3542 and 3552. 6. A configuration in which a server with only one FC host bus adapter connects directly to any DS4000 storage subsystem with dual controllers is not supported. The supported configuration is the one in which the server with only one FC host bus adapter connects to both controller ports of any DS4000 storage subsystem with dual controllers via Fibre Channel (FC) switch (SAN-attached configuration.) 7. RHEL5 on System p (Linux on Power) is not supported with this release. 3.3 Helpful Hints ------------------ 1. Depending on the storage subsystem that you have purchased, you may have to purchase the DS4000 storage partitioning premium feature option or an option to upgrade the number of supported partitions in a storage subsystem. Please see IBM Marketing representatives or IBM resellers for more information. - IBM DS4100 storage subsystem (machine type 1724): The standard and single controller configuration does not have the DS4000 storage partitioning premium enabled. Four partition, eight partition, sixteen and an upgrade from four to eight partition storage partitioning premium feature options can be purchased. - IBM DS4200 storage subsystem (machine type 1814): Depending on the ordering channels, the DS4200 storage subsystem is either shipped with 2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage partitions. If the DS4700 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 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. The IBM DS4300 with Turbo option comes with 8 partition storage partitioning premium option installed. An upgrade to 64 partitions can be purchased for the IBM DS4300 with Turbo option. - IBM DS4400 storage subsystems (machine type 1742 - models 1RU and 1RX): The standard configuration has 64 partitions 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 or 64 storage partitions. Similarly, the DS4700-model 72 storage subsystem is either shipped with 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the DS4700 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 DS4800 storage subsystem (machine type 1815): Depending on the ordering channels, the DS4800 storage subsystem is either shipped with an 8 storage partitions or with a user selected 8, 16 or 64 storage partitions. If the subsystem is ordered with less than 64 partitions, an upgrade from 8 to 16, 8 to 64 or 16 to 64 partition storage partitioning premium feature option can be purchased. 2. When making serial connections to the DS4000 Storage controller, the baud rate is recommended to be set at either 38200 or 57600. Note: Do not make any connections to the DS4000 storage subsystem serial ports unless it is instructed by IBM Support. Incorrect use of the serial port might result in lost of configuration, and possibly, data. 3. Fabric topology zoning requirement. To avoid possible problem at the host level, it is best practice that all Fibre Channel (FC) Switches must be zoned such that a single FC host bus adapter can only access one controller per storage array. In addition, this zoning requirement also ensures the maximum number of host connections can be seen and log into the controller FC host port. This is because if a FC HBA port is seen by both controller A and B host ports, it will be counted as two host connections to the storage subsystem - one for controller A port and one for controller B port. Note: The DS4000 storage subsystems DS4500, DS4400 and FAStT500 (IBM machine type 1742 and 3552) have two ports per controller - one per minihub slot. The DS4000 storage subsystems DS4300 (IBM machine type 1722) and DS4100 (IBM machine type 1724) have two ports per controller. The DS4000 storage subsystem FAStT200 (IBM machine type 3542) has only one port per controller. The DS4700 (IBM machine type 1814) has up to 4 ports per controller. The DS4800 (IBM machine type 1815) has 4 ports per controller. The DS4200 (IBM machine type 1814) has 2 ports per controller. 4. 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. 5. 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. 6. IBM recommends at least one hot spare per EXP100 drive expansion enclosure. A total of 15 hot-spares can be defined per DS4000 storage subsystem configuration. 7. Starting with the DS4000 Storage Manager (SM) host software version 9.12 or later, the Storage Manager client script window looks for the files with the file type of ".script" as the possible script command files. In the previous versions of the DS4000 Storage Manager host software, the script window looks for the file type ".scr" instead. (i.e. enableAVT.script for 9.12 or later vs. enableAVT.scr for pre-9.12) 8. Inter-operability with tape devices is supported on separate HBA and switch zones. ======================================================================= 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/servers/storage/disk 5.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 subsystem controller firmware, the DS4000 drive expansion enclosure ESM firmware and the drive firmware at the time of the initial installation and when product updates become available. To be notified of important product updates, you must first register at the IBM Support and Download Web site: http://www.ibm.com/systems/support/storage/disk Perform the following steps to register at the IBM Support and Download Web site: 1. Click on My notifications in the Stay Informed 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 notifications. ======================================================================= 6.0 Trademarks and Notices ---------------------------- 6.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM DS4000 FAStT 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. Other company, product, and 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.