> After building the agent, I am doing snmpwalk from 0.0 which results in > "noSuchName" error. Please let me know, is this a bug in the Agent API's??
It's not a bug in the agent, no. But it could well be regarded as a flaw in the 'snmpwalk' application. What's happening is that snmpwalk starts by sending a GETNEXT request for the specified OID (.0.0). This will return a response for the first MIB object that the agent implements - probably sysUpTime.0 But that OID will start .1.3.6.1... which lies outside the specified OID subtree. So the snmpwalk command discards this result, and doesn't print it. Because this is the *first* request that 'snmpwalk' has send (and it failed), then it doesn't have any results to report. So it tries one last time with a GET request for the same OID (.0.0). This also fails (since there isn't a MIB value for that object), returning a 'noSuchName' error. It's this error that you're seeing. Given the protocol operations involved, this result is not unexpected, but it's certainly confusing if you're not familiar with the underlying workings of the tool. It would probably be better not to display this particular error message (and the equivalent SNMPv2c/3 'noSuchObject' exception) Note that with the latest code (which will become 5.2) you'll be able to turn off this final GET call, using the option -CI Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
