Lines Matching refs:slaves
192 slaves of the active aggregator are down or the active
193 aggregator has no slaves.
213 ports (slaves). Reselection occurs as described under the
289 Validation is performed only for backup slaves.
293 Validation is performed for all slaves.
297 Filtering is applied to all slaves. No validation is
302 Filtering is applied to all slaves, validation is performed
307 Filtering is applied to all slaves, validation is performed
308 only for backup slaves.
317 that they were generated by an arp_ip_target. Since backup slaves
319 for backup slaves is on the broadcast ARP request sent out via the
321 configurations may result in situations wherein the backup slaves
323 of backup slaves must be disabled.
325 The validation of ARP requests on backup slaves is mainly helping
326 bonding to decide which slaves are more likely to work in case of
364 This option affects only active-backup mode for slaves with
390 Specifies whether active-backup mode should set all slaves to
400 bonding to set all slaves of an active-backup bond to
409 address of the slaves is not changed; instead, the MAC
437 However, the second and subsequent slaves are not set
453 This option may be modified via sysfs only when no slaves are
561 duplex settings. Utilizes all slaves in the active
616 address of one of the slaves in the bond such that
626 reply to this peer assigning it to one of the slaves
639 among the group of highest speed slaves in the bond.
643 active slaves in the bond by initiating ARP Replies
711 the primary slave and other slaves. Possible values are:
732 If no slaves are active, the first slave to recover is
751 slaves based on the load in that interval. This gives nice lb
849 slaves, although a single connection will not span
850 multiple slaves.
925 driver sends learning packets to each slaves peer switch.
1107 the slave devices. Without active slaves, the DHCP requests are not
1398 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1403 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1406 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1415 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1457 the bonding driver sends learning packets to each slaves peer switch. The
1475 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1476 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1488 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1489 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1510 active-backup mode, with eth0 and eth1 as slaves.
1514 bond-slaves eth0 eth1
1526 bond-slaves none
1664 contain information on which slaves are associated with which masters.
1667 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1742 information, and it propagates those actions to the slaves. In case
1756 Also, be aware that a similar problem can occur if all slaves
1764 with the correct hardware address if all slaves are removed from a
1801 ARP monitor will immediately fail any slaves using that driver, and
1802 those slaves will stay down. If networking monitoring (tcpdump, etc)
1864 device bond0 has two slaves, eth0 and eth1, and the routing table is
1887 The solution here is simply to insure that slaves do not have
1911 If neither eth0 and eth1 are slaves to bond0, then when the
1973 eth1 are slaves of bond0 and the driver for eth0 is loaded before the
2022 the promiscuous mode setting is propagated to all slaves.
2459 For example, on a bond in active-backup mode with five slaves
2614 slaves in active-backup mode.
2620 4. How many slaves can a bonding device have?
2681 slaves and remains persistent (even if the first slave is removed) until
2692 device and then changing its slaves (or their order):
2701 To restore your slaves' MAC addresses, you need to detach them
2703 then restore the MAC addresses that the slaves had before they were