Lines Matching refs:bond
151 configuring a bond, it is recommended "tail -f /var/log/messages" be
224 - A slave is added to or removed from the bond
230 - The bond's administrative state changes to up
430 bond's MAC address in accordance with the selected policy.
437 bonding to set all slaves of an active-backup bond to
444 MAC address of the bond should always be the MAC
447 address of the bond changes during a failover.
472 address of the bond to be selected normally (normally
473 the MAC address of the first slave added to the bond).
476 slave is programmed with the bond's MAC address at
491 present in the bond.
533 must be up (link-up state) before marking the bond device as up
559 Active-backup policy: Only one slave in the bond is
561 if, the active slave fails. The bond's MAC address is
653 address of one of the slaves in the bond such that
664 in the bond. A problematic outcome of using ARP
667 of the bond. Hence, peers learn the hardware address
668 of the bond and the balancing of receive traffic
673 redistributed when a new slave is added to the bond
676 among the group of highest speed slaves in the bond.
679 bond the receive traffic is redistributed among all
680 active slaves in the bond by initiating ARP Replies
695 team using the bond hardware address (the
697 address for each slave in the bond. If the
795 The sysfs entry can be used to change the setting per bond device
797 sysfs entry is allowed to be changed only if the bond device is
1196 also depend on the final bonding interface name chosen for your bond.
1201 Next, create a bond network script. The file name for this
1203 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1226 will configure the bond with the specified options. The options
1252 will restart the networking subsystem and your bond link should be now
1274 number of the bond. This support requires sysfs support in the kernel,
1295 For example, if you wanted to make a simple bond of two e100
1311 ifup and ifdown scripts on the bond devices. To reload the bonding
1419 To add a new bond foo:
1422 To remove an existing bond bar:
1434 Interfaces may be enslaved to a bond using the file
1435 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1438 To enslave interface eth0 to bond bond0:
1442 To free slave eth0 from bond bond0:
1445 When an interface is enslaved to a bond, symlinks between the
1453 will free eth0 from whatever bond it is enslaved to, regardless of
1454 the name of the bond interface.
1458 Each bond may be configured individually by manipulating the
1459 files located in /sys/class/net/<bond name>/bonding
1475 NOTE: The bond interface must be down before the mode can be
1502 To make a simple bond of two e100 devices (presumed to be eth0
1515 To add a second bond, with two e1000 interfaces in
1537 support. Once installed, this package will provide bond-* options to be used
1551 bond-slaves eth0 eth1
1552 bond-mode active-backup
1553 bond-miimon 100
1554 bond-primary eth0 eth1
1563 bond-slaves none
1564 bond-mode active-backup
1565 bond-miimon 100
1569 bond-master bond0
1570 bond-primary eth0 eth1
1574 bond-master bond0
1575 bond-primary eth0 eth1
1577 For a full list of bond-* supported options in /etc/network/interfaces and some
1591 connects via a public network, it may be desirous to bias the bond to send said
1637 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1655 slave devices as well as bond devices and the bonding driver will simply act as
1803 policy to the bond. Typical choices include XOR of either the MAC or
1813 It is possible to configure VLAN devices over a bond interface
1837 is attached to the bond, the bond device itself will pick up the
1841 are released from a bond that still has one or more VLAN interfaces on
1849 bond interface:
2053 before any network drivers participating in a bond. This requirement
2075 any network drivers participating in a bond. Below is an example of
2332 through the switch to a balance-rr bond will not utilize greater
2339 to the bond.
2392 distributed across the devices in the bond.
2543 For example, on a bond in active-backup mode with five slaves
2562 the interfaces attached to the bond may occupy multiple ports on a
2564 ports, the bond device receives multiple copies of the same packet
2641 for devices in the bond, all connected to an common external switch.
2715 monitored, and should it recover, it will rejoin the bond (in whatever
2786 from the bond (`ifenslave -d bond0 eth0'). The bonding driver will