Lines Matching refs:monitoring

25 Additionally, link integrity monitoring may be performed.
274 	Specifies the ARP link monitoring frequency in milliseconds.
286 	If ARP monitoring is used in an etherchannel compatible mode
292 	fail.  ARP monitoring should not be used in conjunction with
293 	miimon.  A value of 0 disables ARP monitoring.  The default
298 	Specifies the IP addresses to use as ARP monitoring peers when
303 	address must be given for ARP monitoring to function.  The
310 	validated in any mode that supports arp monitoring, or whether
312 	monitoring purposes.
520 	Specifies the MII link monitoring frequency in milliseconds.
523 	link monitoring.  A value of 100 is a good starting point.
1097 for the bonding mode, link monitoring, and so on here.  Do not include
1478 To enable MII monitoring on bond0 with a 1 second interval:
1480 	NOTE: If ARP monitoring is enabled, it will disabled when MII
1481 monitoring is enabled, and vice-versa.
1516 active-backup mode, using ARP monitoring, add the following lines to
1865 monitoring a slave device's link state: the ARP monitor and the MII
1870 monitoring simultaneously.
1886 those slaves will stay down.  If networking monitoring (tcpdump, etc)
1893 	While ARP monitoring can be done with just one target, it can
1898 monitoring.
1902 # example options for ARP monitoring with three targets
1908 # example options for ARP monitoring with one target
2098 	When running network monitoring tools, e.g., tcpdump, it is
2140 support link monitoring of their members, so if individual links fail,
2198 	The choice of link monitoring ultimately depends upon your
2347 	load balancing mode (with link monitoring) will provide the
2428 	The choice of link monitoring may largely depend upon which
2654 Link monitoring issues
2712 	If link monitoring is enabled, then the failing device will be
2720 	Link monitoring can be enabled via either the miimon or
2726 	If no link monitoring is configured, the bonding driver will