Lines Matching +full:local +full:- +full:mac +full:- +full:address
1 .. SPDX-License-Identifier: GPL-2.0
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
119 -----------------------------------------------
135 ---------------------------
148 ``/etc/modprobe.d/*.conf`` configuration files, or in a distro-specific
156 configuring a bond, it is recommended "tail -f /var/log/messages" be
173 (active-backup, balance-alb and balance-tlb). Possible values
190 is 1 - 65535. If the value is not specified, it takes 65535 as the
198 In an AD system, this specifies the mac-address for the actor in
200 multicast. It is preferred to have the local-admin bit set for this
201 mac but driver does not enforce it. If the value is not given then
202 system defaults to using the masters' mac address as actors' system
203 address.
229 - A slave is added to or removed from the bond
231 - Any slave's link state changes
233 - Any slave's 802.3ad association state changes
235 - The bond's administrative state changes to up
252 In an AD system, the port-key has three parts as shown below -
258 01-05 Speed
259 06-15 User-defined
263 from 0 - 1023. If not given, the system defaults to 0.
311 address must be given for ARP monitoring to function. The
319 non-ARP traffic should be filtered (disregarded) for link
409 This option affects only active-backup mode for slaves with
435 Specifies whether active-backup mode should set all slaves to
436 the same MAC address at enslavement (the traditional
438 bond's MAC address in accordance with the selected policy.
445 bonding to set all slaves of an active-backup bond to
446 the same MAC address at enslavement time. This is the
452 MAC address of the bond should always be the MAC
453 address of the currently active slave. The MAC
454 address of the slaves is not changed; instead, the MAC
455 address of the bond changes during a failover.
458 alter their MAC address, or for devices that refuse
459 incoming broadcasts with their own source MAC (which
479 The "follow" fail_over_mac policy causes the MAC
480 address of the bond to be selected normally (normally
481 the MAC address of the first slave added to the bond).
483 to this MAC address while they are in a backup role; a
484 slave is programmed with the bond's MAC address at
486 the newly active slave's MAC address).
490 when multiple ports are programmed with the same MAC
491 address.
495 change its MAC address, in which case the active policy is
551 asserting carrier. It is similar to the Cisco EtherChannel min-links
553 must be up (link-up state) before marking the bond device as up
568 balance-rr (round robin). Possible values are:
570 balance-rr or 0
572 Round-robin policy: Transmit packets in sequential
577 active-backup or 1
579 Active-backup policy: Only one slave in the bond is
581 if, the active slave fails. The bond's MAC address is
586 occurs in active-backup mode, bonding will issue one
591 address configured. Gratuitous ARPs issued for VLAN
598 balance-xor or 2
602 MAC address XOR'd with destination MAC address XOR
626 regards to the packet mis-ordering requirements of
642 balance-tlb or 5
657 the MAC address of the failed receiving slave.
664 balance-alb or 6
666 Adaptive load balancing: includes balance-tlb plus
671 the local system on their way out and overwrites the
672 source hardware address with the unique hardware
673 address of one of the slaves in the bond such that
678 is also balanced. When the local system sends an ARP
681 Reply arrives from the peer, its hardware address is
686 ARP request is broadcast it uses the hardware address
687 of the bond. Hence, peers learn the hardware address
691 their individually assigned hardware address such that
694 and when an inactive slave is re-activated. The
701 with the selected MAC address to each of the
713 address of a device while it is open. This is
715 team using the bond hardware address (the
717 address for each slave in the bond. If the
718 curr_active_slave fails its hardware address is
729 bonding device and each VLAN sub-device. This is repeated at
733 The valid range is 0 - 255; the default value is 1. These options
734 affect only the active-backup mode. These options were added for
747 The valid range is 0 - 65535; the default value is 1. This option
748 has effect only in balance-rr mode.
765 off-line will alternate devices be used. This is useful when
769 The primary option is only valid for active-backup(1),
770 balance-tlb (5) and balance-alb (6) mode.
777 occurs. This option is designed to prevent flip-flopping between
819 characteristics but can cause packet reordering. If re-ordering is
822 xmit-hash-policy can be used to select the appropriate hashing for
867 balance-xor, 802.3ad, and tlb modes. Possible values are:
871 Uses XOR of hardware MAC addresses and packet type ID
874 hash = source MAC XOR destination MAC XOR packet type ID
887 Uses XOR of hardware MAC addresses and IP addresses to
890 hash = source MAC XOR destination MAC XOR packet type ID
900 network peer on the same slave. For non-IP traffic,
932 information is omitted. For non-IP traffic, the
968 This policy uses a very rudimentary vlan ID and source mac
969 hash to load-balance traffic per-vlan, with failover
972 use their own vlan, to give lacp-like functionality
973 without requiring lacp-capable switching hardware.
977 hash = (vlan ID) XOR (source MAC vendor) XOR (source MAC dev)
990 The valid range is 0 - 255; the default value is 1. A value of 0
994 This option is useful for bonding modes balance-rr (0), active-backup
995 (1), balance-tlb (5) and balance-alb (6), in which a failover can
1007 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
1008 has effect only in balance-tlb and balance-alb modes.
1036 $ rpm -qf /sbin/ifup
1051 ----------------------------------------
1064 ifcfg-id file for each slave device. The simplest way to accomplish
1066 file ifcfg-id file created; see below for some issues with DHCP). The
1069 ifcfg-id-xx:xx:xx:xx:xx:xx
1072 the device's permanent MAC address.
1074 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1076 devices (the MAC addresses correspond to those of the slave devices).
1084 _nm_name='bus-pci-0001:61:01.0'
1094 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1096 itself. This file is named ifcfg-bondX, where X is the number of the
1098 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1102 The contents of the ifcfg-bondX file is as follows::
1112 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1114 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1153 (bus-pci-0000:06:08.1 in the example above) specify the physical
1184 -------------------------------
1187 will cause it to query DHCP for its IP address information. At this
1189 attempt to obtain the device address from DHCP prior to adding any of
1194 -----------------------------------------------
1198 bonding instance to have an appropriately configured ifcfg-bondX file
1202 ifcfg-bondX files.
1205 options in the ifcfg-bondX file, it is not necessary to add them to
1209 ------------------------------------------
1220 driver unless the ethX device is configured with an IP address.
1222 network-script file for all physical adapters that will be members of
1225 /etc/sysconfig/network-scripts
1227 The file name must be prefixed with "ifcfg-eth" and suffixed
1229 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1240 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1248 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1249 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1250 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1267 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1270 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1293 options bond0 mode=balance-alb miimon=100
1303 ---------------------------------
1316 -------------------------------------------------
1320 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1328 -----------------------------------------------
1340 /etc/init.d/boot.local and for initscripts it is /etc/rc.d/rc.local.
1344 reboots, edit the appropriate file (/etc/init.d/boot.local or
1345 /etc/rc.d/rc.local), and add the following::
1347 modprobe bonding mode=balance-alb miimon=100
1354 network configuration (IP address, netmask, etc) with the appropriate
1361 # /etc/init.d/boot.local
1365 # /etc/rc.d/rc.local
1369 separate script from within boot.local. This allows for bonding to be
1370 enabled without re-running the entire global init script.
1386 -----------------------------------------
1415 options bond0 -o bond0 mode=balance-rr miimon=100
1418 options bond1 -o bond1 mode=balance-alb miimon=50
1421 named "bond0" and creates the bond0 device in balance-rr mode with an
1423 bond1 device in balance-alb mode with an miimon of 50.
1430 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1431 mode=balance-alb miimon=50
1437 to rename modules at load time (the "-o bond1" part). Attempts to pass
1445 ------------------------------------------
1465 -----------------------------
1472 # echo -bar > /sys/class/net/bonding_masters
1485 --------------------------
1497 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1506 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1511 -------------------------------
1515 The names of these files correspond directly with the command-
1524 To configure bond0 for balance-alb mode::
1528 - or -
1529 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1542 monitoring is enabled, and vice-versa.
1555 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1568 ---------------------
1574 file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the
1579 echo balance-alb > /sys/class/net/bond0/bonding/mode
1586 active-backup mode, using ARP monitoring, add the following lines to
1591 echo active-backup > /sys/class/net/bond1/bonding/mode
1599 -----------------------------------------
1606 the box. The ifenslave-2.6 package should be installed to provide bonding
1607 support. Once installed, this package will provide ``bond-*`` options
1610 Note that ifenslave-2.6 package will load the bonding module and use
1614 ----------------------
1617 active-backup mode, with eth0 and eth1 as slaves::
1621 bond-slaves eth0 eth1
1622 bond-mode active-backup
1623 bond-miimon 100
1624 bond-primary eth0 eth1
1633 bond-slaves none
1634 bond-mode active-backup
1635 bond-miimon 100
1639 bond-master bond0
1640 bond-primary eth0 eth1
1644 bond-master bond0
1645 bond-primary eth0 eth1
1647 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1649 /usr/share/doc/ifenslave-2.6.
1652 ----------------------------------------------
1675 Bonding Mode: fault-tolerance (active-backup)
1726 a pass-through for selecting output queues on the slave device rather than
1730 output slave selection was limited to round-robin and active-backup modes.
1733 ----------------------------------------------------------
1737 destined to link local mac addresses (which switches/bridges are not
1739 or are simply the machine's MAC address (which is trivially known to all
1749 (a) ad_actor_system : You can set a random mac-address that can be used for
1751 Also it's preferable to set the local-admin bit. Following shell code
1752 generates a random mac-address as described above::
1764 is 65535, but system can take the value from 1 - 65535. Following shell
1770 (c) ad_user_port_key : Use the user portion of the port-key. The default
1771 keeps this empty. These are the upper 10 bits of the port-key and value
1772 ranges from 0 - 1023. Following shell code generates these 10 bits and
1783 -------------------------
1785 Each bonding device has a read-only file residing in the
1794 Bonding Mode: load balancing (round-robin)
1813 -------------------------
1822 bond0 have the same MAC address (HWaddr) as bond0 for all modes except
1823 TLB and ALB that require a unique MAC address for each slave::
1838 Interrupt:10 Base address:0x1080
1845 Interrupt:9 Base address:0x1400
1856 The active-backup, balance-tlb and balance-alb modes do not
1867 The balance-rr, balance-xor and broadcast modes generally
1873 policy to the bond. Typical choices include XOR of either the MAC or
1899 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1904 hardware address of 00:00:00:00:00:00 until the first slave is added.
1906 would pick up the all-zeroes hardware address. Once the first slave
1908 slave's hardware address, which is then available for the VLAN device.
1913 obtain its hardware address from the first slave, which might not
1914 match the hardware address of the VLAN interfaces (which was
1918 with the correct hardware address if all slaves are removed from a
1923 2. Set the bonding interface's hardware address so that it
1924 matches the hardware address of the VLAN interfaces.
1926 Note that changing a VLAN interface's HW address would set the
1927 underlying device -- i.e. the bonding interface -- to promiscuous
1943 -------------------------
1949 or more peers on the local network.
1953 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1954 flag must also update netdev_queue->trans_start. If they do not, then the
1961 ------------------------------------
1984 -------------------------
1986 The MII monitor monitors only the carrier state of the local
2013 -------------------------
2048 ----------------------------
2059 options bond0 mode=some-mode miimon=50
2092 ---------------------------------------------------------
2125 the first interface found with a given IP address. That is, there is
2126 only one ipAdEntIfIndex for each IP address. For example, if eth0 and
2128 bonding driver, the interface for the IP address will be associated
2130 address 192.168.1.1 has an interface index of 2 which indexes to eth0
2148 loading the bonding driver first, the IP address 192.168.1.1 is
2163 ifDescr, the association between the IP address and IfIndex remains
2172 is seen (instead of seeing only traffic destined for the local host).
2177 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2180 For the active-backup, balance-tlb and balance-alb modes, the
2183 For balance-tlb mode, the active slave is the slave currently
2186 For balance-alb mode, the active slave is the slave used as a
2187 "primary." This slave is used for mode-specific control traffic, for
2190 For the active-backup, balance-tlb and balance-alb modes, when
2205 --------------------------------------------------
2219 ----------------------------------------------------
2230 +-----+----+ +-----+----+
2232 | switch A +--------------------------+ switch B |
2234 +-----+----+ +-----++---+
2236 | +-------+ |
2237 +-------------+ host1 +---------------+
2238 eth0 +-------+ eth1
2246 -------------------------------------------------------------
2248 In a topology such as the example above, the active-backup and
2253 active-backup:
2266 necessary for some specific one-way traffic to reach both
2270 ----------------------------------------------------------------
2303 ------------------------------------------------------
2312 categorize them into either "gatewayed" or "local" configurations.
2319 +----------+ +----------+
2321 | Host A +---------------------+ router +------------------->
2322 | +---------------------+ | Hosts B and C are out
2324 +----------+ +----------+
2333 and received via one other peer on the local network, the router.
2341 In a local configuration, the "switch" is acting primarily as
2346 +----------+ +----------+ +--------+
2347 | |eth0 port1| +-------+ Host B |
2348 | Host A +------------+ switch |port3 +--------+
2349 | +------------+ | +--------+
2350 | |eth1 port2| +------------------+ Host C |
2351 +----------+ +----------+port4 +--------+
2357 on the same local network (Hosts B and C in the above example).
2360 the bonded device will be to the same MAC level peer on the network
2362 destination. In a local configuration, traffic flows directly to and
2364 will be addressed directly by their individual MAC addresses.
2366 This distinction between a gatewayed and a local network
2368 available use the MAC addresses of the local network source and
2374 -----------------------------------------------------------
2380 balance-rr:
2405 (instead choosing a port based upon IP or MAC level addresses);
2407 through the switch to a balance-rr bond will not utilize greater
2419 active-backup:
2421 the active-backup mode, as the inactive backup devices are all
2425 available bandwidth. On the plus side, active-backup mode
2430 balance-xor:
2433 interface. Since the destination is determined by the MAC
2434 addresses involved, this mode works best in a "local" network
2436 the same local network. This mode is likely to be suboptimal
2440 As with balance-rr, the switch ports need to be configured for
2444 Like active-backup, there is not much advantage to this
2460 balance modes other than balance-rr, no single connection will
2465 distributes traffic by peer (using an XOR of MAC addresses
2470 implementation. In a "local" configuration, traffic will be
2476 balance-tlb:
2477 The balance-tlb mode balances outgoing traffic by peer.
2478 Since the balancing is done according to MAC address, in a
2481 "local" network configuration, this mode balances multiple
2482 local network peers across devices in a vaguely intelligent
2483 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2484 so that mathematically unlucky MAC addresses (i.e., ones that
2495 balance-alb:
2496 This mode is everything that balance-tlb is, and more.
2497 It has all of the features (and restrictions) of balance-tlb,
2498 and will also balance incoming traffic from local network
2503 device driver must support changing the hardware address while
2507 ----------------------------------------------------
2516 -----------------------------------------------------
2522 +-----------+
2524 +-+---+---+-+
2526 +--------+ | +---------+
2528 +------+---+ +-----+----+ +-----+----+
2530 +------+---+ +-----+----+ +-----+----+
2532 +--------+ | +---------+
2534 +-+---+---+-+
2536 +-----------+
2551 -------------------------------------------------------------
2554 configurations of this type is balance-rr. Historically, in this
2559 packets has arrived). When employed in this fashion, the balance-rr
2564 ------------------------------------------------------
2577 -------------------------------------------
2612 --------------------------------
2624 For example, on a bond in active-backup mode with five slaves
2627 # ping -n 10.0.4.2
2639 is a side effect of how many switches update their MAC forwarding
2640 tables. Initially, the switch does not associate the MAC address in
2642 traffic to all ports until its MAC forwarding table is updated. Since
2650 behavior, it can be induced by clearing the MAC forwarding table (on
2651 most Cisco switches, the privileged command "clear mac address-table
2662 --------------------
2667 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2672 --------------------------------
2675 integrated on the planar (that's "motherboard" in IBM-speak). In the
2678 An add-on Broadcom daughter card can be installed on a JS20 to provide
2687 Additional BladeCenter-specific networking information can be
2690 - "IBM eServer BladeCenter Networking Options"
2691 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2694 ------------------------------------
2719 -------------------------------
2721 The balance-rr mode requires the use of passthrough modules
2724 appropriate ports, as is usual for balance-rr.
2726 The balance-alb and balance-tlb modes will function with
2733 The active-backup mode has no additional requirements.
2736 ----------------------
2751 --------------
2761 avoid fail-over delay issues when using bonding.
2768 -------------------
2774 -----------------------------------------
2776 Any Ethernet type cards (you can even mix cards - a Intel
2781 slaves in active-backup mode.
2784 ----------------------------------------
2789 ----------------------------------------------
2796 ----------------------------------------
2799 disabled. The active-backup mode will fail over to a backup link, and
2810 monitors connectivity to another host on the local network.
2819 ----------------------------------------------
2824 ---------------------------------------------
2828 In the basic balance modes (balance-rr and balance-xor), it
2833 The advanced balance modes (balance-tlb and balance-alb) do
2842 The active-backup mode should work with any Layer-II switch.
2844 8. Where does a bonding device get its MAC address from?
2845 ---------------------------------------------------------
2847 When using slave devices that have fixed MAC addresses, or when
2848 the fail_over_mac option is enabled, the bonding device's MAC address is
2849 the MAC address of the active slave.
2852 ifconfig or ip link), the MAC address of the bonding device is taken from
2853 its first slave device. This MAC address is then passed to all following
2857 If you wish to change the MAC address, you can set it with
2862 # ip link set bond0 address 66:77:88:99:aa:bb
2864 The MAC address can be also changed by bringing down/up the
2867 # ifconfig bond0 down ; modprobe -r bonding
2871 This method will automatically take the address from the next
2874 To restore your slaves' MAC addresses, you need to detach them
2875 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2876 then restore the MAC addresses that the slaves had before they were
2890 address is:
2897 http://vger.kernel.org/vger-lists.html#netdev