<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Diagrams on Aaron&#39;s Worthless Words</title>
    <link>https://c2797c86.aww-3cz.pages.dev/tags/diagrams/</link>
    <description>Recent content in Diagrams on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 24 Apr 2008 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://c2797c86.aww-3cz.pages.dev/tags/diagrams/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Diagrams -- Physical Is Not Enough!</title>
      <link>https://c2797c86.aww-3cz.pages.dev/posts/2008/04/diagrams-physical-is-not-enough/</link>
      <pubDate>Thu, 24 Apr 2008 00:00:00 +0000</pubDate>
      <guid>https://c2797c86.aww-3cz.pages.dev/posts/2008/04/diagrams-physical-is-not-enough/</guid>
      <description>&lt;p&gt;In my billion years in the industry, when I&amp;rsquo;ve asked for network diagrams, I&amp;rsquo;ve inevitably received a physical diagram &amp;ndash; a diagram that shows where stuff is plugged in. This is fine and dandy and has lots of information, but that&amp;rsquo;s not really enough these days. In the times of Arthur, when every piece of network gear did a single thing, you only needed to know where things were plugged in. In the modern era, devices do more &amp;ndash; a switch can route and house wireless, an ASA can terminate VPNs and be a switch &amp;ndash; so you need more than just where the cables run.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
