Lines Matching refs:network
22 multiple network interfaces into a single logical "bonded" interface.
154 arp_ip_target parameters be specified, otherwise serious network
320 active slave. It is possible that some switch or network
330 Validation is useful in network configurations in which multiple
352 Filtering is useful in network configurations in which significant
418 the network must be updated via gratuitous ARP,
525 externally visible on only one port (network adapter)
786 it may be that your network device driver does not support
811 network peer on the same slave.
833 network peer on the same slave. For non-IP traffic,
848 traffic to a particular network peer to span multiple
933 You can configure bonding using either your distro's network
936 network initialization scripts: initscripts, sysconfig or interfaces.
943 bonding without support from the network initialization scripts (i.e.,
950 First, look for a file called interfaces in /etc/network directory.
960 package that provides your network initialization scripts.
1019 network configuration system will correctly start multiple instances
1037 values with the appropriate values for your network.
1067 specifier for the network device. The interface name is easier to
1071 network device, and will not change unless the device's bus location
1080 # /etc/init.d/network restart
1082 Note that the network control script (/sbin/ifdown) will
1083 remove the bonding module as part of the network shutdown processing,
1088 devices (they do not show bonding interfaces on its list of network
1095 /etc/sysconfig/network/ifcfg.template
1108 sent to the network.
1113 The sysconfig network initialization system is capable of
1130 version 3 or later, Fedora, etc. On these systems, the network
1136 These distros will not automatically load the network adapter
1139 network-script file for all physical adapters that will be members of
1142 /etc/sysconfig/network-scripts
1146 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1160 As with other network devices, these typically start at 0, and go up
1164 Next, create a bond network script. The file name for this
1165 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1180 NETMASK, NETWORK and BROADCAST) to match your network configuration.
1214 Finally run "/etc/rc.d/init.d/network restart" as root. This
1246 This section applies to distros whose network initialization
1270 network configuration (IP address, netmask, etc) with the appropriate
1305 bonding devices with differing options for those systems whose network
1319 sysconfig network initialization scripts handle this automatically; if
1322 network initialization scripts.
1494 This section applies to distros which use /etc/network/interfaces file
1495 to describe network interface configuration, most notably Debian and it's
1501 into /etc/network/interfaces.
1509 In /etc/network/interfaces, the following stanza will configure bond0, in
1521 Ubuntu versions. The following stanza in /etc/network/interfaces will
1540 For a full list of bond-* supported options in /etc/network/interfaces and some
1553 bonded interface in which eth0 connects to a private network, while eth1
1554 connects via a public network, it may be desirous to bias the bond to send said
1661 The network configuration can be inspected using the ifconfig
1792 queries to one or more designated peer systems on the network, and
1795 or more peers on the local network.
1803 shows the ARP requests and replies on the network, then it may be that
1833 network interface. It accomplishes this in one of three ways: by
1877 case, another host on network 10 would use eth0 or eth1 before bond0).
1896 On systems with network configuration scripts that do not
1897 associate physical devices directly with network interface names (so
1969 before any network drivers participating in a bond. This requirement
1991 any network drivers participating in a bond. Below is an example of
2014 When running network monitoring tools, e.g., tcpdump, it is
2042 maximum network availability by having redundant or backup devices,
2044 goal is to provide the maximum availability of network connectivity
2045 (i.e., the network always works), even though other configurations
2066 network changes dramatically. In multiple switch topologies, there is
2067 a trade off between network availability and usable bandwidth.
2069 Below is a sample network, configured to maximize the
2070 availability of the network:
2099 network configuration is such that one switch is specifically
2127 one for each switch in the network). This will insure that,
2148 throughput depends upon the application and network environment. The
2171 some other network before reaching its final destination.
2173 In a gatewayed network configuration, although Host A may
2175 and received via one other peer on the local network, the router.
2180 traffic is destined for the "gateway" itself, not some other network
2185 reach other stations on the same network. An example would be the
2199 on the same local network (Hosts B and C in the above example).
2202 the bonded device will be to the same MAC level peer on the network
2208 This distinction between a gatewayed and a local network
2210 available use the MAC addresses of the local network source and
2240 configuration. Speaking in general terms, higher speed network
2260 active-backup: There is not much advantage in this network topology to
2264 same level of network availability, but with increased
2273 addresses involved, this mode works best in a "local" network
2275 the same local network. This mode is likely to be suboptimal
2277 "gatewayed" network configuration, as described above).
2283 mode in this type of network topology.
2285 802.3ad: This mode can be a good choice for this type of network
2317 "local" network configuration, this mode balances multiple
2318 local network peers across devices in a vaguely intelligent
2328 network device driver of the slave interfaces, and the ARP
2333 and will also balance incoming traffic from local network
2337 The only additional down side to this mode is that the network
2354 when they are configured in parallel as part of an isolated network
2375 isolated network with many hosts (a cluster configured for high
2377 cost effective than a single larger switch, e.g., on a network with 24
2381 If access beyond the network is required, an individual host
2382 can be equipped with an additional network device connected to an
2383 external network; this host then additionally acts as a gateway.
2390 network configuration, the usual caveats about out of order packet
2391 delivery are mitigated by the use of network adapters that do not do
2406 host in the network is configured with bonding).
2436 immediately reused. This reduces down time of the network if the
2456 a "ping" to some other host on the network, and noticing that the
2503 largely due to the network topology inside the BladeCenter, detailed
2506 JS20 network adapter information
2520 network topology in order to function; these are detailed below.
2546 Depending upon the mix of ESMs and PMs, the network will
2563 specific requirement for these modes is that all network interfaces
2565 bonding device (i.e., the network must converge at some point outside
2576 suggest that the "external" network ports are the ethernet ports for
2591 network traffic, as the SoL system is beyond the control of the
2622 This is limited only by the number of network interfaces Linux
2623 supports and/or the number of network cards you can place in your
2639 the underlying network device, and the arp monitor (arp_interval)
2640 monitors connectivity to another host on the local network.
2646 depends upon the bonding mode and network configuration.
2727 on the main Linux network mailing list, hosted at vger.kernel.org. The list
2738 - http://web.archive.org/web/*/http://www.scyld.com/network/