Thanks for the info:
because no Gauge64 nor Unsigned64 base types are defined, so 
CounterBasedGauge64 and ZeroBasedCounter64 textual conventions are defined in 
RFC 2856.

--- On Thu, 5/28/09, Mike Ayers <mike_ay...@tvworks.com> wrote:

> From: Mike Ayers <mike_ay...@tvworks.com>
> Subject: RE: Is Gauge64 defined in the snmp standard?
> To: "Vincent Bernat" <ber...@luffy.cx>, "PoWah Wong" <wong_po...@yahoo.ca>
> Cc: net-snmp-users@lists.sourceforge.net
> Received: Thursday, May 28, 2009, 7:44 PM
> > From: Vincent Bernat [mailto:ber...@luffy.cx] 
> > Sent: Thursday, May 28, 2009 2:51 PM
> 
> > OoO En ce début  de soirée du jeudi 28 mai
> 2009,  vers 21:23, 
> > PoWah Wong
> > <wong_po...@yahoo.ca>
> disait :
> > 
> > > Is Gauge64 defined in the snmp standard?
> > 
> > It is not  part of SMIv2. You can  use
> CounterBasedGauge64 
> > instead which
> > is a textual convention over Counter64. It is defined
> in 
> > HCNUM-TC and in
> > RFC 2856.
> 
> [SNIP]
>    CounterBasedGauge64 ::=
> TEXTUAL-CONVENTION
>      STATUS   
>    current
>      DESCRIPTION
>            "The
> CounterBasedGauge64 type represents a non-negative
>            integer,
> which may increase or decrease, but shall never
>            exceed a
> maximum value, nor fall below a minimum value. The
>            maximum value
> can not be greater than 2^64-1
>        
>    (18446744073709551615 decimal), and the
> minimum value can
>            not be
> smaller than 0.  The value of a CounterBasedGauge64
>            has its
> maximum value whenever the information being modeled
>            is greater
> than or equal to its maximum value, and has its
>            minimum value
> whenever the information being modeled is
>            smaller than
> or equal to its minimum value.  If the
>            information
> being modeled subsequently decreases below
>            (increases
> above) the maximum (minimum) value, the
>        
>    CounterBasedGauge64 also decreases
> (increases).
> 
>            Note that
> this TC is not strictly supported in SMIv2,
>            because the
> 'always increasing' and 'counter wrap' semantics
>            associated
> with the Counter64 base type are not preserved.
>            It is
> possible that management applications which rely
>            solely upon
> the (Counter64) ASN.1 tag to determine object
>            semantics
> will mistakenly operate upon objects of this type
>            as they would
> for Counter64 objects.
> 
>            This textual
> convention represents a limited and short-term
>            solution, and
> may be deprecated as a long term solution is
>            defined and
> deployed to replace it."
>      SYNTAX Counter64
> [/SNIP]
> 
>     Translation:  Danger, Will
> Robinson, danger!
> 
> 
>     HTH,
> 
> Mike
> 


      __________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your 
favourite sites. Download it now
http://ca.toolbar.yahoo.com.

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to