Lines Matching refs:slaves
220 slaves of the active aggregator are down or the active
221 aggregator has no slaves.
241 ports (slaves). Reselection occurs as described under the
335 Validation is performed only for backup slaves.
339 Validation is performed for all slaves.
343 Filtering is applied to all slaves. No validation is
348 Filtering is applied to all slaves, validation is performed
353 Filtering is applied to all slaves, validation is performed
354 only for backup slaves.
363 that they were generated by an arp_ip_target. Since backup slaves
365 for backup slaves is on the broadcast ARP request sent out via the
367 configurations may result in situations wherein the backup slaves
369 of backup slaves must be disabled.
371 The validation of ARP requests on backup slaves is mainly helping
372 bonding to decide which slaves are more likely to work in case of
410 This option affects only active-backup mode for slaves with
436 Specifies whether active-backup mode should set all slaves to
446 bonding to set all slaves of an active-backup bond to
455 address of the slaves is not changed; instead, the MAC
483 However, the second and subsequent slaves are not set
499 This option may be modified via sysfs only when no slaves are
619 duplex settings. Utilizes all slaves in the active
674 address of one of the slaves in the bond such that
684 reply to this peer assigning it to one of the slaves
697 among the group of highest speed slaves in the bond.
701 active slaves in the bond by initiating ARP Replies
779 the primary slave and other slaves. Possible values are:
800 If no slaves are active, the first slave to recover is
819 slaves based on the load in that interval. This gives nice lb
917 slaves, although a single connection will not span
918 multiple slaves.
1006 driver sends learning packets to each slaves peer switch.
1191 the slave devices. Without active slaves, the DHCP requests are not
1488 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1494 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1498 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1507 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1565 the bonding driver sends learning packets to each slaves peer switch. The
1583 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1584 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1596 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1597 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1618 active-backup mode, with eth0 and eth1 as slaves::
1622 bond-slaves eth0 eth1
1634 bond-slaves none
1819 contain information on which slaves are associated with which masters.
1822 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1897 information, and it propagates those actions to the slaves. In case
1911 Also, be aware that a similar problem can occur if all slaves
1919 with the correct hardware address if all slaves are removed from a
1956 ARP monitor will immediately fail any slaves using that driver, and
1957 those slaves will stay down. If networking monitoring (tcpdump, etc)
2019 device bond0 has two slaves, eth0 and eth1, and the routing table is
2042 The solution here is simply to insure that slaves do not have
2066 If neither eth0 and eth1 are slaves to bond0, then when the
2128 eth1 are slaves of bond0 and the driver for eth0 is loaded before the
2179 the promiscuous mode setting is propagated to all slaves.
2625 For example, on a bond in active-backup mode with five slaves
2782 slaves in active-backup mode.
2789 4. How many slaves can a bonding device have?
2855 slaves and remains persistent (even if the first slave is removed) until
2866 device and then changing its slaves (or their order)::
2875 To restore your slaves' MAC addresses, you need to detach them
2877 then restore the MAC addresses that the slaves had before they were