Lines Matching full:slaves
219 slaves of the active aggregator are down or the active
220 aggregator has no slaves.
240 ports (slaves). Reselection occurs as described under the
334 Validation is performed only for backup slaves.
338 Validation is performed for all slaves.
342 Filtering is applied to all slaves. No validation is
347 Filtering is applied to all slaves, validation is performed
352 Filtering is applied to all slaves, validation is performed
353 only for backup slaves.
362 that they were generated by an arp_ip_target. Since backup slaves
364 for backup slaves is on the broadcast ARP request sent out via the
366 configurations may result in situations wherein the backup slaves
368 of backup slaves must be disabled.
370 The validation of ARP requests on backup slaves is mainly helping
371 bonding to decide which slaves are more likely to work in case of
409 This option affects only active-backup mode for slaves with
435 Specifies whether active-backup mode should set all slaves to
445 bonding to set all slaves of an active-backup bond to
454 address of the slaves is not changed; instead, the MAC
482 However, the second and subsequent slaves are not set
498 This option may be modified via sysfs only when no slaves are
606 duplex settings. Utilizes all slaves in the active
661 address of one of the slaves in the bond such that
671 reply to this peer assigning it to one of the slaves
684 among the group of highest speed slaves in the bond.
688 active slaves in the bond by initiating ARP Replies
766 the primary slave and other slaves. Possible values are:
787 If no slaves are active, the first slave to recover is
806 slaves based on the load in that interval. This gives nice lb
904 slaves, although a single connection will not span
905 multiple slaves.
980 driver sends learning packets to each slaves peer switch.
1165 the slave devices. Without active slaves, the DHCP requests are not
1459 Adding and Removing Slaves
1462 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1468 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1472 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1481 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1539 the bonding driver sends learning packets to each slaves peer switch. The
1557 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1558 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1570 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1571 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1592 active-backup mode, with eth0 and eth1 as slaves::
1596 bond-slaves eth0 eth1
1608 bond-slaves none
1793 contain information on which slaves are associated with which masters.
1796 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1871 information, and it propagates those actions to the slaves. In case
1885 Also, be aware that a similar problem can occur if all slaves
1893 with the correct hardware address if all slaves are removed from a
1930 ARP monitor will immediately fail any slaves using that driver, and
1931 those slaves will stay down. If networking monitoring (tcpdump, etc)
1993 device bond0 has two slaves, eth0 and eth1, and the routing table is
2016 The solution here is simply to insure that slaves do not have
2040 If neither eth0 and eth1 are slaves to bond0, then when the
2102 eth1 are slaves of bond0 and the driver for eth0 is loaded before the
2153 the promiscuous mode setting is propagated to all slaves.
2599 For example, on a bond in active-backup mode with five slaves
2756 slaves in active-backup mode.
2763 4. How many slaves can a bonding device have?
2829 slaves and remains persistent (even if the first slave is removed) until
2840 device and then changing its slaves (or their order)::
2849 To restore your slaves' MAC addresses, you need to detach them
2851 then restore the MAC addresses that the slaves had before they were