<?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: Watch out Cisco</title>
	<atom:link href="http://www.thehotaisle.com/2009/05/11/watch-out-cisco/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thehotaisle.com/2009/05/11/watch-out-cisco/</link>
	<description>Fresh Thinking on IT Operations</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:02:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Watch Out, Cisco &#171; Enterprise Strategy Group</title>
		<link>http://www.thehotaisle.com/2009/05/11/watch-out-cisco/comment-page-1/#comment-7193</link>
		<dc:creator>Watch Out, Cisco &#171; Enterprise Strategy Group</dc:creator>
		<pubDate>Mon, 28 Dec 2009 20:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thehotaisle.com/?p=1354#comment-7193</guid>
		<description>[...] Read the entire blog entry here &gt;&gt; All views and opinions expressed in ESG blog posts are intended to be those of the post&#039;s author and do not necessarily reflect the views of Enterprise Strategy Group, Inc., or its clients. ESG bloggers do not and will not engage in any form of paid-for blogging. Click to see our complete Disclosure Policy. For important information about using this content, please review our Terms &amp; Conditions    Tags: articles, Cisco, cluster, feature, high density, Linux, SAN [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the entire blog entry here &gt;&gt; All views and opinions expressed in ESG blog posts are intended to be those of the post&#39;s author and do not necessarily reflect the views of Enterprise Strategy Group, Inc., or its clients. ESG bloggers do not and will not engage in any form of paid-for blogging. Click to see our complete Disclosure Policy. For important information about using this content, please review our Terms &amp; Conditions    Tags: articles, Cisco, cluster, feature, high density, Linux, SAN [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thehotaisle</title>
		<link>http://www.thehotaisle.com/2009/05/11/watch-out-cisco/comment-page-1/#comment-1593</link>
		<dc:creator>thehotaisle</dc:creator>
		<pubDate>Sat, 18 Jul 2009 11:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thehotaisle.com/?p=1354#comment-1593</guid>
		<description>Thank you for your reply, informative and useful.&lt;br&gt;&lt;br&gt;Steve</description>
		<content:encoded><![CDATA[<p>Thank you for your reply, informative and useful.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meh130</title>
		<link>http://www.thehotaisle.com/2009/05/11/watch-out-cisco/comment-page-1/#comment-1591</link>
		<dc:creator>meh130</dc:creator>
		<pubDate>Fri, 17 Jul 2009 15:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thehotaisle.com/?p=1354#comment-1591</guid>
		<description>This is deceptive.  There is no more requirement to &quot;forklift out&quot; Catalyst 6500s to use Nexus 5000 FCoE than there is with Xsigo InfiniBand.  Both the Nexus 5000 with FCoE and the InfiiBand Xsigo with the InfiniBand vHBA storage protocol replace the access layer FC and Ethernet switching infrastructure.  Existing access layer Catalyst 6500s (in either case) can be reprovisioned to the distribution tier.&lt;br&gt;&lt;br&gt;There is no disruption to existing distribution and core Ethernet infrastructure, and no disruption to core FC SAN director infrastructure in either case.&lt;br&gt;&lt;br&gt;The value prop for either solution is similar.  The difference is, Cisco uses Ethernet as the transport, IP over Ethernet as the IP protocol, and FC as the storage protocol.  Xsigo uses InfiniBand as the transport, vNIC (a mix of IP over InifiniBand and Sockets Direct Protocol over InfiniBand) as the IP protocol, and vHBA as the storage protocol.   vHBA is a newer storage protocol than the more mature SCSI RDMA Protocol (SRP) or iSCSI Extensions for RDMA (iSER).  vHBA will likely be replaced with Fibre Channel over InfiniBand (FCoIB), which is being championed by InfiniBand silicon vendor Mellanox due to the industry momentum behind FCoE.  The transition to FCoIB will likely be disruptive, requiring new drivers on the servers and new firmware on the I/O Directors.  Perhaps Xsigo will not embrace FCoIB, but it is likely FCoIB will become a preferred storage protocol for InfiniBand, as Mellanox is the only vendor of InfiniBand host channel adapter cards.&lt;br&gt;&lt;br&gt;The last time I checked, the Xsigo I/O director was not in EMC&#039;s support matrix, while the Nexus 5000 with FCoE was.  The other advantage of an Ethernet solution like the Nexus 5000 is it also natively supports existing IP storage protocols like CIFS, NFS, and iSCSI.</description>
		<content:encoded><![CDATA[<p>This is deceptive.  There is no more requirement to &#8220;forklift out&#8221; Catalyst 6500s to use Nexus 5000 FCoE than there is with Xsigo InfiniBand.  Both the Nexus 5000 with FCoE and the InfiiBand Xsigo with the InfiniBand vHBA storage protocol replace the access layer FC and Ethernet switching infrastructure.  Existing access layer Catalyst 6500s (in either case) can be reprovisioned to the distribution tier.</p>
<p>There is no disruption to existing distribution and core Ethernet infrastructure, and no disruption to core FC SAN director infrastructure in either case.</p>
<p>The value prop for either solution is similar.  The difference is, Cisco uses Ethernet as the transport, IP over Ethernet as the IP protocol, and FC as the storage protocol.  Xsigo uses InfiniBand as the transport, vNIC (a mix of IP over InifiniBand and Sockets Direct Protocol over InfiniBand) as the IP protocol, and vHBA as the storage protocol.   vHBA is a newer storage protocol than the more mature SCSI RDMA Protocol (SRP) or iSCSI Extensions for RDMA (iSER).  vHBA will likely be replaced with Fibre Channel over InfiniBand (FCoIB), which is being championed by InfiniBand silicon vendor Mellanox due to the industry momentum behind FCoE.  The transition to FCoIB will likely be disruptive, requiring new drivers on the servers and new firmware on the I/O Directors.  Perhaps Xsigo will not embrace FCoIB, but it is likely FCoIB will become a preferred storage protocol for InfiniBand, as Mellanox is the only vendor of InfiniBand host channel adapter cards.</p>
<p>The last time I checked, the Xsigo I/O director was not in EMC&#39;s support matrix, while the Nexus 5000 with FCoE was.  The other advantage of an Ethernet solution like the Nexus 5000 is it also natively supports existing IP storage protocols like CIFS, NFS, and iSCSI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VM Digest</title>
		<link>http://www.thehotaisle.com/2009/05/11/watch-out-cisco/comment-page-1/#comment-7112</link>
		<dc:creator>VM Digest</dc:creator>
		<pubDate>Mon, 11 May 2009 11:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.thehotaisle.com/?p=1354#comment-7112</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Is there an alternative to the Cisco UCP that enables LAN and SAN ... http://bit.ly/LT9bD&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Is there an alternative to the Cisco UCP that enables LAN and SAN &#8230; <a href="http://bit.ly/LT9bD" rel="nofollow">http://bit.ly/LT9bD</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

