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
539 asserting carrier. It is similar to the Cisco EtherChannel min-links
541 must be up (link-up state) before marking the bond device as up
556 balance-rr (round robin). Possible values are:
558 balance-rr or 0
560 Round-robin policy: Transmit packets in sequential
565 active-backup or 1
567 Active-backup policy: Only one slave in the bond is
569 if, the active slave fails. The bond's MAC address is
574 occurs in active-backup mode, bonding will issue one
579 address configured. Gratuitous ARPs issued for VLAN
586 balance-xor or 2
590 MAC address XOR'd with destination MAC address XOR
614 regards to the packet mis-ordering requirements of
630 balance-tlb or 5
645 the MAC address of the failed receiving slave.
652 balance-alb or 6
654 Adaptive load balancing: includes balance-tlb plus
659 the local system on their way out and overwrites the
660 source hardware address with the unique hardware
661 address of one of the slaves in the bond such that
666 is also balanced. When the local system sends an ARP
669 Reply arrives from the peer, its hardware address is
674 ARP request is broadcast it uses the hardware address
675 of the bond. Hence, peers learn the hardware address
679 their individually assigned hardware address such that
682 and when an inactive slave is re-activated. The
689 with the selected MAC address to each of the
701 address of a device while it is open. This is
703 team using the bond hardware address (the
705 address for each slave in the bond. If the
706 curr_active_slave fails its hardware address is
717 bonding device and each VLAN sub-device. This is repeated at
721 The valid range is 0 - 255; the default value is 1. These options
722 affect only the active-backup mode. These options were added for
735 The valid range is 0 - 65535; the default value is 1. This option
736 has effect only in balance-rr mode.
753 off-line will alternate devices be used. This is useful when
757 The primary option is only valid for active-backup(1),
758 balance-tlb (5) and balance-alb (6) mode.
765 occurs. This option is designed to prevent flip-flopping between
807 characteristics but can cause packet reordering. If re-ordering is
810 xmit-hash-policy can be used to select the appropriate hashing for
855 balance-xor, 802.3ad, and tlb modes. Possible values are:
859 Uses XOR of hardware MAC addresses and packet type ID
862 hash = source MAC XOR destination MAC XOR packet type ID
875 Uses XOR of hardware MAC addresses and IP addresses to
878 hash = source MAC XOR destination MAC XOR packet type ID
888 network peer on the same slave. For non-IP traffic,
920 information is omitted. For non-IP traffic, the
965 The valid range is 0 - 255; the default value is 1. A value of 0
969 This option is useful for bonding modes balance-rr (0), active-backup
970 (1), balance-tlb (5) and balance-alb (6), in which a failover can
982 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
983 has effect only in balance-tlb and balance-alb modes.
1011 $ rpm -qf /sbin/ifup
1026 ----------------------------------------
1039 ifcfg-id file for each slave device. The simplest way to accomplish
1041 file ifcfg-id file created; see below for some issues with DHCP). The
1044 ifcfg-id-xx:xx:xx:xx:xx:xx
1047 the device's permanent MAC address.
1049 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1051 devices (the MAC addresses correspond to those of the slave devices).
1059 _nm_name='bus-pci-0001:61:01.0'
1069 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1071 itself. This file is named ifcfg-bondX, where X is the number of the
1073 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1077 The contents of the ifcfg-bondX file is as follows::
1087 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1089 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1128 (bus-pci-0000:06:08.1 in the example above) specify the physical
1159 -------------------------------
1162 will cause it to query DHCP for its IP address information. At this
1164 attempt to obtain the device address from DHCP prior to adding any of
1169 -----------------------------------------------
1173 bonding instance to have an appropriately configured ifcfg-bondX file
1177 ifcfg-bondX files.
1180 options in the ifcfg-bondX file, it is not necessary to add them to
1184 ------------------------------------------
1195 driver unless the ethX device is configured with an IP address.
1197 network-script file for all physical adapters that will be members of
1200 /etc/sysconfig/network-scripts
1202 The file name must be prefixed with "ifcfg-eth" and suffixed
1204 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1215 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1223 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1224 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1225 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1242 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1245 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1268 options bond0 mode=balance-alb miimon=100
1278 ---------------------------------
1291 -------------------------------------------------
1295 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1303 -----------------------------------------------
1315 /etc/init.d/boot.local and for initscripts it is /etc/rc.d/rc.local.
1319 reboots, edit the appropriate file (/etc/init.d/boot.local or
1320 /etc/rc.d/rc.local), and add the following::
1322 modprobe bonding mode=balance-alb miimon=100
1329 network configuration (IP address, netmask, etc) with the appropriate
1336 # /etc/init.d/boot.local
1340 # /etc/rc.d/rc.local
1344 separate script from within boot.local. This allows for bonding to be
1345 enabled without re-running the entire global init script.
1361 -----------------------------------------
1390 options bond0 -o bond0 mode=balance-rr miimon=100
1393 options bond1 -o bond1 mode=balance-alb miimon=50
1396 named "bond0" and creates the bond0 device in balance-rr mode with an
1398 bond1 device in balance-alb mode with an miimon of 50.
1405 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1406 mode=balance-alb miimon=50
1412 to rename modules at load time (the "-o bond1" part). Attempts to pass
1420 ------------------------------------------
1440 -----------------------------
1447 # echo -bar > /sys/class/net/bonding_masters
1460 --------------------------
1472 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1481 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1486 -------------------------------
1490 The names of these files correspond directly with the command-
1499 To configure bond0 for balance-alb mode::
1503 - or -
1504 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1517 monitoring is enabled, and vice-versa.
1530 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1543 ---------------------
1549 file (/etc/init.d/boot.local or /etc/rc.d/rc.local), and add the
1554 echo balance-alb > /sys/class/net/bond0/bonding/mode
1561 active-backup mode, using ARP monitoring, add the following lines to
1566 echo active-backup > /sys/class/net/bond1/bonding/mode
1574 -----------------------------------------
1581 the box. The ifenslave-2.6 package should be installed to provide bonding
1582 support. Once installed, this package will provide ``bond-*`` options
1585 Note that ifenslave-2.6 package will load the bonding module and use
1589 ----------------------
1592 active-backup mode, with eth0 and eth1 as slaves::
1596 bond-slaves eth0 eth1
1597 bond-mode active-backup
1598 bond-miimon 100
1599 bond-primary eth0 eth1
1608 bond-slaves none
1609 bond-mode active-backup
1610 bond-miimon 100
1614 bond-master bond0
1615 bond-primary eth0 eth1
1619 bond-master bond0
1620 bond-primary eth0 eth1
1622 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1624 /usr/share/doc/ifenslave-2.6.
1627 ----------------------------------------------
1650 Bonding Mode: fault-tolerance (active-backup)
1701 a pass-through for selecting output queues on the slave device rather than
1705 output slave selection was limited to round-robin and active-backup modes.
1708 ----------------------------------------------------------
1712 destined to link local mac addresses (which switches/bridges are not
1714 or are simply the machine's MAC address (which is trivially known to all
1724 (a) ad_actor_system : You can set a random mac-address that can be used for
1726 Also it's preferable to set the local-admin bit. Following shell code
1727 generates a random mac-address as described above::
1739 is 65535, but system can take the value from 1 - 65535. Following shell
1745 (c) ad_user_port_key : Use the user portion of the port-key. The default
1746 keeps this empty. These are the upper 10 bits of the port-key and value
1747 ranges from 0 - 1023. Following shell code generates these 10 bits and
1758 -------------------------
1760 Each bonding device has a read-only file residing in the
1769 Bonding Mode: load balancing (round-robin)
1788 -------------------------
1797 bond0 have the same MAC address (HWaddr) as bond0 for all modes except
1798 TLB and ALB that require a unique MAC address for each slave::
1813 Interrupt:10 Base address:0x1080
1820 Interrupt:9 Base address:0x1400
1831 The active-backup, balance-tlb and balance-alb modes do not
1842 The balance-rr, balance-xor and broadcast modes generally
1848 policy to the bond. Typical choices include XOR of either the MAC or
1874 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1879 hardware address of 00:00:00:00:00:00 until the first slave is added.
1881 would pick up the all-zeroes hardware address. Once the first slave
1883 slave's hardware address, which is then available for the VLAN device.
1888 obtain its hardware address from the first slave, which might not
1889 match the hardware address of the VLAN interfaces (which was
1893 with the correct hardware address if all slaves are removed from a
1898 2. Set the bonding interface's hardware address so that it
1899 matches the hardware address of the VLAN interfaces.
1901 Note that changing a VLAN interface's HW address would set the
1902 underlying device -- i.e. the bonding interface -- to promiscuous
1918 -------------------------
1924 or more peers on the local network.
1928 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1929 flag must also update netdev_queue->trans_start. If they do not, then the
1936 ------------------------------------
1959 -------------------------
1961 The MII monitor monitors only the carrier state of the local
1988 -------------------------
2023 ----------------------------
2034 options bond0 mode=some-mode miimon=50
2067 ---------------------------------------------------------
2100 the first interface found with a given IP address. That is, there is
2101 only one ipAdEntIfIndex for each IP address. For example, if eth0 and
2103 bonding driver, the interface for the IP address will be associated
2105 address 192.168.1.1 has an interface index of 2 which indexes to eth0
2123 loading the bonding driver first, the IP address 192.168.1.1 is
2138 ifDescr, the association between the IP address and IfIndex remains
2147 is seen (instead of seeing only traffic destined for the local host).
2152 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2155 For the active-backup, balance-tlb and balance-alb modes, the
2158 For balance-tlb mode, the active slave is the slave currently
2161 For balance-alb mode, the active slave is the slave used as a
2162 "primary." This slave is used for mode-specific control traffic, for
2165 For the active-backup, balance-tlb and balance-alb modes, when
2180 --------------------------------------------------
2194 ----------------------------------------------------
2205 +-----+----+ +-----+----+
2207 | switch A +--------------------------+ switch B |
2209 +-----+----+ +-----++---+
2211 | +-------+ |
2212 +-------------+ host1 +---------------+
2213 eth0 +-------+ eth1
2221 -------------------------------------------------------------
2223 In a topology such as the example above, the active-backup and
2228 active-backup:
2241 necessary for some specific one-way traffic to reach both
2245 ----------------------------------------------------------------
2278 ------------------------------------------------------
2287 categorize them into either "gatewayed" or "local" configurations.
2294 +----------+ +----------+
2296 | Host A +---------------------+ router +------------------->
2297 | +---------------------+ | Hosts B and C are out
2299 +----------+ +----------+
2308 and received via one other peer on the local network, the router.
2316 In a local configuration, the "switch" is acting primarily as
2321 +----------+ +----------+ +--------+
2322 | |eth0 port1| +-------+ Host B |
2323 | Host A +------------+ switch |port3 +--------+
2324 | +------------+ | +--------+
2325 | |eth1 port2| +------------------+ Host C |
2326 +----------+ +----------+port4 +--------+
2332 on the same local network (Hosts B and C in the above example).
2335 the bonded device will be to the same MAC level peer on the network
2337 destination. In a local configuration, traffic flows directly to and
2339 will be addressed directly by their individual MAC addresses.
2341 This distinction between a gatewayed and a local network
2343 available use the MAC addresses of the local network source and
2349 -----------------------------------------------------------
2355 balance-rr:
2380 (instead choosing a port based upon IP or MAC level addresses);
2382 through the switch to a balance-rr bond will not utilize greater
2394 active-backup:
2396 the active-backup mode, as the inactive backup devices are all
2400 available bandwidth. On the plus side, active-backup mode
2405 balance-xor:
2408 interface. Since the destination is determined by the MAC
2409 addresses involved, this mode works best in a "local" network
2411 the same local network. This mode is likely to be suboptimal
2415 As with balance-rr, the switch ports need to be configured for
2419 Like active-backup, there is not much advantage to this
2435 balance modes other than balance-rr, no single connection will
2440 distributes traffic by peer (using an XOR of MAC addresses
2445 implementation. In a "local" configuration, traffic will be
2451 balance-tlb:
2452 The balance-tlb mode balances outgoing traffic by peer.
2453 Since the balancing is done according to MAC address, in a
2456 "local" network configuration, this mode balances multiple
2457 local network peers across devices in a vaguely intelligent
2458 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2459 so that mathematically unlucky MAC addresses (i.e., ones that
2470 balance-alb:
2471 This mode is everything that balance-tlb is, and more.
2472 It has all of the features (and restrictions) of balance-tlb,
2473 and will also balance incoming traffic from local network
2478 device driver must support changing the hardware address while
2482 ----------------------------------------------------
2491 -----------------------------------------------------
2497 +-----------+
2499 +-+---+---+-+
2501 +--------+ | +---------+
2503 +------+---+ +-----+----+ +-----+----+
2505 +------+---+ +-----+----+ +-----+----+
2507 +--------+ | +---------+
2509 +-+---+---+-+
2511 +-----------+
2526 -------------------------------------------------------------
2529 configurations of this type is balance-rr. Historically, in this
2534 packets has arrived). When employed in this fashion, the balance-rr
2539 ------------------------------------------------------
2552 -------------------------------------------
2587 --------------------------------
2599 For example, on a bond in active-backup mode with five slaves
2602 # ping -n 10.0.4.2
2614 is a side effect of how many switches update their MAC forwarding
2615 tables. Initially, the switch does not associate the MAC address in
2617 traffic to all ports until its MAC forwarding table is updated. Since
2625 behavior, it can be induced by clearing the MAC forwarding table (on
2626 most Cisco switches, the privileged command "clear mac address-table
2637 --------------------
2642 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2647 --------------------------------
2650 integrated on the planar (that's "motherboard" in IBM-speak). In the
2653 An add-on Broadcom daughter card can be installed on a JS20 to provide
2662 Additional BladeCenter-specific networking information can be
2665 - "IBM eServer BladeCenter Networking Options"
2666 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2669 ------------------------------------
2694 -------------------------------
2696 The balance-rr mode requires the use of passthrough modules
2699 appropriate ports, as is usual for balance-rr.
2701 The balance-alb and balance-tlb modes will function with
2708 The active-backup mode has no additional requirements.
2711 ----------------------
2726 --------------
2736 avoid fail-over delay issues when using bonding.
2743 -------------------
2749 -----------------------------------------
2751 Any Ethernet type cards (you can even mix cards - a Intel
2756 slaves in active-backup mode.
2759 ----------------------------------------
2764 ----------------------------------------------
2771 ----------------------------------------
2774 disabled. The active-backup mode will fail over to a backup link, and
2785 monitors connectivity to another host on the local network.
2794 ----------------------------------------------
2799 ---------------------------------------------
2803 In the basic balance modes (balance-rr and balance-xor), it
2808 The advanced balance modes (balance-tlb and balance-alb) do
2817 The active-backup mode should work with any Layer-II switch.
2819 8. Where does a bonding device get its MAC address from?
2820 ---------------------------------------------------------
2822 When using slave devices that have fixed MAC addresses, or when
2823 the fail_over_mac option is enabled, the bonding device's MAC address is
2824 the MAC address of the active slave.
2827 ifconfig or ip link), the MAC address of the bonding device is taken from
2828 its first slave device. This MAC address is then passed to all following
2832 If you wish to change the MAC address, you can set it with
2837 # ip link set bond0 address 66:77:88:99:aa:bb
2839 The MAC address can be also changed by bringing down/up the
2842 # ifconfig bond0 down ; modprobe -r bonding
2846 This method will automatically take the address from the next
2849 To restore your slaves' MAC addresses, you need to detach them
2850 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2851 then restore the MAC addresses that the slaves had before they were
2865 address is:
2872 http://vger.kernel.org/vger-lists.html#netdev