<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Where do I put my networks?</title>
    <link>http://communities.vmware.com/community/vmtn/planning?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Mon, 21 Apr 2008 13:14:47 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-04-21T13:14:47Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920761?tstart=0#920761</link>
      <description>2 ESX servers is definitely in the small range I was thinking an upper range of 4-6 ESX server load and you will not have any issues. (AT 6 if most of the VM's are heavy hitters then all bets are off.) &lt;br /&gt;
&lt;br /&gt;
HA on only two servers .... make sure you test that you can successfully load all of your VM's on one server. &lt;br /&gt;
&lt;br /&gt;
You will need to do this when it comes time to patch the hosts and other unforeseen events. &lt;br /&gt;
&lt;p /&gt;
Memory becomes the most important resource, if your VM's are memory starved they will swap active memory to disk and this is not optimum and only testing can tell the real story. &lt;br /&gt;
&lt;p /&gt;
With two physical switches you have the required physical redundancy. In addition to that HA will want to see two IP paths across it, while not critical to HA running you will get warnings. The idea is that if an IP binding is dropped HA can still see hosts on a second logical path. You would need to define the SC logical paths across two vSwitches and have those vSwitches across the respective physical paths. &lt;br /&gt;
&lt;p /&gt;
Sofware iSCSI is OK on teamed NICs,  you should try keep it simple. It can be nasty to figure out if something not working intermitantly. Later as you fully understand it then maybe go more complex. You will have your hands full with what you have now I'm sure. &lt;br /&gt;
&lt;p /&gt;
Regards &lt;br /&gt;
Mike&lt;br /&gt;
&lt;br /&gt;
Message was edited by: mike.laspina - added iSCSI #2</description>
      <pubDate>Mon, 21 Apr 2008 13:04:28 GMT</pubDate>
      <author>mike.laspina</author>
      <guid>http://communities.vmware.com/message/920761?tstart=0#920761</guid>
      <dc:date>2008-04-21T13:04:28Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920560?tstart=0#920560</link>
      <description>&lt;div class="jive-quote"&gt;Yes I did tell you the 1800 will be fine, and it is when an ESX farm is small. The 2900 is much more powerful and would do better under heavy load and thats why I perfer it for iSCSI. But you need it for LAN routing so it will have to stay there.&lt;/div&gt;
&lt;br /&gt;
Our farm definately counts as small - only 2 ESX nodes to begin with &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt; At least with the 1800's we can start out cheap, and then replace with better switches if our load increases to the point where it's necessary.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;You also were looking at jumbo frames, one caution there is that HP flowcontrol and jumbo frames are sometimes an issue when combined.&lt;br /&gt;
&lt;p /&gt;
Some iSCSI product vendors (Lefthand) recommend jumbo frames be turned off on the lowered end switches if you are using flow control.&lt;br /&gt;
&lt;p /&gt;
Flow control will be the better option to leave on for peek load performance.&lt;br /&gt;
&lt;p /&gt;
The 2900 series can handle both on at the same time. The reason for it is buffering and processing power.&lt;/div&gt;
&lt;br /&gt;
Thanks for the tip, I'll be sure to enable flow control but disable jumbo frames.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;I have the 1800 and I don't have issues at 50% load and I have not used jumbo frames yet.&lt;br /&gt;
&lt;p /&gt;
I also have the 2900 and it really is a work horse, you can pin it and it still continue to perform.&lt;/div&gt;
&lt;br /&gt;
Great, thanks.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;As for the SC if you use HA in the future this feature will want redundant network paths across the network for all hosts. Software iSCSI also needs an SC to on the same iSCSI network. This will result in multiple SC's across the networks and you may not what to place them solely on one pNIC pair going over the 1800. So think of the SC as more that just a managment console is what I am saying.&lt;/div&gt;
&lt;br /&gt;
We want to use HA from the start so this sounds like it'll be important to us &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt; &lt;br /&gt;
&lt;br /&gt;
Are you saying that:&lt;br /&gt;
&lt;br /&gt;
1) the SC needs redundant network paths, and,&lt;br /&gt;
2) the SC will need to participate in more than just 1 network - i.e. for iSCSI authentication&lt;br /&gt;
&lt;br /&gt;
?&lt;br /&gt;
&lt;br /&gt;
If so, I think we have #1 covered by the fact that both the 1800 and 2900 will be paired (i.e. we'll actually have 2 x 1800's and 2 x 2900's), meaning we have network path redundancy, and I thought #2 can be managed by adding a SC port to the iSCSI vSwitch.&lt;br /&gt;
&lt;br /&gt;
Have I mis-understood / missed anything?</description>
      <pubDate>Mon, 21 Apr 2008 06:11:33 GMT</pubDate>
      <author>mattjk</author>
      <guid>http://communities.vmware.com/message/920560?tstart=0#920560</guid>
      <dc:date>2008-04-21T06:11:33Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920357?tstart=0#920357</link>
      <description>&lt;br /&gt;
