IBM System Storage� DS Storage Manager version 10.77.35.

16 for Microsoft
Windows Server 2008 SP2 - X64 (64bit), Windows Server 2003 SP2 - X64
(AMD64/EM64T), Windows Server 2008 R2 SP2 with HyperV Clustering edition,
Windows Server 2008 SP2 - x86 (32bit), Windows Server 2003 SP2 - x86
(32bit) and Windows Server 2003 SP2 - IA64 (Intel Itanium 64bit) edition
operating system environments. (Please see Important note #3 below)

Attention:
A problem causing recursive reboots exists while using 7.36.08 and
7.36.12 firmware on IBM System Storage DS4000 or DS5000 systems. This
problem is fixed in 7.36.14.xx and above firmware. All subsystems
currently using 7.36.08 and 7.36.12 firmware MUST run a file system
check tool (DbFix) before and after the firmware upgrade to
7.36.14.xx or higher. Instructions for obtaining and using DbFix are
contained in the 7.36.14.xx or higher firmware package. Carefully
read the firmware readme and the DbFix instructions before upgrading
to firmware 7.36.14.xx or higher. For subsystems with firmware level
7.36.08 or 7.36.12, configuration changes should be avoided until a
firmware upgrade to 7.36.14.xx or higher has been completed
successfully.

Subsystems not currently using 7.36.08 or 7.36.12 do not need to run

DbFix prior to upgrading to 7.36.14.xx or higher. DbFix may be run
after upgrading to 7.36.14.xx or higher, but it is not required.
DbFix is only applicable to subsystems using 7.36.xx.xx or greater
firmware.

If problems are experienced using DbFix or the resulting message

received is �Check Failed��, DO NOT upgrade your firmware and contact
IBM support before taking any further actions.

(C) Copyright International Business Machines Corporation 1999, 2011. 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 section 6.0 "Trademarks and Notices" in this document.

Last Update: 05/24/2011

Please refer to corresponding Change History document for more information

on new features and modifications.

IMPORTANT:
1. This storage manager software package contains non-IBM code (Open Source
code.) Please review and agree to the Non-IBM Licenses and Notices terms
stated in the DS_Storage_Manager_Non_IBM_Licenses_and_Notices_v2.pdf file
before use.

2. Microsoft Windows host attachment to the DS5300, DS5100, DS5020, DS4800,

DS4700, DS4300, DS4200, DS4100, DCS3700, DS3950, and DS3500 requires the
additional purchase of the IBM Ds3000/DS4000/DS5000 Microsoft Windows
operating system Host Kit Option or Feature Code. The IBM DS3000, DS4000
 and DS5000 Microsoft Windows Host Kit options contain the required IBM
licensing to attach an Microsoft Windows Host System to the DS5300,
DS5100, DS5020, DS4800, DS4700, DS4300, DS4200 DS4100, DS3950, DCS3700,
and DS3500. Please contact your IBM service representative or IBM
reseller for purchasing information. This host kit is shipped as
standard in the DS4200 storage subsystem models 7VH, DS4700 storage
subsystem models 70H, 70T, 72H 72T, the DS4800 storage subsystem models
80H, 82H, 84H and 88H, the DS5020 storage subsystem model 20A, and the
DS3950 models 94H and 98H. Windows and Linux host kits are included with
DCS3700 and DS3500. VMWare Host kit is also included with the DS3500.

3. There are three separate IBM DS Storage Manager host software version
10.77 packages for various CPU-platform versions of Microsoft Windows
operating systems. The supported cpu-platforms are as followed:

- 32-bit IA32 (intl386 or x86)

- 64-bit Itanium 64 IA64
- 64-bit (AMD64 or EM64T) x64

Please select the correct Storage Manager host software installer package
for the CPU-platform of your Linux operating system (OS).

4. The Microsoft Windows NT4 and Windows 2000 is not supported with this version
of the IBM System Storage� DS Storage Manager. In addition, the only
DS4000/DS5000 Storage Manager host software support on Microsoft Windows
XP Professional,Microsoft Windows Vista (English only), and Windows 7
operating systems is the DS Storage Manager client program.

5. Review section 3.2 "Hardware status and information" for the list of
recommended fibre channel host bus adapters and their driver versions.

Refer to the IBM System Storage� Support Web Site or CD for the IBM System
Storage DS Storage Manager Version 10 Installation and Host Support Guide.
This guide along with the DS Storage Manager program Online Help provide
the installation and support information.

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

1.1 Overview
--------------

This is the release of the IBM DS Storage Manager 10.77 for Microsoft
Windows Server 2008 SP2, Microsoft Windows Server 2003 SP2, and Windows
Server 2008 SP2 R2 with HyperV Clustering operating system environments.
This version of the DS Storage Manager host software is required for
managing the DS5300-all models, the DS5100-all models, the DS5020-all
models, the DS3950-all models, the DCS3700-all models, and the DS3500-
all models with controller firmware version 07.77.xx.xx. In addition, it
is also recommended for managing DS4000 storage subsystems with
controller firmware version 06.xx.xx.xx or higher installed.

The IBM Storage Manager host software version 10.77 new features and
changes are described in the corresponding Change History document.
Please refer to this document for more information on new features and
modifications.

Notes:

1. There are separate IBM DS Storage Manager host software version 10.77
packages for the following Microsoft Windows Server 2003-x86, Windows
Server 2008-x86; Windows Server 2003 Intel Architecture Itanium 64bit
(IA-64); and Windows Server 2008-x64, and Windows Server 2003-X64
64bit (AMD64 and EM64T). The WS03_WS08_X86_32bit, WS03_IA64, and
WS03_WS08_X64 CD directories contain the files necessary for
installing the IBM DS Storage Manager Version 10.77 host software in
the Windows Server 2003 - x86, Windows Server 2008 - x86, Windows
Server 2003 Intel Itanium2 64bit, Windows Server 2003 x64 and Windows
Server 2008 x64 64bit (AMD64 and EM64T) and 2008 R2 Operating System
(OS) environments, respectively. Please select the appropriate
directory for your operating system environment. The host software
and DS3950/DS4000/DS5000 storage subsystem firmware files are
packaged separately and are available for download from the IBM
System Storage� Disk Storage Systems Technical Support web site:
http://www.ibm.com/systems/support/storage/disk

2. This version of DS Storage Manager host software does not support

Microsoft Windows NT4 and Windows 2000 Operating System. In addition,
the only DS Storage Manager host software support on Windows XP
Professional OS, Windows Vista (English only), and Windows 7 (English
only) is the DS Storage Manager client (SMClient) program from the
IBM DS Storage Manager host software package for Microsoft Windows
Server 2008 - x86 (32bit).

The IBM System Storage DS Storage Manager Version 10 Installation

and Host Support Guide is also available on IBM's Support Web Site as a
downloadable Portable Document Format (PDF) file. It contains the
instructions for installing the IBM DS Storage Manager version 10.77
host software.

Not all versions of Microsoft Windows operating systems are IO-attach

support for each of the DS3950/DS4000/DS5000 storage subsystem model.

Windows Operating Systems Supported

------------------------------------
-----------------------------------------------------------
| DS4000 |Windows Server 2003/2008| Server 2003 |
| Storage Subsystem | 32bit | 64bit - X64 | 64bit - IA64 |
|-------------------|--------|---------------|--------------|
| DS5300 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS5100 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
 | DS5020 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4800 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4700 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4500 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4400 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4300 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4200 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS4100 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS3950 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DCS3700 | Yes | Yes | Yes |
|-------------------|--------|---------------|--------------|
| DS3500 | Yes | Yes | Yes |
------------------------------------------------------------
Note: Only the DS4300 with Standard (base) or Turbo options are supported
for I/O attach with this release of DS Storage Manager Host Software
for Windows.

Products Supported

-----------------------------------------------------------------
| New Model | Old Model | Machine Type | Model |
|----------- |-----------|--------------|-------------------------|
| DS5300 | N/A | 1818 | 53A |
|----------- |-----------|--------------|-------------------------|
| DS5100 | N/A | 1818 | 51A |
|----------- |-----------|--------------|-------------------------|
| DS5020 | N/A | 1814 | 20A |
|----------- |-----------|--------------|-------------------------|
| DS4800 | N/A | 1815 | 82A, 82H, 84A, 84H, |
| | | | 88A, 88H, 80A, 80H |
|----------- |-----------|--------------|-------------------------|
| DS4700 | N/A | 1814 | 70A, 70H, 72A, 72H, |
| | | | 70T, 70S, 72T, 72S, |
|----------- |-----------|--------------|-------------------------|
| DS4500 | FAStT 900 | 1742 | 90X, 90U |
|----------- |-----------|--------------|-------------------------|
| DS4400 | FAStT 700 | 1742 | 1RX, 1RU |
|----------- |-----------|--------------|-------------------------|
| DS4300 | FAStT 600 | 1722 | 60X, 60U, 60J, 60K |
| | | | 60L |
|----------- |-----------|--------------|-------------------------|
| DS4200 | N/A | 1814 | 7VA, 7VH |
|----------- |-----------|--------------|-------------------------|
| DS4100 | FAStT 100 | 1724 | 100, 1SC |
|----------- |-----------|--------------|-------------------------|
| DS3950 | N/A | 1814 | 94H, 98H, |
|------------|-----------|--------------|-------------------------|
| DCS3700 | N/A | 1818 | 80C |
|----------- |-----------|--------------|-------------------------|
| DS3500 | N/A | 1746 | C2A, A2S, A2D, C4A, |
 | | | | A4S, A4D |
|----------- |-----------|--------------|-------------------------|
| DS3200 | N/A | 1726 | 21X, 22X, 22T, HC2, HC6 |
|----------- |-----------|--------------|-------------------------|
| DS3300 | N/A | 1726 | 31X, 32X, 32T, HC3, HC7 |
|----------- |-----------|--------------|-------------------------|
| DS3400 | N/A | 1726 | 41X, 42X, 42T, HC4, HC8 |
|----------- |-----------|--------------|-------------------------|
| Boot DS | N/A | 1726 | 22B, HC3 |
-----------------------------------------------------------------

ATTENTION:
1. For the DS4400 and the DS4100 storage subsystems - all models (Standard
/dual controller and Single Controller), the controller firmware version
06.12.xx.xx and later must be used.
2. The DS4300 with Single Controller option(M/T 1722-6LU,6LX,and 6LJ),
FAStT200 (M/T 3542-all models) and FAStT500 (M/T 3552-all models)
storage subsystems can no longer be managed by DS Storage Manager
version 10.50.xx.23 and higher.
3. For the DS3x00 storage subsystems, please refer to the readme files that
are posted in the IBM DS3000 System Storage support web site for the
latest information about their usage, limitations or configurations.

http://www.ibm.com/systems/support/storage/disk

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

1.2 Limitations
----------------
IMPORTANT:
The listed limitations are cumulative. However, they are listed by the
DS4000/DS5000 storage subsystem controller firmware and Storage Manager
host software releases to indicate which controller firmware and Storage
Manager host software release that they were first seen and documented.

New limitations with Storage Manager version 10.77.xx.16 release

(controller firmware 07.77.xx.xx).

1. When you switch between the Search tab and the TOC tab, the topic that was
open in the Search tab is still open in the TOC tab. Any search terms that
were highlighted in the Search tab are still highlighted in the TOC tab.
This always happens when you switch between the Search tab and the TOC tab.
Workaround: Select another topic in the TOC to remove all search term
highlighting from all the topics.

2. Support tab in the AMW kept open for longer duration will result in
display of unevenly spaced horizontal marks. If the storage Manager is
kept open for long durations a few grey lines may be seen on the
Support Tab after restoring the AMW. Re-launching the AMW eliminates
this problem.

3. The storage subsystem configuration script contains the logical

drive creation commands with incorrect T10PI parameter. The workaround
is to manually edit the file to change instances of dataAssurance
parameters to T10PI.

4. The DS3500 subsysem does not support External Key Management at this time.
Please contact IBM resellers or represeantives for such support in the
 future.

New limitations with Storage Manager version 10.70.xx.25 release

(controller firmware 07.70.xx.xx).

1. Kernel Panic reported on Linux SLES10 SP3 during controller failover.

Probability of this issue happening in the field is low.
Workaround: Avoid placing controllers online/offline frequently.
Novell was informed about this issue. Opened Novell Bugzilla NVBZ589196.

2. CHECK CONDITION b/4e/0 returned during ESM download on DS5000

The interposer running LP1160 firmware is reporting an Overlapped Command
(0B/4E/00) for a Read Command containing an OXID that was very recently
used for a previous read command on the same loop to the same ALPA.
In almost all cases, this command will be re-driven successfully by the
controller. Impact should be negligible.
Workaround: Can be avoided by halting Volume I/O prior to downloading ESM
firmware.

3. If a host sees RAID volumes from the same RAID module that are discovered
through different interface protocols (fibre/SAS/iSCSI) failovers will
not occur properly and hosts IOs will error out. If the user does not
map volumes to a host that can be seen through different host
interfaces this problem will not occur.
Workaround: Place controller online and reboot the server to see all
volumes again.

4. Linux guest OS reported I/O error during Controller Firmware Upgrade on

ESX4.1 with Qlogic HBA. The user will see I/O errors during controller
activation from the guest OS due to mapped devices becoming inaccessible
and offline.
Workaround: This issue occurs on various Linux guest OSes, so to avoid
the issue the user should perform an offline (no I/O to controllers)
controller firmware upgrade.

5. I/O Error on Linux RH 4.8 after rebooting controller on DS3500 iSCSI. The
devices will be disconnected from the host until the iSCSI sessions are
re-established.
workaround: Restart the iSCSI service. Configure the iSCSI service to
start automatically on boot.

6. CFW Upgrade on 4.1 w/SLES 11 fails with IO error on SLES 11 Guest

partition. This issue occurred if there is filesystem volume in SLES11
VM. User will see I/O errors and Filesystem volumes in SLES11 VMs will
be changed to read-only mode.
Workaround: User can perform controller FW upgrade with either no I/O
running on SLES11 VM or no Filesystem created in SLES11 VMs.

7. "gnome-main-menu" crashes unexpectedly while install HSW on Suse 10.

The crashes appear to happen randomly with other applications as well.�
After the crash the menu reloads automatically.� Dismiss the prompt and
the host will reload the application.� This problem appears to be a
vendor issue.

8. I/O errors on RHEL 4.8 guests on VMware 4.1 during controller reset.
VMware has suggested VMware 4.1 P01 may resolve this issue.
No support was issued for RHEL 4.8 guests under VMware 4.1 over SAS.
Workaround: Use RHEL 5.5.
9. VMWare guest OS not accessible on iSCSI DS3524 (VMware SR 1544798051,
VMware PR 582256). VMware has suggested VMware 4.1 P01 may resolve
this issue.
Workaround: Use Fibre Channel or SAS connectivity.

10. When DMMP is running in a BladeCenter SAS environment, I/O errors occur
during failover and controller firmware operations. Support for Device
Mapper and SLES 11.1 SAS has been restricted and will not be published.
Workaround: Install RDAC.

11. SLES11.1ppc SAN boot fails on PS700 with 10 Gb Qlogic ethernet to DS3512.
After configuration and install of Linux on a LUN using software iSCSI,
the JS blade will not boot into the OS.
Workaround: Use local boot, SAS or Fibre Channel.

12. �No response� messages from Device Mapper devices with volumes on
non-preferred path. Any I/O operations against volumes mapped to failed
devices will timeout or hang.
Workaround: This problem requires the host to be rebooted in order to
restart I/O successfully. Update SLES11.1 to maintenance update
20101008 containing kernel version 2.6.32.23-0.3.1. Note that this
kernel version has not been fully certified by LSI and should only be
used if this issue is encountered.
Bugzilla #650593 contains issue details and fix provided by Novell.

13. LifeKeeper 7.2.0 recovery kits require multiple host ports to use SCSI
reservations.
Workaround: Use two single port SAS HBAs. In this case each port will
be represented as a host, and LifeKeeper will identify both separately.
Another way to avoid the issue is to use MPP as the failover driver.

14. Unexpected "jexec" messages during mpp installation/un-installation on

SLES 11.1.
Workaround: None - https://bugzilla.novell.com/show_bug.cgi?id=651156

15. I/O write errors on mounted LifeKeeper volumes before node resources
transfers to another node.
recovery: I/O can be restarted as soon as node resources are transferred
to another node in the cluster.
Workaround: None.

16. Solaris 10u8 guest OS disks become inaccessible on ESX35u5 during sysReboot
on array controller. This can be avoided by not using raw device
mappings and instead using virtual disks. If raw device mappings are
required, they must be used with virtual compatability mode selected
when adding the disks to the guest OS.
Workaround: None.

17. Solaris 10u8 guest OSes reported I/O error during Controller Firmware
Upgrade on ESX35U5 with Qlogic HBA. Permanent restriction.
Workaround: Perform upgrade with no I/O.

18. Solaris guest OS reported I/O error during Controller reset on ESX35U5.
The only recovery method is to rebooting the failed VM host.
Permanent restriction.
New limitations with Storage Manager version 10.70.xx.10 release
(controller firmware 07.70.xx.xx).

1. Storage Manager �Error 1000 - Could not communicate with the

storage...." can occur when actions such as clearing the configuration
on a large system (i.e. 448 drives with a DS5300). The Storage Manager
has a 120 second timeout and retries 2 more times when retrieving
status. Some actions such as this may take 8 minutes or longer.

2. Array Management Window shows 2048 volume copies allowed when only 2047
maximum volume copies can be created. For a given array, at least one
source volume will be present for the volume copy feature; hence, the
actual number of �copy relationships� is one less than the maximum
volume allowed.

3. FDE Drive in �Security Locked� state is reported as �incompatible� state

in the drive profile. The drive can be recovered by importing the
correct lock key.

4. Deselecting product components using keyboard when installing Storage

Manager still installs them. You will have to use mouse for individual
component selection.

New limitations with Storage Manager version 10.60.xx.17 release

(controller firmware 07.60.xx.xx).

1. This version of the Storage Manager installation package includes the

IBM Storage Manager Profiler. This is also referred to as Support
Monitor in some of the IBM publications. The following system
restrictions apply:

Note: Do not use laptops or I/O-attached hosts for installing the IBM
Storage Manager Profiler unless these items fulfill all of the
following requirements.

1. Minimum 1GB memory, 1.5 GB preferred

2. Minimum 1GB hard drive space, 1.5 GB preferred
3. On average 15 to 20 minutes installation duration
4. Static IP address required
5. The Storage Manager Profiler is installed by default with
the IBM DS Storage Manager Install Anywhere (SMIA) package with the
Typical (Full Installation) selection. To not install the Storage
Manager Profiler, select Custom then deselect Support Monitor.
6. A pre-existing MySQL database on the host must be manually uninstalled
before you can install the Storage Manager Profiler.
7. The Storage Manager Profiler installation includes the Apache Tomcat
webserver application. Any other pre-existing applications that use
Apache Tomcat must be uninstalled before you install the Storage
Manager Profiler.
8. Make sure the Storage Manager Profiler directory structure is removed
from antivirus and backup applications.
9. MS Internet Explorer and Mozilla Firefox are the only two Web browsers
supported with the Storage Manager Profiler client application.
10. By default, the Storage Manager Profiler polls all storage subsystems
for storage subsystem support data every day at 2:00am. Ensure that
there is not heavy usage of the storage subsystem during this time
period.

This collection time schedule can be modified to start during the

 window that the storage subsystem has light usage by pointing your
Web browser at http://localhost:9000/ and click on the Calendar
icon to schedule the data collection frequencies and time.
11. The Storage Manager Profiler typically takes five minutes to seven
minutes to collect data, but the time can increase for larger
configurations. There have been exceptional instances where storage
arrays took up to 20 minutes to capture the data when capturing the
drive information.
12. If you have a large system, gathering support data takes longer, and
the compressed files are larger. The Storage Manager Profiler
compresses the collection data file to be between 2 MB and 5 MB.
13. Monitor each storage subsystem from one Storage Manager Profiler
instance. Gathering data from a storage subsystem with multiple
Storage Manager Profiler instances can cause problems. No
mechanisms exist that prevent multiple Storage Manager Profiler
instances from trying to find data from the same storage subsystem.
14. When multiple Storage Manager instances are installed in the
environment, do not define the same storage subsystem twice in the
Storage Manager Enterprise Management window.
15. The data collection process of the Storage Manager Profiler is multi-
threaded with a polling mechanism in place to find the maximum
number of storage subsystems at pre-defined timing intervals. The
polling mechanism is not sequential. For example, if the upper
limit on the number of storage subsystems from which the Storage
Manager Profiler can find data is 20, and 60 storage subsystems are
defined, 20 threads are gathered immediately, while the data from
the remaining 40 storage subsystems are gathered as resources
became available. The Storage Manager Profiler supports at least 10
storage subsystems.
16. The Storage Manager Profiler does not support in-band management of
storage subsystems.
17. The only function that the Storage Manager Profiler supports is the
Support Monitor.
18. A minimum of 06.19.xx.xx controller firmware is required to use the
Storage Manager Profiler.

2. The online help of the Command Line Interface commands (SMcli commands)
incorrectly showed the parameters of certain SMcli commands. The
parameters that were shown incorrectly belong to the "disk" type
parameter such as Drive, Drivechannels, DiskDrives, repositoryDrives ...
These parameters were incorrectly shown with the additional word "disk"
such as diskDrive, DiskDriveChannels, repositoryDiskDrive ... The SMcli
command syntax checking engine will display the correct syntax for these
parameters. Make the modifications as suggested by the SMcli command
syntax checking engine. One can also refer to the pdf copy of the
Command Line Interface and Script Commands Programming Guide - IBM
System Storage DS4200, DS4700, and DS5000 in the IBM DS support web site
for help on the SMcli command syntax.

3. The suggested recovery path in the mis-wired guru event might send the
user down either the wrong path or very long path when trying to fix the
first mis-wired port. The work-around is to use the cabling diagram in
the EXP5060 Installation, User's and Maintenance guide or the DS5100 and
DS5300 Installation, User's and Maintenance guide publications to fix
the cabling mis-wired error. The pdf version of these pubs are available
in the IBM DS support web site.

New limitations with Storage Manager version 10.60.xx.11 release

(controller firmware 07.60.xx.xx).

1. If port 1 of the iSCSI host interface is disconnected when the iSCSI

configuration window is first opened, the status of port 1 shows as
connected. If you switch to port 2 and back to port 1, the status will
refresh and port 1 will show as disconnected.

2. When modifying the iSCSI host port attributes there can be a delay of up
to 3 minutes if the port is inactive. If possible, connect a cable
between the iSCSI host port and a switch prior to configuring any
parameters.

3. When applying the Premium feature keys to enable the 64 or 112 drive
attachment to the DS5020 subsystem, the "drive slot limit" premium
feature entry in the Premium Features and Feature Pack Information
window will not be updated to reflect the maximum number of drives that
can be attached to the subsystem (either 64 or 112). In addition, when
trying to attach more drives than the DS5020 is currently allowed, the
"drive slot limit" premium feature entry in the Premium Features and
Feature Pack Information window will be displayed with the "out of
compliance status". To view the maximum number of drives that can be
attached to a DS5020, obtain the Storage Subsystem profile and search
for the following info.

Drive Limit Management:

Number of drive slots discovered: 32
Number of drive slots allowed: 112

Note: The controllers use the discovered drive slot in the subsystem
configuration number to determine whether the maximum number of drives
limit is exceed or not instead of the actual number of drives
installed. For example, if there are two drive expansion enclosures
attached to the DS5020, the number of discovered drive slot will be 42
which is exceeding the limit of 32 that the DS5020 supported as
standard feature even the total number of installed drives actually
installed in the subsystem is 32 or less. In this case, the drive slot
limit will be shown with the status Out-of-Compliance until the DS5020
33-64 drive attach premium feature key is applied.
(XB014946)

4. The Configure iSCSI host port window always displayed the iSCSI host port
number with respect to the installed iSCSI port in the subsystem only.
It does not take into account of other types of host port installed in
the subsystem. Its port counting starts with the first discovered iSCSI
port in the subsystem instead of the first host port installed in the
subsystem per controller host port scanning order. For example, the
DS5020 controller with iSCSI port option will have the port labeled as
ports 1 and 2 per controller in the Configure iSCSI host port window
instead of as ports 3 and 4 because there are two FC ports installed in
the controller boards. However, the MEL entries will refer to the iSCSI
posts as ports 3 and 4 instead of as ports 1 and 2 as referred to in
the Configure iSCSI host port window. Similarly, in the DS5100 and
DS5300 subsystems, the iSCSI host ports in HIC slot 2 will be referred
to as ports 1 and 2 in the Configure iSCSI host port window and ports 5
and 6 in the MEL if the FC host card is installed in HIC slot 1.
(XB014900)

5. The Premium Feature activation confirmation window for Drive Security (FDE)
feature activation key will show the feature as "Unknown capacity".
 Click Ok to confirm that you want to go ahead with the enablement of
the Drive Security (FDE) feature.

6. When doing a Refresh DHCP operation in the Configure iSCSI port window,
and the iSCSI port is unable to contact the DHCP server, the following
inconsistent informational Mel events can be reported;
- MEL 1810 DHCP failure
- MEL 1807 IP address failure
- MEL 1811 DHCP success.
For this error to occur, the following specific conditions and sequence
must have been met:
- Before enabling DHCP, static addressing was used on the port and that
static address is still valid on the network.
- The port was able to contact the DCHP server and acquire an address.
- Contact with the DHCP server is lost.
- The user performs the Refresh DHCP operation from DS Storage Manager
Client.
- Contact with the DHCP server does not come back during the DHCP refresh
operation and timeouts.
Check the network connection to your iSCSI port and the status of the DHCP
server before attempting the Refresh DHCP operation again.

New limitations with Storage Manager Upgrade Utility package version

10.60.xx.05 release (controller firmware 07.60.xx.xx).

1. none

New limitations with Storage Manager Upgrade Utility package version

10.50.xx.23 release (controller firmware 07.50.xx.xx).

1. The Storage Manager on-line help contains inaccurate information about

locking Encryption Capable drives. The current on-line help states "Use
this command to set the new security key to lock all of the Encryption
capable drives." The on-line help text should state " Use this command
to set the security key that is used throughout the storage subsystem
to implement the Disk Encryption premium feature. When any security-
capable drive in the storage subsystem is assigned to a secured array,
that drive will be security-enabled using the security key."

2. The Storage Manager Re-key operations can fail when there are Encryption
Capable drives present in the system that are spun down. When drives are
marked for export in a storage subsystem the drives are spun down.
Attempting to generate a lock key with spun down drives will fail. Remove
the exported drives from the subsystem and retry the operation.

3. When using the SMcli to create an Encryption drive security key, the SMcli
command will not save the security key in a default location and a
separate location at the same time. The new security key is saved in
the location the SMcli was executed from if the command does not
include a file location with a fully qualified path.

4. The Storage Manager Controller Firmware upgrade status message can be

misleading. The Storage Manager Controller Firmware upgrade screen will
report a controller is running an unsupported firmware version if the
subsystem is unresponsive at the time of the upgrade.

New limitations with Storage Manager Upgrade Utility package version

10.50.xx.19 release (controller firmware 07.50.xx.xx).
1. The DS Storage Manager version 10.50.xx.19 will not manage
DS4000 Storage Subsystems with Controller firmware levels
prior to v5.40.xx.xx.

2. Start of day (a controller reboot) can take a very long time, up to

20 minutes, after a subsystem clear configuration on a DS5000
subsystem. This occurs on very large configurations, now that the
DS5000 can support up to 448 drives, and can be exacerbated if there
are SATA drives.

3. Veritas cluster server node failure when fast fail is enabled.

Recommend setting dmp_fast_fail HBA flag to OFF. Frequency of this
causing a node failure is low unless the storage subsystem is
experiencing repeated controller failover conditions.

4. Brocade HBA does not support direct attach to storage subsystem.

5. At times the link is not restored when inserting a drive side cable
into a DS5000 controller, a data rate mismatch occurs. Try reseating
the cable again to clear the condition.

6. Due to a timing issue with controller firmware, using SMcli or the

script engine to create LUNs and set LUN attributes will sometimes
end with a script error.

7. Mapping host port identifiers to host via Script Editor hangs; fails
via CLI with "... error code 1�. This will occur when using the
CLI/script engine to create an initial host port mapping.

8. Under certain high stress conditions controller firmware upgrade will

fail when volumes do not get transferred to the alternate controller
quick enough. Upgrade controller firmware during maintenance windows
or under low stress IO conditions.

New limitations with Storage Manager Upgrade Utility package version

10.36.xx.13 release (controller firmware 07.36.xx.xx).

1. None

New limitations with Storage Manager Upgrade Utility package version

10.36.xx.07b release (controller firmware 07.36.xx.xx).

1. Upgrade of DS4000 to 7.xx.xx.xx using the upgrade tool with non-English

OSes will end with an error. The current firmware column still shows
the previous version, pending version will show 7.xx.xx.xx, instead of
'none'.

Checking the upgrade tool log you will find:

[12.11.2008 08:51:16] [rey-ds4700-1] [SUPPORT_SERVICES]
[DownloadAndActivate] activation failed

There are two ways to check the content of this log:

1. As long as the upgrade tool is still open: Use the 'View log' button
2. If the upgrade tool was closed already:

For windows all logs can be found in this folder:

C:\Program Files\IBM_DS4000FirmwareUpgrade\client
 For other operating systems, check in the appropriate folder.

Syntax of the name is similar to 20081114_1501.log.

Then check the profile.

Here the new firmware can be found as pending:

Current configuration:
Firmware version: 06.60.17.00
NVSRAM version: N1814D470R916V17.dlp

Pending configuration:
Staged firmware download supported: Yes
Firmware version: 07.36.12.00
NVSRAM version: N1814D47R1036V12.dlp

This shows that firmware was loaded to controller but not yet
activated.

Workaround:

After checking the items listed in Details section, activate the

loaded firmware using this script command:
activate storageSubsystem firmware;

Mark the affected system in the Enterprise Management window of the

Storage Manager.

In the menu, go to Tools -> Execute script. A new window will show
up. Paste the command in the upper part of this window and choose
Tools -> Execute only.

The activation will take a while and the controller will reboot.

New limitations with Storage Manager Installer (SMIA) package version

10.36.xx.07 release.

1. With Windows Vista and Windows Server 2008, when you try to write a
file using the SMcli command, the command reports that the file has
been written, but the file was not written. The SMcli should issue an
error code or a statement that the file was not written to the disk.
Disable the Use User Account Control (UAC) option, or start the DOS
prompt in an administrator mode, which gives you permission to write
to the disk. Try to write the file again.

New limitations with Storage Manager Installer (SMIA) package version

10.30.xx.09 release.

1. Using VDS/VSS utilities (diskraid and diskpart) to create and map

volumes may not immediately see the LUNs listed on the host due to
PnP taking time to scan for the devices. Wait for the devices to
show up in device manager prior to using diskpart.

2. When writing an SMcli command file, the command reports that the file
is written, but you cannot find the file. User Account Control is
enabled on the host, and it does not allow you to modify any files on
the hard drive without permission. Disable this control, and rerun the
 SMcli command.

3. If you use a storage array as a boot device for the Windows Server 2003
operating system, you cannot use the hibernation feature.

New limitations with Storage Manager Installer (SMIA) package version

10.15.xx.08 release.

1. Reconfiguration operation (DRM) is delayed under some circumstances.

When a drive fails before the DRM completes, it can take up to eight
times as long for the DRM to complete. DRM reconfigurations to RAID 6
have the longest impact since there are four times as many calculations
and writes that have to occur compared to other RAID levels.

2. Host Software display of controller current rate is wrong below 4Gbps.

Host Software Client - AMW - Logical/Physical View - Controller
Properties - Host Interfaces - Current rate is displaying "Not
Available" when the controller negotiated speed is 2Gbps. When the
controller negotiated speed is reduced to 1GBs, the Current rate
displays "2Gbps"

New limitations with Storage Manager Installer (SMIA) package version

10.10.xx.xx release (controller firmware 07.10.xx.xx).

1. Controller Alarm Bell icon does not appear as a flashing icon

indicator on the screen to get the user's attention but the icon
does change appearances.

2. Miswire of drive tray cabling with DS4700 and DS4200 can cause
continuous reboot of a controller. To correct this situation, power
down the subsystem, cable the drive trays correctly, and power the
subsystem back up.

3. Controller button may appeared enabled and mislead the user that
a controller is selected where in fact, a controller was not
highlighted for the button to appear ready.

4. Search key is not marked correctly in that page due a JavaHelp

Bug with JavaHelp 2.0_01. A search for keyword "profile" ended
with phase "prese 'nting p' rofile" being marked.

5. storageArrayProfile.txt should be renamed as storageSubsystemProfile.txt

in Support Data.

6. Bullets Incorrectly Placed in Volume Modification Help Page

7. Unable to Escape out of Help Display. User will be required to

close the window by using window close procedure (exit, etc.)

8. Bullets and Descriptions not aligned into same line in "Viewing

mirror properties".

9. The Help window is not getting refreshed properly when using the
AMW.Help window. Workaround is to close and reopen Storage Manager
client.

10. CLI command failure for creation of volume(s) if capacity parameter

syntax is not specified. A space will need to be used between the
integer value and the units used in the capacity option of this
 command or, "create volume volumeGroup[4] capacity=15 GB�".

11. Customer will see high ITW counts displayed in GUI (RLS feature)
and logs (files) for diagnostics (support bundle, DDC, etc.) and
may be concerned that he has a problem. This will not cause a
Critical MEL event. Known problem previously restricted, when a
DS4700 or DS4200 controller reboots, these counters increment.

12. Single tray powercycle during IO activity causes drives in tray to become
failed. Customer may see loss of drive (failed) due to timing issue
of drive detection & spin-up of the drive. There are one of two
conditions that result on power-up:
- (Most likely) Drive will be marked as optimal/missing with
the piece failed, or
- (rarely) Drive will be marked as failed with the piece
failed.
Workaround is to unfail (revive) drive which restarts reconstruction
of all pieces.

13. Event log critical Event 6402 was reported after creating 64 mirror
relations. Eventually, the mirror state transitions to synchronizing
and proceeds to completion on mirror creation. Workaround is to
ignore the MEL logging since this occurs on creation of mirror volumes.

14. Reconfiguration operations during host IO may result in IO errors when

arrays contain more than 32 LUNs. These operations include Dynamic
Capacity Expansion, Defragmentation, Dynamic Volume Expansion, Dynamic
RAID Migration. The workaround is to quiesce host IO activity during
reconfiguration.

15. Heavy IO to a narrow volume group of SATA drives can result in host IO
timeouts. A narrow volume group refers to an array built of very few
drives; namely 1 drive RAID 0, 1x1 RAID 1, and 2 + 1 RAID 5. The
workaround is to build arrays of SATA drives out of 4 + 1 or greater.

16. When managing the storage subsystem in-band, the upgrade utility will
show the upgrade as failed. This is because of the update and reboot
of the controllers when activating the new firmware. SMagent is not
dynamic and will need to be restarted to reconnect to the storage
subsystem.

17. Selecting and dragging text within the storage profile window causes the
window to be continuously refreshed. Work around is to select and copy,
do not drag the text.

18. When configuring alerts through the task assistant, the option stays open
after selecting OK. The window only closes when the cancel button is
selected.

19. The Performance Monitor displays error messages when the storage
subsystem is experiencing exception conditions. The performance
monitor has a lower execution priority within the controller firmware
than responding to system IO and can experience internal timeouts
under these conditions.

20. Critical MEL event (6402 - Data on mirrored pair unsynchronized) can
occur under certain circumstances with synchronous RVM. The most
likely scenario is when both primary and secondary are on a remote
mirror and an error occurs with access to that host. Resynchronization
 should occur automatically, when automatic resynchronization is
selected for a mirror relationship. However if any of the host sites
should go down during this interval, recovery by the user is required.

21. A persistent miswire condition is erroneously reported through the

recovery guru even though the subsystem is properly wired. The
frequency of occurrence is low and is associated with an ESM firmware
download or other reboot of the ESM. The ESM that is reporting the
problem must be reseated to eliminate the false reporting. Not all
miswire conditions are erroneous and must be evaluated to determine
the nature of the error.

22. Drive path loss of redundancy has been reported during ESM download.
This occurs when a drive port is bypassed. In some instances this is
persistent until the drive is reconstructed. In other cases it can be
recovered through an ESM reboot (second ESM download, ESM pull and
replace).

23. Unexpected drive states have been observed during power cycle testing
due to internal controller firmware contention when flushing MEL
events to disk. The drives have been observed as reconstructing or
replaced when they should have been reported as failed. Also volume
groups have been reported degraded when all drives were assigned and
optimal. An indication that this is the situation would be when drive
reconstruction has not completed in the expected amount of time and
does not appear to be making any progress. The work around is to
reboot the controller owning the volume where the reconstruction has
stalled.

24. Sometimes when an ESM is inserted a drive's fault line is asserted

briefly. The fault line almost immediately returns to inactive, but
the ESMs may bypass the drive. In these circumstances, the
administrator will have to reconstruct the failed drive.

25. After a drive fail, a manually initiated copyback to a global hot

spare may also fail. The work around is to remove the failed drive and
reinsert it, then the copyback should resume and complete
successfully.

26. When an erronieous miswire condition occurs (as mentioned above in 21),
the recovery guru reports the miswire on one controller but not on the
other. In this situation, ignore the other controller and use the
information supplied by the controller reporting the problem.

27. Occasionally a controller firmware upgrade to 07.10 will unexpectedly

reboot a controller an extra time. This could generate a diagnostic
data capture, however the firmware upgrade is always successful.

28. When managing previous releases of firmware (06.19 and prior), "working"
gets displayed as "worki" during volume creation.

29. The Performance Monitor error window does not come to the front. You
must minimize all other foreground windows to get to the error popup
window.

30. When a disk array is in a degraded state, the array will report "needs
attention" to both the EMW and the AMW. After taking appropriate
corrective action, the AMW view of the array will report "fixing" but
the EMW state remains at "needs attention". Both statuses are valid,
 when the fault state is resolved both views will change to "optimal".

31. Storage subsystem loses in-band connectivity during volume creation.

This is caused by the controller logout to all hosts that are in the
default host group when those hosts have QLogic HBAs which is not
tolerant of the controller initiated logout. The work around is to
first create the host group and host port mappings prior to creation
of volumes. Then on volume creation avoid using the default host
group.

32. When defining additional LUN mappings to a host, the volume name moves
down to the bottom of the visible list making it difficult to keep
track of the list.

33. A Windows server will experience a Blue Screen and will need to be
rebooted when one or more controllers go offline in a storage
subsystem. A LUN/path may be in the process of being removed because
an HBA has not reestablished a login with the controller and the PnP
process will remove all LUNs associated with that path. The timing of
this should not be seen unless the customer is experiencing major
problems with controllers going into offline states.

34. With SMProvider installed, the disk management on the server does not
complete within 1 hour for a configuration of 20 or more storage
subsystems attached on the subnet. This is an issue with the auto-
discovery of storage IP addresses by the SMProvider that supports the
VDS/VSS feature of Windows. On installation of the SMProvider, add
all of the IP addresses for the storage subsystems into the registry.
On reboot, the registry contains the list of IP addresses and avoids
the auto-discovery delay. The registry location is:
HKEY_LOCAL_MACHINE\SOFTWARE\Storage\SMprovider /v IpAddresses /t REG_SZ /d
If the value is empty, the providers will use the auto-discovery method.

35. Result of an installation not completing normally because of a crash,

blue screen, or other interruption will prevent the SMclient from
being able to uninstall. This is because the InstallAnywhere program
writes to the ZeroG registry file at the very end of the installation
process. Reinstall the package to overwrite the installation and
populate the ZeroG registry.

36. Using ALT-Q to access the QLogic HBA BIOS will hang the host, use CTL-Q
instead.

37. Intermittently the flashcopy utility using the VSS provider fails to
create persistent flashcopies. The flashcopy volume is created at the
storage subsystem and the volume mappings complete successfully, but
after about one minute the vshadow utility removes the volume because
Microsoft's PnP driver does not detect the flashcopy volume in time.
If a flashcopy failure has occurred, or the limit on flashcopies has
been reached, remove any unnecessary flashcopies on the storage
subsystem and retry the failed flashcopy request.
Please note that some utilities such as NetBackup do not
automatically clean up the failed request by removing these failed
flashcopies from the storage array.

38. Startup of MS DISKRAID utility executing through VDS occasionally

reports an error. The following message is reported:
"Diskraid encountered a fatal error while initializing. The
following information may help diagnose the error:
 Error: 0x80080005
Location Code: 2"
The server must be rebooted to recover, shutdown and restart of the
VSS/VDS service does not fix the problem.

39. Configuring separate Email alerts when two Enterprise management

windows are open on the same host will cause the alerts to disappear
if one of the Enterprise windows is shut down and then restarted. It
is recommended that if multiple Enterprise management windows needs to
be open, that they are open on separate Hosts which will indeed allow
the configuration of alerts to be saved if one of the enterprise
management windows is shut down and restarted.

40. DVE (Dynamic Volume expansion) is not possible on a volume which is in

an active mirror relationship and which write-mode is 'Asynchronous
not write-consistent'.The DVE is not possible on either the primary or
the secondary volume. The DVE is possible, if the write-mode is
'Synchronous' or 'Asynchronous write-consistent'. The DVE is also not
possible on a FlashCopy Repository of the secondary volume. The
attribute of the write-mode on the primary volume which is mirrored to
the secondary, is given to the FlashCopy Repository Volume of the
secondary's FlashCopy Volume. A workaround is to set the write-mode of
the mirrored primary volume from 'Asynchronous not write-consistent',
to 'Asynchronous write-consistent' or 'Synchronous', to run DVE and
when DVE is finished to re-set the write-mode to 'Asynchronous not
write-consistent'.

Legacy restrictions that are still applicable:

1. Reflected Fibre Channel (FC) OPN frames occurs when intermixing the
EXP810, EXP710 and EXP100s behind DS4700 or DS4800 storage subsystems.
This behavior causes excessive drive side timeout, drive side link down
and drive side link up events be posted in the DS4000 storage subsystem
Event log (MEL.) It might also cause drives to be by-passed or failed by
the controller. NEW DRIVE SIDE FC CABLING REQUIREMENT MUST BE ADHERED TO
WHEN HAVING EXP100 CONNECTED TO THE DS4700 OR DS4800 STORAGE SUBSYSTEMS.
Please refer to the latest version of the Installation, User's and
Maintenance Guide for these storage subsystems that are posted in the
IBM
DS4000 Support web site for more information.
http://www.ibm.com/systems/support/storage/disk

2. Can not increase the capacity of RAID arrays.

RAID arrays with certain combinations of selected segment size and
number of drives that made up the arrays will exceed the available
working space in controller dacstore, causing a reconfiguration request
(like expanding the capacity of the array) to be denied. These
combinations are generally the largest segment size (512KB) with the
number of drives in the array is 15 drives or more. There is no
work-around. C324144 105008

3. Interoperability problem between the Tachyon DX2 chip in the DS4500 and
the DS4300 storage subsystem controllers and the Emulex SOC 422 chip in
the EXP810 expansion enclosure ESMs causing up to 5 Fibre Channel loop
type errors to be posted in the DS4000 storage subsystem Major Event Log
during a 24 hour period. There is a small window in the SOC 422 chip
that multiple devices can be opened at one time. This ultimately leads
to Fibre Channel loop errors of Fibre Channel link up/down, Drive
 returned CHECK CONDITION, and Timeout on drive side of controller. IBM
recommends the use of the Read-Link-Status function to monitor drive loop
for any problems in the drive loop/channel. There is no work-around.

4. The single digit of the Enclosure IDs for all enclosures (including the
DS4000 storage subsystem with internal drive slots) in a given redundant
drive loop/channel pair must be unique. For example, with four
enclosures attached to the DS4300, the correct enclosure ID settings
should be x1, x2, x3, and x4 (where x can be any digit that can be set).
Examples of incorrect settings would be 11, 21, 31, and 41 or 12, 22,
32, and 62. These examples are incorrect because the x1 digits are the
same in all enclosure IDs (either 1 or 2).

If you do not set the single digit of the enclosure IDs to be unique
among enclosures in a redundant drive loop/channel pair, then drive
loop/channel errors might be randomly posted in the DS4000 subsystem
Major Event Log (MEL), especially in the cases where the DS4300 storage
subsystems are connected to EXP810s and EXP100s. In addition, enclosure
IDs with same single digits in a redundant drive loop/channel pair will
cause the DS4000 subsystem controller to assign a soft AL_PA address to
devices in the redundant drive loop/channel pair. The problem with soft
AL_PA addressing is that AL_PA address assignment can change between
LIPs. This possibility increases the difficulty of troubleshooting drive
loop problems because it is difficult to ascertain whether the same
device with a different address or a different device might be causing a
problem.

5. In DS4000 storage subsystem configurations with controller firmware

6.15.2x.xx and higher installed, the performance of write intense
workloads such as sequential Tape restores to DS4000 Logical drives with
large I/O request sizes (e.g. 256kB) is degraded if the DS4000 logical
drives are created with small segment sizes such as 8KB or 16KB. The
work around is to create the DS4000 logical drives with segment size of
64KB or higher.

6. Do not pull or insert drives during the drive firmware download.

In addition, ALL I/Os must also be stopped during the drive firmware
download. Otherwise, drives may be shown as missing, unavailable or
failed.

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

8. For Microsoft Windows Server 2003 R2 operating systems. When loading the
Microsoft Hot fix KB916048, required in installing Storage Manager, if
the IBM xSeries Server hangs during reboot it may be resolved by using
the latest Broadcom driver for the Bcom HT1000.

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

1.3 Enhancements
-----------------

The DS Storage Manager version 10.77.xx.16 host software in conjunction

 with controller firmware version 7.77.18.xx and higher provides support
for

- Support for SAS drives with T10PI capability in the DS5020, DS3950,
DS5100 and DS5300 storage subsystems.

- Support the new IBM DS storage subsystem DCS3700.

- Support for the DS3524 storage subsystem with DC power supplies.

- Support for the new 1TB NL SAS drive options for the DS3500 storage
subsystems.

- Support for DS3500 subsystem enhanced capabilities. Please refer to the

DS3500 Installation, User's and Maintenance guide or the DS3500
announcement letter for more information.

- Starting with this release, the Microsoft multipath driver MPIO DSM
will be packaged separately from the SMIA bundle that includes the
SMClient, SMUtil and SMAgent. You must install the Microsoft multipath
driver MPIO DSM (SMMPIO) on servers that are IO attached to the
DS storage subsystems.

- When opening the Subsystem Management Window user is asked to set

a password.
+ User can select No to not setting the storage subsystem management
Password
+ If user selects yes, the password can be weak or strong.
If no password is selected, or a weak password is set, then a message
appears recommending a strong password each time the Subsystem
Management Window is opened.

- Host type VMWARE has been added to NVSRAM as an additional host type.
+ The DS4200 and DS4700 will use index 21
+ All other supported systems will use index 16 instead.
Although not required, if using a Linux host type for a VMWARE host, it
is recommended to move to the VMWARE host type since any upgrading of
controller firmware and NVSRAM would continue to require running scripts,
whereas using the VMWARE host type does not require running scripts.

Please refer to the New Features section of the IBM System Storage
DS Storage Manager Version 10 Installation and Host Support Guide
for additional information about the IBM DS Storage Manager version
10 enhancements.

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

1.4 Level Recommendation and Prerequisites for the update

-----------------------------------------------------------

Note: The IBM Storage Manager host software version 10.77 for Microsoft
Windows operating systems, new features and changes are described
in the corresponding Change History document. Please refer to this
document for more information on new features and modifications.

Microsoft Windows NT4 SP6 and Windows 2000 SP4 operating systems are not
supported for this release of IBM DS Storage Manager version
10.77.xx.xx. The only supported Microsoft operating systems are the x86,
 x64 and IA64 editions of Windows Server 2003 with SP2, the x86 and x64
editions of Windows Server 2008, Windows Vista (English only) 32bit,
and Windows 7 (English only).

For the 32bit Windows Vista, Server 2003 (X86), or Server 2008 (x86)
editions, IBM xSeries and other Intel-based servers with minimum 1024MB
Memory with at least 512KB L2 Cache Pentium III 1Ghz processor(s) is
recommended.

For the Intel Itanium II 64bit Microsoft Windows Server 2003 edition, IBM
xSeries and other Intel-based servers with minimum 1024MB Memory with
Intel Itanium II processor(s) is recommended.

For the X64 64bit (AMD64 and EM64T) Microsoft Windows Server 2003 and
Microsoft Windows Server 2008 edition, IBM xSeries and other servers
with minimum 2048MB Memory with Intel EM64T or AMD AMD64 processor(s) is
recommended.

(also see Dependencies section)

Client Code levels at time of release are as follows

---------------------------------------------------------

Important:
1. This release of IBM DS Storage Manager host software Client
supports managing all DS4000/DS500 storage subsystems with general
released firmware versions from 06.xx.xx.xx up to 07.77.xx.xx.

2. There are three separate IBM DS Storage Manager host software

version 10.77 packages for the following Microsoft Windows OSes -
Windows 7, Windows Vista (English only) 32bit, Windows Server 2003
Intel Architecture (x86), and Windows Server 2008 (x86); Windows
Server 2003 Intel Architecture Itanium II 64bit (IA-64); Windows
Server 2003 (x64); Windows Server 2008 (x64) and Windows Server 2008
R2. Please download the correct one for your operating system
environment.

3. Beginning with storage manager version 10.75.xx.xx, the Microsoft

Windows multipath driver - MPIO/DSM - is provided in a separate
installer package.

Operating Systems support Packs:

- Windows Server 2008: SP2. R2
- Windows Server 2003: SP2, R1, R2
- Windows Vista (Supports English OS only)
- Windows 7 (English only)

=============================================================================
For Microsoft Windows Server 2003 x86 (32bit), Server 2008 x86
only:

Starting with the DS4000 storage manager version 9.12, all of the host-
software packages are included in a single host-software installer
wizard. During the execution of the wizard, the user will have a choice
to install all or only certain software packages depending the need for
a given server. The version of the host software installer wizard for
 this release is SMIA-WS32-10.77.35.16.exe. This wizard will install the
following version of the host-software packages:

1. IBM DS Storage Manager Client version: 10.77.G5.16

2. IBM DS Storage Manager Agent version: 10.01.35.07
3. IBM DS Storage Manager Utilities version: 10.00.35.15
4. IBM DS Storage Manager ESM version: 10.77.G5.03
5. IBM DS Storage Manager Profiler (Support monitor) version:
04.96.G5.01

Attention:
Starting with Storage Manager version 10.77, the multipath driver DSM
MPIO (or MPIO DSM) will not be part of the SMIA installer. It is
packaged in a separate installer - SMIA-WS32-01.03.0305.0504.exe. You
must run this installer to install the multipath driver DSM MPIO in
the servers that are IO attached to the DS storage subsystems.
- IBM DS Storage Manager MPIO/DSM version: 01.03.0305.0504
Note: The MPIO/DSM multipath driver is supported with controller
firmware version 06.12.xx.xx or higher.
For Window Server 2003 and Windows Server 2008,
install the latest STORport driver with the MPIO/DSM
multipath driver.

For Windows Vista, XP, and Windows 7 (English only) 32bit (IA32/X86) only:

The version of the host software installer wizard for

this release is SMIA-WS32-10.77.35.16.exe. This wizard will
install the following version of the host-software packages:

1. IBM DS Storage Manager Client version: 10.77.G5.16

2. IBM DS Storage Manager Profiler (Support monitor) version:
04.96.G5.01

=========================================================================
For Microsoft Windows Server 2008 x64, Microsoft Windows Server 2003X64
64bit (AMD64 and EM64T), and Windows Server 2008 SP2 R2 with HyperV
Clustering edition only:

Starting with the DS4000 storage manager version 9.12, all of the host-
software packages are included in a single host-software installer
wizard. During the execution of the wizard, the user will have a choice
to install all or only certain software packages depending the need for
a given server. The version of the host software installer wizard for
this release is SMIA-WSX64-10.77.35.16.exe. This wizard will install the
following version of the host-software packages:

1. IBM DS Storage Manager Client version: 10.77.G5.16

2. IBM DS Storage Manager Agent version: 10.01.35.07
3. IBM DS Storage Manager Utilities version: 10.00.35.15
4. IBM DS Storage Manager ESM version: 10.77.G5.03
5. IBM DS Storage Manager Profiler (Support monitor) version:
04.96.G5.01

Attention:
Starting with Storage Manager version 10.77, the multipath driver DSM
MPIO (or MPIO DSM) will not be part of the SMIA installer. It is
packaged in a separate installer - SMIA-WSX64-01.03.0305.0504.exe. You
 must run this installer to install the multipath driver DSM MPIO in
the servers that are IO attached to the DS storage subsystems.
- IBM DS Storage Manager MPIO/DSM version: 01.03.0305.0504
Note: The MPIO/DSM multipath driver is supported with controller
firmware version 06.12.xx.xx or higher.
For Window Server 2003 and Windows Server 2008,
install the latest STORport driver with the MPIO/DSM
multipath driver.

=========================================================================
For Microsoft Windows Server 2003 Intel Itanium II 64bit (IA64) edition
only:

Starting with the DS4000 storage manager version 9.12, all of the host-
software packages are included in a single host-software installer
wizard. During the execution of the wizard, the user will have a choice
to install all or only certain software packages depending the need for
a given server. The version of the host software installer wizard for
this release is SMIA-WS64-10.77.35.16.exe. This wizard will install the
following version of the host-software packages:

1. IBM DS Storage Manager Client version: 10.77.G5.16

2. IBM DS Storage Manager Agent version: 10.01.35.07
3. IBM DS Storage Manager Utilities version: 10.00.35.15
4. IBM DS Storage Manager ESM version: 10.77.G5.03
5. IBM DS Storage Manager Profiler (Support monitor) version:
04.96.G5.01

Attention:
Starting with Storage Manager version 10.77, the multipath driver DSM
MPIO (or MPIO DSM) will not be part of the SMIA installer. It is
packaged in a separate installer - SMIA-WS64-01.03.0305.0504.exe. You
must run this installer to install the multipath driver DSM MPIO in
the servers that are IO attached to the DS storage subsystems.
- IBM DS Storage Manager MPIO/DSM version: 01.03.0305.0504
Note: The MPIO/DSM multipath driver is supported with controller
firmware version 06.12.xx.xx or higher.
For Window Server 2003 and Windows Server 2008,
install the latest STORport driver with the MPIO/DSM
multipath driver.

Refer to the http://www.ibm.com/systems/support/storage/disk

IBM System Storage� Disk Storage Systems Technical Support web site for
the latest released code levels.

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

1.5 Dependencies
-----------------

ATTENTION:

1. CURRENTLY, THE ONLY DS4000 STORAGE SUBSYSTEMS THAT ARE SUPPORTED BY

THE 06.12.XX.XX CONTROLLER FIRMWARE VERSION ARE THE DS4100 - ALL
MODELS, THE DS4300 WITH STANDARD (DUAL CONTROLLER) OR TURBO OPTIONS,
THE DS4400 AND THE DS4500. DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON
 ANY OTHER DS4000 STORAGE SUBSYSTEM. THERE IS NOT ANY CHECKING FOR THIS
RESTRICTION INSIDE THE STORAGE MANAGER CLIENT PROGRAM.

2. The only DS4000 storage subsystems that are supported by the

06.14.xx.xx or higher (06.14.xx.xx, 06.15.xx.xx, 06.16.xx.xx,
06.19.xx.xx or 6.23.xx.xx) controller firmware version are the DS4200
(06.16.88.xx or higher), DS4300 Standard-dual controller or Turbo
models (06.19.xx.xx or higher), and the DS4500 (06.19.xx.xx or higher),
DS4700 (06.16.4x.xx or higher) and DS4800 (06.14.xx.xx or higher)
storage subsystems. Currently, there are not any controller firmware
packages version 06.14.xx.xx and higher for other DS4000 storage
subsystems. Do not download this controller firmware on any other
DS4000 storage subsystems.

3. Always check the README files (especially the Dependencies section)

that are packaged together with the firmware files for any required
minimum firmware level requirements and the firmware download
sequence for the DS4000 drive expansion enclosure ESM, the DS4000
storage subsystem controller and the hard drive firmware.

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

5. The DS4700 and DS4800 storage subsystems do not support the attachment
of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure
must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700
Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be
attached to the DS4700 and DS4800 storage subsystems.

6. The version 06.16.xx.xx of the DS4700 or DS4800 controller firmware

is not compatible with the EXP100 SATA drive expansion enclosures. DO
NOT download it into the DS4800 storage subsystems that have EXP100
drive expansion enclosures attached. After the 06.16.xx.xx controller
firmware is activated, the DS4800 storage subsystem will not recognize
the drives in EXP100 enclosures, causing loss of data availability to
the raid arrays and logical drives that are defined in those drives.
IBM recommends installing the controller firmware version 6.23.xx.xx
and higher in the DS4000 storage subsystems that have EXP100 SATA drive
expansion enclosure attached instead.

7. When using STORport miniport version of the Fibre Channel host bus
adapter device driver, Windows Server 2003 service pack 1 must be
installed along with the Microsoft Windows Server 2003 STORport hot-
fix KB916048 - An updated Storport storage driver (version
5.2.3790.2723) is available for Windows Server 2003. The Windows
Server 2003 service pack 1 and the STORport hot-fix 916048 are
available for download at the Microsoft support web site.
 8. The latest version of Microsoft Windows SCSIport and the STORport FC
HBA device drivers do not support the BUSCHANGE=0 parameter. It
requires the DS4000 storage subsystem controller firmware to be
compatible with the MS Plug and Play driver. Not all versions of the
DS4000 storage subsystem controller firmware are compatible with the
Microsoft Plug and Play driver. Currently, only the controller
firmware versions that are listed in the table below for each of the
DS4000 subsystems, which support the SCSIport device drivers with
BUSCHANGE parameter set to Microsoft required default value of 2, are
compatible with the MS Plug-and-Play driver.

------------------------------------------
| DS4000 | Controller Firmware |
| Storage Subsystem | Version Required |
-------------------------------------------
| DS4700 | 06.16.8x.xx or later|
| DS4800 | 06.15.2x.xx |
| | 06.16.8x.xx or later|
| DS4500 | 06.12.27.xx or later|
| DS4400 | 06.12.27.xx or later|
| DS4300 | 06.12.27.xx or later|
| DS4200 | 06.16.88.xx or later|
| DS4100 | 06.12.27.xx or later|
------------------------------------------

Do not use STORport miniport device driver or FAStT/DS4000 FC HBA

SCSIport device driver version 9.1.2.11 and higher in the Microsoft
Windows servers that have IO access to the DS4000 storage subsystems
with controller firmware that are not listed in the controller
firmware table above. Please check with your IBM reseller, IBM
representative, or the DS4000 interoperability matrix for information
on future DS4000 storage subsystems support of this device driver
without BUSCHANGE=0 parameter.

IBM DS Storage Manager version 10.77 host software requires the DS3000
/DS4000/DS5000 storage subsystem controller firmware be at version
06.xx.xx.xx or higher. The IBM DS4000 Storage Manager v9.60 supports
storage subsystems with controller firmware version 04.xx.xx.xx up to
05.2x.xx.xx. The IBM DS Storage Manager v10.36 supports storage
subsystems with controller firmware version 05.3x.xx.xx to 07.36.xx.xx.
The IBM DS Storage Manager v10.70 supports storage subsystems with
controller firmware version 05.4x.xx.xx to 07.70.xx.xx.

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

2.0 Installation and Setup Instructions

-----------------------------------------

Note: The web-download Storage Manager version 10.77 host software package
must be first unpacked (unzipped) into a user-defined directory. Then,
go to this directory, locate the Windows directory to access the
Storage Manager version 10.77 host software installer wizard.

2.1 Step-by-step instructions for this code update are as follows

------------------------------------------------------------------

1. Install and update the device driver for the IBM FAStT, FC-2, FC2-133
single port or dual port, FC 4Gbps PCIx single port or dual port,
or Qlogic 4Gb FC PCIe for IBM System X Fibre Channel Host Bus Adapters.

a. Install the hardware by using the instructions that come with the
adapter.
b. Review section 3.2 in this readme file for the minimum recommended
device driver version for your Fibre Channel Host Bus Adapters.
c. Install the IBM DS4000 Host Adapter device driver by using the
instructions provided in the readme.txt file located in either the
Host_Adapter directory on this installation CD or from the
appropriate driver package that is downloaded from the IBM Support
Web site.

2. If there is previous version 7.x, 8.x or 9.10 of the IBM DS4000

storage manager host software installed in the system, you have to
uninstall it first before installing the new version of the storage
manager host software.

IMPORTANT: For servers with boot LUNs in the DS4000 storage subsystems
(aka. SAN Boot or Root Boot), a special utility in the
RDAC_UninstallUtil_for_BootFromSANConfigurations directory must be run
first before Uninstalling the RDAC, especially in the following server
configuration - W2K server with DS4000 Storage Manager 8.4 RDAC installed.
Please refer to the README in the
RDAC_UninstallUtil_for_BootFromSANConfigurations directory for
instructions on running the utility. NOTE: This utility can also be used
to recover from a failed uninstalling of the RDAC in non-SAN boot
Microsoft Windows environments which resulted in a failed reboot of the
Windows operating system.

For instruction to uninstall the DS4000 storage manager host software,

please refer to the IBM System Storage DS Storage Manager Version 10
Installation and Host Support Guide.

If the previously installed DS4000 storage manager version is of 10 or

later, the DS4000 storage manager host software can be updated with the new
code from the installer without the need of uninstalling the existing
storage manager host software packages first. Just click "Yes" in the
window that the installer displays, stating that there are already
installed DS4000 storage manager host software in the server and whether
you want to update it with the new code.

3. Install the new storage manager host software from the appropriate
CD-ROM directory for your Operating Systems or from the host software
package that you downloaded from the IBM Support Web site. Refer to the
IBM System Storage DS Storage Manager Version 10 Installation and
Host Support Guide for detailed installation instructions.

4. Install the Windows MPIO DSM multipath driver.

Starting with the Storage Manger version 10.75.xx release, the Microsoft
multipath driver MPIO DSM was packaged separately from the SMIA
installer bundle that includes the SMClient, SMUtil and SMAgent. You
must use this package to install the Microsoft multipath driver MPIO DSM
on servers that are IO attached to the DS3500/DS3000 subsystems. To
install, execute the package .exe file and click through the installer
 wizard.

5. Upgrade the DS4000/DS5000 storage subsystem firmware in the following

order -
1. Controller firmware and NVSRAM
2. ESM firmware
3. Drive firmware
Refer to the IBM System Storage DS Storage Manager Version 10
Installation and Host Support Guide or the online help in the Subsystem
Management window for detailed instructions.

ATTENTION: Always check the README files (especially the Dependencies

section) that are packaged together with the firmware files for any
required minimum firmware level requirements and the firmware download
sequence for the DS3000/DS4000/DS5000 drive expansion enclosure ESM, the
DS3000/DS4000/DS5000 storage subsystem controller and the hard drive
firmware.

6. (if applicable) Re-enable the FC/SATA intermix premium feature using

the premium key file.

Refer to the http://www.ibm.com/systems/support/storage/disk IBM System

Storage� Disk Storage Systems Technical Support web site for the the
latest DS Storage Manager host software, the DS4000/DS5000 controllers
firmware, the drive expansion enclosure ESM firmware and the hard disk
drive code.

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

2.2 Refer to the Host_Adapter directory on the installation CD for

the applicable drivers.

Refer to the http://www.ibm.com/systems/support/storage/disk IBM

System Storage� Disk Storage Systems Technical Support web site for the
latest supported host adapters, device drivers, and updated readme.

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

2.3 Helpful Hints

------------------

1. The DS4500 and DS4300 storage subsystem have updated recommended drive-side
cabling instructions. The DS4500 instructions are documented in the IBM
System Storage DS4500 Installation, Users, and Maintenance Guide (GC27-
2051-00 or IBM P/N 42D3302). The DS4300 instructions are documented in the
IBM System Storage DS4300 Installation, Users, and Maintenance Guide
(GC26-7722-02 or IBM P/N 42D3300).

Please follow the cabling instructions in these publication to cable the

new DS4500 and DS4300 setup. If you have an existing DS4500 setup with
four drive side minihub installed that was cabled according to the
previously recommended cabling instructions, please schedule down time as
soon as possible to make changes to the drive side FC cabling. Refer to
the IBM System Storage DS4500 and DS4300 Installation, Users, and
Maintenance Guide for more information.

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

3. Depending on the storage subsystem that you have purchased, you

may have to purchase the DS4000 storage partitioning premium feature
option or an option to upgrade the number of supported partitions
in a storage subsystem. Please see IBM Marketing representatives
or IBM resellers for more information.

- IBM DS4100 storage subsystem (machine type 1724): The standard and
single controller configuration does not have the DS4000 storage
partitioning premium enabled. Four partition, eight partition,
sixteen and an upgrade from four to eight partition storage
partitioning premium feature options can be purchased.

- IBM DS4200 storage subsystem (machine type 1814): Depending on the

ordering channels, the DS420 storage subsystem is either shipped with
2 storage partitions or with a user selected 2, 4, 8, 16 or 64 storage
partitions. If the DS4200 storage subsystem is ordered with less than
64 partitions, various storage partition feature upgrade options can
be purchased to increase the maximum number of supported storage
partitions.

- IBM DS4300 storage subsystem (machine type 1722): The standard

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 Turbo option comes with
8 partition storage partitioning premium option installed. An
upgrade to 64 partitions can be purchased for the IBM DS4300
Turbo option.

- IBM FAStT200 (machine type 3542: The standard configuration has 16

partition storage partitioning premium option installed. No additional
storage partitioning premium feature options can be purchased for
these storage subsystems.

- IBM FAStT500 and DS4400 storage subsystems (machine type 3552 and
1742 - models 1RU and 1RX, respectively): The standard configuration
has 64 partition storage partitioning premium option installed. No
additional storage partitioning premium feature options can be
purchased for these storage subsystems.

- IBM DS4500 storage subsystem (machine type 1742 - models 90X and
90U): The standard configuration has 16 partition storage partitioning
premium option installed. An upgrade from 16 to 64 partition storage
partitioning premium feature option can be purchased.

- IBM DS4700 storage subsystem (machine type 1814): Depending on the

ordering channels, the DS4700-model 70 storage subsystem is either
shipped with 2 storage partitions or with a user selected 2, 4, 8, 16,
32, 64 or 128 storage partitions. Similarly, the DS4700-model 72
storage subsystem is either shipped with 8 storage partitions or with
a user selected 8, 16, 32, 64 or 128 storage partitions. If the DS4700
storage subsystem is ordered with less than 128 partitions, various
storage partition feature upgrade options can be purchased to increase
the maximum number of supported storage partitions.
 - IBM DS4800 storage subsystem (machine type 1815): Depending on the
ordering channels, the DS4800 storage subsystem is either shipped with
8 storage partitions or with a user selected 8, 16, 32, 64, 128, 256
or 512 storage partitions. If the subsystem is ordered with less than
512 partitions, an upgrade from 8 to 16, 8 to 32, 8 to 64, 16 to 32,
16 to 64, 32 to 64, 32 to 128, 64 to 128, 64 to 256, 128 to 256,
128 to 512, or 256 to 512 partition storage partitioning premium
feature option can be purchased.

- IBM DS5300 and DS5100 storage subsystem (machine type 1818):

the DS5300 and DS5100 storage subsystem is shipped with a user
selected 8, 16, 32, 64, 128, 256 or 512 storage partitions. If the
subsystem is ordered with less than 512 partitions, various storage
partition feature upgrade options can be purchased to increase the
maximum number of supported storage partitions.

4. Do not delete the Access LUN or Access Volume. The Access LUN is required
by the SMClient to communicate with the storage controllers when using the
in-band management method.

5. The DS4000 controller host ports or the Fibre Channel HBA ports can not
be connected to a Cisco FC switch ports with "trunking" enable. You might
encounter failover and failback problems if you do not change the Cisco
FC switch port to "non-trunking" using the following procedure:

a. Launch the Cisco FC switch Device Manager GUI.

b. Select one or more ports by a single click.
c. Right click the port(s) and select Configure, a new window pops up
d. Select the "Trunk Config" tab from this window, a new window opens
e. In this window under Admin, select the "non-trunk" radio button, it is
set to auto by default.
f. Refresh the entire fabric.

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

7. All enclosures (including DS4000 storage subsystem with internal drive

slots) on any given drive loop/channel should have complete unique ID's,
especially the single digit (x1) portion of the ID, assigned to them.
For example, in a maximum configured DS4500 storage subsystem, enclosures
on one redundant drive loop should be assigned with id's 10-17 and
enclosures on the second drive loop should be assigned with id's 20-27.
Enclosure id's with the same single digit such as 11, 21 and 31 should
not be used on the same drive loop/channel.

In addition, for enclosures with mechanical enclosure ID switch like

DS4300 storage subsystems, EXP100 or EXP710 storage expansion
enclosures, do not use enclosure ID value of 0. The reason is with the
physical design and movement of the mechanical enclosure ID switch, it
is possible to leave the switch in a �dead zone� between ID numbers,
which return an incorrect enclosure ID to the storage management
software. The most commonly returned enclosure ID is 0 (zero). In
addition to causing the subsystem management software to report
incorrect enclosure ID, this behavior also result in enclosure ID
conflict error with the storage expansion enclosure or DS4000 storage
 subsystem intentionally set the ID to 0.

The DS4200 and DS4700 storage subsystems and the EXP420 and EXP810
storage expansion enclosures did not have mechanical ID switches. Thus,
they are not susceptible to this problem. In addition, these storage
subsystems and storage expansion enclosures automatically set the
Enclosure IDs. IBM recommendation is not make any changes to these
settings unless the automatic enclosure ID settings resulting in non-
unique single digit settings for enclosures (including the storage
subsystems with internal drive slots) in a given drive loop/channel.

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

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

10. 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
SM 9.12 or later vs. enableAVT.scr for pre-SM 9.12)

11. When you configure a LUN from the DS4000 storage subsystem as a boot
device, the system displays a blue screen and does not respond when it
is manually or automatically set to hibernate. If you use a LUN in the
DS4000 storage subsystem as a boot device for Windows Server 2003, you
cannot enable the hibernation feature. To ensure that the hibernation
feature is disabled, complete the following steps:

a. Select Start >> Settings >> Control Panel >> Power Options.
b. Select the Hibernate tab.

IMPORTANT: If the Hibernate tab does not appear in this dialog, then
your system does not support hibernate. No additional action is
required.

c. Is the Enable Hibernate Support check box selected?

| Yes � Unselect the check box, select Apply, and then go to step d.
| No � Go to step d.
d. Select the Power Schemes tab.
e. From the Turn Off Hard Disks drop-down menu, select Never.
f. Select OK.

12. (Windows Server 2003) Cluster resources might fail on a host after
rebooting if the "Failback immediately" option is checked in the
Microsoft Cluster Server software. With this option checked, you might
see failed resources or devices not associated with their preferred
node. The current workaround is to make sure that the "Prevent
 failback" option is checked under Group Properties. This is the default
option. Do not use the "Failback immediately" option.

13. (Windows 2000) In a Microsoft Cluster Server (MSCS) environment

configured with VERITAS DMP, rebooting a server node owning the
resources might take a long time (10 to 15 minutes). It is possible
that the long server boot time might cause some Windows delayed write
failures. The workaround is to move all the resources from the server
node you are planning to reboot to another node before rebooting.

14. (Windows Server 2003) When in a server cluster environment, a failed

disk in the storage subsystem does not show as failed in the Cluster
Administrator. The host still receives I/O errors, and the disk is
shown as failed in the storage management software.

This is a known issue with the Windows Server 2003 operating system.
Choose one of the following workarounds:
� Workaround 1 � Reboot the host that owns the disk resource. The
Cluster Administrator should now show the proper state of the disk
resource.
� Workaround 2 � Change the ownership of the disk resource to a
different node in the server cluster configuration.

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

3.0 Configuration Information

-----------------------------

3.1 Configuration Settings

--------------------------

1. For the Microsoft Windows servers in MSCS configuration, the IBM DS4000
FC2, FC2-133 single or dual port and FC 4Gbps single or dual port FC HBA
adapter "Port Down Retry Count" BIOS parameter must be change to 70 from
the default of 30. You can either use the Qlogic SANsurfer (aka. FAStT
Management Suite Java (FAStT MSJ)) program or the FC HBA Fast!UTIL
program to change the setting in 32bit or X64 64bit servers. To invoke
the Fast!UTIL program, perform the following steps:

1. Reboot the server

2. Press <CNTL+Q> when the statement "Press <CNTL+Q> for Fast!UTIL " is
displayed when the server scan the FC-133 adapter during boot to get
invoke the Fast!UTIL program.
3. If there are multiple FC2-133 HBAs in your server, a list of the
HBAs will be displayed. Select the appropriate HBA and press enter to
get to the Fast!Util Options menu. Then, select the Configuration
Settings menu option followed by Advanced Adapter Settings menu
option to display the menu that the Port Down Retry Count parameter
is displayed. Select the parameter and press enter to edit the new
value.
4. Press ESC twice to get to the "Save setting" menu. Select appropriate
option to save the settings and return to the Fast!UTIL Options menu.
You can either select another HBA for modification or press ESC and
select Reboot System when you are prompted.

Alternatively, you can also use the Qlogic SANsurfer program to modify
 the setting from the Microsoft Windows operating system environment.
This is also the recommended method to change NVSRAM setting in Intel
Itanium II 64bit (IA64) servers. However, you must reboot the servers
for the changes to become effective.

In addition, the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk registry value
must be increased to 120 from the default setting of 60. A utility,
SMRegUpdate.reg, is provided in the SMUtil host software package to
facilitate this registry change.

The QLogic SANsurfer program can be downloaded from the DS4000 System
Storage support web site.

2. If a host in a cluster server configuration lost a physical path to a

DS4000 storage subsystem controller, the logical drives that are mapped
to the cluster group will periodically failover and then failback
between cluster nodes until the failed path is restored. This behavior
is the result of the automatic logical drive failback feature of the
RDAC multipath driver. The cluster node with a failed path to a DS4000
controller will issue a failover command of all logical drives that were
mapped to the cluster group to the controller that it can access. After
a programmed interval, the nodes that did not have failed path will
issue failback command for the logical drives because they can access
the logical drives both controllers, resulting in the cluster node with
the failed path not be able to access certain logical drives. This
cluster node will then issue a failover command for all logical drives,
repeating the logical drives failover-failback cycle.

The workaround is to disable this automatic failback feature. For Windows,

change the DisableLunRebalance registry setting of the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rdacdisk\Parameters]
registry key from 0 to 3 in each cluster node. Then, reboot each node
for the changes to take effect.

