Lines Matching full: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
346 Validation is performed only for backup slaves.
350 Validation is performed for all slaves.
354 Filtering is applied to all slaves. No validation is
359 Filtering is applied to all slaves, validation is performed
364 Filtering is applied to all slaves, validation is performed
365 only for backup slaves.
374 that they were generated by an arp_ip_target. Since backup slaves
376 for backup slaves is on the broadcast ARP request sent out via the
378 configurations may result in situations wherein the backup slaves
380 of backup slaves must be disabled.
382 The validation of ARP requests on backup slaves is mainly helping
383 bonding to decide which slaves are more likely to work in case of
421 This option affects only active-backup mode for slaves with
458 Specifies whether active-backup mode should set all slaves to
468 bonding to set all slaves of an active-backup bond to
477 address of the slaves is not changed; instead, the MAC
505 However, the second and subsequent slaves are not set
521 This option may be modified via sysfs only when no slaves are
641 duplex settings. Utilizes all slaves in the active
696 address of one of the slaves in the bond such that
706 reply to this peer assigning it to one of the slaves
719 among the group of highest speed slaves in the bond.
723 active slaves in the bond by initiating ARP Replies
812 the primary slave and other slaves. Possible values are:
833 If no slaves are active, the first slave to recover is
852 slaves based on the load in that interval. This gives nice lb
950 slaves, although a single connection will not span
951 multiple slaves.
1039 driver sends learning packets to each slaves peer switch.
1224 the slave devices. Without active slaves, the DHCP requests are not
1518 Adding and Removing Slaves
1521 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1527 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1531 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1540 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1598 the bonding driver sends learning packets to each slaves peer switch. The
1616 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1617 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1629 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1630 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1651 active-backup mode, with eth0 and eth1 as slaves::
1655 bond-slaves eth0 eth1
1667 bond-slaves none
1852 contain information on which slaves are associated with which masters.
1855 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1930 information, and it propagates those actions to the slaves. In case
1944 Also, be aware that a similar problem can occur if all slaves
1952 with the correct hardware address if all slaves are removed from a
2043 device bond0 has two slaves, eth0 and eth1, and the routing table is
2066 The solution here is simply to insure that slaves do not have
2090 If neither eth0 and eth1 are slaves to bond0, then when the
2152 eth1 are slaves of bond0 and the driver for eth0 is loaded before the
2203 the promiscuous mode setting is propagated to all slaves.
2649 For example, on a bond in active-backup mode with five slaves
2806 slaves in active-backup mode.
2813 4. How many slaves can a bonding device have?
2879 slaves and remains persistent (even if the first slave is removed) until
2890 device and then changing its slaves (or their order)::
2899 To restore your slaves' MAC addresses, you need to detach them
2901 then restore the MAC addresses that the slaves had before they were