<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Area on Aaron&#39;s Worthless Words</title>
    <link>https://8bd9e53a.aww-3cz.pages.dev/tags/area/</link>
    <description>Recent content in Area on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 10 Jul 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://8bd9e53a.aww-3cz.pages.dev/tags/area/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Summary Post - OSPF Network Statement Order and Matching</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2014/07/summary-post-ospf-network-statement-order-and-matching/</link>
      <pubDate>Thu, 10 Jul 2014 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2014/07/summary-post-ospf-network-statement-order-and-matching/</guid>
      <description>&lt;p&gt;When you configure OSPF network statements, IOS orders them most-specific to least-specific then does a top-to-bottom match of the interfaces. It doesn&amp;rsquo;t matter which order you put them in, the configuration will always be ordered with the longest prefix matches first.  Lab time!&lt;/p&gt;&#xA;&lt;p&gt;I have router R1 with these interfaces.&lt;/p&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#sh ip int brief&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;Interface                  IP-Address      OK? Method Status                Protocol&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;FastEthernet0/0            10.0.0.1        YES manual up                    up&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;FastEthernet0/1            unassigned      YES unset  administratively down down&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;Loopback100                10.0.101.1      YES manual up                    up&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;Loopback200                10.2.101.1      YES manual up                    up&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s add the OSPF configuration where 10.0.0.0/8 is in area 2 then check what OSPF thinks is happening.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Little OSPF Story</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2011/09/a-little-ospf-story/</link>
      <pubDate>Mon, 12 Sep 2011 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2011/09/a-little-ospf-story/</guid>
      <description>&lt;p&gt;Here&amp;rsquo;s a story from last week with little of no teaching value.&lt;/p&gt;&#xA;&lt;p&gt;I got a call from one of our business units looking for some routing help.  We don&amp;rsquo;t usually care about their production networks, but they were seeing some funky traceroutes, so I agreed to try and help them out.&lt;/p&gt;&#xA;&lt;p&gt;They sent over two fresh traceroutes from a host on a 7600.  In one of them, the trace went to the 7600 and then on down the line as expected.  In the other, the trace showed the 7600, another router&amp;rsquo;s far interface IP (that is, an interface not facing the 7600), then the 7600&amp;rsquo;s interface facing that router.  Every few minutes, the path was switch between the two.  The dude told me that they were an OSPF shop, so I asked him to send me the standard &lt;em&gt;show ip route&lt;/em&gt; and &lt;em&gt;show ip ospf database&lt;/em&gt; commands so I could see what&amp;rsquo;s going on.  The word &amp;ldquo;unexpected&amp;rdquo; comes to mind when trying to describe what I found.  So do other words that aren&amp;rsquo;t very appropriate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OSPFv3 - The Basics</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2011/02/ospfv3-the-basics/</link>
      <pubDate>Tue, 01 Feb 2011 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2011/02/ospfv3-the-basics/</guid>
      <description>&lt;p&gt;A few hours ago, the last of the IPv4 addresses were allocated by IANA.  Now&amp;rsquo;s the time to learn more about IPv6!  Yesterday, I posted about &lt;a href=&#34;http://aconaway.com/2011/01/30/eigrp-for-ipv6-the-basics/&#34;&gt;EIGRP for IPv6&lt;/a&gt;, so I think I&amp;rsquo;ll continue the trend by introducing OSPFv3, which is the IPv6 implementation of OSPF.  As always, I&amp;rsquo;m using Cisco routers here.  Just as yesterday, this is just a guide to the absolutely basics; if you want to do some funky OSPF magic, you won&amp;rsquo;t find it here - perhaps in time, though.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - OSPF Filtering and Summarization</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-filtering-and-summarization/</link>
      <pubDate>Sun, 20 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-filtering-and-summarization/</guid>
      <description>&lt;p&gt;Feel free to correct all this stuff.  Additions are also welcome.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Study Questions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How do I keep an area route from reaching a router in that area?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;You don’t.  That defeats the whole purpose of having the topology database on every router.  If you filtered one route from a router, there’s no way that SPF could calculate routes correctly.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Fine, then.  Where do I filter routes?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;You filter routes on an ABR or ASBR.  Since routers only have the whole topology for their area, it’s safe to filter routes from another area or from a redistributed routing protocol.  On a more technical note, you’re filtering type-3 LSAs on an ABR and type-5 LSAs on an ASBR.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
