This README file contains the latest information about the  
IBM TotalStorage™ DS4300 Mid-range disk system controller firmware
version 05.34.xx.xx for the DS4300 storage subsystem with single controller
option (SCU) only.

Refer to the IBM TotalStorage™ Support Web Site or CD for the IBM 
DS4000 Storage Manager Version 9 Installation and Support Guide for 
Windows 2000/Server 2003, Netware, ESX Server, and Linux or the IBM 
DS4000 Storage Manager version 9 Installation and Support Guide for 
AIX, HP-UX, Solaris, and Linux on POWER publication 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:  12/09/2005

Products Supported: 
    --------------------------------------------------------------
   | DS4000 / FAStT Model| Machine Type  | Model Number           |
   |---------------------|---------------|------------------------|
   | DS4300 (FAStT600)   |     1722      | 6LX, 6LU, 6LJ          |
    ---------------------|---------------|------------------------
     
    

CONTENTS
--------
1.0 Overview
2.0 Change History
3.0 Installation and Setup Instructions
4.0 Configuration Information
5.0 Unattended Mode
6.0 Web Sites and Support Phone Number
7.0 Trademarks and Notices
8.0 Disclaimer

=======================================================================
1.0 Overview
------------

   This IBM DS4000 mid-range disk system controller firmware 
   release includes the IBM DS4000 05.34.xx.xx disk system 
   controller firmware and NVSRAM files.
   
   The IBM DS4000 Storage Manager Version 9 Installation and Support 
   Guides for Windows 2000/Server 2003, Netware, ESX Server, and 
   Linux or the IBM DS4000 Storage Manager Version 9 Installation and 
   Support Guides for AIX, HP-UX, Solaris and Linux on POWER 
   publication is available on IBM's Support Web Site as a 
   downloadable Portable Document Format (PDF) file. 

   In addition, IBM DS4000 FlashCopy and IBM DS4000 Remote Mirror 
   premium feature options are purchased separately. The IBM 
   FlashCopy option requires firmware version 05.00.04.xx or higher. 
   The IBM Remote Mirror option requires firmware version 
   05.20.0x.xx or higher. 
   
   The DS4000 storage partitioning premium feature is standard on all 
   IBM DS4000 disk systems with the exception of the IBM DS4300 
   (machine type 1722) mid-range disk system. Please contact IBM 
   Marketing representatives or IBM resellers if you want to purchase 
   the IBM DS4000 storage partitioning premium feature option for it. 

   Refer to the IBM Support Web Site for the latest Firmware and 
   NVSRAM files for the IBM DS4000 Mid-range disk systems.

=======================================================================
1.1 Limitations
---------------

IMPORTANT:
The listed limitations are cumulative. However, they are listed by the 
DS4000 mid-range disk controller firmware and Storage Manager host 
software releases to indicate which controller firmware and Storage 
Manager client software release that they were first seen and 
documented. 

1. Do not cut and paste the information in the DS4000 Storage 
   Manager Version 9 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. (IBM problem record 267873)
 
2. 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 mid-range disk system models.

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

4. DS4000 Storage Manager prompts you for a password if all hard 
   disk drives are removed from the storage subsystem.

   After removing all drives from a storage subsystem or if drives   
   do not have power but the controller power is on. The IBM DS4000 
   Storage Manager will prompt you for a password when trying to 
   start the software or when attempting to perform protected 
   operations. Any password entered will fail.

   Password information is stored on a reserved area of each hard 
   disk drive on the storage subsystem. Each drive stores a 
   mirrored copy of the password data. When there are no drives 
   in the disk system, the storage management software does 
   not find the password data when you attempt password protected 
   operations. Add one drive to the disk system and retry the 
   operation.
   
   If the DS4000 controller unit has power, then turn power off 
   the controller unit. The DS4000 controller unit shall not be 
   powered on until the EXP expansion units are attached and 
   powered on. Properly attach all expansion units (with drives 
   installed), to the DS4000 controller unit and apply power to 
   the EXP. The controller can now be powered on.  At this point 
   the mid-range disk system can be re-discovered and managed using 
   the IBM DS4000 Storage Manager.

5. Auto LUN/Array Transfer is not enable for IBM AIX and SUN Solaris 
   operating systems. If arrays failover to an alternate controller 
   and the failed controller is replaced and then brought back online, 
   the arrays do not automatically transfer to the preferred 
   controller. The operation must be done manually by selecting 
   the redistributing arrays menu option in the storage subsystem 
   window of the IBM DS4000 Storage Manager.
      
