Hyper-V Guest NLB unicast Problem
- Hi,
i have an Hyper-V (RTM) 64x Server with two Guest Win2003 Ent. 32x R2 SP2.
Guest NLB Test :
Network Adapter
Multicast = OK
Unicast = KO
Legacy Network Adapter
Multicast = OK
Unicast = OK
Microsoft document write : new virtual switch support NLB cluster, but Unicast + Network Adapter (External/Private) don't work.
Any suggestion is good :-)
Best Regards
Giulio
Risposte
- Hello Giulio,
I am a little confused, but this sounds to be a known bug relating to running Windows Server 2003 with NLB in the child partition.
Though the hotfix of KB 953828 doesn't apply to Windows Server 2003, you can still try the steps listed in this article, in the section "Post-installation instructions", starting from step 8. The key point is that you need to change the Network Adapter MAC Address of the VM to static, not dynamic, and configure MAC address to what the NLB uses.
Doing this is because, for now, the synthetic NIC does not allow adding another MAC address, which is what unicast mode makes it do.
Best regards,
Chang Yin- Contrassegnato come rispostaChang Yin lunedì 1 settembre 2008 2.24
Tutte le risposte
- Step 1: Did you apply the knowledge base hotfix for NLB on Hyper-V?
http://support.microsoft.com/kb/953828/en-us
- Wayne S. Anderson MCITP, MCSE, MCT http://blog.avanadeadvisor.com/blogs/waynea - Hi Wayne,
di NLC cluster is converged (unicast + network adapter).
Localy the VIP and dedicated IP responde corretly to the ping.
On LAN the ping (VIP/Dedicated) responde request time out
If change to Multicast the NLB work fine.
Many thanks
Giulio - Hello Giulio,
I am a little confused, but this sounds to be a known bug relating to running Windows Server 2003 with NLB in the child partition.
Though the hotfix of KB 953828 doesn't apply to Windows Server 2003, you can still try the steps listed in this article, in the section "Post-installation instructions", starting from step 8. The key point is that you need to change the Network Adapter MAC Address of the VM to static, not dynamic, and configure MAC address to what the NLB uses.
Doing this is because, for now, the synthetic NIC does not allow adding another MAC address, which is what unicast mode makes it do.
Best regards,
Chang Yin- Contrassegnato come rispostaChang Yin lunedì 1 settembre 2008 2.24
- I'm running into this same issue. Because I'm doing this with Exchange 2007 it requires x64. I've read that the legacy network adapter doesn't support x64 so I'm stuck with the synthetic adapter which is causing issues with my Hyper-V when i'm trying to do NLB with Exchange 2007. I can't ping from a VM that is not my NLB node but can ping from the NLB node just fine.
This seems to be a pretty big issue if Exchange 2007 can't take advantage of NLB due to this.
- Just an FYI, you can check out the following article to fix this:
http://www.shudnow.net/2008/09/12/exchange-2007-unicast-nlb-issue-on-hyper-v/
- Hello Changthe NBL Cluster is Converged. This esclude the KB 953828 problem.The VIP e DIP response the ping run on localhost, but don't responde the ping from LAN client.If i use Legacy e/o Multicast the ping work fine from LAN Client.I suppose a BUG on Virtual BUS network adapter driver.Many thanksGiulio
- Hi all,
I have working in virtualization, using Virtual Server 2005 and using Windows Server 2008 Hyper-V.
When i have build a NLB for Web Applications (ASP.NET applications, WSS, MOSS, etc.), i can configure NLB in Unicast mode only in Virtual Server Guests. Working with Hyper-V, when i have configure NLB in unicast, client computer can not access NLB (no ping, no http requests, etc.), but changing NLB from unicast to multicast (only in Hyper-V guests!!) was de way...
I have working in some labs about this in my lab (http://www.guillesql.es/Articulos/HyperV.aspx), and the WorkAround was configure NLB in Multicast only in Hyper-V guests.
Best Regards, and sorry my english...
GuilleSQL
http://www.guillesql.es
This posting is provided AS IS with no warranties, and confers no rights
