Documentation/networking/bonding.rst

148 ``/etc/modprobe.d/*.conf`` configuration files, or in a distro-specific
149 configuration file (some of which are detailed in the next section).
663 		Most switches will require some type of configuration
1093 SuSE SLES 9's networking configuration system does support
1094 bonding, however, at this writing, the YaST system configuration
1100 yast2 sysconfig configuration utility.  The goal is for to create an
1104 name of the configuration file for each device will be of the form::
1112 created, it is necessary to edit the configuration files for the slave
1132 it's time to create the configuration file for the bonding device
1136 network configuration system will correctly start multiple instances
1171 	off or   The device configuration is ignored.
1181 the max_bonds bonding parameter; this will confuse the configuration
1196 When all configuration files have been modified or created,
1197 networking must be restarted for the configuration changes to take
1209 devices).  It is necessary to edit the configuration file by hand to
1210 change the bonding configuration.
1243 the system ``/etc/modules.d/*.conf`` configuration files.
1300 NETMASK, NETWORK and BROADCAST) to match your network configuration.
1333 options for your configuration.
1391 network configuration (IP address, netmask, etc) with the appropriate
1392 values for your configuration.
1396 configuration, it is necessary to run the initialization script, e.g.,::
1405 which only initializes the bonding configuration, then call that
1485 via the sysfs interface.  This interface allows dynamic configuration
1639 to describe network interface configuration, most notably Debian and its
1663 If the above configuration doesn't work, you might have a system using
1738 distributions that allow configuration via initscripts, multiple 'queue_id'
1743 slave devices.  For instance, say we wanted, in the above configuration to
1824 about the bonding configuration, options and state of each slave.
1847 bonding configuration, state, and version of the bonding driver.
1849 4.2 Network configuration
1852 The network configuration can be inspected using the ifconfig
1894 require any specific configuration of the switch.
1909 will also have its own configuration options for the switch's transmit
2056 This routing configuration will likely still update the
2062 configuration, because ARP requests (generated by the ARP monitor)
2078 On systems with network configuration scripts that do not
2098 devices, but the bonding configuration tries to enslave eth2 and eth3
2157 with the eth0 interface.  This configuration is shown below, the IP
2249 With multiple switches, the configuration of bonding and the
2268 In this configuration, there is a link between the two
2284 	network configuration is such that one switch is specifically
2323 miimon.  Availability and configuration for trunk failover varies by
2333 In a single switch configuration, the best method to maximize
2342 In a gatewayed configuration, the "switch" is acting primarily
2359 In a gatewayed network configuration, although Host A may
2365 same as a gatewayed configuration.  In that case, it happens that all
2369 In a local configuration, the "switch" is acting primarily as
2387 In summary, in a gatewayed configuration, traffic to and from
2390 destination.  In a local configuration, traffic flows directly to and
2395 configuration is important because many of the load balancing modes
2404 This configuration is the easiest to set up and to understand,
2427 	configuration.  Speaking in general terms, higher speed network
2430 	higher rate than a "many slow to one fast" configuration.
2454 	does not require any configuration of the switch, so it may
2463 	configuration (as described above), with destinations all on
2466 	"gatewayed" network configuration, as described above).
2479 	protocol includes automatic configuration of the aggregates,
2480 	so minimal manual configuration of the switch is needed
2494 	and packet type ID), so in a "gatewayed" configuration, all
2498 	implementation.  In a "local" configuration, traffic will be
2507 	"gatewayed" configuration (as described above), this mode will
2509 	"local" network configuration, this mode balances multiple
2517 	special switch configuration is required.  On the down side,
2566 In this configuration, the switches are isolated from one
2583 network configuration, the usual caveats about out of order packet
2595 in this configuration, as performance is given preference over
2721 BladeCenter networking configuration
2729 modules 1 and 2.  In this configuration, the eth0 and eth1 ports of a
2742 also possible to connect ESMs together, resulting in a configuration
2844 depends upon the bonding mode and network configuration.