[mrtg] Re: MRTG Bandwidth Limits?

Alex Nguyen anguyen at videotron.net
Tue Nov 19 02:11:09 MET 2002


Specify the version 2 in the Target cfg line.

You can find in the MRTG CFG Reference :

Extended Host Name Syntax

In all places where ``community at router'' is accepted, you can add
additional parameters for the SNMP communication using colon-separated
suffixes. The full syntax is as follows:

community at router[:[port][:[timeout][:[retries][:[backoff][:version]]]]]

where the meaning of each parameter is as follows:

port	the UDP port under which to contact the SNMP agent (default: 161) 

timeout	initial timeout for SNMP queries, in seconds (default: 2.0) 

retries	number of times a timed-out request will be retried (default: 5) 

backoff	factor by which the timeout is multiplied on every retry (default: 1.0). 

version	for SNMP version if you have a fast router you might want to put a
	'2' here. This will make mrtg try to poll the 64 bit
	counters. And thus prevent excessive counter wrapping. Not all
	routers support this though. 


 3:public at router1:::::2

A value that equals the default value can be omitted. Trailing colons can
be omitted, too.


On Tue, 19 Nov 2002, Michael Bailey wrote:

MB> Date: Tue, 19 Nov 2002 00:33:29 +0000
MB> From: Michael Bailey <michael at 67mustang.co.uk>
MB> To: 'Alex Nguyen' <anguyen at videotron.net>
MB> Cc: mrtg at list.ee.ethz.ch
MB> Subject: RE: [mrtg] Re: MRTG Bandwidth Limits?
MB> I might have similar problem.
MB> How do you set up using 64bit counters
MB> Thanks
MB> Michael
MB> -----Original Message-----
MB> From: mrtg-bounce at list.ee.ethz.ch [mailto:mrtg-bounce at list.ee.ethz.ch]
MB> On Behalf Of Alex Nguyen
MB> Sent: 18 November 2002 18:19
MB> To: Jeff Strahl
MB> Cc: 'mrtg at list.ee.ethz.ch'
MB> Subject: [mrtg] Re: MRTG Bandwidth Limits?
MB> Jeff,
MB> Did you use 64bits counter instead of 32bits ?
MB> With 32bits counter, the counter will wrap within 300 seconds at
MB> ~114Mbps.
MB> A.
MB> On Mon, 18 Nov 2002, Jeff Strahl wrote:
MB> JS> Date: Mon, 18 Nov 2002 12:01:16 -0600
MB> JS> From: Jeff Strahl <Jeff.Strahl at grandecom.com>
MB> JS> To: "'mrtg at list.ee.ethz.ch'" <mrtg at list.ee.ethz.ch>
MB> JS> Subject: [mrtg] MRTG Bandwidth Limits?
MB> JS> 
MB> JS> 
MB> JS> We have been using MRTG for while now, but it is until recently, 
MB> JS> that we have had enough bandwidth on a couple of interfaces that we 
MB> JS> have identified a problem.  Now, let me first state, that I do not 
MB> JS> know if this is a reporting problem of MRTG, or a problem within our
MB> JS> router that we are polling.
MB> JS> 
MB> JS> The MRTG version that we are currently running is: 2.9.17
MB> JS> 
MB> JS> The interfaces experiencing the problem: OC3 POS & OC3 ATM (both 
MB> JS> reside within the same VIP4-80, within a Cisco 7507 router with dual
MB> JS> RSP4s)
MB> JS> 
MB> JS> The symptoms of the problem are whenever we hit our peak time, if 
MB> JS> the bandwidth exceeds ~110 Mb/sec, the graphs simply draw a flat 
MB> JS> line _very_ close to zero instead of the true bandwidth amount, for 
MB> JS> I have connected to the router during the time that this is seen, 
MB> JS> and the bandwidth stated via 'show interface POS4/1/0' is consistent
MB> JS> with what I would expect to be passing at that time.  Also, it 
MB> JS> should be stated, that I do not have MRTG configured to draw 
MB> JS> unknowns as zero (one of the reasons that this strikes me as odd).  
MB> JS> On the other hand, the ATM interface simply draws straight lines 
MB> JS> whenever this interface exceeds the stated amount of ~110 Mb/sec.  
MB> JS> Like I said, I don't know if this is a problem with MRTG, or the 
MB> JS> router, but I needed to start somewhere, and since it appears that 
MB> JS> the MRTG graphs are broken, rather than the manual reporting of the 
MB> JS> router, I decided to start here.
MB> JS> 
MB> JS> I appreciate any insight anyone might have with this problem.
MB> JS> 
MB> JS> Thanks,
MB> JS> 
MB> JS> Jeff Strahl
MB> JS> 
MB> JS> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MB> JS> Jeff C. Strahl
MB> JS> Sr. IP Network Engineer
MB> JS> Packet Networks
MB> JS> Grande Communications Networks, Inc.
MB> JS> 401 Carlson Circle
MB> JS> San Marcos, TX 78666
MB> JS> Phone - 512.878.5465
MB> JS> Cell - 830.620.8176
MB> JS> Fax - 512.878.4284
MB> JS> Email: jeff.strahl at grandecom.com
MB> JS> 
MB> JS> We will individually and as a Team:
MB> JS> 	-	Work cooperatively, delivering what we said we would
MB> JS> 	-	Be honest and truthful - showing respect for others
MB> JS> 	-	Be easy to do business with - internally and externally
MB> JS> 	-	Serve our customers and communities with passion and
MB> JS> commitment
MB> JS> For you, the world. 
MB> JS> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MB> JS> 
MB> JS> --
MB> JS> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
MB> JS> Archive     http://www.ee.ethz.ch/~slist/mrtg
MB> JS> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
MB> JS> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
MB> JS> 
MB> --
MB> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
MB> Archive     http://www.ee.ethz.ch/~slist/mrtg
MB> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
MB> 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

More information about the mrtg mailing list