Lines Matching refs:bond
156 configuring a bond, it is recommended "tail -f /var/log/messages" be
229 - A slave is added to or removed from the bond
235 - The bond's administrative state changes to up
438 bond's MAC address in accordance with the selected policy.
445 bonding to set all slaves of an active-backup bond to
452 MAC address of the bond should always be the MAC
455 address of the bond changes during a failover.
480 address of the bond to be selected normally (normally
481 the MAC address of the first slave added to the bond).
484 slave is programmed with the bond's MAC address at
499 present in the bond.
553 must be up (link-up state) before marking the bond device as up
579 Active-backup policy: Only one slave in the bond is
581 if, the active slave fails. The bond's MAC address is
673 address of one of the slaves in the bond such that
684 in the bond. A problematic outcome of using ARP
687 of the bond. Hence, peers learn the hardware address
688 of the bond and the balancing of receive traffic
693 redistributed when a new slave is added to the bond
696 among the group of highest speed slaves in the bond.
699 bond the receive traffic is redistributed among all
700 active slaves in the bond by initiating ARP Replies
715 team using the bond hardware address (the
717 address for each slave in the bond. If the
825 The sysfs entry can be used to change the setting per bond device
827 sysfs entry is allowed to be changed only if the bond device is
970 should one leg fail. The intended use case is for a bond
1242 also depend on the final bonding interface name chosen for your bond.
1247 Next, create a bond network script. The file name for this
1249 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1272 will configure the bond with the specified options. The options
1299 will restart the networking subsystem and your bond link should be now
1321 number of the bond. This support requires sysfs support in the kernel,
1342 For example, if you wanted to make a simple bond of two e100
1358 ifup and ifdown scripts on the bond devices. To reload the bonding
1466 To add a new bond foo::
1470 To remove an existing bond bar::
1486 Interfaces may be enslaved to a bond using the file
1487 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1490 To enslave interface eth0 to bond bond0::
1495 To free slave eth0 from bond bond0::
1499 When an interface is enslaved to a bond, symlinks between the
1507 will free eth0 from whatever bond it is enslaved to, regardless of
1508 the name of the bond interface.
1512 Each bond may be configured individually by manipulating the
1513 files located in /sys/class/net/<bond name>/bonding
1533 The bond interface must be down before the mode can be changed.
1572 To make a simple bond of two e100 devices (presumed to be eth0
1585 To add a second bond, with two e1000 interfaces in
1607 support. Once installed, this package will provide ``bond-*`` options
1621 bond-slaves eth0 eth1
1622 bond-mode active-backup
1623 bond-miimon 100
1624 bond-primary eth0 eth1
1633 bond-slaves none
1634 bond-mode active-backup
1635 bond-miimon 100
1639 bond-master bond0
1640 bond-primary eth0 eth1
1644 bond-master bond0
1645 bond-primary eth0 eth1
1647 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1661 connects via a public network, it may be desirous to bias the bond to send said
1707 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1725 slave devices as well as bond devices and the bonding driver will simply act as
1873 policy to the bond. Typical choices include XOR of either the MAC or
1883 It is possible to configure VLAN devices over a bond interface
1907 is attached to the bond, the bond device itself will pick up the
1911 are released from a bond that still has one or more VLAN interfaces on
1919 bond interface:
2123 before any network drivers participating in a bond. This requirement
2147 any network drivers participating in a bond. Below is an example of
2407 through the switch to a balance-rr bond will not utilize greater
2414 to the bond.
2471 distributed across the devices in the bond.
2624 For example, on a bond in active-backup mode with five slaves
2643 the interfaces attached to the bond may occupy multiple ports on a
2645 ports, the bond device receives multiple copies of the same packet
2722 for devices in the bond, all connected to an common external switch.
2801 monitored, and should it recover, it will rejoin the bond (in whatever
2875 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will