Robert, or any net-snmp expert there, I googled the following old discussion about "SET ROW". Does net-snmp support this kind of "set row" operation now? Does net-snmp support any kind of operation that an SNMP manager can creat a new row and set values for all columns with one snmp message? Thanks, Richard
=============================================================================
To: David Battle <[EMAIL PROTECTED]>, "David T. Perkins" <[EMAIL PROTECTED]>
Subject: Re: What is "SET ROW" / making SETs easier
From: Robert Story <[EMAIL PROTECTED]>
Date: Fri, 30 Mar 2001 14:57:28 -0500
Cc: [EMAIL PROTECTED]
Delivery-date: Fri, 30 Mar 2001 12:13:34 -0800
Envelope-to: [EMAIL PROTECTED]
--------------------------------------------------------------------------------
At 2:56 PM -0800 3/27/01, David Battle wrote: >I believe that the idea for this feature came from >Andy Bierman's complaint that one of the reasons >snmp SET's aren't more widely implemented is the need >for the agent to accept pieces of a row in any order. > I don't think that SET ROW helps implementing row sets very much, because it wouldn't change the general SNMP rule that all sets must occur "as if simultaneous." If we want to make SETs easier to implement, we should allow implementations to specify varbind ordering (see SMING WG), or simply process them in the order they appear in the PDU, and reject SETs that don't follow the constraints. Not only would this help for cases where a SET contains varbinds for multiple tables when there is a dependency between tables, but would also allow a row that must be nonInService to be updated to be updated with a single PDU ( status=notInService, colX=newValue, status=active ).
>At 12:00 PM 3/27/2001, you wrote: >>Would someone PLEASE explain: >> 1) what a SETROW operation would do,
I think it could allow more varbinds per PDU via OID compress/suppression.
>> 2) what problems does it solve
it doesn't necessarily solve the problem, but it would certainly help in a lot of cases.
>> 3) what problems does it create >> Hmm... error reporting? If each row is encoded as a sequence, you have indicate the row and the column that caused the error.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