6. Display issues when using 256 color settings. A brownish hash 
   pattern is displayed on the windows and in online help when running 
   in 256 color mode.  Run the DS4000 Storage Manager 8 or higher 
   in a higher display mode.

7. The DS4000 Storage Management dialog windows may be displayed 
   cropped without the vertical and horizontal scroll bars. Just move 
   the mouse pointer over the edge of the window until the mouse 
   pointer change to window resize pointer, left click and hold to 
   grip the window edge to resize it. 

8. If you get "Error 21 - The operation cannot complete because a 
   ...  is in progress" error when you issue a subsystem management 
   command from the IBM DS4000 Storage Manager, the command may 
   be cached. If the command is cached, the IBM DS4000 Storage Manager 
   client will run the command as soon as the controller resources are 
   available. Wait for at least ten minutes and check to see whether 
   the command has been run. If not, re-attempt the command. 

9. When a DS4000 disk system with controller firmware 05.34.xx.xx is 
   connected to a SAN with more than 64 host port logins. Fibre 
   channel switch zoning must be used or the number of SAN 
   connections must be configured to be no more then the maximum 
   allowed number of host login connections allowed by the controller. 
   
   The DS4300 (IBM machine type 1722) has two ports per controller. 
    
10. The IBM DS4000 mid-range disk system hardware and software is 
    designed to have redundant paths from the host system to ensure 
    the availability of disk storage. However, it is possible to 
    connect a single host adapter from the host system to one of 
    the controller minihubs and then connect this minihub to the 
    minihub of the other controller. This configuration will create 
    a FC-AL loop between the host adapter and the two IBM DS4000 
    disk system controllers and no redundant path to the host system. 
    When connecting the two minihubs together, always connect the 
    "IN" port of one minihub to the "OUT" port of the other minihub 
    or vice versa. Do not connect the "IN" port of one to the "IN" 
    port of the other minihub or the "OUT" port of one minihub to 
    the "OUT" port of the other minihub.
                     
11. When creating a Remote Mirror from a base volume the following 
    restriction applies. First, a flashcopy has been created using 
    a base volume and the base volume is experiencing write and 
    read operations. Second, a mirror relationship has been created, 
    using the base volume as the primary volume in the mirrored pair. 
    As the mirror relationship is created, the flashcopy volume fails. 
   
    The work around to this type problem is to stop write and read 
    operations to the base volume while creating the mirror 
    relationship. Alternatively, if the mirror relationship is 
    created before creating the flashcopy volume, the problem will
    not occur.

12. In Microsoft cluster, MSCS configurations, the MSCS service 
    must be stopped and set to manual start after server is 
    rebooted. The Clusdisk driver must be set to offline and the 
    Windows 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. 
    The cluster cannot bring the Quorum disk resources online because 
    the disk signature changes caused the problem. 
    The workaround 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 

13. In a SAN boot configuration, before updating the Windows RDAC 
    driver in a Windows server, one of the two Fibre Channel (FC) 
    cables that are connected to the server must be disconnected. 
    The Windows server will blue screen during the reboot after the 
    un-installation of the RDAC driver if one of the FC cables 
    is not removed. (IBM problem record 258127)

14. Controller diagnostics will not run in a DS4300 storage subsystem 
    with single controller.
    
=======================================================================
                
1.2 Enhancements
----------------
     N/A

=======================================================================
            
1.3 Prerequisites
-----------------
     N/A

=======================================================================
            
1.4 Dependencies
----------------

   The IBM TotalStorage DS4000 Storage Manager Version 9 provides full 
   management support for:

   IBM machine type 1722 (DS4300 models) disk system that 
   have a minimum firmware version of 05.34.xx.xx.
     
      
=======================================================================

2.0 Change History
------------------

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

2.1 Version History
-------------------

This is the latest maintenance release of IBM DS4000 TotalStorage™
controller firmware / NVSRAM for the following DS4000 mid-range disk 
system model: DS4300 (FAStT600).
 
