Escolar Documentos
Profissional Documentos
Cultura Documentos
00 for
DS3950-all models, DS5020-all models, DS5100-all models and DS5300-all models
storage subsystems.
=====================================
BEFORE INSTALLING 07.84.56.00, PLEASE VERIFY ON SSIC (URL BELOW) THAT YOUR
STORAGE ENVIRONMENT IS SUPPORTED:
http://www.ibm.com/storage/support/config/ssic
=====================================
Note: Before using this information and the product it supports, read the
general information in section 6.0 "Trademarks and Notices" in this
document.
Note: Before commencing with any firmware upgrade procedure, use the
Storage Manager client to perform a Collect All Support Data capture.
Save this support data capture on a system other than the one that is
being upgraded.
Refer to the IBM System Storage Support Web Site or CD for the IBM
DS Storage Manager version 10.8 Installation and Host Support Guide for
firmware and NVSRAM download instructions.
Products Supported:
---------------------------------------------------------------
| New Model | Old Model | Machine Type | Model |
|------------|-----------|--------------|-----------------------|
| DS3950 | N/A | 1814 | 94H, 98H |
|------------|-----------|--------------|-----------------------|
| DS5020 | N/A | 1814 | 20A |
|------------|-----------|--------------|-----------------------|
| DS5100 | N/A | 1818 | 51A |
|------------|-----------|--------------|-----------------------|
| DS5300 | N/A | 1818 | 53A |
---------------------------------------------------------------
The DS3950 supports the attachment of EXP395 drive enclosures. EXP810 drive
enclosure attachment is supported as a premium feature and will require a
premium feature key.
The DS5020 supports the attachment of EXP520 drive enclosures. EXP810 drive
enclosure attachment is supported as a premium feature and will require a
premium feature key.
The DS5100 and DS5300 supports the attachment of EXP5000 and the EXP5060
drive enclosures. An IBM RPQ approval is required for support of all EXP810
migration configurations with the DS5100 and DS5300.
Notes:
The following table shows the first four digits of the latest
controller firmware versions that are currently available for
various models of the DS3000/DS3500/DCS3700/DS3950/DS4000/DS5000
storage subsystems.
---------------------------------------------------
| IBM Storage | Controller firmware version |
| Subsystem Model | |
|------------------|--------------------------------|
| DS5300 (1818) | 07.84.xx.xx |
|------------------|--------------------------------|
| DS5100 (1818) | 07.84.xx.xx |
|------------------|--------------------------------|
| DS5020 (1814) | 07.84.xx.xx |
|------------------|--------------------------------|
| DS4800 (1815) | 07.60.xx.xx |
| | (07.60.28.00 or later only) |
|------------------|--------------------------------|
| DS4700 (1814) | 07.60.xx.xx |
| | (07.60.28.00 or later only) |
|------------------|--------------------------------|
| DS4500 (1742) | 06.60.xx.xx |
|------------------|--------------------------------|
| DS4400 (1742) | 06.12.56.xx |
|------------------|--------------------------------|
| DS4300 Turbo | 06.60.xx.xx |
| Option (1722) | |
|------------------|--------------------------------|
| DS4300 | 06.60.xx.xx |
| Standard Option | |
| (1722) | |
|------------------|--------------------------------|
| DS4200 (1814) | 07.60.xx.xx |
| | (07.60.28.00 or later only) |
|------------------|--------------------------------|
| DS4100 (1724) | 06.12.56.xx |
| (standard dual | |
| Single | |
| controller Opt.)| |
| --------------------------------------------------|
| DS3950 (1814) | 07.84.xx.xx |
|------------------|--------------------------------|
| DCS3700 (1818) | 07.86.xx.xx |
|------------------|--------------------------------|
| DS3500 (1746) | 07.86.xx.xx |
|------------------|--------------------------------|
| DS3000 (1726) | 07.35.xx.xx |
---------------------------------------------------
ATTENTION:
1. 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.
2. 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
=======================================================================
CONTENTS
--------
1.0 Overview
2.0 Installation and Setup Instructions
3.0 Configuration Information
4.0 Unattended Mode
5.0 Web Sites and Support Phone Number
6.0 Trademarks and Notices
7.0 Disclaimer
=======================================================================
1.0 Overview
--------------
The IBM System Storage DS Storage Manager version 10.8 Installation and
Host Support Guide is available on IBM's Support Web Site as a down-loadable
Portable Document Format (PDF) file.
In addition, the FC/SATA intermix premium features and the Copy Services
premium features; FlashCopy, Enhanced FlashCopy, VolumeCopy, and Enhanced
Remote Mirroring are separately purchased options.
Refer to the IBM Support Web Site for the latest Firmware and NVSRAM
files and DS Storage Manager host software for the IBM DS Storage
Subsystems.
http://www.ibm.com/systems/support/storage/disk
New features that are introduced with the controller firmware version
07.83.xx.xx or later will not be available for any DS5000/DS3000
storage subsystem controllers without the controller firmware version
07.83.xx.xx or later installed.
The following table shows the controller firmware versions required for
attaching the various models of the DS3500/DCS3700/DS3950/DS4000/DS5000
Storage Expansion Enclosures.
---------------------------------------------------------------------
| Controller | EXP Storage Expansion Enclosures |
| FW Version |-------------------------------------------------------
| | EXP100 | EXP420 | EXP500 | EXP700 | EXP710 | EXP810 |
|------------|---------|--------|--------|--------|--------|--------|
|5.3x.xx.xx | No | No | Yes | Yes | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|5.40.xx.xx | No | No | Yes | Yes | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|5.41.xx.xx | Yes | No | No | No | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|5.42.xx.xx | Yes | No | No | No | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.10.0x.xx | Yes | No | Yes | Yes | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.10.1x.xx | Yes | No | Yes | Yes | Yes | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.12.xx.xx | Yes | No | Yes | Yes | Yes | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.14.xx.xx | Yes | No | No | No | Yes | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.15.xx.xx | Yes | No | No | No | Yes | No |
|------------|---------|--------|--------|--------|--------|--------|
|6.16.2x.xx | No | No | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|6.16.8x.xx | No | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|6.16.9x.xx | No | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|6.19.xx.xx | Yes | No | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|6.23.xx.xx | Yes | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|6.60.xx.xx | Yes | Yes | No | Yes | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|7.10.xx.xx | Yes | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|7.15.xx.xx | Yes | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|7.30.xx.xx | No | No | No | No | No | No |
|------------|---------|--------|--------|--------|--------|--------|
|7.36.xx.xx | Yes | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|7.50.xx.xx | Yes | Yes | No | No | Yes | Yes |
|------------|---------|--------|--------|--------|--------|--------|
|7.60.xx.xx | Yes | Yes | No | No | Yes | Yes |
|-------------------------------------------------------------------|
|7.70.xx.xx | No | No | No | No | No | Yes |
| and later | | | | | | |
---------------------------------------------------------------------
--------------------------------------------------------------------------------
| Controller |EXP Storage Expansion |
| FW Version |Enclosures |
| |-----------------------------------------------------------------|
| | EXP520 | EXP5000 | EXP395 | EXP5060 | EXP3500 | DCS3700 |
| | | | | | | 80E |
|------------|---------|------------|---------|------------|---------|---------|
|7.30.xx.xx | No | Yes | No | No | No | No |
|------------|---------|------------|---------|------------|---------|---------|
|7.36.xx.xx | No | Yes | No | No | No | No |
|------------|---------|------------|---------|------------|---------|---------|
|7.50.xx.xx | No | Yes | No | No | No | No |
|------------|---------|------------|---------|------------|---------|---------|
|7.60.xx.xx | Yes | Yes | Yes | Yes | No | No |
|------------|---------|------------|---------|------------|---------|---------|
|7.70.xx.xx | Yes | Yes | Yes | Yes | Yes | No |
|------------|---------|------------|---------|------------|---------|---------|
The following table shows the storage subsystem (controller module) and
minimum controller firmware versions required for T10-PI support.
Note: To have T10-PI work correctly, please use drives that state in the feature
list that they are T10-PI capable. Also, Refer to 1.4 Dependencies for
further restrictions on particular drive supportability information.
---------------------------------------------------------------
| New Model | Machine Type | T10-PI | Controler FW version |
|------------|--------------|----------|-----------------------|
| DS3500 | 1746 | No | N/A |
| | | | |
|------------|--------------|----------|-----------------------|
| DCS3700 | 1818 | No | N/A |
|------------|--------------|----------|-----------------------|
| DCS3700 | 1818 | Yes | 7.83 or later |
| Performance| | | |
| Module | | | |
| Controller | | | |
|------------|--------------|----------|-----------------------|
| DS3950 | 1814 | Yes | 7.77 or later |
|------------|--------------|----------|-----------------------|
| DS5020 | 1814 | Yes | 7.77 or later |
|------------|--------------|----------|-----------------------|
| DS5100 | 1818 | Yes | 7.77 or later |
|------------|--------------|----------|-----------------------|
| DS5300 | 1818 | Yes | 7.77 or later |
---------------------------------------------------------------
The following table shows the storage subsystem (controller module) and
minimum controller firmware versions required for HIC support.
-----------------------------------------------------------------------------------
----------------
| New Model | Machine Type | FC HIC | SAS HIC | 1Gb iSCSI HIC | 10Gb iSCSI
HIC | 10Gb iSCSI HIC |
| | | | | | (Copper)
| (Optic) |
|------------|--------------|----------|---------|---------------|----------------|
----------------|
| DS3500 | 1746 | 7.77 | 7.77 | 7.77 | 7/77
| N/A |
| | | | | |
| |
|------------|--------------|----------|---------|---------------|----------------|
----------------|
| DCS3700 | 1818 | 7.77 | 7.77 | N/A | N/A
| N/A |
|------------|--------------|----------|---------|---------------|----------------|
----------------|
| DCS3700 | 1818 | 7.83 | 7.84 | N/A | N/A
| 7.84 |
| Performance| | | | |
| |
| Module | | | | |
| |
| Controller | | | | |
| |
---------------------------------------------------------------------------------|-
---------------|
1.1 Limitations
---------------------
IMPORTANT:
The listed limitations are cumulative. However, they are listed by the 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.
No new limitations
No new limitations
No new limitations
No new limitations
No new limitations
No new limitations
1. Disabling individual host side PHY on the SAS switch during IOs
might cause the DS3500 and DCS3700 controllers to have ancient IOs. The work-
around is to disable the entire switch port instead.(LSIP200268504)
2. Rebooting SAS switch during periods with heavy IOs might cause the DS3500
and DCS3700 controllers to have SAS Discovery Errors 0x90. This error might
cause the controllers to continually reboot until it is placed in lockdown
state.(LSIP200274704)
3. Replacing a failed controller in a simplex DS3500 configuration having
controller firmware version 7.83.xx.xx and later installed with a controller
having version 7.77.xx.xx and earlier installed will result in the controller
be placed in "no drive found" state. The recovery procedure is to use the
Storage Manager version 10.83 and later to upgrade the firmware in the
replaced controllers with controller firmware version 7.83.xx.xx and later.
Note: Use the firmware upgrade menu function in the Enterprise management
window instead of the Subsystem management window to initiate the controller
firmware upgrade process.
4. While DS5100/5300 rebooting with heavy I/O, the controller may encounter a
work queue panic. The controller will reboot immediately and continue operations
normally. There owuld be no data lost after this symptom. To reduce I/O
transaction
would minimize the chance of this happen. (LSIP200159241)
No new limitations
1. The ETO setting of the 49Y4235 - Emulex Virtual Fabric Adapter (CFFh)
for IBM BladeCenter HBA must be manually set to 144 second. Please
review the publications that is shipped with the card for instruction
to change the setting.
2. The condition when LUNs within a Raid array have split ownership between the
two controllers could possibly see false positives on synthesized PFA has been
corrected by CR151915. The stagnant I/O will be discarded.
3. ESX 3.5.5:
Filesystem I/O in SLES11 VM failed during CFW upgrade in ESX35U5 + P20 patches.
Restriction: Running I/O with SLES11 VM filesystem while updating controller
firmware in VMware 3.5U5 + P20 patch.
Impact: User will see I/O error and Filesystem volumes in SLES11 VMs will
be changed to read-only mode.
Work-around: User can either perform controller FW upgrade with no I/O running
on SLES11 VM or with no Filesystem created in SLES11 VMs.
Mitigation: User can unmount the filesystem and remount the filesystem, then
I/O should be able to restart.
4. ESX 4.1:
I/O failed on Filesystem volume in SLES11 VM on ESX41.
Restriction: Running I/O with SLES11 VM filesystem while updating controller
firmware in VMware 4.1 env.
Impact: User will see IO error and Filesystem volumes in SLES11 VMs will
be changed to readonly mode.
Work-around: User can either perform controller firmware upgrade with no I/O
running on SLES11 VM or with no Filesystem created in SLES11
VMs.
Mitigation: User can unmount the filesystem and remount the filesystem, then
I/O should be able to restart.
Data Error in Head and Tail Sector is not matching during FcChipLip test with
SANbox.
Restriction: Need excess host and drive side chips reset simultaneously for a
long time on ESX4.1, QLogic QLE2562 and SANbox 5800
Impact: The LBA stored in the header or tail does not match the expected
LBA.
Work-around: N/A
Mitigation: None
I/O's failed in SLES10.2 VM during Controller FW Upgrade test on ESX41 with
Brocade HBA.
Restriction: Avoid online concurrent controller download with Brocade 8Gb HBAs
(8x5) on all guest OSes.
Impact: User will often see this issue if controller firmware upgrade is
performed with I/O.
Work-around: This issue occurs on various guest OSes so to avoid the issue,
user should perform an offline (no I/O to controllers)
controller
firmware upgrade.
Mitigation: Reboot the failed VM host.
BladeCenter: I/O errors reported on Linux VMs during automated CFW download.
Restriction: Running IO with SLES11 VM filesystem while updating CFW in VMware
4.1 env.
Impact: User will see IO errors on Linux Virtual machines if they upgrade
Controller Firmware while they have active I/Os.
Work-around: Stop all I/Os to the array from the ESX4.1 host (at least from the
Linux Virtual Machines) during Controller Firmware Downloads.
Mitigation: Users will have to reissue the I/O after controller firmware
updating has completed.
RHEL5.5 RHCS Node stuck during shutdown when running node failover test.
Restriction: avoid soft-reboot with RHEL5.5 x64, IA64, PPC with Red Hat Cluster
Suite. Need to do hard-boot.
Impact: The node will hang indefinitely and will not come back online.
Work-around: physically power it off.
Mitigation: Will need to turn the node off manually, by physically powering it
off.
RHEL5.5 RHCS GFS failed to mount the filesystems during node bootup.
Restriction: avoid node reboot on RH5.5 x64, IA64, PPC, Red Hat cluster suite env
1. The 7.60.xx release includes the synthesized drive PFA feature. This feature
will provide a critical alert if drive IOs respond slower than expected 30
times within a one hour period. There is a condition when LUNs within a RAID
array have split ownership between the two controllers where false positives
could be received on this.
2. When repeatedly remove and re-insert the fan module in the EXP5060 drive
expansion enclosure, the fan module amber fault LED might stay lit and the
recovery guru in the Storage manager might report that the fan is bad whereas
the fan module is working perfectly fine. This condition persists even when
the fan is replaced with a new fan module. Because the fan was removed and
re-insert many times, the controller might run into timing problem between
replacing the fan module and when the controller polls the ESM for status
updates and misinterprets the status of the removed fan as �failed? That
status bit is never reset, causing the fan amber fault led to remain on and
failed status to persist even after a new fan CRU is installed. If a
replacement fan module exhibits these symptoms, place your hand over the fan
and compare the air flow to the fan with good status on the opposite side of
the enclosure. If air flow is similar you can assume the fan with failed
status working properly. Schedule time for the DS subsystem can be placed
offline so that the whole storage subsystem configuration can be power cycled
to clear the incorrect status bit.
1. 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.
2. 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 DHCP 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.
2. Tivoli Productivity Center server does not retrieve the IPv6 address
from an SMI-S provider on an IPv6 host. You must use an IPv4 host.
4. Maximum sustainable IOPs falls slightly when going above 256 drives
behind a DS5100 or DS5300. Typically adding spindles improves performance
by reducing drive side contention. Not all IO loads will benefit by adding
hardware.
6. If you switch from IPv6 to IPv4 and have an iSNS server running,
you could see IPv6 address still showing up on the iSNS server. To
clear this situation, disable then enable iSNS on the controllers
after you disabled IPv6 support.
7. Long controller Start of Day times have been observed on the iSCSI
DS5020 with a large number of mirrors configured with an Asynchronous
w/ Write Order Consistency mirroring policy.
No new limitations
4. 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. 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.
No new limitations
No new limitations
4. Using 8KB segment size (default) with large IOs on a RAID-6 volume
can result in an ancient IO as a single IO will span several stripes.
Adjusting the segment size to better match the IO sizes such as 16KB
will improve this performance.
8. The IPv6 dynamic Link-Local address for the second management port on the
controller is not set when you toggle Stateless Autoconfig from Disabled
to Enabled. The IPv6 dynamic Link-Local address is assigned when the
controller is rebooted.
1.2 Enhancements
-----------------
Note: Host type VMWARE has been added to NVSRAM as an additional host type,
starting with controller firmware version 7.60.40.00. It is now separated
from the Linux Cluster host type, LNXCLVMWARE or LNXCL, which is now
rename as LNXCLUSTER. The VMWARE host type also has the "Not Ready" sense
data and "Auto Volume Transfer" defined appropriately for VMWare ESX server.
- The controllers do not need to be rebooted after the change of host type.
- The VMware host will need to be rebooted.
- Changing the host type should be done under low I/O conditions.
1.3 Prerequisites
------------------
ATTENTION:
2. The DS5020, DS3950, EXP5000, EXP810, EXP520, and EXP395 FC-SAS drives must
have the FC-SAS interposer firmware version 2264 or later installed. Some
drives with FC-SAS interposer firmware version earlier than version 2264
may report incorrect inquiry information during Start of Day. This causes
the controller firmware to make the drive uncertified (incompatible),
which in turn, causes the drive to no longer be accessible for I/Os. This
condition will also cause the associated array to go offline. Since the
array is no longer accessible, the controller firmware may not recover the
cache for all LUNs under this array. This behavior may result in data not
being written. If you believe that you have encountered this issue, please
call IBM Support for assistance with the recovery actions.
The FC-SAS interposer firmware version 2264 and later is available in the
ESM/HDD firmware package version 1.78 or later.
6. The disk drives and ESM packages are defined in the Hard Disk Drive
and ESM Firmware Update Package version 1.78 or higher found at the IBM
support web site.
a. DS3950: FW_DS3950_07845600
b. DS5020: FW_DS5020_07845600
c. DS5100: FW_DS5100_07845600
d. DS5300: FW_DS5300_07845600
a. DS3950: N1814D50R0784V04.dlp
b. DS5020: N1814D20R0784V04.dlp
c. DS5100: N1818D51R0784V04.dlp
d. DS5300: N1818D53R0784V04.dlp
http://www.ibm.com/systems/support/storage/disk
=======================================================================
Note: Before commencing with any firmware upgrade procedure, use the
Storage Manager client to perform a Collect All Support Data capture.
Save this support data capture on a system other than the one that is
being upgraded.
ATTENTION: If you have not already done so, please check the Dependencies
section for ANY MINIMUM FIRMWARE REQUIREMENTS for the storage server
controllers, the drive expansion enclosure ESMs and the hard drives in the
configurations. The order in which you will need to upgrade firmware levels
can differ based on prerequisites or limitations specified in these
readme files. If no prerequisites, or limitations, are specified, the
upgrade order referred to in section 2.1 Installation For an Existing
Configuration should be observed.
If drive firmware upgrades are required, down time will need to be scheduled.
The drive firmware upgrades require that there are no Host I/Os sent to the
storage controllers during the download.
http://www.ibm.com/systems/support/storage/disk
=======================================================================
For a new installation, after creating new arrays and logical drives;
a. If your host type is not Windows, create a partition with your
host type and map the logical drives to this partition.
b. If your host type is Windows, you can map your logical drives to
the "Default Host Group" or create a partition with a Windows host
type.
The configurations that are currently not being supported are listed below:
1. Any DS4000-all models, DS3200/3300/3400, FAStT500 and FAStT200
storage subsystems configurations are not supported with this
version of controller firmware.
2. The 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.
5. Fibre Channel loop environments with the IBM Fibre Channel Hub,
machine type 3523 and 3534, in conjunction with the IBM Fibre Channel
Switch, machine types 2109-S16, 2109-F16 or 2109-S08. In this
configuration, the hub is connected between the switch and the IBM
Fibre Channel RAID Controllers.
6. The IBM Fibre Channel Hub, machine type 3523, connected to IBM
machine type 1722, 1724, 1742, 1815, 1814, 3542 and 3552.
The DS3950, DS5020, DS4200 and DS4700 storage subsystems and the EXP395,
EXP520, EXP420, EXP810, and EXP5000 storage expansion enclosures do not have
mechanical ID switches. 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.
4. The ideal configuration for SATA drives is 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.
5. Starting with the DS4000 Storage Manager (SM) host software version 9.12
or later, the Storage Manager client script window looks for the files with
the file type of ".script" as the possible script command files. In the
previous versions of the DS4000 Storage Manager host software, the script
window looks for the file type ".scr" instead. (i.e. enableAVT.script for
9.12 or later vs. enableAVT.scr for pre-9.12)
=======================================================================
=======================================================================
5.1 IBM System Storage?Disk Storage Systems Technical Support web site:
http://www.ibm.com/systems/support/storage/disk
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 storage subsystem controller firmware, the
drive expansion enclosure ESM firmware and the drive firmware at
the time of the initial installation and when product updates become
available.
ftp.software.ibm.com/systems/support/tools/mynotifications/overview.pdf
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
=======================================================================
IBM
DS3000
DS4000
DS5000
DCS3700
FAStT
System Storage
xSeries
pSeries
HelpCenter
=======================================================================
7.0 Disclaimer
----------------