subsequent calls to agent after 1st snmpset doesn't get received at agent.

Hi All,

I am facing one strange issue with snmpset commands on some of the MIB
objects (These usually take a bit more time to execute but i have
increased the time delay by option -t 10, which provides enough delay
for me to get the results even then this problem exists.)

On executing snmpset command for these MIB object gets the reply from
the snmpagent for the first time, but the subsequent calls for get and
set commands to the snmpagent does't get any response from the agent.

The observations made are as follows,
When I issue a set on "mib-object1"  

[vmgadag@localhost vmgadag]$ snmpset -v2c -t 10 -c private
192.168.100.140 .1.3.6.1.4.1.12622.2.12.1.5.0 s "hello"
SYSCONF-MIB::mib-object1.0 = STRING: hello
[vmgadag@localhost vmgadag]$ snmpset -v2c -t 10 -c private
192.168.100.140 .1.3.6.1.4.1.12622.2.12.1.5.0 s "hello1"
Timeout: No Response from 192.168.100.140
[vmgadag@localhost vmgadag]$ snmpwalk -v2c -t 10 -c private
192.168.100.140 .1
Timeout: No Response from 192.168.100.140
[vmgadag@localhost vmgadag]$ snmpwalk -v2c -t 100 -c public
192.168.100.140 .1
Timeout: No Response from 192.168.100.140

1. The PID of the hostapd & dhcpc get changed. (they get restarted )
2. When IP address of the Board is set statically the same observation
repeates, but a flushing of the command is observed. That is assume that
the first snmpset has been issued & the reply is obtained. When I issue
the second snmpset command there will be no response from the snmpagent.
Later on if I issue 
"set interface br0 static-ip 192.168.100.140"              on serial
console
I can see the code associated with the second snmp command getting
executed since some debug statements I have inserted scroll on the
serial port at this point of time.
3. If I issue "set interface br0 static-ip 192.168.100.140" or "set snmp
status up" command, while snmpmaster is still waiting for the response,
then I would get the proper response at the master.

Is this something like port getting closed or etc.
Is that some bady has allready seen these kind of issues with net snmp.
Any suggestions please.. 

Thanks & Regards,
Gadag






-------------------------------------------------------DISCLAIMER------------------------------------------------------
The information transmitted herewith is confidential and proprietary information intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
---------------------------------------------------------------------------------------------------------------------------