€•yŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œtranslations”Œ LanguagesNode”“”)”}”(hhh]”(hŒpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ&/translations/zh_CN/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/zh_TW/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/it_IT/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/ja_JP/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/ko_KR/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/pt_BR/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ&/translations/sp_SP/networking/bonding”Œmodname”NŒ classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hµhhh²hh³Œ@/var/lib/git/docbuild/linux/Documentation/networking/bonding.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ#Linux Ethernet Bonding Driver HOWTO”h]”hŒ#Linux Ethernet Bonding Driver HOWTO”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ paragraph”“”)”}”(hŒLatest update: 27 April 2011”h]”hŒLatest update: 27 April 2011”…””}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhÞ)”}”(hŒ2Initial release: Thomas Davis ”h]”hŒ2Initial release: Thomas Davis ”…””}”(hhíh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hhÊh²hubhÞ)”}”(hŒ*Corrections, HA extensions: 2000/10/03-15:”h]”hŒ*Corrections, HA extensions: 2000/10/03-15:”…””}”(hhûh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhŒblock_quote”“”)”}”(hŒß- Willy Tarreau - Constantine Gavrilov - Chad N. Tindel - Janice Girouard - Jay Vosburgh ”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hŒ#Willy Tarreau ”h]”hÞ)”}”(hjh]”hŒ#Willy Tarreau ”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒ+Constantine Gavrilov ”h]”hÞ)”}”(hj/h]”hŒ+Constantine Gavrilov ”…””}”(hj1h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj-ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒ(Chad N. Tindel ”h]”hÞ)”}”(hjFh]”hŒ(Chad N. Tindel ”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjDubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒ0Janice Girouard ”h]”hÞ)”}”(hj]h]”hŒ0Janice Girouard ”…””}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj[ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubj)”}”(hŒ+Jay Vosburgh ”h]”hÞ)”}”(hŒ*Jay Vosburgh ”h]”hŒ*Jay Vosburgh ”…””}”(hjvh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjrubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jh³hÇh´K hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K hhÊh²hubhÞ)”}”(hŒTReorganized and updated Feb 2005 by Jay Vosburgh Added Sysfs information: 2006/04/24”h]”hŒTReorganized and updated Feb 2005 by Jay Vosburgh Added Sysfs information: 2006/04/24”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubj )”}”(hŒ1- Mitch Williams ”h]”j)”}”(hhh]”j)”}”(hŒ/Mitch Williams ”h]”hÞ)”}”(hŒ.Mitch Williams ”h]”hŒ.Mitch Williams ”…””}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjªubah}”(h]”h ]”h"]”h$]”h&]”jj‘uh1jh³hÇh´Khj¦ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KhhÊh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒIntroduction”h]”hŒIntroduction”…””}”(hjÔh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÑh²hh³hÇh´KubhÞ)”}”(hXHThe Linux bonding driver provides a method for aggregating multiple network interfaces into a single logical "bonded" interface. The behavior of the bonded interfaces depends upon the mode; generally speaking, modes provide either hot standby or load balancing services. Additionally, link integrity monitoring may be performed.”h]”hXLThe Linux bonding driver provides a method for aggregating multiple network interfaces into a single logical â€œbondedâ€ interface. The behavior of the bonded interfaces depends upon the mode; generally speaking, modes provide either hot standby or load balancing services. Additionally, link integrity monitoring may be performed.”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjÑh²hubhÞ)”}”(hŒäThe bonding driver originally came from Donald Becker's beowulf patches for kernel 2.0. It has changed quite a bit since, and the original tools from extreme-linux and beowulf sites will not work with this version of the driver.”h]”hŒæThe bonding driver originally came from Donald Beckerâ€™s beowulf patches for kernel 2.0. It has changed quite a bit since, and the original tools from extreme-linux and beowulf sites will not work with this version of the driver.”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K!hjÑh²hubhÞ)”}”(hŒ‚For new versions of the driver, updated userspace tools, and who to ask for help, please follow the links at the end of this file.”h]”hŒ‚For new versions of the driver, updated userspace tools, and who to ask for help, please follow the links at the end of this file.”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K&hjÑh²hubh¶)”}”(hX<Table of Contents 1. Bonding Driver Installation 2. Bonding Driver Options 3. Configuring Bonding Devices 3.1 Configuration with Sysconfig Support 3.1.1 Using DHCP with Sysconfig 3.1.2 Configuring Multiple Bonds with Sysconfig 3.2 Configuration with Initscripts Support 3.2.1 Using DHCP with Initscripts 3.2.2 Configuring Multiple Bonds with Initscripts 3.3 Configuring Bonding Manually with Ifenslave 3.3.1 Configuring Multiple Bonds Manually 3.4 Configuring Bonding Manually via Sysfs 3.5 Configuration with Interfaces Support 3.6 Overriding Configuration for Special Cases 3.7 Configuring LACP for 802.3ad mode in a more secure way 4. Querying Bonding Configuration 4.1 Bonding Configuration 4.2 Network Configuration 5. Switch Configuration 6. 802.1q VLAN Support 7. Link Monitoring 7.1 ARP Monitor Operation 7.2 Configuring Multiple ARP Targets 7.3 MII Monitor Operation 8. Potential Trouble Sources 8.1 Adventures in Routing 8.2 Ethernet Device Renaming 8.3 Painfully Slow Or No Failed Link Detection By Miimon 9. SNMP agents 10. Promiscuous mode 11. Configuring Bonding for High Availability 11.1 High Availability in a Single Switch Topology 11.2 High Availability in a Multiple Switch Topology 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology 11.2.2 HA Link Monitoring for Multiple Switch Topology 12. Configuring Bonding for Maximum Throughput 12.1 Maximum Throughput in a Single Switch Topology 12.1.1 MT Bonding Mode Selection for Single Switch Topology 12.1.2 MT Link Monitoring for Single Switch Topology 12.2 Maximum Throughput in a Multiple Switch Topology 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology 12.2.2 MT Link Monitoring for Multiple Switch Topology 13. Switch Behavior Issues 13.1 Link Establishment and Failover Delays 13.2 Duplicated Incoming Packets 14. Hardware Specific Considerations 14.1 IBM BladeCenter 15. Frequently Asked Questions 16. Resources and Links”h]”hX<Table of Contents 1. Bonding Driver Installation 2. Bonding Driver Options 3. Configuring Bonding Devices 3.1 Configuration with Sysconfig Support 3.1.1 Using DHCP with Sysconfig 3.1.2 Configuring Multiple Bonds with Sysconfig 3.2 Configuration with Initscripts Support 3.2.1 Using DHCP with Initscripts 3.2.2 Configuring Multiple Bonds with Initscripts 3.3 Configuring Bonding Manually with Ifenslave 3.3.1 Configuring Multiple Bonds Manually 3.4 Configuring Bonding Manually via Sysfs 3.5 Configuration with Interfaces Support 3.6 Overriding Configuration for Special Cases 3.7 Configuring LACP for 802.3ad mode in a more secure way 4. Querying Bonding Configuration 4.1 Bonding Configuration 4.2 Network Configuration 5. Switch Configuration 6. 802.1q VLAN Support 7. Link Monitoring 7.1 ARP Monitor Operation 7.2 Configuring Multiple ARP Targets 7.3 MII Monitor Operation 8. Potential Trouble Sources 8.1 Adventures in Routing 8.2 Ethernet Device Renaming 8.3 Painfully Slow Or No Failed Link Detection By Miimon 9. SNMP agents 10. Promiscuous mode 11. Configuring Bonding for High Availability 11.1 High Availability in a Single Switch Topology 11.2 High Availability in a Multiple Switch Topology 11.2.1 HA Bonding Mode Selection for Multiple Switch Topology 11.2.2 HA Link Monitoring for Multiple Switch Topology 12. Configuring Bonding for Maximum Throughput 12.1 Maximum Throughput in a Single Switch Topology 12.1.1 MT Bonding Mode Selection for Single Switch Topology 12.1.2 MT Link Monitoring for Single Switch Topology 12.2 Maximum Throughput in a Multiple Switch Topology 12.2.1 MT Bonding Mode Selection for Multiple Switch Topology 12.2.2 MT Link Monitoring for Multiple Switch Topology 13. Switch Behavior Issues 13.1 Link Establishment and Failover Delays 13.2 Duplicated Incoming Packets 14. Hardware Specific Considerations 14.1 IBM BladeCenter 15. Frequently Asked Questions 16. Resources and Links”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhjÑh²hh³hÇh´Klubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒ1. Bonding Driver Installation”h]”hŒ1. Bonding Driver Installation”…””}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj"h²hh³hÇh´KnubhÞ)”}”(hXMost popular distro kernels ship with the bonding driver already available as a module. If your distro does not, or you have need to compile bonding from source (e.g., configuring and installing a mainline kernel from kernel.org), you'll need to perform the following steps:”h]”hXMost popular distro kernels ship with the bonding driver already available as a module. If your distro does not, or you have need to compile bonding from source (e.g., configuring and installing a mainline kernel from kernel.org), youâ€™ll need to perform the following steps:”…””}”(hj3h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kphj"h²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ/1.1 Configure and build the kernel with bonding”h]”hŒ/1.1 Configure and build the kernel with bonding”…””}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjAh²hh³hÇh´KwubhÞ)”}”(hXThe current version of the bonding driver is available in the drivers/net/bonding subdirectory of the most recent kernel source (which is available on http://kernel.org). Most users "rolling their own" will want to use the most recent kernel from kernel.org.”h]”(hŒ—The current version of the bonding driver is available in the drivers/net/bonding subdirectory of the most recent kernel source (which is available on ”…””}”(hjRh²hh³Nh´NubhŒ reference”“”)”}”(hŒhttp://kernel.org”h]”hŒhttp://kernel.org”…””}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j^uh1jZhjRubhŒ_). Most users â€œrolling their ownâ€ will want to use the most recent kernel from kernel.org.”…””}”(hjRh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KyhjAh²hubhÞ)”}”(hXEConfigure kernel with "make menuconfig" (or "make xconfig" or "make config"), then select "Bonding driver support" in the "Network device support" section. It is recommended that you configure the driver as module since it is currently the only way to pass parameters to the driver or configure more than one bonding device.”h]”hXYConfigure kernel with â€œmake menuconfigâ€ (or â€œmake xconfigâ€ or â€œmake configâ€), then select â€œBonding driver supportâ€ in the â€œNetwork device supportâ€ section. It is recommended that you configure the driver as module since it is currently the only way to pass parameters to the driver or configure more than one bonding device.”…””}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K~hjAh²hubhÞ)”}”(hŒ-Build and install the new kernel and modules.”h]”hŒ-Build and install the new kernel and modules.”…””}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K„hjAh²hubeh}”(h]”Œ+configure-and-build-the-kernel-with-bonding”ah ]”h"]”Œ/1.1 configure and build the kernel with bonding”ah$]”h&]”uh1hÈhj"h²hh³hÇh´KwubhÉ)”}”(hhh]”(hÎ)”}”(hŒ1.2 Bonding Control Utility”h]”hŒ1.2 Bonding Control Utility”…””}”(hjœh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj™h²hh³hÇh´K‡ubhÞ)”}”(hŒvIt is recommended to configure bonding via iproute2 (netlink) or sysfs, the old ifenslave control utility is obsolete.”h]”hŒvIt is recommended to configure bonding via iproute2 (netlink) or sysfs, the old ifenslave control utility is obsolete.”…””}”(hjªh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K‰hj™h²hubeh}”(h]”Œbonding-control-utility”ah ]”h"]”Œ1.2 bonding control utility”ah$]”h&]”uh1hÈhj"h²hh³hÇh´K‡ubeh}”(h]”Œbonding-driver-installation”ah ]”h"]”Œ1. bonding driver installation”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KnubhÉ)”}”(hhh]”(hÎ)”}”(hŒ2. Bonding Driver Options”h]”hŒ2. Bonding Driver Options”…””}”(hjËh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÈh²hh³hÇh´KubhÞ)”}”(hŒyOptions for the bonding driver are supplied as parameters to the bonding module at load time, or are specified via sysfs.”h]”hŒyOptions for the bonding driver are supplied as parameters to the bonding module at load time, or are specified via sysfs.”…””}”(hjÙh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjÈh²hubhÞ)”}”(hX Module options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the ``/etc/modprobe.d/*.conf`` configuration files, or in a distro-specific configuration file (some of which are detailed in the next section).”h]”(hŒModule options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the ”…””}”(hjçh²hh³Nh´NubhŒliteral”“”)”}”(hŒ``/etc/modprobe.d/*.conf``”h]”hŒ/etc/modprobe.d/*.conf”…””}”(hjñh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjçubhŒr configuration files, or in a distro-specific configuration file (some of which are detailed in the next section).”…””}”(hjçh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K’hjÈh²hubhÞ)”}”(hŒpDetails on bonding support for sysfs is provided in the "Configuring Bonding Manually via Sysfs" section, below.”h]”hŒtDetails on bonding support for sysfs is provided in the â€œConfiguring Bonding Manually via Sysfsâ€ section, below.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K—hjÈh²hubhÞ)”}”(hXThe available bonding driver parameters are listed below. If a parameter is not specified the default value is used. When initially configuring a bond, it is recommended "tail -f /var/log/messages" be run in a separate window to watch for bonding driver error messages.”h]”hXThe available bonding driver parameters are listed below. If a parameter is not specified the default value is used. When initially configuring a bond, it is recommended â€œtail -f /var/log/messagesâ€ be run in a separate window to watch for bonding driver error messages.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KšhjÈh²hubhÞ)”}”(hXIt is critical that either the miimon or arp_interval and arp_ip_target parameters be specified, otherwise serious network degradation will occur during link failures. Very few devices do not support at least miimon, so there is really no reason not to use it.”h]”hXIt is critical that either the miimon or arp_interval and arp_ip_target parameters be specified, otherwise serious network degradation will occur during link failures. Very few devices do not support at least miimon, so there is really no reason not to use it.”…””}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KŸhjÈh²hubhÞ)”}”(hŒ¥Options with textual values will accept either the text name or, for backwards compatibility, the option value. E.g., "mode=802.3ad" and "mode=4" set the same mode.”h]”hŒOptions with textual values will accept either the text name or, for backwards compatibility, the option value. E.g., â€œmode=802.3adâ€ and â€œmode=4â€ set the same mode.”…””}”(hj3h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¤hjÈh²hubhÞ)”}”(hŒThe parameters are as follows:”h]”hŒThe parameters are as follows:”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¨hjÈh²hubhÞ)”}”(hŒactive_slave”h]”hŒactive_slave”…””}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KªhjÈh²hubj )”}”(hXµSpecifies the new active slave for modes that support it (active-backup, balance-alb and balance-tlb). Possible values are the name of any currently enslaved interface, or an empty string. If a name is given, the slave and its link must be up in order to be selected as the new active slave. If an empty string is specified, the current active slave is cleared, and a new active slave is selected automatically. Note that this is only available through the sysfs interface. No module parameter by this name exists. The normal value of this option is the name of the currently active slave, or the empty string if there is no active slave or the current mode does not use an active slave. ”h]”(hÞ)”}”(hXžSpecifies the new active slave for modes that support it (active-backup, balance-alb and balance-tlb). Possible values are the name of any currently enslaved interface, or an empty string. If a name is given, the slave and its link must be up in order to be selected as the new active slave. If an empty string is specified, the current active slave is cleared, and a new active slave is selected automatically.”h]”hXžSpecifies the new active slave for modes that support it (active-backup, balance-alb and balance-tlb). Possible values are the name of any currently enslaved interface, or an empty string. If a name is given, the slave and its link must be up in order to be selected as the new active slave. If an empty string is specified, the current active slave is cleared, and a new active slave is selected automatically.”…””}”(hjah²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¬hj]ubhÞ)”}”(hŒfNote that this is only available through the sysfs interface. No module parameter by this name exists.”h]”hŒfNote that this is only available through the sysfs interface. No module parameter by this name exists.”…””}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K´hj]ubhÞ)”}”(hŒ¬The normal value of this option is the name of the currently active slave, or the empty string if there is no active slave or the current mode does not use an active slave.”h]”hŒ¬The normal value of this option is the name of the currently active slave, or the empty string if there is no active slave or the current mode does not use an active slave.”…””}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K·hj]ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K¬hjÈh²hubhÞ)”}”(hŒad_actor_sys_prio”h]”hŒad_actor_sys_prio”…””}”(hj‘h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K»hjÈh²hubj )”}”(hŒóIn an AD system, this specifies the system priority. The allowed range is 1 - 65535. If the value is not specified, it takes 65535 as the default value. This parameter has effect only in 802.3ad mode and is available through SysFs interface. ”h]”(hÞ)”}”(hŒ˜In an AD system, this specifies the system priority. The allowed range is 1 - 65535. If the value is not specified, it takes 65535 as the default value.”h]”hŒ˜In an AD system, this specifies the system priority. The allowed range is 1 - 65535. If the value is not specified, it takes 65535 as the default value.”…””}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K½hjŸubhÞ)”}”(hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”h]”hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”…””}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÁhjŸubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´K½hjÈh²hubhÞ)”}”(hŒactor_port_prio”h]”hŒactor_port_prio”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÄhjÈh²hubj )”}”(hŒñIn an AD system, this specifies the port priority. The allowed range is 1 - 65535. If the value is not specified, it takes 255 as the default value. This parameter has effect only in 802.3ad mode and is available through netlink interface. ”h]”(hÞ)”}”(hŒ”In an AD system, this specifies the port priority. The allowed range is 1 - 65535. If the value is not specified, it takes 255 as the default value.”h]”hŒ”In an AD system, this specifies the port priority. The allowed range is 1 - 65535. If the value is not specified, it takes 255 as the default value.”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÆhjÓubhÞ)”}”(hŒZThis parameter has effect only in 802.3ad mode and is available through netlink interface.”h]”hŒZThis parameter has effect only in 802.3ad mode and is available through netlink interface.”…””}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÊhjÓubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KÆhjÈh²hubhÞ)”}”(hŒad_actor_system”h]”hŒad_actor_system”…””}”(hjùh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÍhjÈh²hubj )”}”(hXIn an AD system, this specifies the mac-address for the actor in protocol packet exchanges (LACPDUs). The value cannot be a multicast address. If the all-zeroes MAC is specified, bonding will internally use the MAC of the bond itself. It is preferred to have the local-admin bit set for this mac but driver does not enforce it. If the value is not given then system defaults to using the masters' mac address as actors' system address. This parameter has effect only in 802.3ad mode and is available through SysFs interface. ”h]”(hÞ)”}”(hX³In an AD system, this specifies the mac-address for the actor in protocol packet exchanges (LACPDUs). The value cannot be a multicast address. If the all-zeroes MAC is specified, bonding will internally use the MAC of the bond itself. It is preferred to have the local-admin bit set for this mac but driver does not enforce it. If the value is not given then system defaults to using the masters' mac address as actors' system address.”h]”hX·In an AD system, this specifies the mac-address for the actor in protocol packet exchanges (LACPDUs). The value cannot be a multicast address. If the all-zeroes MAC is specified, bonding will internally use the MAC of the bond itself. It is preferred to have the local-admin bit set for this mac but driver does not enforce it. If the value is not given then system defaults to using the mastersâ€™ mac address as actorsâ€™ system address.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÏhjubhÞ)”}”(hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”h]”hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K×hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KÏhjÈh²hubhÞ)”}”(hŒ ad_select”h]”hŒ ad_select”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÚhjÈh²hubj )”}”(hXñSpecifies the 802.3ad aggregation selection logic to use. The possible values and their effects are: stable or 0 The active aggregator is chosen by largest aggregate bandwidth. Reselection of the active aggregator occurs only when all slaves of the active aggregator are down or the active aggregator has no slaves. This is the default value. bandwidth or 1 The active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if: - A slave is added to or removed from the bond - Any slave's link state changes - Any slave's 802.3ad association state changes - The bond's administrative state changes to up count or 2 The active aggregator is chosen by the largest number of ports (slaves). Reselection occurs as described under the "bandwidth" setting, above. actor_port_prio or 3 The active aggregator is chosen by the highest total sum of actor port priorities across its active ports. Note this priority is actor_port_prio, not per port prio, which is used for primary reselect. The bandwidth, count and actor_port_prio selection policies permit failover of 802.3ad aggregations when partial failure of the active aggregator occurs. This keeps the aggregator with the highest availability (either in bandwidth, number of ports, or total value of port priorities) active at all times. This option was added in bonding version 3.4.0. ”h]”(hÞ)”}”(hŒeSpecifies the 802.3ad aggregation selection logic to use. The possible values and their effects are:”h]”hŒeSpecifies the 802.3ad aggregation selection logic to use. The possible values and their effects are:”…””}”(hj?h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÜhj;ubhÞ)”}”(hŒstable or 0”h]”hŒstable or 0”…””}”(hjMh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kßhj;ubj )”}”(hŒèThe active aggregator is chosen by largest aggregate bandwidth. Reselection of the active aggregator occurs only when all slaves of the active aggregator are down or the active aggregator has no slaves. This is the default value. ”h]”(hÞ)”}”(hŒ?The active aggregator is chosen by largest aggregate bandwidth.”h]”hŒ?The active aggregator is chosen by largest aggregate bandwidth.”…””}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Káhj[ubhÞ)”}”(hŒŠReselection of the active aggregator occurs only when all slaves of the active aggregator are down or the active aggregator has no slaves.”h]”hŒŠReselection of the active aggregator occurs only when all slaves of the active aggregator are down or the active aggregator has no slaves.”…””}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kähj[ubhÞ)”}”(hŒThis is the default value.”h]”hŒThis is the default value.”…””}”(hj{h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kèhj[ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Káhj;ubhÞ)”}”(hŒbandwidth or 1”h]”hŒbandwidth or 1”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kêhj;ubj )”}”(hXThe active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if: - A slave is added to or removed from the bond - Any slave's link state changes - Any slave's 802.3ad association state changes - The bond's administrative state changes to up ”h]”(hÞ)”}”(hŒWThe active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if:”h]”hŒWThe active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if:”…””}”(hj¡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kìhjubj)”}”(hhh]”(j)”}”(hŒ-A slave is added to or removed from the bond ”h]”hÞ)”}”(hŒ,A slave is added to or removed from the bond”h]”hŒ,A slave is added to or removed from the bond”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kïhj²ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¯ubj)”}”(hŒAny slave's link state changes ”h]”hÞ)”}”(hŒAny slave's link state changes”h]”hŒ Any slaveâ€™s link state changes”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KñhjÊubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¯ubj)”}”(hŒ.Any slave's 802.3ad association state changes ”h]”hÞ)”}”(hŒ-Any slave's 802.3ad association state changes”h]”hŒ/Any slaveâ€™s 802.3ad association state changes”…””}”(hjæh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kóhjâubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¯ubj)”}”(hŒ.The bond's administrative state changes to up ”h]”hÞ)”}”(hŒ-The bond's administrative state changes to up”h]”hŒ/The bondâ€™s administrative state changes to up”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kõhjúubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¯ubeh}”(h]”h ]”h"]”h$]”h&]”jj‘uh1jh³hÇh´Kïhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Kìhj;ubhÞ)”}”(hŒ count or 2”h]”hŒ count or 2”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K÷hj;ubj )”}”(hŒThe active aggregator is chosen by the largest number of ports (slaves). Reselection occurs as described under the "bandwidth" setting, above. ”h]”hÞ)”}”(hŒThe active aggregator is chosen by the largest number of ports (slaves). Reselection occurs as described under the "bandwidth" setting, above.”h]”hŒ“The active aggregator is chosen by the largest number of ports (slaves). Reselection occurs as described under the â€œbandwidthâ€ setting, above.”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kùhj,ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Kùhj;ubhÞ)”}”(hŒactor_port_prio or 3”h]”hŒactor_port_prio or 3”…””}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kýhj;ubj )”}”(hŒÉThe active aggregator is chosen by the highest total sum of actor port priorities across its active ports. Note this priority is actor_port_prio, not per port prio, which is used for primary reselect. ”h]”hÞ)”}”(hŒÈThe active aggregator is chosen by the highest total sum of actor port priorities across its active ports. Note this priority is actor_port_prio, not per port prio, which is used for primary reselect.”h]”hŒÈThe active aggregator is chosen by the highest total sum of actor port priorities across its active ports. Note this priority is actor_port_prio, not per port prio, which is used for primary reselect.”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KÿhjRubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Kÿhj;ubhÞ)”}”(hX0The bandwidth, count and actor_port_prio selection policies permit failover of 802.3ad aggregations when partial failure of the active aggregator occurs. This keeps the aggregator with the highest availability (either in bandwidth, number of ports, or total value of port priorities) active at all times.”h]”hX0The bandwidth, count and actor_port_prio selection policies permit failover of 802.3ad aggregations when partial failure of the active aggregator occurs. This keeps the aggregator with the highest availability (either in bandwidth, number of ports, or total value of port priorities) active at all times.”…””}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj;ubhÞ)”}”(hŒ/This option was added in bonding version 3.4.0.”h]”hŒ/This option was added in bonding version 3.4.0.”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj;ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´KÜhjÈh²hubhÞ)”}”(hŒad_user_port_key”h]”hŒad_user_port_key”…””}”(hjŒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÈh²hubj )”}”(hXŸIn an AD system, the port-key has three parts as shown below - ===== ============ Bits Use ===== ============ 00 Duplex 01-05 Speed 06-15 User-defined ===== ============ This defines the upper 10 bits of the port key. The values can be from 0 - 1023. If not given, the system defaults to 0. This parameter has effect only in 802.3ad mode and is available through SysFs interface. ”h]”(hÞ)”}”(hŒ>In an AD system, the port-key has three parts as shown below -”h]”hŒ>In an AD system, the port-key has three parts as shown below -”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjšubj )”}”(hŒv===== ============ Bits Use ===== ============ 00 Duplex 01-05 Speed 06-15 User-defined ===== ============ ”h]”hŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jºhj·ubj»)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jºhj·ubhŒthead”“”)”}”(hhh]”hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÞ)”}”(hŒBits”h]”hŒBits”…””}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÜubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj×ubjÛ)”}”(hhh]”hÞ)”}”(hŒUse”h]”hŒUse”…””}”(hjöh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjóubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj×ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÒubah}”(h]”h ]”h"]”h$]”h&]”uh1jÐhj·ubhŒtbody”“”)”}”(hhh]”(jÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒ00”h]”hŒ00”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjubjÛ)”}”(hhh]”hÞ)”}”(hŒDuplex”h]”hŒDuplex”…””}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒ01-05”h]”hŒ01-05”…””}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjUubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjRubjÛ)”}”(hhh]”hÞ)”}”(hŒSpeed”h]”hŒSpeed”…””}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjlubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjRubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒ06-15”h]”hŒ06-15”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjŒubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj‰ubjÛ)”}”(hhh]”hÞ)”}”(hŒUser-defined”h]”hŒUser-defined”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj£ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj‰ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj·ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1jµhj²ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°hj¬ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MhjšubhÞ)”}”(hŒxThis defines the upper 10 bits of the port key. The values can be from 0 - 1023. If not given, the system defaults to 0.”h]”hŒxThis defines the upper 10 bits of the port key. The values can be from 0 - 1023. If not given, the system defaults to 0.”…””}”(hjÙh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjšubhÞ)”}”(hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”h]”hŒXThis parameter has effect only in 802.3ad mode and is available through SysFs interface.”…””}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjšubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MhjÈh²hubhÞ)”}”(hŒall_slaves_active”h]”hŒall_slaves_active”…””}”(hjûh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÈh²hubj )”}”(hXoSpecifies that duplicate frames (received on inactive ports) should be dropped (0) or delivered (1). Normally, bonding will drop duplicate frames (received on inactive ports), which is desirable for most users. But there are some times it is nice to allow duplicate frames to be delivered. The default value is 0 (drop duplicate frames received on inactive ports). ”h]”(hÞ)”}”(hŒdSpecifies that duplicate frames (received on inactive ports) should be dropped (0) or delivered (1).”h]”hŒdSpecifies that duplicate frames (received on inactive ports) should be dropped (0) or delivered (1).”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj ubhÞ)”}”(hŒ¼Normally, bonding will drop duplicate frames (received on inactive ports), which is desirable for most users. But there are some times it is nice to allow duplicate frames to be delivered.”h]”hŒ¼Normally, bonding will drop duplicate frames (received on inactive ports), which is desirable for most users. But there are some times it is nice to allow duplicate frames to be delivered.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M#hj ubhÞ)”}”(hŒJThe default value is 0 (drop duplicate frames received on inactive ports).”h]”hŒJThe default value is 0 (drop duplicate frames received on inactive ports).”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M'hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M hjÈh²hubhÞ)”}”(hŒarp_interval”h]”hŒarp_interval”…””}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M*hjÈh²hubj )”}”(hX©Specifies the ARP link monitoring frequency in milliseconds. The ARP monitor works by periodically checking the slave devices to determine whether they have sent or received traffic recently (the precise criteria depends upon the bonding mode, and the state of the slave). Regular traffic is generated via ARP probes issued for the addresses specified by the arp_ip_target option. This behavior can be modified by the arp_validate option, below. If ARP monitoring is used in an etherchannel compatible mode (modes 0 and 2), the switch should be configured in a mode that evenly distributes packets across all links. If the switch is configured to distribute the packets in an XOR fashion, all replies from the ARP targets will be received on the same link which could cause the other team members to fail. ARP monitoring should not be used in conjunction with miimon. A value of 0 disables ARP monitoring. The default value is 0. ”h]”(hÞ)”}”(hŒ 0. These are the targets of the ARP request sent to determine the health of the link to the targets. Specify these values in ddd.ddd.ddd.ddd format. Multiple IP addresses must be separated by a comma. At least one IP address must be given for ARP monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IP addresses. ”h]”hÞ)”}”(hXÅSpecifies the IP addresses to use as ARP monitoring peers when arp_interval is > 0. These are the targets of the ARP request sent to determine the health of the link to the targets. Specify these values in ddd.ddd.ddd.ddd format. Multiple IP addresses must be separated by a comma. At least one IP address must be given for ARP monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IP addresses.”h]”hXÅSpecifies the IP addresses to use as ARP monitoring peers when arp_interval is > 0. These are the targets of the ARP request sent to determine the health of the link to the targets. Specify these values in ddd.ddd.ddd.ddd format. Multiple IP addresses must be separated by a comma. At least one IP address must be given for ARP monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IP addresses.”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MDhj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MDhjÈh²hubhÞ)”}”(hŒ ns_ip6_target”h]”hŒ ns_ip6_target”…””}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MMhjÈh²hubj )”}”(hXÕSpecifies the IPv6 addresses to use as IPv6 monitoring peers when arp_interval is > 0. These are the targets of the NS request sent to determine the health of the link to the targets. Specify these values in ffff:ffff::ffff:ffff format. Multiple IPv6 addresses must be separated by a comma. At least one IPv6 address must be given for NS/NA monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IPv6 addresses. ”h]”hÞ)”}”(hXÔSpecifies the IPv6 addresses to use as IPv6 monitoring peers when arp_interval is > 0. These are the targets of the NS request sent to determine the health of the link to the targets. Specify these values in ffff:ffff::ffff:ffff format. Multiple IPv6 addresses must be separated by a comma. At least one IPv6 address must be given for NS/NA monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IPv6 addresses.”h]”hXÔSpecifies the IPv6 addresses to use as IPv6 monitoring peers when arp_interval is > 0. These are the targets of the NS request sent to determine the health of the link to the targets. Specify these values in ffff:ffff::ffff:ffff format. Multiple IPv6 addresses must be separated by a comma. At least one IPv6 address must be given for NS/NA monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IPv6 addresses.”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MOhjÁubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MOhjÈh²hubhÞ)”}”(hŒarp_validate”h]”hŒarp_validate”…””}”(hjÙh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MXhjÈh²hubj )”}”(hXøSpecifies whether or not ARP probes and replies should be validated in any mode that supports arp monitoring, or whether non-ARP traffic should be filtered (disregarded) for link monitoring purposes. Possible values are: none or 0 No validation or filtering is performed. active or 1 Validation is performed only for the active slave. backup or 2 Validation is performed only for backup slaves. all or 3 Validation is performed for all slaves. filter or 4 Filtering is applied to all slaves. No validation is performed. filter_active or 5 Filtering is applied to all slaves, validation is performed only for the active slave. filter_backup or 6 Filtering is applied to all slaves, validation is performed only for backup slaves. Validation: Enabling validation causes the ARP monitor to examine the incoming ARP requests and replies, and only consider a slave to be up if it is receiving the appropriate ARP traffic. For an active slave, the validation checks ARP replies to confirm that they were generated by an arp_ip_target. Since backup slaves do not typically receive these replies, the validation performed for backup slaves is on the broadcast ARP request sent out via the active slave. It is possible that some switch or network configurations may result in situations wherein the backup slaves do not receive the ARP requests; in such a situation, validation of backup slaves must be disabled. The validation of ARP requests on backup slaves is mainly helping bonding to decide which slaves are more likely to work in case of the active slave failure, it doesn't really guarantee that the backup slave will work if it's selected as the next active slave. Validation is useful in network configurations in which multiple bonding hosts are concurrently issuing ARPs to one or more targets beyond a common switch. Should the link between the switch and target fail (but not the switch itself), the probe traffic generated by the multiple bonding instances will fool the standard ARP monitor into considering the links as still up. Use of validation can resolve this, as the ARP monitor will only consider ARP requests and replies associated with its own instance of bonding. Filtering: Enabling filtering causes the ARP monitor to only use incoming ARP packets for link availability purposes. Arriving packets that are not ARPs are delivered normally, but do not count when determining if a slave is available. Filtering operates by only considering the reception of ARP packets (any ARP packet, regardless of source or destination) when determining if a slave has received traffic for link availability purposes. Filtering is useful in network configurations in which significant levels of third party broadcast traffic would fool the standard ARP monitor into considering the links as still up. Use of filtering can resolve this, as only ARP traffic is considered for link availability purposes. This option was added in bonding version 3.1.0. ”h]”(hÞ)”}”(hŒÇSpecifies whether or not ARP probes and replies should be validated in any mode that supports arp monitoring, or whether non-ARP traffic should be filtered (disregarded) for link monitoring purposes.”h]”hŒÇSpecifies whether or not ARP probes and replies should be validated in any mode that supports arp monitoring, or whether non-ARP traffic should be filtered (disregarded) for link monitoring purposes.”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MZhjçubhÞ)”}”(hŒPossible values are:”h]”hŒPossible values are:”…””}”(hjùh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M_hjçubhÞ)”}”(hŒ none or 0”h]”hŒ none or 0”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mahjçubj )”}”(hŒ)No validation or filtering is performed. ”h]”hÞ)”}”(hŒ(No validation or filtering is performed.”h]”hŒ(No validation or filtering is performed.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mchjubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MchjçubhÞ)”}”(hŒactive or 1”h]”hŒactive or 1”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mehjçubj )”}”(hŒ3Validation is performed only for the active slave. ”h]”hÞ)”}”(hŒ2Validation is performed only for the active slave.”h]”hŒ2Validation is performed only for the active slave.”…””}”(hj?h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mghj;ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MghjçubhÞ)”}”(hŒbackup or 2”h]”hŒbackup or 2”…””}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mihjçubj )”}”(hŒ0Validation is performed only for backup slaves. ”h]”hÞ)”}”(hŒ/Validation is performed only for backup slaves.”h]”hŒ/Validation is performed only for backup slaves.”…””}”(hjeh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mkhjaubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MkhjçubhÞ)”}”(hŒall or 3”h]”hŒall or 3”…””}”(hjyh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mmhjçubj )”}”(hŒ(Validation is performed for all slaves. ”h]”hÞ)”}”(hŒ'Validation is performed for all slaves.”h]”hŒ'Validation is performed for all slaves.”…””}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mohj‡ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MohjçubhÞ)”}”(hŒfilter or 4”h]”hŒfilter or 4”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mqhjçubj )”}”(hŒ@Filtering is applied to all slaves. No validation is performed. ”h]”hÞ)”}”(hŒ?Filtering is applied to all slaves. No validation is performed.”h]”hŒ?Filtering is applied to all slaves. No validation is performed.”…””}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mshjubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MshjçubhÞ)”}”(hŒfilter_active or 5”h]”hŒfilter_active or 5”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mvhjçubj )”}”(hŒWFiltering is applied to all slaves, validation is performed only for the active slave. ”h]”hÞ)”}”(hŒVFiltering is applied to all slaves, validation is performed only for the active slave.”h]”hŒVFiltering is applied to all slaves, validation is performed only for the active slave.”…””}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MxhjÓubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MxhjçubhÞ)”}”(hŒfilter_backup or 6”h]”hŒfilter_backup or 6”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M{hjçubj )”}”(hŒTFiltering is applied to all slaves, validation is performed only for backup slaves. ”h]”hÞ)”}”(hŒSFiltering is applied to all slaves, validation is performed only for backup slaves.”h]”hŒSFiltering is applied to all slaves, validation is performed only for backup slaves.”…””}”(hjýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M}hjùubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M}hjçubhÞ)”}”(hŒValidation:”h]”hŒValidation:”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M€hjçubhÞ)”}”(hŒ¯Enabling validation causes the ARP monitor to examine the incoming ARP requests and replies, and only consider a slave to be up if it is receiving the appropriate ARP traffic.”h]”hŒ¯Enabling validation causes the ARP monitor to examine the incoming ARP requests and replies, and only consider a slave to be up if it is receiving the appropriate ARP traffic.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‚hjçubhÞ)”}”(hXèFor an active slave, the validation checks ARP replies to confirm that they were generated by an arp_ip_target. Since backup slaves do not typically receive these replies, the validation performed for backup slaves is on the broadcast ARP request sent out via the active slave. It is possible that some switch or network configurations may result in situations wherein the backup slaves do not receive the ARP requests; in such a situation, validation of backup slaves must be disabled.”h]”hXèFor an active slave, the validation checks ARP replies to confirm that they were generated by an arp_ip_target. Since backup slaves do not typically receive these replies, the validation performed for backup slaves is on the broadcast ARP request sent out via the active slave. It is possible that some switch or network configurations may result in situations wherein the backup slaves do not receive the ARP requests; in such a situation, validation of backup slaves must be disabled.”…””}”(hj- h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M†hjçubhÞ)”}”(hXThe validation of ARP requests on backup slaves is mainly helping bonding to decide which slaves are more likely to work in case of the active slave failure, it doesn't really guarantee that the backup slave will work if it's selected as the next active slave.”h]”hXThe validation of ARP requests on backup slaves is mainly helping bonding to decide which slaves are more likely to work in case of the active slave failure, it doesnâ€™t really guarantee that the backup slave will work if itâ€™s selected as the next active slave.”…””}”(hj; h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjçubhÞ)”}”(hXValidation is useful in network configurations in which multiple bonding hosts are concurrently issuing ARPs to one or more targets beyond a common switch. Should the link between the switch and target fail (but not the switch itself), the probe traffic generated by the multiple bonding instances will fool the standard ARP monitor into considering the links as still up. Use of validation can resolve this, as the ARP monitor will only consider ARP requests and replies associated with its own instance of bonding.”h]”hXValidation is useful in network configurations in which multiple bonding hosts are concurrently issuing ARPs to one or more targets beyond a common switch. Should the link between the switch and target fail (but not the switch itself), the probe traffic generated by the multiple bonding instances will fool the standard ARP monitor into considering the links as still up. Use of validation can resolve this, as the ARP monitor will only consider ARP requests and replies associated with its own instance of bonding.”…””}”(hjI h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M”hjçubhÞ)”}”(hŒ Filtering:”h]”hŒ Filtering:”…””}”(hjW h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MžhjçubhÞ)”}”(hŒáEnabling filtering causes the ARP monitor to only use incoming ARP packets for link availability purposes. Arriving packets that are not ARPs are delivered normally, but do not count when determining if a slave is available.”h]”hŒáEnabling filtering causes the ARP monitor to only use incoming ARP packets for link availability purposes. Arriving packets that are not ARPs are delivered normally, but do not count when determining if a slave is available.”…””}”(hje h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjçubhÞ)”}”(hŒÊFiltering operates by only considering the reception of ARP packets (any ARP packet, regardless of source or destination) when determining if a slave has received traffic for link availability purposes.”h]”hŒÊFiltering operates by only considering the reception of ARP packets (any ARP packet, regardless of source or destination) when determining if a slave has received traffic for link availability purposes.”…””}”(hjs h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¥hjçubhÞ)”}”(hXFiltering is useful in network configurations in which significant levels of third party broadcast traffic would fool the standard ARP monitor into considering the links as still up. Use of filtering can resolve this, as only ARP traffic is considered for link availability purposes.”h]”hXFiltering is useful in network configurations in which significant levels of third party broadcast traffic would fool the standard ARP monitor into considering the links as still up. Use of filtering can resolve this, as only ARP traffic is considered for link availability purposes.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MªhjçubhÞ)”}”(hŒ/This option was added in bonding version 3.1.0.”h]”hŒ/This option was added in bonding version 3.1.0.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M°hjçubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MZhjÈh²hubhÞ)”}”(hŒarp_all_targets”h]”hŒarp_all_targets”…””}”(hj£ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M²hjÈh²hubj )”}”(hXSpecifies the quantity of arp_ip_targets that must be reachable in order for the ARP monitor to consider a slave as being up. This option affects only active-backup mode for slaves with arp_validation enabled. Possible values are: any or 0 consider the slave up only when any of the arp_ip_targets is reachable all or 1 consider the slave up only when all of the arp_ip_targets are reachable ”h]”(hÞ)”}”(hŒÑSpecifies the quantity of arp_ip_targets that must be reachable in order for the ARP monitor to consider a slave as being up. This option affects only active-backup mode for slaves with arp_validation enabled.”h]”hŒÑSpecifies the quantity of arp_ip_targets that must be reachable in order for the ARP monitor to consider a slave as being up. This option affects only active-backup mode for slaves with arp_validation enabled.”…””}”(hjµ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M´hj± ubhÞ)”}”(hŒPossible values are:”h]”hŒPossible values are:”…””}”(hjÃ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¹hj± ubhÞ)”}”(hŒany or 0”h]”hŒany or 0”…””}”(hjÑ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M»hj± ubj )”}”(hŒGconsider the slave up only when any of the arp_ip_targets is reachable ”h]”hÞ)”}”(hŒFconsider the slave up only when any of the arp_ip_targets is reachable”h]”hŒFconsider the slave up only when any of the arp_ip_targets is reachable”…””}”(hjã h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M½hjß ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M½hj± ubhÞ)”}”(hŒall or 1”h]”hŒall or 1”…””}”(hj÷ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÀhj± ubj )”}”(hŒHconsider the slave up only when all of the arp_ip_targets are reachable ”h]”hÞ)”}”(hŒGconsider the slave up only when all of the arp_ip_targets are reachable”h]”hŒGconsider the slave up only when all of the arp_ip_targets are reachable”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÂhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÂhj± ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M´hjÈh²hubhÞ)”}”(hŒarp_missed_max”h]”hŒarp_missed_max”…””}”(hj# h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÅhjÈh²hubj )”}”(hXrSpecifies the number of arp_interval monitor checks that must fail in order for an interface to be marked down by the ARP monitor. In order to provide orderly failover semantics, backup interfaces are permitted an extra monitor check (i.e., they must fail arp_missed_max + 1 times before being marked down). The default value is 2, and the allowable range is 1 - 255. ”h]”(hÞ)”}”(hŒ‚Specifies the number of arp_interval monitor checks that must fail in order for an interface to be marked down by the ARP monitor.”h]”hŒ‚Specifies the number of arp_interval monitor checks that must fail in order for an interface to be marked down by the ARP monitor.”…””}”(hj5 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÇhj1 ubhÞ)”}”(hŒ°In order to provide orderly failover semantics, backup interfaces are permitted an extra monitor check (i.e., they must fail arp_missed_max + 1 times before being marked down).”h]”hŒ°In order to provide orderly failover semantics, backup interfaces are permitted an extra monitor check (i.e., they must fail arp_missed_max + 1 times before being marked down).”…””}”(hjC h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÊhj1 ubhÞ)”}”(hŒ;The default value is 2, and the allowable range is 1 - 255.”h]”hŒ;The default value is 2, and the allowable range is 1 - 255.”…””}”(hjQ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÎhj1 ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÇhjÈh²hubhÞ)”}”(hŒcoupled_control”h]”hŒcoupled_control”…””}”(hje h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÐhjÈh²hubj )”}”(hXœSpecifies whether the LACP state machine's MUX in the 802.3ad mode should have separate Collecting and Distributing states. This is by implementing the independent control state machine per IEEE 802.1AX-2008 5.4.15 in addition to the existing coupled control state machine. The default value is 1. This setting does not separate the Collecting and Distributing states, maintaining the bond in coupled control. ”h]”(hÞ)”}”(hŒ{Specifies whether the LACP state machine's MUX in the 802.3ad mode should have separate Collecting and Distributing states.”h]”hŒ}Specifies whether the LACP state machineâ€™s MUX in the 802.3ad mode should have separate Collecting and Distributing states.”…””}”(hjw h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÒhjs ubhÞ)”}”(hŒ•This is by implementing the independent control state machine per IEEE 802.1AX-2008 5.4.15 in addition to the existing coupled control state machine.”h]”hŒ•This is by implementing the independent control state machine per IEEE 802.1AX-2008 5.4.15 in addition to the existing coupled control state machine.”…””}”(hj… h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÕhjs ubhÞ)”}”(hŒ‡The default value is 1. This setting does not separate the Collecting and Distributing states, maintaining the bond in coupled control.”h]”hŒ‡The default value is 1. This setting does not separate the Collecting and Distributing states, maintaining the bond in coupled control.”…””}”(hj“ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÙhjs ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÒhjÈh²hubhÞ)”}”(hŒ downdelay”h]”hŒ downdelay”…””}”(hj§ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÜhjÈh²hubj )”}”(hX7Specifies the time, in milliseconds, to wait before disabling a slave after a link failure has been detected. This option is only valid for the miimon link monitor. The downdelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0. ”h]”hÞ)”}”(hX6Specifies the time, in milliseconds, to wait before disabling a slave after a link failure has been detected. This option is only valid for the miimon link monitor. The downdelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0.”h]”hX6Specifies the time, in milliseconds, to wait before disabling a slave after a link failure has been detected. This option is only valid for the miimon link monitor. The downdelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0.”…””}”(hj¹ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÞhjµ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÞhjÈh²hubhÞ)”}”(hŒ fail_over_mac”h]”hŒ fail_over_mac”…””}”(hjÍ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MåhjÈh²hubj )”}”(hX² Specifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bond's MAC address in accordance with the selected policy. Possible values are: none or 0 This setting disables fail_over_mac, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time. This is the default. active or 1 The "active" fail_over_mac policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover. This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor). The down side of this policy is that every device on the network must be updated via gratuitous ARP, vs. just updating a switch or set of switches (which often takes place for any traffic, not just ARP traffic, if the switch snoops incoming traffic to update its tables) for the traditional method. If the gratuitous ARP is lost, communication may be disrupted. When this policy is used in conjunction with the mii monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required. follow or 2 The "follow" fail_over_mac policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address). This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address. The default policy is none, unless the first slave cannot change its MAC address, in which case the active policy is selected by default. This option may be modified via sysfs only when no slaves are present in the bond. This option was added in bonding version 3.2.0. The "follow" policy was added in bonding version 3.3.0. ”•Ih]”(hÞ)”}”(hŒêSpecifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bond's MAC address in accordance with the selected policy.”h]”hŒìSpecifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bondâ€™s MAC address in accordance with the selected policy.”…””}”(hjß h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MçhjÛ ubhÞ)”}”(hŒPossible values are:”h]”hŒPossible values are:”…””}”(hjí h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MìhjÛ ubhÞ)”}”(hŒ none or 0”h]”hŒ none or 0”…””}”(hjû h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MîhjÛ ubj )”}”(hŒ¦This setting disables fail_over_mac, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time. This is the default. ”h]”hÞ)”}”(hŒ¥This setting disables fail_over_mac, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time. This is the default.”h]”hŒ¥This setting disables fail_over_mac, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time. This is the default.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mðhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MðhjÛ ubhÞ)”}”(hŒactive or 1”h]”hŒactive or 1”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MõhjÛ ubj )”}”(hX(The "active" fail_over_mac policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover. This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor). The down side of this policy is that every device on the network must be updated via gratuitous ARP, vs. just updating a switch or set of switches (which often takes place for any traffic, not just ARP traffic, if the switch snoops incoming traffic to update its tables) for the traditional method. If the gratuitous ARP is lost, communication may be disrupted. When this policy is used in conjunction with the mii monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required. ”h]”(hÞ)”}”(hŒûThe "active" fail_over_mac policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover.”h]”hŒÿThe â€œactiveâ€ fail_over_mac policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover.”…””}”(hj3h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M÷hj/ubhÞ)”}”(hŒ½This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor).”h]”hŒ½This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor).”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mýhj/ubhÞ)”}”(hXjThe down side of this policy is that every device on the network must be updated via gratuitous ARP, vs. just updating a switch or set of switches (which often takes place for any traffic, not just ARP traffic, if the switch snoops incoming traffic to update its tables) for the traditional method. If the gratuitous ARP is lost, communication may be disrupted.”h]”hXjThe down side of this policy is that every device on the network must be updated via gratuitous ARP, vs. just updating a switch or set of switches (which often takes place for any traffic, not just ARP traffic, if the switch snoops incoming traffic to update its tables) for the traditional method. If the gratuitous ARP is lost, communication may be disrupted.”…””}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj/ubhÞ)”}”(hŒÿWhen this policy is used in conjunction with the mii monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required.”h]”hŒÿWhen this policy is used in conjunction with the mii monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required.”…””}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj/ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M÷hjÛ ubhÞ)”}”(hŒfollow or 2”h]”hŒfollow or 2”…””}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÛ ubj )”}”(hXBThe "follow" fail_over_mac policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address). This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address. ”h]”(hÞ)”}”(hXšThe "follow" fail_over_mac policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address).”h]”hX¢The â€œfollowâ€ fail_over_mac policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bondâ€™s MAC address at failover time (and the formerly active slave receives the newly active slaveâ€™s MAC address).”…””}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjubhÞ)”}”(hŒ¤This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address.”h]”hŒ¤This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address.”…””}”(hj‘h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MhjÛ ubhÞ)”}”(hŒ‰The default policy is none, unless the first slave cannot change its MAC address, in which case the active policy is selected by default.”h]”hŒ‰The default policy is none, unless the first slave cannot change its MAC address, in which case the active policy is selected by default.”…””}”(hj¥h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M"hjÛ ubhÞ)”}”(hŒRThis option may be modified via sysfs only when no slaves are present in the bond.”h]”hŒRThis option may be modified via sysfs only when no slaves are present in the bond.”…””}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M&hjÛ ubhÞ)”}”(hŒhThis option was added in bonding version 3.2.0. The "follow" policy was added in bonding version 3.3.0.”h]”hŒlThis option was added in bonding version 3.2.0. The â€œfollowâ€ policy was added in bonding version 3.3.0.”…””}”(hjÁh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M)hjÛ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MçhjÈh²hubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hXlacp_active Option specifying whether to send LACPDU frames periodically. off or 0 LACPDU frames acts as "speak when spoken to". on or 1 LACPDU frames are sent along the configured links periodically. See lacp_rate for more details. The default is on. ”h]”(hŒterm”“”)”}”(hŒlacp_active”h]”hŒlacp_active”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M6hjÜubhŒ definition”“”)”}”(hhh]”(hÞ)”}”(hŒ=Option specifying whether to send LACPDU frames periodically.”h]”hŒ=Option specifying whether to send LACPDU frames periodically.”…””}”(hjõh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M-hjòubjÖ)”}”(hhh]”(jÛ)”}”(hŒ7off or 0 LACPDU frames acts as "speak when spoken to". ”h]”(já)”}”(hŒoff or 0”h]”hŒoff or 0”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M0hjubjñ)”}”(hhh]”hÞ)”}”(hŒ-LACPDU frames acts as "speak when spoken to".”h]”hŒ1LACPDU frames acts as â€œspeak when spoken toâ€.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M0hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M0hjubjÛ)”}”(hŒhon or 1 LACPDU frames are sent along the configured links periodically. See lacp_rate for more details. ”h]”(já)”}”(hŒon or 1”h]”hŒon or 1”…””}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M4hj5ubjñ)”}”(hhh]”hÞ)”}”(hŒ_LACPDU frames are sent along the configured links periodically. See lacp_rate for more details.”h]”hŒ_LACPDU frames are sent along the configured links periodically. See lacp_rate for more details.”…””}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M3hjGubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhj5ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M4hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjòubhÞ)”}”(hŒThe default is on.”h]”hŒThe default is on.”…””}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6hjòubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhjÜubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M6hj×ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÈh²hh³hÇh´NubhÞ)”}”(hŒ lacp_rate”h]”hŒ lacp_rate”…””}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M8hjÈh²hubj )”}”(hX%Option specifying the rate in which we'll ask our link partner to transmit LACPDU packets in 802.3ad mode. Possible values are: slow or 0 Request partner to transmit LACPDUs every 30 seconds fast or 1 Request partner to transmit LACPDUs every 1 second The default is slow. ”h]”(hÞ)”}”(hŒ€Option specifying the rate in which we'll ask our link partner to transmit LACPDU packets in 802.3ad mode. Possible values are:”h]”hŒ‚Option specifying the rate in which weâ€™ll ask our link partner to transmit LACPDU packets in 802.3ad mode. Possible values are:”…””}”(hjœh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M:hj˜ubjÖ)”}”(hhh]”(jÛ)”}”(hŒ?slow or 0 Request partner to transmit LACPDUs every 30 seconds ”h]”(já)”}”(hŒ slow or 0”h]”hŒ slow or 0”…””}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M?hjubjñ)”}”(hhh]”hÞ)”}”(hŒ4Request partner to transmit LACPDUs every 30 seconds”h]”hŒ4Request partner to transmit LACPDUs every 30 seconds”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M?hj¿ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M?hjªubjÛ)”}”(hŒ=fast or 1 Request partner to transmit LACPDUs every 1 second ”h]”(já)”}”(hŒ fast or 1”h]”hŒ fast or 1”…””}”(hjàh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´MBhjÜubjñ)”}”(hhh]”hÞ)”}”(hŒ2Request partner to transmit LACPDUs every 1 second”h]”hŒ2Request partner to transmit LACPDUs every 1 second”…””}”(hjñh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MBhjîubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhjÜubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´MBhjªubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhj˜ubhÞ)”}”(hŒThe default is slow.”h]”hŒThe default is slow.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MDhj˜ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M:hjÈh²hubhÞ)”}”(hŒbroadcast_neighbor”h]”hŒbroadcast_neighbor”…””}”(hj% h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MFhjÈh²hubj )”}”(hŒ¢Option specifying whether to broadcast ARP/ND packets to all active slaves. This option has no effect in modes other than 802.3ad mode. The default is off (0). ”h]”hÞ)”}”(hŒ¡Option specifying whether to broadcast ARP/ND packets to all active slaves. This option has no effect in modes other than 802.3ad mode. The default is off (0).”h]”hŒ¡Option specifying whether to broadcast ARP/ND packets to all active slaves. This option has no effect in modes other than 802.3ad mode. The default is off (0).”…””}”(hj7 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MHhj3 ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MHhjÈh²hubhÞ)”}”(hŒ max_bonds”h]”hŒ max_bonds”…””}”(hjK h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MLhjÈh²hubj )”}”(hX6Specifies the number of bonding devices to create for this instance of the bonding driver. E.g., if max_bonds is 3, and the bonding driver is not already loaded, then bond0, bond1 and bond2 will be created. The default value is 1. Specifying a value of 0 will load bonding, but will not create any devices. ”h]”hÞ)”}”(hX5Specifies the number of bonding devices to create for this instance of the bonding driver. E.g., if max_bonds is 3, and the bonding driver is not already loaded, then bond0, bond1 and bond2 will be created. The default value is 1. Specifying a value of 0 will load bonding, but will not create any devices.”h]”hX5Specifies the number of bonding devices to create for this instance of the bonding driver. E.g., if max_bonds is 3, and the bonding driver is not already loaded, then bond0, bond1 and bond2 will be created. The default value is 1. Specifying a value of 0 will load bonding, but will not create any devices.”…””}”(hj] h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MNhjY ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MNhjÈh²hubhÞ)”}”(hŒmiimon”h]”hŒmiimon”…””}”(hjq h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MThjÈh²hubj )”}”(hX#Specifies the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures. A value of zero disables MII link monitoring. A value of 100 is a good starting point. The default value is 100 if arp_interval is not set. ”h]”(hÞ)”}”(hŒìSpecifies the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures. A value of zero disables MII link monitoring. A value of 100 is a good starting point.”h]”hŒìSpecifies the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures. A value of zero disables MII link monitoring. A value of 100 is a good starting point.”…””}”(hjƒ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MVhj ubhÞ)”}”(hŒ4The default value is 100 if arp_interval is not set.”h]”hŒ4The default value is 100 if arp_interval is not set.”…””}”(hj‘ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M[hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MVhjÈh²hubhÞ)”}”(hŒ min_links”h]”hŒ min_links”…””}”(hj¥ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M]hjÈh²hubj )”}”(hX/Specifies the minimum number of links that must be active before asserting carrier. It is similar to the Cisco EtherChannel min-links feature. This allows setting the minimum number of member ports that must be up (link-up state) before marking the bond device as up (carrier on). This is useful for situations where higher level services such as clustering want to ensure a minimum number of low bandwidth links are active before switchover. This option only affect 802.3ad mode. The default value is 0. This will cause carrier to be asserted (for 802.3ad mode) whenever there is an active aggregator, regardless of the number of available links in that aggregator. Note that, because an aggregator cannot be active without at least one available link, setting this option to 0 or to 1 has the exact same effect. ”h]”(hÞ)”}”(hXàSpecifies the minimum number of links that must be active before asserting carrier. It is similar to the Cisco EtherChannel min-links feature. This allows setting the minimum number of member ports that must be up (link-up state) before marking the bond device as up (carrier on). This is useful for situations where higher level services such as clustering want to ensure a minimum number of low bandwidth links are active before switchover. This option only affect 802.3ad mode.”h]”hXàSpecifies the minimum number of links that must be active before asserting carrier. It is similar to the Cisco EtherChannel min-links feature. This allows setting the minimum number of member ports that must be up (link-up state) before marking the bond device as up (carrier on). This is useful for situations where higher level services such as clustering want to ensure a minimum number of low bandwidth links are active before switchover. This option only affect 802.3ad mode.”…””}”(hj· h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M_hj³ ubhÞ)”}”(hXLThe default value is 0. This will cause carrier to be asserted (for 802.3ad mode) whenever there is an active aggregator, regardless of the number of available links in that aggregator. Note that, because an aggregator cannot be active without at least one available link, setting this option to 0 or to 1 has the exact same effect.”h]”hXLThe default value is 0. This will cause carrier to be asserted (for 802.3ad mode) whenever there is an active aggregator, regardless of the number of available links in that aggregator. Note that, because an aggregator cannot be active without at least one available link, setting this option to 0 or to 1 has the exact same effect.”…””}”(hjÅ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhhj³ ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M_hjÈh²hubhÞ)”}”(hŒlacp_strict”h]”hŒlacp_strict”…””}”(hjÙ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MnhjÈh²hubj )”}”(hXšSpecifies the fallback behavior of a bonding when LACP negotiation fails on all slave links, i.e. when no slave is in the Collecting_Distributing state, while at least `min_links` link still reports carrier up. This option is only applicable to 802.3ad mode (mode 4). Valid values are: off or 0 One interface of the bond is selected to be active, in order to facilitate communication with peer devices that do not implement LACP. on or 1 Interfaces are only permitted to be made active if they have an active LACP partner and have successfully reached Collecting_Distributing state. The default value is 0 (off). ”h]”(hÞ)”}”(hŒÒSpecifies the fallback behavior of a bonding when LACP negotiation fails on all slave links, i.e. when no slave is in the Collecting_Distributing state, while at least `min_links` link still reports carrier up.”h]”(hŒ¨Specifies the fallback behavior of a bonding when LACP negotiation fails on all slave links, i.e. when no slave is in the Collecting_Distributing state, while at least ”…””}”(hjë h²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒ`min_links`”h]”hŒ min_links”…””}”(hjõ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jó hjë ubhŒ link still reports carrier up.”…””}”(hjë h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mphjç ubhÞ)”}”(hŒ8This option is only applicable to 802.3ad mode (mode 4).”h]”hŒ8This option is only applicable to 802.3ad mode (mode 4).”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Muhjç ubhÞ)”}”(hŒValid values are:”h]”hŒValid values are:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mwhjç ubjÖ)”}”(hhh]”(jÛ)”}”(hŒoff or 0 One interface of the bond is selected to be active, in order to facilitate communication with peer devices that do not implement LACP. ”h]”(já)”}”(hŒoff or 0”h]”hŒoff or 0”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M|hj,ubjñ)”}”(hhh]”hÞ)”}”(hŒ†One interface of the bond is selected to be active, in order to facilitate communication with peer devices that do not implement LACP.”h]”hŒ†One interface of the bond is selected to be active, in order to facilitate communication with peer devices that do not implement LACP.”…””}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mzhj>ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhj,ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M|hj)ubjÛ)”}”(hŒ™on or 1 Interfaces are only permitted to be made active if they have an active LACP partner and have successfully reached Collecting_Distributing state. ”h]”(já)”}”(hŒon or 1”h]”hŒon or 1”…””}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´Mhj[ubjñ)”}”(hhh]”hÞ)”}”(hŒInterfaces are only permitted to be made active if they have an active LACP partner and have successfully reached Collecting_Distributing state.”h]”hŒInterfaces are only permitted to be made active if they have an active LACP partner and have successfully reached Collecting_Distributing state.”…””}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjmubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhj[ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´Mhj)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjç ubhÞ)”}”(hŒThe default value is 0 (off).”h]”hŒThe default value is 0 (off).”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mƒhjç ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MphjÈh²hubhÞ)”}”(hŒmode”h]”hŒmode”…””}”(hj¤h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M…hjÈh²hubj )”}”(hX<Specifies one of the bonding policies. The default is balance-rr (round robin). Possible values are: balance-rr or 0 Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance. active-backup or 1 Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. In bonding version 2.6.2 or later, when a failover occurs in active-backup mode, bonding will issue one or more gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for the bonding master interface and each VLAN interfaces configured above it, provided that the interface has at least one IP address configured. Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate VLAN id. This mode provides fault tolerance. The primary option, documented below, affects the behavior of this mode. balance-xor or 2 XOR policy: Transmit based on the selected transmit hash policy. The default policy is a simple [(source MAC address XOR'd with destination MAC address XOR packet type ID) modulo slave count]. Alternate transmit policies may be selected via the xmit_hash_policy option, described below. This mode provides load balancing and fault tolerance. broadcast or 3 Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance. 802.3ad or 4 IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification. Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option, documented below. Note that not all transmit policies may be 802.3ad compliant, particularly in regards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Differing peer implementations will have varying tolerances for noncompliance. Prerequisites: 1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave. 2. A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode. balance-tlb or 5 Adaptive transmit load balancing: channel bonding that does not require any special switch support. In tlb_dynamic_lb=1 mode; the outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. In tlb_dynamic_lb=0 mode; the load balancing based on current load is disabled and the load is distributed only using the hash distribution. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave. balance-alb or 6 Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server. Receive traffic from connections created by the server is also balanced. When the local system sends an ARP Request the bonding driver copies and saves the peer's IP information from the ARP packet. When the ARP Reply arrives from the peer, its hardware address is retrieved and the bonding driver initiates an ARP reply to this peer assigning it to one of the slaves in the bond. A problematic outcome of using ARP negotiation for balancing is that each time that an ARP request is broadcast it uses the hardware address of the bond. Hence, peers learn the hardware address of the bond and the balancing of receive traffic collapses to the current slave. This is handled by sending updates (ARP Replies) to all the peers with their individually assigned hardware address such that the traffic is redistributed. Receive traffic is also redistributed when a new slave is added to the bond and when an inactive slave is re-activated. The receive load is distributed sequentially (round robin) among the group of highest speed slaves in the bond. When a link is reconnected or a new slave joins the bond the receive traffic is redistributed among all active slaves in the bond by initiating ARP Replies with the selected MAC address to each of the clients. The updelay parameter (detailed below) must be set to a value equal or greater than the switch's forwarding delay so that the ARP Replies sent to the peers will not be blocked by the switch. Prerequisites: 1. Ethtool support in the base drivers for retrieving the speed of each slave. 2. Base driver support for setting the hardware address of a device while it is open. This is required so that there will always be one slave in the team using the bond hardware address (the curr_active_slave) while having a unique hardware address for each slave in the bond. If the curr_active_slave fails its hardware address is swapped with the new curr_active_slave that was chosen. ”h]”(hÞ)”}”(hŒeSpecifies one of the bonding policies. The default is balance-rr (round robin). Possible values are:”h]”hŒeSpecifies one of the bonding policies. The default is balance-rr (round robin). Possible values are:”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‡hj²ubhÞ)”}”(hŒbalance-rr or 0”h]”hŒbalance-rr or 0”…””}”(hjÄh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŠhj²ubj )”}”(hŒ¢Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance. ”h]”hÞ)”}”(hŒ¡Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.”h]”hŒ¡Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŒhjÒubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MŒhj²ubhÞ)”}”(hŒactive-backup or 1”h]”hŒactive-backup or 1”…””}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‘hj²ubj )”}”(hXActive-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. In bonding version 2.6.2 or later, when a failover occurs in active-backup mode, bonding will issue one or more gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for the bonding master interface and each VLAN interfaces configured above it, provided that the interface has at least one IP address configured. Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate VLAN id. This mode provides fault tolerance. The primary option, documented below, affects the behavior of this mode. ”h]”(hÞ)”}”(hŒöActive-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch.”h]”hŒøActive-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bondâ€™s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch.”…””}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M“hjøubhÞ)”}”(hXŸIn bonding version 2.6.2 or later, when a failover occurs in active-backup mode, bonding will issue one or more gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for the bonding master interface and each VLAN interfaces configured above it, provided that the interface has at least one IP address configured. Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate VLAN id.”h]”hXŸIn bonding version 2.6.2 or later, when a failover occurs in active-backup mode, bonding will issue one or more gratuitous ARPs on the newly active slave. One gratuitous ARP is issued for the bonding master interface and each VLAN interfaces configured above it, provided that the interface has at least one IP address configured. Gratuitous ARPs issued for VLAN interfaces are tagged with the appropriate VLAN id.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M™hjøubhÞ)”}”(hŒmThis mode provides fault tolerance. The primary option, documented below, affects the behavior of this mode.”h]”hŒmThis mode provides fault tolerance. The primary option, documented below, affects the behavior of this mode.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¢hjøubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M“hj²ubhÞ)”}”(hŒbalance-xor or 2”h]”hŒbalance-xor or 2”…””}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¦hj²ubj )”}”(hXYXOR policy: Transmit based on the selected transmit hash policy. The default policy is a simple [(source MAC address XOR'd with destination MAC address XOR packet type ID) modulo slave count]. Alternate transmit policies may be selected via the xmit_hash_policy option, described below. This mode provides load balancing and fault tolerance. ”h]”(hÞ)”}”(hX XOR policy: Transmit based on the selected transmit hash policy. The default policy is a simple [(source MAC address XOR'd with destination MAC address XOR packet type ID) modulo slave count]. Alternate transmit policies may be selected via the xmit_hash_policy option, described below.”h]”hX"XOR policy: Transmit based on the selected transmit hash policy. The default policy is a simple [(source MAC address XORâ€™d with destination MAC address XOR packet type ID) modulo slave count]. Alternate transmit policies may be selected via the xmit_hash_policy option, described below.”…””}”(hj>h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¨hj:ubhÞ)”}”(hŒ6This mode provides load balancing and fault tolerance.”h]”hŒ6This mode provides load balancing and fault tolerance.”…””}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¯hj:ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M¨hj²ubhÞ)”}”(hŒbroadcast or 3”h]”hŒbroadcast or 3”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M±hj²ubj )”}”(hŒeBroadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance. ”h]”hÞ)”}”(hŒdBroadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.”h]”hŒdBroadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.”…””}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M³hjnubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M³hj²ubhÞ)”}”(hŒ802.3ad or 4”h]”hŒ802.3ad or 4”…””}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¶hj²ubj )”}”(hX~IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification. Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option, documented below. Note that not all transmit policies may be 802.3ad compliant, particularly in regards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Differing peer implementations will have varying tolerances for noncompliance. Prerequisites: 1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave. 2. A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode. ”h]”(hÞ)”}”(hŒÇIEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.”h]”hŒÇIEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¸hj”ubhÞ)”}”(hX¸Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option, documented below. Note that not all transmit policies may be 802.3ad compliant, particularly in regards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Differing peer implementations will have varying tolerances for noncompliance.”h]”hX¸Slave selection for outgoing traffic is done according to the transmit hash policy, which may be changed from the default simple XOR policy via the xmit_hash_policy option, documented below. Note that not all transmit policies may be 802.3ad compliant, particularly in regards to the packet mis-ordering requirements of section 43.2.4 of the 802.3ad standard. Differing peer implementations will have varying tolerances for noncompliance.”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M½hj”ubhÞ)”}”(hŒPrerequisites:”h]”hŒPrerequisites:”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÇhj”ubhÞ)”}”(hŒY1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave.”h]”hŒY1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave.”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÉhj”ubhÞ)”}”(hŒ@2. A switch that supports IEEE 802.3ad Dynamic link aggregation.”h]”hŒ@2. A switch that supports IEEE 802.3ad Dynamic link aggregation.”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÌhj”ubhÞ)”}”(hŒMMost switches will require some type of configuration to enable 802.3ad mode.”h]”hŒMMost switches will require some type of configuration to enable 802.3ad mode.”…””}”(hjÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÏhj”ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M¸hj²ubhÞ)”}”(hŒbalance-tlb or 5”h]”hŒbalance-tlb or 5”…””}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÒhj²ubj )”}”(hXuAdaptive transmit load balancing: channel bonding that does not require any special switch support. In tlb_dynamic_lb=1 mode; the outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. In tlb_dynamic_lb=0 mode; the load balancing based on current load is disabled and the load is distributed only using the hash distribution. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave. ”h]”(hÞ)”}”(hŒcAdaptive transmit load balancing: channel bonding that does not require any special switch support.”h]”hŒcAdaptive transmit load balancing: channel bonding that does not require any special switch support.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÔhjubhÞ)”}”(hŒ‹In tlb_dynamic_lb=1 mode; the outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave.”h]”hŒ‹In tlb_dynamic_lb=1 mode; the outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M×hjubhÞ)”}”(hŒŒIn tlb_dynamic_lb=0 mode; the load balancing based on current load is disabled and the load is distributed only using the hash distribution.”h]”hŒŒIn tlb_dynamic_lb=0 mode; the load balancing based on current load is disabled and the load is distributed only using the hash distribution.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÛhjubhÞ)”}”(hŒ˜Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.”h]”hŒ˜Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.”…””}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MßhjubhÞ)”}”(hŒ Prerequisite:”h]”hŒ Prerequisite:”…””}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MãhjubhÞ)”}”(hŒKEthtool support in the base drivers for retrieving the speed of each slave.”h]”hŒKEthtool support in the base drivers for retrieving the speed of each slave.”…””}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Måhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÔhj²ubhÞ)”}”(hŒbalance-alb or 6”h]”hŒbalance-alb or 6”…””}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mèhj²ubj )”}”(hXt Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server. Receive traffic from connections created by the server is also balanced. When the local system sends an ARP Request the bonding driver copies and saves the peer's IP information from the ARP packet. When the ARP Reply arrives from the peer, its hardware address is retrieved and the bonding driver initiates an ARP reply to this peer assigning it to one of the slaves in the bond. A problematic outcome of using ARP negotiation for balancing is that each time that an ARP request is broadcast it uses the hardware address of the bond. Hence, peers learn the hardware address of the bond and the balancing of receive traffic collapses to the current slave. This is handled by sending updates (ARP Replies) to all the peers with their individually assigned hardware address such that the traffic is redistributed. Receive traffic is also redistributed when a new slave is added to the bond and when an inactive slave is re-activated. The receive load is distributed sequentially (round robin) among the group of highest speed slaves in the bond. When a link is reconnected or a new slave joins the bond the receive traffic is redistributed among all active slaves in the bond by initiating ARP Replies with the selected MAC address to each of the clients. The updelay parameter (detailed below) must be set to a value equal or greater than the switch's forwarding delay so that the ARP Replies sent to the peers will not be blocked by the switch. Prerequisites: 1. Ethtool support in the base drivers for retrieving the speed of each slave. 2. Base driver support for setting the hardware address of a device while it is open. This is required so that there will always be one slave in the team using the bond hardware address (the curr_active_slave) while having a unique hardware address for each slave in the bond. If the curr_active_slave fails its hardware address is swapped with the new curr_active_slave that was chosen. ”h]”(hÞ)”}”(hXÞAdaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.”h]”hXÞAdaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.”…””}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MêhjlubhÞ)”}”(hXReceive traffic from connections created by the server is also balanced. When the local system sends an ARP Request the bonding driver copies and saves the peer's IP information from the ARP packet. When the ARP Reply arrives from the peer, its hardware address is retrieved and the bonding driver initiates an ARP reply to this peer assigning it to one of the slaves in the bond. A problematic outcome of using ARP negotiation for balancing is that each time that an ARP request is broadcast it uses the hardware address of the bond. Hence, peers learn the hardware address of the bond and the balancing of receive traffic collapses to the current slave. This is handled by sending updates (ARP Replies) to all the peers with their individually assigned hardware address such that the traffic is redistributed. Receive traffic is also redistributed when a new slave is added to the bond and when an inactive slave is re-activated. The receive load is distributed sequentially (round robin) among the group of highest speed slaves in the bond.”h]”hXReceive traffic from connections created by the server is also balanced. When the local system sends an ARP Request the bonding driver copies and saves the peerâ€™s IP information from the ARP packet. When the ARP Reply arrives from the peer, its hardware address is retrieved and the bonding driver initiates an ARP reply to this peer assigning it to one of the slaves in the bond. A problematic outcome of using ARP negotiation for balancing is that each time that an ARP request is broadcast it uses the hardware address of the bond. Hence, peers learn the hardware address of the bond and the balancing of receive traffic collapses to the current slave. This is handled by sending updates (ARP Replies) to all the peers with their individually assigned hardware address such that the traffic is redistributed. Receive traffic is also redistributed when a new slave is added to the bond and when an inactive slave is re-activated. The receive load is distributed sequentially (round robin) among the group of highest speed slaves in the bond.”…””}”(hj~h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MõhjlubhÞ)”}”(hXWhen a link is reconnected or a new slave joins the bond the receive traffic is redistributed among all active slaves in the bond by initiating ARP Replies with the selected MAC address to each of the clients. The updelay parameter (detailed below) must be set to a value equal or greater than the switch's forwarding delay so that the ARP Replies sent to the peers will not be blocked by the switch.”h]”hX’When a link is reconnected or a new slave joins the bond the receive traffic is redistributed among all active slaves in the bond by initiating ARP Replies with the selected MAC address to each of the clients. The updelay parameter (detailed below) must be set to a value equal or greater than the switchâ€™s forwarding delay so that the ARP Replies sent to the peers will not be blocked by the switch.”…””}”(hjŒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjlubhÞ)”}”(hŒPrerequisites:”h]”hŒPrerequisites:”…””}”(hjšh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjlubhÞ)”}”(hŒN1. Ethtool support in the base drivers for retrieving the speed of each slave.”h]”hŒN1. Ethtool support in the base drivers for retrieving the speed of each slave.”…””}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjlubhÞ)”}”(hX…2. Base driver support for setting the hardware address of a device while it is open. This is required so that there will always be one slave in the team using the bond hardware address (the curr_active_slave) while having a unique hardware address for each slave in the bond. If the curr_active_slave fails its hardware address is swapped with the new curr_active_slave that was chosen.”h]”hX…2. Base driver support for setting the hardware address of a device while it is open. This is required so that there will always be one slave in the team using the bond hardware address (the curr_active_slave) while having a unique hardware address for each slave in the bond. If the curr_active_slave fails its hardware address is swapped with the new curr_active_slave that was chosen.”…””}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjlubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Mêhj²ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M‡hjÈh²hubhÞ)”}”(hŒnum_grat_arp, num_unsol_na”h]”hŒnum_grat_arp, num_unsol_na”…””}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M"hjÈh²hubj )”}”(hXòSpecify the number of peer notifications (gratuitous ARPs and unsolicited IPv6 Neighbor Advertisements) to be issued after a failover event. As soon as the link is up on the new slave (possibly immediately) a peer notification is sent on the bonding device and each VLAN sub-device. This is repeated at the rate specified by peer_notif_delay if the number is greater than 1. The valid range is 0 - 255; the default value is 1. These options affect the active-backup or 802.3ad (broadcast_neighbor enabled) mode. These options were added for bonding versions 3.3.0 and 3.4.0 respectively. From Linux 3.0 and bonding version 3.7.1, these notifications are generated by the ipv4 and ipv6 code and the numbers of repetitions cannot be set independently. ”h]”(hÞ)”}”(hXwSpecify the number of peer notifications (gratuitous ARPs and unsolicited IPv6 Neighbor Advertisements) to be issued after a failover event. As soon as the link is up on the new slave (possibly immediately) a peer notification is sent on the bonding device and each VLAN sub-device. This is repeated at the rate specified by peer_notif_delay if the number is greater than 1.”h]”hXwSpecify the number of peer notifications (gratuitous ARPs and unsolicited IPv6 Neighbor Advertisements) to be issued after a failover event. As soon as the link is up on the new slave (possibly immediately) a peer notification is sent on the bonding device and each VLAN sub-device. This is repeated at the rate specified by peer_notif_delay if the number is greater than 1.”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M%hjÞubhÞ)”}”(hŒÕThe valid range is 0 - 255; the default value is 1. These options affect the active-backup or 802.3ad (broadcast_neighbor enabled) mode. These options were added for bonding versions 3.3.0 and 3.4.0 respectively.”h]”hŒÕThe valid range is 0 - 255; the default value is 1. These options affect the active-backup or 802.3ad (broadcast_neighbor enabled) mode. These options were added for bonding versions 3.3.0 and 3.4.0 respectively.”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M-hjÞubhÞ)”}”(hŒ¡From Linux 3.0 and bonding version 3.7.1, these notifications are generated by the ipv4 and ipv6 code and the numbers of repetitions cannot be set independently.”h]”hŒ¡From Linux 3.0 and bonding version 3.7.1, these notifications are generated by the ipv4 and ipv6 code and the numbers of repetitions cannot be set independently.”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M2hjÞubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M%hjÈh²hubhÞ)”}”(hŒpackets_per_slave”h]”hŒpackets_per_slave”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6hjÈh²hubj )”}”(hŒðSpecify the number of packets to transmit through a slave before moving to the next one. When set to 0 then a slave is chosen at random. The valid range is 0 - 65535; the default value is 1. This option has effect only in balance-rr mode. ”h]”(hÞ)”}”(hŒˆSpecify the number of packets to transmit through a slave before moving to the next one. When set to 0 then a slave is chosen at random.”h]”hŒˆSpecify the number of packets to transmit through a slave before moving to the next one. When set to 0 then a slave is chosen at random.”…””}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M8hj ubhÞ)”}”(hŒeThe valid range is 0 - 65535; the default value is 1. This option has effect only in balance-rr mode.”h]”hŒeThe valid range is 0 - 65535; the default value is 1. This option has effect only in balance-rr mode.”…””}”(hj2h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MSpecifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This option is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:”h]”hX>Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This option is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MchjubhÞ)”}”(hŒalways or 0 (default)”h]”hŒalways or 0 (default)”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mihjubj )”}”(hŒFThe primary slave becomes the active slave whenever it comes back up. ”h]”hÞ)”}”(hŒEThe primary slave becomes the active slave whenever it comes back up.”h]”hŒEThe primary slave becomes the active slave whenever it comes back up.”…””}”(hj4h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mkhj0ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MkhjubhÞ)”}”(hŒbetter or 1”h]”hŒbetter or 1”…””}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mnhjubj )”}”(hŒ°The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave. ”h]”hÞ)”}”(hŒ¯The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.”h]”hŒ¯The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.”…””}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MphjVubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MphjubhÞ)”}”(hŒfailure or 2”h]”hŒfailure or 2”…””}”(hjnh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Muhjubj )”}”(hŒoThe primary slave becomes the active slave only if the current active slave fails and the primary slave is up. ”h]”hÞ)”}”(hŒnThe primary slave becomes the active slave only if the current active slave fails and the primary slave is up.”h]”hŒnThe primary slave becomes the active slave only if the current active slave fails and the primary slave is up.”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mwhj|ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MwhjubhÞ)”}”(hŒ5The primary_reselect setting is ignored in two cases:”h]”hŒ5The primary_reselect setting is ignored in two cases:”…””}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mzhjubj )”}”(hŒ›If no slaves are active, the first slave to recover is made the active slave. When initially enslaved, the primary slave is always made the active slave. ”h]”(hÞ)”}”(hŒMIf no slaves are active, the first slave to recover is made the active slave.”h]”hŒMIf no slaves are active, the first slave to recover is made the active slave.”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M|hj¢ubhÞ)”}”(hŒKWhen initially enslaved, the primary slave is always made the active slave.”h]”hŒKWhen initially enslaved, the primary slave is always made the active slave.”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj¢ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M|hjubhÞ)”}”(hŒåChanging the primary_reselect policy via sysfs will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances.”h]”hŒåChanging the primary_reselect policy via sysfs will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances.”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‚hjubhÞ)”}”(hŒ0This option was added for bonding version 3.6.0.”h]”hŒ0This option was added for bonding version 3.6.0.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‡hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MchjÈh²hubhÞ)”}”(hŒtlb_dynamic_lb”h]”hŒtlb_dynamic_lb”…””}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‰hjÈh²hubj )”}”(hXLSpecifies if dynamic shuffling of flows is enabled in tlb or alb mode. The value has no effect on any other modes. The default behavior of tlb mode is to shuffle active flows across slaves based on the load in that interval. This gives nice lb characteristics but can cause packet reordering. If re-ordering is a concern use this variable to disable flow shuffling and rely on load balancing provided solely by the hash distribution. xmit-hash-policy can be used to select the appropriate hashing for the setup. The sysfs entry can be used to change the setting per bond device and the initial value is derived from the module parameter. The sysfs entry is allowed to be changed only if the bond device is down. The default value is "1" that enables flow shuffling while value "0" disables it. This option was added in bonding driver 3.7.1 ”h]”(hÞ)”}”(hŒrSpecifies if dynamic shuffling of flows is enabled in tlb or alb mode. The value has no effect on any other modes.”h]”hŒrSpecifies if dynamic shuffling of flows is enabled in tlb or alb mode. The value has no effect on any other modes.”…””}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‹hjøubhÞ)”}”(hXŒThe default behavior of tlb mode is to shuffle active flows across slaves based on the load in that interval. This gives nice lb characteristics but can cause packet reordering. If re-ordering is a concern use this variable to disable flow shuffling and rely on load balancing provided solely by the hash distribution. xmit-hash-policy can be used to select the appropriate hashing for the setup.”•3h]”hXŒThe default behavior of tlb mode is to shuffle active flows across slaves based on the load in that interval. This gives nice lb characteristics but can cause packet reordering. If re-ordering is a concern use this variable to disable flow shuffling and rely on load balancing provided solely by the hash distribution. xmit-hash-policy can be used to select the appropriate hashing for the setup.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŽhjøubhÞ)”}”(hŒÇThe sysfs entry can be used to change the setting per bond device and the initial value is derived from the module parameter. The sysfs entry is allowed to be changed only if the bond device is down.”h]”hŒÇThe sysfs entry can be used to change the setting per bond device and the initial value is derived from the module parameter. The sysfs entry is allowed to be changed only if the bond device is down.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M–hjøubhÞ)”}”(hŒThe default value is "1" that enables flow shuffling while value "0" disables it. This option was added in bonding driver 3.7.1”h]”hŒ‡The default value is â€œ1â€ that enables flow shuffling while value â€œ0â€ disables it. This option was added in bonding driver 3.7.1”…””}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M›hjøubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M‹hjÈh²hubhÞ)”}”(hŒupdelay”h]”hŒupdelay”…””}”(hj:h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŸhjÈh²hubj )”}”(hX5Specifies the time, in milliseconds, to wait before enabling a slave after a link recovery has been detected. This option is only valid for the miimon link monitor. The updelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0. ”h]”hÞ)”}”(hX4Specifies the time, in milliseconds, to wait before enabling a slave after a link recovery has been detected. This option is only valid for the miimon link monitor. The updelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0.”h]”hX4Specifies the time, in milliseconds, to wait before enabling a slave after a link recovery has been detected. This option is only valid for the miimon link monitor. The updelay value should be a multiple of the miimon value; if not, it will be rounded down to the nearest multiple. The default value is 0.”…””}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¡hjHubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M¡hjÈh²hubhÞ)”}”(hŒuse_carrier”h]”hŒuse_carrier”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M§hjÈh²hubj )”}”(hXObsolete option that previously selected between MII / ETHTOOL ioctls and netif_carrier_ok() to determine link state. All link state checks are now done with netif_carrier_ok(). For backwards compatibility, this option's value may be inspected or set. The only valid setting is 1. ”h]”(hÞ)”}”(hŒuObsolete option that previously selected between MII / ETHTOOL ioctls and netif_carrier_ok() to determine link state.”h]”hŒuObsolete option that previously selected between MII / ETHTOOL ioctls and netif_carrier_ok() to determine link state.”…””}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M©hjnubhÞ)”}”(hŒ;All link state checks are now done with netif_carrier_ok().”h]”hŒ;All link state checks are now done with netif_carrier_ok().”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjnubhÞ)”}”(hŒgFor backwards compatibility, this option's value may be inspected or set. The only valid setting is 1.”h]”hŒiFor backwards compatibility, this optionâ€™s value may be inspected or set. The only valid setting is 1.”…””}”(hjŽh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¯hjnubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M©hjÈh²hubhÞ)”}”(hŒxmit_hash_policy”h]”hŒxmit_hash_policy”…””}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M²hjÈh²hubj )”}”(hX<Selects the transmit hash policy to use for slave selection in balance-xor, 802.3ad, and tlb modes. Possible values are: layer2 Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is hash = source MAC[5] XOR destination MAC[5] XOR packet type ID slave number = hash modulo slave count This algorithm will place all traffic to a particular network peer on the same slave. This algorithm is 802.3ad compliant. layer2+3 This policy uses a combination of layer2 and layer3 protocol information to generate the hash. Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is hash = source MAC[5] XOR destination MAC[5] XOR packet type ID hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) And then hash is reduced modulo slave count. If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash. This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations. This algorithm is 802.3ad compliant. layer3+4 This policy uses upper layer protocol information, when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. The formula for unfragmented TCP and UDP packets is hash = source port, destination port (as in the header) hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) hash = hash RSHIFT 1 And then hash is reduced modulo slave count. If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash. For fragmented TCP or UDP packets and all other IPv4 and IPv6 protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This algorithm is not fully 802.3ad compliant. A single TCP or UDP conversation containing both fragmented and unfragmented packets will see packets striped across two interfaces. This may result in out of order delivery. Most traffic types will not meet this criteria, as TCP rarely fragments traffic, and most UDP traffic is not involved in extended conversations. Other implementations of 802.3ad may or may not tolerate this noncompliance. encap2+3 This policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows. encap3+4 This policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows. vlan+srcmac This policy uses a very rudimentary vlan ID and source mac hash to load-balance traffic per-vlan, with failover should one leg fail. The intended use case is for a bond shared by multiple virtual machines, all configured to use their own vlan, to give lacp-like functionality without requiring lacp-capable switching hardware. The formula for the hash is simply hash = (vlan ID) XOR (source MAC vendor) XOR (source MAC dev) The default value is layer2. This option was added in bonding version 2.6.3. In earlier versions of bonding, this parameter does not exist, and the layer2 policy is the only policy. The layer2+3 value was added for bonding version 3.2.2. ”h]”(hÞ)”}”(hŒySelects the transmit hash policy to use for slave selection in balance-xor, 802.3ad, and tlb modes. Possible values are:”h]”hŒySelects the transmit hash policy to use for slave selection in balance-xor, 802.3ad, and tlb modes. Possible values are:”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M´hj°ubhÞ)”}”(hŒlayer2”h]”hŒlayer2”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M·hj°ubj )”}”(hXEUses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is hash = source MAC[5] XOR destination MAC[5] XOR packet type ID slave number = hash modulo slave count This algorithm will place all traffic to a particular network peer on the same slave. This algorithm is 802.3ad compliant. ”h]”(hÞ)”}”(hŒ`Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is”h]”hŒ`Uses XOR of hardware MAC addresses and packet type ID field to generate the hash. The formula is”…””}”(hjÔh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¹hjÐubhÞ)”}”(hŒehash = source MAC[5] XOR destination MAC[5] XOR packet type ID slave number = hash modulo slave count”h]”hŒehash = source MAC[5] XOR destination MAC[5] XOR packet type ID slave number = hash modulo slave count”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¼hjÐubhÞ)”}”(hŒUThis algorithm will place all traffic to a particular network peer on the same slave.”h]”hŒUThis algorithm will place all traffic to a particular network peer on the same slave.”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¿hjÐubhÞ)”}”(hŒ$This algorithm is 802.3ad compliant.”h]”hŒ$This algorithm is 802.3ad compliant.”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÂhjÐubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M¹hj°ubhÞ)”}”(hŒlayer2+3”h]”hŒlayer2+3”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÄhj°ubj )”}”(hX‘This policy uses a combination of layer2 and layer3 protocol information to generate the hash. Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is hash = source MAC[5] XOR destination MAC[5] XOR packet type ID hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) And then hash is reduced modulo slave count. If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash. This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations. This algorithm is 802.3ad compliant. ”h]”(hÞ)”}”(hŒ^This policy uses a combination of layer2 and layer3 protocol information to generate the hash.”h]”hŒ^This policy uses a combination of layer2 and layer3 protocol information to generate the hash.”…””}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÆhj ubhÞ)”}”(hŒYUses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is”h]”hŒYUses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is”…””}”(hj2h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÉhj ubhÞ)”}”(hŒÙhash = source MAC[5] XOR destination MAC[5] XOR packet type ID hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) And then hash is reduced modulo slave count.”h]”hŒÙhash = source MAC[5] XOR destination MAC[5] XOR packet type ID hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) And then hash is reduced modulo slave count.”…””}”(hj@h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÌhj ubhÞ)”}”(hŒhIf the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash.”h]”hŒhIf the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash.”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÒhj ubhÞ)”}”(hŒªThis algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.”h]”hŒªThis algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.”…””}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÕhj ubhÞ)”}”(hŒ¾This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.”h]”hŒ¾This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.”…””}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÚhj ubhÞ)”}”(hŒ$This algorithm is 802.3ad compliant.”h]”hŒ$This algorithm is 802.3ad compliant.”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mßhj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MÆhj°ubhÞ)”}”(hŒlayer3+4”h]”hŒlayer3+4”…””}”(hjŒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Máhj°ubj )”}”(hXThis policy uses upper layer protocol information, when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. The formula for unfragmented TCP and UDP packets is hash = source port, destination port (as in the header) hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) hash = hash RSHIFT 1 And then hash is reduced modulo slave count. If the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash. For fragmented TCP or UDP packets and all other IPv4 and IPv6 protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. This algorithm is not fully 802.3ad compliant. A single TCP or UDP conversation containing both fragmented and unfragmented packets will see packets striped across two interfaces. This may result in out of order delivery. Most traffic types will not meet this criteria, as TCP rarely fragments traffic, and most UDP traffic is not involved in extended conversations. Other implementations of 802.3ad may or may not tolerate this noncompliance. ”h]”(hÞ)”}”(hŒãThis policy uses upper layer protocol information, when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.”h]”hŒãThis policy uses upper layer protocol information, when available, to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MãhjšubhÞ)”}”(hŒ3The formula for unfragmented TCP and UDP packets is”h]”hŒ3The formula for unfragmented TCP and UDP packets is”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MéhjšubhÞ)”}”(hŒçhash = source port, destination port (as in the header) hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) hash = hash RSHIFT 1 And then hash is reduced modulo slave count.”h]”hŒçhash = source port, destination port (as in the header) hash = hash XOR source IP XOR destination IP hash = hash XOR (hash RSHIFT 16) hash = hash XOR (hash RSHIFT 8) hash = hash RSHIFT 1 And then hash is reduced modulo slave count.”…””}”(hjºh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MëhjšubhÞ)”}”(hŒhIf the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash.”h]”hŒhIf the protocol is IPv6 then the source and destination addresses are first hashed using ipv6_addr_hash.”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MòhjšubhÞ)”}”(hŒÜFor fragmented TCP or UDP packets and all other IPv4 and IPv6 protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.”h]”hŒÜFor fragmented TCP or UDP packets and all other IPv4 and IPv6 protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MõhjšubhÞ)”}”(hX¿This algorithm is not fully 802.3ad compliant. A single TCP or UDP conversation containing both fragmented and unfragmented packets will see packets striped across two interfaces. This may result in out of order delivery. Most traffic types will not meet this criteria, as TCP rarely fragments traffic, and most UDP traffic is not involved in extended conversations. Other implementations of 802.3ad may or may not tolerate this noncompliance.”h]”hX¿This algorithm is not fully 802.3ad compliant. A single TCP or UDP conversation containing both fragmented and unfragmented packets will see packets striped across two interfaces. This may result in out of order delivery. Most traffic types will not meet this criteria, as TCP rarely fragments traffic, and most UDP traffic is not involved in extended conversations. Other implementations of 802.3ad may or may not tolerate this noncompliance.”…””}”(hjäh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mûhjšubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Mãhj°ubhÞ)”}”(hŒencap2+3”h]”hŒencap2+3”…””}”(hjøh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj°ubj )”}”(hXMThis policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows. ”h]”hÞ)”}”(hXLThis policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows.”h]”hXLThis policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Mhj°ubhÞ)”}”(hŒencap3+4”h]”hŒencap3+4”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj°ubj )”}”(hXMThis policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows. ”h]”hÞ)”}”(hXLThis policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows.”h]”hXLThis policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. For example this will improve the performance for tunnel users because the packets will be distributed according to the encapsulated flows.”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj,ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Mhj°ubhÞ)”}”(hŒvlan+srcmac”h]”hŒvlan+srcmac”…””}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj°ubj )”}”(hXªThis policy uses a very rudimentary vlan ID and source mac hash to load-balance traffic per-vlan, with failover should one leg fail. The intended use case is for a bond shared by multiple virtual machines, all configured to use their own vlan, to give lacp-like functionality without requiring lacp-capable switching hardware. The formula for the hash is simply hash = (vlan ID) XOR (source MAC vendor) XOR (source MAC dev) ”h]”(hÞ)”}”(hXFThis policy uses a very rudimentary vlan ID and source mac hash to load-balance traffic per-vlan, with failover should one leg fail. The intended use case is for a bond shared by multiple virtual machines, all configured to use their own vlan, to give lacp-like functionality without requiring lacp-capable switching hardware.”h]”hXFThis policy uses a very rudimentary vlan ID and source mac hash to load-balance traffic per-vlan, with failover should one leg fail. The intended use case is for a bond shared by multiple virtual machines, all configured to use their own vlan, to give lacp-like functionality without requiring lacp-capable switching hardware.”…””}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjRubhÞ)”}”(hŒ"The formula for the hash is simply”h]”hŒ"The formula for the hash is simply”…””}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M"hjRubhÞ)”}”(hŒ=hash = (vlan ID) XOR (source MAC vendor) XOR (source MAC dev)”h]”hŒ=hash = (vlan ID) XOR (source MAC vendor) XOR (source MAC dev)”…””}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M$hjRubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´Mhj°ubhÞ)”}”(hŒðThe default value is layer2. This option was added in bonding version 2.6.3. In earlier versions of bonding, this parameter does not exist, and the layer2 policy is the only policy. The layer2+3 value was added for bonding version 3.2.2.”h]”hŒðThe default value is layer2. This option was added in bonding version 2.6.3. In earlier versions of bonding, this parameter does not exist, and the layer2 policy is the only policy. The layer2+3 value was added for bonding version 3.2.2.”…””}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M&hj°ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M´hjÈh²hubhÞ)”}”(hŒresend_igmp”h]”hŒresend_igmp”…””}”(hjšh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M+hjÈh²hubj )”}”(hXØSpecifies the number of IGMP membership reports to be issued after a failover event. One membership report is issued immediately after the failover, subsequent packets are sent in each 200ms interval. The valid range is 0 - 255; the default value is 1. A value of 0 prevents the IGMP membership report from being issued in response to the failover event. This option is useful for bonding modes balance-rr (0), active-backup (1), balance-tlb (5) and balance-alb (6), in which a failover can switch the IGMP traffic from one slave to another. Therefore a fresh IGMP report must be issued to cause the switch to forward the incoming IGMP traffic over the newly selected slave. This option was added for bonding version 3.7.0. ”h]”(hÞ)”}”(hŒÈSpecifies the number of IGMP membership reports to be issued after a failover event. One membership report is issued immediately after the failover, subsequent packets are sent in each 200ms interval.”h]”hŒÈSpecifies the number of IGMP membership reports to be issued after a failover event. One membership report is issued immediately after the failover, subsequent packets are sent in each 200ms interval.”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M-hj¨ubhÞ)”}”(hŒ™The valid range is 0 - 255; the default value is 1. A value of 0 prevents the IGMP membership report from being issued in response to the failover event.”h]”hŒ™The valid range is 0 - 255; the default value is 1. A value of 0 prevents the IGMP membership report from being issued in response to the failover event.”…””}”(hjºh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M1hj¨ubhÞ)”}”(hX@This option is useful for bonding modes balance-rr (0), active-backup (1), balance-tlb (5) and balance-alb (6), in which a failover can switch the IGMP traffic from one slave to another. Therefore a fresh IGMP report must be issued to cause the switch to forward the incoming IGMP traffic over the newly selected slave.”h]”hX@This option is useful for bonding modes balance-rr (0), active-backup (1), balance-tlb (5) and balance-alb (6), in which a failover can switch the IGMP traffic from one slave to another. Therefore a fresh IGMP report must be issued to cause the switch to forward the incoming IGMP traffic over the newly selected slave.”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M5hj¨ubhÞ)”}”(hŒ0This option was added for bonding version 3.7.0.”h]”hŒ0This option was added for bonding version 3.7.0.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M;hj¨ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M-hjÈh²hubhÞ)”}”(hŒlp_interval”h]”hŒlp_interval”…””}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M=hjÈh²hubj )”}”(hŒüSpecifies the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch. The valid range is 1 - 0x7fffffff; the default value is 1. This Option has effect only in balance-tlb and balance-alb modes. ”h]”(hÞ)”}”(hŒ}Specifies the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch.”h]”hŒ}Specifies the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch.”…””}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M?hjøubhÞ)”}”(hŒ|The valid range is 1 - 0x7fffffff; the default value is 1. This Option has effect only in balance-tlb and balance-alb modes.”h]”hŒ|The valid range is 1 - 0x7fffffff; the default value is 1. This Option has effect only in balance-tlb and balance-alb modes.”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MBhjøubeh}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M?hjÈh²hubeh}”(h]”Œbonding-driver-options”ah ]”h"]”Œ2. bonding driver options”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒ3. Configuring Bonding Devices”h]”hŒ3. Configuring Bonding Devices”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj&h²hh³hÇh´MFubhÞ)”}”(hXbYou can configure bonding using either your distro's network initialization scripts, or manually using either iproute2 or the sysfs interface. Distros generally use one of three packages for the network initialization scripts: initscripts, sysconfig or interfaces. Recent versions of these packages have support for bonding, while older versions do not.”h]”hXdYou can configure bonding using either your distroâ€™s network initialization scripts, or manually using either iproute2 or the sysfs interface. Distros generally use one of three packages for the network initialization scripts: initscripts, sysconfig or interfaces. Recent versions of these packages have support for bonding, while older versions do not.”…””}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MHhj&h²hubhÞ)”}”(hXAWe will first describe the options for configuring bonding for distros using versions of initscripts, sysconfig and interfaces with full or partial support for bonding, then provide information on enabling bonding without support from the network initialization scripts (i.e., older versions of initscripts or sysconfig).”h]”hXAWe will first describe the options for configuring bonding for distros using versions of initscripts, sysconfig and interfaces with full or partial support for bonding, then provide information on enabling bonding without support from the network initialization scripts (i.e., older versions of initscripts or sysconfig).”…””}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MOhj&h²hubhÞ)”}”(hŒ«If you're unsure whether your distro uses sysconfig, initscripts or interfaces, or don't know if it's new enough, have no fear. Determining this is fairly straightforward.”h]”hŒ±If youâ€™re unsure whether your distro uses sysconfig, initscripts or interfaces, or donâ€™t know if itâ€™s new enough, have no fear. Determining this is fairly straightforward.”…””}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MUhj&h²hubhÞ)”}”(hŒ·First, look for a file called interfaces in /etc/network directory. If this file is present in your system, then your system use interfaces. See Configuration with Interfaces Support.”h]”hŒ·First, look for a file called interfaces in /etc/network directory. If this file is present in your system, then your system use interfaces. See Configuration with Interfaces Support.”…””}”(hjah²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MYhj&h²hubhÞ)”}”(hŒElse, issue the command::”h]”hŒElse, issue the command:”…””}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M]hj&h²hubhŒ literal_block”“”)”}”(hŒ$ rpm -qf /sbin/ifup”h]”hŒ$ rpm -qf /sbin/ifup”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M_hj&h²hubhÞ)”}”(hŒ¸It will respond with a line of text starting with either "initscripts" or "sysconfig," followed by some numbers. This is the package that provides your network initialization scripts.”h]”hŒÀIt will respond with a line of text starting with either â€œinitscriptsâ€ or â€œsysconfig,â€ followed by some numbers. This is the package that provides your network initialization scripts.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mahj&h²hubhÞ)”}”(hŒMNext, to determine if your installation supports bonding, issue the command::”h]”hŒLNext, to determine if your installation supports bonding, issue the command:”…””}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mehj&h²hubj~)”}”(hŒ$ grep ifenslave /sbin/ifup”h]”hŒ$ grep ifenslave /sbin/ifup”…””}”hj©sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mhhj&h²hubhÞ)”}”(hŒXIf this returns any matches, then your initscripts or sysconfig has support for bonding.”h]”hŒXIf this returns any matches, then your initscripts or sysconfig has support for bonding.”…””}”(hj·h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mjhj&h²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ(3.1 Configuration with Sysconfig Support”h]”hŒ(3.1 Configuration with Sysconfig Support”…””}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÅh²hh³hÇh´MnubhÞ)”}”(hŒThis section applies to distros using a version of sysconfig with bonding support, for example, SuSE Linux Enterprise Server 9.”h]”hŒThis section applies to distros using a version of sysconfig with bonding support, for example, SuSE Linux Enterprise Server 9.”…””}”(hjÖh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MphjÅh²hubhÞ)”}”(hŒûSuSE SLES 9's networking configuration system does support bonding, however, at this writing, the YaST system configuration front end does not provide any means to work with bonding devices. Bonding devices can be managed by hand, however, as follows.”h]”hŒýSuSE SLES 9â€™s networking configuration system does support bonding, however, at this writing, the YaST system configuration front end does not provide any means to work with bonding devices. Bonding devices can be managed by hand, however, as follows.”…””}”(hjäh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MshjÅh²hubhÞ)”}”(hXÚFirst, if they have not already been configured, configure the slave devices. On SLES 9, this is most easily done by running the yast2 sysconfig configuration utility. The goal is for to create an ifcfg-id file for each slave device. The simplest way to accomplish this is to configure the devices for DHCP (this is only to get the file ifcfg-id file created; see below for some issues with DHCP). The name of the configuration file for each device will be of the form::”h]”hXÙFirst, if they have not already been configured, configure the slave devices. On SLES 9, this is most easily done by running the yast2 sysconfig configuration utility. The goal is for to create an ifcfg-id file for each slave device. The simplest way to accomplish this is to configure the devices for DHCP (this is only to get the file ifcfg-id file created; see below for some issues with DHCP). The name of the configuration file for each device will be of the form:”…””}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MxhjÅh²hubj~)”}”(hŒifcfg-id-xx:xx:xx:xx:xx:xx”h]”hŒifcfg-id-xx:xx:xx:xx:xx:xx”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M€hjÅh²hubhÞ)”}”(hŒ`Where the "xx" portion will be replaced with the digits from the device's permanent MAC address.”h]”hŒfWhere the â€œxxâ€ portion will be replaced with the digits from the deviceâ€™s permanent MAC address.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‚hjÅh²hubhÞ)”}”(hX Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been created, it is necessary to edit the configuration files for the slave devices (the MAC addresses correspond to those of the slave devices). Before editing, the file will contain multiple lines, and will look something like this::”h]”hXOnce the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been created, it is necessary to edit the configuration files for the slave devices (the MAC addresses correspond to those of the slave devices). Before editing, the file will contain multiple lines, and will look something like this:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M…hjÅh²hubj~)”}”(hŒfBOOTPROTO='dhcp' STARTMODE='on' USERCTL='no' UNIQUE='XNzu.WeZGOGF+4wE' _nm_name='bus-pci-0001:61:01.0'”h]”hŒfBOOTPROTO='dhcp' STARTMODE='on' USERCTL='no' UNIQUE='XNzu.WeZGOGF+4wE' _nm_name='bus-pci-0001:61:01.0'”…””}”hj*sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M‹hjÅh²hubhÞ)”}”(hŒ;Change the BOOTPROTO and STARTMODE lines to the following::”h]”hŒ:Change the BOOTPROTO and STARTMODE lines to the following:”…””}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‘hjÅh²hubj~)”}”(hŒ BOOTPROTO='none' STARTMODE='off'”h]”hŒ BOOTPROTO='none' STARTMODE='off'”…””}”hjFsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M“hjÅh²hubhÞ)”}”(hŒRDo not alter the UNIQUE or _nm_name lines. Remove any other lines (USERCTL, etc).”h]”hŒRDo not alter the UNIQUE or _nm_name lines. Remove any other lines (USERCTL, etc).”…””}”(hjTh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M–hjÅh²hubhÞ)”}”(hX™Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified, it's time to create the configuration file for the bonding device itself. This file is named ifcfg-bondX, where X is the number of the bonding device to create, starting at 0. The first such file is ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig network configuration system will correctly start multiple instances of bonding.”h]”hX›Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified, itâ€™s time to create the configuration file for the bonding device itself. This file is named ifcfg-bondX, where X is the number of the bonding device to create, starting at 0. The first such file is ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig network configuration system will correctly start multiple instances of bonding.”…””}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M™hjÅh²hubhÞ)”}”(hŒ4The contents of the ifcfg-bondX file is as follows::”h]”hŒ3The contents of the ifcfg-bondX file is as follows:”…””}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¡hjÅh²hubj~)”}”(hXBOOTPROTO="static" BROADCAST="10.0.2.255" IPADDR="10.0.2.10" NETMASK="255.255.0.0" NETWORK="10.0.2.0" REMOTE_IPADDR="" STARTMODE="onboot" BONDING_MASTER="yes" BONDING_MODULE_OPTS="mode=active-backup miimon=100" BONDING_SLAVE0="eth0" BONDING_SLAVE1="bus-pci-0000:06:08.1"”h]”hXBOOTPROTO="static" BROADCAST="10.0.2.255" IPADDR="10.0.2.10" NETMASK="255.255.0.0" NETWORK="10.0.2.0" REMOTE_IPADDR="" STARTMODE="onboot" BONDING_MASTER="yes" BONDING_MODULE_OPTS="mode=active-backup miimon=100" BONDING_SLAVE0="eth0" BONDING_SLAVE1="bus-pci-0000:06:08.1"”…””}”hj~sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M£hjÅh²hubhÞ)”}”(hŒnReplace the sample BROADCAST, IPADDR, NETMASK and NETWORK values with the appropriate values for your network.”h]”hŒnReplace the sample BROADCAST, IPADDR, NETMASK and NETWORK values with the appropriate values for your network.”…””}”(hjŒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¯hjÅh²hubhÞ)”}”(hŒSThe STARTMODE specifies when the device is brought online. The possible values are:”h]”hŒSThe STARTMODE specifies when the device is brought online. The possible values are:”…””}”(hjšh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M²hjÅh²hubj )”}”(hXb======== ====================================================== onboot The device is started at boot time. If you're not sure, this is probably what you want. manual The device is started only when ifup is called manually. Bonding devices may be configured this way if you do not wish them to start automatically at boot for some reason. hotplug The device is started by a hotplug event. This is not a valid choice for a bonding device. off or The device configuration is ignored. ignore ======== ====================================================== ”h]”j±)”}”(hhh]”j¶)”}”(hhh]”(j»)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jºhj¯ubj»)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K6uh1jºhj¯ubj)”}”(hhh]”(jÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒonboot”h]”hŒonboot”…””}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¶hjÌubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjÉubjÛ)”}”(hhh]”hÞ)”}”(hŒXThe device is started at boot time. If you're not sure, this is probably what you want.”h]”hŒZThe device is started at boot time. If youâ€™re not sure, this is probably what you want.”…””}”(hjæh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¶hjãubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjÉubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÆubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒmanual”h]”hŒmanual”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¹hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjubjÛ)”}”(hhh]”hÞ)”}”(hŒ¬The device is started only when ifup is called manually. Bonding devices may be configured this way if you do not wish them to start automatically at boot for some reason.”h]”hŒ¬The device is started only when ifup is called manually. Bonding devices may be configured this way if you do not wish them to start automatically at boot for some reason.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¹hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÆubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒhotplug”h]”hŒhotplug”…””}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¾hj:ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj7ubjÛ)”}”(hhh]”hÞ)”}”(hŒ[The device is started by a hotplug event. This is not a valid choice for a bonding device.”h]”hŒ[The device is started by a hotplug event. This is not a valid choice for a bonding device.”…””}”(hjTh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¾hjQubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj7ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÆubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒoff or”h]”hŒoff or”…””}”(hjth²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÁhjqubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjnubjÛ)”}”(hhh]”hÞ)”}”(hŒ$The device configuration is ignored.”h]”hŒ$The device configuration is ignored.”…””}”(hj‹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÁhjˆubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhjnubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÆubjÖ)”}”(hhh]”(jÛ)”}”(hhh]”hÞ)”}”(hŒignore”h]”hŒignore”…””}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÂhj¨ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj¥ubjÛ)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1jÚhj¥ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjÆubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj¯ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1jµhj¬ubah}”(h]”h ]”h"]”h$]”h&]”uh1j°hj¨ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´MµhjÅh²hubhÞ)”}”(hŒtThe line BONDING_MASTER='yes' indicates that the device is a bonding master device. The only useful value is "yes."”h]”hŒ|The line BONDING_MASTER=â€™yesâ€™ indicates that the device is a bonding master device. The only useful value is â€œyes.â€”…””}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÅhjÅh²hubhÞ)”}”(hX5The contents of BONDING_MODULE_OPTS are supplied to the instance of the bonding module for this device. Specify the options for the bonding mode, link monitoring, and so on here. Do not include the max_bonds bonding parameter; this will confuse the configuration system if you have multiple bonding devices.”h]”hX5The contents of BONDING_MODULE_OPTS are supplied to the instance of the bonding module for this device. Specify the options for the bonding mode, link monitoring, and so on here. Do not include the max_bonds bonding parameter; this will confuse the configuration system if you have multiple bonding devices.”…””}”(hjõh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÈhjÅh²hubhÞ)”}”(hXâFinally, supply one BONDING_SLAVEn="slave device" for each slave. where "n" is an increasing value, one for each slave. The "slave device" is either an interface name, e.g., "eth0", or a device specifier for the network device. The interface name is easier to find, but the ethN names are subject to change at boot time if, e.g., a device early in the sequence has failed. The device specifiers (bus-pci-0000:06:08.1 in the example above) specify the physical network device, and will not change unless the device's bus location changes (for example, it is moved from one PCI slot to another). The example above uses one of each type for demonstration purposes; most configurations will choose one or the other for all slave devices.”h]”hXôFinally, supply one BONDING_SLAVEn=â€slave deviceâ€ for each slave. where â€œnâ€ is an increasing value, one for each slave. The â€œslave deviceâ€ is either an interface name, e.g., â€œeth0â€, or a device specifier for the network device. The interface name is easier to find, but the ethN names are subject to change at boot time if, e.g., a device early in the sequence has failed. The device specifiers (bus-pci-0000:06:08.1 in the example above) specify the physical network device, and will not change unless the deviceâ€™s bus location changes (for example, it is moved from one PCI slot to another). The example above uses one of each type for demonstration purposes; most configurations will choose one or the other for all slave devices.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÎhjÅh²hubhÞ)”}”(hŒ´When all configuration files have been modified or created, networking must be restarted for the configuration changes to take effect. This can be accomplished via the following::”h]”hŒ³When all configuration files have been modified or created, networking must be restarted for the configuration changes to take effect. This can be accomplished via the following:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÚhjÅh²hubj~)”}”(hŒ# /etc/init.d/network restart”h]”hŒ# /etc/init.d/network restart”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MÞhjÅh²hubhÞ)”}”(hŒàNote that the network control script (/sbin/ifdown) will remove the bonding module as part of the network shutdown processing, so it is not necessary to remove the module by hand if, e.g., the module parameters have changed.”h]”hŒàNote that the network control script (/sbin/ifdown) will remove the bonding module as part of the network shutdown processing, so it is not necessary to remove the module by hand if, e.g., the module parameters have changed.”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MàhjÅh²hubhÞ)”}”(hŒäAlso, at this writing, YaST/YaST2 will not manage bonding devices (they do not show bonding interfaces on its list of network devices). It is necessary to edit the configuration file by hand to change the bonding configuration.”h]”hŒäAlso, at this writing, YaST/YaST2 will not manage bonding devices (they do not show bonding interfaces on its list of network devices). It is necessary to edit the configuration file by hand to change the bonding configuration.”…””}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MåhjÅh²hubhÞ)”}”(hŒpAdditional general options and details of the ifcfg file format can be found in an example ifcfg template file::”h]”hŒoAdditional general options and details of the ifcfg file format can be found in an example ifcfg template file:”…””}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MêhjÅh²hubj~)”}”(hŒ%/etc/sysconfig/network/ifcfg.template”h]”hŒ%/etc/sysconfig/network/ifcfg.template”…””}”hjWsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MíhjÅh²hubhÞ)”}”(hŒ‰Note that the template does not document the various ``BONDING_*`` settings described above, but does describe many of the other options.”h]”(hŒ5Note that the template does not document the various ”…””}”(hjeh²hh³Nh´Nubjð)”}”(hŒ ``BONDING_*``”h]”hŒ BONDING_*”…””}”(hjmh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjeubhŒG settings described above, but does describe many of the other options.”…””}”(hjeh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MïhjÅh²hubeh}”(h]”Œ$configuration-with-sysconfig-support”ah ]”h"]”Œ(3.1 configuration with sysconfig support”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MnubhÉ)”}”(hhh]”(hÎ)”}”(hŒ3.1.1 Using DHCP with Sysconfig”h]”hŒ3.1.1 Using DHCP with Sysconfig”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´MóubhÞ)”}”(hXaUnder sysconfig, configuring a device with BOOTPROTO='dhcp' will cause it to query DHCP for its IP address information. At this writing, this does not function for bonding devices; the scripts attempt to obtain the device address from DHCP prior to adding any of the slave devices. Without active slaves, the DHCP requests are not sent to the network.”h]”hXeUnder sysconfig, configuring a device with BOOTPROTO=â€™dhcpâ€™ will cause it to query DHCP for its IP address information. At this writing, this does not function for bonding devices; the scripts attempt to obtain the device address from DHCP prior to adding any of the slave devices. Without active slaves, the DHCP requests are not sent to the network.”…””}”(hjžh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mõhjh²hubeh}”(h]”Œusing-dhcp-with-sysconfig”ah ]”h"]”Œ3.1.1 using dhcp with sysconfig”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MóubhÉ)”}”(hhh]”(hÎ)”}”(hŒ/3.1.2 Configuring Multiple Bonds with Sysconfig”h]”hŒ/3.1.2 Configuring Multiple Bonds with Sysconfig”…””}”(hj·h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj´h²hh³hÇh´MýubhÞ)”}”(hX¨The sysconfig network initialization system is capable of handling multiple bonding devices. All that is necessary is for each bonding instance to have an appropriately configured ifcfg-bondX file (as described above). Do not specify the "max_bonds" parameter to any instance of bonding, as this will confuse sysconfig. If you require multiple bonding devices with identical parameters, create multiple ifcfg-bondX files.”h]”hX¬The sysconfig network initialization system is capable of handling multiple bonding devices. All that is necessary is for each bonding instance to have an appropriately configured ifcfg-bondX file (as described above). Do not specify the â€œmax_bondsâ€ parameter to any instance of bonding, as this will confuse sysconfig. If you require multiple bonding devices with identical parameters, create multiple ifcfg-bondX files.”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mÿhj´h²hubhÞ)”}”(hŒµBecause the sysconfig scripts supply the bonding module options in the ifcfg-bondX file, it is not necessary to add them to the system ``/etc/modules.d/*.conf`` configuration files.”h]”(hŒ‡Because the sysconfig scripts supply the bonding module options in the ifcfg-bondX file, it is not necessary to add them to the system ”…””}”(hjÓh²hh³Nh´Nubjð)”}”(hŒ``/etc/modules.d/*.conf``”h]”hŒ/etc/modules.d/*.conf”…””}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjÓubhŒ configuration files.”…””}”(hjÓh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj´h²hubeh}”(h]”Œ)configuring-multiple-bonds-with-sysconfig”ah ]”h"]”Œ/3.1.2 configuring multiple bonds with sysconfig”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MýubhÉ)”}”(hhh]”(hÎ)”}”(hŒ*3.2 Configuration with Initscripts Support”h]”hŒ*3.2 Configuration with Initscripts Support”…””}”(hjþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjûh²hh³hÇh´MubhÞ)”}”(hX©This section applies to distros using a recent version of initscripts with bonding support, for example, Red Hat Enterprise Linux version 3 or later, Fedora, etc. On these systems, the network initialization scripts have knowledge of bonding, and can be configured to control bonding devices. Note that older versions of the initscripts package have lower levels of support for bonding; this will be noted where applicable.”h]”hX©This section applies to distros using a recent version of initscripts with bonding support, for example, Red Hat Enterprise Linux version 3 or later, Fedora, etc. On these systems, the network initialization scripts have knowledge of bonding, and can be configured to control bonding devices. Note that older versions of the initscripts package have lower levels of support for bonding; this will be noted where applicable.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjûh²hubhÞ)”}”(hXAThese distros will not automatically load the network adapter driver unless the ethX device is configured with an IP address. Because of this constraint, users must manually configure a network-script file for all physical adapters that will be members of a bondX link. Network script files are located in the directory:”h]”hXAThese distros will not automatically load the network adapter driver unless the ethX device is configured with an IP address. Because of this constraint, users must manually configure a network-script file for all physical adapters that will be members of a bondX link. Network script files are located in the directory:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjûh²hubhÞ)”}”(hŒ/etc/sysconfig/network-scripts”h]”hŒ/etc/sysconfig/network-scripts”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjûh²hubhÞ)”}”(hŒëThe file name must be prefixed with "ifcfg-eth" and suffixed with the adapter's physical adapter number. For example, the script for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0. Place the following text in the file::”h]”hŒðThe file name must be prefixed with â€œifcfg-ethâ€ and suffixed with the adapterâ€™s physical adapter number. For example, the script for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0. Place the following text in the file:”…””}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjûh²hubj~)”}”(hŒGDEVICE=eth0 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none”h]”hŒGDEVICE=eth0 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none”…””}”hjDsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M#hjûh²hubhÞ)”}”(hX±The DEVICE= line will be different for every ethX device and must correspond with the name of the file, i.e., ifcfg-eth1 must have a device line of DEVICE=eth1. The setting of the MASTER= line will also depend on the final bonding interface name chosen for your bond. As with other network devices, these typically start at 0, and go up one for each device, i.e., the first bonding instance is bond0, the second is bond1, and so on.”h]”hX±The DEVICE= line will be different for every ethX device and must correspond with the name of the file, i.e., ifcfg-eth1 must have a device line of DEVICE=eth1. The setting of the MASTER= line will also depend on the final bonding interface name chosen for your bond. As with other network devices, these typically start at 0, and go up one for each device, i.e., the first bonding instance is bond0, the second is bond1, and so on.”…””}”(hjRh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M*hjûh²hubhÞ)”}”(hX"Next, create a bond network script. The file name for this script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is the number of the bond. For bond0 the file is named "ifcfg-bond0", for bond1 it is named "ifcfg-bond1", and so on. Within that file, place the following text::”h]”hX)Next, create a bond network script. The file name for this script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is the number of the bond. For bond0 the file is named â€œifcfg-bond0â€, for bond1 it is named â€œifcfg-bond1â€, and so on. Within that file, place the following text:”…””}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M2hjûh²hubj~)”}”(hŒ†DEVICE=bond0 IPADDR=192.168.1.1 NETMASK=255.255.255.0 NETWORK=192.168.1.0 BROADCAST=192.168.1.255 ONBOOT=yes BOOTPROTO=none USERCTL=no”h]”hŒ†DEVICE=bond0 IPADDR=192.168.1.1 NETMASK=255.255.255.0 NETWORK=192.168.1.0 BROADCAST=192.168.1.255 ONBOOT=yes BOOTPROTO=none USERCTL=no”…””}”hjnsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M8hjûh²hubhÞ)”}”(hŒ}Be sure to change the networking specific lines (IPADDR, NETMASK, NETWORK and BROADCAST) to match your network configuration.”h]”hŒ}Be sure to change the networking specific lines (IPADDR, NETMASK, NETWORK and BROADCAST) to match your network configuration.”…””}”(hj|h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MAhjûh²hubhÞ)”}”(hŒþFor later versions of initscripts, such as that found with Fedora 7 (or later) and Red Hat Enterprise Linux version 5 (or later), it is possible, and, indeed, preferable, to specify the bonding options in the ifcfg-bond0 file, e.g. a line of the format::”h]”hŒýFor later versions of initscripts, such as that found with Fedora 7 (or later) and Red Hat Enterprise Linux version 5 (or later), it is possible, and, indeed, preferable, to specify the bonding options in the ifcfg-bond0 file, e.g. a line of the format:”…””}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MDhjûh²hubj~)”}”(hŒMBONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"”h]”hŒMBONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"”…””}”hj˜sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MIhjûh²hubhÞ)”}”(hXÐwill configure the bond with the specified options. The options specified in BONDING_OPTS are identical to the bonding module parameters except for the arp_ip_target field when using versions of initscripts older than and 8.57 (Fedora 8) and 8.45.19 (Red Hat Enterprise Linux 5.2). When using older versions each target should be included as a separate option and should be preceded by a '+' to indicate it should be added to the list of queried targets, e.g.,::”h]”hXÓwill configure the bond with the specified options. The options specified in BONDING_OPTS are identical to the bonding module parameters except for the arp_ip_target field when using versions of initscripts older than and 8.57 (Fedora 8) and 8.45.19 (Red Hat Enterprise Linux 5.2). When using older versions each target should be included as a separate option and should be preceded by a â€˜+â€™ to indicate it should be added to the list of queried targets, e.g.,:”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MKhjûh²hubj~)”}”(hŒ5arp_ip_target=+192.168.1.1 arp_ip_target=+192.168.1.2”h]”hŒ5arp_ip_target=+192.168.1.1 arp_ip_target=+192.168.1.2”…””}”hj´sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MShjûh²hubhÞ)”}”(hŒ”is the proper syntax to specify multiple targets. When specifying options via BONDING_OPTS, it is not necessary to edit ``/etc/modprobe.d/*.conf``.”h]”(hŒyis the proper syntax to specify multiple targets. When specifying options via BONDING_OPTS, it is not necessary to edit ”…””}”(hjÂh²hh³Nh´Nubjð)”}”(hŒ``/etc/modprobe.d/*.conf``”h]”hŒ/etc/modprobe.d/*.conf”…””}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjÂubhŒ.”…””}”(hjÂh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MUhjûh²hubhÞ)”}”(hXVFor even older versions of initscripts that do not support BONDING_OPTS, it is necessary to edit /etc/modprobe.d/*.conf, depending upon your distro) to load the bonding module with your desired options when the bond0 interface is brought up. The following lines in /etc/modprobe.d/*.conf will load the bonding module, and select its options:”h]”(hŒqFor even older versions of initscripts that do not support BONDING_OPTS, it is necessary to edit /etc/modprobe.d/”…””}”(hjâh²hh³Nh´NubhŒemphasis”“”)”}”(hŒª*.conf, depending upon your distro) to load the bonding module with your desired options when the bond0 interface is brought up. The following lines in /etc/modprobe.d/*”h]”hŒ¨.conf, depending upon your distro) to load the bonding module with your desired options when the bond0 interface is brought up. The following lines in /etc/modprobe.d/”…””}”(hjìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhjâubhŒ;.conf will load the bonding module, and select its options:”…””}”(hjâh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MYhjûh²hubj )”}”(hŒ>alias bond0 bonding options bond0 mode=balance-alb miimon=100 ”h]”hÞ)”}”(hŒ=alias bond0 bonding options bond0 mode=balance-alb miimon=100”h]”hŒ=alias bond0 bonding options bond0 mode=balance-alb miimon=100”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M_hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M_hjûh²hubhÞ)”}”(hŒYReplace the sample parameters with the appropriate set of options for your configuration.”h]”hŒYReplace the sample parameters with the appropriate set of options for your configuration.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mbhjûh²hubhÞ)”}”(hŒ”Finally run "/etc/rc.d/init.d/network restart" as root. This will restart the networking subsystem and your bond link should be now up and running.”h]”hŒ˜Finally run â€œ/etc/rc.d/init.d/network restartâ€ as root. This will restart the networking subsystem and your bond link should be now up and running.”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mehjûh²hubeh}”(h]”Œ&configuration-with-initscripts-support”ah ]”h"]”Œ*3.2 configuration with initscripts support”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MubhÉ)”}”(hhh]”(hÎ)”}”(hŒ!3.2.1 Using DHCP with Initscripts”h]”hŒ!3.2.1 Using DHCP with Initscripts”…””}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj@h²hh³hÇh´MjubhÞ)”}”(hŒØRecent versions of initscripts (the versions supplied with Fedora Core 3 and Red Hat Enterprise Linux 4, or later versions, are reported to work) have support for assigning IP information to bonding devices via DHCP.”h]”hŒØRecent versions of initscripts (the versions supplied with Fedora Core 3 and Red Hat Enterprise Linux 4, or later versions, are reported to work) have support for assigning IP information to bonding devices via DHCP.”…””}”(hjQh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mlhj@h²hubhÞ)”}”(hŒØTo configure bonding for DHCP, configure it as described above, except replace the line "BOOTPROTO=none" with "BOOTPROTO=dhcp" and add a line consisting of "TYPE=Bonding". Note that the TYPE value is case sensitive.”h]”hŒäTo configure bonding for DHCP, configure it as described above, except replace the line â€œBOOTPROTO=noneâ€ with â€œBOOTPROTO=dhcpâ€ and add a line consisting of â€œTYPE=Bondingâ€. Note that the TYPE value is case sensitive.”…””}”(hj_h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mqhj@h²hubeh}”(h]”Œusing-dhcp-with-initscripts”ah ]”h"]”Œ!3.2.1 using dhcp with initscripts”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MjubhÉ)”}”(hhh]”(hÎ)”}”(hŒ13.2.2 Configuring Multiple Bonds with Initscripts”h]”hŒ13.2.2 Configuring Multiple Bonds with Initscripts”…””}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjuh²hh³hÇh´MwubhÞ)”}”(hXñInitscripts packages that are included with Fedora 7 and Red Hat Enterprise Linux 5 support multiple bonding interfaces by simply specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the number of the bond. This support requires sysfs support in the kernel, and a bonding driver of version 3.0.0 or later. Other configurations may not support this method for specifying multiple bonding interfaces; for those instances, see the "Configuring Multiple Bonds Manually" section, below.”h]”hXõInitscripts packages that are included with Fedora 7 and Red Hat Enterprise Linux 5 support multiple bonding interfaces by simply specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the number of the bond. This support requires sysfs support in the kernel, and a bonding driver of version 3.0.0 or later. Other configurations may not support this method for specifying multiple bonding interfaces; for those instances, see the â€œConfiguring Multiple Bonds Manuallyâ€ section, below.”…””}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Myhjuh²hubeh}”(h]”Œ+configuring-multiple-bonds-with-initscripts”ah ]”h"]”Œ13.2.2 configuring multiple bonds with initscripts”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MwubhÉ)”}”(hhh]”(hÎ)”}”(hŒ.3.3 Configuring Bonding Manually with iproute2”h]”hŒ.3.3 Configuring Bonding Manually with iproute2”…””}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjœh²hh³hÇh´MƒubhÞ)”}”(hŒÒThis section applies to distros whose network initialization scripts (the sysconfig or initscripts package) do not have specific knowledge of bonding. One such distro is SuSE Linux Enterprise Server version 8.”h]”hŒÒThis section applies to distros whose network initialization scripts (the sysconfig or initscripts package) do not have specific knowledge of bonding. One such distro is SuSE Linux Enterprise Server version 8.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M…hjœh²hubhÞ)”}”(hXwThe general method for these systems is to place the bonding module parameters into a config file in /etc/modprobe.d/ (as appropriate for the installed distro), then add modprobe and/or `ip link` commands to the system's global init script. The name of the global init script differs; for sysconfig, it is /etc/init.d/boot.local and for initscripts it is /etc/rc.d/rc.local.”h]”(hŒºThe general method for these systems is to place the bonding module parameters into a config file in /etc/modprobe.d/ (as appropriate for the installed distro), then add modprobe and/or ”…””}”(hj»h²hh³Nh´Nubjô )”}”(hŒ `ip link`”h]”hŒip link”…””}”(hjÃh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jó hj»ubhŒ¶ commands to the systemâ€™s global init script. The name of the global init script differs; for sysconfig, it is /etc/init.d/boot.local and for initscripts it is /etc/rc.d/rc.local.”…””•}”(hj»h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŠhjœh²hubhÞ)”}”(hŒêFor example, if you wanted to make a simple bond of two e100 devices (presumed to be eth0 and eth1), and have it persist across reboots, edit the appropriate file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the following::”h]”hŒéFor example, if you wanted to make a simple bond of two e100 devices (presumed to be eth0 and eth1), and have it persist across reboots, edit the appropriate file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the following:”…””}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‘hjœh²hubj~)”}”(hŒªmodprobe bonding mode=balance-alb miimon=100 modprobe e100 ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up ip link set eth0 master bond0 ip link set eth1 master bond0”h]”hŒªmodprobe bonding mode=balance-alb miimon=100 modprobe e100 ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up ip link set eth0 master bond0 ip link set eth1 master bond0”…””}”hjésbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M–hjœh²hubhÞ)”}”(hŒœReplace the example bonding module parameters and bond0 network configuration (IP address, netmask, etc) with the appropriate values for your configuration.”h]”hŒœReplace the example bonding module parameters and bond0 network configuration (IP address, netmask, etc) with the appropriate values for your configuration.”…””}”(hj÷h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mœhjœh²hubhÞ)”}”(hŒÈUnfortunately, this method will not provide support for the ifup and ifdown scripts on the bond devices. To reload the bonding configuration, it is necessary to run the initialization script, e.g.,::”h]”hŒÇUnfortunately, this method will not provide support for the ifup and ifdown scripts on the bond devices. To reload the bonding configuration, it is necessary to run the initialization script, e.g.,:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjœh²hubj~)”}”(hŒ# /etc/init.d/boot.local”h]”hŒ# /etc/init.d/boot.local”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M¤hjœh²hubhÞ)”}”(hŒor::”h]”hŒor:”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¦hjœh²hubj~)”}”(hŒ# /etc/rc.d/rc.local”h]”hŒ# /etc/rc.d/rc.local”…””}”hj/sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M¨hjœh²hubhÞ)”}”(hXIt may be desirable in such a case to create a separate script which only initializes the bonding configuration, then call that separate script from within boot.local. This allows for bonding to be enabled without re-running the entire global init script.”h]”hXIt may be desirable in such a case to create a separate script which only initializes the bonding configuration, then call that separate script from within boot.local. This allows for bonding to be enabled without re-running the entire global init script.”…””}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mªhjœh²hubhÞ)”}”(hŒÎTo shut down the bonding devices, it is necessary to first mark the bonding device itself as being down, then remove the appropriate device driver modules. For our example above, you can do the following::”h]”hŒÍTo shut down the bonding devices, it is necessary to first mark the bonding device itself as being down, then remove the appropriate device driver modules. For our example above, you can do the following:”…””}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¯hjœh²hubj~)”}”(hŒ2# ifconfig bond0 down # rmmod bonding # rmmod e100”h]”hŒ2# ifconfig bond0 down # rmmod bonding # rmmod e100”…””}”hjYsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M´hjœh²hubhÞ)”}”(hŒSAgain, for convenience, it may be desirable to create a script with these commands.”h]”hŒSAgain, for convenience, it may be desirable to create a script with these commands.”…””}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¸hjœh²hubeh}”(h]”Œ*configuring-bonding-manually-with-iproute2”ah ]”h"]”Œ.3.3 configuring bonding manually with iproute2”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MƒubhÉ)”}”(hhh]”(hÎ)”}”(hŒ)3.3.1 Configuring Multiple Bonds Manually”h]”hŒ)3.3.1 Configuring Multiple Bonds Manually”…””}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj}h²hh³hÇh´M½ubhÞ)”}”(hŒÄThis section contains information on configuring multiple bonding devices with differing options for those systems whose network initialization scripts lack support for configuring multiple bonds.”h]”hŒÄThis section contains information on configuring multiple bonding devices with differing options for those systems whose network initialization scripts lack support for configuring multiple bonds.”…””}”(hjŽh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¿hj}h²hubhÞ)”}”(hŒIf you require multiple bonding devices, but all with the same options, you may wish to use the "max_bonds" module parameter, documented above.”h]”hŒ“If you require multiple bonding devices, but all with the same options, you may wish to use the â€œmax_bondsâ€ module parameter, documented above.”…””}”(hjœh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÃhj}h²hubhÞ)”}”(hŒ™To create multiple bonding devices with differing options, it is preferable to use bonding parameters exported by sysfs, documented in the section below.”h]”hŒ™To create multiple bonding devices with differing options, it is preferable to use bonding parameters exported by sysfs, documented in the section below.”…””}”(hjªh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÇhj}h²hubhÞ)”}”(hXÅFor versions of bonding without sysfs support, the only means to provide multiple instances of bonding with differing options is to load the bonding driver multiple times. Note that current versions of the sysconfig network initialization scripts handle this automatically; if your distro uses these scripts, no special action is needed. See the section Configuring Bonding Devices, above, if you're not sure about your network initialization scripts.”h]”hXÇFor versions of bonding without sysfs support, the only means to provide multiple instances of bonding with differing options is to load the bonding driver multiple times. Note that current versions of the sysconfig network initialization scripts handle this automatically; if your distro uses these scripts, no special action is needed. See the section Configuring Bonding Devices, above, if youâ€™re not sure about your network initialization scripts.”…””}”(hj¸h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MËhj}h²hubhÞ)”}”(hXWTo load multiple instances of the module, it is necessary to specify a different name for each instance (the module loading system requires that every loaded module, even multiple instances of the same module, have a unique name). This is accomplished by supplying multiple sets of bonding options in ``/etc/modprobe.d/*.conf``, for example::”h]”(hX.To load multiple instances of the module, it is necessary to specify a different name for each instance (the module loading system requires that every loaded module, even multiple instances of the same module, have a unique name). This is accomplished by supplying multiple sets of bonding options in ”…””}”(hjÆh²hh³Nh´Nubjð)”}”(hŒ``/etc/modprobe.d/*.conf``”h]”hŒ/etc/modprobe.d/*.conf”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhjÆubhŒ, for example:”…””}”(hjÆh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÓhj}h²hubj~)”}”(hŒŒalias bond0 bonding options bond0 -o bond0 mode=balance-rr miimon=100 alias bond1 bonding options bond1 -o bond1 mode=balance-alb miimon=50”h]”hŒŒalias bond0 bonding options bond0 -o bond0 mode=balance-rr miimon=100 alias bond1 bonding options bond1 -o bond1 mode=balance-alb miimon=50”…””}”hjæsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MÙhj}h²hubhÞ)”}”(hXwill load the bonding module two times. The first instance is named "bond0" and creates the bond0 device in balance-rr mode with an miimon of 100. The second instance is named "bond1" and creates the bond1 device in balance-alb mode with an miimon of 50.”h]”hXwill load the bonding module two times. The first instance is named â€œbond0â€ and creates the bond0 device in balance-rr mode with an miimon of 100. The second instance is named â€œbond1â€ and creates the bond1 device in balance-alb mode with an miimon of 50.”…””}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mßhj}h²hubhÞ)”}”(hŒÓIn some circumstances (typically with older distributions), the above does not work, and the second bonding instance never sees its options. In that case, the second options line can be substituted as follows::”h]”hŒÒIn some circumstances (typically with older distributions), the above does not work, and the second bonding instance never sees its options. In that case, the second options line can be substituted as follows:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mähj}h²hubj~)”}”(hŒxinstall bond1 /sbin/modprobe --ignore-install bonding -o bond1 \ mode=balance-alb miimon=50”h]”hŒxinstall bond1 /sbin/modprobe --ignore-install bonding -o bond1 \ mode=balance-alb miimon=50”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Méhj}h²hubhÞ)”}”(hŒzThis may be repeated any number of times, specifying a new and unique name in place of bond1 for each subsequent instance.”h]”hŒzThis may be repeated any number of times, specifying a new and unique name in place of bond1 for each subsequent instance.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mìhj}h²hubhÞ)”}”(hX×It has been observed that some Red Hat supplied kernels are unable to rename modules at load time (the "-o bond1" part). Attempts to pass that option to modprobe will produce an "Operation not permitted" error. This has been reported on some Fedora Core kernels, and has been seen on RHEL 4 as well. On kernels exhibiting this problem, it will be impossible to configure multiple bonds with differing parameters (as they are older kernels, and also lack sysfs support).”h]”hXßIt has been observed that some Red Hat supplied kernels are unable to rename modules at load time (the â€œ-o bond1â€ part). Attempts to pass that option to modprobe will produce an â€œOperation not permittedâ€ error. This has been reported on some Fedora Core kernels, and has been seen on RHEL 4 as well. On kernels exhibiting this problem, it will be impossible to configure multiple bonds with differing parameters (as they are older kernels, and also lack sysfs support).”…””}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mïhj}h²hubeh}”(h]”Œ#configuring-multiple-bonds-manually”ah ]”h"]”Œ)3.3.1 configuring multiple bonds manually”ah$]”h&]”uh1hÈhj&h²hh³hÇh´M½ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ*3.4 Configuring Bonding Manually via Sysfs”h]”hŒ*3.4 Configuring Bonding Manually via Sysfs”…””}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjBh²hh³hÇh´MøubhÞ)”}”(hX7Starting with version 3.0.0, Channel Bonding may be configured via the sysfs interface. This interface allows dynamic configuration of all bonds in the system without unloading the module. It also allows for adding and removing bonds at runtime. Ifenslave is no longer required, though it is still supported.”h]”hX7Starting with version 3.0.0, Channel Bonding may be configured via the sysfs interface. This interface allows dynamic configuration of all bonds in the system without unloading the module. It also allows for adding and removing bonds at runtime. Ifenslave is no longer required, though it is still supported.”…””}”(hjSh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MúhjBh²hubhÞ)”}”(hŒéUse of the sysfs interface allows you to use multiple bonds with different configurations without having to reload the module. It also allows you to use multiple, differently configured bonds when bonding is compiled into the kernel.”h]”hŒéUse of the sysfs interface allows you to use multiple bonds with different configurations without having to reload the module. It also allows you to use multiple, differently configured bonds when bonding is compiled into the kernel.”…””}”(hjah²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjBh²hubhÞ)”}”(hXYou must have the sysfs filesystem mounted to configure bonding this way. The examples in this document assume that you are using the standard mount point for sysfs, e.g. /sys. If your sysfs filesystem is mounted elsewhere, you will need to adjust the example paths accordingly.”h]”hXYou must have the sysfs filesystem mounted to configure bonding this way. The examples in this document assume that you are using the standard mount point for sysfs, e.g. /sys. If your sysfs filesystem is mounted elsewhere, you will need to adjust the example paths accordingly.”…””}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjBh²hubeh}”(h]”Œ&configuring-bonding-manually-via-sysfs”ah ]”h"]”Œ*3.4 configuring bonding manually via sysfs”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MøubhÉ)”}”(hhh]”(hÎ)”}”(hŒCreating and Destroying Bonds”h]”hŒCreating and Destroying Bonds”…””}”(hjˆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj…h²hh³hÇh´MubhÞ)”}”(hŒTo add a new bond foo::”h]”hŒTo add a new bond foo:”…””}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj…h²hubj~)”}”(hŒ,# echo +foo > /sys/class/net/bonding_masters”h]”hŒ,# echo +foo > /sys/class/net/bonding_masters”…””}”hj¤sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mhj…h²hubhÞ)”}”(hŒ To remove an existing bond bar::”h]”hŒTo remove an existing bond bar:”…””}”(hj²h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj…h²hubj~)”}”(hŒ,# echo -bar > /sys/class/net/bonding_masters”h]”hŒ,# echo -bar > /sys/class/net/bonding_masters”…””}”hjÀsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mhj…h²hubhÞ)”}”(hŒTo show all existing bonds::”h]”hŒTo show all existing bonds:”…””}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj…h²hubj~)”}”(hŒ$# cat /sys/class/net/bonding_masters”h]”hŒ$# cat /sys/class/net/bonding_masters”…””}”hjÜsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mhj…h²hubhŒnote”“”)”}”(hŒdue to 4K size limitation of sysfs files, this list may be truncated if you have more than a few hundred bonds. This is unlikely to occur under normal operating conditions.”h]”hÞ)”}”(hŒdue to 4K size limitation of sysfs files, this list may be truncated if you have more than a few hundred bonds. This is unlikely to occur under normal operating conditions.”h]”hŒdue to 4K size limitation of sysfs files, this list may be truncated if you have more than a few hundred bonds. This is unlikely to occur under normal operating conditions.”…””}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjìubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj…h²hh³hÇh´Nubeh}”(h]”Œcreating-and-destroying-bonds”ah ]”h"]”Œcreating and destroying bonds”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MubhÉ)”}”(hhh]”(hÎ)”}”(hŒAdding and Removing Slaves”h]”hŒAdding and Removing Slaves”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh²hh³hÇh´M ubhÞ)”}”(hŒ¤Interfaces may be enslaved to a bond using the file /sys/class/net//bonding/slaves. The semantics for this file are the same as for the bonding_masters file.”h]”hŒ¤Interfaces may be enslaved to a bond using the file /sys/class/net//bonding/slaves. The semantics for this file are the same as for the bonding_masters file.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M!hjh²hubhÞ)”}”(hŒ)To enslave interface eth0 to bond bond0::”h]”hŒ(To enslave interface eth0 to bond bond0:”…””}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M%hjh²hubj~)”}”(hŒF# ifconfig bond0 up # echo +eth0 > /sys/class/net/bond0/bonding/slaves”h]”hŒF# ifconfig bond0 up # echo +eth0 > /sys/class/net/bond0/bonding/slaves”…””}”hj9sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M'hjh²hubhÞ)”}”(hŒ$To free slave eth0 from bond bond0::”h]”hŒ#To free slave eth0 from bond bond0:”…””}”(hjGh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M*hjh²hubj~)”}”(hŒ2# echo -eth0 > /sys/class/net/bond0/bonding/slaves”h]”hŒ2# echo -eth0 > /sys/class/net/bond0/bonding/slaves”…””}”hjUsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M,hjh²hubhÞ)”}”(hXWhen an interface is enslaved to a bond, symlinks between the two are created in the sysfs filesystem. In this case, you would get /sys/class/net/bond0/slave_eth0 pointing to /sys/class/net/eth0, and /sys/class/net/eth0/master pointing to /sys/class/net/bond0.”h]”hXWhen an interface is enslaved to a bond, symlinks between the two are created in the sysfs filesystem. In this case, you would get /sys/class/net/bond0/slave_eth0 pointing to /sys/class/net/eth0, and /sys/class/net/eth0/master pointing to /sys/class/net/bond0.”…””}”(hjch²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M.hjh²hubhÞ)”}”(hXThis means that you can tell quickly whether or not an interface is enslaved by looking for the master symlink. Thus: # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves will free eth0 from whatever bond it is enslaved to, regardless of the name of the bond interface.”h]”hXThis means that you can tell quickly whether or not an interface is enslaved by looking for the master symlink. Thus: # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves will free eth0 from whatever bond it is enslaved to, regardless of the name of the bond interface.”…””}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M3hjh²hubeh}”(h]”Œadding-and-removing-slaves”ah ]”h"]”Œadding and removing slaves”ah$]”h&]”uh1hÈhj&h²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒChanging a Bond's Configuration”h]”hŒ!Changing a Bondâ€™s Configuration”…””}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj‡h²hh³hÇh´M:ubhÞ)”}”(hŒpEach bond may be configured individually by manipulating the files located in /sys/class/net//bonding”h]”hŒpEach bond may be configured individually by manipulating the files located in /sys/class/net//bonding”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M;hj‡h²hubhÞ)”}”(hŒõThe names of these files correspond directly with the command- line parameters described elsewhere in this file, and, with the exception of arp_ip_target, they accept the same values. To see the current setting, simply cat the appropriate file.”h]”hŒõThe names of these files correspond directly with the command- line parameters described elsewhere in this file, and, with the exception of arp_ip_target, they accept the same values. To see the current setting, simply cat the appropriate file.”…””}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M>hj‡h²hubhÞ)”}”(hŒ‚A few examples will be given here; for specific usage guidelines for each parameter, see the appropriate section in this document.”h]”hŒ‚A few examples will be given here; for specific usage guidelines for each parameter, see the appropriate section in this document.”…””}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MChj‡h²hubhÞ)”}”(hŒ)To configure bond0 for balance-alb mode::”h]”hŒ(To configure bond0 for balance-alb mode:”…””}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MGhj‡h²hubj~)”}”(hŒ€# ifconfig bond0 down # echo 6 > /sys/class/net/bond0/bonding/mode - or - # echo balance-alb > /sys/class/net/bond0/bonding/mode”h]”hŒ€# ifconfig bond0 down # echo 6 > /sys/class/net/bond0/bonding/mode - or - # echo balance-alb > /sys/class/net/bond0/bonding/mode”…””}”hjÐsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MIhj‡h²hubjë)”}”(hŒ?The bond interface must be down before the mode can be changed.”h]”hÞ)”}”(hjàh]”hŒ?The bond interface must be down before the mode can be changed.”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MPhjÞubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj‡h²hh³hÇh´NubhÞ)”}”(hŒ /sys/class/net/bond0/bonding/miimon”h]”hŒ1# echo 1000 > /sys/class/net/bond0/bonding/miimon”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MThj‡h²hubjë)”}”(hŒ^If ARP monitoring is enabled, it will disabled when MII monitoring is enabled, and vice-versa.”h]”hÞ)”}”(hŒ^If ARP monitoring is enabled, it will disabled when MII monitoring is enabled, and vice-versa.”h]”hŒ^If ARP monitoring is enabled, it will disabled when MII monitoring is enabled, and vice-versa.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MXhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj‡h²hh³hÇh´NubhÞ)”}”(hŒTo add ARP targets::”h]”hŒTo add ARP targets:”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M[hj‡h²hubj~)”}”(hŒ…# echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target”h]”hŒ…# echo +192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target # echo +192.168.0.101 > /sys/class/net/bond0/bonding/arp_ip_target”…””}”hj7sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M]hj‡h²hubjë)”}”(hŒ+up to 16 target addresses may be specified.”h]”hÞ)”}”(hjGh]”hŒ+up to 16 target addresses may be specified.”…””}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MbhjEubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj‡h²hh³hÇh´NubhÞ)”}”(hŒTo remove an ARP target::”h]”hŒTo remove an ARP target:”…””}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mdhj‡h²hubj~)”}”(hŒB# echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target”h]”hŒB# echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target”…””}”hjjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mfhj‡h²hubhÞ)”}”(hŒ=To configure the interval between learning packet transmits::”h]”hŒ /sys/class/net/bond0/bonding/lp_interval”h]”hŒ4# echo 12 > /sys/class/net/bond0/bonding/lp_interval”…””}”hj†sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mjhj‡h²hubjë)”}”(hŒ©the lp_interval is the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch. The default interval is 1 second.”h]”hÞ)”}”(hŒ©the lp_interval is the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch. The default interval is 1 second.”h]”hŒ©the lp_interval is the number of seconds between instances where the bonding driver sends learning packets to each slaves peer switch. The default interval is 1 second.”…””}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mnhj”ubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj‡h²hh³hÇh´Nubeh}”(h]”Œchanging-a-bond-s-configuration”ah ]”h"]”Œchanging a bond's configuration”ah$]”h&]”uh1hÈhj&h²hh³hÇh´M:ubhÉ)”}”(hhh]”(hÎ)”}”(hŒExample Configuration”h]”hŒExample Configuration”…””}”(hj·h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj´h²hh³hÇh´MsubhÞ)”}”(hŒnWe begin with the same example that is shown in section 3.3, executed with sysfs, and without using ifenslave.”h]”hŒnWe begin with the same example that is shown in section 3.3, executed with sysfs, and without using ifenslave.”…””}”(hjÅh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mthj´h²hubhÞ)”}”(hŒÏTo make a simple bond of two e100 devices (presumed to be eth0 and eth1), and have it persist across reboots, edit the appropriate file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the following::”h]”hŒÎTo make a simple bond of two e100 devices (presumed to be eth0 and eth1), and have it persist across reboots, edit the appropriate file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the following:”…””}”(hjÓh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mwhj´h²hubj~)”}”(hXmodprobe bonding modprobe e100 echo balance-alb > /sys/class/net/bond0/bonding/mode ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up echo 100 > /sys/class/net/bond0/bonding/miimon echo +eth0 > /sys/class/net/bond0/bonding/slaves echo +eth1 > /sys/class/net/bond0/bonding/slaves”h]”hXmodprobe bonding modprobe e100 echo balance-alb > /sys/class/net/bond0/bonding/mode ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up echo 100 > /sys/class/net/bond0/bonding/miimon echo +eth0 > /sys/class/net/bond0/bonding/slaves echo +eth1 > /sys/class/net/bond0/bonding/slaves”…””}”hjásbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M|hj´h²hubhÞ)”}”(hŒŠTo add a second bond, with two e1000 interfaces in active-backup mode, using ARP monitoring, add the following lines to your init script::”h]”hŒ‰To add a second bond, with two e1000 interfaces in active-backup mode, using ARP monitoring, add the following lines to your init script:”…””}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M„hj´h²hubj~)”}”(hX}modprobe e1000 echo +bond1 > /sys/class/net/bonding_masters echo active-backup > /sys/class/net/bond1/bonding/mode ifconfig bond1 192.168.2.1 netmask 255.255.255.0 up echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target echo 2000 > /sys/class/net/bond1/bonding/arp_interval echo +eth2 > /sys/class/net/bond1/bonding/slaves echo +eth3 > /sys/class/net/bond1/bonding/slaves”h]”hX}modprobe e1000 echo +bond1 > /sys/class/net/bonding_masters echo active-backup > /sys/class/net/bond1/bonding/mode ifconfig bond1 192.168.2.1 netmask 255.255.255.0 up echo +192.168.2.100 /sys/class/net/bond1/bonding/arp_ip_target echo 2000 > /sys/class/net/bond1/bonding/arp_interval echo +eth2 > /sys/class/net/bond1/bonding/slaves echo +eth3 > /sys/class/net/bond1/bonding/slaves”…””}”hjýsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mˆhj´h²hubeh}”(h]”Œexample-configuration”ah ]”h"]”Œexample configuration”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MsubhÉ)”}”(hhh]”(hÎ)”}”(hŒ)3.5 Configuration with Interfaces Support”h]”hŒ)3.5 Configuration with Interfaces Support”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj h²hh³hÇh´M’ubhÞ)”}”(hŒœThis section applies to distros which use /etc/network/interfaces file to describe network interface configuration, most notably Debian and its derivatives.”h]”hŒœThis section applies to distros which use /etc/network/interfaces file to describe network interface configuration, most notably Debian and its derivatives.”…””}”(hj$ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M”hj h²hubhÞ)”}”(hŒýThe ifup and ifdown commands on Debian don't support bonding out of the box. The ifenslave-2.6 package should be installed to provide bonding support. Once installed, this package will provide ``bond-*`` options to be used into /etc/network/interfaces.”h]”(hŒÄThe ifup and ifdown commands on Debian donâ€™t support bonding out of the box. The ifenslave-2.6 package should be installed to provide bonding support. Once installed, this package will provide ”…””}”(hj2 h²hh³Nh´Nubjð)”}”(hŒ ``bond-*``”h]”hŒbond-*”…””}”(hj: h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhj2 ubhŒ1 options to be used into /etc/network/interfaces.”…””}”(hj2 h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M˜hj h²hubhÞ)”}”(hŒlNote that ifenslave-2.6 package will load the bonding module and use the ifenslave command when appropriate.”h]”hŒlNote that ifenslave-2.6 package will load the bonding module and use the ifenslave command when appropriate.”…””}”(hjR h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj h²hubeh}”(h]”Œ%configuration-with-interfaces-support”ah ]”h"]”Œ)3.5 configuration with interfaces support”ah$]”h&]”uh1hÈhj&h²hh³hÇh´M’ubhÉ)”}”(hhh]”(hÎ)”}”(hŒExample Configurations”h]”hŒExample Configurations”…””}”(hjk h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjh h²hh³hÇh´M¡ubhÞ)”}”(hŒ|In /etc/network/interfaces, the following stanza will configure bond0, in active-backup mode, with eth0 and eth1 as slaves::”h]”hŒ{In /etc/network/interfaces, the following stanza will configure bond0, in active-backup mode, with eth0 and eth1 as slaves:”…””}”(hjy h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M£hjh h²hubj~)”}”(hŒ•auto bond0 iface bond0 inet dhcp bond-slaves eth0 eth1 bond-mode active-backup bond-miimon 100 bond-primary eth0 eth1”h]”hŒ•auto bond0 iface bond0 inet dhcp bond-slaves eth0 eth1 bond-mode active-backup bond-miimon 100 bond-primary eth0 eth1”…””}”hj‡ sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M¦hjh h²hubhÞ)”}”(hŒøIf the above configuration doesn't work, you might have a system using upstart for system startup. This is most notably true for recent Ubuntu versions. The following stanza in /etc/network/interfaces will produce the same result on those systems::”h]”hŒùIf the above configuration doesnâ€™t work, you might have a system using upstart for system startup. This is most notably true for recent Ubuntu versions. The following stanza in /etc/network/interfaces will produce the same result on those systems:”…””}”(hj• h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjh h²hubj~)”}”(hX'auto bond0 iface bond0 inet dhcp bond-slaves none bond-mode active-backup bond-miimon 100 auto eth0 iface eth0 inet manual bond-master bond0 bond-primary eth0 eth1 auto eth1 iface eth1 inet manual bond-master bond0 bond-primary eth0 eth1”h]”hX'auto bond0 iface bond0 inet dhcp bond-slaves none bond-mode active-backup bond-miimon 100 auto eth0 iface eth0 inet manual bond-master bond0 bond-primary eth0 eth1 auto eth1 iface eth1 inet manual bond-master bond0 bond-primary eth0 eth1”…””}”hj£ sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M²hjh h²hubhÞ)”}”(hŒ½For a full list of ``bond-*`` supported options in /etc/network/interfaces and some more advanced examples tailored to you particular distros, see the files in /usr/share/doc/ifenslave-2.6.”h]”(hŒFor a full list of ”…””}”(hj± h²hh³Nh´Nubjð)”}”(hŒ ``bond-*``”h]”hŒbond-*”…””}”(hj¹ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jïhj± ubhŒ supported options in /etc/network/interfaces and some more advanced examples tailored to you particular distros, see the files in /usr/share/doc/ifenslave-2.6.”…””}”(hj± h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÂhjh h²hubeh}”(h]”Œexample-configurations”ah ]”h"]”Œexample configurations”ah$]”h&]”uh1hÈhj&h²hh³hÇh´M¡ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ.3.6 Overriding Configuration for Special Cases”h]”hŒ.3.6 Overriding Configuration for Special Cases”…””}”(hjÜ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÙ h²hh³hÇh´MÇubhÞ)”}”(hX=When using the bonding driver, the physical port which transmits a frame is typically selected by the bonding driver, and is not relevant to the user or system administrator. The output port is simply selected using the policies of the selected bonding mode. On occasion however, it is helpful to direct certain classes of traffic to certain physical interfaces on output to implement slightly more complex policies. For example, to reach a web server over a bonded interface in which eth0 connects to a private network, while eth1 connects via a public network, it may be desirous to bias the bond to send said traffic over eth0 first, using eth1 only as a fall back, while all other traffic can safely be sent over either interface. Such configurations may be achieved using the traffic control utilities inherent in linux.”h]”hX=When using the bonding driver, the physical port which transmits a frame is typically selected by the bonding driver, and is not relevant to the user or system administrator. The output port is simply selected using the policies of the selected bonding mode. On occasion however, it is helpful to direct certain classes of traffic to certain physical interfaces on output to implement slightly more complex policies. For example, to reach a web server over a bonded interface in which eth0 connects to a private network, while eth1 connects via a public network, it may be desirous to bias the bond to send said traffic over eth0 first, using eth1 only as a fall back, while all other traffic can safely be sent over either interface. Such configurations may be achieved using the traffic control utilities inherent in linux.”…””}”(hjê h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÉhjÙ h²hubhÞ)”}”(hX]By default the bonding driver is multiqueue aware and 16 queues are created when the driver initializes (see Documentation/networking/multiqueue.rst for details). If more or less queues are desired the module parameter tx_queues can be used to change this value. There is no sysfs parameter available as the allocation is done at module init time.”h]”hX]By default the bonding driver is multiqueue aware and 16 queues are created when the driver initializes (see Documentation/networking/multiqueue.rst for details). If more or less queues are desired the module parameter tx_queues can be used to change this value. There is no sysfs parameter available as the allocation is done at module init time.”…””}”(hjø h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÕhjÙ h²hubhÞ)”}”(hŒqThe output of the file /proc/net/bonding/bondX has changed so the output Queue ID is now printed for each slave::”h]”hŒpThe output of the file /proc/net/bonding/bondX has changed so the output Queue ID is now printed for each slave:”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÛhjÙ h²hubj~)”}”(hX”Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1a:a0:12:8f:cb Slave queue ID: 0 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1a:a0:12:8f:cc Slave queue ID: 2”h]”hX”Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth0 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1a:a0:12:8f:cb Slave queue ID: 0 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:1a:a0:12:8f:cc Slave queue ID: 2”…””}”hj!sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MÞhjÙ h²hubhÞ)”}”(hŒ7The queue_id for a slave can be set using the command::”h]”hŒ6The queue_id for a slave can be set using the command:”…””}”(hj"!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MòhjÙ h²hubj~)”}”(hŒ7# echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id”h]”hŒ7# echo "eth1:2" > /sys/class/net/bond0/bonding/queue_id”…””}”hj0!sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MôhjÙ h²hubhÞ)”}”(hX'Any interface that needs a queue_id set should set it with multiple calls like the one above until proper priorities are set for all interfaces. On distributions that allow configuration via initscripts, multiple 'queue_id' arguments can be added to BONDING_OPTS to set all needed slave queues.”h]”hX+Any interface that needs a queue_id set should set it with multiple calls like the one above until proper priorities are set for all interfaces. On distributions that allow configuration via initscripts, multiple â€˜queue_idâ€™ arguments can be added to BONDING_OPTS to set all needed slave queues.”…””}”(hj>!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MöhjÙ h²hubhÞ)”}”(hXkThese queue id's can be used in conjunction with the tc utility to configure a multiqueue qdisc and filters to bias certain traffic to transmit on certain slave devices. For instance, say we wanted, in the above configuration to force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output device. The following commands would accomplish this::”h]”hXlThese queue idâ€™s can be used in conjunction with the tc utility to configure a multiqueue qdisc and filters to bias certain traffic to transmit on certain slave devices. For instance, say we wanted, in the above configuration to force all traffic bound to 192.168.1.100 to use eth1 in the bond as its output device. The following commands would accomplish this:”…””}”(hjL!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MûhjÙ h²hubj~)”}”(hŒ# tc qdisc add dev bond0 handle 1 root multiq # tc filter add dev bond0 protocol ip parent 1: prio 1 u32 match ip \ dst 192.168.1.100 action skbedit queue_mapping 2”h]”hŒ# tc qdisc add dev bond0 handle 1 root multiq # tc filter add dev bond0 protocol ip parent 1: prio 1 u32 match ip \ dst 192.168.1.100 action skbedit queue_mapping 2”…””}”hjZ!sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MhjÙ h²hubhÞ)”}”(hXƒThese commands tell the kernel to attach a multiqueue queue discipline to the bond0 interface and filter traffic enqueued to it, such that packets with a dst ip of 192.168.1.100 have their output queue mapping value overwritten to 2. This value is then passed into the driver, causing the normal output path selection policy to be overridden, selecting instead qid 2, which maps to eth1.”h]”hXƒThese commands tell the kernel to attach a multiqueue queue discipline to the bond0 interface and filter traffic enqueued to it, such that packets with a dst ip of 192.168.1.100 have their output queue mapping value overwritten to 2. This value is then passed into the driver, causing the normal output path selection policy to be overridden, selecting instead qid 2, which maps to eth1.”…””}”(hjh!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÙ h²hubhÞ)”}”(hXçNote that qid values begin at 1. Qid 0 is reserved to initiate to the driver that normal output policy selection should take place. One benefit to simply leaving the qid for a slave to 0 is the multiqueue awareness in the bonding driver that is now present. This awareness allows tc filters to be placed on slave devices as well as bond devices and the bonding driver will simply act as a pass-through for selecting output queues on the slave device rather than output port selection.”h]”hXçNote that qid values begin at 1. Qid 0 is reserved to initiate to the driver that normal output policy selection should take place. One benefit to simply leaving the qid for a slave to 0 is the multiqueue awareness in the bonding driver that is now present. This awareness allows tc filters to be placed on slave devices as well as bond devices and the bonding driver will simply act as a pass-through for selecting output queues on the slave device rather than output port selection.”…””}”(hjv!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÙ h²hubhÞ)”}”(hŒ–This feature first appeared in bonding driver version 3.7.0 and support for output slave selection was limited to round-robin and active-backup modes.”h]”hŒ–This feature first appeared in bonding driver version 3.7.0 and support for output slave selection was limited to round-robin and active-backup modes.”…””}”(hj„!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjÙ h²hubeh}”(h]”Œ*overriding-configuration-for-special-cases”ah ]”h"]”Œ.3.6 overriding configuration for special cases”ah$]”h&]”uh1hÈhj&h²hh³hÇh´MÇubhÉ)”}”(hhh]”(hÎ)”}”(hŒ:3.7 Configuring LACP for 802.3ad mode in a more secure way”h]”hŒ:3.7 Configuring LACP for 802.3ad mode in a more secure way”…””}”(hj!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjš!h²hh³hÇh´MubhÞ)”}”(hX~When using 802.3ad bonding mode, the Actor (host) and Partner (switch) exchange LACPDUs. These LACPDUs cannot be sniffed, because they are destined to link local mac addresses (which switches/bridges are not supposed to forward). However, most of the values are easily predictable or are simply the machine's MAC address (which is trivially known to all other hosts in the same L2). This implies that other machines in the L2 domain can spoof LACPDU packets from other hosts to the switch and potentially cause mayhem by joining (from the point of view of the switch) another machine's aggregate, thus receiving a portion of that hosts incoming traffic and / or spoofing traffic from that machine themselves (potentially even successfully terminating some portion of flows). Though this is not a likely scenario, one could avoid this possibility by simply configuring few bonding parameters:”h]”hX‚When using 802.3ad bonding mode, the Actor (host) and Partner (switch) exchange LACPDUs. These LACPDUs cannot be sniffed, because they are destined to link local mac addresses (which switches/bridges are not supposed to forward). However, most of the values are easily predictable or are simply the machineâ€™s MAC address (which is trivially known to all other hosts in the same L2). This implies that other machines in the L2 domain can spoof LACPDU packets from other hosts to the switch and potentially cause mayhem by joining (from the point of view of the switch) another machineâ€™s aggregate, thus receiving a portion of that hosts incoming traffic and / or spoofing traffic from that machine themselves (potentially even successfully terminating some portion of flows). Though this is not a likely scenario, one could avoid this possibility by simply configuring few bonding parameters:”…””}”(hj«!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhjš!h²hubj )”}”(hXÇ(a) ad_actor_system : You can set a random mac-address that can be used for these LACPDU exchanges. The value can not be either NULL or Multicast. Also it's preferable to set the local-admin bit. Following shell code generates a random mac-address as described above:: # sys_mac_addr=$(printf '%02x:%02x:%02x:%02x:%02x:%02x' \ $(( (RANDOM & 0xFE) | 0x02 )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF ))) # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system (b) ad_actor_sys_prio : Randomize the system priority. The default value is 65535, but system can take the value from 1 - 65535. Following shell code generates random priority and sets it:: # sys_prio=$(( 1 + RANDOM + RANDOM )) # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio (c) ad_user_port_key : Use the user portion of the port-key. The default keeps this empty. These are the upper 10 bits of the port-key and value ranges from 0 - 1023. Following shell code generates these 10 bits and sets it:: # usr_port_key=$(( RANDOM & 0x3FF )) # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key ”h]”hŒenumerated_list”“”)”}”(hhh]”(j)”}”(hXèad_actor_system : You can set a random mac-address that can be used for these LACPDU exchanges. The value can not be either NULL or Multicast. Also it's preferable to set the local-admin bit. Following shell code generates a random mac-address as described above:: # sys_mac_addr=$(printf '%02x:%02x:%02x:%02x:%02x:%02x' \ $(( (RANDOM & 0xFE) | 0x02 )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF ))) # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system ”h]”(hÞ)”}”(hXad_actor_system : You can set a random mac-address that can be used for these LACPDU exchanges. The value can not be either NULL or Multicast. Also it's preferable to set the local-admin bit. Following shell code generates a random mac-address as described above::”h]”hX ad_actor_system : You can set a random mac-address that can be used for these LACPDU exchanges. The value can not be either NULL or Multicast. Also itâ€™s preferable to set the local-admin bit. Following shell code generates a random mac-address as described above:”…””}”(hjÆ!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M(hjÂ!ubj~)”}”(hX¥# sys_mac_addr=$(printf '%02x:%02x:%02x:%02x:%02x:%02x' \ $(( (RANDOM & 0xFE) | 0x02 )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF ))) # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system”h]”hX¥# sys_mac_addr=$(printf '%02x:%02x:%02x:%02x:%02x:%02x' \ $(( (RANDOM & 0xFE) | 0x02 )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF )) \ $(( RANDOM & 0xFF ))) # echo $sys_mac_addr > /sys/class/net/bond0/bonding/ad_actor_system”…””}”hjÔ!sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M-hjÂ!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj¿!ubj)”}”(hX-ad_actor_sys_prio : Randomize the system priority. The default value is 65535, but system can take the value from 1 - 65535. Following shell code generates random priority and sets it:: # sys_prio=$(( 1 + RANDOM + RANDOM )) # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio ”h]”(hÞ)”}”(hŒ¹ad_actor_sys_prio : Randomize the system priority. The default value is 65535, but system can take the value from 1 - 65535. Following shell code generates random priority and sets it::”h]”hŒ¸ad_actor_sys_prio : Randomize the system priority. The default value is 65535, but system can take the value from 1 - 65535. Following shell code generates random priority and sets it:”…””}”(hjì!h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6hjè!ubj~)”}”(hŒg# sys_prio=$(( 1 + RANDOM + RANDOM )) # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio”h]”hŒg# sys_prio=$(( 1 + RANDOM + RANDOM )) # echo $sys_prio > /sys/class/net/bond0/bonding/ad_actor_sys_prio”…””}”hjú!sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M:hjè!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj¿!ubj)”}”(hXTad_user_port_key : Use the user portion of the port-key. The default keeps this empty. These are the upper 10 bits of the port-key and value ranges from 0 - 1023. Following shell code generates these 10 bits and sets it:: # usr_port_key=$(( RANDOM & 0x3FF )) # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key ”h]”(hÞ)”}”(hŒÝad_user_port_key : Use the user portion of the port-key. The default keeps this empty. These are the upper 10 bits of the port-key and value ranges from 0 - 1023. Following shell code generates these 10 bits and sets it::”h]”hŒÜad_user_port_key : Use the user portion of the port-key. The default keeps this empty. These are the upper 10 bits of the port-key and value ranges from 0 - 1023. Following shell code generates these 10 bits and sets it:”…””}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M=hj"ubj~)”}”(hŒi# usr_port_key=$(( RANDOM & 0x3FF )) # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key”h]”hŒi# usr_port_key=$(( RANDOM & 0x3FF )) # echo $usr_port_key > /sys/class/net/bond0/bonding/ad_user_port_key”…””}”hj "sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MBhj"ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj¿!ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ loweralpha”Œprefix”Œ(”Œsuffix”Œ)”uh1j½!hj¹!ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M(hjš!h²hubeh}”(h]”Œ6configuring-lacp-for-802-3ad-mode-in-a-more-secure-way”ah ]”h"]”Œ:3.7 configuring lacp for 802.3ad mode in a more secure way”ah$]”h&]”uh1hÈhj&h²hh³hÇh´Mubeh}”(h]”Œconfiguring-bonding-devices”ah ]”h"]”Œ3. configuring bonding devices”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´MFubhÉ)”}”(hhh]”(hÎ)”}”(hŒ 4 Querying Bonding Configuration”h]”hŒ 4 Querying Bonding Configuration”…””}”(hjY"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjV"h²hh³hÇh´MGubhÉ)”}”(hhh]”(hÎ)”}”(hŒ4.1 Bonding Configuration”h]”hŒ4.1 Bonding Configuration”…””}”(hjj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjg"h²hh³hÇh´MJubhÞ)”}”(hŒ¾Each bonding device has a read-only file residing in the /proc/net/bonding directory. The file contents include information about the bonding configuration, options and state of each slave.”h]”hŒ¾Each bonding device has a read-only file residing in the /proc/net/bonding directory. The file contents include information about the bonding configuration, options and state of each slave.”…””}”(hjx"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MLhjg"h²hubhÞ)”}”(hŒ“For example, the contents of /proc/net/bonding/bond0 after the driver is loaded with parameters of mode=0 and miimon=1000 is generally as follows::”h]”hŒ’For example, the contents of /proc/net/bonding/bond0 after the driver is loaded with parameters of mode=0 and miimon=1000 is generally as follows:”…””}”(hj†"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MPhjg"h²hubj~)”}”(hXLEthernet Channel Bonding Driver: 2.6.1 (October 29, 2004) Bonding Mode: load balancing (round-robin) Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 1000 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth1 MII Status: up Link Failure Count: 1 Slave Interface: eth0 MII Status: up Link Failure Count: 1”h]”hXLEthernet Channel Bonding Driver: 2.6.1 (October 29, 2004) Bonding Mode: load balancing (round-robin) Currently Active Slave: eth0 MII Status: up MII Polling Interval (ms): 1000 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth1 MII Status: up Link Failure Count: 1 Slave Interface: eth0 MII Status: up Link Failure Count: 1”…””}”hj”"sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MThjg"h²hubhÞ)”}”(hŒThe precise format and contents will change depending upon the bonding configuration, state, and version of the bonding driver.”h]”hŒThe precise format and contents will change depending upon the bonding configuration, state, and version of the bonding driver.”…””}”(hj¢"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mdhjg"h²hubeh}”(h]”Œbonding-configuration”ah ]”h"]”Œ4.1 bonding configuration”ah$]”h&]”uh1hÈhjV"h²hh³hÇh´MJubhÉ)”}”(hhh]”(hÎ)”}”(hŒ4.2 Network configuration”h]”hŒ4.2 Network configuration”…””}”(hj»"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj¸"h²hh³hÇh´MhubhÞ)”}”(hXThe network configuration can be inspected using the ifconfig command. Bonding devices will have the MASTER flag set; Bonding slave devices will have the SLAVE flag set. The ifconfig output does not contain information on which slaves are associated with which masters.”h]”hXThe network configuration can be inspected using the ifconfig command. Bonding devices will have the MASTER flag set; Bonding slave devices will have the SLAVE flag set. The ifconfig output does not contain information on which slaves are associated with which masters.”…””}”(hjÉ"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mjhj¸"h²hubhÞ)”}”(hXIn the example below, the bond0 interface is the master (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of bond0 have the same MAC address (HWaddr) as bond0 for all modes except TLB and ALB that require a unique MAC address for each slave::”h]”hXIn the example below, the bond0 interface is the master (MASTER) while eth0 and eth1 are slaves (SLAVE). Notice all slaves of bond0 have the same MAC address (HWaddr) as bond0 for all modes except TLB and ALB that require a unique MAC address for each slave:”…””}”(hj×"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mohj¸"h²hubj~)”}”(hX0# /sbin/ifconfig bond0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0 TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:0 eth0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:3573025 errors:0 dropped:0 overruns:0 frame:0 TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x1080 eth1 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:3651769 errors:0 dropped:0 overruns:0 frame:0 TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0x1400”h]”hX0# /sbin/ifconfig bond0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0 TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:0 eth0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:3573025 errors:0 dropped:0 overruns:0 frame:0 TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 Interrupt:10 Base address:0x1080 eth1 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:3651769 errors:0 dropped:0 overruns:0 frame:0 TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0x1400”…””}”hjå"sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mthj¸"h²hubeh}”(h]”Œnetwork-configuration”ah ]”h"]”Œ4.2 network configuration”ah$]”h&]”uh1hÈhjV"h²hh³hÇh´Mhubeh}”(h]”Œquerying-bonding-configuration”ah ]”h"]”Œ 4 querying bonding configuration”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´MGubhÉ)”}”(hhh]”(hÎ)”}”(hŒ5. Switch Configuration”h]”hŒ5. Switch Configuration”…””}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj#h²hh³hÇh´M‹ubhÞ)”}”(hXFor this section, "switch" refers to whatever system the bonded devices are directly connected to (i.e., where the other end of the cable plugs into). This may be an actual dedicated switch device, or it may be another regular system (e.g., another computer running Linux),”h]”hXFor this section, â€œswitchâ€ refers to whatever system the bonded devices are directly connected to (i.e., where the other end of the cable plugs into). This may be an actual dedicated switch device, or it may be another regular system (e.g., another computer running Linux),”…””}”(hj#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj#h²hubhÞ)”}”(hŒmThe active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch.”h]”hŒmThe active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch.”…””}”(hj"#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M“hj#h²hubhÞ)”}”(hX¤The 802.3ad mode requires that the switch have the appropriate ports configured as an 802.3ad aggregation. The precise method used to configure this varies from switch to switch, but, for example, a Cisco 3550 series switch requires that the appropriate ports first be grouped together in a single etherchannel instance, then that etherchannel is set to mode "lacp" to enable 802.3ad (instead of standard EtherChannel).”h]”hX¨The 802.3ad mode requires that the switch have the appropriate ports configured as an 802.3ad aggregation. The precise method used to configure this varies from switch to switch, but, for example, a Cisco 3550 series switch requires that the appropriate ports first be grouped together in a single etherchannel instance, then that etherchannel is set to mode â€œlacpâ€ to enable 802.3ad (instead of standard EtherChannel).”…””}”(hj0#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M–hj#h²hubhÞ)”}”(hXÉThe balance-rr, balance-xor and broadcast modes generally require that the switch have the appropriate ports grouped together. The nomenclature for such a group differs between switches, it may be called an "etherchannel" (as in the Cisco example, above), a "trunk group" or some other similar variation. For these modes, each switch will also have its own configuration options for the switch's transmit policy to the bond. Typical choices include XOR of either the MAC or IP addresses. The transmit policy of the two peers does not need to match. For these three modes, the bonding mode really selects a transmit policy for an EtherChannel group; all three will interoperate with another EtherChannel group.”h]”hXÓThe balance-rr, balance-xor and broadcast modes generally require that the switch have the appropriate ports grouped together. The nomenclature for such a group differs between switches, it may be called an â€œetherchannelâ€ (as in the Cisco example, above), a â€œtrunk groupâ€ or some other similar variation. For these modes, each switch will also have its own configuration options for the switchâ€™s transmit policy to the bond. Typical choices include XOR of either the MAC or IP addresses. The transmit policy of the two peers does not need to match. For these three modes, the bonding mode really selects a transmit policy for an EtherChannel group; all three will interoperate with another EtherChannel group.”…””}”(hj>#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mžhj#h²hubeh}”(h]”Œswitch-configuration”ah ]”h"]”Œ5. switch configuration”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M‹ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ6. 802.1q VLAN Support”h]”hŒ6. 802.1q VLAN Support”…””}”(hjW#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjT#h²hh³hÇh´M¬ubhÞ)”}”(hXëIt is possible to configure VLAN devices over a bond interface using the 8021q driver. However, only packets coming from the 8021q driver and passing through bonding will be tagged by default. Self generated packets, for example, bonding's learning packets or ARP packets generated by either ALB mode or the ARP monitor mechanism, are tagged internally by bonding itself. As a result, bonding must "learn" the VLAN IDs configured above it, and use those IDs to tag self generated packets.”h]”hXñIt is possible to configure VLAN devices over a bond interface using the 8021q driver. However, only packets coming from the 8021q driver and passing through bonding will be tagged by default. Self generated packets, for example, bondingâ€™s learning packets or ARP packets generated by either ALB mode or the ARP monitor mechanism, are tagged internally by bonding itself. As a result, bonding must â€œlearnâ€ the VLAN IDs configured above it, and use those IDs to tag self generated packets.”…””}”(hje#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M®hjT#h²hubhÞ)”}”(hXFor reasons of simplicity, and to support the use of adapters that can do VLAN hardware acceleration offloading, the bonding interface declares itself as fully hardware offloading capable, it gets the add_vid/kill_vid notifications to gather the necessary information, and it propagates those actions to the slaves. In case of mixed adapter types, hardware accelerated tagged packets that should go through an adapter that is not offloading capable are "un-accelerated" by the bonding driver so the VLAN tag sits in the regular location.”h]”hXFor reasons of simplicity, and to support the use of adapters that can do VLAN hardware acceleration offloading, the bonding interface declares itself as fully hardware offloading capable, it gets the add_vid/kill_vid notifications to gather the necessary information, and it propagates those actions to the slaves. In case of mixed adapter types, hardware accelerated tagged packets that should go through an adapter that is not offloading capable are â€œun-acceleratedâ€ by the bonding driver so the VLAN tag sits in the regular location.”…””}”(hjs#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M·hjT#h²hubhÞ)”}”(hXÚVLAN interfaces *must* be added on top of a bonding interface only after enslaving at least one slave. The bonding interface has a hardware address of 00:00:00:00:00:00 until the first slave is added. If the VLAN interface is created prior to the first enslavement, it would pick up the all-zeroes hardware address. Once the first slave is attached to the bond, the bond device itself will pick up the slave's hardware address, which is then available for the VLAN device.”h]”(hŒVLAN interfaces ”…””}”(hj#h²hh³Nh´Nubjë)”}”(hŒ*must*”h]”hŒmust”…””}”(hj‰#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jêhj#ubhXÆ be added on top of a bonding interface only after enslaving at least one slave. The bonding interface has a hardware address of 00:00:00:00:00:00 until the first slave is added. If the VLAN interface is created prior to the first enslavement, it would pick up the all-zeroes hardware address. Once the first slave is attached to the bond, the bond device itself will pick up the slaveâ€™s hardware address, which is then available for the VLAN device.”…””}”(hj#h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÁhjT#h²hubhÞ)”}”(hXoAlso, be aware that a similar problem can occur if all slaves are released from a bond that still has one or more VLAN interfaces on top of it. When a new slave is added, the bonding interface will obtain its hardware address from the first slave, which might not match the hardware address of the VLAN interfaces (which was ultimately copied from an earlier slave).”h]”hXoAlso, be aware that a similar problem can occur if all slaves are released from a bond that still has one or more VLAN interfaces on top of it. When a new slave is added, the bonding interface will obtain its hardware address from the first slave, which might not match the hardware address of the VLAN interfaces (which was ultimately copied from an earlier slave).”…””}”(hj¡#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÉhjT#h²hubhÞ)”}”(hŒThere are two methods to ensure that the VLAN device operates with the correct hardware address if all slaves are removed from a bond interface:”h]”hŒThere are two methods to ensure that the VLAN device operates with the correct hardware address if all slaves are removed from a bond interface:”…””}”(hj¯#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÐhjT#h²hubj¾!)”}”(hhh]”j)”}”(hŒ.Remove all VLAN interfaces then recreate them ”h]”hÞ)”}”(hŒ-Remove all VLAN interfaces then recreate them”h]”hŒ-Remove all VLAN interfaces then recreate them”…””}”(hjÄ#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÔhjÀ#ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj½#h²hh³hÇh´Nubah}”(h]”h ]”h"]”h$]”h&]”j:"Œarabic”j<"hj>"Œ.”uh1j½!hjT#h²hh³hÇh´MÔubhÞ)”}”(hŒo2. Set the bonding interface's hardware address so that it matches the hardware address of the VLAN interfaces.”h]”hŒq2. Set the bonding interfaceâ€™s hardware address so that it matches the hardware address of the VLAN interfaces.”…””}”(hjà#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÖhjT#h²hubhÞ)”}”(hŒ¨Note that changing a VLAN interface's HW address would set the underlying device -- i.e. the bonding interface -- to promiscuous mode, which might not be what you want.”h]”hŒªNote that changing a VLAN interfaceâ€™s HW address would set the underlying device -- i.e. the bonding interface -- to promiscuous mode, which might not be what you want.”…””}”(hjî#h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÙhjT#h²hubeh}”(h]”Œq-vlan-support”ah ]”h"]”Œ6. 802.1q vlan support”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M¬ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ7. Link Monitoring”h]”hŒ7. Link Monitoring”…””}”(hj$h²hh³Nh´Nubah}”(•-h]”h ]”h"]”h$]”h&]”uh1hÍhj$h²hh³hÇh´MßubhÞ)”}”(hŒƒThe bonding driver at present supports two schemes for monitoring a slave device's link state: the ARP monitor and the MII monitor.”h]”hŒ…The bonding driver at present supports two schemes for monitoring a slave deviceâ€™s link state: the ARP monitor and the MII monitor.”…””}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Máhj$h²hubhÞ)”}”(hŒžAt the present time, due to implementation restrictions in the bonding driver itself, it is not possible to enable both ARP and MII monitoring simultaneously.”h]”hŒžAt the present time, due to implementation restrictions in the bonding driver itself, it is not possible to enable both ARP and MII monitoring simultaneously.”…””}”(hj#$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Måhj$h²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ7.1 ARP Monitor Operation”h]”hŒ7.1 ARP Monitor Operation”…””}”(hj4$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj1$h²hh³hÇh´MêubhÞ)”}”(hX-The ARP monitor operates as its name suggests: it sends ARP queries to one or more designated peer systems on the network, and uses the response as an indication that the link is operating. This gives some assurance that traffic is actually flowing to and from one or more peers on the local network.”h]”hX-The ARP monitor operates as its name suggests: it sends ARP queries to one or more designated peer systems on the network, and uses the response as an indication that the link is operating. This gives some assurance that traffic is actually flowing to and from one or more peers on the local network.”…””}”(hjB$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mìhj1$h²hubeh}”(h]”Œarp-monitor-operation”ah ]”h"]”Œ7.1 arp monitor operation”ah$]”h&]”uh1hÈhj$h²hh³hÇh´MêubhÉ)”}”(hhh]”(hÎ)”}”(hŒ$7.2 Configuring Multiple ARP Targets”h]”hŒ$7.2 Configuring Multiple ARP Targets”…””}”(hj[$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjX$h²hh³hÇh´MóubhÞ)”}”(hX\While ARP monitoring can be done with just one target, it can be useful in a High Availability setup to have several targets to monitor. In the case of just one target, the target itself may go down or have a problem making it unresponsive to ARP requests. Having an additional target (or several) increases the reliability of the ARP monitoring.”h]”hX\While ARP monitoring can be done with just one target, it can be useful in a High Availability setup to have several targets to monitor. In the case of just one target, the target itself may go down or have a problem making it unresponsive to ARP requests. Having an additional target (or several) increases the reliability of the ARP monitoring.”…””}”(hji$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MõhjX$h²hubhÞ)”}”(hŒ=Multiple ARP targets must be separated by commas as follows::”h]”hŒhjd%h²hubhÞ)”}”(hŒ&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‚hj&h²hubj )”}”(hXíinterfaces.ifTable.ifEntry.ifDescr.1 = lo interfaces.ifTable.ifEntry.ifDescr.2 = bond0 interfaces.ifTable.ifEntry.ifDescr.3 = eth0 interfaces.ifTable.ifEntry.ifDescr.4 = eth1 interfaces.ifTable.ifEntry.ifDescr.5 = eth2 interfaces.ifTable.ifEntry.ifDescr.6 = eth3 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.10.10.10 = 6 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.192.168.1.1 = 2 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.74.20.94 = 5 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.127.0.0.1 = 1 ”h]”hÞ)”}”(hXìinterfaces.ifTable.ifEntry.ifDescr.1 = lo interfaces.ifTable.ifEntry.ifDescr.2 = bond0 interfaces.ifTable.ifEntry.ifDescr.3 = eth0 interfaces.ifTable.ifEntry.ifDescr.4 = eth1 interfaces.ifTable.ifEntry.ifDescr.5 = eth2 interfaces.ifTable.ifEntry.ifDescr.6 = eth3 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.10.10.10 = 6 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.192.168.1.1 = 2 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.74.20.94 = 5 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.127.0.0.1 = 1”h]”hXìinterfaces.ifTable.ifEntry.ifDescr.1 = lo interfaces.ifTable.ifEntry.ifDescr.2 = bond0 interfaces.ifTable.ifEntry.ifDescr.3 = eth0 interfaces.ifTable.ifEntry.ifDescr.4 = eth1 interfaces.ifTable.ifEntry.ifDescr.5 = eth2 interfaces.ifTable.ifEntry.ifDescr.6 = eth3 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.10.10.10 = 6 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.192.168.1.1 = 2 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.10.74.20.94 = 5 ip.ipAddrTable.ipAddrEntry.ipAdEntIfIndex.127.0.0.1 = 1”…””}”(hjP&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‡hjL&ubah}”(h]”h ]”h"]”h$]”h&]”uh1j h³hÇh´M‡hj&h²hubhÞ)”}”(hŒÎWhile some distributions may not report the interface name in ifDescr, the association between the IP address and IfIndex remains and SNMP functions such as Interface_Scan_Next will report that association.”h]”hŒÎWhile some distributions may not report the interface name in ifDescr, the association between the IP address and IfIndex remains and SNMP functions such as Interface_Scan_Next will report that association.”…””}”(hjd&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M’hj&h²hubeh}”(h]”Œsnmp-agents”ah ]”h"]”Œ9. snmp agents”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´MhubhÉ)”}”(hhh]”(hÎ)”}”(hŒ10. Promiscuous mode”h]”hŒ10. Promiscuous mode”…””}”(hj}&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjz&h²hh³hÇh´M˜ubhÞ)”}”(hXWWhen running network monitoring tools, e.g., tcpdump, it is common to enable promiscuous mode on the device, so that all traffic is seen (instead of seeing only traffic destined for the local host). The bonding driver handles promiscuous mode changes to the bonding master device (e.g., bond0), and propagates the setting to the slave devices.”h]”hXWWhen running network monitoring tools, e.g., tcpdump, it is common to enable promiscuous mode on the device, so that all traffic is seen (instead of seeing only traffic destined for the local host). The bonding driver handles promiscuous mode changes to the bonding master device (e.g., bond0), and propagates the setting to the slave devices.”…””}”(hj‹&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mšhjz&h²hubhÞ)”}”(hŒxFor the balance-rr, balance-xor, broadcast, and 802.3ad modes, the promiscuous mode setting is propagated to all slaves.”h]”hŒxFor the balance-rr, balance-xor, broadcast, and 802.3ad modes, the promiscuous mode setting is propagated to all slaves.”…””}”(hj™&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¡hjz&h²hubhÞ)”}”(hŒ~For the active-backup, balance-tlb and balance-alb modes, the promiscuous mode setting is propagated only to the active slave.”h]”hŒ~For the active-backup, balance-tlb and balance-alb modes, the promiscuous mode setting is propagated only to the active slave.”…””}”(hj§&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¤hjz&h²hubhÞ)”}”(hŒXFor balance-tlb mode, the active slave is the slave currently receiving inbound traffic.”h]”hŒXFor balance-tlb mode, the active slave is the slave currently receiving inbound traffic.”…””}”(hjµ&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M§hjz&h²hubhÞ)”}”(hŒÆFor balance-alb mode, the active slave is the slave used as a "primary." This slave is used for mode-specific control traffic, for sending to peers that are unassigned or if the load is unbalanced.”h]”hŒÊFor balance-alb mode, the active slave is the slave used as a â€œprimary.â€ This slave is used for mode-specific control traffic, for sending to peers that are unassigned or if the load is unbalanced.”…””}”(hjÃ&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mªhjz&h²hubhÞ)”}”(hŒºFor the active-backup, balance-tlb and balance-alb modes, when the active slave changes (e.g., due to a link failure), the promiscuous setting will be propagated to the new active slave.”h]”hŒºFor the active-backup, balance-tlb and balance-alb modes, when the active slave changes (e.g., due to a link failure), the promiscuous setting will be propagated to the new active slave.”…””}”(hjÑ&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M®hjz&h²hubeh}”(h]”Œpromiscuous-mode”ah ]”h"]”Œ10. promiscuous mode”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M˜ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ-11. Configuring Bonding for High Availability”h]”hŒ-11. Configuring Bonding for High Availability”…””}”(hjê&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjç&h²hh³hÇh´M³ubhÞ)”}”(hXfHigh Availability refers to configurations that provide maximum network availability by having redundant or backup devices, links or switches between the host and the rest of the world. The goal is to provide the maximum availability of network connectivity (i.e., the network always works), even though other configurations could provide higher throughput.”h]”hXfHigh Availability refers to configurations that provide maximum network availability by having redundant or backup devices, links or switches between the host and the rest of the world. The goal is to provide the maximum availability of network connectivity (i.e., the network always works), even though other configurations could provide higher throughput.”…””}”(hjø&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mµhjç&h²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ211.1 High Availability in a Single Switch Topology”h]”hŒ211.1 High Availability in a Single Switch Topology”…””}”(hj 'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj'h²hh³hÇh´M½ubhÞ)”}”(hXÍIf two hosts (or a host and a single switch) are directly connected via multiple physical links, then there is no availability penalty to optimizing for maximum bandwidth. In this case, there is only one switch (or peer), so if it fails, there is no alternative access to fail over to. Additionally, the bonding load balance modes support link monitoring of their members, so if individual links fail, the load will be rebalanced across the remaining devices.”h]”hXÍIf two hosts (or a host and a single switch) are directly connected via multiple physical links, then there is no availability penalty to optimizing for maximum bandwidth. In this case, there is only one switch (or peer), so if it fails, there is no alternative access to fail over to. Additionally, the bonding load balance modes support link monitoring of their members, so if individual links fail, the load will be rebalanced across the remaining devices.”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¿hj'h²hubhÞ)”}”(hŒySee Section 12, "Configuring Bonding for Maximum Throughput" for information on configuring bonding with one peer device.”h]”hŒ}See Section 12, â€œConfiguring Bonding for Maximum Throughputâ€ for information on configuring bonding with one peer device.”…””}”(hj%'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÇhj'h²hubeh}”(h]”Œ-high-availability-in-a-single-switch-topology”ah ]”h"]”Œ211.1 high availability in a single switch topology”ah$]”h&]”uh1hÈhjç&h²hh³hÇh´M½ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ411.2 High Availability in a Multiple Switch Topology”h]”hŒ411.2 High Availability in a Multiple Switch Topology”…””}”(hj>'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj;'h²hh³hÇh´MËubhÞ)”}”(hŒÂWith multiple switches, the configuration of bonding and the network changes dramatically. In multiple switch topologies, there is a trade off between network availability and usable bandwidth.”h]”hŒÂWith multiple switches, the configuration of bonding and the network changes dramatically. In multiple switch topologies, there is a trade off between network availability and usable bandwidth.”…””}”(hjL'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÍhj;'h²hubhÞ)”}”(hŒSBelow is a sample network, configured to maximize the availability of the network::”h]”hŒRBelow is a sample network, configured to maximize the availability of the network:”…””}”(hjZ'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÑhj;'h²hubj~)”}”(hX | | |port3 port3| +-----+----+ +-----+----+ | |port2 ISL port2| | | switch A +--------------------------+ switch B | | | | | +-----+----+ +-----++---+ |port1 port1| | +-------+ | +-------------+ host1 +---------------+ eth0 +-------+ eth1”h]”hX | | |port3 port3| +-----+----+ +-----+----+ | |port2 ISL port2| | | switch A +--------------------------+ switch B | | | | | +-----+----+ +-----++---+ |port1 port1| | +-------+ | +-------------+ host1 +---------------+ eth0 +-------+ eth1”…””}”hjh'sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MÔhj;'h²hubhÞ)”}”(hŒúIn this configuration, there is a link between the two switches (ISL, or inter switch link), and multiple ports connecting to the outside world ("port3" on each switch). There is no technical reason that this could not be extended to a third switch.”h]”hŒþIn this configuration, there is a link between the two switches (ISL, or inter switch link), and multiple ports connecting to the outside world (â€œport3â€ on each switch). There is no technical reason that this could not be extended to a third switch.”…””}”(hjv'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Màhj;'h²hubeh}”(h]”Œ/high-availability-in-a-multiple-switch-topology”ah ]”h"]”Œ411.2 high availability in a multiple switch topology”ah$]”h&]”uh1hÈhjç&h²hh³hÇh´MËubhÉ)”}”(hhh]”(hÎ)”}”(hŒ=11.2.1 HA Bonding Mode Selection for Multiple Switch Topology”h]”hŒ=11.2.1 HA Bonding Mode Selection for Multiple Switch Topology”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjŒ'h²hh³hÇh´MæubhÞ)”}”(hŒñIn a topology such as the example above, the active-backup and broadcast modes are the only useful bonding modes when optimizing for availability; the other modes require all links to terminate on the same peer for them to behave rationally.”h]”hŒñIn a topology such as the example above, the active-backup and broadcast modes are the only useful bonding modes when optimizing for availability; the other modes require all links to terminate on the same peer for them to behave rationally.”…””}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MèhjŒ'h²hubjÖ)”}”(hhh]”(jÛ)”}”(hXeactive-backup: This is generally the preferred mode, particularly if the switches have an ISL and play together well. If the network configuration is such that one switch is specifically a backup switch (e.g., has lower capacity, higher cost, etc), then the primary option can be used to ensure that the preferred link is always used when it is available. ”h]”(já)”}”(hŒactive-backup:”h]”hŒactive-backup:”…””}”(hj²'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´Móhj®'ubjñ)”}”(hhh]”hÞ)”}”(hXUThis is generally the preferred mode, particularly if the switches have an ISL and play together well. If the network configuration is such that one switch is specifically a backup switch (e.g., has lower capacity, higher cost, etc), then the primary option can be used to ensure that the preferred link is always used when it is available.”h]”hXUThis is generally the preferred mode, particularly if the switches have an ISL and play together well. If the network configuration is such that one switch is specifically a backup switch (e.g., has lower capacity, higher cost, etc), then the primary option can be used to ensure that the preferred link is always used when it is available.”…””}”(hjÃ'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MîhjÀ'ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhj®'ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´Móhj«'ubjÛ)”}”(hXjbroadcast: This mode is really a special purpose mode, and is suitable only for very specific needs. For example, if the two switches are not connected (no ISL), and the networks beyond them are totally independent. In this case, if it is necessary for some specific one-way traffic to reach both independent networks, then the broadcast mode may be suitable. ”h]”(já)”}”(hŒ broadcast:”h]”hŒ broadcast:”…””}”(hjá'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´MûhjÝ'ubjñ)”}”(hhh]”hÞ)”}”(hX^This mode is really a special purpose mode, and is suitable only for very specific needs. For example, if the two switches are not connected (no ISL), and the networks beyond them are totally independent. In this case, if it is necessary for some specific one-way traffic to reach both independent networks, then the broadcast mode may be suitable.”h]”hX^This mode is really a special purpose mode, and is suitable only for very specific needs. For example, if the two switches are not connected (no ISL), and the networks beyond them are totally independent. In this case, if it is necessary for some specific one-way traffic to reach both independent networks, then the broadcast mode may be suitable.”…””}”(hjò'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Möhjï'ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhjÝ'ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´Mûhj«'h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhjŒ'h²hh³hÇh´Nubeh}”(h]”Œ6ha-bonding-mode-selection-for-multiple-switch-topology”ah ]”h"]”Œ=11.2.1 ha bonding mode selection for multiple switch topology”ah$]”h&]”uh1hÈhjç&h²hh³hÇh´MæubhÉ)”}”(hhh]”(hÎ)”}”(hŒ@11.2.2 HA Link Monitoring Selection for Multiple Switch Topology”h]”hŒ@11.2.2 HA Link Monitoring Selection for Multiple Switch Topology”…””}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj(h²hh³hÇh´MþubhÞ)”}”(hXÁThe choice of link monitoring ultimately depends upon your switch. If the switch can reliably fail ports in response to other failures, then either the MII or ARP monitors should work. For example, in the above example, if the "port3" link fails at the remote end, the MII monitor has no direct means to detect this. The ARP monitor could be configured with a target at the remote end of port3, thus detecting that failure without switch support.”h]”hXÅThe choice of link monitoring ultimately depends upon your switch. If the switch can reliably fail ports in response to other failures, then either the MII or ARP monitors should work. For example, in the above example, if the â€œport3â€ link fails at the remote end, the MII monitor has no direct means to detect this. The ARP monitor could be configured with a target at the remote end of port3, thus detecting that failure without switch support.”…””}”(hj+(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj(h²hubhÞ)”}”(hXãIn general, however, in a multiple switch topology, the ARP monitor can provide a higher level of reliability in detecting end to end connectivity failures (which may be caused by the failure of any individual component to pass traffic for any reason). Additionally, the ARP monitor should be configured with multiple targets (at least one for each switch in the network). This will ensure that, regardless of which switch is active, the ARP monitor has a suitable target to query.”h]”hXãIn general, however, in a multiple switch topology, the ARP monitor can provide a higher level of reliability in detecting end to end connectivity failures (which may be caused by the failure of any individual component to pass traffic for any reason). Additionally, the ARP monitor should be configured with multiple targets (at least one for each switch in the network). This will ensure that, regardless of which switch is active, the ARP monitor has a suitable target to query.”…””}”(hj9(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj(h²hubhÞ)”}”(hXHNote, also, that of late many switches now support a functionality generally referred to as "trunk failover." This is a feature of the switch that causes the link state of a particular switch port to be set down (or up) when the state of another switch port goes down (or up). Its purpose is to propagate link failures from logically "exterior" ports to the logically "interior" ports that bonding is able to monitor via miimon. Availability and configuration for trunk failover varies by switch, but this can be a viable alternative to the ARP monitor when using suitable switches.”h]”hXTNote, also, that of late many switches now support a functionality generally referred to as â€œtrunk failover.â€ This is a feature of the switch that causes the link state of a particular switch port to be set down (or up) when the state of another switch port goes down (or up). Its purpose is to propagate link failures from logically â€œexteriorâ€ ports to the logically â€œinteriorâ€ ports that bonding is able to monitor via miimon. Availability and configuration for trunk failover varies by switch, but this can be a viable alternative to the ARP monitor when using suitable switches.”…””}”(hjG(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj(h²hubeh}”(h]”Œ9ha-link-monitoring-selection-for-multiple-switch-topology”ah ]”h"]”Œ@11.2.2 ha link monitoring selection for multiple switch topology”ah$]”h&]”uh1hÈhjç&h²hh³hÇh´Mþubeh}”(h]”Œ)configuring-bonding-for-high-availability”ah ]”h"]”Œ-11. configuring bonding for high availability”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M³ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ.12. Configuring Bonding for Maximum Throughput”h]”hŒ.12. Configuring Bonding for Maximum Throughput”…””}”(hjh(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhje(h²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ612.1 Maximizing Throughput in a Single Switch Topology”h]”hŒ612.1 Maximizing Throughput in a Single Switch Topology”…””}”(hjy(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjv(h²hh³hÇh´M ubhÞ)”}”(hŒñIn a single switch configuration, the best method to maximize throughput depends upon the application and network environment. The various load balancing modes each have strengths and weaknesses in different environments, as detailed below.”h]”hŒñIn a single switch configuration, the best method to maximize throughput depends upon the application and network environment. The various load balancing modes each have strengths and weaknesses in different environments, as detailed below.”…””}”(hj‡(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M! hjv(h²hubhÞ)”}”(hŒÂFor this discussion, we will break down the topologies into two categories. Depending upon the destination of most traffic, we categorize them into either "gatewayed" or "local" configurations.”h]”hŒÊFor this discussion, we will break down the topologies into two categories. Depending upon the destination of most traffic, we categorize them into either â€œgatewayedâ€ or â€œlocalâ€ configurations.”…””}”(hj•(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M& hjv(h²hubhÞ)”}”(hŒºIn a gatewayed configuration, the "switch" is acting primarily as a router, and the majority of traffic passes through this router to other networks. An example would be the following::”h]”hŒ½In a gatewayed configuration, the â€œswitchâ€ is acting primarily as a router, and the majority of traffic passes through this router to other networks. An example would be the following:”…””}”(hj£(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M* hjv(h²hubj~)”}”(hX^+----------+ +----------+ | |eth0 port1| | to other networks | Host A +---------------------+ router +-------------------> | +---------------------+ | Hosts B and C are out | |eth1 port2| | here somewhere +----------+ +----------+”h]”hX^+----------+ +----------+ | |eth0 port1| | to other networks | Host A +---------------------+ router +-------------------> | +---------------------+ | Hosts B and C are out | |eth1 port2| | here somewhere +----------+ +----------+”…””}”hj±(sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´M/ hjv(h²hubhÞ)”}”(hXThe router may be a dedicated router device, or another host acting as a gateway. For our discussion, the important point is that the majority of traffic from Host A will pass through the router to some other network before reaching its final destination.”h]”hXThe router may be a dedicated router device, or another host acting as a gateway. For our discussion, the important point is that the majority of traffic from Host A will pass through the router to some other network before reaching its final destination.”…””}”(hj¿(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6 hjv(h²hubhÞ)”}”(hŒÀIn a gatewayed network configuration, although Host A may communicate with many other systems, all of its traffic will be sent and received via one other peer on the local network, the router.”h]”hŒÀIn a gatewayed network configuration, although Host A may communicate with many other systems, all of its traffic will be sent and received via one other peer on the local network, the router.”…””}”(hjÍ(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M; hjv(h²hubhÞ)”}”(hXNote that the case of two systems connected directly via multiple physical links is, for purposes of configuring bonding, the same as a gatewayed configuration. In that case, it happens that all traffic is destined for the "gateway" itself, not some other network beyond the gateway.”h]”hX Note that the case of two systems connected directly via multiple physical links is, for purposes of configuring bonding, the same as a gatewayed configuration. In that case, it happens that all traffic is destined for the â€œgatewayâ€ itself, not some other network beyond the gateway.”…””}”(hjÛ(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M? hjv(h²hubhÞ)”}”(hŒÐIn a local configuration, the "switch" is acting primarily as a switch, and the majority of traffic passes through this switch to reach other stations on the same network. An example would be the following::”h]”hŒÓIn a local configuration, the â€œswitchâ€ is acting primarily as a switch, and the majority of traffic passes through this switch to reach other stations on the same network. An example would be the following:”…””}”(hjé(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´ME hjv(h²hubj~)”}”(hXd+----------+ +----------+ +--------+ | |eth0 port1| +-------+ Host B | | Host A +------------+ switch |port3 +--------+ | +------------+ | +--------+ | |eth1 port2| +------------------+ Host C | +----------+ +----------+port4 +--------+”h]”hXd+----------+ +----------+ +--------+ | |eth0 port1| +-------+ Host B | | Host A +------------+ switch |port3 +--------+ | +------------+ | +--------+ | |eth1 port2| +------------------+ Host C | +----------+ +----------+port4 +--------+”…””}”hj÷(sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´MJ hjv(h²hubhÞ)”}”(hX Again, the switch may be a dedicated switch device, or another host acting as a gateway. For our discussion, the important point is that the majority of traffic from Host A is destined for other hosts on the same local network (Hosts B and C in the above example).”h]”hX Again, the switch may be a dedicated switch device, or another host acting as a gateway. For our discussion, the important point is that the majority of traffic from Host A is destined for other hosts on the same local network (Hosts B and C in the above example).”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MR hjv(h²hubhÞ)”}”(hXŠIn summary, in a gatewayed configuration, traffic to and from the bonded device will be to the same MAC level peer on the network (the gateway itself, i.e., the router), regardless of its final destination. In a local configuration, traffic flows directly to and from the final destinations, thus, each destination (Host B, Host C) will be addressed directly by their individual MAC addresses.”h]”hXŠIn summary, in a gatewayed configuration, traffic to and from the bonded device will be to the same MAC level peer on the network (the gateway itself, i.e., the router), regardless of its final destination. In a local configuration, traffic flows directly to and from the final destinations, thus, each destination (Host B, Host C) will be addressed directly by their individual MAC addresses.”…””}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MW hjv(h²hubhÞ)”}”(hXThis distinction between a gatewayed and a local network configuration is important because many of the load balancing modes available use the MAC addresses of the local network source and destination to make load balancing decisions. The behavior of each mode is described below.”h]”hXThis distinction between a gatewayed and a local network configuration is important because many of the load balancing modes available use the MAC addresses of the local network source and destination to make load balancing decisions. The behavior of each mode is described below.”…””}”(hj!)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M^ hjv(h²hubeh}”(h]”Œ1maximizing-throughput-in-a-single-switch-topology”ah ]”h"]”Œ612.1 maximizing throughput in a single switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ;12.1.1 MT Bonding Mode Selection for Single Switch Topology”h]”hŒ;12.1.1 MT Bonding Mode Selection for Single Switch Topology”…””}”(hj:)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj7)h²hh³hÇh´Mf ubhÞ)”}”(hŒ»This configuration is the easiest to set up and to understand, although you will have to decide which bonding mode best suits your needs. The trade offs for each mode are detailed below:”h]”hŒ»This configuration is the easiest to set up and to understand, although you will have to decide which bonding mode best suits your needs. The trade offs for each mode are detailed below:”…””}”(hjH)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mh hj7)h²hubjÖ)”}”(hhh]”(jÛ)”}”(hX-balance-rr: This mode is the only mode that will permit a single TCP/IP connection to stripe traffic across multiple interfaces. It is therefore the only mode that will allow a single TCP/IP stream to utilize more than one interface's worth of throughput. This comes at a cost, however: the striping generally results in peer systems receiving packets out of order, causing TCP/IP's congestion control system to kick in, often by retransmitting segments. It is possible to adjust TCP/IP's congestion limits by altering the net.ipv4.tcp_reordering sysctl parameter. The usual default value is 3. But keep in mind TCP stack is able to automatically increase this when it detects reorders. Note that the fraction of packets that will be delivered out of order is highly variable, and is unlikely to be zero. The level of reordering depends upon a variety of factors, including the networking interfaces, the switch, and the topology of the configuration. Speaking in general terms, higher speed network cards produce more reordering (due to factors such as packet coalescing), and a "many to many" topology will reorder at a higher rate than a "many slow to one fast" configuration. Many switches do not support any modes that stripe traffic (instead choosing a port based upon IP or MAC level addresses); for those devices, traffic for a particular connection flowing through the switch to a balance-rr bond will not utilize greater than one interface's worth of bandwidth. If you are utilizing protocols other than TCP/IP, UDP for example, and your application can tolerate out of order delivery, then this mode can allow for single stream datagram performance that scales near linearly as interfaces are added to the bond. This mode requires the switch to have the appropriate ports configured for "etherchannel" or "trunking." ”h]”(já)”}”(hŒbalance-rr:”h]”hŒbalance-rr:”…””}”(hj])h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M‘ hjY)ubjñ)”}”(hhh]”(hÞ)”}”(hX»This mode is the only mode that will permit a single TCP/IP connection to stripe traffic across multiple interfaces. It is therefore the only mode that will allow a single TCP/IP stream to utilize more than one interface's worth of throughput. This comes at a cost, however: the striping generally results in peer systems receiving packets out of order, causing TCP/IP's congestion control system to kick in, often by retransmitting segments.”h]”hX¿This mode is the only mode that will permit a single TCP/IP connection to stripe traffic across multiple interfaces. It is therefore the only mode that will allow a single TCP/IP stream to utilize more than one interfaceâ€™s worth of throughput. This comes at a cost, however: the striping generally results in peer systems receiving packets out of order, causing TCP/IPâ€™s congestion control system to kick in, often by retransmitting segments.”…””}”(hjn)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mm hjk)ubhÞ)”}”(hŒèIt is possible to adjust TCP/IP's congestion limits by altering the net.ipv4.tcp_reordering sysctl parameter. The usual default value is 3. But keep in mind TCP stack is able to automatically increase this when it detects reorders.”h]”hŒêIt is possible to adjust TCP/IPâ€™s congestion limits by altering the net.ipv4.tcp_reordering sysctl parameter. The usual default value is 3. But keep in mind TCP stack is able to automatically increase this when it detects reorders.”…””}”(hj|)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mv hjk)ubhÞ)”}”(hXîNote that the fraction of packets that will be delivered out of order is highly variable, and is unlikely to be zero. The level of reordering depends upon a variety of factors, including the networking interfaces, the switch, and the topology of the configuration. Speaking in general terms, higher speed network cards produce more reordering (due to factors such as packet coalescing), and a "many to many" topology will reorder at a higher rate than a "many slow to one fast" configuration.”h]”hXöNote that the fraction of packets that will be delivered out of order is highly variable, and is unlikely to be zero. The level of reordering depends upon a variety of factors, including the networking interfaces, the switch, and the topology of the configuration. Speaking in general terms, higher speed network cards produce more reordering (due to factors such as packet coalescing), and a â€œmany to manyâ€ topology will reorder at a higher rate than a â€œmany slow to one fastâ€ configuration.”…””}”(hjŠ)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M{ hjk)ubhÞ)”}”(hX#Many switches do not support any modes that stripe traffic (instead choosing a port based upon IP or MAC level addresses); for those devices, traffic for a particular connection flowing through the switch to a balance-rr bond will not utilize greater than one interface's worth of bandwidth.”h]”hX%Many switches do not support any modes that stripe traffic (instead choosing a port based upon IP or MAC level addresses); for those devices, traffic for a particular connection flowing through the switch to a balance-rr bond will not utilize greater than one interfaceâ€™s worth of bandwidth.”…””}”(hj˜)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M„ hjk)ubhÞ)”}”(hŒúIf you are utilizing protocols other than TCP/IP, UDP for example, and your application can tolerate out of order delivery, then this mode can allow for single stream datagram performance that scales near linearly as interfaces are added to the bond.”h]”hŒúIf you are utilizing protocols other than TCP/IP, UDP for example, and your application can tolerate out of order delivery, then this mode can allow for single stream datagram performance that scales near linearly as interfaces are added to the bond.”…””}”(hj¦)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŠ hjk)ubhÞ)”}”(hŒhThis mode requires the switch to have the appropriate ports configured for "etherchannel" or "trunking."”h]”hŒpThis mode requires the switch to have the appropriate ports configured for â€œetherchannelâ€ or â€œtrunking.â€”…””}”(hj´)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjk)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhjY)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M‘ hjV)ubjÛ)”}”(hXactive-backup: There is not much advantage in this network topology to the active-backup mode, as the inactive backup devices are all connected to the same peer as the primary. In this case, a load balancing mode (with link monitoring) will provide the same level of network availability, but with increased available bandwidth. On the plus side, active-backup mode does not require any configuration of the switch, so it may have value if the hardware available does not support any of the load balance modes. ”h]”(já)”}”(hŒactive-backup:”h]”hŒactive-backup:”…””}”(hjÒ)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´Mœ hjÎ)ubjñ)”}”(hhh]”hÞ)”}”(hXñThere is not much advantage in this network topology to the active-backup mode, as the inactive backup devices are all connected to the same peer as the primary. In this case, a load balancing mode (with link monitoring) will provide the same level of network availability, but with increased available bandwidth. On the plus side, active-backup mode does not require any configuration of the switch, so it may have value if the hardware available does not support any of the load balance modes.”h]”hXñThere is not much advantage in this network topology to the active-backup mode, as the inactive backup devices are all connected to the same peer as the primary. In this case, a load balancing mode (with link monitoring) will provide the same level of network availability, but with increased available bandwidth. On the plus side, active-backup mode does not require any configuration of the switch, so it may have value if the hardware available does not support any of the load balance modes.”…””}”(hjã)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M” hjà)ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhjÎ)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´Mœ hjV)h²hubjÛ)”}”(hXCbalance-xor: This mode will limit traffic such that packets destined for specific peers will always be sent over the same interface. Since the destination is determined by the MAC addresses involved, this mode works best in a "local" network configuration (as described above), with destinations all on the same local network. This mode is likely to be suboptimal if all your traffic is passed through a single router (i.e., a "gatewayed" network configuration, as described above). As with balance-rr, the switch ports need to be configured for "etherchannel" or "trunking." ”h]”(já)”}”(hŒbalance-xor:”h]”hŒbalance-xor:”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M© hjý)ubjñ)”}”(hhh]”(hÞ)”}”(hX×This mode will limit traffic such that packets destined for specific peers will always be sent over the same interface. Since the destination is determined by the MAC addresses involved, this mode works best in a "local" network configuration (as described above), with destinations all on the same local network. This mode is likely to be suboptimal if all your traffic is passed through a single router (i.e., a "gatewayed" network configuration, as described above).”h]”hXßThis mode will limit traffic such that packets destined for specific peers will always be sent over the same interface. Since the destination is determined by the MAC addresses involved, this mode works best in a â€œlocalâ€ network configuration (as described above), with destinations all on the same local network. This mode is likely to be suboptimal if all your traffic is passed through a single router (i.e., a â€œgatewayedâ€ network configuration, as described above).”…””}”(hj*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŸ hj*ubhÞ)”}”(hŒ\As with balance-rr, the switch ports need to be configured for "etherchannel" or "trunking."”h]”hŒdAs with balance-rr, the switch ports need to be configured for â€œetherchannelâ€ or â€œtrunking.â€”…””}”(hj *h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¨ hj*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhjý)ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M© hjV)h²hubjÛ)”}”(hŒjbroadcast: Like active-backup, there is not much advantage to this mode in this type of network topology. ”h]”(já)”}”(hŒ broadcast:”h]”hŒ broadcast:”…””}”(hj>*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´M hj:*ubjñ)”}”(hhh]”hÞ)”}”(hŒ^Like active-backup, there is not much advantage to this mode in this type of network topology.”h]”hŒ^Like active-backup, there is not much advantage to this mode in this type of network topology.”…””}”(hjO*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¬ hjL*ubah}”(h]”h ]”h"]”h$]”h&]”uh1jðhj:*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´M hjV)h²hubjÛ)”}”(hXš802.3ad: This mode can be a good choice for this type of network topology. The 802.3ad mode is an IEEE standard, so all peers that implement 802.3ad should interoperate well. The 802.3ad protocol includes automatic configuration of the aggregates, so minimal manual configuration of the switch is needed (typically only to designate that some set of devices is available for 802.3ad). The 802.3ad standard also mandates that frames be delivered in order (within certain limits), so in general single connections will not see misordering of packets. The 802.3ad mode does have some drawbacks: the standard mandates that all devices in the aggregate operate at the same speed and duplex. Also, as with all bonding load balance modes other than balance-rr, no single connection will be able to utilize more than a single interface's worth of bandwidth. Additionally, the linux bonding 802.3ad implementation distributes traffic by peer (using an XOR of MAC addresses and packet type ID), so in a "gatewayed" configuration, all outgoing traffic will generally use the same device. Incoming traffic may also end up on a single device, but that is dependent upon the balancing policy of the peer's 802.3ad implementation. In a "local" configuration, traffic will be distributed across the devices in the bond. Finally, the 802.3ad mode mandates the use of the MII monitor, therefore, the ARP monitor is not available in this mode. ”h]”(já)”}”(hŒ802.3ad:”h]”hŒ802.3ad:”…””}”(hjm*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´MÊ hji*ubjñ)”}”(hhh]”(hÞ)”}”(hXMThis mode can be a good choice for this type of network topology. The 802.3ad mode is an IEEE standard, so all peers that implement 802.3ad should interoperate well. The 802.3ad protocol includes automatic configuration of the aggregates, so minimal manual configuration of the switch is needed (typically only to designate that some set of devices is available for 802.3ad). The 802.3ad standard also mandates that frames be delivered in order (within certain limits), so in general single connections will not see misordering of packets. The 802.3ad mode does have some drawbacks: the standard mandates that all devices in the aggregate operate at the same speed and duplex. Also, as with all bonding load balance modes other than balance-rr, no single connection will be able to utilize more than a single interface's worth of bandwidth.”h]”hXOThis mode can be a good choice for this type of network topology. The 802.3ad mode is an IEEE standard, so all peers that implement 802.3ad should interoperate well. The 802.3ad protocol includes automatic configuration of the aggregates, so minimal manual configuration of the switch is needed (typically only to designate that some set of devices is available for 802.3ad). The 802.3ad standard also mandates that frames be delivered in order (within certain limits), so in general single connections will not see misordering of packets. The 802.3ad mode does have some drawbacks: the standard mandates that all devices in the aggregate operate at the same speed and duplex. Also, as with all bonding load balance modes other than balance-rr, no single connection will be able to utilize more than a single interfaceâ€™s worth of bandwidth.”…””}”(hj~*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M° hj{*ubhÞ)”}”(hXÇAdditionally, the linux bonding 802.3ad implementation distributes traffic by peer (using an XOR of MAC addresses and packet type ID), so in a "gatewayed" configuration, all outgoing traffic will generally use the same device. Incoming traffic may also end up on a single device, but that is dependent upon the balancing policy of the peer's 802.3ad implementation. In a "local" configuration, traffic will be distributed across the devices in the bond.”h]”hXÑAdditionally, the linux bonding 802.3ad implementation distributes traffic by peer (using an XOR of MAC addresses and packet type ID), so in a â€œgatewayedâ€ configuration, all outgoing traffic will generally use the same device. Incoming traffic may also end up on a single device, but that is dependent upon the balancing policy of the peerâ€™s 802.3ad implementation. In a â€œlocalâ€ configuration, traffic will be distributed across the devices in the bond.”…””}”(hjŒ*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÀ hj{*ubhÞ)”}”(hŒxFinally, the 802.3ad mode mandates the use of the MII monitor, therefore, the ARP monitor is not available in this mode.”h]”hŒxFinally, the 802.3ad mode mandates the use of the MII monitor, therefore, the ARP monitor is not available in this mode.”…””}”(hjš*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÉ hj{*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhji*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´MÊ hjV)h²hubjÛ)”}”(hXubalance-tlb: The balance-tlb mode balances outgoing traffic by peer. Since the balancing is done according to MAC address, in a "gatewayed" configuration (as described above), this mode will send all traffic across a single device. However, in a "local" network configuration, this mode balances multiple local network peers across devices in a vaguely intelligent manner (not a simple XOR as in balance-xor or 802.3ad mode), so that mathematically unlucky MAC addresses (i.e., ones that XOR to the same value) will not all "bunch up" on a single interface. Unlike 802.3ad, interfaces may be of differing speeds, and no special switch configuration is required. On the down side, in this mode all incoming traffic arrives over a single interface, this mode requires certain ethtool support in the network device driver of the slave interfaces, and the ARP monitor is not available. ”h]”(já)”}”(hŒbalance-tlb:”h]”hŒbalance-tlb:”…””}”(hj¸*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´MÝ hj´*ubjñ)”}”(hhh]”(hÞ)”}”(hX!The balance-tlb mode balances outgoing traffic by peer. Since the balancing is done according to MAC address, in a "gatewayed" configuration (as described above), this mode will send all traffic across a single device. However, in a "local" network configuration, this mode balances multiple local network peers across devices in a vaguely intelligent manner (not a simple XOR as in balance-xor or 802.3ad mode), so that mathematically unlucky MAC addresses (i.e., ones that XOR to the same value) will not all "bunch up" on a single interface.”h]”hX-The balance-tlb mode balances outgoing traffic by peer. Since the balancing is done according to MAC address, in a â€œgatewayedâ€ configuration (as described above), this mode will send all traffic across a single device. However, in a â€œlocalâ€ network configuration, this mode balances multiple local network peers across devices in a vaguely intelligent manner (not a simple XOR as in balance-xor or 802.3ad mode), so that mathematically unlucky MAC addresses (i.e., ones that XOR to the same value) will not all â€œbunch upâ€ on a single interface.”…””}”(hjÉ*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÍ hjÆ*ubhÞ)”}”(hXDUnlike 802.3ad, interfaces may be of differing speeds, and no special switch configuration is required. On the down side, in this mode all incoming traffic arrives over a single interface, this mode requires certain ethtool support in the network device driver of the slave interfaces, and the ARP monitor is not available.”h]”hXDUnlike 802.3ad, interfaces may be of differing speeds, and no special switch configuration is required. On the down side, in this mode all incoming traffic arrives over a single interface, this mode requires certain ethtool support in the network device driver of the slave interfaces, and the ARP monitor is not available.”…””}”(hj×*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MØ hjÆ*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhj´*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´MÝ hjV)h²hubjÛ)”}”(hX’balance-alb: This mode is everything that balance-tlb is, and more. It has all of the features (and restrictions) of balance-tlb, and will also balance incoming traffic from local network peers (as described in the Bonding Module Options section, above). The only additional down side to this mode is that the network device driver must support changing the hardware address while the device is open. ”h]”(já)”}”(hŒbalance-alb:”h]”hŒbalance-alb:”…””}”(hjõ*h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jàh³hÇh´Mè hjñ*ubjñ)”}”(hhh]”(hÞ)”}”(hŒñThis mode is everything that balance-tlb is, and more. It has all of the features (and restrictions) of balance-tlb, and will also balance incoming traffic from local network peers (as described in the Bonding Module Options section, above).”h]”hŒñThis mode is everything that balance-tlb is, and more. It has all of the features (and restrictions) of balance-tlb, and will also balance incoming traffic from local network peers (as described in the Bonding Module Options section, above).”…””}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mà hj+ubhÞ)”}”(hŒ‘The only additional down side to this mode is that the network device driver must support changing the hardware address while the device is open.”h]”hŒ‘The only additional down side to this mode is that the network device driver must support changing the hardware address while the device is open.”…””•ÐÃ}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mæ hj+ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jðhjñ*ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÚh³hÇh´Mè hjV)h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÕhj7)h²hh³hÇh´Nubeh}”(h]”Œ4mt-bonding-mode-selection-for-single-switch-topology”ah ]”h"]”Œ;12.1.1 mt bonding mode selection for single switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´Mf ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ412.1.2 MT Link Monitoring for Single Switch Topology”h]”hŒ412.1.2 MT Link Monitoring for Single Switch Topology”…””}”(hj?+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj<+h²hh³hÇh´Më ubhÞ)”}”(hX,The choice of link monitoring may largely depend upon which mode you choose to use. The more advanced load balancing modes do not support the use of the ARP monitor, and are thus restricted to using the MII monitor (which does not provide as high a level of end to end assurance as the ARP monitor).”h]”hX,The choice of link monitoring may largely depend upon which mode you choose to use. The more advanced load balancing modes do not support the use of the ARP monitor, and are thus restricted to using the MII monitor (which does not provide as high a level of end to end assurance as the ARP monitor).”…””}”(hjM+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mí hj<+h²hubeh}”(h]”Œ-mt-link-monitoring-for-single-switch-topology”ah ]”h"]”Œ412.1.2 mt link monitoring for single switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´Më ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ512.2 Maximum Throughput in a Multiple Switch Topology”h]”hŒ512.2 Maximum Throughput in a Multiple Switch Topology”…””}”(hjf+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjc+h²hh³hÇh´Mô ubhÞ)”}”(hŒ«Multiple switches may be utilized to optimize for throughput when they are configured in parallel as part of an isolated network between two or more systems, for example::”h]”hŒªMultiple switches may be utilized to optimize for throughput when they are configured in parallel as part of an isolated network between two or more systems, for example:”…””}”(hjt+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mö hjc+h²hubj~)”}”(hXæ +-----------+ | Host A | +-+---+---+-+ | | | +--------+ | +---------+ | | | +------+---+ +-----+----+ +-----+----+ | Switch A | | Switch B | | Switch C | +------+---+ +-----+----+ +-----+----+ | | | +--------+ | +---------+ | | | +-+---+---+-+ | Host B | +-----------+”h]”hXæ +-----------+ | Host A | +-+---+---+-+ | | | +--------+ | +---------+ | | | +------+---+ +-----+----+ +-----+----+ | Switch A | | Switch B | | Switch C | +------+---+ +-----+----+ +-----+----+ | | | +--------+ | +---------+ | | | +-+---+---+-+ | Host B | +-----------+”…””}”hj‚+sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mú hjc+h²hubhÞ)”}”(hX¨In this configuration, the switches are isolated from one another. One reason to employ a topology such as this is for an isolated network with many hosts (a cluster configured for high performance, for example), using multiple smaller switches can be more cost effective than a single larger switch, e.g., on a network with 24 hosts, three 24 port switches can be significantly less expensive than a single 72 port switch.”h]”hX¨In this configuration, the switches are isolated from one another. One reason to employ a topology such as this is for an isolated network with many hosts (a cluster configured for high performance, for example), using multiple smaller switches can be more cost effective than a single larger switch, e.g., on a network with 24 hosts, three 24 port switches can be significantly less expensive than a single 72 port switch.”…””}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjc+h²hubhÞ)”}”(hŒ¿If access beyond the network is required, an individual host can be equipped with an additional network device connected to an external network; this host then additionally acts as a gateway.”h]”hŒ¿If access beyond the network is required, an individual host can be equipped with an additional network device connected to an external network; this host then additionally acts as a gateway.”…””}”(hjž+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjc+h²hubeh}”(h]”Œ0maximum-throughput-in-a-multiple-switch-topology”ah ]”h"]”Œ512.2 maximum throughput in a multiple switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´Mô ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ=12.2.1 MT Bonding Mode Selection for Multiple Switch Topology”h]”hŒ=12.2.1 MT Bonding Mode Selection for Multiple Switch Topology”…””}”(hj·+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj´+h²hh³hÇh´M ubhÞ)”}”(hX@In actual practice, the bonding mode typically employed in configurations of this type is balance-rr. Historically, in this network configuration, the usual caveats about out of order packet delivery are mitigated by the use of network adapters that do not do any kind of packet coalescing (via the use of NAPI, or because the device itself does not generate interrupts until some number of packets has arrived). When employed in this fashion, the balance-rr mode allows individual connections between two hosts to effectively utilize greater than one interface's bandwidth.”h]”hXBIn actual practice, the bonding mode typically employed in configurations of this type is balance-rr. Historically, in this network configuration, the usual caveats about out of order packet delivery are mitigated by the use of network adapters that do not do any kind of packet coalescing (via the use of NAPI, or because the device itself does not generate interrupts until some number of packets has arrived). When employed in this fashion, the balance-rr mode allows individual connections between two hosts to effectively utilize greater than one interfaceâ€™s bandwidth.”…””}”(hjÅ+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hj´+h²hubeh}”(h]”Œ6mt-bonding-mode-selection-for-multiple-switch-topology”ah ]”h"]”Œ=12.2.1 mt bonding mode selection for multiple switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ612.2.2 MT Link Monitoring for Multiple Switch Topology”h]”hŒ612.2.2 MT Link Monitoring for Multiple Switch Topology”…””}”(hjÞ+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÛ+h²hh³hÇh´M$ ubhÞ)”}”(hX}Again, in actual practice, the MII monitor is most often used in this configuration, as performance is given preference over availability. The ARP monitor will function in this topology, but its advantages over the MII monitor are mitigated by the volume of probes needed as the number of systems involved grows (remember that each host in the network is configured with bonding).”h]”hX}Again, in actual practice, the MII monitor is most often used in this configuration, as performance is given preference over availability. The ARP monitor will function in this topology, but its advantages over the MII monitor are mitigated by the volume of probes needed as the number of systems involved grows (remember that each host in the network is configured with bonding).”…””}”(hjì+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M& hjÛ+h²hubeh}”(h]”Œ/mt-link-monitoring-for-multiple-switch-topology”ah ]”h"]”Œ612.2.2 mt link monitoring for multiple switch topology”ah$]”h&]”uh1hÈhje(h²hh³hÇh´M$ ubeh}”(h]”Œ*configuring-bonding-for-maximum-throughput”ah ]”h"]”Œ.12. configuring bonding for maximum throughput”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ13. Switch Behavior Issues”h]”hŒ13. Switch Behavior Issues”…””}”(hj ,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj ,h²hh³hÇh´M. ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ+13.1 Link Establishment and Failover Delays”h]”hŒ+13.1 Link Establishment and Failover Delays”…””}”(hj,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj,h²hh³hÇh´M1 ubhÞ)”}”(hŒqSome switches exhibit undesirable behavior with regard to the timing of link up and down reporting by the switch.”h]”hŒqSome switches exhibit undesirable behavior with regard to the timing of link up and down reporting by the switch.”…””}”(hj,,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M3 hj,h²hubhÞ)”}”(hXçFirst, when a link comes up, some switches may indicate that the link is up (carrier available), but not pass traffic over the interface for some period of time. This delay is typically due to some type of autonegotiation or routing protocol, but may also occur during switch initialization (e.g., during recovery after a switch failure). If you find this to be a problem, specify an appropriate value to the updelay bonding module option to delay the use of the relevant interface(s).”h]”hXçFirst, when a link comes up, some switches may indicate that the link is up (carrier available), but not pass traffic over the interface for some period of time. This delay is typically due to some type of autonegotiation or routing protocol, but may also occur during switch initialization (e.g., during recovery after a switch failure). If you find this to be a problem, specify an appropriate value to the updelay bonding module option to delay the use of the relevant interface(s).”…””}”(hj:,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6 hj,h²hubhÞ)”}”(hŒÏSecond, some switches may "bounce" the link state one or more times while a link is changing state. This occurs most commonly while the switch is initializing. Again, an appropriate updelay value may help.”h]”hŒÓSecond, some switches may â€œbounceâ€ the link state one or more times while a link is changing state. This occurs most commonly while the switch is initializing. Again, an appropriate updelay value may help.”…””}”(hjH,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M? hj,h²hubhÞ)”}”(hX,Note that when a bonding interface has no active links, the driver will immediately reuse the first link that goes up, even if the updelay parameter has been specified (the updelay is ignored in this case). If there are slave interfaces waiting for the updelay timeout to expire, the interface that first went into that state will be immediately reused. This reduces down time of the network if the value of updelay has been overestimated, and since this occurs only in cases with no connectivity, there is no additional penalty for ignoring the updelay.”h]”hX,Note that when a bonding interface has no active links, the driver will immediately reuse the first link that goes up, even if the updelay parameter has been specified (the updelay is ignored in this case). If there are slave interfaces waiting for the updelay timeout to expire, the interface that first went into that state will be immediately reused. This reduces down time of the network if the value of updelay has been overestimated, and since this occurs only in cases with no connectivity, there is no additional penalty for ignoring the updelay.”…””}”(hjV,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MD hj,h²hubhÞ)”}”(hXIn addition to the concerns about switch timings, if your switches take a long time to go into backup mode, it may be desirable to not activate a backup interface immediately after a link goes down. Failover may be delayed via the downdelay bonding module option.”h]”hXIn addition to the concerns about switch timings, if your switches take a long time to go into backup mode, it may be desirable to not activate a backup interface immediately after a link goes down. Failover may be delayed via the downdelay bonding module option.”…””}”(hjd,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MN hj,h²hubeh}”(h]”Œ&link-establishment-and-failover-delays”ah ]”h"]”Œ+13.1 link establishment and failover delays”ah$]”h&]”uh1hÈhj ,h²hh³hÇh´M1 ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ 13.2 Duplicated Incoming Packets”h]”hŒ 13.2 Duplicated Incoming Packets”…””}”(hj},h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjz,h²hh³hÇh´MT ubhÞ)”}”(hŒ¼NOTE: Starting with version 3.0.2, the bonding driver has logic to suppress duplicate packets, which should largely eliminate this problem. The following description is kept for reference.”h]”hŒ¼NOTE: Starting with version 3.0.2, the bonding driver has logic to suppress duplicate packets, which should largely eliminate this problem. The following description is kept for reference.”…””}”(hj‹,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MV hjz,h²hubhÞ)”}”(hXCIt is not uncommon to observe a short burst of duplicated traffic when the bonding device is first used, or after it has been idle for some period of time. This is most easily observed by issuing a "ping" to some other host on the network, and noticing that the output from ping flags duplicates (typically one per slave).”h]”hXGIt is not uncommon to observe a short burst of duplicated traffic when the bonding device is first used, or after it has been idle for some period of time. This is most easily observed by issuing a â€œpingâ€ to some other host on the network, and noticing that the output from ping flags duplicates (typically one per slave).”…””}”(hj™,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MZ hjz,h²hubhÞ)”}”(hŒ}For example, on a bond in active-backup mode with five slaves all connected to one switch, the output may appear as follows::”h]”hŒ|For example, on a bond in active-backup mode with five slaves all connected to one switch, the output may appear as follows:”…””}”(hj§,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M` hjz,h²hubj~)”}”(hX)# ping -n 10.0.4.2 PING 10.0.4.2 (10.0.4.2) from 10.0.3.10 : 56(84) bytes of data. 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms”h]”hX)# ping -n 10.0.4.2 PING 10.0.4.2 (10.0.4.2) from 10.0.3.10 : 56(84) bytes of data. 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!) 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms”…””}”hjµ,sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j}h³hÇh´Mc hjz,h²hubhÞ)”}”(hX1This is not due to an error in the bonding driver, rather, it is a side effect of how many switches update their MAC forwarding tables. Initially, the switch does not associate the MAC address in the packet with a particular switch port, and so it may send the traffic to all ports until its MAC forwarding table is updated. Since the interfaces attached to the bond may occupy multiple ports on a single switch, when the switch (temporarily) floods the traffic to all ports, the bond device receives multiple copies of the same packet (one per slave device).”h]”hX1This is not due to an error in the bonding driver, rather, it is a side effect of how many switches update their MAC forwarding tables. Initially, the switch does not associate the MAC address in the packet with a particular switch port, and so it may send the traffic to all ports until its MAC forwarding table is updated. Since the interfaces attached to the bond may occupy multiple ports on a single switch, when the switch (temporarily) floods the traffic to all ports, the bond device receives multiple copies of the same packet (one per slave device).”…””}”(hjÃ,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mn hjz,h²hubhÞ)”}”(hX)The duplicated packet behavior is switch dependent, some switches exhibit this, and some do not. On switches that display this behavior, it can be induced by clearing the MAC forwarding table (on most Cisco switches, the privileged command "clear mac address-table dynamic" will accomplish this).”h]”hX-The duplicated packet behavior is switch dependent, some switches exhibit this, and some do not. On switches that display this behavior, it can be induced by clearing the MAC forwarding table (on most Cisco switches, the privileged command â€œclear mac address-table dynamicâ€ will accomplish this).”…””}”(hjÑ,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mx hjz,h²hubeh}”(h]”Œduplicated-incoming-packets”ah ]”h"]”Œ 13.2 duplicated incoming packets”ah$]”h&]”uh1hÈhj ,h²hh³hÇh´MT ubeh}”(h]”Œswitch-behavior-issues”ah ]”h"]”Œ13. switch behavior issues”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M. ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ$14. Hardware Specific Considerations”h]”hŒ$14. Hardware Specific Considerations”…””}”(hjò,h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjï,h²hh³hÇh´M ubhÞ)”}”(hŒªThis section contains additional information for configuring bonding on specific hardware platforms, or for interfacing bonding with particular switches or other devices.”h]”hŒªThis section contains additional information for configuring bonding on specific hardware platforms, or for interfacing bonding with particular switches or other devices.”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M hjï,h²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒ14.1 IBM BladeCenter”h]”hŒ14.1 IBM BladeCenter”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj-h²hh³hÇh´M† ubhÞ)”}”(hŒ-This applies to the JS20 and similar systems.”h]”hŒ-This applies to the JS20 and similar systems.”…””}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mˆ hj-h²hubhÞ)”}”(hŒÇOn the JS20 blades, the bonding driver supports only balance-rr, active-backup, balance-tlb and balance-alb modes. This is largely due to the network topology inside the BladeCenter, detailed below.”h]”hŒÇOn the JS20 blades, the bonding driver supports only balance-rr, active-backup, balance-tlb and balance-alb modes. This is largely due to the network topology inside the BladeCenter, detailed below.”…””}”(hj--h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŠ hj-h²hubeh}”(h]”Œibm-bladecenter”ah ]”h"]”Œ14.1 ibm bladecenter”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´M† ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ JS20 network adapter information”h]”hŒ JS20 network adapter information”…””}”(hjF-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjC-h²hh³hÇh´M ubhÞ)”}”(hX¾All JS20s come with two Broadcom Gigabit Ethernet ports integrated on the planar (that's "motherboard" in IBM-speak). In the BladeCenter chassis, the eth0 port of all JS20 blades is hard wired to I/O Module #1; similarly, all eth1 ports are wired to I/O Module #2. An add-on Broadcom daughter card can be installed on a JS20 to provide two more Gigabit Ethernet ports. These ports, eth2 and eth3, are wired to I/O Modules 3 and 4, respectively.”h]”hXÄAll JS20s come with two Broadcom Gigabit Ethernet ports integrated on the planar (thatâ€™s â€œmotherboardâ€ in IBM-speak). In the BladeCenter chassis, the eth0 port of all JS20 blades is hard wired to I/O Module #1; similarly, all eth1 ports are wired to I/O Module #2. An add-on Broadcom daughter card can be installed on a JS20 to provide two more Gigabit Ethernet ports. These ports, eth2 and eth3, are wired to I/O Modules 3 and 4, respectively.”…””}”(hjT-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M’ hjC-h²hubhÞ)”}”(hXEach I/O Module may contain either a switch or a passthrough module (which allows ports to be directly connected to an external switch). Some bonding modes require a specific BladeCenter internal network topology in order to function; these are detailed below.”h]”hXEach I/O Module may contain either a switch or a passthrough module (which allows ports to be directly connected to an external switch). Some bonding modes require a specific BladeCenter internal network topology in order to function; these are detailed below.”…””}”(hjb-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mš hjC-h²hubhÞ)”}”(hŒoAdditional BladeCenter-specific networking information can be found in two IBM Redbooks (www.ibm.com/redbooks):”h]”hŒoAdditional BladeCenter-specific networking information can be found in two IBM Redbooks (www.ibm.com/redbooks):”…””}”(hjp-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MŸ hjC-h²hubj)”}”(hhh]”(j)”}”(hŒ,"IBM eServer BladeCenter Networking Options"”h]”hÞ)”}”(hjƒ-h]”hŒ0â€œIBM eServer BladeCenter Networking Optionsâ€”…””}”(hj…-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¢ hj-ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj~-h²hh³hÇh´Nubj)”}”(hŒ6"IBM eServer BladeCenter Layer 2-7 Network Switching" ”h]”hÞ)”}”(hŒ5"IBM eServer BladeCenter Layer 2-7 Network Switching"”h]”hŒ9â€œIBM eServer BladeCenter Layer 2-7 Network Switchingâ€”…””}”(hjœ-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M£ hj˜-ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj~-h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jj‘uh1jh³hÇh´M¢ hjC-h²hubeh}”(h]”Œ js20-network-adapter-information”ah ]”h"]”Œ js20 network adapter information”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ$BladeCenter networking configuration”h]”hŒ$BladeCenter networking configuration”…””}”(hjÁ-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj¾-h²hh³hÇh´M¦ ubhÞ)”}”(hŒŒBecause a BladeCenter can be configured in a very large number of ways, this discussion will be confined to describing basic configurations.”h]”hŒŒBecause a BladeCenter can be configured in a very large number of ways, this discussion will be confined to describing basic configurations.”…””}”(hjÏ-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¨ hj¾-h²hubhÞ)”}”(hŒÕNormally, Ethernet Switch Modules (ESMs) are used in I/O modules 1 and 2. In this configuration, the eth0 and eth1 ports of a JS20 will be connected to different internal switches (in the respective I/O modules).”h]”hŒÕNormally, Ethernet Switch Modules (ESMs) are used in I/O modules 1 and 2. In this configuration, the eth0 and eth1 ports of a JS20 will be connected to different internal switches (in the respective I/O modules).”…””}”(hjÝ-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¬ hj¾-h²hubhÞ)”}”(hX A passthrough module (OPM or CPM, optical or copper, passthrough module) connects the I/O module directly to an external switch. By using PMs in I/O module #1 and #2, the eth0 and eth1 interfaces of a JS20 can be redirected to the outside world and connected to a common external switch.”h]”hX A passthrough module (OPM or CPM, optical or copper, passthrough module) connects the I/O module directly to an external switch. By using PMs in I/O module #1 and #2, the eth0 and eth1 interfaces of a JS20 can be redirected to the outside world and connected to a common external switch.”…””}”(hjë-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M± hj¾-h²hubhÞ)”}”(hX]Depending upon the mix of ESMs and PMs, the network will appear to bonding as either a single switch topology (all PMs) or as a multiple switch topology (one or more ESMs, zero or more PMs). It is also possible to connect ESMs together, resulting in a configuration much like the example in "High Availability in a Multiple Switch Topology," above.”h]”hXaDepending upon the mix of ESMs and PMs, the network will appear to bonding as either a single switch topology (all PMs) or as a multiple switch topology (one or more ESMs, zero or more PMs). It is also possible to connect ESMs together, resulting in a configuration much like the example in â€œHigh Availability in a Multiple Switch Topology,â€ above.”…””}”(hjù-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M· hj¾-h²hubeh}”(h]”Œ$bladecenter-networking-configuration”ah ]”h"]”Œ$bladecenter networking configuration”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´M¦ ubhÉ)”}”(hhh]”(hÎ)”}”(hŒRequirements for specific modes”h]”hŒRequirements for specific modes”…””}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj.h²hh³hÇh´M¿ ubhÞ)”}”(hŒöThe balance-rr mode requires the use of passthrough modules for devices in the bond, all connected to an common external switch. That switch must be configured for "etherchannel" or "trunking" on the appropriate ports, as is usual for balance-rr.”h]”hŒþThe balance-rr mode requires the use of passthrough modules for devices in the bond, all connected to an common external switch. That switch must be configured for â€œetherchannelâ€ or â€œtrunkingâ€ on the appropriate ports, as is usual for balance-rr.”…””}”(hj .h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÁ hj.h²hubhÞ)”}”(hXXThe balance-alb and balance-tlb modes will function with either switch modules or passthrough modules (or a mix). The only specific requirement for these modes is that all network interfaces must be able to reach all destinations for traffic sent over the bonding device (i.e., the network must converge at some point outside the BladeCenter).”h]”hXXThe balance-alb and balance-tlb modes will function with either switch modules or passthrough modules (or a mix). The only specific requirement for these modes is that all network interfaces must be able to reach all destinations for traffic sent over the bonding device (i.e., the network must converge at some point outside the BladeCenter).”…””}”(hj..h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÆ hj.h²hubhÞ)”}”(hŒ6The active-backup mode has no additional requirements.”h]”hŒ6The active-backup mode has no additional requirements.”…””}”(hj<.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÍ hj.h²hubeh}”(h]”Œrequirements-for-specific-modes”ah ]”h"]”Œrequirements for specific modes”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´M¿ ubhÉ)”}”(hhh]”(hÎ)”}”(hŒLink monitoring issues”h]”hŒLink monitoring issues”…””}”(hjU.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjR.h²hh³hÇh´MÐ ubhÞ)”}”(hXÖWhen an Ethernet Switch Module is in place, only the ARP monitor will reliably detect link loss to an external switch. This is nothing unusual, but examination of the BladeCenter cabinet would suggest that the "external" network ports are the ethernet ports for the system, when it fact there is a switch between these "external" ports and the devices on the JS20 system itself. The MII monitor is only able to detect link failures between the ESM and the JS20 system.”h]”hXÞWhen an Ethernet Switch Module is in place, only the ARP monitor will reliably detect link loss to an external switch. This is nothing unusual, but examination of the BladeCenter cabinet would suggest that the â€œexternalâ€ network ports are the ethernet ports for the system, when it fact there is a switch between these â€œexternalâ€ ports and the devices on the JS20 system itself. The MII monitor is only able to detect link failures between the ESM and the JS20 system.”…””}”(hjc.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÒ hjR.h²hubhÞ)”}”(hŒ˜When a passthrough module is in place, the MII monitor does detect failures to the "external" port, which is then directly connected to the JS20 system.”h]”hŒœWhen a passthrough module is in place, the MII monitor does detect failures to the â€œexternalâ€ port, which is then directly connected to the JS20 system.”…””}”(hjq.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÚ hjR.h²hubeh}”(h]”Œlink-monitoring-issues”ah ]”h"]”Œlink monitoring issues”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´MÐ ubhÉ)”}”(hhh]”(hÎ)”}”(hŒOther concerns”h]”hŒOther concerns”…””}”(hjŠ.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj‡.h²hh³hÇh´Mß ubhÞ)”}”(hXThe Serial Over LAN (SoL) link is established over the primary ethernet (eth0) only, therefore, any loss of link to eth0 will result in losing your SoL connection. It will not fail over with other network traffic, as the SoL system is beyond the control of the bonding driver.”h]”hXThe Serial Over LAN (SoL) link is established over the primary ethernet (eth0) only, therefore, any loss of link to eth0 will result in losing your SoL connection. It will not fail over with other network traffic, as the SoL system is beyond the control of the bonding driver.”…””}”(hj˜.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Má hj‡.h²hubhÞ)”}”(hŒ²It may be desirable to disable spanning tree on the switch (either the internal Ethernet Switch Module, or an external switch) to avoid fail-over delay issues when using bonding.”h]”hŒ²It may be desirable to disable spanning tree on the switch (either the internal Ethernet Switch Module, or an external switch) to avoid fail-over delay issues when using bonding.”…””}”(hj¦.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mç hj‡.h²hubeh}”(h]”Œother-concerns”ah ]”h"]”Œother concerns”ah$]”h&]”uh1hÈhjï,h²hh³hÇh´Mß ubeh}”(h]”Œ hardware-specific-considerations”ah ]”h"]”Œ$14. hardware specific considerations”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ15. Frequently Asked Questions”h]”hŒ15. Frequently Asked Questions”…””}”(hjÇ.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÄ.h²hh³hÇh´Mí ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ1. Is it SMP safe?”h]”hŒ1. Is it SMP safe?”…””}”(hjØ.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÕ.h²hh³hÇh´Mð ubhÞ)”}”(hŒvYes. The old 2.0.xx channel bonding patch was not SMP safe. The new driver was designed to be SMP safe from the start.”h]”hŒvYes. The old 2.0.xx channel bonding patch was not SMP safe. The new driver was designed to be SMP safe from the start.”…””}”(hjæ.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mò hjÕ.h²hubeh}”(h]”Œis-it-smp-safe”ah ]”h"]”Œ1. is it smp safe?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´Mð ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ)2. What type of cards will work with it?”h]”hŒ)2. What type of cards will work with it?”…””}”(hjÿ.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjü.h²hh³hÇh´Mö ubhÞ)”}”(hŒ§Any Ethernet type cards (you can even mix cards - a Intel EtherExpress PRO/100 and a 3com 3c905b, for example). For most modes, devices need not be of the same speed.”h]”hŒ§Any Ethernet type cards (you can even mix cards - a Intel EtherExpress PRO/100 and a 3com 3c905b, for example). For most modes, devices need not be of the same speed.”…””}”(hj /h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mø hjü.h²hubhÞ)”}”(hŒ[Starting with version 3.2.1, bonding also supports Infiniband slaves in active-backup mode.”h]”hŒ[Starting with version 3.2.1, bonding also supports Infiniband slaves in active-backup mode.”…””}”(hj/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mü hjü.h²hubeh}”(h]”Œ$what-type-of-cards-will-work-with-it”ah ]”h"]”Œ(2. what type of cards will work with it?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´Mö ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ(3. How many bonding devices can I have?”h]”hŒ(3. How many bonding devices can I have?”…””}”(hj4/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj1/h²hh³hÇh´MubhÞ)”}”(hŒThere is no limit.”h]”hŒThere is no limit.”…””}”(hjB/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj1/h²hubeh}”(h]”Œ#how-many-bonding-devices-can-i-have”ah ]”h"]”Œ'3. how many bonding devices can i have?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´MubhÉ)”}”(hhh]”(hÎ)”}”(hŒ.4. How many slaves can a bonding device have?”h]”hŒ.4. How many slaves can a bonding device have?”…””}”(hj[/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjX/h²hh³hÇh´MubhÞ)”}”(hŒˆThis is limited only by the number of network interfaces Linux supports and/or the number of network cards you can place in your system.”h]”hŒˆThis is limited only by the number of network interfaces Linux supports and/or the number of network cards you can place in your system.”…””}”(hji/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MhjX/h²hubeh}”(h]”Œ)how-many-slaves-can-a-bonding-device-have”ah ]”h"]”Œ-4. how many slaves can a bonding device have?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´MubhÉ)”}”(hhh]”(hÎ)”}”(hŒ(5. What happens when a slave link dies?”h]”hŒ(5. What happens when a slave link dies?”…””}”(hj‚/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj/h²hh³hÇh´MubhÞ)”}”(hXžIf link monitoring is enabled, then the failing device will be disabled. The active-backup mode will fail over to a backup link, and other modes will ignore the failed link. The link will continue to be monitored, and should it recover, it will rejoin the bond (in whatever manner is appropriate for the mode). See the sections on High Availability and the documentation for each mode for additional information.”h]”hXžIf link monitoring is enabled, then the failing device will be disabled. The active-backup mode will fail over to a backup link, and other modes will ignore the failed link. The link will continue to be monitored, and should it recover, it will rejoin the bond (in whatever manner is appropriate for the mode). See the sections on High Availability and the documentation for each mode for additional information.”…””}”(hj/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj/h²hubhÞ)”}”(hX>Link monitoring can be enabled via either the miimon or arp_interval parameters (described in the module parameters section, above). In general, miimon monitors the carrier state as sensed by the underlying network device, and the arp monitor (arp_interval) monitors connectivity to another host on the local network.”h]”hX>Link monitoring can be enabled via either the miimon or arp_interval parameters (described in the module parameters section, above). In general, miimon monitors the carrier state as sensed by the underlying network device, and the arp monitor (arp_interval) monitors connectivity to another host on the local network.”…””}”(hjž/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj/h²hubhÞ)”}”(hXAIf no link monitoring is configured, the bonding driver will be unable to detect link failures, and will assume that all links are always available. This will likely result in lost packets, and a resulting degradation of performance. The precise performance loss depends upon the bonding mode and network configuration.”h]”hXAIf no link monitoring is configured, the bonding driver will be unable to detect link failures, and will assume that all links are always available. This will likely result in lost packets, and a resulting degradation of performance. The precise performance loss depends upon the bonding mode and network configuration.”…””}”(hj¬/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mhj/h²hubeh}”(h]”Œ#what-happens-when-a-slave-link-dies”ah ]”h"]”Œ'5. what happens when a slave link dies?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´MubhÉ)”}”(hhh]”(hÎ)”}”(hŒ.6. Can bonding be used for High Availability?”h]”hŒ.6. Can bonding be used for High Availability?”…””}”(hjÅ/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjÂ/h²hh³hÇh´M#ubhÞ)”}”(hŒ7Yes. See the section on High Availability for details.”h]”hŒ7Yes. See the section on High Availability for details.”…””}”(hjÓ/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M%hjÂ/h²hubeh}”(h]”Œ)can-bonding-be-used-for-high-availability”ah ]”h"]”Œ-6. can bonding be used for high availability?”ah$]”h&]”uh1hÈhjÄ.h²hh³hÇh´M#ubhÉ)”}”(hhh]”(hÎ)”}”(hŒ-7. Which switches/systems does it work with?”h]”hŒ-7. Which switches/systems does it work with?”…””}”(hjì/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjé/h²hh³hÇh´M(ubhÞ)”}”(hŒ6The full answer to this depends upon the desired mode.”h]”hŒ6The full answer to this depends upon the desired mode.”…””}”(hjú/h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M*hjé/h²hubhÞ)”}”(hŒçIn the basic balance modes (balance-rr and balance-xor), it works with any system that supports etherchannel (also called trunking). Most managed switches currently available have such support, and many unmanaged switches as well.”h]”hŒçIn the basic balance modes (balance-rr and balance-xor), it works with any system that supports etherchannel (also called trunking). Most managed switches currently available have such support, and many unmanaged switches as well.”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M,hjé/h²hubhÞ)”}”(hŒâThe advanced balance modes (balance-tlb and balance-alb) do not have special switch requirements, but do need device drivers that support specific features (described in the appropriate section under module parameters, above).”h]”hŒâThe advanced balance modes (balance-tlb and balance-alb) do not have special switch requirements, but do need device drivers that support specific features (described in the appropriate section under module parameters, above).”…””}”(hj0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M1hjé/h²hubhÞ)”}”(hŒ©In 802.3ad mode, it works with systems that support IEEE 802.3ad Dynamic Link Aggregation. Most managed and many unmanaged switches currently available support 802.3ad.”h]”hŒ©In 802.3ad mode, it works with systems that support IEEE 802.3ad Dynamic Link Aggregation. Most managed and many unmanaged switches currently available support 802.3ad.”…””}”(hj$0h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M6hjé/h²hubhÞ)”}”(hŒ2Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÇŒ_destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j2j2jjjÅjÂj–j“j½jºj#j jS"jP"jŠj‡j±j®jøjõj=j:jrjoj™j–jzjwj?j<j‚jj jj„jj±j®j j je jb jÖ jÓ j—!j”!jK"jH"j#jý"jµ"j²"jø"jõ"jQ#jN#j$jþ#jñ$jî$jU$jR$j´$j±$jé$jæ$j&j&ja%j^%j&j&jw&jt&jä&já&jb(j_(j8'j5'j‰'j†'j(j(jZ(jW(j,j,j4)j1)j9+j6+j`+j]+j±+j®+jØ+jÕ+jÿ+jü+jì,jé,jw,jt,jä,já,jÁ.j¾.j@-j=-j»-j¸-j.j .jO.jL.j„.j.j¹.j¶.j€1j}1jù.jö.j./j+/jU/jR/j|/jy/j¿/j¼/jæ/jã/jE0jB0jà0jÝ0jx1ju1j2j2uŒ nametypes”}”(j2‰j‰jÅ‰j–‰j½‰j#‰jS"‰jŠ‰j±‰jø‰j=‰jr‰j™‰jz‰j?‰j‚‰j ‰j„‰j±‰j ‰je ‰jÖ ‰j—!‰jK"‰j#‰jµ"‰jø"‰jQ#‰j$‰jñ$‰jU$‰j´$‰jé$‰j&‰ja%‰j&‰jw&‰jä&‰jb(‰j8'‰j‰'‰j(‰jZ(‰j,‰j4)‰j9+‰j`+‰j±+‰jØ+‰jÿ+‰jì,‰jw,‰jä,‰jÁ.‰j@-‰j»-‰j.‰jO.‰j„.‰j¹.‰j€1‰jù.‰j./‰jU/‰j|/‰j¿/‰jæ/‰jE0‰jà0‰jx1‰j2‰uh}”(j2hÊjjÑjÂj"j“jAjºj™j jÈjP"j&j‡jÅj®jjõj´j:jûjoj@j–jujwjœj<j}jjBjj…jjj®j‡j j´jb j jÓ jh j”!jÙ jH"jš!jý"jV"j²"jg"jõ"j¸"jN#j#jþ#jT#jî$j$jR$j1$j±$jX$jæ$j·$j&jô$j^%j%j&jd%jt&j&já&jz&j_(jç&j5'j'j†'j;'j(jŒ'jW(j(j,je(j1)jv(j6+j7)j]+j<+j®+jc+jÕ+j´+jü+jÛ+jé,j ,jt,j,já,jz,j¾.jï,j=-j-j¸-jC-j .j¾-jL.j.j.jR.j¶.j‡.j}1jÄ.jö.jÕ.j+/jü.jR/j1/jy/jX/j¼/j/jã/jÂ/jB0jé/jÝ0jH0ju1jã0j2jƒ1uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ decoration”Nh²hub.