IBM System Storage™ DS4000 storage subsystem controller firmware version 
06.12.56.00 for the DS4100 with dual controller (standard/base) and 
DS4100 Single Controller option, the DS4300 with dual controller 
(standard/base) or Turbo options, the DS4400 and the DS4500 storage 
servers only. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER 
DS4000 STORAGE SUBSYSTEM MODELS. 

ATTENTION: 
1. FOR DS4100 and DS4300 CONTROLLERS: WHEN DOWNLOADING CONTROLLER 
   FIRMWARE 06.12.23.00 0R HIGHER USING STORAGE MANAGER CLIENT YOU MUST 
   SELECT "Download NVSRAM file with firmware" OPTION. 
   FAILING TO PERFORM THIS ACTION MAY RESULT IN BOTH CONTROLLERS  
   REPORTING 'not ready' STATUS.

2. PRIOR TO DOWNLOADING CONTROLLER FIRMWARE 06.12.40.00 TO THE DS4000
   CONTROLLER, THERE IS A PREREQUISTE TO UPGRADE THE DS4000 STORAGE
   MANAGER CLIENT TO v9.19 or higher.
   STORAGE MANAGER v9.19 or higher is required for Drive Predictive 
   Failure Analysis PFA) feature available with 06.12.40.00 release.

3. New NVSRAM available with controller firmware 06.12.40.00 or higher 
   must be used for Drive Predictive Failure Analysis (PFA) feature.
        
4. IBM Network attached storage (NAS) N5000 and N7000 Gateways must
   use NVSRAM levels released with controller firmware 06.12.40.00 
   or higher for proper handling of SCSI persistent reservations. 
   NOTE: Only DS4300 and DS4500 controller types are supported with 
         IBM N5000 and N7000 Gateways.

5. Integrated Backup for Databases (IBD) for Exchange users must 
   upgrade to controller firmware 06.12.23.00 or higher.
   A critical fix is required for proper recovery when a fibre channel
   path is lost to the controller while performing Flashcopy. 


NOTE TO SERVICE – Reference RETAIN # N/A

(C) Copyright International Business Machines Corporation 1999, 2005. All 
rights reserved. US Government Users Restricted Rights - Use, duplication, 
or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Note: Before using this information and the product it supports, read the 
general information in "Notices and trademarks” in this document.


Refer to the IBM System Storage™ Support Web Site or CD for the IBM DS4000 
Storage Manager version 9 (Intel or Unix Operating Systems) Installation 
and Support Guides for firmware and NVSRAM download instructions.

For other related publications (refer to Related Publications in the 
installation and support guide) and the latest information and updated 
readme file.

Last Update:   04/22/2007

Products Supported: 

    -----------------------------------------------------------------
   | New Model  | Old Model | Machine Type |     Model               |
   |------------|-----------|--------------|-------------------------|
   |  DS4500    | FAStT 900 |     1742     | 90X, 90U                |
   |------------|-----------|--------------|-------------------------|
   |  DS4400    | FAStT 700 |     1742     | 1RX, 1RU                |
   |------------|-----------|--------------|-------------------------|
   |  DS4300    | FAStT 600 |     1722     | 60X,60U, 60J, 60K,      |
   |            |           |              | 60L                     |
   | dual       |           |              | (base or turbo option)  |
   | controller |           |              |                         |
     / Standard |           |              |                         |
   | or Turbo   |           |              |                         |
   |------------|-----------|--------------|-------------------------|
   |  DS4100    | FAStT 100 |     1724     | 100, 1SC                |
   | Standard   |           |              | (Base Option)           |
   | / dual     |           |              |                         |
   | controller |           |              |                         |
   | or Single  |           |              | 1Sx                     |
   | Controller |           |              | (SCU  Option)           |
    ------------------------------------------------------------------

Notes: 
  1. The DS4000 storage subsystem controller firmware version 06.12.xx.xx
     with its associated NVSRAM file ARE NOT AVAILABLE for the following 
     DS4000 storage subsystems - FAStT200 (M/T 3542-all models), FAStT500 
     (M/T 3552-all models) and DS4300 with Single Controller option (M/T 1722 
     models 6LU, 6LX). Please contact your IBM service representative or IBM 
     resellers for availability of additional DS4000 storage subsystem models 
     support with controller firmware version 6.12.xx.xx in the future. 
  2. For the DS4100 storage subsystems with Single Controller option, the 
     controller firmware version 6.12.16.xx or higher is now supported. 
     Please upgrade the your controller firmware from version 05.42.xx.xx to
     controller firmware version 06.12.16.xx or higher. 
  3. For the DS4300 storage subsystems with Single Controller option, the 
     controller firmware version 05.34.xx.xx and its associated NVSRAM file 
     must be used. Do not attempt to download the controller firmware 
     version 06.1x.xx.xx into these DS4300 storage subsystem with single
     controller option models.                           

=======================================================================
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.12.56.00 release includes the DS4000 storage subsystem 
   controller firmware and NVSRAM files for upgrading the following IBM 
   machine types - 1724 (all models), 1722 with Standard (base) or Turbo 
   options (models 60X and 60U) and 1742 (all models). The IBM DS4000 
   storage subsystem controller firmware version 06.12.56.00 new features 
   and changes are described in the corresponding Change History (*.chg) 
   document. Please refer to this document for more information on 
   firmware modifications.
   
   The IBM System Storage DS4000 Storage Manager version 9 Installation 
   and Support Guide for Windows 2000/Server 2003, Netware, ESX Server, 
   and Linux or the IBM System Storage DS4000 Storage Manager version 9 
   Installation and Support Guide for AIX, HP-UX, Solaris, and Linux on 
   Power are available on IBM's Support Web Site as a downloadable 
   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 options purchased separately. The 
   Copy Services premium features require a minimum level of DS4000 
   midrange disk system controller firmware installed.

    ------------------------------------------------------------------
   | Premium Feature          | Required controller firmware version  | 
   |--------------------------|---------------------------------------|
   | FlashCopy                | 05.00.04.xx or higher                 |
   |--------------------------|---------------------------------------|
   | VolumeCopy               | 05.40.xx.xx or higher                 |
   |--------------------------|---------------------------------------|
   | Enhanced Remote Mirror   | 06.10.0x.xx or higher                 |
   |------------------------------------------------------------------|
   | FC/SATA intermix         | 06.10.0x.xx or higher                 |
    ------------------------------------------------------------------
 
   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/dual controller 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. 
   The Turbo option of the IBM DS4300 is shipped with the IBM DS4000 
   Storage partitioning premium feature enabled (8 partitions).

   The DS4000 Storage Controller firmware 06.12.56.00 for this release 
   is available for the IBM machine types 1724-All models (DS4100 with 
   standard/base and single controller option), 1722-60X/60U (DS4300 with 
   Standard/base or Turbo option), 1742-1RX/1RU and 1742-90X/90U (DS4400 and 
   DS4500) only. The DS4000 Storage Controller firmware 06.12.xx.xx for this 
   release is not available for IBM machine types 3542, 3552, or 1722-6LX/6LU 
   (DS4300 with Single controller option). However, the IBM DS4000 Storage 
   Manager 9.16 host software for this release will manage all DS4000 
   midrange disk subsystem with the controller firmware 04.01.xx.xx or newer 
   (05.xx.xx.xx or newer in Microsoft Windows environments). But, any new 
   features and updates that are introduced in this DS4000 Storage Manager 
   version 9.16 or higher will not be available for any DS4000 midrange disk 
   subsystem controllers without the controller firmware version 06.16.xx.xx 
   installed.

   Refer to the IBM Support Web Site for the latest Firmware and NVSRAM 
   files and DS4000 Storage Manager host software for the IBM DS4000 
   midrange disk subsystems.
   
   http://www.ibm.com/servers/storage/support/disk/

