Lines Matching refs:bond
150 configuring a bond, it is recommended "tail -f /var/log/messages" be
202 - A slave is added to or removed from the bond
208 - The bond's administrative state changes to up
393 bond's MAC address in accordance with the selected policy.
400 bonding to set all slaves of an active-backup bond to
407 MAC address of the bond should always be the MAC
410 address of the bond changes during a failover.
435 address of the bond to be selected normally (normally
436 the MAC address of the first slave added to the bond).
439 slave is programmed with the bond's MAC address at
454 present in the bond.
496 must be up (link-up state) before marking the bond device as up
522 Active-backup policy: Only one slave in the bond is
524 if, the active slave fails. The bond's MAC address is
616 address of one of the slaves in the bond such that
627 in the bond. A problematic outcome of using ARP
630 of the bond. Hence, peers learn the hardware address
631 of the bond and the balancing of receive traffic
636 redistributed when a new slave is added to the bond
639 among the group of highest speed slaves in the bond.
642 bond the receive traffic is redistributed among all
643 active slaves in the bond by initiating ARP Replies
658 team using the bond hardware address (the
660 address for each slave in the bond. If the
758 The sysfs entry can be used to change the setting per bond device
760 sysfs entry is allowed to be changed only if the bond device is
1159 also depend on the final bonding interface name chosen for your bond.
1164 Next, create a bond network script. The file name for this
1166 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1189 will configure the bond with the specified options. The options
1215 will restart the networking subsystem and your bond link should be now
1237 number of the bond. This support requires sysfs support in the kernel,
1258 For example, if you wanted to make a simple bond of two e100
1274 ifup and ifdown scripts on the bond devices. To reload the bonding
1382 To add a new bond foo:
1385 To remove an existing bond bar:
1397 Interfaces may be enslaved to a bond using the file
1398 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1401 To enslave interface eth0 to bond bond0:
1405 To free slave eth0 from bond bond0:
1408 When an interface is enslaved to a bond, symlinks between the
1416 will free eth0 from whatever bond it is enslaved to, regardless of
1417 the name of the bond interface.
1421 Each bond may be configured individually by manipulating the
1422 files located in /sys/class/net/<bond name>/bonding
1438 NOTE: The bond interface must be down before the mode can be
1465 To make a simple bond of two e100 devices (presumed to be eth0
1478 To add a second bond, with two e1000 interfaces in
1500 support. Once installed, this package will provide bond-* options to be used
1514 bond-slaves eth0 eth1
1515 bond-mode active-backup
1516 bond-miimon 100
1517 bond-primary eth0 eth1
1526 bond-slaves none
1527 bond-mode active-backup
1528 bond-miimon 100
1532 bond-master bond0
1533 bond-primary eth0 eth1
1537 bond-master bond0
1538 bond-primary eth0 eth1
1540 For a full list of bond-* supported options in /etc/network/interfaces and some
1554 connects via a public network, it may be desirous to bias the bond to send said
1600 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1618 slave devices as well as bond devices and the bonding driver will simply act as
1719 policy to the bond. Typical choices include XOR of either the MAC or
1729 It is possible to configure VLAN devices over a bond interface
1753 is attached to the bond, the bond device itself will pick up the
1757 are released from a bond that still has one or more VLAN interfaces on
1765 bond interface:
1969 before any network drivers participating in a bond. This requirement
1991 any network drivers participating in a bond. Below is an example of
2248 through the switch to a balance-rr bond will not utilize greater
2255 to the bond.
2308 distributed across the devices in the bond.
2459 For example, on a bond in active-backup mode with five slaves
2478 the interfaces attached to the bond may occupy multiple ports on a
2480 ports, the bond device receives multiple copies of the same packet
2557 for devices in the bond, all connected to an common external switch.
2631 monitored, and should it recover, it will rejoin the bond (in whatever
2702 from the bond (`ifenslave -d bond0 eth0'). The bonding driver will