3. By default, the IBM DS4000 Storage Manager 8.3 and higher firmware does
not automatically map logical drives when the IBM DS4000 storage
partitioning premium feature is enabled. This means that the logical
drives after being created are not automatically presented to the host
systems.

a. For a new installation, after creating new arrays and logical drives,
create a storage partition with the host type of Windows 2000/Server
2003 non-clustered or Windows 2000/Server 2003 clustered and map the
logical drives to this partition.

b. If you are upgrading the NVSRAM with Storage Partitions, you may have
to change the default host type to match the host system OS. After
upgrading the NVSRAM, the default host type is reset to Windows
2000/Server 2003 non-clustered for DS4000 storage subsystem with
controller firmware version 06.14.xx.xx or later. For DS4000 storage
server with controller firmware version 06.12.xx.xx or earlier, it is
reset to Windows non-clustered (SP5 or higher), instead.

Refer to the IBM DS4000 Storage Manager online help to learn more about
creating storage partitions and changing host types.

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

- EnableAVT_W2K_S2003_noncluster.script: The script will enable automatic

logical 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.script: 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)

5. When you are configuring IBM machine type 1722, 1724, 1742, 1814, 1815
or 3552 storage subsystems 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.

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

3.2 Hardware status and information

-----------------------------------

Up to date interoperability information can be found at:

