Lines Matching refs:bonding
27 The Linux bonding driver provides a method for aggregating
33 The bonding driver originally came from Donald Becker's
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
130 to the driver or configure more than one bonding device.
137 It is recommended to configure bonding via iproute2 (netlink)
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
154 The available bonding driver parameters are listed below. If a
157 run in a separate window to watch for bonding driver error messages.
248 This option was added in bonding version 3.4.0.
273 Normally, bonding will drop duplicate frames (received on inactive
287 bonding mode, and the state of the slave). Regular traffic is
371 bonding to decide which slaves are more likely to work in case of
376 bonding hosts are concurrently issuing ARPs to one or more targets
379 generated by the multiple bonding instances will fool the standard
383 bonding.
403 This option was added in bonding version 3.1.0.
445 bonding to set all slaves of an active-backup bond to
501 This option was added in bonding version 3.2.0. The "follow"
502 policy was added in bonding version 3.3.0.
532 Specifies the number of bonding devices to create for this
533 instance of the bonding driver. E.g., if max_bonds is 3, and
534 the bonding driver is not already loaded, then bond0, bond1
536 a value of 0 will load bonding, but will not create any devices.
567 Specifies one of the bonding policies. The default is
585 In bonding version 2.6.2 or later, when a failover
586 occurs in active-backup mode, bonding will issue one
588 One gratuitous ARP is issued for the bonding master
644 Adaptive transmit load balancing: channel bonding that
670 The bonding driver intercepts the ARP Replies sent by
679 Request the bonding driver copies and saves the peer's
682 retrieved and the bonding driver initiates an ARP
729 bonding device and each VLAN sub-device. This is repeated at
735 bonding versions 3.3.0 and 3.4.0 respectively.
737 From Linux 3.0 and bonding version 3.7.1, these notifications
810 This option was added for bonding version 3.6.0.
831 disables it. This option was added in bonding driver 3.7.1
852 If bonding insists that the link is up when it should not be,
857 setting use_carrier to 0 will cause bonding to revert to the
979 The default value is layer2. This option was added in bonding
980 version 2.6.3. In earlier versions of bonding, this parameter
982 layer2+3 value was added for bonding version 3.2.2.
994 This option is useful for bonding modes balance-rr (0), active-backup
1000 This option was added for bonding version 3.7.0.
1004 Specifies the number of seconds between instances where the bonding
1013 You can configure bonding using either your distro's network
1017 Recent versions of these packages have support for bonding, while older
1020 We will first describe the options for configuring bonding for
1022 or partial support for bonding, then provide information on enabling
1023 bonding without support from the network initialization scripts (i.e.,
1042 Next, to determine if your installation supports bonding,
1048 sysconfig has support for bonding.
1054 with bonding support, for example, SuSE Linux Enterprise Server 9.
1057 bonding, however, at this writing, the YaST system configuration
1058 front end does not provide any means to work with bonding devices.
1095 it's time to create the configuration file for the bonding device
1097 bonding device to create, starting at 0. The first such file is
1100 of bonding.
1132 a valid choice for a bonding device.
1139 bonding master device. The only useful value is "yes."
1142 instance of the bonding module for this device. Specify the options
1143 for the bonding mode, link monitoring, and so on here. Do not include
1144 the max_bonds bonding parameter; this will confuse the configuration
1145 system if you have multiple bonding devices.
1166 remove the bonding module as part of the network shutdown processing,
1170 Also, at this writing, YaST/YaST2 will not manage bonding
1171 devices (they do not show bonding interfaces on its list of network
1173 change the bonding configuration.
1188 writing, this does not function for bonding devices; the scripts
1197 handling multiple bonding devices. All that is necessary is for each
1198 bonding instance to have an appropriately configured ifcfg-bondX file
1200 instance of bonding, as this will confuse sysconfig. If you require
1201 multiple bonding devices with identical parameters, create multiple
1204 Because the sysconfig scripts supply the bonding module
1212 initscripts with bonding support, for example, Red Hat Enterprise Linux
1214 initialization scripts have knowledge of bonding, and can be configured to
1215 control bonding devices. Note that older versions of the initscripts
1216 package have lower levels of support for bonding; this will be noted where
1242 also depend on the final bonding interface name chosen for your bond.
1244 one for each device, i.e., the first bonding instance is bond0, the
1267 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1273 specified in BONDING_OPTS are identical to the bonding module parameters
1288 your distro) to load the bonding module with your desired options when the
1290 will load the bonding module, and select its options:
1292 alias bond0 bonding
1307 work) have support for assigning IP information to bonding devices via
1310 To configure bonding for DHCP, configure it as described
1319 Enterprise Linux 5 support multiple bonding interfaces by simply
1322 and a bonding driver of version 3.0.0 or later. Other configurations may
1323 not support this method for specifying multiple bonding interfaces; for
1332 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1335 The general method for these systems is to place the bonding
1347 modprobe bonding mode=balance-alb miimon=100
1353 Replace the example bonding module parameters and bond0
1358 ifup and ifdown scripts on the bond devices. To reload the bonding
1368 which only initializes the bonding configuration, then call that
1369 separate script from within boot.local. This allows for bonding to be
1372 To shut down the bonding devices, it is necessary to first
1373 mark the bonding device itself as being down, then remove the
1378 # rmmod bonding
1389 bonding devices with differing options for those systems whose network
1392 If you require multiple bonding devices, but all with the same
1396 To create multiple bonding devices with differing options, it is
1397 preferable to use bonding parameters exported by sysfs, documented in the
1400 For versions of bonding without sysfs support, the only means to
1401 provide multiple instances of bonding with differing options is to load
1402 the bonding driver multiple times. Note that current versions of the
1412 sets of bonding options in ``/etc/modprobe.d/*.conf``, for example::
1414 alias bond0 bonding
1417 alias bond1 bonding
1420 will load the bonding module two times. The first instance is
1426 the above does not work, and the second bonding instance never sees
1430 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1456 bonding is compiled into the kernel.
1459 bonding this way. The examples in this document assume that you
1487 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1493 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1497 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1506 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1513 files located in /sys/class/net/<bond name>/bonding
1527 # echo 6 > /sys/class/net/bond0/bonding/mode
1529 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1537 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1546 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1547 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1555 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1559 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1564 the bonding driver sends learning packets to each slaves peer switch. The
1577 modprobe bonding
1579 echo balance-alb > /sys/class/net/bond0/bonding/mode
1581 echo 100 > /sys/class/net/bond0/bonding/miimon
1582 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1583 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1591 echo active-backup > /sys/class/net/bond1/bonding/mode
1593 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1594 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1595 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1596 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1605 The ifup and ifdown commands on Debian don't support bonding out of
1606 the box. The ifenslave-2.6 package should be installed to provide bonding
1610 Note that ifenslave-2.6 package will load the bonding module and use
1654 When using the bonding driver, the physical port which transmits a frame is
1655 typically selected by the bonding driver, and is not relevant to the user or
1657 the selected bonding mode. On occasion however, it is helpful to direct certain
1666 By default the bonding driver is multiqueue aware and 16 queues are created
1672 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1697 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1723 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1725 slave devices as well as bond devices and the bonding driver will simply act as
1729 This feature first appeared in bonding driver version 3.7.0 and support for
1735 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1747 few bonding parameters:
1761 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1768 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1776 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1785 Each bonding device has a read-only file residing in the
1786 /proc/net/bonding directory. The file contents include information
1787 about the bonding configuration, options and state of each slave.
1789 For example, the contents of /proc/net/bonding/bond0 after the
1810 bonding configuration, state, and version of the bonding driver.
1875 match. For these three modes, the bonding mode really selects a
1885 driver and passing through bonding will be tagged by default. Self
1886 generated packets, for example, bonding's learning packets or ARP
1888 tagged internally by bonding itself. As a result, bonding must
1893 that can do VLAN hardware acceleration offloading, the bonding
1899 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1902 VLAN interfaces *must* be added on top of a bonding interface
1903 only after enslaving at least one slave. The bonding interface has a
1912 top of it. When a new slave is added, the bonding interface will
1923 2. Set the bonding interface's hardware address so that it
1927 underlying device -- i.e. the bonding interface -- to promiscuous
1934 The bonding driver at present supports two schemes for
1939 bonding driver itself, it is not possible to enable both ARP and MII
1973 alias bond0 bonding
1979 alias bond0 bonding
2015 When bonding is configured, it is important that the slave
2017 generally, not have routes at all). For example, suppose the bonding
2030 may bypass the bonding driver (because outgoing traffic to, in this
2058 alias bond0 bonding
2067 happens because bonding is loaded first, then its slave device's
2070 devices, but the bonding configuration tries to enslave eth2 and eth3
2075 add above bonding e1000 tg3
2078 bonding is loaded. This command is fully documented in the
2085 softdep bonding pre: tg3 e1000
2087 This will load tg3 and e1000 modules before loading the bonding one.
2094 By default, bonding enables the use_carrier option, which
2095 instructs bonding to trust the driver to maintain carrier state.
2099 With use_carrier enabled, bonding will always see these links as up,
2122 If running SNMP agents, the bonding driver should be loaded
2128 bonding driver, the interface for the IP address will be associated
2146 This problem is avoided by loading the bonding driver before
2148 loading the bonding driver first, the IP address 192.168.1.1 is
2173 The bonding driver handles promiscuous mode changes to the bonding
2211 access to fail over to. Additionally, the bonding load balance modes
2216 for information on configuring bonding with one peer device.
2221 With multiple switches, the configuration of bonding and the
2249 broadcast modes are the only useful bonding modes when optimizing for
2294 to the logically "interior" ports that bonding is able to monitor via
2336 multiple physical links is, for purposes of configuring bonding, the
2377 although you will have to decide which bonding mode best suits your
2459 the same speed and duplex. Also, as with all bonding load
2464 Additionally, the linux bonding 802.3ad implementation
2553 In actual practice, the bonding mode typically employed in
2571 host in the network is configured with bonding).
2588 value to the updelay bonding module option to delay the use of the
2596 Note that when a bonding interface has no active links, the
2609 Failover may be delayed via the downdelay bonding module option.
2614 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2619 traffic when the bonding device is first used, or after it has been
2638 This is not due to an error in the bonding driver, rather, it
2658 bonding on specific hardware platforms, or for interfacing bonding
2666 On the JS20 blades, the bonding driver supports only
2684 switch). Some bonding modes require a specific BladeCenter internal
2712 appear to bonding as either a single switch topology (all PMs) or as a
2730 bonding device (i.e., the network must converge at some point outside
2757 bonding driver.
2761 avoid fail-over delay issues when using bonding.
2770 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2780 Starting with version 3.2.1, bonding also supports Infiniband
2783 3. How many bonding devices can I have?
2788 4. How many slaves can a bonding device have?
2812 If no link monitoring is configured, the bonding driver will
2816 depends upon the bonding mode and network configuration.
2818 6. Can bonding be used for High Availability?
2844 8. Where does a bonding device get its MAC address from?
2848 the fail_over_mac option is enabled, the bonding device's MAC address is
2852 ifconfig or ip link), the MAC address of the bonding device is taken from
2855 the bonding device is brought down or reconfigured.
2867 # ifconfig bond0 down ; modprobe -r bonding
2875 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2882 The latest version of the bonding driver can be found in the latest
2886 source (named Documentation/networking/bonding.rst).
2888 Discussions regarding the development of the bonding driver take place