Migrating aliases, Defining base and alias devices, Considerations for defining the – HP StorageWorks XP Remote Web Console Software User Manual
Page 34
Migrating Aliases
The alias assigned to the base device must be canceled and reassigned in order to migrate it.
WARNING!
When migrating aliases, you must confirm that the number of requests to the base
device that the alias is moved from, is less then 50 IOPS by acquiring performance information
using RMF (Resource Measurement Facility Report Analysis) etc. before migrating the alias. If the
alias is migrated when there are many requests to the base device, the process performance may
decline in the worst cases.
To migrate aliases to volumes in the connected storage system:
1.
Execute step
to
of Canceling Aliases (see
).
2.
Execute step
of Assigning Aliases (see
).
3.
Select Apply in the Compatible PAV window. When the set Compatible PAV confirmation
dialog box appears, click OK to migrate the aliases as specified. To cancel your request, click
Cancel.
When migrating aliases included in another LDKC, change the LDKC by step
of
, and then execute step
to
.
Considerations for Defining the Storage System Devices to the Host System
This section simply describes the considerations when you define the device from the host system.
The serial number of the storage system differs from the LDKC serial number which the host
recognizes per LDKC. The device address which is specified from the host differs from the LDEV
number (CU:LDEV) of the subsystem.
IMPORTANT:
For CC, the 2105 or 2107 controller emulation type cannot be intermixed with
other emulation types within the storage system. If the storage system has existing CC volumes and
you want to implement Compatible PAV, you must change to 2105 or 2107 emulation as follows:
1.
Stop all Concurrent Copy jobs.
2.
Change the DKC emulation type of all CHA packages in the storage system to I-2105 or
I-2107.
3.
Restart Concurrent Copy jobs.
Compatible PAV operations require that one SSID be set for each set of 256 LDEVs.
Defining Base and Alias Devices
The unit address mapping for base and alias devices must be defined to the host operating system
and must match the address mapping defined at the Remote Web Console computer. If the mappings
do not match, serious failures can occur during data processing.
shows examples
of mappings between base devices and alias devices.
Table 8 Mapping Between Base Devices and Alias Devices
x00-x3F:Alias
(D)
x00-x7F:Alias
(C)
x00-x3F:Base
(B)
x00-x3F:Base
(A)
x40-x7F:Base
x80-xFF:Base
x40-x7F:Alias
x40-xFF:Alias
x80-xBF:Alias
x80-xBF:Base
xC0-xFF:Base
xC0-xFF:Alias
34
Performing Compatible PAV Operations