Here's my problem with Hyper-V:
Don't ask me why, but today, some of my VM can't ping other VM on another host! The only change i've made is to install .Net Framework 4 on all VM.
Here's the detail of my environnement:
Here's the detail of the problem:
Some VM (5 have the problem) can't ping other VM on another host: So VM1 on host1 can't ping VM2 and VM3 on host2 BUT can ping VM4 on host2!! By this time, VM1 can ping all other VM on host1 and all other on host3. This behaviour is "unpredictable". Sometimes it's a VM from host3 who have problem with VM on host1..
I solve the problem by different way: assigning static MAC adress, deleting network card on VM and create new one, create legacy acrd instead of network card, deleting all entry in the registry from old card, etc.
Now I have two VM where I already try all thoses solutions without succes!
It's not a VLAN problem as when a VM can't ping another one, it can ping some other in the same VLAN and across others VLAN...
Here's another test i've made: If i take VM1 who's in problem (VM1 on Host1 can't ping VM2 on Host2) and VM3 who's OK. I shut those two VMs, and switch the MAC adresse and IP between the VMS, VM1 start to work OK and VM3 is in problem. So i think it's a MAC problem! But if i try to put different static MAC to all my VM i still have the problem.
Another information: all my physical host are SUN Fire x4170 with 4 Intel Network cards. The first NIC is reserved for manageemnt and the other tree are in Teaming (command line :PROSetCL.exe Team_Create 1,3,4 TeamVM VMLB) for Virtual Machine Load Balancing. No special configuration on the Cisco switch.
Someone already see that?
sounds like our problem exactly! We currently have a case open with MS, we'll see what happens. My gut feeling is that there is an issue with
vmlb + dynamic mac's+vlans.
15.2 is the latest and greatest I believe (I am checking on that with folks, as this is not my area). It can be downloaded here:
I am not sure if the VMLB fix is in this version or not, as I said I'm checking on it.
Seems like this was fixed in 15.4. The latest driver available is 15.4.1 which you can get from here:
I've no idea why the normal driver download site has 15.2 as the latest - I'm poking folks on that. However I'm told that the link above has the drivers that should fix this issue for you.
Patrick, can you confirm me that 15.4.1 solve this problem? I don't have time to update all my server if the problem isn't solve!
Also, which advantage i have to use VMLB instead of ALB?
Thanks for your help!
Based upon the description of the issue, it appears to match the symptoms of a bug fixed in release 15.4, which would also be included in 15.4.1.
I'm not an expert on teaming, however I have found a nice web page the explains the differences for you:
Hopefully we'll be able to apply these today, I'll let you know if it works for us. VMLB sounds cool so we went with it, it seems to be more dynamic then the other teaming options. Note that since none of this has worked properly yet I can't say if its cool or not!
ok it didn't resolve the issue, but I've got to be truthful here. Its a hp server with hp nic drivers with the intel ans software installed on top. Do you think this would cause a conflict? Hp's NCU doesn't support the VMLB mode as far as I can tell, we've backed out the configuration.