Lines Matching refs:monitor

239 	The ARP monitor works by periodically checking the slave
312 	Enabling validation causes the ARP monitor to examine the incoming
335 	ARP monitor into considering the links as still up.  Use of
336 	validation can resolve this, as the ARP monitor will only consider
342 	Enabling filtering causes the ARP monitor to only use incoming ARP
354 	ARP monitor into considering the links as still up.  Use of
363 	in order for the ARP monitor to consider a slave as being up.
383 	is only valid for the miimon link monitor.  The downdelay
415 		interferes with the ARP monitor).
427 		monitor, devices which assert link up prior to being
673 	each link monitor interval (arp_interval or miimon, whichever
771 	only valid for the miimon link monitor.  The updelay value
1733 packets generated by either ALB mode or the ARP monitor mechanism, are
1781 monitoring a slave device's link state: the ARP monitor and the MII
1782 monitor.
1791 	The ARP monitor operates as its name suggests: it sends ARP
1797 	The ARP monitor relies on the device driver itself to verify
1801 ARP monitor will immediately fail any slaves using that driver, and
1811 monitor.  In the case of just one target, the target itself may go
1832 	The MII monitor monitors only the carrier state of the local
1839 then the MII monitor will rely on the driver for carrier state
1841 use_carrier parameter information, above, if the MII monitor fails to
1846 	If use_carrier is 0, then the MII monitor will first query the
1849 monitor will make an ethtool ETHOOL_GLINK request to attempt to obtain
1852 and ethtool requests), then the MII monitor will assume the link is
1875 receive/transmit times in the driver (needed by the ARP monitor), but
1879 	The ARP monitor (and ARP itself) may become confused by this
1880 configuration, because ARP requests (generated by the ARP monitor)
1884 interface basis), and is discarded.  The MII monitor is not affected
2118 end, the MII monitor has no direct means to detect this.  The ARP
2119 monitor could be configured with a target at the remote end of port3,
2123 monitor can provide a higher level of reliability in detecting end to
2126 the ARP monitor should be configured with multiple targets (at least
2128 regardless of which switch is active, the ARP monitor has a suitable
2136 to the logically "interior" ports that bonding is able to monitor via
2138 switch, but this can be a viable alternative to the ARP monitor when using
2310 	Finally, the 802.3ad mode mandates the use of the MII monitor,
2311 	therefore, the ARP monitor is not available in this mode.
2329 	monitor is not available.
2346 support the use of the ARP monitor, and are thus restricted to using
2347 the MII monitor (which does not provide as high a level of end to end
2348 assurance as the ARP monitor).
2401 	Again, in actual practice, the MII monitor is most often used
2403 availability.  The ARP monitor will function in this topology, but its
2404 advantages over the MII monitor are mitigated by the volume of probes
2574 monitor will reliably detect link loss to an external switch.  This is
2578 ports and the devices on the JS20 system itself.  The MII monitor is
2581 	When a passthrough module is in place, the MII monitor does
2639 the underlying network device, and the arp monitor (arp_interval)