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
372 bonding to decide which slaves are more likely to work in case of
377 bonding hosts are concurrently issuing ARPs to one or more targets
380 generated by the multiple bonding instances will fool the standard
384 bonding.
404 This option was added in bonding version 3.1.0.
446 bonding to set all slaves of an active-backup bond to
502 This option was added in bonding version 3.2.0. The "follow"
503 policy was added in bonding version 3.3.0.
521 Specifies the number of bonding devices to create for this
522 instance of the bonding driver. E.g., if max_bonds is 3, and
523 the bonding driver is not already loaded, then bond0, bond1
525 a value of 0 will load bonding, but will not create any devices.
556 Specifies one of the bonding policies. The default is
574 In bonding version 2.6.2 or later, when a failover
575 occurs in active-backup mode, bonding will issue one
577 One gratuitous ARP is issued for the bonding master
633 Adaptive transmit load balancing: channel bonding that
659 The bonding driver intercepts the ARP Replies sent by
668 Request the bonding driver copies and saves the peer's
671 retrieved and the bonding driver initiates an ARP
718 bonding device and each VLAN sub-device. This is repeated at
724 bonding versions 3.3.0 and 3.4.0 respectively.
726 From Linux 3.0 and bonding version 3.7.1, these notifications
799 This option was added for bonding version 3.6.0.
820 disables it. This option was added in bonding driver 3.7.1
841 If bonding insists that the link is up when it should not be,
846 setting use_carrier to 0 will cause bonding to revert to the
955 The default value is layer2. This option was added in bonding
956 version 2.6.3. In earlier versions of bonding, this parameter
958 layer2+3 value was added for bonding version 3.2.2.
970 This option is useful for bonding modes balance-rr (0), active-backup
976 This option was added for bonding version 3.7.0.
980 Specifies the number of seconds between instances where the bonding
989 You can configure bonding using either your distro's network
993 Recent versions of these packages have support for bonding, while older
996 We will first describe the options for configuring bonding for
998 or partial support for bonding, then provide information on enabling
999 bonding without support from the network initialization scripts (i.e.,
1018 Next, to determine if your installation supports bonding,
1024 sysconfig has support for bonding.
1030 with bonding support, for example, SuSE Linux Enterprise Server 9.
1033 bonding, however, at this writing, the YaST system configuration
1034 front end does not provide any means to work with bonding devices.
1071 it's time to create the configuration file for the bonding device
1073 bonding device to create, starting at 0. The first such file is
1076 of bonding.
1108 a valid choice for a bonding device.
1115 bonding master device. The only useful value is "yes."
1118 instance of the bonding module for this device. Specify the options
1119 for the bonding mode, link monitoring, and so on here. Do not include
1120 the max_bonds bonding parameter; this will confuse the configuration
1121 system if you have multiple bonding devices.
1142 remove the bonding module as part of the network shutdown processing,
1146 Also, at this writing, YaST/YaST2 will not manage bonding
1147 devices (they do not show bonding interfaces on its list of network
1149 change the bonding configuration.
1164 writing, this does not function for bonding devices; the scripts
1173 handling multiple bonding devices. All that is necessary is for each
1174 bonding instance to have an appropriately configured ifcfg-bondX file
1176 instance of bonding, as this will confuse sysconfig. If you require
1177 multiple bonding devices with identical parameters, create multiple
1180 Because the sysconfig scripts supply the bonding module
1188 initscripts with bonding support, for example, Red Hat Enterprise Linux
1190 initialization scripts have knowledge of bonding, and can be configured to
1191 control bonding devices. Note that older versions of the initscripts
1192 package have lower levels of support for bonding; this will be noted where
1218 also depend on the final bonding interface name chosen for your bond.
1220 one for each device, i.e., the first bonding instance is bond0, the
1243 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1249 specified in BONDING_OPTS are identical to the bonding module parameters
1264 your distro) to load the bonding module with your desired options when the
1266 will load the bonding module, and select its options:
1268 alias bond0 bonding
1283 work) have support for assigning IP information to bonding devices via
1286 To configure bonding for DHCP, configure it as described
1295 Enterprise Linux 5 support multiple bonding interfaces by simply
1298 and a bonding driver of version 3.0.0 or later. Other configurations may
1299 not support this method for specifying multiple bonding interfaces; for
1308 knowledge of bonding. One such distro is SuSE Linux Enterprise Server
1311 The general method for these systems is to place the bonding
1323 modprobe bonding mode=balance-alb miimon=100
1329 Replace the example bonding module parameters and bond0
1334 ifup and ifdown scripts on the bond devices. To reload the bonding
1344 which only initializes the bonding configuration, then call that
1345 separate script from within boot.local. This allows for bonding to be
1348 To shut down the bonding devices, it is necessary to first
1349 mark the bonding device itself as being down, then remove the
1354 # rmmod bonding
1365 bonding devices with differing options for those systems whose network
1368 If you require multiple bonding devices, but all with the same
1372 To create multiple bonding devices with differing options, it is
1373 preferable to use bonding parameters exported by sysfs, documented in the
1376 For versions of bonding without sysfs support, the only means to
1377 provide multiple instances of bonding with differing options is to load
1378 the bonding driver multiple times. Note that current versions of the
1388 sets of bonding options in ``/etc/modprobe.d/*.conf``, for example::
1390 alias bond0 bonding
1393 alias bond1 bonding
1396 will load the bonding module two times. The first instance is
1402 the above does not work, and the second bonding instance never sees
1406 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1432 bonding is compiled into the kernel.
1435 bonding this way. The examples in this document assume that you
1463 /sys/class/net/<bond>/bonding/slaves. The semantics for this file
1469 # echo +eth0 > /sys/class/net/bond0/bonding/slaves
1473 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1482 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1489 files located in /sys/class/net/<bond name>/bonding
1503 # echo 6 > /sys/class/net/bond0/bonding/mode
1505 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1513 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1522 # echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1523 # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target
1531 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1535 # echo 12 > /sys/class/net/bond0/bonding/lp_interval
1540 the bonding driver sends learning packets to each slaves peer switch. The
1553 modprobe bonding
1555 echo balance-alb > /sys/class/net/bond0/bonding/mode
1557 echo 100 > /sys/class/net/bond0/bonding/miimon
1558 echo +eth0 > /sys/class/net/bond0/bonding/slaves
1559 echo +eth1 > /sys/class/net/bond0/bonding/slaves
1567 echo active-backup > /sys/class/net/bond1/bonding/mode
1569 echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target
1570 echo 2000 > /sys/class/net/bond1/bonding/arp_interval
1571 echo +eth2 > /sys/class/net/bond1/bonding/slaves
1572 echo +eth3 > /sys/class/net/bond1/bonding/slaves
1581 The ifup and ifdown commands on Debian don't support bonding out of
1582 the box. The ifenslave-2.6 package should be installed to provide bonding
1586 Note that ifenslave-2.6 package will load the bonding module and use
1630 When using the bonding driver, the physical port which transmits a frame is
1631 typically selected by the bonding driver, and is not relevant to the user or
1633 the selected bonding mode. On occasion however, it is helpful to direct certain
1642 By default the bonding driver is multiqueue aware and 16 queues are created
1648 The output of the file /proc/net/bonding/bondX has changed so the output Queue
1673 # echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id
1699 leaving the qid for a slave to 0 is the multiqueue awareness in the bonding
1701 slave devices as well as bond devices and the bonding driver will simply act as
1705 This feature first appeared in bonding driver version 3.7.0 and support for
1711 When using 802.3ad bonding mode, the Actor (host) and Partner (switch)
1723 few bonding parameters:
1737 # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system
1744 # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio
1752 # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key
1761 Each bonding device has a read-only file residing in the
1762 /proc/net/bonding directory. The file contents include information
1763 about the bonding configuration, options and state of each slave.
1765 For example, the contents of /proc/net/bonding/bond0 after the
1786 bonding configuration, state, and version of the bonding driver.
1851 match. For these three modes, the bonding mode really selects a
1861 driver and passing through bonding will be tagged by default. Self
1862 generated packets, for example, bonding's learning packets or ARP
1864 tagged internally by bonding itself. As a result, bonding must
1869 that can do VLAN hardware acceleration offloading, the bonding
1875 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1878 VLAN interfaces *must* be added on top of a bonding interface
1879 only after enslaving at least one slave. The bonding interface has a
1888 top of it. When a new slave is added, the bonding interface will
1899 2. Set the bonding interface's hardware address so that it
1903 underlying device -- i.e. the bonding interface -- to promiscuous
1910 The bonding driver at present supports two schemes for
1915 bonding driver itself, it is not possible to enable both ARP and MII
1949 alias bond0 bonding
1955 alias bond0 bonding
1991 When bonding is configured, it is important that the slave
1993 generally, not have routes at all). For example, suppose the bonding
2006 may bypass the bonding driver (because outgoing traffic to, in this
2034 alias bond0 bonding
2043 happens because bonding is loaded first, then its slave device's
2046 devices, but the bonding configuration tries to enslave eth2 and eth3
2051 add above bonding e1000 tg3
2054 bonding is loaded. This command is fully documented in the
2061 softdep bonding pre: tg3 e1000
2063 This will load tg3 and e1000 modules before loading the bonding one.
2070 By default, bonding enables the use_carrier option, which
2071 instructs bonding to trust the driver to maintain carrier state.
2075 With use_carrier enabled, bonding will always see these links as up,
2098 If running SNMP agents, the bonding driver should be loaded
2104 bonding driver, the interface for the IP address will be associated
2122 This problem is avoided by loading the bonding driver before
2124 loading the bonding driver first, the IP address 192.168.1.1 is
2149 The bonding driver handles promiscuous mode changes to the bonding
2187 access to fail over to. Additionally, the bonding load balance modes
2192 for information on configuring bonding with one peer device.
2197 With multiple switches, the configuration of bonding and the
2225 broadcast modes are the only useful bonding modes when optimizing for
2270 to the logically "interior" ports that bonding is able to monitor via
2312 multiple physical links is, for purposes of configuring bonding, the
2353 although you will have to decide which bonding mode best suits your
2435 the same speed and duplex. Also, as with all bonding load
2440 Additionally, the linux bonding 802.3ad implementation
2529 In actual practice, the bonding mode typically employed in
2547 host in the network is configured with bonding).
2564 value to the updelay bonding module option to delay the use of the
2572 Note that when a bonding interface has no active links, the
2585 Failover may be delayed via the downdelay bonding module option.
2590 NOTE: Starting with version 3.0.2, the bonding driver has logic to
2595 traffic when the bonding device is first used, or after it has been
2614 This is not due to an error in the bonding driver, rather, it
2634 bonding on specific hardware platforms, or for interfacing bonding
2642 On the JS20 blades, the bonding driver supports only
2660 switch). Some bonding modes require a specific BladeCenter internal
2688 appear to bonding as either a single switch topology (all PMs) or as a
2706 bonding device (i.e., the network must converge at some point outside
2733 bonding driver.
2737 avoid fail-over delay issues when using bonding.
2746 Yes. The old 2.0.xx channel bonding patch was not SMP safe.
2756 Starting with version 3.2.1, bonding also supports Infiniband
2759 3. How many bonding devices can I have?
2764 4. How many slaves can a bonding device have?
2788 If no link monitoring is configured, the bonding driver will
2792 depends upon the bonding mode and network configuration.
2794 6. Can bonding be used for High Availability?
2820 8. Where does a bonding device get its MAC address from?
2824 the fail_over_mac option is enabled, the bonding device's MAC address is
2828 ifconfig or ip link), the MAC address of the bonding device is taken from
2831 the bonding device is brought down or reconfigured.
2843 # ifconfig bond0 down ; modprobe -r bonding
2851 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2858 The latest version of the bonding driver can be found in the latest
2862 source (named Documentation/networking/bonding.rst).
2864 Discussions regarding the development of the bonding driver take place