<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Nexus 5000 &amp; Nexus 2000: New technology requires new thinking</title>
	<atom:link href="http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Sun, 05 Sep 2010 13:21:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Stand</title>
		<link>http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/comment-page-1/#comment-802</link>
		<dc:creator>Chris Stand</dc:creator>
		<pubDate>Tue, 09 Mar 2010 13:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/?p=801#comment-802</guid>
		<description>Livio,
  
  If you need storage over ethernet and don&#039;t yet have support for fcoe in your storage or server products take a look at a recent VMware document on Exchange performance using iSCSI and NFS - http://blogs.vmware.com/performance/2009/07/exchange-performs-well-using-fibre-channel-iscsi-and-nfs-on-vsphere.html

The testing used generic Intel nics vs dedicated fiber HBAs and showed iSCSI and NFS ( our interest is iSCSI which unlike FC CAN be port channeled and run over distance greater than FCOE distance limit of 300m) to be very close in performance.  If the testing had used hardware iSCSI adapters it likely would have beaten native Fiber Channel. 

From your postings ... the N5K &amp; FEXes don&#039;t seem to be candidates  your environment - a couple of 3750Gs would probably be ideal and they could handle limited ethernet over IP in whatever fashion you needed now.</description>
		<content:encoded><![CDATA[<p>Livio,</p>
<p>  If you need storage over ethernet and don&#8217;t yet have support for fcoe in your storage or server products take a look at a recent VMware document on Exchange performance using iSCSI and NFS &#8211; <a href="http://blogs.vmware.com/performance/2009/07/exchange-performs-well-using-fibre-channel-iscsi-and-nfs-on-vsphere.html" rel="nofollow">http://blogs.vmware.com/performance/2009/07/exchange-performs-well-using-fibre-channel-iscsi-and-nfs-on-vsphere.html</a></p>
<p>The testing used generic Intel nics vs dedicated fiber HBAs and showed iSCSI and NFS ( our interest is iSCSI which unlike FC CAN be port channeled and run over distance greater than FCOE distance limit of 300m) to be very close in performance.  If the testing had used hardware iSCSI adapters it likely would have beaten native Fiber Channel. </p>
<p>From your postings &#8230; the N5K &#038; FEXes don&#8217;t seem to be candidates  your environment &#8211; a couple of 3750Gs would probably be ideal and they could handle limited ethernet over IP in whatever fashion you needed now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Livio</title>
		<link>http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/comment-page-1/#comment-700</link>
		<dc:creator>Livio</dc:creator>
		<pubDate>Fri, 12 Feb 2010 01:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/?p=801#comment-700</guid>
		<description>Well,

Can&#039;t I make &quot;the cloud&quot; with traditional switches (4948 for example)? As I&#039;ve said before, my only concern is that I&#039;ll loose A LOT of access ports on Nexus 5000 that could be used by servers with 10GE/FCoE. Again, the only reasons you are giving me to use this design is &quot;management facility&quot; and vPC.

So, putting it in a balance I see more losses than benefits. What&#039;s the big problem on connecting to another device to manage it? Is this really a big loss? It&#039;ll take 5 minutes more to make a service. I don&#039;t think that this is the best benefit of this design. I would really appreciate  to have all switches of the same series managed by the same program (cisco DCNM), unfortunally I think we are going the other way. Loosing 20 access interfaces, isn&#039;t a good option for me...

I&#039;m not talking about a huge datacenter. I will only need 10 1G switch for the next years, so &quot;big L2 domain&quot; for me isn&#039;t to much trouble. If you could explain better this problem maybe I change my mind...

I&#039;m expecting that 10G(with FCoE on some cases) will dominate the servers design, so my loss will be huge. I&#039;ll maintain 1Gbps only for backward compatibility (10 years? hehehe).

If Nexux 2000 could be attached directly to an Nexus 7000 (it is not quite difficult to make that works) the deisgn would perfect fit for our needs...

I&#039;ll send this to the list too.

By the way,
Nice blog.
[]&#039;s</description>
		<content:encoded><![CDATA[<p>Well,</p>
<p>Can&#8217;t I make &#8220;the cloud&#8221; with traditional switches (4948 for example)? As I&#8217;ve said before, my only concern is that I&#8217;ll loose A LOT of access ports on Nexus 5000 that could be used by servers with 10GE/FCoE. Again, the only reasons you are giving me to use this design is &#8220;management facility&#8221; and vPC.</p>
<p>So, putting it in a balance I see more losses than benefits. What&#8217;s the big problem on connecting to another device to manage it? Is this really a big loss? It&#8217;ll take 5 minutes more to make a service. I don&#8217;t think that this is the best benefit of this design. I would really appreciate  to have all switches of the same series managed by the same program (cisco DCNM), unfortunally I think we are going the other way. Loosing 20 access interfaces, isn&#8217;t a good option for me&#8230;</p>
<p>I&#8217;m not talking about a huge datacenter. I will only need 10 1G switch for the next years, so &#8220;big L2 domain&#8221; for me isn&#8217;t to much trouble. If you could explain better this problem maybe I change my mind&#8230;</p>
<p>I&#8217;m expecting that 10G(with FCoE on some cases) will dominate the servers design, so my loss will be huge. I&#8217;ll maintain 1Gbps only for backward compatibility (10 years? hehehe).</p>
<p>If Nexux 2000 could be attached directly to an Nexus 7000 (it is not quite difficult to make that works) the deisgn would perfect fit for our needs&#8230;</p>
<p>I&#8217;ll send this to the list too.</p>
<p>By the way,<br />
Nice blog.<br />
[]&#8217;s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Hedlund</title>
		<link>http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/comment-page-1/#comment-693</link>
		<dc:creator>Brad Hedlund</dc:creator>
		<pubDate>Tue, 09 Feb 2010 16:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/?p=801#comment-693</guid>
		<description>Brian,
I hear you loud and clear.  The Catalyst 4900M&#039;s small form factor and high performance fits nicely as the 10GE L3 switch aggregating the Nexus 5000&#039;s in these small footprint environments.

Cheers,
Brad</description>
		<content:encoded><![CDATA[<p>Brian,<br />
I hear you loud and clear.  The Catalyst 4900M&#8217;s small form factor and high performance fits nicely as the 10GE L3 switch aggregating the Nexus 5000&#8217;s in these small footprint environments.</p>
<p>Cheers,<br />
Brad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Landers</title>
		<link>http://bradhedlund.com/2010/02/09/nexus-5000-2000-new-technology-requires-new-thinking/comment-page-1/#comment-692</link>
		<dc:creator>Brian Landers</dc:creator>
		<pubDate>Tue, 09 Feb 2010 16:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.bradhedlund.com/?p=801#comment-692</guid>
		<description>My only real problem with the Nexus 5000+2000 combo is that it doesn&#039;t seem to map very well to smaller data centers.  I&#039;d *love* to do top-of-rack N2K&#039;s with N5K aggregation, but I don&#039;t *need* a N7K (and can&#039;t justify one) when the data center only has 16 cabinets and a single DS3 WAN circuit.  With the N5K unable to do inter-VLAN L3 switching, I&#039;m in a bind.</description>
		<content:encoded><![CDATA[<p>My only real problem with the Nexus 5000+2000 combo is that it doesn&#8217;t seem to map very well to smaller data centers.  I&#8217;d *love* to do top-of-rack N2K&#8217;s with N5K aggregation, but I don&#8217;t *need* a N7K (and can&#8217;t justify one) when the data center only has 16 cabinets and a single DS3 WAN circuit.  With the N5K unable to do inter-VLAN L3 switching, I&#8217;m in a bind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
