<?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: CCIE R&amp;S &#8211; Sample Trouble Tickets &#8211; Part 3</title>
	<atom:link href="http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/</link>
	<description>Helping you become a Cisco Certified Internetwork Expert</description>
	<lastBuildDate>Sun, 14 Mar 2010 17:16:45 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kristopher Climie</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-85976</link>
		<dc:creator>Kristopher Climie</dc:creator>
		<pubDate>Mon, 21 Dec 2009 22:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-85976</guid>
		<description>Scott is correct -- FRS *may or may not* be on the exam, and it *may or may not* be configured for you in either the Troubleshooting or the Configuration section.

Regardless of what you thought to be the case, or how they have tested in the last few years, you *must* know how to do this.  In the grand scheme of things that we have to know for the current lab blueprint, FRS is one of the easiest and is a pretty much a gimme.

Now how their stupid troubleshooting virtual environment reacts to the config is a completely separate issue...</description>
		<content:encoded><![CDATA[<p>Scott is correct &#8212; FRS *may or may not* be on the exam, and it *may or may not* be configured for you in either the Troubleshooting or the Configuration section.</p>
<p>Regardless of what you thought to be the case, or how they have tested in the last few years, you *must* know how to do this.  In the grand scheme of things that we have to know for the current lab blueprint, FRS is one of the easiest and is a pretty much a gimme.</p>
<p>Now how their stupid troubleshooting virtual environment reacts to the config is a completely separate issue&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marlon</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-83083</link>
		<dc:creator>Marlon</dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-83083</guid>
		<description>To this date I always thought that as a CCIE R&amp;S candidate we do not need troubleshoot or get involved with frame-relay switch configuration, since that has been presented as a &#039;black blox&#039; to us.

Now we are saying that we should expect to fix configuration on the frame-relay switch(or the router simulating a frame-relay switch), right? OKKKKK.

Thanks Anthony.</description>
		<content:encoded><![CDATA[<p>To this date I always thought that as a CCIE R&amp;S candidate we do not need troubleshoot or get involved with frame-relay switch configuration, since that has been presented as a &#8216;black blox&#8217; to us.</p>
<p>Now we are saying that we should expect to fix configuration on the frame-relay switch(or the router simulating a frame-relay switch), right? OKKKKK.</p>
<p>Thanks Anthony.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandeep</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-83027</link>
		<dc:creator>Sandeep</dc:creator>
		<pubDate>Fri, 04 Dec 2009 07:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-83027</guid>
		<description>Thanks 
This is very helpful information</description>
		<content:encoded><![CDATA[<p>Thanks<br />
This is very helpful information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CCIE Pilot</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82837</link>
		<dc:creator>CCIE Pilot</dc:creator>
		<pubDate>Thu, 03 Dec 2009 15:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82837</guid>
		<description>Nick, I would certainly be familiar of how a FR switch be configured, troubleshoot and work. :-)</description>
		<content:encoded><![CDATA[<p>Nick, I would certainly be familiar of how a FR switch be configured, troubleshoot and work. <img src='http://blog.ine.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Morris, CCIE #4713</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82756</link>
		<dc:creator>Scott Morris, CCIE #4713</dc:creator>
		<pubDate>Thu, 03 Dec 2009 06:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82756</guid>
		<description>As was announced at last year&#039;s Networkers, while Frame-Relay may be &quot;less&quot; on this version of the blueprint, the frame-relay switch will NOT necessarily be configured for you.

So just like in the old days (my time!) you will need to be aware of how to configure it.  One quick and easy way (for customers of ours) is to take a look at the configuration of the BB1 router which acts as the frame-relay switch in our topology.</description>
		<content:encoded><![CDATA[<p>As was announced at last year&#8217;s Networkers, while Frame-Relay may be &#8220;less&#8221; on this version of the blueprint, the frame-relay switch will NOT necessarily be configured for you.</p>
<p>So just like in the old days (my time!) you will need to be aware of how to configure it.  One quick and easy way (for customers of ours) is to take a look at the configuration of the BB1 router which acts as the frame-relay switch in our topology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick G</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82697</link>
		<dc:creator>Nick G</dc:creator>
		<pubDate>Thu, 03 Dec 2009 01:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82697</guid>
		<description>@ Anthony - Well I guess that makes things more fun now doesn&#039;t it? :)</description>
		<content:encoded><![CDATA[<p>@ Anthony &#8211; Well I guess that makes things more fun now doesn&#8217;t it? <img src='http://blog.ine.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesus Espinoza</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82689</link>
		<dc:creator>Jesus Espinoza</dc:creator>
		<pubDate>Wed, 02 Dec 2009 23:29:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82689</guid>
		<description>Thank`s Anthony!!! Good excercise!!! Nowadays, I been having troubles configuring FR DTE Routers because of these issues on my ISP. Now I understand the reason why FR connection failed on my side. Excellent!!!</description>
		<content:encoded><![CDATA[<p>Thank`s Anthony!!! Good excercise!!! Nowadays, I been having troubles configuring FR DTE Routers because of these issues on my ISP. Now I understand the reason why FR connection failed on my side. Excellent!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CCIE R/S 4.X Expanded Study Blueprint - CCIE Blog</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82684</link>
		<dc:creator>CCIE R/S 4.X Expanded Study Blueprint - CCIE Blog</dc:creator>
		<pubDate>Wed, 02 Dec 2009 21:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82684</guid>
		<description>[...] CCIE R&amp;S &#8211; Sample Trouble Tickets &#8211; Part 3  [...]</description>
		<content:encoded><![CDATA[<p>[...] CCIE R&amp;S &#8211; Sample Trouble Tickets &#8211; Part 3  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Sequeira, #15626</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82682</link>
		<dc:creator>Anthony Sequeira, #15626</dc:creator>
		<pubDate>Wed, 02 Dec 2009 21:11:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82682</guid>
		<description>All of the devices in the Troubleshooting section are accessible - including the Frame Relay switches.</description>
		<content:encoded><![CDATA[<p>All of the devices in the Troubleshooting section are accessible &#8211; including the Frame Relay switches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MCL.Nicolas</title>
		<link>http://blog.ine.com/2009/12/01/ccie-rs-sample-trouble-tickets-part-3/comment-page-1/#comment-82628</link>
		<dc:creator>MCL.Nicolas</dc:creator>
		<pubDate>Wed, 02 Dec 2009 13:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ine.com/?p=2911#comment-82628</guid>
		<description>Very nice !!!!! thanks anthony for this layered troubleshooting ticket ! 

it will Help me in my everyday job !</description>
		<content:encoded><![CDATA[<p>Very nice !!!!! thanks anthony for this layered troubleshooting ticket ! </p>
<p>it will Help me in my everyday job !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
