RE: Regarding obsolete and not-accessible objects
"Pamidipati Suresh-G20238" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Dave & Subrahmanya, Thanks for your reply. Regards, Suresh. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield Sent: Tuesday, October 24, 2006 4:34 PM To: Subrahmanya Hegde Cc: Pamidipati Suresh-G20238; [email protected] Subject: Re: Regarding obsolete and not-accessible objects On 24/10/06, Subrahmanya Hegde <[email protected]> wrote: > One should not register both these objects with the agent. Correct. The agent should handle such "missing" objects automatically. > If I remember correctly, agent will reply with NO SUCH INSTANCE for > these. No. The agent should *not* return 'noSuchInstance' in either case. > Hence whether it is GET or SET, return code will be NO SUCH INSTANCE. For a GET, the agent should return the exception 'noSuchObject'. For a SET, the agent should return the error 'notWritable' - see RFC 1905, section 4.2.5, clause (2) There are *NO* circumstances where 'noSuchObject' or 'noSuchInstance' would be appropriate responses to a SET request. 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