E troubleshooting – HP MPX200 Multifunction Router User Manual
Page 171
E Troubleshooting
lists some problems that may occur with the data migration service and provides
a possible reason or solution for each.
Table 25 Troubleshooting
Reason and Solution
Problem
Ensure that the zoning is correctly set up on the switches.
The show array command either:
Ensure that the show targets command is not showing
any entry for the array. If show targets is showing an
•
Does not show any array entities.
•
Does not show all the controller ports zoned in with the
MPX200.
entry for the target array, it means that the MPX200 is
zoned correctly, but no data LUNs are mapped to the
MPX200 ports. Add masking for the required data LUNs
so that they are seen by the MPX200. For more information,
see
.
By default, the target type attribute for an array is
Unknown. Use the set array command to set it
appropriately.
The migration add command does not show any
source or destination array.
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
Setting the array bandwidth does not cause any change
in the data transfer rate in show perf output.
that contains the source LUN. If the setting is configured
on the array holding the destination LUN, no effect is seen.
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 FC ports.
Migration failover to active path does not occur.
To remove a remote peer, first remove the remote
presentations and the remote peer entry from both the local
Resetting the local MPX200 router (by issuing the reset
factory
and reboot commands) deletes its own
and remote MPX200 routers, and then reset the MPX200s
as follows:
database, but does not delete user-configured data on the
remote router. Because the presentations are still active on
the remote MPX200, resetting prevents remote peer
1.
On both MPX200 routers, remove presentations by
issuing the targetmap rm command.
removal until you delete presentations from both the local
and remote MPX200.
2.
On both MPX200 routers, remove the remote peer by
issuing the remotepeer rm command.
3.
On both MPX200 routers, reset the MPX200 by issuing
either the reset mappings or the reset factory
command.
4.
On both MPX200 routers, restart the blade firmware
by issuing the reboot command.
If you cannot remove presentations and remote peers, issue
the reset mappings command to remove
user-configurable settings on the router.
Make sure that the controller ports zoned for the accessing
source and destination array LUNs also own the respective
A migration job goes into running state, halts at the
Running (0% complete) state for a while, and then fails.
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 will not be able to do any data access operations for
that LUN.
The MPX200 sees the same LUN ID being presented for
two different LUNs. This situation can occur if you try to
The MPX200 displays the following messages, for example
(your WWULN and LUN ID will be different):
change the set of LUNs exposed to the MPX200 without
Array reconfiguration detected. Refer to
removing associated migration jobs and zoning out the
original set of LUNs. To keep the LUN object database
user manual for trouble shooting.
maintained by the MPX200 in a sane state, ensure that
WWULN:
171