{"id":13840,"date":"2012-11-23T13:01:57","date_gmt":"2012-11-23T13:01:57","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=13840"},"modified":"2012-11-23T13:01:57","modified_gmt":"2012-11-23T13:01:57","slug":"enabling-smb-multichannel-to-scale-out-file-server-cluster","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=13840","title":{"rendered":"Enabling SMB Multichannel On Scale-Out File Server Cluster Nodes"},"content":{"rendered":"<p>Ten days ago I <a href=\"https:\/\/aidanfinn.com\/?p=13783\" target=\"_blank\">highlighted<\/a> a blog post by Microsoft\u2019s Jose Baretto that SMB Multichannel across multiple NICs in a clustered node required that both NICs be in different subnets.\u00a0 That means:<\/p>\n<ul>\n<li>You have 2 NICs in each node in the Scale-Out File Server cluster<\/li>\n<li>Both NICs must be in different subnets<\/li>\n<li>You must enable both NICs for client access<\/li>\n<li>There will be 2 NICs in each of the hosts that are also on these subnets, probably dedicated to SMB 3.0 comms, depending on if\/how you do converged fabrics<\/li>\n<\/ul>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image11.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border: 0px;\" title=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image_thumb9.png\" border=\"0\" alt=\"image\" width=\"504\" height=\"626\" \/><\/a><\/p>\n<p>You can figure out cabling and IP addressing for yourself \u2013 if not, you need to <em>not <\/em>be doing this work!<\/p>\n<p>The question is, what else must you do?\u00a0 Well, SMB Multichannel doesn\u2019t need any configuration to work.\u00a0 Pop the NICs into the Hyper-V hosts and away you go.\u00a0 On the SOFS\u00a0cluster, there\u2019s a little bit more work.<\/p>\n<p>After you create the SOFS cluster, you need to make sure that client communications is enabled on both of the NICs on subnet 1 and subnet 2 (as above).\u00a0 This is to allow the Hyper-V hosts to talk to the SOFS across both NICs (the green NICs in the diagram) in the SOFS cluster nodes.\u00a0 You can see this setting below.\u00a0 In my demo lab, my second subnet is not routed and it wasn\u2019t available to configure when I created the SOFS cluster.<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image12.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image_thumb10.png\" border=\"0\" alt=\"image\" width=\"404\" height=\"482\" \/><\/a><\/p>\n<p>You\u2019ll get a warning that you need to enable a Client Access Point (with an IP address) for the cluster to accept communications on this network.\u00a0 Damned if I\u2019ve found a way to do that.\u00a0 I don\u2019t think it\u2019s necessary to do that additional step in the case of an SOFS, as you\u2019ll see in a moment.\u00a0 I\u2019ll try to confirm that with MSFT.\u00a0 Ignore the warning and continue.\u00a0 My cluster (uses iSCSI because I don\u2019t have a JBOD) looks like:<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image13.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image_thumb11.png\" border=\"0\" alt=\"image\" width=\"404\" height=\"202\" \/><\/a><\/p>\n<p>You can see ManagementOS1 and ManagementOS2 (on different subnets) are Enabled, meaning that I\u2019ve allowed clients to connect through both networks.\u00a0 ManagementOS1 has the default CAP (configured when the cluster was created).<\/p>\n<p>Next I created the file server for application data role (aka the SOFS).\u00a0 Over in AD we find a computer object for the SOFS and we should see that 4 IP addresses have been registered in DNS.\u00a0 Note how the SOFS role uses the IP addresses of the SOFS cluster nodes (demo-fs1 and demo-fs2).\u00a0 You can also need the DNS records for my 2 hosts (on 2 subnets) here.<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image14.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/11\/image_thumb12.png\" border=\"0\" alt=\"image\" width=\"504\" height=\"208\" \/><\/a><\/p>\n<p>If you don\u2019t see 2 IP address for each SOFS node registered with the SOFS name (as above \u2013 2 addresses * 2 nodes = 4) then double check that you have enabled client communications across both cluster networks for the NICs on the SOFS cluster nodes (as previous).<\/p>\n<p>Now we should be all ready to rock and role.<\/p>\n<p>In my newly modified demo lab, I run this with the hosts clustered (to show new cluster Live Migration features) and not clustered (to show Live Migration with SMB storage).\u00a0 The eagle-eyed will notice that my demo Hyper-V hosts don\u2019t have dedicated NICs for SMB comms.\u00a0 In the real world, I\u2019d probably have dedicated NICs for SMB 3.0 comms on the Hyper-V hosts.\u00a0 They\u2019d be on the 2 subnets that have been referred to in this post.<\/p>\n<div id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:f4d52ed7-0e68-47dc-b2b9-ab4009be4c48\" class=\"wlWriterEditableSmartContent\" style=\"float: none; margin: 0px; display: inline; padding: 0px;\">Technorati Tags: <a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Hyper-V\">Hyper-V<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012\">Windows Server 2012<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Storage\">Storage<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Failover+Clustering\">Failover Clustering<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Ten days ago I highlighted a blog post by Microsoft\u2019s Jose Baretto that SMB Multichannel across multiple NICs in a clustered node required that both NICs be in different subnets.\u00a0 That means: You have 2 NICs in each node in the Scale-Out File Server cluster Both NICs must be in different subnets You must enable &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=13840\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Enabling SMB Multichannel On Scale-Out File Server Cluster Nodes&#8221;<\/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":[63,181,99,118],"class_list":["post-13840","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-failover-clustering","tag-hyper-v","tag-storage","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\/13840","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=13840"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/13840\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}