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 address. If the all-zeroes MAC is specified, bonding will internally
201 use the MAC of the bond itself. It is preferred to have the
202 local-admin bit set for this mac but driver does not enforce it. If
204 mac address as actors' system address.
230 - A slave is added to or removed from the bond
232 - Any slave's link state changes
234 - Any slave's 802.3ad association state changes
236 - The bond's administrative state changes to up
253 In an AD system, the port-key has three parts as shown below -
259 01-05 Speed
260 06-15 User-defined
264 from 0 - 1023. If not given, the system defaults to 0.
312 address must be given for ARP monitoring to function. The
320 non-ARP traffic should be filtered (disregarded) for link
410 This option affects only active-backup mode for slaves with
436 Specifies whether active-backup mode should set all slaves to
437 the same MAC address at enslavement (the traditional
439 bond's MAC address in accordance with the selected policy.
446 bonding to set all slaves of an active-backup bond to
447 the same MAC address at enslavement time. This is the
453 MAC address of the bond should always be the MAC
454 address of the currently active slave. The MAC
455 address of the slaves is not changed; instead, the MAC
456 address of the bond changes during a failover.
459 alter their MAC address, or for devices that refuse
460 incoming broadcasts with their own source MAC (which
480 The "follow" fail_over_mac policy causes the MAC
481 address of the bond to be selected normally (normally
482 the MAC address of the first slave added to the bond).
484 to this MAC address while they are in a backup role; a
485 slave is programmed with the bond's MAC address at
487 the newly active slave's MAC address).
491 when multiple ports are programmed with the same MAC
492 address.
496 change its MAC address, in which case the active policy is
540 asserting carrier. It is similar to the Cisco EtherChannel min-links
542 must be up (link-up state) before marking the bond device as up
557 balance-rr (round robin). Possible values are:
559 balance-rr or 0
561 Round-robin policy: Transmit packets in sequential
566 active-backup or 1
568 Active-backup policy: Only one slave in the bond is
570 if, the active slave fails. The bond's MAC address is
575 occurs in active-backup mode, bonding will issue one
580 address configured. Gratuitous ARPs issued for VLAN
587 balance-xor or 2
591 MAC address XOR'd with destination MAC address XOR
615 regards to the packet mis-ordering requirements of
631 balance-tlb or 5
646 the MAC address of the failed receiving slave.
653 balance-alb or 6
655 Adaptive load balancing: includes balance-tlb plus
660 the local system on their way out and overwrites the
661 source hardware address with the unique hardware
662 address of one of the slaves in the bond such that
667 is also balanced. When the local system sends an ARP
670 Reply arrives from the peer, its hardware address is
675 ARP request is broadcast it uses the hardware address
676 of the bond. Hence, peers learn the hardware address
680 their individually assigned hardware address such that
683 and when an inactive slave is re-activated. The
690 with the selected MAC address to each of the
702 address of a device while it is open. This is
704 team using the bond hardware address (the
706 address for each slave in the bond. If the
707 curr_active_slave fails its hardware address is
718 bonding device and each VLAN sub-device. This is repeated at
722 The valid range is 0 - 255; the default value is 1. These options
723 affect only the active-backup mode. These options were added for
736 The valid range is 0 - 65535; the default value is 1. This option
737 has effect only in balance-rr mode.
754 off-line will alternate devices be used. This is useful when
758 The primary option is only valid for active-backup(1),
759 balance-tlb (5) and balance-alb (6) mode.
766 occurs. This option is designed to prevent flip-flopping between
808 characteristics but can cause packet reordering. If re-ordering is
811 xmit-hash-policy can be used to select the appropriate hashing for
856 balance-xor, 802.3ad, and tlb modes. Possible values are:
860 Uses XOR of hardware MAC addresses and packet type ID
863 hash = source MAC XOR destination MAC XOR packet type ID
876 Uses XOR of hardware MAC addresses and IP addresses to
879 hash = source MAC XOR destination MAC XOR packet type ID
889 network peer on the same slave. For non-IP traffic,
921 information is omitted. For non-IP traffic, the
966 The valid range is 0 - 255; the default value is 1. A value of 0
970 This option is useful for bonding modes balance-rr (0), active-backup
971 (1), balance-tlb (5) and balance-alb (6), in which a failover can
983 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
984 has effect only in balance-tlb and balance-alb modes.
1012 $ rpm -qf /sbin/ifup
1027 ----------------------------------------
1040 ifcfg-id file for each slave device. The simplest way to accomplish
1042 file ifcfg-id file created; see below for some issues with DHCP). The
1045 ifcfg-id-xx:xx:xx:xx:xx:xx
1048 the device's permanent MAC address.
1050 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1052 devices (the MAC addresses correspond to those of the slave devices).
1060 _nm_name='bus-pci-0001:61:01.0'
1070 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1072 itself. This file is named ifcfg-bondX, where X is the number of the
1074 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1078 The contents of the ifcfg-bondX file is as follows::
1088 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1090 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1129 (bus-pci-0000:06:08.1 in the example above) specify the physical
1160 -------------------------------
1163 will cause it to query DHCP for its IP address information. At this
1165 attempt to obtain the device address from DHCP prior to adding any of
1170 -----------------------------------------------
1174 bonding instance to have an appropriately configured ifcfg-bondX file
1178 ifcfg-bondX files.
1181 options in the ifcfg-bondX file, it is not necessary to add them to
1185 ------------------------------------------
1196 driver unless the ethX device is configured with an IP address.
1198 network-script file for all physical adapters that will be members of
1201 /etc/sysconfig/network-scripts
1203 The file name must be prefixed with "ifcfg-eth" and suffixed
1205 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1216 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1224 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1225 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1226 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1243 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1246 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1269 options bond0 mode=balance-alb miimon=100
1279 ---------------------------------
1292 -------------------------------------------------
1296 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1304 -----------------------------------------------
1316 /etc/init.d/boot.local and for initscripts it is /etc/rc.d/rc.local.
1320 reboots, edit the appropriate file (/etc/init.d/boot.local or
1321 /etc/rc.d/rc.local), and add the following::
1323 modprobe bonding mode=balance-alb miimon=100
1330 network configuration (IP address, netmask, etc) with the appropriate
1337 # /etc/init.d/boot.local
1341 # /etc/rc.d/rc.local
1345 separate script from within boot.local. This allows for bonding to be
1346 enabled without re-running the entire global init script.
1362 -----------------------------------------
1391 options bond0 -o bond0 mode=balance-rr miimon=100
1394 options bond1 -o bond1 mode=balance-alb miimon=50
1397 named "bond0" and creates the bond0 device in balance-rr mode with an
1399 bond1 device in balance-alb mode with an miimon of 50.
1406 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1407 mode=balance-alb miimon=50
1413 to rename modules at load time (the "-o bond1" part). Attempts to pass
1421 ------------------------------------------
1441 -----------------------------
1448 # echo -bar > /sys/class/net/bonding_masters
1461 --------------------------
1473 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1482 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1487 -------------------------------
1491 The names of these files correspond directly with the command-
1500 To configure bond0 for balance-alb mode::
1504 - or -
1505 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1518 monitoring is enabled, and vice-versa.
1531 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1544 ---------------------
1550 file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the
1555 echo balance-alb > /sys/class/net/bond0/bonding/mode
1562 active-backup mode, using ARP monitoring, add the following lines to
1567 echo active-backup > /sys/class/net/bond1/bonding/mode
1575 -----------------------------------------
1582 the box. The ifenslave-2.6 package should be installed to provide bonding
1583 support. Once installed, this package will provide ``bond-*`` options
1586 Note that ifenslave-2.6 package will load the bonding module and use
1590 ----------------------
1593 active-backup mode, with eth0 and eth1 as slaves::
1597 bond-slaves eth0 eth1
1598 bond-mode active-backup
1599 bond-miimon 100
1600 bond-primary eth0 eth1
1609 bond-slaves none
1610 bond-mode active-backup
1611 bond-miimon 100
1615 bond-master bond0
1616 bond-primary eth0 eth1
1620 bond-master bond0
1621 bond-primary eth0 eth1
1623 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1625 /usr/share/doc/ifenslave-2.6.
1628 ----------------------------------------------
1651 Bonding Mode: fault-tolerance (active-backup)
1702 a pass-through for selecting output queues on the slave device rather than
1706 output slave selection was limited to round-robin and active-backup modes.
1709 ----------------------------------------------------------
1713 destined to link local mac addresses (which switches/bridges are not
1715 or are simply the machine's MAC address (which is trivially known to all
1725 (a) ad_actor_system : You can set a random mac-address that can be used for
1727 Also it's preferable to set the local-admin bit. Following shell code
1728 generates a random mac-address as described above::
1740 is 65535, but system can take the value from 1 - 65535. Following shell
1746 (c) ad_user_port_key : Use the user portion of the port-key. The default
1747 keeps this empty. These are the upper 10 bits of the port-key and value
1748 ranges from 0 - 1023. Following shell code generates these 10 bits and
1759 -------------------------
1761 Each bonding device has a read-only file residing in the
1770 Bonding Mode: load balancing (round-robin)
1789 -------------------------
1798 bond0 have the same MAC address (HWaddr) as bond0 for all modes except
1799 TLB and ALB that require a unique MAC address for each slave::
1814 Interrupt:10 Base address:0x1080
1821 Interrupt:9 Base address:0x1400
1832 The active-backup, balance-tlb and balance-alb modes do not
1843 The balance-rr, balance-xor and broadcast modes generally
1849 policy to the bond. Typical choices include XOR of either the MAC or
1875 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1880 hardware address of 00:00:00:00:00:00 until the first slave is added.
1882 would pick up the all-zeroes hardware address. Once the first slave
1884 slave's hardware address, which is then available for the VLAN device.
1889 obtain its hardware address from the first slave, which might not
1890 match the hardware address of the VLAN interfaces (which was
1894 with the correct hardware address if all slaves are removed from a
1899 2. Set the bonding interface's hardware address so that it
1900 matches the hardware address of the VLAN interfaces.
1902 Note that changing a VLAN interface's HW address would set the
1903 underlying device -- i.e. the bonding interface -- to promiscuous
1919 -------------------------
1925 or more peers on the local network.
1929 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1930 flag must also update netdev_queue->trans_start. If they do not, then the
1937 ------------------------------------
1960 -------------------------
1962 The MII monitor monitors only the carrier state of the local
1989 -------------------------
2024 ----------------------------
2035 options bond0 mode=some-mode miimon=50
2068 ---------------------------------------------------------
2101 the first interface found with a given IP address. That is, there is
2102 only one ipAdEntIfIndex for each IP address. For example, if eth0 and
2104 bonding driver, the interface for the IP address will be associated
2106 address 192.168.1.1 has an interface index of 2 which indexes to eth0
2124 loading the bonding driver first, the IP address 192.168.1.1 is
2139 ifDescr, the association between the IP address and IfIndex remains
2148 is seen (instead of seeing only traffic destined for the local host).
2153 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2156 For the active-backup, balance-tlb and balance-alb modes, the
2159 For balance-tlb mode, the active slave is the slave currently
2162 For balance-alb mode, the active slave is the slave used as a
2163 "primary." This slave is used for mode-specific control traffic, for
2166 For the active-backup, balance-tlb and balance-alb modes, when
2181 --------------------------------------------------
2195 ----------------------------------------------------
2206 +-----+----+ +-----+----+
2208 | switch A +--------------------------+ switch B |
2210 +-----+----+ +-----++---+
2212 | +-------+ |
2213 +-------------+ host1 +---------------+
2214 eth0 +-------+ eth1
2222 -------------------------------------------------------------
2224 In a topology such as the example above, the active-backup and
2229 active-backup:
2242 necessary for some specific one-way traffic to reach both
2246 ----------------------------------------------------------------
2279 ------------------------------------------------------
2288 categorize them into either "gatewayed" or "local" configurations.
2295 +----------+ +----------+
2297 | Host A +---------------------+ router +------------------->
2298 | +---------------------+ | Hosts B and C are out
2300 +----------+ +----------+
2309 and received via one other peer on the local network, the router.
2317 In a local configuration, the "switch" is acting primarily as
2322 +----------+ +----------+ +--------+
2323 | |eth0 port1| +-------+ Host B |
2324 | Host A +------------+ switch |port3 +--------+
2325 | +------------+ | +--------+
2326 | |eth1 port2| +------------------+ Host C |
2327 +----------+ +----------+port4 +--------+
2333 on the same local network (Hosts B and C in the above example).
2336 the bonded device will be to the same MAC level peer on the network
2338 destination. In a local configuration, traffic flows directly to and
2340 will be addressed directly by their individual MAC addresses.
2342 This distinction between a gatewayed and a local network
2344 available use the MAC addresses of the local network source and
2350 -----------------------------------------------------------
2356 balance-rr:
2381 (instead choosing a port based upon IP or MAC level addresses);
2383 through the switch to a balance-rr bond will not utilize greater
2395 active-backup:
2397 the active-backup mode, as the inactive backup devices are all
2401 available bandwidth. On the plus side, active-backup mode
2406 balance-xor:
2409 interface. Since the destination is determined by the MAC
2410 addresses involved, this mode works best in a "local" network
2412 the same local network. This mode is likely to be suboptimal
2416 As with balance-rr, the switch ports need to be configured for
2420 Like active-backup, there is not much advantage to this
2436 balance modes other than balance-rr, no single connection will
2441 distributes traffic by peer (using an XOR of MAC addresses
2446 implementation. In a "local" configuration, traffic will be
2452 balance-tlb:
2453 The balance-tlb mode balances outgoing traffic by peer.
2454 Since the balancing is done according to MAC address, in a
2457 "local" network configuration, this mode balances multiple
2458 local network peers across devices in a vaguely intelligent
2459 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2460 so that mathematically unlucky MAC addresses (i.e., ones that
2471 balance-alb:
2472 This mode is everything that balance-tlb is, and more.
2473 It has all of the features (and restrictions) of balance-tlb,
2474 and will also balance incoming traffic from local network
2479 device driver must support changing the hardware address while
2483 ----------------------------------------------------
2492 -----------------------------------------------------
2498 +-----------+
2500 +-+---+---+-+
2502 +--------+ | +---------+
2504 +------+---+ +-----+----+ +-----+----+
2506 +------+---+ +-----+----+ +-----+----+
2508 +--------+ | +---------+
2510 +-+---+---+-+
2512 +-----------+
2527 -------------------------------------------------------------
2530 configurations of this type is balance-rr. Historically, in this
2535 packets has arrived). When employed in this fashion, the balance-rr
2540 ------------------------------------------------------
2553 -------------------------------------------
2588 --------------------------------
2600 For example, on a bond in active-backup mode with five slaves
2603 # ping -n 10.0.4.2
2615 is a side effect of how many switches update their MAC forwarding
2616 tables. Initially, the switch does not associate the MAC address in
2618 traffic to all ports until its MAC forwarding table is updated. Since
2626 behavior, it can be induced by clearing the MAC forwarding table (on
2627 most Cisco switches, the privileged command "clear mac address-table
2638 --------------------
2643 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2648 --------------------------------
2651 integrated on the planar (that's "motherboard" in IBM-speak). In the
2654 An add-on Broadcom daughter card can be installed on a JS20 to provide
2663 Additional BladeCenter-specific networking information can be
2666 - "IBM eServer BladeCenter Networking Options"
2667 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2670 ------------------------------------
2695 -------------------------------
2697 The balance-rr mode requires the use of passthrough modules
2700 appropriate ports, as is usual for balance-rr.
2702 The balance-alb and balance-tlb modes will function with
2709 The active-backup mode has no additional requirements.
2712 ----------------------
2727 --------------
2737 avoid fail-over delay issues when using bonding.
2744 -------------------
2750 -----------------------------------------
2752 Any Ethernet type cards (you can even mix cards - a Intel
2757 slaves in active-backup mode.
2760 ----------------------------------------
2765 ----------------------------------------------
2772 ----------------------------------------
2775 disabled. The active-backup mode will fail over to a backup link, and
2786 monitors connectivity to another host on the local network.
2795 ----------------------------------------------
2800 ---------------------------------------------
2804 In the basic balance modes (balance-rr and balance-xor), it
2809 The advanced balance modes (balance-tlb and balance-alb) do
2818 The active-backup mode should work with any Layer-II switch.
2820 8. Where does a bonding device get its MAC address from?
2821 ---------------------------------------------------------
2823 When using slave devices that have fixed MAC addresses, or when
2824 the fail_over_mac option is enabled, the bonding device's MAC address is
2825 the MAC address of the active slave.
2828 ifconfig or ip link), the MAC address of the bonding device is taken from
2829 its first slave device. This MAC address is then passed to all following
2833 If you wish to change the MAC address, you can set it with
2838 # ip link set bond0 address 66:77:88:99:aa:bb
2840 The MAC address can be also changed by bringing down/up the
2843 # ifconfig bond0 down ; modprobe -r bonding
2847 This method will automatically take the address from the next
2850 To restore your slaves' MAC addresses, you need to detach them
2851 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2852 then restore the MAC addresses that the slaves had before they were
2866 address is:
2873 http://vger.kernel.org/vger-lists.html#netdev