Documentation/networking/bonding.rst

159 It is critical that either the miimon or arp_interval and
162 support at least miimon, so there is really no reason not to use it.
302 	miimon.  A value of 0 disables ARP monitoring.  The default
429 	is only valid for the miimon link monitor.  The downdelay
430 	value should be a multiple of the miimon value; if not, it
527 miimon
745 	(arp_interval or miimon, whichever is active). The default
827 	only valid for the miimon link monitor.  The updelay value
828 	should be a multiple of the miimon value; if not, it will be
833 	Specifies whether or not miimon should use MII or ETHTOOL
1088 	BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1269 	options bond0 mode=balance-alb miimon=100
1323 	modprobe bonding mode=balance-alb miimon=100
1391 	options bond0 -o bond0 mode=balance-rr miimon=100
1394 	options bond1 -o bond1 mode=balance-alb miimon=50
1398 miimon of 100.  The second instance is named "bond1" and creates the
1399 bond1 device in balance-alb mode with an miimon of 50.
1407 				     mode=balance-alb miimon=50
1513 	# echo 1000 > /sys/class/net/bond0/bonding/miimon
1557 	echo 100 > /sys/class/net/bond0/bonding/miimon
1599 		bond-miimon 100
1611 		bond-miimon 100
1766 driver is loaded with parameters of mode=0 and miimon=1000 is
2035 	options bond0 mode=some-mode miimon=50
2080 some fixed interval.  In this case, miimon will detect failures, but
2082 miimon is very slow in detecting link failures, try specifying
2090 Also, remember that miimon only checks for the device's
2271 miimon.  Availability and configuration for trunk failover varies by
2782 Link monitoring can be enabled via either the miimon or
2784 above).  In general, miimon monitors the carrier state as sensed by