<?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>FirstDigest &#187; Tips&amp;Tricks</title>
	<atom:link href="http://www.firstdigest.com/category/tips-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.firstdigest.com</link>
	<description>Technical blog</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:15:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>InterVLAN routing using Private VLANs</title>
		<link>http://www.firstdigest.com/2011/09/intervlan-routing-using-private-vlans/</link>
		<comments>http://www.firstdigest.com/2011/09/intervlan-routing-using-private-vlans/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 13:04:06 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Cisco-routing]]></category>
		<category><![CDATA[Cisco-switching]]></category>
		<category><![CDATA[cisco private-vlan intervlan routing]]></category>
		<category><![CDATA[intervlan routing]]></category>
		<category><![CDATA[private vlan]]></category>
		<category><![CDATA[private vlan configuration]]></category>
		<category><![CDATA[private vlan routing]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=3363</guid>
		<description><![CDATA[<p>Private VLANs  is one possible solutions for service providers to offer secure connections to their customers and avoid inter-vlan communication in the same switched environment.</p> <p>I&#8217;m sure that you heard (and most probably practice already) InterVLAN routing. When it comes to Private VLANs the routing part may be a bit tricky. Keep in mind that this is not something that I would recommend to use as a standard in a productive environment, but for things like Cisco exams (e.g. CCIE R&#38;S) or last resort solution, [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2011/09/intervlan-routing-using-private-vlans/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Would you do such things to an ISR 819?</title>
		<link>http://www.firstdigest.com/2011/09/would-you-do-such-things-to-an-isr-819/</link>
		<comments>http://www.firstdigest.com/2011/09/would-you-do-such-things-to-an-isr-819/#comments</comments>
		<pubDate>Fri, 09 Sep 2011 10:03:41 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[819]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[isr]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=3232</guid>
		<description><![CDATA[<p>Lucky there is a big disclaimer at the beginning of this video. Otherwise I would be tempted to test such things and then plug it in to see if it still start (at least) and run.</p> <p>It&#8217;s a nice commercial from Cisco, but to be honest I feel bad for this poor device:</p> <p></p> <p style="text-align: center;">]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2011/09/would-you-do-such-things-to-an-isr-819/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interface software loop</title>
		<link>http://www.firstdigest.com/2011/08/interface-software-loop/</link>
		<comments>http://www.firstdigest.com/2011/08/interface-software-loop/#comments</comments>
		<pubDate>Tue, 30 Aug 2011 08:13:13 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Cisco-routing]]></category>
		<category><![CDATA[cisco loop]]></category>
		<category><![CDATA[interface loop]]></category>
		<category><![CDATA[interface soft loop]]></category>
		<category><![CDATA[loop testing]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=3165</guid>
		<description><![CDATA[<p>If you ever worked in an environment where you have to deal with leased / dedicated lines provider by your SP (service provider) then you know that whenever it&#8217;s a problem on the line they request, if possible, to put a loop on the line from one end toward the other end, so they can do some measurements. Usually from my experience with SP, this is a standard approach in case that they don&#8217;t know exactly what problem is with your line or where the [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2011/08/interface-software-loop/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Cisco IOS release naming</title>
		<link>http://www.firstdigest.com/2011/07/cisco-ios-release-naming/</link>
		<comments>http://www.firstdigest.com/2011/07/cisco-ios-release-naming/#comments</comments>
		<pubDate>Mon, 11 Jul 2011 13:42:26 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[IOS]]></category>
		<category><![CDATA[naming convention]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=3160</guid>
		<description><![CDATA[<p>Most probably you already know this, but for those who are interested, here is a list of the letter definitions for Cisco IOS release trains. In more human terms, if you have loaded an IOS image like c2900-universalk9-mz.SPA.150-1.M5.bin, what those letters (in this case SPA) mean:</p> A = Aggregation/Access Server/Dial technology B = Broadband C = Core routers (11.1CA, 11.1CT, 11.1CC) D = xDSL technology E = Enterprise feature set F = Feature Specific enhancements (11.2F) G = Gigabit Switch Routers (GSR) H = SDH/SONET [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2011/07/cisco-ios-release-naming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to connect Vyatta to Cisco using VirtualBox and GNS3</title>
		<link>http://www.firstdigest.com/2010/08/connect-vyatta-to-cisco-using-virtualbox-gns3/</link>
		<comments>http://www.firstdigest.com/2010/08/connect-vyatta-to-cisco-using-virtualbox-gns3/#comments</comments>
		<pubDate>Tue, 17 Aug 2010 10:40:28 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Free-tools]]></category>
		<category><![CDATA[GNS3]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[cisco on gns3]]></category>
		<category><![CDATA[connect vyatta to cisco]]></category>
		<category><![CDATA[how to configure vyatta network]]></category>
		<category><![CDATA[how to install vyatta]]></category>
		<category><![CDATA[install vyatta on virtualbox]]></category>
		<category><![CDATA[simple vyatta configuration]]></category>
		<category><![CDATA[vyatta configuration]]></category>
		<category><![CDATA[vyatta interface configuration]]></category>
		<category><![CDATA[vyatta on virtualbox]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2836</guid>
		<description><![CDATA[<p>&#8220;<a title="Vyatta" href="http://www.vyatta.com/" target="_blank">Vyatta</a> is  a software-based, open-source, network operating system that is portable to standard x86 hardware as well as common virtualization and cloud computing platforms. By deploying Vyatta, users benefit from a flexible enterprise-class routing and security feature set capable of scaling from DSL to 20Gbps performance at a fraction of the cost of proprietary solutions.&#8221;</p> <p>Shortly, you take this piece of software, install it on a x86 machine (any decent PC with quality network card will do) and have yourself a network [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/08/connect-vyatta-to-cisco-using-virtualbox-gns3/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Cisco 2900 &#8211; Interface related chassis modification</title>
		<link>http://www.firstdigest.com/2010/08/cisco-2900-interface-related-chassis-modification/</link>
		<comments>http://www.firstdigest.com/2010/08/cisco-2900-interface-related-chassis-modification/#comments</comments>
		<pubDate>Mon, 09 Aug 2010 11:41:50 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[cisco 2900 chassis]]></category>
		<category><![CDATA[cisco 2900 module]]></category>
		<category><![CDATA[features]]></category>
		<category><![CDATA[how to change cisco module]]></category>
		<category><![CDATA[how to change module in 2900]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2793</guid>
		<description><![CDATA[<p><br /> </p> <br /> <p></p> <p>The Cisco Enhanced EtherSwitch Service Modules seen above, expands the router&#8217;s capabilities by integrating Layer 2 and Layer 3 switching feature sets identical to those found in the Cisco Catalyst 3560-E and Catalyst 2960 Series Switches.</p> <p>The new Cisco Enhanced EtherSwitch Service Modules are the first modules to take advantage of the increased capabilities on the Cisco 3900 and 2900 Series Integrated Services Routers. Additionally, these service modules enable Cisco&#8217;s industry-leading power initiatives, Cisco EnergyWise®, Cisco Enhanced Power over [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/08/cisco-2900-interface-related-chassis-modification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco IOS: single user access in CLI configuration terminal</title>
		<link>http://www.firstdigest.com/2010/07/cisco-ios-single-user-access-in-cli-configuration-terminal/</link>
		<comments>http://www.firstdigest.com/2010/07/cisco-ios-single-user-access-in-cli-configuration-terminal/#comments</comments>
		<pubDate>Wed, 07 Jul 2010 10:00:17 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[cli]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[configuration mode]]></category>
		<category><![CDATA[configuration terminal]]></category>
		<category><![CDATA[conflict]]></category>
		<category><![CDATA[mode exclusive]]></category>
		<category><![CDATA[one user at the time]]></category>
		<category><![CDATA[single user]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2729</guid>
		<description><![CDATA[<p><br /> </p> <p>Usually big companies with large network have a dedicated department which deals with all the network configuration.  The problem that I have in mind is when this department is splitted over large geographical areas (e.g. some colleagues in Europe, some in Asia and some in America) it may happen that more than one colleague is working on the same device at the time.</p> <p>This can cause overlapping configuration or other problems, due to the fact that more than one config is applied [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/07/cisco-ios-single-user-access-in-cli-configuration-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco: Use TTCP to test together with TTCPW or JPerf</title>
		<link>http://www.firstdigest.com/2010/04/cisco-use-ttcp-to-test-together-with-ttcpw-or-jperf/</link>
		<comments>http://www.firstdigest.com/2010/04/cisco-use-ttcp-to-test-together-with-ttcpw-or-jperf/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 13:27:26 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Cisco IOS]]></category>
		<category><![CDATA[Cisco Systems]]></category>
		<category><![CDATA[connection]]></category>
		<category><![CDATA[Education]]></category>
		<category><![CDATA[IP address]]></category>
		<category><![CDATA[iperf]]></category>
		<category><![CDATA[jperf]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Microsoft Windows]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[tcp connectivity]]></category>
		<category><![CDATA[tcp testing]]></category>
		<category><![CDATA[ttcp]]></category>
		<category><![CDATA[ttcpw]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2610</guid>
		<description><![CDATA[<p>In one<a title="Test TCP connection with TTCP" href="http://www.firstdigest.com/2008/11/cisco-hidden-tools-testing-tcp-connection/" target="_self"> my previous posts</a>, I shown you how to test a connection using a hidden Cisco IOS tool called <a class="zem_slink" title="Ttcp" rel="wikipedia" href="http://en.wikipedia.org/wiki/Ttcp">TTCP</a>.  A few days ago I run into an issue. I had to test a <a class="zem_slink" title="Transmission Control Protocol" rel="wikipedia" href="http://en.wikipedia.org/wiki/Transmission_Control_Protocol">TCP</a> connection to a remote Cisco router, but I had not other router on which to initiate the TTCP connection. As explained in <a title="Test TCP connection with TTCP" href="http://www.firstdigest.com/2008/11/cisco-hidden-tools-testing-tcp-connection/" target="_blank">Testing TCP Connection [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/04/cisco-use-ttcp-to-test-together-with-ttcpw-or-jperf/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Cisco tips: Track down communication issues &#8211; Part 2</title>
		<link>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-2/</link>
		<comments>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-2/#comments</comments>
		<pubDate>Tue, 16 Mar 2010 11:58:12 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[Cisco Systems]]></category>
		<category><![CDATA[communication error]]></category>
		<category><![CDATA[Data Communications]]></category>
		<category><![CDATA[Data Link Layer]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[interface errors]]></category>
		<category><![CDATA[packet drop]]></category>
		<category><![CDATA[packet loss]]></category>
		<category><![CDATA[Physical Layer]]></category>
		<category><![CDATA[queue]]></category>
		<category><![CDATA[storm-control]]></category>
		<category><![CDATA[switch]]></category>
		<category><![CDATA[switch port]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2519</guid>
		<description><![CDATA[<p>In the <a title="Track down communication issues" href="http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-1/" target="_blank">1st Part of this series</a>, I&#8217;ve described the most common steps that you should follow to <a class="zem_slink" title="Troubleshooting" rel="wikipedia" href="http://en.wikipedia.org/wiki/Troubleshooting">troubleshoot</a> a total lack of communication between a <a class="zem_slink" title="Data Link Layer" rel="wikipedia" href="http://en.wikipedia.org/wiki/Data_Link_Layer">Layer 2</a> device (Cisco switch) and an end user connected device. As I promised here is the second part, in which I&#8217;ll try to show you what you can check when you have no problem with connection, but still you encounter a degradation [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Cisco tips: Track down communication issues &#8211; Part 1</title>
		<link>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-1/</link>
		<comments>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-1/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 14:55:51 +0000</pubDate>
		<dc:creator>Calin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[bpdu]]></category>
		<category><![CDATA[bpduguard]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[Cisco Systems]]></category>
		<category><![CDATA[communication issues]]></category>
		<category><![CDATA[duplex]]></category>
		<category><![CDATA[Greg Ferro]]></category>
		<category><![CDATA[layer 2]]></category>
		<category><![CDATA[mac access group]]></category>
		<category><![CDATA[mac-address]]></category>
		<category><![CDATA[Network switch]]></category>
		<category><![CDATA[port security]]></category>
		<category><![CDATA[Ports]]></category>
		<category><![CDATA[Spanning tree protocol]]></category>
		<category><![CDATA[spanning-tree]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[stp]]></category>
		<category><![CDATA[switch]]></category>
		<category><![CDATA[switchport]]></category>
		<category><![CDATA[Virtual LAN]]></category>

		<guid isPermaLink="false">http://www.firstdigest.com/?p=2458</guid>
		<description><![CDATA[<p>You know how sometimes you plug in everything, configure device / ports and then the un-expected result is &#8220;not working&#8221;. Then you start to troubleshoot, which is a good point, but very important is where are you looking for the root cause of your issue.</p> <p>A lot of people who have communication issue start by issuing a ping from one end to the other one. This is a good approach when somebody is reporting service issue (e.g. my webserver doesn&#8217;t work) as with the ping [...]]]></description>
		<wfw:commentRss>http://www.firstdigest.com/2010/03/cisco-tips-track-down-communication-issues-part-1/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (Feed is rejected)
Page Caching using disk: enhanced (User agent is rejected)
Content Delivery Network via cdn.firstdigest.com

Served from: www.firstdigest.com @ 2012-02-07 18:03:06 -->
