Documentation/networking/bonding.rst

156 configuring a bond, it is recommended "tail -f /var/log/messages" be
201 	use the MAC of the bond itself. It is preferred to have the
230 		- A slave is added to or removed from the bond
236 		- The bond's administrative state changes to up
457     and Distributing states, maintaining the bond in coupled control.
473 	bond's MAC address in accordance with the selected policy.
480 		bonding to set all slaves of an active-backup bond to
487 		MAC address of the bond should always be the MAC
490 		address of the bond changes during a failover.
515 		address of the bond to be selected normally (normally
516 		the MAC address of the first slave added to the bond).
519 		slave is programmed with the bond's MAC address at
534 	present in the bond.
589 	must be up (link-up state) before marking the bond device as up
615 		Active-backup policy: Only one slave in the bond is
617 		if, the active slave fails.  The bond's MAC address is
709 		address of one of the slaves in the bond such that
720 		in the bond.  A problematic outcome of using ARP
723 		of the bond.  Hence, peers learn the hardware address
724 		of the bond and the balancing of receive traffic
729 		redistributed when a new slave is added to the bond
732 		among the group of highest speed slaves in the bond.
735 		bond the receive traffic is redistributed among all
736 		active slaves in the bond by initiating ARP Replies
751 		team using the bond hardware address (the
753 		address for each slave in the bond.  If the
873 	The sysfs entry can be used to change the setting per bond device
875 	sysfs entry is allowed to be changed only if the bond device is
1019 		should one leg fail. The intended use case is for a bond
1291 also depend on the final bonding interface name chosen for your bond.
1296 Next, create a bond network script.  The file name for this
1298 the number of the bond.  For bond0 the file is named "ifcfg-bond0",
1321 will configure the bond with the specified options.  The options
1348 will restart the networking subsystem and your bond link should be now
1370 number of the bond.  This support requires sysfs support in the kernel,
1391 For example, if you wanted to make a simple bond of two e100
1407 ifup and ifdown scripts on the bond devices.  To reload the bonding
1515 To add a new bond foo::
1519 To remove an existing bond bar::
1535 Interfaces may be enslaved to a bond using the file
1536 /sys/class/net/<bond>/bonding/slaves.  The semantics for this file
1539 To enslave interface eth0 to bond bond0::
1544 To free slave eth0 from bond bond0::
1548 When an interface is enslaved to a bond, symlinks between the
1556 will free eth0 from whatever bond it is enslaved to, regardless of
1557 the name of the bond interface.
1559 Changing a Bond's Configuration
1561 Each bond may be configured individually by manipulating the
1562 files located in /sys/class/net/<bond name>/bonding
1582    The bond interface must be down before the mode can be changed.
1621 To make a simple bond of two e100 devices (presumed to be eth0
1634 To add a second bond, with two e1000 interfaces in
1656 support.  Once installed, this package will provide ``bond-*`` options
1670 		bond-slaves eth0 eth1
1671 		bond-mode active-backup
1672 		bond-miimon 100
1673 		bond-primary eth0 eth1
1682 		bond-slaves none
1683 		bond-mode active-backup
1684 		bond-miimon 100
1688 		bond-master bond0
1689 		bond-primary eth0 eth1
1693 		bond-master bond0
1694 		bond-primary eth0 eth1
1696 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1710 connects via a public network, it may be desirous to bias the bond to send said
1756 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1774 slave devices as well as bond devices and the bonding driver will simply act as
1922 policy to the bond.  Typical choices include XOR of either the MAC or
1932 It is possible to configure VLAN devices over a bond interface
1956 is attached to the bond, the bond device itself will pick up the
1960 are released from a bond that still has one or more VLAN interfaces on
1968 bond interface:
2163 before any network drivers participating in a bond.  This requirement
2187 any network drivers participating in a bond.  Below is an example of
2447 	through the switch to a balance-rr bond will not utilize greater
2454 	to the bond.
2511 	distributed across the devices in the bond.
2664 For example, on a bond in active-backup mode with five slaves
2683 the interfaces attached to the bond may occupy multiple ports on a
2685 ports, the bond device receives multiple copies of the same packet
2762 for devices in the bond, all connected to an common external switch.
2841 monitored, and should it recover, it will rejoin the bond (in whatever
2915 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will