mirror of
https://github.com/prometheus/node_exporter.git
synced 2024-11-25 14:27:21 +01:00
18fc512fc4
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> |
||
|---|---|---|
| .. | ||
| proc | ||
| qdisc | ||
| textfile | ||
| wifi | ||
| e2e-64k-page-output.txt | ||
| e2e-output.txt | ||
| ip_vs_result.txt | ||
| sys.ttar | ||