<?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>CCIE Notes</title>
	<atom:link href="http://daxm.net/ccienotes/feed" rel="self" type="application/rss+xml" />
	<link>http://daxm.net/ccienotes</link>
	<description>Technical notes gathered while studying for the CCIE certification.</description>
	<lastBuildDate>Mon, 15 Feb 2010 03:40:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Frame Relay</title>
		<link>http://daxm.net/ccienotes/20100214/frame-relay</link>
		<comments>http://daxm.net/ccienotes/20100214/frame-relay#comments</comments>
		<pubDate>Sun, 14 Feb 2010 18:27:23 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Frame Relay]]></category>
		<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[WAN]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=85</guid>
		<description><![CDATA[&#8230; What is Frame Relay &#8230; Devices that &#8220;speak&#8221; Frame Relay fall into 1 of 2 categories:  data terminal equipment (DTE) or data circuit-terminating equipment (DCE). DTE equipment is at the customer premise and are usually the &#8220;user&#8221; end of the connection.  Think of terminals, PCs, routers. DCE equipment is the service provider end of [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100214/frame-relay/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FHRP &#8212; GLBP</title>
		<link>http://daxm.net/ccienotes/20100209/fhrp-glbp</link>
		<comments>http://daxm.net/ccienotes/20100209/fhrp-glbp#comments</comments>
		<pubDate>Tue, 09 Feb 2010 19:12:37 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=80</guid>
		<description><![CDATA[Gateway Load Balancing Protocol (GLBP) is a Cisco proprietary protocol to provide redundancy to LAN clients with only a &#8220;default gateway&#8221; as their routing option (so is HSRP but that is for a different post). GLBP uses the multicast address of 224.0.0.102 to communicate with GLBP enabled routers in the LAN.  A hello message is [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100209/fhrp-glbp/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Switchport Protected Command</title>
		<link>http://daxm.net/ccienotes/20100208/switchport-protected-command</link>
		<comments>http://daxm.net/ccienotes/20100208/switchport-protected-command#comments</comments>
		<pubDate>Mon, 08 Feb 2010 22:32:07 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=71</guid>
		<description><![CDATA[Similar to Private VLAN&#8217;s concept of an isolated VLAN is a command called Switchport Protected.  It is similar in that any interface that is in the same VLAN and is in &#8220;switchport protected&#8221; mode cannot see each other but can see other ports NOT in switchport protected mode that are in the same VLAN.  This [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100208/switchport-protected-command/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Private VLANs</title>
		<link>http://daxm.net/ccienotes/20100201/private-vlans</link>
		<comments>http://daxm.net/ccienotes/20100201/private-vlans#comments</comments>
		<pubDate>Tue, 02 Feb 2010 00:40:16 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=39</guid>
		<description><![CDATA[To help myself better understand private VLANs I created the following picture: Private VLANs are in two categories: Primary and Secondary. There can be only 1 primary VLAN per private VLAN.  When an interface is configured as a private VLAN promiscious port the primary VLAN is the &#8220;active&#8221; VLAN on that port.  This interface will [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100201/private-vlans/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dynamic ARP Inspection (DAI)</title>
		<link>http://daxm.net/ccienotes/20100131/dynamic-arp-inspection-dai</link>
		<comments>http://daxm.net/ccienotes/20100131/dynamic-arp-inspection-dai#comments</comments>
		<pubDate>Sun, 31 Jan 2010 23:26:32 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=31</guid>
		<description><![CDATA[As mentioned in my previous post, here are my notes on DAI. To enable DAI all is needed is 1 command:  (config)#ip arp inspection vlan &#60;num&#62; HOWEVER there is so much behind this simple command it is scary. Unless additional parameters are configured DAI uses the DHCP snooping bindings table to know what IP-to-MAC-to-Interface mappings [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100131/dynamic-arp-inspection-dai/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>DHCP Snooping</title>
		<link>http://daxm.net/ccienotes/20100131/dhcp-snooping</link>
		<comments>http://daxm.net/ccienotes/20100131/dhcp-snooping#comments</comments>
		<pubDate>Sun, 31 Jan 2010 20:50:11 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/20100131/dhcp-snooping</guid>
		<description><![CDATA[DHCP snooping seems to me to be a strange security enhancement. Though I do agree that securing against a rogue DHCP server is important the way Cisco implements it is odd. In order for DHCP snooping to work at least 3 configurations are  needed: 1) Enable DHCP snooping on the switch &#8212; (config)#ip dhcp snooping [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20100131/dhcp-snooping/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spanning-tree Timers</title>
		<link>http://daxm.net/ccienotes/20091208/spanning-tree-timers</link>
		<comments>http://daxm.net/ccienotes/20091208/spanning-tree-timers#comments</comments>
		<pubDate>Wed, 09 Dec 2009 05:16:33 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Layer2 Technologies]]></category>
		<category><![CDATA[Spanning-Tree]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/20091208/spanning-tree-timers</guid>
		<description><![CDATA[Quick note about STP timers: &#8211; STP timers are inherited from the root bridge. Therefore you only need to configure the timers on the root bridge and backup root bridge. &#8211; STP timers are configured per VLAN. Therefore if you want to configure the timers for all the vlans you&#8217;ll need to use the &#8216;vlan [...]]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20091208/spanning-tree-timers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VLANs Traversing a Network</title>
		<link>http://daxm.net/ccienotes/20091202/vlans-over-trunks</link>
		<comments>http://daxm.net/ccienotes/20091202/vlans-over-trunks#comments</comments>
		<pubDate>Wed, 02 Dec 2009 15:24:41 +0000</pubDate>
		<dc:creator>daxm</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[Layer2 Technologies]]></category>

		<guid isPermaLink="false">http://daxm.net/ccienotes/?p=3</guid>
		<description><![CDATA[Switches only process tagged frames for VLANs they are aware of.]]></description>
		<wfw:commentRss>http://daxm.net/ccienotes/20091202/vlans-over-trunks/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

