Lines Matching refs:slave
166 Specifies the new active slave for modes that support it
169 string. If a name is given, the slave and its link must be up in order
170 to be selected as the new active slave. If an empty string is
171 specified, the current active slave is cleared, and a new active
172 slave is selected automatically.
178 active slave, or the empty string if there is no active slave or
179 the current mode does not use an active slave.
202 - A slave is added to or removed from the bond
204 - Any slave's link state changes
206 - Any slave's 802.3ad association state changes
239 The ARP monitor works by periodically checking the slave
242 bonding mode, and the state of the slave). Regular traffic is
285 Validation is performed only for the active slave.
303 only for the active slave.
313 ARP requests and replies, and only consider a slave to be up if it
316 For an active slave, the validation checks ARP replies to confirm
320 active slave. It is possible that some switch or network
327 the active slave failure, it doesn't really guarantee that the
328 backup slave will work if it's selected as the next active slave.
345 if a slave is available.
349 determining if a slave has received traffic for link availability
363 in order for the ARP monitor to consider a slave as being up.
371 consider the slave up only when any of the arp_ip_targets
376 consider the slave up only when all of the arp_ip_targets
382 a slave after a link failure has been detected. This option
408 address of the currently active slave. The MAC
436 the MAC address of the first slave added to the bond).
439 slave is programmed with the bond's MAC address at
440 failover time (and the formerly active slave receives
441 the newly active slave's MAC address).
449 The default policy is none, unless the first slave cannot
484 This determines how often the link state of each slave is
516 order from the first available slave through the
522 Active-backup policy: Only one slave in the bond is
523 active. A different slave becomes active if, and only
524 if, the active slave fails. The bond's MAC address is
530 or more gratuitous ARPs on the newly active slave.
546 packet type ID) modulo slave count]. Alternate transmit
554 Broadcast policy: transmits everything on all slave
577 the speed and duplex of each slave.
592 relative to the speed) on each slave.
598 Incoming traffic is received by the current slave.
599 If the receiving slave fails, another slave takes over
600 the MAC address of the failed receiving slave.
605 speed of each slave.
632 collapses to the current slave. This is handled by
636 redistributed when a new slave is added to the bond
637 and when an inactive slave is re-activated. The
641 When a link is reconnected or a new slave joins the
653 the speed of each slave.
657 required so that there will always be one slave in the
660 address for each slave in the bond. If the
670 failover event. As soon as the link is up on the new slave
686 Specify the number of packets to transmit through a slave before
687 moving to the next one. When set to 0 then a slave is chosen at
695 A string (eth0, eth2, etc) specifying which slave is the
697 active slave while it is available. Only when the primary is
699 one slave is preferred over another, e.g., when one slave has
707 Specifies the reselection policy for the primary slave. This
708 affects how the primary slave is chosen to become the active slave
709 when failure of the active slave or recovery of the primary slave
711 the primary slave and other slaves. Possible values are:
715 The primary slave becomes the active slave whenever it
720 The primary slave becomes the active slave when it comes
721 back up, if the speed and duplex of the primary slave is
723 slave.
727 The primary slave becomes the active slave only if the
728 current active slave fails and the primary slave is up.
732 If no slaves are active, the first slave to recover is
733 made the active slave.
735 When initially enslaved, the primary slave is always made
736 the active slave.
739 immediate selection of the best active slave according to the new
741 slave, depending upon the circumstances.
770 slave after a link recovery has been detected. This option is
799 Selects the transmit hash policy to use for slave selection in
808 slave number = hash modulo slave count
811 network peer on the same slave.
827 And then hash is reduced modulo slave count.
833 network peer on the same slave. For non-IP traffic,
858 And then hash is reduced modulo slave count.
916 switch the IGMP traffic from one slave to another. Therefore a fresh
918 IGMP traffic over the newly selected slave.
982 slave devices. On SLES 9, this is most easily done by running the
984 ifcfg-id file for each slave device. The simplest way to accomplish
995 created, it is necessary to edit the configuration files for the slave
996 devices (the MAC addresses correspond to those of the slave devices).
1064 Finally, supply one BONDING_SLAVEn="slave device" for each
1065 slave. where "n" is an increasing value, one for each slave. The
1066 "slave device" is either an interface name, e.g., "eth0", or a device
1074 configurations will choose one or the other for all slave devices.
1107 the slave devices. Without active slaves, the DHCP requests are not
1405 To free slave eth0 from bond bond0:
1566 ID is now printed for each slave:
1588 The queue_id for a slave can be set using the command:
1595 arguments can be added to BONDING_OPTS to set all needed slave queues.
1599 slave devices. For instance, say we wanted, in the above configuration to
1616 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1618 slave devices as well as bond devices and the bonding driver will simply act as
1619 a pass-through for selecting output queues on the slave device rather than
1623 output slave selection was limited to round-robin and active-backup modes.
1633 about the bonding configuration, options and state of each slave.
1662 command. Bonding devices will have the MASTER flag set; Bonding slave
1669 TLB and ALB that require a unique MAC address for each slave.
1749 only after enslaving at least one slave. The bonding interface has a
1750 hardware address of 00:00:00:00:00:00 until the first slave is added.
1752 would pick up the all-zeroes hardware address. Once the first slave
1754 slave's hardware address, which is then available for the VLAN device.
1758 top of it. When a new slave is added, the bonding interface will
1759 obtain its hardware address from the first slave, which might not
1761 ultimately copied from an earlier slave).
1781 monitoring a slave device's link state: the ARP monitor and the MII
1861 When bonding is configured, it is important that the slave
1913 happens because bonding is loaded first, then its slave device's
2018 master device (e.g., bond0), and propagates the setting to the slave
2025 promiscuous mode setting is propagated only to the active slave.
2027 For balance-tlb mode, the active slave is the slave currently
2030 For balance-alb mode, the active slave is the slave used as a
2031 "primary." This slave is used for mode-specific control traffic, for
2035 the active slave changes (e.g., due to a link failure), the
2036 promiscuous setting will be propagated to the new active slave.
2328 network device driver of the slave interfaces, and the ARP
2434 case). If there are slave interfaces waiting for the updelay timeout
2457 output from ping flags duplicates (typically one per slave).
2481 (one per slave device).
2626 5. What happens when a slave link dies?
2674 When using slave devices that have fixed MAC addresses, or when
2676 the MAC address of the active slave.
2680 its first slave device. This MAC address is then passed to all following
2681 slaves and remains persistent (even if the first slave is removed) until
2699 slave that is added.