Lines Matching refs:monitor
276 The ARP monitor works by periodically checking the slave
349 Enabling validation causes the ARP monitor to examine the incoming
372 ARP monitor into considering the links as still up. Use of
373 validation can resolve this, as the ARP monitor will only consider
379 Enabling filtering causes the ARP monitor to only use incoming ARP
391 ARP monitor into considering the links as still up. Use of
400 in order for the ARP monitor to consider a slave as being up.
420 is only valid for the miimon link monitor. The downdelay
452 interferes with the ARP monitor).
464 monitor, devices which assert link up prior to being
710 each link monitor interval (arp_interval or miimon, whichever
808 only valid for the miimon link monitor. The updelay value
1817 packets generated by either ALB mode or the ARP monitor mechanism, are
1865 monitoring a slave device's link state: the ARP monitor and the MII
1866 monitor.
1875 The ARP monitor operates as its name suggests: it sends ARP
1881 The ARP monitor relies on the device driver itself to verify
1885 ARP monitor will immediately fail any slaves using that driver, and
1895 monitor. In the case of just one target, the target itself may go
1916 The MII monitor monitors only the carrier state of the local
1923 then the MII monitor will rely on the driver for carrier state
1925 use_carrier parameter information, above, if the MII monitor fails to
1930 If use_carrier is 0, then the MII monitor will first query the
1933 monitor will make an ethtool ETHOOL_GLINK request to attempt to obtain
1936 and ethtool requests), then the MII monitor will assume the link is
1959 receive/transmit times in the driver (needed by the ARP monitor), but
1963 The ARP monitor (and ARP itself) may become confused by this
1964 configuration, because ARP requests (generated by the ARP monitor)
1968 interface basis), and is discarded. The MII monitor is not affected
2202 end, the MII monitor has no direct means to detect this. The ARP
2203 monitor could be configured with a target at the remote end of port3,
2207 monitor can provide a higher level of reliability in detecting end to
2210 the ARP monitor should be configured with multiple targets (at least
2212 regardless of which switch is active, the ARP monitor has a suitable
2220 to the logically "interior" ports that bonding is able to monitor via
2222 switch, but this can be a viable alternative to the ARP monitor when using
2394 Finally, the 802.3ad mode mandates the use of the MII monitor,
2395 therefore, the ARP monitor is not available in this mode.
2413 monitor is not available.
2430 support the use of the ARP monitor, and are thus restricted to using
2431 the MII monitor (which does not provide as high a level of end to end
2432 assurance as the ARP monitor).
2485 Again, in actual practice, the MII monitor is most often used
2487 availability. The ARP monitor will function in this topology, but its
2488 advantages over the MII monitor are mitigated by the volume of probes
2658 monitor will reliably detect link loss to an external switch. This is
2662 ports and the devices on the JS20 system itself. The MII monitor is
2665 When a passthrough module is in place, the MII monitor does
2723 the underlying network device, and the arp monitor (arp_interval)