![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/05\/image12.png\" "\\"image\\"")
<\/a><\/p>\nGo through the diagram of this clustered Windows Server 2012 Hyper-V host:<\/p>\n
- \n
- In case you\u2019re wondering, this example is using SAS or FC attached storage so it doesn\u2019t require Ethernet NICs for iSCSI.\u00a0 Don\u2019t worry iSCSI fans \u2013 I\u2019ll come to that topic in another post.<\/li>\n
- There are two 10 GbE NICs in a NIC team.\u00a0 We covered that already.<\/li>\n
- There is a Hyper-V Extensible Switch that is connected to the NIC team.\u00a0 OK.<\/li>\n
- Two VMs are connected to the virtual switch.\u00a0 Nothing unexpected there!<\/li>\n
- Huh!\u00a0 The host, or the parent partition, has 3 NICs for cluster communications\/CSV, management, and live migration.\u00a0 But \u2026 they\u2019re connected to the Hyper-V Extensible Switch?!?!?\u00a0 That\u2019s new!\u00a0 They used to require physical NICs.<\/li>\n<\/ul>\n
In Windows Server 2008 a host with this storage would require the following NICs as a minimum:<\/p>\n
- \n
- Parent (Management)<\/li>\n
- VM (for the Virtual Network, prior to the Virtual Switch)<\/li>\n
- Cluster Communications\/CSV<\/li>\n
- Live Migration<\/li>\n<\/ul>\n
All that accumulation of NICs wasn\u2019t a matter of bandwidth. What we really care about in clustering is quality of service: bandwidth when <\/em>we need it and low latency. Converged fabrics assume we can guarantee those things. If we have those SLA features available to us (more in later posts) then 2 * 10 GbE physical NICs in each clustered hosts might<\/em> be enough, depending on business and technology requirements of the site.\u00a0 4 NICs per host \u2026 and that\u2019s without NIC teaming.\u00a0 Double the NICs!<\/p>\n
The amount of NICs go up.\u00a0 The number of switch ports goes up.\u00a0 The wasted rack space cost goes up.\u00a0 The power bill for all that goes up.\u00a0 The support cost for your network goes up.\u00a0 In truth, the complexity goes up.<\/p>\n
NICs aren\u2019t important.\u00a0 Quality communications channels are<\/span> important.<\/p>\n
In this WS2012 converged fabrics design, we can create virtual NICs that attach to the Virtual Switch.\u00a0 That\u2019s done by using the Add-VMNetworkAdapter<\/a> PowerShell cmdlet, for example:<\/p>\n
Add-VMNetworkAdapter -ManagementOS -Name “Manage” -SwitchName External1<\/p>\n
\u2026 where Manage will be the name of the new NIC and the name of the Virtual Switch is External1.\u00a0 The \u2013ManagementOS tells the cmdlet that the new vNIC is for the parent partition or the host OS.<\/p>\n
You can then:<\/p>\n
- \n
- Configure the vNIC using Set-VMNetworkAdapter<\/a><\/li>\n
- Specify the VLAN for the vNIC using Set-VMNetworkAdapterVLAN<\/a><\/li>\n
- Configure IPv4\/IPv6<\/li>\n<\/ul>\n
I think configuring the VLAN binding of these NICs with port trunking (or whatever) would be the right way to go with this.\u00a0 That will further isolate the traffic on the physical network.\u00a0 Please bear in mind that we\u2019re still in the beta days and I haven\u2019t had a chance to try this architecture yet.<\/p>\n
Armed with this knowledge and these cmdlets, we can now create all the NICs we need that connect to our converged physical fabrics.\u00a0 Next we need to look at securing and guaranteeing quality levels of communications.<\/p>\n
Technorati Tags: Hyper-V<\/a>,Windows Server 2012<\/a>,Virtualisation<\/a>,Networking<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"We continue further down the road of understanding converged fabrics in WS2012 Hyper-V.\u00a0 The following diagram illustrates a possible design goal: Go through the diagram of this clustered Windows Server 2012 Hyper-V host: In case you\u2019re wondering, this example is using SAS or FC attached storage so it doesn\u2019t require Ethernet NICs for iSCSI.\u00a0 Don\u2019t … Continue reading “Windows Server 2012 Hyper-V & Management OS Virtual NICs”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","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":[181,80,195,118],"class_list":["post-12588","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-hyper-v","tag-networking","tag-virtualisation","tag-windows-server-2012"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12588","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=12588"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12588\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12588"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12588"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Specify the VLAN for the vNIC using Set-VMNetworkAdapterVLAN<\/a><\/li>\n
- Configure the vNIC using Set-VMNetworkAdapter<\/a><\/li>\n