they shouldn't.. your only going to have a 32 bit or a 64 bit counter. So what happens when you get that counter full? your software craps out again?
The software needs to determine wether it's a 32 or 64 bit counter, and check to see if it's lowe than it was last time it was checked.
That was what I meant - some software will assume that the counter wrapped around and you get a ridiculous value if the counter didn't wrap but was reset instead.
Let's say that you poll the txframes value every 5 minutes, and you get this: previous_value = 1234567890 current_value = 1234
If the software assumes a 32bit unsigned counter (4294967295), and assumes that the counter wrapped, you get:
4294967295 - 1234567890 + 1234 = 3060400639 3060400639/60/5 = 10201335 txframes/sec
The SNMP poller/reporter/grapher needs to know more about the values
to be able to determine whether the above result is valid or not (for example a rule that says 'txframes per sec will never exceed 1000').
-- LarsG
The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org
