<?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>#SH RUN &#187; switch</title>
	<atom:link href="http://sh-run.com/tag/switch/feed/" rel="self" type="application/rss+xml" />
	<link>http://sh-run.com</link>
	<description></description>
	<lastBuildDate>Tue, 27 Mar 2012 14:30:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to configure a VTP Server and Client</title>
		<link>http://sh-run.com/2010/10/25/how-to-configure-a-vtp-server-and-client/</link>
		<comments>http://sh-run.com/2010/10/25/how-to-configure-a-vtp-server-and-client/#comments</comments>
		<pubDate>Mon, 25 Oct 2010 20:41:31 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Configuration]]></category>
		<category><![CDATA[802.1q]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[switch]]></category>
		<category><![CDATA[Trunking]]></category>
		<category><![CDATA[VLAN]]></category>
		<category><![CDATA[VTP]]></category>

		<guid isPermaLink="false">http://sh-run.com/?p=41</guid>
		<description><![CDATA[VLAN Trunking Protocol (VTP) is Cisco&#8217;s proprietary protocal for propagating VLAN information that exists on one switch to another switch.  The advantage of VTP is that it eliminates the need to create VLANs on each individual switch within a site.  Instead you only need to create your VLANs on the switch you designate as the&#8230;]]></description>
			<content:encoded><![CDATA[<p>VLAN Trunking Protocol (VTP) is Cisco&#8217;s proprietary protocal for propagating VLAN information that exists on one switch to another switch.  The advantage of VTP is that it eliminates the need to create VLANs on each individual switch within a site.  Instead you only need to create your VLANs on the switch you designate as the server and assign your other switches to the role of a client.</p>
<p>For the purposes of this example Switch A will be the VTP Server and Switch B will be the VTP client.</p>
<p><a href="http://sh-run.com/wordpressSHRUN/wp-content/uploads/2010/03/VTP-drawing.jpg"><img class="alignnone size-medium wp-image-42" title="VTP switch diagram" src="http://sh-run.com/wordpressSHRUN/wp-content/uploads/2010/03/VTP-drawing-300x72.jpg" alt="VTP switch diagram" width="300" height="72" /></a></p>
<ol>
<li>Setup VTP server role for Switch A</li>
<li>Create VLANs on Switch A</li>
<li>Setup VTP client role for Switch B</li>
<li>Setup 802.1q Trunking between Switch A and Switch B</li>
<li>Assign VLANs to specific interfaces</li>
</ol>
<p>The configuration goes like this:<br />
<strong>1. Setup VTP server on Switch A</strong></p>
<blockquote><p>SwitchA#vlan database (enter vlan configuration mode)<br />
SwitchA(vlan)#vtp server (sets the VTP mode)<br />
SwitchA(vlan)#vtp password MYPASSWORD (optional, assign a password to the VTP domain)<br />
SwitchA(vlan)#vtp domian CORP (assigns a name to the VTP domain)<br />
SwitchA(vlan)#exit (exit vlan configuration mode)</p></blockquote>
<p><strong>2. Create VLANs on Switch A (the VTP server)</strong></p>
<blockquote><p>SwitchA#configure teminal (enter into configuration mode)<br />
SwitchA(config)#vlan 2 (defines the vlan, in this case vlan 2)<br />
SwitchA(config)#vlan 2 name accounting (assigns a name to the vlan for description)<br />
SwitchA(config)#exit (exit configuration mode)</p></blockquote>
<p><strong>3. Setup VTP client role on Switch B</strong></p>
<blockquote><p>SwitchB#vlan database (enter vlan configuration mode)<br />
SwitchB(vlan)#vtp client (sets the VTP mode)<br />
SwitchB(vlan)#vtp domain CORP (defines the VTP domain name)<br />
SwitchB(vlan)#vtp password MYPASSWORD (the password for the VTP domain)<br />
SwitchB(vlan)#exit (exits VTP configuration mode)</p></blockquote>
<p><strong>4. Setup Trunking between Switch A and Switch B</strong></p>
<blockquote><p>SwitchA(config)#configure terminal (enter the configuration mode)<br />
SwitchA(config)#interface fastethernet 0/1 (select ethernet port 1)<br />
SwitchA(config-if)#switchport mode trunk (set port 1 as a trunk port)<br />
SwitchA(config-if)#switchport trunk encapsulation dot1q (set the trunk type)<br />
SwitchA(config-if)#end (exit configuration mode)</p>
<p>SwitchB(config)#interface fastethernet 0/1 (select ethernet port 1)<br />
SwitchB(config-if)#switchport mode trunk  (set port 1 as a trunk port)<br />
SwitchA(config-if)#switchport trunk encapsulation dot1q (set the trunk type)<br />
SwitchB(config-if)#end (exit configuration mode)</p></blockquote>
<p><strong>5. Assign VLANs to particular interfaces</strong></p>
<blockquote><p>SwitchA(config)#configure terminal (enter configuration mode)<br />
SwitchA(config)#interface fastethernet 0/2 (select the interface)<br />
SwitchA(config-if)# switchport access vlan2 (assign the VLAN to the interface)<br />
SwitchA(config-if)#exit (exit interface configuration)</p></blockquote>
<p>Of course there are a few other options, but the above example covers all the basics you need to know to setup VTP on your switches.</p>
]]></content:encoded>
			<wfw:commentRss>http://sh-run.com/2010/10/25/how-to-configure-a-vtp-server-and-client/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Helpful Cisco Documents</title>
		<link>http://sh-run.com/2009/06/11/helpful-cisco-documents/</link>
		<comments>http://sh-run.com/2009/06/11/helpful-cisco-documents/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 13:28:33 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[catalyst]]></category>
		<category><![CDATA[docs]]></category>
		<category><![CDATA[guide]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[switch]]></category>

		<guid isPermaLink="false">http://sh-run.com/?p=32</guid>
		<description><![CDATA[I always need to look up features on different Cisco routers and switches.  Cisco actually produces two documents that let you quickly see all the available models and associated features: Cisco Router Guide Cisco Catalyst Switch Guide]]></description>
			<content:encoded><![CDATA[<p>I always need to look up features on different Cisco routers and switches.  Cisco actually produces two documents that let you quickly see all the available models and associated features:</p>
<p><a title="Cisco Router Guide" href="http://www.cisco.com/en/US/prod/collateral/routers/ps5855/prod_brochure0900aecd8019dc1f.pdf" target="_blank">Cisco Router Guide<br />
Cisco Catalyst Switch Guide</a></p>
]]></content:encoded>
			<wfw:commentRss>http://sh-run.com/2009/06/11/helpful-cisco-documents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to find the port a device is plugged into</title>
		<link>http://sh-run.com/2009/06/03/how-to-find-the-port-a-device-is-plugged-into/</link>
		<comments>http://sh-run.com/2009/06/03/how-to-find-the-port-a-device-is-plugged-into/#comments</comments>
		<pubDate>Wed, 03 Jun 2009 13:34:45 +0000</pubDate>
		<dc:creator>Bill</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[switch]]></category>

		<guid isPermaLink="false">http://sh-run.com/?p=8</guid>
		<description><![CDATA[Have you ever needed to quickly find out which switch port a network device is plugged into and you only know the IP address of the device?  You could always trace the cables in your data closet and drive yourself crazy or you could use a few simple commands on your switch and quickly find&#8230;]]></description>
			<content:encoded><![CDATA[<p>Have you ever needed to quickly find out which switch port a network device is plugged into and you only know the IP address of the device?  You could always trace the cables in your data closet and drive yourself crazy or you could use a few simple commands on your switch and quickly find it.</p>
<p><strong>sh ip arp | inc &lt;ip address&gt;</strong><br />
<em>This will return the mac address<br />
</em><strong>sh mac-address-table | inc &lt;mac address&gt;</strong><br />
<em>This will return the switch port<br />
If the IP address is on another switch, the port that is returned in the output will be for the trunked port that goes to the next &#8220;hop&#8221;.  Go to the next switch and repeat.</em><br />
<strong>sh run int &lt;switch port&gt;<br />
</strong><em>This will return the config for that interface</em></p>
<p><em>Here is an example:</em></p>
<blockquote><p>switch01#sh ip arp | inc 172.16.11.200<br />
Internet  172.16.11.200           0   0080.a38a.10dc  ARPA   Vlan11<br />
switch01#sh mac-address-table | inc 0080.a38a.10dc<br />
  11    0080.a38a.10dc   dynamic ip                     GigabitEthernet3/3 <br />
switch01#sh run int gi3/3<br />
Building configuration&#8230;<br />
Current configuration : 152 bytes<br />
!<br />
interface GigabitEthernet3/3<br />
 description IBM APPLICATION SERVER<br />
 switchport access vlan 11<br />
 switchport mode access<br />
 qos trust dscp<br />
 spanning-tree portfast<br />
end<br />
switch01#</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://sh-run.com/2009/06/03/how-to-find-the-port-a-device-is-plugged-into/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

