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

On Tue, 22 Jan 2008, Dave Shield wrote:

> On 21/01/2008, Manfred Wassmann <[email protected]> wrote:
>>               I actually have at least two instances of myVersion
>> but they have to have different access clauses, so I guess I can't put
>> them into one table.
>
> Not so - remember that the access clause is actually MAX-ACCESS.
> So you could have a MAX-ACCESS of read-write (or read-create) for
> the column object, and explain any further restrictions in the relevant
> description field.
>
>   It's a bit difficult to give more precise advise without knowing more
> about what exactly you are trying to do.

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. There may be other instances of version numbers in the future but 
they are limited to these two. I.e. the two instances are rather 
unrelated - you either get the first or set the second - so I think it is 
more appropriate not to put them into one table. The stuff is v3 only (the 
read-write part, at least) and I thought about using the 
SNMP-USM-DH-OBJECTS-MIB to have the agent and manager negotiate a password 
for read-write access so I don't have to store that password anywhere on 
the device but I still have to work that out.

Regarding the type concept in SNMP I think that is clear to me now thanks 
to your answers.

Regards Manfred

-------------------------------------------------------------------------
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