Even though the System Storage™ DS4000 Storage Manager version 9.15.G5.08 for Microsoft Windows 
Server 2003 SP1 - X64 editions is the first release of the Storage Manager host software that support the X64 servers, it is based on the previously released Storage Manager host software for
the x86 and IA64 versions of the Windows operating systems. Some of the limitations that are documented in the various releases of the previous Storage Manager host software may be still applicable for this host software release to support. Therefore, those limitations are documented in this file for your informational purposes.

12/16/2005 dtl


New limitations with version 09.15.xx.06 release for DS4000 controller
firmware version 06.12.xx.xx and 06.15.xx.xx release 

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

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

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


New limitations with Storage Manager version 9.15.xx.0x and DS4000 
controller firmware version 06.15.xx.xx release

1. There are not any DS4000 Storage Manager host software packages 
   for the AMD-64 or EM64T servers running in native AMD-64 or EM64T code 
   version of the Microsoft Windows Server 2003 - 64bit (X64 edition) OS. 
   Note: This limitation is fixed with the release of the DS4000 Storage 
   Manager version 9.15.G5.08 for Microsoft Windows Server 2003 SP1 - X64 
   editions on 12/19/2006. 

    
New limitations with Storage Manager version 9.14.xx.05 and DS4000 
controller firmware version 06.14.xx.xx release

1. With this release of DS4000 Storage Manager, Veritas Volume Manager 
   (DMP) version 4.2 is supported in Microsoft Windows operating system 
   environment. However, the Veritas Cluster Server is not supported. Please 
   contact IBM representatives or resellers for the support of this program 
   in the future.
   
2. Always click the Recovery Guru icon in the DS4800 Subsystem Management
   window to check for DS4800 storage subsystem problems. In certain rare
   error condition, the Subsystem Management window displays the subsystem
   with Optimal icon instead of Need Attention icon and a flashing Recovery
   Guru icon.
    

New limitations with Storage Manager version 9.12.xx.08 and DS4000 
controller firmware version 06.12.03.xx release

1. Do not cut and paste the information in the DS4000 Storage Manager 
   online help into the DS4000 Storage Manager script command window or 
   into the text file that will be used as input for the SMcli script 
   engine. Extra space may be inserted in the required parameter names 
   which will cause error(s) during the script command execution. (267873)

2. In the configuration that have both SATA-technology drives (EXP100) 
   and Fibre-Channel technology drives (EXP700/EXP710/DS4100) behind the 
   same DS4000 storage 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.
   
5. The disk resource might become offline when you execute the SMrepassist
   utility in the Windows Server 2003 MSCS environment. The work around is 
   to set the big enough value (>120 seconds) for IsAlive and LooksAlive 
   parameter of the disk resource before you execute the SMrepassist 
   utility. This limitation is not applicable to Windows 2000 MSCS 
   environment.

6. The RDAC driver in the DS4000 Storage Manager host software package
   for Windows version 9.12 or higher does not recognize the mapped logical 
   drives from the DS4000 storage subsystem with controller firmware version 
   04.01.xx.xx. The work around is to upgrade the DS4000 storage subsystem 
   controllers with firmware version 05.xx.xx.xx or later.  

Limitations with Storage Manager version 9.10.xx.05 and DS4000 
controller firmware version 06.10.11.xx release

1. 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, modifications to the Fibre Channel (FC) cabling between the 
   Host Server HBA ports and the DS4000 storage subsystem Fibre Channel 
   (FC) host ports or to the FC switch zoning must be performed so that 
   the FC HBA port in the host server will see either controller A or 
   controller B only. The server will bluescreened during the reboot after 
   the un-installation of the RDAC driver if the HBA port can see the boot 
   LUN on both controller A and B. (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 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 to 06.1x.xx.xx 
   version. The work around is to update the EXP700 ESM firmware to the 
   version 9326 or higher 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 blade under certain DS4000 
   storage subsystem reboot scenarios. (261188)


Limitations with Storage Manager version 9.10.xx.02 and DS4000 
controller firmware 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 list 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 IOs 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 IOs 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 spun 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.
   
   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.

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

2. 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 hung or blue-screen.  
                       
3. 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. 

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

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

9. In a direct Fibre Channel connection between the DS4000 storage 
   server 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 
   server.   
       
10. 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.  

11. There is not an IA-64 version of the DS4000 Management Suite Java 
    (FAStT_MSJ). Use the 32-bit version of the DS4000 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 IO loads.
    
12. 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. 

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

14. When managing a single controller DS4000 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.

15. 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. 
    
16. When migrating drive Customer Replaceable Units (CRUs) from multiple
    DS4000 storage subsystems into a single destination DS4000 storage 
    servers, all of the drive CRUs from the same DS4000 storage subsystem 
    should be moved as a ‘set’ into the new destination DS4000 storage 
    server. 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.

17. Enclosure IDs may be listed incorrectly in the Subsystem Management 
    window, even if the Enclosure ID switch settings appear to be 
    correct. This is because of the physical design and movement of the 
    Enclosure ID switch, it is possible to leave the switch in a “dead 
    zone” between ID numbers, which will return an incorrect Enclosure ID 
    (this value is 0 in most cases) to the storage management software. 
    When setting the Enclosure ID, ensure that the switch has actuated 
    completely and has settled where the value is clearly visible in the 
    viewing window.
  
18. 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:.

19. 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 IOs are allowed during the duration that the EXP100 ESMs are 
    being updated with new firmware, including clustering reservation 
    checking IOs. 

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

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

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