Dave,
It is working fine now. :-) The problem is for a Read-Write OID I didnt implement SET_ACTION,RESERVE1 etc., Now I fixed that issue. Moreover sysLocation and sysContact being a read-write oid, I configured them in snmpd.conf during agent configuration which will write-protect these oids. In this case, we are setting sysContact and sysLocation using our application. It created a problem. But now it is working fine. Thanks for your kind help. Thanks On 6/24/05, Dave Shield <[EMAIL PROTECTED]> wrote: > On Fri, 2005-06-24 at 07:33, aakansha rajvi wrote: > > > I want to capture the snmp packets alone as a result of snmpget > > and snmpset operations. > > I want to know how to frame the "tcpdump" command to do this. > > Untested, but something like > > tcpdump udp port 161 > > should do the trick. > You might want to add the option '-T snmp' if it's supported, > as that should format the SNMP packet more readably. > > Alternatively, you could use the option '-Ddump' to either the > SNMP agent, or the snmpget/set command, which would display the > packets as they're sent or received by the agent/client. > > Dave > > > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
