Problems with bonding

Hello!

I am using a linux kernel v2.4.21 and tried to incorporate bonding on
two interfaces (eth1 and eth2) in active backup mode.

Everything works fine, but when I unplug the first involved ethernet
interface (eth1), a connection is lost. My logs and "cat
/proc/net/bond0/info" show that the bonding module correctly switched
over from eth1 to eth2, but the communication seems to stop until I plug
in the eth1 cable again.

Is there anyone who faced the same problem and found a solution?

Thank you in advance,
kind regards,

Heiko

Heiko Gerstung <(E-Mail Removed)> wrote in message news:<kfqov1-(E-Mail Removed)>...
> Hello!
>
> I am using a linux kernel v2.4.21 and tried to incorporate bonding on
> two interfaces (eth1 and eth2) in active backup mode.

Googled for any info specific to this kernel? I tried:
Linux Channel Bonding kernel 2.4.21
but turned up no widespread/generic problems

What about same with your distro?

> Everything works fine, but when I unplug the first involved ethernet
> interface (eth1), a connection is lost. My logs and "cat
> /proc/net/bond0/info" show that the bonding module correctly switched
> over from eth1 to eth2, but the communication seems to stop until I plug
> in the eth1 cable again.

Does mii-tool provide any clues? $ man mii-tool How about ethtool?

> Is there anyone who faced the same problem and found a solution?
>
> Thank you in advance,
> kind regards,
>
> Heiko

Checked your distro's bonding.txt file? Eg., this old RH8 box I'm at
now:
$ locate bonding.txt
/usr/src/linux-2.4.18-14/Documentation/networking/bonding.txt
$ cat /usr/src/linux-2.4.18-14/Documentation/networking/bonding.txt |
more

also check:
$ locate ifenslave
/usr/share/doc/iputils-20020124/README.ifenslave
$ cat /usr/share/doc/iputils-20020124/README.ifenslave | more

If not a setup or config error (which your info suggests is not the
case), and one would think the nic drivers would properly support mii
(though not _all_ do) I can only think of one other thing that _might_
get in the way ;-)

This is sheer speculation -- is your distro loading ifplugd as part of
the ifup script?

Well 2, I guess -- can your upstream connection deal with it without
getting confused?

Note that RH (as usual) is likely a bit different in seting up HA
bonding:
http://www.redhat.com/docs/manuals/e...NTERFACES-CHAN
See -- 8.2.3. Channel Bonding Interfaces and look at:
http://www.redhat.com/docs/manuals/e...-ethernet.html

Can't think of anything else to check offhand -- more details re: your
setup/config?

hth,
prg
email above disabled

Hi P !

Thank you very much for your answer. After a whole day of testing I
found out that its a driver issue. I had to implement a feature in the
nic driver we are using and I missed a little detail.

Sorry to steal your time,
now everything works fine!

Kind regards,
Heiko

P Gentry wrote:
> Heiko Gerstung <(E-Mail Removed)> wrote in message news:<kfqov1-(E-Mail Removed)>...
>
>>Hello!
>>
>>I am using a linux kernel v2.4.21 and tried to incorporate bonding on
>>two interfaces (eth1 and eth2) in active backup mode.
>
>
> Googled for any info specific to this kernel? I tried:
> Linux Channel Bonding kernel 2.4.21
> but turned up no widespread/generic problems
>
> What about same with your distro?
>
>
>>Everything works fine, but when I unplug the first involved ethernet
>>interface (eth1), a connection is lost. My logs and "cat
>>/proc/net/bond0/info" show that the bonding module correctly switched
>>over from eth1 to eth2, but the communication seems to stop until I plug
>>in the eth1 cable again.
>
>
> Does mii-tool provide any clues? $ man mii-tool How about ethtool?
>
>
>>Is there anyone who faced the same problem and found a solution?
>>
>>Thank you in advance,
>>kind regards,
>>
>>Heiko
>
>
> Checked your distro's bonding.txt file? Eg., this old RH8 box I'm at
> now:
> $ locate bonding.txt
> /usr/src/linux-2.4.18-14/Documentation/networking/bonding.txt
> $ cat /usr/src/linux-2.4.18-14/Documentation/networking/bonding.txt |
> more
>
> also check:
> $ locate ifenslave
> /usr/share/doc/iputils-20020124/README.ifenslave
> $ cat /usr/share/doc/iputils-20020124/README.ifenslave | more
>
> If not a setup or config error (which your info suggests is not the
> case), and one would think the nic drivers would properly support mii
> (though not _all_ do) I can only think of one other thing that _might_
> get in the way ;-)
>
> This is sheer speculation -- is your distro loading ifplugd as part of
> the ifup script?
>
> Well 2, I guess -- can your upstream connection deal with it without
> getting confused?
>
> Note that RH (as usual) is likely a bit different in seting up HA
> bonding:
> http://www.redhat.com/docs/manuals/e...NTERFACES-CHAN
> See -- 8.2.3. Channel Bonding Interfaces and look at:
> http://www.redhat.com/docs/manuals/e...-ethernet.html
>
> Can't think of anything else to check offhand -- more details re: your
> setup/config?
>
> hth,
> prg
> email above disabled