Lines Matching refs:slaves
214 slaves of the active aggregator are down or the active
215 aggregator has no slaves.
235 ports (slaves). Reselection occurs as described under the
326 Validation is performed only for backup slaves.
330 Validation is performed for all slaves.
334 Filtering is applied to all slaves. No validation is
339 Filtering is applied to all slaves, validation is performed
344 Filtering is applied to all slaves, validation is performed
345 only for backup slaves.
354 that they were generated by an arp_ip_target. Since backup slaves
356 for backup slaves is on the broadcast ARP request sent out via the
358 configurations may result in situations wherein the backup slaves
360 of backup slaves must be disabled.
362 The validation of ARP requests on backup slaves is mainly helping
363 bonding to decide which slaves are more likely to work in case of
401 This option affects only active-backup mode for slaves with
427 Specifies whether active-backup mode should set all slaves to
437 bonding to set all slaves of an active-backup bond to
446 address of the slaves is not changed; instead, the MAC
474 However, the second and subsequent slaves are not set
490 This option may be modified via sysfs only when no slaves are
598 duplex settings. Utilizes all slaves in the active
653 address of one of the slaves in the bond such that
663 reply to this peer assigning it to one of the slaves
676 among the group of highest speed slaves in the bond.
680 active slaves in the bond by initiating ARP Replies
748 the primary slave and other slaves. Possible values are:
769 If no slaves are active, the first slave to recover is
788 slaves based on the load in that interval. This gives nice lb
886 slaves, although a single connection will not span
887 multiple slaves.
962 driver sends learning packets to each slaves peer switch.
1144 the slave devices. Without active slaves, the DHCP requests are not
1435 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1440 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1443 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1452 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1494 the bonding driver sends learning packets to each slaves peer switch. The
1512 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1513 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1525 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1526 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1547 active-backup mode, with eth0 and eth1 as slaves.
1551 bond-slaves eth0 eth1
1563 bond-slaves none
1748 contain information on which slaves are associated with which masters.
1751 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1826 information, and it propagates those actions to the slaves. In case
1840 Also, be aware that a similar problem can occur if all slaves
1848 with the correct hardware address if all slaves are removed from a
1885 ARP monitor will immediately fail any slaves using that driver, and
1886 those slaves will stay down. If networking monitoring (tcpdump, etc)
1948 device bond0 has two slaves, eth0 and eth1, and the routing table is
1971 The solution here is simply to insure that slaves do not have
1995 If neither eth0 and eth1 are slaves to bond0, then when the
2057 eth1 are slaves of bond0 and the driver for eth0 is loaded before the
2106 the promiscuous mode setting is propagated to all slaves.
2543 For example, on a bond in active-backup mode with five slaves
2698 slaves in active-backup mode.
2704 4. How many slaves can a bonding device have?
2765 slaves and remains persistent (even if the first slave is removed) until
2776 device and then changing its slaves (or their order):
2785 To restore your slaves' MAC addresses, you need to detach them
2787 then restore the MAC addresses that the slaves had before they were