=======================================================================
1.1  Limitations
---------------------
IMPORTANT:
The listed limitations are cumulative. However, they are listed by the 
DS4000 midrange disk 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. 

Limitations with version 06.12.56.00, 06.12.40.00, 06.12.27.xx 
 - NONE

Limitations with version 06.12.16.xx 

1. The following error message may be encountered under certain conditions
   when attempting to create a 2 TB LUN using the Create Logical drive 
   wizard in the Subsystem Management window:

    "Error 4 - The operation cannot complete because of an incorrect 
    parameter in the command sent to the controller."

   To avoid this error message, you must take certain steps while using the 
   Create Logical Drive wizard to create a 2 TB LUN.  Within the Specify 
   Capacity/Name window within the create logical drive wizard, you must not 
   manually specify the numeric value '2' in the New logical drive capacity 
   field in tandem with the "TB"  Units designator.  If you do this, the 
   Error 4 message will be issued and you will be unable to create the 2 TB 
   LUN. Click on the up or down arrows next to the input field to select the 
   desire capacity instead. When using the arrows, the program will display 
   the correct maximum logical drive capacity value that can be specified for 
   a given capacity unit (TB, GB, or MB). 

Limitations with version 06.12.03.xx.

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. 
   (CMVC 267873)

2. In the configuration that have both SATA-technology drives (EXP100) 
   and Fibre-Channel technology drives (EXP700/EXP710) behind the 
   same DS4000 storage subsystem, do not download drives firmware to both 
   SATA-technology drives and Fibre-Channel(FC) technology drives at the 
   same time. Download the drive firmware to drives of a single drive 
   technology (either SATA or FC) at a time.
    
3. Currently, IBM does not support Gold key Premium Feature as a 
   chargeable upgrade. The Gold key Premium Feature is enable or 
   disable depending on the DS4000 storage subsystem models.

4. The Asynchronous Remote Mirroring utility, asyncRVMUtil, is not
   supported. This utility is used to automatically synchronize the 
   logical drives in the Remote Mirroring pairs. Please contact IBM 
   representatives or resellers for the support of this utility in the 
   future.


Limitations with version 06.10.11.xx release
     
1. In MSCS configurations, the MSCS service must be stopped and set to 
   manual start after server rebooting, the clusdisk driver must have to 
   be set to offline and, then, the server must be rebooted before 
   uninstalling the RDAC driver in the server. If the clusdisk driver is 
   not set to offline and the MSCS service is not set to manual start, 
   the MS cluster service will not start after the new RDAC driver is 
   installed because it can not bring the Quorum disk resource online. 
   The problem is caused by the changing of the disk signatures. The 
   work around is stated in the first sentence of this paragraph.
    
   To recover from this problem, you must:
     
   1. Look up the old disk signatures of the disk that are defined as
      cluster disk resources. They could be found either in the registry 
      under the 
      HKLM/System/CurrentControlSet/Services/Clusdisk/Parameters/Signatures
      registry key or in the cluster.log file.
   2. Look up the new disk signatures of the disks that are defined as 
      cluster disk resources using the dumpcfg utility that is packaged
      in the Microsoft Windows resource kit. 
   3. Compare the new and old disk signatures. If new disk signature did
      not match the old signature, you have to change the new disk 
      signature to the old disk signature values by using the dumpcfg 
      command. The syntax of the command is 
       
      dumpcfg.exe -s <old-signature> <Disk#>     

      For example,  dumpcfg.exe -s 12345678 0 

2. Before updating the RDAC driver in a server that is setting up as 
   SAN boot, one of the two Fibre Channel (FC) cables that are connected 
   to the server must be disconnected. The server will bluescreened 
   during the reboot after the un-installation of the RDAC driver if 
   one of the FC cables was not removed. (258127 (82146))

3. Do not update the DS4000 storage subsystem controller firmware 
   to version 06.1x.xx.xx from versions 05.4x.xx.xx or earlier if 
   the EXP700 ESM firmware of the attached EXP700 was not at 9326 
   or 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 work around is to update the EXP700 ESM firmware 
   to the 9326 or higher version first before upgrading the controller 
   firmware to version 06.1x.xx.xx. (260160 - (82841))
    
4. When connecting the EXP100 drive expansion enclosures, one must set 
   the single digit (X1) of the enclosure ID to unique values. This 
   is to prevent the possibility that one of the drives in the EXP100 
   enclosures be assigned the same ALPA as the DS4000 controller  
   under certain DS4000 storage subsystem reboot scenarios. 
   (261188)


Limitations with version 06.10.06.xx release

1. The DS4000 Copy Service RVM is not supported at this time for the
   DS4100 and the DS4300 storage subsystem with Standard or Single Controller 
   options. (Note: With the release of the controller firmware version 
   06.12.16.00 or higher, the DS4100 with standard option is now supported 
   Copy Service Remote Mirroring and VolumeCopy premium features.)
   
2. In the Storage Manager version 9 client Subsystem Management window, 
   the preferred owner of a defined logical drive can not be changed if 
   the  logical drive is not managed by the preferred owner/controller. 
   The Storage Manager client will grey-out (not allowing one to select) 
   the controller that is currently managing the logical drive in the 
   selection of the new preferred owner/controller. One is allowed to 
   only select the controller that is not managing the logical to be the 
   new preferred owner. There is no work-around.
    
