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
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.
576 must be up (link-up state) before marking the bond device as up
602 Active-backup policy: Only one slave in the bond is
604 if, the active slave fails. The bond's MAC address is
696 address of one of the slaves in the bond such that
707 in the bond. A problematic outcome of using ARP
710 of the bond. Hence, peers learn the hardware address
711 of the bond and the balancing of receive traffic
716 redistributed when a new slave is added to the bond
719 among the group of highest speed slaves in the bond.
722 bond the receive traffic is redistributed among all
723 active slaves in the bond by initiating ARP Replies
738 team using the bond hardware address (the
740 address for each slave in the bond. If the
859 The sysfs entry can be used to change the setting per bond device
861 sysfs entry is allowed to be changed only if the bond device is
1004 should one leg fail. The intended use case is for a bond
1276 also depend on the final bonding interface name chosen for your bond.
1281 Next, create a bond network script. The file name for this
1283 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1306 will configure the bond with the specified options. The options
1333 will restart the networking subsystem and your bond link should be now
1355 number of the bond. This support requires sysfs support in the kernel,
1376 For example, if you wanted to make a simple bond of two e100
1392 ifup and ifdown scripts on the bond devices. To reload the bonding
1500 To add a new bond foo::
1504 To remove an existing bond bar::
1520 Interfaces may be enslaved to a bond using the file
1521 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1524 To enslave interface eth0 to bond bond0::
1529 To free slave eth0 from bond bond0::
1533 When an interface is enslaved to a bond, symlinks between the
1541 will free eth0 from whatever bond it is enslaved to, regardless of
1542 the name of the bond interface.
1546 Each bond may be configured individually by manipulating the
1547 files located in /sys/class/net/<bond name>/bonding
1567 The bond interface must be down before the mode can be changed.
1606 To make a simple bond of two e100 devices (presumed to be eth0
1619 To add a second bond, with two e1000 interfaces in
1641 support. Once installed, this package will provide ``bond-*`` options
1655 bond-slaves eth0 eth1
1656 bond-mode active-backup
1657 bond-miimon 100
1658 bond-primary eth0 eth1
1667 bond-slaves none
1668 bond-mode active-backup
1669 bond-miimon 100
1673 bond-master bond0
1674 bond-primary eth0 eth1
1678 bond-master bond0
1679 bond-primary eth0 eth1
1681 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1695 connects via a public network, it may be desirous to bias the bond to send said
1741 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1759 slave devices as well as bond devices and the bonding driver will simply act as
1907 policy to the bond. Typical choices include XOR of either the MAC or
1917 It is possible to configure VLAN devices over a bond interface
1941 is attached to the bond, the bond device itself will pick up the
1945 are released from a bond that still has one or more VLAN interfaces on
1953 bond interface:
2148 before any network drivers participating in a bond. This requirement
2172 any network drivers participating in a bond. Below is an example of
2432 through the switch to a balance-rr bond will not utilize greater
2439 to the bond.
2496 distributed across the devices in the bond.
2649 For example, on a bond in active-backup mode with five slaves
2668 the interfaces attached to the bond may occupy multiple ports on a
2670 ports, the bond device receives multiple copies of the same packet
2747 for devices in the bond, all connected to an common external switch.
2826 monitored, and should it recover, it will rejoin the bond (in whatever
2900 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will