Lines Matching +full:switch +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
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 multicast. It is preferred to have the local-admin bit set for this
205 This parameter has effect only in 802.3ad mode and is available through
229 - A slave is added to or removed from the bond
231 - Any slave's link state changes
233 - Any slave's 802.3ad association state changes
235 - The bond's administrative state changes to up
252 In an AD system, the port-key has three parts as shown below -
258 01-05 Speed
259 06-15 User-defined
263 from 0 - 1023. If not given, the system defaults to 0.
265 This parameter has effect only in 802.3ad mode and is available through
287 bonding mode, and the state of the slave). Regular traffic is
294 If ARP monitoring is used in an etherchannel compatible mode
295 (modes 0 and 2), the switch should be configured in a mode
297 switch is configured to distribute the packets in an XOR
318 validated in any mode that supports arp monitoring, or whether
319 non-ARP traffic should be filtered (disregarded) for link
365 active slave. It is possible that some switch or network
377 beyond a common switch. Should the link between the switch and
378 target fail (but not the switch itself), the probe traffic
409 This option affects only active-backup mode for slaves with
435 Specifies whether active-backup mode should set all slaves to
445 bonding to set all slaves of an active-backup bond to
464 vs. just updating a switch or set of switches (which
466 traffic, if the switch snoops incoming traffic to
507 to transmit LACPDU packets in 802.3ad mode. Possible values
539 asserting carrier. It is similar to the Cisco EtherChannel min-links
541 must be up (link-up state) before marking the bond device as up
545 mode.
548 802.3ad mode) whenever there is an active aggregator, regardless of the
553 mode
556 balance-rr (round robin). Possible values are:
558 balance-rr or 0
560 Round-robin policy: Transmit packets in sequential
562 last. This mode provides load balancing and fault
565 active-backup or 1
567 Active-backup policy: Only one slave in the bond is
571 to avoid confusing the switch.
574 occurs in active-backup mode, bonding will issue one
582 This mode provides fault tolerance. The primary
584 mode.
586 balance-xor or 2
595 This mode provides load balancing and fault tolerance.
600 interfaces. This mode provides fault tolerance.
614 regards to the packet mis-ordering requirements of
624 2. A switch that supports IEEE 802.3ad Dynamic link
628 to enable 802.3ad mode.
630 balance-tlb or 5
633 does not require any special switch support.
635 In tlb_dynamic_lb=1 mode; the outgoing traffic is
639 In tlb_dynamic_lb=0 mode; the load balancing based on
652 balance-alb or 6
654 Adaptive load balancing: includes balance-tlb plus
656 does not require any special switch support. The
682 and when an inactive slave is re-activated. The
691 be set to a value equal or greater than the switch's
693 peers will not be blocked by the switch.
717 bonding device and each VLAN sub-device. This is repeated at
721 The valid range is 0 - 255; the default value is 1. These options
722 affect only the active-backup mode. These options were added for
735 The valid range is 0 - 65535; the default value is 1. This option
736 has effect only in balance-rr mode.
753 off-line will alternate devices be used. This is useful when
757 The primary option is only valid for active-backup(1),
758 balance-tlb (5) and balance-alb (6) mode.
765 occurs. This option is designed to prevent flip-flopping between
803 mode. The value has no effect on any other modes.
805 The default behavior of tlb mode is to shuffle active flows across
807 characteristics but can cause packet reordering. If re-ordering is
810 xmit-hash-policy can be used to select the appropriate hashing for
855 balance-xor, 802.3ad, and tlb modes. Possible values are:
888 network peer on the same slave. For non-IP traffic,
920 information is omitted. For non-IP traffic, the
965 The valid range is 0 - 255; the default value is 1. A value of 0
969 This option is useful for bonding modes balance-rr (0), active-backup
970 (1), balance-tlb (5) and balance-alb (6), in which a failover can
971 switch the IGMP traffic from one slave to another. Therefore a fresh
972 IGMP report must be issued to cause the switch to forward the incoming
980 driver sends learning packets to each slaves peer switch.
982 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
983 has effect only in balance-tlb and balance-alb modes.
1011 $ rpm -qf /sbin/ifup
1026 ----------------------------------------
1039 ifcfg-id file for each slave device. The simplest way to accomplish
1041 file ifcfg-id file created; see below for some issues with DHCP). The
1044 ifcfg-id-xx:xx:xx:xx:xx:xx
1049 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1059 _nm_name='bus-pci-0001:61:01.0'
1069 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1071 itself. This file is named ifcfg-bondX, where X is the number of the
1073 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1077 The contents of the ifcfg-bondX file is as follows::
1087 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1089 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1118 for the bonding mode, link monitoring, and so on here. Do not include
1128 (bus-pci-0000:06:08.1 in the example above) specify the physical
1159 -------------------------------
1169 -----------------------------------------------
1173 bonding instance to have an appropriately configured ifcfg-bondX file
1177 ifcfg-bondX files.
1180 options in the ifcfg-bondX file, it is not necessary to add them to
1184 ------------------------------------------
1197 network-script file for all physical adapters that will be members of
1200 /etc/sysconfig/network-scripts
1202 The file name must be prefixed with "ifcfg-eth" and suffixed
1204 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1215 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1223 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1224 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1225 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1242 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1245 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1268 options bond0 mode=balance-alb miimon=100
1278 ---------------------------------
1291 -------------------------------------------------
1295 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1303 -----------------------------------------------
1322 modprobe bonding mode=balance-alb miimon=100
1345 enabled without re-running the entire global init script.
1361 -----------------------------------------
1390 options bond0 -o bond0 mode=balance-rr miimon=100
1393 options bond1 -o bond1 mode=balance-alb miimon=50
1396 named "bond0" and creates the bond0 device in balance-rr mode with an
1398 bond1 device in balance-alb mode with an miimon of 50.
1405 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1406 mode=balance-alb miimon=50
1412 to rename modules at load time (the "-o bond1" part). Attempts to pass
1420 ------------------------------------------
1440 -----------------------------
1447 # echo -bar > /sys/class/net/bonding_masters
1460 --------------------------
1472 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1481 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1486 -------------------------------
1490 The names of these files correspond directly with the command-
1499 To configure bond0 for balance-alb mode::
1502 # echo 6 > /sys/class/net/bond0/bonding/mode
1503 - or -
1504 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1508 The bond interface must be down before the mode can be changed.
1517 monitoring is enabled, and vice-versa.
1530 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1539 the bonding driver sends learning packets to each slaves peer switch. The
1543 ---------------------
1554 echo balance-alb > /sys/class/net/bond0/bonding/mode
1561 active-backup mode, using ARP monitoring, add the following lines to
1566 echo active-backup > /sys/class/net/bond1/bonding/mode
1574 -----------------------------------------
1581 the box. The ifenslave-2.6 package should be installed to provide bonding
1582 support. Once installed, this package will provide ``bond-*`` options
1585 Note that ifenslave-2.6 package will load the bonding module and use
1589 ----------------------
1592 active-backup mode, with eth0 and eth1 as slaves::
1596 bond-slaves eth0 eth1
1597 bond-mode active-backup
1598 bond-miimon 100
1599 bond-primary eth0 eth1
1608 bond-slaves none
1609 bond-mode active-backup
1610 bond-miimon 100
1614 bond-master bond0
1615 bond-primary eth0 eth1
1619 bond-master bond0
1620 bond-primary eth0 eth1
1622 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1624 /usr/share/doc/ifenslave-2.6.
1627 ----------------------------------------------
1632 the selected bonding mode. On occasion however, it is helpful to direct certain
1650 Bonding Mode: fault-tolerance (active-backup)
1701 a pass-through for selecting output queues on the slave device rather than
1705 output slave selection was limited to round-robin and active-backup modes.
1707 3.7 Configuring LACP for 802.3ad mode in a more secure way
1708 ----------------------------------------------------------
1710 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1716 domain can spoof LACPDU packets from other hosts to the switch and potentially
1717 cause mayhem by joining (from the point of view of the switch) another
1724 (a) ad_actor_system : You can set a random mac-address that can be used for
1726 Also it's preferable to set the local-admin bit. Following shell code
1727 generates a random mac-address as described above::
1739 is 65535, but system can take the value from 1 - 65535. Following shell
1745 (c) ad_user_port_key : Use the user portion of the port-key. The default
1746 keeps this empty. These are the upper 10 bits of the port-key and value
1747 ranges from 0 - 1023. Following shell code generates these 10 bits and
1758 -------------------------
1760 Each bonding device has a read-only file residing in the
1765 driver is loaded with parameters of mode=0 and miimon=1000 is
1769 Bonding Mode: load balancing (round-robin)
1788 -------------------------
1822 5. Switch Configuration
1825 For this section, "switch" refers to whatever system the
1827 the cable plugs into). This may be an actual dedicated switch device,
1831 The active-backup, balance-tlb and balance-alb modes do not
1832 require any specific configuration of the switch.
1834 The 802.3ad mode requires that the switch have the appropriate
1836 to configure this varies from switch to switch, but, for example, a
1837 Cisco 3550 series switch requires that the appropriate ports first be
1839 etherchannel is set to mode "lacp" to enable 802.3ad (instead of
1842 The balance-rr, balance-xor and broadcast modes generally
1843 require that the switch have the appropriate ports grouped together.
1846 group" or some other similar variation. For these modes, each switch
1847 will also have its own configuration options for the switch's transmit
1850 match. For these three modes, the bonding mode really selects a
1862 packets generated by either ALB mode or the ARP monitor mechanism, are
1874 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1881 would pick up the all-zeroes hardware address. Once the first slave
1902 underlying device -- i.e. the bonding interface -- to promiscuous
1903 mode, which might not be what you want.
1918 -------------------------
1928 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1929 flag must also update netdev_queue->trans_start. If they do not, then the
1936 ------------------------------------
1959 -------------------------
1988 -------------------------
2023 ----------------------------
2034 options bond0 mode=some-mode miimon=50
2067 ---------------------------------------------------------
2091 beyond other ports of a switch, or if a switch is refusing to pass
2142 10. Promiscuous mode
2146 common to enable promiscuous mode on the device, so that all traffic
2148 The bonding driver handles promiscuous mode changes to the bonding
2152 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2153 the promiscuous mode setting is propagated to all slaves.
2155 For the active-backup, balance-tlb and balance-alb modes, the
2156 promiscuous mode setting is propagated only to the active slave.
2158 For balance-tlb mode, the active slave is the slave currently
2161 For balance-alb mode, the active slave is the slave used as a
2162 "primary." This slave is used for mode-specific control traffic, for
2165 For the active-backup, balance-tlb and balance-alb modes, when
2179 11.1 High Availability in a Single Switch Topology
2180 --------------------------------------------------
2182 If two hosts (or a host and a single switch) are directly
2185 only one switch (or peer), so if it fails, there is no alternative
2193 11.2 High Availability in a Multiple Switch Topology
2194 ----------------------------------------------------
2197 network changes dramatically. In multiple switch topologies, there is
2205 +-----+----+ +-----+----+
2207 | switch A +--------------------------+ switch B |
2209 +-----+----+ +-----++---+
2211 | +-------+ |
2212 +-------------+ host1 +---------------+
2213 eth0 +-------+ eth1
2216 switches (ISL, or inter switch link), and multiple ports connecting to
2217 the outside world ("port3" on each switch). There is no technical
2218 reason that this could not be extended to a third switch.
2220 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
2221 -------------------------------------------------------------
2223 In a topology such as the example above, the active-backup and
2228 active-backup:
2229 This is generally the preferred mode, particularly if
2231 network configuration is such that one switch is specifically
2232 a backup switch (e.g., has lower capacity, higher cost, etc),
2237 This mode is really a special purpose mode, and is suitable
2241 necessary for some specific one-way traffic to reach both
2242 independent networks, then the broadcast mode may be suitable.
2244 11.2.2 HA Link Monitoring Selection for Multiple Switch Topology
2245 ----------------------------------------------------------------
2248 switch. If the switch can reliably fail ports in response to other
2253 thus detecting that failure without switch support.
2255 In general, however, in a multiple switch topology, the ARP
2260 one for each switch in the network). This will insure that,
2261 regardless of which switch is active, the ARP monitor has a suitable
2266 switch that causes the link state of a particular switch port to be set
2267 down (or up) when the state of another switch port goes down (or up).
2271 switch, but this can be a viable alternative to the ARP monitor when using
2277 12.1 Maximizing Throughput in a Single Switch Topology
2278 ------------------------------------------------------
2280 In a single switch configuration, the best method to maximize
2289 In a gatewayed configuration, the "switch" is acting primarily
2294 +----------+ +----------+
2296 | Host A +---------------------+ router +------------------->
2297 | +---------------------+ | Hosts B and C are out
2299 +----------+ +----------+
2316 In a local configuration, the "switch" is acting primarily as
2317 a switch, and the majority of traffic passes through this switch to
2321 +----------+ +----------+ +--------+
2322 | |eth0 port1| +-------+ Host B |
2323 | Host A +------------+ switch |port3 +--------+
2324 | +------------+ | +--------+
2325 | |eth1 port2| +------------------+ Host C |
2326 +----------+ +----------+port4 +--------+
2329 Again, the switch may be a dedicated switch device, or another
2345 mode is described below.
2348 12.1.1 MT Bonding Mode Selection for Single Switch Topology
2349 -----------------------------------------------------------
2352 although you will have to decide which bonding mode best suits your
2353 needs. The trade offs for each mode are detailed below:
2355 balance-rr:
2356 This mode is the only mode that will permit a single
2358 interfaces. It is therefore the only mode that will allow a
2373 networking interfaces, the switch, and the topology of the
2382 through the switch to a balance-rr bond will not utilize greater
2387 delivery, then this mode can allow for single stream datagram
2391 This mode requires the switch to have the appropriate ports
2394 active-backup:
2396 the active-backup mode, as the inactive backup devices are all
2398 load balancing mode (with link monitoring) will provide the
2400 available bandwidth. On the plus side, active-backup mode
2401 does not require any configuration of the switch, so it may
2405 balance-xor:
2406 This mode will limit traffic such that packets destined
2409 addresses involved, this mode works best in a "local" network
2411 the same local network. This mode is likely to be suboptimal
2415 As with balance-rr, the switch ports need to be configured for
2419 Like active-backup, there is not much advantage to this
2420 mode in this type of network topology.
2423 This mode can be a good choice for this type of network
2424 topology. The 802.3ad mode is an IEEE standard, so all peers
2427 so minimal manual configuration of the switch is needed
2432 packets. The 802.3ad mode does have some drawbacks: the
2435 balance modes other than balance-rr, no single connection will
2448 Finally, the 802.3ad mode mandates the use of the MII monitor,
2449 therefore, the ARP monitor is not available in this mode.
2451 balance-tlb:
2452 The balance-tlb mode balances outgoing traffic by peer.
2454 "gatewayed" configuration (as described above), this mode will
2456 "local" network configuration, this mode balances multiple
2458 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2464 special switch configuration is required. On the down side,
2465 in this mode all incoming traffic arrives over a single
2466 interface, this mode requires certain ethtool support in the
2470 balance-alb:
2471 This mode is everything that balance-tlb is, and more.
2472 It has all of the features (and restrictions) of balance-tlb,
2477 The only additional down side to this mode is that the network
2481 12.1.2 MT Link Monitoring for Single Switch Topology
2482 ----------------------------------------------------
2485 mode you choose to use. The more advanced load balancing modes do not
2490 12.2 Maximum Throughput in a Multiple Switch Topology
2491 -----------------------------------------------------
2497 +-----------+
2499 +-+---+---+-+
2501 +--------+ | +---------+
2503 +------+---+ +-----+----+ +-----+----+
2504 | Switch A | | Switch B | | Switch C |
2505 +------+---+ +-----+----+ +-----+----+
2507 +--------+ | +---------+
2509 +-+---+---+-+
2511 +-----------+
2517 cost effective than a single larger switch, e.g., on a network with 24
2519 a single 72 port switch.
2525 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
2526 -------------------------------------------------------------
2528 In actual practice, the bonding mode typically employed in
2529 configurations of this type is balance-rr. Historically, in this
2534 packets has arrived). When employed in this fashion, the balance-rr
2535 mode allows individual connections between two hosts to effectively
2538 12.2.2 MT Link Monitoring for Multiple Switch Topology
2539 ------------------------------------------------------
2548 13. Switch Behavior Issues
2552 -------------------------------------------
2555 timing of link up and down reporting by the switch.
2561 during switch initialization (e.g., during recovery after a switch
2568 the switch is initializing. Again, an appropriate updelay value may
2581 In addition to the concerns about switch timings, if your
2582 switches take a long time to go into backup mode, it may be desirable
2587 --------------------------------
2599 For example, on a bond in active-backup mode with five slaves
2600 all connected to one switch, the output may appear as follows::
2602 # ping -n 10.0.4.2
2615 tables. Initially, the switch does not associate the MAC address in
2616 the packet with a particular switch port, and so it may send the
2619 single switch, when the switch (temporarily) floods the traffic to all
2623 The duplicated packet behavior is switch dependent, some
2626 most Cisco switches, the privileged command "clear mac address-table
2637 --------------------
2642 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2647 --------------------------------
2650 integrated on the planar (that's "motherboard" in IBM-speak). In the
2653 An add-on Broadcom daughter card can be installed on a JS20 to provide
2657 Each I/O Module may contain either a switch or a passthrough
2659 switch). Some bonding modes require a specific BladeCenter internal
2662 Additional BladeCenter-specific networking information can be
2665 - "IBM eServer BladeCenter Networking Options"
2666 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2669 ------------------------------------
2675 Normally, Ethernet Switch Modules (ESMs) are used in I/O
2682 switch. By using PMs in I/O module #1 and #2, the eth0 and eth1
2684 connected to a common external switch.
2687 appear to bonding as either a single switch topology (all PMs) or as a
2688 multiple switch topology (one or more ESMs, zero or more PMs). It is
2690 much like the example in "High Availability in a Multiple Switch
2694 -------------------------------
2696 The balance-rr mode requires the use of passthrough modules
2697 for devices in the bond, all connected to an common external switch.
2698 That switch must be configured for "etherchannel" or "trunking" on the
2699 appropriate ports, as is usual for balance-rr.
2701 The balance-alb and balance-tlb modes will function with
2702 either switch modules or passthrough modules (or a mix). The only
2708 The active-backup mode has no additional requirements.
2711 ----------------------
2713 When an Ethernet Switch Module is in place, only the ARP
2714 monitor will reliably detect link loss to an external switch. This is
2717 the system, when it fact there is a switch between these "external"
2726 --------------
2734 It may be desirable to disable spanning tree on the switch
2735 (either the internal Ethernet Switch Module, or an external switch) to
2736 avoid fail-over delay issues when using bonding.
2743 -------------------
2749 -----------------------------------------
2751 Any Ethernet type cards (you can even mix cards - a Intel
2756 slaves in active-backup mode.
2759 ----------------------------------------
2764 ----------------------------------------------
2771 ----------------------------------------
2774 disabled. The active-backup mode will fail over to a backup link, and
2777 manner is appropriate for the mode). See the sections on High
2778 Availability and the documentation for each mode for additional
2791 depends upon the bonding mode and network configuration.
2794 ----------------------------------------------
2799 ---------------------------------------------
2801 The full answer to this depends upon the desired mode.
2803 In the basic balance modes (balance-rr and balance-xor), it
2808 The advanced balance modes (balance-tlb and balance-alb) do
2809 not have special switch requirements, but do need device drivers that
2813 In 802.3ad mode, it works with systems that support IEEE
2817 The active-backup mode should work with any Layer-II switch.
2820 ---------------------------------------------------------
2842 # ifconfig bond0 down ; modprobe -r bonding
2850 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2872 http://vger.kernel.org/vger-lists.html#netdev