3Par Evaimport failed to admit volume on dest system

[Sylvester]

I have this issue with Evaimport to 3Par Tool about migration Vdisk on Ws2003 cluster environment with "minimal disruption"
"Failed to admit volume on dest. system"
Eva 6400 Xcs 11001100
3Par7200 Os 3.1.2 Mu3
The destination 3par is Ok:

• no Cpg space problem
• no duplicate WWN or VV name
• the required lun numer is available on host object
• source volume is visible to destination system on both path

Any idea to resolve this issue?

Thanks a lot.

Bruno

[RitonLaBevue]

When we try Peer Motion a couple of month ago (maybe around june 2013) there was an issue creating volumes on 3PAR.
It has been corrected some months ago.
Now you maybe have a look to HP release notes from Inform OS 3.1.2 but also with your CV version.

HP EVA P6000 to HP 3PAR StoreServ Online Import Best Practices
HP EVA to 3PAR StoreServ Online Import Migration Guide

And HP P6000 Enterprise Virtual Array Compatibility Reference §4.2

4.2 Supported Host Operating Systems and Migration Types for HP EVA to 3PAR
StoreServ Online Import
HP EVA to 3PAR StoreServ Online Import is supported when running HP P6000
Command View 10.2 or later to a 3PAR array running HP 3PAR Operating System 3.1.2
MU1 or later.
Additional information on Command View version requirements, 3PAR OS version
requirements, supported host operating systems and XCS controller software can be found
on the Single Point of Connectivity Knowledge (SPOCK) website:
http://www.hp.com/storage/spock.

Go to Software > Array SW: 3PAR > HP 3PAR Peer Motion Online Migration Host Support.
Note: P6000 Command View and 3PAR Management Console can co-exist on the same
server.

[Patrick]

You could also try upgrading the 3Par to 3.1.3 MU1, there are some enhancements for the EVA import in the later releases.

[murphy01au]

Hi

We used the HP EVA to 3PAR Online Import with great succes. But we did encounter a few problems and this was one of them. The cause of our issues was how the P6500 EVA was zoned to the 3PAR array.

There must be two unique paths between the source and destination storage systems. To create two paths, the two controller host ports on the source EVA must be zoned to two peer ports

The 8000/8100 arrays have four ports per controller and can meet this requirement, because two odd and two even ports per controller can zoned the 3PAR peer ports. However, the P6500 array only has two ports per controller, one on the ODD Fabric, one on the EVEN Fabric.

The P6500 Host Posts (HP) were originally zoned as Ctrl A/HP3 to one 3PAR peer port and Ctrl B HP3 to another 3PAR peep port on the ODD Fabric. The same was repeated on the EVEN fabric Ctrl A/HP4 and Ctrl B/HP4. This created four zones but with only one port per controller on each fabric.

I rezoned the P6500 array Host Ports so that the both ODD ports Ctrl A & Ctrl B/HP3 were in the same zone with the 3PAR peer port. This was repeated on the EVEN Fabric. Once the 3PAR could see two ports on one peer port it allowed the migration to proceed.

Sample zoning:

ODD Fbric SAN SWitch> zoneshow *P6500*
zone: P6500_CTRLAB_HP3__3PAR01_N0S1P1_ZONE
3PAR01_N0S1P1_ALIAS; P6500_CTRLA_HP3_ALIAS;
GPHSV15_CTRLB_HP3_ALIAS

EVEN Fabric SAN SWitch> zoneshow *P6500*
zone: P6500_CTRLAB_HP4__PAR01_N1S1P2_ZONE
3PAR01_N1S1P2_ALIAS; P6500_CTRLA_HP4_ALIAS;
P65000_CTRLB_HP4_ALIAS

P6500 to 3PAR01 Peer Ports

P6500-3PAR01-PEER-PORTS.JPG (39.51 KiB) Viewed 16509 times