Lines Matching +full:individual +full:- +full:port +full:- +full:switching
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
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
263 This defines the upper 10 bits of the port key. The values can be
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.
458 Specifies whether active-backup mode should set all slaves to
468 bonding to set all slaves of an active-backup bond to
575 asserting carrier. It is similar to the Cisco EtherChannel min-links
577 must be up (link-up state) before marking the bond device as up
592 balance-rr (round robin). Possible values are:
594 balance-rr or 0
596 Round-robin policy: Transmit packets in sequential
601 active-backup or 1
603 Active-backup policy: Only one slave in the bond is
606 externally visible on only one port (network adapter)
610 occurs in active-backup mode, bonding will issue one
622 balance-xor or 2
650 regards to the packet mis-ordering requirements of
666 balance-tlb or 5
688 balance-alb or 6
690 Adaptive load balancing: includes balance-tlb plus
718 and when an inactive slave is re-activated. The
753 bonding device and each VLAN sub-device. This is repeated at
757 The valid range is 0 - 255; the default value is 1. These options
758 affect only the active-backup mode. These options were added for
771 The valid range is 0 - 65535; the default value is 1. This option
772 has effect only in balance-rr mode.
782 The valid range is 0 - 300000. The default value is 0, which means
791 for active-backup(1), balance-tlb (5) and balance-alb (6) mode.
801 off-line will alternate devices be used. This is useful when
805 The primary option is only valid for active-backup(1),
806 balance-tlb (5) and balance-alb (6) mode.
813 occurs. This option is designed to prevent flip-flopping between
855 characteristics but can cause packet reordering. If re-ordering is
858 xmit-hash-policy can be used to select the appropriate hashing for
903 balance-xor, 802.3ad, and tlb modes. Possible values are:
936 network peer on the same slave. For non-IP traffic,
957 hash = source port, destination port (as in the header)
968 IPv6 protocol traffic, the source and destination port
969 information is omitted. For non-IP traffic, the
1006 hash to load-balance traffic per-vlan, with failover
1009 use their own vlan, to give lacp-like functionality
1010 without requiring lacp-capable switching hardware.
1027 The valid range is 0 - 255; the default value is 1. A value of 0
1031 This option is useful for bonding modes balance-rr (0), active-backup
1032 (1), balance-tlb (5) and balance-alb (6), in which a failover can
1044 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
1045 has effect only in balance-tlb and balance-alb modes.
1073 $ rpm -qf /sbin/ifup
1088 ----------------------------------------
1101 ifcfg-id file for each slave device. The simplest way to accomplish
1103 file ifcfg-id file created; see below for some issues with DHCP). The
1106 ifcfg-id-xx:xx:xx:xx:xx:xx
1111 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1121 _nm_name='bus-pci-0001:61:01.0'
1131 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1133 itself. This file is named ifcfg-bondX, where X is the number of the
1135 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1139 The contents of the ifcfg-bondX file is as follows::
1149 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1151 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1190 (bus-pci-0000:06:08.1 in the example above) specify the physical
1221 -------------------------------
1231 -----------------------------------------------
1235 bonding instance to have an appropriately configured ifcfg-bondX file
1239 ifcfg-bondX files.
1242 options in the ifcfg-bondX file, it is not necessary to add them to
1246 ------------------------------------------
1259 network-script file for all physical adapters that will be members of
1262 /etc/sysconfig/network-scripts
1264 The file name must be prefixed with "ifcfg-eth" and suffixed
1266 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1277 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1285 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1286 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1287 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1304 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1307 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1330 options bond0 mode=balance-alb miimon=100
1340 ---------------------------------
1353 -------------------------------------------------
1357 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1365 -----------------------------------------------
1384 modprobe bonding mode=balance-alb miimon=100
1407 enabled without re-running the entire global init script.
1423 -----------------------------------------
1452 options bond0 -o bond0 mode=balance-rr miimon=100
1455 options bond1 -o bond1 mode=balance-alb miimon=50
1458 named "bond0" and creates the bond0 device in balance-rr mode with an
1460 bond1 device in balance-alb mode with an miimon of 50.
1467 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1468 mode=balance-alb miimon=50
1474 to rename modules at load time (the "-o bond1" part). Attempts to pass
1482 ------------------------------------------
1502 -----------------------------
1509 # echo -bar > /sys/class/net/bonding_masters
1522 --------------------------
1534 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1543 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1548 -------------------------------
1552 The names of these files correspond directly with the command-
1561 To configure bond0 for balance-alb mode::
1565 - or -
1566 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1579 monitoring is enabled, and vice-versa.
1592 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1605 ---------------------
1616 echo balance-alb > /sys/class/net/bond0/bonding/mode
1623 active-backup mode, using ARP monitoring, add the following lines to
1628 echo active-backup > /sys/class/net/bond1/bonding/mode
1636 -----------------------------------------
1643 the box. The ifenslave-2.6 package should be installed to provide bonding
1644 support. Once installed, this package will provide ``bond-*`` options
1647 Note that ifenslave-2.6 package will load the bonding module and use
1651 ----------------------
1654 active-backup mode, with eth0 and eth1 as slaves::
1658 bond-slaves eth0 eth1
1659 bond-mode active-backup
1660 bond-miimon 100
1661 bond-primary eth0 eth1
1670 bond-slaves none
1671 bond-mode active-backup
1672 bond-miimon 100
1676 bond-master bond0
1677 bond-primary eth0 eth1
1681 bond-master bond0
1682 bond-primary eth0 eth1
1684 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1686 /usr/share/doc/ifenslave-2.6.
1689 ----------------------------------------------
1691 When using the bonding driver, the physical port which transmits a frame is
1693 system administrator. The output port is simply selected using the policies of
1712 Bonding Mode: fault-tolerance (active-backup)
1763 a pass-through for selecting output queues on the slave device rather than
1764 output port selection.
1767 output slave selection was limited to round-robin and active-backup modes.
1770 ----------------------------------------------------------
1786 (a) ad_actor_system : You can set a random mac-address that can be used for
1788 Also it's preferable to set the local-admin bit. Following shell code
1789 generates a random mac-address as described above::
1801 is 65535, but system can take the value from 1 - 65535. Following shell
1807 (c) ad_user_port_key : Use the user portion of the port-key. The default
1808 keeps this empty. These are the upper 10 bits of the port-key and value
1809 ranges from 0 - 1023. Following shell code generates these 10 bits and
1820 -------------------------
1822 Each bonding device has a read-only file residing in the
1831 Bonding Mode: load balancing (round-robin)
1850 -------------------------
1893 The active-backup, balance-tlb and balance-alb modes do not
1904 The balance-rr, balance-xor and broadcast modes generally
1936 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1943 would pick up the all-zeroes hardware address. Once the first slave
1964 underlying device -- i.e. the bonding interface -- to promiscuous
1980 -------------------------
1989 ------------------------------------
2012 -------------------------
2041 -------------------------
2076 ----------------------------
2087 options bond0 mode=some-mode miimon=50
2120 ---------------------------------------------------------
2205 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2208 For the active-backup, balance-tlb and balance-alb modes, the
2211 For balance-tlb mode, the active slave is the slave currently
2214 For balance-alb mode, the active slave is the slave used as a
2215 "primary." This slave is used for mode-specific control traffic, for
2218 For the active-backup, balance-tlb and balance-alb modes, when
2233 --------------------------------------------------
2240 support link monitoring of their members, so if individual links fail,
2247 ----------------------------------------------------
2258 +-----+----+ +-----+----+
2260 | switch A +--------------------------+ switch B |
2262 +-----+----+ +-----++---+
2264 | +-------+ |
2265 +-------------+ host1 +---------------+
2266 eth0 +-------+ eth1
2274 -------------------------------------------------------------
2276 In a topology such as the example above, the active-backup and
2281 active-backup:
2294 necessary for some specific one-way traffic to reach both
2298 ----------------------------------------------------------------
2311 individual component to pass traffic for any reason). Additionally,
2319 switch that causes the link state of a particular switch port to be set
2320 down (or up) when the state of another switch port goes down (or up).
2331 ------------------------------------------------------
2347 +----------+ +----------+
2349 | Host A +---------------------+ router +------------------->
2350 | +---------------------+ | Hosts B and C are out
2352 +----------+ +----------+
2374 +----------+ +----------+ +--------+
2375 | |eth0 port1| +-------+ Host B |
2376 | Host A +------------+ switch |port3 +--------+
2377 | +------------+ | +--------+
2378 | |eth1 port2| +------------------+ Host C |
2379 +----------+ +----------+port4 +--------+
2392 will be addressed directly by their individual MAC addresses.
2402 -----------------------------------------------------------
2408 balance-rr:
2433 (instead choosing a port based upon IP or MAC level addresses);
2435 through the switch to a balance-rr bond will not utilize greater
2447 active-backup:
2449 the active-backup mode, as the inactive backup devices are all
2453 available bandwidth. On the plus side, active-backup mode
2458 balance-xor:
2468 As with balance-rr, the switch ports need to be configured for
2472 Like active-backup, there is not much advantage to this
2488 balance modes other than balance-rr, no single connection will
2504 balance-tlb:
2505 The balance-tlb mode balances outgoing traffic by peer.
2511 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2523 balance-alb:
2524 This mode is everything that balance-tlb is, and more.
2525 It has all of the features (and restrictions) of balance-tlb,
2535 ----------------------------------------------------
2544 -----------------------------------------------------
2550 +-----------+
2552 +-+---+---+-+
2554 +--------+ | +---------+
2556 +------+---+ +-----+----+ +-----+----+
2558 +------+---+ +-----+----+ +-----+----+
2560 +--------+ | +---------+
2562 +-+---+---+-+
2564 +-----------+
2571 hosts, three 24 port switches can be significantly less expensive than
2572 a single 72 port switch.
2574 If access beyond the network is required, an individual host
2579 -------------------------------------------------------------
2582 configurations of this type is balance-rr. Historically, in this
2587 packets has arrived). When employed in this fashion, the balance-rr
2588 mode allows individual connections between two hosts to effectively
2592 ------------------------------------------------------
2605 -------------------------------------------
2640 --------------------------------
2652 For example, on a bond in active-backup mode with five slaves
2655 # ping -n 10.0.4.2
2669 the packet with a particular switch port, and so it may send the
2679 most Cisco switches, the privileged command "clear mac address-table
2690 --------------------
2695 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2700 --------------------------------
2703 integrated on the planar (that's "motherboard" in IBM-speak). In the
2704 BladeCenter chassis, the eth0 port of all JS20 blades is hard wired to
2706 An add-on Broadcom daughter card can be installed on a JS20 to provide
2715 Additional BladeCenter-specific networking information can be
2718 - "IBM eServer BladeCenter Networking Options"
2719 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2722 ------------------------------------
2747 -------------------------------
2749 The balance-rr mode requires the use of passthrough modules
2752 appropriate ports, as is usual for balance-rr.
2754 The balance-alb and balance-tlb modes will function with
2761 The active-backup mode has no additional requirements.
2764 ----------------------
2775 detect failures to the "external" port, which is then directly
2779 --------------
2789 avoid fail-over delay issues when using bonding.
2796 -------------------
2802 -----------------------------------------
2804 Any Ethernet type cards (you can even mix cards - a Intel
2809 slaves in active-backup mode.
2812 ----------------------------------------
2817 ----------------------------------------------
2824 ----------------------------------------
2827 disabled. The active-backup mode will fail over to a backup link, and
2847 ----------------------------------------------
2852 ---------------------------------------------
2856 In the basic balance modes (balance-rr and balance-xor), it
2861 The advanced balance modes (balance-tlb and balance-alb) do
2870 The active-backup mode should work with any Layer-II switch.
2873 ---------------------------------------------------------
2895 # ifconfig bond0 down ; modprobe -r bonding
2903 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2925 http://vger.kernel.org/vger-lists.html#netdev