<?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>AlwaysTheNetwork &#187; Troubleshooting Labs</title>
	<atom:link href="http://blog.alwaysthenetwork.com/category/troubleshooting-labs/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.alwaysthenetwork.com</link>
	<description>Just another Cisco blog</description>
	<lastBuildDate>Tue, 07 Sep 2010 15:29:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Troubleshooting Lab #6</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-6/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-6/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 12:22:59 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[BGP]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[CCIP]]></category>
		<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[EIGRP]]></category>
		<category><![CDATA[GRE]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[OSPF]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=822</guid>
		<description><![CDATA[First lab with our new topology. I&#8217;m excited! This should be an easy one. When functioning correctly, Customer &#8220;a&#8221; connects to AS 6500 using MPLS VPNs and running OSPF with the provider between sites. Site 2 (CE2a) has internet access through a physical connection to AS 6500s global RIB, it also has a GRE tunnel]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-6/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>New Troubleshooting Lab Topology</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/new-troubleshooting-lab-topology/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/new-troubleshooting-lab-topology/#comments</comments>
		<pubDate>Sat, 03 Apr 2010 06:27:20 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[CCIP]]></category>
		<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[Lab]]></category>
		<category><![CDATA[MPLS]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=816</guid>
		<description><![CDATA[The old topology I&#8217;ve been using for the weekly labs is pretty limited. I created a new one today which should keep us going for awhile. It&#8217;s relatively complex, it consists of two customer MPLS VPNs and lots of routing. The two customer VPNs also have internet access through one of their sites. We are]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/new-troubleshooting-lab-topology/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Lab #5</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-5/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-5/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 14:00:29 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[EIGRP]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[OSPF]]></category>
		<category><![CDATA[RIP]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=800</guid>
		<description><![CDATA[This one might be easy, but I&#8217;m having trouble gauging it after last week. Same topology, users are having trouble communicating from one VLAN to the other. Soon I&#8217;ll make a new (bigger) topology with more diverse technologies, I haven&#8217;t had the time lately. You can run the .net on your own Dynamips server or]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-5/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Lab #4</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-4/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-4/#comments</comments>
		<pubDate>Thu, 18 Mar 2010 14:42:43 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[Lab]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=794</guid>
		<description><![CDATA[Today is probably going to be another easy one, but I threw it together pretty quick. We&#8217;re using the same topology as last time. Same issue, users cannot communicate, but different problem. You can run the .net on your own Dynamips server or you can use mine. Run the topology and login with username &#8220;tshoot&#8221;]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-4/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Lab #3</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-3/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-3/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 12:21:24 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[EIGRP]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[OSPF]]></category>
		<category><![CDATA[RIP]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=779</guid>
		<description><![CDATA[This one is a little different (again). I&#8217;ll be posting the .net file with the configs, like last time. I will also have accessibility to the topology through a sandboxed Dynamips VM. This time you will be able to see the running config. You can run the .net on your own Dynamips server or you]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-3/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Lab #2</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-2/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-2/#comments</comments>
		<pubDate>Sat, 06 Mar 2010 14:15:42 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[CCIP]]></category>
		<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[MPLS]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=762</guid>
		<description><![CDATA[I don&#8217;t usually post on weekends, but I want to try out an idea for troubleshooting labs (and I&#8217;m bored). This is the second in the series. We got a lot of answers for the last one, most all of which were correct. I&#8217;ve started requiring approval for all comments, this way the answer won&#8217;t]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-2/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Lab #1</title>
		<link>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-1/</link>
		<comments>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-1/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 05:27:28 +0000</pubDate>
		<dc:creator>Colby</dc:creator>
				<category><![CDATA[Troubleshooting Labs]]></category>
		<category><![CDATA[BGP]]></category>
		<category><![CDATA[CCIE]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Dynagen]]></category>
		<category><![CDATA[Dynamips]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[Lab]]></category>
		<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://blog.alwaysthenetwork.com/?p=756</guid>
		<description><![CDATA[This will be the first in a series of troubleshooting labs. I will post a topology and the issue I&#8217;m seeing. Hopefully you guys will attempt to solve it and post your ideas, questions and solutions in the comments. We&#8217;ll start with a relatively easy one. Today we are having an issue with BGP neighbor]]></description>
		<wfw:commentRss>http://blog.alwaysthenetwork.com/troubleshooting-labs/troubleshooting-lab-1/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>
