IBM System Storage DCS, System Storage DCS3700, System Storage DCS3860 Installation And Migration Manual
IBM System Storage DCS Series with Gen2 controllers
Hard Disk Drive and Storage Enclosure
Installation and Migration Guide
IBM
GA32-0962-07
Note
Before using this information and the product it supports, be sure to read the general information in “Notices and
statements in this document” on page x and “Notices” on page 61.
This edition applies to version 11 modification 20 of the IBM DS Storage Manager, and to all subsequent releases
and modifications until otherwise indicated in new editions.
This edition replaces GA32-0962-06.
© Copyright IBM Corporation 2008, 2015.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures ............... v
Tables ............... vii
Introduction............. ix
Supported IBM System Storage DCS Series with
Gen2 controllers ............. ix
Receiving product updates and support notifications ix
DS Storage Subsystem installation and support
guides ................ ix
Notices and statements in this document ..... x
Chapter 1. Prerequisites to adding
capacity and hard disk drive migration . 1
Preparing the storage subsystem........ 1
Preparing to export and import drives...... 3
Determining the supported number of drives and
drive loop pairs ............. 4
Verifying controller, NVSRAM, and ESM firmware
compatibility .............. 4
Storage subsystem profile ......... 5
Physical View pane ........... 6
Upgrading ESM and controller firmware ..... 6
Drive migration limitations ......... 7
Verifying hard disk drive model compatibility ... 8
Viewing the product ID and model of a hard disk
drive ................. 9
Bringing storage subsystems and drive loops into
optimal state .............. 11
Intermixing storage enclosures ........ 11
Chapter 2. Adding or migrating hard
disk drives ............. 13
Considerations ............. 13
Handling static-sensitive devices ....... 14
Adding new hard disk drives ........ 14
Migrating hard disk drives ......... 15
Step 1: Preliminary activities........ 16
Step 2: Verifying drive migration enable settings 17
Step 3: Placing drives offline........ 17
Step 4: Removing drives ......... 18
Step 5: Inserting drives ......... 19
Migrating arrays within the same storage subsystem 21
Chapter 3. Adding or migrating storage
enclosures ............. 25
Considerations ............. 25
Step 1: Preliminary activities......... 26
Adding new storage enclosures with new hard
disk drives ............. 27
Migrating storage enclosures with hard disk
drives that have defined logical drive
configurations ............ 27
Step 2: Preparing and backing up the drives ... 28
Step 3: Shutting down and moving the storage
enclosures ............... 29
Step 4: Verifying the drive migration enable settings 30
Step 5: Installing and setting storage enclosure IDs 30
Step 6: Cabling, turning on, and verifying storage
enclosure operation ............ 31
Cabling the new enclosures ........ 31
Connecting storage enclosures at the end
(bottom) of a drive loop ......... 31
Connecting storage enclosures at the end
(bottom) of a SAS drive cable loop scheme in a
DCS3700 and DCS3860 storage subsystems with
Gen2 controllers configuration ....... 32
Returning the drive/loop channel to optimal
state ................ 33
Storage subsystem SAS drive channel/loop
schemes for enclosures in a DCS3700
configuration ............. 33
Storage subsystem SAS drive channel/loop
schemes for enclosures in a DCS3860 with Gen2
controllers configuration ......... 35
Cabling multiple enclosures ........ 36
Step 7: Inserting drives and cabling additional
storage enclosures ............ 38
Step 8: Inserting hard disk drives and placing
logical drives online ........... 38
Chapter 4. Upgrading a storage
subsystem controller ........ 41
Upgrade considerations .......... 41
Host attachment and premium feature
entitlements ............. 41
Storage firmware migration ........ 42
Alternative procedure to upgrade a storage
subsystem controller enclosure ....... 42
Supported upgrades .......... 43
Configuration behavior after an upgrade and
storage subsystem replacement ....... 44
Storage subsystem behavior when turning on the
power with no drives attached ....... 46
Performing an upgrade .......... 46
Redeploying the original storage subsystem ... 53
Redeployment limitations......... 53
Configuration behavior in a redeployed storage
subsystem .............. 54
Appendix. Getting information, help,
and service ............. 57
Before you call ............. 57
Using the documentation .......... 57
Finding Storage Manager software, controller
firmware, and readme files ......... 57
Getting help and information from the World Wide
Web ................. 58
Software service and support ........ 59
© Copyright IBM Corp. 2008, 2015 iii
Hardware service and support ........ 59
Taiwan Contact Information ......... 59
Fire suppression systems .......... 59
Notices .............. 61
Trademarks .............. 63
Important notes ............. 64
Particulate contamination.......... 65
Documentation format........... 65
Electronic emission notices ......... 66
Federal Communications Commission Statement 66
Industry Canada Compliance Statement .... 66
Australia and New Zealand Class A Statement 66
European Union Electromagnetic Compatibility
Directive .............. 66
Taiwan Class A Statement ........ 67
Germany Electromagnetic Compatibility Directive 67
People's Republic of China Class A Statement .. 68
Japan Voluntary Control Council for Interference
Class A Statement ........... 68
Japan Electronics and Information Technology
Industries Association Statement ...... 69
Korean Communications Commission Class A
Statement .............. 69
Index ............... 71
iv IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Figures
1. Subsystem Management Logical/Physical
View of exported drives ........ 18
2. Drive CRU assembly ......... 19
3. Best practice for reordering a defined array by
using empty bays in one storage enclosure .. 21
4. Best practice for reordering a defined array by
using empty bays in two storage enclosures.. 21
5. Reordering multiple defined arrays across
previously used bays in two storage enclosures 22
6. Subsystem Management Logical/Physical
View of missing logical drives ...... 22
7. Connecting the first EXP3800/DCS3700
expansion enclosure.......... 35
8. Adding enclosures .......... 37
9. Firmware compatibility flowchart for a storage
subsystem upgrade .......... 49
© Copyright IBM Corp. 2008, 2015 v
vi IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Tables
1. Supported drives and drive loop pairs in
storage subsystems .......... 4
2. Machine types, supported controller firmware,
and supported Storage Manager software ... 5
3. Compatible storage enclosure ESM firmware
level by machine type and model number... 5
4. Drive migration limitations based on controller
firmware levels............ 8
5. Snapshot of profile information identifying the
product ID of the drive in bay 12 of enclosure
ID 1 ............... 10
6. Storage enclosure compatibility with storage
subsystems by model for DCS Series storage
subsystems............. 12
7. DCS3700 and EXP3800 expansion enclosures
supported by controller firmware levels ... 12
8. Connecting storage enclosures at the end
(bottom) of a SAS drive cable loop scheme in a
DCS3700 and DCS3860 storage subsystems
with Gen2 controllers configuration .... 33
9. Supported replacement storage subsystems 43
10. Snapshot of profile information that identifies
the storage subsystem worldwide identifier
(ID) ............... 45
11. Limits for particulates and gases ..... 65
© Copyright IBM Corp. 2008, 2015 vii
viii IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Introduction
This document describes how to add new SAS hard disk drives or a new IBM
System Storage®storage enclosures that contain new SAS hard disk drives to an
existing IBM storage subsystem configuration. This document also describes how
to migrate hard disk drives or IBM System Storage storage enclosures that contain
hard disk drives from one storage subsystem to another.
This document also describes how to replace the storage subsystem with a new
storage subsystem of the same or different model. In this case, all the hard disk
drives and storage enclosures in the original configuration become part of the new
configuration.
Before you begin, familiarize yourself with the information in Chapter 1,
“Prerequisites to adding capacity and hard disk drive migration,” on page 1. Your
familiarity with the information described in this document is critical to preventing
loss of data availability, and in some cases, loss of data.
Supported IBM System Storage DCS Series with Gen2 controllers
IBM System Storage DCS Series include the following storage models:
v IBM System DCS3700 Storage Subsystem with Gen2 Controllers
v IBM System DCS3860 Storage Subsystem with Gen2 Controllers
Receiving product updates and support notifications
®
Be sure to download the latest levels of the following packages at the time of
initial installation and when product updates become available:
v DS Storage Manager host software
v Controller firmware
v Environmental service modules (ESM) firmware
v Hard disk drive firmware
Important: Keep your system up-to-date with the latest firmware and other
product updates by subscribing to receive support notifications.
For more information about how to register for support notifications, see
http://www.ibm.com/systems/support/ and click My notifications.
DS Storage Subsystem installation and support guides
This document frequently refers to the IBM System Storage DS Storage Manager
Version 11.2 Installation and Host Support Guide for the storage subsystems.
To access the documentation related to your storage subsystem, operating system,
and DS Storage Manager version from the IBM Support Portal, complete the
following steps:
1. Go to http://www.ibm.com/support/entry/portal.
2. Under Choose your products, click Browse for a product or Search for a
product.
3. Under Choose your task, click Documentation.
© Copyright IBM Corp. 2008, 2015 ix
4. Under See your results, click View your page.
5. In the Product documentation box, click the link for the publication that you
want to access.
Notices and statements in this document
The caution and danger statements in this document are also in the multilingual
Safety Information document, which is on the IBM Support Software DVD. Each
statement is numbered for reference to the corresponding statement in your
language in the Safety Information document.
The following notices and statements are used in this document:
v Note: These notices provide important tips, guidance, or advice.
v Important: These notices provide information or advice that might help you
avoid inconvenient or problem situations.
v Attention: These notices indicate potential damage to programs, devices, or data.
An attention notice is placed just before the instruction or situation in which
damage might occur.
v Caution: These statements indicate situations that can be potentially hazardous
to you. A caution statement is placed just before the description of a potentially
hazardous procedure step or situation.
v Danger: These statements indicate situations that can be potentially lethal or
hazardous to you. A danger statement is placed just before the description of a
potentially lethal or hazardous procedure step or situation.
Before installing this product, read the following danger and caution notices.
Statement 1
x IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
DANGER
Electrical current from power, telephone, and communication cables is
hazardous.
To avoid a shock hazard:
v Do not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical storm.
v Connect all power cords to a properly wired and grounded electrical outlet.
v Connect to properly wired outlets any equipment that will be attached to
this product.
v When possible, use one hand only to connect or disconnect signal cables.
v Never turn on any equipment when there is evidence of fire, water, or
structural damage.
v Disconnect the attached power cords, telecommunications systems,
networks, and modems before you open the device covers, unless
instructed otherwise in the installation and configuration procedures.
v Connect and disconnect cables as described in the following table when
installing, moving, or opening covers on this product or attached devices.
To Connect: To Disconnect:
1. Turn everything OFF.
2. First, attach all cables to devices.
3. Attach signal cables to connectors.
4. Attach power cords to outlet.
5. Turn device ON.
1. Turn everything OFF.
2. First, remove power cords from outlet.
3. Remove signal cables from connectors.
4. Remove all cables from devices.
Statement 3
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable parts
inside the device.
v Use of controls or adjustments or performance of procedures other than those
specified herein might result in hazardous radiation exposure.
Introduction xi
DANGER
1
2
Some laser products contain an embedded Class 3A or Class 3B laser diode.
Note the following.
Laser radiation when open. Do not stare into the beam, do not view directly
with optical instruments, and avoid direct exposure to the beam.
Statement 4
≥ 18 kg (39.7 lb) ≥ 32 kg (70.5 lb) ≥ 55 kg (121.2 lb)
CAUTION:
Use safe practices when lifting.
Statement 5
CAUTION:
The power control button on the device and the power switch on the power
supply do not turn off the electrical current supplied to the device. The device
also might have more than one power cord. To remove all electrical current from
the device, ensure that all power cords are disconnected from the power source.
Statement 8
xii IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
CAUTION:
Never remove the cover on a power supply or any part that has the following
label attached.
Hazardous voltage, current, and energy levels are present inside any component
that has this label attached. There are no serviceable parts inside these
components. If you suspect a problem with one of these parts, contact a service
technician.
Statement 29
CAUTION:
This equipment is designed to permit the connection of the earthed conductor of
the dc supply circuit to the earthing conductor at the equipment.
This equipment is designed to permit the connection of the earthed conductor of
the dc supply circuit to the earthing conductor at the equipment. If this
connection is made, all of the following conditions must be met:
v This equipment shall be connected directly to the dc supply system earthing
electrode conductor or to a bonding jumper from an earthing terminal bar or
bus to which the dc supply system earthing electrode conductor is connected.
v This equipment shall be in the same immediate area (such as, adjacent
cabinets) as any other equipment that has a connection between the earthed
conductor of the same dc supply circuit and the earthing conductor, and also
the point of earthing of the dc system. The dc system shall not be earthed
elsewhere.
v The dc supply source shall be located within the same premises as this
equipment.
v Switching or disconnecting devices shall not be in the earthed circuit
conductor between the dc source and the point of connection of the earthing
electrode conductor.
Statement 30
Introduction xiii
CAUTION:
To reduce the risk of electric shock or energy hazards:
v This equipment must be installed by trained service personnel in a
restricted-access location, as defined by the NEC and IEC 60950-1, First
Edition, The Standard for Safety of Information Technology Equipment.
v Connect the equipment to a reliably grounded safety extra low voltage (SELV)
source. An SELV source is a secondary circuit that is designed so that normal
and single fault conditions do not cause the voltages to exceed a safe level (60
V direct current).
v The branch circuit overcurrent protection must be rated 20 A.
v Use 12 American Wire Gauge (AWG) or 2.5 mm2 copper conductor only, not
exceeding 4.5 meters in length.
v Incorporate a readily available approved and rated disconnect device in the
field wiring.
CAUTION:
This unit has more than one power source. To remove all power from the unit,
all DC MAINS must be disconnected.
Cable Warning
WARNING: Handling the cord on this product or cords associated with
accessories sold with this product will expose you to lead, a chemical known to the
State of California to cause cancer and birth defects or other reproductive harm.
Wash hands after handling.
xiv IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Chapter 1. Prerequisites to adding capacity and hard disk drive migration
The following notes describe general information that you must consider when
you perform the procedures in this document.
v Check the controller firmware readme files, the documentation that comes with
your hardware, and this guide for the following information:
– The latest information about storage subsystem and storage enclosure
compatibility
– The latest information and rules about storage enclosure cabling to the
storage subsystem drive port
– Any requirements of the installed microcode and firmware to support the
storage subsystem and storage enclosure
v To prevent damage to the storage subsystem or to the storage enclosure
backplane, ensure that the hard disk drives are compatible with your storage
subsystem before you install them. Refer to the storage subsystem
announcement letter for information about compatible devices.
v For more information about the procedures in this document, contact your IBM
marketing representative or authorized reseller.
Preparing the storage subsystem
To prepare the target and source storage subsystems to add storage capacity or
migrate hard disk drives, complete the following steps. Unless it is specified
otherwise, perform the following steps on the target subsystem for adding new
hard disk drive capacity and on both the target and source storage subsystems for
migrating hard disk drives with data.
Attention: Failure to complete the following steps before you add storage
capacity or migrate hard disk drives might result in loss of data availability or loss
of data.
1. Complete a full backup of all data on the storage subsystem.
2. Ensure that the backup was successful.
3. Verify the hardware compatibility and requirements by reviewing the
information in “Determining the supported number of drives and drive loop
pairs” on page 4 and the storage subsystem announcement letters. If addition
of storage enclosures is required, review “Intermixing storage enclosures” on
page 11 and the cabling information in the Installation, User's, and Maintenance
Guide for any special cabling requirements.
4. If you want to perform a drive migration between storage subsystems, verify
that the drives can be migrated to the new storage subsystem.
Note: Currently, drives with disk pools cannot be migrated from one
subsystem to another. The data in the disk pool must be backed up to a tape
or to drives that are part of traditional arrays. Then, the data is restored to
newly created disk pools in another storage subsystem. For more information,
see the “Drive migration limitations” on page 7 section.
5. Ensure that the storage subsystem has the latest controller firmware,
nonvolatile storage random access memory (NVSRAM), and ESM firmware.
Also, ensure that the installed controller firmware in the storage subsystem
© Copyright IBM Corp. 2008, 2015 1
supports the drives and storage enclosures. See “Verifying controller,
NVSRAM, and ESM firmware compatibility” on page 4.
6. Ensure that the hard disk drive firmware is the latest level. Upgrading drive
firmware is a nonconcurrent operation. Schedule a maintenance window
during which you can stop input and output to the storage subsystem for
drive firmware updates.
Note: 3 Gbps SAS drives in a 6-Gbps SAS enclosure or 6-Gbps SAS drive in a
3-Gbps SAS enclosure is not supported.
7. Verify that the storage subsystem is in Optimal state and does not stop in the
middle of long running tasks such as modifications to the dynamic logical
drive expansion (DVE) or Array RAID levels. See the Recovery Guru function
in the Storage Subsystem Management window for instructions on bringing
the storage subsystem into Optimal state. Also, see “Bringing storage
subsystems and drive loops into optimal state” on page 11.
8. Resolve any critical errors reported in the Storage Subsystem MEL.
9. Save and store the storage subsystem profile and configuration script along
with the collect all support data bundle.
Attention: To prevent loss of data, do not store storage subsystem profiles or
collect all support data information in the same location as the logical drives
defined on your storage subsystem.
10. Obtain and activate any required premium features.
11. Ensure that the hard disk drives are compatible. See “Verifying hard disk
drive model compatibility” on page 8. Also, see the information for your
drives in the announcement letter.
12. If you are adding capacity, see Chapter 2, “Adding or migrating hard disk
drives,” on page 13 or Chapter 3, “Adding or migrating storage enclosures,”
on page 25, depending on the task you are performing.
13. (For the source storage subsystem only) Stop all programs, services, and
processes in the host servers that access the logical drives defined in the
migrated hard disk drives.
14. (For the source storage subsystem only) Ensure that no programs, services, or
processes are running in the background that might write data to the logical
drives. For example, Microsoft MSCS service periodically writes to the
Quorum disk.
15. (For the source storage subsystem only) Unmount the file systems to flush
I/O from the server cache to disk.
Note:
a. In a Microsoft Windows environment, remove the drive letter or the
mount points of the mapped LUNs instead of unmounting the file
systems.
b. See your operating-system documentation for detailed information about
the unmount procedure.
16. Back up the changes that you made during this procedure.
17. If the migrated drives are FDE drives and were configured as part of secured
array, save the storage subsystem security (lock) key to unlock the drives after
installing them in a new storage subsystem. Without this key, the controllers
cannot unlock the drives to perform input and output processes. For details
about the security key, see the IBM System Storage DS Storage Manager Version
11.2 Installation and Host Support Guide.
2 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
If the migrated drives from the storage subsystem operate in external license
key management mode, ensure that the new storage subsystem also operates
in external license key management mode and uses the same external key
server.
18. See the applicable chapter to complete the task that you plan to perform.
v Chapter 2, “Adding or migrating hard disk drives,” on page 13.
v Chapter 3, “Adding or migrating storage enclosures,” on page 25.
v Chapter 4, “Upgrading a storage subsystem controller,” on page 41.
Preparing to export and import drives
Complete the following steps on the source storage subsystem to prepare to export
drives:
1. Save the storage subsystem configuration so that a copy of the array
configuration is available, if the export fails.
2. Stop all I/O and unmount or disconnect the file system.
3. Back up the array data.
4. Use the Locate Array function in the Storage Subsystem Manager window to
identify the physical disks that are associated with the array. Then, label each
drive with source and target storage subsystem names, array name, and total
number of drives in the array. After the drives are exported or offline, you
might not be able to use the array locate function to locate the drives that are
part of an array, depending on the version of installed controller firmware.
5. Ensure that you have enough blank drive canisters or new drives to cover the
drive bays from which the drives are removed to maintain airflow in the
storage enclosure.
6. If the source storage subsystem contains secured full data encryption (FDE)
arrays, save a copy of the security key in the target storage subsystem.
Verify the following on the target (destination) storage subsystem to prepare to
export drives:
v You have enough drive bays for the drives.
v The storage subsystem supports the drives. You cannot exceed the maximum
number of drives that the storage subsystem supports.
v The storage subsystem supports the RAID level that you are importing. You
cannot exceed the maximum number of logical drives that the storage subsystem
supports.
v The target storage subsystem supports RAID level 6, if you are importing RAID
level 6.
v The controllers in the storage subsystem have the latest version of controller
firmware.
v The latest DS Storage Manager software is installed.
v You have purchased and enabled any premium feature keys.
v If the source storage subsystem operates in external key management mode, the
target storage subsystem also operates in external key management mode and is
managed by the same external key manager. That way, you do not have to
supply the security key to unlock the secured FDE drives when importing them.
Otherwise, save the security key in the source storage subsystem.
Chapter 1. Prerequisites to adding capacity and hard disk drive migration 3
Determining the supported number of drives and drive loop pairs
Use the information in this section to determine the hardware requirements before
you migrate storage subsystems or add hard disk drives. Table 1 provides a list of
the supported number of drives and drive loop pairs for each storage subsystem
by machine type and model number. It also specifies storage enclosure license
requirements.
Table 1. Supported drives and drive loop pairs in storage subsystems
Maximum
drive
Machine
Storage subsystem
DCS3700 with Gen2
Controllers
DCS3860 with Gen2
Controllers
Notes:
1. The DCS3700 expansion enclosure is the only supported drive expansion enclosure for
the DCS3700 with Gen2 controllers storage subsystem.
2. The EXP3800 and DCS3700 expansion enclosures are the only supported drive expansion
enclosure for the DCS3860 storage subsystem.
1
2
type
1818 90C 180 1 None
1813 96C 360 0 None
Model
number
Maximum
drives
loop/channel
pairs
Storage
enclosure
license
requirement
Verifying controller, NVSRAM, and ESM firmware compatibility
Use the information in this section to verify controller, NVSRAM, and ESM
firmware compatibility before you migrate storage subsystems or add hard disk
drives. For firmware compatibility between the migrating and original hardware,
the controller firmware and NVSRAM of the target migration storage subsystem
must be at the levels that are indicated in Table 2 on page 5.
You can use the DS Storage Manager Client software and the controller firmware
to upgrade the ESM firmware while the storage subsystem receives I/O from the
host server, if you select only one storage enclosure to download the ESM
firmware at a time in the Select Drive Enclosure To Download ESM Firmware
Window.
Note:
1. See the most recent readme file that is included with the storage subsystem
controller firmware package. To access the most recent readme file, see
“Finding Storage Manager software, controller firmware, and readme files” on
page 57.
2. See the readme file for any I/O operation requirements. Some controller
firmware upgrade scenarios might require that you first quiesce host I/O
operations.
3. See the readme file to ensure that the firmware is compatible with the
controller firmware in the storage subsystem that you are upgrading.
4. Although you can upgrade the storage subsystem and ESM firmware while it
processes I/O from the host server, schedule upgrades to occur during time
periods of low I/O between the storage subsystems and host servers.
Table 2 on page 5 lists the supported machine types, model numbers, and the latest
version of released Storage Manager software and controller firmware levels for
4 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
each machine type. Review the announcement letter for your drives and the
readme file of the ESM and hard disk drive firmware package for any controller
firmware and ESM firmware requirements.
Table 2. Machine types, supported controller firmware, and supported Storage Manager
software
Storage subsystem Machine
type
DCS3700 with Gen2 Controllers 1818 90C 8.20.xx.xx 11.20.xx.xx
DCS3860 with Gen2 Controllers 1813 96C 8.20.xx.xx 11.20.xx.xx
Model Supported
controller
firmware
12
level
Supported Storage
Manager software
version
Important:
1. For the latest NVSRAM versions, see http://www.ibm.com/systems/support/
storage/disk/.
2. To verify software version levels or to identify possible interim updates to
firmware and NVSRAM file versions that are described in Table 2, go to
http://www.ibm.com/systems/support/storage/disk/.
Before you update the controller firmware and NVSRAM to the version that is
indicated in Table 3, see the readme file included in the controller firmware
code package for information about upgrades or stepping-stone controller
firmware upgrades that you must perform first.
Table 3 lists storage enclosure models by name, machine type, model number,
and current ESM firmware level.
Table 3. Compatible storage enclosure ESM firmware level by machine type and model
number
Storage subsystem and storage
enclosure product name/model
DCS3700 expansion enclosure 1818 80E 039C or later
DCS3860 EXP3800 1813 80E 039C or later
Storage subsystem profile
When the Storage Subsystem Profile window opens, click the All tab and scroll
through the Profile For Storage Subsystem section to locate the following
information.
Note: The Profile For Storage Subsystem section contains all the profile
information for the entire subsystem. Therefore, it might be necessary to scroll
through a large amount of information to locate the firmware level numbers.
Storage Subsystem
v NVSRAM version
v Controller firmware (or appware, bootware, or both) version
See the following example of profile information.
Machine
type
Model
number ESM firmware level
Chapter 1. Prerequisites to adding capacity and hard disk drive migration 5
Controller in Enclosure 0, Slot A
Status: Online
Current configuration
Firmware version: 06.10.07.00
Appware version: 06.10.07.00
Bootware version: 06.10.07.00
NVSRAM version: 1722F600R910V05
Drives
v Firmware level
ESM
v ESM card firmware level
Physical View pane
Select a procedure to view the firmware level from the Physical View pane of the
Storage Subsystem Management window.
To obtain the controller firmware level:
Right-click the Controller icon in the Physical View pane of the Storage
Subsystem Management window and select Properties. The Controller
Enclosure properties window opens, and the properties for that controller
are shown.
You must perform this step for each individual controller.
To obtain the ESM firmware and drive enclosure component firmware levels:
1. In the Physical View pane of the Storage Subsystem Management
window, click the Drive Enclosure Component icon (the icon farthest
to the right). The Drive Enclosure Component Information window
opens.
2. Click the ESM icon in the left pane. The ESM information is shown in
the right pane of the Drive Enclosure Component Information window.
3. Locate the firmware level of each ESM in the drive enclosure.
You must perform this step for each storage enclosure.
Upgrading ESM and controller firmware
Use the information in this section to upgrade the ESM and controller firmware in
the source and target storage subsystems before you start the migration procedure.
To upgrade ESM and controller firmware, complete the following steps:
1. Upgrade the DS Storage Manager software to the latest version. For more
information, see the applicable IBM System Storage DS Storage Manager
Installation and Support Guide. To access the latest document, go to
http://www.ibm.com/systems/support/storage/disk/.
Note: To maintain compatibility, update the multi-path software on the host
server to the level that is supported by or released with the controller firmware
that you intend to download. For details about software compatibility, see
http://www.ibm.com/systems/support/storage/config/ssic/index.jsp.
2. Upgrade the storage enclosure ESM firmware. You can use DS Storage Manager
and controller firmware to update the ESM firmware while the storage
subsystem is processing I/O from the host server if the ESM firmware
download is performed to only one storage enclosure at a time. If you select
6 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
multiple entries in the ESM firmware download window for ESM firmware
download, you must quiesce I/O operations from the host servers before you
start the ESM firmware download process.
Note: Even though the storage subsystem supports controller and ESM
firmware upgrade while the storage subsystem processes I/O from the host
server, schedule controller and ESM firmware upgrades to occur during time
periods of low I/O between the storage subsystems and host servers.
3. Upgrade the controller firmware and NVSRAM. See Table 2 on page 5 and step
1 on page 6.
Note: See the readme file in the DS Storage Manager controller firmware
package that is associated with the applicable host operating system
environment for a support statement about the concurrent controller firmware
download .
Attention: Before you upgrade the controller firmware, see the readme file that
comes with the firmware for any special prerequisite tasks, ESM firmware, and
stepping-stone controller firmware that must be installed before the controller can
be upgraded. Failure to do so might result in loss of data availability. There are
certain minimum controller firmware level requirements that are associated with
various storage enclosures. See “Intermixing storage enclosures” on page 11,
“Intermixing storage enclosures” on page 11, and “Intermixing storage enclosures”
on page 11 for related information.
Drive migration limitations
In general, drives with existing data and logical drives configuration can be
migrated between storage subsystems that have the same level of controller
firmware installed or from a source storage subsystem that has an older version of
controller firmware installed than the one installed in the destination storage
subsystem. However, it is a best practice to limit the drive migration between
storage subsystems of the same level of controller firmware. The reason is that
different versions of controller firmware might implement different metadata
(DACstore) data structures to store the logical drive information. These metadata
(DACstore) data structures are not interchangeable. If a newer version of controller
firmware changes the metadata structure, all of the controller firmware versions
older than this controller firmware cannot decode the metadata structure to obtain
the logical drive information in the migrated drives and recreate them in the
destination storage subsystem. But, this newer version of controller firmware
normally includes the code to decode the previous metadata structure that it
changes to allow the migration of the drives in the storage subsystem with older
version of controller firmware. For more information about drive migration
limitations based on controller firmware levels, see Table 4 on page 8.
Only the logical drive and array definitions along with their data can be migrated
between storage subsystems. The Host-to-LUN mappings and the configuration
definition and data of the copy services premium features like FlashCopy,
VolumeCopy and Remote Mirroring must be removed prior to drive migration.
Depending on the version of the installed controller firmware, the LUN mappings
and the copy service configuration information can be saved in script file so that
they can be recreated in the destination storage subsystem. If the drives with data
cannot be migrated to the destination storage subsystem, one has to backup the
data in those drives to a different medium like tape and then restores the data into
the destination storage subsystem.
Chapter 1. Prerequisites to adding capacity and hard disk drive migration 7
Table 4. Drive migration limitations based on controller firmware levels
Source storage
subsystem controller
firmware level
7.8x.xx.xx or later 8.2x.xx.xx Drives can be
7.7x.xx.xx 7.8x.xx.xx or later Drives can be
7.8x.xx.xx or later 7.8x.xx.xx Drives can be
7.8x.xx.xx or later 7.7x.xx.xx or earlier Drives cannot be
Destination storage
subsystem controller
firmware level Action Notes
migrated.
migrated into the
destination storage
subsystem when it is
powered up and
optimal.
migrated.
migrated.
Drives with disk pool
configuration cannot
be migrated between
storage subsystems.
1. Drives with disk
pool
configuration
cannot be
migrated between
storage
subsystems.
2. DS3500 and
DCS3700 storage
subsystems with
controller
firmware version
7.86 or later
support T10PI. If
an array has been
configured and
T10PI enabled, it
cannot be
migrated to a
storage subsystem
with controller
firmware version
7.84 or earlier.
Verifying hard disk drive model compatibility
Use the information in this section to verify hard disk drive compatibility before
you start the migration procedure or to add hard disk drives.
v Do not use the drive product identifier as the only source to determine drive
compatibility for a subsystem. Drives that have the same product identifier
might require a different mounting tray or interposer in a storage subsystem.
Instead, use the drive option part number or drive CRU part number to check
for drive compatibility in a storage subsystem.
v Ensure that the drives can operate at the interface speed of the drive
loop/channel. If not, the drives are in Bypassed mode or are not identified by
the controllers. In a few instances, inserting a drive with the wrong drive
interface speed causes problems in the drive loops which could result in loss of
data access.
8 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
v Some storage subsystem and expansion enclosures can support different drive
interface speeds. Ensure that these storage subsystem and expansion enclosure
speed switches are set to the correct values to support the drive interface speeds.
Intermixing storage subsystems and expansion enclosures that support different
drive interface speeds is not supported. The drive loop/channel must be set to
support the lowest drive interface speed.
v Do not install a DS3000, a DS4000, or a DS5000 storage subsystem drive in a
DCS Series storage subsystem.
v T10PI capable drives require controller firmware version 10.77.xx.xx and later.
v The DCS3700 storage expansion enclosure is supported with both the IBM
System DCS3700 and DCS3860 Storage Subsystems with Gen2 Controllers.
v The EXP3800 storage expansion enclosure is supported with the DCS3860
storage subsystem with Gen2 Controllers only.
v For information about supported drive capacity and interface and drive speeds,
contact your IBM marketing representative or authorized reseller, go to
http://www.ibm.com/systems/support/storage/disk/, or see the latest Storage
Subsystem announcement.
Viewing the product ID and model of a hard disk drive
Use the information in this section to view the product ID and model of a hard
disk drive by using the storage server profile before you start the migration
procedure or to add hard disk drives. You can determine the product ID and
model of a hard disk drive from the storage server profile through the menu
option in the Subsystem Management window. To get the profile, in the Subsystem
Management window, click Storage Subsystem ->View Profile When the Storage
Subsystem Profile window is shown, click the Drives tab and scroll down to view
the product ID and model of a hard disk drive.
See Table 5 on page 10 for a sample profile that indicates the product ID of the
drive in bay 12 of enclosure ID 1 as ST3146756FC F. The Speed and Current Data
Rate fields show that this drive is a 15 krpm drive and is operating at 4-Gbps
Fibre Channel date rate. In addition, the drive is security capable and in a secure
state that allows input and output processing to the drive from the controller.
Chapter 1. Prerequisites to adding capacity and hard disk drive migration 9
Table 5. Snapshot of profile information identifying the product ID of the drive in bay 12 of
enclosure ID 1
HOT SPARE COVERAGE:
The following arrays are not protected: 0
Total hot spare drives: 0
Standby: 0
In use: 0
DETAILS
Drive at Enclosure 1, Slot 12
Status: Optimal
Mode: Assigned
Raw capacity: 136.732 GB
Usable capacity: 136.232 GB
World-wide identifier: 20:00:00:1d:38:1d:1d:d0:00:00:00:00:00:00:00:00
Associated array: 0
Port Channel ID
0 1 11/0xD4
1 5 11/0xD4
Security Capable: Yes
Secure: Yes
Read/write accessible: Yes
Security key identifier: 27000000600A0B80004777A40000717049A6B239
Speed: 15,015 RPM
Current data rate: 4 Gbps
Product ID: ST3146756FC F
Firmware version: E097
Serial number: 3QN07PR700009912TLHK
Vendor: IBM-SSG
Date of manufacture: October 16, 2008
Drive at Enclosure 1, Slot 13
Status: Optimal
Mode: Assigned
Raw capacity: 136.732 GB
Usable capacity: 136.232 GB
World-wide identifier: 20:00:00:1d:38:1d:1e:7b:00:00:00:00:00:00:00:00
Associated array: 0
Port Channel ID
0 5 12/0xD3
1 1 12/0xD3
Security Capable: Yes
Secure: Yes
Read/write accessible: Yes
Security key identifier: 27000000600A0B80004777A40000717049A6B239
Speed: 15,015 RPM
Current data rate: 4 Gbps
Product ID: ST3146756FC F
10 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Bringing storage subsystems and drive loops into optimal state
You can add or migrate storage enclosures only while the storage subsystem is
turned on and in optimal state. To bring storage subsystems and drive loops into
optimal state, complete the following steps:
1. Bring the storage subsystem to Optimal state before you reconfigure it with
new hardware.
2. Use the DS Storage Manager Client program to display the status of the storage
subsystem and to correct any problems that might cause the storage subsystem
to enter Needs Attention state.
3. Verify that all indicator lights on the storage subsystem are in Optimal state.
4. Use the Read_Link_Status function of the DS Storage Manager Client program
and the storage subsystem MEL to verify that all components in the drive loop
are in Optimal state. (Optimal state indicates that there are no drive loop
component errors in the event log and no errors in the Read_Link_Status
window.) Use the drive channel diagnostics to determine whether the drive
loop/channel is in Optimal state. For more information about the RLS and
drive channel diagnostics if they are supported by the installed version of your
controller firmware, see the Subsystem Management window online help of the
DS Storage Manager Client program.
5. If the arrays are in degraded state because of a failed drive, correct the problem
before migration.
Note: If necessary, contact IBM support for assistance with event log
interpretation.
Before you add drives or storage enclosures, verify that the storage subsystem is
not performing any of the following tasks:
v Dynamic logical drive capacity expansion
– Dynamic logical drive expansion (DVE)
– Dynamic capacity expansion (DCE)
v Logical drive segment size modification
v Array RAID-level modification
v User-initiated array redundancy checking (click Array > Check Redundancy in
the Storage Subsystem Management window)
v Remote mirror logical drive synchronization
v FlashCopy®or VolumeCopy logical drive creation
v Logical drive reconstruction or copyback (logical drive sparing)
Intermixing storage enclosures
This section describes general information about intermixing storage enclosures in
a storage subsystem. Use the information in this section to plan a storage
subsystem migration or to add hard disk drives.
For the DCS3700 with Gen2 Controllers, IBM supports the DCS3700 storage
expansion enclosure. For the DCS3860 storage subsystem, IBM supports both the
EXP3800 and DCS3700 storage expansion enclosures.
When you increase the capacity of your storage subsystem in either of these ways,
you might choose to add external drive enclosures of the same model and type or
of different types. IBM does not support the combination of every external drive
Chapter 1. Prerequisites to adding capacity and hard disk drive migration 11
enclosure type and model in every storage subsystem configuration. In addition,
not all controller firmware levels support all available storage enclosures or storage
subsystems.
In general, if a storage subsystem supports multiple storage enclosures with
different model numbers and machine types, you can connect the storage
enclosures to the storage subsystem on the same redundant drive loop/channel by
using the cabling rules that are described in the storage subsystem documentation.
As a best practice, group the storage enclosures by model and machine type when
you connect cables in the same redundant drive loop/channels. However, because
of storage enclosure architecture differences, there might be certain restrictions
when you connect some combinations of storage enclosures in the same drive
loop/channel.
Table 6. Storage enclosure compatibility with storage subsystems by model for DCS Series storage subsystems
Storage subsystem DCS3700 Expansion Enclosure EXP3800
DCS3700 with Gen2 Controllers
DCS3860 with Gen2 Controllers U U
Table 7. DCS3700 and EXP3800 expansion enclosures supported by controller firmware levels
Firmware level DCS3700 Expansion
07.84.xx.xx Yes No
07.86.xx.xx or later Yes Yes
U
EXP3800
Enclosure
Important: To avoid unpredictable results, do not change the speed of a drive loop
while the storage subsystem is turned on. Also, the storage enclosures must be
power cycled for the new speed setting to be recognized correctly.
To change the speed of a drive loop, complete the following steps:
1. Prepare applications for storage subsystem shutdown.
2. Shut down the storage subsystem.
3. Shut down the storage enclosures.
4. Change the storage enclosure speed settings.
5. Turn on the power to the storage enclosures.
6. Turn on the power to the storage subsystem.
7. Restore storage subsystem host application operations.
Note: For more information about turning on a storage subsystem and turning it
off, see the documentation that comes with your storage subsystem. For more
information, see http://www.ibm.com/systems/support/storage/disk/.
12 IBM System Storage DCS Series with Gen2 controllers Hard Disk Drive and Storage Enclosure Installation and Migration
Guide
Chapter 2. Adding or migrating hard disk drives
To add hard disk drives to the storage subsystem configuration or place the drives
(that made up a RAID array) in different drive bays, see the following sections:
v To add new hard disk drives to an existing storage subsystem, see “Adding new
hard disk drives” on page 14.
Note: Any hard disk drive might contain configuration data. Unless you intend
to migrate drives from another storage subsystem (retaining its configuration
data), always use this procedure to add hard disk drives to an existing storage
subsystem configuration.
v To add new unassigned drives in different drive bays, see “Adding new hard
disk drives” on page 14.
v To migrate drives from one storage subsystem configuration to another, see
“Migrating hard disk drives” on page 15.
v To rearrange the drives (that made up a RAID array) in different drive bays in
the same storage subsystem, see “Migrating arrays within the same storage
subsystem” on page 21.
Before you begin, review Chapter 1, “Prerequisites to adding capacity and hard
disk drive migration,” on page 1.
Considerations
The following notes describe information that you must consider when you add a
hard disk drive to a controller or a storage enclosure:
v Observe proper electrostatic discharge (ESD) procedures when you handle
electronic equipment. For more information, see “Handling static-sensitive
devices” on page 14.
v Never alter the physical configuration of a storage subsystem while the power is
turned off unless you are instructed to do so as part of a configuration
procedure. Specifically, never attach storage components to, or remove storage
components from, a configured storage subsystem while the power is turned off.
v Updated readme files contain important configuration and procedural
information that supersede information in this document. Always check the
readme file before you perform any procedure or activity described in this
document. To access the most recent readme file, see “Finding Storage Manager
software, controller firmware, and readme files” on page 57.
v Before you migrate hard disk drives, complete the following steps to establish
drive model compatibility:
1. Check the drive CRU form factor options.
2. If the form factors are not the same, there are no replacement parts such as
bezels and drive trays. For more information, see the announcement letter,
the Installation, User's, and Maintenance Guide for your storage subsystem, and
your IBM marketing representative or authorized reseller.
3. If the form factors are the same, check to determine whether the drive is
supported by the storage subsystem.
4. Ensure that the drive can operate at the storage subsystem drive
loop/channel Fibre Channel or SAS speed. For more information, see the
© Copyright IBM Corp. 2008, 2015 13
Loading...