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.
541 must be up (link-up state) before marking the bond device as up
567 Active-backup policy: Only one slave in the bond is
569 if, the active slave fails. The bond's MAC address is
661 address of one of the slaves in the bond such that
672 in the bond. A problematic outcome of using ARP
675 of the bond. Hence, peers learn the hardware address
676 of the bond and the balancing of receive traffic
681 redistributed when a new slave is added to the bond
684 among the group of highest speed slaves in the bond.
687 bond the receive traffic is redistributed among all
688 active slaves in the bond by initiating ARP Replies
703 team using the bond hardware address (the
705 address for each slave in the bond. If the
813 The sysfs entry can be used to change the setting per bond device
815 sysfs entry is allowed to be changed only if the bond device is
1217 also depend on the final bonding interface name chosen for your bond.
1222 Next, create a bond network script. The file name for this
1224 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1247 will configure the bond with the specified options. The options
1274 will restart the networking subsystem and your bond link should be now
1296 number of the bond. This support requires sysfs support in the kernel,
1317 For example, if you wanted to make a simple bond of two e100
1333 ifup and ifdown scripts on the bond devices. To reload the bonding
1441 To add a new bond foo::
1445 To remove an existing bond bar::
1461 Interfaces may be enslaved to a bond using the file
1462 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1465 To enslave interface eth0 to bond bond0::
1470 To free slave eth0 from bond bond0::
1474 When an interface is enslaved to a bond, symlinks between the
1482 will free eth0 from whatever bond it is enslaved to, regardless of
1483 the name of the bond interface.
1487 Each bond may be configured individually by manipulating the
1488 files located in /sys/class/net/<bond name>/bonding
1508 The bond interface must be down before the mode can be changed.
1547 To make a simple bond of two e100 devices (presumed to be eth0
1560 To add a second bond, with two e1000 interfaces in
1582 support. Once installed, this package will provide ``bond-*`` options
1596 bond-slaves eth0 eth1
1597 bond-mode active-backup
1598 bond-miimon 100
1599 bond-primary eth0 eth1
1608 bond-slaves none
1609 bond-mode active-backup
1610 bond-miimon 100
1614 bond-master bond0
1615 bond-primary eth0 eth1
1619 bond-master bond0
1620 bond-primary eth0 eth1
1622 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1636 connects via a public network, it may be desirous to bias the bond to send said
1682 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1700 slave devices as well as bond devices and the bonding driver will simply act as
1848 policy to the bond. Typical choices include XOR of either the MAC or
1858 It is possible to configure VLAN devices over a bond interface
1882 is attached to the bond, the bond device itself will pick up the
1886 are released from a bond that still has one or more VLAN interfaces on
1894 bond interface:
2098 before any network drivers participating in a bond. This requirement
2122 any network drivers participating in a bond. Below is an example of
2382 through the switch to a balance-rr bond will not utilize greater
2389 to the bond.
2446 distributed across the devices in the bond.
2599 For example, on a bond in active-backup mode with five slaves
2618 the interfaces attached to the bond may occupy multiple ports on a
2620 ports, the bond device receives multiple copies of the same packet
2697 for devices in the bond, all connected to an common external switch.
2776 monitored, and should it recover, it will rejoin the bond (in whatever
2850 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will