bonding mode 1 works as designed. Or not?
Hi, there!
I just set up bonding for a 2.6.12 box in active-backup mode (mode 1) and found out that every packet is duplicated, despite the fact that the documentation (Documentation/network/bonding.txt) says:
"active-backup or 1
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode."
My understanding of this mode is:
eth0 and eth1 are in a bonding group, mode=1, miimon=100 ... eth0 is the active slave and used as long as the physical link is available (checked by using MII monitoring), at the same time eth1 is totally passive, neither passing any received packets to the kernel nor sending packets, if the kernel wants it to do so. As soon as the eth0 link status changes to "down", eth1 is activated and used, and now eth0 remains silent and deaf until it becomes the active slave again.
Any comments on that? Is the documentation wrong OR is there a bug in the implementation of the bonding module?
Thank you in advance,
kind regards,
Heiko
Hi Heiko,
Quoted 25 lines · Heiko Gerstung
Hi, there!
I just set up bonding for a 2.6.12 box in active-backup mode (mode 1) and found out that every packet is duplicated, despite the fact that the documentation (
Documentation/network/bonding.txt) says:"active-backup or 1
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode."My understanding of this mode is:
eth0 and eth1 are in a bonding group, mode=1, miimon=100 ... eth0 is the active slave and used as long as the physical link is available (checked by using MII monitoring), at the same time eth1 is totally passive, neither passing any received packets to the kernel nor sending packets, if the kernel wants it to do so. As soon as the eth0 link status changes to "down", eth1 is activated and used, and now eth0 remains silent and deaf until it becomes the active slave again.
Quoted 2 lines
Any comments on that? Is the documentation wrong OR is there a bug in the implementation of the bonding module?
Neither, it's your understanding described above :-)
In fact, the bonding is used to select an OUTPUT device. If some trafic manages to enter through the backup interface, it will reach the kernel. It can be useful to implement some link health-checks for instance. However, the only packets that you should receive are multicast and broadcast packets, so this should be very limited anyway by design. After several years using it, it has not caused me any trouble, including in environments involving multicast for VRRP.
Quoted 4 lines
Thank you in advance,
kind regards,Heiko
Regards,
willy
Hi Willy,
Quoted 12 lines · Willy Tarreau
Quoted 11 lines
[...]eth0 and eth1 are in a bonding group, mode=1, miimon=100 ... eth0 is the active slave and used as long as the physical link is available (checked by using MII monitoring), at the same time eth1 is totally passive, neither passing any received packets to the kernel nor sending packets, if the kernel wants it to do so. As soon as the eth0 link status changes to "down", eth1 is activated and used, and now eth0 remains silent and deaf until it becomes the active slave again.
Any comments on that? Is the documentation wrong OR is there a bug in the implementation of the bonding module?
Quoted 10 lines
Neither, it's your understanding described above :-)
In fact, the bonding is used to select an OUTPUT device. If some trafic manages to enter through the backup interface, it will reach the kernel. It can be useful to implement some link health-checks for instance. However, the only packets that you should receive are multicast and broadcast packets, so this should be very limited anyway by design. After several years using it, it has not caused me any trouble, including in environments involving multicast for VRRP.
Unfortunately the ping replies come in on both interfaces, as well as any other traffic (like ssh or web traffic). Everything works but the load of the system caused by network traffic is nearly doubled this way and may cause confusion in a number of applications.
Would there be a way to stop the non-active slave(s) from "listening", i.e. drop all traffic received by them? If yes, where could I do that?
Quoted 4 lines
Regards,
willy
Thank you for your reply,
kind regards,
Heiko
Quoted 25 lines · On Tue, 14 Feb 2006 22:52:56 +0100 Heiko Gerstung <[email protected]> wrote:
Hi Willy,
Quoted 12 lines · Willy Tarreau
Quoted 11 lines
[...]eth0 and eth1 are in a bonding group, mode=1, miimon=100 ... eth0 is the active slave and used as long as the physical link is available (checked by using MII monitoring), at the same time eth1 is totally passive, neither passing any received packets to the kernel nor sending packets, if the kernel wants it to do so. As soon as the eth0 link status changes to "down", eth1 is activated and used, and now eth0 remains silent and deaf until it becomes the active slave again.
Any comments on that? Is the documentation wrong OR is there a bug in the implementation of the bonding module?
Quoted 10 lines
Neither, it's your understanding described above :-)
In fact, the bonding is used to select an OUTPUT device. If some trafic manages to enter through the backup interface, it will reach the kernel. It can be useful to implement some link health-checks for instance. However, the only packets that you should receive are multicast and broadcast packets, so this should be very limited anyway by design. After several years using it, it has not caused me any trouble, including in environments involving multicast for VRRP.
Quoted 11 lines
Unfortunately the ping replies come in on both interfaces, as well as any other traffic (like ssh or web traffic). Everything works but the load of the system caused by network traffic is nearly doubled this way and may cause confusion in a number of applications.
Would there be a way to stop the non-active slave(s) from "listening", i.e. drop all traffic received by them? If yes, where could I do that?
Quoted 4 lines
Regards,
willy
You will probably get a better answer if you ask the developers directly.
BONDING DRIVER
P: Chad Tindel M: [email protected] P: Jay Vosburgh M: [email protected] L: [email protected] W: http://sourceforge.net/projects/bonding
Quoted 29 lines · Heiko Gerstung
Hi Willy,
Quoted 13 lines · Willy Tarreau
Quoted 9 lines
[...]eth0 and eth1 are in a bonding group, mode=1, miimon=100 ... eth0 is the
active slave and used as long as the physical link is available (checked by using MII monitoring), at the same time eth1 is totally passive, neither passing any received packets to the kernel nor sending packets, if the kernel wants it to do so. As soon as the eth0 link status changes to "down", eth1 is activated and used, and now eth0 remains silent and deaf until it becomes the active slave again.Quoted 3 lines
Any comments on that? Is the documentation wrong OR is there a bug in the implementation of the bonding module?
Quoted 13 lines
Neither, it's your understanding described above :-)
In fact, the bonding is used to select an OUTPUT device. If some trafic manages to enter through the backup interface, it will reach the kernel. It can be useful to implement some link health-checks for instance. However,
the only packets that you should receive are multicast and broadcast packets,
so this should be very limited anyway by design. After several years using
it, it has not caused me any trouble, including in environments involving multicast for VRRP.
Quoted 4 lines
Unfortunately the ping replies come in on both interfaces, as well as any other traffic (like ssh or web traffic). Everything works but the load of the system caused by network traffic is nearly doubled this way and may cause confusion in a number of applications.
So you are using a hub instead of a switch, otherwise, your switch is duplicating the traffic. You agree that it's not expected to find an unicast packet on two different ports of the same switch when mirroring is disabled and mac-learning has not been disabled ?
Quoted 2 lines
Would there be a way to stop the non-active slave(s) from "listening", i.e. drop all traffic received by them? If yes, where could I do that?
I don't see how. It would be fairly simpler IMHO to fix the switch's configuration.
Quoted 7 lines
Quoted 4 lines
Regards,
willyThank you for your reply,
kind regards,
Heiko
Regards,
Willy