[mrtg] Re: MRTG methodology

[Paul C. Williamson]

I would agree.  Unless the ifOperStatus happened to be ISDN.

Paul

>>> "Dana Hudes" <dhudes at hudes.org> 09/28/01 09:30AM >>>
If you are using the 5 minutes to poll for dead things, certainly that's an appropriate interval.
If you are using it for capacity planning, you don't need that fine level of resolution.
There is no need to use MRTG to poll ifOperStatus.
I could see using it to send an alert based on ifInErrors though.

----- Original Message ----- 
From: "Paul C. Williamson" <pwilliamson at mandtbank.com>
To: <dhudes at hudes.org>; <mrtg at list.ee.ethz.ch>
Sent: Friday, September 28, 2001 9:23 AM
Subject: [mrtg] Re: MRTG methodology


> 5 minutes is an awful lot of polling?  Not hardly.  That's the 
> standard for network management services of just about 
> anything I can think of (HPOV, NetView, etc.)  5 seconds 
> would be too much, 1 minute would be a lot.  5 minutes is 
> hardly a blip on the radar screen.  I've had to fight to get my 
> NOC to understand that anything more often than 5 minutes, 
> and they won't have time to process the alerts, anything more 
> and they risk being late to the party (whatever that error or fault 
> may be).
> 
> Paul
> 
> >>> "Dana Hudes" <dhudes at hudes.org> 09/28/01 09:06AM >>>
> btw 5 minutes is an awful lot of polling. consider whether you can live with
> less fine-grain information. I run now at 15 minutes monitoring an E1, but if you have a T3 that would
> not be a good idea.
> 



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