http://www-03.ibm.com/systems/support/storage/config/ssic/

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

3.3 Unsupported configurations

------------------------------

The following lists configurations that are currently not being

supported with IBM DS Storage Manager Version 10.77.
 1. The IBM EXP395 Expansion Enclosure is not supported attached to
any other IBM DS Storage Subsystems except the DS3950. EXP810 drive
enclosures are also supported in the DS3950 with the purchase of a premium
feature key.

2. The IBM EXP520 Expansion Enclosure is not supported attached to

any other IBM DS Storage Subsystems except the DS5020. EXP810 drive
enclosures are also supported in the DS5020 with the purchase of a premium
feature key.

3. The IBM EXP5000 Expansion Enclosure is not supported attached

to any other IBM DS Storage Subsystems except the DS5100 and DS5300.

4. The DS4100 (machine type 1724-all models) storage subsystem does not
support the attachment of the DS4000 EXP710, EXP700 and EXP500 (FC)
drive expansion enclosure.

5. The DS4800 storage subsystem (machine type 1815-all models) does not
support the attachment of the FAStT EXP500 and DS4000 EXP700 drive
expansion enclosures.

6. The DS4200 (machine type 1814 - models 7VA/H) does not support the
attachment of the DS4000 EXP100 (SATA), EXP710 (FC) and EXP810
(SATA and FC) drive expansion enclosures. In addition, it does not
support Fibre Channel disk drive options.

