NIC teaming, bonding, load balancing, A+B networking, or whatever you want to call it, is a core concept in highly available server computing.\u00a0 In Windows, we’ve been able to create a virtual NIC that we configured TCP in by using 3rd party drivers from the likes of HP or Intel.\n<\/p>\n
The virtual network is no different.\u00a0 ESX can do this by using two host physical NIC’s to connect a virtual switch.\u00a0 A VM has one virtual NIC that connects to this virtual switch and has the benefit of A+B networking.\u00a0 The Hyper-V virtual switch can only use one NIC.\u00a0 Hyper-V relies on drivers in the parent partition.\u00a0 You’d think "OK, lets team two physical NIC’s in the parent partition and use the resulting virtual NIC to connect the virtual switch".\u00a0 Right now, that’s not possible.\u00a0 HP says<\/a>:\n<\/p>\n "IMPORTANT<\/em>\n<\/p>\n Windows Server 2008 Hyper-V RC1 does not support the Network Configuration Utility (NIC Teaming). Deselect this component before installing the PSP components".<\/em>\n<\/p>\n This is not good, not good at all.\u00a0 We cannot do A+B networking in Hyper-V until this changes.\u00a0 I’m told that MS is relying on partners, e.g. HP and Intel, to resolve this like they have done for Windows up to now.\u00a0 I’m really hoping that they do.\n<\/p>\n EDIT:\n<\/p>\n I got a respnse from Microsoft when I sent in some feedback on this issue.\u00a0 Officialy, MS does not support any kind of NIC teaming on Windows.\u00a0 Currently, this is no different with Hyper-V.\u00a0 They are relying 100% on partners such as the likes of HP, Broadcom and Intel to provide updated versions of their teaming drivers for Hyper-V.\u00a0 There is an opening in the parent paritition to allow partners to accomplish NIC teaming and present one virtual (teamed) NIC to a virtual switch in Hyper-V.<\/p>\n","protected":false},"excerpt":{"rendered":" NIC teaming, bonding, load balancing, A+B networking, or whatever you want to call it, is a core concept in highly available server computing.\u00a0 In Windows, we’ve been able to create a virtual NIC that we configured TCP in by using 3rd party drivers from the likes of HP or Intel. The virtual network is no … Continue reading “Hyper-V and NIC Teaming”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[20],"tags":[],"class_list":["post-9084","post","type-post","status-publish","format-standard","hentry","category-hyper-v"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/9084","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=9084"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/9084\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=9084"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=9084"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=9084"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}