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 multicast. It is preferred to have the local-admin bit set for this
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.
284 The ARP monitor works by periodically checking the slave
319 non-ARP traffic should be filtered (disregarded) for link
357 Enabling validation causes the ARP monitor to examine the incoming
380 ARP monitor into considering the links as still up. Use of
381 validation can resolve this, as the ARP monitor will only consider
387 Enabling filtering causes the ARP monitor to only use incoming ARP
399 ARP monitor into considering the links as still up. Use of
408 in order for the ARP monitor to consider a slave as being up.
409 This option affects only active-backup mode for slaves with
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
460 interferes with the ARP monitor).
472 monitor, devices which assert link up prior to being
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
586 occurs in active-backup mode, bonding will issue one
598 balance-xor or 2
626 regards to the packet mis-ordering requirements of
642 balance-tlb or 5
664 balance-alb or 6
666 Adaptive load balancing: includes balance-tlb plus
694 and when an inactive slave is re-activated. The
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.
755 This delay should be a multiple of the link monitor interval
757 value is 0 which means to match the value of the link monitor
758 interval.
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
818 slaves based on the load in that interval. This gives nice lb
819 characteristics but can cause packet reordering. If re-ordering is
822 xmit-hash-policy can be used to select the appropriate hashing for
838 only valid for the miimon link monitor. The updelay value
867 balance-xor, 802.3ad, and tlb modes. Possible values are:
900 network peer on the same slave. For non-IP traffic,
932 information is omitted. For non-IP traffic, the
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.
988 the failover, subsequent packets are sent in each 200ms interval.
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
1074 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
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 -------------------------------
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 ------------------------------------------
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 -----------------------------------------------
1347 modprobe bonding mode=balance-alb miimon=100
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
1535 To enable MII monitoring on bond0 with a 1 second interval::
1542 monitoring is enabled, and vice-versa.
1555 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1557 To configure the interval between learning packet transmits::
1565 default interval is 1 second.
1568 ---------------------
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)
1679 MII Polling Interval (ms): 0
1680 Up Delay (ms): 0
1681 Down Delay (ms): 0
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 ----------------------------------------------------------
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)
1797 MII Polling Interval (ms): 1000
1798 Up Delay (ms): 0
1799 Down Delay (ms): 0
1813 -------------------------
1856 The active-backup, balance-tlb and balance-alb modes do not
1867 The balance-rr, balance-xor and broadcast modes generally
1887 packets generated by either ALB mode or the ARP monitor mechanism, are
1899 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1906 would pick up the all-zeroes hardware address. Once the first slave
1927 underlying device -- i.e. the bonding interface -- to promiscuous
1935 monitoring a slave device's link state: the ARP monitor and the MII
1936 monitor.
1942 7.1 ARP Monitor Operation
1943 -------------------------
1945 The ARP monitor operates as its name suggests: it sends ARP
1951 The ARP monitor relies on the device driver itself to verify
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
1955 ARP monitor will immediately fail any slaves using that driver, and
1961 ------------------------------------
1965 monitor. In the case of just one target, the target itself may go
1983 7.3 MII Monitor Operation
1984 -------------------------
1986 The MII monitor monitors only the carrier state of the local
1993 then the MII monitor will rely on the driver for carrier state
1995 use_carrier parameter information, above, if the MII monitor fails to
2000 If use_carrier is 0, then the MII monitor will first query the
2003 monitor will make an ethtool ETHTOOL_GLINK request to attempt to obtain
2006 and ethtool requests), then the MII monitor will assume the link is
2013 -------------------------
2029 receive/transmit times in the driver (needed by the ARP monitor), but
2033 The ARP monitor (and ARP itself) may become confused by this
2034 configuration, because ARP requests (generated by the ARP monitor)
2038 interface basis), and is discarded. The MII monitor is not affected
2048 ----------------------------
2059 options bond0 mode=some-mode miimon=50
2092 ---------------------------------------------------------
2104 some fixed interval. In this case, miimon will detect failures, but
2109 fixed interval, but does not cache the MII register values (so the
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 ----------------------------------------------------------------
2276 end, the MII monitor has no direct means to detect this. The ARP
2277 monitor could be configured with a target at the remote end of port3,
2281 monitor can provide a higher level of reliability in detecting end to
2284 the ARP monitor should be configured with multiple targets (at least
2286 regardless of which switch is active, the ARP monitor has a suitable
2294 to the logically "interior" ports that bonding is able to monitor via
2296 switch, but this can be a viable alternative to the ARP monitor when using
2303 ------------------------------------------------------
2319 +----------+ +----------+
2321 | Host A +---------------------+ router +------------------->
2322 | +---------------------+ | Hosts B and C are out
2324 +----------+ +----------+
2346 +----------+ +----------+ +--------+
2347 | |eth0 port1| +-------+ Host B |
2348 | Host A +------------+ switch |port3 +--------+
2349 | +------------+ | +--------+
2350 | |eth1 port2| +------------------+ Host C |
2351 +----------+ +----------+port4 +--------+
2374 -----------------------------------------------------------
2380 balance-rr:
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:
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
2473 Finally, the 802.3ad mode mandates the use of the MII monitor,
2474 therefore, the ARP monitor is not available in this mode.
2476 balance-tlb:
2477 The balance-tlb mode balances outgoing traffic by peer.
2483 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2493 monitor is not available.
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,
2507 ----------------------------------------------------
2511 support the use of the ARP monitor, and are thus restricted to using
2512 the MII monitor (which does not provide as high a level of end to end
2513 assurance as the ARP monitor).
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 ------------------------------------------------------
2566 Again, in actual practice, the MII monitor is most often used
2568 availability. The ARP monitor will function in this topology, but its
2569 advantages over the MII monitor are mitigated by the volume of probes
2577 -------------------------------------------
2612 --------------------------------
2624 For example, on a bond in active-backup mode with five slaves
2627 # ping -n 10.0.4.2
2629 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms
2630 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2631 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2632 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2633 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2634 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms
2635 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms
2636 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms
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 ----------------------
2739 monitor will reliably detect link loss to an external switch. This is
2743 ports and the devices on the JS20 system itself. The MII monitor is
2746 When a passthrough module is in place, the MII monitor does
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
2809 the underlying network device, and the arp monitor (arp_interval)
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.
2845 ---------------------------------------------------------
2867 # ifconfig bond0 down ; modprobe -r bonding
2875 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2897 http://vger.kernel.org/vger-lists.html#netdev