Lines Matching refs:bonding
21 The Linux bonding driver provides a method for aggregating
27 The bonding driver originally came from Donald Becker's
107 Most popular distro kernels ship with the bonding driver
109 have need to compile bonding from source (e.g., configuring and
113 1.1 Configure and build the kernel with bonding
116 The current version of the bonding driver is available in the
117 drivers/net/bonding subdirectory of the most recent kernel source
125 to the driver or configure more than one bonding device.
132 It is recommended to configure bonding via iproute2 (netlink)
138 Options for the bonding driver are supplied as parameters to the
139 bonding module at load time, or are specified via sysfs.
146 Details on bonding support for sysfs is provided in the
149 The available bonding driver parameters are listed below. If a
152 run in a separate window to watch for bonding driver error messages.
243 This option was added in bonding version 3.4.0.
265 Normally, bonding will drop duplicate frames (received on inactive
279 bonding mode, and the state of the slave). Regular traffic is
363 bonding to decide which slaves are more likely to work in case of
368 bonding hosts are concurrently issuing ARPs to one or more targets
371 generated by the multiple bonding instances will fool the standard
375 bonding.
395 This option was added in bonding version 3.1.0.
437 bonding to set all slaves of an active-backup bond to
493 This option was added in bonding version 3.2.0. The "follow"
494 policy was added in bonding version 3.3.0.
512 Specifies the number of bonding devices to create for this
513 instance of the bonding driver. E.g., if max_bonds is 3, and
514 the bonding driver is not already loaded, then bond0, bond1
516 a value of 0 will load bonding, but will not create any devices.
547 Specifies one of the bonding policies. The default is
565 In bonding version 2.6.2 or later, when a failover
566 occurs in active-backup mode, bonding will issue one
568 One gratuitous ARP is issued for the bonding master
624 Adaptive transmit load balancing: channel bonding that
650 The bonding driver intercepts the ARP Replies sent by
659 Request the bonding driver copies and saves the peer's
662 retrieved and the bonding driver initiates an ARP
709 bonding device and each VLAN sub-device. This is repeated at
715 bonding versions 3.3.0 and 3.4.0 respectively.
717 From Linux 3.0 and bonding version 3.7.1, these notifications
780 This option was added for bonding version 3.6.0.
801 disables it. This option was added in bonding driver 3.7.1
822 If bonding insists that the link is up when it should not be,
827 setting use_carrier to 0 will cause bonding to revert to the
936 The default value is layer2. This option was added in bonding
937 version 2.6.3. In earlier versions of bonding, this parameter
939 layer2+3 value was added for bonding version 3.2.2.
951 This option is useful for bonding modes balance-rr (0), active-backup
957 This option was added for bonding version 3.7.0.
961 Specifies the number of seconds between instances where the bonding
970 You can configure bonding using either your distro's network
974 Recent versions of these packages have support for bonding, while older
977 We will first describe the options for configuring bonding for
979 or partial support for bonding, then provide information on enabling
980 bonding without support from the network initialization scripts (i.e.,
999 Next, to determine if your installation supports bonding,
1005 sysconfig has support for bonding.
1011 with bonding support, for example, SuSE Linux Enterprise Server 9.
1014 bonding, however, at this writing, the YaST system configuration
1015 front end does not provide any means to work with bonding devices.
1052 it's time to create the configuration file for the bonding device
1054 bonding device to create, starting at 0. The first such file is
1057 of bonding.
1088 a valid choice for a bonding device.
1093 bonding master device. The only useful value is "yes."
1096 instance of the bonding module for this device. Specify the options
1097 for the bonding mode, link monitoring, and so on here. Do not include
1098 the max_bonds bonding parameter; this will confuse the configuration
1099 system if you have multiple bonding devices.
1120 remove the bonding module as part of the network shutdown processing,
1124 Also, at this writing, YaST/YaST2 will not manage bonding
1125 devices (they do not show bonding interfaces on its list of network
1127 change the bonding configuration.
1142 writing, this does not function for bonding devices; the scripts
1151 handling multiple bonding devices. All that is necessary is for each
1152 bonding instance to have an appropriately configured ifcfg-bondX file
1154 instance of bonding, as this will confuse sysconfig. If you require
1155 multiple bonding devices with identical parameters, create multiple
1158 Because the sysconfig scripts supply the bonding module
1166 initscripts with bonding support, for example, Red Hat Enterprise Linux
1168 initialization scripts have knowledge of bonding, and can be configured to
1169 control bonding devices. Note that older versions of the initscripts
1170 package have lower levels of support for bonding; this will be noted where
1196 also depend on the final bonding interface name chosen for your bond.
1198 one for each device, i.e., the first bonding instance is bond0, the
1221 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1227 specified in BONDING_OPTS are identical to the bonding module parameters
1241 your distro) to load the bonding module with your desired options when the
1243 will load the bonding module, and select its options:
1245 alias bond0 bonding
1260 work) have support for assigning IP information to bonding devices via
1263 To configure bonding for DHCP, configure it as described
1272 Enterprise Linux 5 support multiple bonding interfaces by simply
1275 and a bonding driver of version 3.0.0 or later. Other configurations may
1276 not support this method for specifying multiple bonding interfaces; for
1285 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1288 The general method for these systems is to place the bonding
1300 modprobe bonding mode=balance-alb miimon=100
1306 Replace the example bonding module parameters and bond0
1311 ifup and ifdown scripts on the bond devices. To reload the bonding
1321 which only initializes the bonding configuration, then call that
1322 separate script from within boot.local. This allows for bonding to be
1325 To shut down the bonding devices, it is necessary to first
1326 mark the bonding device itself as being down, then remove the
1331 # rmmod bonding
1342 bonding devices with differing options for those systems whose network
1345 If you require multiple bonding devices, but all with the same
1349 To create multiple bonding devices with differing options, it is
1350 preferable to use bonding parameters exported by sysfs, documented in the
1353 For versions of bonding without sysfs support, the only means to
1354 provide multiple instances of bonding with differing options is to load
1355 the bonding driver multiple times. Note that current versions of the
1365 sets of bonding options in /etc/modprobe.d/*.conf, for example:
1367 alias bond0 bonding
1370 alias bond1 bonding
1373 will load the bonding module two times. The first instance is
1379 the above does not work, and the second bonding instance never sees
1383 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1409 bonding is compiled into the kernel.
1412 bonding this way. The examples in this document assume that you
1435 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1440 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1443 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1452 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1459 files located in /sys/class/net/<bond name>/bonding
1472 # echo 6 > /sys/class/net/bond0/bonding/mode
1474 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1479 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1484 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1485 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1489 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1492 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1494 the bonding driver sends learning packets to each slaves peer switch. The
1507 modprobe bonding
1509 echo balance-alb > /sys/class/net/bond0/bonding/mode
1511 echo 100 > /sys/class/net/bond0/bonding/miimon
1512 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1513 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1521 echo active-backup > /sys/class/net/bond1/bonding/mode
1523 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1524 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1525 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1526 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1535 The ifup and ifdown commands on Debian don't support bonding out of
1536 the box. The ifenslave-2.6 package should be installed to provide bonding
1540 Note that ifenslave-2.6 package will load the bonding module and use
1584 When using the bonding driver, the physical port which transmits a frame is
1585 typically selected by the bonding driver, and is not relevant to the user or
1587 the selected bonding mode. On occasion however, it is helpful to direct certain
1596 By default the bonding driver is multiqueue aware and 16 queues are created
1602 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1627 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1653 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1655 slave devices as well as bond devices and the bonding driver will simply act as
1659 This feature first appeared in bonding driver version 3.7.0 and support for
1665 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1677 few bonding parameters:
1691 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1698 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1706 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1715 Each bonding device has a read-only file residing in the
1716 /proc/net/bonding directory. The file contents include information
1717 about the bonding configuration, options and state of each slave.
1719 For example, the contents of /proc/net/bonding/bond0 after the
1740 bonding configuration, state, and version of the bonding driver.
1805 match. For these three modes, the bonding mode really selects a
1815 driver and passing through bonding will be tagged by default. Self
1816 generated packets, for example, bonding's learning packets or ARP
1818 tagged internally by bonding itself. As a result, bonding must
1823 that can do VLAN hardware acceleration offloading, the bonding
1829 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1832 VLAN interfaces *must* be added on top of a bonding interface
1833 only after enslaving at least one slave. The bonding interface has a
1842 top of it. When a new slave is added, the bonding interface will
1853 2. Set the bonding interface's hardware address so that it
1857 underlying device -- i.e. the bonding interface -- to promiscuous
1864 The bonding driver at present supports two schemes for
1869 bonding driver itself, it is not possible to enable both ARP and MII
1903 alias bond0 bonding
1909 alias bond0 bonding
1945 When bonding is configured, it is important that the slave
1947 generally, not have routes at all). For example, suppose the bonding
1960 may bypass the bonding driver (because outgoing traffic to, in this
1988 alias bond0 bonding
1997 happens because bonding is loaded first, then its slave device's
2000 devices, but the bonding configuration tries to enslave eth2 and eth3
2005 add above bonding e1000 tg3
2008 bonding is loaded. This command is fully documented in the
2015 softdep bonding pre: tg3 e1000
2017 This will load tg3 and e1000 modules before loading the bonding one.
2024 By default, bonding enables the use_carrier option, which
2025 instructs bonding to trust the driver to maintain carrier state.
2029 With use_carrier enabled, bonding will always see these links as up,
2052 If running SNMP agents, the bonding driver should be loaded
2058 bonding driver, the interface for the IP address will be associated
2074 This problem is avoided by loading the bonding driver before
2076 loading the bonding driver first, the IP address 192.168.1.1 is
2101 The bonding driver handles promiscuous mode changes to the bonding
2139 access to fail over to. Additionally, the bonding load balance modes
2144 for information on configuring bonding with one peer device.
2149 With multiple switches, the configuration of bonding and the
2177 broadcast modes are the only useful bonding modes when optimizing for
2220 to the logically "interior" ports that bonding is able to monitor via
2262 multiple physical links is, for purposes of configuring bonding, the
2303 although you will have to decide which bonding mode best suits your
2380 the same speed and duplex. Also, as with all bonding load
2385 Additionally, the linux bonding 802.3ad implementation
2472 In actual practice, the bonding mode typically employed in
2490 host in the network is configured with bonding).
2507 value to the updelay bonding module option to delay the use of the
2515 Note that when a bonding interface has no active links, the
2528 Failover may be delayed via the downdelay bonding module option.
2533 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2538 traffic when the bonding device is first used, or after it has been
2557 This is not due to an error in the bonding driver, rather, it
2577 bonding on specific hardware platforms, or for interfacing bonding
2585 On the JS20 blades, the bonding driver supports only
2603 switch). Some bonding modes require a specific BladeCenter internal
2631 appear to bonding as either a single switch topology (all PMs) or as a
2649 bonding device (i.e., the network must converge at some point outside
2676 bonding driver.
2680 avoid fail-over delay issues when using bonding.
2688 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2697 Starting with version 3.2.1, bonding also supports Infiniband
2700 3. How many bonding devices can I have?
2704 4. How many slaves can a bonding device have?
2726 If no link monitoring is configured, the bonding driver will
2730 depends upon the bonding mode and network configuration.
2732 6. Can bonding be used for High Availability?
2756 8. Where does a bonding device get its MAC address from?
2759 the fail_over_mac option is enabled, the bonding device's MAC address is
2763 ifconfig or ip link), the MAC address of the bonding device is taken from
2766 the bonding device is brought down or reconfigured.
2778 # ifconfig bond0 down ; modprobe -r bonding
2786 from the bond (`ifenslave -d bond0 eth0'). The bonding driver will
2793 The latest version of the bonding driver can be found in the latest
2797 source (named Documentation/networking/bonding.txt).
2799 Discussions regarding the usage of the bonding driver take place on the
2800 bonding-devel mailing list, hosted at sourceforge.net. If you have questions or
2803 bonding-devel@lists.sourceforge.net
2808 https://lists.sourceforge.net/lists/listinfo/bonding-devel
2810 Discussions regarding the development of the bonding driver take place