Lines Matching refs:bonding
21 The Linux bonding driver provides a method for aggregating
27 The bonding driver originally came from Donald Becker's
106 Most popular distro kernels ship with the bonding driver
108 have need to compile bonding from source (e.g., configuring and
112 1.1 Configure and build the kernel with bonding
115 The current version of the bonding driver is available in the
116 drivers/net/bonding subdirectory of the most recent kernel source
124 to the driver or configure more than one bonding device.
131 It is recommended to configure bonding via iproute2 (netlink)
137 Options for the bonding driver are supplied as parameters to the
138 bonding module at load time, or are specified via sysfs.
145 Details on bonding support for sysfs is provided in the
148 The available bonding driver parameters are listed below. If a
151 run in a separate window to watch for bonding driver error messages.
221 This option was added in bonding version 3.4.0.
228 Normally, bonding will drop duplicate frames (received on inactive
242 bonding mode, and the state of the slave). Regular traffic is
326 bonding to decide which slaves are more likely to work in case of
331 bonding hosts are concurrently issuing ARPs to one or more targets
334 generated by the multiple bonding instances will fool the standard
338 bonding.
358 This option was added in bonding version 3.1.0.
400 bonding to set all slaves of an active-backup bond to
456 This option was added in bonding version 3.2.0. The "follow"
457 policy was added in bonding version 3.3.0.
475 Specifies the number of bonding devices to create for this
476 instance of the bonding driver. E.g., if max_bonds is 3, and
477 the bonding driver is not already loaded, then bond0, bond1
479 a value of 0 will load bonding, but will not create any devices.
510 Specifies one of the bonding policies. The default is
528 In bonding version 2.6.2 or later, when a failover
529 occurs in active-backup mode, bonding will issue one
531 One gratuitous ARP is issued for the bonding master
587 Adaptive transmit load balancing: channel bonding that
613 The bonding driver intercepts the ARP Replies sent by
622 Request the bonding driver copies and saves the peer's
625 retrieved and the bonding driver initiates an ARP
672 bonding device and each VLAN sub-device. This is repeated at
678 bonding versions 3.3.0 and 3.4.0 respectively.
680 From Linux 3.0 and bonding version 3.7.1, these notifications
743 This option was added for bonding version 3.6.0.
764 disables it. This option was added in bonding driver 3.7.1
785 If bonding insists that the link is up when it should not be,
790 setting use_carrier to 0 will cause bonding to revert to the
899 The default value is layer2. This option was added in bonding
900 version 2.6.3. In earlier versions of bonding, this parameter
902 layer2+3 value was added for bonding version 3.2.2.
914 This option is useful for bonding modes balance-rr (0), active-backup
920 This option was added for bonding version 3.7.0.
924 Specifies the number of seconds between instances where the bonding
933 You can configure bonding using either your distro's network
937 Recent versions of these packages have support for bonding, while older
940 We will first describe the options for configuring bonding for
942 or partial support for bonding, then provide information on enabling
943 bonding without support from the network initialization scripts (i.e.,
962 Next, to determine if your installation supports bonding,
968 sysconfig has support for bonding.
974 with bonding support, for example, SuSE Linux Enterprise Server 9.
977 bonding, however, at this writing, the YaST system configuration
978 front end does not provide any means to work with bonding devices.
1015 it's time to create the configuration file for the bonding device
1017 bonding device to create, starting at 0. The first such file is
1020 of bonding.
1051 a valid choice for a bonding device.
1056 bonding master device. The only useful value is "yes."
1059 instance of the bonding module for this device. Specify the options
1060 for the bonding mode, link monitoring, and so on here. Do not include
1061 the max_bonds bonding parameter; this will confuse the configuration
1062 system if you have multiple bonding devices.
1083 remove the bonding module as part of the network shutdown processing,
1087 Also, at this writing, YaST/YaST2 will not manage bonding
1088 devices (they do not show bonding interfaces on its list of network
1090 change the bonding configuration.
1105 writing, this does not function for bonding devices; the scripts
1114 handling multiple bonding devices. All that is necessary is for each
1115 bonding instance to have an appropriately configured ifcfg-bondX file
1117 instance of bonding, as this will confuse sysconfig. If you require
1118 multiple bonding devices with identical parameters, create multiple
1121 Because the sysconfig scripts supply the bonding module
1129 initscripts with bonding support, for example, Red Hat Enterprise Linux
1131 initialization scripts have knowledge of bonding, and can be configured to
1132 control bonding devices. Note that older versions of the initscripts
1133 package have lower levels of support for bonding; this will be noted where
1159 also depend on the final bonding interface name chosen for your bond.
1161 one for each device, i.e., the first bonding instance is bond0, the
1184 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1190 specified in BONDING_OPTS are identical to the bonding module parameters
1204 your distro) to load the bonding module with your desired options when the
1206 will load the bonding module, and select its options:
1208 alias bond0 bonding
1223 work) have support for assigning IP information to bonding devices via
1226 To configure bonding for DHCP, configure it as described
1235 Enterprise Linux 5 support multiple bonding interfaces by simply
1238 and a bonding driver of version 3.0.0 or later. Other configurations may
1239 not support this method for specifying multiple bonding interfaces; for
1248 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1251 The general method for these systems is to place the bonding
1263 modprobe bonding mode=balance-alb miimon=100
1269 Replace the example bonding module parameters and bond0
1274 ifup and ifdown scripts on the bond devices. To reload the bonding
1284 which only initializes the bonding configuration, then call that
1285 separate script from within boot.local. This allows for bonding to be
1288 To shut down the bonding devices, it is necessary to first
1289 mark the bonding device itself as being down, then remove the
1294 # rmmod bonding
1305 bonding devices with differing options for those systems whose network
1308 If you require multiple bonding devices, but all with the same
1312 To create multiple bonding devices with differing options, it is
1313 preferable to use bonding parameters exported by sysfs, documented in the
1316 For versions of bonding without sysfs support, the only means to
1317 provide multiple instances of bonding with differing options is to load
1318 the bonding driver multiple times. Note that current versions of the
1328 sets of bonding options in /etc/modprobe.d/*.conf, for example:
1330 alias bond0 bonding
1333 alias bond1 bonding
1336 will load the bonding module two times. The first instance is
1342 the above does not work, and the second bonding instance never sees
1346 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1372 bonding is compiled into the kernel.
1375 bonding this way. The examples in this document assume that you
1398 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1403 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1406 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1415 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1422 files located in /sys/class/net/<bond name>/bonding
1435 # echo 6 > /sys/class/net/bond0/bonding/mode
1437 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1442 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1447 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1448 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1452 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1455 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1457 the bonding driver sends learning packets to each slaves peer switch. The
1470 modprobe bonding
1472 echo balance-alb > /sys/class/net/bond0/bonding/mode
1474 echo 100 > /sys/class/net/bond0/bonding/miimon
1475 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1476 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1484 echo active-backup > /sys/class/net/bond1/bonding/mode
1486 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1487 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1488 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1489 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1498 The ifup and ifdown commands on Debian don't support bonding out of
1499 the box. The ifenslave-2.6 package should be installed to provide bonding
1503 Note that ifenslave-2.6 package will load the bonding module and use
1547 When using the bonding driver, the physical port which transmits a frame is
1548 typically selected by the bonding driver, and is not relevant to the user or
1550 the selected bonding mode. On occasion however, it is helpful to direct certain
1559 By default the bonding driver is multiqueue aware and 16 queues are created
1565 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1590 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1616 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1618 slave devices as well as bond devices and the bonding driver will simply act as
1622 This feature first appeared in bonding driver version 3.7.0 and support for
1631 Each bonding device has a read-only file residing in the
1632 /proc/net/bonding directory. The file contents include information
1633 about the bonding configuration, options and state of each slave.
1635 For example, the contents of /proc/net/bonding/bond0 after the
1656 bonding configuration, state, and version of the bonding driver.
1721 match. For these three modes, the bonding mode really selects a
1731 driver and passing through bonding will be tagged by default. Self
1732 generated packets, for example, bonding's learning packets or ARP
1734 tagged internally by bonding itself. As a result, bonding must
1739 that can do VLAN hardware acceleration offloading, the bonding
1745 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1748 VLAN interfaces *must* be added on top of a bonding interface
1749 only after enslaving at least one slave. The bonding interface has a
1758 top of it. When a new slave is added, the bonding interface will
1769 2. Set the bonding interface's hardware address so that it
1773 underlying device -- i.e. the bonding interface -- to promiscuous
1780 The bonding driver at present supports two schemes for
1785 bonding driver itself, it is not possible to enable both ARP and MII
1819 alias bond0 bonding
1825 alias bond0 bonding
1861 When bonding is configured, it is important that the slave
1863 generally, not have routes at all). For example, suppose the bonding
1876 may bypass the bonding driver (because outgoing traffic to, in this
1904 alias bond0 bonding
1913 happens because bonding is loaded first, then its slave device's
1916 devices, but the bonding configuration tries to enslave eth2 and eth3
1921 add above bonding e1000 tg3
1924 bonding is loaded. This command is fully documented in the
1931 softdep bonding pre: tg3 e1000
1933 This will load tg3 and e1000 modules before loading the bonding one.
1940 By default, bonding enables the use_carrier option, which
1941 instructs bonding to trust the driver to maintain carrier state.
1945 With use_carrier enabled, bonding will always see these links as up,
1968 If running SNMP agents, the bonding driver should be loaded
1974 bonding driver, the interface for the IP address will be associated
1990 This problem is avoided by loading the bonding driver before
1992 loading the bonding driver first, the IP address 192.168.1.1 is
2017 The bonding driver handles promiscuous mode changes to the bonding
2055 access to fail over to. Additionally, the bonding load balance modes
2060 for information on configuring bonding with one peer device.
2065 With multiple switches, the configuration of bonding and the
2093 broadcast modes are the only useful bonding modes when optimizing for
2136 to the logically "interior" ports that bonding is able to monitor via
2178 multiple physical links is, for purposes of configuring bonding, the
2219 although you will have to decide which bonding mode best suits your
2296 the same speed and duplex. Also, as with all bonding load
2301 Additionally, the linux bonding 802.3ad implementation
2388 In actual practice, the bonding mode typically employed in
2406 host in the network is configured with bonding).
2423 value to the updelay bonding module option to delay the use of the
2431 Note that when a bonding interface has no active links, the
2444 Failover may be delayed via the downdelay bonding module option.
2449 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2454 traffic when the bonding device is first used, or after it has been
2473 This is not due to an error in the bonding driver, rather, it
2493 bonding on specific hardware platforms, or for interfacing bonding
2501 On the JS20 blades, the bonding driver supports only
2519 switch). Some bonding modes require a specific BladeCenter internal
2547 appear to bonding as either a single switch topology (all PMs) or as a
2565 bonding device (i.e., the network must converge at some point outside
2592 bonding driver.
2596 avoid fail-over delay issues when using bonding.
2604 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2613 Starting with version 3.2.1, bonding also supports Infiniband
2616 3. How many bonding devices can I have?
2620 4. How many slaves can a bonding device have?
2642 If no link monitoring is configured, the bonding driver will
2646 depends upon the bonding mode and network configuration.
2648 6. Can bonding be used for High Availability?
2672 8. Where does a bonding device get its MAC address from?
2675 the fail_over_mac option is enabled, the bonding device's MAC address is
2679 ifconfig or ip link), the MAC address of the bonding device is taken from
2682 the bonding device is brought down or reconfigured.
2694 # ifconfig bond0 down ; modprobe -r bonding
2702 from the bond (`ifenslave -d bond0 eth0'). The bonding driver will
2709 The latest version of the bonding driver can be found in the latest
2713 source (named Documentation/networking/bonding.txt).
2715 Discussions regarding the usage of the bonding driver take place on the
2716 bonding-devel mailing list, hosted at sourceforge.net. If you have questions or
2719 bonding-devel@lists.sourceforge.net
2724 https://lists.sourceforge.net/lists/listinfo/bonding-devel
2726 Discussions regarding the development of the bonding driver take place