Failover clustering isn\u2019t exactly fussy about what networks it uses. That can be troublesome, especially when people are buying servers with lots and lots of NICs. Document everything, and only use what you need. Here\u2019s just a few tips:<\/p>\n
Tip #1<\/u><\/strong><\/p>\n Label your network connections with something descriptive such as \u201cParent\u201d, \u201cCSV\u201d, \u201cVM1\u201d, \u201cLM\u201d, or \u201ciSCSI1\u201d, instead of the useless \u201cLocal Area Connection 2\u201d. This allows you to track what is doing what.<\/p>\n Tip #2<\/u><\/strong><\/p>\n Disable unused NICs. They just clutter up stuff all over the place. And they can cause a nightmare in when they are patched into DHCP networks.<\/p>\n Tip #3<\/u><\/strong><\/p>\n Do not disable IPv6, even if you have no IPv6 on your network. MS will support you, but it\u2019s recommended that IPv6 is left bound to all the physical NICs in your cluster nodes. I recently had that discussion with MCS on a customer site. A reach out to Redmond gave us this recommendation.<\/p>\n Tip #4<\/u><\/strong><\/p>\n Disable everything except for the Hyper-V switching protocol on the host NICs that are used for VM networking once you verify that they are patched into the right network(s). This is to prevent the host being a n accidental participant on a guest\u2019s network if that VLAN has a DHCP scope. It also keeps things tidy.<\/p>\n Tip #5<\/u><\/strong><\/p>\n Unbind everything except for TCP on the iSCSI network (which should be a dedicated network for iSCSI with dedicated switches). I found that you can get some weird funnies like CSV suddenly not cooperating if you don\u2019t.<\/p>\n Failover clustering isn\u2019t exactly fussy about what networks it uses. That can be troublesome, especially when people are buying servers with lots and lots of NICs. Document everything, and only use what you need. Here\u2019s just a few tips: Tip #1 Label your network connections with something descriptive such as \u201cParent\u201d, \u201cCSV\u201d, \u201cVM1\u201d, \u201cLM\u201d, or … Continue reading “Hyper-V Cluster: Be Careful With Your Protocol Bindings”<\/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,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[20],"tags":[63,181,195,117],"class_list":["post-11029","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-failover-clustering","tag-hyper-v","tag-virtualisation","tag-windows-server-2008-r2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t