Lines Matching +full:slave +full:- +full:mode
1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
29 The behavior of the bonded interfaces depends upon the mode; generally
35 the original tools from extreme-linux and beowulf sites will not work
59 3.7 Configuring LACP for 802.3ad mode in a more secure way
81 10. Promiscuous mode
86 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
91 12.1.1 MT Bonding Mode Selection for Single Switch Topology
94 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
119 -----------------------------------------------
135 ---------------------------
148 ``/etc/modprobe.d/*.conf`` configuration files, or in a distro-specific
156 configuring a bond, it is recommended "tail -f /var/log/messages" be
166 "mode=802.3ad" and "mode=4" set the same mode.
172 Specifies the new active slave for modes that support it
173 (active-backup, balance-alb and balance-tlb). Possible values
175 string. If a name is given, the slave and its link must be up in order
176 to be selected as the new active slave. If an empty string is
177 specified, the current active slave is cleared, and a new active
178 slave is selected automatically.
184 active slave, or the empty string if there is no active slave or
185 the current mode does not use an active slave.
190 is 1 - 65535. If the value is not specified, it takes 65535 as the
193 This parameter has effect only in 802.3ad mode and is available through
198 In an AD system, this specifies the mac-address for the actor in
200 address. If the all-zeroes MAC is specified, bonding will internally
202 local-admin bit set for this mac but driver does not enforce it. If
206 This parameter has effect only in 802.3ad mode and is available through
230 - A slave is added to or removed from the bond
232 - Any slave's link state changes
234 - Any slave's 802.3ad association state changes
236 - The bond's administrative state changes to up
253 In an AD system, the port-key has three parts as shown below -
259 01-05 Speed
260 06-15 User-defined
264 from 0 - 1023. If not given, the system defaults to 0.
266 This parameter has effect only in 802.3ad mode and is available through
285 The ARP monitor works by periodically checking the slave
288 bonding mode, and the state of the slave). Regular traffic is
295 If ARP monitoring is used in an etherchannel compatible mode
296 (modes 0 and 2), the switch should be configured in a mode
319 validated in any mode that supports arp monitoring, or whether
320 non-ARP traffic should be filtered (disregarded) for link
331 Validation is performed only for the active slave.
349 only for the active slave.
359 ARP requests and replies, and only consider a slave to be up if it
362 For an active slave, the validation checks ARP replies to confirm
366 active slave. It is possible that some switch or network
373 the active slave failure, it doesn't really guarantee that the
374 backup slave will work if it's selected as the next active slave.
391 if a slave is available.
395 determining if a slave has received traffic for link availability
409 in order for the ARP monitor to consider a slave as being up.
410 This option affects only active-backup mode for slaves with
417 consider the slave up only when any of the arp_ip_targets
422 consider the slave up only when all of the arp_ip_targets
428 a slave after a link failure has been detected. This option
436 Specifies whether active-backup mode should set all slaves to
446 bonding to set all slaves of an active-backup bond to
454 address of the currently active slave. The MAC
482 the MAC address of the first slave added to the bond).
485 slave is programmed with the bond's MAC address at
486 failover time (and the formerly active slave receives
487 the newly active slave's MAC address).
495 The default policy is none, unless the first slave cannot
508 to transmit LACPDU packets in 802.3ad mode. Possible values
530 This determines how often the link state of each slave is
540 asserting carrier. It is similar to the Cisco EtherChannel min-links
542 must be up (link-up state) before marking the bond device as up
546 mode.
549 802.3ad mode) whenever there is an active aggregator, regardless of the
554 mode
557 balance-rr (round robin). Possible values are:
559 balance-rr or 0
561 Round-robin policy: Transmit packets in sequential
562 order from the first available slave through the
563 last. This mode provides load balancing and fault
566 active-backup or 1
568 Active-backup policy: Only one slave in the bond is
569 active. A different slave becomes active if, and only
570 if, the active slave fails. The bond's MAC address is
575 occurs in active-backup mode, bonding will issue one
576 or more gratuitous ARPs on the newly active slave.
583 This mode provides fault tolerance. The primary
585 mode.
587 balance-xor or 2
592 packet type ID) modulo slave count]. Alternate transmit
596 This mode provides load balancing and fault tolerance.
600 Broadcast policy: transmits everything on all slave
601 interfaces. This mode provides fault tolerance.
610 Slave selection for outgoing traffic is done according
615 regards to the packet mis-ordering requirements of
623 the speed and duplex of each slave.
629 to enable 802.3ad mode.
631 balance-tlb or 5
636 In tlb_dynamic_lb=1 mode; the outgoing traffic is
638 relative to the speed) on each slave.
640 In tlb_dynamic_lb=0 mode; the load balancing based on
644 Incoming traffic is received by the current slave.
645 If the receiving slave fails, another slave takes over
646 the MAC address of the failed receiving slave.
651 speed of each slave.
653 balance-alb or 6
655 Adaptive load balancing: includes balance-tlb plus
678 collapses to the current slave. This is handled by
682 redistributed when a new slave is added to the bond
683 and when an inactive slave is re-activated. The
687 When a link is reconnected or a new slave joins the
699 the speed of each slave.
703 required so that there will always be one slave in the
706 address for each slave in the bond. If the
716 failover event. As soon as the link is up on the new slave
718 bonding device and each VLAN sub-device. This is repeated at
722 The valid range is 0 - 255; the default value is 1. These options
723 affect only the active-backup mode. These options were added for
732 Specify the number of packets to transmit through a slave before
733 moving to the next one. When set to 0 then a slave is chosen at
736 The valid range is 0 - 65535; the default value is 1. This option
737 has effect only in balance-rr mode.
751 A string (eth0, eth2, etc) specifying which slave is the
753 active slave while it is available. Only when the primary is
754 off-line will alternate devices be used. This is useful when
755 one slave is preferred over another, e.g., when one slave has
758 The primary option is only valid for active-backup(1),
759 balance-tlb (5) and balance-alb (6) mode.
763 Specifies the reselection policy for the primary slave. This
764 affects how the primary slave is chosen to become the active slave
765 when failure of the active slave or recovery of the primary slave
766 occurs. This option is designed to prevent flip-flopping between
767 the primary slave and other slaves. Possible values are:
771 The primary slave becomes the active slave whenever it
776 The primary slave becomes the active slave when it comes
777 back up, if the speed and duplex of the primary slave is
779 slave.
783 The primary slave becomes the active slave only if the
784 current active slave fails and the primary slave is up.
788 If no slaves are active, the first slave to recover is
789 made the active slave.
791 When initially enslaved, the primary slave is always made
792 the active slave.
795 immediate selection of the best active slave according to the new
797 slave, depending upon the circumstances.
804 mode. The value has no effect on any other modes.
806 The default behavior of tlb mode is to shuffle active flows across
808 characteristics but can cause packet reordering. If re-ordering is
811 xmit-hash-policy can be used to select the appropriate hashing for
826 slave after a link recovery has been detected. This option is
855 Selects the transmit hash policy to use for slave selection in
856 balance-xor, 802.3ad, and tlb modes. Possible values are:
864 slave number = hash modulo slave count
867 network peer on the same slave.
883 And then hash is reduced modulo slave count.
889 network peer on the same slave. For non-IP traffic,
914 And then hash is reduced modulo slave count.
921 information is omitted. For non-IP traffic, the
966 The valid range is 0 - 255; the default value is 1. A value of 0
970 This option is useful for bonding modes balance-rr (0), active-backup
971 (1), balance-tlb (5) and balance-alb (6), in which a failover can
972 switch the IGMP traffic from one slave to another. Therefore a fresh
974 IGMP traffic over the newly selected slave.
983 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
984 has effect only in balance-tlb and balance-alb modes.
1012 $ rpm -qf /sbin/ifup
1027 ----------------------------------------
1038 slave devices. On SLES 9, this is most easily done by running the
1040 ifcfg-id file for each slave device. The simplest way to accomplish
1042 file ifcfg-id file created; see below for some issues with DHCP). The
1045 ifcfg-id-xx:xx:xx:xx:xx:xx
1050 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1051 created, it is necessary to edit the configuration files for the slave
1052 devices (the MAC addresses correspond to those of the slave devices).
1060 _nm_name='bus-pci-0001:61:01.0'
1070 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1072 itself. This file is named ifcfg-bondX, where X is the number of the
1074 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1078 The contents of the ifcfg-bondX file is as follows::
1088 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1090 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1119 for the bonding mode, link monitoring, and so on here. Do not include
1123 Finally, supply one BONDING_SLAVEn="slave device" for each
1124 slave. where "n" is an increasing value, one for each slave. The
1125 "slave device" is either an interface name, e.g., "eth0", or a device
1129 (bus-pci-0000:06:08.1 in the example above) specify the physical
1133 configurations will choose one or the other for all slave devices.
1160 -------------------------------
1166 the slave devices. Without active slaves, the DHCP requests are not
1170 -----------------------------------------------
1174 bonding instance to have an appropriately configured ifcfg-bondX file
1178 ifcfg-bondX files.
1181 options in the ifcfg-bondX file, it is not necessary to add them to
1185 ------------------------------------------
1198 network-script file for all physical adapters that will be members of
1201 /etc/sysconfig/network-scripts
1203 The file name must be prefixed with "ifcfg-eth" and suffixed
1205 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1212 SLAVE=yes
1216 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1224 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1225 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1226 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1243 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1246 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1269 options bond0 mode=balance-alb miimon=100
1279 ---------------------------------
1292 -------------------------------------------------
1296 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1304 -----------------------------------------------
1323 modprobe bonding mode=balance-alb miimon=100
1346 enabled without re-running the entire global init script.
1362 -----------------------------------------
1391 options bond0 -o bond0 mode=balance-rr miimon=100
1394 options bond1 -o bond1 mode=balance-alb miimon=50
1397 named "bond0" and creates the bond0 device in balance-rr mode with an
1399 bond1 device in balance-alb mode with an miimon of 50.
1406 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1407 mode=balance-alb miimon=50
1413 to rename modules at load time (the "-o bond1" part). Attempts to pass
1421 ------------------------------------------
1441 -----------------------------
1448 # echo -bar > /sys/class/net/bonding_masters
1461 --------------------------
1471 To free slave eth0 from bond bond0::
1473 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1482 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1487 -------------------------------
1491 The names of these files correspond directly with the command-
1500 To configure bond0 for balance-alb mode::
1503 # echo 6 > /sys/class/net/bond0/bonding/mode
1504 - or -
1505 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1509 The bond interface must be down before the mode can be changed.
1518 monitoring is enabled, and vice-versa.
1531 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1544 ---------------------
1555 echo balance-alb > /sys/class/net/bond0/bonding/mode
1562 active-backup mode, using ARP monitoring, add the following lines to
1567 echo active-backup > /sys/class/net/bond1/bonding/mode
1575 -----------------------------------------
1582 the box. The ifenslave-2.6 package should be installed to provide bonding
1583 support. Once installed, this package will provide ``bond-*`` options
1586 Note that ifenslave-2.6 package will load the bonding module and use
1590 ----------------------
1593 active-backup mode, with eth0 and eth1 as slaves::
1597 bond-slaves eth0 eth1
1598 bond-mode active-backup
1599 bond-miimon 100
1600 bond-primary eth0 eth1
1609 bond-slaves none
1610 bond-mode active-backup
1611 bond-miimon 100
1615 bond-master bond0
1616 bond-primary eth0 eth1
1620 bond-master bond0
1621 bond-primary eth0 eth1
1623 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1625 /usr/share/doc/ifenslave-2.6.
1628 ----------------------------------------------
1633 the selected bonding mode. On occasion however, it is helpful to direct certain
1649 ID is now printed for each slave::
1651 Bonding Mode: fault-tolerance (active-backup)
1652 Primary Slave: None
1653 Currently Active Slave: eth0
1659 Slave Interface: eth0
1663 Slave queue ID: 0
1665 Slave Interface: eth1
1669 Slave queue ID: 2
1671 The queue_id for a slave can be set using the command::
1678 arguments can be added to BONDING_OPTS to set all needed slave queues.
1682 slave devices. For instance, say we wanted, in the above configuration to
1699 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1701 slave devices as well as bond devices and the bonding driver will simply act as
1702 a pass-through for selecting output queues on the slave device rather than
1706 output slave selection was limited to round-robin and active-backup modes.
1708 3.7 Configuring LACP for 802.3ad mode in a more secure way
1709 ----------------------------------------------------------
1711 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1725 (a) ad_actor_system : You can set a random mac-address that can be used for
1727 Also it's preferable to set the local-admin bit. Following shell code
1728 generates a random mac-address as described above::
1740 is 65535, but system can take the value from 1 - 65535. Following shell
1746 (c) ad_user_port_key : Use the user portion of the port-key. The default
1747 keeps this empty. These are the upper 10 bits of the port-key and value
1748 ranges from 0 - 1023. Following shell code generates these 10 bits and
1759 -------------------------
1761 Each bonding device has a read-only file residing in the
1763 about the bonding configuration, options and state of each slave.
1766 driver is loaded with parameters of mode=0 and miimon=1000 is
1770 Bonding Mode: load balancing (round-robin)
1771 Currently Active Slave: eth0
1777 Slave Interface: eth1
1781 Slave Interface: eth0
1789 -------------------------
1792 command. Bonding devices will have the MASTER flag set; Bonding slave
1793 devices will have the SLAVE flag set. The ifconfig output does not
1797 (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of
1799 TLB and ALB that require a unique MAC address for each slave::
1810 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
1817 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
1832 The active-backup, balance-tlb and balance-alb modes do not
1835 The 802.3ad mode requires that the switch have the appropriate
1840 etherchannel is set to mode "lacp" to enable 802.3ad (instead of
1843 The balance-rr, balance-xor and broadcast modes generally
1851 match. For these three modes, the bonding mode really selects a
1863 packets generated by either ALB mode or the ARP monitor mechanism, are
1875 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1879 only after enslaving at least one slave. The bonding interface has a
1880 hardware address of 00:00:00:00:00:00 until the first slave is added.
1882 would pick up the all-zeroes hardware address. Once the first slave
1884 slave's hardware address, which is then available for the VLAN device.
1888 top of it. When a new slave is added, the bonding interface will
1889 obtain its hardware address from the first slave, which might not
1891 ultimately copied from an earlier slave).
1903 underlying device -- i.e. the bonding interface -- to promiscuous
1904 mode, which might not be what you want.
1911 monitoring a slave device's link state: the ARP monitor and the MII
1919 -------------------------
1929 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1930 flag must also update netdev_queue->trans_start. If they do not, then the
1937 ------------------------------------
1960 -------------------------
1989 -------------------------
1991 When bonding is configured, it is important that the slave
2024 ----------------------------
2035 options bond0 mode=some-mode miimon=50
2043 happens because bonding is loaded first, then its slave device's
2068 ---------------------------------------------------------
2143 10. Promiscuous mode
2147 common to enable promiscuous mode on the device, so that all traffic
2149 The bonding driver handles promiscuous mode changes to the bonding
2150 master device (e.g., bond0), and propagates the setting to the slave
2153 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2154 the promiscuous mode setting is propagated to all slaves.
2156 For the active-backup, balance-tlb and balance-alb modes, the
2157 promiscuous mode setting is propagated only to the active slave.
2159 For balance-tlb mode, the active slave is the slave currently
2162 For balance-alb mode, the active slave is the slave used as a
2163 "primary." This slave is used for mode-specific control traffic, for
2166 For the active-backup, balance-tlb and balance-alb modes, when
2167 the active slave changes (e.g., due to a link failure), the
2168 promiscuous setting will be propagated to the new active slave.
2181 --------------------------------------------------
2195 ----------------------------------------------------
2206 +-----+----+ +-----+----+
2208 | switch A +--------------------------+ switch B |
2210 +-----+----+ +-----++---+
2212 | +-------+ |
2213 +-------------+ host1 +---------------+
2214 eth0 +-------+ eth1
2221 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
2222 -------------------------------------------------------------
2224 In a topology such as the example above, the active-backup and
2229 active-backup:
2230 This is generally the preferred mode, particularly if
2238 This mode is really a special purpose mode, and is suitable
2242 necessary for some specific one-way traffic to reach both
2243 independent networks, then the broadcast mode may be suitable.
2246 ----------------------------------------------------------------
2279 ------------------------------------------------------
2295 +----------+ +----------+
2297 | Host A +---------------------+ router +------------------->
2298 | +---------------------+ | Hosts B and C are out
2300 +----------+ +----------+
2322 +----------+ +----------+ +--------+
2323 | |eth0 port1| +-------+ Host B |
2324 | Host A +------------+ switch |port3 +--------+
2325 | +------------+ | +--------+
2326 | |eth1 port2| +------------------+ Host C |
2327 +----------+ +----------+port4 +--------+
2346 mode is described below.
2349 12.1.1 MT Bonding Mode Selection for Single Switch Topology
2350 -----------------------------------------------------------
2353 although you will have to decide which bonding mode best suits your
2354 needs. The trade offs for each mode are detailed below:
2356 balance-rr:
2357 This mode is the only mode that will permit a single
2359 interfaces. It is therefore the only mode that will allow a
2383 through the switch to a balance-rr bond will not utilize greater
2388 delivery, then this mode can allow for single stream datagram
2392 This mode requires the switch to have the appropriate ports
2395 active-backup:
2397 the active-backup mode, as the inactive backup devices are all
2399 load balancing mode (with link monitoring) will provide the
2401 available bandwidth. On the plus side, active-backup mode
2406 balance-xor:
2407 This mode will limit traffic such that packets destined
2410 addresses involved, this mode works best in a "local" network
2412 the same local network. This mode is likely to be suboptimal
2416 As with balance-rr, the switch ports need to be configured for
2420 Like active-backup, there is not much advantage to this
2421 mode in this type of network topology.
2424 This mode can be a good choice for this type of network
2425 topology. The 802.3ad mode is an IEEE standard, so all peers
2433 packets. The 802.3ad mode does have some drawbacks: the
2436 balance modes other than balance-rr, no single connection will
2449 Finally, the 802.3ad mode mandates the use of the MII monitor,
2450 therefore, the ARP monitor is not available in this mode.
2452 balance-tlb:
2453 The balance-tlb mode balances outgoing traffic by peer.
2455 "gatewayed" configuration (as described above), this mode will
2457 "local" network configuration, this mode balances multiple
2459 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2466 in this mode all incoming traffic arrives over a single
2467 interface, this mode requires certain ethtool support in the
2468 network device driver of the slave interfaces, and the ARP
2471 balance-alb:
2472 This mode is everything that balance-tlb is, and more.
2473 It has all of the features (and restrictions) of balance-tlb,
2478 The only additional down side to this mode is that the network
2483 ----------------------------------------------------
2486 mode you choose to use. The more advanced load balancing modes do not
2492 -----------------------------------------------------
2498 +-----------+
2500 +-+---+---+-+
2502 +--------+ | +---------+
2504 +------+---+ +-----+----+ +-----+----+
2506 +------+---+ +-----+----+ +-----+----+
2508 +--------+ | +---------+
2510 +-+---+---+-+
2512 +-----------+
2526 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
2527 -------------------------------------------------------------
2529 In actual practice, the bonding mode typically employed in
2530 configurations of this type is balance-rr. Historically, in this
2535 packets has arrived). When employed in this fashion, the balance-rr
2536 mode allows individual connections between two hosts to effectively
2540 ------------------------------------------------------
2553 -------------------------------------------
2575 case). If there are slave interfaces waiting for the updelay timeout
2583 switches take a long time to go into backup mode, it may be desirable
2588 --------------------------------
2598 output from ping flags duplicates (typically one per slave).
2600 For example, on a bond in active-backup mode with five slaves
2603 # ping -n 10.0.4.2
2622 (one per slave device).
2627 most Cisco switches, the privileged command "clear mac address-table
2638 --------------------
2643 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2648 --------------------------------
2651 integrated on the planar (that's "motherboard" in IBM-speak). In the
2654 An add-on Broadcom daughter card can be installed on a JS20 to provide
2663 Additional BladeCenter-specific networking information can be
2666 - "IBM eServer BladeCenter Networking Options"
2667 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2670 ------------------------------------
2695 -------------------------------
2697 The balance-rr mode requires the use of passthrough modules
2700 appropriate ports, as is usual for balance-rr.
2702 The balance-alb and balance-tlb modes will function with
2709 The active-backup mode has no additional requirements.
2712 ----------------------
2727 --------------
2737 avoid fail-over delay issues when using bonding.
2744 -------------------
2750 -----------------------------------------
2752 Any Ethernet type cards (you can even mix cards - a Intel
2757 slaves in active-backup mode.
2760 ----------------------------------------
2765 ----------------------------------------------
2771 5. What happens when a slave link dies?
2772 ----------------------------------------
2775 disabled. The active-backup mode will fail over to a backup link, and
2778 manner is appropriate for the mode). See the sections on High
2779 Availability and the documentation for each mode for additional
2792 depends upon the bonding mode and network configuration.
2795 ----------------------------------------------
2800 ---------------------------------------------
2802 The full answer to this depends upon the desired mode.
2804 In the basic balance modes (balance-rr and balance-xor), it
2809 The advanced balance modes (balance-tlb and balance-alb) do
2814 In 802.3ad mode, it works with systems that support IEEE
2818 The active-backup mode should work with any Layer-II switch.
2821 ---------------------------------------------------------
2823 When using slave devices that have fixed MAC addresses, or when
2825 the MAC address of the active slave.
2829 its first slave device. This MAC address is then passed to all following
2830 slaves and remains persistent (even if the first slave is removed) until
2843 # ifconfig bond0 down ; modprobe -r bonding
2848 slave that is added.
2851 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2873 http://vger.kernel.org/vger-lists.html#netdev