Lines Matching +full:primary +full:- +full:bond
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>
35 the original tools from extreme-linux and beowulf sites will not work
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
173 (active-backup, balance-alb and balance-tlb). Possible values
190 is 1 - 65535. If the value is not specified, it takes 65535 as the
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
201 use the MAC of the bond itself. It is preferred to have the
202 local-admin bit set for this mac but driver does not enforce it. If
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.
331 non-ARP traffic should be filtered (disregarded) for link
421 This option affects only active-backup mode for slaves with
445 The default value is 2, and the allowable range is 1 - 255.
453 IEEE 802.1AX-2008 5.4.15 in addition to the existing coupled control
457 and Distributing states, maintaining the bond in coupled control.
470 Specifies whether active-backup mode should set all slaves to
473 bond's MAC address in accordance with the selected policy.
480 bonding to set all slaves of an active-backup bond to
487 MAC address of the bond should always be the MAC
490 address of the bond changes during a failover.
515 address of the bond to be selected normally (normally
516 the MAC address of the first slave added to the bond).
519 slave is programmed with the bond's MAC address at
534 present in the bond.
587 asserting carrier. It is similar to the Cisco EtherChannel min-links
589 must be up (link-up state) before marking the bond device as up
604 balance-rr (round robin). Possible values are:
606 balance-rr or 0
608 Round-robin policy: Transmit packets in sequential
613 active-backup or 1
615 Active-backup policy: Only one slave in the bond is
617 if, the active slave fails. The bond's MAC address is
622 occurs in active-backup mode, bonding will issue one
630 This mode provides fault tolerance. The primary
634 balance-xor or 2
662 regards to the packet mis-ordering requirements of
678 balance-tlb or 5
700 balance-alb or 6
702 Adaptive load balancing: includes balance-tlb plus
709 address of one of the slaves in the bond such that
720 in the bond. A problematic outcome of using ARP
723 of the bond. Hence, peers learn the hardware address
724 of the bond and the balancing of receive traffic
729 redistributed when a new slave is added to the bond
730 and when an inactive slave is re-activated. The
732 among the group of highest speed slaves in the bond.
735 bond the receive traffic is redistributed among all
736 active slaves in the bond by initiating ARP Replies
751 team using the bond hardware address (the
753 address for each slave in the bond. If the
765 bonding device and each VLAN sub-device. This is repeated at
769 The valid range is 0 - 255; the default value is 1. These options
770 affect only the active-backup mode. These options were added for
783 The valid range is 0 - 65535; the default value is 1. This option
784 has effect only in balance-rr mode.
794 The valid range is 0 - 300000. The default value is 0, which means
799 The primary slave has the highest priority. This option also
803 for active-backup(1), balance-tlb (5) and balance-alb (6) mode.
808 primary
811 primary device. The specified device will always be the
812 active slave while it is available. Only when the primary is
813 off-line will alternate devices be used. This is useful when
817 The primary option is only valid for active-backup(1),
818 balance-tlb (5) and balance-alb (6) mode.
822 Specifies the reselection policy for the primary slave. This
823 affects how the primary slave is chosen to become the active slave
824 when failure of the active slave or recovery of the primary slave
825 occurs. This option is designed to prevent flip-flopping between
826 the primary slave and other slaves. Possible values are:
830 The primary slave becomes the active slave whenever it
835 The primary slave becomes the active slave when it comes
836 back up, if the speed and duplex of the primary slave is
842 The primary slave becomes the active slave only if the
843 current active slave fails and the primary slave is up.
850 When initially enslaved, the primary slave is always made
867 characteristics but can cause packet reordering. If re-ordering is
870 xmit-hash-policy can be used to select the appropriate hashing for
873 The sysfs entry can be used to change the setting per bond device
875 sysfs entry is allowed to be changed only if the bond device is
915 balance-xor, 802.3ad, and tlb modes. Possible values are:
948 network peer on the same slave. For non-IP traffic,
981 information is omitted. For non-IP traffic, the
1018 hash to load-balance traffic per-vlan, with failover
1019 should one leg fail. The intended use case is for a bond
1021 use their own vlan, to give lacp-like functionality
1022 without requiring lacp-capable switching hardware.
1039 The valid range is 0 - 255; the default value is 1. A value of 0
1043 This option is useful for bonding modes balance-rr (0), active-backup
1044 (1), balance-tlb (5) and balance-alb (6), in which a failover can
1056 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
1057 has effect only in balance-tlb and balance-alb modes.
1085 $ rpm -qf /sbin/ifup
1100 ----------------------------------------
1113 ifcfg-id file for each slave device. The simplest way to accomplish
1115 file ifcfg-id file created; see below for some issues with DHCP). The
1118 ifcfg-id-xx:xx:xx:xx:xx:xx
1123 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1133 _nm_name='bus-pci-0001:61:01.0'
1143 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1145 itself. This file is named ifcfg-bondX, where X is the number of the
1147 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1151 The contents of the ifcfg-bondX file is as follows::
1161 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1163 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1202 (bus-pci-0000:06:08.1 in the example above) specify the physical
1233 -------------------------------
1243 -----------------------------------------------
1247 bonding instance to have an appropriately configured ifcfg-bondX file
1251 ifcfg-bondX files.
1254 options in the ifcfg-bondX file, it is not necessary to add them to
1258 ------------------------------------------
1271 network-script file for all physical adapters that will be members of
1274 /etc/sysconfig/network-scripts
1276 The file name must be prefixed with "ifcfg-eth" and suffixed
1278 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1289 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1291 also depend on the final bonding interface name chosen for your bond.
1296 Next, create a bond network script. The file name for this
1297 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1298 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1299 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1316 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1319 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1321 will configure the bond with the specified options. The options
1342 options bond0 mode=balance-alb miimon=100
1348 will restart the networking subsystem and your bond link should be now
1352 ---------------------------------
1365 -------------------------------------------------
1369 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1370 number of the bond. This support requires sysfs support in the kernel,
1377 -----------------------------------------------
1391 For example, if you wanted to make a simple bond of two e100
1396 modprobe bonding mode=balance-alb miimon=100
1407 ifup and ifdown scripts on the bond devices. To reload the bonding
1419 enabled without re-running the entire global init script.
1435 -----------------------------------------
1464 options bond0 -o bond0 mode=balance-rr miimon=100
1467 options bond1 -o bond1 mode=balance-alb miimon=50
1470 named "bond0" and creates the bond0 device in balance-rr mode with an
1472 bond1 device in balance-alb mode with an miimon of 50.
1479 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1480 mode=balance-alb miimon=50
1486 to rename modules at load time (the "-o bond1" part). Attempts to pass
1494 ------------------------------------------
1514 -----------------------------
1515 To add a new bond foo::
1519 To remove an existing bond bar::
1521 # echo -bar > /sys/class/net/bonding_masters
1534 --------------------------
1535 Interfaces may be enslaved to a bond using the file
1536 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1539 To enslave interface eth0 to bond bond0::
1544 To free slave eth0 from bond bond0::
1546 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1548 When an interface is enslaved to a bond, symlinks between the
1555 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1556 will free eth0 from whatever bond it is enslaved to, regardless of
1557 the name of the bond interface.
1559 Changing a Bond's Configuration
1560 -------------------------------
1561 Each bond may be configured individually by manipulating the
1562 files located in /sys/class/net/<bond name>/bonding
1564 The names of these files correspond directly with the command-
1573 To configure bond0 for balance-alb mode::
1577 - or -
1578 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1582 The bond interface must be down before the mode can be changed.
1591 monitoring is enabled, and vice-versa.
1604 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1617 ---------------------
1621 To make a simple bond of two e100 devices (presumed to be eth0
1628 echo balance-alb > /sys/class/net/bond0/bonding/mode
1634 To add a second bond, with two e1000 interfaces in
1635 active-backup mode, using ARP monitoring, add the following lines to
1640 echo active-backup > /sys/class/net/bond1/bonding/mode
1648 -----------------------------------------
1655 the box. The ifenslave-2.6 package should be installed to provide bonding
1656 support. Once installed, this package will provide ``bond-*`` options
1659 Note that ifenslave-2.6 package will load the bonding module and use
1663 ----------------------
1666 active-backup mode, with eth0 and eth1 as slaves::
1670 bond-slaves eth0 eth1
1671 bond-mode active-backup
1672 bond-miimon 100
1673 bond-primary eth0 eth1
1682 bond-slaves none
1683 bond-mode active-backup
1684 bond-miimon 100
1688 bond-master bond0
1689 bond-primary eth0 eth1
1693 bond-master bond0
1694 bond-primary eth0 eth1
1696 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1698 /usr/share/doc/ifenslave-2.6.
1701 ----------------------------------------------
1710 connects via a public network, it may be desirous to bias the bond to send said
1724 Bonding Mode: fault-tolerance (active-backup)
1725 Primary Slave: None
1756 force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output
1774 slave devices as well as bond devices and the bonding driver will simply act as
1775 a pass-through for selecting output queues on the slave device rather than
1779 output slave selection was limited to round-robin and active-backup modes.
1782 ----------------------------------------------------------
1798 (a) ad_actor_system : You can set a random mac-address that can be used for
1800 Also it's preferable to set the local-admin bit. Following shell code
1801 generates a random mac-address as described above::
1813 is 65535, but system can take the value from 1 - 65535. Following shell
1819 (c) ad_user_port_key : Use the user portion of the port-key. The default
1820 keeps this empty. These are the upper 10 bits of the port-key and value
1821 ranges from 0 - 1023. Following shell code generates these 10 bits and
1832 -------------------------
1834 Each bonding device has a read-only file residing in the
1843 Bonding Mode: load balancing (round-robin)
1862 -------------------------
1905 The active-backup, balance-tlb and balance-alb modes do not
1916 The balance-rr, balance-xor and broadcast modes generally
1922 policy to the bond. Typical choices include XOR of either the MAC or
1932 It is possible to configure VLAN devices over a bond interface
1948 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1955 would pick up the all-zeroes hardware address. Once the first slave
1956 is attached to the bond, the bond device itself will pick up the
1960 are released from a bond that still has one or more VLAN interfaces on
1968 bond interface:
1976 underlying device -- i.e. the bonding interface -- to promiscuous
1992 -------------------------
2001 ------------------------------------
2024 -------------------------
2053 -------------------------
2088 ----------------------------
2099 options bond0 mode=some-mode miimon=50
2132 ---------------------------------------------------------
2163 before any network drivers participating in a bond. This requirement
2187 any network drivers participating in a bond. Below is an example of
2217 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2220 For the active-backup, balance-tlb and balance-alb modes, the
2223 For balance-tlb mode, the active slave is the slave currently
2226 For balance-alb mode, the active slave is the slave used as a
2227 "primary." This slave is used for mode-specific control traffic, for
2230 For the active-backup, balance-tlb and balance-alb modes, when
2245 --------------------------------------------------
2259 ----------------------------------------------------
2270 +-----+----+ +-----+----+
2272 | switch A +--------------------------+ switch B |
2274 +-----+----+ +-----++---+
2276 | +-------+ |
2277 +-------------+ host1 +---------------+
2278 eth0 +-------+ eth1
2286 -------------------------------------------------------------
2288 In a topology such as the example above, the active-backup and
2293 active-backup:
2298 then the primary option can be used to ensure that the
2306 necessary for some specific one-way traffic to reach both
2310 ----------------------------------------------------------------
2343 ------------------------------------------------------
2359 +----------+ +----------+
2361 | Host A +---------------------+ router +------------------->
2362 | +---------------------+ | Hosts B and C are out
2364 +----------+ +----------+
2386 +----------+ +----------+ +--------+
2387 | |eth0 port1| +-------+ Host B |
2388 | Host A +------------+ switch |port3 +--------+
2389 | +------------+ | +--------+
2390 | |eth1 port2| +------------------+ Host C |
2391 +----------+ +----------+port4 +--------+
2414 -----------------------------------------------------------
2420 balance-rr:
2447 through the switch to a balance-rr bond will not utilize greater
2454 to the bond.
2459 active-backup:
2461 the active-backup mode, as the inactive backup devices are all
2462 connected to the same peer as the primary. In this case, a
2465 available bandwidth. On the plus side, active-backup mode
2470 balance-xor:
2480 As with balance-rr, the switch ports need to be configured for
2484 Like active-backup, there is not much advantage to this
2500 balance modes other than balance-rr, no single connection will
2511 distributed across the devices in the bond.
2516 balance-tlb:
2517 The balance-tlb mode balances outgoing traffic by peer.
2523 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2535 balance-alb:
2536 This mode is everything that balance-tlb is, and more.
2537 It has all of the features (and restrictions) of balance-tlb,
2547 ----------------------------------------------------
2556 -----------------------------------------------------
2562 +-----------+
2564 +-+---+---+-+
2566 +--------+ | +---------+
2568 +------+---+ +-----+----+ +-----+----+
2570 +------+---+ +-----+----+ +-----+----+
2572 +--------+ | +---------+
2574 +-+---+---+-+
2576 +-----------+
2591 -------------------------------------------------------------
2594 configurations of this type is balance-rr. Historically, in this
2599 packets has arrived). When employed in this fashion, the balance-rr
2604 ------------------------------------------------------
2617 -------------------------------------------
2652 --------------------------------
2664 For example, on a bond in active-backup mode with five slaves
2667 # ping -n 10.0.4.2
2683 the interfaces attached to the bond may occupy multiple ports on a
2685 ports, the bond device receives multiple copies of the same packet
2691 most Cisco switches, the privileged command "clear mac address-table
2702 --------------------
2707 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2712 --------------------------------
2715 integrated on the planar (that's "motherboard" in IBM-speak). In the
2718 An add-on Broadcom daughter card can be installed on a JS20 to provide
2727 Additional BladeCenter-specific networking information can be
2730 - "IBM eServer BladeCenter Networking Options"
2731 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2734 ------------------------------------
2759 -------------------------------
2761 The balance-rr mode requires the use of passthrough modules
2762 for devices in the bond, all connected to an common external switch.
2764 appropriate ports, as is usual for balance-rr.
2766 The balance-alb and balance-tlb modes will function with
2773 The active-backup mode has no additional requirements.
2776 ----------------------
2791 --------------
2793 The Serial Over LAN (SoL) link is established over the primary
2801 avoid fail-over delay issues when using bonding.
2808 -------------------
2814 -----------------------------------------
2816 Any Ethernet type cards (you can even mix cards - a Intel
2821 slaves in active-backup mode.
2824 ----------------------------------------
2829 ----------------------------------------------
2836 ----------------------------------------
2839 disabled. The active-backup mode will fail over to a backup link, and
2841 monitored, and should it recover, it will rejoin the bond (in whatever
2859 ----------------------------------------------
2864 ---------------------------------------------
2868 In the basic balance modes (balance-rr and balance-xor), it
2873 The advanced balance modes (balance-tlb and balance-alb) do
2882 The active-backup mode should work with any Layer-II switch.
2885 ---------------------------------------------------------
2907 # ifconfig bond0 down ; modprobe -r bonding
2915 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2920 ------------------------------------------
2922 * balance-rr (0)
2923 * active-backup (1)
2924 * balance-xor (2)
2948 http://vger.kernel.org/vger-lists.html#netdev