Version 05.34.10.00 12/09/2005 Maintenance release
    IBM Problem
    Record        Abstract 
    ---------     -------------------------------------------------
    85397 (64475) Problem: Controller went into Debugger due to 
                  Bad devnum received from SYMBOL. PANIC during 
                  Start Of Day (SOD).
                  Fix: Changed the call to PANIC into a print statement.
    85739 (85628) Problem: Controller repeatedly reboots during 
                  Dynamic Volume Expansion (DVE). 
                  The controller get a data abort fault when more than 
                  2 volumes are performing Dynamic Volume Expansion.
                  Fix: The volume number array was increased to handle 
                  more then 2 volume numbers.
    85756 (85456) Data corruption after large VolGrp with 2 LUN 
                  reconstruction
    85953 (85799) Problem: Storage Manager lost communication with the 
                  array after controller was taken out of the controller 
                  cluster.
                  Fix: Schedule the parity scan for all volumes at once.
    86328 (85820) Problem: Controller A is attempting to fail a drive 
                  and attempting to suspend volume activity only it 
                  can't get the controller B to quiesce.
                  Fix: Placed a limit on how long a controller should 
                  wait attempting to quiesce volumes.
    86488 (86424) Problem: Error that happens when an integrated GHS 
                  drive is replaced by the original spared drive but 
                  copyback to the volumes in the volume group is 
                  interrupted by a drive spinning down.
                  Fix: Reset a flag for all volumes that might have 
                  completed operations when it has been determined that
                  the "spared for" drive is failed.
    86508 (86138) Ancient I/O (mode select I/O) 
    86924 (84579) Problem: When an ASV_GET_PART_INFO message is received,
                  a memory fault occurs.
                  Fix: Initialized the partHdr variable in function 
                  asvReceiveMessage.
    87020 (86609) Problem: PANIC when inserting a drive that contains 
                  invalid volume number.
                  Fix: Call legacyVolumePresentEvent for valid volumes.
    87045 (86915) Problem: When an ASV_GET_PART_INFO message is received,
                  a memory fault occurs.
                  Fix: Initialized the partHdr variable in function 
                  asvReceiveMessage.
    87774 (87720) Ancient I/O (mode select I/O) 
    88188 (88120) Controller does not finish Start of day (SOD) 
                  when only one controller.
    88722 (88617) Media Scan effectively disabled for volumes
    89437 (86821) A Single HDA fallout caused all Hotspares
    90219 (88260) Ancient I/O being aborted while running 
                  flashcopy.
    90279 (90179) (CMVC 275409) Controller lock down due to PCI errors


Version 05.34.04.00 03/31/2005 Maintenance release

    IBM Problem
    Record        Abstract 
    ---------     -------------------------------------------------
    260503        Storage Partition feature key changed after firmware 
                  upgrade and reboot
    263452        Controller sends LPE with out specifying ID in 
                  primitive
    265068        Media Scan not running on all LUNs
    269157 80752 (78907)  Data problem while running I/O to flashcopy
                  on DS4300 where the LBA in the head and tail did 
                  match as expected
    269158 83558 (77888) Invalid CDB for read capacity caused 
                         I/O error
    269159 83833 (82874) Controller panic in SOD routines
    hlpct_53699 84041 (79556) Hot spare capacity reported as 
                              unconfigured in controller firmware 
                              05.30.19.00
    269161 84623 (82306)DBM Blockset mismatch causes occasional 
                         controller reboot
    269162 84740 (83625) Bad record entry in DBM 
    269163 85321 (66322) PANIC error occurred on DS4300 controller
    269165 85729 (84886) Read Capacity command returns the new 
                         capacity before the expansion of a volume 
                         is completed

Version 05.34.07.00 Maintenance release

   IBM Problem Record      Abstract      
   ------------------      ---------------------------------------
   71338  253097           Need a way to clear both SSTOR header and 
                           DBM database from a given drive
   78095  253100  (76791)  Data problem detected by hammer after 
                           transfer
   78384  253101  (75360)  Data problem while running triple fault 
   78437  253104  (74842)  Data problem when pulling and replacing 
                           a drive
   79063  253106  (78862)  Reconstruction active to a GHS for the 
                           second 
   79479  253107  (79298)  Data problem occurred after spindown of 
                           GHS 
   79556  253109           The capacity of the hotspare shows in the 
                           logical/physical view
   79698  253111  (79212)  Data problem during triple fault test      
   79819  253112  (70279)  Divide by zero error while executing 
                           _cfgSetLunS
   81761  255595f_1        memory leak problem with 5.34.02.00
   81444  255496           DS4000 RAID 10 not any longer redundant 
                           after DVE
   77628  253323           Volume state not consistent between the 
                           controllers
   77580  253310           Controllers did not agree on the state 
                           of a drive
   77878  253330           Memory fault during SOD when IAC received
   77950  253336           Memory fault while running sysReboot 
   78049  253340           Mapping exceeds 32-lun limit for default 
                           host
   78348  253394           Watchdog timeout while running I/Os and 
                           sysReboot

