Lines Matching +full:single +full:- +full:link
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>
28 multiple network interfaces into a single logical "bonded" interface.
31 Additionally, link integrity monitoring may be performed.
35 the original tools from extreme-linux and beowulf sites will not work
69 7. Link Monitoring
77 8.3 Painfully Slow Or No Failed Link Detection By Miimon
84 11.1 High Availability in a Single 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
95 12.2.2 MT Link Monitoring for Multiple Switch Topology
98 13.1 Link Establishment and Failover Delays
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
161 degradation will occur during link failures. Very few devices do not
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
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
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.
283 Specifies the ARP link monitoring frequency in milliseconds.
300 the same link which could cause the other team members to
309 sent to determine the health of the link to the targets.
320 non-ARP traffic should be filtered (disregarded) for link
378 beyond a common switch. Should the link between the switch and
389 packets for link availability purposes. Arriving packets that are
395 determining if a slave has received traffic for link availability
402 link availability purposes.
410 This option affects only active-backup mode for slaves with
428 a slave after a link failure has been detected. This option
429 is only valid for the miimon link monitor. The downdelay
436 Specifies whether active-backup mode should set all slaves to
446 bonding to set all slaves of an active-backup bond to
473 monitor, devices which assert link up prior to being
507 Option specifying the rate in which we'll ask our link partner
529 Specifies the MII link monitoring frequency in milliseconds.
530 This determines how often the link state of each slave is
531 inspected for link failures. A value of zero disables MII
532 link monitoring. A value of 100 is a good starting point.
533 The use_carrier option, below, affects how the link state 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
551 aggregator cannot be active without at least one available link,
557 balance-rr (round robin). Possible values are:
559 balance-rr or 0
561 Round-robin policy: Transmit packets in sequential
566 active-backup or 1
568 Active-backup policy: Only one slave in the bond is
575 occurs in active-backup mode, bonding will issue one
587 balance-xor or 2
605 IEEE 802.3ad Dynamic link aggregation. Creates
615 regards to the packet mis-ordering requirements of
625 2. A switch that supports IEEE 802.3ad Dynamic link
631 balance-tlb or 5
653 balance-alb or 6
655 Adaptive load balancing: includes balance-tlb plus
683 and when an inactive slave is re-activated. The
687 When a link is reconnected or a new slave joins 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
736 The valid range is 0 - 65535; the default value is 1. This option
737 has effect only in balance-rr mode.
744 This delay should be a multiple of the link monitor interval
746 value is 0 which means to match the value of the link monitor
754 off-line will alternate devices be used. This is useful when
758 The primary option is only valid for active-backup(1),
759 balance-tlb (5) and balance-alb (6) mode.
766 occurs. This option is designed to prevent flip-flopping between
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
827 only valid for the miimon link monitor. The updelay value
834 ioctls vs. netif_carrier_ok() to determine the link
841 If bonding insists that the link is up when it should not be,
845 it will appear as if the link is always up. In this case,
847 MII / ETHTOOL ioctl method to determine the link state.
856 balance-xor, 802.3ad, and tlb modes. Possible values are:
889 network peer on the same slave. For non-IP traffic,
905 slaves, although a single connection will not span
921 information is omitted. For non-IP traffic, the
926 single TCP or UDP conversation containing both
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
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 ----------------------------------------
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
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
1129 (bus-pci-0000:06:08.1 in the example above) specify the physical
1160 -------------------------------
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
1199 a bondX link. Network script files are located in the directory:
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.
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
1275 will restart the networking subsystem and your bond link should be now
1279 ---------------------------------
1292 -------------------------------------------------
1296 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1304 -----------------------------------------------
1314 `ip link` commands to the system's global init script. The name of
1323 modprobe bonding mode=balance-alb miimon=100
1326 ip link set eth0 master bond0
1327 ip link set eth1 master bond0
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 --------------------------
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::
1504 - or -
1505 # echo balance-alb > /sys/class/net/bond0/bonding/mode
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 ----------------------------------------------
1651 Bonding Mode: fault-tolerance (active-backup)
1661 Link Failure Count: 0
1667 Link Failure Count: 0
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.
1709 ----------------------------------------------------------
1713 destined to link local mac addresses (which switches/bridges are not
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
1770 Bonding Mode: load balancing (round-robin)
1779 Link Failure Count: 1
1783 Link Failure Count: 1
1789 -------------------------
1802 bond0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1809 eth0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1816 eth1 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1832 The active-backup, balance-tlb and balance-alb modes do not
1839 grouped together in a single etherchannel instance, then that
1843 The balance-rr, balance-xor and broadcast modes generally
1875 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1882 would pick up the all-zeroes hardware address. Once the first slave
1903 underlying device -- i.e. the bonding interface -- to promiscuous
1907 7. Link Monitoring
1911 monitoring a slave device's link state: the ARP monitor and the MII
1919 -------------------------
1923 uses the response as an indication that the link is operating. This
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 ------------------------------------
1952 For just a single target the options would resemble::
1960 -------------------------
1977 device's (via ioctl) MII registers and check the link state. If that
1982 and ethtool requests), then the MII monitor will assume the link is
1989 -------------------------
2024 ----------------------------
2035 options bond0 mode=some-mode miimon=50
2067 8.3. Painfully Slow Or No Failed Link Detection By Miimon
2068 ---------------------------------------------------------
2074 not support the netif_carrier_on/_off link state tracking system.
2079 not maintain it in real time, e.g., only polling the link state at
2082 miimon is very slow in detecting link failures, try specifying
2153 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2156 For the active-backup, balance-tlb and balance-alb modes, the
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
2180 11.1 High Availability in a Single Switch Topology
2181 --------------------------------------------------
2183 If two hosts (or a host and a single switch) are directly
2188 support link monitoring of their members, so if individual links fail,
2195 ----------------------------------------------------
2206 +-----+----+ +-----+----+
2208 | switch A +--------------------------+ switch B |
2210 +-----+----+ +-----++---+
2212 | +-------+ |
2213 +-------------+ host1 +---------------+
2214 eth0 +-------+ eth1
2216 In this configuration, there is a link between the two
2217 switches (ISL, or inter switch link), and multiple ports connecting to
2222 -------------------------------------------------------------
2224 In a topology such as the example above, the active-backup and
2229 active-backup:
2235 preferred link is always used when it is available.
2242 necessary for some specific one-way traffic to reach both
2245 11.2.2 HA Link Monitoring Selection for Multiple Switch Topology
2246 ----------------------------------------------------------------
2248 The choice of link monitoring ultimately depends upon your
2251 example, in the above example, if the "port3" link fails at the remote
2267 switch that causes the link state of a particular switch port to be set
2269 Its purpose is to propagate link failures from logically "exterior" ports
2278 12.1 Maximizing Throughput in a Single Switch Topology
2279 ------------------------------------------------------
2281 In a single switch configuration, the best method to maximize
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 +--------+
2349 12.1.1 MT Bonding Mode Selection for Single Switch Topology
2350 -----------------------------------------------------------
2356 balance-rr:
2357 This mode is the only mode that will permit a single
2360 single TCP/IP stream to utilize more than one interface's
2383 through the switch to a balance-rr bond will not utilize greater
2388 delivery, then this mode can allow for single stream datagram
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:
2413 if all your traffic is passed through a single router (i.e., a
2416 As with balance-rr, the switch ports need to be configured for
2420 Like active-backup, there is not much advantage to this
2432 in general single connections will not see misordering of
2436 balance modes other than balance-rr, no single connection will
2437 be able to utilize more than a single interface's worth of
2444 traffic may also end up on a single device, but that is
2452 balance-tlb:
2453 The balance-tlb mode balances outgoing traffic by peer.
2456 send all traffic across a single device. However, in a
2459 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2461 XOR to the same value) will not all "bunch up" on a single
2466 in this mode all incoming traffic arrives over a single
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,
2482 12.1.2 MT Link Monitoring for Single Switch Topology
2483 ----------------------------------------------------
2485 The choice of link monitoring may largely depend upon which
2492 -----------------------------------------------------
2498 +-----------+
2500 +-+---+---+-+
2502 +--------+ | +---------+
2504 +------+---+ +-----+----+ +-----+----+
2506 +------+---+ +-----+----+ +-----+----+
2508 +--------+ | +---------+
2510 +-+---+---+-+
2512 +-----------+
2518 cost effective than a single larger switch, e.g., on a network with 24
2520 a single 72 port switch.
2527 -------------------------------------------------------------
2530 configurations of this type is balance-rr. Historically, in this
2535 packets has arrived). When employed in this fashion, the balance-rr
2539 12.2.2 MT Link Monitoring for Multiple Switch Topology
2540 ------------------------------------------------------
2552 13.1 Link Establishment and Failover Delays
2553 -------------------------------------------
2556 timing of link up and down reporting by the switch.
2558 First, when a link comes up, some switches may indicate that
2559 the link is up (carrier available), but not pass traffic over the
2567 Second, some switches may "bounce" the link state one or more
2568 times while a link is changing state. This occurs most commonly while
2573 driver will immediately reuse the first link that goes up, even if the
2584 to not activate a backup interface immediately after a link goes down.
2588 --------------------------------
2600 For example, on a bond in active-backup mode with five slaves
2603 # ping -n 10.0.4.2
2620 single switch, when the switch (temporarily) floods the traffic to all
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 ------------------------------------
2688 appear to bonding as either a single switch topology (all PMs) or as a
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.
2711 Link monitoring issues
2712 ----------------------
2715 monitor will reliably detect link loss to an external switch. This is
2720 only able to detect link failures between the ESM and the JS20 system.
2727 --------------
2729 The Serial Over LAN (SoL) link is established over the primary
2730 ethernet (eth0) only, therefore, any loss of link to eth0 will result
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 ----------------------------------------
2774 If link monitoring is enabled, then the failing device will be
2775 disabled. The active-backup mode will fail over to a backup link, and
2776 other modes will ignore the failed link. The link will continue to be
2782 Link monitoring can be enabled via either the miimon or
2788 If no link monitoring is configured, the bonding driver will
2789 be unable to detect link failures, and will assume that all links are
2795 ----------------------------------------------
2800 ---------------------------------------------
2804 In the basic balance modes (balance-rr and balance-xor), it
2809 The advanced balance modes (balance-tlb and balance-alb) do
2815 802.3ad Dynamic Link Aggregation. Most managed and many unmanaged
2818 The active-backup mode should work with any Layer-II switch.
2821 ---------------------------------------------------------
2828 ifconfig or ip link), the MAC address of the bonding device is taken from
2834 ifconfig or ip link::
2838 # ip link set bond0 address 66:77:88:99:aa:bb
2843 # ifconfig bond0 down ; modprobe -r bonding
2851 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2873 http://vger.kernel.org/vger-lists.html#netdev