Lines Matching +full:monitor +full:- +full:interval +full:- +full:ms
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
70 7.1 ARP Monitor Operation
72 7.3 MII Monitor Operation
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
202 local-admin bit set for this mac but driver does not enforce it. If
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.
285 The ARP monitor works by periodically checking the slave
331 non-ARP traffic should be filtered (disregarded) for link
369 Enabling validation causes the ARP monitor to examine the incoming
392 ARP monitor into considering the links as still up. Use of
393 validation can resolve this, as the ARP monitor will only consider
399 Enabling filtering causes the ARP monitor to only use incoming ARP
411 ARP monitor into considering the links as still up. Use of
420 in order for the ARP monitor to consider a slave as being up.
421 This option affects only active-backup mode for slaves with
438 Specifies the number of arp_interval monitor checks that must
439 fail in order for an interface to be marked down by the ARP monitor.
442 are permitted an extra monitor check (i.e., they must fail
445 The default value is 2, and the allowable range is 1 - 255.
451 is only valid for the miimon link monitor. The downdelay
458 Specifies whether active-backup mode should set all slaves to
468 bonding to set all slaves of an active-backup bond to
483 interferes with the ARP monitor).
495 monitor, devices which assert link up prior to being
574 asserting carrier. It is similar to the Cisco EtherChannel min-links
576 must be up (link-up state) before marking the bond device as up
591 balance-rr (round robin). Possible values are:
593 balance-rr or 0
595 Round-robin policy: Transmit packets in sequential
600 active-backup or 1
602 Active-backup policy: Only one slave in the bond is
609 occurs in active-backup mode, bonding will issue one
621 balance-xor or 2
649 regards to the packet mis-ordering requirements of
665 balance-tlb or 5
687 balance-alb or 6
689 Adaptive load balancing: includes balance-tlb plus
717 and when an inactive slave is re-activated. The
752 bonding device and each VLAN sub-device. This is repeated at
756 The valid range is 0 - 255; the default value is 1. These options
757 affect only the active-backup mode. These options were added for
770 The valid range is 0 - 65535; the default value is 1. This option
771 has effect only in balance-rr mode.
778 This delay should be a multiple of the link monitor interval
780 value is 0 which means to match the value of the link monitor
781 interval.
789 for active-backup(1), balance-tlb (5) and balance-alb (6) mode.
799 off-line will alternate devices be used. This is useful when
803 The primary option is only valid for active-backup(1),
804 balance-tlb (5) and balance-alb (6) mode.
811 occurs. This option is designed to prevent flip-flopping between
852 slaves based on the load in that interval. This gives nice lb
853 characteristics but can cause packet reordering. If re-ordering is
856 xmit-hash-policy can be used to select the appropriate hashing for
872 only valid for the miimon link monitor. The updelay value
901 balance-xor, 802.3ad, and tlb modes. Possible values are:
934 network peer on the same slave. For non-IP traffic,
966 information is omitted. For non-IP traffic, the
1003 hash to load-balance traffic per-vlan, with failover
1006 use their own vlan, to give lacp-like functionality
1007 without requiring lacp-capable switching hardware.
1022 the failover, subsequent packets are sent in each 200ms interval.
1024 The valid range is 0 - 255; the default value is 1. A value of 0
1028 This option is useful for bonding modes balance-rr (0), active-backup
1029 (1), balance-tlb (5) and balance-alb (6), in which a failover can
1041 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
1042 has effect only in balance-tlb and balance-alb modes.
1070 $ rpm -qf /sbin/ifup
1085 ----------------------------------------
1098 ifcfg-id file for each slave device. The simplest way to accomplish
1100 file ifcfg-id file created; see below for some issues with DHCP). The
1103 ifcfg-id-xx:xx:xx:xx:xx:xx
1108 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1118 _nm_name='bus-pci-0001:61:01.0'
1128 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1130 itself. This file is named ifcfg-bondX, where X is the number of the
1132 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1136 The contents of the ifcfg-bondX file is as follows::
1146 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1148 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1187 (bus-pci-0000:06:08.1 in the example above) specify the physical
1218 -------------------------------
1228 -----------------------------------------------
1232 bonding instance to have an appropriately configured ifcfg-bondX file
1236 ifcfg-bondX files.
1239 options in the ifcfg-bondX file, it is not necessary to add them to
1243 ------------------------------------------
1256 network-script file for all physical adapters that will be members of
1259 /etc/sysconfig/network-scripts
1261 The file name must be prefixed with "ifcfg-eth" and suffixed
1263 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1274 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1282 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1283 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1284 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1301 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1304 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1327 options bond0 mode=balance-alb miimon=100
1337 ---------------------------------
1350 -------------------------------------------------
1354 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1362 -----------------------------------------------
1381 modprobe bonding mode=balance-alb miimon=100
1404 enabled without re-running the entire global init script.
1420 -----------------------------------------
1449 options bond0 -o bond0 mode=balance-rr miimon=100
1452 options bond1 -o bond1 mode=balance-alb miimon=50
1455 named "bond0" and creates the bond0 device in balance-rr mode with an
1457 bond1 device in balance-alb mode with an miimon of 50.
1464 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1465 mode=balance-alb miimon=50
1471 to rename modules at load time (the "-o bond1" part). Attempts to pass
1479 ------------------------------------------
1499 -----------------------------
1506 # echo -bar > /sys/class/net/bonding_masters
1519 --------------------------
1531 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1540 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1545 -------------------------------
1549 The names of these files correspond directly with the command-
1558 To configure bond0 for balance-alb mode::
1562 - or -
1563 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1569 To enable MII monitoring on bond0 with a 1 second interval::
1576 monitoring is enabled, and vice-versa.
1589 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1591 To configure the interval between learning packet transmits::
1599 default interval is 1 second.
1602 ---------------------
1613 echo balance-alb > /sys/class/net/bond0/bonding/mode
1620 active-backup mode, using ARP monitoring, add the following lines to
1625 echo active-backup > /sys/class/net/bond1/bonding/mode
1633 -----------------------------------------
1640 the box. The ifenslave-2.6 package should be installed to provide bonding
1641 support. Once installed, this package will provide ``bond-*`` options
1644 Note that ifenslave-2.6 package will load the bonding module and use
1648 ----------------------
1651 active-backup mode, with eth0 and eth1 as slaves::
1655 bond-slaves eth0 eth1
1656 bond-mode active-backup
1657 bond-miimon 100
1658 bond-primary eth0 eth1
1667 bond-slaves none
1668 bond-mode active-backup
1669 bond-miimon 100
1673 bond-master bond0
1674 bond-primary eth0 eth1
1678 bond-master bond0
1679 bond-primary eth0 eth1
1681 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1683 /usr/share/doc/ifenslave-2.6.
1686 ----------------------------------------------
1709 Bonding Mode: fault-tolerance (active-backup)
1713 MII Polling Interval (ms): 0
1714 Up Delay (ms): 0
1715 Down Delay (ms): 0
1760 a pass-through for selecting output queues on the slave device rather than
1764 output slave selection was limited to round-robin and active-backup modes.
1767 ----------------------------------------------------------
1783 (a) ad_actor_system : You can set a random mac-address that can be used for
1785 Also it's preferable to set the local-admin bit. Following shell code
1786 generates a random mac-address as described above::
1798 is 65535, but system can take the value from 1 - 65535. Following shell
1804 (c) ad_user_port_key : Use the user portion of the port-key. The default
1805 keeps this empty. These are the upper 10 bits of the port-key and value
1806 ranges from 0 - 1023. Following shell code generates these 10 bits and
1817 -------------------------
1819 Each bonding device has a read-only file residing in the
1828 Bonding Mode: load balancing (round-robin)
1831 MII Polling Interval (ms): 1000
1832 Up Delay (ms): 0
1833 Down Delay (ms): 0
1847 -------------------------
1890 The active-backup, balance-tlb and balance-alb modes do not
1901 The balance-rr, balance-xor and broadcast modes generally
1921 packets generated by either ALB mode or the ARP monitor mechanism, are
1933 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1940 would pick up the all-zeroes hardware address. Once the first slave
1961 underlying device -- i.e. the bonding interface -- to promiscuous
1969 monitoring a slave device's link state: the ARP monitor and the MII
1970 monitor.
1976 7.1 ARP Monitor Operation
1977 -------------------------
1979 The ARP monitor operates as its name suggests: it sends ARP
1986 ------------------------------------
1990 monitor. In the case of just one target, the target itself may go
2008 7.3 MII Monitor Operation
2009 -------------------------
2011 The MII monitor monitors only the carrier state of the local
2018 then the MII monitor will rely on the driver for carrier state
2020 use_carrier parameter information, above, if the MII monitor fails to
2025 If use_carrier is 0, then the MII monitor will first query the
2028 monitor will make an ethtool ETHTOOL_GLINK request to attempt to obtain
2031 and ethtool requests), then the MII monitor will assume the link is
2038 -------------------------
2054 receive/transmit times in the driver (needed by the ARP monitor), but
2058 The ARP monitor (and ARP itself) may become confused by this
2059 configuration, because ARP requests (generated by the ARP monitor)
2063 interface basis), and is discarded. The MII monitor is not affected
2073 ----------------------------
2084 options bond0 mode=some-mode miimon=50
2117 ---------------------------------------------------------
2129 some fixed interval. In this case, miimon will detect failures, but
2134 fixed interval, but does not cache the MII register values (so the
2202 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2205 For the active-backup, balance-tlb and balance-alb modes, the
2208 For balance-tlb mode, the active slave is the slave currently
2211 For balance-alb mode, the active slave is the slave used as a
2212 "primary." This slave is used for mode-specific control traffic, for
2215 For the active-backup, balance-tlb and balance-alb modes, when
2230 --------------------------------------------------
2244 ----------------------------------------------------
2255 +-----+----+ +-----+----+
2257 | switch A +--------------------------+ switch B |
2259 +-----+----+ +-----++---+
2261 | +-------+ |
2262 +-------------+ host1 +---------------+
2263 eth0 +-------+ eth1
2271 -------------------------------------------------------------
2273 In a topology such as the example above, the active-backup and
2278 active-backup:
2291 necessary for some specific one-way traffic to reach both
2295 ----------------------------------------------------------------
2301 end, the MII monitor has no direct means to detect this. The ARP
2302 monitor could be configured with a target at the remote end of port3,
2306 monitor can provide a higher level of reliability in detecting end to
2309 the ARP monitor should be configured with multiple targets (at least
2311 regardless of which switch is active, the ARP monitor has a suitable
2319 to the logically "interior" ports that bonding is able to monitor via
2321 switch, but this can be a viable alternative to the ARP monitor when using
2328 ------------------------------------------------------
2344 +----------+ +----------+
2346 | Host A +---------------------+ router +------------------->
2347 | +---------------------+ | Hosts B and C are out
2349 +----------+ +----------+
2371 +----------+ +----------+ +--------+
2372 | |eth0 port1| +-------+ Host B |
2373 | Host A +------------+ switch |port3 +--------+
2374 | +------------+ | +--------+
2375 | |eth1 port2| +------------------+ Host C |
2376 +----------+ +----------+port4 +--------+
2399 -----------------------------------------------------------
2405 balance-rr:
2432 through the switch to a balance-rr bond will not utilize greater
2444 active-backup:
2446 the active-backup mode, as the inactive backup devices are all
2450 available bandwidth. On the plus side, active-backup mode
2455 balance-xor:
2465 As with balance-rr, the switch ports need to be configured for
2469 Like active-backup, there is not much advantage to this
2485 balance modes other than balance-rr, no single connection will
2498 Finally, the 802.3ad mode mandates the use of the MII monitor,
2499 therefore, the ARP monitor is not available in this mode.
2501 balance-tlb:
2502 The balance-tlb mode balances outgoing traffic by peer.
2508 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2518 monitor is not available.
2520 balance-alb:
2521 This mode is everything that balance-tlb is, and more.
2522 It has all of the features (and restrictions) of balance-tlb,
2532 ----------------------------------------------------
2536 support the use of the ARP monitor, and are thus restricted to using
2537 the MII monitor (which does not provide as high a level of end to end
2538 assurance as the ARP monitor).
2541 -----------------------------------------------------
2547 +-----------+
2549 +-+---+---+-+
2551 +--------+ | +---------+
2553 +------+---+ +-----+----+ +-----+----+
2555 +------+---+ +-----+----+ +-----+----+
2557 +--------+ | +---------+
2559 +-+---+---+-+
2561 +-----------+
2576 -------------------------------------------------------------
2579 configurations of this type is balance-rr. Historically, in this
2584 packets has arrived). When employed in this fashion, the balance-rr
2589 ------------------------------------------------------
2591 Again, in actual practice, the MII monitor is most often used
2593 availability. The ARP monitor will function in this topology, but its
2594 advantages over the MII monitor are mitigated by the volume of probes
2602 -------------------------------------------
2637 --------------------------------
2649 For example, on a bond in active-backup mode with five slaves
2652 # ping -n 10.0.4.2
2654 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms
2655 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2656 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2657 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2658 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2659 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms
2660 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms
2661 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms
2676 most Cisco switches, the privileged command "clear mac address-table
2687 --------------------
2692 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2697 --------------------------------
2700 integrated on the planar (that's "motherboard" in IBM-speak). In the
2703 An add-on Broadcom daughter card can be installed on a JS20 to provide
2712 Additional BladeCenter-specific networking information can be
2715 - "IBM eServer BladeCenter Networking Options"
2716 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2719 ------------------------------------
2744 -------------------------------
2746 The balance-rr mode requires the use of passthrough modules
2749 appropriate ports, as is usual for balance-rr.
2751 The balance-alb and balance-tlb modes will function with
2758 The active-backup mode has no additional requirements.
2761 ----------------------
2764 monitor will reliably detect link loss to an external switch. This is
2768 ports and the devices on the JS20 system itself. The MII monitor is
2771 When a passthrough module is in place, the MII monitor does
2776 --------------
2786 avoid fail-over delay issues when using bonding.
2793 -------------------
2799 -----------------------------------------
2801 Any Ethernet type cards (you can even mix cards - a Intel
2806 slaves in active-backup mode.
2809 ----------------------------------------
2814 ----------------------------------------------
2821 ----------------------------------------
2824 disabled. The active-backup mode will fail over to a backup link, and
2834 the underlying network device, and the arp monitor (arp_interval)
2844 ----------------------------------------------
2849 ---------------------------------------------
2853 In the basic balance modes (balance-rr and balance-xor), it
2858 The advanced balance modes (balance-tlb and balance-alb) do
2867 The active-backup mode should work with any Layer-II switch.
2870 ---------------------------------------------------------
2892 # ifconfig bond0 down ; modprobe -r bonding
2900 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2922 http://vger.kernel.org/vger-lists.html#netdev