1827807 Members
2795 Online
109969 Solutions
New Discussion

Linux bonding fails

 
Aaron Carr
New Member

Linux bonding fails

I'm attempting to configure bonding on an HP Proliant DL380G3 running Red Hat Enterprise Linux 2.1 update 4.

I configure bond0 as follows:

DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.1.57.111
NETWORK=10.1.57.0
USERCTL=no
NETMASK=255.255.252.0

I configure eth0:

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

I configure eth1:

DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

This is my modules.conf:

alias parport_lowlevel parport_pc
alias eth0 bcm5700
alias eth1 bcm5700
options bcm5700 line_speed=100,100 auto_speed=0,0 full_duplex=1,1
alias bond0 bonding
probeall bond0 eth0 eth1 bonding
options bond0 mode=1 miimon=100 primary=eth0
alias scsi_hostadapter cciss
alias scsi_hostadapter1 cciss_2445
alias scsi_hostadapter2 cciss_2445
alias usb-controller usb-ohci

Once this is done, I attempt to restart the network for bonding to take effect, but I get the following error:

bonding_init(): either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not work - see bonding.txt for details. Bonding driver not loaded.

Any help here would be greatly appreciated.
9 REPLIES 9
Vitaly Karasik_1
Honored Contributor

Re: Linux bonding fails

Aaron,

Try to start bonding without "mode=1 miimon=100 primary=eth0" parameters - I don't sure if bcm5700 support MII.

BTW, this may be relevant : http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112926

Rgds,
Vitaly
Aaron Carr
New Member

Re: Linux bonding fails

I tried removing miimon=100 primary=eth0 as you suggested, but still no luck.

Also, I don't think this relates to the bug you pointed out, because the bonding driver does not load at all.

I also get "Bringing up interface bond0: bonding device does not seem to be present, delaying bond0 initialization." and sometimes it says "bond0 not an ethernet like device".

If there's any more info I can supply, let me know and I'll dig it up.
Vitaly Karasik_1
Honored Contributor

Re: Linux bonding fails

you're right, this bug doesn't related to your problem.


If I understand properly, bonding module isn't loaded . did you try "insmod bonding" from commmand line?


ginnie nuckles_1
New Member

Re: Linux bonding fails

I have not seen a post to this that stats the resolution ??? I am tearing my hair out on this one .. did you find a solution please ?? thanks
Vitaly Karasik_1
Honored Contributor

Re: Linux bonding fails

Ginnie,
Do you have exactly the same problem?
ginnie nuckles_1
New Member

Re: Linux bonding fails

yes
Vitaly Karasik_1
Honored Contributor

Re: Linux bonding fails

can you check in "lsmod" output if bonding module is running? and if no, try "insmod bonding".
Aaron Carr
New Member

Re: Linux bonding fails

My solution was to ditch 2.1 AS and move to RHEL 3 (once the Proliant Support Pack was updated to v 7.1).

I tried the insmod bonding, as mentioned earlier, but that didn't help.
Matti_Kurkela
Honored Contributor

Re: Linux bonding fails

> I tried the insmod bonding, as mentioned earlier, but that didn't help.

For future reference:
It seems that the bonding module didn't load.
When you're having module problems, the error messages of insmod/modprobe commands may not be very informative. More information can usually be found in the kernel message buffer. You can check it with the "dmesg" command.
MK