Sachi King 18fc512fc4 Bond: Monitor bond mii_status not link operstate (#1124) ... With a bond interface the state of the slave interface from the bond's point of view is reflected in `mii_status` and is independent of the link's `operstate`. When a bond is monitored with `miimon`, `mii_status` will reflect the state of the physical link as configured via the operator. When a bond is monitored via `arp_interval` the `mii_status` will reflect the results of the bond ARP checking. This means the link can be down from the bond's point of view, but up from a physical connection point of view. If a bond is not monitored via miimon or arp, the `mii_status` should likely be always `up`, however I have observed a case where this is not true and the `operstate` is `up` while `mii_status` is `down`. Kernel bond documentation stresses that a bond should not be configured without one of `mii_mon` or `arp_interval` configured however. This change results in the metric 'node_bonding_active' matching the up/down state of the bond's point of view rather than operstate. Signed-off-by: Sachi King <nakato@nakato.io>		2019-02-10 11:00:04 +01:00
..
proc	Update diskstats for linux kernel 4.19 (#1109)	2018-10-15 17:24:28 +02:00
qdisc	Add qdisc collector for Linux (#580)	2017-05-23 11:55:50 +02:00
textfile	Treat custom textfile metric timestamps as errors (#769)	2018-02-27 19:43:38 +01:00
wifi	Update wifi stats to support multiple stations (#977) (#980)	2018-07-16 16:02:25 +02:00
e2e-64k-page-output.txt	netclass_linux: remove varying labels from the 'up' metric (#1243)	2019-02-07 15:59:32 +01:00
e2e-output.txt	netclass_linux: remove varying labels from the 'up' metric (#1243)	2019-02-07 15:59:32 +01:00
ip_vs_result.txt	Rearrange fixtures to match "real" proc and sys.	2015-09-28 13:56:22 +00:00
sys.ttar	Bond: Monitor bond mii_status not link operstate (#1124)	2019-02-10 11:00:04 +01:00