Lines Matching +full:ether +full:- +full:link +full:- +full:active +full:- +full:low
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>
31 Additionally, link integrity monitoring may be performed.
35 the original tools from extreme-linux and beowulf sites will not work
69 7. Link Monitoring
77 8.3 Painfully Slow Or No Failed Link Detection By Miimon
87 11.2.2 HA Link Monitoring for Multiple Switch Topology
92 12.1.2 MT Link Monitoring for Single Switch Topology
95 12.2.2 MT Link Monitoring for Multiple Switch Topology
98 13.1 Link Establishment and Failover Delays
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
161 degradation will occur during link failures. Very few devices do not
172 Specifies the new active slave for modes that support it
173 (active-backup, balance-alb and balance-tlb). Possible values
175 string. If a name is given, the slave and its link must be up in order
176 to be selected as the new active slave. If an empty string is
177 specified, the current active slave is cleared, and a new active
184 active slave, or the empty string if there is no active slave or
185 the current mode does not use an active slave.
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
215 The active aggregator is chosen by largest aggregate
218 Reselection of the active aggregator occurs only when all
219 slaves of the active aggregator are down or the active
226 The active aggregator is chosen by largest aggregate
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
239 The active aggregator is chosen by the largest number of
244 802.3ad aggregations when partial failure of the active aggregator
246 (either in bandwidth or in number of ports) active at all times.
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.
282 Specifies the ARP link monitoring frequency in milliseconds.
299 the same link which could cause the other team members to
308 sent to determine the health of the link to the targets.
319 non-ARP traffic should be filtered (disregarded) for link
328 active or 1
330 Validation is performed only for the active slave.
348 only for the active slave.
361 For an active slave, the validation checks ARP replies to confirm
365 active slave. It is possible that some switch or network
372 the active slave failure, it doesn't really guarantee that the
373 backup slave will work if it's selected as the next active slave.
377 beyond a common switch. Should the link between the switch and
388 packets for link availability purposes. Arriving packets that are
394 determining if a slave has received traffic for link availability
401 link availability purposes.
409 This option affects only active-backup mode for slaves with
427 a slave after a link failure has been detected. This option
428 is only valid for the miimon link monitor. The downdelay
435 Specifies whether active-backup mode should set all slaves to
445 bonding to set all slaves of an active-backup bond to
449 active or 1
451 The "active" fail_over_mac policy indicates that the
453 address of the currently active slave. The MAC
472 monitor, devices which assert link up prior to being
485 failover time (and the formerly active slave receives
486 the newly active slave's MAC address).
495 change its MAC address, in which case the active policy is
506 Option specifying the rate in which we'll ask our link partner
528 Specifies the MII link monitoring frequency in milliseconds.
529 This determines how often the link state of each slave is
530 inspected for link failures. A value of zero disables MII
531 link monitoring. A value of 100 is a good starting point.
532 The use_carrier option, below, affects how the link state is
538 Specifies the minimum number of links that must be active before
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
543 such as clustering want to ensure a minimum number of low bandwidth
544 links are active before switchover. This option only affect 802.3ad
548 802.3ad mode) whenever there is an active aggregator, regardless of the
550 aggregator cannot be active without at least one available link,
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
568 active. A different slave becomes active if, and only
569 if, the active slave fails. The bond's MAC address is
574 occurs in active-backup mode, bonding will issue one
575 or more gratuitous ARPs on the newly active slave.
586 balance-xor or 2
604 IEEE 802.3ad Dynamic link aggregation. Creates
606 duplex settings. Utilizes all slaves in the active
614 regards to the packet mis-ordering requirements of
624 2. A switch that supports IEEE 802.3ad Dynamic link
630 balance-tlb or 5
652 balance-alb or 6
654 Adaptive load balancing: includes balance-tlb plus
682 and when an inactive slave is re-activated. The
686 When a link is reconnected or a new slave joins the
688 active slaves in the bond by initiating ARP Replies
715 failover event. As soon as the link is up on the new slave
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.
743 This delay should be a multiple of the link monitor interval
744 (arp_interval or miimon, whichever is active). The default
745 value is 0 which means to match the value of the link monitor
752 active slave while it is available. Only when the primary is
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.
763 affects how the primary slave is chosen to become the active slave
764 when failure of the active slave or recovery of the primary slave
765 occurs. This option is designed to prevent flip-flopping between
770 The primary slave becomes the active slave whenever it
775 The primary slave becomes the active slave when it comes
777 better than the speed and duplex of the current active
782 The primary slave becomes the active slave only if the
783 current active slave fails and the primary slave is up.
787 If no slaves are active, the first slave to recover is
788 made the active slave.
791 the active slave.
794 immediate selection of the best active slave according to the new
795 policy. This may or may not result in a change of the active
805 The default behavior of tlb mode is to shuffle active flows across
807 characteristics but can cause packet reordering. If re-ordering is
810 xmit-hash-policy can be used to select the appropriate hashing for
825 slave after a link recovery has been detected. This option is
826 only valid for the miimon link monitor. The updelay value
833 ioctls vs. netif_carrier_ok() to determine the link
840 If bonding insists that the link is up when it should not be,
844 it will appear as if the link is always up. In this case,
846 MII / ETHTOOL ioctl method to determine the link state.
855 balance-xor, 802.3ad, and tlb modes. Possible values are:
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
1049 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
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"
1118 for the bonding mode, link monitoring, and so on here. Do not include
1128 (bus-pci-0000:06:08.1 in the example above) specify the physical
1159 -------------------------------
1165 the slave devices. Without active slaves, the DHCP requests are not
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 ------------------------------------------
1197 network-script file for all physical adapters that will be members of
1198 a bondX link. Network script files are located in the directory:
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
1274 will restart the networking subsystem and your bond link should be now
1278 ---------------------------------
1291 -------------------------------------------------
1295 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1303 -----------------------------------------------
1313 `ip link` commands to the system's global init script. The name of
1322 modprobe bonding mode=balance-alb miimon=100
1325 ip link set eth0 master bond0
1326 ip link set eth1 master bond0
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 ---------------------
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)
1652 Currently Active Slave: eth0
1660 Link Failure Count: 0
1666 Link Failure Count: 0
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
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)
1770 Currently Active Slave: eth0
1778 Link Failure Count: 1
1782 Link Failure Count: 1
1788 -------------------------
1801 bond0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1808 eth0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1815 eth1 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
1831 The active-backup, balance-tlb and balance-alb modes do not
1842 The balance-rr, balance-xor and broadcast modes generally
1874 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1881 would pick up the all-zeroes hardware address. Once the first slave
1902 underlying device -- i.e. the bonding interface -- to promiscuous
1906 7. Link Monitoring
1910 monitoring a slave device's link state: the ARP monitor and the MII
1918 -------------------------
1922 uses the response as an indication that the link is operating. This
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 -------------------------
1976 device's (via ioctl) MII registers and check the link state. If that
1981 and ethtool requests), then the MII monitor will assume the link is
1988 -------------------------
2023 ----------------------------
2034 options bond0 mode=some-mode miimon=50
2066 8.3. Painfully Slow Or No Failed Link Detection By Miimon
2067 ---------------------------------------------------------
2073 not support the netif_carrier_on/_off link state tracking system.
2078 not maintain it in real time, e.g., only polling the link state at
2081 miimon is very slow in detecting link failures, try specifying
2152 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2155 For the active-backup, balance-tlb and balance-alb modes, the
2156 promiscuous mode setting is propagated only to the active slave.
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
2166 the active slave changes (e.g., due to a link failure), the
2167 promiscuous setting will be propagated to the new active slave.
2180 --------------------------------------------------
2187 support link monitoring of their members, so if individual links fail,
2194 ----------------------------------------------------
2205 +-----+----+ +-----+----+
2207 | switch A +--------------------------+ switch B |
2209 +-----+----+ +-----++---+
2211 | +-------+ |
2212 +-------------+ host1 +---------------+
2213 eth0 +-------+ eth1
2215 In this configuration, there is a link between the two
2216 switches (ISL, or inter switch link), and multiple ports connecting to
2221 -------------------------------------------------------------
2223 In a topology such as the example above, the active-backup and
2228 active-backup:
2234 preferred link is always used when it is available.
2241 necessary for some specific one-way traffic to reach both
2244 11.2.2 HA Link Monitoring Selection for Multiple Switch Topology
2245 ----------------------------------------------------------------
2247 The choice of link monitoring ultimately depends upon your
2250 example, in the above example, if the "port3" link fails at the remote
2261 regardless of which switch is active, the ARP monitor has a suitable
2266 switch that causes the link state of a particular switch port to be set
2268 Its purpose is to propagate link failures from logically "exterior" ports
2278 ------------------------------------------------------
2294 +----------+ +----------+
2296 | Host A +---------------------+ router +------------------->
2297 | +---------------------+ | Hosts B and C are out
2299 +----------+ +----------+
2321 +----------+ +----------+ +--------+
2322 | |eth0 port1| +-------+ Host B |
2323 | Host A +------------+ switch |port3 +--------+
2324 | +------------+ | +--------+
2325 | |eth1 port2| +------------------+ Host C |
2326 +----------+ +----------+port4 +--------+
2349 -----------------------------------------------------------
2355 balance-rr:
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
2398 load balancing mode (with link monitoring) will provide the
2400 available bandwidth. On the plus side, active-backup mode
2405 balance-xor:
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
2451 balance-tlb:
2452 The balance-tlb mode balances outgoing traffic by peer.
2458 manner (not a simple XOR as in balance-xor or 802.3ad mode),
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,
2481 12.1.2 MT Link Monitoring for Single Switch Topology
2482 ----------------------------------------------------
2484 The choice of link monitoring may largely depend upon which
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
2538 12.2.2 MT Link Monitoring for Multiple Switch Topology
2539 ------------------------------------------------------
2551 13.1 Link Establishment and Failover Delays
2552 -------------------------------------------
2555 timing of link up and down reporting by the switch.
2557 First, when a link comes up, some switches may indicate that
2558 the link is up (carrier available), but not pass traffic over the
2566 Second, some switches may "bounce" the link state one or more
2567 times while a link is changing state. This occurs most commonly while
2571 Note that when a bonding interface has no active links, the
2572 driver will immediately reuse the first link that goes up, even if the
2583 to not activate a backup interface immediately after a link goes down.
2587 --------------------------------
2599 For example, on a bond in active-backup mode with five slaves
2602 # ping -n 10.0.4.2
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.
2710 Link monitoring issues
2711 ----------------------
2714 monitor will reliably detect link loss to an external switch. This is
2719 only able to detect link failures between the ESM and the JS20 system.
2726 --------------
2728 The Serial Over LAN (SoL) link is established over the primary
2729 ethernet (eth0) only, therefore, any loss of link to eth0 will result
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 ----------------------------------------------
2770 5. What happens when a slave link dies?
2771 ----------------------------------------
2773 If link monitoring is enabled, then the failing device will be
2774 disabled. The active-backup mode will fail over to a backup link, and
2775 other modes will ignore the failed link. The link will continue to be
2781 Link monitoring can be enabled via either the miimon or
2787 If no link monitoring is configured, the bonding driver will
2788 be unable to detect link failures, and will assume that all links are
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
2814 802.3ad Dynamic Link Aggregation. Most managed and many unmanaged
2817 The active-backup mode should work with any Layer-II switch.
2820 ---------------------------------------------------------
2824 the MAC address of the active slave.
2827 ifconfig or ip link), the MAC address of the bonding device is taken from
2833 ifconfig or ip link::
2835 # ifconfig bond0 hw ether 00:11:22:33:44:55
2837 # ip link set bond0 address 66:77:88:99:aa:bb
2842 # ifconfig bond0 down ; modprobe -r bonding
2850 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2872 http://vger.kernel.org/vger-lists.html#netdev