3. Concurrent firmware download (downloading firmware/NVSRAM to the 
   DS4000 storage subsystem controllers with I/Os to the host servers) 
   is not supported when upgrading the controller firmware from a 
   05.xx.xx.xx version to a 06.1x.xx.xx version. ALL I/Os must be 
   stopped during the version 06.1x.xx.xx controller firmware 
   upgrade from a 05.xx.xx.xx version. 
    
4. Do not pull or insert drives during the drive firmware download. 
   In addition, ALL IOs must also be stopped during the drive firmware 
   download. Otherwise, drives may be shown as missing, unavailable or 
   failed. 
    
5. Controller diagnostics will not run in a DS4000 storage subsystem 
   with single controller.
    
6. When instructed to remove and reinsert or to replace a hard drive, 
   wait at least 70 seconds before inserting either the removed 
   existing drive or the new drive into the drive slot. Then, wait 
   up to 3 minutes for the drive to be spined up, recognized by the 
   DS4000 storage subsystem and displayed in the Subsystem Management 
   window before repeating the process for another hard drive. 
   There is no work-around available.
   
   Similarly, wait at least 70 seconds before reinserting either the 
   removed existing ESM module or the new ESM module into the empty ESM 
   slot in the EXP drive expansion enclosure. Then, wait up to 3 minutes 
   for the ESM CRU to be recognized by the DS4000 storage subsystem and 
   displayed in the Subsystem Management window before repeating the 
   process for another ESM. There is no work-around available.

7. Staged firmware and NVSRAM download function is not available on the
   DS4400 (machine type 1742) models with firmware 06.1x.00.00 in 
   conjunction with IBM Storage Manager 09.1x.xx.xx.
     
Limitations with Storage Manager version 8.4x.xx.xx (and earlier) and
DS4000 controller firmware version 05.4x.xx.xx (and earlier) releases

1. Auto LUN/Array Transfer is not enable for IBM AIX and SUN Solaris 
   operating systems.
   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 selecting the redistributing arrays 
   menu option in the storage subsystem window of the IBM DS4000 
   Storage manager client program.

2. You must use the Add/Remove program function in the Control Panel 
   window to uninstall or to disable the IBM DS4000 Storage Manager RDAC 
   device. To re-install the IBM DS4000 Storage Manager RDAC device, 
   follow the instructions in the IBM DS4000 Storage Manager version 9 
   Installation and Support Guide for Windows 2000/Server 2003, 
   Netware, ESX Server, and Linux.  

3. You must always uninstall IBM DS4000 Storage Manager RDAC before 
   you uninstall the Host Bus Adapter driver. Failure to do so may 
   result in system hang or blue-screen condition.
                       
4. When creating a Remote Mirror of a base logical drive, in the 
   case where a FlashCopy of the base logical drive has already
   been created, the following restriction applies. If the Remote 
   Mirror relationship is created while the base logical drive is
   receiving I/O, the FlashCopy logical drive will be failed. The 
   work around is to quiesce I/O to the base logical drive while you 
   are creating the remote mirror relationship. Alternatively, if the
   Remote Mirror relationship is created before creating the FlashCopy
   logical drive, the FlashCopy logical drive will not be failed. 

5. When alternately switching back and forth the roles of the logical
   drives in a remote mirrored relationship, Windows NT4, Windows 2000
   and Server 2003 may cache the file(s) on the logical drive(disk) in
   memory  and use these cached data instead of going out to the disk
   to get the data. This windows OS behavior may make the data look like
   it was not synchronized between logical drives in a remote mirrored
   relationship. The fix to the problem is to dismount the primary
   logical drive in the server before demoting it to secondary role. 
   In Microsoft Windows environment, this is best done by shutting down 
   the server that the primary logical drive is mapped to. Then, 
   promote the secondary logical drive to the primary role and hot_add
   it to the appropriate server.
    
   If the logical drive is of "Dynamic Disk" type, there is a possible
   solution without requiring server to be shut down. First, in the 
   server that has the primary logical drive, run the SMrepassist 
   program in the DS4000 Storage Manager 8.xx/9.xx util directory 
   with the -f option to flush the cached data to disk. Then, 
   promote the secondary logical drive and hot_add it to the 
   appropriate server.
   Before promoting the logical drive to primary role in the original
   server, force a failure to the disk, for example, by running a chkdsk
   on the disk. Then, promote the logical drive to primary role
   in the original server and hot_add it. One may have to reactivate
   the disk after it is hot_added to the server.
   
   If the server environment prevents the server from being
   rebooted and the logical drive is of "basic disk" type, you may
   use the following steps 

   1. In the server that has the primary logical drive, run the 
      SMrepassist program in the DS4000 Storage Manager 8.3x
      util directory with the -f option to flush the cached data
      to disk.
   2. Using the DS4000 Storage Manager to remove the LUN mapping 
      of the logical drive that had the primary role from its
      server (host computer). 
   3. Promote the secondary role LUN to the primary role and 
      hot_add it in the appropriate server assuming that the LUN  
      mapping is already defined for this server in the DS4000 
      storage subsystem.
   4. Before promoting the logical drive to primary role in the 
      original server, run Hot_add program or initiate a Scan for
      Hardware Changes task in the original server. This is to
      remove the logical drive from the available disks. In W2K,
      you may see Unsafe Removal of Devices messages.
   5. Using the DS4000 Storage Manager to add the LUN mapping of 
      the logical drive that will be promoted to primary role to 
      the original server(host computer). 
   6. Promote the Logical Drive to Primary role and hot_add it in
      the original server. If you are unable to hot_add the logical
      drive or the data still appears to be mismatched, you must 
      reboot the server.  

