<?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; Switching</title>
	<atom:link href="http://bradhedlund.com/topics/ethernet/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradhedlund.com</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Wed, 23 Jun 2010 01:50:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<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[Data Center]]></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>23</slash:comments>
		</item>
		<item>
		<title>Outage Story with VTP</title>
		<link>http://bradhedlund.com/2007/12/02/outage-story-with-vtp/</link>
		<comments>http://bradhedlund.com/2007/12/02/outage-story-with-vtp/#comments</comments>
		<pubDate>Sun, 02 Dec 2007 07:48:01 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[Switching]]></category>
		<category><![CDATA[VTP]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/2007/12/02/outage-story-with-vtp/</guid>
		<description><![CDATA[One of my accounts had an unfortunate network outage that lasted about an hour.  This outage was caused by human error with VTP but not in the classic revision number way we have heard about before.
Here is what happened&#8230;

1) A CatOS access switch fails and is scheduled to be replaced by the network team.
2) [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/12/02/outage-story-with-vtp/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Switchport Configurations Explained</title>
		<link>http://bradhedlund.com/2007/11/27/switchport-configurations-explained/</link>
		<comments>http://bradhedlund.com/2007/11/27/switchport-configurations-explained/#comments</comments>
		<pubDate>Tue, 27 Nov 2007 23:07:02 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[DTP]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/24/dtp-configurations-explained/</guid>
		<description><![CDATA[It always helps me to think of the English translation when trying to memorize and understand some the Cisco IOS settings I think are important.
Here are some Cisco IOS switchport configurations translated into English:
&#8216;switchport mode trunk&#8216; says: &#8220;Always trunk on this end, and I will send DTP to attempt to negotiate a trunk on the [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/27/switchport-configurations-explained/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>VLAN Trunking using IEEE 802.1Q</title>
		<link>http://bradhedlund.com/2007/11/27/vlan-trunking-using-ieee-8021q/</link>
		<comments>http://bradhedlund.com/2007/11/27/vlan-trunking-using-ieee-8021q/#comments</comments>
		<pubDate>Tue, 27 Nov 2007 20:54:43 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[802.1q]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/22/ethernet-trunking-using-ieee-8021q/</guid>
		<description><![CDATA[IEEE 802.1Q (sometimes referred to as 1Q or DOT1Q) is a industry standards based implementation of carring traffic for multiple VLANs on a single trunking interface between two Ethernet switches.  802.1Q is for Ethernet networks only.
Unlike ISL , 802.1Q does not encapsulate the original Ethernet frame.
For Ethernet V2 frames, 802.1Q inserts a new 4-byte [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/27/vlan-trunking-using-ieee-8021q/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>VLAN Trunking using ISL</title>
		<link>http://bradhedlund.com/2007/11/26/vlan-trunking-using-isl/</link>
		<comments>http://bradhedlund.com/2007/11/26/vlan-trunking-using-isl/#comments</comments>
		<pubDate>Mon, 26 Nov 2007 05:18:38 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[ISL]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/14/ethernet-trunking-using-isl/</guid>
		<description><![CDATA[Inter-Switch Link (ISL) is a Cisco specific implementation of trunking multiple VLANs between two Cisco switches where a single interface will carry traffic for more than one VLAN.  ISL was designed to work with Ethernet, FDDI, Token Ring, and ATM.
ISL completely encapsulates the original Ethernet frame by adding a new 26 byte header and [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/26/vlan-trunking-using-isl/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Things to know about VTP</title>
		<link>http://bradhedlund.com/2007/11/21/things-to-know-about-vtp/</link>
		<comments>http://bradhedlund.com/2007/11/21/things-to-know-about-vtp/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 22:43:17 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[VTP]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/13/some-notes-on-vtp/</guid>
		<description><![CDATA[Some notes about VTP (VLAN Trunking Protocol):

Cisco switches running Cisco IOS store VTP and VLAN information in a separate database stored in Flash, in file called vlan.dat.
Cisco switches running CatOS store VTP and VLAN information in the main switch configuration file, stored in NVRAM.
VTP information is only transmitted over trunk ports.
A VTP client does not [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/21/things-to-know-about-vtp/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Identifying Ethernet Multicast</title>
		<link>http://bradhedlund.com/2007/11/21/identifying-ethernet-multicast/</link>
		<comments>http://bradhedlund.com/2007/11/21/identifying-ethernet-multicast/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 21:52:40 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/11/identifying-ethernet-multicast/</guid>
		<description><![CDATA[Just like there are 3 different Ethernet header types, there are also 3 different types of Ethernet addresses:

Unicast
Broadcast
Multicast

A unicast frame contains the unique MAC address of the destination receiver.  A broadcast frame contains all binary 1&#8217;s as the destination address (FFFF.FFFF.FFFF).  A multicast frame contains the unique multicast MAC address of an application, [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/21/identifying-ethernet-multicast/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Identifying Ethernet Header Types</title>
		<link>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/</link>
		<comments>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/#comments</comments>
		<pubDate>Mon, 19 Nov 2007 21:36:45 +0000</pubDate>
		<dc:creator>Brad Hedlund</dc:creator>
				<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Switching]]></category>

		<guid isPermaLink="false">http://www.bradhedlund.com/articles/5/identifying-ethernet-header-types/</guid>
		<description><![CDATA[There are 3 different Ethernet Header types defined by the IEEE and in use today.  So, one question comes to mind: When a Ethernet receiver receives a frame, how does it know what kind of header it is?  After all, if a receiver is unable to properly recognize the header type, it will [...]]]></description>
		<wfw:commentRss>http://bradhedlund.com/2007/11/19/identifying-ethernet-header-types/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
