Lines Matching refs:network
22 multiple network interfaces into a single logical "bonded" interface.
155 arp_ip_target parameters be specified, otherwise serious network
357 active slave. It is possible that some switch or network
367 Validation is useful in network configurations in which multiple
389 Filtering is useful in network configurations in which significant
455 the network must be updated via gratuitous ARP,
562 externally visible on only one port (network adapter)
823 it may be that your network device driver does not support
848 network peer on the same slave.
870 network peer on the same slave. For non-IP traffic,
885 traffic to a particular network peer to span multiple
970 You can configure bonding using either your distro's network
973 network initialization scripts: initscripts, sysconfig or interfaces.
980 bonding without support from the network initialization scripts (i.e.,
987 First, look for a file called interfaces in /etc/network directory.
997 package that provides your network initialization scripts.
1056 network configuration system will correctly start multiple instances
1074 values with the appropriate values for your network.
1104 specifier for the network device. The interface name is easier to
1108 network device, and will not change unless the device's bus location
1117 # /etc/init.d/network restart
1119 Note that the network control script (/sbin/ifdown) will
1120 remove the bonding module as part of the network shutdown processing,
1125 devices (they do not show bonding interfaces on its list of network
1132 /etc/sysconfig/network/ifcfg.template
1145 sent to the network.
1150 The sysconfig network initialization system is capable of
1167 version 3 or later, Fedora, etc. On these systems, the network
1173 These distros will not automatically load the network adapter
1176 network-script file for all physical adapters that will be members of
1179 /etc/sysconfig/network-scripts
1183 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1197 As with other network devices, these typically start at 0, and go up
1201 Next, create a bond network script. The file name for this
1202 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1217 NETMASK, NETWORK and BROADCAST) to match your network configuration.
1251 Finally run "/etc/rc.d/init.d/network restart" as root. This
1283 This section applies to distros whose network initialization
1307 network configuration (IP address, netmask, etc) with the appropriate
1342 bonding devices with differing options for those systems whose network
1356 sysconfig network initialization scripts handle this automatically; if
1359 network initialization scripts.
1531 This section applies to distros which use /etc/network/interfaces file
1532 to describe network interface configuration, most notably Debian and it's
1538 into /etc/network/interfaces.
1546 In /etc/network/interfaces, the following stanza will configure bond0, in
1558 Ubuntu versions. The following stanza in /etc/network/interfaces will
1577 For a full list of bond-* supported options in /etc/network/interfaces and some
1590 bonded interface in which eth0 connects to a private network, while eth1
1591 connects via a public network, it may be desirous to bias the bond to send said
1745 The network configuration can be inspected using the ifconfig
1876 queries to one or more designated peer systems on the network, and
1879 or more peers on the local network.
1887 shows the ARP requests and replies on the network, then it may be that
1917 network interface. It accomplishes this in one of three ways: by
1961 case, another host on network 10 would use eth0 or eth1 before bond0).
1980 On systems with network configuration scripts that do not
1981 associate physical devices directly with network interface names (so
2053 before any network drivers participating in a bond. This requirement
2075 any network drivers participating in a bond. Below is an example of
2098 When running network monitoring tools, e.g., tcpdump, it is
2126 maximum network availability by having redundant or backup devices,
2128 goal is to provide the maximum availability of network connectivity
2129 (i.e., the network always works), even though other configurations
2150 network changes dramatically. In multiple switch topologies, there is
2151 a trade off between network availability and usable bandwidth.
2153 Below is a sample network, configured to maximize the
2154 availability of the network:
2183 network configuration is such that one switch is specifically
2211 one for each switch in the network). This will insure that,
2232 throughput depends upon the application and network environment. The
2255 some other network before reaching its final destination.
2257 In a gatewayed network configuration, although Host A may
2259 and received via one other peer on the local network, the router.
2264 traffic is destined for the "gateway" itself, not some other network
2269 reach other stations on the same network. An example would be the
2283 on the same local network (Hosts B and C in the above example).
2286 the bonded device will be to the same MAC level peer on the network
2292 This distinction between a gatewayed and a local network
2294 available use the MAC addresses of the local network source and
2324 configuration. Speaking in general terms, higher speed network
2344 active-backup: There is not much advantage in this network topology to
2348 same level of network availability, but with increased
2357 addresses involved, this mode works best in a "local" network
2359 the same local network. This mode is likely to be suboptimal
2361 "gatewayed" network configuration, as described above).
2367 mode in this type of network topology.
2369 802.3ad: This mode can be a good choice for this type of network
2401 "local" network configuration, this mode balances multiple
2402 local network peers across devices in a vaguely intelligent
2412 network device driver of the slave interfaces, and the ARP
2417 and will also balance incoming traffic from local network
2421 The only additional down side to this mode is that the network
2438 when they are configured in parallel as part of an isolated network
2459 isolated network with many hosts (a cluster configured for high
2461 cost effective than a single larger switch, e.g., on a network with 24
2465 If access beyond the network is required, an individual host
2466 can be equipped with an additional network device connected to an
2467 external network; this host then additionally acts as a gateway.
2474 network configuration, the usual caveats about out of order packet
2475 delivery are mitigated by the use of network adapters that do not do
2490 host in the network is configured with bonding).
2520 immediately reused. This reduces down time of the network if the
2540 a "ping" to some other host on the network, and noticing that the
2587 largely due to the network topology inside the BladeCenter, detailed
2590 JS20 network adapter information
2604 network topology in order to function; these are detailed below.
2630 Depending upon the mix of ESMs and PMs, the network will
2647 specific requirement for these modes is that all network interfaces
2649 bonding device (i.e., the network must converge at some point outside
2660 suggest that the "external" network ports are the ethernet ports for
2675 network traffic, as the SoL system is beyond the control of the
2706 This is limited only by the number of network interfaces Linux
2707 supports and/or the number of network cards you can place in your
2723 the underlying network device, and the arp monitor (arp_interval)
2724 monitors connectivity to another host on the local network.
2730 depends upon the bonding mode and network configuration.
2811 on the main Linux network mailing list, hosted at vger.kernel.org. The list
2822 - http://web.archive.org/web/*/http://www.scyld.com/network/