This mail has bouned twice now, not bothering to remove the extra crap this
time... Basically I get the following error when posting :
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
ilug at linux.ie
unrouteable mail domain "linux.ie"
Anyone know if adaptive load balancing supports vlans?
This will be for two gigabit cards =3D> so 2Gbit in alb mode.
Documentation here, but I am not sure I understand it all.
"active-backup or 1
=09=09Active-backup policy: Only one slave in the bond is
=09=09active. A different slave becomes active if, and only
=09=09if, the active slave fails. The bond's MAC address is
=09=09externally visible on only one port (network adapter)
=09=09to avoid confusing the switch.
=09=09In bonding version 2.6.2 or later, when a failover
=09=09occurs in active-backup mode, bonding will issue one
=09=09or more gratuitous ARPs on the newly active slave.
=09=09One gratuitous ARP is issued for the bonding master
=09=09interface and each VLAN interfaces configured above
=09=09it, provided that the interface has at least one IP
=09=09address configured. Gratuitous ARPs issued for VLAN
=09=09interfaces are tagged with the appropriate VLAN id.
=09=09This mode provides fault tolerance. The primary
=09=09option, documented below, affects the behavior of this
6. 802.1q VLAN Support
=09It is possible to configure VLAN devices over a bond interface
using the 8021q driver. However, only packets coming from the 8021q
driver and passing through bonding will be tagged by default. Self
generated packets, for example, bonding's learning packets or ARP
packets generated by either ALB mode or the ARP monitor mechanism, are
tagged internally by bonding itself. As a result, bonding must
"learn" the VLAN IDs configured above it, and use those IDs to tag
self generated packets.
=09For reasons of simplicity, and to support the use of adapters
that can do VLAN hardware acceleration offloading, the bonding
interface declares itself as fully hardware offloading capable, it gets
the add_vid/kill_vid notifications to gather the necessary
information, and it propagates those actions to the slaves. In case
of mixed adapter types, hardware accelerated tagged packets that
should go through an adapter that is not offloading capable are
"un-accelerated" by the bonding driver so the VLAN tag sits in the
=09VLAN interfaces *must* be added on top of a bonding interface
only after enslaving at least one slave. The bonding interface has a
hardware address of 00:00:00:00:00:00 until the first slave is added.
If the VLAN interface is created prior to the first enslavement, it
would pick up the all-zeroes hardware address. Once the first slave
is attached to the bond, the bond device itself will pick up the
slave's hardware address, which is then available for the VLAN device.
=09Also, be aware that a similar problem can occur if all slaves
are released from a bond that still has one or more VLAN interfaces on
top of it. When a new slave is added, the bonding interface will
obtain its hardware address from the first slave, which might not
match the hardware address of the VLAN interfaces (which was
ultimately copied from an earlier slave).
=09There are two methods to insure that the VLAN device operates
with the correct hardware address if all slaves are removed from a
=091. Remove all VLAN interfaces then recreate them
=092. Set the bonding interface's hardware address so that it
matches the hardware address of the VLAN interfaces.
=09Note that changing a VLAN interface's HW address would set the
underlying device -- i.e. the bonding interface -- to promiscuous
mode, which might not be what you want."
Hmm, not sure I fully understand this, anyone?
Conor - must do some lab work....
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!