Version 05.34.04.00 Maintenance Release 

IBM Problem Record   Abstract      
-------------------  ---------------------------------------
    72232 (71757)    AWM and Recovery Guru give conflicting status
    78200 (78004)    CMVC 242386 RAID1 remained degraded after a 
                     drive pull/replace
    78345 (77338)    Fatal vproc after replacing drive
    78606 (78357)    disk array became unmanageable in benchmark
    74127 (70794)    One volume never finishes reconstruction when
    75769  237800    Multiple Hot Spare failures.                                  
    76014 (75805)    Incomplete transfer of host information during 
    76185 (75746)    Ancient I/O (mode select I/O) during 2 second
    76248 (76148)    Controller assertion when validateCmdInfo 
                     routine calls
    76265 (75283)    CMVC 236739 I/O error during controller offline 
                     testing
    76723 (75055)    DCE operation on RAID 1 volume invalidates 
                     tray loss protection
    77498 (77464)    Controllers did not agree on the state of a 
                     spindown drive
    77531 (65736)    How a Controller locks down on too many ECC 
                     errors 
    77535 (75629)    MEMORY FAULT in "symPrepareAltControllerInfo"  
    77553 (75895)    Request for ctlr resets to be blocked by 
                     controller
    77577 (69894)    Controller did not clear AEN after the failed 
                     drive was replaced
    73409 (70407)    CMCVC 221434 Recovery Guru indicates Subsystem 
                     error
    73275 (73265)    Pick up 05.20 Flash driver changes into 05.30
    76148            Controller assertion when validateCmdInfo 
                     routine calls cfgSaveCmdInfo
    75283  C236739   I/O error during controller offline testing 
                     with SUN and Windows Server 2003 

Version 05.34.02.00 April 2004 Maintenance Release 

    The controller firmware version 05.34.xx.xx replaces the 
    controller firmware version 05.33.xx.xx. 
    
IBM Problem Record   Abstract      
-------------------  ---------------------------------------
    70561 (68445)    CMVCs 219318, 217537: Data miscompare while 
                     doing online controller firmware downloads 
    70772 (68894)    Analysis of a MEL log shows DACstore Scrub is 
                     repeating on a volume group 
    72993 (72339)    CMVC hlpct_42401 Error importing a 7.3 GB 
                     FlashCopy LUN 
    73059 (70407)    CMVC 221434 Recovery Guru indicates Subsystem 
                     errors when no error exists 
    70385 (70309)    CMVC 222814 Data corruption on AIX hosts. 
    70443 (68872)    Stable storage method write Header sends address 
                     of a pointer to main write Header method. 
    70444 (67313)    Memory fault when error reading drive headers at 
                     start-of-day. 
    67718 C214226    Logical drive shows rebuilding in client but has 
                     finished in controller.
    67990 (67720)    Improve handling of drive reported parity/CRC 
                     error
    68263 (67670)    Can't create volume if drive sizes are similar 
                     (181GB and 146GB)
    68387 (68281)    Drive failed by controller still being logged 
                     after removing
    68506 (68410)    "Link Error" component location = "none" in 
                     MEL
    68580 (68565)    NVSRAM setting to ignore Sync Cache requests 
    68736 (68330)    DDE with devnum of 0 is logged when removed 
                     drive is present
    69202 (68807)    Profile not reporting correct unconfigured 
                     capacity on volume group
        
Version 05.33.07.00 09/2003 Initial Release

Version 05.33.05.00 09/2003 Initial Release for Netware only

           
=======================================================================
        
2.2 Code levels at time of release are as follows
-------------------------------------------------

       a. Controller firmware version 
          DS4300  (6LU/6LX)       :  SNAP_05341000
                                        
       b. NVSRAM versions:
          DS4300  (6LU/6LX)       :  N1722F60LR834V04
          
                                    
 
 Refer to the IBM TotalStorage™ support web site for the latest 
 released code levels.
 http://www.ibm.com/servers/storage/support/disk/ 
          
=======================================================================
              
3.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 mid-range disk system 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 mid-range disk system to be OUT-OF-SERVICE.  

3.1  Updated the firmware of the ESMs in the attached drive expansion
     enclosures to latest levels before the upgrading the controller 
     firmware. 
     Specifically, 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 higher.
     
     To download drive expansion ESM firmware, do the following: 
   
     a.  Open the Subsystem Management window. 
     b.  Click Advanced => Download => Environmental(ESM) Card Firmware. 
         Follow the online instructions.
         
         Note: If the existing controller firmware in the DS4000 storage 
         server is of version 05.34.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.2 Important: You must install the firmware update prior to 
                downloading the NVSRAM update.

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

   To download NVSRAM, do the following: 
   
   a. Open the Subsystem Management window. 
   b. Click Storage Subsystem => Download => NVSRAM. 
      Follow the online instructions.
       
