<?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: FCoE, Will you believe the hype?</title>
	<atom:link href="http://blogs.rupturedmonkey.com/?feed=rss2&#038;p=156" rel="self" type="application/rss+xml" />
	<link>http://blogs.rupturedmonkey.com/?p=156</link>
	<description>The greatest storage blog in the world....</description>
	<lastBuildDate>Mon, 30 Aug 2010 22:25:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jesse</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-801</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Sun, 10 Aug 2008 16:54:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-801</guid>
		<description>Very interesting.&#160; It&#039;s been a while since I&#039;ve had the time to post to my own blog, let alone browse the others.&#160; So far I&#039;ve found very little real-world implementations of FCoE.&#160; Seems to me that that particular implementation would be inefficient as you&#039;re wrapping a SCSI packet in an FC packet, then turning right around and wrapping that up in an ethernet packet.&#160; Seems like the overhead would be excessive.So far I&#039;ve found iSCSI to be useful in small implementations.&#160; Much easier and less expensive to put a dedicated $1,000 Ethernet switch (a good one, you don&#039;t want to use a crappy switch for storage traffic) than a $10,000 fibrechannel switch.</description>
		<content:encoded><![CDATA[<p>Very interesting.&nbsp; It&#8217;s been a while since I&#8217;ve had the time to post to my own blog, let alone browse the others.&nbsp; So far I&#8217;ve found very little real-world implementations of FCoE.&nbsp; Seems to me that that particular implementation would be inefficient as you&#8217;re wrapping a SCSI packet in an FC packet, then turning right around and wrapping that up in an ethernet packet.&nbsp; Seems like the overhead would be excessive.So far I&#8217;ve found iSCSI to be useful in small implementations.&nbsp; Much easier and less expensive to put a dedicated $1,000 Ethernet switch (a good one, you don&#8217;t want to use a crappy switch for storage traffic) than a $10,000 fibrechannel switch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak Munjal</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-762</link>
		<dc:creator>Deepak Munjal</dc:creator>
		<pubDate>Tue, 06 May 2008 17:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-762</guid>
		<description>I&#039;ve read some valid points but let me expand on some of the other ones. The fact is that customers are looking for a converged solution.&#160; Maintaining multiple parallel networks has never made sense.&#160; You only have to look at networks in the past that have been converged (FDDI, ATM, Token Ring, X.25, etc.) to understand that the future will be a single network to attach all types of devices.&#160; Historically, IP and Ethernet have seen the most success here. No one is advocating one converged solution over another.&#160; FCoE makes sense for those who have invested millions in Fibre Channel and provides an elegant migration solution.&#160; iSCSI appeals to many small and medium businesses that want to build a SAN but don&#039;t want to make an investment in Fibre Channel. Cisco is investing in all of these solutions to give customers the choice.&#160; The MDS 9000 will continue to be our flagship Fibre Channel solution and will support FCoE.&#160; The Nexus platforms support Data Center Ethernet which provide the platform to converge storage and data traffic whether you&#039;re using iSCSI or FCoE.</description>
		<content:encoded><![CDATA[<p>I&#39;ve read some valid points but let me expand on some of the other ones. The fact is that customers are looking for a converged solution.&nbsp; Maintaining multiple parallel networks has never made sense.&nbsp; You only have to look at networks in the past that have been converged (FDDI, ATM, Token Ring, X.25, etc.) to understand that the future will be a single network to attach all types of devices.&nbsp; Historically, IP and Ethernet have seen the most success here. No one is advocating one converged solution over another.&nbsp; FCoE makes sense for those who have invested millions in Fibre Channel and provides an elegant migration solution.&nbsp; iSCSI appeals to many small and medium businesses that want to build a SAN but don&#39;t want to make an investment in Fibre Channel. Cisco is investing in all of these solutions to give customers the choice.&nbsp; The MDS 9000 will continue to be our flagship Fibre Channel solution and will support FCoE.&nbsp; The Nexus platforms support Data Center Ethernet which provide the platform to converge storage and data traffic whether you&#39;re using iSCSI or FCoE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Etherealmind</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-761</link>
		<dc:creator>Etherealmind</dc:creator>
		<pubDate>Tue, 06 May 2008 06:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-761</guid>
		<description>I agree with most of what you say, but I also think that FCoE looks&#160; a &#039;transition technology&#039; for all those people who have invested personal energy into the FC. I have seen quite a bit of reaction from people who have FC skills and can see that disappearing and they will lose influence in the their organisations.&#160; Those folks are not going to give up easy and will point the finger at the Networking Team and say that IP networking is not ready. &#160;I have put some design articles for iSCSI on my blog. Maybe you will find them interesting.&#160; &#160;Etherealmind </description>
		<content:encoded><![CDATA[<p>I agree with most of what you say, but I also think that FCoE looks&nbsp; a &#39;transition technology&#39; for all those people who have invested personal energy into the FC. I have seen quite a bit of reaction from people who have FC skills and can see that disappearing and they will lose influence in the their organisations.&nbsp; Those folks are not going to give up easy and will point the finger at the Networking Team and say that IP networking is not ready. &nbsp;I have put some design articles for iSCSI on my blog. Maybe you will find them interesting.&nbsp; &nbsp;Etherealmind</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-759</link>
		<dc:creator>Nigel</dc:creator>
		<pubDate>Fri, 02 May 2008 19:19:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-759</guid>
		<description>&lt;p&gt;Its not that long ago that most of us only connected our high performance servers to the SAN.&#160; This connectivity was was over dedicated fibre, running a purpose written protocol to dedicated high speed (and cost) switches into subsystems stuffed with high speed FC disks running RAID1/10&#8230;&#8230;.&lt;/p&gt; &lt;p&gt;What will we have tomorrow&#8230;&#8230;&#160; Nearly all of our server estate crammed onto the &lt;strike&gt;SAN&lt;/strike&gt; shared network via iSCSI and FCOE over a shared medium, through shared switches (share processor clock cycles etc with TCP/IP traffic) and into subsystems loaded with everything from SSD to FC to SATA running every RAID level you could care to imagine and a few you&#8217;d rather not imagine.&lt;/p&gt; &lt;p&gt;At least you will get predictable performance&#8230;&#8230;. Predictably bad!&lt;/p&gt; &lt;p&gt;Actually, may be it wont work like that&#8230;.. I haven&#8217;t done enough research into it yet, but it certainly seems to be the way the industry is going.&#160; While Ive always liked EMC&#8217;s pitch on SSD, I also see that it brings its own problems.&#160; The industry seems to be desperate to cram as many products, protocols and features as possible into a single entity, be it piece of tin, apiece of cable, a switch or array&#8230;&#8230;..&#160; all under the name of consolidation.&#160; The thing is, I personally prefer expansion and widening my horizons rather than cutting back and consolidating.&#160; But the market dictates.&lt;/p&gt; &lt;p&gt;BTW I don&#8217;t see the big banks and the likes being keen on FCOE.&#160; Too risky in my opinion.&#160; May be 10 years after the rest have adopted it!?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Its not that long ago that most of us only connected our high performance servers to the SAN.&nbsp; This connectivity was was over dedicated fibre, running a purpose written protocol to dedicated high speed (and cost) switches into subsystems stuffed with high speed FC disks running RAID1/10&hellip;&hellip;.</p>
<p>What will we have tomorrow&hellip;&hellip;&nbsp; Nearly all of our server estate crammed onto the <strike>SAN</strike> shared network via iSCSI and FCOE over a shared medium, through shared switches (share processor clock cycles etc with TCP/IP traffic) and into subsystems loaded with everything from SSD to FC to SATA running every RAID level you could care to imagine and a few you&rsquo;d rather not imagine.</p>
<p>At least you will get predictable performance&hellip;&hellip;. Predictably bad!</p>
<p>Actually, may be it wont work like that&hellip;.. I haven&rsquo;t done enough research into it yet, but it certainly seems to be the way the industry is going.&nbsp; While Ive always liked EMC&rsquo;s pitch on SSD, I also see that it brings its own problems.&nbsp; The industry seems to be desperate to cram as many products, protocols and features as possible into a single entity, be it piece of tin, apiece of cable, a switch or array&hellip;&hellip;..&nbsp; all under the name of consolidation.&nbsp; The thing is, I personally prefer expansion and widening my horizons rather than cutting back and consolidating.&nbsp; But the market dictates.</p>
<p>BTW I don&rsquo;t see the big banks and the likes being keen on FCOE.&nbsp; Too risky in my opinion.&nbsp; May be 10 years after the rest have adopted it!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: billy bathgates</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-758</link>
		<dc:creator>billy bathgates</dc:creator>
		<pubDate>Tue, 29 Apr 2008 23:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-758</guid>
		<description>The comment about cisco is disconcerting. Cisco keeps&#160; doing their damndest trying to make storage management and storage groups be seen as part of &#039;networking&#039; in corporate organizational charts. Gee wonder why they would want to do that? I&#039;m pretty sure I don&#039;t wnat cisco deciding what the future of storage networking will be (not that I have any control over the matter, I can still bitch though:-) </description>
		<content:encoded><![CDATA[<p>The comment about cisco is disconcerting. Cisco keeps&nbsp; doing their damndest trying to make storage management and storage groups be seen as part of &#39;networking&#39; in corporate organizational charts. Gee wonder why they would want to do that? I&#39;m pretty sure I don&#39;t wnat cisco deciding what the future of storage networking will be (not that I have any control over the matter, I can still bitch though:-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: billy bathgates</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-757</link>
		<dc:creator>billy bathgates</dc:creator>
		<pubDate>Tue, 29 Apr 2008 23:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-757</guid>
		<description>Amen Chris, In my shop, it is quite rare that a 4G link is more than 50% utilized, although lets face it, it is nice to be able to use fewer ISLs with the higher bandwidth (and by &quot;higner bandwidth, I mean 4G). I bet the number of shops that would really benefit from 8G is small, and even there, the number of 8G links they need is a small percentage of their SAN.</description>
		<content:encoded><![CDATA[<p>Amen Chris, In my shop, it is quite rare that a 4G link is more than 50% utilized, although lets face it, it is nice to be able to use fewer ISLs with the higher bandwidth (and by &quot;higner bandwidth, I mean 4G). I bet the number of shops that would really benefit from 8G is small, and even there, the number of 8G links they need is a small percentage of their SAN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris M Evans</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-756</link>
		<dc:creator>Chris M Evans</dc:creator>
		<pubDate>Tue, 29 Apr 2008 20:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-756</guid>
		<description>I think customers have more fundamental issues to solve rather than whether they should use host based 8GB or FCoE.&#160; Perhaps people out there should take a step back and look at solving all the existing issues in their environment first, rather than putting in the new toys!</description>
		<content:encoded><![CDATA[<p>I think customers have more fundamental issues to solve rather than whether they should use host based 8GB or FCoE.&nbsp; Perhaps people out there should take a step back and look at solving all the existing issues in their environment first, rather than putting in the new toys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Whyte</title>
		<link>http://blogs.rupturedmonkey.com/?p=156&#038;cpage=1#comment-755</link>
		<dc:creator>Barry Whyte</dc:creator>
		<pubDate>Fri, 25 Apr 2008 21:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rupturedmonkey.com/?p=156#comment-755</guid>
		<description>I guess the major question is if you can use the same Ethernet infrastructure for your TCP/IP connectivity and your FCoE connectivity. A la DCE.  However,  unless there is a major benefit (and the major issues with CPU overhead are overcome that have dogged iSCSI&#039;s break through in the enterprise market - amazing that even offload iSCSI cards save very little of that overhead)  then FC as we know it will be here for a while longer. 

8Gbit is here and now, but who is asking for it?</description>
		<content:encoded><![CDATA[<p>I guess the major question is if you can use the same Ethernet infrastructure for your TCP/IP connectivity and your FCoE connectivity. A la DCE.  However,  unless there is a major benefit (and the major issues with CPU overhead are overcome that have dogged iSCSI&#8217;s break through in the enterprise market &#8211; amazing that even offload iSCSI cards save very little of that overhead)  then FC as we know it will be here for a while longer. </p>
<p>8Gbit is here and now, but who is asking for it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.783 seconds -->
