Can you confirm that all of the follow requirements are met?
- The source and destination vCenter Server instances and ESXi hosts must be running version 6.0 or later.
- The cross vCenter Server and long distance vMotion features require an Enterprise Plus license. For more information, see Compare vSphere Editions.
- When using the vSphere Web Client, both vCenter Server instances must be in Enhanced Linked Mode and must be in the same vCenter Single Sign-On domain so that the source vCenter Server can authenticate to the destination vCenter Server.
- Both vCenter Server instances must be time-synchronized with each other for correct vCenter Single Sign-On token verification.
- For migration of compute resources only, both vCenter Server instances must be connected to the shared virtual machine storage.
Thank you for your response,
- source is running on 6.5 in our test scenario. Destination 6.7
- Enterprise Plus License is activated
- both vCenters are in the same SSO Domain and we tried the migration with the cross vcenter migration utility from vmware and via powercli
- both vCenters are using the same timeserver but i will check if they are synchronized
- source and destination are using different storage resources
Okay. So, the basic requirements should be fine.
new management network, old management network, new vMotion network and old vMotion network are all different VLANs.
If the source and destination vMotion network are different, you need to enable the vMotion TCP/IP Stack and must not use the default TCP/IP Stack.
To have the vMotion traffic routed across IP subnets, enable the vMotion TCP/IP stack on the host. See Place vMotion Traffic on the vMotion TCP/IP Stack of an ESXi Host.
is it configured that way?
all hosts used the default gw of the management network for vmotion.
it its working for me now