Hi Deve, Thanks for a quick response. I did some more investigations and found things are close to what you said. On the scenario I mentioned (snmpget from Machine B to A), the packet captures are as below. 1. Get from B to A (I was wrong early) 2. Report from A to B 3. Get on OID which I gave from B to A 4. Response from A to B.
1 and 2 got removed when I used -e <Context Engine ID> in the snmpget. Is there any other way I can avoid step 1 and 2 than explicitly setting the context engine ID? I think I am missing some authentication configurations. Thanks and regards -Ragesh -----Original Message----- From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield Sent: Thursday, February 05, 2009 6:25 PM To: Ragesh V Cc: net-snmp-users@lists.sourceforge.net Subject: Re: How can I remove get for for report?? 2009/2/5 Ragesh V <vrag...@hcl.in>: > The issue is explained below with machine A and machine B. > > Machine A : snmpd running > Machine B : Requesting set or get. > > On the command below on machine B. > snmpget -v3 -u <USERNAME> -n <USERNAME> -m <mymib> <IP machine A> <my > OID> > > The snmp network capture shows the below order for the single get > request in our lab. > > 1. Get from A to B Hmmm... Surely the GET is being sent *from* B *to* A ? That's what you've described above. In any case, if you look closely at a detailed dump of this request, you'll probably see that the securityEngineID is empty. The client typically doesn't know the engineID of the agent, so has to send a probe to discover this. > 2. Report from B to A This is an error message from the agent back to the client, saying "you didn't include a valid securityEngineID". But that report also includes the securityEngineID for the agent. > 3. Get from B to A This is a repeat of step 1, but with the securityEngineID field filled in. (using the value returned in step 2). > 4. Response from A to B. The request is now valid, so can be processed. > This is returning values in our test setup, but at client's setup the > report (step 2) is not sent by B to A and the get/set fails. Hmmmm.... That sounds wrong. If the agent receives a request with an invalid (or missing) securityEngineID, then it ought to return a Report-PDU to indicate this fact. Is your client running the Net-SNMP agent, or some other agent? What happens if you explicitly supply the engineID as an option to the "snmpget" command? Dave DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ----------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
