This may result in out of order delivery. A single TCP or UDP conversation containing both fragmented and unfragmented packets will see packets striped across two interfaces. This algorithm is not fully 802.3ad compliant. This policy is intended to mimic the behavior of certain switches, notably Cisco switches with PFC2 as well as some Foundry and IBM products. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy. The formula for unfragmented TCP and UDP packets isįor fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. This policy uses upper layer protocol information, when available, to generate the hash. “mode=802.3ad” and “mode=4” set the same mode. Or, for backwards compatibility, the option value. Options with textual values will accept either the text name Support at least miimon, so there is really no reason not to use it. It is critical that either the miimon or arp_interval and arp_ip_target parameters be specified, otherwise serious networkĭegradation will occur during link failures.
CLEARING ALTERNATE MAC ADDRESS DRIVER
Run in a separate window to watch for bonding driver error messages. When initiallyĬonfiguring a bond, it is recommended “tail -f /var/log/messages” be Parameter is not specified the default value is used. The available bonding driver parameters are listed below. In either the /etc/nf or /etc/nf configurationįile, or in a distro-specific configuration file (some of which are They may be given as command lineĪrguments to the insmod or modprobe command, but are usually specified Options for the bonding driver are supplied as parameters to Onwards) do not have /usr/include/linux symbolically linked to the May end up with an ifenslave that is incompatible with the kernel If you omit the “-I” or specify an incorrect directory, you (e.g., name the ifenslave executable /sbin/ifenslave-2.6.10). Testing or informal use, tag the ifenslave to the kernel version You may wish to back up any existing /sbin/ifenslave, or, for “/usr/src/linux/include” in the above with the location of your kernel If your kernel source is not in “/usr/src/linux,” then replace # gcc -Wall -O -I/usr/src/linux/include ifenslave.c -o ifenslave That is newer than the kernel is not supported, and may or may not Than the ifenslave release are not supported). Source tree or supplied with the distro), however, ifenslaveĮxecutables from older kernels should function (but features newer It is generally recommended that you use the ifenslave thatĬorresponds to the kernel that you are using (either from the same Kernel source tree, in the file Documentation/networking/ifenslave.c. The ifenslave user level control program is included in the
0 kommentar(er)