6. When the DS4000 Storage subsystem controller firmware is upgraded 
   from any version 05.00.xx.xx or earlier to version 05.2x.xx.xx or 
   later, all of the Windows 2000 servers that had LUNs mapped in this
   storage subsystem must be rebooted after the new DS4000 Storage 
   subsystem controller firmware and NVSRAM are successfully applied. 
   The reason is that when the new DS4000 Storage subsystem controller 
   firmware is installed, the controller returns the first four bytes
   of the firmware revision in the Product Revision field of the SCSI
   LUN inquiry data. Windows 2000 uses the Product Revision data as 
   part of the LUN identification. So, as the Product Revision data 
   changes due to the new firmware revision level, Windows 2000 
   thinks that the LUNs with the old Product Revision data were 
   removed from the server. When the 'scan for hardware changes' task
   is executed by running the DS4000 Storage manager hot_add utility
   or by selecting the Scan For Hardware Changes menu option of the 
   Devices folder in the Computer Management window, Windows 2000
   displays Unsafe Removal of Devices dialogs for these LUNs. The
   devices in these dialogs are RDAC Virtual Disks and xxxx SCSI 
   devices where xxxx are either 1742, 3552 or 3542 depending on the
   model type of  DS4000 storage subsystem(s) that the Windows 2000 
   server had LUNs mapped from. The Windows 2000 server will lose 
   connectivity to the LUNs in the DS4000 Storage that has firmware
   updated. The server must be scanned again for hardware changes. If
   the logical drives are not added back to the server, one must 
   reboot the server to reconnect to the logical drives. 
   This problem will not occur when upgrading the DS4000 Storage 
   subsystem controller firmware from version 05.20.xx.xx to version
   05.3x.xx.xx or later because the product revision data field was 
   fixed at 0520.

7. When the server HBA ports are directly connected to the DS4000 
   storage subsystem controllers, do not download firmware and NVSRAM 
   files to the controllers with I/Os being generated to the LUNs in 
   the DS4000 storage subsystem. There is no I/Os restriction in SAN
   Fabric environment i.e. when the HBA port are connected to the 
   DS4000 storage subsystem controller ports via Fibre Channel switches.
   
8. The supplied SMrepassist utility did not utilize Microsoft Volume
   Shadow Services APIs to quiesce the LUNs. Appropriate steps are 
   still need to shut down/quiesce the applications like MS Exchange
   and SQL Server before the FlashCopy logical drive can be made.

9. Uninstalling RDAC may cause Windows Dynamic disks to fail. After the
   new RDAC is installed and the server is rebooted, these disks must be 
   reactivated and Chkdsk must be run. The work-around is to stop the
   applications and remove the drive letters or the mount points to 
   these disks before uninstalling and reinstalling RDAC.
   
10. The current RDAC driver will coexist with Storport model driver as
    long as it is not the driver for the adapter that talks to the LUNs
    in the DS4000 Storage subsystems. Note: the current release drivers
    for all of the Fibre Channel host bus adapters that DS4000 Storage
    Servers support are based on the SCSIport model.
        
11. This following behavior applies for the direct Fibre Channel 
    connection setup between the DS4300 storage subsystem host ports and
    the server HBA ports only. If all DS4300 host ports are occupied,
    the DS4300 event log may show "host-side data rate negotiation
    failed" error when the server is booted up, this is normal error 
    that were generated during the host rate negotiation routine inside 
    the DS4300 storage subsystem.

12. In a direct Fibre Channel connection between the DS4000 Storage 
    subsystem and the HBAs in the host server, the system bluescreen
    may occur if the DS4000 storage subsystem is powered off. The 
    work around is to power down the server first before powering down 
    the DS4000 storage subsystem.   
       
13. Only logical drives that are configured as "Basic Disks" in the 
    Windows Disk Management folder can have FlashCopy made. The 
    FlashCopy of a logical drive configured as "Dynamic Disk" type
    will always be failed by the DS4000 storage subsystem when it is 
    added to the host server.  

14. There is not an IA-64 version of the DS4000 Management Suite Java 
    (FAStT_MSJ). Use the 32-bit version of the FAStT Management Suite
    Java for the Windows Server 2003 64-bit edition. However, one
    should uninstall it once the diagnostic is completed. It could 
    cause the server to bluescreen in heavy I/O loads.
    
15. Veritas DMP 4.1 is not supported at this time in Windows operating 
    environment. Veritas Volume Manager (DMP) 4.2 is supported with 
    Windows Server 2003 and Windows 2000. 

16. When managing the DS4000 storage subsystems with firmware version 
    05.3x.xx.xx, the Help window of the Subsystem Management window may
    not be displayed correctly the topics that are listed as result of 
    executing a full text search. 

17. When migrating array(s) from a dual controller DS4000 storage 
    subsystem to a single controller DS4000 storage subsystem, you 
    must first set the preferred owner of the to-be-migrated array(s) 
    to be controller A before inserting it into the drive slots of a 
    single controller DS4000 storage subsystem. Otherwise, the array(s) 
    will not be added to the single controller DS4000 storage subsystem 
    correctly which might cause problems.

18. When managing a single controller DS4300 storage subsystem model, 
    do not use the menu option - Configuration->Automatic... - in the 
    Subsystem Management window to create LUNs. You might not be able 
    to access or manage LUNs that are created this way.

19. After you replace a controller with a new controller in the single 
    controller models of DS4000 storage subsystems, the premium features 
    become unauthorized and are out of compliance. Any premium features 
    not supported by the firmware of the new controller are unavailable. 
    The work-around is to upgrade the firmware in the new controller to 
    the same level as the removed controller and re-enable the premium 
    features using the key files that you were provided when the premium 
    feature was originally enabled. 
    
20. When you migrating drive Customer Replaceable Units (CRUs) from 
    multiple DS4000 storage subsystems into a single destination 
    DS4000 Storage subsystems, all of the drive CRUs from the same 
    DS4000 storage subsystem should be moved as a ‘set’ into the new 
    destination DS4000 Storage subsystem. Before moving the next ‘set’ 
    of drive CRUs, ensure that all of the drive CRUs for a single ‘set’ 
    have been moved to the destination DS4000 storage subsystem. 
    If drive CRUs are not moved as a ‘set’ to the destination DS4000 
    storage subsystems, the newly relocated array may not appear in 
    the Subsystem Management window.

21. 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.
  
22. To download controller firmware, you must select the drive where the
    firmware is located. If the drive you select does not respond, the 
    File Selection dialog box will revert to the A: drive and display an 
    error message that drive A: is not ready if there are no media in 
    drive A:.

23. You must suspend all I/O while ESM firmware downloads if you select 
    multiple enclosures for downloading ESM firmware. If you select only
    one enclosure for download at a time, you can download ESM firmware
    with I/Os. However, IBM recommends that you suspend all I/O activity
    to perform firmware upgrades. 
    
    Furthermore, if the EXP100 ESM firmware version is 953x or earlier, 
    no I/Os are allowed during the duration that the EXP100 ESMs are 
    being updated with new firmware, including clustering reservation 
    checking IOs. 

