<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Teaming on Aaron&#39;s Worthless Words</title>
    <link>https://a996c8ee.aww-3cz.pages.dev/tags/teaming/</link>
    <description>Recent content in Teaming on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 14 Apr 2009 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://a996c8ee.aww-3cz.pages.dev/tags/teaming/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
