<?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 Lab &#187; Switching</title>
	<atom:link href="http://ccielab.ro/tag/switching/feed/" rel="self" type="application/rss+xml" />
	<link>http://ccielab.ro</link>
	<description>Cry in the Lab, Laugh in the Datacenter</description>
	<lastBuildDate>Wed, 09 May 2012 12:02:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Weird Things on Cisco Switches &#8211; Case study #1: DTP</title>
		<link>http://ccielab.ro/2009/11/wierd-things-on-cisco-switches-case-study-1-dtp/</link>
		<comments>http://ccielab.ro/2009/11/wierd-things-on-cisco-switches-case-study-1-dtp/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 15:06:40 +0000</pubDate>
		<dc:creator>Alex Juncu</dc:creator>
				<category><![CDATA[CCNP]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[dtp]]></category>
		<category><![CDATA[trunking]]></category>

		<guid isPermaLink="false">http://ccielab.ro/?p=45</guid>
		<description><![CDATA[Networking is sometimes hard not because of the concepts that you need to apply, but because of the difference in implementation of some protocols on the equipment. For example, the default settings for DTP differ from one switch model to the next.
DTP (Dynamic Trunking Protocol) is used to negotiate a trunk link between two switches. [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify">Networking is sometimes hard not because of the concepts that you need to apply, but because of the difference in implementation of some protocols on the equipment. For example, the default settings for DTP differ from one switch model to the next.</p>
<p style="text-align: justify"><strong>DTP</strong> (Dynamic Trunking Protocol) is used to negotiate a trunk link between two switches. From the DTP point of view, a port can be &#8216;<strong>desirable</strong>&#8216; (it will actively try to negotiate a  trunk), &#8216;<strong>auto</strong>&#8216; (it will form a trunk if the other side wants to be a trunk) and &#8216;<strong>non-negotiate</strong>&#8216; (port will not negotiate the link). The reason for this protocol is to have a working access or trunk link immediately after you connect the switch to the network.   Most of the combinations are:</p>
<ul style="text-align: justify">
<li>auto &#8211; auto =&gt; access</li>
<li>auto &#8211; desirable =&gt; trunk</li>
<li>desirable-desirable =&gt; trunk</li>
<li>auto &#8211; trunk =&gt; trunk</li>
<li>auto &#8211; access =&gt; access</li>
<li>desirable &#8211; trunk =&gt; trunk</li>
<li>desirable &#8211; access =&gt; access</li>
</ul>
<p style="text-align: justify">What you should pay attention to is the default setting of a port on different switch models. On a <strong>2950 </strong>(Layer 2 switch) and a <strong>3550 </strong>(Layer 3 switch), a port is, before any configurations, in <strong>desirable</strong>. If you connect two of these switches, you will have a trunk link formed. On the other hand, on a <strong>2960</strong> or a <strong>3560</strong>, a port is in <strong>auto</strong>, so between these models, you will have an access port (by default, in VLAN 1). Even more problems could arrive when you have in a network switches of different models. If you connect a 2960 and a 2950, because the first is in auto and the second  is in desirable, a trunk link will be negotiated, so you should be careful when dealing with these kinds of situations.</p>
]]></content:encoded>
			<wfw:commentRss>http://ccielab.ro/2009/11/wierd-things-on-cisco-switches-case-study-1-dtp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

