Lines Matching refs:configuration
143 /etc/modrobe.d/*.conf configuration files, or in a distro-specific
144 configuration file (some of which are detailed in the next section).
619 Most switches will require some type of configuration
1013 SuSE SLES 9's networking configuration system does support
1014 bonding, however, at this writing, the YaST system configuration
1020 yast2 sysconfig configuration utility. The goal is for to create an
1024 name of the configuration file for each device will be of the form:
1032 created, it is necessary to edit the configuration files for the slave
1052 it's time to create the configuration file for the bonding device
1056 network configuration system will correctly start multiple instances
1090 off or ignore: The device configuration is ignored.
1098 the max_bonds bonding parameter; this will confuse the configuration
1113 When all configuration files have been modified or created,
1114 networking must be restarted for the configuration changes to take
1126 devices). It is necessary to edit the configuration file by hand to
1127 change the bonding configuration.
1160 the system /etc/modules.d/*.conf configuration files.
1217 NETMASK, NETWORK and BROADCAST) to match your network configuration.
1249 options for your configuration.
1307 network configuration (IP address, netmask, etc) with the appropriate
1308 values for your configuration.
1312 configuration, it is necessary to run the initialization script, e.g.,
1321 which only initializes the bonding configuration, then call that
1401 via the sysfs interface. This interface allows dynamic configuration
1532 to describe network interface configuration, most notably Debian and it's
1556 If the above configuration doesn't work, you might have a system using
1631 distributions that allow configuration via initscripts, multiple 'queue_id'
1636 slave devices. For instance, say we wanted, in the above configuration to
1717 about the bonding configuration, options and state of each slave.
1740 bonding configuration, state, and version of the bonding driver.
1742 4.2 Network configuration
1745 The network configuration can be inspected using the ifconfig
1787 require any specific configuration of the switch.
1802 will also have its own configuration options for the switch's transmit
1958 This routing configuration will likely still update the
1964 configuration, because ARP requests (generated by the ARP monitor)
1980 On systems with network configuration scripts that do not
2000 devices, but the bonding configuration tries to enslave eth2 and eth3
2059 with the eth0 interface. This configuration is shown below, the IP
2149 With multiple switches, the configuration of bonding and the
2168 In this configuration, there is a link between the two
2183 network configuration is such that one switch is specifically
2221 miimon. Availability and configuration for trunk failover varies by
2231 In a single switch configuration, the best method to maximize
2240 In a gatewayed configuration, the "switch" is acting primarily
2257 In a gatewayed network configuration, although Host A may
2263 same as a gatewayed configuration. In that case, it happens that all
2267 In a local configuration, the "switch" is acting primarily as
2285 In summary, in a gatewayed configuration, traffic to and from
2288 destination. In a local configuration, traffic flows directly to and
2293 configuration is important because many of the load balancing modes
2302 This configuration is the easiest to set up and to understand,
2324 configuration. Speaking in general terms, higher speed network
2327 higher rate than a "many slow to one fast" configuration.
2350 does not require any configuration of the switch, so it may
2358 configuration (as described above), with destinations all on
2361 "gatewayed" network configuration, as described above).
2372 protocol includes automatic configuration of the aggregates,
2373 so minimal manual configuration of the switch is needed
2387 and packet type ID), so in a "gatewayed" configuration, all
2391 implementation. In a "local" configuration, traffic will be
2399 "gatewayed" configuration (as described above), this mode will
2401 "local" network configuration, this mode balances multiple
2409 special switch configuration is required. On the down side,
2457 In this configuration, the switches are isolated from one
2474 network configuration, the usual caveats about out of order packet
2486 in this configuration, as performance is given preference over
2612 BladeCenter networking configuration
2620 modules 1 and 2. In this configuration, the eth0 and eth1 ports of a
2633 also possible to connect ESMs together, resulting in a configuration
2730 depends upon the bonding mode and network configuration.