Lines Matching +full:mode +full:- +full:switch
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
65 5. Switch Configuration
81 10. Promiscuous mode
84 11.1 High Availability in a Single Switch Topology
85 11.2 High Availability in a Multiple Switch Topology
86 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
87 11.2.2 HA Link Monitoring for Multiple Switch Topology
90 12.1 Maximum Throughput in a Single Switch Topology
91 12.1.1 MT Bonding Mode Selection for Single Switch Topology
92 12.1.2 MT Link Monitoring for Single Switch Topology
93 12.2 Maximum Throughput in a Multiple Switch Topology
94 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
95 12.2.2 MT Link Monitoring for Multiple Switch Topology
97 13. Switch Behavior Issues
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.
173 (active-backup, balance-alb and balance-tlb). Possible values
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
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
298 switch is configured to distribute the packets in an XOR
330 validated in any mode that supports arp monitoring, or whether
331 non-ARP traffic should be filtered (disregarded) for link
377 active slave. It is possible that some switch or network
389 beyond a common switch. Should the link between the switch and
390 target fail (but not the switch itself), the probe traffic
421 This option affects only active-backup mode for slaves with
445 The default value is 2, and the allowable range is 1 - 255.
458 Specifies whether active-backup mode should set all slaves to
468 bonding to set all slaves of an active-backup bond to
487 vs. just updating a switch or set of switches (which
489 traffic, if the switch snoops incoming traffic to
542 to transmit LACPDU packets in 802.3ad mode. Possible values
574 asserting carrier. It is similar to the Cisco EtherChannel min-links
576 must be up (link-up state) before marking the bond device as up
580 mode.
583 802.3ad mode) whenever there is an active aggregator, regardless of the
588 mode
591 balance-rr (round robin). Possible values are:
593 balance-rr or 0
595 Round-robin policy: Transmit packets in sequential
597 last. This mode provides load balancing and fault
600 active-backup or 1
602 Active-backup policy: Only one slave in the bond is
606 to avoid confusing the switch.
609 occurs in active-backup mode, bonding will issue one
617 This mode provides fault tolerance. The primary
619 mode.
621 balance-xor or 2
630 This mode provides load balancing and fault tolerance.
635 interfaces. This mode provides fault tolerance.
649 regards to the packet mis-ordering requirements of
659 2. A switch that supports IEEE 802.3ad Dynamic link
663 to enable 802.3ad mode.
665 balance-tlb or 5
668 does not require any special switch support.
670 In tlb_dynamic_lb=1 mode; the outgoing traffic is
674 In tlb_dynamic_lb=0 mode; the load balancing based on
687 balance-alb or 6
689 Adaptive load balancing: includes balance-tlb plus
691 does not require any special switch support. The
717 and when an inactive slave is re-activated. The
726 be set to a value equal or greater than the switch's
728 peers will not be blocked by the switch.
752 bonding device and each VLAN sub-device. This is repeated at
756 The valid range is 0 - 255; the default value is 1. These options
757 affect only the active-backup mode. These options were added for
770 The valid range is 0 - 65535; the default value is 1. This option
771 has effect only in balance-rr mode.
789 for active-backup(1), balance-tlb (5) and balance-alb (6) mode.
799 off-line will alternate devices be used. This is useful when
803 The primary option is only valid for active-backup(1),
804 balance-tlb (5) and balance-alb (6) mode.
811 occurs. This option is designed to prevent flip-flopping between
849 or alb mode. The value has no effect on any other modes.
851 The default behavior of tlb mode is to shuffle active flows across
853 characteristics but can cause packet reordering. If re-ordering is
856 xmit-hash-policy can be used to select the appropriate hashing for
901 balance-xor, 802.3ad, and tlb modes. Possible values are:
934 network peer on the same slave. For non-IP traffic,
966 information is omitted. For non-IP traffic, the
1003 hash to load-balance traffic per-vlan, with failover
1006 use their own vlan, to give lacp-like functionality
1007 without requiring lacp-capable switching hardware.
1024 The valid range is 0 - 255; the default value is 1. A value of 0
1028 This option is useful for bonding modes balance-rr (0), active-backup
1029 (1), balance-tlb (5) and balance-alb (6), in which a failover can
1030 switch the IGMP traffic from one slave to another. Therefore a fresh
1031 IGMP report must be issued to cause the switch to forward the incoming
1039 driver sends learning packets to each slaves peer switch.
1041 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
1042 has effect only in balance-tlb and balance-alb modes.
1070 $ rpm -qf /sbin/ifup
1085 ----------------------------------------
1098 ifcfg-id file for each slave device. The simplest way to accomplish
1100 file ifcfg-id file created; see below for some issues with DHCP). The
1103 ifcfg-id-xx:xx:xx:xx:xx:xx
1108 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1118 _nm_name='bus-pci-0001:61:01.0'
1128 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1130 itself. This file is named ifcfg-bondX, where X is the number of the
1132 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1136 The contents of the ifcfg-bondX file is as follows::
1146 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1148 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1177 for the bonding mode, link monitoring, and so on here. Do not include
1187 (bus-pci-0000:06:08.1 in the example above) specify the physical
1218 -------------------------------
1228 -----------------------------------------------
1232 bonding instance to have an appropriately configured ifcfg-bondX file
1236 ifcfg-bondX files.
1239 options in the ifcfg-bondX file, it is not necessary to add them to
1243 ------------------------------------------
1256 network-script file for all physical adapters that will be members of
1259 /etc/sysconfig/network-scripts
1261 The file name must be prefixed with "ifcfg-eth" and suffixed
1263 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1274 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1282 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1283 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1284 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1301 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1304 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1327 options bond0 mode=balance-alb miimon=100
1337 ---------------------------------
1350 -------------------------------------------------
1354 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1362 -----------------------------------------------
1381 modprobe bonding mode=balance-alb miimon=100
1404 enabled without re-running the entire global init script.
1420 -----------------------------------------
1449 options bond0 -o bond0 mode=balance-rr miimon=100
1452 options bond1 -o bond1 mode=balance-alb miimon=50
1455 named "bond0" and creates the bond0 device in balance-rr mode with an
1457 bond1 device in balance-alb mode with an miimon of 50.
1464 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1465 mode=balance-alb miimon=50
1471 to rename modules at load time (the "-o bond1" part). Attempts to pass
1479 ------------------------------------------
1499 -----------------------------
1506 # echo -bar > /sys/class/net/bonding_masters
1519 --------------------------
1531 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1540 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1545 -------------------------------
1549 The names of these files correspond directly with the command-
1558 To configure bond0 for balance-alb mode::
1561 # echo 6 > /sys/class/net/bond0/bonding/mode
1562 - or -
1563 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1567 The bond interface must be down before the mode can be changed.
1576 monitoring is enabled, and vice-versa.
1589 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1598 the bonding driver sends learning packets to each slaves peer switch. The
1602 ---------------------
1613 echo balance-alb > /sys/class/net/bond0/bonding/mode
1620 active-backup mode, using ARP monitoring, add the following lines to
1625 echo active-backup > /sys/class/net/bond1/bonding/mode
1633 -----------------------------------------
1640 the box. The ifenslave-2.6 package should be installed to provide bonding
1641 support. Once installed, this package will provide ``bond-*`` options
1644 Note that ifenslave-2.6 package will load the bonding module and use
1648 ----------------------
1651 active-backup mode, with eth0 and eth1 as slaves::
1655 bond-slaves eth0 eth1
1656 bond-mode active-backup
1657 bond-miimon 100
1658 bond-primary eth0 eth1
1667 bond-slaves none
1668 bond-mode active-backup
1669 bond-miimon 100
1673 bond-master bond0
1674 bond-primary eth0 eth1
1678 bond-master bond0
1679 bond-primary eth0 eth1
1681 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1683 /usr/share/doc/ifenslave-2.6.
1686 ----------------------------------------------
1691 the selected bonding mode. On occasion however, it is helpful to direct certain
1709 Bonding Mode: fault-tolerance (active-backup)
1760 a pass-through for selecting output queues on the slave device rather than
1764 output slave selection was limited to round-robin and active-backup modes.
1766 3.7 Configuring LACP for 802.3ad mode in a more secure way
1767 ----------------------------------------------------------
1769 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1775 domain can spoof LACPDU packets from other hosts to the switch and potentially
1776 cause mayhem by joining (from the point of view of the switch) another
1783 (a) ad_actor_system : You can set a random mac-address that can be used for
1785 Also it's preferable to set the local-admin bit. Following shell code
1786 generates a random mac-address as described above::
1798 is 65535, but system can take the value from 1 - 65535. Following shell
1804 (c) ad_user_port_key : Use the user portion of the port-key. The default
1805 keeps this empty. These are the upper 10 bits of the port-key and value
1806 ranges from 0 - 1023. Following shell code generates these 10 bits and
1817 -------------------------
1819 Each bonding device has a read-only file residing in the
1824 driver is loaded with parameters of mode=0 and miimon=1000 is
1828 Bonding Mode: load balancing (round-robin)
1847 -------------------------
1881 5. Switch Configuration
1884 For this section, "switch" refers to whatever system the
1886 the cable plugs into). This may be an actual dedicated switch device,
1890 The active-backup, balance-tlb and balance-alb modes do not
1891 require any specific configuration of the switch.
1893 The 802.3ad mode requires that the switch have the appropriate
1895 to configure this varies from switch to switch, but, for example, a
1896 Cisco 3550 series switch requires that the appropriate ports first be
1898 etherchannel is set to mode "lacp" to enable 802.3ad (instead of
1901 The balance-rr, balance-xor and broadcast modes generally
1902 require that the switch have the appropriate ports grouped together.
1905 group" or some other similar variation. For these modes, each switch
1906 will also have its own configuration options for the switch's transmit
1909 match. For these three modes, the bonding mode really selects a
1921 packets generated by either ALB mode or the ARP monitor mechanism, are
1933 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1940 would pick up the all-zeroes hardware address. Once the first slave
1961 underlying device -- i.e. the bonding interface -- to promiscuous
1962 mode, which might not be what you want.
1977 -------------------------
1986 ------------------------------------
2009 -------------------------
2038 -------------------------
2073 ----------------------------
2084 options bond0 mode=some-mode miimon=50
2117 ---------------------------------------------------------
2141 beyond other ports of a switch, or if a switch is refusing to pass
2192 10. Promiscuous mode
2196 common to enable promiscuous mode on the device, so that all traffic
2198 The bonding driver handles promiscuous mode changes to the bonding
2202 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2203 the promiscuous mode setting is propagated to all slaves.
2205 For the active-backup, balance-tlb and balance-alb modes, the
2206 promiscuous mode setting is propagated only to the active slave.
2208 For balance-tlb mode, the active slave is the slave currently
2211 For balance-alb mode, the active slave is the slave used as a
2212 "primary." This slave is used for mode-specific control traffic, for
2215 For the active-backup, balance-tlb and balance-alb modes, when
2229 11.1 High Availability in a Single Switch Topology
2230 --------------------------------------------------
2232 If two hosts (or a host and a single switch) are directly
2235 only one switch (or peer), so if it fails, there is no alternative
2243 11.2 High Availability in a Multiple Switch Topology
2244 ----------------------------------------------------
2247 network changes dramatically. In multiple switch topologies, there is
2255 +-----+----+ +-----+----+
2257 | switch A +--------------------------+ switch B |
2259 +-----+----+ +-----++---+
2261 | +-------+ |
2262 +-------------+ host1 +---------------+
2263 eth0 +-------+ eth1
2266 switches (ISL, or inter switch link), and multiple ports connecting to
2267 the outside world ("port3" on each switch). There is no technical
2268 reason that this could not be extended to a third switch.
2270 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
2271 -------------------------------------------------------------
2273 In a topology such as the example above, the active-backup and
2278 active-backup:
2279 This is generally the preferred mode, particularly if
2281 network configuration is such that one switch is specifically
2282 a backup switch (e.g., has lower capacity, higher cost, etc),
2287 This mode is really a special purpose mode, and is suitable
2291 necessary for some specific one-way traffic to reach both
2292 independent networks, then the broadcast mode may be suitable.
2294 11.2.2 HA Link Monitoring Selection for Multiple Switch Topology
2295 ----------------------------------------------------------------
2298 switch. If the switch can reliably fail ports in response to other
2303 thus detecting that failure without switch support.
2305 In general, however, in a multiple switch topology, the ARP
2310 one for each switch in the network). This will insure that,
2311 regardless of which switch is active, the ARP monitor has a suitable
2316 switch that causes the link state of a particular switch port to be set
2317 down (or up) when the state of another switch port goes down (or up).
2321 switch, but this can be a viable alternative to the ARP monitor when using
2327 12.1 Maximizing Throughput in a Single Switch Topology
2328 ------------------------------------------------------
2330 In a single switch configuration, the best method to maximize
2339 In a gatewayed configuration, the "switch" is acting primarily
2344 +----------+ +----------+
2346 | Host A +---------------------+ router +------------------->
2347 | +---------------------+ | Hosts B and C are out
2349 +----------+ +----------+
2366 In a local configuration, the "switch" is acting primarily as
2367 a switch, and the majority of traffic passes through this switch to
2371 +----------+ +----------+ +--------+
2372 | |eth0 port1| +-------+ Host B |
2373 | Host A +------------+ switch |port3 +--------+
2374 | +------------+ | +--------+
2375 | |eth1 port2| +------------------+ Host C |
2376 +----------+ +----------+port4 +--------+
2379 Again, the switch may be a dedicated switch device, or another
2395 mode is described below.
2398 12.1.1 MT Bonding Mode Selection for Single Switch Topology
2399 -----------------------------------------------------------
2402 although you will have to decide which bonding mode best suits your
2403 needs. The trade offs for each mode are detailed below:
2405 balance-rr:
2406 This mode is the only mode that will permit a single
2408 interfaces. It is therefore the only mode that will allow a
2423 networking interfaces, the switch, and the topology of the
2432 through the switch to a balance-rr bond will not utilize greater
2437 delivery, then this mode can allow for single stream datagram
2441 This mode requires the switch to have the appropriate ports
2444 active-backup:
2446 the active-backup mode, as the inactive backup devices are all
2448 load balancing mode (with link monitoring) will provide the
2450 available bandwidth. On the plus side, active-backup mode
2451 does not require any configuration of the switch, so it may
2455 balance-xor:
2456 This mode will limit traffic such that packets destined
2459 addresses involved, this mode works best in a "local" network
2461 the same local network. This mode is likely to be suboptimal
2465 As with balance-rr, the switch ports need to be configured for
2469 Like active-backup, there is not much advantage to this
2470 mode in this type of network topology.
2473 This mode can be a good choice for this type of network
2474 topology. The 802.3ad mode is an IEEE standard, so all peers
2477 so minimal manual configuration of the switch is needed
2482 packets. The 802.3ad mode does have some drawbacks: the
2485 balance modes other than balance-rr, no single connection will
2498 Finally, the 802.3ad mode mandates the use of the MII monitor,
2499 therefore, the ARP monitor is not available in this mode.
2501 balance-tlb:
2502 The balance-tlb mode balances outgoing traffic by peer.
2504 "gatewayed" configuration (as described above), this mode will
2506 "local" network configuration, this mode balances multiple
2508 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2514 special switch configuration is required. On the down side,
2515 in this mode all incoming traffic arrives over a single
2516 interface, this mode requires certain ethtool support in the
2520 balance-alb:
2521 This mode is everything that balance-tlb is, and more.
2522 It has all of the features (and restrictions) of balance-tlb,
2527 The only additional down side to this mode is that the network
2531 12.1.2 MT Link Monitoring for Single Switch Topology
2532 ----------------------------------------------------
2535 mode you choose to use. The more advanced load balancing modes do not
2540 12.2 Maximum Throughput in a Multiple Switch Topology
2541 -----------------------------------------------------
2547 +-----------+
2549 +-+---+---+-+
2551 +--------+ | +---------+
2553 +------+---+ +-----+----+ +-----+----+
2554 | Switch A | | Switch B | | Switch C |
2555 +------+---+ +-----+----+ +-----+----+
2557 +--------+ | +---------+
2559 +-+---+---+-+
2561 +-----------+
2567 cost effective than a single larger switch, e.g., on a network with 24
2569 a single 72 port switch.
2575 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
2576 -------------------------------------------------------------
2578 In actual practice, the bonding mode typically employed in
2579 configurations of this type is balance-rr. Historically, in this
2584 packets has arrived). When employed in this fashion, the balance-rr
2585 mode allows individual connections between two hosts to effectively
2588 12.2.2 MT Link Monitoring for Multiple Switch Topology
2589 ------------------------------------------------------
2598 13. Switch Behavior Issues
2602 -------------------------------------------
2605 timing of link up and down reporting by the switch.
2611 during switch initialization (e.g., during recovery after a switch
2618 the switch is initializing. Again, an appropriate updelay value may
2631 In addition to the concerns about switch timings, if your
2632 switches take a long time to go into backup mode, it may be desirable
2637 --------------------------------
2649 For example, on a bond in active-backup mode with five slaves
2650 all connected to one switch, the output may appear as follows::
2652 # ping -n 10.0.4.2
2665 tables. Initially, the switch does not associate the MAC address in
2666 the packet with a particular switch port, and so it may send the
2669 single switch, when the switch (temporarily) floods the traffic to all
2673 The duplicated packet behavior is switch dependent, some
2676 most Cisco switches, the privileged command "clear mac address-table
2687 --------------------
2692 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2697 --------------------------------
2700 integrated on the planar (that's "motherboard" in IBM-speak). In the
2703 An add-on Broadcom daughter card can be installed on a JS20 to provide
2707 Each I/O Module may contain either a switch or a passthrough
2709 switch). Some bonding modes require a specific BladeCenter internal
2712 Additional BladeCenter-specific networking information can be
2715 - "IBM eServer BladeCenter Networking Options"
2716 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2719 ------------------------------------
2725 Normally, Ethernet Switch Modules (ESMs) are used in I/O
2732 switch. By using PMs in I/O module #1 and #2, the eth0 and eth1
2734 connected to a common external switch.
2737 appear to bonding as either a single switch topology (all PMs) or as a
2738 multiple switch topology (one or more ESMs, zero or more PMs). It is
2740 much like the example in "High Availability in a Multiple Switch
2744 -------------------------------
2746 The balance-rr mode requires the use of passthrough modules
2747 for devices in the bond, all connected to an common external switch.
2748 That switch must be configured for "etherchannel" or "trunking" on the
2749 appropriate ports, as is usual for balance-rr.
2751 The balance-alb and balance-tlb modes will function with
2752 either switch modules or passthrough modules (or a mix). The only
2758 The active-backup mode has no additional requirements.
2761 ----------------------
2763 When an Ethernet Switch Module is in place, only the ARP
2764 monitor will reliably detect link loss to an external switch. This is
2767 the system, when it fact there is a switch between these "external"
2776 --------------
2784 It may be desirable to disable spanning tree on the switch
2785 (either the internal Ethernet Switch Module, or an external switch) to
2786 avoid fail-over delay issues when using bonding.
2793 -------------------
2799 -----------------------------------------
2801 Any Ethernet type cards (you can even mix cards - a Intel
2806 slaves in active-backup mode.
2809 ----------------------------------------
2814 ----------------------------------------------
2821 ----------------------------------------
2824 disabled. The active-backup mode will fail over to a backup link, and
2827 manner is appropriate for the mode). See the sections on High
2828 Availability and the documentation for each mode for additional
2841 depends upon the bonding mode and network configuration.
2844 ----------------------------------------------
2849 ---------------------------------------------
2851 The full answer to this depends upon the desired mode.
2853 In the basic balance modes (balance-rr and balance-xor), it
2858 The advanced balance modes (balance-tlb and balance-alb) do
2859 not have special switch requirements, but do need device drivers that
2863 In 802.3ad mode, it works with systems that support IEEE
2867 The active-backup mode should work with any Layer-II switch.
2870 ---------------------------------------------------------
2892 # ifconfig bond0 down ; modprobe -r bonding
2900 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2922 http://vger.kernel.org/vger-lists.html#netdev