Linux Kernel Documentation : : networking : bonding. Custom Search. Based on kernel version 4. Page generated on 2. EST. 1. 2 Linux Ethernet Bonding Driver HOWTO. Latest update: 2. April 2. 01. 1. 5. Initial release : Thomas Davis < tadavis at lbl. Corrections, HA extensions : 2. Willy Tarreau < willy at meta- x. Constantine Gavrilov < const- g at xpert. Chad N. Tindel < ctindel at ieee dot org>. Janice Girouard < girouard at us dot ibm dot com>. Jay Vosburgh < fubar at us dot ibm dot com>. Reorganized and updated Feb 2. Jay Vosburgh. 1. 5Added Sysfs information: 2. CVE (version 20061101) and Candidates as of 20170922 Candidates must be reviewed and accepted by the CVE Editorial Board before they can be added to the official CVE. 42315 في في في stop_word 39592 من من من stop_word.
Mitch Williams < mitch. Introduction. 2. 02. The Linux bonding driver provides a method for aggregating. The behavior of the bonded interfaces depends upon the mode; generally. Additionally, link integrity monitoring may be performed. The bonding driver originally came from Donald Becker's. It has changed quite a bit since, and. For new versions of the driver, updated userspace tools, and. Table of Contents. Bonding Driver Installation. Bonding Driver Options. Configuring Bonding Devices. Configuration with Sysconfig Support. Using DHCP with Sysconfig. Configuring Multiple Bonds with Sysconfig. Configuration with Initscripts Support. Using DHCP with Initscripts. Configuring Multiple Bonds with Initscripts. Configuring Bonding Manually with Ifenslave. Configuring Multiple Bonds Manually. Configuring Bonding Manually via Sysfs. Configuration with Interfaces Support. Overriding Configuration for Special Cases. Configuring LACP for 8. Querying Bonding Configuration. Bonding Configuration. Network Configuration. Switch Configuration. VLAN Support. 6. 36. Link Monitoring. 6. ARP Monitor Operation. Configuring Multiple ARP Targets. MII Monitor Operation. Potential Trouble Sources. Adventures in Routing. Ethernet Device Renaming. Painfully Slow Or No Failed Link Detection By Miimon. SNMP agents. 7. 57. Promiscuous mode. Configuring Bonding for High Availability. High Availability in a Single Switch Topology. High Availability in a Multiple Switch Topology. HA Bonding Mode Selection for Multiple Switch Topology. HA Link Monitoring for Multiple Switch Topology. Configuring Bonding for Maximum Throughput. Maximum Throughput in a Single Switch Topology. MT Bonding Mode Selection for Single Switch Topology. MT Link Monitoring for Single Switch Topology. Maximum Throughput in a Multiple Switch Topology. MT Bonding Mode Selection for Multiple Switch Topology. MT Link Monitoring for Multiple Switch Topology. Switch Behavior Issues. Link Establishment and Failover Delays. Duplicated Incoming Packets. Hardware Specific Considerations. IBM Blade. Center. Frequently Asked Questions. Resources and Links. Bonding Driver Installation. Most popular distro kernels ship with the bonding driver. If your distro does not, or you. Configure and build the kernel with bonding. The current version of the bonding driver is available in the. Most users "rolling their. Configure kernel with "make menuconfig" (or "make xconfig" or. Bonding driver support" in the "Network. It is recommended that you configure the. Build and install the new kernel and modules. Bonding Control Utility. It is recommended to configure bonding via iproute. Bonding Driver Options. Options for the bonding driver are supplied as parameters to the. Module options may be given as command line arguments to the. Details on bonding support for sysfs is provided in the. Configuring Bonding Manually via Sysfs" section, below. The available bonding driver parameters are listed below. If a. 1. 50parameter is not specified the default value is used. When initially. 1. It is critical that either the miimon or arp_interval and. Very few devices do not. Options with textual values will accept either the text name. E. g.. 1. 61"mode=8. The parameters are as follows. Specifies the new active slave for modes that support it. Possible values. 1. If a name is given, the slave and its link must be up in order. If an empty string is. Note that this is only available through the sysfs interface. No module. 1. 76 parameter by this name exists. The normal value of this option is the name of the currently. In an AD system, this specifies the system priority. The allowed range. If the value is not specified, it takes 6. This parameter has effect only in 8. Sys. Fs interface. In an AD system, this specifies the mac- address for the actor in. LACPDUs). The value cannot be NULL or. It is preferred to have the local- admin bit set for this. If the value is not given then. This parameter has effect only in 8. Sys. Fs interface. Specifies the 8. 02. The. 2. 06 possible values and their effects are. The active aggregator is chosen by largest aggregate. Reselection of the active aggregator occurs only when all. This is the default value. The active aggregator is chosen by largest aggregate. Reselection occurs if. A slave is added to or removed from the bond. Any slave's link state changes. Any slave's 8. 02. The bond's administrative state changes to up. The active aggregator is chosen by the largest number of. Reselection occurs as described under the. The bandwidth and count selection policies permit failover of. This keeps the aggregator with the highest availability. This option was added in bonding version 3. In an AD system, the port- key has three parts as shown below - . Bits Use. 2. 50 0. Duplex. 2. 51 0. Speed. 2. 52 0. User- defined. 2. This defines the upper 1. The values can be. If not given, the system defaults to 0. This parameter has effect only in 8. Sys. Fs interface. Specifies that duplicate frames (received on inactive ports) should be. Normally, bonding will drop duplicate frames (received on inactive. But there are some times. The default value is 0 (drop duplicate frames received on inactive. Specifies the ARP link monitoring frequency in milliseconds. The ARP monitor works by periodically checking the slave. Regular traffic is. ARP probes issued for the addresses specified by. This behavior can be modified by the arp_validate option. If ARP monitoring is used in an etherchannel compatible mode. If the. 2. 89 switch is configured to distribute the packets in an XOR. ARP targets will be received on. ARP monitoring should not be used in conjunction with. A value of 0 disables ARP monitoring. The default. 2. 94 value is 0. Specifies the IP addresses to use as ARP monitoring peers when. These are the targets of the ARP request. Specify these values in ddd. Multiple IP. 3. 02 addresses must be separated by a comma. At least one IP. 3. ARP monitoring to function. The. 3. 04 maximum number of targets that can be specified is 1. The. 3. 05 default value is no IP addresses. Specifies whether or not ARP probes and replies should be. ARP traffic should be filtered (disregarded) for link. Possible values are. No validation or filtering is performed. Validation is performed only for the active slave. Validation is performed only for backup slaves. Validation is performed for all slaves. Filtering is applied to all slaves. No validation is. Filtering is applied to all slaves, validation is performed. Filtering is applied to all slaves, validation is performed. Validation. 3. 48. Enabling validation causes the ARP monitor to examine the incoming. ARP requests and replies, and only consider a slave to be up if it. ARP traffic. 3. 52. For an active slave, the validation checks ARP replies to confirm. Since backup slaves. ARP request sent out via the. It is possible that some switch or network. ARP requests; in such a situation, validation. The validation of ARP requests on backup slaves is mainly helping. Validation is useful in network configurations in which multiple. ARPs to one or more targets. Should the link between the switch and. ARP monitor into considering the links as still up. Use of. 3. 73 validation can resolve this, as the ARP monitor will only consider. ARP requests and replies associated with its own instance of. Filtering. 3. 78. Enabling filtering causes the ARP monitor to only use incoming ARP. Arriving packets that are. ARPs are delivered normally, but do not count when determining. Filtering operates by only considering the reception of ARP. ARP packet, regardless of source or destination) when. Filtering is useful in network configurations in which significant. ARP monitor into considering the links as still up. Use of. 3. 92 filtering can resolve this, as only ARP traffic is considered for. This option was added in bonding version 3. Specifies the quantity of arp_ip_targets that must be reachable. ARP monitor to consider a slave as being up. This option affects only active- backup mode for slaves with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |