<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ccnp on Aaron&#39;s Worthless Words</title>
    <link>https://efb97021.aww-3cz.pages.dev/categories/ccnp/</link>
    <description>Recent content in Ccnp on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 06 Jul 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://efb97021.aww-3cz.pages.dev/categories/ccnp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Advertising a Default Route Into EIGRP</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2014/07/advertising-a-default-route-into-eigrp/</link>
      <pubDate>Sun, 06 Jul 2014 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2014/07/advertising-a-default-route-into-eigrp/</guid>
      <description>&lt;p&gt;Let&amp;rsquo;s get an IPv4 default route into EIGRP.  There are a few methods to do it.  I hate most of them, though.  I think it will be obvious which one I like.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the lab I have set up to test everything.  I want R4 to generate the default in each case.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/topology-300x176.svg&#34; alt=&#34;topology&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Default Network&lt;/strong&gt; - Candidate default.  I don&amp;rsquo;t think I&amp;rsquo;ve ever used that all my years in networking, but here&amp;rsquo;s how to use it in EIGRP for a default route.  You basically say &amp;ldquo;If you don&amp;rsquo;t know where to send a packet, send it to where network &lt;em&gt;X&lt;/em&gt; lives.&amp;rdquo;  We&amp;rsquo;re going to set the 192.168.1.0/24 as the default network, so, in our case X = 192.168.1.0. R4 will tag that route as a default candidate when it advertises it to the rest of the network.  The config is easy but requires a classful (yes, classful) network to be configured as the default.&lt;/p&gt;</description>
    </item>
    <item>
      <title>EIGRP and OSPF - Are We Connected?</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-and-ospf-are-we-connected/</link>
      <pubDate>Fri, 27 Jun 2014 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-and-ospf-are-we-connected/</guid>
      <description>&lt;p&gt;For both OSPF and EIGRP routers to become neighbors, their interface&amp;rsquo;s primary IP address must be on the same subnet. That statement is true. There is a difference in the definition of &amp;ldquo;same subnet&amp;rdquo;, though.&lt;/p&gt;&#xA;&lt;p&gt;In OSPF, both routers have to be configured to be on the same subnet with the same mask or else they won&amp;rsquo;t neighbor up.  When an hello packet is sent, the subnet mask is sent embedded in there.  The router does a quick look to be sure the subnets are defined the same way on both ends.  If everything doesn&amp;rsquo;t match, they don&amp;rsquo;t neighbor. Here&amp;rsquo;s a &lt;a href=&#34;http://www.wireshark.org/&#34;&gt;Wireshark&lt;/a&gt; screenshot to show you the OSPF hello.  &lt;em&gt;Note: See edit below.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>EIGRP Redistribution - Default Metrics of Connected and Static Routes</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-redistribution-default-metrics-of-connected-and-static-routes/</link>
      <pubDate>Thu, 19 Jun 2014 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-redistribution-default-metrics-of-connected-and-static-routes/</guid>
      <description>&lt;p&gt;I wanted to do some analysis of the EIGRP topology table last night, so I fired up a small lab. I was especially interested in how external routes appear there and compare to internal entries. Like all good scientific endeavors, the whole thing got derailed when I made a realization.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the lab I set up. You can ignore the IPv6 info for this exercise.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/eigrp1-300x198.svg&#34; alt=&#34;eigrp1&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s a simple little thing.  All the networks you see are included in EIGRP 100 for simplicity.  I limited the network statements to 192.0.2.0/24 to keep my options open. I went ahead and added Loopback100 on R3 with an address of 3.3.3.3/32 and added a &lt;em&gt;redistribute&lt;/em&gt; &lt;em&gt;connected&lt;/em&gt; with a route-map to get the route out in the wild.  Here&amp;rsquo;s what I had.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE - Epic Win!</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-epic-win/</link>
      <pubDate>Mon, 19 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-epic-win/</guid>
      <description>&lt;p&gt;Woohoo!  I passed the ROUTE test this morning.  That means I&amp;rsquo;m done with the CCNP track!  :)&lt;/p&gt;&#xA;&lt;p&gt;If you remember, &lt;a href=&#34;http://aconaway.com/2010/07/07/route-epic-fail-1/&#34;&gt;I took it over a week ago&lt;/a&gt; and had some bad luck on it.  Alright, bad luck is the wrong phrase.  I didn&amp;rsquo;t study enough and failed it.  This time, though, I had a special weapon on my side - &lt;a href=&#34;http://www.ciscopress.com/bookstore/product.asp?isbn=9781587058820&#34;&gt;the ROUTE Foundations book&lt;/a&gt;.  I haven&amp;rsquo;t used the Foundations books before, but, I saw some tweets about this one, so I picked it up off of Safari.  In just a couple pages, I realized that I was reading the answers to several questions directly out of the book.  It was amazing.  I only studied my weak points and wound up with 144 more points than I did last time.  I can&amp;rsquo;t say that was entirely because of the book, but I must say it was a big reason.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Further IGP Redistribution</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-further-igp-redistribution/</link>
      <pubDate>Sun, 18 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-further-igp-redistribution/</guid>
      <description>&lt;p&gt;As always, corrections are requested.&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;I&amp;rsquo;ve got IGRP and EIGRP both configured with the same AS number.  What&amp;rsquo;s special about this configuration?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;If both use the same AS number, then they automatically redistribute their routes into each other without using the &lt;em&gt;redistribute&lt;/em&gt; command.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When redistributing one IGP into another, where&amp;rsquo;s a good place to filter routes?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;There&amp;rsquo;s no one good place, but at the router(s) that&amp;rsquo;s doing the redistribution is a good start.  There&amp;rsquo;s no need to send an IGP a bunch of routes it doesn&amp;rsquo;t need.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Even More IGP Redistribution</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-even-more-igp-redistribution/</link>
      <pubDate>Sat, 17 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-even-more-igp-redistribution/</guid>
      <description>&lt;p&gt;I didn&amp;rsquo;t do so well on IGP redistribution the last time out, so here&amp;rsquo;s some more stuff to study.  As always, feel free to correct.&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;What three things are needed to be able to redistribute one routing protocol into another?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;1. One or more links into each routing protocol 2. A proper, working config for each protocol 3. The addition of the &lt;em&gt;redistribute&lt;/em&gt; command to one or more of the protocols&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE - Epic Fail (#1?)</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-epic-fail-1/</link>
      <pubDate>Thu, 08 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-epic-fail-1/</guid>
      <description>&lt;p&gt;I took the ROUTE test today and failed like I usually do.  That makes me 3-4 on these P-level tests if you&amp;rsquo;re scoring at home.  Don&amp;rsquo;t worry, though.  I&amp;rsquo;m not giving up.  :)&lt;/p&gt;&#xA;&lt;p&gt;In atypical fashion, I must say that the ROUTE test was a good test.  Let me say that again.  The ROUTE test was a good test.  I said good, though&amp;hellip;not great.  There were a few problems with it that I&amp;rsquo;ll get to, but, overall, this is the best test I&amp;rsquo;ve ever taken for a Cisco cert.  The questions were very well-written and there were no obvious omissions or wrong details.  I failed this test because I simply didn&amp;rsquo;t put in enough work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Controlling BGP</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-controlling-bgp/</link>
      <pubDate>Tue, 06 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-controlling-bgp/</guid>
      <description>&lt;p&gt;Corrections, please.  I skipped a bunch of BGP intro stuff to get to the juicy center.  I&amp;rsquo;ll see if I can come back later and finish the other parts for posterity.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Study Notes&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Is BGP route selection a controversial subject?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Yes.  If you ask 1000 network guys the best way to influence BGP, you&amp;rsquo;ll probably get 1000 different answers.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;At what position in the PA list of a BGP update do you find the weight attribute?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;You don&amp;rsquo;t.  Weight is a Cisco-proprietary thing.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Branch Office Routing</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-branch-office-routing/</link>
      <pubDate>Mon, 05 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-branch-office-routing/</guid>
      <description>&lt;p&gt;Corrigeme, por favor.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Study Notes&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What do IPSec tunnels give you when a branch office is on a broadband connection?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Privacy through encryption Authentication of the remote peer through ISAKMP Delivery of private data over the public Internet&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What do you need to configure to get your branch router talking to the Internet?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;ISP connection configuration such as PPPoE or PPPoA DHCP server configuration for internal users NAT Firewall services like inspection and filtering&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Implementing IPv6 in an IPv4 Network</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-implementing-ipv6-in-an-ipv4-network/</link>
      <pubDate>Sun, 04 Jul 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/07/route-notes-implementing-ipv6-in-an-ipv4-network/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Study Questions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Your boss says that ever host in the network needs to be converted over to IPv6 by the end of the day.  Which of multipoint tunnels, point-to-point tunnels, or native IPv6 would be the most appropriate to use to help with that conversion?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Native IPv6&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The engineering department wants to permanently use IPv6 on their test boxes in two offices.  Which of multipoint tunnels, point-to-point tunnels, or native IPv6 would be the most appropriate to use?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Point-to-point tunnels&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Routing IPv6</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-routing-ipv6/</link>
      <pubDate>Wed, 30 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-routing-ipv6/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Study Questions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Why would anyone develop a version of RIP that supports IPv6?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I have no idea.  Boredom, maybe.  Whatever the case, it works just like RIPv2, which is pretty scary.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;In EIGRP for IPv4, there are several requirements for two routers to neighbor up.  Which of those is not true for EIGRP for IPv6?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The two routers don&amp;rsquo;t need to be in the same subnet.  The concept of the link local address takes care of that need since neighbors always share a common medium like an Ethernet segment or a serial link.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Intro to IPv6</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-intro-to-ipv6/</link>
      <pubDate>Tue, 29 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-intro-to-ipv6/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Study Notes&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Exactly how big is an IPv6 address?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;It&amp;rsquo;s 128 bits long.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;This shouldn&amp;rsquo;t be on the test, but how many unique addresses is that?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;That&amp;rsquo;s 2^128 or a &amp;ldquo;3&amp;rdquo; with 38 zeros after it.  That&amp;rsquo;s also 2^95 addresses for each person on earth.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Surely we&amp;rsquo;re not writing in binary, are we?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;No way.  IPv6 uses 32 hex characters.  Each character is 4 bits, so we wind up with 128 bits of data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - PBR and IP SLA</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-pbr-and-ip-sla/</link>
      <pubDate>Thu, 24 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-pbr-and-ip-sla/</guid>
      <description>&lt;p&gt;Feel free to correct.&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;What&amp;rsquo;s the most primitive way to get traffic destined to a single host to use a different path than your dynamic IGP dictates?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Use a static route.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What&amp;rsquo;s the most primitive way to get traffic sourced from a single host to use a different path than your dynamic IGP dictates?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Use policy-based routing (PBR).&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What&amp;rsquo;s the most primitive way to get traffic sourced from a single host and destined for another host to use a different path than your dynamic IGP dictates?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Use PBR.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - More IGP Redistribution</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-more-igp-redistribution/</link>
      <pubDate>Wed, 23 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-more-igp-redistribution/</guid>
      <description>&lt;p&gt;As always, feel free to correct.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Study Notes&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When a router redistributes from one routing protocol to another, where does the router get the list of routes to redistribute?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;From the routing table.  Only IGP A&amp;rsquo;s routes (not topology or successors) are redistributed into IGP B&amp;rsquo;s domain.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What are two methods of filtering redistributed routes?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Use a &lt;em&gt;route-map&lt;/em&gt; in the &lt;em&gt;redistribute&lt;/em&gt; line or a &lt;em&gt;distribute-list&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Of the two methods for filtering, which one has more options?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The route-map method has more options.  You can match on all sorts of stuff, including an ACL or interface, and filter based on that.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - IGP Redistribution</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-igp-redistribution/</link>
      <pubDate>Tue, 22 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-igp-redistribution/</guid>
      <description>&lt;p&gt;As always, feel free to correct.&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;When you redistribute OSPF into EIGRP, what are you really redistributing?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Routes knows via OSPF Networks of OSPF-enabled interfaces&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What&amp;rsquo;s the default cost of an EIGRP route redistributed into OSPF?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;20&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What&amp;rsquo;s the default metric of an OSPF route redistributed into EIGRP?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;There is none since EIGRP has all those nifty k-values that have to be processed.  Routes actually won&amp;rsquo;t redistribute without them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - OSPF Virtual Links and Frame Relay Stuff</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-virtual-links-and-frame-relay-stuff/</link>
      <pubDate>Mon, 21 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-virtual-links-and-frame-relay-stuff/</guid>
      <description>&lt;p&gt;Feel free to correct.  I feel like I&amp;rsquo;m missing a big piece here, so please fill in a gap if you see one.  Thanks.  :)&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 many area 0s (zero) can you have in an OSPF implementation&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Just one.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;If my company merges with another company, and we&amp;rsquo;re both running OSPF, how can we get our networks routing together properly?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The easiest thing to do is to connect your two area 0s together through some physical link.  If you can, you can use virtual links to connect an ABR to another ABR to extend the zones together.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - OSPF Filtering and Summarization</title>
      <link>https://efb97021.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://efb97021.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>
    <item>
      <title>ROUTE Notes - OSPF Neighbor Relationships</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-neighbor-relationships/</link>
      <pubDate>Fri, 18 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-neighbor-relationships/</guid>
      <description>&lt;p&gt;Feel free to correct.&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;What are the definitions of the hello and dead intervals?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The hello intervals is how often a router sends hello messages.  The dead interval is how long to wait before considering a neighbor dead from lack of hello messages; this is 4x the hello interval by default.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How do you keep OSPF from trying to detect neighbors on an interface?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Don’t configure a &lt;em&gt;network&lt;/em&gt; statement for that interface Make that interface passive&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - Controlling Routes in EIGRP</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-controlling-routes-in-eigr/</link>
      <pubDate>Thu, 17 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-controlling-routes-in-eigr/</guid>
      <description>&lt;p&gt;Corrections 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;Why would you ever want to summarize routes?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Summarizing routes minimizes the routes advertised to the network.  For example, instead of advertising 192.168.0.0/24, 192.168.1.0/24…192.168.n.0/24, a router can advertise a single route to 192.168.0.0/16.  Keeping routing tables small saves hardware resources, minimizes convergence times, helps avoid route flapping, and makes the routing table easier to read for humans.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;When will an EIGRP router auto-summarize a route?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;If a router has interfaces that that are in different classes of network (Class A, B, C), then that router will auto-summarize those routes up to the classful boundary.  For example, if you have a 10.0.0.1/24 and a 192.168.100.1/30, the router will advertise 10.0.0.0/8 and 192.168.100.0/24.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - EIGRP Topology Stuff</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-eigrp-topology-stuff/</link>
      <pubDate>Thu, 17 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-eigrp-topology-stuff/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Study Questions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How do you keep EIGRP from killing your WAN?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;You can use the &lt;em&gt;ip bandwidth-percent eigrp AS X&lt;/em&gt; command to limit the amount of bandwidth that EIGRP uses to update neighbors.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How does EIGRP calculate how much bandwidth it can use for each frame relay PVC?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;By default, EIGRP takes 50% of the (sub)interface&amp;rsquo;s configured bandwidth (with the &lt;em&gt;bandwidth&lt;/em&gt; command) to use for updates on NBMA (non-broadcast mutliaccess) networks like frame relay.  This value is divided equally among all the PVC configured on that interface.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE - Redistribution Nuance #2 - OSPF External Metric Types</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-redistribution-nuance-2-ospf-external-metric-types/</link>
      <pubDate>Sun, 06 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-redistribution-nuance-2-ospf-external-metric-types/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://aconaway.com/2010/05/24/route-redistribution-nuance-1/&#34;&gt;Last time&lt;/a&gt;, we talked about a nifty little lab I set up for redistribution and how the OSPF ASBRs acted a little differently than I expected.  This time, let&amp;rsquo;s look at how changing external OSPF routes to a metric-type of 1 (E1) affects the routing tables.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the network again.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://aconaway.com/wp-content/uploads/2010/05/redist21.png&#34;&gt;&lt;img src=&#34;images/redist21-300x138.svg&#34; alt=&#34;&#34; title=&#34;Redistribution&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The static routes are being redistributed into their respective IGPs, and EIGRP is being redistributed into OSPF.  Let&amp;rsquo;s look at the routing table on R1.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stubby Post - VTP Clients Send Updates</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/05/stubby-post-vtp-clients-send-updates/</link>
      <pubDate>Tue, 18 May 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/05/stubby-post-vtp-clients-send-updates/</guid>
      <description>&lt;p&gt;VTP clients send VLAN updates.  Did you know that?&lt;/p&gt;&#xA;&lt;p&gt;I had a VTP server and client in the same VTP domain, and, when I cabled up the trunk, the client overwrote the VLAN database on the server.&lt;/p&gt;&#xA;&lt;p&gt;The moral of the story is that the best revision number will win no matter what the operating mode of the switch.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SWITCH - Epic Fail</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/05/switch-epic-fail/</link>
      <pubDate>Thu, 06 May 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/05/switch-epic-fail/</guid>
      <description>&lt;p&gt;I did my standard 2ish-hour drive to the closest testing center today to take the SWTCH test (642-813).  Utter failure.  That’s 3 for those scoring at home.&lt;/p&gt;&#xA;&lt;p&gt;The test was the absolute worst I’ve ever taken.  I know that I complain a lot, but this is totally justified in my eyes.  My 4th grade spelling tests were better than this.  I’ve seen kindergarten plays with better production value.&lt;/p&gt;&#xA;&lt;p&gt;First of all, it was poorly written.  Whoever wrote those questions has a few pieces of information about English sentence structure missing from their skill set.  A sentence needs a verb, right?  Well, a lot of the sentences were missing those.  It’s kind of important to know what the whole point of the sentence is, or is that too much to ask?  The “drag this over here” exercise questions all started with the same 13-word phrase that left the question so long that it was unreadable.  A couple of commas would have been nice in some.  Others I just had to infer from the answers what they were trying to ask.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stubby Post - UplinkFast</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/04/stubby-post-uplinkfast/</link>
      <pubDate>Wed, 28 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/04/stubby-post-uplinkfast/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve got a few switches daisy chained together with single links and have enabled UplinkFast on them.  This switch is not the root bridge; F0/24 is the root port and F0/23 is a blocked alternate port. I&amp;rsquo;ve got &lt;em&gt;debug spanning-tree uplinkfast&lt;/em&gt; on to help out.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;SW3#sh span | incl 0/2[34]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Fa0/23           Altn BLK 3019      128.23   P2p&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Fa0/24           Root FWD 3019      128.24   P2p&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Now let&amp;rsquo;s unplug F0/24 and see what happens.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stubby Post - Path Cost of EtherChannels</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/04/stubby-post-path-cost-of-etherchannels/</link>
      <pubDate>Tue, 27 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/04/stubby-post-path-cost-of-etherchannels/</guid>
      <description>&lt;p&gt;I was doing some STP labs tonight and found something that caught me off guard a bit.  I had been meddling with some EtherChannels between a pair of 3750s earlier today, and I forgot to reset the configs before starting on the STP stuff.  One my secondary root switch, I ran a &lt;em&gt;show spanning-tree vlan 1&lt;/em&gt; to see what status the ports were in, and I noticed the root path cost.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SWITCH – STP Exercise #1 Solution</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/04/switch-stp-exercise-1-solution/</link>
      <pubDate>Sat, 24 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/04/switch-stp-exercise-1-solution/</guid>
      <description>&lt;p&gt;Did you guys have any trouble with the solution to the STP exercise?  Let&amp;rsquo;s work through it and see what happens.  I got a few responses to the solution, and everyone seems to get the same answer, so I assume we&amp;rsquo;re all right.&lt;/p&gt;&#xA;&lt;p&gt;Before we get started, I wanted to mention the tie breakers since there can be ties in STP.  If there is a tie in any calculation, the same tie breakers are used, so I&amp;rsquo;ll list them here to use as we move through the calculations.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SWITCH - STP Exercise #1</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/04/switch-stp-exercise-1/</link>
      <pubDate>Thu, 22 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/04/switch-stp-exercise-1/</guid>
      <description>&lt;p&gt;Here&amp;rsquo;s an STP exercise for you.  Given the bridge priorities, MAC addresses, and interface types in the diagram, calculate the root bridge, root ports, designated ports, and blocked ports.  You can click on the image to enlarge it.  I&amp;rsquo;ll post a solution in the next few days.  As always, feel free to comment and ridicule my utter idiocy.  Be gentle, though; I don&amp;rsquo;t usually post exercises like this.&lt;/p&gt;&#xA;&lt;p&gt;Send any &lt;del&gt;configuration BPDUs&lt;/del&gt; questions my way.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ONT - Epic WIN!</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/04/ont-epic-win/</link>
      <pubDate>Thu, 08 Apr 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/04/ont-epic-win/</guid>
      <description>&lt;p&gt;Two down, two to go.  After much groaning and moaning, I&amp;rsquo;ve finally passed my ONT test.  The path to this point has been full of road blocks and covered in potholes, but I finally managed to power through it.  Thank $deity.&lt;/p&gt;&#xA;&lt;p&gt;If you remember, I&amp;rsquo;ve had quite a time with finding a testing center that&amp;rsquo;s convenient (or open for that matter), so I took the test at yet another center to see what they offer.  The facility was great; it was very quiet and clean, and the people were wonderfully friendly, which is a new concept to me.  Usually, the people don&amp;rsquo;t care about testers, but, being a center for inmates at state prisons (yes, prisoners), they do nothing but vocational and professional testing there.  That&amp;rsquo;s a lot better than the facilities who give their own students priority or who make money on training instead of testing.  The center is just over 2 hours away, but I think this place may be the best so far.  I&amp;rsquo;ll have to see what the future holds, though.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NBAR and HTTP Data Conversations</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/03/nbar-and-http-data-conversations/</link>
      <pubDate>Mon, 08 Mar 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/03/nbar-and-http-data-conversations/</guid>
      <description>&lt;p&gt;I’m still working on the ONT test and doing labs, so I marked up a lab for me to work.  I’m using the same setup as I did last time.  The two routers are 3640s running 12.4(25b).&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://aconaway.com/wp-content/uploads/2010/03/nbarclassmap1.png&#34;&gt;&lt;img src=&#34;images/nbarclassmap1_thumb.svg&#34; alt=&#34;nbar-classmap1&#34; title=&#34;nbar-classmap1&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Part of the lab was to identify HTTP traffic coming into F0/0 and mark it as CS3.  That’s pretty easy, right?  Of course, the lab I made up was a little more complicated, but the point comes clear with a simpler example.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stubby post: ROUTE Cert Kit Giveaway</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/03/stubby-post-route-cert-kit-giveaway/</link>
      <pubDate>Thu, 04 Mar 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/03/stubby-post-route-cert-kit-giveaway/</guid>
      <description>&lt;p&gt;Rofi at ITDualism is &lt;a href=&#34;http://itdualism.wordpress.com/2010/03/03/giveaway-route-cert-kit/&#34; title=&#34;ITDualism ROUTE Cert Kit Giveaway&#34;&gt;giving away a ROUTE cert kit&lt;/a&gt; to a random commenter.  Swing by there and put your name in the hat.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ONT - Epic Fail</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-epic-fail/</link>
      <pubDate>Tue, 16 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-epic-fail/</guid>
      <description>&lt;p&gt;I failed the ONT test today.  It was an utter lack of subject matter knowledge that did me in from the beginning.  When the first three questions mention things that I&amp;rsquo;ve never even heard, it&amp;rsquo;s going to be a long test.  I&amp;rsquo;ll take blame on it for sure, but the test was a lot darker than I imagined it would be.&lt;/p&gt;&#xA;&lt;p&gt;I heard from a couple people that the ONT test was the easiest of the 4 CCNP test.  I must say today&amp;rsquo;s test was a LOT harder than the ISCW test I took back in December.  Most of the questions were fair, but there were a few that were down-right evil or unanswerable.  Without giving too much away, there were some matching questions that had multiple items with multiple answers, rendering the answer to a guess.  I even ran into a CLI question about the WLC, which surely wasn&amp;rsquo;t mentioned anywhere I studied, and I don&amp;rsquo;t have a spare sitting around on which to test.  The icing, though, was the number of questions about FRTS; I know I need to understand it, but the magical question dice landed on that topic way too many times in my opinion.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ONT Notes - WLAN Management</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-wlan-management/</link>
      <pubDate>Sat, 13 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-wlan-management/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Elements of Cisco Unified Wireless Network&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Client devices - Cisco compatible extensions on WLAN clients&lt;/li&gt;&#xA;&lt;li&gt;Mobility platform - allows configuration of LWAPs through WLCs&lt;/li&gt;&#xA;&lt;li&gt;Network unification - integration into the rest of the network with WLCs doing RF management, IPS, etc.&lt;/li&gt;&#xA;&lt;li&gt;World-class network management - centralized management through WCS&lt;/li&gt;&#xA;&lt;li&gt;Unified advanced services - supports advanced technologies and threat detection&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;WLAN Implementation&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Autonomous and LWAP&lt;/p&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Category&lt;/th&gt;&#xA;          &lt;th&gt;Autonomous&lt;/th&gt;&#xA;          &lt;th&gt;LWAP&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Access Point&lt;/td&gt;&#xA;          &lt;td&gt;Autonomous APs&lt;/td&gt;&#xA;          &lt;td&gt;LWAPs&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Control&lt;/td&gt;&#xA;          &lt;td&gt;Individual configurations&lt;/td&gt;&#xA;          &lt;td&gt;Configuration through WLCs&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Dependency&lt;/td&gt;&#xA;          &lt;td&gt;Independent operations&lt;/td&gt;&#xA;          &lt;td&gt;Dependent on WLC&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Management&lt;/td&gt;&#xA;          &lt;td&gt;CiscoWorks WLSE and WDS&lt;/td&gt;&#xA;          &lt;td&gt;WCS&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Redundancy&lt;/td&gt;&#xA;          &lt;td&gt;Through APs&lt;/td&gt;&#xA;          &lt;td&gt;Through WLCs&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;&lt;strong&gt;Wireless LAN Services Engine (WLSE)&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ONT Notes - 802.1x and Encryption on LWAPs</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-802-1x-and-encryption-on-lwaps/</link>
      <pubDate>Fri, 12 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-802-1x-and-encryption-on-lwaps/</guid>
      <description>&lt;ul&gt;&#xA;&lt;li&gt;Traditional WLAN weaknesses&#xA;&lt;ul&gt;&#xA;&lt;li&gt;SSID for security&lt;/li&gt;&#xA;&lt;li&gt;Vulnerable to rogue APs&lt;/li&gt;&#xA;&lt;li&gt;MAC filtering for security&lt;/li&gt;&#xA;&lt;li&gt;WEP&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;WEP weaknesses&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Disribution of static keys is not scalable&lt;/li&gt;&#xA;&lt;li&gt;WEP keys can be cracked easily&lt;/li&gt;&#xA;&lt;li&gt;Vulnerable to dictionary attacks&lt;/li&gt;&#xA;&lt;li&gt;No protection against rogue APs&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Benefits of 802.1x&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Centralized authentication through Radius via AAA&lt;/li&gt;&#xA;&lt;li&gt;Mutual authentication between client and auth server&lt;/li&gt;&#xA;&lt;li&gt;Can use multiple encryption algorithms (AES, WPA, TKIP, WEP)&lt;/li&gt;&#xA;&lt;li&gt;Automatic dynamic WEP keys&lt;/li&gt;&#xA;&lt;li&gt;Roaming&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Requirements of 802.1x&#xA;&lt;ul&gt;&#xA;&lt;li&gt;EAP-capable client (supplicant)&lt;/li&gt;&#xA;&lt;li&gt;802.1x-capable AP (authenticator)&lt;/li&gt;&#xA;&lt;li&gt;EAP-capable auth server&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Table 1. Characteristics of the EAP variants&lt;/p&gt;</description>
    </item>
    <item>
      <title>ONT Notes - AutoQoS</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-autoqos/</link>
      <pubDate>Wed, 10 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-autoqos/</guid>
      <description>&lt;ul&gt;&#xA;&lt;li&gt;AutoQoS benefits&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Automates QoS for most deployments&lt;/li&gt;&#xA;&lt;li&gt;Protects business-critical apps to maximize availability&lt;/li&gt;&#xA;&lt;li&gt;Simplifies QoS deployments&lt;/li&gt;&#xA;&lt;li&gt;Reduces configuration errors&lt;/li&gt;&#xA;&lt;li&gt;Cheaper, faster, and simpler deployments&lt;/li&gt;&#xA;&lt;li&gt;Follows DiffServ&lt;/li&gt;&#xA;&lt;li&gt;Allows complete control over QoS configs&lt;/li&gt;&#xA;&lt;li&gt;Allows modification of auto-generated configs&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;AutoQoS phases of evolution&#xA;&lt;ul&gt;&#xA;&lt;li&gt;AutoQoS VOIP - Early version that configures the basics without discovery&lt;/li&gt;&#xA;&lt;li&gt;AutoQoS for Enterprise - Second version that only runs on routers and uses two-step process&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Autodiscovery using NBAR&lt;/li&gt;&#xA;&lt;li&gt;Generation of class maps&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;AutoQoS key elements&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Application classification&lt;/li&gt;&#xA;&lt;li&gt;Policy generation&lt;/li&gt;&#xA;&lt;li&gt;Configuration&lt;/li&gt;&#xA;&lt;li&gt;Monitoring and reporting&lt;/li&gt;&#xA;&lt;li&gt;Consistency&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Interfaces that you can configure AutoQoS on&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Serial ifs with PPP and HDLC&lt;/li&gt;&#xA;&lt;li&gt;FR point-to-point subifs (NOT multipoint)&lt;/li&gt;&#xA;&lt;li&gt;ATM point-to-point subifs&lt;/li&gt;&#xA;&lt;li&gt;FR-to-ATM links&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Prerequsites&#xA;&lt;ul&gt;&#xA;&lt;li&gt;No Qos policy already configured on if&lt;/li&gt;&#xA;&lt;li&gt;CEF enabled on if&lt;/li&gt;&#xA;&lt;li&gt;Correct bandwidth configured on if&lt;/li&gt;&#xA;&lt;li&gt;IP address on low-speed if&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Configuring AutoQoS Enterprise on a router (NOT a switch)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;auto qos discovery&lt;/strong&gt; - begins discovery process&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;auto qos&lt;/strong&gt; - generates and applies MQC-based policies&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Configuring AutoQoS VOIP&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;auto qos voip [ trust | cisco-phone ]&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Verifying AutoQoS on router&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;show auto discovery qos&lt;/strong&gt; - get autodiscovery results&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;show auto qos&lt;/strong&gt; - examine configuration generated&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Number of classes&lt;/li&gt;&#xA;&lt;li&gt;Classification options&lt;/li&gt;&#xA;&lt;li&gt;Marking options&lt;/li&gt;&#xA;&lt;li&gt;Queuing mechanisms&lt;/li&gt;&#xA;&lt;li&gt;Other QoS mechanisms&lt;/li&gt;&#xA;&lt;li&gt;If, subif, PVC where policy is applied&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;show policy-map interface&lt;/strong&gt; - look at if stats&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Verify AutoQoS VOIP&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;show auto qos&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;show policy-map interface&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;show mls qos maps&lt;/strong&gt; - shows CoS to DSCP mappings&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Possible issues with AutoQoS&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Too many traffic classes - manually consolidate some&lt;/li&gt;&#xA;&lt;li&gt;Configuration doesn&amp;rsquo;t change - rerun AutoQoS&lt;/li&gt;&#xA;&lt;li&gt;Configuration may not fit your situation - fine-tune it by hand&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Fine-tuning AutoQoS&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Use QPM&lt;/li&gt;&#xA;&lt;li&gt;CLI&lt;/li&gt;&#xA;&lt;li&gt;copy policy into editor, change, reapply&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;AutoQoS can match on characteristics besides ACLs and NBAR&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;match input interface&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;match cos&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;match ip precedence&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;match ip dscp&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;match ip rtp&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>ONT Notes - Pre-classify and End-to-end QoS</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-pre-classify-and-end-to-end-qos/</link>
      <pubDate>Thu, 04 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-pre-classify-and-end-to-end-qos/</guid>
      <description>&lt;ul&gt;&#xA;&lt;li&gt;VPNs (Didn&amp;rsquo;t ISCW cover this?)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Provide&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Confidentiality&lt;/li&gt;&#xA;&lt;li&gt;Integrity&lt;/li&gt;&#xA;&lt;li&gt;Authentication&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Types&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Remote-access&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Client-initiated&lt;/li&gt;&#xA;&lt;li&gt;NAS-initiated&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Site-to-site&#xA;&lt;ul&gt;&#xA;&lt;li&gt;LAN-to-LAN&lt;/li&gt;&#xA;&lt;li&gt;Extranet&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;L3 Tunneling protocols&#xA;&lt;ul&gt;&#xA;&lt;li&gt;GRE&lt;/li&gt;&#xA;&lt;li&gt;IPSec&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Pre-classify allows traffic to be classified before being sent across a tunnel or crypto-ed.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;em&gt;qos pre-classify&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;Provides a view into the original IP headers&lt;/li&gt;&#xA;&lt;li&gt;To classify on pre-tunnel header, apply the policy to the tunnel interface WITHOUT pre-classify.&lt;/li&gt;&#xA;&lt;li&gt;To classify on post-tunnel header, apply the policy to the physical interface WITHOUT pre-classify.&lt;/li&gt;&#xA;&lt;li&gt;To classify on pre-tunnel header, apply the policy to the physical interface WITH pre-classify.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;SLA - agreement with provider to guarantee QoS mechanisms across their network based on your markings.&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Assures availability, loss, throughput, delay, and jitter.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;End-to-end QoS&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To be effective, each hop in the path must have QoS configured similarly.&lt;/li&gt;&#xA;&lt;li&gt;Necessary in three locations&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Campus - within the customer network&lt;/li&gt;&#xA;&lt;li&gt;The edges - customer facing the provider, provider facing customer&lt;/li&gt;&#xA;&lt;li&gt;On the provider network&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;QoS tasks&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Campus access switches&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Speed/duplex settings&lt;/li&gt;&#xA;&lt;li&gt;Classification&lt;/li&gt;&#xA;&lt;li&gt;Trust&lt;/li&gt;&#xA;&lt;li&gt;Phone/access switch configs&lt;/li&gt;&#xA;&lt;li&gt;Multiple queues on switch ports, including priority for VOIP&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Campus distribution&#xA;&lt;ul&gt;&#xA;&lt;li&gt;L3 policing and marking&lt;/li&gt;&#xA;&lt;li&gt;Multiple queues on switch ports, including priority for VOIP&lt;/li&gt;&#xA;&lt;li&gt;WRED&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;WAN edge&#xA;&lt;ul&gt;&#xA;&lt;li&gt;SLA definitions&lt;/li&gt;&#xA;&lt;li&gt;LLQ&lt;/li&gt;&#xA;&lt;li&gt;LFI&lt;/li&gt;&#xA;&lt;li&gt;WRED&lt;/li&gt;&#xA;&lt;li&gt;Shaping&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Provider cloud&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Capacity planning&lt;/li&gt;&#xA;&lt;li&gt;PHB&lt;/li&gt;&#xA;&lt;li&gt;LLQ&lt;/li&gt;&#xA;&lt;li&gt;WRED&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Enterprise campus QoS implementation&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Implement multiple queues to avoid congestion&lt;/li&gt;&#xA;&lt;li&gt;Assign VOIP and video to highest priority queue&lt;/li&gt;&#xA;&lt;li&gt;Esablish trust boundaries&lt;/li&gt;&#xA;&lt;li&gt;Use policing to rate-limit excess traffic&lt;/li&gt;&#xA;&lt;li&gt;Use hardware QoS when possible&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Control Plane Policing (CoPP)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Applies QoS policy to traffic destined for the router&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Routing protocols&lt;/li&gt;&#xA;&lt;li&gt;Management protocols&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Can be used to avoid DOS attacks&lt;/li&gt;&#xA;&lt;li&gt;Applied to &lt;em&gt;control-plane&lt;/em&gt; in global config&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>ONT Notes - Congestion Avoidance, Policing, Shaping, and Link Efficiency</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-congestion-avoidance-policing-shaping-and-link-efficiency/</link>
      <pubDate>Wed, 03 Feb 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/02/ont-notes-congestion-avoidance-policing-shaping-and-link-efficiency/</guid>
      <description>&lt;ul&gt;&#xA;&lt;li&gt;Tail drop drawbacks&#xA;&lt;ul&gt;&#xA;&lt;li&gt;TCP synchronization - Dropping TCP packets from different flows can cause them all to window down and back up again at the same time in cycles.&lt;/li&gt;&#xA;&lt;li&gt;TCP starvation - Non-TCP or aggressive flows can starve everyone else out when TCP throttles back.&lt;/li&gt;&#xA;&lt;li&gt;No differentiated drop - Tail drop doesn&amp;rsquo;t care who you are, so you get dropped if the queue is full.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;RED - Random Early Detection&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Avoids tail drop by randomly dropping packets from the queue before it gets full&lt;/li&gt;&#xA;&lt;li&gt;Only dropped TCP flows slow down instead of everyone who has sent a packet since the queue filled&lt;/li&gt;&#xA;&lt;li&gt;Queues are smaller.&lt;/li&gt;&#xA;&lt;li&gt;Link utilization is more efficient&lt;/li&gt;&#xA;&lt;li&gt;Configured with&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Minimum threshold - start dropping when the queue is this size&lt;/li&gt;&#xA;&lt;li&gt;Maximum threshold - if the queue is this big, start tail dropping&lt;/li&gt;&#xA;&lt;li&gt;Mark probability denominator (MPD) - 1/MPD is the ratio of packets to drop when between the thresholds&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;WRED - Weighted RED&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Based on IP precedence or DSCP values&lt;/li&gt;&#xA;&lt;li&gt;Less-important packets are dropped more aggressively than important packets&lt;/li&gt;&#xA;&lt;li&gt;Applied to an interface, VC or a class within a policy map&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;CBWRED - Class based WRED&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Configured with CBWFQ&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Policing&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Limits subrate bandwidth (give you 100kbps on a T1)&lt;/li&gt;&#xA;&lt;li&gt;Limits traffic of certain applications&lt;/li&gt;&#xA;&lt;li&gt;Any traffic that exceeds police is dropped or re-classified; it&amp;rsquo;s a hard limit&lt;/li&gt;&#xA;&lt;li&gt;Inbound or outbound&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Shaping&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Sets a limit but buffers any in excess&lt;/li&gt;&#xA;&lt;li&gt;Requires memory to store the buffer&lt;/li&gt;&#xA;&lt;li&gt;Buffers = delay and/or jitter&lt;/li&gt;&#xA;&lt;li&gt;Outbound only&lt;/li&gt;&#xA;&lt;li&gt;Can respond to network signals like BECNs and FECNs&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Token and bucket&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The queue is a bucket; if a byte of data needs to be sent, it needs a token.&lt;/li&gt;&#xA;&lt;li&gt;If there are enough tokens, the traffic is considered conforming.&lt;/li&gt;&#xA;&lt;li&gt;If there aren&amp;rsquo;t enough tokens, the traffic is considered exceeding, which triggers the drop (policing), re-classify (policing), or buffer (shaping).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Frame relay traffic shaping (FRTS)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Only controls frame relay traffic&lt;/li&gt;&#xA;&lt;li&gt;Applied on subif or DLCI&lt;/li&gt;&#xA;&lt;li&gt;Support fragmentation and interleaving&lt;/li&gt;&#xA;&lt;li&gt;Reacts to FECNs and BECNs&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Compression&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Removed redundancy and patterns in data&lt;/li&gt;&#xA;&lt;li&gt;Less data = less latency&lt;/li&gt;&#xA;&lt;li&gt;Hardware compression or hardware-assisted compression does not involve the main CPU&lt;/li&gt;&#xA;&lt;li&gt;Software compression does&lt;/li&gt;&#xA;&lt;li&gt;Payload compression&lt;/li&gt;&#xA;&lt;li&gt;Header compression&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Link fragmentation and interleaving&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Small data might be waiting for larger data pieces to finish sending&lt;/li&gt;&#xA;&lt;li&gt;Chunks data into smaller fragments so they don&amp;rsquo;t have to wait&lt;/li&gt;&#xA;&lt;li&gt;Interleaving shuffles flows in the Tx queue&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
  </channel>
</rss>
