<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Nic-Redundancy on BAFM</title><link>https://christian.blog.pakiheim.de/tags/nic-redundancy/</link><description>Recent content in Nic-Redundancy on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 10:18:13 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/nic-redundancy/index.xml" rel="self" type="application/rss+xml"/><item><title>Adapter teaming on SLES10</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_adapter-teaming-on-sles10/</link><pubDate>Sat, 16 Aug 2014 10:18:13 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/07/04/adapter-teaming-on-sles10/</guid><description>&lt;p&gt;Since one of the requirements for my current project is having NIC redundancy, I didn&amp;rsquo;t get around looking at the available &amp;quot; &lt;em&gt;adapter teaming&lt;/em&gt;&amp;quot; (or adapter bonding) solutions available for Linux/SLES.&lt;/p&gt;
&lt;p&gt;First I tried to dig into the Broadcom solution (since the Blade I first implemented the stuff uses a Broadcom NetXtreme II card) , but found out pretty soon that the basp configuration tool, which is &lt;em&gt;&lt;strong&gt;only&lt;/strong&gt;&lt;/em&gt; available on the Broadcom driver CD&amp;rsquo;s shipped with the Blade itself, pretty much doesn&amp;rsquo;t work.&lt;/p&gt;</description></item></channel></rss>