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
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
574 occurs in active-backup mode, bonding will issue one
586 balance-xor or 2
614 regards to the packet mis-ordering requirements of
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
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
745 value is 0 which means to match the value of the link monitor
746 interval.
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
806 slaves based on the load in that interval. This gives nice lb
807 characteristics but can cause packet reordering. If re-ordering is
810 xmit-hash-policy can be used to select the appropriate hashing for
826 only valid for the miimon link monitor. The updelay value
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
963 the failover, subsequent packets are sent in each 200ms interval.
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"
1128 (bus-pci-0000:06:08.1 in the example above) specify the physical
1159 -------------------------------
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
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 -----------------------------------------------
1322 modprobe bonding mode=balance-alb miimon=100
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
1510 To enable MII monitoring on bond0 with a 1 second interval::
1517 monitoring is enabled, and vice-versa.
1530 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1532 To configure the interval between learning packet transmits::
1540 default interval is 1 second.
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)
1654 MII Polling Interval (ms): 0
1655 Up Delay (ms): 0
1656 Down Delay (ms): 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 ----------------------------------------------------------
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)
1772 MII Polling Interval (ms): 1000
1773 Up Delay (ms): 0
1774 Down Delay (ms): 0
1788 -------------------------
1831 The active-backup, balance-tlb and balance-alb modes do not
1842 The balance-rr, balance-xor and broadcast modes generally
1862 packets generated by either ALB mode or the ARP monitor mechanism, are
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
1910 monitoring a slave device's link state: the ARP monitor and the MII
1911 monitor.
1917 7.1 ARP Monitor Operation
1918 -------------------------
1920 The ARP monitor operates as its name suggests: it sends ARP
1926 The ARP monitor relies on the device driver itself to verify
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
1930 ARP monitor will immediately fail any slaves using that driver, and
1936 ------------------------------------
1940 monitor. In the case of just one target, the target itself may go
1958 7.3 MII Monitor Operation
1959 -------------------------
1961 The MII monitor monitors only the carrier state of the local
1968 then the MII monitor will rely on the driver for carrier state
1970 use_carrier parameter information, above, if the MII monitor fails to
1975 If use_carrier is 0, then the MII monitor will first query the
1978 monitor will make an ethtool ETHOOL_GLINK request to attempt to obtain
1981 and ethtool requests), then the MII monitor will assume the link is
1988 -------------------------
2004 receive/transmit times in the driver (needed by the ARP monitor), but
2008 The ARP monitor (and ARP itself) may become confused by this
2009 configuration, because ARP requests (generated by the ARP monitor)
2013 interface basis), and is discarded. The MII monitor is not affected
2023 ----------------------------
2034 options bond0 mode=some-mode miimon=50
2067 ---------------------------------------------------------
2079 some fixed interval. In this case, miimon will detect failures, but
2084 fixed interval, but does not cache the MII register values (so the
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 ----------------------------------------------------------------
2251 end, the MII monitor has no direct means to detect this. The ARP
2252 monitor could be configured with a target at the remote end of port3,
2256 monitor can provide a higher level of reliability in detecting end to
2259 the ARP monitor should be configured with multiple targets (at least
2261 regardless of which switch is active, the ARP monitor has a suitable
2269 to the logically "interior" ports that bonding is able to monitor via
2271 switch, but this can be a viable alternative to the ARP monitor when using
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
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
2448 Finally, the 802.3ad mode mandates the use of the MII monitor,
2449 therefore, the ARP monitor is not available in this mode.
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),
2468 monitor is not available.
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,
2482 ----------------------------------------------------
2486 support the use of the ARP monitor, and are thus restricted to using
2487 the MII monitor (which does not provide as high a level of end to end
2488 assurance as the ARP monitor).
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 ------------------------------------------------------
2541 Again, in actual practice, the MII monitor is most often used
2543 availability. The ARP monitor will function in this topology, but its
2544 advantages over the MII monitor are mitigated by the volume of probes
2552 -------------------------------------------
2587 --------------------------------
2599 For example, on a bond in active-backup mode with five slaves
2602 # ping -n 10.0.4.2
2604 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms
2605 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2606 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2607 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2608 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.8 ms (DUP!)
2609 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms
2610 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms
2611 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms
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 ----------------------
2714 monitor will reliably detect link loss to an external switch. This is
2718 ports and the devices on the JS20 system itself. The MII monitor is
2721 When a passthrough module is in place, the MII monitor does
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
2784 the underlying network device, and the arp monitor (arp_interval)
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.
2820 ---------------------------------------------------------
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