Destination Cluster is not visible while migrating VM

[wasilraye]

Dear Friends,

I want to migrate VM from cluster A to cluster B all host are version 6.5 both cluster in same vCenter.

but while migrating can not see the destination cluster.

tried migrating VM in power off status but no luck.

Regards,

Wasil Raye

[IRIX201110141]

Datastore available on both cluster?

Regards,
Joerg

[wasilraye]

Thanks for the reply.

There is no datastore visibility between cluster A and B but i have permission on both the cluster.

Regards,

Wasil

[Scott Vessey]

Do you have datacenter level permissions?

[nachogonzalez]

As a requirement for cross cluster vMotion you need to have a shared datastore

Also the VM's portgroup backing vlan needs to be propagated on both source and destination site

[sjesse]

Thats not true,

Migration with vMotion in Environments Without Shared Storage

vMotion does not require environments with shared storage. This is useful for performing cross-cluster migrations, when the target cluster machines might not have access to the source cluster's storage. Processes that are working on the virtual machine continue to run during the migration with vMotion.

[jasmeetsinghsur]

For vMotion with out shared storage what is the port or network requirement?

[Scott Vessey]

Why not ask that question on your own thread?

Migration of virtual machines from vcenter 6.0 to vcenter 6.7 with new esxi hardware.

[jasmeetsinghsur]

I don't know the policies of VMware. If there is any guidelines please let me know to take care in future.

[Scott Vessey]

There aren’t any hard policies, but this topic is being discussed by multiple people in your own thread - so rather than asking on a loosely related thread it would seem to make more sense to keep your thread going.

[wasilraye]

Thanks for the reply friends.

Hello nachogonzalez​

("portgroup backing vlan needs to be propagated") you mean to say same port groups, vlan and label should be available on both cluster hosts (right now i am having Distributed switch in cluster A and Standard switch in cluster B both are in same VC and DC) please suggest.

[sjesse]

That means is there network connectivity betyween the clusters,  preferably there should be the same network. In my lab I use vlan 6

but it doesn't need to be the same switch, just the vmotion vmkernel adapters in cluster a need to be able to talk to vmotion kernel adapters in cluster b.

[wasilraye]

Thanks sjesse,

This will help me I will check and let you know.

Regards,

Wasil

[nachogonzalez]

Usually a port group is backed by a vlan propagated to all pNICs in the host.
So, If VM1 is on host1 in porgtgroup "VLAN400" and the backing VLAN is VLAN400 to other cluster you can move it to whatever portgroup you like but in order for that VM to keep network conectivity you will need to have VLAN400 propagated to any portgroup (doesn't mind the naming convention, if it is a vDS it will be the same on all hosts, if it is a vSS keep it the same since "portgroup" and "Portgroup" are different things to ESXi

Hope that works

[sjesse]

How close are the clusters, in the same datacenter or further aport? Do you have vmotion vmkernel adapters setup and can they communicate with each other.

[sjesse]

Also it would help if you share the error your seeing.