Date: Wed, 11 Jan 2012 13:32:10 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Ott =?utf-8?Q?K=C3=B6stner?= <ottk@zzz.ee> Cc: freebsd-questions@freebsd.org Subject: Re: Network throughput Message-ID: <20120111193210.GF91606@dan.emsphone.com> In-Reply-To: <4F0DDB79.2010907@zzz.ee> References: <20120111112400.Horde.g4QFfgcXel9PDXFQSwJwfrA@webmail.geofront.co.uk> <4F0D7B87.9060808@zzz.ee> <4F0DA344.9030504@infracaninophile.co.uk> <4F0DDB79.2010907@zzz.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jan 11), Ott Köstner said: > On 11.01.2012 16:57, Matthew Seaman wrote: > > Yes -- mrtg is nice, but it relies on the snmp interface counters, and > > in this case with Gb traffic levels a 32bit counter will wrap in a few > > minutes. mrtg samples the interface counter every 5 minutes IIRC, so > > would probably be confused by that wrap-around happening at around the > > same frequency. Unless you switch to using 64bit interface counters, > > but I don't know if mrtg can cope with integer types that wide... > > Cheers, Matthew > > Yes, I have seen that wrapping with few hundred megabit port traffic. New > snmp port has 64 bit counter option. Personally, I have already built a > new snmp with 64 bit counter option, but not yet tested if it works. > Maybe somebody here can comment? Definitely works. You will have to tell mrtg to make SNMPv2 requests for the 64-bit OIDs to appear, but that's it. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120111193210.GF91606>