<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cdp on Aaron&#39;s Worthless Words</title>
    <link>https://8bd9e53a.aww-3cz.pages.dev/tags/cdp/</link>
    <description>Recent content in Cdp on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Sep 2010 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://8bd9e53a.aww-3cz.pages.dev/tags/cdp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stubby Post - Cabling and EtherChannel</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2010/09/stubby-post-cabling-and-etherchannel/</link>
      <pubDate>Mon, 13 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2010/09/stubby-post-cabling-and-etherchannel/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve done it.  You&amp;rsquo;ve done it.  We&amp;rsquo;ve all done it.  You turn up another EtherChannel bundle and realize the hard way that your interface descriptions aren&amp;rsquo;t accurate.  Or you&amp;rsquo;ve swapped out a &lt;a href=&#34;http://aconaway.com/2010/08/30/catalyst-3750s-bad-luck-with-a-cisco-logo/&#34;&gt;piece-of-crap 3750&lt;/a&gt; and didn&amp;rsquo;t notice that the labels on the cables were wrong.  In either case, we all know that EtherChannel bundles don&amp;rsquo;t really work if the links aren&amp;rsquo;t plugged into the right switches.&lt;/p&gt;&#xA;&lt;p&gt;So, what do you to make sure that your links are cabled the way you think they are?  Personally, I don&amp;rsquo;t trust any label at all - no matter if I did it or not.  At some point, someone has changed something on a switch, and that just might have been a change to where the port is question is cabled.  If I was onsite, I would hand-trace the cabling from one end to the other then do it again to make sure I didn&amp;rsquo;t hose it up the first time.  The big problem with this technique is that I&amp;rsquo;m not everywhere at the same time, and the travel budget isn&amp;rsquo;t very big these days.  If I can&amp;rsquo;t get my hands on the cables, I relegate myself to using CDP to see what&amp;rsquo;s on the other end of links when putting ports into EtherChannel bundles.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using CDP To Track Down Physical Connections</title>
      <link>https://8bd9e53a.aww-3cz.pages.dev/posts/2008/10/using-cdp-to-track-down-physical-connections/</link>
      <pubDate>Fri, 31 Oct 2008 00:00:00 +0000</pubDate>
      <guid>https://8bd9e53a.aww-3cz.pages.dev/posts/2008/10/using-cdp-to-track-down-physical-connections/</guid>
      <description>&lt;p&gt;We have a location that&amp;rsquo;s a few blocks down from the main office here, and we were reviewing the circuit size to make sure it was sized properly.  Since not one person knows what&amp;rsquo;s going on and the trending graphs gave us conflicting details, one of our network dudes took me down to the site to do a physical survey to see what&amp;rsquo;s going on.  Well, besides the fact that no one was there, we discovered a hodgepodge of routers and switches that were cross-connected to one another on multiple floors of the building (I really wish I could post pics to emote the effect).  It&amp;rsquo;s kind of hard to figure out what&amp;rsquo;s going on when you can&amp;rsquo;t see both ends of the cable, so we had to abandon all hope.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
