Lines Matching refs:miimon

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
451 	is only valid for the miimon link monitor.  The downdelay
452 	value should be a multiple of the miimon value; if not, it
561 miimon
779 	(arp_interval or miimon, whichever is active). The default
872 	only valid for the miimon link monitor.  The updelay value
873 	should be a multiple of the miimon value; if not, it will be
878 	Specifies whether or not miimon should use MII or ETHTOOL
1146 	BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1327 	options bond0 mode=balance-alb miimon=100
1381 	modprobe bonding mode=balance-alb miimon=100
1449 	options bond0 -o bond0 mode=balance-rr miimon=100
1452 	options bond1 -o bond1 mode=balance-alb miimon=50
1456 miimon of 100.  The second instance is named "bond1" and creates the
1457 bond1 device in balance-alb mode with an miimon of 50.
1465 				     mode=balance-alb miimon=50
1571 	# echo 1000 > /sys/class/net/bond0/bonding/miimon
1615 	echo 100 > /sys/class/net/bond0/bonding/miimon
1657 		bond-miimon 100
1669 		bond-miimon 100
1824 driver is loaded with parameters of mode=0 and miimon=1000 is
2084 	options bond0 mode=some-mode miimon=50
2129 some fixed interval.  In this case, miimon will detect failures, but
2131 miimon is very slow in detecting link failures, try specifying
2139 Also, remember that miimon only checks for the device's
2320 miimon.  Availability and configuration for trunk failover varies by
2831 Link monitoring can be enabled via either the miimon or
2833 above).  In general, miimon monitors the carrier state as sensed by