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

On 28/01/2008, Manfred Wassmann <[email protected]> wrote:
> The current design is that there is one OID where I can query the current
> version of a device and a second OID where I can set a Version to be
> updated.

something like:

    versionCurrent   OBJECT-TYPE
          MAX-ACCESS   read-only
          DESCRIPTION  "The current version of the device"
             :

     versionToUpdate   OBJECT-TYPE
            MAX-ACCESS  read-write
            DESCRIPTION
  "Setting the value of this object will (automatically?) trigger the
   updating of the device to the specified version.   Reading this
   object will return {WHAT?}.  {How to indicate errors}."


?

Note that it's probably worth including information in the
DESCRIPTION clause about what the result of reading the
second "write-only" object should be.   Also, perhaps mention
how this mechanism will indicate problems - e.g. specifying
a version to upload that is not valid, or is unavailable, or if the
upload fails for some reason.

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