Lines Matching refs:bond
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
439 bond's MAC address in accordance with the selected policy.
446 bonding to set all slaves of an active-backup bond to
453 MAC address of the bond should always be the MAC
456 address of the bond changes during a failover.
481 address of the bond to be selected normally (normally
482 the MAC address of the first slave added to the bond).
485 slave is programmed with the bond's MAC address at
500 present in the bond.
554 must be up (link-up state) before marking the bond device as up
580 Active-backup policy: Only one slave in the bond is
582 if, the active slave fails. The bond's MAC address is
674 address of one of the slaves in the bond such that
685 in the bond. A problematic outcome of using ARP
688 of the bond. Hence, peers learn the hardware address
689 of the bond and the balancing of receive traffic
694 redistributed when a new slave is added to the bond
697 among the group of highest speed slaves in the bond.
700 bond the receive traffic is redistributed among all
701 active slaves in the bond by initiating ARP Replies
716 team using the bond hardware address (the
718 address for each slave in the bond. If the
826 The sysfs entry can be used to change the setting per bond device
828 sysfs entry is allowed to be changed only if the bond device is
971 should one leg fail. The intended use case is for a bond
1243 also depend on the final bonding interface name chosen for your bond.
1248 Next, create a bond network script. The file name for this
1250 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1273 will configure the bond with the specified options. The options
1300 will restart the networking subsystem and your bond link should be now
1322 number of the bond. This support requires sysfs support in the kernel,
1343 For example, if you wanted to make a simple bond of two e100
1359 ifup and ifdown scripts on the bond devices. To reload the bonding
1467 To add a new bond foo::
1471 To remove an existing bond bar::
1487 Interfaces may be enslaved to a bond using the file
1488 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1491 To enslave interface eth0 to bond bond0::
1496 To free slave eth0 from bond bond0::
1500 When an interface is enslaved to a bond, symlinks between the
1508 will free eth0 from whatever bond it is enslaved to, regardless of
1509 the name of the bond interface.
1513 Each bond may be configured individually by manipulating the
1514 files located in /sys/class/net/<bond name>/bonding
1534 The bond interface must be down before the mode can be changed.
1573 To make a simple bond of two e100 devices (presumed to be eth0
1586 To add a second bond, with two e1000 interfaces in
1608 support. Once installed, this package will provide ``bond-*`` options
1622 bond-slaves eth0 eth1
1623 bond-mode active-backup
1624 bond-miimon 100
1625 bond-primary eth0 eth1
1634 bond-slaves none
1635 bond-mode active-backup
1636 bond-miimon 100
1640 bond-master bond0
1641 bond-primary eth0 eth1
1645 bond-master bond0
1646 bond-primary eth0 eth1
1648 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1662 connects via a public network, it may be desirous to bias the bond to send said
1708 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1726 slave devices as well as bond devices and the bonding driver will simply act as
1874 policy to the bond. Typical choices include XOR of either the MAC or
1884 It is possible to configure VLAN devices over a bond interface
1908 is attached to the bond, the bond device itself will pick up the
1912 are released from a bond that still has one or more VLAN interfaces on
1920 bond interface:
2124 before any network drivers participating in a bond. This requirement
2148 any network drivers participating in a bond. Below is an example of
2408 through the switch to a balance-rr bond will not utilize greater
2415 to the bond.
2472 distributed across the devices in the bond.
2625 For example, on a bond in active-backup mode with five slaves
2644 the interfaces attached to the bond may occupy multiple ports on a
2646 ports, the bond device receives multiple copies of the same packet
2723 for devices in the bond, all connected to an common external switch.
2802 monitored, and should it recover, it will rejoin the bond (in whatever
2876 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will