2016-08-24 08:12:20 +01:00
|
|
|
source: Extensions/RRDTune.md
|
2018-10-27 23:04:34 +01:00
|
|
|
path: blob/master/doc/
|
2015-11-18 21:52:32 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
# RRDTune
|
|
|
|
|
|
|
|
|
|
When we create rrd files for ports, we currently do so with a max
|
|
|
|
|
value of 12500000000 (100G). Because of this if a device sends us bad
|
|
|
|
|
data back then it can appear as though a 100M port is doing 40G+ which
|
|
|
|
|
is impossible. To counter this you can enable the rrdtool tune option
|
|
|
|
|
which will fix the max value to the interfaces physical speed (minimum
|
|
|
|
|
of 10M).
|
2015-11-18 21:52:32 +00:00
|
|
|
|
|
|
|
|
To enable this you can do so in three ways!
|
|
|
|
|
|
2020-04-02 12:02:36 +02:00
|
|
|
- Globally under Global Settings -> Poller -> Datastore: RRDTool
|
2019-09-09 05:48:35 -05:00
|
|
|
- For the actual device, Edit Device -> Misc
|
|
|
|
|
- For each port, Edit Device -> Port Settings
|
2015-11-18 21:52:32 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
Now when a port interface speed changes (this can happen because of a
|
|
|
|
|
physical change or just because the device has misreported) the max
|
|
|
|
|
value is set. If you don't want to wait until a port speed changes
|
|
|
|
|
then you can run the included script:
|
2015-11-18 21:52:32 +00:00
|
|
|
|
2017-02-07 00:49:16 +00:00
|
|
|
`./scripts/tune_port.php -h <hostname> -p <ifName>`
|
2015-11-18 21:52:32 +00:00
|
|
|
|
|
|
|
|
Wildcards are supported using *, i.e:
|
|
|
|
|
|
2017-02-07 00:49:16 +00:00
|
|
|
`./scripts/tune_port.php -h local* -p eth*`
|
2015-11-18 21:52:32 +00:00
|
|
|
|
2019-09-09 05:48:35 -05:00
|
|
|
This script will then perform the rrdtool tune on each port found
|
|
|
|
|
using the provided ifSpeed for that port.
|
2017-02-07 00:49:16 +00:00
|
|
|
|
|
|
|
|
Run `./scripts/tune_port.php` to see help page.
|
