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
320 non-ARP traffic should be filtered (disregarded) for link
358 Enabling validation causes the ARP monitor to examine the incoming
381 ARP monitor into considering the links as still up. Use of
382 validation can resolve this, as the ARP monitor will only consider
388 Enabling filtering causes the ARP monitor to only use incoming ARP
400 ARP monitor into considering the links as still up. Use of
409 in order for the ARP monitor to consider a slave as being up.
410 This option affects only active-backup mode for slaves with
429 is only valid for the miimon link monitor. The downdelay
436 Specifies whether active-backup mode should set all slaves to
446 bonding to set all slaves of an active-backup bond to
461 interferes with the ARP monitor).
473 monitor, devices which assert link up prior to being
540 asserting carrier. It is similar to the Cisco EtherChannel min-links
542 must be up (link-up state) before marking the bond device as up
557 balance-rr (round robin). Possible values are:
559 balance-rr or 0
561 Round-robin policy: Transmit packets in sequential
566 active-backup or 1
568 Active-backup policy: Only one slave in the bond is
575 occurs in active-backup mode, bonding will issue one
587 balance-xor or 2
615 regards to the packet mis-ordering requirements of
631 balance-tlb or 5
653 balance-alb or 6
655 Adaptive load balancing: includes balance-tlb plus
683 and when an inactive slave is re-activated. The
718 bonding device and each VLAN sub-device. This is repeated at
722 The valid range is 0 - 255; the default value is 1. These options
723 affect only the active-backup mode. These options were added for
736 The valid range is 0 - 65535; the default value is 1. This option
737 has effect only in balance-rr mode.
744 This delay should be a multiple of the link monitor interval
746 value is 0 which means to match the value of the link monitor
747 interval.
754 off-line will alternate devices be used. This is useful when
758 The primary option is only valid for active-backup(1),
759 balance-tlb (5) and balance-alb (6) mode.
766 occurs. This option is designed to prevent flip-flopping between
807 slaves based on the load in that interval. This gives nice lb
808 characteristics but can cause packet reordering. If re-ordering is
811 xmit-hash-policy can be used to select the appropriate hashing for
827 only valid for the miimon link monitor. The updelay value
856 balance-xor, 802.3ad, and tlb modes. Possible values are:
889 network peer on the same slave. For non-IP traffic,
921 information is omitted. For non-IP traffic, the
964 the failover, subsequent packets are sent in each 200ms interval.
966 The valid range is 0 - 255; the default value is 1. A value of 0
970 This option is useful for bonding modes balance-rr (0), active-backup
971 (1), balance-tlb (5) and balance-alb (6), in which a failover can
983 The valid range is 1 - 0x7fffffff; the default value is 1. This Option
984 has effect only in balance-tlb and balance-alb modes.
1012 $ rpm -qf /sbin/ifup
1027 ----------------------------------------
1040 ifcfg-id file for each slave device. The simplest way to accomplish
1042 file ifcfg-id file created; see below for some issues with DHCP). The
1045 ifcfg-id-xx:xx:xx:xx:xx:xx
1050 Once the set of ifcfg-id-xx:xx:xx:xx:xx:xx files has been
1060 _nm_name='bus-pci-0001:61:01.0'
1070 Once the ifcfg-id-xx:xx:xx:xx:xx:xx files have been modified,
1072 itself. This file is named ifcfg-bondX, where X is the number of the
1074 ifcfg-bond0, the second is ifcfg-bond1, and so on. The sysconfig
1078 The contents of the ifcfg-bondX file is as follows::
1088 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1090 BONDING_SLAVE1="bus-pci-0000:06:08.1"
1129 (bus-pci-0000:06:08.1 in the example above) specify the physical
1160 -------------------------------
1170 -----------------------------------------------
1174 bonding instance to have an appropriately configured ifcfg-bondX file
1178 ifcfg-bondX files.
1181 options in the ifcfg-bondX file, it is not necessary to add them to
1185 ------------------------------------------
1198 network-script file for all physical adapters that will be members of
1201 /etc/sysconfig/network-scripts
1203 The file name must be prefixed with "ifcfg-eth" and suffixed
1205 for eth0 would be named /etc/sysconfig/network-scripts/ifcfg-eth0.
1216 must correspond with the name of the file, i.e., ifcfg-eth1 must have
1224 script will be /etc/sysconfig/network-scripts/ifcfg-bondX where X is
1225 the number of the bond. For bond0 the file is named "ifcfg-bond0",
1226 for bond1 it is named "ifcfg-bond1", and so on. Within that file,
1243 and, indeed, preferable, to specify the bonding options in the ifcfg-bond0
1246 BONDING_OPTS="mode=active-backup arp_interval=60 arp_ip_target=192.168.1.254"
1269 options bond0 mode=balance-alb miimon=100
1279 ---------------------------------
1292 -------------------------------------------------
1296 specifying the appropriate BONDING_OPTS= in ifcfg-bondX where X is the
1304 -----------------------------------------------
1323 modprobe bonding mode=balance-alb miimon=100
1346 enabled without re-running the entire global init script.
1362 -----------------------------------------
1391 options bond0 -o bond0 mode=balance-rr miimon=100
1394 options bond1 -o bond1 mode=balance-alb miimon=50
1397 named "bond0" and creates the bond0 device in balance-rr mode with an
1399 bond1 device in balance-alb mode with an miimon of 50.
1406 install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
1407 mode=balance-alb miimon=50
1413 to rename modules at load time (the "-o bond1" part). Attempts to pass
1421 ------------------------------------------
1441 -----------------------------
1448 # echo -bar > /sys/class/net/bonding_masters
1461 --------------------------
1473 # echo -eth0 > /sys/class/net/bond0/bonding/slaves
1482 # echo -eth0 > /sys/class/net/eth0/master/bonding/slaves
1487 -------------------------------
1491 The names of these files correspond directly with the command-
1500 To configure bond0 for balance-alb mode::
1504 - or -
1505 # echo balance-alb > /sys/class/net/bond0/bonding/mode
1511 To enable MII monitoring on bond0 with a 1 second interval::
1518 monitoring is enabled, and vice-versa.
1531 # echo -192.168.0.100 > /sys/class/net/bond0/bonding/arp_ip_target
1533 To configure the interval between learning packet transmits::
1541 default interval is 1 second.
1544 ---------------------
1555 echo balance-alb > /sys/class/net/bond0/bonding/mode
1562 active-backup mode, using ARP monitoring, add the following lines to
1567 echo active-backup > /sys/class/net/bond1/bonding/mode
1575 -----------------------------------------
1582 the box. The ifenslave-2.6 package should be installed to provide bonding
1583 support. Once installed, this package will provide ``bond-*`` options
1586 Note that ifenslave-2.6 package will load the bonding module and use
1590 ----------------------
1593 active-backup mode, with eth0 and eth1 as slaves::
1597 bond-slaves eth0 eth1
1598 bond-mode active-backup
1599 bond-miimon 100
1600 bond-primary eth0 eth1
1609 bond-slaves none
1610 bond-mode active-backup
1611 bond-miimon 100
1615 bond-master bond0
1616 bond-primary eth0 eth1
1620 bond-master bond0
1621 bond-primary eth0 eth1
1623 For a full list of ``bond-*`` supported options in /etc/network/interfaces and
1625 /usr/share/doc/ifenslave-2.6.
1628 ----------------------------------------------
1651 Bonding Mode: fault-tolerance (active-backup)
1655 MII Polling Interval (ms): 0
1656 Up Delay (ms): 0
1657 Down Delay (ms): 0
1702 a pass-through for selecting output queues on the slave device rather than
1706 output slave selection was limited to round-robin and active-backup modes.
1709 ----------------------------------------------------------
1725 (a) ad_actor_system : You can set a random mac-address that can be used for
1727 Also it's preferable to set the local-admin bit. Following shell code
1728 generates a random mac-address as described above::
1740 is 65535, but system can take the value from 1 - 65535. Following shell
1746 (c) ad_user_port_key : Use the user portion of the port-key. The default
1747 keeps this empty. These are the upper 10 bits of the port-key and value
1748 ranges from 0 - 1023. Following shell code generates these 10 bits and
1759 -------------------------
1761 Each bonding device has a read-only file residing in the
1770 Bonding Mode: load balancing (round-robin)
1773 MII Polling Interval (ms): 1000
1774 Up Delay (ms): 0
1775 Down Delay (ms): 0
1789 -------------------------
1832 The active-backup, balance-tlb and balance-alb modes do not
1843 The balance-rr, balance-xor and broadcast modes generally
1863 packets generated by either ALB mode or the ARP monitor mechanism, are
1875 "un-accelerated" by the bonding driver so the VLAN tag sits in the
1882 would pick up the all-zeroes hardware address. Once the first slave
1903 underlying device -- i.e. the bonding interface -- to promiscuous
1911 monitoring a slave device's link state: the ARP monitor and the MII
1912 monitor.
1918 7.1 ARP Monitor Operation
1919 -------------------------
1921 The ARP monitor operates as its name suggests: it sends ARP
1927 The ARP monitor relies on the device driver itself to verify
1929 date the last receive time, dev->last_rx. Drivers that use NETIF_F_LLTX
1930 flag must also update netdev_queue->trans_start. If they do not, then the
1931 ARP monitor will immediately fail any slaves using that driver, and
1937 ------------------------------------
1941 monitor. In the case of just one target, the target itself may go
1959 7.3 MII Monitor Operation
1960 -------------------------
1962 The MII monitor monitors only the carrier state of the local
1969 then the MII monitor will rely on the driver for carrier state
1971 use_carrier parameter information, above, if the MII monitor fails to
1976 If use_carrier is 0, then the MII monitor will first query the
1979 monitor will make an ethtool ETHOOL_GLINK request to attempt to obtain
1982 and ethtool requests), then the MII monitor will assume the link is
1989 -------------------------
2005 receive/transmit times in the driver (needed by the ARP monitor), but
2009 The ARP monitor (and ARP itself) may become confused by this
2010 configuration, because ARP requests (generated by the ARP monitor)
2014 interface basis), and is discarded. The MII monitor is not affected
2024 ----------------------------
2035 options bond0 mode=some-mode miimon=50
2068 ---------------------------------------------------------
2080 some fixed interval. In this case, miimon will detect failures, but
2085 fixed interval, but does not cache the MII register values (so the
2153 For the balance-rr, balance-xor, broadcast, and 802.3ad modes,
2156 For the active-backup, balance-tlb and balance-alb modes, the
2159 For balance-tlb mode, the active slave is the slave currently
2162 For balance-alb mode, the active slave is the slave used as a
2163 "primary." This slave is used for mode-specific control traffic, for
2166 For the active-backup, balance-tlb and balance-alb modes, when
2181 --------------------------------------------------
2195 ----------------------------------------------------
2206 +-----+----+ +-----+----+
2208 | switch A +--------------------------+ switch B |
2210 +-----+----+ +-----++---+
2212 | +-------+ |
2213 +-------------+ host1 +---------------+
2214 eth0 +-------+ eth1
2222 -------------------------------------------------------------
2224 In a topology such as the example above, the active-backup and
2229 active-backup:
2242 necessary for some specific one-way traffic to reach both
2246 ----------------------------------------------------------------
2252 end, the MII monitor has no direct means to detect this. The ARP
2253 monitor could be configured with a target at the remote end of port3,
2257 monitor can provide a higher level of reliability in detecting end to
2260 the ARP monitor should be configured with multiple targets (at least
2262 regardless of which switch is active, the ARP monitor has a suitable
2270 to the logically "interior" ports that bonding is able to monitor via
2272 switch, but this can be a viable alternative to the ARP monitor when using
2279 ------------------------------------------------------
2295 +----------+ +----------+
2297 | Host A +---------------------+ router +------------------->
2298 | +---------------------+ | Hosts B and C are out
2300 +----------+ +----------+
2322 +----------+ +----------+ +--------+
2323 | |eth0 port1| +-------+ Host B |
2324 | Host A +------------+ switch |port3 +--------+
2325 | +------------+ | +--------+
2326 | |eth1 port2| +------------------+ Host C |
2327 +----------+ +----------+port4 +--------+
2350 -----------------------------------------------------------
2356 balance-rr:
2383 through the switch to a balance-rr bond will not utilize greater
2395 active-backup:
2397 the active-backup mode, as the inactive backup devices are all
2401 available bandwidth. On the plus side, active-backup mode
2406 balance-xor:
2416 As with balance-rr, the switch ports need to be configured for
2420 Like active-backup, there is not much advantage to this
2436 balance modes other than balance-rr, no single connection will
2449 Finally, the 802.3ad mode mandates the use of the MII monitor,
2450 therefore, the ARP monitor is not available in this mode.
2452 balance-tlb:
2453 The balance-tlb mode balances outgoing traffic by peer.
2459 manner (not a simple XOR as in balance-xor or 802.3ad mode),
2469 monitor is not available.
2471 balance-alb:
2472 This mode is everything that balance-tlb is, and more.
2473 It has all of the features (and restrictions) of balance-tlb,
2483 ----------------------------------------------------
2487 support the use of the ARP monitor, and are thus restricted to using
2488 the MII monitor (which does not provide as high a level of end to end
2489 assurance as the ARP monitor).
2492 -----------------------------------------------------
2498 +-----------+
2500 +-+---+---+-+
2502 +--------+ | +---------+
2504 +------+---+ +-----+----+ +-----+----+
2506 +------+---+ +-----+----+ +-----+----+
2508 +--------+ | +---------+
2510 +-+---+---+-+
2512 +-----------+
2527 -------------------------------------------------------------
2530 configurations of this type is balance-rr. Historically, in this
2535 packets has arrived). When employed in this fashion, the balance-rr
2540 ------------------------------------------------------
2542 Again, in actual practice, the MII monitor is most often used
2544 availability. The ARP monitor will function in this topology, but its
2545 advantages over the MII monitor are mitigated by the volume of probes
2553 -------------------------------------------
2588 --------------------------------
2600 For example, on a bond in active-backup mode with five slaves
2603 # ping -n 10.0.4.2
2605 64 bytes from 10.0.4.2: icmp_seq=1 ttl=64 time=13.7 ms
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=1 ttl=64 time=13.8 ms (DUP!)
2610 64 bytes from 10.0.4.2: icmp_seq=2 ttl=64 time=0.216 ms
2611 64 bytes from 10.0.4.2: icmp_seq=3 ttl=64 time=0.267 ms
2612 64 bytes from 10.0.4.2: icmp_seq=4 ttl=64 time=0.222 ms
2627 most Cisco switches, the privileged command "clear mac address-table
2638 --------------------
2643 balance-rr, active-backup, balance-tlb and balance-alb modes. This is
2648 --------------------------------
2651 integrated on the planar (that's "motherboard" in IBM-speak). In the
2654 An add-on Broadcom daughter card can be installed on a JS20 to provide
2663 Additional BladeCenter-specific networking information can be
2666 - "IBM eServer BladeCenter Networking Options"
2667 - "IBM eServer BladeCenter Layer 2-7 Network Switching"
2670 ------------------------------------
2695 -------------------------------
2697 The balance-rr mode requires the use of passthrough modules
2700 appropriate ports, as is usual for balance-rr.
2702 The balance-alb and balance-tlb modes will function with
2709 The active-backup mode has no additional requirements.
2712 ----------------------
2715 monitor will reliably detect link loss to an external switch. This is
2719 ports and the devices on the JS20 system itself. The MII monitor is
2722 When a passthrough module is in place, the MII monitor does
2727 --------------
2737 avoid fail-over delay issues when using bonding.
2744 -------------------
2750 -----------------------------------------
2752 Any Ethernet type cards (you can even mix cards - a Intel
2757 slaves in active-backup mode.
2760 ----------------------------------------
2765 ----------------------------------------------
2772 ----------------------------------------
2775 disabled. The active-backup mode will fail over to a backup link, and
2785 the underlying network device, and the arp monitor (arp_interval)
2795 ----------------------------------------------
2800 ---------------------------------------------
2804 In the basic balance modes (balance-rr and balance-xor), it
2809 The advanced balance modes (balance-tlb and balance-alb) do
2818 The active-backup mode should work with any Layer-II switch.
2821 ---------------------------------------------------------
2843 # ifconfig bond0 down ; modprobe -r bonding
2851 from the bond (``ifenslave -d bond0 eth0``). The bonding driver will
2873 http://vger.kernel.org/vger-lists.html#netdev