<?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>Braindump &#187; Cisco</title>
	<atom:link href="http://www.curtis-lamasters.com/category/cisco/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.curtis-lamasters.com</link>
	<description>Another TechBlog</description>
	<lastBuildDate>Sun, 25 Jul 2010 09:19:00 +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>Cisco &#8211; tcp-small-servers and udp-small-servers</title>
		<link>http://www.curtis-lamasters.com/2009/02/19/cisco-tcp-small-servers-and-udp-small-servers/</link>
		<comments>http://www.curtis-lamasters.com/2009/02/19/cisco-tcp-small-servers-and-udp-small-servers/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 05:57:25 +0000</pubDate>
		<dc:creator>clamasters</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[blog]]></category>

		<guid isPermaLink="false">http://www.curtis-lamasters.com/?p=221</guid>
		<description><![CDATA[For some truly unknown reason, Cisco&#8217;s devices still have support for &#8220;small servers&#8221; or &#8220;simple services&#8221;. Examples of these include echo, chargen, daytime and discard.  An attacker could possibly start a denial of service attack (DoS) against one or more network devices with those configured.  In this case; echo and chargen are to blame by [...]]]></description>
			<content:encoded><![CDATA[<p>For some truly unknown reason, Cisco&#8217;s devices still have support for &#8220;small servers&#8221; or &#8220;simple services&#8221;. Examples of these include echo, chargen, daytime and discard.  An attacker could possibly start a denial of service attack (DoS) against one or more network devices with those configured.  In this case; echo and chargen are to blame by allowing an attacker to cause  the chargen service to hit the echo services causing an endless loop of character generation and echo between the two hosts.  To disable this, simply enter the following commands:</p>
<p style="padding-left: 30px;"><code>configure terminal<br />
no service tcp-small-servers<br />
no service udp-small-servers</code></p>
<p>These commands can be run on nearly all IOS based Cisco equipment.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2009/02/19/cisco-tcp-small-servers-and-udp-small-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco Switching &#8211; switchport nonegotiate</title>
		<link>http://www.curtis-lamasters.com/2009/02/19/cisco-switching-switchport-nonegotiate/</link>
		<comments>http://www.curtis-lamasters.com/2009/02/19/cisco-switching-switchport-nonegotiate/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 07:07:47 +0000</pubDate>
		<dc:creator>clamasters</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[blog]]></category>

		<guid isPermaLink="false">http://www.curtis-lamasters.com/?p=218</guid>
		<description><![CDATA[Dynamic Trunking Protocol (DTP) is a standard feature of Cisco switches and allows two switches to dynamically configure interfaces interconnecting each other to be trunked ports.  DTP has 5 modes; Auto (default), On, Off, desirable and nonegotiate.  These 5 modes all have a purpose.  I have layed out the groundwork below: auto &#8211; The default [...]]]></description>
			<content:encoded><![CDATA[<p>Dynamic Trunking Protocol (DTP) is a standard feature of Cisco switches and allows two switches to dynamically configure interfaces interconnecting each other to be trunked ports.  DTP has 5 modes; Auto (default), On, Off, desirable and nonegotiate.  These 5 modes all have a purpose.  I have layed out the groundwork below:</p>
<ul>
<li><strong>auto</strong> &#8211; The default setting allows the port to willingly convert to trunking, however, the port will not trunk unless the neighbor is set to on or desirable.  When two switches are connected together and set for auto, they will NOT trunk.</li>
<li><strong>on</strong> &#8211; This setting forces the port to be a trunk regardless of the neighbor&#8217;s settings.</li>
<li><strong>off</strong> &#8211; This setting forces the port to not trunk, even if the neighbor is set to on.</li>
<li><strong>desirable</strong> &#8211; This causes the port to attempt to become a trunk, however, the neighbor would have to be set to on, desirable or auto.</li>
<li><strong>nonegotiate</strong> &#8211; This setting, forces the port to be a trunk but disables DTP frames between the two switches.  This is useful when you are working with non-Cisco equipment and just want to ensure that the ports won&#8217;t do anything you do not want them to&#8230;.this is my preference.</li>
</ul>
<p>To configure this on your switches, issue the following:</p>
<p style="padding-left: 30px;"><code><br />
configure terminal<br />
interface g1/0/49<br />
switchport trunk encapsulation dot1q<br />
switchport mode trunk<br />
switchport nonegotiate<br />
</code></p>
<p>Hopefully this was somewhat worthwhile.  It is very basic so I apologize but this is the easiest way to give you the needed information without boring you to death <img src='http://www.curtis-lamasters.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2009/02/19/cisco-switching-switchport-nonegotiate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco Command Reference</title>
		<link>http://www.curtis-lamasters.com/2009/02/19/cisco-command-reference/</link>
		<comments>http://www.curtis-lamasters.com/2009/02/19/cisco-command-reference/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 06:47:12 +0000</pubDate>
		<dc:creator>clamasters</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[blog]]></category>

		<guid isPermaLink="false">http://www.curtis-lamasters.com/?p=216</guid>
		<description><![CDATA[I was working on a client&#8217;s network tonight and thought of about 10k topics to blog about.Â  All the commands on Cisco routers and switches.Â  The purpose of this would be to help remind me that the basics are not good enought and also expand your mind on what a command does, how to use [...]]]></description>
			<content:encoded><![CDATA[<p>I was working on a client&#8217;s network tonight and thought of about 10k topics to blog about.Â  All the commands on Cisco routers and switches.Â  The purpose of this would be to help remind me that the basics are not good enought and also expand your mind on what a command does, how to use it and possibly when to implement it.Â  If at any point I&#8217;m completely off my rocker, you know what to do <img src='http://www.curtis-lamasters.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2009/02/19/cisco-command-reference/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco PIX 515E upgrade to 7.0 Code</title>
		<link>http://www.curtis-lamasters.com/2008/03/17/cisco-pix-515e-upgrade-to-70-code/</link>
		<comments>http://www.curtis-lamasters.com/2008/03/17/cisco-pix-515e-upgrade-to-70-code/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 04:10:08 +0000</pubDate>
		<dc:creator>clamasters</dc:creator>
				<category><![CDATA[Cisco]]></category>

		<guid isPermaLink="false">http://www.curtis-lamasters.com/index.php/2008/03/17/cisco-pix-515e-upgrade-to-70-code/</guid>
		<description><![CDATA[Today I used the monitor mode version of the installation procedure to upgrade a Cisco PIX 515E that was 2 months from being out of a SMARTNet contract. Just in time. This is done by rebooting the firewall with the reload command or flipping the switch (whichever you prefer), and pressing ESC during the boot [...]]]></description>
			<content:encoded><![CDATA[<p>Today I used the monitor mode version of the installation procedure to upgrade a Cisco PIX 515E that was 2 months from being out of a SMARTNet contract. Just in time.  This is done by rebooting the firewall with the reload command or flipping the switch (whichever you prefer), and pressing ESC during the boot cycle when the prompt tells you to, then getting started with the string of commands that are required.</p>
<p>First lets set the interface.</p>
<p><code>interface inside</code></p>
<p>Then lets set the IP address</p>
<p><code>address 10.0.0.1</code></p>
<p>Next lets tell it where the TFTP Server is.</p>
<p><code>server 10.0.0.10</code></p>
<p>Now lets tell it the file name.</p>
<p><code>file pix707.bin</code></p>
<p>Finally, lets tell the firewall to upload the file.</p>
<p><code>tftp</code></p>
<p>The firewall will start to download, then install the code and it&#8217;ll reboot.  When it comes up, the boot image is not saved to flash so we need to issue the following command.</p>
<p><code>copy tftp://10.0.0.10/pix707.bin flash:</code></p>
<p>Accept the following prompts and it&#8217;ll finally upload the image to flash.  Issue a &#8220;write memory&#8221; and you are done.  Now it&#8217;s time to upload the new ASDM image.  You can do that with TFTP as well using the following commands.</p>
<p><code>copy tftp://10.0.0.10/asdm-506.bin flash:</code></p>
<p>Accept the prompts and it&#8217;ll upload the file to flash.  Now we need to tell the configuration where that file is located with the following.</p>
<p><code>asdm location flash:/asdm-506.bin</code></p>
<p>Reboot and you should be able to access the firewall from the GUI interface using the 7.07 code and ASDM to match.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2008/03/17/cisco-pix-515e-upgrade-to-70-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Packet Capture with Cisco PIX / ASA</title>
		<link>http://www.curtis-lamasters.com/2008/03/11/packet-capture-with-cisco-pix-asa/</link>
		<comments>http://www.curtis-lamasters.com/2008/03/11/packet-capture-with-cisco-pix-asa/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 03:49:30 +0000</pubDate>
		<dc:creator>clamasters</dc:creator>
				<category><![CDATA[Cisco]]></category>

		<guid isPermaLink="false">http://www.curtis-lamasters.com/index.php/2008/03/11/packet-capture-with-cisco-pix-asa/</guid>
		<description><![CDATA[One of the guys I work with learned a cool trick and decided to pass it on to me. From a Cisco ASA / PIX firewall you can create a pcap file from the command line for use in Wireshark or just to debug from the console. First we need to create an access list. [...]]]></description>
			<content:encoded><![CDATA[<p>One of the guys I work with learned a cool trick and decided to pass it on to me.  From a Cisco ASA / PIX firewall you can create a pcap file from the command line for use in Wireshark or just to debug from the console.</p>
<p>First we need to create an access list.</p>
<p><code>access-list testpcap permit tcp any any</code></p>
<p>Next we start the capture.</p>
<p><code>capture testpcapname access-list testpcap interface outside</code></p>
<p>Now that the capture is started you can view your capture with</p>
<p><code>show capture testpcapname</code></p>
<p>or you can download the current pcap file from the SDM with</p>
<p><a href="http://www.curtis-lamasters.com/#">http://ipoffirewall/testpcapname/pcap</a></p>
<p>To stop the capture issue</p>
<p><code>no capture testpcapname</code></p>
<p>and don&#8217;t forget to delete your access list unless you want to use it later.  This example was very basic but you could get pretty granular with the access list rules to only pickup the data that you absolutely need to troubleshoot an issue or just for fun.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2008/03/11/packet-capture-with-cisco-pix-asa/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Cisco vs. Extreme Networks Switching Commands</title>
		<link>http://www.curtis-lamasters.com/2007/07/18/cisco-vs-extreme-networks-switching-commands/</link>
		<comments>http://www.curtis-lamasters.com/2007/07/18/cisco-vs-extreme-networks-switching-commands/#comments</comments>
		<pubDate>Wed, 18 Jul 2007 18:00:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Extreme Networks]]></category>

		<guid isPermaLink="false">http://wordpress.curtis-lamasters.com/?p=26</guid>
		<description><![CDATA[Don&#8217;t get your hopes up, I&#8217;m not taking sides here. I just wanted to show how the companies differ in basic switch configuration. Now for you who don&#8217;t know who Extreme is, they are the purple ones, better known as Extreme Networks. They offer some pretty nice products that compete very well with the likes [...]]]></description>
			<content:encoded><![CDATA[<p>Don&#8217;t get your hopes up, I&#8217;m not taking sides here. I just wanted to show how the companies differ in basic switch configuration. Now for you who don&#8217;t know who Extreme is, they are the purple ones, better known as Extreme Networks. They offer some pretty nice products that compete very well with the likes of Cisco or HP. Feel free to check out their product line at http://www.extremenetworks.com/.</p>
<p><span style="font-weight: bold; color: #330099">Configuring VLANs:</span></p>
<p><span style="font-weight: bold">Extreme &#8211; Create 2 VLANs and basic configuration</span></p>
<p>create vlan data<br />
configure vlan data tag 2<br />
configure vlan data ipaddress 10.0.2.1/24<br />
create vlan voice<br />
configure vlan voice tag 3<br />
configure vlan voice ipaddress 10.0.3.1/24<br />
enable ipforwarding</p>
<p><span style="font-weight: bold">Cisco &#8211; Create 2 VLAN interfaces and basic configuration</span></p>
<p>vlan dat<br />
vlan 2 name data<br />
vlan 3 name voice<br />
exit<br />
configure terminal<br />
interface vlan 2<br />
ip address 10.0.2.1 255.255.255.0<br />
no shutdown<br />
interface vlan 3<br />
ip address 10.0.3.1 255.255.255.0</p>
<p><span style="font-weight: bold; color: #330099">Port Configuration</span></p>
<p><span style="font-weight: bold">Extreme</p>
<p></span><span style="font-weight: bold">-switch to pc on (vlan 2)</span><br />
configure vlan data add port 4 untagged<br />
<span style="font-weight: bold">-switch to phone (vlan 3) and PC (vlan 2)</span><br />
configure vlan voice add port 4 tagged<br />
configure vlan data add port 4 untagged<br />
<span style="font-weight: bold">-switch to phone (vlan 3)</span><br />
configure vlan voice add port 4 tagged<br />
<span style="font-weight: bold">-switch to switch</span><br />
configure vlan default add port 1 tagged<br />
configure vlan data add port 1 tagged<br />
configure vlan voice add port 1 tagged</p>
<p><span style="font-weight: bold">Cisco </span>(skipping configure terminal)<br />
<span style="font-weight: bold"><br />
-switch to pc on (vlan 2)</span><br />
interface g0/4<br />
sw mode access<br />
sw acc vlan 2<br />
<span style="font-weight: bold"> -switch to phone (vlan 3) and PC (vlan 2)</span><br />
interface g0/4<br />
switchport mode trunk<br />
switchport trunk encapsulation dot1q<br />
switchport access vlan 2<br />
<span style="font-weight: bold"> -switch to phone (vlan 3)<br />
</span>interface g0/4<span style="font-weight: bold"><br />
</span>switchport mode trunk<br />
switchport trunk encapsulation dot1q<br />
<span style="font-weight: bold"> -switch to switch</span><br />
interface g0/4<br />
switchport mode trunk<br />
switchport trunk encapsulation dot1q</p>
<p><span style="font-weight: bold">Show Commands</p>
<p></span>Extreme &#8211; show port 4 information detail<br />
Cisco &#8211; show interface g0/4<br />
Extreme &#8211; show iproute<br />
Cisco &#8211; show ip route<br />
Extreme &#8211; show edp port all<br />
Cisco &#8211; show cdp neigh<br />
Extreme &#8211; show vlan<br />
Cisco &#8211; show vlan<br />
Extreme &#8211; show fdb<br />
Cisco &#8211; show mac-address-table<br />
Extreme &#8211; show config<br />
Cisco &#8211; show run</p>
<p><span style="font-weight: bold">Saving your work</span></p>
<p>Extreme &#8211; save<br />
Cisco &#8211; write memory<br />
Extreme &#8211; upload configuration vr vr-default 10.0.0.100<br />
Cisco &#8211; copy start tftp</p>
<p><span style="font-weight: bold">Starting over</span></p>
<p>Extreme &#8211; unconfigure switch all<br />
Cisco &#8211; write erase</p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2007/07/18/cisco-vs-extreme-networks-switching-commands/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Helpful Cisco Commands</title>
		<link>http://www.curtis-lamasters.com/2007/07/10/helpful-cisco-commands/</link>
		<comments>http://www.curtis-lamasters.com/2007/07/10/helpful-cisco-commands/#comments</comments>
		<pubDate>Tue, 10 Jul 2007 19:00:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Cisco]]></category>

		<guid isPermaLink="false">http://wordpress.curtis-lamasters.com/?p=14</guid>
		<description><![CDATA[Well, this is my first tech post so I&#8217;ll make it an easy one. I&#8217;ll put a few of the commands that I regularly utilize on Cisco routers and Switches to make my life easier. &#124; (Pipe) command output modifier - Alrighty, this truly is a basic command. You issue a normal command at the [...]]]></description>
			<content:encoded><![CDATA[<p>Well, this is my first tech post so I&#8217;ll make it an easy one. I&#8217;ll put a few of the commands that I regularly utilize on Cisco routers and Switches to make my life easier.</p>
<p><span style="font-weight: bold">|</span> (<span style="font-weight: bold">Pipe) command output modifier -</span></p>
<p>Alrighty, this truly is a basic command. You issue a normal command at the privilege exec level and add the | (pipe) afterwards followed by an i (include) e (exclude) or b (begin). Begin is not available in all IOS versions.</p>
<p>Command Example:</p>
<p><span style="font-weight: bold">show run | i ip route</span></p>
<p>would show something like this:</p>
<p><span style="font-weight: bold">ip route 10.0.0.0 255.255.255.0 11.24.1.1 name default</span><br />
<span style="font-weight: bold">ip route 10.1.255.0 255.255.255.0 11.24.1.2 name backup_net</span></p>
<p>If you were to replace the <span style="font-weight: bold">i</span> with a <span style="font-weight: bold">b</span> the output would begin at &#8220;ip route&#8221; and continue on with the rest of the config. This would be useful for those really long configs where you might be working on the dial-peers and don&#8217;t care to scroll through 500 lines of the config to get there. The <span style="font-weight: bold">e</span> option would exclude anything that you have following it. This might come into handy when you want to skip ip address or access-lists. Hope this helps, I was lucky enough to learn these tricks early on and didn&#8217;t have to struggle for too aweful long. Good luck.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.curtis-lamasters.com/2007/07/10/helpful-cisco-commands/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
