From: Andy Gospodarek <gospo@redhat.com>
To: Simon Chen <simonchennj@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: stable bonding config
Date: Mon, 16 Jan 2012 10:57:55 -0500 [thread overview]
Message-ID: <20120116155755.GF32485@quad.redhat.com> (raw)
In-Reply-To: <CANj2Ebf4f3o+zKMLvqiVGyMegdJiqUzVupkOLuKqmxuaVSTdyg@mail.gmail.com>
On Thu, Jan 12, 2012 at 09:52:25PM -0500, Simon Chen wrote:
> I am using the following:
>
> Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
> ixgbe 3.7.17 driver (latest from intel)
>
> Thanks.
> -Simon
>
Use the module option to disable RSC and I think it will work.
> On Thu, Jan 12, 2012 at 9:31 PM, Simon Chen <simonchennj@gmail.com> wrote:
> > Hi all,
> >
> > Not sure if this is the right place to ask, but I got very good
> > answers about this topic in the past...
> >
> > I am mostly using Ubuntu 10.10. Each server has dual intel 10G NICs,
> > which I want to bond. I configured the switches to support 802.3ad.
> > Based on this post http://ubuntuforums.org/showthread.php?t=1595177, I
> > configure the server as:
> >
> > /home/simon# cat /etc/modprobe.d/aliases.conf
> > alias bond0 bonding
> > options bonding mode=4 miimon=100 lacp_rate=1 downdelay=200
> > updelay=200 ad_select=1 xmit_hash_policy=1
> >
> > /home/simon# cat /etc/network/interfaces
> > ...
> > auto bond0
> > iface bond0 inet manual
> > bond-slaves none
> > bond-mode 4
> > bond-miimon 100
> > up /sbin/ifenslave bond0 eth2 eth3
> > down /sbin/ifenslave bond0 eth2 eth3
> >
> > auto eth2
> > iface eth2 inet manual
> > bond-master bond0
> > bond-primary eth2 eth3
> >
> > auto eth3
> > iface eth3 inet manual
> > bond-master bond0
> > bond-primary eth2 eth3
> >
> > auto bond0.200
> > iface bond0.200 inet static
> > address ...
> > vlan_raw_device bond0
> > ==========================
> >
> > However, after a reboot the bonding doesn't work immediately. In particular:
> >
> > /home/simon# cat /proc/net/bonding/bond0
> > ...
> > 802.3ad info
> > LACP rate: fast
> > Aggregator selection policy (ad_select): bandwidth
> > Active Aggregator Info:
> > Aggregator ID: 3
> > Number of ports: 2
> > Actor Key: 33
> > Partner Key: 19
> > Partner Mac Address: 00:00:00:00:00:00 <------bonding not working
> > ======================================
> >
> > The only magic to get it work that I know of, is to perform "rmmod
> > ixgbe" "modprobe ixgbe" and then "ifconfig eth2 0.0.0.0 up" "ifconfig
> > eth3 0.0.0.0 up" "ifdown bond0" "ifup bond0".
> >
> > Is there a hassle-free bonding configuration that I can use? Or some
> > trick that I am not aware of?
> >
> > Thanks.
> > -Simon
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-16 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 2:31 stable bonding config Simon Chen
2012-01-13 2:52 ` Simon Chen
2012-01-16 15:57 ` Andy Gospodarek [this message]
2012-01-14 12:51 ` Nicolas de Pesloüan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120116155755.GF32485@quad.redhat.com \
--to=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simonchennj@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).