24. The DS4000 storage subsystem when configured with the DS4000 EXP100 
    SATA Drive Expansion Unit is currently reporting a higher frequency 
    of informational events such as Destination Driver Events (DDEs) and 
    Fibre Channel link up/down events ... in the DS4000 Controller event 
    log compared to the DS4000 storage subsystem configured with Fibre 
    Channel drives. Slower response times of SATA disk drives compared 
    to Fibre Channel disk drives cause higher I/O retries from the 
    DS4000 storage subsystem controllers, resulting in a greater number 
    of informational events logged. In addition, the number of 
    information events reported in the DS4000 storage subsystem event 
    log will also grow in proportion to the increase in I/Os to the 
    Logical Drives. In all cases, the DS4000 storage subsystem 
    controller will always successfully service the timeout I/O on 
    the subsequent retries.   

25. When saving the DS4000 storage subsystem event log entries, it may 
    take up to several minutes to save all entries in the event log 
    depending on the DS4000 management workstation resources. However, 
    the DS4000 Storage Manager client GUI will show the completion of 
    the event log saving almost instantly. The work around is to 
    check the file size of the file that the event log entries are 
    saved periodically; if the file size does not change, the event 
    log saving is completed.

26. Do not perform other storage management tasks, such as creating or 
    deleting logical drives, reconstructing arrays, and so on, while 
    downloading the DS4000 storage subsystem controller firmware and 
    DS4000 EXP ESM firmware. It is recommended that you close all 
    storage management sessions (other than the session that you use to 
    upgrade the firmware) to the DS4000 storage subsystem that you plan 
    to update.

27. Inter-operability with tape devices is supported on separate HBA and 
    switch zones.


=======================================================================
                
1.2  Enhancements
-----------------

   IMPORTANT: The DS4000 storage subsystem controller firmware version 
   6.12.xx.xx is available for the following DS4000 Storage server 
   only - the DS4100 - all models, the DS4300 with dual controller/Standard 
   or Turbo option, DS4400, DS4500 models. 
   Please contact your IBM service representative or IBM resellers 
   for the availability of DS4000 storage subsystem models support 
   with controller firmware version 6.12.xx.xx in the future. 
   
   Enhancements for controller firmware 06.12.40.00 release 

   1. Enhanced performance with Read/Verify operations
     Summary of controller firmware changes.
      + Leave data, but not parity, in cache following a parity check
        operation so that the subsequent read will be satisfied 
        entirely from cache. 
      + Honor the DPO option on a read request when all of the data 
        was found in cache.
      + Change the symbol parity scan operation such that it uses 
        the DPO option when issuing parity check requests to the 
        RAID engine. Since the RAID engine no longer explicitly 
        deletes data from cache, then this change will cause it to 
        be deleted. This prevents read data from polluting user 
        cache during a redundancy check (parity scan) operation.
      + In order to improve performance when scanning the temporary 
        buffer for zeros, the temporary buffer size was increased 
        from 16KB to 512KB. The scanning code was changed to use 
        the entire buffer instead of one IOV buffer at a time which 
        was typically the cache block size.
      + The actual scanning routine was re-written in assembly 
        language to make use of load-multiple instructions, 
        CPU cache prefetch instructions, and CPU cache invalidation 
        instructions. This routine greatly reduces pollution of the 
        CPU's 32KB data cache and the number of instructions used to 
        perform the operation.

  2. Drive Predictive Failure Analysis (PFA) feature.
     The described Predictive Failure Analysis capability is unique in 
     the storage industry and will provide new levels of reliability to 
     DS4000 disk storage customers.

     The drive PFA reporting feature monitors the rate of drive 
     reported errors as well as detecting drive performance degradation 
     often associated with unreported internal drive issues.
 
     This feature automatically issues a critical alert notification 
     when any error rate or degraded performance threshold is exceeded.

    DS4000 controllers will not fail a drive even when a PFA threshold 
    is exceeded if failing the drive will cause loss of data availability 
    (i.e. volume is already degraded, or volume has no redundant data 
    to begin with).   However, no matter what the volume type and state, 
    a critical alert is always issued when a PFA threshold is exceeded 
    so a user will always be notified of a drive with developing 
    reliability problems.


  Enhancements for controller firmware 06.12.16.00, Storage 
  Manager v9.16 releases.
   
   A summary list of the new features that are introduced with the 
   DS4000 Storage Manager version 9.16 or later host software level in 
   conjunction with the DS4000 storage subsystem controller firmware 
   version 06.12.16.00 or higher is as followed:
    
   1. Support the 400G SATA drive options and CRUs (P/Ns 39M4570 and 
      39M4575, respectively) in addition to the new 250G SATA drive CRUs 
      (P/N 40K6837.) The 250G SATA drive CRU is functionally 
      equivalent to the previously-released CRUs (P/N 90P1349). 
   2. Support the DS4100 storage subsystem with Single Controller option
   3. When having this controller firmware version 06.12.16.00 or higher
      installed, the DS4100 is now supported the DS4000 Copy Services
      Remote Mirroring and VolumeCopy premium features.  

   Please refer to the New Features section of the IBM DS4000 Storage 
   Manager version 9 Installation and Support Guide for the appropriate 
   host server operating system environment for additional information 
   about the IBM DS4000 Storage Manager version 9 enhancements.

   
=======================================================================
            
1.3  Prerequisites
------------------

     The DS4000 controller firmware and NVSRAM file that are packaged 
     with this README file can ONLY be loaded in the following DS4000
     storage subsystems:
     
     1. DS4100 storage subsystems with dual controller/standard or 
        single controller option
     2. DS4300 storage subsystems with dual controller/standard or 
        Turbo Option or with no EXP disk expansion attachment.
     2. DS4400 storage subsystems
     3. DS4500 storage subsystems
     
     DO NOT DOWNLOAD this controller firmware on any other DS4000 
     storage subsystem. There is not any checking for this restriction 
     inside the DS4000 Storage Manager client program. In addition, 
     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. 

     Note: 
     1. PRIOR TO DOWNLOADING CONTROLLER FIRMWARE 06.12.40.00 OR HIGHER 
        TO THE DS4000 CONTROLLER, THERE IS A PREREQUISTE TO UPGRADE THE 
        STORAGE MANAGER CLIENT TO v9.19 or higher.

        PRIOR TO DOWNLOADING CONTROLLER FIRMWARE 06.12.23.00 or
        06.12.27.xx TO THE DS4000 CONTROLLER, THERE IS A PREREQUISTE TO 
        UPGRADE THE STORAGE MANAGER CLIENT TO v9.16 or higher.

     2. NVSRAM available with controller firmware 06.12.40.00 or higher 
        must be used for Drive Predictive Failure Analysis (PFA) feature.
                
     3. IBM Network attached storage (NAS) N5000 and N7000 Gateways must
        use NVSRAM levels released with this package for proper handling of
        SCSI persistent reservations. 
        NOTE: Only DS4300 and DS4500 controller types are supported with 
            IBM N5000 and N7000 Gateways.

