In order to work out some IP address issues we came up with this solution...
We have set up a new vSwitch named VM Network with ZERO physical NICs.
We change the network card of each VDI VMs set to the VM Network.
We have installed and configired a Win 2008 R2 server. It's first NIC is connected to a vSwitch with 6 physical NICs that is connected to our internal network. It's second NIC is connected to the VM Network as above.
We are running DHCP bound to the VM Network side.
We have routing configured so traffice flows between the two NICs.
I have added static routes to out main router so for a different subnet we can get to the VM Network.
This setup is running on our three hosts. The VM Network on each host has a different IP subnet. We are also using DRS across the three hosts.
I have a test VDI VM. When I try to manually migrate that VM to one of the other hosts, I get a warning that Network Adapter 1 is a 'virtual intranet', which prevents a live migration. If i then shut the VM down and do the migrate, I still get the warning, but it allows me to proceed and the test VDI VM works.
IThe main quest is, if we were to modify our production VDI VMs to the above scheme (where Network Adapter 1) is on the VM Network (which is considered a 'virtual intranet'), will DRS be able to move those VDI VMs to any of the hosts or is it going to fail?
Thanks in advance
Regarding migration of the test VM:
If a VM has a vNIC attached to an internal network vSwitch which has no pNICs assigned there's an issue regarding vMotion which DRS ofc relies on but can be resolved by configuring the vpxd.cfg on the vCenter server..
http://kb.vmware.com/kb/1006701
/Rubeck
Regarding migration of the test VM:
If a VM has a vNIC attached to an internal network vSwitch which has no pNICs assigned there's an issue regarding vMotion which DRS ofc relies on but can be resolved by configuring the vpxd.cfg on the vCenter server..
http://kb.vmware.com/kb/1006701
/Rubeck
Rubec, thanks.
The advanced setting config.migrate.test.CompatibleNetworks.VMOnVirtualIntranet = false solved the issue of DRS migration error due to the 'virtual intranet' (vSwitch with ZERO NICs).
So the initial question is answered...but more issues have popped up.
The new issue is related to our setup. Each host has it's own VM Network. The IP setting given out oer host are on different subnets.
When the VM is migrated from one host to the other, it doesn't renegotiate DHCP, it retains an IP address from it's previous host, which causes it to lost it's connectivity.
Is there a way to force the VM to renegotiate DHCP?
Or is there an alternative solution?
Note we are currently running everything under a Class C subnet, we could renumber everything under a Class B address, but that would a enormous complexity as we'd have to manually reset all of our servers and printers.
As most IP enabled OS' does renegotiaon upon link state up/downs you could disconnect/reconnect the vNIC in the VM seeting or a powershell script targeting vCemter to do it.. A VM to host relation check using powershell when scheduled might be able to trigger this also..
/Rubeck
