<?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>.::&#124;Dide(3)d&#039;s Blog::. &#187; Tunneling</title>
	<atom:link href="http://www.dide3d.com/category/cisco-stuff/tunneling-cisco-stuff/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dide3d.com</link>
	<description>Get Tech&#039;d...!                                              </description>
	<lastBuildDate>Wed, 28 Jul 2010 09:50:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>QinQ: 802.1q Tunneling on Cisco Switches</title>
		<link>http://www.dide3d.com/2009/03/qinq-8021q-tunneling-on-cisco-switches/</link>
		<comments>http://www.dide3d.com/2009/03/qinq-8021q-tunneling-on-cisco-switches/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 15:00:55 +0000</pubDate>
		<dc:creator>Divin John</dc:creator>
				<category><![CDATA[Cisco *STUFF*]]></category>
		<category><![CDATA[QinQ]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[Tunneling]]></category>
		<category><![CDATA[dot1q]]></category>
		<category><![CDATA[802.1q tunneling]]></category>
		<category><![CDATA[L2PT]]></category>
		<category><![CDATA[l2pt tunneiling]]></category>
		<category><![CDATA[tunneling]]></category>

		<guid isPermaLink="false">http://www.dide3d.com/?p=702</guid>
		<description><![CDATA[One of Metro Ethernet solution to extend Layer 2 Ethernet Connection between two customer sites is use 802.1q Tunneling, also known as QinQ. QinQ concept is explained based on the diagram below: Customer Switch Site A and B connected to SP (Service Provider) Edge Switch, usually use trunk mode on the port that facing to [...]]]></description>
			<content:encoded><![CDATA[<div class="postentry">
<div class="snap_preview">
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">One of Metro Ethernet solution to extend Layer 2 Ethernet Connection between two customer sites is use 802.1q Tunneling, also known as QinQ.</span></p>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">QinQ concept is explained based on the diagram below:</span></p>
<p class="MsoNormal" style="text-align: justify;"><a href="http://irwanp.files.wordpress.com/2008/06/qinq11.jpg"><img class="alignnone size-full wp-image-28" src="http://irwanp.files.wordpress.com/2008/06/qinq11.jpg?w=470&amp;h=170" alt="" width="470" height="170" /></a></p>
<p class="MsoNormal" style="text-align: justify;">
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">Customer Switch Site A and B connected to SP (Service Provider) Edge Switch, usually use trunk mode on the port that facing to SP. SP Edge Switch use 802.1q Tunnel mode. Service Provider usually allocated one VLAN tag per-customer and used to tagging ethernet frames that coming from customer.</span></p>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">How the 802.1q work? See the example below:</span></p>
<p><a href="http://irwanp.files.wordpress.com/2008/06/qinq2.jpg"><img class="alignnone size-full wp-image-27" src="http://irwanp.files.wordpress.com/2008/06/qinq2.jpg?w=470&amp;h=230" alt="" width="470" height="230" /></a></p>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">Every frames from Customer is tagged with the SP allocated VLAN tag for customer. This process done in the SP Edge Switch that facing to the Customer Switch site A. The existing VLAN tag of the frames is not changed. So, every frames from customer will have two VLAN tag in the SP Networks. The inner tag is the customers real VLAN tag, and the outer tag is the SP VLAN Tag allocated to the customer. In the SP Edge Swtich that facing to the Site B, the outer VLAN tag is stripped, and the frames is forwarded to the Customer Site B switch. </span></p>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">In the diagram above, we look that every customers can use the same VLAN tags, and this will not conflicted. Every customers can not see the other customer even their VLAN tags is same, because Service Provider will tagging the customers frame with the unique per-customer VLAN tag. We see that Customer XYZ is allocated with the VLAN Tag 10 and Customer ABC with the VLAN tag 9.</span></p>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">Because the port from customer switch that connected to SP Edge switch can use the trunk-mode, so there are a few requirement: </span></p>
<ol style="margin-top: 0pt;" type="1">
<li class="MsoNormal"><span style="font-size: 10pt; font-family: Arial;">Port in the SP Edge switch that facing to the customer must set BPDU Filter and Root Guard to prevent the customer switches act as a STP root switch. The customer switches can see the BDPU from their opponent switches.</span></li>
<li class="MsoNormal"><span style="font-size: 10pt; font-family: Arial;">By default, VTP between two customer switches across the Service Provider network is not work. You must configure protocol tunneling to enabled the VTP between the customer switches in both of the SP Edge Switches.</span></li>
<li class="MsoNormal"><span style="font-size: 10pt; font-family: Arial;">UDLD, PAgP and CDP (disabled by default) can work.</span></li>
<li class="MsoNormal"><span style="font-size: 10pt; font-family: Arial;">The maximum VLAN that can allocated to the customer is 4096 VLAN ID, because the VLAN ID field in the 802.1q frame is 12 bits.</span></li>
</ol>
<p class="MsoNormal" style="text-align: justify;"><span style="font-size: 10pt; font-family: Arial;">See the example configuration of Service Provider Edge Switch below:</span></p>
<p><span style="font-size: 10pt; font-family: Courier;">SPE-Site-A#sh run int f0/10</span><br />
<span style="font-size: 10pt; font-family: Courier;">interface FastEthernet0/10</span><br />
<span style="font-size: 10pt; font-family: Courier;">description Connection to Customer-XYZ-Site-A</span><br />
<span style="font-size: 10pt; font-family: Courier;"><span> </span>switchport access vlan 10</span><br />
<span style="font-size: 10pt; font-family: Courier;"><span> </span>switchport mode dot1q-tunnel</span></p>
<p><span style="font-size: 10pt; font-family: Courier;">SPE-Site-A#sh run int f0/9</span><br />
<span style="font-size: 10pt; font-family: Courier;">interface FastEthernet0/9</span><br />
<span style="font-size: 10pt; font-family: Courier;">description Connection to Customer-ABC-Site-A</span><br />
<span style="font-size: 10pt; font-family: Courier;"><span> </span>switchport access vlan 9</span><br />
<span style="font-size: 10pt; font-family: Courier;"><span> </span>switchport mode dot1q-tunnel</span><br />
Original post @ http://irwanp.wordpress.com/2008/06/23/qinq-8021q-tunneling-on-cisco-switches/</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.dide3d.com/2009/03/qinq-8021q-tunneling-on-cisco-switches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
