On 10/08/07, Dominique bastien <[EMAIL PROTECTED]> wrote: > I curently updating a MIB to add the functionality of > row creation. I add to the table definition the > RowStatus with the ACCESS set to read-create. But I > want to know if I have to change the other read-write > entries pf the table to read-create.
You can't actually do it that way. (At least, not according to a strict reading of RFC 2578) Two sections are relevant here: a) Section 7.3. states that writable column objects must either all be "read-write" or all be "read-create". You can't have a mixture of the two. So at first sight, that would imply that the existing read-write column objects do indeed need to be changed to read-create. However, section 10 lists the changes that can legitimately be made to a published MIB object. This does *not* include changing the MAX-ACCESS values. So strictly speaking, you should deprecate the whole table, and define a completely new one. If you haven't yet released the original MIB file (or aren't too bothered about playing fast-and-loose with existing applications based upon it), then you might be able to get away with updating the MAX-ACCESS clauses to be 'read-create'. But it's not strictly legit. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