=======================================================================
            
1.4  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. 
 
   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. 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 RESELLER FOR ASSISTANCE.
       
   3. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED 
      BY THE 06.1X.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 WITH 
      STANDARD OR SINGLE CONTROLLER OPTION, THE DS4300 WITH STANDARD OR TURBO 
      OPTION, 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 DS4000 STORAGE MANAGER CLIENT PROGRAM VERSION 9.16.XX.XX OR 
      HIGHER MUST BE INSTALLED AND CONFIGURED TO MANAGE YOUR DS4000 
      STORAGE SUBSYSTEM. THIS PROGRAM IS INCLUDED IN THE APPROPRIATE 
      DS4000 STORAGE MANAGER VERSION 9.16 OR HIGHER HOST SOFTWARE 
      PACKAGES FOR THE OPERATING SYSTEM OF YOUR DS4000 MANAGEMENT 
      STATION. 
       
   5. 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.

   6. THE DS4000 STORAGE SUBSYSTEM WITH CONTROLLER FIRMWARE VERSION 
      05.41.1X.XX MUST BE UPGRADED TO CONTROLLER FIRMWARE VERSION 
      05.41.5X.XX FIRST BEFORE IT CAN BE UPGRADED TO CONTROLLER 
      FIRMWARE VERSON 06.1X.XX.XX OR LATER. OTHERWISE, THE ERROR 
      231-FIRMWARE INCOMPATIBLE WILL BE DISPLAYED. 
      
   7. PRIOR TO UPGRADING THE DS4000 CONTROLLER FIRMWARE TO VERSION 
      06.12.23.00 or 06.12.27.xx, THERE IS A PREREQUISITE TO UPGRADE THE 
      LATEST VERSION OF STORAGE MANAGER CLIENT 9.16 or higher
      IF THE INCORRECT VERSION OF THE STORAGE MANAGER CLIENT PROGRAM 
      IS USED TO MANAGE THE TO-BE-UPGRADED DS4000 SUBSYSTEM, 
      THE STORAGE MANAGER CLIENT WILL SHOW THAT THE NEW FIRMWARE FILE IS NOT
      COMPATIBLE WITH THE TO-BE-UPGRADED DS4000 SUBSYSTEM.
      
   8. The DS4000 controller firmware versions 6.12.16.xx or higher 
      and EXP100 ESM firmware version 9563 or higher are required to 
      provide support for the 400G SATA drive options and CRUs 
      (P/Ns 39M4570 and 39M4575, respectively) in addition to the 250G 
      SATA drive CRUs (P/N 40K6837.)
      The 250G SATA drive CRU is functionally equivalent to the 
      previously-released CRUs (P/N 90P1349). 

   9. PRIOR TO UPGRADING THE DS4000 CONTROLLER FIRMWARE TO VERSION 
      06.12.40.00, THERE IS A PREREQUISITE TO UPGRADE THE 
      LATEST VERSION OF STORAGE MANAGER CLIENT 9.19 or higher
      IF THE INCORRECT VERSION OF THE STORAGE MANAGER CLIENT PROGRAM 
      IS USED TO MANAGE THE TO-BE-UPGRADED DS4000 SUBSYSTEM, 
      THE STORAGE MANAGER CLIENT WILL SHOW THAT THE NEW FIRMWARE FILE IS NOT
      COMPATIBLE WITH THE TO-BE-UPGRADED DS4000 SUBSYSTEM.


   IBM DS4000 Storage Manager host software version 09.16.xx.xx or later 
   provides full management support for IBM machine types 3552 and 3542 
   storage controllers that have at least firmware version 04.01.xx.xx 
   (05.xx.xx.xx in Microsoft Windows environment), IBM Machine type 1742-900 
   and 1742 storage controllers that have at least firmware version 
   05.00.04.xx, IBM Machine type 1722 storage controllers that have at least 
   firmware version 05.3x.xx.xx, IBM Machine type 1724 storage controllers 
   that have at least firmware version 05.4x.xx.xx or IBM Machine type 1815 
   storage controllers that have at least firmware version 06.14.xx.xx.
    
   The only IBM DS4000 Storage Manager version 09.16.xx.xx supported 
   management function on controllers with non-supported controller 
   firmware versions is controller firmware and NVSRAM download. 

   
=======================================================================
       
