Re: Regarding obsolete and not-accessible objects
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 23/10/06, Pamidipati Suresh-G20238 <[email protected]> wrote: > What should be the error code to be returned for a set request on > 1. an object whose STATUS is defined as obsolete > 2. an object whose MAX-ACCESS is defined as not-accessible If an object is defined as "obsolete", then this basically mean you don't have to implement the object at all - the object doesn't exist any more. In an object is defined as MAX-ACCESS not-accessible, then again, it's as if that object doesn't exit. > [From RFC 1905] > (9) Otherwise, if the variable binding's name specifies a variable which exists... So this particular clause is not relevant - the objct does *not* exist as far as clients are concerned. > Please let me know if this (notWritable) is correct or noAccess has to be > returned for the above 2 cases. Neither. Dave ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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