<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BRAD HEDLUND .com&#187; TRILL</title>
	<atom:link href="http://bradhedlund.com/topics/trill/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Thu, 26 Jan 2012 01:03:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Construct a Leaf Spine design with 40G or 10G? An observation in scaling the fabric.</title>
		<link>http://bradhedlund.com/2012/01/25/construct-a-leaf-spine-design-with-40g-or-10g-an-observation-in-scaling-the-fabric/</link>
		<comments>http://bradhedlund.com/2012/01/25/construct-a-leaf-spine-design-with-40g-or-10g-an-observation-in-scaling-the-fabric/#comments</comments>
		<pubDate>Wed, 25 Jan 2012 22:05:02 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Design Diagrams]]></category>
		<category><![CDATA[Fabrics]]></category>
		<category><![CDATA[Routing]]></category>
		<category><![CDATA[TRILL]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=3482</guid>
		<description><![CDATA[Should you construct a Leaf/Spine fabric with 10G or 40G? In this post I’ll make the simple observation that using 10G interfaces in your leaf/spine fabric scales to more servers than using 40G interfaces, all with the same hardware, bandwidth, and oversubscription. Let’s suppose you’ve decided to build a Leaf/Spine fabric for your data center [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2012/01/25/construct-a-leaf-spine-design-with-40g-or-10g-an-observation-in-scaling-the-fabric/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>On &#8220;Why TRILL wont work for the data center&#8221;</title>
		<link>http://bradhedlund.com/2011/06/15/on-why-trill-wont-work-in-the-data-center/</link>
		<comments>http://bradhedlund.com/2011/06/15/on-why-trill-wont-work-in-the-data-center/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 00:39:10 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FUD]]></category>
		<category><![CDATA[QFabric]]></category>
		<category><![CDATA[TRILL]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2998</guid>
		<description><![CDATA[Today I came across &#8220;Why TRILL won&#8217;t work for data center network architecture&#8221; by Anjan Venkatramani of Juniper. Anjan&#8217;s article makes a few myopic and flawed arguments in slamming TRILL, setting up a sale for QFabric.  The stated problems with TRILL include FCoE, L3 multi-pathing, VLAN scale, and large failure domains. The one and only Ivan Pepelnjak has already tackled the [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2011/06/15/on-why-trill-wont-work-in-the-data-center/feed/</wfw:commentRss>
		<slash:comments>24</slash:comments>
		</item>
		<item>
		<title>&#8220;Jawbreaker&#8221;, merchant silicon, QFabric, and flat networks</title>
		<link>http://bradhedlund.com/2011/06/10/jawbreaker-merchant-silicon-qfabric-and-flat-networks/</link>
		<comments>http://bradhedlund.com/2011/06/10/jawbreaker-merchant-silicon-qfabric-and-flat-networks/#comments</comments>
		<pubDate>Fri, 10 Jun 2011 05:09:36 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FabricPath]]></category>
		<category><![CDATA[merchant silicon]]></category>
		<category><![CDATA[Nexus]]></category>
		<category><![CDATA[QFabric]]></category>
		<category><![CDATA[SDN]]></category>
		<category><![CDATA[TRILL]]></category>

		<guid isPermaLink="false">http://bradhedlund.com/?p=2977</guid>
		<description><![CDATA[Brad, can you elaborate on Cisco’s Jawbreaker project? What exactly is it? Is it a response to Juniper’s Q-Fabric? Is it an attempt to rectify the inconsistencies in the differing purpose-built approaches of the N7K and N5K? Why create a new architecture? It seems like Cisco is really in trouble – creating a new architecture, [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2011/06/10/jawbreaker-merchant-silicon-qfabric-and-flat-networks/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Setting the stage for TRILL, rethinking data center switching</title>
		<link>http://bradhedlund.com/2010/05/07/setting-the-stage-for-trill/</link>
		<comments>http://bradhedlund.com/2010/05/07/setting-the-stage-for-trill/#comments</comments>
		<pubDate>Fri, 07 May 2010 17:21:32 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[FabricPath]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[TRILL]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/?p=1003</guid>
		<description><![CDATA[As data centers become increasingly dynamic and dense with virtualization &#8211; how the classic Ethernet switching design adopts to these new models and scales becomes an important and challenging question. Virtualization and cloud based services says that any workload can exist anywhere, at anytime, on demand, and move to any location without disruption. This is [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2010/05/07/setting-the-stage-for-trill/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
	</channel>
</rss>

