Re: Is there a standard type Unsigned64 or Interger64?
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <CAKoMtGZrAYFpw-=sLsO7E=MViOC0-ZgHOWyb_z63oijXm8jJag@mail.gmail.com> |
On 22 August 2012 08:08, Naama Bar Menachem <[email protected]> wrote: > If I need an unsigned integer of size 64 bit, why not simply use Counter64? Because of the semantics of this type. The two Counter types (32 and 64-bit versions) are designed for monitoring changing values - there is no defined starting value and the object can easily wrap without warning. This means that a single value of a Counter object has no meaning - you can only legitimately work with the *difference* between two Counter values. If you require a MIB object that can report a _single_ 64-bit value, then you need some way of indicating that the usual Counter semantics don't apply. That's the purpose of the HCNUM-TC.txt:CounterBasedGauge64 type that Wes mentioned. It effectively says "I know this looks like a counter, but it's not really" Anything to add, Wes? Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users