Re: How to correctly create multiple bonding interfaces in kernel 2.6.29.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Dan,

Unfortunately, Debian based methods would not do much for me.

I can try to experiment with lacp_rate .

So the way I got it working in kernel 2.6.26 was actually this, in /etc/modprobe.conf:

install bond0 /sbin/modprobe --ignore-install bonding -o bond0 mode=balance-alb miimon=100 updelay=0 downdelay=0 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 mode=802.3ad miimon=100 updelay=0 downdelay=0

Doing the same in 2.6.29, for bond1 (cross over between the 2 servers) a single ping would cause kernel panic.
Pings in bond0 (switch) would go on and off every 10 seconds or so...

So...
I will be trying to use similar options to these now in 2.6.29, maybe using sysfs ( /sys ) or... maybe rolling back to 2.6.26 and deal with other issues that I had with filesystems...

What else?


Thanks,


-----Original Message-----
From: Dan White
Cc: linux-net@xxxxxxxxxxxxxxx
Sent: Tue, Feb 2, 2010 6:25 pm
Subject: Re: How to correctly create multiple bonding interfaces in kernel 2.6.29.6


On 02/02/10 15:40 -0500, Hugo wrote: 
Folks, 
 
I am currently working with kernel 2.6.29.6-0.16.smp.gcc3.4.x86_64 . 
Per this conversation: 
 
[Bonding-devel] [PATCH] bonding: fix multiple module load problem 
http://lkml.indiana.edu/hypermail/linux/kernel/0906.1/01121.html ;
 
, I would like to know how to correctly create multiple bonding >
interfaces with different options / modes. 
 
Can anybody help me with that? 
 
I recently upgraded from kernel 2.6.26 which was working fine using something like in modprobe.conf: 
 
install bond0 /sbin/modprobe --ignore-install bonding -o bond0 >
mode=balance-alb miimon=100 
install bond1 /sbin/modprobe --ignore-install bonding -o bond1 >
mode=balance-rr miimon=100 
 
, unfortunately kernel 2.6.29 does not seem to like these and when I test the bonding interfaces using just a ping, I got a kernel panic. 
 
Also, I have trying several different ways to configure the bonding interface, but it is never stable.  Ping will work for 10 seconds, time out for another 0 or so and back
and > forth. 
 
Here are the bonding options I use (specified in /etc/modules on Debian): 
bonding miimon=100 mode=4 lacp_rate=1 
 
This has worked for me on the following kernels: 
2.6.18-6-686 
2.6.26-2-amd64 
 
I have not tried newer kernels. You can obtain a list of options for 
bonding for your newer kernel with 'modinfo bonding'. 
 
Those options work well with my Cisco 3750 switch. Without these options  set, I would only link up at 100meg (on gig interfaces) and/or I would drop 
every other packet. 
 
Hope that helps. 
 
An FYI for other Debian users, you can bond like this in 
/etc/network/interfaces: 
 
auto bond0 
iface bond0 inet static 
        address 192.168.1.2 
        netmask 255.255.255.0 
        gateway 192.168.1.1 
        slaves eth0 eth1 
 
(I have no eth0 or eth1 entries interfaces)  
-- Dan White 

--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Photo]     [Yosemite]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]     [Video 4 Linux]     [Linux Resources]

Add to Google