IBM System Storage?subsystem controller firmware version 07.77.20.00 for
the DS3950-all models, DS5020-all models, DS3500-all models and DCS3700-all
models storage subsystems.
=====================================
BEFORE INSTALLING 07.77.20.00, PLEASE VERIFY ON SSIC (URL BELOW) THAT YOUR
STORAGE ENVIRONMENT IS SUPPORTED:
http://www.ibm.com/storage/support/config/ssic
=====================================
Attention:
A potential issue with the cache memory Error Correcting Code (ECC)
logic had been identified in the IBM System Storage DS3500 (DS3512 and
DS3524) ONLY with controller firmware versions 7.70.40.0 and older,
controller firmware version 7.75.11.0 and controller firmware version
7.77.18.0. The DS3500 storage systems with these controller firmware
versions installed should be upgraded to controller firmware version
7.77.19.00 (or later) immediately to avoid possible data integrity
issues. This issue does not exist in other IBM System Storage DS3000,
DS4000 and DS5000 systems.
(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.
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 Installation and Host Support Guide for
firmware and NVSRAM download instructions.
For other related publications, refer to Related Publications in the
Installation, User's and Maintenance guide of your DS storage subsystem
or storage expansion enclosures.
Last Update: 06/29/2011
Products Supported:
---------------------------------------------------------------
| New Model | Old Model | Machine Type | Model |
|------------|-----------|--------------|-----------------------|
| DS3950 | N/A | 1814 | 94H, 98H |
|------------|-----------|--------------|-----------------------|
| DS5020 | N/A | 1814 | 20A |
|------------|-----------|--------------|-----------------------|
| DS3500 | N/A | 1746 | C2A, A2S, A2D, C4A, |
| | | | A4S, A4D, C4T |
|------------|-----------|--------------|-----------------------|
| DCS3700 | N/A | 1818 | 80C |
---------------------------------------------------------------
Supported Enclosure Attachments:
The DCS3700-80C supports the attachment of the DCS3700-80E drive enclosure
only.
The DS3500 (DS3512 and DS3524) supports the attachment of EXP3500 (EXP3512
and EXP3524) drive enclosures only.
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.
Notes:
The following table shows the first four digits of the latest controller
firmware versions that are currently available for various models of the
DCS3700/DS3500/DS3950/DS4000/DS5000 storage subsystems.
---------------------------------------------------
| IBM Storage | Controller firmware version |
| Subsystem Model | |
|------------------|--------------------------------|
| DS5300 (1818) | 07.77.xx.xx |
|------------------|--------------------------------|
| DS5100 (1818) | 07.77.xx.xx |
|------------------|--------------------------------|
| DS5020 (1814) | 07.77.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.77.xx.xx |
|------------------|--------------------------------|
| DCS3700 (1818) | 07.77.xx.xx |
|------------------|--------------------------------|
| DS3500 (1746) | 07.77.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?controller firmware version 07.77.20.00 release
includes the storage subsystem controller firmware and NVSRAM files for
the DS3950-all models, DS5020-all models, DS3500-all models and DCS3700-
all models. This is a controller firmware update release for the DS5020,
DS3950, DS3500 and the DCS3700 storage subsystems. The IBM DS Storage
Manager host software version 10.77.x5.16 is required to manage DS
storage subsystems with controller firmware version 7.77.20.00
installed.
ATTENTION: DO NOT DOWNLOAD THIS CONTROLLER FIRMWARE ON ANY OTHER DS3000,
DS4000 or DS5000 STORAGE SUBSYSTEM MODELS.
The IBM System Storage DS Storage Manager version 10 Installation and
Host Support Guide is available on IBM's Support Web Site as a down-loadable
Portable Document Format (PDF) file.
The DS5020, DS3950, DS3500 and DCS3700 are shipped with a complimentary
of two partition storage partitioning premium feature. Please contact
IBM Marketing representatives or IBM resellers if you want to purchase
additional Storage partitioning options for your subsystems. In
addition, the Full Disk Encryption and Copy Services premium features -
FlashCopy, VolumeCopy and Enhanced Remote Mirroring are separately
purchased premium feature options.
See section 3.3 "Helpful Hints" for more information.
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.77.xx.xx or later will not be available for any DS3950/DS5020/
DS3500/DCS3700 storage subsystem controllers without the controller
firmware version 07.77.xx.xx or later installed.
The following table shows the controller firmware versions required for
attaching the various models of the DS3950/DS5020/DS3500/DCS3700 drive
expansion enclosures.
----------------------------------------------------
| Controller |EXP Storage Expansion |
| FW Version |Enclosures |
| |---------------------------------------|
| | EXP520 | EXP395 | EXP3500 | DCS3700 |
| | | | | 80E |
|------------|---------|---------|---------|---------|
|7.60.xx.xx | Yes | Yes | No | No |
|------------|---------|---------|---------|---------|
|7.70.xx.xx | Yes | Yes | Yes | No |
|------------|---------|---------|---------|---------|
|7.77.xx.xx | Yes | Yes | Yes | Yes |
------------------------------------------------------
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.
Note: For limitations in certain operating system environments, refer to the
readme file that is included in the DS Storage Manager host software package for
that operating system environment.
Limitations with version 07.77.20.00 release.
None
Limitations with version 07.77.19.00 release.
None
Limitations with version 07.77.18.00 release.
1. "Transferred on" date for Pending configuration is incorrect in AMW
physical tab. The timestamp displayed for the staged-firmware image will
be incorrect. This problem can be avoided by ensuring the controller뭩
real-time clock is correct before upgrading firmware.
2. ESM State capture info is truncated during support bundle collection.
An additional support-bundle can be collected to obtain valid ESM
capture-data. If this issue occurs, the support-bundle that is captured
will be missing some information in the ESM state-capture.
Limitations with version 07.70.38.00 release.
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.
Limitations with version 07.70.23.00 release.
1. FDE Drive in 밪ecurity Locked?state is reported as 밿ncompatible?state
in the drive profile. The drive can be recovered by importing the
correct lock key.
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 firwmare
updating has completed.
- RHEL5.5 RHCS Node stuck during shutdown when running nodefailover test.
Restriction: avoid soft-reboot with RHEL5.5 x64, IA64, PPC with Redhat
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, Redhat cluster
suite env with nodes running GFS.
Impact: The node failed to remount all the external storage disks
file systems (GFS) during boot up. Applications will lost access
to the cluster뭩 resource when the 2nd node reboot/offline.
Work-around: create a script to sleep for 30 sec and allow it executes
at startup.
Mitigation: Restart clvmd after boot , then restart gfs.
Limitations with versions 07.70.16.01 release.
1. After a host cable is removed, it could take up to 5 minutes before the
error condition is reported in the Storage Manager client.
2. When performing a replacement of a BladeCenter SAS switch module, wait
at least 5 minutes before reconnecting the SAS cables to the switch module.
This is to allow the switch module time to boot-up and complete it's SAS
discovery prior to re-discovery of the SAS paths. Reattaching the SAS cables
to soon can result in the SAS path's to not be discovered.
3. During deletion of a logical drive it is possible that a "ghost" (I.E. a
logical drive displayed with a dotted line picture) will be visible. If
this occurs you will need to go to Modify -> Edit Host-to-Logical Drive
Mappings. Then select the logical drive in question and click on the
remove option. This will destroy the "ghost" logical drive.
4. Arrays created using RAID levels 3,5, or 6 that will be mapped to an AIX
host, need to contain at a minimum five (5) hard drives.
5. VMware is currently not supported by the DS3500 using iSCSI.
6. When using Linux Device Mapper failover solution, the host will now
initiate failover after a specified number of outstanding I/Os rather
then a specified length of time when using the RDAC failover solution.
7. Currently when running some JSxx and QSxx blades with a SAS HBAs it is
possible to see intermittent IO failures after a path failure. This
issue is still being investigated but the following steps will insure
that the failure does not occur:
Edit the kernel boot line in your /boot/grub.conf file and add mem=3G boot
option to the command line.
8. When using a DS3500 with a SAS host daughter care attached to a IBM
BladeCenter chassis, you will not be able to swap installed and
configured blades into an additional chassis and maintain those
connections. You must power cycle the DS3500 before connecting it to
the new BladeCenter chassis.
9. Currently the device drivers for RHEL 4.5 and above for the MPT SAS driver
do not support the Enhanced Error Handling supported by the IBM JS
blades. If you are running these Operating systems you could see errors
during path restoration indicating that the MPT SAS driver has crashed.
10. If you are running SLES 10 with XEN support enabled you will be unable to
connect to a DS3500 controller.
11. The Storage Manager Client will accept accepts a value of 9000 for the
TCP MSS setting. The iSCSI host daughter card will only negotiate the
TCP MSS value to 8240 when a connection is established.
12. In a single controller configuration, a copy of the controller firmware
image is written to enclosure hard disk drives. In the event of a
controller failure and replacement, the replacement controller firmware
will sync with the image stored on the disk drives. Drives that are
newly imported into a single controller storage subsystem will not
store the current controller firmware image.
1.2 Enhancements
-----------------
The DS Storage Manager version 10.77.xx.10 host software in conjunction
with controller firmware version 7.77.20.xx and higher provides a fix
for the cache battery failures after an incomplete learn cycle. In
addition, controller firmware version 7.77.19.00 and higher also
provides
- Support the new IBM DS storage subsystem DCS3700 controller and drive
expansion enclosure.
- 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.
- Support for SAS drives with T10PI capability in the DS5020 and DS3950
storage subsystems.
- Various RAS enhancements.
- A fix to prevent a potential data integrity issue involving the DS3500
(DS3512 and DS3524) cache memory Error Correcting Code (ECC) logic in
the IBM System Storage DS3500s. The DS3500 controller firmware must be
upgraded to controller firmware version 7.77.19.00 or later (ie
7.77.20.00) to avoid possible data integrity issues. Please review the
changelist file for a list of additional DS3500 fixes included in this
version of controller firmware.
Note:
Host type VMWARE has been added to NVSRAM as an additional host type.
DS4200 and DS4700 will use index 21
All other supported systems will use index 16
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.
- The controllers do not need to be rebooted after the change of host type.
- The host will need to be rebooted.
- Changing the host type should be done under low I/O conditions.
1.3 Prerequisites
------------------
The IBM DS Storage Manager host software version 10.77.x5.16 is required to
manage DS3000, DS4000, and DS5000 storage subsystems with controller firmware
version 07.77.20.00 installed.
1.4 Dependencies
-----------------
The information in this section is pertinent to the controller firmware
version 7.77.xx.xx release only. For the dependency requirements of
previously released controller firmware versions, please consult
the Dependencies section in the readme file that was packaged with each
of those controller firmware releases.
ATTENTION:
1. 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 storage/drive expansion enclosure ESM, the
storage subsystem controller and the hard drive firmware.
2. The EXP810 and EXP520 ESM firmware version must be at or greater
than 98C5.
3. The disk drives and ESM packages are defined in the Hard Disk Drive
and ESM Firmware Update Package version 1.67 or higher found at the IBM
support web site.
1.5 Level Recommendations
-----------------------------------------
1. Storage Controller Firmware versions:
a. DS3500: FW_DS3500_07772000
b. DCS3700: FW_DS3500_07772000
c. DS3950: FW_DS3950_07772000
d. DS5020: FW_DS5020_07772000
Note: The DCS3700/DS3500 controller firmware version 7.77.19.00 has a
fix to prevent a potential data integrity issue involving the DS3500
(DS3512 and DS3524) and DCS3700 cache memory Error Correcting Code
(ECC) logic in the DS3500 storage subsystems. The DS3500 and DCS3700
storage subsystems must be upgraded to controller firmware version
7.77.19.00 (or later) immediately to avoid possible data integrity
issue. In general, follow the Recommendation Firmware Levels web link
in the IBM Support web page for your storage system model for the IBM
controller firmware level recommendation.
2. Storage Controller NVSRAM versions:
a. DS3500: N1746D35R0777V05.dlp (dual controller)
N1746D35L0777V05.dlp (single controller)
b. DCS3700 N1818D37R0777V05.dlp
c. DS3950: N1814D50R0777V05.dlp
d. DS5020: N1814D20R0777V05.dlp
Note: The DS3500/DS3950/DS4000/DS5000 storage subsystems shipped from
the factory may have NVSRAM versions installed with a different
first character prefix. Both manufacturing NVSRAM version and the
"N" prefixed NVSRAM version are the same. You do not need to update
your DS3950/DS4000/DS5000 storage subsystem with the "N" prefixed
NVSRAM version as stated above. For example, the N1815D480R923V08
and M1815D480R923V08 (or C1815D480R923V08 or D1815D480R923V08 or ...)
versions are the same. Both versions share the same
"1815D480R923V08" string value.
Refer to the following IBM System Storage?Disk Storage Systems
Technical Support web site for the latest released code levels.
http://www.ibm.com/systems/support/storage/disk
=======================================================================
2.0 Installation and Setup Instructions
-----------------------------------------
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.
The sequence for updating your Storage Subsystem firmware may be
different depending on whether you are updating an existing configuration,
installing a new configuration, or adding drive expansion enclosures.
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 refered 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.
Note: For additional setup instructions, Refer to the Installation, User's
and Maintenance Guide of your storage subsystem or storage expansion
enclosures.
2.1 Installation For an Existing Configuration
-------------------------------------------------
1. Upgrade the storage manager client program to the latest storage
manager 10.77 version that is available from the IBM system storage
support web site. Older versions of the storage manager client program
will show that the new firmware file is not compatible with the to-be-
upgraded subsystem, even when the existing version of the controller
firmware installed in the DS storage subsystem is of 7.7x.xx.xx code
thread.
http://www.ibm.com/systems/support/storage/disk
2. Download controller firmware and NVSRAM.
Please refer to the IBM DS Storage Manager version 10 Installation
and Host Support Guide for additional information.
Important: It is possible to download the controller firmware and
NVSRAM at the same time by selecting the option check box
in the controller firmware download window. However if
you have made any setting changes to the host parameters,
downloading NVSRAM will overwrite those changes. These
modifications must be reapplied after loading the new
NVSRAM file. You may need to update firmware and NVSRAM
during a maintenance window.
To download controller firmware and NVSRAM using the DS Storage
Manager application, do the following:
a. Open the Subsystem Management window.
b. Click Advanced => Maintenance => Download => Controller Firmware
Follow the online instructions.
c. Reapply any modifications to the NVSRAM. Both controllers must be
rebooted to activate the new NVSRAM settings.
To download controller NVSRAM separately, do the following:
a. Open the Subsystem Management window.
b. Click Advanced => Maintenance => Download => Controller => Controller
NVSRAM.
Follow the online instructions.
c. Reapply and modifications to the NVSRAM. Both controllers must be
rebooted to activate the new NVSRAM settings.
3. Update the firmware of the ESMs in the attached drive expansion
enclosures to latest levels. (See 1.4 Dependencies)
To download drive expansion ESM firmware, do the following:
a. Open the Subsystem Management window.
b. Click Advanced => Maintenance => Download => Environmental(ESM)
Card Firmware.
Follow the online instructions.
Note: The drive expansion enclosure ESM firmware can be updated
online with no downtime if both ESMs in each of the drive expansion
enclosures are functional and one (and ONLY one) drive expansion
enclosure is selected in the ESM firmware download window for ESM
firmware updating at a time.
Note: SAN Volume Controller (SVC) customers are now allowed to
download ESM firmware with concurrent I/O to the disk subsystem
with the following restrictions.
1) The ESM Firmware upgrade must be done on one disk expansion
enclosure at a time.
2) A 10 minute delay from when one enclosure is upgraded to the
start of the upgrade of another enclosure is required.
Confirm via the Storage Manager Application's "Recovery Guru"
that the DS5000 status is in an optimal state before upgrading the
next enclosure. If it is not, then do not continue ESM firmware
upgrades until the problem is resolved.
Note: Reference IBM System Storage?Disk Storage Systems
Technical Support web site for the current ESM firmware
versions for the drive expansion enclosures.
4. Make any hard disk drive firmware updates as required. FAILURE to
observe the minimum firmware requirement might cause your storage
subsystem to be OUT-OF-SERVICE. Check the IBM System Storage? Disk Storage Systems Technical Support web site for the latest released
hard drive firmware if you have not already upgraded drive firmware to
the latest supported version. (See 1.4 Dependencies)
To download hard disk drive firmware, do the following:
a. Schedule down time because the drive firmware upgrades require
that there are no HOST I/Os to be sent to the DS5000 controllers.
b. Open the Subsystem Management window.
c. Click Advanced => Maintenance => Download => Drive Firmware.
Follow the online instructions.
Note: with controller firmware version 06.1x.xx.xx or later,
multiple drives from up to four different drive types can be updated
at the same time.
=======================================================================
3.0 Configuration Information
-----------------------------
3.1 Configuration Settings
--------------------------
1. By default the IBM DS Storage Manager 10.77 does not automatically
map logical drives if storage partitioning feature is enabled.
This means that the logical drives are not automatically presented
to host systems.
For a new installation, after creating new arrays and logical drives;
a. If your host type is not Windows, 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.
When upgrading from previous versions of IBM DS Storage Manager
to version 10.70.
a. If upgrading with no partitions created and you have an operating
system other than Windows, you will need to create a partition
with your host type and map the logical drives from the "Default
Host Group" to this partition.
b. If upgrading with Storage Partitions and an operating system other
than Windows is accessing the default host group, you will need
to change the default host type. After upgrading the NVSRAM, the
default host type is reset to Windows Server 2003/2008 non-clustered
for DS storage server 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 DS Storage Manager online help to learn more
about creating storage partitions and changing host types.
2. Running script files for specific configurations. Apply the
appropriate scripts to your subsystem based on the instructions
you have read in the publications or any instructions in the
operating system readme file. A description of each script is
shown below.
- SameWWN.scr: Setup RAID controllers to have the same World Wide
Names. The World Wide Names (node) will be the same for each
controller pair. The NVSRAM default sets the RAID controllers
to have the same World Wide Names.
- DifferentWWN.scr: Setup RAID controllers to have different World
Wide Names. The World Wide Names (node) will be different for each
controller pair. The NVSRAM default sets the RAID controllers
to have the same World Wide Names.
- EnableAVT_W2K_S2003_noncluster.scr: The script will enable automatic
logical drive transfer (AVT/ADT) for the Windows 2000/Server 2003
non- cluster heterogeneous host region. The default setting is to
disable AVT for this heterogeneous host region. This setting is one
of the requirements for setting up the remote boot or SAN-boot. Do
not use this script unless it is specifically mentioned in the
applicable instructions. (This script can be used for other host
type if modifications are made in the script, replacing the Windows
2000/Server 2003 non-cluster host type with the appropriate host
type that needs to have AVT/ADT enabled)
- DisableAVT_W2K_S2003_noncluster.scr: The script will disable the
automatic logical drive transfer (AVT) for the Windows 2000/Server
2003 non-cluster heterogenous host region. This script will reset the
Windows 2000/Server 2003 non-cluster AVT setting to the default.
(This script can be used for other host type if modifications are
made in the script, replacing the Windows 2000/Server 2003 non-cluster
host type with the appropriate host type that needs to have AVT/ADT
disabled)
- EnableAVT_Linux.scr: The script will enable automatic logical drive
transfer (AVT) for the Linux heterogeneous host region. Do not use this
script unless it is specifically mentioned in the applicable
instructions.
- DisableAVT_Linux.scr: The script will disable the automatic logical
drive transfer (AVT) for the Linux heterogeneous host region. Do not
use this script unless it is specifically mentioned in the
applicable instructions.
- EnableAVT_Netware.script: The script will enable automatic logical
drive transfer (AVT) for the NetWare Failover heterogeneous host
region. Do not use this script unless it is specifically mentioned in
the applicable instructions.
- DisableAVT_Netware.script: The script will disable the automatic
logical drive transfer (AVT) for the NetWare Failover heterogeneous
host region. Do not use this script unless it is specifically
mentioned in the applicable instructions.
- disable_ignoreAVT8192_HPUX.script: This script will disable the DS4000
storage subsystem ignoring of AVT requests for the HP-UX server
specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request
for the LBA 8192 reads was implemented to prevent a possible occurrence
of an AVT storm caused by the HP-UX server probing in the wrong order
of available paths to the volume(s) when it detect server to LUN path
failure. Use this script only when you do not have defined LVM mirrored
volumes using the mapped logical drives from the DS4000 storage
subsystems. Please contact IBM support for additional information, if
required.
- enable_ignoreAVT8192_HPUX.script: This script will enable the DS4000
storage subsystem ignoring of AVT requests for the HP-UX server
specific read pattern of 2 blocks at LBA 8192. The AVT ignoring request
for the LBA 8192 reads was implemented to prevent a possible occurrence
of an AVT storm caused by the HP-UX server probing in the wrong order of
available paths to the volume(s) when it detect server to LUN path
failure. Use this script only when you do have defined LVM mirrored
volumes using the mapped logical drives from the DS4000 storage
subsystems. Please contact IBM support for additional information, if
required.
3.2 Unsupported configurations
------------------------------
The configurations that are currently not being supported with controller
firmware version 07.77.xx.xx in conjunction with DS Storage Manager
version 10.77 are listed below:
1. Any DS4200, DS4700, DS4800, DS4500, DS4400, DS4300, DS4100, FAStT500
and FAStT200 storage subsystems configurations are not supported with
this version of controller firmware.
2. 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.
3. The IBM Fibre Channel Hub, machine type 3523, connected to IBM
machine type 1722, 1724, 1742, 1815, 1814, 3542 and 3552.
4. A configuration in which a server with only one FC host bus
adapter connects directly to any 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 DS storage subsystem with dual
controllers via Fibre Channel (FC) switch (SAN-attached
configuration.)
3.3 Helpful Hints
------------------
1. Depending on the storage subsystem that you have purchased, you may have
to purchase the 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.
2. When making serial connections to the DS storage controller, the baud
rate is recommended to be set at 38400. Note: Do not make any connections to
the DS3000/DS4000/DS5000 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.
3. All enclosures (including storage subsystems with internal drive
slots) on any given drive loop/channel should have complete unique IDs,
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 ids 10- 17 and enclosures on
the second drive loop should be assigned with ids 20-27. Enclosure ids with
the same single digit such as 11, 21 and 31 should not be used on the same
drive loop/channel.
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)
6. Inter-operability with tape devices is supported on separate HBA and
switch zones.
=======================================================================
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/disk
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 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.
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
----------------------------
6.1 The following terms are trademarks of the IBM Corporation
in the United States or other countries or both:
IBM
DS4000
DS5000
FAStT
System Storage?
the e-business logo
xSeries
pSeries
HelpCenter
Microsoft Windows are trademarks of
Microsoft Corporation in the United States, other
countries, or both.
Java and all Java-based trademarks and logos are
trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the
United States and other countries.
Linux is a registered trademark of Linus Torvalds.
Other company, product, and service names may be
trademarks or service marks of others.
=======================================================================
7.0 Disclaimer
----------------
7.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS
OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
LICENSES TO ANY PATENTS OR COPYRIGHTS.
7.2 Note to U.S. Government Users -- Documentation related to
restricted rights -- Use, duplication or disclosure is
subject to restrictions set forth in GSA ADP Schedule
Contract with IBM Corporation.
'My Retain Tip > Storage DS' 카테고리의 다른 글
| vxAbsTicks 스토리지 uptime(사용시간) 확인 방법 (0) | 2012.02.28 |
|---|---|
| VTL RSA IP 기본 정보 (0) | 2012.02.15 |
| IBM DS4700 기본 정보 (0) | 2012.01.11 |
| DS3500시리즈의 기본구성품 (0) | 2012.01.05 |
| 스토리지 Error threshold exceeded 상태 Degraded (0) | 2012.01.01 |