<?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 Management Network in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430756#M33806</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand it is best practice to have Management network on its own subnet/VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a small environment - 3 hosts (8-10 VMS), do you think it would impact performance much to ahve it on same subnet as VM network and regular PC network traffic.&amp;nbsp; This is a small environment with 7-8 servers and about 40 PC's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I isolated vMotion and iSCSI traffic each on their own VLANS.&amp;nbsp; But it would make things much easier to leave Management on the same subnet as VM/PC traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any guidance or recommendations are very much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Feb 2013 05:13:58 GMT</pubDate>
    <dc:creator>danm71</dc:creator>
    <dc:date>2013-02-08T05:13:58Z</dc:date>
    <item>
      <title>Management Network</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430756#M33806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand it is best practice to have Management network on its own subnet/VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a small environment - 3 hosts (8-10 VMS), do you think it would impact performance much to ahve it on same subnet as VM network and regular PC network traffic.&amp;nbsp; This is a small environment with 7-8 servers and about 40 PC's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I isolated vMotion and iSCSI traffic each on their own VLANS.&amp;nbsp; But it would make things much easier to leave Management on the same subnet as VM/PC traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any guidance or recommendations are very much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 05:13:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430756#M33806</guid>
      <dc:creator>danm71</dc:creator>
      <dc:date>2013-02-08T05:13:58Z</dc:date>
    </item>
    <item>
      <title>Re: Management Network</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430757#M33807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;its not full about the performance, its a secutiry perspective also.&lt;/P&gt;&lt;P&gt;it is good and recommended to at least use a vlan for the managment traffic.if you share with the vm traffic also no issue...for small env it is ok&lt;/P&gt;&lt;P&gt;but in best practice is , use a dedicated nics vlan for iscsi vmotion management.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 05:26:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430757#M33807</guid>
      <dc:creator>Gkeerthy</dc:creator>
      <dc:date>2013-02-08T05:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Management Network</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430758#M33808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I usually configure the Management Network in a server VLAN to ensure a user (client) cannot accidentally (or on purpose) use the same IP address and cause issues with magament and/or HA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;André&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 12:22:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430758#M33808</guid>
      <dc:creator>a_p_</dc:creator>
      <dc:date>2013-02-08T12:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: Management Network</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430759#M33809</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;one of the worker in my company while working on his VM, did a ping of death and it caused the ESX to timeout the heartbeat resulting in HA and vmotioning the VMS and being powered off..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so the management network is better of in a separate VLAN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 15:55:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430759#M33809</guid>
      <dc:creator>zXi_Gamer</dc:creator>
      <dc:date>2013-02-08T15:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Management Network</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430760#M33810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for all of the input.&amp;nbsp; I will put in seperate VLAN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 16:16:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Management-Network/m-p/430760#M33810</guid>
      <dc:creator>danm71</dc:creator>
      <dc:date>2013-02-08T16:16:11Z</dc:date>
    </item>
  </channel>
</rss>

