Lines Matching refs:miimon

154 	It is critical that either the miimon or arp_interval and
157 support at least miimon, so there is really no reason not to use it.
293 	miimon.  A value of 0 disables ARP monitoring.  The default
420 	is only valid for the miimon link monitor.  The downdelay
421 	value should be a multiple of the miimon value; if not, it
518 miimon
710 	each link monitor interval (arp_interval or miimon, whichever
808 	only valid for the miimon link monitor.  The updelay value
809 	should be a multiple of the miimon value; if not, it will be
814 	Specifies whether or not miimon should use MII or ETHTOOL
1069 BONDING_MODULE_OPTS="mode=active-backup miimon=100"
1246 options bond0 mode=balance-alb miimon=100
1300 modprobe bonding mode=balance-alb miimon=100
1368 options bond0 -o bond0 mode=balance-rr miimon=100
1371 options bond1 -o bond1 mode=balance-alb miimon=50
1375 miimon of 100.  The second instance is named "bond1" and creates the
1376 bond1 device in balance-alb mode with an miimon of 50.
1384 	mode=balance-alb miimon=50
1479 # echo 1000 > /sys/class/net/bond0/bonding/miimon
1511 echo 100 > /sys/class/net/bond0/bonding/miimon
1553 	bond-miimon 100
1565 	bond-miimon 100
1720 driver is loaded with parameters of mode=0 and miimon=1000 is
1989 options bond0 mode=some-mode miimon=50
2034 some fixed interval.  In this case, miimon will detect failures, but
2036 miimon is very slow in detecting link failures, try specifying
2044 	Also, remember that miimon only checks for the device's
2221 miimon.  Availability and configuration for trunk failover varies by
2720 	Link monitoring can be enabled via either the miimon or
2722 above).  In general, miimon monitors the carrier state as sensed by