Yes I did tell you the 1800 will be fine, and it is when an ESX farm is small. The 2900 is much more powerful and would do better under heavy load and thats why I perfer it for iSCSI. But you need it for LAN routing so it will have to stay there. &lt;br /&gt;
&lt;p /&gt;
You also were looking at jumbo frames, one caution there is that HP flowcontrol and jumbo frames are sometimes an issue when combined.&lt;br /&gt;
&lt;p /&gt;
Some iSCSI product vendors (Lefthand) recommend jumbo frames be turned off on the lowered end switches if you are using flow control.&lt;br /&gt;
&lt;p /&gt;
Flow control will be the better option to leave on for peek load performance.  &lt;br /&gt;
&lt;p /&gt;
The 2900 series can handle both on at the same time. The reason for it is buffering and processing power.&lt;br /&gt;
&lt;p /&gt;
I have the 1800 and I don't have issues at 50% load and I have not used jumbo frames yet.&lt;br /&gt;
&lt;p /&gt;
I also have the 2900 and it really is a work horse, you can pin it and it still continue to perform.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
As for the SC if you use HA in the future this feature will want redundant network paths across the network for all hosts. Software iSCSI also needs an SC to on the same iSCSI network. This will result in multiple SC's across the networks and you may not what to place them solely on one pNIC pair going over the 1800. So think of the SC as more that just a managment console is what I am saying.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sun, 20 Apr 2008 15:40:17 GMT</pubDate>
      <author>mike.laspina</author>
      <guid>http://communities.vmware.com/message/920357?tstart=0#920357</guid>
      <dc:date>2008-04-20T15:40:17Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920254?tstart=0#920254</link>
      <description>&lt;div class="jive-quote"&gt;1) iSCSI will utiliize a switch much more heavily that the network, I would use the 2900 series for iSCSI&lt;/div&gt;
&lt;br /&gt;
Didn't you tell me a couple of days ago - &lt;a class="jive-link-external" href="http://communities.vmware.com/message/915061#915061"&gt;http://communities.vmware.com/message/915061#915061&lt;/a&gt;  and &lt;a class="jive-link-external" href="http://communities.vmware.com/message/918825#918825"&gt;http://communities.vmware.com/message/918825#918825&lt;/a&gt; - that the 1800's should be fine for iSCSI? &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;br /&gt;
Regardless, I don't think we have much choice: we need some of the features offered in the 2900 on the LAN side (L3 routing, etc), and can't afford to buy 4 x 2900's (2 for SAN, 2 for LAN). So, we're "stuck" with the 1800's for the SAN, unless an alternative solution can be found. I &lt;i&gt;might&lt;/i&gt; be able to afford 2810-24G's instead of 1800's, but it'll be pushing it.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;2) SC and VMotion are the lower priority in terms of normal activity. If you have a large farm the activity increases but what is the percentage of the whole....&lt;/div&gt;
&lt;br /&gt;
We only have a small farm &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;3) You may need more than one SC in an average config so you have to rethink it from the physical side&lt;/div&gt;
&lt;br /&gt;
Could you elaborate on what you mean here please?&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;4) VMotion and SC do need security isolation but do not mix it with iSCSI because it is normal network traffic and this goes against best practice&lt;/div&gt;
&lt;br /&gt;
OK, that's what I was looking for. Thanks.</description>
      <pubDate>Sun, 20 Apr 2008 04:07:46 GMT</pubDate>
      <author>mattjk</author>
      <guid>http://communities.vmware.com/message/920254?tstart=0#920254</guid>
      <dc:date>2008-04-20T04:07:46Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920252?tstart=0#920252</link>
      <description>&lt;div class="jive-quote"&gt;There are lots of posts about this out there check out these:&lt;/div&gt;
&lt;br /&gt;
&amp;lt;snip&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;All pretty much say the same thing however, you really want 6 pNIC for your load not just 2. But this depends on your Security Policy, Regulatory Stance, and comfort level.&lt;/div&gt;
&lt;br /&gt;
I think you may have mis-understood my question as none of those posts seem to answer it.&lt;br /&gt;
&lt;br /&gt;
It's not regarding how many NICs - we already will have lots of pNICs (10 actually, not 6) - in my original post I said "Our ESX deployment will include the following networks, with 2 x pNICs in each ESX host &lt;i&gt;for each network&lt;/i&gt;".&lt;br /&gt;
&lt;br /&gt;
The question is regarding where to physically connect the SC and vMotion networks - i.e. which switch pair (out of the two described) should they connect to?</description>
      <pubDate>Sun, 20 Apr 2008 04:01:28 GMT</pubDate>
      <author>mattjk</author>
      <guid>http://communities.vmware.com/message/920252?tstart=0#920252</guid>
      <dc:date>2008-04-20T04:01:28Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920004?tstart=0#920004</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
