<?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: Lippis Report 155: The Two-Tier High-End Data Center Ethernet Fabric Network Gains Steam</title>
	<atom:link href="http://lippisreport.com/2010/08/lippis-report-155-the-two-tier-high-end-data-center-ethernet-fabric-network-gains-steam/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2010/08/lippis-report-155-the-two-tier-high-end-data-center-ethernet-fabric-network-gains-steam/</link>
	<description>Resources for Network / IT Business Decision Makers</description>
	<lastBuildDate>Tue, 22 May 2012 00:38:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Nick Lippis</title>
		<link>http://lippisreport.com/2010/08/lippis-report-155-the-two-tier-high-end-data-center-ethernet-fabric-network-gains-steam/comment-page-1/#comment-212625</link>
		<dc:creator>Nick Lippis</dc:creator>
		<pubDate>Fri, 03 Sep 2010 09:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3326#comment-212625</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;Lippis Report 155: The Two-Tier High-End Data Center Ethernet Fabric Network Gains Steam http://bit.ly/cT9l3N&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">Lippis Report 155: The Two-Tier High-End Data Center Ethernet Fabric Network Gains Steam <a href="http://bit.ly/cT9l3N" rel="nofollow">http://bit.ly/cT9l3N</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan Banks</title>
		<link>http://lippisreport.com/2010/08/lippis-report-155-the-two-tier-high-end-data-center-ethernet-fabric-network-gains-steam/comment-page-1/#comment-211230</link>
		<dc:creator>Ethan Banks</dc:creator>
		<pubDate>Wed, 25 Aug 2010 13:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3326#comment-211230</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;&quot;It’s a 2-tier network fabric that...data center architects have gravitated toward...&quot; an edited quote from http://bit.ly/c1qran&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">&quot;It’s a 2-tier network fabric that&#8230;data center architects have gravitated toward&#8230;&quot; an edited quote from <a href="http://bit.ly/c1qran" rel="nofollow">http://bit.ly/c1qran</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Lippis</title>
		<link>http://lippisreport.com/2010/08/lippis-report-155-the-two-tier-high-end-data-center-ethernet-fabric-network-gains-steam/comment-page-1/#comment-211227</link>
		<dc:creator>Nick Lippis</dc:creator>
		<pubDate>Wed, 25 Aug 2010 13:35:49 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/?p=3326#comment-211227</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;My take on 2 &amp; 3 tier dc Ethernet fabrics via Lippis Report 155: http://bit.ly/dcAOSq&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">My take on 2 &amp; 3 tier dc Ethernet fabrics via Lippis Report 155: <a href="http://bit.ly/dcAOSq" rel="nofollow">http://bit.ly/dcAOSq</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

