Jags S wrote: > The reason is latest SNMP requires .0 at the end of OID for set request.
Nonsense! Whatever gave you that idea? The sole instance of a *scalar* MIB object will always end in .0, which holds for both GET and SET requests. But entries within a table will use the index instances appropriate for that table (again for both GET and SET requests), and these need not end in .0. In fact, it's relatively unusual for such indexes to be precisely .0 > Using this application when do set, SNMP agent returns a error saying > "Set, Failed - SNMP: Variable does not exist, > 1.3.6.1.4.1.14399.20.12.1.108.3.1". The most likely cause of this error is that the agent doesn't support SET requests for that particular object - particularly if a GET request for the same OID succeeds. You don't say anything about which version of SNMP you are using - I suspect that you're using SNMPv1, since SNMPv2c and SNMPv3 would normally give a more informative error message. The OID that you're querying is not part of the standard Net-SNMP agent, so this is presumably an agent module you have developed yourself, or else one obtained from another vendor? In the latter case, you'll need to talk to that vendor. In the former case, you should look at the code you have written to implement SET requests. 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-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
