Lines Matching refs:slave
167 Specifies the new active slave for modes that support it
170 string. If a name is given, the slave and its link must be up in order
171 to be selected as the new active slave. If an empty string is
172 specified, the current active slave is cleared, and a new active
173 slave is selected automatically.
179 active slave, or the empty string if there is no active slave or
180 the current mode does not use an active slave.
224 - A slave is added to or removed from the bond
226 - Any slave's link state changes
228 - Any slave's 802.3ad association state changes
276 The ARP monitor works by periodically checking the slave
279 bonding mode, and the state of the slave). Regular traffic is
322 Validation is performed only for the active slave.
340 only for the active slave.
350 ARP requests and replies, and only consider a slave to be up if it
353 For an active slave, the validation checks ARP replies to confirm
357 active slave. It is possible that some switch or network
364 the active slave failure, it doesn't really guarantee that the
365 backup slave will work if it's selected as the next active slave.
382 if a slave is available.
386 determining if a slave has received traffic for link availability
400 in order for the ARP monitor to consider a slave as being up.
408 consider the slave up only when any of the arp_ip_targets
413 consider the slave up only when all of the arp_ip_targets
419 a slave after a link failure has been detected. This option
445 address of the currently active slave. The MAC
473 the MAC address of the first slave added to the bond).
476 slave is programmed with the bond's MAC address at
477 failover time (and the formerly active slave receives
478 the newly active slave's MAC address).
486 The default policy is none, unless the first slave cannot
521 This determines how often the link state of each slave is
553 order from the first available slave through the
559 Active-backup policy: Only one slave in the bond is
560 active. A different slave becomes active if, and only
561 if, the active slave fails. The bond's MAC address is
567 or more gratuitous ARPs on the newly active slave.
583 packet type ID) modulo slave count]. Alternate transmit
591 Broadcast policy: transmits everything on all slave
614 the speed and duplex of each slave.
629 relative to the speed) on each slave.
635 Incoming traffic is received by the current slave.
636 If the receiving slave fails, another slave takes over
637 the MAC address of the failed receiving slave.
642 speed of each slave.
669 collapses to the current slave. This is handled by
673 redistributed when a new slave is added to the bond
674 and when an inactive slave is re-activated. The
678 When a link is reconnected or a new slave joins the
690 the speed of each slave.
694 required so that there will always be one slave in the
697 address for each slave in the bond. If the
707 failover event. As soon as the link is up on the new slave
723 Specify the number of packets to transmit through a slave before
724 moving to the next one. When set to 0 then a slave is chosen at
732 A string (eth0, eth2, etc) specifying which slave is the
734 active slave while it is available. Only when the primary is
736 one slave is preferred over another, e.g., when one slave has
744 Specifies the reselection policy for the primary slave. This
745 affects how the primary slave is chosen to become the active slave
746 when failure of the active slave or recovery of the primary slave
748 the primary slave and other slaves. Possible values are:
752 The primary slave becomes the active slave whenever it
757 The primary slave becomes the active slave when it comes
758 back up, if the speed and duplex of the primary slave is
760 slave.
764 The primary slave becomes the active slave only if the
765 current active slave fails and the primary slave is up.
769 If no slaves are active, the first slave to recover is
770 made the active slave.
772 When initially enslaved, the primary slave is always made
773 the active slave.
776 immediate selection of the best active slave according to the new
778 slave, depending upon the circumstances.
807 slave after a link recovery has been detected. This option is
836 Selects the transmit hash policy to use for slave selection in
845 slave number = hash modulo slave count
848 network peer on the same slave.
864 And then hash is reduced modulo slave count.
870 network peer on the same slave. For non-IP traffic,
895 And then hash is reduced modulo slave count.
953 switch the IGMP traffic from one slave to another. Therefore a fresh
955 IGMP traffic over the newly selected slave.
1019 slave devices. On SLES 9, this is most easily done by running the
1021 ifcfg-id file for each slave device. The simplest way to accomplish
1032 created, it is necessary to edit the configuration files for the slave
1033 devices (the MAC addresses correspond to those of the slave devices).
1101 Finally, supply one BONDING_SLAVEn="slave device" for each
1102 slave. where "n" is an increasing value, one for each slave. The
1103 "slave device" is either an interface name, e.g., "eth0", or a device
1111 configurations will choose one or the other for all slave devices.
1144 the slave devices. Without active slaves, the DHCP requests are not
1442 To free slave eth0 from bond bond0:
1603 ID is now printed for each slave:
1625 The queue_id for a slave can be set using the command:
1632 arguments can be added to BONDING_OPTS to set all needed slave queues.
1636 slave devices. For instance, say we wanted, in the above configuration to
1653 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1655 slave devices as well as bond devices and the bonding driver will simply act as
1656 a pass-through for selecting output queues on the slave device rather than
1660 output slave selection was limited to round-robin and active-backup modes.
1717 about the bonding configuration, options and state of each slave.
1746 command. Bonding devices will have the MASTER flag set; Bonding slave
1753 TLB and ALB that require a unique MAC address for each slave.
1833 only after enslaving at least one slave. The bonding interface has a
1834 hardware address of 00:00:00:00:00:00 until the first slave is added.
1836 would pick up the all-zeroes hardware address. Once the first slave
1838 slave's hardware address, which is then available for the VLAN device.
1842 top of it. When a new slave is added, the bonding interface will
1843 obtain its hardware address from the first slave, which might not
1845 ultimately copied from an earlier slave).
1865 monitoring a slave device's link state: the ARP monitor and the MII
1945 When bonding is configured, it is important that the slave
1997 happens because bonding is loaded first, then its slave device's
2102 master device (e.g., bond0), and propagates the setting to the slave
2109 promiscuous mode setting is propagated only to the active slave.
2111 For balance-tlb mode, the active slave is the slave currently
2114 For balance-alb mode, the active slave is the slave used as a
2115 "primary." This slave is used for mode-specific control traffic, for
2119 the active slave changes (e.g., due to a link failure), the
2120 promiscuous setting will be propagated to the new active slave.
2412 network device driver of the slave interfaces, and the ARP
2518 case). If there are slave interfaces waiting for the updelay timeout
2541 output from ping flags duplicates (typically one per slave).
2565 (one per slave device).
2710 5. What happens when a slave link dies?
2758 When using slave devices that have fixed MAC addresses, or when
2760 the MAC address of the active slave.
2764 its first slave device. This MAC address is then passed to all following
2765 slaves and remains persistent (even if the first slave is removed) until
2783 slave that is added.