MRTG graphs are in bytes instead of bits
I started using mrtg to graph traffic over a 1 Gbps point-to-point link to a DR site. It is currently being monitored using cricket. When comparing the mrtg graph to the cricket graphs, the mrtg graph seems to be in bytes/second instead of bits/second. The y-axis label says bits/second but the values are way to small.
This is the configuration for the switch port.
CA to AZ P2P
Directory[mrtg.ca-coresw.gi_1_1_1]: ca2az-p2p.lereta.net Target[mrtg.ca-coresw.gi_1_1_1]: 1:ROcommunity at ca-coresw.lereta.net Options[mrtg.ca-coresw.gi_1_1_1]: bits Title[mrtg.ca-coresw.gi_1_1_1]: P2P to AZ MaxBytes[mrtg.ca-coresw.gi_1_1_1]: 125000000
I haven't used mrtg in years so I may be just screwing up the configuration. Any help is appreciated.
-- Stephen Carville
Stephen, not sure what this has to do with Xymon.
On Wed, 24 Apr 2019 at 03:01, Stephen Carville (xymon list) < scarville at lereta.com> wrote:
I started using mrtg to graph traffic over a 1 Gbps point-to-point link to a DR site. It is currently being monitored using cricket. When comparing the mrtg graph to the cricket graphs, the mrtg graph seems to be in bytes/second instead of bits/second. The y-axis label says bits/second but the values are way to small.
This is the configuration for the switch port.
CA to AZ P2P
Directory[mrtg.ca-coresw.gi_1_1_1]: ca2az-p2p.lereta.net Target[mrtg.ca-coresw.gi_1_1_1]: 1:ROcommunity at ca-coresw.lereta.net Options[mrtg.ca-coresw.gi_1_1_1]: bits Title[mrtg.ca-coresw.gi_1_1_1]: P2P to AZ MaxBytes[mrtg.ca-coresw.gi_1_1_1]: 125000000
I haven't used mrtg in years so I may be just screwing up the configuration. Any help is appreciated.
-- Stephen Carville
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On 4/25/19 3:58 PM, Jeremy Laidman wrote:
Stephen, not sure what this has to do with Xymon.
I followed the instructions here:
http://xymon.sourceforge.net/xymon/help/xymon-mrtg.html
From that it looks to me like mrtg gathers the data, puts in in the rrd file, then XYMon invokes rrdtool to create the graphs. I was hoping there was something I overlooked -- and someone else can see -- in the config that would explain the difference.
Not really a big deal. It may be better to just divorce mrtg and XYMon. Or I could rewrite the "broken" parts of cricket so it works on a 64 bits. I just liked the idea of it all being in one place.
On Wed, 24 Apr 2019 at 03:01, Stephen Carville (xymon list) < scarville at lereta.com> wrote:
I started using mrtg to graph traffic over a 1 Gbps point-to-point link to a DR site. It is currently being monitored using cricket. When comparing the mrtg graph to the cricket graphs, the mrtg graph seems to be in bytes/second instead of bits/second. The y-axis label says bits/second but the values are way to small.
This is the configuration for the switch port.
CA to AZ P2P
Directory[mrtg.ca-coresw.gi_1_1_1]: ca2az-p2p.lereta.net Target[mrtg.ca-coresw.gi_1_1_1]: 1:ROcommunity at ca-coresw.lereta.net Options[mrtg.ca-coresw.gi_1_1_1]: bits Title[mrtg.ca-coresw.gi_1_1_1]: P2P to AZ MaxBytes[mrtg.ca-coresw.gi_1_1_1]: 125000000
I haven't used mrtg in years so I may be just screwing up the configuration. Any help is appreciated.
-- Stephen Carville
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
On Fri, 26 Apr 2019 at 09:30, Stephen Carville (xymon list) < scarville at lereta.com> wrote:
On 4/25/19 3:58 PM, Jeremy Laidman wrote:
Stephen, not sure what this has to do with Xymon.
I followed the instructions here:
Ah, it was news to me that this even existed! (Or maybe I just forgot.)
From that it looks to me like mrtg gathers the data, puts in in the rrd file, then XYMon invokes rrdtool to create the graphs.
Yep, that's how I read it too.
I was hoping
there was something I overlooked -- and someone else can see -- in the config that would explain the difference.
Nothing stands out to me. However, it's been over a decade since I did anything with MRTG.
Not really a big deal. It may be better to just divorce mrtg and XYMon.
Or I could rewrite the "broken" parts of cricket so it works on a 64 bits. I just liked the idea of it all being in one place.
Agreed - it's annoying having all your data in different places.
First, I would check the RRD file contents (rrdtool fetch yada yada) to see if the numbers look like those from Cricket data. If they don't match, then MRTG probably needs a tweak.
Also check that the RRD file shows the values as COUNTER or DERIVE (rrdtool info).
It would seem that showgraph uses an [mrtg] section in graphs.cfg to determine how to display network traffic. This configuration causes data from the RRD file to be fetched, then multiplied by 8, to turn it into bits. This all seems fine, and should produce the desired results, as long as the RRD data is stored in bytes.
J
participants (2)
-
jeremy＠laidman.org
-
scarville＠lereta.com