Alex, I pointed out what I was observing and where I thought the problem was. As I see it, when using SNMPv2 against a bunch of cisco routers here, some interface speeds are being reported incorrectly by mrtg, and yes, I consider this a bug. I see that cfgmaker seeks to make a bunch of decisions about what the correct values should be, and I see that there is some attempt in the code to adjust to improper values. My assertion is that it is not handling this particular case, and that I do not see an obvious fix for the problem, thus my attempt to document what I'm observing so that someone who is more familiar with the code can offer either a fix or advice.
Given the number of cisco routers out there, what is your opinion of the problem that I've reported? Are my observations and judgment off base? --Larry On Tue, Nov 23, 2004 at 10:00:19AM +0100, Alex van den Goaded wrote: > On Mon, Nov 22, 2004 at 03:44:23PM -0600, Larry Fahnoe wrote: > > > Recently I started using SNMPv2 queries to talk to some of my routers > > by passing --snmp-options=:::::2 to cfgmaker (2.10.15), and while this > > works well for many interfaces, on some I'm getting speeds that are > > too high. It looks like cfgmaker is being too trusting of the value > > it gets from ifHighSpeed. > > So to summarize: > The device is reporting a wrong value and you blame cfgmaker ? > > Alex -- Larry Fahnoe, Fahnoe Technology Consulting, [EMAIL PROTECTED] 952/925-0744 Minneapolis, Minnesota www.FahnoeTech.com -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg-developers