1.5 Code levels at time of release are as follows
-------------------------------------------------
Important: The same controller firmware or NVSRAM file can be used for 
     upgrading the controller firmware or NVSRAM through the SMClient GUI or 
     through the controller serial port. Do not attempt to download the 
     firmware or NVSRAM through serial port without the present of IBM 
     Support personnel. A botched controller firmware download via the serial 
     port can cause to the controller to be inoperable. 

     1. Storage Controller Firmware versions:
        a. DS4500:  FW_06125600_06100800
        b. DS4400:  FW_06125600_06100800
        c. DS4300 Dual controller/standard: SNAP_288X_06125600     
        d. DS4300 Turbo : SNAP_288X_06125600
        e. DS4100 Dual controller/standard: SNAP_282X_06125600          
        f. DS4100 Single controller : SNAP_282X_06125600            
                                            
     2. Storage Controller NVSRAM versions:
        ATTENTION: The DS4000 storage subsystem controller firmware 
                   version 06.12.xx.xx uses the FC/SATA intermix 
                   premium key file to enable the FC/SATA intermix 
                   functionality. 
                   It does not rely on a certain version of the NVSRAM 
                   file like the controller firmware version 
                   06.10.xx.xx. 
                   Do not apply this version 06.12.xx.xx of the firmware 
                   until a FC/SATA intermix premium feature key file 
                   is generated and available.
                    
         Current NVSRAM Levels.
          
          - DS4100 Single Controller: N1724F10LR912V09
          - DS4100 Dual/base/standard controllers: N1724F100R912V14          
          
          - DS4300 with no EXP attachment: N1722F600R912V13
          
          - DS4300 Dual/standard controllers: N1722F600R912V13  
            (Note: for EXP700/EXP710 ONLY attachment or when FC/SATA 
                   intermix premium feature is enabled)

          - DS4300 Turbo: N1722F600R912V13
            (Note: for EXP700/EXP710 ONLY attachment or when FC/SATA 
                   intermix premium feature is enabled)

          - DS4300 Dual controller/standard/turbo: N1722F600R28encA
                   (Note: for 8 EXP100 SATA attachment ONLY.)
          
          - DS4400: N1742F700R912V14
          - DS4500: N1742F900R912V14   

                
         ATTENTION: DO NOT LOAD NVSRAM FILE - N1722F600R28encA - 
         ONTO ANY OF THE DS4300 STORAGE SUBSYSTEMS THAT HAVE DRIVES 
         IN THE DS4300 INTERNAL CHASSIS DRIVE SLOTS. 
         THIS WILL CAUSE THE DS4300 storage subsystem TO NOT CONFIGURE 
         OR RECOGNIZE ANY OF THE DRIVES IN THE DS4300 INTERNAL CHASSIS. 
         THIS COULD RESULT IN THE DEGRADATION OF THE DEFINED RAID 
         ARRAY OR A POSSIBLE LOSS OF ACCESS TO DATA. 
         IF THIS NVSRAM FILE IS LOADED INTO A DS4300 storage subsystem 
         WITHOUT ANY DRIVE EXPANSION ENCLOSURES ATTACHED, 
         IT WILL PREVENT THE storage subsystem FROM COMPLETING THE 
         BOOT PROCESS THAT IS INITIATED TO ACTIVATE THE NEW NVSRAM 
         SETTINGS, WHICH MIGHT RESULT IN LOST OF MANAGEMENT ACCESS TO 
         THE DS4300 STORAGE SUBSYSTEM. THERE IS NO SAFETY MECHANISM 
         TO PREVENT THE UNINTENTIONAL LOADING OF THIS NVSRAM FILE. 
         IN ADDITION, DO NOT USE THIS NVSRAM FILE IN THE DS4300 STORAGE 
         SUBSYSTEMS WITH FC/SATA INTERMIX PREMIUM FEATURE ENABLE.             
 
   Note: The DS4000 storage subsystems that are shipped from the factory
         will show the NVSRAM version with a "M" prefix instead of the "N" 
         prefixed. Both the "M" prefix and the "N" prefixed NVSRAM versions 
         are the same if the rest of the version information is the same. 
         For example, the N1742F900R912V14 and M1742R900R912V14 NVSRAM versions 
         are the same because both versions share the same "1742R900R912V14" 
         string. The M1742R900R12V14 version was loaded to the DS4500 
         storage subsystem at the factory. The N1742R900R12V14 version is 
         posted to the DS4000 support web site for download.
        
                                          
   Refer to the following IBM System Storage™ Disk Storage Systems 
   Technical Support web site for the latest released code levels.
  
   http://www.ibm.com/servers/storage/support/disk/
   
=======================================================================
              
2.0   Installation and Setup Instructions
-----------------------------------------

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 before upgrading the controller firmware. 
Make any firmware updates as required BEFORE proceeding to upgrade the 
DS4000 controller with the firmware and NVSRAM files packaged with this 
README file. FAILURE to observer the minimum firmware requirement might 
cause your DS4000 storage subsystem to be OUT-OF-SERVICE.  

1.   Upgrade the storage manager client program to latest storage manager 
     9.16 version that is avaible 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.12.xx.xx 
     code thread. 
     
     http://www.ibm.com/servers/storage/support/disk/

2.   Updated the firmware of the ESMs in the attached drive expansion
     enclosures that are recognized by the DS4000 controllers to the latest 
     levels before the upgrading the controller firmware with the exception of 
     EXP710. Note: The support of certain drive expansion enclosure model 
     attachment requires certain level of controller firmware. For example, the 
     attachment of EXP710 required controller firmware 6.10.11.xx or higher.
     

     EXP700:  
       If the to-be-updated controller is attached to any EXP700 drive expansion 
       enclosures, the EXP700 ESM firmware must be updated to version 9326 or 
       later before the 06.1x.xx.xx controller firmware is downloaded into the 
       DS4000 storage subsystem controllers. Otherwise, the installed drives in 
       the EXP700 drive expansion enclosures may not be displayed in the DS4000 
       subsystem management window after the controller firmware is upgraded. 

     EXP100:
       The ESM firmware of any attached EXP100 drive expansion enclosures must 
       be at version 956x or higher before updating the DS4000 storage subsystem 
       controller firmware to version 06.12.16.xx or higher.
     
     EXP710: 
       If the existing controller firmware version is 6.12.27.00 or earlier, DO 
       NOT upgrade the EXP710 ESM firmware to version 9639 or later without 
       upgrading the controller firmware to version 6.12.27.03 or later first. 
       Drives might be incorrectly marked as failed if the EXP710 ESM firmware 
       is upgraded to version 9639 or higher with controller firmware is at 
       version 6.12.27.00 or earlier.


     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.
     
  3.   If the managed DS4000 storage subsystem with controller firmware 
     version 06.10.xx.xx installed had the FC/SATA intermix premium feature 
     enable, do not continue with the next step until a FC/SATA intermix 
     premium feature key file is generated and available. Once the controller 
     firmware is upgraded to version 06.12.xx.xx, the FC/SATA intermix 
     premium feature will be shown as out-of-compliance and the FC/SATA 
     intermix premium feature key file is required to re-enable the feature. 
     When the FC/SATA intermix premium feature is in out-of-compliance state, 
     LUNs management functions like creations, deletions and modifications 
     will not be operational. Please refer to the FC/SATA intermix premium 
     feature activation card that was shipped with the FC/SATA intermix 
     premium feature kit for instructions to generate the required premium 
     key file. 
 

4.   Important: You must install the firmware update prior to 
                downloading  the NVSRAM update. 
                Make sure that the firmware and NVSRAM file names match 
                the name listed section 2.4 for your particular DS4000 
                storage subsystem model.

     To download firmware, do the following: 
   
     a.  Open the Subsystem Management window. 
     b.  Click Advanced => Maintenance => Download => Controller Firmware. 
         Follow the online instructions.

     To download NVSRAM, do the following: 
   
     a.  Open the Subsystem Management window. 
     b.  Click Advanced => Maintenance => Download => Controller NVSRAM
         (or Storage Subsystem => Download => NVSRAM for controller with 
         firmware version 5.x and earlier). Follow the online instructions.
       
5.   (if applicable) Re-enable the FC/SATA intermix premium feature 
      using the premium key file.

6.   After the controller firmware and NVSRAM is updated, consider
     checking the IBM System Storage™ Disk Storage Systems Technical 
     Support web site for the latest released hard drive firmware. 
     
     To download hard disk drive firmware, do the following: 
   
     a.  Schedule down time because the drive firmware upgrades require 
         that there are no HOST IOs 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. 
      

