Table 4. Drive migration limitations based on controller firmware levels
Source storage
subsystem controller
firmware level
Destination storage
subsystem controller
firmware level
Action
Notes
7.8x.xx.xx or later
8.2x.xx.xx
Drives can be
migrated.
Drives with disk pool
configuration cannot
be migrated between
storage subsystems.
7.7x.xx.xx
7.8x.xx.xx or later
Drives can be
migrated into the
destination storage
subsystem when it is
powered up and
optimal.
7.8x.xx.xx or later
7.8x.xx.xx
Drives can be
migrated.
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.
7.8x.xx.xx or later
7.7x.xx.xx or earlier
Drives cannot be
migrated.
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
Summary of Contents for System Storage DCS Series
Page 89: ......
