Lines Matching full:bonding
4 Linux Ethernet Bonding Driver HOWTO
27 The Linux bonding driver provides a method for aggregating
33 The bonding driver originally came from Donald Becker's
43 1. Bonding Driver Installation
45 2. Bonding Driver Options
47 3. Configuring Bonding Devices
54 3.3 Configuring Bonding Manually with Ifenslave
56 3.4 Configuring Bonding Manually via Sysfs
61 4. Querying Bonding Configuration
62 4.1 Bonding Configuration
83 11. Configuring Bonding for High Availability
86 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
89 12. Configuring Bonding for Maximum Throughput
91 12.1.1 MT Bonding Mode Selection for Single Switch Topology
94 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
109 1. Bonding Driver Installation
112 Most popular distro kernels ship with the bonding driver
114 have need to compile bonding from source (e.g., configuring and
118 1.1 Configure and build the kernel with bonding
121 The current version of the bonding driver is available in the
122 drivers/net/bonding subdirectory of the most recent kernel source
127 "make config"), then select "Bonding driver support" in the "Network
130 to the driver or configure more than one bonding device.
134 1.2 Bonding Control Utility
137 It is recommended to configure bonding via iproute2 (netlink)
140 2. Bonding Driver Options
143 Options for the bonding driver are supplied as parameters to the
144 bonding module at load time, or are specified via sysfs.
151 Details on bonding support for sysfs is provided in the
152 "Configuring Bonding Manually via Sysfs" section, below.
154 The available bonding driver parameters are listed below. If a
157 run in a separate window to watch for bonding driver error messages.
200 address. If the all-zeroes MAC is specified, bonding will internally
249 This option was added in bonding version 3.4.0.
274 Normally, bonding will drop duplicate frames (received on inactive
288 bonding mode, and the state of the slave). Regular traffic is
383 bonding to decide which slaves are more likely to work in case of
388 bonding hosts are concurrently issuing ARPs to one or more targets
391 generated by the multiple bonding instances will fool the standard
395 bonding.
415 This option was added in bonding version 3.1.0.
480 bonding to set all slaves of an active-backup bond to
536 This option was added in bonding version 3.2.0. The "follow"
537 policy was added in bonding version 3.3.0.
567 Specifies the number of bonding devices to create for this
568 instance of the bonding driver. E.g., if max_bonds is 3, and
569 the bonding driver is not already loaded, then bond0, bond1
571 a value of 0 will load bonding, but will not create any devices.
603 Specifies one of the bonding policies. The default is
621 In bonding version 2.6.2 or later, when a failover
622 occurs in active-backup mode, bonding will issue one
624 One gratuitous ARP is issued for the bonding master
680 Adaptive transmit load balancing: channel bonding that
706 The bonding driver intercepts the ARP Replies sent by
715 Request the bonding driver copies and saves the peer's
718 retrieved and the bonding driver initiates an ARP
765 bonding device and each VLAN sub-device. This is repeated at
771 bonding versions 3.3.0 and 3.4.0 respectively.
773 From Linux 3.0 and bonding version 3.7.1, these notifications
858 This option was added for bonding version 3.6.0.
879 disables it. This option was added in bonding driver 3.7.1
900 If bonding insists that the link is up when it should not be,
905 setting use_carrier to 0 will cause bonding to revert to the
1028 The default value is layer2. This option was added in bonding
1029 version 2.6.3. In earlier versions of bonding, this parameter
1031 layer2+3 value was added for bonding version 3.2.2.
1043 This option is useful for bonding modes balance-rr (0), active-backup
1049 This option was added for bonding version 3.7.0.
1053 Specifies the number of seconds between instances where the bonding
1059 3. Configuring Bonding Devices
1062 You can configure bonding using either your distro's network
1066 Recent versions of these packages have support for bonding, while older
1069 We will first describe the options for configuring bonding for
1071 or partial support for bonding, then provide information on enabling
1072 bonding without support from the network initialization scripts (i.e.,
1091 Next, to determine if your installation supports bonding,
1097 sysconfig has support for bonding.
1103 with bonding support, for example, SuSE Linux Enterprise Server 9.
1106 bonding, however, at this writing, the YaST system configuration
1107 front end does not provide any means to work with bonding devices.
1108 Bonding devices can be managed by hand, however, as follows.
1144 it's time to create the configuration file for the bonding device
1146 bonding device to create, starting at 0. The first such file is
1149 of bonding.
1176 manually. Bonding devices may be configured this
1181 a valid choice for a bonding device.
1188 bonding master device. The only useful value is "yes."
1191 instance of the bonding module for this device. Specify the options
1192 for the bonding mode, link monitoring, and so on here. Do not include
1193 the max_bonds bonding parameter; this will confuse the configuration
1194 system if you have multiple bonding devices.
1215 remove the bonding module as part of the network shutdown processing,
1219 Also, at this writing, YaST/YaST2 will not manage bonding
1220 devices (they do not show bonding interfaces on its list of network
1222 change the bonding configuration.
1237 writing, this does not function for bonding devices; the scripts
1246 handling multiple bonding devices. All that is necessary is for each
1247 bonding instance to have an appropriately configured ifcfg-bondX file
1249 instance of bonding, as this will confuse sysconfig. If you require
1250 multiple bonding devices with identical parameters, create multiple
1253 Because the sysconfig scripts supply the bonding module
1261 initscripts with bonding support, for example, Red Hat Enterprise Linux
1263 initialization scripts have knowledge of bonding, and can be configured to
1264 control bonding devices. Note that older versions of the initscripts
1265 package have lower levels of support for bonding; this will be noted where
1291 also depend on the final bonding interface name chosen for your bond.
1293 one for each device, i.e., the first bonding instance is bond0, the
1316 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1322 specified in BONDING_OPTS are identical to the bonding module parameters
1337 your distro) to load the bonding module with your desired options when the
1339 will load the bonding module, and select its options:
1341 alias bond0 bonding
1356 work) have support for assigning IP information to bonding devices via
1359 To configure bonding for DHCP, configure it as described
1361 and add a line consisting of "TYPE=Bonding". Note that the TYPE value
1368 Enterprise Linux 5 support multiple bonding interfaces by simply
1371 and a bonding driver of version 3.0.0 or later. Other configurations may
1372 not support this method for specifying multiple bonding interfaces; for
1376 3.3 Configuring Bonding Manually with iproute2
1381 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1384 The general method for these systems is to place the bonding
1396 modprobe bonding mode=balance-alb miimon=100
1402 Replace the example bonding module parameters and bond0
1407 ifup and ifdown scripts on the bond devices. To reload the bonding
1417 which only initializes the bonding configuration, then call that
1418 separate script from within boot.local. This allows for bonding to be
1421 To shut down the bonding devices, it is necessary to first
1422 mark the bonding device itself as being down, then remove the
1427 # rmmod bonding
1438 bonding devices with differing options for those systems whose network
1441 If you require multiple bonding devices, but all with the same
1445 To create multiple bonding devices with differing options, it is
1446 preferable to use bonding parameters exported by sysfs, documented in the
1449 For versions of bonding without sysfs support, the only means to
1450 provide multiple instances of bonding with differing options is to load
1451 the bonding driver multiple times. Note that current versions of the
1454 section Configuring Bonding Devices, above, if you're not sure about your
1461 sets of bonding options in ``/etc/modprobe.d/*.conf``, for example::
1463 alias bond0 bonding
1466 alias bond1 bonding
1469 will load the bonding module two times. The first instance is
1475 the above does not work, and the second bonding instance never sees
1479 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1493 3.4 Configuring Bonding Manually via Sysfs
1496 Starting with version 3.0.0, Channel Bonding may be configured
1505 bonding is compiled into the kernel.
1508 bonding this way. The examples in this document assume that you
1536 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1542 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1546 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1555 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1562 files located in /sys/class/net/<bond name>/bonding
1576 # echo 6 > /sys/class/net/bond0/bonding/mode
1578 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1586 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1595 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1596 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1604 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1608 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1613 the bonding driver sends learning packets to each slaves peer switch. The
1626 modprobe bonding
1628 echo balance-alb > /sys/class/net/bond0/bonding/mode
1630 echo 100 > /sys/class/net/bond0/bonding/miimon
1631 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1632 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1640 echo active-backup > /sys/class/net/bond1/bonding/mode
1642 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1643 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1644 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1645 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1654 The ifup and ifdown commands on Debian don't support bonding out of
1655 the box. The ifenslave-2.6 package should be installed to provide bonding
1659 Note that ifenslave-2.6 package will load the bonding module and use
1703 When using the bonding driver, the physical port which transmits a frame is
1704 typically selected by the bonding driver, and is not relevant to the user or
1706 the selected bonding mode. On occasion however, it is helpful to direct certain
1715 By default the bonding driver is multiqueue aware and 16 queues are created
1721 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1724 Bonding Mode: fault-tolerance (active-backup)
1746 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1772 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1774 slave devices as well as bond devices and the bonding driver will simply act as
1778 This feature first appeared in bonding driver version 3.7.0 and support for
1784 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1796 few bonding parameters:
1810 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1817 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1825 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1828 4 Querying Bonding Configuration
1831 4.1 Bonding Configuration
1834 Each bonding device has a read-only file residing in the
1835 /proc/net/bonding directory. The file contents include information
1836 about the bonding configuration, options and state of each slave.
1838 For example, the contents of /proc/net/bonding/bond0 after the
1842 Ethernet Channel Bonding Driver: 2.6.1 (October 29, 2004)
1843 Bonding Mode: load balancing (round-robin)
1859 bonding configuration, state, and version of the bonding driver.
1865 command. Bonding devices will have the MASTER flag set; Bonding slave
1924 match. For these three modes, the bonding mode really selects a
1934 driver and passing through bonding will be tagged by default. Self
1935 generated packets, for example, bonding's learning packets or ARP
1937 tagged internally by bonding itself. As a result, bonding must
1942 that can do VLAN hardware acceleration offloading, the bonding
1948 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1951 VLAN interfaces *must* be added on top of a bonding interface
1952 only after enslaving at least one slave. The bonding interface has a
1961 top of it. When a new slave is added, the bonding interface will
1972 2. Set the bonding interface's hardware address so that it
1976 underlying device -- i.e. the bonding interface -- to promiscuous
1983 The bonding driver at present supports two schemes for
1988 bonding driver itself, it is not possible to enable both ARP and MII
2013 alias bond0 bonding
2019 alias bond0 bonding
2055 When bonding is configured, it is important that the slave
2057 generally, not have routes at all). For example, suppose the bonding
2070 may bypass the bonding driver (because outgoing traffic to, in this
2098 alias bond0 bonding
2107 happens because bonding is loaded first, then its slave device's
2110 devices, but the bonding configuration tries to enslave eth2 and eth3
2115 add above bonding e1000 tg3
2118 bonding is loaded. This command is fully documented in the
2125 softdep bonding pre: tg3 e1000
2127 This will load tg3 and e1000 modules before loading the bonding one.
2134 By default, bonding enables the use_carrier option, which
2135 instructs bonding to trust the driver to maintain carrier state.
2139 With use_carrier enabled, bonding will always see these links as up,
2162 If running SNMP agents, the bonding driver should be loaded
2168 bonding driver, the interface for the IP address will be associated
2186 This problem is avoided by loading the bonding driver before
2188 loading the bonding driver first, the IP address 192.168.1.1 is
2213 The bonding driver handles promiscuous mode changes to the bonding
2234 11. Configuring Bonding for High Availability
2251 access to fail over to. Additionally, the bonding load balance modes
2255 See Section 12, "Configuring Bonding for Maximum Throughput"
2256 for information on configuring bonding with one peer device.
2261 With multiple switches, the configuration of bonding and the
2285 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology
2289 broadcast modes are the only useful bonding modes when optimizing for
2334 to the logically "interior" ports that bonding is able to monitor via
2339 12. Configuring Bonding for Maximum Throughput
2376 multiple physical links is, for purposes of configuring bonding, the
2413 12.1.1 MT Bonding Mode Selection for Single Switch Topology
2417 although you will have to decide which bonding mode best suits your
2499 the same speed and duplex. Also, as with all bonding load
2504 Additionally, the linux bonding 802.3ad implementation
2539 peers (as described in the Bonding Module Options section,
2590 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology
2593 In actual practice, the bonding mode typically employed in
2611 host in the network is configured with bonding).
2628 value to the updelay bonding module option to delay the use of the
2636 Note that when a bonding interface has no active links, the
2649 Failover may be delayed via the downdelay bonding module option.
2654 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2659 traffic when the bonding device is first used, or after it has been
2678 This is not due to an error in the bonding driver, rather, it
2698 bonding on specific hardware platforms, or for interfacing bonding
2706 On the JS20 blades, the bonding driver supports only
2724 switch). Some bonding modes require a specific BladeCenter internal
2752 appear to bonding as either a single switch topology (all PMs) or as a
2770 bonding device (i.e., the network must converge at some point outside
2797 bonding driver.
2801 avoid fail-over delay issues when using bonding.
2810 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2820 Starting with version 3.2.1, bonding also supports Infiniband
2823 3. How many bonding devices can I have?
2828 4. How many slaves can a bonding device have?
2852 If no link monitoring is configured, the bonding driver will
2856 depends upon the bonding mode and network configuration.
2858 6. Can bonding be used for High Availability?
2884 8. Where does a bonding device get its MAC address from?
2888 the fail_over_mac option is enabled, the bonding device's MAC address is
2892 ifconfig or ip link), the MAC address of the bonding device is taken from
2895 the bonding device is brought down or reconfigured.
2907 # ifconfig bond0 down ; modprobe -r bonding
2915 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2922 The latest version of the bonding driver can be found in the latest
2926 source (named Documentation/networking/bonding.rst).
2928 Discussions regarding the development of the bonding driver take place