Runing SCVMM 2012 SP1 rollup 2 on dedicated server. Two Hosts - 2012 Server connected via SMB to a 2012 File Server.
Each of the hosts and the file server has 6x 1Gbps NICs in a team.
I setup the Logical Networks within SCVMM and pushed them to the hosts, thus teaming the NICs. I currently have 6 different networks - Cluster, LiveMigration, SMB, Backups, DMZ, and Private.
So far everything is working great, I can migrate VM's between the hosts, and I can migrate storage back and forth from the hosts to the file server. Throughput is outstanding, and my NIC teams appear to be functioning properly.
In order to force the SMB traffic between the hosts and file server, I put entries in the hosts files on the Hyper-V servers for the IP of the File Server that is on my SMB network. This appears to be working, I can see traffic on the virtual NIC's for the SMB network.
I am having a problem with Live VSM migration. I should be able to migrate a VM that is on Host1 and stored on FileServer1 using Live VSM over to Host2 and stored locally on it's D:\ drive.
When I run the Migrate VM wizard, I see the transfer type Live (VSM) in the window, but my host has 0 stars. In the Rating Explanation, I get this error:
"Migration check for virtual machine VM2 failed to create a planned virtual machine in the target host. Detailed error message: The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'Host2': A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (0x8007274C) "
If I login to the Hyper-V console on either Host, I can do shared nothing migration between them with no problem. I did a netstat-na and I can see that the VMM service has bound port 6600 to my vNIC that I have configured for live migration. However, when I do nslookup for the Hosts, I am getting their Private network IP's.
I suspect that the problem is that SCVMM is trying to make a connection via name resolution, and port 6600 is not available on the IP that is coming back.
Should I put the LiveMigration IP in the hosts file on my Hyper-V Hosts? Will this cause problems for cluster communication? Perhaps I'm barking up the wrong tree entirely, but it sure seems like it's a DNS/IP issue.