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
790 This option was added for bonding version 3.6.0.
811 disables it. This option was added in bonding driver 3.7.1
832 If bonding insists that the link is up when it should not be,
837 setting use_carrier to 0 will cause bonding to revert to the
946 The default value is layer2. This option was added in bonding
947 version 2.6.3. In earlier versions of bonding, this parameter
949 layer2+3 value was added for bonding version 3.2.2.
961 This option is useful for bonding modes balance-rr (0), active-backup
967 This option was added for bonding version 3.7.0.
971 Specifies the number of seconds between instances where the bonding
980 You can configure bonding using either your distro's network
984 Recent versions of these packages have support for bonding, while older
987 We will first describe the options for configuring bonding for
989 or partial support for bonding, then provide information on enabling
990 bonding without support from the network initialization scripts (i.e.,
1009 Next, to determine if your installation supports bonding,
1015 sysconfig has support for bonding.
1021 with bonding support, for example, SuSE Linux Enterprise Server 9.
1024 bonding, however, at this writing, the YaST system configuration
1025 front end does not provide any means to work with bonding devices.
1062 it's time to create the configuration file for the bonding device
1064 bonding device to create, starting at 0. The first such file is
1067 of bonding.
1098 a valid choice for a bonding device.
1103 bonding master device. The only useful value is "yes."
1106 instance of the bonding module for this device. Specify the options
1107 for the bonding mode, link monitoring, and so on here. Do not include
1108 the max_bonds bonding parameter; this will confuse the configuration
1109 system if you have multiple bonding devices.
1130 remove the bonding module as part of the network shutdown processing,
1134 Also, at this writing, YaST/YaST2 will not manage bonding
1135 devices (they do not show bonding interfaces on its list of network
1137 change the bonding configuration.
1152 writing, this does not function for bonding devices; the scripts
1161 handling multiple bonding devices. All that is necessary is for each
1162 bonding instance to have an appropriately configured ifcfg-bondX file
1164 instance of bonding, as this will confuse sysconfig. If you require
1165 multiple bonding devices with identical parameters, create multiple
1168 Because the sysconfig scripts supply the bonding module
1176 initscripts with bonding support, for example, Red Hat Enterprise Linux
1178 initialization scripts have knowledge of bonding, and can be configured to
1179 control bonding devices. Note that older versions of the initscripts
1180 package have lower levels of support for bonding; this will be noted where
1206 also depend on the final bonding interface name chosen for your bond.
1208 one for each device, i.e., the first bonding instance is bond0, the
1231 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1237 specified in BONDING_OPTS are identical to the bonding module parameters
1251 your distro) to load the bonding module with your desired options when the
1253 will load the bonding module, and select its options:
1255 alias bond0 bonding
1270 work) have support for assigning IP information to bonding devices via
1273 To configure bonding for DHCP, configure it as described
1282 Enterprise Linux 5 support multiple bonding interfaces by simply
1285 and a bonding driver of version 3.0.0 or later. Other configurations may
1286 not support this method for specifying multiple bonding interfaces; for
1295 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1298 The general method for these systems is to place the bonding
1310 modprobe bonding mode=balance-alb miimon=100
1316 Replace the example bonding module parameters and bond0
1321 ifup and ifdown scripts on the bond devices. To reload the bonding
1331 which only initializes the bonding configuration, then call that
1332 separate script from within boot.local. This allows for bonding to be
1335 To shut down the bonding devices, it is necessary to first
1336 mark the bonding device itself as being down, then remove the
1341 # rmmod bonding
1352 bonding devices with differing options for those systems whose network
1355 If you require multiple bonding devices, but all with the same
1359 To create multiple bonding devices with differing options, it is
1360 preferable to use bonding parameters exported by sysfs, documented in the
1363 For versions of bonding without sysfs support, the only means to
1364 provide multiple instances of bonding with differing options is to load
1365 the bonding driver multiple times. Note that current versions of the
1375 sets of bonding options in /etc/modprobe.d/*.conf, for example:
1377 alias bond0 bonding
1380 alias bond1 bonding
1383 will load the bonding module two times. The first instance is
1389 the above does not work, and the second bonding instance never sees
1393 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1419 bonding is compiled into the kernel.
1422 bonding this way. The examples in this document assume that you
1445 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1450 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1453 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1462 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1469 files located in /sys/class/net/<bond name>/bonding
1482 # echo 6 > /sys/class/net/bond0/bonding/mode
1484 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1489 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1494 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1495 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1499 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1502 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1504 the bonding driver sends learning packets to each slaves peer switch. The
1517 modprobe bonding
1519 echo balance-alb > /sys/class/net/bond0/bonding/mode
1521 echo 100 > /sys/class/net/bond0/bonding/miimon
1522 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1523 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1531 echo active-backup > /sys/class/net/bond1/bonding/mode
1533 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1534 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1535 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1536 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1545 The ifup and ifdown commands on Debian don't support bonding out of
1546 the box. The ifenslave-2.6 package should be installed to provide bonding
1550 Note that ifenslave-2.6 package will load the bonding module and use
1594 When using the bonding driver, the physical port which transmits a frame is
1595 typically selected by the bonding driver, and is not relevant to the user or
1597 the selected bonding mode. On occasion however, it is helpful to direct certain
1606 By default the bonding driver is multiqueue aware and 16 queues are created
1612 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1637 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1663 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1665 slave devices as well as bond devices and the bonding driver will simply act as
1669 This feature first appeared in bonding driver version 3.7.0 and support for
1675 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1687 few bonding parameters:
1701 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1708 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1716 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1725 Each bonding device has a read-only file residing in the
1726 /proc/net/bonding directory. The file contents include information
1727 about the bonding configuration, options and state of each slave.
1729 For example, the contents of /proc/net/bonding/bond0 after the
1750 bonding configuration, state, and version of the bonding driver.
1815 match. For these three modes, the bonding mode really selects a
1825 driver and passing through bonding will be tagged by default. Self
1826 generated packets, for example, bonding's learning packets or ARP
1828 tagged internally by bonding itself. As a result, bonding must
1833 that can do VLAN hardware acceleration offloading, the bonding
1839 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1842 VLAN interfaces *must* be added on top of a bonding interface
1843 only after enslaving at least one slave. The bonding interface has a
1852 top of it. When a new slave is added, the bonding interface will
1863 2. Set the bonding interface's hardware address so that it
1867 underlying device -- i.e. the bonding interface -- to promiscuous
1874 The bonding driver at present supports two schemes for
1879 bonding driver itself, it is not possible to enable both ARP and MII
1913 alias bond0 bonding
1919 alias bond0 bonding
1955 When bonding is configured, it is important that the slave
1957 generally, not have routes at all). For example, suppose the bonding
1970 may bypass the bonding driver (because outgoing traffic to, in this
1998 alias bond0 bonding
2007 happens because bonding is loaded first, then its slave device's
2010 devices, but the bonding configuration tries to enslave eth2 and eth3
2015 add above bonding e1000 tg3
2018 bonding is loaded. This command is fully documented in the
2025 softdep bonding pre: tg3 e1000
2027 This will load tg3 and e1000 modules before loading the bonding one.
2034 By default, bonding enables the use_carrier option, which
2035 instructs bonding to trust the driver to maintain carrier state.
2039 With use_carrier enabled, bonding will always see these links as up,
2062 If running SNMP agents, the bonding driver should be loaded
2068 bonding driver, the interface for the IP address will be associated
2084 This problem is avoided by loading the bonding driver before
2086 loading the bonding driver first, the IP address 192.168.1.1 is
2111 The bonding driver handles promiscuous mode changes to the bonding
2149 access to fail over to. Additionally, the bonding load balance modes
2154 for information on configuring bonding with one peer device.
2159 With multiple switches, the configuration of bonding and the
2187 broadcast modes are the only useful bonding modes when optimizing for
2230 to the logically "interior" ports that bonding is able to monitor via
2272 multiple physical links is, for purposes of configuring bonding, the
2313 although you will have to decide which bonding mode best suits your
2390 the same speed and duplex. Also, as with all bonding load
2395 Additionally, the linux bonding 802.3ad implementation
2482 In actual practice, the bonding mode typically employed in
2500 host in the network is configured with bonding).
2517 value to the updelay bonding module option to delay the use of the
2525 Note that when a bonding interface has no active links, the
2538 Failover may be delayed via the downdelay bonding module option.
2543 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2548 traffic when the bonding device is first used, or after it has been
2567 This is not due to an error in the bonding driver, rather, it
2587 bonding on specific hardware platforms, or for interfacing bonding
2595 On the JS20 blades, the bonding driver supports only
2613 switch). Some bonding modes require a specific BladeCenter internal
2641 appear to bonding as either a single switch topology (all PMs) or as a
2659 bonding device (i.e., the network must converge at some point outside
2686 bonding driver.
2690 avoid fail-over delay issues when using bonding.
2698 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2707 Starting with version 3.2.1, bonding also supports Infiniband
2710 3. How many bonding devices can I have?
2714 4. How many slaves can a bonding device have?
2736 If no link monitoring is configured, the bonding driver will
2740 depends upon the bonding mode and network configuration.
2742 6. Can bonding be used for High Availability?
2766 8. Where does a bonding device get its MAC address from?
2769 the fail_over_mac option is enabled, the bonding device's MAC address is
2773 ifconfig or ip link), the MAC address of the bonding device is taken from
2776 the bonding device is brought down or reconfigured.
2788 # ifconfig bond0 down ; modprobe -r bonding
2796 from the bond (`ifenslave -d bond0 eth0'). The bonding driver will
2803 The latest version of the bonding driver can be found in the latest
2807 source (named Documentation/networking/bonding.txt).
2809 Discussions regarding the usage of the bonding driver take place on the
2810 bonding-devel mailing list, hosted at sourceforge.net. If you have questions or
2813 bonding-devel@lists.sourceforge.net
2818 https://lists.sourceforge.net/lists/listinfo/bonding-devel
2820 Discussions regarding the development of the bonding driver take place