hyper-v vm cannot be reached with IP aliases when the v-switch is mapped to a teamed adapter
-
Sunday, April 22, 2012 8:13 PM
Background:
host:
OS: Windows 20008 R2 SP1 with latest updates.
adapters:
NIC1 -> host management only
NIC2, NIC3 ->broadcom adapters teamed in 802.3ad mode, used for VM onlyswitch:
Dell PowerConnect 6248. Port channel configured accordingly to match the teamVirtual Network:
1 external network (v-switch) configured with the teamed adaptersVMs:
Windows 2008 R2 SP1 with latest updates and hyper-v drivers.
Symptoms:
The primary IP address works just fine. the IP aliases cannot be reached from outside world, other than another vm in the same v-switch(aka in same host). All IP addresses, including the primary ip are in the same subnet. With the same configuration, if I map the v-switch to a single NIC (as opposite to teamed NICs), the IP aliases will work, until it fails over to another node... At all times, the primary IP will work just fine.Question: What has caused above issues? How can I fix it?
Cheers!
- Edited by troo007 Sunday, April 22, 2012 9:05 PM
All Replies
-
Tuesday, April 24, 2012 5:45 AMModerator
Hi,
The primary IP address works just fine. the IP aliases cannot be reached from outside world, other than another vm in the same v-switch(aka in same host)
>> What did you mean by the “outside world”? Did you mean other physical computers in the same LAN or a computer on internet?
By the way, as you may have known, network teaming is only provided by hardware vendors, Microsoft doesn’t support Hyper-V network teaming officially. You may contact the manufacturer or the hardware vendor to have more information on compatibility information. You may also wait for other customer's experience sharing on this. Thanks for your understanding.
More Information
-------------------------
Microsoft Support Policy for NIC Teaming with Hyper-V
http://support.microsoft.com/kb/968703
- Edited by Vincent HuModerator Thursday, April 26, 2012 7:38 AM
-
Tuesday, April 24, 2012 4:33 PM
What I meant by outside world is that any machines that are *not* connected directly to the same v-switch cannot reach the vm.
Further to above, I noticed that IP aliases in Redhat 5.x works fine, but not on Redhat 6.x. So the problem seems to exist in Redhat 6.x and Windows 2008 R2 SP1.
- Edited by troo007 Tuesday, April 24, 2012 10:22 PM

