Sorry for the top posting.. my work enforced client doesn't like to give me any other options. Anyway..
I am actually running at a 5 minute interval which, by the calculation you posted Alex, shows ~115 megabit per second, which was what I was typically seeing. I ran some quick tests, and the devices I'm monitoring all appear to support the ifHC OID. I'm doing some further testing to ensure it won't break any graphs, but so far, using the 64 bit counters appears to be working fine. From the responses I've received, it appears that is likely to be the cause of the issue (which I very much appreciate, as I don't think I would have come to that conclusion for quite some time.) -- Simon Westlake Time Warner Cable Business Class Network Engineer Ph: 414.908.4791 | Cell: 414.688.7956 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex van den Bogaerdt Sent: Monday, March 19, 2007 8:46 AM To: [email protected] Subject: Re: [rrd-users] Bits to Bytes.. trying to figure out what'shappening On Mon, Mar 19, 2007 at 09:31:42AM -0400, Dan Cech wrote: > Westlake, Simon wrote: > > In my gig test yesterday, I was hitting between 930 and 970 megs per > > second on the packet generator, and the 5 minute input/output rate on > > the switch interface confirmed this to be accurate. However, my graphs > > show anywhere between 100 and 115 megs. At first, I wondered if it was > > some type of 'MaxBytes' problem in MRTG, so I changed that value to a > > very large amount and it didn't rectify it. I then realized that 115 > > megabytes was ~964 megabit. > > Simon, > > ~115Mbps is also around the point where you'll max out 32bit SNMP > counters with a 1 minute polling interval, as you'll have multiple > rollovers per minute. > > Are you using 32bit or 64bit (SNMPv2c ifHCInOctets & ifHCOutOctets) > counters? If you're not using 64bit counters I'd recommend switching to > them and suspect it would solve your problem. Almost agree, except that this happens with a 5 minute polling interval: 2^32 = 4294967296 4294967296 bytes / 300 seconds = 14316557 bytes per second (Bps) 14316557 Bps * 8 bits per byte = 114532456 bits per second (bps) Temporarily switching to a one minute polling interval (I think you can keep "step" to 300, no problem): 2^32 = 4294967296 4294967296/60 = 71582788 71582788*8 = 572662304 -> able to monitor 570 Mbps This buys you some time to see if and how you can use the HC counters. HTH -- Alex van den Bogaerdt http://www.vandenbogaerdt.nl/rrdtool/ _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users ----------------------------------------- This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
