[mrtg] Re: Forking MRTG

[Jason Frisvold]

Well, everyone else is chiming in, I might as well..  :)

Our strategy here is to break it down by equipment and by oid.  I
currently have 35 instances of MRTG running on various items from
traffic on ATM switches and Routers, to discards and errors.

I was experimenting with the forking because some of the larger configs
that aren't broken down by line size are, obviously, taking a long time
to run.  I figured forking would help the situation...  I guess I need
to take all the others offline long enough for me to check if forking is
really working..  :)

It's taken me a while to get this system in place, but it's quite
elaborate...  If anyone's interested in how we handle everything, feel
free to email me...  :)

---------------------------
Jason H. Frisvold
Senior ATM Engineer
Engineering Dept.
Penteledata
CCNA Certified - CSCO10151622
friz at corp.ptd.net
---------------------------
"Imagination is more important than knowledge. Knowledge is limited.
Imagination encircles the world." -- Albert Einstein [1879-1955]


-----Original Message-----
From: Garry Cook [mailto:Garry.Cook at mactec.com] 
Sent: Monday, June 03, 2002 11:51 PM
To: Tobias Oetiker; Greg.Volk at edwardjones.com
Cc: mrtg at list.ee.ethz.ch
Subject: [mrtg] Re: Forking MRTG

What I've done to combat this issue is to break my network up into
regions. Each region has a separate MRTG daemon that calls a regional
config file. The regional config file contains all of the global config
commands, an include line for each device, and 'n' forks, 'n' being
equal to the number of devices. With one fork for each device, it seems
to work much better, but I believe that the issue still occurs (luckily,
I have not had to test this theory recently).
I also edited my crontab to check for all 7 daemons at five minute
intervals and restart if necessary. If cron has to restart a process, it
emails me to let me know.
 
Tobi, it sounds as if you plan to implement the skipping of queries to
known dead hosts. Would this include some type of notification to let
users know that a problem was encountered?
 
-garry
 
>>> your problem with the router going offline does not get solved by
>>> this ... but it does not become worse either. What could be done
>>> about it is to make mrtg kill all other queries to the same host if
>>> one comes back without answer ... would this help ?
>>>
>>
>> That would be very useful to be able to skip queries to known
>> dead hosts. Is there a global config command that does this?
>
>not yet :-)
>
>tobi

 

--
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

--
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