{"id":15638,"date":"2013-10-22T13:12:00","date_gmt":"2013-10-22T12:12:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=15638"},"modified":"2014-07-28T08:24:22","modified_gmt":"2014-07-28T08:24:22","slug":"how-to-avoid-networking-issues-in-hyper-v","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=15638","title":{"rendered":"How To Avoid Common Networking Issues In Hyper-V"},"content":{"rendered":"<p>This subject seems to rear it\u2019s ugly head with every new version of Hyper-V.\u00a0 We get new people trying the product for the first time who don\u2019t know the best practices.\u00a0 And we get people who forget the best practices from last time around.<\/p>\n<p>Here is my advice:<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Use Logo Tested NICs<\/span><\/strong><\/p>\n<p>Only NICs that are on the HCL for your version of Windows Server (or Windows client OS if using Client Hyper-V) should be used.\u00a0 Make sure that your hardware manufacturer supports your version of Hyper-V (i.e. Windows Server) for all components that you are using from them.\u00a0 This is a starting point because \u2026<\/p>\n<p><strong><span style=\"text-decoration: underline;\">If At All Possible, Do Not Use Broadcom NICs<\/span><\/strong><\/p>\n<p>Sure, that might preclude you from using certain stuck-in-2009 server manufacturers.\u00a0 And maybe that\u2019s not a bad thing \ud83d\ude00<\/p>\n<p>Broadcom seems to be a name that comes up over and over, version after version, when there are problems.\u00a0 My lab is all Chelsio, but that moves you into the territory of 10 GbE iWARP, which is more expensive than what comes onboard a host.\u00a0 But it allows me to get great SMB 3.0 performance for storage and Live Migration over converged networks.\u00a0 Intel seems to produce decent NICs, firmwares, and drivers, which leads me to \u2026<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Update Your Firmware<\/span><\/strong><\/p>\n<p>Assumption \u2026 ARGH!\u00a0 Do not assume that your firmwares are up to date.\u00a0 I don\u2019t care how new your server is.\u00a0 This goes for every part of the server.\u00a0 Update the firmware.\u00a0 Faulty older firmware is a common cause of issues.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Update Your Drivers<\/span><\/strong><\/p>\n<p>Use the latest drivers <em>from the manufacturer<\/em>.\u00a0 The drivers you got with the server might be old.\u00a0 The drivers in Windows Server might be old too.\u00a0 For example, the automatically detected Chelsio drivers in WS2012 R2 give poor performance.\u00a0 The fix is to download the drivers from Chelsio.\u00a0 If you bought a HP NIC then get the latest drivers from HP.\u00a0 If you bought a NIC from Dell then get the drivers from Dell.<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Install The Recommended Updates For Windows Server<\/strong><\/span><\/p>\n<p>Windows Update is not enough. Let me repeat that: WINDOWS UPDATE IS NOT ENOUGH. If you think it is, then please stop reading, print off a resignation letter, and go home now. Download and install the recommended updates for Windows Server. This <a href=\"https:\/\/aidanfinn.com\/?p=15869\" target=\"_blank\">link<\/a>\u00a0will lead you to 3 sets of updates for WS2012 R2.<\/p>\n<p><strong><span style=\"text-decoration: underline;\"><em>Understand<\/em> And Use Microsoft NIC Teaming<\/span><\/strong><\/p>\n<p>Third-party NIC teaming has never been supported by Microsoft for <span style=\"text-decoration: underline;\">anything<\/span>.\u00a0 Why?\u00a0 Because third-party NIC teaming pulls out the guts of Windows NIC teaming, pushes itself in, squeezes the networking stack back in, finds a few of those \u201cspare screws\u201d and throws them aside.<\/p>\n<p>Take the <a href=\"www.microsoft.com\/download\/confirmation.aspx?id=40319\" target=\"_blank\">time to learn Microsoft NIC teaming<\/a> (there\u2019s more to any teaming than the default options) and use it instead of the third-party unsupported crapware.<\/p>\n<p>EDIT (28\/07\/2014):<\/p>\n<p>One more to add ..<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Don&#8217;t Use Blade Servers<\/strong><\/span><\/p>\n<p>You have no choice but to use what the manufacturer gives you. For many of you, that will be Emulex NICs &#8230; and using those are like going fire-walking after taking a bath in petrol (benzine for Europeans, and gas for Americans).<\/p>\n<p><span style=\"text-decoration: underline;\"><strong>Disable VMQ on Virtual Switch NICs<\/strong><\/span><\/p>\n<p>This is a workaround, and not a solution. We want and may even need VMQ for networking performance and scalability. However, we have seen NICs (Emulex and Broadcom) where having VMQ enabled has caused issues. This should be fixed by the manufacturer using firmware\/driver updates &#8230; but some manufacturers don&#8217;t give a damn about their customers. Emulex &#8211; care to prove me wrong?<\/p>\n<div class=\"wlWriterEditableSmartContent\" id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:29e282e3-13d2-482b-a89e-675d5d7e9eee\" style=\"float: none; margin: 0px; display: inline; padding: 0px;\">Technorati Tags: <a href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012\" rel=\"tag\">Windows Server 2012<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012+R2\" rel=\"tag\">Windows Server 2012 R2<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Hyper-V\" rel=\"tag\">Hyper-V<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Virtualisation\" rel=\"tag\">Virtualisation<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Networking\" rel=\"tag\">Networking<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>This subject seems to rear it\u2019s ugly head with every new version of Hyper-V.\u00a0 We get new people trying the product for the first time who don\u2019t know the best practices.\u00a0 And we get people who forget the best practices from last time around. Here is my advice: Use Logo Tested NICs Only NICs that &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=15638\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;How To Avoid Common Networking Issues In Hyper-V&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","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,120],"class_list":["post-15638","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-hyper-v","tag-networking","tag-virtualisation","tag-windows-server-2012","tag-windows-server-2012-r2"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/15638","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=15638"}],"version-history":[{"count":5,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/15638\/revisions"}],"predecessor-version":[{"id":16875,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/15638\/revisions\/16875"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=15638"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=15638"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=15638"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}