Verify that the arrays are still visible and online.
The
migration add
command fails to start a
job.
Array bandwidth is a source-only feature. Make sure that
the bandwidth setting has been configured on the array
that contains the source LUN. If the setting is configured
on the array holding the destination LUN, no effect is
seen.
Setting the array bandwidth does not cause any
change in the data transfer rate in
show perf
output.
Ensure that both the MPX200 ports are correctly masked
for the LUN under consideration, and that both controllers
are correctly zoned with both the MPX200 Fibre Channel
ports.
Migration failover to active path does not occur.
Make sure that the controller ports zoned for the accessing
source and destination array LUNs also own the respective
LUNs. In other words, if the source LUN is being accessed
by the MPX200 through a controller port belonging to
Controller A while the LUN is actually owned by Controller
B, the MPX200 will allow you to configure a migration
job but may not be able to do any data access operations
for that LUN.
A migration job goes into running state, halts at
the
Running (0% complete)
state for awhile,
and then fails.
The MPX200 sees the same LUN ID being presented for
two different LUNs. This can happen if you try to change
the set of LUNs exposed to the MPX200 without removing
associated migration jobs and zoning out the original set
of LUNs.
In order to keep the LUN object database maintained by
the MPX200 in a sane state, ensure that you explicitly
acknowledge or remove all migration jobs associated
with a set of LUNs that need to be removed. Only after
that should you assign the new set of LUNs to the MPX200
host group. You must refresh the GUI three times to
rediscover the new set of LUNs.
The MPX200 displays the following messages:
Array reconfiguration detected. Refer
to user manual for trouble shooting.
WWULN:
60:05:08:b4:00:05:4d:94:00:00:c0:0
0:00:2c:00:00 and WWULN:
60:05:08:b4:00:05:4d:94:00:00:c0:0
0:00:2d:00:00 mapped on same LUN ID:
8.
Marking LUN offline: LUN ID: 8 WWULN:
60:05:08:b4:00:05:4d:94:00:00:c0:0
0:00:2d:00:00
The MPX200 sees the same WWULN through different
LUN IDs from the same array. This can happen if the two
MPX200 ports are placed in different host groups and
you inadvertently assign different LUN IDs while presenting
a specific LUN to the two host groups. To avoid this situ-
ation, put both MPX200 ports under the same host group.
The MPX200 displays the following messages:
Array reconfiguration detected. Refer
to user manual for trouble shooting.
WWULN:
60:05:08:b4:00:05:4d:94:00:00:c0:0
0:00:2d:00:00 mapped on different LUN
IDs: 8 and 9.
Marking LUN offline: LUN ID: 8,
WWULN:
60:05:08:b4:00:05:4d:94:00:00:c0:0
0:00:2d:00:00. LUN with ID: 8 is not
presented
Offline Data Migration
246
Содержание Storageworks 8100 - enterprise virtual array
Страница 20: ...20 ...
Страница 30: ...MPX200 Multifunction Router overview 30 ...
Страница 47: ...Figure 27 iSCSI controller options Remove controller MPX200 Multifunction Router 47 ...
Страница 48: ...Managing the MPX200 using HP Command View EVA 48 ...
Страница 59: ...Figure 32 Virtual disk properties Figure 33 Host details MPX200 Multifunction Router 59 ...
Страница 112: ...MPX200 iSCSI configuration rules and guidelines 112 ...
Страница 219: ...Load Balancing Enabled Array License Not Applied MPX200 Multifunction Router 219 ...
Страница 222: ...Controller Id WWPN PortId Path Status 0 20 78 00 c0 ff d5 92 e5 02 04 00 Current Optimized Offline Data Migration 222 ...
Страница 248: ...Offline Data Migration 248 ...
Страница 258: ...Diagnostics and troubleshooting 258 ...
Страница 306: ...Command referencecommand reference 306 ...
Страница 330: ... Blade number 1 or 2 Simple Network Management Protocol setup 330 ...
Страница 368: ...Saving and restoring the MPX200 configuration 368 ...
Страница 402: ...Data migration best practices 402 ...
Страница 408: ...408 ...