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
461 	bond's MAC address in accordance with the selected policy.
468 		bonding to set all slaves of an active-backup bond to
475 		MAC address of the bond should always be the MAC
478 		address of the bond changes during a failover.
503 		address of the bond to be selected normally (normally
504 		the MAC address of the first slave added to the bond).
507 		slave is programmed with the bond's MAC address at
522 	present in the bond.
577 	must be up (link-up state) before marking the bond device as up
603 		Active-backup policy: Only one slave in the bond is
605 		if, the active slave fails.  The bond's MAC address is
697 		address of one of the slaves in the bond such that
708 		in the bond.  A problematic outcome of using ARP
711 		of the bond.  Hence, peers learn the hardware address
712 		of the bond and the balancing of receive traffic
717 		redistributed when a new slave is added to the bond
720 		among the group of highest speed slaves in the bond.
723 		bond the receive traffic is redistributed among all
724 		active slaves in the bond by initiating ARP Replies
739 		team using the bond hardware address (the
741 		address for each slave in the bond.  If the
861 	The sysfs entry can be used to change the setting per bond device
863 	sysfs entry is allowed to be changed only if the bond device is
1007 		should one leg fail. The intended use case is for a bond
1279 also depend on the final bonding interface name chosen for your bond.
1284 Next, create a bond network script.  The file name for this
1286 the number of the bond.  For bond0 the file is named "ifcfg-bond0",
1309 will configure the bond with the specified options.  The options
1336 will restart the networking subsystem and your bond link should be now
1358 number of the bond.  This support requires sysfs support in the kernel,
1379 For example, if you wanted to make a simple bond of two e100
1395 ifup and ifdown scripts on the bond devices.  To reload the bonding
1503 To add a new bond foo::
1507 To remove an existing bond bar::
1523 Interfaces may be enslaved to a bond using the file
1524 /sys/class/net/<bond>/bonding/slaves.  The semantics for this file
1527 To enslave interface eth0 to bond bond0::
1532 To free slave eth0 from bond bond0::
1536 When an interface is enslaved to a bond, symlinks between the
1544 will free eth0 from whatever bond it is enslaved to, regardless of
1545 the name of the bond interface.
1547 Changing a Bond's Configuration
1549 Each bond may be configured individually by manipulating the
1550 files located in /sys/class/net/<bond name>/bonding
1570    The bond interface must be down before the mode can be changed.
1609 To make a simple bond of two e100 devices (presumed to be eth0
1622 To add a second bond, with two e1000 interfaces in
1644 support.  Once installed, this package will provide ``bond-*`` options
1658 		bond-slaves eth0 eth1
1659 		bond-mode active-backup
1660 		bond-miimon 100
1661 		bond-primary eth0 eth1
1670 		bond-slaves none
1671 		bond-mode active-backup
1672 		bond-miimon 100
1676 		bond-master bond0
1677 		bond-primary eth0 eth1
1681 		bond-master bond0
1682 		bond-primary eth0 eth1
1684 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1698 connects via a public network, it may be desirous to bias the bond to send said
1744 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1762 slave devices as well as bond devices and the bonding driver will simply act as
1910 policy to the bond.  Typical choices include XOR of either the MAC or
1920 It is possible to configure VLAN devices over a bond interface
1944 is attached to the bond, the bond device itself will pick up the
1948 are released from a bond that still has one or more VLAN interfaces on
1956 bond interface:
2151 before any network drivers participating in a bond.  This requirement
2175 any network drivers participating in a bond.  Below is an example of
2435 	through the switch to a balance-rr bond will not utilize greater
2442 	to the bond.
2499 	distributed across the devices in the bond.
2652 For example, on a bond in active-backup mode with five slaves
2671 the interfaces attached to the bond may occupy multiple ports on a
2673 ports, the bond device receives multiple copies of the same packet
2750 for devices in the bond, all connected to an common external switch.
2829 monitored, and should it recover, it will rejoin the bond (in whatever
2903 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will