{"id":10088,"date":"2009-11-28T09:38:11","date_gmt":"2009-11-28T09:38:11","guid":{"rendered":"https:\/\/aidanfinn.com\/index.php\/2009\/11\/network-requirements-for-live-migration\/"},"modified":"2009-11-28T09:38:11","modified_gmt":"2009-11-28T09:38:11","slug":"network-requirements-for-live-migration","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=10088","title":{"rendered":"Network Requirements for Live Migration"},"content":{"rendered":"<p>As more and more people start deploying Windows Server 2008 R2 Hyper-V, the most common question will be: \u201chow many NIC\u2019s or network cards do I need to implement Live Migration?\u201d.&#160; Here\u2019s the answer for you.<\/p>\n<p>Your minimum optimal configuration is:<\/p>\n<ul>\n<li>NIC #1: Parent partition (normal network) <\/li>\n<li>NIC #2: Cluster heartbeat (private network) <\/li>\n<li>NIC #3: Live Migration (private network) <\/li>\n<li>NIC #4: Virtual Switch (normal\/trunked network) <\/li>\n<\/ul>\n<p>You\u2019ll need to add more NIC\u2019s if you want NIC teaming or need to dedicate NIC\u2019s to virtual switches or VM\u2019s.&#160; This does not account for iSCSI NIC\u2019s which should obviously be dedicated to their role.<\/p>\n<p>How does Windows know which NIC to use for Live Migration?&#160; Failover Clustering picks a private network for the job.&#160; You can see the results by launching the Failover Clustering MMC, opening up the properties of a VM, and going to the last tab.&#160; Here you\u2019ll see which network was chosen.&#160; You can specify an alternative if you wish.<\/p>\n<p>I\u2019ve gone with a different layout.&#160; We\u2019re using HP Blade servers with virtual connects.&#160; Adding NIC\u2019s is a pricey operation because it means buying more pricey virtual connects.&#160; I also need fault tolerance for the virtual machines so a balance had to be found.&#160; Here\u2019s the layout we have:<\/p>\n<ul>\n<li>NIC #1: Parent partition (normal network) <\/li>\n<li>NIC #2: Cluster heartbeat \/ Live Migration (private network) <\/li>\n<li>NIC #3: Virtual Switch (trunked network) <\/li>\n<li>NIC #4: Virtual Switch (trunked network) <\/li>\n<\/ul>\n<p>I\u2019ve tested this quite a bit and pairing live migration with the cluster heartbeat has had no ill effects.&#160; But what happens if I need to live migrate all the VM\u2019s on a host?&#160; Won\u2019t that flood the heartbeat network and cause failovers all over the place?<\/p>\n<p>No.&#160; Live Migration is serial.&#160; That means only one VM is transferred at once.&#160; It\u2019s designed not to flood a network.&#160; Say you initiate maintenance mode in VMM on a cluster node.&#160; Each VM is moved one at a time across the Live Migration network.<\/p>\n<p>You can also see I\u2019ve trunked the virtual switch NIC\u2019s.&#160; That allows us to place VM\u2019s onto different VLAN\u2019s or subnets, each being firewalled from each other.&#160; This barrier is controlled entirely by the firewalls.&#160; I\u2019ll blog about this later because it\u2019s one that deserves some time and concentration.&#160; It has totally wrecked the minds of very senior Cisco admins I\u2019ve worked with in the past when doing Hyper-V and VMware deployments \u2013 eventually I just told them to treat virtualisation as a black box and to trust me \ud83d\ude42<\/p>\n<p>I just thought of another question.&#160; \u201cWhat if I had a configuration that was OK for Windows Server 2008 Hyper-V Quick Migration?\u201d.&#160; That\u2019s exactly what I had and why I chose the last configuration.&#160; Really, you could do that with 3 NIC\u2019s instead of 4 (drop the last one for no virtual switch fault tolerance).<\/p>\n<p>Recommended Reading:<\/p>\n<ul>\n<li><a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/cc732181(WS.10).aspx\" target=\"_blank\">TechNet &#8211; Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2<\/a> <\/li>\n<\/ul>\n<div style=\"padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px\" id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:9b627fa0-13ae-400b-9436-fff035a59ff3\" class=\"wlWriterEditableSmartContent\">Technorati Tags: <a href=\"http:\/\/technorati.com\/tags\/Live+Migration\" rel=\"tag\">Live Migration<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Hyper-V\" rel=\"tag\">Hyper-V<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Windows+Server+2008+R2\" rel=\"tag\">Windows Server 2008 R2<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>As more and more people start deploying Windows Server 2008 R2 Hyper-V, the most common question will be: \u201chow many NIC\u2019s or network cards do I need to implement Live Migration?\u201d.&#160; Here\u2019s the answer for you. Your minimum optimal configuration is: NIC #1: Parent partition (normal network) NIC #2: Cluster heartbeat (private network) NIC #3: &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=10088\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Network Requirements for Live Migration&#8221;<\/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":[181,117],"class_list":["post-10088","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-hyper-v","tag-windows-server-2008-r2"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/10088","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=10088"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/10088\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=10088"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=10088"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=10088"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}