=======================================================================
                                
2.2  Helpful Hints
------------------

1. If you are unable to see the maximum number of drives during 
   Automatic Configuration, you should be able to use Manual 
   Configuration to select individual drives and select the maximum 
   number of drives allowed.

2. Depending on the storage subsystem that you have purchased, you
   may have to purchase the DS4000 storage partitioning premium feature
   option or an option to upgrade the number of supported partitions
   in a storage subsystem. Please see IBM Marketing representatives
   or IBM resellers for more information.
   
   - IBM DS4100 storage subsystem (machine type 1724): The standard
     and single controller configuration does not have the DS4000 
     storage partitioning premium enabled. Four partition, 
     eight partition, sixteen and an upgrade from four to eight 
     partition storage partitioning premium feature options can 
     be purchased. 

   - IBM DS4300 storage subsystem (machine type 1722): The standard 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.

3. 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. 

4. 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.

5. All drive enclosures on any given loop should have complete unique 
   ID's 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. 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.    
     
6. 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.

7. 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.
   
8. 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)
 


=======================================================================

3.0 Configuration Information
-----------------------------

        
3.1 Configuration Settings
--------------------------

1. By default the IBM DS4000 Storage Manager 9.16 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 9.12 or higher.
   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 default host 
      type is reset to Windows NT. 
              
   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 1722, 1742, 3542 or 3552 
   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 
     automaticlogical drive transfer (AVT/ADT) for the Windows 
     2000/Server 2003 non- cluster heterogenous host region. 
     The default setting is to disable AVT for this heterogenous 
     host region. This setting is one of the requirements for setting 
     up the remote boot or SAN boot. Do not use this script unless 
     it is specifically mentioned in the applicable instructions. 
     (This script can be used for other host type if modifications 
     are made in the script, replacing the Windows 2000/Server 2003 
     non-cluster host type with the appropriate host type that needs 
     to have AVT/ADT enabled) 
  
   - DisableAVT_W2K_S2003_noncluster.scr:  The script will disable the 
     automatic logical drive transfer (AVT) for the Windows 2000/Server 
     2003 non-cluster heterogenous host region. This script will reset the 
     Windows 2000/Server 2003 non-cluster AVT setting to the default.
     (This script can be used for other host type if modifications are
     made in the script, replacing the Windows 2000/Server 2003 non-cluster
     host type with the appropriate host type that needs to have AVT/ADT
     disabled) 

   - EnableAVT_Linux.scr:  The script will enable automatic logical drive 
     transfer (AVT) for the Linux heterogenous 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 heterogenous 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.  
     
   - EnableAVT_Netware.script:  The script will enable automatic logical 
     drive transfer (AVT) for the Netware heterogenous 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 heterogenous host region. 
     Do not use this script unless it is specifically mentioned in the 
     applicable instructions.   
     
     
=======================================================================

3.2 Unsupported configurations
------------------------------

   The configurations that are currently not being supported with IBM DS4000 
   controller firmware version 06.12.xx.xx and Storage Manager Version 9.12 or
   higher are listed below:

   1. The DS4100 (machine type 1724) storage subsystem does not support the 
      attachment of the DS4000 EXP710 and EXP700 (FC) drive expansion 
      enclosure. Please contact IBM representatives or resellers for the 
      availability of such support in the future.
   
   2. The DS4100 with Single Controller option does not support the 
      attachment of the DS4000 EXP100 drive expansion enclosures.
      
   3. The DS4300 storage subsystem with Single Controller option does not 
      support the controller firmware version 06.1x.xx.xx. The correct 
      firmware version for these DS4300 storage subsystem models is 
      05.34.xx.xx.   
     
   4. Controller firmware version 6.12.xx.xx does not support the DS4800
      storage subsystem (machine type 1815 - all models). The DS4800 storage 
      subsystems required controller firmware version 06.15.xx.xx and higher.
  
   5. Fibre Channel loop environments with the IBM Fibre Channel Hub, 
      machine type 3523 and 3534, in conjunction with the IBM Fibre Channel 
      Switch, machine types 2109-S16, 2109-F16 or 2109-S8. In this 
      configuration, the hub is connected between the switch and the IBM 
      Fibre Channel RAID Controllers.

   6. The IBM Fibre Channel Hub, machine type 3523, connected to IBM 
      machine type 1722, 1742, 3542 and 3552.
   
   7. 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.)
      
   8. Controller firmware version 6.12.xx.xx does not support the DS4700
      storage subsystem (machine type 1814 - all models). The DS4700 storage 
      subsystems required controller firmware version 06.16.xx.xx and higher.


=======================================================================

4.0   Unattended Mode
---------------------
        N/A

=======================================================================

5.0   WEB Sites and Support Phone Number
----------------------------------------

   5.1  IBM System Storage™ Disk Storage Systems Technical Support web site:
        http://www.ibm.com/servers/storage/support/disk/

   5.2  IBM System Storage™ Marketing Web Site:
        http://www.ibm.com/servers/storage/disk

   5.3  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/servers/storage/support/disk/
  
  Perform the following steps to register at the IBM Support and Download 
  Web site: 
  
  1. Click on My Support in the Additional Support box in the right side 
     of the DS4000 Support web page.
  2. The Sign In window displays. Either enter your IBM ID and Password 
     in the sign in area to sign in and proceed to step 6 or, if you are 
     not currently registered with the site, click Register Now. 
  3. The My IBM Registration window Step 1 of 2 opens. Enter the 
     appropriate information and click Continue to get to the second My 
     IBM Registration window. 
  4. In the My IBM Registration window Step 2 of 2, enter the appropriate 
     information and click Submit to register. 
  5. The My IBM Registration windows opens with the following message, 
     “Thank you for registering with ibm.com. Continue to explore ibm.com 
     as a registered user.” Click Edit Profile in the My IBM box on the 
     right side of the window. 
  6. The My Support window opens. Click Add Products to add products to 
     your profile. 
  7. Use the pull-down menus to choose the appropriate DS4000 storage 
     server and expansion enclosures that you want to add to your profile.
     To add the product to your profile, select the appropriate box or 
     boxes next to the product names and click Add Product. 
  8. Once the product or products are added to your profile, click 
     Subscribe to Email folder tab 
  9. Select Storage in the pull down menu. Select Please send these 
     documents by weekly email and select Downloads and drivers and 
     Flashes to receive important information about product updates. 
     Click Updates. 
 10. Click Sign Out to log out of My Support.
 
=======================================================================

6.0   Trademarks and Notices
----------------------------

        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.