7. The IBM DS4000 EXP420 Expansion Enclosure is not supported attached

to any other IBM DS4000 Storage Subsystems except the DS4200.

8. The DS4100 with Single Controller option does not support the
attachment of the DS4000 storage expansion enclosures.

9. The DS5100 and DS5300 storage subsystems do not support the attachment
of the DS4000 EXP100, EXP700, EXP710 drive expansion enclosures. The
EXP810 is only supported through an RPQ process.

10. The DS5000 EXP5000 drive expansion enclosure is supported attached

to the DS5100 and DS5300 only.

11. The DS4700 and DS4800 storage subsystems do not support the attachment
of the DS4000 EXP700 drive expansion enclosures. The EXP700 enclosure
must be upgraded into DS4000 EXP710 enclosure using the DS4000 EXP700
Models 1RU/1RX Switched-ESM Option Upgrade Kit before it can be
attached to the DS4700 and DS4800 storage subsystems.

12. The DS4300 storage subsystem with Single Controller option does not
support the controller firmware version 06.xx.xx.xx. The correct
firmware version for these DS4300 storage subsystem models is
05.34.xx.xx.

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

14. The IBM Fibre Channel hub, machine type 3523, connected to IBM
machine type 1722, 1724, 1742, 1814, 1815, 3542 and 3552.
 15. 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.)

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

