Everyone should feel free to offer any documentation patches they think are
appropriate. It won't hurt my feelings if you clear up anything I wrote
that isn't coming across to folks. I'm guessing others are so inclined.
Paul Lantinga <prl@...>
Sent by: To: "'bonding-devel@...'"
Subject: RE: [Bonding-devel] "Ah, Mr. Bond0, too bad there's only one of y
ou..." Mr. Vmlinuz-2 .4.18 hissed
03/12/2002 03:23 PM
> Try this:
> options bond1 -o bonding1 miimon=100 mode=0
> (or mode=1, or whatever you do)
> That should fix your problem. This is addressed in the
> bonding.txt right at
> the end of section 4. It's kind of hidden, and hard to
> understand. :)
btw, that little '-o' was all that I needed.
from the cisco side you can see the following:
Switch#sh etherchannel summary
Flags: d - default D - down
I - in use
2 Fa0/20(I) Fa0/21(Id)
5 Fa0/26(I) Fa0/25(Id) Fa0/28(I) Fa0/27(I)
Switch#sh port group
Group Interface Transmit Distribution
----- --------------------- ---------------------
2 FastEthernet0/20 destination address
2 FastEthernet0/21 destination address
5 FastEthernet0/26 source address
5 FastEthernet0/25 source address
5 FastEthernet0/28 source address
5 FastEthernet0/27 source address
As an added bonus, I believe that I now have every single parameter
memorized for bonding.o, modinfo, modprobe, insmod, lsmod, depmod, and
rmmod. modprobe -c being among the more helpful of them.
The linux virtual server I'm testing this with has pushed up to
286mbits/sec through the 4 bonded channels.
Great stuff this bonding!
#### smime.p7s has been removed from this note on March 12 2002 by Janice