<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Router on Aaron&#39;s Worthless Words</title>
    <link>https://a996c8ee.aww-3cz.pages.dev/tags/router/</link>
    <description>Recent content in Router on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 02 Mar 2013 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://a996c8ee.aww-3cz.pages.dev/tags/router/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Junos - Logical Tunnel Interfaces with Virtual Routers</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2013/03/junos-logical-tunnel-interfaces-with-virtual-routers/</link>
      <pubDate>Sat, 02 Mar 2013 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2013/03/junos-logical-tunnel-interfaces-with-virtual-routers/</guid>
      <description>&lt;p&gt;There are a few ways to leak routes in and out of virtual routers in Junos. On the list is a cool feature called the logical tunnel interface.&lt;/p&gt;&#xA;&lt;p&gt;So, what am I talking about?  One way to separate traffic on a router is to use virtual routers (VRs) so that you wind up with multiple routing tables on the same router.  This separate traffic, but you will usually (read: always) have a demand to get traffic from one VR to another.  There are a few different way to do that (see rib-group, instance-import, next-table, et al.), but one really cool way to do it is through logical tunnel interfaces.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CME Exercise #1</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/cme-exercise-1/</link>
      <pubDate>Thu, 07 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/cme-exercise-1/</guid>
      <description>&lt;p&gt;I tried something like this earlier this year with STP.  It got rave reviews (from my mother), so I figured I try it again.  &lt;/p&gt;&#xA;&lt;p&gt;Below is a list of requirements for configuring a router as a call processor.  In a lab or in your head, configure the router to support the features as listed.  This isn&amp;rsquo;t a contest or anything like that.  If you get it right, a virtual thumbs up is all I can afford to give you.  There are some licensing issues for running this stuff in GNS3/dynamips, so I can&amp;rsquo;t help you out on that.  I&amp;rsquo;ll just hint that GNS3 and dynamips will bind to real networks and that copies of a compatible IP softphone are available.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IIUC Notes - Voice Ports and Dial Peers</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-voice-ports-and-dial-peers/</link>
      <pubDate>Mon, 04 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-voice-ports-and-dial-peers/</guid>
      <description>&lt;p&gt;More of my IIUC study notes.  As always, feel free to correct.  I really need to have a real post, don&amp;rsquo;t I?&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;show voice port summary&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Shows the voice ports available for use&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code data-lang=&#34;fallback&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1#show voice port summary&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;                                          IN       OUT&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;PORT           CH   SIG-TYPE   ADMIN OPER STATUS   STATUS   EC&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;============== == ============ ===== ==== ======== ======== ==&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/1         1      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/1         2      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/2         1      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/2         2      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/3         1      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/4         1      efxs     up    up   on-hook  idle     y&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;50/0/5         1      efxs     up    up   on-hook  idle     y&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;An ephone-dn shows up as efxs, so all these are ephone-dns.&lt;/li&gt;&#xA;&lt;li&gt;Channels are numbered 0-23; timeslots are numbered 1-24&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;FXS Ports&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>IIUC Notes - More Phone Features</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-more-phone-features/</link>
      <pubDate>Sat, 02 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-more-phone-features/</guid>
      <description>&lt;p&gt;Here are some more notes from my IIUC studies.  As always, corrections requested.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Paging&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Broadcasts messages to a group for a one-way communication&lt;/li&gt;&#xA;&lt;li&gt;Paging groups are used to limit which phones get the broadcast&lt;/li&gt;&#xA;&lt;li&gt;Paging can be unicast or multicast&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Unicast groups limited to 10 members&lt;/li&gt;&#xA;&lt;li&gt;Multicast requires mcast support on the network&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Paging configurations can be unicast, multicast, or multiple-group&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;!  Unicast Paging&lt;br&gt;&#xA;!  When 1044 is dialed, ephone 1 is paged&lt;br&gt;&#xA;R1(config)#ephone-dn 44&lt;br&gt;&#xA;R1(config-ephone-dn)#number 1044&lt;br&gt;&#xA;R1(config-ephone-dn)#paging&lt;br&gt;&#xA;R1(config-ephone-dn)#exit&lt;br&gt;&#xA;R1(config)#ephone 1&lt;br&gt;&#xA;R1(config-ephone)#paging-dn 44&lt;/p&gt;</description>
    </item>
    <item>
      <title>IIUC Notes - Phone Features</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-phone-features/</link>
      <pubDate>Fri, 01 Oct 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/10/iiuc-notes-phone-features/</guid>
      <description>&lt;p&gt;Here are some more notes from my IIUC studies.  As always, corrections requested.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Local Directory&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Allows users to look up names&lt;/li&gt;&#xA;&lt;li&gt;Allows names to show up when dialing or receiving a call&lt;/li&gt;&#xA;&lt;li&gt;Most phones have a directory button; some have a menu options for the directory&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;R1(config)#ephone-dn 1&lt;br&gt;&#xA;R1(config-ephone-dn)#name Roger Smith&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Directory entries can be added manually&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;R1(config-telephony)#directory entry 1 1700 Corporate Fax&lt;br&gt;&#xA;R1(config-telephony)#directory entry 2 1701 HR Fax&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;By default, sorting is done alphabetically by first name.&lt;/li&gt;&#xA;&lt;li&gt;Sorting can be changed&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;R1(config-telephony)#directory last-name-first&lt;/p&gt;</description>
    </item>
    <item>
      <title>IIUC Notes - Getting Phones on the LAN</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-getting-phones-on-the-lan/</link>
      <pubDate>Thu, 30 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-getting-phones-on-the-lan/</guid>
      <description>&lt;p&gt;More study notes.  Correct if wrong, though I hope I get some of it right since I already since I&amp;rsquo;m an R&amp;amp;S guy.  :$&lt;/p&gt;&#xA;&lt;p&gt;**Switchport Configuration&lt;br&gt;&#xA;**&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;switchport mode access&lt;/strong&gt;:  This config makes the port an access port that carries the primary and voice VLAN traffic&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;switchport mode trunk&lt;/strong&gt;:  This config akes the port a trunk unconditionally, but it will still send DTP messages&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;switchport nonegotiate&lt;/strong&gt;:  This config keeps the port from sending DTP messages.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;switchport mode dynamic auto&lt;/strong&gt;:  If the port receives DTP messages, it will become a trunk.  If not, it will be an access port.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;switchport mode dynamic desirable&lt;/strong&gt;:  The port actively sends DTP messages trying to become a trunk.  This is the default configuration on a Cisco switch.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Cisco IP Phone Boot Process&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stubby Post - What&#39;s an IDB?</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/stubby-post-whats-an-idb/</link>
      <pubDate>Fri, 03 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/stubby-post-whats-an-idb/</guid>
      <description>&lt;p&gt;I &lt;a href=&#34;http://twitter.com/aconaway/status/22554005934&#34;&gt;posed the philosophical question&lt;/a&gt; on Twitter the other day asking if single trunk links should be in an EtherChannel bundle just in case you need to expand later.  I didn&amp;rsquo;t really expect an answer, but the ever-verbose &lt;a href=&#34;http://twitter.com/WannabeCCIE&#34;&gt;@WannabeCCIE&lt;/a&gt; pointed out (in not so many words) that you should watch your IDBs.  What is that?&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s an &lt;a href=&#34;http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_tech_note09186a0080094322.shtml&#34;&gt;interface descriptor block&lt;/a&gt;.  I admit that I&amp;rsquo;m not intimately familiar with them, bu they&amp;rsquo;re data structs in IOS used to keep track of the interfaces on that device.  They come in two flavors - hardware and software.  HWIDBs usually represent a physical interface but they also represent tunnels, SVIs, PortChannels, subinterfaces, and any other virtual interface that you can configure.  The SWIDBs represent the layer-2 encapsulation of each HWIDB, so you&amp;rsquo;ll see entries talking about Ethernet, HDLC, PPP, etc.  That means that every interface you have on a router consumes two IDBs (there are always exceptions).  That&amp;rsquo;s important because each platform and IOS version combination has a limit to the number IDBs that device supports.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using SSH to Run Commands on a Router or Switch</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2009/04/using-ssh-to-run-commands-on-a-router-or-switch/</link>
      <pubDate>Thu, 30 Apr 2009 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2009/04/using-ssh-to-run-commands-on-a-router-or-switch/</guid>
      <description>&lt;p&gt;SSH is more than just a shell.  You can copy files from and to a server or piece of network gear with it.  You can use it to tunnel traffic.  Possibly my favorite, though, is to use SSH to run a command on a remote box without interacting with a shell.&lt;/p&gt;&#xA;&lt;p&gt;One of my biggest pet peeves with IOS (or pretty much any Cisco OS) is the lack of complex filtering.  Let&amp;rsquo;s say I want to look at all the downed ports and interfaces on modules 3 and 6 of my 6509.  I can&amp;rsquo;t easily do that with command from the IOS, but, on my Linux box, I can use multiple &lt;em&gt;grep&lt;/em&gt; commands to get exactly what I want really easily.  Let&amp;rsquo;s work through the example, shall we?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
