d.
Connect the new storage subsystem to the IBM DS Storage Manager Client
either through the out-of-band method by using the applicable TCP/IP
addresses of the controller Ethernet management ports, or through the
in-band method through Fibre Channel connections.
Note:
The new storage subsystem identifies itself as the machine type that
it replaced until you download the applicable NVSRAM firmware for the
new storage subsystem.
e.
If there are FDE drives that were configured as part of a secured array, use
the security key backup file to unlock the secured (locked) FDE drives.
Note:
If all of the drives in the original storage subsystem are security
enabled FDE drives (FDE drives that were defined as part of secured
arrays), both controllers are booted to No Drives Found state. This is
because the controllers cannot unlock the drives without the applicable
security key. When the security enabled FDE drives are unlocked, both
controllers are rebooted so that the controllers can read the configuration
data that is stored in the drives.
If all the FDE drives are from storage subsystems that operate in external
license key management mode, use the security key file you saved (see step
3g on page 48) to unlock the secured FDE drives.
f.
Ensure that the new storage subsystem configuration is in Optimal state and
that all of the drives are identified. Use the Recovery Guru in the DS Storage
Manager Client Subsystem Management window to resolve any Needs
Attention conditions.
g.
Update the controller firmware of the new storage subsystem to the latest
available version, if required.
h.
Download the applicable NVSRAM firmware for the new storage
subsystem.
i.
Ensure that all of the arrays are online and in Optimal state.
j.
If there are any ghost hard disk drives or hard disk drives that are indicated
as incompatible, or if any of the following conditions persist, contact IBM
support for assistance:
v
The Empty Drive Bay icon (
) is displayed for the drive bay into which
you inserted the migrating drive.
v
The Failed Unconfigured Drive icon (
) or the Failed Configured
Drive
icon (
) is displayed for the drive bay into which you inserted
the migrating drive.
v
Array configuration data on the drives that you added is incomplete.
v
You cannot import the array.
k.
Use the Enable Identifier storage subsystem premium feature to generate
and apply premium feature keys to remove Out of Compliance errors on
enabled premium features from the original storage subsystem. See the
instructions that come with the Enable Identifier premium feature for
information about generating the premium feature keys.
l.
Extract the applicable SMCli commands in the configuration script file that
you saved in step 4c on page 50 to re-create the FlashCopy images,
VolumeCopy images, remote mirror relationships, and host-to-LUNs map
definitions, as required.
52
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: ......
