<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Zakir A. Khan - Bridging &amp; Switching</title>
    <link>http://blog.zakir.net/</link>
    <description>CCIE# 25121</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.3.1 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Catalyst Link-State Tracking </title>
    <link>http://blog.zakir.net/index.php?/archives/38-Catalyst-Link-State-Tracking.html</link>
            <category>Bridging &amp; Switching</category>
    
    <comments>http://blog.zakir.net/index.php?/archives/38-Catalyst-Link-State-Tracking.html#comments</comments>
    <wfw:comment>http://blog.zakir.net/wfwcomment.php?cid=38</wfw:comment>

    <slash:comments>4</slash:comments>
    <wfw:commentRss>http://blog.zakir.net/rss.php?version=2.0&amp;type=comments&amp;cid=38</wfw:commentRss>
    

    <author>nospam@example.com (Zakir A. Khan, CCIE# 25121)</author>
    <content:encoded>
    &lt;p&gt;&lt;font style=&quot;BACKGROUND-COLOR: #faffff&quot;&gt;Catalyst 3750/3560 supports &amp;quot;&lt;strong&gt;Link-State Tracking&lt;/strong&gt;&amp;quot;. It is a simple and straightforward feature. First, some ports are defined upstream ports and some as downstream ports. Then, if all of the upstream ports go down, all the associated downstream ports are forced into the error-disabled (down) state automatically.&lt;/font&gt;&lt;/p&gt;&lt;p&gt;&lt;font style=&quot;BACKGROUND-COLOR: #faffff&quot;&gt;In the following example, if the upstream FastEthernet0/1 interface goes down, the downstream interface FastEthernet0/2 will go into a link down state.&lt;/font&gt;&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://blog.zakir.net/index.php?/archives/38-Catalyst-Link-State-Tracking.html#extended&quot;&gt;Continue reading &quot;Catalyst Link-State Tracking &quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sat, 13 Jun 2009 11:28:20 -0400</pubDate>
    <guid isPermaLink="false">http://blog.zakir.net/index.php?/archives/38-guid.html</guid>
    <category>catalyst</category>

</item>
<item>
    <title>Stacked VLAN (Q-in-Q on a router)</title>
    <link>http://blog.zakir.net/index.php?/archives/34-Stacked-VLAN-Q-in-Q-on-a-router.html</link>
            <category>Bridging &amp; Switching</category>
    
    <comments>http://blog.zakir.net/index.php?/archives/34-Stacked-VLAN-Q-in-Q-on-a-router.html#comments</comments>
    <wfw:comment>http://blog.zakir.net/wfwcomment.php?cid=34</wfw:comment>

    <slash:comments>6</slash:comments>
    <wfw:commentRss>http://blog.zakir.net/rss.php?version=2.0&amp;type=comments&amp;cid=34</wfw:commentRss>
    

    <author>nospam@example.com (Zakir A. Khan, CCIE# 25121)</author>
    <content:encoded>
    &lt;p&gt;A cisco router can be configured to do double tagging (Q-in-Q) on VLANs. Cisco calls it &amp;quot;Stacked VLAN Processing&amp;quot;. Per cisco website, &amp;quot;&lt;em&gt;A double-tagged, stacked VLAN frame is terminated or tunneled on an Ethernet subinterface by using the encapsulation dot1q second-dot1q command that specifies the two VLAN ID tags: an outer SP-VLAN ID and an inner CE-VLAN ID&lt;/em&gt;&amp;quot;. So the command syntax for stacked VLAN is &amp;quot;&lt;em&gt;encapsulation dot1q &amp;lt;outer-vlan-id&amp;gt; second-dot1q &amp;lt;inner-vlan-id&amp;gt;&lt;/em&gt;&amp;quot; or &amp;quot;&lt;em&gt;encapsulation dot1q &amp;lt;sp-vlan-id&amp;gt; second-dot1q &amp;lt;ce-vlan-id&amp;gt;&lt;/em&gt;&amp;quot;.&lt;/p&gt;&lt;p align=&quot;center&quot;&gt;&lt;a class=&quot;serendipity_image_link&quot; onclick=&quot;F1 = window.open(&#039;/uploads/images/BS-1.jpg&#039;,&#039;Zoom&#039;,&#039;height=157,width=515,top=329,left=390,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot; href=&quot;http://blog.zakir.net/uploads/images/BS-1.jpg&quot;&gt;&lt;img class=&quot;serendipity_image_center&quot; style=&quot;BORDER-RIGHT: 0px; PADDING-RIGHT: 5px; BORDER-TOP: 0px; PADDING-LEFT: 5px; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px&quot; height=&quot;142&quot; src=&quot;http://blog.zakir.net/uploads/images/BS-1.jpg&quot; width=&quot;500&quot; /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p align=&quot;left&quot;&gt;Ethernet subinterfaces on R1 are configured for the stacked VLAN processing. Here R1 is tagging inner VLANs 10 and 20 with  outer VLAN 100 which is preserved all the way upto SW2&#039;s dot1q tunnel port (fa0/2). On fa0/2 port SW2 strips the outer VLAN 100 and sends the inner VLANs 10 and 20 to R2. The routers and switches are configured as following:&lt;/p&gt; &lt;br /&gt;&lt;a href=&quot;http://blog.zakir.net/index.php?/archives/34-Stacked-VLAN-Q-in-Q-on-a-router.html#extended&quot;&gt;Continue reading &quot;Stacked VLAN (Q-in-Q on a router)&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 22 May 2009 20:11:32 -0400</pubDate>
    <guid isPermaLink="false">http://blog.zakir.net/index.php?/archives/34-guid.html</guid>
    <category>q-in-q</category>
<category>vlan</category>

</item>

</channel>
</rss>