Lines Matching refs:configuration
142 /etc/modrobe.d/*.conf configuration files, or in a distro-specific
143 configuration file (some of which are detailed in the next section).
582 Most switches will require some type of configuration
976 SuSE SLES 9's networking configuration system does support
977 bonding, however, at this writing, the YaST system configuration
983 yast2 sysconfig configuration utility. The goal is for to create an
987 name of the configuration file for each device will be of the form:
995 created, it is necessary to edit the configuration files for the slave
1015 it's time to create the configuration file for the bonding device
1019 network configuration system will correctly start multiple instances
1053 off or ignore: The device configuration is ignored.
1061 the max_bonds bonding parameter; this will confuse the configuration
1076 When all configuration files have been modified or created,
1077 networking must be restarted for the configuration changes to take
1089 devices). It is necessary to edit the configuration file by hand to
1090 change the bonding configuration.
1123 the system /etc/modules.d/*.conf configuration files.
1180 NETMASK, NETWORK and BROADCAST) to match your network configuration.
1212 options for your configuration.
1270 network configuration (IP address, netmask, etc) with the appropriate
1271 values for your configuration.
1275 configuration, it is necessary to run the initialization script, e.g.,
1284 which only initializes the bonding configuration, then call that
1364 via the sysfs interface. This interface allows dynamic configuration
1495 to describe network interface configuration, most notably Debian and it's
1519 If the above configuration doesn't work, you might have a system using
1594 distributions that allow configuration via initscripts, multiple 'queue_id'
1599 slave devices. For instance, say we wanted, in the above configuration to
1633 about the bonding configuration, options and state of each slave.
1656 bonding configuration, state, and version of the bonding driver.
1658 4.2 Network configuration
1661 The network configuration can be inspected using the ifconfig
1703 require any specific configuration of the switch.
1718 will also have its own configuration options for the switch's transmit
1874 This routing configuration will likely still update the
1880 configuration, because ARP requests (generated by the ARP monitor)
1896 On systems with network configuration scripts that do not
1916 devices, but the bonding configuration tries to enslave eth2 and eth3
1975 with the eth0 interface. This configuration is shown below, the IP
2065 With multiple switches, the configuration of bonding and the
2084 In this configuration, there is a link between the two
2099 network configuration is such that one switch is specifically
2137 miimon. Availability and configuration for trunk failover varies by
2147 In a single switch configuration, the best method to maximize
2156 In a gatewayed configuration, the "switch" is acting primarily
2173 In a gatewayed network configuration, although Host A may
2179 same as a gatewayed configuration. In that case, it happens that all
2183 In a local configuration, the "switch" is acting primarily as
2201 In summary, in a gatewayed configuration, traffic to and from
2204 destination. In a local configuration, traffic flows directly to and
2209 configuration is important because many of the load balancing modes
2218 This configuration is the easiest to set up and to understand,
2240 configuration. Speaking in general terms, higher speed network
2243 higher rate than a "many slow to one fast" configuration.
2266 does not require any configuration of the switch, so it may
2274 configuration (as described above), with destinations all on
2277 "gatewayed" network configuration, as described above).
2288 protocol includes automatic configuration of the aggregates,
2289 so minimal manual configuration of the switch is needed
2303 and packet type ID), so in a "gatewayed" configuration, all
2307 implementation. In a "local" configuration, traffic will be
2315 "gatewayed" configuration (as described above), this mode will
2317 "local" network configuration, this mode balances multiple
2325 special switch configuration is required. On the down side,
2373 In this configuration, the switches are isolated from one
2390 network configuration, the usual caveats about out of order packet
2402 in this configuration, as performance is given preference over
2528 BladeCenter networking configuration
2536 modules 1 and 2. In this configuration, the eth0 and eth1 ports of a
2549 also possible to connect ESMs together, resulting in a configuration
2646 depends upon the bonding mode and network configuration.