4.0 Unattended Mode

-------------------------------
N/A

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

5.0 WEB Sites and Support Phone Number

--------------------------------------------------------------

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

5.2 IBM System Storage� Marketing Web Site:

http://www.ibm.com/systems/storage

5.3 IBM System Storage� Interoperation Center (SSIC) web site:

http://www.ibm.com/systems/support/storage/ssic/

5.4 You can receive hardware service through IBM Services or through your
IBM reseller, if your reseller is authorized by IBM to provide warranty
service. See http://www.ibm.com/planetwide/ for support telephone
numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-
7378).

IMPORTANT:
You should download the latest version of the DS Storage Manager host
software, the DS4000/DS5000 storage subsystem controller firmware, the
DS4000/DS5000 drive expansion enclosure ESM firmware and the drive
firmware at the time of the initial installation and when product updates
become available.

For more information about how to register for support notifications,

see the following IBM Support Web page:

www.ibm.com/systems/support/storage/subscribe/moreinfo.html

You can also check the Stay Informed section of the IBM Disk Support
Web site, at the following address:

www.ibm.com/systems/support/storage/disk

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

6.0 Trademarks and Notices

--------------------------
 The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:

IBM

System Storage

the e-business logo

xSeries, pSeries

HelpCenter

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

Microsoft, Windows, and Windows NT are of Microsoft Corporation in the

United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other

countries, or both.

Java and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

QLogic and SANsurfer are trademarks of QLogic Corporation.

Other company, product, or 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.