Lines Matching refs:miimon

153 	It is critical that either the miimon or arp_interval and
156 support at least miimon, so there is really no reason not to use it.
256 	miimon.  A value of 0 disables ARP monitoring.  The default
383 	is only valid for the miimon link monitor.  The downdelay
384 	value should be a multiple of the miimon value; if not, it
481 miimon
673 	each link monitor interval (arp_interval or miimon, whichever
771 	only valid for the miimon link monitor.  The updelay value
772 	should be a multiple of the miimon value; if not, it will be
777 	Specifies whether or not miimon should use MII or ETHTOOL
1032 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1209 options bond0 mode=balance-alb miimon=100
1263 modprobe bonding mode=balance-alb miimon=100
1331 options bond0 -o bond0 mode=balance-rr miimon=100
1334 options bond1 -o bond1 mode=balance-alb miimon=50
1338 miimon of 100.  The second instance is named "bond1" and creates the
1339 bond1 device in balance-alb mode with an miimon of 50.
1347 	mode=balance-alb miimon=50
1442 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1474 echo 100 > /sys/class/net/bond0/bonding/miimon
1516 	bond-miimon 100
1528 	bond-miimon 100
1636 driver is loaded with parameters of mode=0 and miimon=1000 is
1905 options bond0 mode=some-mode miimon=50
1950 some fixed interval.  In this case, miimon will detect failures, but
1952 miimon is very slow in detecting link failures, try specifying
1960 	Also, remember that miimon only checks for the device's
2137 miimon.  Availability and configuration for trunk failover varies by
2636 	Link monitoring can be enabled via either the miimon or
2638 above).  In general, miimon monitors the carrier state as sensed by