Lines Matching refs:monitoring

25 Additionally, link integrity monitoring may be performed.
237 	Specifies the ARP link monitoring frequency in milliseconds.
249 	If ARP monitoring is used in an etherchannel compatible mode
255 	fail.  ARP monitoring should not be used in conjunction with
256 	miimon.  A value of 0 disables ARP monitoring.  The default
261 	Specifies the IP addresses to use as ARP monitoring peers when
266 	address must be given for ARP monitoring to function.  The
273 	validated in any mode that supports arp monitoring, or whether
275 	monitoring purposes.
483 	Specifies the MII link monitoring frequency in milliseconds.
486 	link monitoring.  A value of 100 is a good starting point.
1060 for the bonding mode, link monitoring, and so on here.  Do not include
1441 To enable MII monitoring on bond0 with a 1 second interval:
1443 	NOTE: If ARP monitoring is enabled, it will disabled when MII
1444 monitoring is enabled, and vice-versa.
1479 active-backup mode, using ARP monitoring, add the following lines to
1781 monitoring a slave device's link state: the ARP monitor and the MII
1786 monitoring simultaneously.
1802 those slaves will stay down.  If networking monitoring (tcpdump, etc)
1809 	While ARP monitoring can be done with just one target, it can
1814 monitoring.
1818 # example options for ARP monitoring with three targets
1824 # example options for ARP monitoring with one target
2014 	When running network monitoring tools, e.g., tcpdump, it is
2056 support link monitoring of their members, so if individual links fail,
2114 	The choice of link monitoring ultimately depends upon your
2263 	load balancing mode (with link monitoring) will provide the
2344 	The choice of link monitoring may largely depend upon which
2570 Link monitoring issues
2628 	If link monitoring is enabled, then the failing device will be
2636 	Link monitoring can be enabled via either the miimon or
2642 	If no link monitoring is configured, the bonding driver will