[mrtg] Weired behavior of MRTG
Koelstra, J. (Jan)
JKoelstra at MINSZW.NL
Mon Sep 10 14:25:02 CEST 2007
Peter,
I might be wrong, but when seeing the irregularities in the graph I would say the polling of the data is not regular at the time of the little tremours in the graph.
Normally MRTG deals with delayed polls by calculating the time between the last and the previous poll. With aggregated targets however there is no exact polling time that is valid for all three targets. In stead the stored polling time is the time when the last target reported it's data.
Do you start mrtg with a log file? (To do so add --logging=<file name>)
If so, are there any messages from missed polls or retries in the log file?
Some things that can cause the polling to be irregular: Congestion in the network between your MRTG box and the target, or an heavily loaded MRTG box, ...
To avoid problems in graphs with aggregated bandwith you have to switch to RRDtool for your backend, store the bandwith of the individual targets, and create the aggregated graph with a frontend like routers2.cgi.
In this way all calculattions for counter rollovers, offset polling time etc. is done before the data is summarized.
HTH,
Jan.
-----Original Message-----
From: mrtg-bounces at lists.oetiker.ch [mailto:mrtg-bounces at lists.oetiker.ch] On Behalf Of Peter
Sent: Monday, September 10, 2007 12:59 PM
To: mrtg at lists.oetiker.ch
Subject: [mrtg] Weired behavior of MRTG
Dear all
I'm using mrtg 2.11.1 and i have the following
problem;
As you can see in the attached image (img0.png,
img0-w.png), every day at the same time period i have
this strange increase and decrease of the bandwidth.
This is not normal, because when i'm checking each
interface separately (img1.png, img2.png, img3.png),
it seems that everything works ok. I have also
crosschecked with the other end (my customer) and he
doesn't see any problem on his graphs...
Bellow you can find my cfg file which produced the
img0.png and img0-w.png
WorkDir: /usr/local/apache/htdocs/mrtg/cust/otenet
Options[_]: growright, bits, transparent, noborder,
nobanner, nolegend
ThreshDir: /var/log/mrtg-thresh
### Interface 42 ###
Target[ath-CiscoRouter-02_XXX_all3]:
\GigabitEthernet4/0/0:mycommunicty at ath-CiscoRouter-02:::::2
+
\GigabitEthernet0/0/0:mycommunicty at ath-CiscoRouter-03:::::2
+
\GigabitEthernet1/0/0:mycommunicty at ath-CiscoRouter-04:::::2
SetEnv[ath-CiscoRouter-02_XXX_all3]:
MRTG_INT_IP="62.XX.XX.XXX" MRTG_INT_DESCR="XXX ALL"
MaxBytes[ath-CiscoRouter-02_XXX_all3]: 3737500000
ThreshMaxO[ath-CiscoRouter-02_XXX_all3]: 1437500000
ThreshProgO[ath-CiscoRouter-02_XXX_all3]:
/var/log/mrtg-thresh/XXX.sh
Title[ath-CiscoRouter-02_XXX_all3]: XXX ALL
PageTop[ath-CiscoRouter-02_XXX_all3]: <H1>XXX ALL</H1>
<TABLE>
<TR><TD>Customer ID</TD>
<TD>01-XXX-XXXX</TD></TR>
<TR><TD>Service ID</TD> <TD>XXXX</TD></TR>
<TR><TD>Description:</TD><TD>XXX_all *** 3x10GB *** </TD></TR>
<TR><TD>Speed:</TD> <TD>30 Gb</TD></TR>
</TABLE>
----
Today, i removed the Threshold feature (i have placed
it at 11.5GB/sec) and i will monitor it, but i don't
think that the problem begins from the Trheshold
checking... Any advise? does anyone else faced the
same problem or a similar issue?
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's
Comedy with an Edge to see what's on, when.
http://tv.yahoo.com/collections/222
_________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
_________________________________________________________
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The state accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
_________________________________________________________
More information about the mrtg
mailing list