Re: Problem with defining custom data type (TEXTUAL-CONVENTION)

On 19/01/2008, Manfred Wassmann <[email protected]> wrote:
> I'm trying to use a custom data type for storing version information
> composed of three numbers and a release state:


>      MyVersionNumber ::= SEQUENCE {
>          myVersionDigits MyVersionDigits,
>          myVersionState MyVersionState
>      }
>
>      myVersion OBJECT-TYPE
>      SYNTAX MyVersionNumber


> but smilint complains

> So what is the correct way to handle this?

If you will only have one instance of this "myVersion" value,
then define two scalar objects - myVersionDigits and
myVersion.  If you might have multiple instances of these
values, then you'd define a table with these as the columns.

But part of the "Simple" in SNMP is that it doesn't actually
support user-defined structures - you've got single instances
and tables, and nothing else.
   Any higher-level structuring needs to be imposed on top
of this, by suitable MIB-specific applications.   As far as the
MIB and agent are concerned, the version number and the
state are separate objects.

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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