Here is my thinking.&lt;br /&gt;
&lt;p /&gt;
1) iSCSI will utiliize a switch much more heavily that the network, I would use the 2900 series for iSCSI&lt;br /&gt;
&lt;p /&gt;
2) SC and VMotion are the lower priority in terms of normal activity. If you have a large farm the activity increases but what is the percentage of the whole....&lt;br /&gt;
&lt;p /&gt;
3) You may need more than one SC in an average config so you have to rethink it from the physical side  &lt;br /&gt;
&lt;p /&gt;
4) VMotion and SC do need security isolation but do not mix it with iSCSI because it is normal network traffic and this goes against best practice.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 19 Apr 2008 13:29:36 GMT</pubDate>
      <author>mike.laspina</author>
      <guid>http://communities.vmware.com/message/920004?tstart=0#920004</guid>
      <dc:date>2008-04-19T13:29:36Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/920029?tstart=0#920029</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
There are lots of posts about this out there check out these:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/111463?tstart=0"&gt;http://communities.vmware.com/thread/111463?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/111877?tstart=0"&gt;http://communities.vmware.com/thread/111877?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/792421"&gt;http://communities.vmware.com/message/792421&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/791014"&gt;http://communities.vmware.com/message/791014&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/788939"&gt;http://communities.vmware.com/message/788939&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/108662?tstart=0"&gt;http://communities.vmware.com/thread/108662?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/829962"&gt;http://communities.vmware.com/message/829962&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/840206#840206"&gt;http://communities.vmware.com/message/840206#840206&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/115578?tstart=0&amp;#38;start=0"&gt;http://communities.vmware.com/thread/115578?tstart=0&amp;#38;start=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/132974?tstart=0"&gt;http://communities.vmware.com/thread/132974?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/133447?tstart=0"&gt;http://communities.vmware.com/thread/133447?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/138450?tstart=0"&gt;http://communities.vmware.com/thread/138450?tstart=0&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/906562#906562"&gt;http://communities.vmware.com/message/906562#906562&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
All pretty much say the same thing however, you really want 6 pNIC for your load not just 2. But this depends on your Security Policy, Regulatory Stance, and comfort level.&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;Best regards,&lt;br /&gt;
Edward L. Haletky&lt;br /&gt;
VMware Communities User Moderator&lt;br /&gt;
====&lt;br /&gt;
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. As well as the Virtualization Wiki at &lt;a class="jive-link-external" href="http://www.astroarch.com/wiki/index.php/Virtualization"&gt;http://www.astroarch.com/wiki/index.php/Virtualization&lt;/a&gt;</description>
      <pubDate>Sat, 19 Apr 2008 13:27:12 GMT</pubDate>
      <author>Texiwill</author>
      <guid>http://communities.vmware.com/message/920029?tstart=0#920029</guid>
      <dc:date>2008-04-19T13:27:12Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Where do I put my networks?</title>
      <link>http://communities.vmware.com/message/919988?tstart=0#919988</link>
      <description>Hi all,&lt;br /&gt;
&lt;br /&gt;
Quick question regarding where it is best to "place" vMotion and SC (Management) networks.&lt;br /&gt;
&lt;br /&gt;
Our ESX deployment will include the following networks, with 2 x pNICs in each ESX host for each network:&lt;br /&gt;
&lt;br /&gt;
vMotion&lt;br /&gt;
SAN (iSCSI and/or NFS)&lt;br /&gt;
SC (Management network)&lt;br /&gt;
LAN (a couple of different ones seperated by VLANs)&lt;br /&gt;
DMZ&lt;br /&gt;
&lt;br /&gt;
These will be connected to 4 physical switches - 2 pairs of 2 for redundancy. I think we're going to use 2 x ProCurve 1800-24G for the SAN network, and 2 x ProCurve 2900-24G for the LAN &amp;#38; DMZ networks (separated by VLANs).&lt;br /&gt;
&lt;br /&gt;
This leaves the vMotion and SC (Management) networks.&lt;br /&gt;
&lt;br /&gt;
Which of the pairs of switches should we run these two through? Are these any special considerations?&lt;br /&gt;
&lt;br /&gt;
I'm leaning towards putting both the vMotion and SC networks on the SAN switches, firstly because they will both be rather simple networks in our small environment, and secondly because the SAN switches will be isolated from other traffic so vMotion and SC security will be higher.&lt;br /&gt;
&lt;br /&gt;
Whichever way we go we'll of course be using VLANs to seperate the different networks inside the switch.&lt;br /&gt;
&lt;br /&gt;
Thoughts? Opinions?&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
Matt</description>
      <pubDate>Sat, 19 Apr 2008 09:41:59 GMT</pubDate>
      <author>mattjk</author>
      <guid>http://communities.vmware.com/message/919988?tstart=0#919988</guid>
      <dc:date>2008-04-19T09:41:59Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
  </channel>
</rss>

