not able to migrate VM from one clusster to other cluster in data center

[iamphane]

Hi

we are running with vcenter 5.1 esxi 5.1 vesrion . there are two clusters in a datacenter .two clusters configured on different dv switches. (same vlans ,management networks,kernal networks ,switch version etc)

now when i tried to migrate VM's from cluster to other cluster giving error saying "currently connected network interface network adapter1 uses network dv switch (uuid xxxxxxx); which is not accessble "

only cold migration is working . seems there was not communication between two switches ,.Now if i want to perform hot migration between two clusters what i neeed to do ? what are the possible ways ? is it possible or not ? please suggest.

[NagangoudaPatil]

As per error it is related to network configuration, need to check with network team on "VLAN trunk", could you attach some screenshots to verify dvSwitch configuration.

[grasshopper]

This is the expected behavior and is _not_ indicative of a vlan/network issue.  The common work-around for this is to create a temporary vStandard Switch (vSS) and add a portgroup to it using the desired vlan.  Ensure that it is named the same (case sensitive) on both the source and target hosts and you should be good to go.  This implies that you have spare NICs or can remove at least one NIC from the main distributed switch for this interim solution.

[kermic]

vMotion between different dvSwitches is currently not supported.

As per Host management guide (http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.vcenterhost.doc/GUID-3B41119A-1276-404B-8...)

If you are using vSphere Distributed Switches for networking, ensure that source and destination hosts are members of all vSphere Distributed Switches that virtual machines use for networking.

What you could do is use the same dvSwitch across both clusters, assuming your physical infrastructure allows that.

[bhaskarmano45]

Hi ,

We will split issues into sub groups.

1. Is issue with 1 VM or all VM's?

2. did you tried VMotion between clusters on any other VM's?

3. Verify Network label's are same.

[iamphane]

For all VM's

source and destination vlan id number is same but the given name is different for (managment ,kernal,vlans)

source vlan name is n1k-ipc-xx and destination name is n1k-bgr-xx was this causing issue  ?

[iamphane]

And its nexus1000v dv switch not a standard switch .

[bhaskarmano45]

Hi,

Yes, please change name to unique on source and destination.

[kermic]

If the VM is connected to portgoup named "Portgroup-A", vMotion looks for a portgroup with exactly same name on destination host. In case if one can't be found, validation check fails.

Now let's try to visualise it a bit:

vMotion works within a single vCenter Server inventory.

You're saying that you have 2 clusters, let's say "Cluster-A" and "Cluster-B". I'm assuming they're both under same vCenter instance.

Cluster-A has hosts Host-A1 and Host-A2

Cluster-B has hosts Host-B1 and Host-B2

Now you create a dvSwitch named "dvSwitch1" and attach hosts from Cluster-A, that is Host-A1 and Host-A2, power on a VM there, attach it to portgroup "Portgroup-A", which has been created on "dvSwitch1". Life's good so far.

You go ahead and start creating a dvSwitch for Cluster-B, to attach it's hosts (Host-B1 and Host-B2). You recall something about identical naming of switches / portgroups and try to give the new dvSwitch the same name - "dvSwitch1", but that picky vCenter doesn't allow you to do that, complaining that there already is an object with the same name. Essentially you change it and name the new dvSwitch "dvSwitch2" and it finally gets created. Now we need to create a portgroup on dvSwitch2, preferably named "Portgroup-A" because that would allow vMotioning VMs. But guess what, that picky thing again complains that the name is already in use and doesn't allow you to get to the magic button called "Finish" in the wizard. You think of few heavy words and finally change the name of the portgroup to "Portgroup-B". vCenter is happy because there is no naming conflict, you're happy (so far) because you have created a dvSwitch and a portgroup for each cluster.

Now there is a running VM, living on Host-A1, connected to Portgroup-A. You attempt to live-migrate it to Host-B1, validation check kicks in and tries to verify wether Host-B1 has access to portgroup "Portgroup-A" and it doesn't because Host-B1 is not connected to the dvSwitch1 where Portgroup-A actually exists, so the check fails, gives you the error message that you posted in very beginning of this thread and you can't proceed.

At this point you have probably already figured out a solution, which is attaching Hosts A1, A2, B1 and B2, respectively hosts from both clusters to the same dvSwitch, however that's a lot easier said than done as it involves quite a bit of design and planning, which might get little complicated if both of your clusters are already running production workloads.

I hope I managed to clarify it at least a bit.