3.3 After the controller firmware and NVSRAM is updated, consider
    checking the IBM TotalStorage™ Support web site for the latest 
    released drive expansion enclosure ESM firmware and the Fibre 
    Channel hard drive firmware. 
    http://www-1.ibm.com/servers/storage/support/index.html
     
   To download drive expansion ESM firmware, do the following: 
   
   a. Open the Subsystem Management window. 
   b. Click Advanced => Download => Environmental(ESM) Card Firmware. 
      Follow the online instructions.

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

=======================================================================
                                
3.4 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 DS4000 mid-range disk system that has been 
   purchased, there may be a need to purchase the DS4000 storage 
   partitioning premium feature option or an option to upgrade 
   the number of supported partitions in a disk system. 
   Please see IBM Marketing representatives or IBM resellers for 
   more information.
   
   - IBM DS4300 mid-range disk system (machine type 1722). The 
     standard configuration does not have the DS4300 storage 
     partitioning premium enabled. Four partition, eight partition, 
     sixteen and an upgrade from four to eight partition storage 
     partitioning premium feature options can be purchased. The 
     IBM DS4300 Turbo option comes with 8 partition storage 
     partitioning premium option installed. An upgrade to 64 
     partitions can be purchased for the IBM DS4300 with Turbo 
     option. 

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

4.0 Configuration Information
-----------------------------

        
4.1 Configuration Settings
--------------------------

1. By default the IBM DS4000 Storage Manager Version 9 client, the 
   controller firmware 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. 
   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 
   disk systems as boot devices, contact IBM support for 
   supported configurations and instructions for configuring LUNs 
   as operating system 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 DS4000 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 DS4000 
     controllers to have the same World Wide Names.

   - DifferentWWN.scr:  Setup DS4000 controllers to have different 
     World Wide Names. The World Wide Names (node) will be different 
     for each controller pair. The NVSRAM default sets the DS4000 
     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.
     
4. When you are configuring IBM machine type 1742 or 3552 disk system 
   controllers in host cluster Remote Mirror configurations, contact 
   IBM support for supported host cluster configurations and 
   instructions for configuring IBM storage controllers in clustered 
   Remote Mirror configurations. 

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

4.2 Unsupported configurations
------------------------------

   The following lists configurations that are currently not being 
   supported with IBM DS4000 Storage Manager Version 9.

   1. 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 SAN configurations, the hub is connected between the 
      switch and the IBM DS4000 controllers.

   2. The IBM Fibre Channel Hub, machine type 3523, connected 
      to IBM machine type 1722, 1742, 3542 and 3552.

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

5.0 Unattended Mode
-------------------
        N/A

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

6.0 WEB Sites and Support Phone Number
--------------------------------------

   6.1 IBM TotalStorage™ Support: Disk Storage Systems web site:
       http://www.ibm.com/servers/storage/support/disk/

   6.2 IBM TotalStorage™ Disk Storage Systems: Overview Web Site:
       http://www.ibm.com/servers/storage/disk

   6.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
       IBM Directory of worldwide contacts

  IMPORTANT: 
  You should download the latest version of the DS4000 Storage 
  Manager software, the DS4000 mid-range disk 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-1.ibm.com/servers/storage/support/index.html
    
  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 IBM TotalStorage 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 disk  
     system 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.
 

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

7.0 Trademarks and Notices
--------------------------

        7.1 The following terms are trademarks of the IBM Corporation
            in the United States or other countries or both:
                 
                 DS4000
                 
                 IBM
                 
                 FAStT
                 
                 ToTalStorage™ 

                 the e-business logo

                 xSeries
                 
                 pSeries

                 HelpCenter

                 Microsoft, Windows, and Windows NT are trademarks of Microsoft
                 Corporation in the United States, other countries, or both.
                
                 Java and all Java-based trademarks and logos are trademarks or
                 registered trademarks of Sun Microsystems, Inc. in the United
                 states, other countries, or both.

                 UNIX is a registered trademark of The Open Group in the United 
                 States and other countries.

                 Linux is a registered trademark of Linus Torvalds.

                 Other company, product, and service names may be 
                 trademarks or service marks of others.

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

8.0 Disclaimer
--------------

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


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

