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.
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.
468 bonding to set all slaves of an active-backup bond to
524 This option was added in bonding version 3.2.0. The "follow"
525 policy was added in bonding version 3.3.0.
555 Specifies the number of bonding devices to create for this
556 instance of the bonding driver. E.g., if max_bonds is 3, and
557 the bonding driver is not already loaded, then bond0, bond1
559 a value of 0 will load bonding, but will not create any devices.
590 Specifies one of the bonding policies. The default is
608 In bonding version 2.6.2 or later, when a failover
609 occurs in active-backup mode, bonding will issue one
611 One gratuitous ARP is issued for the bonding master
667 Adaptive transmit load balancing: channel bonding that
693 The bonding driver intercepts the ARP Replies sent by
702 Request the bonding driver copies and saves the peer's
705 retrieved and the bonding driver initiates an ARP
752 bonding device and each VLAN sub-device. This is repeated at
758 bonding versions 3.3.0 and 3.4.0 respectively.
760 From Linux 3.0 and bonding version 3.7.1, these notifications
844 This option was added for bonding version 3.6.0.
865 disables it. This option was added in bonding driver 3.7.1
886 If bonding insists that the link is up when it should not be,
891 setting use_carrier to 0 will cause bonding to revert to the
1013 The default value is layer2. This option was added in bonding
1014 version 2.6.3. In earlier versions of bonding, this parameter
1016 layer2+3 value was added for bonding version 3.2.2.
1028 This option is useful for bonding modes balance-rr (0), active-backup
1034 This option was added for bonding version 3.7.0.
1038 Specifies the number of seconds between instances where the bonding
1047 You can configure bonding using either your distro's network
1051 Recent versions of these packages have support for bonding, while older
1054 We will first describe the options for configuring bonding for
1056 or partial support for bonding, then provide information on enabling
1057 bonding without support from the network initialization scripts (i.e.,
1076 Next, to determine if your installation supports bonding,
1082 sysconfig has support for bonding.
1088 with bonding support, for example, SuSE Linux Enterprise Server 9.
1091 bonding, however, at this writing, the YaST system configuration
1092 front end does not provide any means to work with bonding devices.
1129 it's time to create the configuration file for the bonding device
1131 bonding device to create, starting at 0. The first such file is
1134 of bonding.
1166 a valid choice for a bonding device.
1173 bonding master device. The only useful value is "yes."
1176 instance of the bonding module for this device. Specify the options
1177 for the bonding mode, link monitoring, and so on here. Do not include
1178 the max_bonds bonding parameter; this will confuse the configuration
1179 system if you have multiple bonding devices.
1200 remove the bonding module as part of the network shutdown processing,
1204 Also, at this writing, YaST/YaST2 will not manage bonding
1205 devices (they do not show bonding interfaces on its list of network
1207 change the bonding configuration.
1222 writing, this does not function for bonding devices; the scripts
1231 handling multiple bonding devices. All that is necessary is for each
1232 bonding instance to have an appropriately configured ifcfg-bondX file
1234 instance of bonding, as this will confuse sysconfig. If you require
1235 multiple bonding devices with identical parameters, create multiple
1238 Because the sysconfig scripts supply the bonding module
1246 initscripts with bonding support, for example, Red Hat Enterprise Linux
1248 initialization scripts have knowledge of bonding, and can be configured to
1249 control bonding devices. Note that older versions of the initscripts
1250 package have lower levels of support for bonding; this will be noted where
1276 also depend on the final bonding interface name chosen for your bond.
1278 one for each device, i.e., the first bonding instance is bond0, the
1301 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1307 specified in BONDING_OPTS are identical to the bonding module parameters
1322 your distro) to load the bonding module with your desired options when the
1324 will load the bonding module, and select its options:
1326 alias bond0 bonding
1341 work) have support for assigning IP information to bonding devices via
1344 To configure bonding for DHCP, configure it as described
1353 Enterprise Linux 5 support multiple bonding interfaces by simply
1356 and a bonding driver of version 3.0.0 or later. Other configurations may
1357 not support this method for specifying multiple bonding interfaces; for
1366 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1369 The general method for these systems is to place the bonding
1381 modprobe bonding mode=balance-alb miimon=100
1387 Replace the example bonding module parameters and bond0
1392 ifup and ifdown scripts on the bond devices. To reload the bonding
1402 which only initializes the bonding configuration, then call that
1403 separate script from within boot.local. This allows for bonding to be
1406 To shut down the bonding devices, it is necessary to first
1407 mark the bonding device itself as being down, then remove the
1412 # rmmod bonding
1423 bonding devices with differing options for those systems whose network
1426 If you require multiple bonding devices, but all with the same
1430 To create multiple bonding devices with differing options, it is
1431 preferable to use bonding parameters exported by sysfs, documented in the
1434 For versions of bonding without sysfs support, the only means to
1435 provide multiple instances of bonding with differing options is to load
1436 the bonding driver multiple times. Note that current versions of the
1446 sets of bonding options in ``/etc/modprobe.d/*.conf``, for example::
1448 alias bond0 bonding
1451 alias bond1 bonding
1454 will load the bonding module two times. The first instance is
1460 the above does not work, and the second bonding instance never sees
1464 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1490 bonding is compiled into the kernel.
1493 bonding this way. The examples in this document assume that you
1521 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1527 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1531 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1540 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1547 files located in /sys/class/net/<bond name>/bonding
1561 # echo 6 > /sys/class/net/bond0/bonding/mode
1563 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1571 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1580 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1581 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1589 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1593 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1598 the bonding driver sends learning packets to each slaves peer switch. The
1611 modprobe bonding
1613 echo balance-alb > /sys/class/net/bond0/bonding/mode
1615 echo 100 > /sys/class/net/bond0/bonding/miimon
1616 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1617 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1625 echo active-backup > /sys/class/net/bond1/bonding/mode
1627 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1628 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1629 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1630 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1639 The ifup and ifdown commands on Debian don't support bonding out of
1640 the box. The ifenslave-2.6 package should be installed to provide bonding
1644 Note that ifenslave-2.6 package will load the bonding module and use
1688 When using the bonding driver, the physical port which transmits a frame is
1689 typically selected by the bonding driver, and is not relevant to the user or
1691 the selected bonding mode. On occasion however, it is helpful to direct certain
1700 By default the bonding driver is multiqueue aware and 16 queues are created
1706 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1731 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1757 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1759 slave devices as well as bond devices and the bonding driver will simply act as
1763 This feature first appeared in bonding driver version 3.7.0 and support for
1769 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1781 few bonding parameters:
1795 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1802 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1810 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1819 Each bonding device has a read-only file residing in the
1820 /proc/net/bonding directory. The file contents include information
1821 about the bonding configuration, options and state of each slave.
1823 For example, the contents of /proc/net/bonding/bond0 after the
1844 bonding configuration, state, and version of the bonding driver.
1909 match. For these three modes, the bonding mode really selects a
1919 driver and passing through bonding will be tagged by default. Self
1920 generated packets, for example, bonding's learning packets or ARP
1922 tagged internally by bonding itself. As a result, bonding must
1927 that can do VLAN hardware acceleration offloading, the bonding
1933 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1936 VLAN interfaces *must* be added on top of a bonding interface
1937 only after enslaving at least one slave. The bonding interface has a
1946 top of it. When a new slave is added, the bonding interface will
1957 2. Set the bonding interface's hardware address so that it
1961 underlying device -- i.e. the bonding interface -- to promiscuous
1968 The bonding driver at present supports two schemes for
1973 bonding driver itself, it is not possible to enable both ARP and MII
1998 alias bond0 bonding
2004 alias bond0 bonding
2040 When bonding is configured, it is important that the slave
2042 generally, not have routes at all). For example, suppose the bonding
2055 may bypass the bonding driver (because outgoing traffic to, in this
2083 alias bond0 bonding
2092 happens because bonding is loaded first, then its slave device's
2095 devices, but the bonding configuration tries to enslave eth2 and eth3
2100 add above bonding e1000 tg3
2103 bonding is loaded. This command is fully documented in the
2110 softdep bonding pre: tg3 e1000
2112 This will load tg3 and e1000 modules before loading the bonding one.
2119 By default, bonding enables the use_carrier option, which
2120 instructs bonding to trust the driver to maintain carrier state.
2124 With use_carrier enabled, bonding will always see these links as up,
2147 If running SNMP agents, the bonding driver should be loaded
2153 bonding driver, the interface for the IP address will be associated
2171 This problem is avoided by loading the bonding driver before
2173 loading the bonding driver first, the IP address 192.168.1.1 is
2198 The bonding driver handles promiscuous mode changes to the bonding
2236 access to fail over to. Additionally, the bonding load balance modes
2241 for information on configuring bonding with one peer device.
2246 With multiple switches, the configuration of bonding and the
2274 broadcast modes are the only useful bonding modes when optimizing for
2319 to the logically "interior" ports that bonding is able to monitor via
2361 multiple physical links is, for purposes of configuring bonding, the
2402 although you will have to decide which bonding mode best suits your
2484 the same speed and duplex. Also, as with all bonding load
2489 Additionally, the linux bonding 802.3ad implementation
2578 In actual practice, the bonding mode typically employed in
2596 host in the network is configured with bonding).
2613 value to the updelay bonding module option to delay the use of the
2621 Note that when a bonding interface has no active links, the
2634 Failover may be delayed via the downdelay bonding module option.
2639 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2644 traffic when the bonding device is first used, or after it has been
2663 This is not due to an error in the bonding driver, rather, it
2683 bonding on specific hardware platforms, or for interfacing bonding
2691 On the JS20 blades, the bonding driver supports only
2709 switch). Some bonding modes require a specific BladeCenter internal
2737 appear to bonding as either a single switch topology (all PMs) or as a
2755 bonding device (i.e., the network must converge at some point outside
2782 bonding driver.
2786 avoid fail-over delay issues when using bonding.
2795 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2805 Starting with version 3.2.1, bonding also supports Infiniband
2808 3. How many bonding devices can I have?
2813 4. How many slaves can a bonding device have?
2837 If no link monitoring is configured, the bonding driver will
2841 depends upon the bonding mode and network configuration.
2843 6. Can bonding be used for High Availability?
2869 8. Where does a bonding device get its MAC address from?
2873 the fail_over_mac option is enabled, the bonding device's MAC address is
2877 ifconfig or ip link), the MAC address of the bonding device is taken from
2880 the bonding device is brought down or reconfigured.
2892 # ifconfig bond0 down ; modprobe -r bonding
2900 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2907 The latest version of the bonding driver can be found in the latest
2911 source (named Documentation/networking/bonding.rst).
2913 Discussions regarding the development of the bonding driver take place