<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ethernet on Aaron&#39;s Worthless Words</title>
    <link>https://a996c8ee.aww-3cz.pages.dev/tags/ethernet/</link>
    <description>Recent content in Ethernet on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 10 Jan 2011 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://a996c8ee.aww-3cz.pages.dev/tags/ethernet/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Network Protocol Overhead</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2011/01/network-protocol-overhead/</link>
      <pubDate>Mon, 10 Jan 2011 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2011/01/network-protocol-overhead/</guid>
      <description>&lt;p&gt;Here are some packet overhead numbers for a few popular protocols to help with doing bandwidth requirement calculations.  This may be another add-as-we-go post, so please comment with additions or corrections.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Ethernet : 20 bytes&lt;br&gt;&#xA;Frame Relay : 4 - 6 bytes&lt;br&gt;&#xA;PPP : 6 bytes&lt;br&gt;&#xA;MLPPP: 10 bytes&lt;br&gt;&#xA;MPLS : 4 bytes&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;IP : 20 bytes&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;TCP : 20+ bytes&lt;br&gt;&#xA;UDP : 8 bytes&lt;br&gt;&#xA;GRE:  4 - 20+ bytes&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>IIUC Notes - Assigning Ephone-dns to Ephone Buttons</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-assigning-ephone-dns-to-ephone-buttons/</link>
      <pubDate>Thu, 23 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-assigning-ephone-dns-to-ephone-buttons/</guid>
      <description>&lt;p&gt;These are some of my notes on my IIUC studies.  Since I am a novice as voice stuff, please let me know what I get wrong.&lt;/p&gt;&#xA;&lt;p&gt;An &lt;strong&gt;ephone&lt;/strong&gt; is a representation of a phone.  It&amp;rsquo;s basically a structure of features that a phone will have. &lt;/p&gt;&#xA;&lt;p&gt;Configuration in CME:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;R1(config)#ephone 34  &amp;lt;&amp;ndash; This is just a tag and has nothing to do with an extension or phone&lt;br&gt;&#xA;R1(config-ephone)#mac-address 1111.2222.3333    &amp;lt;&amp;ndash; Assigns this ephone to the phone with that MAC address&lt;/p&gt;</description>
    </item>
    <item>
      <title>IIUC Notes - Powering Cisco Phones</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-powering-cisco-phones/</link>
      <pubDate>Tue, 21 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2010/09/iiuc-notes-powering-cisco-phones/</guid>
      <description>&lt;p&gt;Feel free to correct anything that is wrong or incomplete.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Power over Ethernet (PoE)&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Can provide power to a Cisco phone, access point, security camera, etc., through the network cabling, eliminating the need to plug the phone into the wall for power.&lt;/li&gt;&#xA;&lt;li&gt;Generic term for providing power on the Ethernet cable&lt;/li&gt;&#xA;&lt;li&gt;Provides centralized power that can be put on a UPS&lt;/li&gt;&#xA;&lt;li&gt;Allows devices to be located away from power outlets&lt;/li&gt;&#xA;&lt;li&gt;Removes cabling clutter at the user&amp;rsquo;s desk&lt;/li&gt;&#xA;&lt;li&gt;Can be provided through PoE-enabled switches, power panels or inline couplers (power injectors)&lt;/li&gt;&#xA;&lt;li&gt;Oversubscription is common&#xA;&lt;ul&gt;&#xA;&lt;li&gt;If every device on a switch asks for full power, the switch may not be able to handle the load.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Of course, devices can be powered with a power brick at the desk&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;802.3af&lt;/p&gt;</description>
    </item>
    <item>
      <title>Server NIC Aggregation to a Cisco Switch</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2009/04/server-nic-aggregation-to-a-cisco-switch/</link>
      <pubDate>Tue, 14 Apr 2009 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2009/04/server-nic-aggregation-to-a-cisco-switch/</guid>
      <description>&lt;p&gt;Have you even noticed that your new servers all have 2 NICs on the board?  At least all of them that I&amp;rsquo;ve seen in the last 3 years have.  A lot of server admin actually use them in a NIC teaming scenario where both NICs are used as one logical device &amp;ndash; much the same as Etherchannel on a switch.  This provides some fault tolerance and availability in case of failure, which is good idea in most cases.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Make Your Own Ethernet Cables</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2007/08/make-your-own-ethernet-cables/</link>
      <pubDate>Wed, 29 Aug 2007 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2007/08/make-your-own-ethernet-cables/</guid>
      <description>&lt;p&gt;If you need to buy an Ethernet cable, you&amp;rsquo;ll pay quite a premium for it at your local CompUSA or Circuit City. $22.99 for a 7&amp;rsquo; Ethernet cable is terrible. For just a few dollars more, you can &lt;a href=&#34;http://www.amazon.com/Feet-Category-Computer-Network-Cable/dp/B000UR1F3Y/ref=sr_1_15/104-2013292-9976757?ie=UTF8&amp;amp;s=electronics&amp;amp;qid=1187980741&amp;amp;sr=1-15&#34; title=&#34;Amazon -- Bulk Ethernet Cable&#34;&gt;buy a 250&amp;rsquo; roll of cable&lt;/a&gt; and make 35 of them yourself. You&amp;rsquo;ll need to invest in a &lt;a href=&#34;http://www.amazon.com/Belkin-RJ45-Medium-Duty-Crimp/dp/B00004Z62S&#34; title=&#34;Amazon -- Crimp Tool&#34;&gt;good crimper&lt;/a&gt; and &lt;a href=&#34;http://www.amazon.com/50-pack-Modular-Connectors-Cat5e-Stranded/dp/B000067SC4/ref=pd_bbs_sr_1/104-2013292-9976757?ie=UTF8&amp;amp;s=electronics&amp;amp;qid=1187980690&amp;amp;sr=8-1&#34; title=&#34;Amazon -- RJ45 Heads&#34;&gt;some RJ45 heads&lt;/a&gt; as well, but that cost is quite small compared to how much you can save by making your own.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
