Re: ENUM syntax type

Thanks Dave.

Yes, you right. But As per my requirement I want 0 and 1 instead of 1
and 2. That is reason I want to change this type from TruthValue to
ENUM.

Thank you again.

Thanks,
Harendra

"Sometimes there is a difference between theory and practice. The
difference between theory and practice in theory is not as large as the
difference between theory and practice in practice."

On Mon, 2009-04-06 at 12:58, Dave Shield wrote:

> 2009/4/6 Harendra Pratap Singh <[email protected]>:
> > operStatus OBJECT-TYPE
> >    SYNTAX TruthValue
> 
> If you are defining an object with the syntax TruthValue,
> then this means that it takes the values
>     true(1)
> or
>     false(2)
> 
> See the definition in SNMPv2-TC
> 
> >    DESCRIPTION
> > " This object reflects whether endpoint has been re-instated
> >       into service or is out of service. If the value of this
> >       object is 'up', service has been re-instated. If the
> >       value is down', it is out of service."
> 
> This description is misleading.
> TruthValue takes values of 'true(1)' or 'false(2)'
> 
> 
> > can't I substitute TruthValue with( INTEGER{  down(0),  up(1) } ) instead of
> > defining TEXTUAL-CONVENTION.
> 
> Yes
> 
> There are numerous examples of this in the standard MIBs.
> (For example,   ifType, ipForwarding, ipRouteType, ipRouteProto,
>    ipNetToMediaType, tcpRtoAlgorithm, tcpConnState,
>    egpNeighState, snmpEnableAuthenTraps
>          in RFC1213 alone).
> 
> Dave

------------------------------------------------------------------------------

_______________________________________________
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