HP 3PAR Online Import for EMC Storage Release Notes

DescriptionItemIssue ID
The OIU reports importvv command “Failed” but the migration will still proceed.
The OIU does not check for available space before starting a migration.
Migration will proceed
after “Failed” message
719
Conditions: An 11TB LUN existed in a CPG and an attempt was made to import
two 6TB virtual volumes into the CPG.
Behavior: The OIU appeared to accept the task without issue. The migration
proceeded normally but failed after several hours (>11).
Cannot add source to 3PAR destination when it already exists with a different WWN.
The createmigration command adds the host being migrated to the destination
Unable to add source
host if WWN already
exists on destination
734
HP 3PAR StoreServ Storage system. If the host already exists with the same name
and WWN, then you can specify the same host for migration and it gets reused.
However, if the host specified for migration already exists on the destination 3PAR
system without a full match (i.e. only name or WWN match), the OIU throws an
error that the host already exists on the destination HP 3PAR StoreServ Storage
system.
The createmigration command hangs due to SMI-S communications. This issue
was found with SMI-S Provider running on a Windows 2008 R2 server. Problem
createmigration
command hangs
775
symptom is that the createmigration command never returns. To verify that this
is an SMI-S Provider issue you can: , , run the refsys command (refsys command
normally returns after approximately 30 seconds on a SMI-S system that is connected
to three hosts)
1. Login to the SMI-S provider server
2. Run testsmisprovider.exe
3. Run the refsys command (refsys command normally returns after approximately
30 seconds on a SMI-S system that is connected to three hosts)
4. If this error appears, then the issue is verified:
Example 2 Connection timed out
Error: connection timed out
In 1200.000908 Seconds
Workaround:
Restart SMI-S Provider
A problem occurs when the SMI-S Provider managing more than one storage system
that has the same host in different storage groups on each storage system. This
SMI-S Provider error792
happens when the OIU asks the SMI-S Provider to retrieve host information. With
OIU asking for a specific host, if there is the same host on two different storage
systems and you ask to retrieve the associated LUNs, you will get LUNs on both
source storage systems which causes the problem.
Workaround: The SMI-S Provider should not manage multiple arrays where the
same host is provisioned in different storage groups. In a situation where the SMI-S
Provider is installed only for migration, then only the storage system being migrated
should be added. In a situation where the SMI-S Provider is already installed and
being used by another application, a separate SMI-S Provider should be installed
for the migration.
Known Issues with the HP 3PAR Online Import Utility for EMC Storage 5