Cross vCenter vMotion Utility usage problem.

[golfradio]

Hello all,

I'm using the Cross vCenter vMotion Utility v2.2 to move vms from vcsa 6.0 to vcsa 6.5 (both use embedded psc).  I am able to transfer from 6.0 to 6.5 pretty much without issue.  However going from 6.5 back to 6.0 doesn't seem to work.  Here is a typical error...

Please ignore the source and target site names as I labeled them as going from 6.0 to 6.5.  In the info field it speaks about the dvportgroup-347 network device not present.  This is true but I do not have a dvportgroup-347 configured for either vcsa. 

Anyone else using this fling?  Any problems?  VISHALGUPTA​ williamlamb​

Thank you...

Regards,

Mark Johnsen

[daphnissov · Accepted solution]

It is not supported in any configuration to go from 6.5 back to 6.0 (unless at 6.5 U2 and destination is 6.0 U3). This isn't a limitation of the Fling utility but of vSphere. See the following KB for a complete matrix.

https://kb.vmware.com/s/article/2106952

[golfradio]

Thanks for your prompt reply, daphnissov...

I did read this kb.  I did not believe there was going to be any switch upgrade from 6.0 to 6.5 but I guess there is.

I saw this and assumed the dswitch to dswitch would be fine.  Not sure how (or why) the fling would state dvportgroup-347 if not already created.

[daphnissov]

This is true only for forward migrations and not reverse. If your vSphere 6.5 environment uses a 6.5 vDS then movement to to a vSphere 6.0 environment using a 6.0 vDS would be problematic.

[golfradio]

One item I neglected to mention is that I exported the dswitches from vcsa 6 and imported into 6.5.  Would the importation of those switches automatically update them to the new (higher) level?

[daphnissov]

Not necessarily, but at what revisions are your two vCenters?

[golfradio]

Version 6.0.0 Build 3617395 and Version 6.5.0.13000 Build 8024368 (U1g).

[daphnissov]

Then, as I stated earlier, you are not at the required versions to perform a 6.5 -> 6.0 migration.

[golfradio]

I'll go with that, daphnissov.  Again, thanks for your time and consideration.

Mark Johnsen