<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vMotion traffic isolation with VDswitch best practive question (ESXi 5.1) in vMotion &amp; Resource Management Discussions</title>
    <link>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865615#M1307</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;I have a question regarding what is the best practice for vMotion traffic utilizing a VDswitch in vSphere 5.1.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Our&amp;nbsp; VDS is shared between two (soon to be 3) ESXi 5.1 hosts. They all have&amp;nbsp; twelve 1GB physical NIC ports. I have created 11 port groups as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;VLAN trunking is utilized.&lt;/LI&gt;&lt;LI&gt;Four&amp;nbsp; iSCSI port groups. They all physically lead to a switch that is&amp;nbsp; isolated from other switches in our infrastructure so we isolate all&amp;nbsp; iSCSI traffic. This is our VLAN 1060. These port groups each have a&amp;nbsp; dedicated physical NIC assigned to them.&lt;/LI&gt;&lt;LI&gt;All other port groups are physically connected to the same switch.&lt;/LI&gt;&lt;LI&gt;One port group is for Fault Tolerance, VLAN 1066.&lt;/LI&gt;&lt;LI&gt;One port group is for vMotion, VLAN 1065.&lt;/LI&gt;&lt;LI&gt;One port group is for Management, VLAN 1100.&lt;/LI&gt;&lt;LI&gt;We&amp;nbsp; have four other port groups, each with their own VLAN ID. These are for&amp;nbsp; VMs that will reside on various VLANs within our infrastructure (VLAN&amp;nbsp; IDs 20, 30, 1100, 2003).&lt;/LI&gt;&lt;LI&gt;All non-iSCSI port groups share the&amp;nbsp; same active uplinks within the Teaming and Failover settings of the port&amp;nbsp; group. Route is based on physical NIC load.&lt;/LI&gt;&lt;LI&gt;We are using shares defined in the Network Resource Pool to prioritize traffic:&lt;BR /&gt; NFS=50, Management=5, vMotion =10, vSphere SAN=50, vSphere&amp;nbsp; replication=50, iSCSI=50, VM=20, FT=10. I believe these are default&amp;nbsp; values of the network resource pool.&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Here&amp;nbsp; is my question: Should we be isolating vMotion traffic by dedicating&amp;nbsp; physical NICs that are exclusively dedicated for vMotion, rather than&amp;nbsp; isolating via VLAN as I have described above? Will vMotion traffic&amp;nbsp; degrade performance in the way I have it configured above?&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;From&amp;nbsp; the various best practice white papers put out by VMware, I understand&amp;nbsp; that vMotion traffic should be isolated from other traffic. I have done&amp;nbsp; this by utilizing different VLANs for different traffic types. However, I&amp;nbsp; am wondering if vMotion traffic should be isolated by using NIC ports&amp;nbsp; dedicated exclusively for vMotion.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Any help with determining which design is best to use would be greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Feb 2013 19:58:51 GMT</pubDate>
    <dc:creator>TheKenApp</dc:creator>
    <dc:date>2013-02-26T19:58:51Z</dc:date>
    <item>
      <title>vMotion traffic isolation with VDswitch best practive question (ESXi 5.1)</title>
      <link>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865615#M1307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;I have a question regarding what is the best practice for vMotion traffic utilizing a VDswitch in vSphere 5.1.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Our&amp;nbsp; VDS is shared between two (soon to be 3) ESXi 5.1 hosts. They all have&amp;nbsp; twelve 1GB physical NIC ports. I have created 11 port groups as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;VLAN trunking is utilized.&lt;/LI&gt;&lt;LI&gt;Four&amp;nbsp; iSCSI port groups. They all physically lead to a switch that is&amp;nbsp; isolated from other switches in our infrastructure so we isolate all&amp;nbsp; iSCSI traffic. This is our VLAN 1060. These port groups each have a&amp;nbsp; dedicated physical NIC assigned to them.&lt;/LI&gt;&lt;LI&gt;All other port groups are physically connected to the same switch.&lt;/LI&gt;&lt;LI&gt;One port group is for Fault Tolerance, VLAN 1066.&lt;/LI&gt;&lt;LI&gt;One port group is for vMotion, VLAN 1065.&lt;/LI&gt;&lt;LI&gt;One port group is for Management, VLAN 1100.&lt;/LI&gt;&lt;LI&gt;We&amp;nbsp; have four other port groups, each with their own VLAN ID. These are for&amp;nbsp; VMs that will reside on various VLANs within our infrastructure (VLAN&amp;nbsp; IDs 20, 30, 1100, 2003).&lt;/LI&gt;&lt;LI&gt;All non-iSCSI port groups share the&amp;nbsp; same active uplinks within the Teaming and Failover settings of the port&amp;nbsp; group. Route is based on physical NIC load.&lt;/LI&gt;&lt;LI&gt;We are using shares defined in the Network Resource Pool to prioritize traffic:&lt;BR /&gt; NFS=50, Management=5, vMotion =10, vSphere SAN=50, vSphere&amp;nbsp; replication=50, iSCSI=50, VM=20, FT=10. I believe these are default&amp;nbsp; values of the network resource pool.&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Here&amp;nbsp; is my question: Should we be isolating vMotion traffic by dedicating&amp;nbsp; physical NICs that are exclusively dedicated for vMotion, rather than&amp;nbsp; isolating via VLAN as I have described above? Will vMotion traffic&amp;nbsp; degrade performance in the way I have it configured above?&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;From&amp;nbsp; the various best practice white papers put out by VMware, I understand&amp;nbsp; that vMotion traffic should be isolated from other traffic. I have done&amp;nbsp; this by utilizing different VLANs for different traffic types. However, I&amp;nbsp; am wondering if vMotion traffic should be isolated by using NIC ports&amp;nbsp; dedicated exclusively for vMotion.&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;Any help with determining which design is best to use would be greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 19:58:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865615#M1307</guid>
      <dc:creator>TheKenApp</dc:creator>
      <dc:date>2013-02-26T19:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion traffic isolation with VDswitch best practive question (ESXi 5.1)</title>
      <link>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865616#M1308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you configuration is right you use most of what you have and when you need it.&lt;/P&gt;&lt;P&gt;If you want to prioritize any traffic you can create resource allocation on the switch based on the type of traffic or defined by you based on your VLAN's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--ep4p&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 20:21:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865616#M1308</guid>
      <dc:creator>ep4p</dc:creator>
      <dc:date>2013-02-26T20:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion traffic isolation with VDswitch best practive question (ESXi 5.1)</title>
      <link>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865617#M1309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Welcome to the Forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In most environments, the vlan segregation will be sufficient. If you would like you could also make that a non-routable network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 18:48:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865617#M1309</guid>
      <dc:creator>maishsk</dc:creator>
      <dc:date>2013-02-27T18:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion traffic isolation with VDswitch best practive question (ESXi 5.1)</title>
      <link>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865618#M1310</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could use multi-nic vmotion seeing you have plenty. Here is Duncan's article on how to do it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.yellow-bricks.com/2011/09/17/multiple-nic-vmotion-in-vsphere-5/"&gt;http://www.yellow-bricks.com/2011/09/17/multiple-nic-vmotion-in-vsphere-5/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are not splitting up between multiple vswitches make sure you turn on NIOC(Network I/O Control) so network traffic is prioritized. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 21:03:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vMotion-Resource-Management/vMotion-traffic-isolation-with-VDswitch-best-practive-question/m-p/865618#M1310</guid>
      <dc:creator>vSchu</dc:creator>
      <dc:date>2013-02-27T21:03:43Z</dc:date>
    </item>
  </channel>
</rss>

