<?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>Adapter-Bonding on BAFM</title><link>https://christian.blog.pakiheim.de/tags/adapter-bonding/</link><description>Recent content in Adapter-Bonding on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Thu, 16 Oct 2008 16:47:23 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/adapter-bonding/index.xml" rel="self" type="application/rss+xml"/><item><title>Adapter bonding on Linux</title><link>https://christian.blog.pakiheim.de/posts/2008-10-16_adapter-bonding-on-linux/</link><pubDate>Thu, 16 Oct 2008 16:47:23 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1185</guid><description>&lt;p&gt;Well, today I had a rather weird error. I was testing the adapter bonding on one of the boxen designated as Tivoli Storage Manager Server, when I noticed that the bonding wasn&amp;rsquo;t working as expected when simulating an error (that is unplugging one of the TP cables for the bond).&lt;/p&gt;
&lt;p&gt;Now, the bond had &amp;ldquo;mode=6 miimon=100&amp;rdquo; as options. After running &amp;ldquo;linux bond debug&amp;rdquo; through Google (which turned up nothing useful, besides one document on the Oracle Wiki about IOS/Linux adapter teaming), I figured &amp;ldquo;Hey, just lets test switching the arguments.&amp;rdquo; And guess what ?&lt;/p&gt;</description></item></channel></rss>