[mrtg] Re: Wrong log entries when using high AbsMax-option?
Alex van den Bogaerdt
alex at slot.hollandcasino.nl
Wed Sep 19 23:43:35 MEST 2001
Christoph Wagner wrote:
> The reason for using the AbsMax of 1024Mbit/s was that this is the highest
> bandwidth we have. So I could set AbsMax[_] as global option for all
> interfaces (about 1000 are monitored) and all devices (would work fine with
> cfgmaker-script).
IMHO you could as well skip the AbsMax setting altogether unless the
bigger part of the links are capable of actually doing 1024Mbps.
It is designed to avoid that 80Mbps spike but it needs to be set below
80 to be able to do so.
> But since the problem with inactive device showing 1 percent cpu util within
> MRTG2-9-17(by gauge-option) I am not sure if MRTG is not the thing causing
> my problems.
I've heard to many reports of things going wrong to say it doesn't happen.
There seems to be something wrong with the (-1) value written to the logs
when a failure occurs. Perhaps there's a kind perl-native who can look
into it?
cheers,
--
__________________________________________________________________
/ alex at slot.hollandcasino.nl alex at ergens.op.het.net \
| work private |
| My employer is capable of speaking therefore I speak only for myself |
+----------------------------------------------------------------------+
| Technical questions sent directly to me will be nuked. Use the list. |
+----------------------------------------------------------------------+
| http://faq.mrtg.org/ |
| http://rrdtool.eu.org --> tutorial |
+----------------------------------------------------------------------+
--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive http://www.ee.ethz.ch/~slist/mrtg
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
More information about the mrtg
mailing list