HP 3PAR Online Import for EMC Storage Data Migration Guide

Retrieve and Display data - 1 Iteration(s) In 0.014121 Seconds
Please press enter key to continue...
Troubleshooting Issues
Not able to add a source EMC Storage system
Possible causes:
• The EMC SMI-S Provider is running an unsupported software version.
• Invalid source array UID specified when executing the addsource command (no error
message displayed).
• Invalid user and/or password provided for EMC SMI-S Provider.
• Invalid IP Address or Port (secure/unsecure) provided for EMC SMI-S Provider.
• EMC SMI-S Provider has client IP address filtering enabled and OIU server is not on the trusted
IP address list.
• EMC SMI-S Provider is not managing the EMC Storage system.
• HP OIU server and EMC SMI-S Provider do not have network connectivity.
• EMC SMI-S Provider and EMC Storage system do not have network connectivity.
• The EMC Storage system is running an unsupported firmware version.
Solution: Check each of the above conditions to identify which may be causing the problem, then
resolve it.
Not able to createmigration
Possible causes:
• Duplicate volumes exist. This may occur if either a virtual volume with same name or with the
same WWN exists on the destination storage system.
• A host on the destination storage system has a duplicate name.
• The destination storage system does not have enough capacity.
• The EMC SMI-S Provider is running an unsupported software version.
• EMC SMI-S Provider username/password have changed since source storage system was
added.
• EMC SMI-S Provider is not managing the EMC Storage system.
• HP OIU server and EMC SMI-S Provider do not have network connectivity.
• EMC SMI-S Provider and EMC Storage system do not have network connectivity.
• The EMC Storage system is running an unsupported firmware version.
• LUNs or Host provided are in an invalid storage group configuration.
• LUN(s) not eligible for migration (must be Fibre Channel, cannot be replication LUN or
reserved).
• Operational state of EMC Storage system.
• No connection between source and destination storage systems.
• Wrong migration type is used.
Solution: Check each of the above conditions to identify which may be causing the problem, then
resolve it.
Troubleshooting Issues 53